|Publication number||US7768413 B2|
|Application number||US 11/944,329|
|Publication date||Aug 3, 2010|
|Filing date||Nov 21, 2007|
|Priority date||Mar 5, 2002|
|Also published as||US7626508, US20070103324, US20080155064|
|Publication number||11944329, 944329, US 7768413 B2, US 7768413B2, US-B2-7768413, US7768413 B2, US7768413B2|
|Inventors||Roy KOSUGE, Pat CRANE, Alan PITTMAN, John Maris|
|Original Assignee||Aeromesh Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (18), Non-Patent Citations (82), Referenced by (10), Classifications (12), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation of U.S. application Ser. No. 11/426,006 filed Jun. 22, 2006, which is a continuation-in-part of U.S. application Ser. No. 11/303,435 filed Dec. 16, 2005, which is a continuation of U.S. application Ser. No. 10/091,852 filed Mar. 5, 2002, now U.S. Pat. No. 7,002,481, all of which are hereby incorporated by reference as if set forth fully herein.
1) Field of the Invention
The field of the present invention relates generally to monitoring devices and methods and, more particularly, to devices and methods for monitoring water depth and other aspects of sewers, storm drains, waterways, and the like.
Most municipalities have a sanitary wastewater system, the purpose of which is to collect and transport waste matter from the various drains, disposals and other sources within the community to a sewage treatment plant or other such facility. Ideally, the waste matter is transported via the sanitary wastewater system without any spillage or leakage whatsoever. However, sanitary wastewater systems can be enormous in scale, making their management and maintenance extremely challenging tasks. Even in smaller municipalities, managing and maintaining the local sanitary wastewater system can be difficult. Problems often arise from the demands placed upon these systems, which may be found in widely varying states of repair. Such demands generally include severe weather conditions (such as heavy rains or freezing temperatures), accumulation of obstructive materials (e.g., grease, sediment, roots or other debris), and groundwater infiltration, to name a few. In addition, community growth, either industrial or residential, can lead to increased strain on an existing sanitary wastewater system. When the wastewater collection system becomes taxed beyond capacity, manhole overflows and/or backflow into residential areas may result.
The adverse conditions preceding an overflow (or other similar event) often exist over an extended period of time (usually several days or weeks), gradually worsen, and, if not detected and rectified, cause the inevitable result. During the time preceding such an overflow event, wastewater begins to accumulate in one or more localized areas within the collection system, until gradually the level of the wastewater becomes so high it breaches the nearest outlet—usually a manhole opening—or else backs upstream where further problems can be caused.
A sewer overflow can pose significant health hazards within a local community. The cleanup operation can be costly, and an overflow can bring about an interruption in sewer service. Also, a sewer overflow can harm the local environment, and result in potential state and/or federal penalties.
To reduce the likelihood of overflow and backflow events, it has been common practice to place flowmeters at various points within the wastewater collection system, thereby allowing the liquid flow within the system to be monitored. Often the flowmeters are placed at locations where access is convenient, such as in sewer manholes.
A variety of different flowmeters have been developed, a number of which have been used or proposed for use in a wastewater monitoring system. One common class of flowmeters has a “primary” element and a “secondary” element. The primary element is a restriction in a flow line that induces a differential pressure and/or level, and the secondary element measures the differential pressure and/or level, converts the measurements into a flow rate, and records the flow rate data. Weirs and flumes are some of the oldest and most common devices used as flowmeter primary elements. More recently, flowmeters have been developed which use ultrasonic pulses to measure the liquid level, which is then converted into a flow rate.
A variety of drawbacks exist with conventional flowmeter monitoring systems. First, many flowmeter installations are configured to provide manual reading of the flow data that has been acquired over time. Reading the flow meter data can be a burdensome task. Generally, a field worker is required to travel to the physical location of the manhole, pry off the manhole cover, descend into the manhole, and attempt to collect the data from the secondary element of the installed flowmeter. Where numerous flowmeters are installed throughout a large municipal wastewater collection system, the task of collecting flow data from all of the flow meters can be a time-consuming, labor intensive (and therefore expensive) process. In situations of sudden rainfall events or other circumstances, it can be very difficult for field workers to monitor all of the flowmeters in the system, and a risk of overflow increases.
In addition to the difficulty in obtaining flow data from flowmeters installed in a wastewater collection system, flowmeters can also be expensive, and often require a high level of accuracy that can be difficult to maintain over time. Inaccurate liquid flow measurements in the context of a wastewater collection system can lead to serious or even disastrous results. Flowmeters may also require periodic inspection and cleaning, and can therefore be relatively expensive to maintain.
Various types of sewer monitoring systems have been developed or proposed to alleviate the need for manual data collection. One example is illustrated in U.S. Pat. No. 5,608,171 to Hunter et al. However, available sewer monitoring systems of the wireless variety generally require devices that are expensive or require expensive components, can be difficult to install or remove, and/or have limited functionality or compatibility with other equipment.
It would therefore be advantageous to provide an improved technique for monitoring sewers, storm drains, waterways, and other such areas, to prevent overflows, facilitate maintenance, and improve information available for municipal planning purposes.
The invention in one aspect is generally directed to systems and methods for monitoring water depth and other conditions of sewers, storm drains, waterways, and other such areas.
In one aspect, a monitoring device is placed within a manhole or other suitable location for monitoring the buildup of water, sediment or other materials. The monitoring device preferably has a moisture-proof housing made of a non-corrosive, water-resistant material, and includes internal electrical circuitry (microprocessor, memory, etc.) for controlling the functions of the device. A sensor is oriented downward to obtain depth measurements at periodic intervals, and the measurements are stored in the device until readout at a later time. At certain intervals, the stored measurements are transmitted wirelessly to a remote monitoring station for evaluation and analysis.
In a preferred embodiment, the sample rate of the depth sensor and the frequency of reporting to the remote monitoring station are adjustable through commands downloaded wirelessly from the remote monitoring station. The monitoring device may also have internal alert modes which are entered when the monitored water level passes specific threshold values. Entry into a higher alert state may result in an increase in sampling and/or reporting rates.
In one embodiment, the monitoring device has a housing with multiple legs extending outwardly, for allowing the device to be mounted to the interior walls of a manhole. The legs can be made of a flexible, bendable, or compressible material, or else can be adjusted in size by way of a rotatable screw member or a telescoping member. In another embodiment, the monitoring device has a cylindrical housing with a slightly wider cap or head, adapted for, e.g., drop-down insertion into a hole in a manhole cover.
In various embodiments, additional external monitoring instruments may be deployed in the manhole or other location where the monitoring device is situated, and connected to ports in the monitoring device, which transmits data received from the external monitoring instruments to the remote monitoring station. Also, the monitoring device may include a second sensor, oriented upwards instead of downwards, to monitor disturbances to the manhole cover for security purposes.
A monitoring device as described herein may be used in the context of a preferred monitoring system, wherein a plurality of the monitoring devices are positioned within different manholes or other locations over a geographic region, for monitoring water level or other conditions within the various manholes or other locations. In such a system, the remote monitoring station communicates wirelessly with the monitoring devices and receives depth measurements at periodic intervals for processing and analysis. The sampling frequency and reporting frequency of the monitoring devices are preferably programmably adjustable, individually for each of the monitoring devices, through wireless commands transmitted from the remote monitoring station to the various monitoring devices. The wireless communications may be facilitated using a distributed mesh network of wireless nodes which provide for alternative communication paths from the various monitoring devices to the remote monitoring station via one or more bridge nodes, which may be wireless in nature and may utilize a public wireless or cellular network.
Further embodiments, variations and enhancements are also disclosed herein.
As further illustrated in
While only one monitoring device 105 is shown in
In the example of
Operation of the monitoring system 100 shown in
The monitoring device 300 preferably includes a processor 312 (which may comprise, e.g., a microprocessor, microcomputer, or digital circuitry) for controlling the basic functions of the monitoring device 300, including, for example, instructions to transmit data via the wireless communication unit 310, or interpretation of data received via the wireless communication unit 310. The processor 312 preferably includes (or is connected to) a non-volatile memory portion 314 for storing programming instructions for execution by the processor 312 and other data, and a volatile memory portion (e.g., random-access memory or RAM) 315 for storing programmable operation parameters, and for storing depth (e.g., water level) measurements as needed.
The processor 312 may be connected to various clocks and/or timers 317 for carrying out timing of certain events (e.g., timing of intervals between samples or data transmissions), and may be connected to a sensor 325 for measuring depth (e.g., water level). The sensor 325 is preferably capable of taking distance measurements in conditions of very low light as may be experienced when the device is installed in a manhole. The sensor 325 may, for example, be embodied as an ultrasonic sensor which uses the time delay of echoed sound waves to detect the distance from the sensor 325 to the nearest solid object (e.g., water surface). The sensor 325 may also, for example, utilize an electrostatic transducer for ultrasonic detection. Ultrasonic sensors utilizing electrostatic transducers are known in the art and are manufactured, for example, by SensComp, Inc. of Livornia, Mich., and others. An electrostatic transducer may be well suited for detecting soft objects and ranging to targets at both near and far distances. The sensor 325 may have a sensor window 326 affixed to the housing 305 of the monitoring device 300, for providing a viewpath 329 (illustrated as 107 in
The monitoring device 300 preferably draws operating energy from an in-unit, low-voltage battery 322, which supplies energy to the processor 312, sensor 325, wireless communication unit 310, and any other components as necessary. As indicated elsewhere herein, the sensor sampling rate and data transmission rate of the monitoring device 300 are preferably kept to a minimum to prolong the life of the battery 322 as much as possible.
The monitoring device 300 may include one or more input/output (I/O) ports 319, to which can optionally be connected to various peripheral monitoring devices or instruments 320. Examples of peripheral monitoring devices include, for example, external flowmeters, heavy metal detectors, toxic gas detectors, and any other type of useful monitoring device. A peripheral monitoring device may also comprise a so-called “lab-on-a-chip,” in other words, a microchip consisting of, e.g., interconnected fluid reservoirs and pathways that effectively duplicate the function of valves and pumps capable of performing manipulations such as reagent dispensing and mixing, incubation/reaction, sample partition, and analyte detection. The processor 312 may be configured to receive input signals, via the I/O ports 319, from the various peripheral monitoring devices 320, and to process the input signals, store the input signals in volatile memory 315, and/or convey the input signals, via the wireless communication unit 310, to the remote monitoring station. The monitoring device 300 may identify the various peripheral monitoring devices 320 by their particular I/O port number, by an equipment identification number or type number, or by any other suitable means, so that the remote monitoring station can interpret the source of readings or other information received from the monitoring device 300.
When not active, the various components of the monitoring device 300 are preferably rendered inactive by, e.g., placing them in a “sleep” state wherein no or minimal power is consumed. For example, the sensor 325, processor 312, and wireless communication unit 310, and possibly other components, may all be placed in an inactive state when no activity is necessary, and awakened upon the occurrence of an event needing attention (for example, the timeout of a sampling or reporting interval in a timer). At that point, power may be re-connected to the inactive components as necessary. Operation in this manner may significantly preserve battery life.
In operation, the monitoring device 300 takes periodic measurements of depth (e.g., water level) using the sensor 325, and stores the depth measurements in either the non-volatile memory 314 or the volatile memory (e.g., RAM) 315. The non-volatile memory 314 may be comprised of, e.g., flash memory for durably storing data, although the data may be rewritten or erased at a later point in time. Preferably, the sample period of the sensor 325 is programmable or adjustable, so that the sample period can be varied according to circumstances. The stored depth measurements, or a subset of stored depth measurements, can be subsequently read out from the non-volatile memory 314 or volatile memory 315, as the case may be, and transmitted, via the wireless communication unit 310, to the remote monitoring station 170. The monitoring device 300 can also periodically report its battery level to the remote monitoring station 170.
In a preferred embodiment, the time interval(s) between samples taken by the sensor 325 and the time interval(s) between data transmission from the monitoring device 300 to the remote monitoring station 170 are programmed through commands transmitted from the remote monitoring station 170 to the monitoring device 300. The time intervals are preferably stored, along with other operating parameters, in either the non-volatile memory 314 or volatile memory 315 of the monitoring device 300. Re-programming can be initiated in any of a variety of ways. For example, the remote monitoring station 170 may transmit a re-programming command to the monitoring device 300, followed by an identification of parameters to be altered, followed by the new parameter values. The particular format and protocol of the re-programming operation depends upon the communication technique employed. The remote monitoring station 170 may also re-program, through wireless commands transmitted to the monitoring device 170, parameters relating to any peripheral monitoring devices, such as the time interval(s) between transmitting data from the peripheral monitoring devices to the remote monitoring station 170. In one embodiment, the monitoring device 300 is configured to pass through re-programming instructions to a specified peripheral monitoring device that can itself be remotely re-programmed.
The monitoring device 300 may also be configured to automatically adjust the sample rate of water measurements obtained from the sensor 325 without intervention needed by the remote monitoring station 170. In this embodiment, the monitoring device 300 is programmed with a number of different alert levels, each of which corresponds to a specified (optionally programmable) sensor sample rate and/or data transmission rate. As an example, the monitoring device 300 could be configured with a normal operating mode, a low alert operating mode, and a high alert operating mode. The particular operating mode can be dictated by the detected water level. The monitoring device 300 may ordinarily operate in the normal operating mode, wherein it may sample the depth (e.g., water level) at a first rate (e.g., every 60 minutes). If the water level exceeds a low alert threshold, then the monitoring device 300 transitions to a low alert operating mode, and increases sampling frequency to a second rate (e.g., every 20 minutes). When entering the low alert operating mode, the monitoring device 300 may optionally transmit a message to that effect to the remote monitoring station 170. If the water level then rises to an extent that it exceeds a high alert threshold, the monitoring device 300 transitions to a high alert operating mode, and increases sampling frequency to a third rate (e.g., every 10 minutes). When entering the high alert operating mode, the monitoring device may optionally transmit a message to that effect to the remote monitoring station 170.
The low alert threshold and high alert threshold may be pre-programmed, or may be programmed or re-programmed after installation of the monitoring device 300. The low alert and high alert thresholds may be based in part on data collected during the initial period of installation of the monitoring device 300.
The frequency with which data is transmitted from the monitoring device 300 to the remote monitoring station 170 may also be varied depending upon the operating mode. For example, in the normal operating mode, the monitoring device 300 may be programmed or configured to transmit data at a first rate (e.g., once/week) to the remote operating station 170. In the low alert operating mode, the monitoring device 300 may be programmed to transmit data at a second rate (e.g., once/day). In the high alert operating mode, the monitoring device 300 may be programmed to transmit data at a third rate (e.g., once/hour).
The above sampling and broadcast rates are merely exemplary and are not intended to be limiting in any way. The actual sampling and broadcast rates may be selected based upon a number of factors, including the desired level of scrutiny for the particular manhole, the amount of available memory storage space to hold depth (e.g., water level) readings, and the need to preserve battery life to the maximum extent possible. Likewise, the monitoring device 300 may have more or fewer operating modes, depending upon the particular needs of the monitoring system 100.
In addition to automatic transitioning between operating modes, the monitoring device 300 may also be forced to transition between operating modes by commands received from the remote monitoring station 170, or may be programmed with override values for the sensor sampling interval and reporting interval (as well as the low and high alert threshold values). Alternatively, or in addition, the monitoring device 300, including its operating modes, can be programmable via one of the I/O ports 319. A benefit of remote programming of the sample and reporting intervals is that the monitoring device 300 may be manually set to more frequent sampling or reporting rates during certain times such as periods of bad weather (because of, e.g., possible rainwater infiltration) or local construction (which may cause obstructions, breaks, or leakages).
In a preferred embodiment, when reporting to the remote monitoring station 170 in the normal course of operation, the monitoring device 300 transmits a unique device identifier followed by the stored depth (e.g., water level) measurements. The monitoring device 300 may also record timestamp data relating to the depth measurements as the readings are taken, and transmit this information along with the stored depth measurements to the remote monitoring station 170. At the same time, or at other reporting intervals, the monitoring device 300 may also transmit data from any peripheral monitoring devices connected to it. When a water level reading exceeds an alert level (low or high), the monitoring device 300 preferably transmits immediately to the remote monitoring station 170 the device identifier, water measurement reading value, and an alarm code indicating the nature of the alert. At the same time, as noted above, the monitoring device 300 preferably enters an alert mode wherein it takes more frequent water level readings and/or reports to the remote monitoring station 170 more frequently.
The remote monitoring station 170 preferably processes the data received from all of the monitoring devices 105 and centrally manages the overall operation of the monitoring system 100. As previously indicated, the remote monitoring station 170 may transmit new operating parameters (including mode selections) to the various monitoring devices 105. The new operating parameters may, for example, by manually selected or entered by an administrator or operator via the user interface 173 at the remote monitoring station 170. Upon receiving an alert or alarm message from any of the monitoring devices 105, the processing system 172 may signal an operator or administrator by, e.g., activating a display light or audible alarm, and/or sending an electronic message (e.g., by e-mail or pager) or electronic facsimile communication to appropriate personnel. Historical data from the monitoring devices 105 may be stored in the database 174 and analyzed for whatever desired purpose—e.g., hazard evaluation, growth planning, etc. The database 174 may also correlate each device's unique identifier with its location, customer billing information (if applicable), and emergency handling procedure.
When an alert or alarm message is received by the remote monitoring station 170, the processing system 172 or a manual operator may attempt to confirm the existence of a hazardous situation, or evaluate a possible cause thereof, by comparing the water level readings of the monitoring device 105 sending the alert or alarm with the readings received from other monitoring devices 105 along the same pipeline (upstream or downstream). If those monitoring devices 105 are not yet at their typical reporting period, the remote monitoring station 170, automatically or under manual control, can issue commands to the other monitoring devices 105 to send their current water level readings to the remote monitoring station 170 for evaluation.
The remote monitoring station 170 may communicate with the various monitoring devices 105 according to any available and suitable wireless communication technique. Preferably, the wireless communication equipment on the monitoring device 105 and the wireless communication technique are selected so as to provide adequate penetration through the sewer manhole cover 103, to allow proper monitoring of and communication with the installed monitoring device 105. In a particular embodiment, the monitoring device 105 communicates with the remote monitoring station 170 using a suitable two-way pager communication protocol, such as, for example, the Wireless Communications Transport Protocol (WCTP), which offers mechanisms for passing alphanumeric and binary messages. Two-way pager communication may be carried out over the ReFLEX™ network, which provides widespread geographical coverage of the United States, or any other available network. Communicating through a two-way pager network may have the advantage of being less costly than, e.g., communicating over a wireless cellular network.
In alternative embodiments, the monitoring devices 105 may communicate with the remote monitoring station 170 through other types of wireless networks, such as a cellular, PCS, or GSM wireless network, or through any other type of wireless network. Communication may be conducted through base stations 152 (as illustrated in
In some embodiments, messages transmitted wirelessly between the monitoring device 105 and the remote monitoring station 170 are formatted or exchanged according to a standard Internet protocol, such as, for example, the Simple Mail Transport Protocol (SMTP), HyperText Transfer Protocol (HTTP), or Transmission Control Protocol/Internet Protocol (TCP/IP). Scaled-down versions of these protocols may be utilized where certain functionality is not necessary for the purposes of the monitoring system 100.
Various features of a preferred monitoring device relate to means for securing the monitoring device to the interior of a manhole cavity.
To facilitate rapid installation and removal of the monitoring device 105, the monitoring device 105 is preferably suspended in the manhole by multiple legs which emanate from the housing of the monitoring device 105.
The number of legs 482 used to secure the monitoring device 405 to the interior of the manhole may vary depending upon a number of factors. Generally, three or four legs 482 should be sufficient to secure the monitoring device 405. However, even a single leg can be used, if one side of the housing 480 is in contact with the interior surface of the manhole frame 409. In such an embodiment, the contacting side of the device housing 480 may be surfaced with a gripping material such as soft rubber or foam, for example. From a composition standpoint, it may be desirable to manufacture the legs 482 from a non-metallic material, to avoid possible interference with wireless transmission or reception by the monitoring device 405.
Installation of the monitoring device 405 shown in
While no clamps or screws are necessary to secure the monitoring device 405 in the above example, in alternative embodiments, screws, clamps, mounting brackets, or other means for securing the monitoring device 405 may be utilized.
An advantage of various mounting structures and techniques described above is that the monitoring device 405 may be relatively simple and easy to install or remove, even by unskilled workers, and generally does not require the use of tools nor the need to drill into the wall of the manhole. Also, the monitoring device 405 can be installed without necessarily requiring workers to bodily enter the manhole enclosure, which can be advantageous in certain settings. For example, when a worker bodily enters a manhole enclosure, government regulations may impose special requirements, such as additional workers outside the manhole, the use of safety harness, an air supply, and so on, all of which increases cost and time of installation or removal.
In the example shown in
The antenna piece 609 is preferably manufactured of durable, resilient material such as plastic, that nevertheless allows for propagation of wireless signals both upwards, outside of the manhole 608, and downwards towards the monitoring device 605. Any of a variety of conventional wireless repeater antennas may be used or adapted for the antenna array 612 of the antenna piece 609; examples of conventional wireless repeater antennas which propagate signals through glass or other dielectrics are known, for example, in the automotive industry. The monitoring device 605 preferably includes a separate antenna 606 which wirelessly couples to the antenna array 612 within the antenna piece 609, to allow wireless communication between the monitoring device 605 and a wireless base station or network. The antenna piece 609 is preferably flush with the top surface 618 of the manhole cover 603 to prevent it from interfering with surface activity (for example, snow plow blades), but nevertheless should have a clear “horizon” view for optimal wireless reception and transmission. Likewise, the antenna piece 609 is preferably shaped such that it does not protrude from the bottom surface 619 of the manhole cover 603, so that the manhole cover 603 can be easily dragged along the ground without causing harm to the antenna piece 609. The antenna array 612 may constitute, for example, a directional-type antenna, so that loss of energy is minimized.
In certain embodiments, in order to provide as close proximity as possible between coupled antenna elements, the antenna 606 connected to the monitoring device 605 is formed as or contained within a springy wire loop that touches or nearly touches the underside of the antenna piece 609. The flexibility of the antenna 606 in such an embodiment can help prevent damage when the manhole cover 603 is removed (since the manhole cover 603 is heavy, it may be swept across the manhole opening just above the monitoring device 605).
The monitoring device 705 preferably includes, encapsulated within the body 781 and/or cap 782, the various internal components illustrated for the monitoring device 300 in
An advantage of the configuration of the monitoring device 705 in
In one embodiment, illustrated in
The actual shape and dimensions of the monitoring device 705 may vary depending upon a number of factors. For example, it may, in certain situations (especially, e.g., where peripheral monitoring devices are not going to be used), be possible to fit all necessary electronics (including a battery/power supply) and sensor components in a housing roughly the size of the antenna piece 609 shown in
If the second sensor 540 is required to sample periodically, the interval between sample periods is preferably programmable or otherwise selectable. The time between samples may, for example, be programmable via wireless commands received from the remote monitoring station 170. The second sensor 540 might be commanded to sample more frequently prior to or during important events in the local area, such as a parade, etc., where it may be considered important to ensure that manholes are not removed or otherwise tampered with. Likewise, the monitoring device 500 may be programmed to report back more frequently to the remote monitoring station 170 during such events. The failure to receive an expected reporting transmission at the remote monitoring station 170 at a particular time may result in an alarm or alert signal being generating at the remote monitoring station 170, indicating the monitoring device 500 may have malfunctioned or else been tampered with. In the absence of extraordinary events, the sampling period may be selected so as to provide the desired level of security while at the same time maximizing battery life.
In certain embodiments, the remote monitoring station 170 may, pursuant to programmed instructions or manual commands entered via the user interface 173, transmit a status request signal to the monitoring device 500, requesting verification that the manhole cover is in place. Upon receiving such a status request signal, the monitoring device 500 activates the second sensor 540, obtains a reading, and transmits the information back to the remote monitoring station 170. This operation allows greater flexibility in verifying the proper placement of manhole covers without necessarily having to increase the sampling/reporting rates of the second sensor 540 significantly, and can advantageously be used for test and verification purposes as well.
Alternatively, or in addition, a photocell sensor can be used in the monitoring device 500, to detect the presence of light entering the manhole (thereby indicating that the manhole cover has been removed or that a source of light, such as a flashlight or lantern, is nearby).
In any of the various embodiments, a monitoring device may be outfitted with a digital camera or other imaging device, and/or a microphone, for collecting visual images and/or audio data which can be stored or transmitted directly to the remote monitoring station. The visual or audio data may be used to verify an alert condition, allow engineers or field workers to make remote observations, or provide an additional level of security. The digital camera or imaging device, and/or microphone, may be integrated as part of the monitoring device, or else may be an external component connected to one of the monitoring device's input/output ports.
The digital camera or imaging device 1050 may be oriented, for example, downwards to provide observation of the base of the manhole 108 or other location, or upwards to provide observations of the manhole cover 103 or other features. The digital camera or imaging device 1050 may view through a window 1051 (similar to window 1026 through which sensor 1025 views) or else may, for example, be mounted to the exterior of the monitoring device 1000, or view through a fiber optic cable. The digital camera or imaging device 1050 may also share a common window with the sensor 1025. The digital camera or imaging device 1050 may also be used to take an image of a meter within the manhole or other area. The image can then be transmitted back to the remote monitoring station 170, where it may, if a visual meter reading, optionally be processed with optical character recognition (OCR) software to convert the image into a numerical value. A mirror (possibly movable) may be used to allow a single digital camera or imaging device 1050 to view more than one area. The digital camera or imaging device 1050 may comprise, in one example, a CMOS image sensor, or else a CCD image sensor (which may use more power, however, than a CMOS image sensor). The digital camera or imaging device 1050, and/or microphone 1055, may be remotely controlled through the remote monitoring station 170, and/or may be programmed to take periodic snapshots of visual or audio data according to a selectable time schedule. The data may be stored in RAM 1015 or in non-volatile memory 1014 for later readout.
In certain environments, it may be advantageous for the monitoring system to include a local wireless relays in a distributed, self-forming wireless network which may provide, e.g., redundant communication paths for the various monitoring devices. Such a network may be referred to as a mesh network for its ability to form new communication paths and/or redundant communication paths, in a distributed fashion.
The local wireless relay device 1145 is ideally located in relatively close physical proximity to the monitoring device 1105—for example, attached or secured to a nearby telephone/utility pole or streetlamp 1160—to minimize the distance that the RF signals from the monitoring device 1105 need to travel. The local wireless relay device 1145 may have an independent power source (e.g., battery), and/or may advantageously be connected to a power socket of the streetlamp 1160. Using the power socket of the streetlamp 1160 may significantly reduce the maintenance required for the overall monitoring system, and may allow the local wireless relay device 1145 to communicate more frequently without necessarily a concern for premature drain of the battery. If a streetlamp 1160 is not in the vicinity of the monitoring device 1105, the local wireless relay device 1145 may alternatively be connected to another continuous electrical power source that is in the area (including drawing power from utility lines, if placed on a utility pole), or else may rely on battery power.
The wireless communication unit 1107 of the monitoring device 1105 may be embodied as a low power RF wireless device, such as a one-watt radio transceiver, which transmits an RF signal through the manhole 1103 in order to communicate with the local wireless relay device 1145, and likewise receives an RF signal through the manhole 1103 from the local wireless relay device 1145. Similarly, the wireless communication unit of the local wireless relay device 1145 may be embodied as a low power RF wireless device, such as a one-watt radio transceiver. In turn, the local wireless relay device 1145 may rebroadcast the information received from the monitoring device 1105 to other local wireless relay devices and eventually to the remote monitoring station, as will be explained with respect to a more complete system as depicted in
The monitoring devices 1305, or end nodes, each manage one or more data sensors and provides timing, control, data and programming storage, and wireless communication functions to allow remote monitoring of the activity and operation of the monitoring devices 1305 by the remote monitoring station 1370. The monitoring devices 1320 communicate with the local wireless relay devices 1322, or street nodes, according to techniques generally described above with respect to
In certain embodiments, in addition to or instead of using cellular gateway nodes 1324 as the bridge nodes, the mesh network 1320 may include a bridge node 1360 that relies primarily on landlines 1361 for conveying data to the remote monitoring station 1370. The cellular gateway nodes 1324 may allow for increased flexibility in terms of deployment and regions of service, however.
While only a limited number of monitoring devices (i.e., end nodes) 1305, local wireless relay devices (i.e., street nodes) 1322, and bridge nodes 1324, 1360 are depicted in
According to one embodiment, the data carried by radio signals from a monitoring device 1305, or end node, to a local wireless relay device 1322, or street node, can “mesh hop” to reach an available bridge node, such as a cellular gateway node (i.e., sky node) 1324. “Mesh hopping” permits data to find the most efficient path to a cellular gateway node (i.e., sky node) 1324 or other bridge node, and helps prevent data loss by providing redundant paths back to a central server or other computer at the remote monitoring station 1370. This network topology permits large scale installations where each monitoring device (end node) 1305 generally communicates to a single local wireless relay device (street node) 1322, in a one-to-one fashion, but where the street nodes 1322 all communicate with one another and can pass data along to strategically placed bridge nodes, such as cellular gateway nodes 1324 or other bridge node 1360, which operate in a many-to-one mode. The street nodes 1322 (and the bridge nodes 1324, 1360) may inter-communicate using any available communication protocol, but preferably one that is relatively low power, resistant to interference, and compatible with other wireless communication systems as may geographically overlap the mesh network 1320. For example, the street nodes may communicate using a spread spectrum technique.
In the example in
Mesh networking possesses several characteristics that result in an intelligent, self-forming and/or self-healing wireless network. Although in certain cases nodes may server different or overlapping functions, in general the end node in the mesh network 1320 represents a termination point where data is collected—i.e., the monitoring devices 1305 with built-in sensor(s) to collect data. A mesh node is generally a node that passes along data to other mesh nodes, or to a bridge node. A bridge node conveys data to a remote monitoring station, and/or bridges to another type of network. According to one embodiment, the mesh network 1320 self-forms by allowing individual local wireless relay devices (street nodes) 1322 and bridge nodes (such as cellular gateway nodes, or sky nodes 1324, or other bridge nodes 1360) to listen for, and associate themselves, with the strongest signals emitted by the other nodes around them in the mesh network 1320 to determine the ultimate routing paths for delivering the data. Thus, while various wireless communication paths are illustrated in basic example of the mesh network 1320 in
The mesh-like operation may be illustrated by way of example with the layout in
A variety of different communication protocols may be used within the mesh network 1320. Nodes may associate or de-associate themselves with the mesh network 1320 in a variety of different manners as well. According to one example, a node interacts with the mesh network 1320 by sending an association request to associate it with the mesh network 1320, and then transmits data over the mesh network 1320 upon being accepted as part of the network. To initiate communication, a monitoring device 1305, or end node, may first detect the network presence (by listening to communications occurring within the mesh network 1320), and then send out an association request at a certain predetermined time window and/or at a certain time interval. The time interval can be predetermined (e.g., every 5 minutes), or else may be trigged by an event (such as, for example, when a sensor detects motion). The mesh nodes listen for these association requests and, upon detection, send the detected association request along to the node's nearest bridge, such as a cellular gateway node 1324 or other bridge node 1360. The cellular gateway node 1324 or other bridge node 1360 broadcasts signals back through the various mesh nodes of the mesh network 1320 to the end nodes 1305, which creates a routing path for the data to travel upon. Each mesh node 1305 ranks the strength or quality of the routing responses it observes from the various links, or “meshes,” and may select the best or highest quality link as its primary route, the second highest quality link as its secondary route, etc., and thereby forms the routing path. This process is repeated throughout the mesh network 1320, such that if a particular cluster of links are broken, the mesh nodes find other paths to get the data to a live bridge node 1324 or 1360 by, e.g., using their second or third choice routes.
In certain embodiments, the individual nodes of the mesh network 1320 may use a frequency hopping technology that allows the nodes to communicate over different frequencies at different times, thereby potentially minimizing interference from other networks that geographically overlap with the mesh network 1320. For example, the street nodes 1322 and bridge nodes 1324, 1360 may employ a frequency-hopping spread spectrum (FHSS) technique, or else may periodically switch communications to different frequencies in an attempt to reduce interference, particularly if all of the incoming signals are weak or have errors.
The fact that the mesh nodes generally will be regularly be listening for communications from other mesh nodes, or end nodes, can be taxing from a power consumption perspective, and may be a consideration in designing the scalability of mesh.
Although in a preferred embodiment a local wireless relay device 1322 associates with a single monitoring device 1305, in other embodiments a local wireless relay device 1322 may associate with multiple monitoring devices 1305. The local wireless relay device 1322 may accomplish multiple association by, e.g., establishing different time windows for communicating with the different monitoring devices 1305.
The particular architecture of the mesh network 1320 provides it with the ability to utilize or be maintained over a large variety of wired and wireless formats including, for example, 900 Mhz radio, 2.4 Ghz radio, CDMA cellular, GSM/GPRS cellular, Ethernet cable, ISDN cable, serial cable, or others. Using TCP/IP at the bridge/gateway level, the mesh network 1320 may allow ready integration with new wireless formats as technology becomes available; for example, it may be adaptable to WiMax radio, which has recently been publicized but is not yet commercially available. Similarly, reporting to end users from the remote monitoring center 1370 can be made essentially platform agnostic, by relying upon a SQL (Structured Query Language) database which can dynamically push and pull the data into multiple formats (e.g. voice/phone, website, SMS, email, etc.).
The various nodes in the mesh network 1320 may pass along information concerning the frequency, reliability, and other statistical or analytical information concerning node inter-communications to the remote monitoring station 1370, which may maintain, for example, the number of readings received and number of packets forwarded by each node. Reports may be generated for operators at the remote monitoring station 1370 to assess the status of the mesh network 1320. This information may allow the operators to, for example, recommend adding new local wireless relay devices 1322 or bridge nodes 1324, 1360 to the mesh network 1320, or changing the location of certain nodes, or making other adjustments as may be necessary to improve communications within the mesh network 1320. The mesh network 1320 also has the ability, via the remote monitoring center 1370 or otherwise, to remotely update firmware on each of the mesh nodes, to permit for example new software functionality to be introduced remotely and to assist in network management and improvement.
In any of the embodiments described herein, a monitoring device or other device may use multiple (e.g., four) batteries in connection with a switching methodology to extend battery power. The battery control system for the monitoring devices, or end nodes, may periodically rotate the batteries so that only one of the multiple batteries is active at a time (or more if multiple batteries are needed for regular operation) or as each battery drains to below a critical level. To accomplish this, the monitoring device may include circuitry for periodically measuring the remaining battery voltage and for conveying this information to the device processor or controller, and circuitry for switching power supply connections from one battery to another. The effective battery life for the monitoring device becomes the cumulative battery life for each battery (or set of batteries), and the longevity of the monitoring device may thus be significantly increased before battery replacement is required.
In any of the monitoring systems described herein, a particular type of monitoring device may be used exclusively, or else a combination of different monitoring devices may be used. For example, an in-hole monitoring device (such as illustrated, e.g., in
With any of the monitoring devices described herein, a selection of different types of wireless communication may be provided. According to one technique, for example, the specific wireless circuitry is selected at the time of installation. Field workers may test a number of different types of wireless equipment at an installation site, and select the one with optimal reception (e.g., signal strength). The monitoring device may be configured such that a small module (e.g., circuit board, electronic chip, or other type of module) containing the appropriate wireless circuitry may be inserted into the monitoring device prior to installation. Different monitoring devices may therefore utilize different types of wireless communications, and different wireless providers, to communicate with the remote monitoring station. According to an alternative technique, several different types of wireless circuitry are included in the same monitoring device, and a switch provided on the monitoring device is used to select which type of wireless circuitry to utilize.
While various components are described in certain embodiments as being “connected” to one another, it should be understood that such language encompasses any type of communication or transference of data, whether or not the components are actually physically connected to one another, or else whether intervening elements are present. It will be understood that various additional circuit or system components may be added without departing from teachings provided herein.
Implementation of one or more embodiments as disclosed herein may lead to various benefits and advantages. For example, a monitoring system in accordance with certain embodiments as disclosed herein may provide sanitary wastewater system owners and/or operators with an early warning of possible overflow conditions at specifically monitored manhole or other locations, thus allowing the owner/operators sufficient time to prevent actual overflow by cleaning, servicing, shutoff, or other measures. Overflow prevention reduces the risk of costly cleanup operations, health hazards and environmental damage, interruption in service, and penalties from regulatory authorities or agencies. Other potential benefits of various monitoring systems as disclosed herein include reduction of routine preventative pipe cleaning and its associated costs, sewer system historical data for growth planning, and gross rainwater infiltration measurements.
While various systems and devices disclosed herein have most often been described in the particular context of monitoring, it will be understood that the techniques and principles disclosed may be applicable or adapted to other situations wherein it may be necessary or desirable to monitor the level of water, liquid, or any other time of substance that can accumulate over time. For example, monitoring systems as disclosed herein may be applicable to measuring and monitoring any type of water body (such as rivers, lakes, or coastal waters), or any type of liquid in an open pipe setting, or any other type of measurable matter (e.g., sand, ore, silt, mud, etc.) that accumulates.
While preferred embodiments of the invention have been described herein, many variations are possible which remain within the concept and scope of the invention. Such variations would become clear to one of ordinary skill in the art after inspection of the specification and the drawings. The invention therefore is not to be restricted except within the spirit and scope of any appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4119382||Aug 30, 1976||Oct 10, 1978||Agl Corporation||Self-leveling construction alignment laser|
|US4799388||May 19, 1987||Jan 24, 1989||Hunter Robert M||Apparatus and technique for metering liquid flow|
|US4896542||Dec 20, 1988||Jan 30, 1990||Hunter Robert M||Portable wastewater flow meter|
|US5111201||Dec 26, 1989||May 5, 1992||Tokyo Tatsuno Co., Ltd.||System radio transmission of liquid level data and battery saving technique|
|US5199306||Nov 16, 1990||Apr 6, 1993||Hunter Robert M||Method and apparatus for metering flow in closed conduits that surcharge|
|US5330061||Mar 17, 1993||Jul 19, 1994||Zenith Products Corporation||Spinning shower rod mechanism|
|US5406828||Nov 16, 1993||Apr 18, 1995||Yellowstone Environmental Science, Inc.||Method and apparatus for pressure and level transmission and sensing|
|US5423226||Dec 9, 1993||Jun 13, 1995||Yellowstone Environmental Science, Inc.||Flow measurement system|
|US5565783||Aug 2, 1995||Oct 15, 1996||Pacific Gas And Electric Company||Fault sensor device with radio transceiver|
|US5608171 *||Dec 21, 1994||Mar 4, 1997||Hunter; Robert M.||Distributed, unattended wastewater monitoring system|
|US5684250||Aug 21, 1995||Nov 4, 1997||Marsh-Mcbirney, Inc.||Self-calibrating open-channel flowmeter|
|US5811688||Jan 22, 1997||Sep 22, 1998||Marsh-Mcbirney, Inc.||Open channel flowmeter utilizing surface velocity and lookdown level devices|
|US6539794 *||Sep 2, 1999||Apr 1, 2003||Johanngeorg Otto||Arrangement for measuring the level of contents in a container|
|US6585428 *||Feb 12, 2001||Jul 1, 2003||Richard H. Wesselink||Temporary surveillance system|
|US7423985 *||Jun 2, 2005||Sep 9, 2008||Jason Lester Hill||System for large area telemetry data collection networks|
|US20020041238||Aug 1, 2001||Apr 11, 2002||Johnson Roderick Michael||Pager based monitoring|
|USRE35503||Jan 24, 1991||May 13, 1997||Hunter; Robert M.||Apparatus and technique for metering liquid flow|
|USRE36069||Jan 29, 1992||Feb 2, 1999||Hunter; Robert M.||Portable wastewater flow meter|
|1||"ADS Flow Monitoring," http://web.archive.org/web/20020618032830/www.adsenv.com/what-we-do-services.flomon.htm, Jan. 22, 2002.|
|2||"ADS Introduces IntelliScan?" http://web.archive.org/web/20020113194034/www.adsenv.com/what-we-doproducts-IntelliScanrel.htm, Jan. 22, 2002.|
|3||"ADS Model 3600," http://web..archive.org/web/20020917011001/adsenv.com/what-we-do-products-3600.htm, Jan. 22, 2002.|
|4||"ADS Model 4000 Open Channel," http:/web.archive.org/web/20020917010215/adsenv.com/what-we-do-products-4000.htm, Jan. 22, 2002.|
|5||"ADS What We Do, The products, services, and capabilities we offer," http://web.archive.org/web/20020214224239/www.adsenv.com/what-we-do.htm, Jan. 22, 2002.|
|6||"ADS What We Do: Products," http://web.archive.org/web/20011122165419/www.adsenv.com/what-we-do-products.htm, Jan. 22, 2002.|
|7||"ADS What We Do: Services," http://web.archive.org/web/20011226224643/www.adsenv.com/what-we-do-services.htm, Jan. 22, 2002.|
|8||"Colorado Water Utility Saves Personnel, Maintenance Costs with Digital pressure Recorder," Oct. 27, 2000, reprinted from Water & Wastes Digest Magazine, Apr. 2000.|
|9||"CSO/SSO Monitoring," http://web.archive.org/web/20011126192020/www.telog.com/applications/wwd-3.htm, Dec. 2, 2001.|
|10||"Flow Monitoring," http://web.archive.org/web/20001008100634/www.adsenv.com/what-we -do-services-flomon.html, Dec. 19, 2000.|
|11||"Flow Monitors and Communications, Flow Monitoring Systems," webpage link for ADS Corporation, specifically http://www.adsenv.com/default.aspx?id=21, printed on Sep. 12, 2007.|
|12||"HPR-21 Hydrant Pressure Recorder," http://web.archive.org/web/20011218224035/www.telog.com/Applications/hpr-21.htm, Dec. 2, 2001.|
|13||"HPR-21 Specification," http://web.archive.org/web/20020102173628/www.telog.com/hpr-21-specs.htm, Dec. 2, 2001.|
|14||"Liquid Flowmeters," Omega.com Technical Reference, website printout from www.omega.com/techref/flowcontrol.html, reprinted from Plant Engineering Magazine, Nov. 21, 1984, by Cahners Publishing Company.|
|15||"Master Series(TM), Infrastructure Management Software," http://web.archive.org/web/20010106103300/www.adsenv.com/what-we-do-products-mast.html, Dec. 19, 2000.|
|16||"Model 1500," http://web.archive.org/web/20010302080448/www.adsenv.com/what-we-do-products-1500.html, Dec. 19, 2000.|
|17||"Model 1600," http://web.archive.org/web/20010303013913/www.adsenv.com/what-we-do-products-1600-.html, Dec. 19, 2000.|
|18||"Model 3500," http://web.archive.org/web/20010106114800/www.adsenv.com/what-we-do-products-3500.html, Dec. 19, 2000.|
|19||"Model 3600," http://web.archive.org/web/20010106120600/www.adsenv.com/what-we-do-products-3600.html, Dec. 19, 2000.|
|20||"Model 4000," http://web.archive.org/web/200101240757/www.adsenv.com/what-we-do-products-4000.html, Dec. 19, 2000.|
|21||"Model 5600," http://web.archive.org/web/20010106121800/www.adsenv.com/what-we-do-products-5600.html, Dec. 19, 2000.|
|22||"MOSCAD Wireless Monitoring and Control Solutions for the Water/Wastewater Industry," MotoMonitor, Motorola, Inc., 2005.|
|23||"Profile(TM) Software, Profile the Performance of Your Collection System," http://web.archive.org/web/20010420171548/www.adsenv.com/what-we-do-products-prof.html, Dec. 19, 2000.|
|24||"Rain Alert 3600," http://web.archive.org/web/20010106100700/www.adsenv.com/what-we-do-p-rainalrt-3600.html, Dec. 19, 2000.|
|25||"RS-33 Remote Monitoring System," http://web.archive.org/web20070124200102/http://www.telog.com/remote-monitoring.htm, Dec. 2, 2001.|
|26||"SCADA Systems," http://web.archive.org/web/20010106101800/www.adsenv.com/what-we-do-products-SCADA.html, Dec. 19, 2000.|
|27||"System Integration and Design Inc., BOTAS Natural Gas Project," printed from http://www.sys-inc.com/projects/prj-bng.htm, 2001 SYS System Integration and Design Inc., Oct. 5, 2001.|
|28||"Telog Data Acquisition Remote Wireless," http://web.archive.org/web/20011202155956/http://www.telog.com/, Dec. 2, 2001.|
|29||"Telog Gas Products," http://web.archive.org/web/20011031122217/www.telog.com/gas.htm, Dec. 2, 2001.|
|30||"Telog Products," Oct. 27, 2000, http://web.archive.org/web/20000919231955/www.telog.com/products.shtml.|
|31||"Telog R-3308 Teloger Eight-channel Recorder for Remote Data Acquisition," Oct. 27, 2000.|
|32||"Telog R-3314 Teloger 14-channel Recorder for Remote Data Acquisition," Rev. 0898, Oct. 27, 2000.|
|33||"Telog's RS-33 Recording System for Remote Monitoring of Distribution System," Dec. 2, 2001.|
|34||"The Telogers Enterprise System," webpage link for Telog Instruments, Inc., http://www.telog.com/flash/Enterprise-System-applications.htm, dated 2006.|
|35||"Ultrasonic Technology Simplifies Flow and Level Management," Water Engineering & Management, Dec. 1994.|
|36||"Utility Systems Science and Software, About Us," http://www.uscubed.com/usss/about.htm, printed on Sep. 12, 2007.|
|37||"Water & Wastes Digest (WWD), Data Logger/SCADA Integration Saves Time for Field Crews, Permits Early Warning of Problems," Water & Wastes Digest, Feb. 2002, vol. 42 No. 2.|
|38||"Water & Wastes Digest (WWD), Making the Right Choices for Your Wireless SCADA System," Water & Wastes Digest, Feb. 2000.|
|39||"Welcome to ADS Corporation's Homepage," http://web.archive.org/web/20020122183413/http://www.adsenv.com, Jan. 22, 2002.|
|40||"Welcome to ADS's Homepage!" http://web.archive.org/web/20001219092900/http://www.adsenv.com/index.html, Dec. 19, 2000.|
|41||"Welcome to ORE Offshore," http://web.archive.org/web/20010301205753/www.ore.com, Dec. 19, 2000.|
|42||"Welcome to Telog Instruments, Inc. Provider of Remote Data Acquisition Solutions," Oct. 27, 2000, http://web.archive.org/web/20001027104728/http://www.telog.com.|
|43||"What We Do Products," portrait version, http://web.archive.org/web/20010106110500/www.adsenv.com/what-we-do-products.html, Dec. 19, 2000.|
|44||"What We Do, The products, services, and capabilities we offer," http://web.archive.org/web/20001219183100/www.adsenv.com/what-we-do.html, Dec. 19, 2000.|
|45||"What We Do: Products," landscape version, http://web.archive.org/web/20010106110500/www.adsenv.com/what-we-do-products.html, Dec. 19, 2000.|
|46||"What We Do: Services," http://web.archive.org/web/20001212212300/www.adsenv.com/what-we-do-services.html, Dec. 19, 2000.|
|47||"WLS-2109e Technical Specifications," http://web.archive.org/web/20020102190214/www.telog.com/wls-21-specs.htm, Dec. 2, 2001.|
|48||"WLS-2109e Water Level Recorder," http://web.archive.org/web/20011031113133/www.telog.com/applications/wls-21.htm, Dec. 2, 2001.|
|49||"ADS Flow Monitoring," http://web.archive.org/web/20020618032830/www.adsenv.com/what—we—do-services.flomon.htm, Jan. 22, 2002.|
|50||"ADS Introduces IntelliScan?" http://web.archive.org/web/20020113194034/www.adsenv.com/what—we-doproducts—IntelliScanrel.htm, Jan. 22, 2002.|
|51||"ADS Model 3600," http://web..archive.org/web/20020917011001/adsenv.com/what—we—do-products—3600.htm, Jan. 22, 2002.|
|52||"ADS Model 4000 Open Channel," http:/web.archive.org/web/20020917010215/adsenv.com/what—we—do-products—4000.htm, Jan. 22, 2002.|
|53||"ADS What We Do, The products, services, and capabilities we offer," http://web.archive.org/web/20020214224239/www.adsenv.com/what—we—do.htm, Jan. 22, 2002.|
|54||"ADS What We Do: Products," http://web.archive.org/web/20011122165419/www.adsenv.com/what—we—do-products.htm, Jan. 22, 2002.|
|55||"ADS What We Do: Services," http://web.archive.org/web/20011226224643/www.adsenv.com/what—we—do-services.htm, Jan. 22, 2002.|
|56||"CSO/SSO Monitoring," http://web.archive.org/web/20011126192020/www.telog.com/applications/wwd—3.htm, Dec. 2, 2001.|
|57||"Flow Monitoring," http://web.archive.org/web/20001008100634/www.adsenv.com/what—we —do-services-flomon.html, Dec. 19, 2000.|
|58||"HPR-21 Hydrant Pressure Recorder," http://web.archive.org/web/20011218224035/www.telog.com/Applications/hpr—21.htm, Dec. 2, 2001.|
|59||"HPR-21 Specification," http://web.archive.org/web/20020102173628/www.telog.com/hpr—21—specs.htm, Dec. 2, 2001.|
|60||"Master Series™, Infrastructure Management Software," http://web.archive.org/web/20010106103300/www.adsenv.com/what—we—do-products-mast.html, Dec. 19, 2000.|
|61||"Model 1500," http://web.archive.org/web/20010302080448/www.adsenv.com/what—we—do-products—1500.html, Dec. 19, 2000.|
|62||"Model 1600," http://web.archive.org/web/20010303013913/www.adsenv.com/what—we—do-products—1600—.html, Dec. 19, 2000.|
|63||"Model 3500," http://web.archive.org/web/20010106114800/www.adsenv.com/what—we—do-products—3500.html, Dec. 19, 2000.|
|64||"Model 3600," http://web.archive.org/web/20010106120600/www.adsenv.com/what—we—do-products—3600.html, Dec. 19, 2000.|
|65||"Model 4000," http://web.archive.org/web/200101240757/www.adsenv.com/what—we—do-products—4000.html, Dec. 19, 2000.|
|66||"Model 5600," http://web.archive.org/web/20010106121800/www.adsenv.com/what—we—do-products—5600.html, Dec. 19, 2000.|
|67||"Profile™ Software, Profile the Performance of Your Collection System," http://web.archive.org/web/20010420171548/www.adsenv.com/what—we—do-products-prof.html, Dec. 19, 2000.|
|68||"Rain Alert 3600," http://web.archive.org/web/20010106100700/www.adsenv.com/what—we—do-p-rainalrt—3600.html, Dec. 19, 2000.|
|69||"RS-33 Remote Monitoring System," http://web.archive.org/web20070124200102/http://www.telog.com/remote—monitoring.htm, Dec. 2, 2001.|
|70||"SCADA Systems," http://web.archive.org/web/20010106101800/www.adsenv.com/what—we—do-products-SCADA.html, Dec. 19, 2000.|
|71||"System Integration and Design Inc., BOTAS Natural Gas Project," printed from http://www.sys-inc.com/projects/prj—bng.htm, 2001 SYS System Integration and Design Inc., Oct. 5, 2001.|
|72||"The Telogers Enterprise System," webpage link for Telog Instruments, Inc., http://www.telog.com/flash/Enterprise—System—applications.htm, dated 2006.|
|73||"What We Do Products," portrait version, http://web.archive.org/web/20010106110500/www.adsenv.com/what—we—do-products.html, Dec. 19, 2000.|
|74||"What We Do, The products, services, and capabilities we offer," http://web.archive.org/web/20001219183100/www.adsenv.com/what—we—do.html, Dec. 19, 2000.|
|75||"What We Do: Products," landscape version, http://web.archive.org/web/20010106110500/www.adsenv.com/what—we—do-products.html, Dec. 19, 2000.|
|76||"What We Do: Services," http://web.archive.org/web/20001212212300/www.adsenv.com/what—we—do-services.html, Dec. 19, 2000.|
|77||"WLS-2109e Technical Specifications," http://web.archive.org/web/20020102190214/www.telog.com/wls—21—specs.htm, Dec. 2, 2001.|
|78||"WLS-2109e Water Level Recorder," http://web.archive.org/web/20011031113133/www.telog.com/applications/wls—21.htm, Dec. 2, 2001.|
|79||Internet archive summary page for adsenv.com, http:/web.archive.org/web/*/http://www.adsenv.com, printed Jan. 24, 2007.|
|80||Internet archive summary page for telog.com, http:/web.archive.org/web/*/http://www.telog.com, printed Jan. 24, 2007.|
|81||Johnson, Dick, "Differential Flowmeters: Simple Can Be Better," Control Engineering Online, website printout from www.controleng.com (Sep. 2000), pp. 1-3.|
|82||Product Family Overview, Stevens Water Monitoring System, website printout from www.stevenswater.com (Nov. 9, 2001).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8594851 *||Dec 18, 2007||Nov 26, 2013||Data Flow Systems, Inc.||Wastewater collection flow management system and techniques|
|US8946548 *||Mar 17, 2011||Feb 3, 2015||Dean Sanders||Nautilus self pressurizing equipment enclosure system, apparatus and methods|
|US8983667||Oct 25, 2013||Mar 17, 2015||Data Flow Systems, Inc.||Fluid flow management through a wastewater level manipulation system and associated methods|
|US9014998 *||Oct 9, 2009||Apr 21, 2015||Vega Grieshaber Kg||Sensor with subassemblies featuring storage devices|
|US9091753||Jan 31, 2013||Jul 28, 2015||Krohne Messtechnik Gmbh||Level measuring system operating according to the radar principle|
|US9371727 *||Dec 8, 2011||Jun 21, 2016||Expro North Sea Limited||Well monitoring|
|US20100256942 *||Oct 9, 2009||Oct 7, 2010||Martin Gaiser||Sensor with subassemblies featuring storage devices|
|US20110164373 *||Mar 17, 2011||Jul 7, 2011||Dean Sanders||Nautilus Self Pressurizing Equipment Enclosure System, Apparatus and Methods|
|US20140002088 *||Dec 8, 2011||Jan 2, 2014||Expro North Sea Limited||Well monitoring|
|US20140354426 *||May 30, 2013||Dec 4, 2014||Andrey LUYBYANITSKY||Device for container leakage detection and method for the same|
|Cooperative Classification||G08B21/10, G01F15/063, G08B21/20, G01F23/296, E03F7/00|
|European Classification||G01F23/296, G01F15/06B2, E03F7/00, G08B21/10, G08B21/20|
|Mar 14, 2014||REMI||Maintenance fee reminder mailed|
|Aug 3, 2014||LAPS||Lapse for failure to pay maintenance fees|
|Sep 23, 2014||FP||Expired due to failure to pay maintenance fee|
Effective date: 20140803