The present subject-matter generally relates to a distributed monitoring and control system. More specifically, the present subject-matter relates to a system using distributed monitoring and control of combined sewer systems to reduce combined sewer overflow conditions.
In many cities wastewater and rainwater are collected together in a combined sewer system. These combined sewer systems create a potential for a combined sewer overflow (CSO). A CSO occurs when a wastewater treatment facility experiences excessive inflow due to wet weather conditions resulting in an overflow or discharge of contaminated water. In some cases, the overflow water backs up into homes or businesses. In order to prevent raw sewage backup into homes and businesses, waste water treatment facilities often divert the overflow into an open stream or river. Accordingly, a CSO event often results in the contamination or rivers, lakes and ocean shores and presents numerous environmental health-related dangers.
The problems associated with CSO events have been addressed by replacing combined sewers with dual collection and disposal systems, providing off-line storage facilities, such as providing underground tunnels, or expanding the capacity of the overloaded waste water treatment facility. However, these solutions require intensive and expensive construction, which can be disruptive to cities and their population. Moreover, separating wastewater and rainwater collection does not completely solve the environmental problems since untreated storm water often carries contaminants washed away from streets.
An alternative option is to use in-line storage using real-time monitoring, which monitors the flow and composition of the fluid in the sewer. When a CSO event is predicted the system reacts by using the pipes as a temporary storage. A real-time control system calculates the unused volume in each of the main arterial pipes and sends command signals to gates, inflatable dams or valves to regulate the flow. Existing in-line storage solutions suffer because the large amount of information required to effectively control the system must be transmitted to a central processor for processing and the communication, monitoring and control require great expense and are prone to failure.
The present subject-matter provides a distributed monitoring and control system. The distributed monitoring and control system may be implemented to reduce the occurrence of combined sewer overflow. The distributed monitoring and control system includes a plurality of nodes, each of which includes a processor, a memory and a transceiver. The system includes a plurality of nodes, including nodes having different functions, such as rNodes, iNodes, aNodes and gNodes. Each of the nodes provides interconnectivity between nodes that cannot communicate directly. The iNodes further include sensors to monitor the flow in the sewer and a sensor interface. The aNodes further include actuators for the control systems. The gNodes may include the functionality of the other nodes and further include a connection to another network outside of the wireless network of nodes. The nodes may use a control algorithm that allows the system to function without a central computing element, thereby increasing the robustness of the system.
An advantage of the distributed monitoring and control system is the reduction of overflow conditions in combined sewer systems.
Another advantage of the distributed monitoring and control system is the ability to use of a distributed control algorithm and an ad-hoc wireless communication system to manipulate flow control structures.
A further advantage of the distributed monitoring and control system is the ability for wireless and battery operation to allow fast and easy installation.
Yet another advantage of the distributed monitoring and control system is the decentralization and redundancy provides robustness to allow the system to function even with some malfunctioning parts.
Still another advantage of the distributed monitoring and control system is the distributed nodes and the lack of a centralized control system provides decreased vulnerability to individual sensor failure and central computer failure.
Another advantage of the distributed monitoring and control system is the distribution of the sensors enables more precise and more accurate measurements even when individual measurements are not as accurate.
Additional objects, advantages and novel features of the examples will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following description and the accompanying drawings or may be learned by production or operation of the examples. The objects and advantages of the concepts may be realized and attained by means of the methodologies, instrumentalities and combinations particularly pointed out in the appended claims.
As shown in
The rNodes 16 include a microprocessor, a memory and a transceiver, such as, for example, a radio transceiver. The main purpose of the rNodes 16 is to provide interconnectivity between nodes 12 that cannot communicate directly. For example, an rNode 16, or a series of rNodes 16, may function to connect an iNode 14 and an aNode 18 that are geographically separated by a distance greater than their transceivers' range.
The iNodes 14 include the same elements as the rNodes 16 and additionally include a sensor interface. The sensor interface allows a variety of sensors to be attached to the iNode 14. In the embodiment shown in
The aNodes 18 include the same elements as the rNodes 16 and additionally include an actuator interface. The actuator interface allows different types of actuators 23 (see
The gNodes 20 include the same elements as the rNodes 16 and additionally include a networking interface. The networking interface allows the gNodes 20 to connect the wireless network formed by the nodes 12 to another network, such as, for example, a wide area network, a local area network or a cellular data network. Connecting the wireless network of nodes 12 to another network allows an operator or observer to interact with the network or the network data, as well as additional nodes 12 outside of the wireless network. It is contemplated that the gNodes 20 are not essential for the operation of the distributed monitoring and control system 10, particularly if there is no need to share the information with other networks.
In the embodiment shown in
In the embodiment shown in
The memory 24 in the embodiment of the iNode 14 shown in
The transceiver 26 in the embodiment of the iNode 14 shown in
The processor 22 controls the transceiver power control. The transceiver power control drastically reduces the power consumption of the transceiver 26 when no events require the transmission of information. Further, the use of wireless multihop connections allows the use of small transceivers 26 with limited transmission range since it is not necessary to transmit to a distant central location, which allows the use of batteries or solar power to power the nodes 12. In addition, as shown in
The power supply 28 in the embodiment of the iNode 14 shown in
The nodes 12 and other devices connected to the nodes 12, such as the sensors 21 and actuators 23, may operate using limited power sources, such as, for example, batteries or solar power, in order to allow wireless installation. Although wireless installation can reduce installation costs, it may require aggressive power management. Accordingly, the processor 22 may be programmed with power management software to control power delivery to components such as, for example, sensors 21, actuators 23, transceivers 26, memory 24 and processor 22. For example, in low power state, the power management software disconnects the power to the sensors 21, actuators 23 and transceivers 26 and reduces the power provided to the memory 24 and processors 22, when advantageous. In particular, the power management software only delivers power to the sensors 21 when needed via the sensor interface 30, which contains MOSFET transistors that connect the power supply 28 to the sensors 21 for short periods of time.
Although
For example, the aNodes 18 may include an actuator interface capable of generating a 12 Volt pulse modulated signal for controlling a DC electric motor and two current outputs. The current outputs can be used to send signals to an actuator 23 using a standard 4-20 mA input interface. Since the aNodes 18 are typically connected to power consuming actuators 23 that require external electrical connection, power management is not as critical in these devices.
Also as an example, the gNodes 20 may be formed by connecting an iNode 14, an rNode 16 or an aNode 18 to a larger processor board. For example, the gNodes 20 may be connected to a Technologic Systems TS5600 that features a 133 MHz AMD 586 embedded microprocessor running the Linux operating system. The processor board also includes a PC card slot that can allocate a 802.11 or WiFi interface card or a cellular modem card. The processor board further includes an Ethernet connector. The processor board communicates to the gNode 20 using the serial interface 36.
As described above with respect to the iNode 14 shown in
To implement the distributed monitoring and control system 10 shown in
For example, in the embodiment of the distributed monitoring and control system 10 described herein with respect to monitoring and controlling sewer systems, it is contemplated that the expected internode connectivity will be low, typically in the range of 60% of data packet throughput between neighboring nodes 12. Assuming an in-line configuration, in which only neighboring nodes 12 can communicate with each other, the data packet throughput between one end of the line to the other using conventional communication algorithms would be 0.6% or 0.6%. Accordingly, a robust routing algorithm is required to increase throughput in these types of low connectivity networks.
The distributed monitoring and control system 10 shown in
Each data packet contains data to aid the broadcasting process. For example, a hop counter may be used to limit the number of nodes 12 through which a message can travel from its original source. Each time a node 12 transmits a broadcast message data packet, the hop count increases. When the hop counter reaches a predefined value, the data packet gets discarded without being retransmitted. An identification number may also be appended to the data packet to ensure each message is propagated outward from its origin. The identification number is generated at the origin node by combining the hop counter with the network address of the node 12. If a node 12 receives a data packet with an identification number that matches the identification number of a previously received message, the data packet gets discarded without being retransmitted. Moreover, timing information may be appended to a message to allow each node 12 to calculate the time it took a message received to arrive since being transmitted by the origin node 12.
The routing algorithm allows any node 12 in the network to transmit a message to specific nodes 12 within the network designated as data sinks. This feature is particularly useful, for example, for the iNodes 14 that need to send information to specific aNodes 18 or gNodes 20. Each node 12 contains a table of the data sinks in the network. Associated with each entry is a number called the gradient. The gradient number is smaller when the node 12 is closer to the data sink. Each data sink itself has a gradient number of 0. When a node 12 is required to transmit a message to a data sink, the node 12 broadcasts the message with its own gradient number and the data sink address appended to the data to be transmitted. If a node with lower gradient number receives the message, it broadcasts an acknowledgement packet, including its own gradient number, to the data sink. If the original message source does not receive an acknowledgement packet with a gradient lower than its own before a specified time it broadcasts again. The number of retries can be specified in the software and may, for example, have a default value of three. If a node 12 receives a packet with a gradient number equal or greater than the senders gradient, the packet may be discarded. Alternatively, additional routes may be established by allowing rebroadcasting when the gradient difference is within an established threshold. In either example, after a node 12 has sent an acknowledgement packet, it will rebroadcast the original message with its own gradient number and the process is repeated until the message arrives to its destination, specifically, the node with the matching data sink address. In this way the routing algorithm ensures that the message will approach the destination even if it must branch off in the process and take different routes. This type of routing protocol belongs to a class of stateless routing protocols that are particularly resilient to node failure because it allows the network to function without any node keeping track of information paths. This type of stateless routing protocol avoids the problems associated with gateway based routing protocols.
A message identification number similar to the one used for the broadcasting algorithm can be used to prevent the algorithm from using overlapping routes. Also, by enforcing a requirement that the gradient difference between the sender and the rebroadcasting node has to be bigger than a certain threshold, the number of potential routes can be reduced.
In order to establish the algorithms described above ad-hoc, a broadcasting algorithm is used by the data sink nodes 12 to setup routing (or gradient) tables in each node 12. By receiving the message broadcast by the data sink, each node 12 can establish its number of hops from the data sink. This information is used to generate an appropriate gradient number that is then stored in each node's routing algorithm table together with the data sink address.
Several additional tasks may be performed by the network, including, for example, network synchronization. Network synchronization allows the nodes 12 to undergo alternating cycles of deep sleep mode and active mode in a synchronized fashion. In this way, the nodes 12 may all be active and can perform control and communication activities while in the active mode and otherwise enter deep sleep modes for low power consumption.
Typically, the power consumption in active modes can be up to 2500 times the power consumed in sleep modes. Therefore, it is essential that the nodes 12 remain in sleep mode as long as possible. To achieve this, the nodes 12 enter and leave power cycles in a synchronized fashion. The time when all the nodes 12 are in active mode is referred to as the “active window.” The active window can be a few seconds per cycle, for example, thirty seconds. During the active window all internodal and control algorithms must be executed. In one example, one node 12 in the network or subnetwork is in charge of synchronization for the entire network or subnetwork. Typically, this node 12 will be a gNode 20, but it can be any other node 12. This node 12 is referred to as the synchronization node 12.
The synchronization node 12 can send out a synchronization packet via the broadcasting algorithm previously described. The synchronization packet is sent during the active window. The synchronization packet may include, for example, the time when the request for a new synchronization was issued, the packet traveling time and the sleeping time. Each receiving node 12 will adjust the remaining active window time to match the one described in the packet by using the traveling time. Additionally, in the case of CSO control for example, an adaptive power cycle scheduling may be used to reduce power consumption when wet weather conditions are not forecasted by using a greater amount of time between active windows. Conversely, when wet weather conditions are forecasted, the sleeping time may be reduced, allowing critical information about the sewer system to be shared throughout the network on an accelerated schedule. Due to the natural drift of the internal clocks of the nodes 12, the synchronization process must be performed periodically, typically once a day. Regular synchronization of the internal clocks of the nodes 12 ensures tight synchronization and, therefore, well aligned active windows among all the nodes 12.
As described herein, the low power sleep mode may be executed by a software component within the node 12 that puts the radio transceiver 26 in low power mode, disables the memory 24, turns the power supply for the sensors 21 off, and stops all timers except for a single unique timer that is used to maintain the adaptive power scheduling cycle. The timer allowed to run by the low power mode software component and is setup to wake up the processor after a time specified by the adaptive power cycle scheduling protocol.
The robustness of the distributed monitoring and control system 10 can be further enhanced by organizing the nodes 12 into hierarchical subnetworks. For example, a subnetwork can be formed to include at least one gNode 20 which may communicate with other networks or subnetworks. By way of example, the distributed monitoring and control system 10 shown in
As shown in
The distributed monitoring and control system 10 can be implemented to reduce the occurrence of combined sewer overflow (CSO) events. In order to reduce the occurrence of CSO events, the distributed monitoring and control system 10 performs two functions: monitoring and actuation. Similarly, the distributed monitoring and control system 10 can be implemented to maximize system performance, optimize collector pipes capacity, flush sewer pipes to reduce solids attached to pipe walls, divert flow to other locations and to reduce sewer overflow to other external systems, such as, for example, a treatment facility.
The monitoring function of the distributed monitoring and control system 10 is accomplished using the information acquired through the iNodes 14. For example, in the embodiment described with respect to
The actuation function of the distributed monitoring and control system 10 is accomplished by the aNodes 18 or other nodes 12 including the functionality described above with respect to the aNodes 18. For example, the actuation function may be carried out by a node 12 that incorporates the functions of both the aNode 18 and the gNode 20 described above.
The control actions performed by the aNodes 18 are determined using a model-based distributed system control algorithm incorporating a model of the combined sewer system. Each aNode 18 receives the relevant information from the surrounding nodes 12 to make its own control command decision. The model-based distributed system control algorithm further enhances the robustness of the distributed monitoring and control system 10 and enables the distributed monitoring and control system 10 to operate with limited amount of communication between nodes 12. Limited communication is key to the aggressive power management schemes described above. Moreover, limited communication requires limited bandwidth to operate the wireless network of nodes 12, further improving the cost effectiveness and robustness of the distributed monitoring and control system 10.
Using a model-based distributed system control algorithm further allows the distributed monitoring and control system 10 to operate in a distributed fashion. In other words, the distributed monitoring and control system 10 does not require a central computing element to process the data from the entire system to determine and execute control commands. As a result, the distributed monitoring and control system 10 is capable of being employed to monitor and control massive amounts of information and geography.
A small sewer network including a distributed monitoring and control system 100 is shown in
ha(k+1)=ha(k)+(ua(k)−qa(k))Ta
hb(k+1)=hb(k)+(ub(k)−qb(k))Tb
qc(k+1)=qa(k+1)+qb(k)
qd(k+2)=qc(k)
he(k+1)=he(k)+(qd(k)−qe(k))
This equation system can be further represented in the form of a traditional discrete linear time invariant state space equation with unknown disturbances Ua and Ub:
The mathematical description of the sewer elements can be made more accurate by utilizing more detailed mathematical descriptions of the individual elements. The above simplified system is used here for clarity of the control approach used. The region over which the system is allowed to evolve is constraint as a result of limitations in the actual system such as maximum height in the reservoirs or maximum flow capacity in the pipes. With the information obtained by any sensors measuring Ua and Ub, control strategies can be calculated to maximize the use of the reservoirs during rain event, thus reducing flow directed to the water treatment facility. Networked model-based techniques, such as the ones described in Ref. Handbook of Networked and Embedded Control Systems, 2005, Birkhäusen, pp. 601-625, the entirety of which is incorporated herein by reference, can be used to determine the appropriate control strategy for the linearized system presented with reference to
An alternate decentralized approach for controlling CSO events is a “price-based” model-predictive control scheme. A price-based control can, for example, be implemented to stagger the operation of the actuators 23 connected to the aNodes 18 in a manner that maximizes the power of the water flowing through the sewer network. This is accomplished by having each of the aNodes 18 make local decisions about actuation on the basis of the head measured by the nodes 12 immediately upstream and downstream from each aNode 18. Because an individual aNode's 18 control decision is based only on the head of its immediate upstream/downstream nodes 12, this control strategy is highly decentralized
For example, the price-based model predictive control algorithm may use a decentralized approach to solve the following flow optimization problem
where x is a real vector whose components represent the head in the sewer network and q is a real vector whose components represent the flow rates in the sewer network. D is an incidence matrix for the directed graph formed by the sewer system, for example, the manholes and pipes. The optimization problem seeks to maximize the integrated flow power, xTDTq, discounted by the square of the head levels, xTx. This maximization is done subject to a constraint that the flow rate, q, is bounded above by the function, Q(DTx), which relates flow rate, q, to the difference between the head levels in a pipe's upstream and downstream manhole. The second constraint is a differential equation that requires the rate of change in the head equal the total inflows into the manhole minus the total outflows from the manhole.
The flow optimization problem shown above is an optimal control problem whose solution via Pontryagin's maximum principle yields an optimal flow of the form
where di is the jth row of the incidence matrix D and where x and p are time-varying functions satisfying a two-point boundary value problem (“TPBVP”). The function x represents the head in the sewer system nodes 12. The function p (also called the co-state) is interpreted as a price that the network charges for storing water. The control law says that if the head difference exceeds a level set by the price, p, then the corresponding aNode 18 should increase flow, otherwise the flow should be decreased or stopped. This is a decentralized control since decisions are based on heads and prices of nodes 12 adjacent to the current node 12. The strategy controls the nodes' 12 outflows in a way that maximizes the difference between the head of two adjacent nodes 12. This leads to a staggered closing and opening of flow in a way that maximizes the flow power (product of the head difference and flow rate) while trying to control the head level at all nodes 12.
The TPBVP shown above in the price-based model predictive control algorithm is solved using a model-predictive control. Model-predictive (also called receding horizon) control generates a sequence of controls that are optimal over a finite horizon of length T. Using this stabilization technique it can be assured that this sequence asymptotically converges to the solution of an infinite-horizon optimization problem for any choice of horizon, T. Since the computational complexity associated with solving the TPBVP decreases with smaller T, the use of the stabilized receding horizon controller allows us to develop a computationally tractable control algorithm that is well suited to processing power of the nodes 12.
In another example, the system provided with reference to
Although the embodiment of the distributed monitoring and control system 10 described above specifically addresses the problems associated with combined sewer systems, the distributed monitoring and control system 10 provided herein may be adapted to address various environmental, security, engineering and other problems. For example, a distributed monitoring and control system may be used for tracking and monitoring people, vehicles and animals, for traffic control, as a forest fire early warning system, for fire or harmful gas detection, for inventory monitoring, for structural integrity monitoring or any other system in which distributed monitoring and control may be advantageous. In order to address these various systems, the sensors, actuators and algorithms described above may be adapted to the problems associated with the particular application.
It should be noted that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. Such changes and modifications may be made without departing from the spirit and scope of the present invention and without diminishing its attendant advantages.
The present application claims the benefit of U.S. Provisional Application No. 60/682,384, filed May 19, 2005.
Number | Name | Date | Kind |
---|---|---|---|
3638490 | Brettner | Feb 1972 | A |
4026151 | Fitzgerald | May 1977 | A |
4058011 | Martig, Jr. | Nov 1977 | A |
4070563 | Petroff | Jan 1978 | A |
4116061 | Petroff | Sep 1978 | A |
4150683 | Simon | Apr 1979 | A |
4188968 | Trobaugh et al. | Feb 1980 | A |
4200911 | Matsumoto | Apr 1980 | A |
4211111 | Petroff | Jul 1980 | A |
4221127 | McClure | Sep 1980 | A |
4258747 | Trobaugh | Mar 1981 | A |
4268383 | Trobaugh | May 1981 | A |
4295197 | Petroff | Oct 1981 | A |
4344329 | Petroff | Aug 1982 | A |
4386409 | Petroff | May 1983 | A |
4407158 | Petroff | Oct 1983 | A |
4571997 | Kepple et al. | Feb 1986 | A |
4630474 | Petroff | Dec 1986 | A |
4892440 | Regan | Jan 1990 | A |
4987913 | Kodate et al. | Jan 1991 | A |
4997312 | Regan | Mar 1991 | A |
5020374 | Petroff et al. | Jun 1991 | A |
5161911 | Regan | Nov 1992 | A |
5198989 | Petroff | Mar 1993 | A |
5321601 | Riedel et al. | Jun 1994 | A |
5342144 | McCarthy | Aug 1994 | A |
5365423 | Chand | Nov 1994 | A |
5371859 | Lennartsson | Dec 1994 | A |
5423226 | Hunter et al. | Jun 1995 | A |
5448476 | Kurokawa et al. | Sep 1995 | A |
5506791 | Hungerford et al. | Apr 1996 | A |
5608171 | Hunter et al. | Mar 1997 | A |
5633809 | Wissenbach et al. | May 1997 | A |
5684250 | Marsh et al. | Nov 1997 | A |
5834659 | Ortiz et al. | Nov 1998 | A |
5835836 | Hirao | Nov 1998 | A |
5870692 | Millo | Feb 1999 | A |
5874903 | Shuey et al. | Feb 1999 | A |
5886267 | Ortiz | Mar 1999 | A |
5905208 | Ortiz et al. | May 1999 | A |
5942698 | Stevens | Aug 1999 | A |
5978364 | Melnik | Nov 1999 | A |
5979493 | Simpkins, Jr. | Nov 1999 | A |
6009762 | Ockleston | Jan 2000 | A |
6021664 | Granato et al. | Feb 2000 | A |
6082925 | Raasch | Jul 2000 | A |
6216543 | Colin | Apr 2001 | B1 |
6317051 | Cohen | Nov 2001 | B1 |
6318395 | Anderson et al. | Nov 2001 | B1 |
6406216 | Raasch | Jun 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6474153 | Yamanaka et al. | Nov 2002 | B1 |
6498968 | Bush | Dec 2002 | B1 |
6558077 | Colson | May 2003 | B1 |
6565284 | Gearhart | May 2003 | B2 |
6618648 | Shirota et al. | Sep 2003 | B1 |
6638424 | Stever et al. | Oct 2003 | B2 |
6696961 | Uhler | Feb 2004 | B2 |
6701261 | Schutzbach | Mar 2004 | B2 |
6757623 | Schutzbach et al. | Jun 2004 | B2 |
6807494 | Schutzbach et al. | Oct 2004 | B2 |
6823729 | Brombach | Nov 2004 | B2 |
6832166 | Schutzbach | Dec 2004 | B2 |
6862498 | Davis et al. | Mar 2005 | B2 |
6914893 | Petite | Jul 2005 | B2 |
20020035497 | Mazereeuw et al. | Mar 2002 | A1 |
20020094799 | Elliott et al. | Jul 2002 | A1 |
20020170350 | Schutzbach | Nov 2002 | A1 |
20030236639 | Curry | Dec 2003 | A1 |
20040239523 | Paoli et al. | Dec 2004 | A1 |
20050005093 | Bartels et al. | Jan 2005 | A1 |
20050071139 | Patwarahan et al. | Mar 2005 | A1 |
20050072465 | Preul | Apr 2005 | A1 |
20050072469 | Preul | Apr 2005 | A1 |
20060164771 | Heidepriem | Jul 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
60682384 | May 2005 | US |