AU2020202063A1 - Bulk liquid monitoring and management system - Google Patents

Abstract

A monitoring and/or management system for monitoring bulk liquid from a remote location is disclosed. The system includes at least one tank, configured to receive and store bulk liquid and at least one sensor associated with the at least one tank. The at least one sensor is configured to sense a measurement relating to the quantity of liquid in the at least one tank. The system also includes a controller in proximity to the at least one tank that is configured to determine a volume of liquid in the tank in response to the measurement sensed by the at least one sensor. The controller is also configured to transmit volume data relating to the determined volume to a central server. The controller includes a transmitter that is configurable to transmit the volume data using a non-data cellular service such as text messaging. A method of monitoring and/or managing bulk liquid from a remote location is also disclosed. Figure 1 7/11 Navman Driver [D Module Teletrac Navman Qube 300 240V-12V Power Timrne Supply PCB MainPCIBBatch Flow Controller Meter 2-24V Step Us Converter ignition Switch Immob. Battery Valve Connection Figure 8

Description

7/11

Navman Driver [D Module

Teletrac Navman Qube 300

240V-12V Power Timrne Supply PCB

MainPCIBBatch Flow Controller Meter

2-24V Step Us Converter

ignition Switch

Immob. Battery Valve Connection

Figure 8

BULK LIQUID MONITORING AND MANAGEMENT SYSTEM FIELD

[0001] The present invention relates to monitoring and management of bulk fluids.

[0002] The invention relates particularly but not exclusively, to a system for monitoring and/or managing bulk quantities of liquid from a remote location, e.g. liquid fuels such as diesel and water. The invention also extends to a method of monitoring and/or managing a bulk liquid from a remote location.

DEFINITION

[0003] In the present specification and claims (if any), the word 'comprising' and its derivatives including 'comprises' and 'comprise' include each of the stated integers but does not exclude the inclusion of one or more further integers.

BACKGROUND ART

[0004] Farming, mine, construction and earthmoving sites generally require significant amounts of diesel to operate their equipment, which is used for performing a variety of tasks from harvesting to transportation to development. The equipment is generally spread out over large areas, and as such, many sites include multiple diesel storage tanks, thereby providing diesel close to the equipment. In short, diesel is generally transported to the sites in bulk from nearby cities or towns, to fill the tanks when needed.

[0005] Many centrally managed farming and mining sites are spread out over a region, and are often located in remote locations. Furthermore, several operators may operate the equipment, and thus use the diesel. As such, management of the diesel across these sites is often very difficult. As a result, it is generally difficult to predict when the diesel tanks will need refilling. Accordingly, the diesel tanks are often refilled based on know-how and best guesses, which is inefficient.

[0006] Several attempts have been made to improve diesel management in such cases, based upon regular, manual tank level monitoring. While such monitoring enables a manager or other person to get a better understanding of the diesel levels, the monitoring, management and travel to and from the site are all time-consuming tasks, which take staff away from other more productive tasks.

[0007] In more recent years, remote tank monitoring systems have been developed, where level sensors are used to remotely sense a level of diesel in a tank, and transport details of the tank levels by the Internet. A problem, however, with such remote monitoring of tanks is that the systems are generally complex and expensive. Furthermore, in many cases the systems must be custom made to suit each configuration, which is complex and time consuming.

[0008] Another problem with such remote monitoring systems is that the data therefrom can be difficult to interpret, and as a result, it can be difficult for a manager to get a good overview of the diesel levels and usage information.

[0009] A further problem with such Internet-based remote monitoring systems is that they are not well-suited to remote areas. In Australia, a large portion of the country is without mobile broadband Internet coverage, and as a result, such systems are generally not suitable.

[0010] Satellite based Internet is available in many remote areas, but these systems are generally complex, difficult to install and expensive. Furthermore, many remote tanks may not have access to mains power, and as such, require further associated infrastructure to be installed.

[0011] It will be clearly understood that, if a prior art publication is referred to herein, this reference does not constitute an admission that the publication forms part of the common general knowledge in the art in Australia or in any other country.

SUMMARY OF INVENTION

[0012] The applicant has recognised that it would be beneficial if improved methods and systems for bulk liquid monitoring and/or managing bulk liquids could be devised.

[0013] The present invention is directed to methods and systems for monitoring and/or managing bulk liquids, which may at least partially overcome at least one of the abovementioned disadvantages or provide the consumer with a useful or commercial choice.

[0014] According to one aspect of the invention, there is provided a monitoring and/or management system for monitoring bulk liquid from a remote location, the system including: at least one tank, configured to receive and store bulk liquid; at least one sensor associated with the at least one tank, the at least one sensor configured to sense a measurement relating to the quantity of liquid in the at least one tank; and a controller in proximity to the at least one tank, the controller being configured to determine a volume of liquid in the tank in response to the measurement sensed by the at least one sensor, and the controller also being configured to transmit volume data relating to the determined volume to a central server.

[0015] The measurement relating to the quantity of liquid may be the level of liquid in the tank and the controller may be configured to determine the volume of liquid in response to the level of liquid sensed by the sensor.

[0016] The controller may be configured to determine a volume of liquid in the tank based upon the level of liquid sensed by the sensor and a model of tank, or the controller may be configured to determine a volume of liquid in the tank based upon the sensor level and a lookup table.

[0017] The model of the tank may comprise a cylindrical model. The cylindrical model may comprise a horizontal or a vertical cylinder. The lookup table may be determined heuristically.

[0018] The liquid may comprise diesel. Alternatively, the liquid may comprise water, or one or more chemicals.

[0019] The at least one sensor may be an ultrasonic sensor that is configured to determine a level of liquid in the tank with reference to a reference point, e.g. being the position and height of the sensor in the tank. The use of an ultrasonic sensor alleviates the need to lower a sensor, or a part of the sensor, into the liquid, while still enabling accurate measurement to be performed.

[0020] The controller may include a transmitter that is configured to wirelessly transmit the determined volume of liquid to the central server.

[0021] The transmitter may include a cellular transmitter transmitting wirelessly to the central server using a cellular base station.

[0022] The cellular transmitter may be configurable to include transmitting the volume data using a non-data cellular service, such as text messaging.

[0023] Further, the controller may be configurable to include transmitting the data over the internet.

[0024] The monitoring and/or management system may include a valve operatively associated with each tank for controlling the discharge of liquid from the tank, and the valve may be operatively connected to the controller associated with that tank which controls the flow of liquid from the tank by opening and closing the valve.

[0025] In this way, the controller controls the delivery of liquid from its associated tank by opening and closing the valve.

[0026] The system may further include a liquid volume measuring arrangement for measuring the volume of liquid drawn from the tank each time a user draws liquid from the tank.

[0027] The liquid volume measuring arrangement may be like a fuel volume measuring arrangement of the type found at a fuel bowser.

[0028] Optionally, the liquid volume measuring arrangement may include the flow meter.

[0029] The liquid volume measuring arrangement may be operatively connected to the controller to communicate liquid data regarding liquid volume drawn from the tank to the controller.

[0030] Further, the controller may transmit the liquid data to the central server.

[0031] The monitoring and/or management system may further include a flow meter mounted in line with the valve for measure the flow of liquid from the tank. Further, the controller may be operatively connected to the flow meter for receiving flow measurements therefrom, determining a volume of liquid discharged from the tank, and transmitting data relating to the volume of liquid discharged from the tank to the central server.

[0032] The system may include a reader for controlling access to the the/each tank and limiting access to authorized users.

[0033] The reader may include a wireless access tag reader that is operatively coupled to the controller, and the controller may be configured to control access in response to data read by the wireless access tag reader.

[0034] The monitoring and/or management system may optionally include a keypad, for enabling a user to enter a pin code or password. The controller may be configured to control access to the one or more tanks at least in part through data entered into the keypad.

[0035] Optionally, the system may include a keypad in addition to the reader. Alternatively, the system may include a keypad instead of the reader.

[0036] The controller may be configured to receive an equipment identifier identifying a piece of equipment to which liquid is to be supplied, to log a record of the piece of equipment to which the liquid is supplied.

[0037] The controller may be configured to transmit data relating to the equipment identifier and equipment usage associated with that equipment identifier to the central server.

[0038] Alternatively, a user may be associated with the equipment, thereby providing an indirect equipment identifier by virtue of a known association between a user and their equipment.

[0039] At least one piece of equipment may have an odometer or hour meter reflecting usage of that piece of equipment, and the controller may be configured to log an odometer or hour reading of that equipment when liquid, e.g. diesel is delivered to that equipment.

[0040] The central server may associate the determined volume of liquid discharged with the particular user. Alternatively, the central server may associate the determined volume of liquid discharged with a particular piece of equipment.

[0041] The central server may be configured to generate a graphical user interface (GUI), and the GUI is configured to display at least volume data of the at least one tank. In particular, the GUI may comprise an interactive dashboard.

[0042] The GUI may be configured to display data indicative of a flow of liquid from the tank, and/or data for a particular piece of equipment, and/or data for a particular operator, and/or data for a particular tank.

[0043] The GUI may be configurable to display data for a selected time period.

[0044] In one embodiment, the monitoring and/or management system may have a plurality of said tanks, and the GUI may be configured to display volume data for the plurality of tanks. The volume data may include displaying volume data for each of the plurality of tanks. Additionally, or alternatively, the volume data may include volume data that is aggregated for the plurality of tanks in addition to or instead of volume data for each of the plurality of tanks.

[0045] The controller may be contained in a housing.

[0046] The GUI may be further configurable to transmit control instructions to the controller for controlling operation of a piece of equipment.

[0047] The system may further include a pump for pumping liquid from the tank.

[0048] The controller may be configurable to enable a user to control the pump by transmitting instructions through the GUI to the controller.

[0049] In particular, a user may transmit instructions to the controller to switch on a pump to draw water from the tank and also to switch off the pump.

[0050] Generally, the system enables tanks to be added in a modular manner which renders the system flexible and capable of incremental expansion.

[0051] The system is easy to install and configure and the server does not need have information on the shape or volume of the tanks.

[0052] According to another aspect of the invention, there is provided a method for monitoring and/or managing bulk liquid from a remote location, the method including: using at least one sensor associated with at least one tank configured to receive and store bulk liquid to sense a measurement relating to the quantity of liquid in the at least one tank; and determining, using at least one controller in proximity to the at least one tank, a volume of liquid in the tank based upon the measurement in the at least one tank, and transmitting volume data relating to the determined volume of liquid to a central server.

[0053] A valve may be operatively associated with each tank for controlling the flow of liquid from the tank, and the method includes controlling opening and closing the valve to control the flow of liquid by means of the controller.

[0054] Transmitting to a central server may include wirelessly transmitting the volume data to the central server by means of a cellular transmitter.

[0055] Further, wirelessly transmitting to the central server may include transmitting the volume data using a non-data cellular service, such as text messaging.

[0056] The method may further include configuring the central server to generate a GUI and configuring the GUI to display volume data of the at least one tank.

[0057] The method may include monitoring and/or managing a bulk liquid which is diesel fuel which is used by pieces of equipment such as vehicles and pumps. Further, the method may include monitoring and/or managing a bulk liquid which is water which may be used for irrigation of farmland.

[0058] Any of the features described herein can be combined in any combination with any one or more of the other features described herein within the scope of the invention.

[0059] In particular, the method may include using the system defined in a preceding statement of invention. Further, the system used in the method may include any one or more of the optional or preferred features of the system defined in a preceding statement of invention.

BRIEF DESCRIPTION OF DRAWINGS

[0060] Various embodiments of the invention will be described with reference to the following drawings, in which:

[0061] Figure 1 illustrates a system for managing and monitoring diesel across a plurality of remote sites, according to an embodiment of the present invention;

[0062] Figure 2 illustrates a simplified overview of a site including a tank of the system of Figure 1 and remote monitoring modules;

[0063] Figure 3 illustrates a schematic of a site of the system of Figure 1 with associated remote monitoring modules;

[0064] Figure 4 illustrates a screenshot of a first dashboard screen of the system of Figure 1, according to an embodiment of the present invention;

[0065] Figure 5 illustrates a screenshot of a second dashboard screen of the system of Figure 1, according to an embodiment of the present invention;

[0066] Figure 6 illustrates a screenshot of a third dashboard screen of the system of Figure 1, according to an embodiment of the present invention;

[0067] Figure 7 is a schematic flow sheet illustrating a method of remotely monitoring and managing a bulk liquid; and

[0068] Figure 8 is a schematic drawing illustrating an example controller for a system in accordance with one embodiment of the invention.

[0069] Figure 9 show some screenshots of example fuel management software.

[0070] Preferred features, embodiments and variations of the invention may be discerned from the following Detailed Description which provides sufficient information for those skilled in the art to perform the invention. The Detailed Description is not to be regarded as limiting the scope of the preceding Summary of the Invention in any way.

DETAILED DESCRIPTION

[0071] Figure 1 illustrates a system 100 for managing and monitoring diesel across a plurality of remote sites, according to an embodiment of the present invention. In particular, the system 100 enables a manager 105, or other authorised individual, to obtain an accurate overview of each of a plurality of tanks 110 storing the diesel, distributed across a plurality of remote sites 115, in a manner that is easy to use and understand. This enables better decisions to be made about the diesel, and reduces the likelihood that the diesel unexpectedly runs out in one of the tanks 110. The system 100 also enables sites 115 to be monitored in areas without mobile broadband Internet coverage, as outlined in further detail below.

[0072] The sites 115 may be agricultural or mine sites, where equipment 120, such as mining or agricultural machinery, is operated. The equipment 120 is powered by diesel from the tanks 110. Operators 125 of the equipment 120 use RFID tags 130 to gain access to the tanks 110, which thereby enable the operators 125 to fill the equipment 120 with diesel.

[0073] Each tank 110 is associated with remote monitoring modules 135, which provide access control (i.e. ensure that the operator 125 is authorised to access the diesel), and monitoring of the diesel usage, such as monitoring of the amounts of diesel distributed, to whom, and when. The remote monitoring modules 135 may also obtain data of the equipment 120, such as an equipment identifier and associated running data (e.g. hour meter or odometer readings).

[0074] The monitored data is uploaded to a remote server 140 by way of one or more cellular base stations 145. The cellular base stations 145 may receive the monitored data using a mobile broadband Internet configuration, when available, and messaging (or voice) configurations otherwise. As an illustrative example, the remote monitoring modules 135 may communicate with the cellular base station 145 using 3G or 4G mobile broadband Internet when available, and revert to text messaging when 3G or 4G mobile broadband Internet is not available.

[0075] In case text messaging is used, the data may be encoded and compressed in the text message prior to being uploaded, to save transmission costs, and to increase reliability. As an illustrative example, the data may be encoded as a string of hexadecimal characters.

[0076] The use of messaging, when required, enables the system to function in areas where mobile broadband Internet is not available, but when cellular coverage is available. As such, this configuration provides a cost-effective step between mobile broadband based solutions and expensive satellite-based solutions.

[0077] The server 140 receives data from each of the remote locations 115, and both saves and analyses this information. This in turn enables the manager 105 to receive intelligent warnings and messages, as well as be able to access the received data in its original (untransformed) state, e.g. for investigative purposes.

[0078] As outlined below, the server 140 generates a dashboard, which is displayed to the manager 105 on a manager computing device 150, such as a personal computer. The dashboard includes warnings and alerts (if relevant), and information regarding levels of diesel in the tanks, as well as usage statistics and other important information. The dashboards are configurable, which enables managers 105 to see data that is most relevant to them.

[0079] In addition to monitoring, the manager 105 may select one or more restrictions to place on an operator 125 and or equipment 120. As an illustrative example, the manager 105 may, using the system 100, direct an operator 125 to use a particular tank 110, either generally or for particular equipment 120. This is preferably achieved by sending a message, using the system 100, to the operator 125. As a result, the manager 125 is able to have better control over how the diesel in the tanks 110 is used.

[0080] The manager 105 may also arrange for diesel to be transported from one tank 110 to another tank 110, instead of simply arranging for the other tank 110 to be filled. This may be arranged using the system 100, for example using messaging, or directly with a transport vehicle. This in turn enables the manager 105 to have better control over the diesel in the tanks 110 as a whole, rather than considering each tank 110 in isolation. This may in turn enable the manager 105 to reduce a total amount of diesel stored on site, while maintaining availability of the diesel where required.

[0081] Figure 2 illustrates a simplified overview of a site 200 including a tank 110 and remote monitoring modules, and Figure 3 illustrates a schematic of the site 200 including the tank 110 and associated remote monitoring modules.

[0082] The tank 110 includes a control panel 205 in association therewith, which provides connectivity to the server 140, and provides access control and monitoring. In particular, the control panel 205 includes an RFID tag reader 210, which enables the operator 125 to scan an RFID tag for identification purposes. The RFID tag may comprise a fob, which is held against the reader 210 in use by one or more magnets.

[0083] The control panel 205 further includes a keypad 215, which enables the operator 125 to enter a pin number associated with the RFID tag, to provide further security in case the RFID tag becomes lost or otherwise in the hands of someone that is unauthorised.

[0084] Diesel 220, which is stored in the tank 110, is provided using a dispensing hose with a nozzle 225, to enable the tank 110 to function much like a diesel bowser (also known as a diesel pump). A valve 230 is provided intermediate the tank 110 and the nozzle 225, to enable access to diesel from the nozzle 225 to be controlled. In particular, a processor 235 of the control panel 205 is coupled to the valve 230, and is configured to prevent access to the diesel of the tank 110 by keeping the valve 230 closed unless the operator 125 is authorised using the RFID card and associated code.

[0085] The keypad 215 is also configured to receive odometer or hour meter readings of the equipment 120 prior to dispensing the diesel. The odometer or hour meter readings may be used to determine inconsistencies in diesel usage, which may correspond to faults in the equipment 120, theft or other issues. In such case, an alert may issue to the manager 105, for further investigation.

[0086] The keypad 215 may also be used to enter other details, such as fleet number, employee number or the like. In such case, the system may be configured to communicate with a fleet management system, and update data thereto. Such data could include fuel usage associated with the equipment, or any other suitable information. Similarly, information from the fleet management system, such as kilometres travelled, may be obtained and associated with the dispensed fuel. Such configuration provides more accurate travel data than if the operator is required to manually enter odometer data.

[0087] The tank 110 includes an ultrasonic level sensor 240, which is configured to measure a level of diesel 220 in the tank, by measuring an ultrasonic reflection from a surface thereof. In particular, the ultrasonic level sensor 240 is used to measure a height of the diesel with respect to a reference point (i.e. the location of the sensor). That height data is then used with either a table, or geometric information, which is stored in a memory 245 of the control panel 205 to determine a volume of diesel in the tank.

[0088] In case a model of the tank 110 is used, the model may, for example, comprise a cylinder (which may be standing or sitting) defined by a length and diameter. Similar, the model may be cuboid in shape, and defined by a length, width and height. The model is then used to define a volume of diesel in the tank using geometry. As an illustrative example, a shape may be defined by the model, truncated at a height corresponding to the level of diesel in the tank. A volume of the shape may then be determined, to determine a volume of diesel in the tank.

[0089] As the sensor 240 may not be able to be mounted directly on an edge of the model, a sensor offset may also be defined. The sensor offset may be applied to the sensor data to align the sensor reading to the model.

[0090] When it isn't possible, feasible or desirable to create a model for the tank 110, a lookup table may instead be used to map sensor data to tank volume. This data of the lookup table may be determined from known characteristics of the tank 110 (e.g. the tank is of a known type and size), or may be measured in a one-off manner. In particular, when empty, the tank 110 may be progressively filled with known volumes of diesel, and incrementally. That sensor data of these measurements may then be mapped to the associated volume in the look up table.

[0091] The ultrasonic level sensor 240 is advantageous in that it does not have any moving parts, and does not require any sensors or parts thereof to be submerged in the diesel. Furthermore, by determining the volume on site (rather than at the server 140), tanks can be added in a modular manner without needing to configure details of the tanks at the server 140. In particular, it enables the reported data to have meaning (i.e. volume), regardless of the shape or size of the tank.

[0092] A flow meter 250 is coupled intermediate the tank 110 and the nozzle 225, and when the operator 125 is dispensing diesel 220 through the nozzle 225, the flow rate is used to determine a volume dispensed. As such, the volumes dispensed from the tank 110 are logged by the control panel.

[0093] The control panel may be configured to take a volume measurement using the ultrasonic sensor 240 before and after filling. As such, the volume data of the flow meter 250 may be compared with the readings of the ultrasonic sensor 240 for consistency. Similarly, taking volume measurements in association with use of the diesel 220 ensures that measurements are taken when needed, rather than needlessly across a large time period of non-use.

[0094] While it is desirable to only measure liquid levels when needed, measurements may also be taken periodically. This is particularly useful in identifying leaks or damage to the tank, or unauthorised entry to the tank, particularly if the tank is not used often. As an illustrative example, an event may be scheduled to verify that the control panel 105 is still operational, and that the tanks 110 are at their expected levels.

[0095] While not illustrated, the skilled addressee will readily appreciate that the tank will include a pump, configured to pump the diesel through the nozzle. The pump is preferably activated on demand, such that it does not use power when idle. Similarly, the skilled addressee will readily appreciate that the control panel 105 and associated components (including the pump) are powered by an external power source. In remote environments, the power source may comprise one or more solar panels, coupled to batteries, to power the control panel 105 and associated components whether there is sun powering the solar panels or not.

[0096] Finally, the control panel 105 will generally be housed in a cabinet having doors, or is otherwise sheltered and protected from the weather and damage. The cabinet may be located on a side of the tank 110, or in proximity to the tank 110.

[0097] The control panel 105 may be configured to detect irregularities or tampering with the tank, and sound an alarm and issue an alert or notification when an irregularity or tampering is detected. One or more security sensors may be provided on the tank and/or the control panel.

[0098] As outlined above, the data captured and generated by the control panel is uploaded to the server 140, and this is performed using a remote data interface 255 in the form of a cellular data interface.

[0099] The server 140 is configured to generate dashboards based upon the received data of the tanks, which enables the manager 105 to make data-based decisions, rather than decisions based upon intuition alone. In particular, the dashboards may give important information to the manager 105 such as how much and when the diesel is used, which may be used to identify trends, and provides a record (log) of diesel use and deliveries, which is useful from an audit perspective.

[00100] Figure 4 illustrates a screenshot 400 of a first dashboard screen of the system 100, according to an embodiment of the present invention. The first dashboard screen provides an overview of all of the tanks 110, including total amounts of fuel remaining, historical usage and the like, as outlined below.

[00101] The first dashboard screen includes a reporting period selection component 405, which enables the manager 105 to select a reporting period for which the data of the dashboard relates. The reporting period selection component 405 includes a pre-defined period drop down menu, enabling the manager 105 to select from one or more pre-defined periods (e.g. last 7 days, last month), and custom range definition elements, enabling the manager 105 to choose custom start and end dates.

[00102] This is particularly useful if the manager 105 is interested only in recent activity, or activity over a specific period of time (e.g. in association with an incident).

[00103] The first dashboard screen includes a historical usage chart 410, which includes details of diesel usage of the tanks 110 over a period of time (e.g. the last 30 days). The historical usage chart 410 shows usage for each of a plurality of different sub periods (e.g. days).

[00104] The first dashboard screen further includes a fuel summary portion 415, which includes an overview of the fuel remaining, as well as the fuel used and delivered for a particular period of time. The period of time is defined by the reporting period selection component 405, defined above. As such, the manager 105 is able to quickly see how much fuel was used and delivered for a particular period selected by the manager 105.

[00105] The first dashboard further includes an alerts portion 420, which provides an overview of any alerts associated with the tanks. The alerts may be level alerts (e.g. the level of a tank 110 is below a defined threshold), or any other suitable alert.

[00106] In regard to low-level alerts, the system may be configured to enable the manager 105 to manually define the thresholds or criteria defining the alert. Similarly, the server 140 may be configured to send email or SMS alerts to the manager 105 or other users when an alert is detected.

[00107] The first dashboard includes a user usage portion 425, which graphically illustrates a portion of usage for each of a plurality of operators, based upon their usage of diesel. This is particularly useful in identifying operators whose diesel usage is above or below that of others, which can be further investigated, if desired.

[00108] Similarly, the first dashboard includes a tank usage portion 430, which graphically illustrates a portion of usage for each of the tanks 110. This is particularly useful in identifying tanks which are used much more or less than other tanks, which can be further investigated, if desired, or used in future planning.

[00109] Tables are associated with each of the user usage portion 425 and the tank usage portion 430, enabling the manager 105 to get an overview of the absolute usage (in addition to the relative usage provided by the graphical charts).

[00110] Finally, the first dashboard includes an event log portion 435, which provides a log of all events for the period defined by the reporting period selection component 405.

[00111] The first dashboard is designed to give the manager 105 a quick overview of all tanks, and thereby enable high-level discrepancies to be identified, and high-level decisions to be made. Different dashboards are, however, provided for individual tanks, and individual operators, as outlined below, and the user may navigate between different dashboards using a menu 440.

[00112] Figure 5 illustrates a screenshot 500 of a second dashboard screen of the system 100, according to an embodiment of the present invention. The second dashboard screen is similar to the first dashboard screen, but provides an overview of a selected tank 110, rather than all tanks.

[00113] The second dashboard screen includes a tank selection menu 505, which enables the manager 105 to select the tank.

[00114] The second dashboard screen includes the reporting period selection component 405, which enables the manager 105 to select the reporting period in the same manner as outlined above. Similarly, the second dashboard, includes the historical usage chart 410, which is configured to display historical usage data for the selected tank, rather than all tanks.

[00115] A fuel summary portion 510 is provided, much like the fuel summary portion 415 above, and includes an overview of the fuel remaining, as well as the fuel used and delivered for a particular period of time but for the particular tank. The fuel summary portion 510 also includes a graphical element showing a representation of the tank and the level (as a percentage) it is full.

[00116] The second dashboard further includes the user usage portion 425, as outlined above but in relation to the selected tank, and a delivery summary portion 515, which graphically illustrates a portion of delivery for each of a plurality of different operators, based upon their delivery of diesel. This is particularly useful in identifying who is delivering the diesel to the tank 110.

[00117] Finally, the second dashboard includes the event log 425, as illustrated above, but for the selected tank.

[00118] Figure 6 illustrates a screenshot 600 of a third dashboard screen of the system 100, according to an embodiment of the present invention. The third dashboard screen is similar to the second dashboard screen, but provides an overview for a selected operator 125 (user) rather than a selected tank 110.

[00119] The third dashboard screen includes an operator selection menu 605, which enables the manager 105 to select the operator to which the dashboard relates.

[00120] The third dashboard screen includes the reporting period selection component 405, which enables the manager 105 to select the reporting period in the same manner as outlined above. Similarly, the second dashboard, includes the historical usage chart 410, which is configured to display historical usage data for the selected user, rather than all users.

[00121] A fuel summary portion 610 is provided, much like the fuel summary portion 415 above, and includes an overview of the fuel used and delivered for a particular period of time but for the particular operator.

[00122] The third dashboard screen further includes a tank usage portion 615, which graphically illustrates the proportion of tanks from which the operator has used diesel, and a delivery summary portion 620, which graphically illustrates a portion of delivery by the operator to each of the tanks. This is particularly useful in identifying from where the operator is obtaining his diesel, and to where he is delivering diesel.

[00123] Finally, the third dashboard includes the event log 425, as illustrated above, but for the selected operator.

[00124] As mentioned above, the system 100 may be configured to generate alerts and send the alerts to one or more users, such as the manager 105. As an illustrative example, the system 100 may be configured to send the manager 105 (and/or other key personnel) an automatic text message or email when the tanks 110, or one or more of the tanks 110, meets a pre-defined criteria, such as a level condition (e.g. below a certain level), or a usage condition (e.g. usage from a tank was above a certain level). This provides the operator 125 with the information that they need to respond appropriately to the situation, in a timely manner.

[00125] The system 100 may also be used to issue alerts about the equipment 120, such as, when unexplained additional diesel usage from equipment is detected. This enables the manager 105 to investigate the equipment, and service the equipment if that is at fault, or secure the equipment if theft of diesel has been occurring.

[00126] Figure 7 illustrates a bulk liquid remote monitoring and management method 700, according to an embodiment of the present invention. The method 700 may be similar or identical to the method performed by the system 100 above.

[00127] At step 705, a liquid level in at least one tank is determined, using at least one sensor associated with the at least one tank. The at least one tank is configured to receive and store bulk liquid, such as diesel.

[00128] At step 710, a volume of liquid in the tank is determined using at least one controller in proximity to the at least one tank. The controller determines the volume of liquid based upon the sensor data of the at least one tank (i.e. the liquid level). This may be performed using a model of the tank and geometry, for example.

[00129] At step 715, the determined volume data is transmitted to a central server. As outlined above, the central server may log the volume data and use the volume data when generating dashboards.

[00130] At step 720, a user that is in proximity to the at least one tanks is authenticated. This may include scanning an RFID tag or fob of the user, and receiving a pin or other identifier associated with the user.

[00131] At step 725, liquid (e.g. diesel) is dispensed from the tank to the user. As an example, the liquid may be dispensed directly into a tank of equipment using a nozzle. The liquid is dispensed to the user upon authentication of the user, and if authentication fails, the user may be prevented from accessing the liquid.

[00132] At step 730, the flow of liquid to the user is monitored to determine a dispensed volume. In particular, a flow rate of the liquid may, together with a time the liquid was dispensed, may be used to determine the volume of liquid dispensed.

[00133] At step 735, the determined volume of liquid dispensed is transmitted to the central server. The determined volume may be transmitted with an identifier of the user, and a timestamp associated with the dispensing of the liquid. The central server may log the volume data, associated with the user, and use the volume data when generating dashboards.

[00134] While much the above has been made with reference to diesel, other fluids may be used. As an illustrative example, water may be stored and dispensed in similar ways, as may chemicals such as herbicides and pesticides.

[00135] Furthermore, while the tanks are generally static, embodiments of the invention may be used in relation to transportable/movable tanks. In such case, GPS data may be associated with the tank as it moves, and location information may be associated with the delivery of fuel.

[00136] Advantageously, the systems and methods described above enable remote monitoring of liquid storage tanks in a simple to use manner. This enables better decisions to be made about the tanks, such as the ability to place bulk delivery orders at a desirable time (such as when costs are relatively low). This in turn reduces the likelihood of a tank running low.

[00137] The systems and methods work with 2G, 3G, or 4G wireless communication, and can be fitted with solar panels and batteries, allowing it to be setup in remote areas without a direct power source. As the systems and methods enable non-mobile broadband communication (e.g. using messaging over 2G), the system 100 also enables sites 115 to be monitored in areas without mobile broadband Internet coverage.

[00138] The controller is enclosed in an electrical enclosure 10 and includes a main PCB 12 which acts as a central connection point and simplifies the wiring loom. The timer functionality is built into a separate daughter board 14 that is connected to the main PCB. The timer PCB 14 controls signals within the enclosure and delays switching on the ignition power after the operator has actuated the ignition switch. It also delays turning off the batch controller to allow time for a batch to be finalised. The system can be built with either a 240V to 12V supply or an external 12V supply. Both these options require a 12V to 24 V step up.

[00139] As shown in the drawing, the main PCB is operatively connected to a batch controller which, in turn, is operatively connected to a flow meter.

[00140] The main PCB is operatively connected to a Teletrac Navman Qube 300 which transmits the signals to a remote server.

[00141] Reference throughout this specification to 'one embodiment' or 'an embodiment' means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearance of the phrases 'in one embodiment' or 'in an embodiment' in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more combinations.

[00142] In compliance with the statute, the invention has been described in language more or less specific to structural or methodical features. It is to be understood that the invention is not limited to specific features shown or described since the means herein described comprises preferred forms of putting the invention into effect. The invention is, therefore, claimed in any of its forms or modifications within the proper scope of the appended claims (if any) appropriately interpreted by those skilled in the art.

Claims (24)

CLAIMS:

1. A monitoring and/or management system for monitoring bulk liquid from a remote location, the system including: at least one tank, configured to receive and store bulk liquid; at least one sensor associated with the at least one tank, the at least one sensor configured to sense a measurement relating to the quantity of liquid in the at least one tank; and a controller in proximity to the at least one tank, the controller being configured to determine a volume of liquid in the tank in response to the measurement sensed by the at least one sensor, and the controller also being configured to transmit volume data relating to the determined volume to a central server.

2. A monitoring and/or management system according to claim 1, wherein the at least one sensor is configured to sense the level of liquid in the tank in response to the level of liquid sensed by the sensor.

3. A monitoring and/or management system according to claim 1 or claim 2, wherein the sensor is an ultrasonic sensor that is configured to determine a level of liquid in the tank with reference to a reference point.

4. A monitoring and/or management system according to any one of claims 1 to 3, wherein the controller includes a transmitter that is configured to wirelessly transmit the determined volume of liquid to the central server.

5. A monitoring and/or management system according to claim 4, wherein the transmitter is a cellular transmitter transmitting the volume data wirelessly to the central server using a cellular base station.

6. A monitoring and/or management system according to claim 5, wherein the cellular transmitter is configurable to include transmitting the volume data using a non-data cellular service.

7. A monitoring and/or management system according to any one of claims 1 to 6, including a valve operatively associated with each tank for controlling the discharge of liquid from the tank, the valve being operatively connected to the controller associated with that tank for controlling the flow of liquid from the tank by opening and closing the valve.

8. A monitoring and/or management system according to any one of claims 1 to 7, further including a flow meter mounted in line with the valve for measure the flow of liquid from the tank, and wherein the controller is operatively connected to the flow meter for receiving flow measurements therefrom, determining a volume of liquid discharged from the tank, and transmitting data relating to the volume of liquid discharged from the tank to the central server.

9. A monitoring and/or management system according to any one of claims 1 to 8, wherein the system includes a reader for controlling access to the/each tank and limiting access to authorized users.

10. A monitoring and/or management system according to claim 7, wherein the reader includes a wireless access tag reader a wireless access tag reader that is operatively coupled to the controller, and the controller is configured to control access in response to data read by the wireless access tag reader.

11. A monitoring and/or management system according to claim 9 or claim 10, further including a keypad, for enabling a user to enter a pin code or password, wherein the controller is configured to control access to the/ each tank at least in part through data entered in the keypad.

12. A monitoring and/or management system according to any one of claims 1 to 11, wherein the controller is configured to receive an equipment identifier identifying a piece of equipment to which liquid is to be supplied, to log a record of the piece of equipment to which the liquid is supplied.

13. A monitoring and/or management system according to claim 12, wherein the controller is configured to transmit data relating to relating to the equipment identifier and equipment usage associated with that equipment identifier to the central server.

14. A monitoring and/or management system according to claim 10 or claim 11, wherein at least one piece of equipment has an odometer or hour meter reflecting usage of that piece of equipment, and the controller is configured to log an odometer or hour reading of that equipment when liquid is delivered to that equipment.

15. A monitoring and/or management system according to any one of claims 1 to 14, wherein the central server is configured to generate a graphical user interface (GUI), and the GUI is configured to display at least volume data of the at least one tank.

16. A monitoring and/or management system according to claim 15, wherein the GUI is configured to display data indicative of a flow of liquid from the tank, and/or data relating to a particular piece of equipment, and/or data relating to a particular operator.

17. A monitoring and/or management system according to claim 15 or claim 16, having a plurality of said tanks, and the GUI is configured to display volume data for the plurality of tanks, wherein the volume data includes displaying volume data for each of the plurality of tanks and/or volume data that is aggregated for the plurality of tanks.

18. A method for monitoring and/or managing bulk liquid from a remote location, the method including: using at least one sensor associated with at least one tank configured to receive and store bulk liquid, to sense a measurement relating to the quantity of liquid in the at least one tank; and determining, using at least one controller in proximity to the at least one tank, a volume of liquid in the tank based upon the measurement in the at least one tank, and transmitting volume data relating to the determined volume of liquid to a central server.

19. A method for monitoring and/or managing bulk liquid according to claim 18, wherein a valve is operatively associated with each tank for controlling the flow of liquid from the tank, and the method includes controlling opening and closing the valve to control the flow of liquid by means of the controller.

20. A method for monitoring and/or managing bulk liquid according to claim 18 or claim 19, wherein transmitting to a central server includes wirelessly transmitting the volume data to the central server by means of a cellular transmitter.

21. A method for monitoring and/or managing bulk liquid according to claim 20, wherein wirelessly transmitting to the central server includes transmitting the volume data using a non data cellular service, such as text messaging.

22. A method for monitoring and/or managing bulk liquid according to any one of claims 18 to 21, further including configuring the central server to generate a GUI and configuring the GUI to display volume data of the at least one tank.

23. A method for monitoring and/or managing bulk liquid according to any one of claims 18 to 22, wherein the at least one tank stores diesel fuel which is used as a fuel for a piece of equipment.

24. A method for monitoring and/or managing bulk liquid according to any one of claims 18 to 22, wherein the at least one tank stores water.

` 150 130 125 115 135

145

105 120 110 1/11

135 140

110 115

Figure 1