System and method for automating aviation fuel supply

Abstract

The present disclosure provides a system (106) and a method (600) for automating aviation fuel supply. The system (106) determines one or more fuelling services located at one or more locations. The system (106) receives a schedule plan associated with navigation of one or more vehicles. The system (106) facilitates fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan. The system (106) records information associated with the fuel supply to the one or more vehicles from the one or more locations. The system (106) automatically generates a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, where the FDN indicates cost associated with the fuel supply. The system (106) transmits the FDN to one or more users of the one or more fuelling services.

Description

SYSTEM AND METHOD FOR AUTOMATING AVIATION FUEL SUPPLYTECHNICAL FIELD

[0001] The present disclosure relates generally to the field of operational processes managing Aviation Turbine Fuel (ATF). In particular, the present disclosure pertains to a system and a method for automating aviation fuel supply.BACKGROUND

[0002] At present, all the operational processes of Aviation Turbine Fuel (ATF) through tank, trucks, and pipeline and further delivery through dispensers, refuellers are performed manually. This leads to various issues of product losses, requires excess manpower, incurs manual errors in preparing fuel delivery vouchers (FDV), improper logistics planning with huge costs, delayed invoicing, and operational delays. Existing processes involves manual operations of product receipts through tanks, manual dipping of tanks, creation of manual fuel delivery notes (FDNs) on flights, and keying all the data to generate invoices to the customers.

[0003] However, manual operations of product receipt through tanks leads to product losses. Manual dipping of aboveground tanks involves working on heights and safety related issues. Manual Creation of FDNs on flights involves writing errors leading to incorrect and delayed invoicing. Further, unavailability of real time data leads to improper logistics, manpower planning, and under-utilized assets.

[0004] Therefore, there is a well-established need to provide an improved system and method that overcomes the shortcomings associated with the conventional systems.OBJECTS OF THE PRESENT DISCLOSURE

[0005] An object of the present disclosure is to provide a system and a method for automating aviation fuel supply that determines fuelling services at multiple locations.

[0006] An object of the present disclosure is to provide a system that receives a schedule plan associated with navigation of one or more vehicles and facilitate fuel supply to the vehicles through the fuelling services based on the schedule plan.

[0007] An object of the present disclosure is to provide a system that records information associated with the fuel supply to the vehicles from the multiple locations.

[0008] An object of the present disclosure is to provide a system that automatically generates a fuel delivery note (FDN) associated with the fuel supply based on the recorded information.

[0009] An object of the present disclosure is to provide a system that transmits the FDN to users of the one or more fuelling services.SUMMARY

[0010] In an aspect, the present disclosure relates to an automation system. The automation system includes a processor and a memory operatively coupled with the processor where said memory stores instructions which, when executed by the processor, cause the processor to determine one or more fuelling services located at one or more locations. The processor receives a schedule plan associated with navigation of one or more vehicles. The processor facilitates fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan. The processor records information associated with the fuel supply to the one or more vehicles from the one or more locations. The processor automatically generates a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, wherein the FDN indicates cost associated with the fuel supply. The processor transmits the FDN to one or more users of the one or more fuelling services.

[0011] In an embodiment, the processor may be configured to transmit data associated with the one or more fuelling services to a cloud based server, where the data may include one or more parameters indicating supplying capacity associated with the one or more fuelling services.

[0012] In an embodiment, to determine the one or more fuelling services located at the one or more locations, the processor may be configured to use at least one of one or more gauges, an Internet of Things (loT) device, one or more controllers, and one or more digital flowmeters.

[0013] In an embodiment, the processor may be configured to record the information from the one or more digital flowmeters which indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

[0014] In an embodiment, to determine the amount of fuel delivered, the processor may be configured to use a touchpad device and the loT device to record the information associated with the fuel supply, wherein the information comprises any or a combination of a density parameter associated with the fuel, a temperature parameter associated with the fuel,one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.

[0015] In an aspect, the present disclosure relates to a method for supplying fuel. The method includes determining, by a processor, associated with a system, one or more fuelling services located at one or more locations. The method includes receiving, by the processor, a schedule plan associated with navigation of one or more vehicles. The method includes facilitating, by the processor, fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan. The method includes recording information, by the processor, associated with the fuel supply to the one or more vehicles from the one or more locations. The method includes automatically generating, by the processor, a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, where the FDN may indicate cost associated with the fuel supply. The method includes transmitting, by the processor, the FDN to one or more users of the one or more fuelling services.

[0016] In an embodiment, the method may include transmitting, by the processor, data associated with the one or more fuelling services to a cloud based server, wherein the data comprises one or more parameters indicating supplying capacity associated with the one or more fuelling services.

[0017] In an embodiment, for determining the one or more fuelling services located at the one or more locations, the method may include using, by the processor at least one of one or more gauges, an Internet of Things (loT) device, one or more controllers, and one or more digital flowmeters.

[0018] In an embodiment, the method may include recording, by the processor, the information from the one or more digital flowmeters which may indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

[0019] In an embodiment, for determining the amount of fuel delivered, the method may include using, by the processor, a touchpad device and the loT device to record the information associated with the fuel supply, where the information may include any or a combination of a density parameter associated with the fuel, a temperature parameter associated with the fuel, one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0021] FIG. 1 illustrates an example architecture 100 of a proposed system 106, in accordance with an embodiment of the present disclosure.

[0022] FIG. 2 illustrates an example block diagram 200 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0023] FIG. 3 illustrates an example architecture diagram 300 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0024] FIG. 4 illustrates an example solution architecture diagram 400 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0025] FIG. 5 illustrates an example process flow diagram 500 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0026] FIG. 6 illustrates an example flow diagram 600 of a method implemented by the proposed system 106, in accordance with an embodiment of the present disclosure.

[0027] FIG. 7 illustrates an exemplary computer system 700 in which or with which embodiments of the present disclosure may be implemented.DETAILED DESCRIPTION

[0028] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.

[0029] The present disclosure relates to a system that employs operational and accounting processes associated with field-level aviation fuelling stations. The system automates an entire journey of Aviation Turbine Fuel (ATF), from its receipt at the Aviation Fuelling Station (AFS) to its delivery at the wing tip, utilizing state-of-the-art technologies. By harnessing cloud-based data storage and integration, Internet of Things (loT) capabilities, and machine to machine (M2M) Subscriber Identity Module (SIM) connectivity, the system ensures seamless, real-time communication, and data transfer. Further, the system capturesand transmits refuelling data efficiently, and generates electronic fuel delivery notes (FDNs) ensuring comprehensive documentation.

[0030] Various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1-7.

[0031] FIG. 1 illustrates an example architecture 100 of a proposed system 106, in accordance with an embodiment of the present disclosure.

[0032] As illustrated in FIG. 1, in an embodiment, the system 106 may be communicatively coupled to one or more vehicles (102-1, 102-2... 102-N) via a network 104. A person skilled in the art may understand that the one or more vehicles (102-1, 102-2. . . 102- N) may also be referred as the vehicles 102 or the vehicle 102 throughout the disclosure. The vehicles 102 may include but not limited to aircrafts.

[0033] In an embodiment, the network 104 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 104 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0034] In an embodiment, the system 106 may determine one or more fuelling services located at one or more locations. The one or more fuelling services may include an Aviation Fuelling Station (AFS) that supplies aviation fuel to the aircrafts. The system 106 may transmit data associated with the one or more fuelling services to a cloud based server, where the data may include but not limited to one or more parameters indicating supplying capacity associated with the one or more fuelling services. The data may include but not limited to airport codes, aircraft types, aircraft registration information, city codes, payment card details, customer / user names, bay master, vehicle master, tank master, meter masters. This data may be recorded by the system 106 in the cloud based server.

[0035] In an embodiment, to determine the one or more fuelling services located at the one or more locations, the system 106 may use at least one of one or more gauges, an Internet of Things (loT) device, one or more controllers, and one or more digital flowmeters. Further, the system 106 may record the information from the one or more digital flowmeters whichmay indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

[0036] In an embodiment, the system 106 may record the data at the AFS locations / the one or more locations during the receipt of the ATF through tanks or pipeline transfer and ensure delivery of the fuel through pipelines. The system 106 may record tank stock / fuel stock data through one or more auto tank gauging devices.

[0037] In an embodiment, to determine the amount of fuel delivered to the aircraft, the system 106 may use a touchpad device and the loT device to record the information associated with the fuel supply, where the information may include any or a combination of a density parameter associated with the fuel, a temperature parameter associated with the fuel, one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.

[0038] In an embodiment, the system 106 may receive a schedule plan associated with navigation of the aircraft 102 / vehicle 102. The system 106 may facilitate fuel supply to the aircraft 102 / vehicle 102 through the one or more fuelling services based on the schedule plan.

[0039] In an embodiment, the system 106 may record information associated with the fuel supply to the aircraft 102 / vehicle 102from the one or more locations. Further, the system 106 may automatically generate a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, where the FDN may indicate cost associated with the fuel supply. The system 106 may transmit the FDN to one or more users of the one or more fuelling services / AFS.

[0040] Therefore in an embodiment, the system 106 minimizes non -accounting of daily stock and sales, minimizes uncontrolled product losses, and manages improper manpower planning. Further, the system 106 prevents delayed invoicing due to manual errors in the FDN writing and manual entries. The system 106 prevents an unsafe working environment of heights due to periodic manual dipping of tanks, mimeses improper logistic planning, and provides availability of real-time integrated data. The system 106 captures the data through various hardware and software interventions, where hardware intervention may be enabled through the one or more gauges, the Internet of Things (loT) device, the one or more controllers, and the one or more digital flowmeters.

[0041] FIG. 2 illustrates an example block diagram 200 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0042] Referring to FIG. 2, the system 106 may comprise one or more processor(s) 202 that may be implemented as one or more microprocessors, microcomputers, microcontrollers,digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 106. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0043] In an embodiment, the system 106 may include an interface(s) 206. The interface(s) 206 may comprise a variety of interfaces, for example, interfaces for data input and output (I / O) devices, storage devices, and the like. The interface(s) 206 may also provide a communication pathway for one or more components of the system 106. Examples of such components include, but are not limited to, processing engine(s) 208 and a database 210, where the processing engine(s) 208 may include, but not be limited to, a data ingestion engine 212 and other engine(s) 214. In an embodiment, the other engine(s) 214 may include, but not limited to, a data management engine, an input / output engine, and a notification engine.

[0044] In an embodiment, the processing engine(s) 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 208 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, the system 106 may comprise the machine -readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 106 and the processing resource. In other examples, the processing engine(s) 208 may be implemented by electronic circuitry.

[0045] In an embodiment, the processor 202 may receive a schedule plan associated with navigation of the vehicles 102 through the data ingestion engine 212. The processor 202 may record the schedule plan in the database 210. The processor 202 may determine one or more fuelling services located at one or more locations. The one or more fuelling services may include an Aviation Fuelling Station (AFS) that supplies aviation fuel to the aircrafts.

[0046] In an embodiment, the processor 202 may transmit data associated with the one or more fuelling services to a cloud based server, where the data may include but not limited to one or more parameters indicating supplying capacity associated with the one or more fuelling services. The data may include but not limited to airport codes, aircraft types, aircraft registration information, city codes, payment card details, customer / user names, bay master, vehicle master, tank master, meter masters. This data may be recorded by the processor 202 in the cloud based server.

[0047] In an embodiment, to determine the one or more fuelling services located at the one or more locations, the processor 202 may use at least one of one or more gauges, an Internet of Things (loT) device, one or more controllers, and one or more digital flowmeters. Further, the processor 202 may record the information from the one or more digital flowmeters which may indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

[0048] In an embodiment, the processor 202 may record the data at the AFS locations / the one or more locations during the receipt of the ATF through tanks or pipeline transfer and ensure delivery of the fuel through pipelines. The processor 202 may record tank stock / fuel stock data through one or more auto tank gauging devices.

[0049] In an embodiment, to determine the amount of fuel delivered to the aircraft, the processor 202 may use a touchpad device and the loT device to record the information associated with the fuel supply, where the information may include any or a combination of a density parameter associated with the fuel, a temperature parameter associated with the fuel, one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.

[0050] In an embodiment, the processor 202 may receive a schedule plan associated with navigation of the aircraft 102 / vehicle 102. The processor 202 may facilitate fuel supply to the aircraft 102 / vehicle 102 through the one or more fuelling services based on the schedule plan.

[0051] In an embodiment, the processor 202 may record information associated with the fuel supply to the aircraft 102 / vehicle 102 from the one or more locations. Further, the processor 202 may automatically generate a fuel delivery note (FDN) associated with the fuelsupply based on the recorded information, where the FDN may indicate cost associated with the fuel supply. The processor 202 may transmit the FDN to one or more users of the one or more fuelling services / AFS.

[0052] FIG. 3 illustrates an example architecture diagram 300 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0053] As illustrated in FIG. 3, in an embodiment, the architecture diagram 300 explains the relationships between the modules to achieve the complete functionality of the system 106. The architecture diagram 300 is a high-level associated with the tasks that were partitioned and assigned to subsystems. Further, architecture diagram 300 describes collaboration among subsystems in order to achieve a desired functionality.

[0054] In an embodiment, the system 106 may receive data associated with one or more third party systems 302. The system 106 may record the data in a cloud based database / server 304. The cloud based database / server 304 may include an application component 306, a web component 308, and an integration component 310 for processing the data.

[0055] In an embodiment, the system 106 may determine a station 312 / or one or more fuelling services 312. The system 106 may use one or more first devices 314 to record information association with the station 312. The system 106 may use a controller 316 to process the information from the one or more first devices 314 and transmit the processed information to an application programming interface (API) 318. The controller 316 may perform monitoring 316-A of the one or more first devices 314 and transmit the processed information.

[0056] In an embodiment, the system 106 may use a bowser / hydrant valve 320 and one or more second devices 322 with the bowser / 320 to transport and distribute fuel and use the hydrant valve 320 in case of fire related emergencies. The system 106 may further transmit information associated with the bowser / hydrant valve 320 to the API 318. Further, the system 106 may supply fuel to the aircraft 324 based on the schedule plan of the aircraft 324 on the air ground 326.

[0057] FIG. 4 illustrates an example solution architecture diagram 400 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0058] As illustrated in FIG. 4, in an embodiment, the system 106 may receive data associated with a client 402. The system 106 may receive information from a refueller / dispenser / aviation facility 404. The system 106 may use an loT controller 406 and a tablet 408 to record the information. The system 106 may further record information associated with internal / external users 410.

[0059] In an embodiment, the system 106 may transmit the data and information via internet 412 to a cloud security layer 414. Further, the system 106 may include an interface layer 416 that receives the data and information. The system 106 may include an integration layer 418 that integrates the data and information. The system 106 may include a processing layer 420 that provides data validation 422, data processing 424, data ingestion 426, and historical data 428. The historical data 428 may be recorded in one or more databases 430 and provided to a scheduler 432.

[0060] In an embodiment, the system 106 may further receive information from the cloud security layer 414 and the processing layer 420 to a presentation layer 434. The presentation layer 434 may include an accessible web portal 436. The system 106 may communicate information to an application server 438.

[0061] Further, in an embodiment, the system 106 may transmit the information from the integration layer 418 to one or more integration channels 440.

[0062] FIG. 5 illustrates an example process flow diagram 500 of the proposed system 106, in accordance with an embodiment of the present disclosure.

[0063] As illustrated in FIG. 5, in an embodiment, the system 106 may include a flight management schedule module 502. The flight management schedule module 502 may perform customer acceptance and digital signature in tablet 502-1. The flight management schedule module 502 may include a customer portal 504. The flight management schedule module 502 may maintain and create customer masters 506, record a flight schedule 508, record changes in the flight schedule 510, record information of non-scheduled flights 512, and delivery confirmation 514 associated with booked flights. The flight management schedule module 502 may create and maintain all masters required for fuel delivery 516 and upload file using an excel sheet 518.

[0064] Further, in an embodiment, the system 106 may include various details, where the details available to the customer 544 may include a fuel operation module 520 which may record tank stock availability 522, create a daily flight chart 524, determine refueller and hydrant stock 526 based on the tank stock availability 522. The fuel operation module 520 may record availability of driver and sales officer 528. The fuel operation module 520 may determine a daily flight plan 530 based on the uploaded flight schedule 518 and further enable allocation of resources 532. The fuel operation module 520 may create the FDV 542 based on the daily flight plan 530 and the allocation of resources 532. Further, the fuel operation module 520 may enable fuelling to flight 534 based on the allocation of resources 520 and further update all required details in the FDV 542 via a tablet 536. The details maybe updated in the FDV 542 based on the delivery confirmation 514. The fuel operation module 520 may provide FDV 542 corrections and transmit the FDV 542 for approval 538 with the required sales details 540 to the customer portal 504.

[0065] FIG. 6 illustrates an example flow diagram 600 of a method implemented by the proposed system 106, in accordance with an embodiment of the present disclosure.

[0066] In an embodiment, at step 602, the method may include, determining, by a system 106, one or more fuelling services located at one or more locations. At step 604, the method may include receiving, by the system 106, a schedule plan associated with navigation of one or more vehicles. At step 606, the method may include facilitating, by the system 106, fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan. At step 608, the method may include recording information, by the system 106, associated with the fuel supply to the one or more vehicles from the one or more locations. At step 610, the method may include automatically generating, by the system 106, a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, where the FDN may indicate cost associated with the fuel supply. At step 612, the method may include transmitting, by the system 106, the FDN to one or more users of the one or more fuelling services.

[0067] FIG. 7 illustrates an exemplary computer system 700 in which or with which embodiments of the present disclosure may be implemented.

[0068] As shown in FIG. 7, the computer system 700 may include an external storage device 710, a bus 720, a main memory 730, a read-only memory 740, a mass storage device 750, a communication port(s) 760, and a processor 770. A person skilled in the art will appreciate that the computer system 700 may include more than one processor and communication ports. The processor 770 may include various modules associated with embodiments of the present disclosure. The communication port(s) 760 may be any of an RS- 232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) 760 may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 700 connects.

[0069] In an embodiment, the main memory 730 may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 740 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basicinput / output system (BIOS) instructions for the processor 770. The mass storage device 750 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0070] In an embodiment, the bus 720 may communicatively couple the processor(s) 770 with the other memory, storage, and communication blocks. The bus 720 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 770 to the computer system 700.

[0071] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus 720 to support direct operator interaction with the computer system 700. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 760. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 700 limit the scope of the present disclosure.

[0072] While the foregoing describes various embodiments of the disclosure, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the disclosure is determined by the claims that follow. The disclosure is not limited to the described embodiments, versions, or examples, which are included to enable a person having ordinary skill in the art to make and use the disclosure when combined with information and knowledge available to the person having ordinary skill in the art.ADVANTAGES OF THE PRESENT DISCLOSURE

[0073] The present disclosure integrates an entire aviation operation right from the receipt of product in tanks to the delivery of the product in the wing tip of the aircraft with no manual inputs or intervention at any stage.

[0074] The present disclosure captures data on real time basis and enhances the decision making process in terms on manpower planning , logistics plarming, flight operationsplanning, optimum assets utilization, error free documentation, daily stock and sales accounting.

[0075] The present disclosure can be used in aviation, other hydrocarbon industries, petrochemical or chemical industries to capture all the stock movements and sales data as an end-to-end solution.

Claims

We Claim:

1. An automation system (106) comprising: a processor (202); a memory (204) operatively coupled with the processor (202), wherein said memory (204) stores instructions which, when executed by the processor (202), cause the processor (202) to: determine one or more fuelling services located at one or more locations; receive a schedule plan associated with navigation of one or more vehicles; facilitate fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan; record information associated with the fuel supply to the one or more vehicles from the one or more locations; automatically generate a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, wherein the FDN indicates cost associated with the fuel supply; and transmit the FDN to one or more users of the one or more fuelling services.

2. The system (106) as claimed in claim 1, wherein the processor (202) is configured to transmit data associated with the one or more fuelling services to a cloud based server, wherein the data comprises one or more parameters indicating supplying capacity associated with the one or more fuelling services.

3. The system (106) as claimed in claim 1, wherein to determine the one or more fuelling services located at the one or more locations, the processor (202) is configured to use at least one of: one or more gauges, an Internet of Things (loT) device , one or more controllers, and one or more digital flowmeters.

4. The system (106) as claimed in claim 3, wherein the processor (202) is configured to record the information from the one or more digital flowmeters which indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

5. The system (106) as claimed in claim 4, wherein to determine the amount of fuel delivered, the processor (202) is configured to use a touchpad device and the loT device to record the information associated with the fuel supply, wherein the information comprises any or a combination of: a density parameter associated with the fuel, a temperatureparameter associated with the fuel, one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.

6. A method for supplying fuel (600), the method (600) comprising: determining (602), by a processor (202), associated with a system (106), one or more fuelling services located at one or more locations; receiving (604), by the processor (202), a schedule plan associated with navigation of one or more vehicles; facilitating (606), by the processor (202), fuel supply to the one or more vehicles through the one or more fuelling services based on the schedule plan; recording information (608), by the processor (202), associated with the fuel supply to the one or more vehicles from the one or more locations; automatically generating (610), by the processor (202), a fuel delivery note (FDN) associated with the fuel supply based on the recorded information, wherein the FDN indicates cost associated with the fuel supply; and transmitting (612), by the processor (202), the FDN to one or more users of the one or more fuelling services.

7. The method as claimed in claim 6, comprising transmitting, by the processor (202), data associated with the one or more fuelling services to a cloud based server, wherein the data comprises one or more parameters indicating supplying capacity associated with the one or more fuelling services.

8. The method as claimed in claim 6, for determining the one or more fuelling services located at the one or more locations, comprises using, by the processor (202), at least one of: one or more gauges, an Internet of Things (loT) device, one or more controllers, and one or more digital flowmeters.

9. The method as claimed in claim 8, comprising recording, by the processor (202), the information from the one or more digital flowmeters which indicate an amount of fuel delivered to the one or more vehicles and generate the FDN based on the amount of fuel delivered.

10. The method as claimed in claim 8, for determining the amount of fuel delivered, comprises using, by the processor (202) a touchpad device and the loT device to record the information associated with the fuel supply, wherein the information comprises any or a combination of: a density parameter associated with the fuel, a temperature parameter associated with the fuel, one or more details associated with the one or more users, a start time and an end time associated with the fuel supply to the one or more vehicles.

Images