NZ722479B2 - Fuel management system and method - Google Patents

Abstract

fuel management system for controlling and managing the delivery of fuel from at least one fuel storage tank is described. The control and managing of delivery is through at least one flow meter and at least one fuel dispensing device connected to the at least one storage tank. The fuel management system including: at least one tank controller for tracking a dispensed volume of fuel; a dispensing controller in communication with each of the at least one tank controller, the dispensing controller having information on at least one fuel account, wherein the dispensing controller: authenticates a fuel transaction against the information on the at least one fuel account; and stores transaction data on the dispensed volume of fuel in association with the at least one fuel account. The fuel management system including an information store and wherein the dispensing controller uploads transaction data to the information store. nt system including: at least one tank controller for tracking a dispensed volume of fuel; a dispensing controller in communication with each of the at least one tank controller, the dispensing controller having information on at least one fuel account, wherein the dispensing controller: authenticates a fuel transaction against the information on the at least one fuel account; and stores transaction data on the dispensed volume of fuel in association with the at least one fuel account. The fuel management system including an information store and wherein the dispensing controller uploads transaction data to the information store.

Description

(12) Granted patent specificaon (19) NZ (11) 722479 (13) B2 (47) Publicaon date: 2021.12.24 (54) FUEL MANAGEMENT SYSTEM AND METHOD (51) Internaonal Patent Classificaon(s): G06Q 50/06 G01F 1/00 B60K 15/06 (22) Filing date: (73) Owner(s): 2015.07.30 Janet Sharon Perry (as trustee for the Perry Family Trust) (23) Complete specificaon filing date: Graeme Esmond Perry (as trustee for the Pe 2016.07.29 rry Family Trust) (74) Contact: ELLIS TERRY (72) Inventor(s): Graeme Esmond PERRY (57) Abstract: A fuel management system for controlling and managing the delivery of fuel from at least one fuel storage tank is described. The control and managing of delivery is through at least one flow meter and at least one fuel dispensing device connected to the at least one storage tank. The fuel management system including: at least one tank controller for tracking a dispensed volume of fuel; a dispensing controller in communicaon with each of the at least one tank controller, the dispensing controller having informaon on at least one fuel account, wherein the dispensing controller: authencates a fuel transacon against the informaon on the at least one fuel account; and stores transacon data on the dispensed volume of fuel in associaon with the at least one fuel account. The fuel management system including an informaon store and wherein the dispensing controller uploads transacon data to the informaon store.

NZ 722479 B2 FUEL MANAGEMENT SYSTEM AND METHOD FIELD This invention relates to a fuel management system and method. More particularly but not exclusively, the invention relates to a fuel management system and method including dispensing controllers storing fuel account data and transaction data.

BACKGROUND Fuel management is used to control and monitor fuel consumption in various industries such as transport and construction. Fuel management systems and methods are typically used for vehicle fleets and employ various methods to track fuel inventories, fuel purchases and fuel dispensed. Tracked information can be stored, analysed and presented by computer systems to inform management practices such as consumption control, cost analysis and tax accounting for fuel purchases.

Improvements in fuel management have been proposed including fuel inventory monitoring, fuel delivery validation and management of transactional data, and communication between local controllers and a remote computing system. Card or other identification based systems may record the volume, location and time of fuel dispensed by an authorised individual.

However prior systems and methods have failed to capture fuel card data in addition to tank controller fuel and transaction data. It is an object of the invention to provide improved fuel management systems and methods or to at least provide the public with a useful choice.

SUMMARY A fuel management system for controlling and managing the delivery of fuel from at least one fuel storage tank through at least one flow meter and at least one fuel dispensing device connected to the at least one storage tank, the system including: at least one tank controller for tracking a dispensed volume of fuel; a dispensing controller in communication with each of the at least one tank controller, the dispensing controller having a local information store, the local information store, storing information on at least one fuel account, wherein the stored information on the at least one fuel account includes information on authorised vehicles and/or plant, the information on authorised vehicles and/or plant further including a unique identifier associated with each authorised vehicle and/or plant, the dispensing controller further including information receiving means for receiving a received identifier, and a remote information store, the remote information store located remotely from the dispensing controller, wherein: the dispensing controller periodically downloads information on at least one fuel account from the remote information store to the local information store; and updates the local information store; the dispensing controller authenticates a fuel transaction using the received identifier against the stored information in the local information store on the at least one fuel account; the dispensing controller stores transaction data in the local information store on the dispensed volume of fuel in association with the at least one fuel account and authorised vehicles and/or plant; and the dispensing controller periodically uploads transaction data from the local information store to the remote information store.

Optionally the dispensing controller is a mobile device.

Optionally the dispensing controller is an application on a device.

Optionally the information on the at least one fuel account includes information on the geographical areas in which fuel dispensing is authorised.

Optionally the dispensing controller includes location information receiving means.

Optionally the location information receiving means is GPS.

Optionally location information is used to authenticate the fuel transaction against the fuel account information on the geographical areas in which fuel dispensing is authorised.

Optionally the dispensing controller authenticates the fuel transaction by receiving confirmation about the authenticity of the transaction from the information receiving means.

Optionally the dispensing controller periodically receives at least fuel account information from the remote information store.

Optionally the tank controller is associated with a static fuel storage tank.

Optionally the tank controller is associated with a mobile fuel storage tank.

Optionally transaction data includes at least one of: a time, date, person, location and volume relating to dispensed fuel, an associated plant or vehicle ID.

A fuel management method for controlling and managing the delivery of fuel from at least one fuel storage tank through at least one flow meter and at least one fuel dispensing device connected to the at least one storage tank, the method including the steps of: a. periodically receiving at the dispensing controller fuel account data on at least one fuel account from a remote information store, wherein the fuel account data on the at least one fuel account includes information on a set of authorised vehicles and/or plant, the information on each authorised vehicle and/or plant further including a unique identifier associated with each authorised vehicle and/or plant; b. storing at a local information store of the dispensing controller the received fuel account data; c. receiving at the dispensing controller an identifier; d. authenticating at the dispensing controller a fuel transaction using the received identifier against the stored fuel account data in the local information store; e. dispensing fuel if the transaction is authenticated; f. tracking at the dispensing controller a dispensed volume of fuel; g. storing at the local information store of the dispensing controller transaction data on the dispensed volume of fuel in association with the authenticated fuel account; and h. periodically uploading from the local information store of the dispensing controller the transaction data to the remote information store.

Optionally steps a, b, c, d, f and g are implemented on a mobile device.

Optionally steps a, b, c, d, f and g are implemented on an application on a device.

Optionally the method includes the step of receiving via the information receiving means confirmation of the validity of the transaction.

Optionally the method includes the step of detecting at the dispensing controller, a dispensing controller location.

Optionally the step of detecting the dispensing controller location uses GPS.

Optionally the fuel is dispensed from a static tank.

Optionally the fuel is dispensed from a mobile tank.

Optionally transaction data includes at least one of: a time, date, person, location and volume relating to dispensed fuel, an associated plant or vehicle ID.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings which are incorporated in and constitute part of the specification, illustrate embodiments of the invention and, together with the general description of the invention given above, and the detailed description of embodiments given below, serve to explain the principles of the invention.

Figure 1 shows the devices of the fuel management system according to one embodiment; Figure 2 shows a front view of a tank controller; Figure 3 shows a screenshot of an example dispensing controller fuel loading page; Figure 4 shows a screenshot of an example manual entry of a vehicle tank-id; Figure 5 shows a block diagram of a controller; Figure 6 shows a schematic diagram according to one embodiment; Figure 7 shows a schematic diagram according to another embodiment; and Figure 8 shows a schematic diagram according to another embodiment.

DETAILED DESCRIPTION The system broadly relates to an integrated fuel management and tracking system for vehicle fleet and plant users for both retail and non-retail fuel management. The system combines information from incumbent fuel cards with tank controller and transaction data from mobile and static fuel tanks, to provide data on all dispensing of fuel across an enterprise. The system can also calculate residual fuel in tanks based on fuel usage to aid logistics around fuel delivery.

Figure 1 shows a fuel management system according to one embodiment. The fuel management system 1 includes at least one fuel storage tank 2 and at least one fuel dispensing device 3 connected to the storage tank 2. A tank controller 4 for tracking a dispensed volume of fuel is connected to the fuel dispensing device 3 and the storage tank 2. A dispensing controller 5 contains information on at least one fuel account. As will be discussed in more detail below, the dispensing controller 5 and the tank controller 4 may be part of a single unit. Alternatively the dispensing controller 5 may be a separate unit such as a mobile device or a web or mobile application. In either case, he dispensing controller 5 is in communication with the tank controller 4. The dispensing controller 5 stores transaction data on the dispensed volume of fuel in association with the at least one fuel account. An information store 6 is also provided. The dispensing controller 5 uploads transaction data to the information store 6.

A method of fuel management can be achieved by connecting at least one dispensing device 3 to at least one storage tank 2. Multiple dispensing devices 3 may be connected to a single storage tank 2, and multiple storage tanks 2 may be included in the system, each connected to one or more dispensing devices 3. The storage tanks 2 may be in proximity to each other or they may be in different geographic areas. A dispensed volume of fuel, from the one or more dispensing devices 3 is tracked using tank controllers 4 connected to the dispensing devices 3.

The tank controllers 4 are in communication with a dispensing controller 5, which has information on at least one fuel account. The dispensing controller 5 stores transaction data on dispensed volumes of fuel in association with at least one fuel account. The dispensing controller 5 then uploads transaction data to an information store 6 and receives account information from the information store 6. A mobile dispensing controller 5 may be used with multiple tanks 2.

Fuel Storage Tanks Fuel tanks 2 may be static or mobile. An example of a static tank is an underground storage tank, commonly used at petrol stations or a tank at a truck stop or depot.

Static tanks may provide fuel directly to vehicles and/or plant, or they may provide fuel to mobile tanks. Mobile fuel tanks are used to provide on-site fuel delivery and refuelling services. Examples of mobile tanks include fuel trucks or tankers which provide fuel supply to commercial fleets of trucks or construction equipment of a construction site. A “Bulk tank” generally refers to a tank with capacity of 10,000L or above. A “home base” tank is usually dedicated to individual customer with capacity of 10,000L or less.

A tank gauge 13 may be fitted to tanks 2 to measure and communicate the volume of fuel within a tank 2. Such monitoring devices/sensors will automatically upload the data to the information store 6 via tank controller 4 and/or the dispensing controller 5.

Alternatively and/or additionally the fuel management system may calculate the residual volume of the fuel tank based on the volume of fuel dispensed from that tank.

The fuel storage tank 2 may store any suitable fuel, including but not limited to liquid fuels such as ethanol, diesel, liquid petroleum, or biofuels or gaseous fuels such as methane, propane or hydrogen.

Fuel dispensing device The fuel dispensing device 3 connected to the fuel storage tank 2 may be any suitable arrangement for dispensing fuel from a fuel tank 2. Generally this is a hose and gun combination attached to a fuel pump. The nature of the fuel dispensing device 3 will depend on the type of fuel storage tank 2, the type of fuel being dispensed or the type of vehicle and/or plant being dispensed to. Fuel may be dispensed to vehicles (e.g. land vehicles, ships, or aircraft), plant (e.g. machinery), or other storage tanks.

The fuel dispensing device 3 may be diesel or electric driven with human activation.

In cases where the dispensing controller authenticates fuel dispensing as will be discussed below, the fuel dispensing device 3 can include a solenoid valve to restrict the flow of fuel until commanded by the tank controller 4 or another remote device to ‘open’.

Tank controller and dispensing controller The system includes a controller which consists of both a tank controller 4 and a dispensing controller 5. In some embodiments (in particular in embodiments including static tanks), the tank controller 4 and dispensing controller 5 may be a single unit/device. In other embodiments (in particular embodiments including mobile tanks), the tank controller 4 may be separate from the dispensing controller 5 and communicate with the dispensing controller 4 (e.g. via Bluetooth, WiFI or the 3G/4G network).

Tank controller The tank controller 4 tracks the volume of fuel dispensed. The tank controller 4 is connected to a flow meter 15 which measures the flow of fuel and generates a pulse to the tank controller 4 indicating the fuel dispensed.

A tank controller 4 is connected to the tank 2 to track the volume of fuel dispensed and other relevant information from the fuel dispensing device 3. The tank controller 4 is capable of capturing and transmitting specific data when fuel is dispensed through the system. Preferably, the tank controller 4 allows two-way communication between the tank controller 4 and a dispensing controller 5. The tank controller 4 can gather data for remote reporting. Preferably the tank controller 4 is flameproof and can withstand temperatures between the range of -40⁰C to 80⁰c.

In mobile tanks the tank controller 4 may be powered by an internal battery, or it may be powered by the vehicle on which the mobile tank is driven. In static tanks the tank controller 4 may be battery powered, wirelessly powered, externally powered.

Dispensing controller The dispensing controller 5 includes a user interface for the initiation of fuel transactions by a user and a means for communicating with the tank controller 4. In addition to storing information relating to at least one fuel account, the dispensing controller 5 also stores information relating to fuel dispensing.

The dispensing controller 5 is in communication with the tank controller 4. The dispensing controller 5 and tank controller 4 may communicate in any suitable way, for example through radio communication, WIFI or Bluetooth. The dispensing controller 5 receives transaction data from the tank controller 4 and stores this information.

The dispensing controller 5 stores transaction data on the dispensed volume of fuel in association with the at least one fuel account. The dispensing controller uploads transaction data to the information store 6 which will be discussed in more detail below.

The dispensing controller 5 may upload transaction data to the information store 6 in real time. In other words, it may upload transaction data to the information store 6 as soon as it receives the transaction data from the tank controller 4.

Alternatively, the dispensing controller 5 may store the transaction data and periodically upload the transaction data to the information store. Periodic uploads may occur at any suitable intervals, e.g. weekly, daily, hourly or in response to certain events, triggers or thresholds or when in the range of a suitable network.

Uploads and downloads from the information store 6 may be automatic or manual.

A combination may be used wherein the dispensing controller continuously uploads data when there is connectivity between the dispensing controller and the information store 6, and when connectivity is lost it stores the data until connectivity is regained.

The fuel dispensing controller 5 may include a way to monitor network connectivity to determine when to download/upload information from the information store 6.

The fuel dispensing controller 5 may also include a GPS or other mechanism to detect its location. This may be particularly useful for dispensing controllers connected to mobile tanks. Location data may be recorded as part of transaction data and transmitted to the information store 6. Location data may also be used as part of the authentication process to lock or activate the fuel dispenser.

Example embodiment 1 - Mobile Tanks Figure 2 shows a front view of a tank controller 4 for a mobile tank. The tank controller 4 in Figure 2 is configured to mount to a mobile tank and interface with a suitable dispensing controller. The tank controller 4 has a display 13 and a series of indicators (14a to 14e). It is mounted to a fuel tank (not shown) via a mounting mechanism 16 and is connected to a flow meter 15.

The indicators show the power status of the meter 14a, the battery strength 14b, a warning light 14c, Bluetooth connection 14d and Bluetooth functionality 14e. The tank controller’s display 13 may display the battery charge, tank ID, current flow, date, time and total flow for the tank controller 4.

In some embodiments, a computer, web and/or mobile application may act as a dispensing controller 5. The application be installed on a suitable device, such as a tablet, mobile phone, or laptop. A user can log into the application by entering a pincode, username and password, or in some other way.

An administrator can access the application and download data that has been set up within the company database and upload all data/captured information to the information store. This data may be uploaded via a Wi-FI or 3G Connection.

Figure 3 shows an example screenshot of a dispensing controller fuel loading page.

The page prompts the user to fill Tank and/or Plant detail and the odometer reading.

In other embodiments, the user may not enter a desired volume but rather dispense a desired amount of fuel which is recorded by the flow meter 15. In this embodiment the user starts and stops the fuel dispenser as desired, and the dispensed amount is recorded by the tank controller 4 and communicated to the dispensing controller 5.

Tank and/or plant details may be easily loaded by scanning a barcode, QR code or other suitable identifier on the tank and/or plant. Alternatively, a tankID can be entered manually via the device’s keyboard. Figure 4 shows a screenshot of an example manual entry of a trailer tank-id.

As the dispensing controller locally stores user, tank and plant information, it can authenticate the dispensing of fuel by comparing the information entered by a user with the information locally stored in its memory.

When a user enters a vehicle and/or plant id, the dispensing controller locates the details of that vehicle/and or plant from its local database. Optionally the dispensing controller may display further details of the vehicle and/or plant corresponding to the ID entered, for example a model/make or even a photograph of the vehicle and/or plant.

In some embodiments, the dispensing controller 5 may require a supervisor (who may be located remotely) to authorise the transaction, as a further authentication step. The supervisor may view the user, vehicle details and desired odometer value and approve or deny the fuel transaction. The system may have a camera to allow the supervisor to view the vehicle or the user.

A user may initiate the dispense of fuel by clicking a button on the dispensing controller. The dispensing controller may wait for connectivity to the tank controller (e.g. Bluetooth connectivity).

Fuel transactions are initially stored locally on the dispensing controller. As discussed above, the dispensing controller may upload fuel transactions to the information store periodically, on certain triggers, or when initiated by a user. A user may be able to view which transactions are yet to be uploaded to the information store.

Example 2 - Static controller Tank controller and dispensing controller functionality may be incorporated into a single unit (“the controller”). A single controller would primarily be used in static tanks but may also be used in mobile tanks.

Figure 5 shows a block diagram of a controller with both tank controller 4 and dispensing controller functionality. The controller includes a wireless sensor 17 and a control meter 18.

The wireless sensor 17 may capture flow data through a flow meter and transmit wirelessly to a control meter 18 at runtime. The wireless sensor 17 does not support any user interaction. It may be operated by a control unit for calibration or changes to parameters to support different range of flow meters.

The wireless sensor 17 includes connectors 41 and 42.

Connector C-B1 is a power supply to the wireless sensor 17 unit. For example this may be a 12VDC power supply.

The connector 42 is a flow sensor connector, which captures flow pulses from the flow sensor.

The control meter 18 provides a human machine interface and machine to machine communication with the wireless sensor 17. In an example embodiment, it supports following functionality: • User interaction through Keyboard and 7” LCD based GUI • Communication with wireless sensor 17 to capture runtime flow data and display • 3G based communication with the information store to support database sync operation and authentication • 8GB storage to prevent transaction data offline in control unit • USB stick connection for offline sync operation in case of unavailability if 3G connection.

The control meter 18 includes three connections 43, 44 and 45, and optionally a USB port 21 for a USB stick.

The connector 43 connects the control meter 18 to a power source. In one embodiment, the control unit is connected with a 12VDC 2Amp external adapter, which is connected with a main board.

The connector 44 is an input connector to detect the state of the fuel nozzle. The detector may detect whether the nozzle is in a hanging state or a pulled-up state (e.g. held inside its holster). The input connector may be a limit switch connection. The connector may include additional input connections for the detection of other conditions.

The connector 45 is an output connection for pump control. This may be a potential free relay output contact, with common and normally open relay contact. This connector allows the control meter 18 to initiate and halt the flow of fuel from the fuel dispenser.

The control meter 18 may also include a wireless communication module 21 for wireless communication with a wireless communication module 22 on the wireless sensor 17. This wireless communication may be via Bluetooth, wireless internet (e.g. 3G/4G or WIFI), or some other means. In other embodiments the connection between the wireless sensor 17 and the control meter 18 may be wired.

The controller may include a display 13. The display 13 may display the battery charge, tank ID, current flow, date, time and total flow for the tank controller 4.

In some embodiments the controller may also include a user interface and input means so that administrators and/or users of the fuel management system can log in and use the fuel management system. This user interface may function a similar manner to the web or mobile application described above in relation to the mobile meter. The interface may also display the status of the fuel nozzle (i.e. hanging or pulled-up/held in the its holster).

An administrator may log into the system to manually synchronise data between the mobile unit and the information store 6. Data downloaded from the information store may be stored permanently in a local memory store of the static controller.

Transaction data may be uploaded to the information store 6.

A user may log in to the fuel management system via a user pin or some other means. A tank ID and/or plant ID and a desired amount of fuel to be dispensed may be entered and validated by the system in order to initiated fuel dispensing, as described above with respect to the mobile meter. Once a tank-ID or plant-ID has been successfully validated, the fuel dispenser may be automatically turned on/unlocked. A user may dispense fuel. The display 13 of the control meter 18 19 may show the current fuel dispensed in real-time. Fuel dispensing may be automatically stopped once the desired amount of fuel has been dispensed. The control meter 18 may upload transaction data to the information store 6 immediately and/or store the transaction data in its local memory. In the case of an upload failure (e.g. when network connectivity is lost), the system may locally store the transaction data and upload it at a later stage (e.g. when network connectivity is regained). Optionally a USB or some other storage device may be used to manually copy transaction data from the controller to the information store 6.

The controller may include LED indicators for errors, Bluetooth connectivity, 3D and power status.

Even in the case where a single controller incorporating a tank controller 4 and dispensing controller functionality, the controller may also interface with a mobile application.

The static controller may further include smart card identification capability for user authentication and tank and/or plant authentication. In other embodiments it may include a camera for face detection and/or capture.

In other embodiments the static controller may integrate with a payment terminal for fuel reloading with payments.

The static controller may support Ethernet, WiFi, and/or directly communicate with a computer such as a desktop computer or laptop.

The static controller may output to a printer. For example, a list, summary or graphic of collated transactions may be printed by a user. It may also print receipts for individual transactions.

The tank controller 4 may be used to control fuel dispensing. The tank controller 4 may include a mechanism for authenticating a user with an identifier before dispensing fuel. For example, the tank controller 4 may allow fuel to be dispensed only once an authorized PIN number is entered. The tank controller 4 may authenticate a fuel account, authorised individuals, authorised plant and/or vehicles or on some other basis.

Individual users may be authenticated with a “fuel card”, a pin-number, password, smart card, biometric identification, Near Field Communication tag, fingerprint recognition or by some other identifier.

Plant/and or vehicles may also be authenticated before allowing fuel to be dispensed to them using a suitable identifier. For example vehicles and/or plant may include a scannable barcode which is scanned by a reader at the fuel dispenser before fuel dispense is allowed. Another example is activating using an optical transmitter located on a vehicle which is paired to an optical fiber receiver on the fuel dispensing nozzle.

Location coordinates may be another basis for authenticating the dispensing of fuel.

For example this may prevent the dispensing of fuel from mobile tanks outside of authorized zones for vehicle fleet or plant fuel reloading.

In some cases, combinations of user, vehicle/plant and/or location authentication may be used to control the dispensing of fuel.

Transaction Data Transaction data is captured by the tank controller 4. Transaction data may include time, date, person, location, volume and other information relating to dispensed fuel, which may be associated with a plant, vehicle or user ID. Transaction data is also linked to a particular fuel account.

Fuel Accounts A dispensing controller 5 stores information on at least one fuel account. A fuel account may be associated with a particular object or group of objects. For example, fuel accounts may be associated with entities (e.g. business entities), individuals, vehicle fleets, individual vehicles or plant. A fuel account may be linked to a user with an account number, contact and address details, and linked to associated plant and tank transactions.

Fuel account information may include any information relating to fuel dispensing, such as the person/s dispensing fuel or the time, date, location and volume of dispensing. Such information is linked to one or more fuel accounts.

Fuel accounts may be identified in various ways, such as with fuel cards, unique identifiers (e.g. pin codes), bar-codes, NFC or biometric information or any other suitable method. A location ID based on GPS coordinates may also be used as identification. The tank controller 4 links transaction data to a fuel account by virtue of the identification provided with the fuel transaction. The identification provided may also be used to authenticate fuel dispensing. A fuel account links a user with an account number, contact and address details, and further is linked to plant and tanks a user may use.

A fuel card or fleet card is commonly used as a payment card most commonly for gasoline, diesel, and other fuels at gas stations. Fleet cards can also be used to pay for vehicle maintenance and expenses at the discretion of the fleet owner or manager.

Transactions details may be sent to the information controller periodically, for example hourly, daily or weekly. The dispensing controller may upload transactions from the field. Card detail transactions are sent from fuel suppliers to us daily, transactions updated from field via the dispensing controller or mobile handheld device. No card reader device.

Information store The information store 6 may be a computer, a laptop, a tablet or other computing device capable of storing transaction data associated with at least one fuel account.

The information store 6 may be in communication with and receive data from several dispensing controllers. The information store 6 may store, process and/or display the transaction data from the one or several dispensing controllers.

The information store may also provide one or more dispensing controllers with certain information, such as user account information, vehicle/plant information and fuel storage tank information.

Shrinkage The system includes methods for monitoring and detecting fuel theft and/or fraud, known as “shrinkage”. The dispensing controller 5 detects discrepancies in dispensed fuel. This may involve reconciling fuel remaining in storage tank 2 with fuel volume dispensed from the tank 2 to determine errors. Errors may be determined on the dispensing controller and/or the information store 6.

If shrinkage is detected, fuel account holders and/or fuel providers are notified of this in a suitable way. For example, they may be alerted via SMS or email.

Figure 6 shows a schematic diagram showing an example of the authentication of fuel dispensing. In this embodiment, the information store 6 provides the fuel dispensing controller 5 with certain information, such as user account information, plant information and tank information. This information is then stored locally on the fuel dispensing controller 5, and may be used to authenticate fuel use, and/or to link to transaction data as measured by the tank controller 4. A tank controller connected to a fuel tank (not shown), transmits transaction data to the fuel dispensing controller . Transaction data may include a tankID, userID, plantID, the current fuel dispensed, the total fuel dispensed, a date, time and location. Transaction data linked to a particular fuel account is then uploaded from the fuel dispensing controller 5 to the information store 6.

Figure 7 shows another schematic diagram showing the upload of information to the information store. Transaction data 7 is uploaded to the fuel dispensing controller 5.

Unknown plant or vehicle details 9 are also uploaded to the fuel dispensing controller. This allows the dispensing of fuel to the vehicle not yet loaded on the system by an authenticated user. Details regarding the registration number of the vehicle/plant or identification of the vehicle/plant can be captured for later update.

The fuel dispensing controller 5 detects which network/s 10 are available. Such networks 10 may include WIFI, Bluetooth, Phone networks, or wired internet connections. When a suitable network 10 is available the fuel dispensing controller uploads transaction data 7 to the information store 6, and downloads any updates from the information store 6.

Figure 8 shows another schematic diagram in which the fuel dispensing controller authenticates use of the fuel dispensing system. An identifier 11 is presented to the fuel dispensing system. An authentication process 12 determines whether the identifier 11 is valid.

If a user, vehicle/plant and/or location is successfully authenticated, the fuel dispenser is activated 31. If use of the fuel dispensing system is not successfully authenticated, the fuel dispenser is locked 32 and a user is prevented from dispensing fuel. A list of users, vehicles and/or plant which are authenticated for use with the fuel dispensing system may be downloaded by the fuel dispensing controller by the information store 6. Successful and/or unsuccessful attempts of authentication may also be stored by the fuel dispensing controller and uploaded to the information store 6.

Those skilled in the art understand that the various embodiments described herein and claimed in the appended claims provide an utilisable invention and at least provide the public with a useful choice.

While the present invention has been illustrated by the description of the embodiments thereof, and while the embodiments have been described in detail, it is not the intention of the Applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details, representative apparatus and method, and illustrative examples shown and described. Accordingly, departures may be made from such details without departure from the spirit or scope of the Applicant’s general inventive concept.

Claims (15)

1. A fuel management system for controlling and managing the delivery of fuel from at least one fuel storage tank through at least one flow meter and at 5 least one fuel dispensing device connected to the at least one storage tank, the system including: at least one tank controller for tracking a dispensed volume of fuel; a dispensing controller in communication with each of the at least one tank controller, the dispensing controller having a local information 10 store, the local information store, storing information on at least one fuel account, wherein the stored information on the at least one fuel account includes information on authorised vehicles and/or plant, the information on authorised vehicles and/or plant further including a unique identifier associated with each authorised vehicle and/or plant, 15 the dispensing controller further including information receiving means for receiving a received identifier, and a remote information store, the remote information store located remotely from the dispensing controller, wherein: 20 the dispensing controller periodically downloads information on at least one fuel account from the remote information store to the local information store; and updates the local information store; the dispensing controller authenticates a fuel transaction using 25 the received identifier against the stored information in the local information store on the at least one fuel account; the dispensing controller stores transaction data in the local information store on the dispensed volume of fuel in association with the at least one fuel account and authorised 30 vehicles and/or plant; and the dispensing controller periodically uploads transaction data from the local information store to the remote information store.

2. The fuel management system of claim 1 wherein the dispensing controller is a mobile device. 5

3. The fuel management system of claim 1 or claim 2 wherein the dispensing controller is an application on a device.

4. The fuel management system of any one of the preceding claims wherein the information on the at least one fuel account includes information on the 10 geographical areas in which fuel dispensing is authorised.

5. The fuel management system of any one of the preceding claims wherein the dispensing controller further includes location information receiving means. 15

6. The fuel management system of claim 5 wherein the location information receiving means is GPS.

7. The fuel management system of claim 5 or claim 6 wherein location information is used to authenticate the fuel transaction against the fuel 20 account information on the geographical areas in which fuel dispensing is authorised.

8. The fuel management system of any one of the preceding claims wherein the dispensing controller authenticates the fuel transaction by receiving 25 confirmation about the authenticity of the transaction from the information receiving means.

9. The fuel management system of any one of the preceding claims wherein the dispensing controller periodically receives at least fuel account information 30 from the remote information store.

10. The fuel management system of any one of the preceding claims wherein the tank controller is associated with a static fuel storage tank. 35

11. The fuel management system of any one of claims 1 to 9, wherein the tank controller is associated with a mobile fuel storage tank.

12. The fuel management system of any one of the preceding claims wherein transaction data includes at least one of: a time, date, person, location and volume relating to dispensed fuel, an associated plant or vehicle ID. 5

13. The fuel management system of any one of the preceding claims wherein the dispensing controller and the tank controller are a single unit.

14. A fuel management method for controlling and managing the delivery of fuel from at least one fuel storage tank through at least one flow meter and at 10 least one fuel dispensing device connected to the at least one storage tank, the method including the steps of: a. periodically receiving at the dispensing controller fuel account data on at least one fuel account from a remote information store, wherein the fuel account data on the at least one fuel account includes information 15 on a set of authorised vehicles and/or plant, the information on each authorised vehicle and/or plant further including a unique identifier associated with each authorised vehicle and/or plant; b. storing at a local information store of the dispensing controller the received fuel account data; 20 c. receiving at the dispensing controller an identifier; d. authenticating at the dispensing controller a fuel transaction using the received identifier against the stored fuel account data in the local information store; e. dispensing fuel if the transaction is authenticated; 25 f. tracking at the dispensing controller a dispensed volume of fuel; g. storing at the local information store of the dispensing controller transaction data on the dispensed volume of fuel in association with the authenticated fuel account; and h. periodically uploading from the local information store of the 30 dispensing controller the transaction data to the remote information store.

15. The method of claim 14, wherein steps a, b, c, d, f and g are implemented on a mobile device.