The present invention relates to a demand management system and method of demand management for fluid networks, and relates particularly, though not exclusively, to demand management systems for open conduits (channel networks) and closed conduits (pipelines).
In our U.S. Pat. No. 7,152,001, the entirety of which is herein incorporated, there is disclosed a computer based system for predicting the fluid level in a fluid flow network. The system has been very successful as it can use past and present measurements of parameters to predict and control fluid level and flow. The system gathers data from timed fluid levels and opening positions of regulators or valves to provide a model from which fluid levels and flow can be determined in real time.
Water providers, for example, irrigation authorities, are being required to provide accurate delivery of water to their customers at a time determined by the customer.
It is an object of the present invention to provide a demand management system for fluid networks to provide a measured fluid flow under a time regime.
The present invention in one aspect provides a method of demand management for fluid networks, said method including the steps of providing a computer controlled fluid network for delivery of fluid to at least one customer, maintaining a real time database within said computer controlled fluid network of predetermined parameters, requesting a flow rate and time of delivery of said fluid from the fluid network through a user interface to said at least one customer, determining, using predetermined parameters from said real time database, the availability of providing said delivery of said fluid from the fluid network to said at least one customer based on hydraulic capacity of said fluid network, and, if said hydraulic capacity is available, calculating parameters using said real time database to deliver said fluid to said at least one customer through said computer controlled fluid network.
Preferably said method includes the steps of allowing a plurality of customers to access the user interface and said computer controlled fluid network determining a priority and weighting of each request to ensure continuance of said hydraulic capacity.
The invention may also provide the steps of simulating the hydrostatic pressure within said computer controlled fluid network to determine said hydraulic capacity.
In yet a further embodiment said computer controlled fluid network may include a selection from one or more of fluid regulators, valves and sensors coupled to an interface for providing system measurements to said real time database.
Preferably data from a SCADA interface is used to calibrate and continually fine tune the computer controlled fluid network using a model of the pipe network based on system identification techniques.
The structure and functional features of a preferred embodiment of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawing, in which:
A demand management system 10 has a SCADA (Supervisory Control and Data Acquisition) or network software interface 12 which controls the demand management system 10. The term SCADA usually refers to centralized systems which monitor and control systems spread out over large areas.
Known models for pipe networks would be used in the management of demand for these networks. Data from the SCADA interface 12 would be used to calibrate and continually fine tune the model of the pipe network based on system identification techniques. Flow measurement and pressure head measurements (not shown) are located at points (not shown) on the pipe network and are interrogated by the SCADA interface 12. The SCADA interface 12 will interpret the data supplied to calibrate a model of operation to the desired accuracy. The supply points to users 14 are the primary form of control used with a pipe network. The SCADA interface 12 interacts with a main database 16 which has the models and control software associated therewith. The real time measurements from the system are all transferred to main database 16. An operator 18 can interact with the interface 12 to allow the operator to review remote monitoring, control the system 10, check and react to alarm criteria, review real time and historic data and other predetermined requirements.
Customers 20 communicate with an interface 22 which allows a customer to order a selected flow rate at a selected time. Interface 22 can be computer, keyboard or Internet based to allow the customer's desired selections to be entered into the system 10. The desired selections can be considered to be an order for an allocation of water. The system software at step 24 ascertains whether the selected flow rate and selected time can be met by the hydraulic capacity of the network.
If the system can meet the selected flow rate and selected time the order is accepted at step 26. The order will be added to the main database 16 as indicated by path 28. Main database 16 will schedule the selected flow rate and selected time at step 30 to provide appropriate control signals to required valves (not shown) to deliver the selected flow rate at the selected time at step 32.
If the system cannot meet the selected flow rate at the selected time, then at step 34 an array of alternatives, for example, different times and/or different flow rates will be provided to customer 20. The management of demand ensures the hydraulic performance of the fluid network does not deteriorate when the required flow rate exceeds the hydraulic capacity of the fluid network. Business rules, specific to the water supply authority, can be used to determine the priority given to orders and the re-scheduling of any orders that cannot be satisfied. Customer 20 can then accept the rescheduling of the selected time and/or flow rate at step 36 or cancel the order.
Step 24 has a further input from step 38 which calculates the available pressure capacity of the system and provides the desired flow rate to step 24. Step 38 will have further inputs on the maximum pressure that the pipeline can tolerate at 40 and the minimum pressure available for satisfactory service at 42. The software includes a step 44 providing a model which simulates hydrostatic pressure along the pipeline based on demand parameters from main database 16. The model at step 44 provides information in real time and will be influenced by the output 46 from the flow rate delivered to the required valves (not shown) to deliver the selected flow rate at the selected time from step 32.
Main database 16 provides an input 48 to the model at step 44 containing current and future demand information. The fluid network model at steps 38, 44 ensures any future flow demand on the fluid network is within the hydraulic capacity of the fluid network to deliver the required flow regime. This procedure requires that any planned future change in flow demand be processed using the model 38, 44 of the fluid network before being accepted as future change in demand on the fluid network. Future changes in flow demand are therefore processed by the model 38, 44 to determine if the controller of the fluid network is capable of delivering the required flow. Under this regime changes in flow demand are processed as order transactions as previously described. The model establishes if an order request does not result in the maximum and minimum flow boundaries 40, 42 to be exceeded at any point on the network.
The system requires orders to be first processed some period in advance of the desired flow change. The preferred embodiment uses a computer application or program to process individual orders on-line with the model 38, 44 determining if the demand can be met given the aggregate knowledge of all orders on the fluid network. Orders may also be processed in batch mode where a group of orders are pre-processed where each order may be given a pre-determined priority or weighting. If a pump is used as part of the fluid network, the pump can also provide regulated control of the fluid network to achieve the required flows, levels and pressures.
Although the preferred embodiment uses a closed conduit (pipeline network) the management of demand is equally applicable to channel networks (open conduits). Pipes typically operate within a wider range of head pressure and therefore do not require as much network control as a channel network. The controller for a pipe network is much simpler for a pipe network with the principle form of control being maintaining the flow at the supply point equal to that of the order. The management of demand is especially applicable to gravity pipe networks commonly used for the supply of irrigation water.
Gravity pipe networks typically operate within limited pressure head and therefore are constrained in their capability to continually meet demand.
Pumps may also be used in open conduits.
The invention will be understood to embrace many further modifications as will be readily apparent to persons skilled in the art and which will be deemed to reside within the broad scope and ambit of the invention, there having been set forth herein only the broad nature of the invention and certain specific embodiments by way of example.
Number | Date | Country | Kind |
---|---|---|---|
2011903084 | Aug 2011 | AU | national |
This application is a continuation of U.S. patent application Ser. No. 14/236,616, filed Jun. 17, 2014 and entitled “Demand Management System for Fluid Networks,” now U.S. Pat. No. 9,563,207, which is a national stage application pursuant to 35 U.S.C. § 371 of International Application No. PCT/AU2012/000907, filed Aug. 1, 2012, which claims priority to AU Patent Application No. 2011903084, filed Aug. 1, 2011, the disclosures of which are hereby incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
4444625 | Smith | Apr 1984 | A |
4730637 | White | Mar 1988 | A |
4925444 | Orkin | May 1990 | A |
5154314 | Van Wormer | Oct 1992 | A |
5257982 | Cohen | Nov 1993 | A |
5741980 | Hill | Apr 1998 | A |
5941305 | Thrasher | Aug 1999 | A |
6801135 | Schultz | Oct 2004 | B2 |
6817419 | Reid | Nov 2004 | B2 |
7017116 | Elsbree | Mar 2006 | B2 |
7152001 | Aughton | Dec 2006 | B2 |
7274996 | Lapinski | Sep 2007 | B2 |
7673690 | Somogyi | Mar 2010 | B2 |
7869978 | Anderson | Jan 2011 | B2 |
8886482 | Higgins | Nov 2014 | B2 |
8892372 | Peterson | Nov 2014 | B2 |
9322512 | Bremer et al. | Apr 2016 | B2 |
20030107588 | Elsbree | Jun 2003 | A1 |
20040128034 | Lenker | Jul 2004 | A1 |
20080281534 | Hurley | Nov 2008 | A1 |
20090099701 | Li | Apr 2009 | A1 |
20100168927 | Burrows | Jul 2010 | A1 |
20100204924 | Wolfe | Aug 2010 | A1 |
20100329903 | Fong | Dec 2010 | A1 |
20110093123 | Alexanian | Apr 2011 | A1 |
20110115223 | Stahlkopf | May 2011 | A1 |
20110231320 | Irving | Sep 2011 | A1 |
20110307203 | Higgins | Dec 2011 | A1 |
20120192965 | Popper | Aug 2012 | A1 |
20120317058 | Abhulimen | Dec 2012 | A1 |
20130231787 | Chapman | Sep 2013 | A1 |
20160058933 | Ballantyne | Mar 2016 | A1 |
Number | Date | Country |
---|---|---|
101641654 | Feb 2010 | CN |
101858095 | Oct 2010 | CN |
H09217900 | Aug 1997 | JP |
20090002115 | Jan 2009 | KR |
2012019898 | Feb 2012 | WO |
Entry |
---|
Yao, Xiaoming, “Design and Implementation of Java EE-based Urban Water Supply Management System,” Master's Degree Thesis, Information Science and Technology Series, No. 6, Jun. 15, 2010. |
Chinese Patent Application No. 201280046810.X, Office Action dated Oct. 8, 2016. |
European Patent Application No. 12820610.9, Search Report dated May 13, 2016. |
International Application No. PCT/AU2012/000907, International Search Report and Written Opinion dated Sep. 12, 2012 (annotated by Applicant to indicate errors in original document). |
Number | Date | Country | |
---|---|---|---|
20170147010 A1 | May 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14236616 | US | |
Child | 15425911 | US |