AU2007214283B2 - Sewer flow monitoring method and system - Google Patents

Description

AUSTRALIA Patents Act 1990 COMPLETE SPECIFICATION (Divisional of Australian Patent Application No. 2002305036) Standard Patent Applicant(s): ADS LLC Invention Title: SEWER FLOW MONITORING METHOD AND SYSTEM The following statement is a full description of this invention, including the best method for performing it known to me/us: SEWER FLOW MONITORING METHOD AND SYSTEM BACKGROUND OF THE INVENTION s This patent application is a divisional application of Australian patent application number 2002305036 and relates to subject matter disclosed in that application. Some description of the invention of 2002305036 is included herein to facilitate understanding of the present invention. If necessary, reference may be made to the disclosure of application 2002305036 to understand the present invention, and the whole of the disclosure of that 10 application is incorporated herein by reference. Cross-Reference to Related Applications This application claims priority under 35 U. S. C. 119 (e) to U. S. Provisional Application Serial No. 60/274,839, entitled "Sewer Flow Monitoring Method and System", is filed March 9, 2001, the contents of which are incorporated herein by reference. Field of the Invention The present invention relates generally to sewage flow monitoring systems. More particularly, the present invention relates to a method and system of monitoring the flow 20 of a fluid substance to detect flow loss based on a predicted flow volume. Description of the Related Art Fluid flows in pipes and open channels are common in numerous industrial, commercial, municipal, and residential systems. Proper and efficient operation of these systems, 25 and meaningful planning for future expansion and maintenance of such systems, depends upon accurate measurement of the flow that passes through such systems. Sewer systems, such as municipal sanitary sewer systems, are an example of one system in which accurate flow measurement is critical. 30 Many sewer flow measuring devices operate by detecting both the depth of flow in a channel or pipe and the velocity of the flow in the same location of channel of pipe. The data is collected at periodic sampling times and is used to calculate a flow rate. Examples of such flow measurement devices are disclosed in U. S. Patent No. 4,397,191, to Forden ; U. S. Patent No. 4,630,474, to Petroff ; and U. S. Patent No. 5,198,989, to Petroff N \Mclbourne\Cases\Patent\50000-50999\P50872 AU I\Specis\P50872.AU I Spcification 2007.8-27 doc 28/08/07 2 each of which is incorporated herein by reference in its entirety. In the wastewater industry, real-time detection of problem events and accurate prediction of future system operation have become increasingly important. Real-time detection of system problems, such as leaks or system breaks, sanitary sewer overflows, and system blockages, allows system managers 5 to quickly respond to such problems. With a rapid response, system managers can prevent or minimize unwanted incidents such as basement back-ups or sewage in waterways that may result from system overflows or breaks. For example, with early detection of a system blockage, managers could respond to and clear the blockage or repair the pipe before it causes an overflow or a buildup of pressure within the system resulting in a break or leak. 10 Further, if an overflow occurs, such as may happen during a storm event, system managers can take action to redirect the flow to other channels within the system in order to reduce or eliminate the overflow condition. Further, a system with predictive capabilities could allow managers to stop 15 overflows before they occur, to more effectively use existing system features, and identify and plan for required system expansions. Conventional monitoring systems have exhibited several problems. The conventional systems are limited to reporting of data and basic alarming. Such systems do 20 not reliably validate, in real time, monitored data. Further, alarm conditions are typically triggered based on predetermined levels, and the monitoring systems are susceptible to false alarms during storm conditions, holidays, and other unusual events that are not necessarily reflective of a sewer system problem. Further, the conventional monitoring systems lack reliable predictive capabilities for predicting flow at vanous points in a sewer system. 25 3 Accordingly, it is desirable to provide an improved method and system for monitoring flow in a sewer system. SUMMARY OF THE INVENTION 5 In accordance with one embodiment of the present invention, there is provided a method of monitoring and analyzing flow in a sewer system, comprising the steps of: collecting, using a monitoring assembly, data representative of actual flow volume, flow velocity and depth in a first location and a detection time thereof; 10 validating the data representative of actual flow volume, flow velocity and depth; storing the data representative of actual flow volume, flow velocity and depth in a memory; maintaining, in the memory, previously stored data representative of previous flow volumes; 15 determining a predicted flow volume, wherein the predicted flow volume is dependent upon data stored in the memory and the detection time associated with said data, wherein the detection time corresponds to both the data selected from the previously stored data and the data representative of actual flow volume, flow velocity and depth; comparing the actual flow volume with the predicted flow volume to yield a 20 difference value; computing a current threshold value on the basis of the predicted flow volume and the actual flow volume and periodically updating the current threshold value based on a predetermined number of readings, and issuing an alarm when the actual flow volume is less than the periodically updated 25 threshold value. In situations where the difference value exceeds a predetermined variance value, the method may further include the step of issuing a flow loss notification. If the difference value does not exceed a predetermined variance value, the method may also include 30 storing the actual flow volume in the memory as stored calibration data. As additional options, the method may include the additional step of transmitting the flow velocity data, depth data, and/or the actual flow volume over a data network such as the Internet to a computing device. Also optionally, the actual flow volume may be a rolling average flow volume. 35 As additional options, at least one of the determining step and the comparing step may be performed by the monitoring assembly. In the alternative, the determining step and/or the comparing step may be performed by the computing device. As a further option, the 4 2390801_1 (GHMatters) 31/0/10 method may include the additional step of validating the data representative of flow velocity and depth, in such a case, the validating step may optionally be performed by the monitoring assembly. In addition, the data representative of actual flow volume may include at least one of flow velocity data and depth data, and the method may include calculating the flow volume 5 based upon such data. In accordance with an additional embodiment of the present invention, there is provided a flow monitoring system, comprising: a first monitoring assembly having at least one sensor, wherein the at least one sensor 10 is operative to detect data representative of actual flow volume, flow velocity and depth of a fluid substance at a first location, the data comprising at least one of flow velocity data and depth data; a processor in communication with the first monitoring assembly; a memory, wherein the memory is operative to store the data representative of actual 15 flow volume, flow velocity, depth, and a detection time associated with said data; and a central computing device in communication with the first monitoring assembly, wherein the processor is trained to validate the data representative of actual flow volume, flow velocity and depth, calculate an actual flow volume corresponding to the at least one of flow velocity data and depth data and compare the actual flow volume with a predicted 20 flow volume to yield a difference value, the predicted flow volume being dependent upon the data stored in the memory and the detection time associated with said data, and wherein the means for processing is trained to issue a notification if the difference value exceeds a predetermined variance amount. 25 As an additional option, the processor may be integral with the first monitoring assembly. As an alternative option, the processor may be integral with the central computing device. Also in accordance with this embodiment, a first monitoring assembly may 30 optionally be capable of validating the flow velocity in depth. As an additional option, the system may include a second monitoring assembly that has a means for detecting the quantity of rain at a location during a period of time, such as a rain gauge, a weather service, or even a weather web site. Further, the central computing device may be trained to predict an anticipated flow velocity, depth, and/or flow volume of the fluid substance at a second location. 35 In accordance with yet another embodiment of the present invention, there is provided an apparatus for monitoring and analyzing flow of a fluid substance in a sewer system, 5 2390801_1 (GHMattrs) 31s08110 the apparatus comprising: a first means for monitoring fluid flow having at least one means for sensing, wherein the at least one means for sensing is operative to detect data representative of actual flow volume, flow velocity and depth comprising at least one of flow velocity data and depth data at s a first location; a means for processing in communication with the first means for monitoring; a means for storing data, wherein the means for storing data is operative to store the data representative of actual flow volume, flow velocity and depth and a detection time associated with said data; and 10 a means for computing in communication with the first means for monitoring, wherein the means for processing is trained to validate the data representative of actual flow volume, flow velocity and depth, calculate an actual flow volume corresponding to the at least one of flow velocity data and depth data, is compare the actual flow volume with a predicted flow volume to yield a difference value, compute a current threshold value on the basis of the predicted flow volume and the actual flow volume and to periodically update the current threshold value, and wherein a means for alarming is configured to issue an alarm when the actual flow volume is less than the current 20 threshold value, the predicted flow volume being dependent upon the data stored in the means for storing data and the detection time associated with said data, and issue a notification if the difference value exceeds a predetermined variance amount. BRIEF DESCRIPTION OF THE DRAWINGS 25 FIG. 1 is a flow chart illustrating the steps that may be followed in an embodiment of the present invention as a method. 6 2390801_1 (GHMatters) 31108/10 FIG. 2 illustrates an example of the operation of the flow loss detection feature of the present invention. FIG. 3 further illustrates the flow loss detection feature. 5 FIG. 4 further illustrates the flow loss detection feature. FIG. 5 illustrates examples of certain hardware aspects of the present system. 10 FIG. 6 is an exemplary scatterplot hydrograph in a normal pipe. FIG. 7 is an exemplary scatterplot hydrograph in a blocked system. FIG. 8 is an exemplary scatterplot hydrograph in a system experiencing 15 sanitary sewer overflow. FIG. 9 is a block diagram that illustrates data validation features of the present invention. 20 FIG. 10 is a block diagram that illustrates alann event detection features of the present invention. DETAILED DESCRIPTION OF THE INVENTION The present invention provides a novel sewer flow monitoring method and 25 system. A flow chart 100 of the present invention in a method embodiment, and the 7 potential steps to be implemented by a system embodiment, are illustrated in FIG. 1. Referring to FIG. 1, the method includes the step of using a monitoring assembly to collect 12 data representative of flow velocity in depth of the fluid substance in a first sewer location. This data may be collected by velocity and depth sensors that are integral with the 5 monitoring assembly, such as those described in col. 2 of U.S. Patent No. 4,397,191, to Forden (including the drawings referenced therein), and col. 2 of U.S. Patent No. 5,821,427, to Byrd (including the drawings referenced therein), each of which is incorporated herein by reference. 1 0 The method also includes determining a flow volume 16 corresponding to the flow velocity and depth detected. The flow volume may be determined by any appropriate method, such as simply by multiplying the flow velocity and the depth to result in a volume, or by using methods that consider additional variables such as temperature as described for example in U.S. Patent No. 5,198,989, to Petroff, which is incorporated herein by reference 15 in its entirety. The steps of detecting a flow velocity and depth and determining a flow volume are preferably performed in the monitoring assembly itself. In such an embodiment, the monitoring assembly would include a processor and a memory, and the processor would 20 he trained, such as through computer program instructions or digital logic, to perform the calculation of flow velocity. Optionally, the flow velocity and depth data may be transferred to a remote or central computing device over a communications network such as the Internet, 8 and the determination of flow velocity may be performed by the remote or central computing device. The processes of detecting flow velocity and depth and calculating flow volume are periodically repeated, such as may occur during one-minute intervals, fifteen-minute intervals, or any regular or irregular interval that is desired. The flow velocity data, depth 5 data, and flow volume data are stored in a memory 18. In the embodiment where the flow volume is determined at the monitor level, the memory 18 is preferably integral with the monitor. In the embodiment where the flow volume is determined at the computer, the memory 18 is preferably integral with the computer. The memory 18 maintains stored data 20 over a period of time, although optionally data may be discarded after it achieves a 10 predetermined age, such as a week, a month, a year, or (such as many be desirable for data relating to unique days such as holidays) several years. As an additional option, in step 12 only one of flow velocity and depth data may be obtained. For example, flow volume could be calculated as a function of either 15 depth or velocity, without need for collecting the other data item. Further, in an optional embodiment, step 12 may be completely eliminated and the system may directly collect flow volume data, such as when data from a pump station or other area is available. Optionally, the method may include validating 14 the flow volume and/or 20 depth data before determining the flow volume, or it may include validating 14 the flow volume data after it is determined or calculated. In a preferred embodiment, using depth data for purposes of discussion, the validation is performed by comparing the detected depth 9 with previously-collected depth data stored in the memory. The validation step considers the time that the data is collected, and preferably the day that the data is collected, and compares it to data previously collected for similar days and times. For example, the system may collect depth data at 8:00 a.m. on a weekday, and the validation step will include 5 comparing that data to depth data collected at or near 8:00 a.m. on previous weekdays. Similarly, weekend days may correspond, and the system may also optionally be programmed to recognize, holidays (which typically have unique flow trends) and/or individual days within the week, such as Mondays, Tuesdays, etc. 10 _ The comparison may be done to the most recent relevant previously-collected data, or it may be to a set of previous data. Preferably, the previously-collected data is limited to that collected recently, such as during the past ten related days and times, so that trends are followed and gradual changes do not result in false determinations of invalidity. Optionally, the previously-collected data may be averaged, or a mean may be calculated for 15 comparison purposes. Optionally, the average may be a weighted average, such that the most recent data is given the most weight, while older data is given less weight. If the current depth data differs from the previous data by more than a predetennined variance level, then the system assumes that the data is invalid, and the monitor is re-fired to collect another set of data. The predetermined variance level may be any amount, such as a 20 percentage or a set number, and is preferably set to be large enough to avoid false invalidity determinations and small enough to capture most invalid readings. After re-firing, the system may perform the validation step again. Optionally, if a predetennined number of re 10 firings yield similar results, the system will presume that the data is valid. Preferably, the validation step is performed at the monitor level, but optionally and alternatively the validation may be performed by the remote or central 5 computer. Returning to FIG. 1, the system includes the feature of detecting flow loss by comparing the actual, detected flow volume with a predicted flow volume. First, the system determines a predicted flow volume 22 based on the data representative of flow velocity and 10 depth in that is previously stored in the memory. As with the validation feature described above, the predicted flow volume is determined based on the day and time of the current reading and comparing 24 it with readings taken at previous, related days and times. If the current reading falls below a predetermined threshold 26, such as 75% of the expected reading, an alarm may be issued 28. 15 An illustration 200 of such a comparison is shown in FIG. 2, where the calculated velocity 205 is identified as Qc and the predetermined threshold 210, such as 75% of the predicted flow loss, is identified as QM[N. Qc and QMIN typically vary over different days and times, as sewage flow on weekdays typically differs f&om that on weekends, and 20 flows during different times of day also vary. For example, flows at 3:00 a.m. on a weekday are typically much lower than flows at 8:00 a.m. on a weekday. Trends associated with holidays or individual days may also be considered. As illustrated in FIG. 2, if the flow 205 l l drops below the predetermined threshold 210, an alarm is triggered 215. The alarm, as well as any or all of the data, may be transmitted to a remote or central computer over a communications network, as illustrated by step 30 in FIG. 1. 5 FIG. 3 illustrates that the method may include compensation for wet weather. For example, FIG. 3 illustrates that when the system detects a gradual increase in flow volume or a gradual decrease in flow volume, the system may presume that the increase or decrease results from a storm event. In such a situation, a quick loss is identified 305 as an actual flow loss, while a gradual decrease is identified as an end of a storm event. 10 Optionally, the system may use actual data collected from one or more rain gauges, or even data obtained from a weather service or weather web site, to determine when a storm event is occurring. FIG. 4 illustrates that the predetermined threshold 210 is preferably set at a 15 level that is not too close to the actual readings in order to avoid false alarms. For example, starts and stops of purnp stations in a sewer system can cause spikes and/or erratic flows 405. Thus to avoid a change and pump status causing a false alarm, the predetermined threshold 210 may be anywhere from 5% to 50% below the predicted value, or more or less as may be appropriate for the system. [n addition, to avoid "spikes" 405, the actual flow volume 20 205 may be calculated on a "moving boxcar" or rolling average basis, such as by using the average of the previous two, ten, or any predetermined number of readings. 12 FIG. 5 illustrates an example of several elements of the system embodiment 500 of the present invention. Referring to FIG. 5, a network of flow monitors 505 detects depth and velocity at various locations in a sewer system. The monitors 505 communicate with a central or remote server 510 over a data network such as a local area network, wide 5 area network, or the Internet. Optionally, the central server 510 may also communicate with one or more user workstations 515 over a data network such as a local area network, wide area network, or the Internet. The system 500 may also be used to monitor or predict potential problems with a sewer system. 10 During the last century, several hydraulic engineers developed equations, known as pipe curve equations or hydraulic element curves, to describe the relationship between the depth of open channel gravity flow to the velocity of that flow. For a given depth of flow there is a unique and predictable velocity (and flow rate). Figure 6 shows an exemplary scattergraph 600 from a normal open channel flow sewer. The plot of paired 15 depth and velocity readings from an open channel flow meter should form a pattern similar to this pipe curve 600. Patterns that deviate from the expected pipe curve 600 indicate that either the hydraulics of the pipe are changing or the meter is malfunctioning. It is a rare sewer system that produces an ideal scattergraph 600. Bottlenecks 20 can be caused by undemiized pipes, broken pipes, roots and severe turns in manholes. Figure 7 illustrates the classic "ski jump" shape 700 which is the distinguishing characteristic of a sewer with a downstream bottleneck. The hydraulic grade line 700 in this example will 13 become flat during the surcharge period and the backwater condition can be detected several manholes upstream of the bottleneck. Sanitary sewer overflows (SSOs) are also a problem in many sewer systems. 5 They are difficult to witness or document because they usually occur during rain events when people are indoors. Also, they frequently are located out of sight at the lowest manholes or structures along creeks and ravines. Toilet paper in the branches along the creek may be the only evidence that some SSOs leave behind. The first reaction to SSO's from casual observers and some collection system managers may be that they "need a bigger 10 pipe." However, in whole or in part, many SSOs are caused by a downstream bottleneck. Thus, in such cases, bigger pipes may not be needed, and simple elimination of the bottleneck may solve the problem. SSOs and bottlenecks each will leave telltale evidence in the data of nearby flow meters. Figure 8 is an exemplary scattergraph 800 produced by flow monitor data collected during an upstream SSO event. 15 Referring to FIG. 9, a block diagram 900 illustrates how the present inventive method 100 and system 500 can use scatterplots to validate data and identify bottlenecks and SSOs. An optional "scatterplot feature" 905 compares valid depth and velocity data points to an expected hydraulic signature curve. If these data points do not fall within the expected 20 hydraulic signature curve limits, the sensors are re-fired to collect new data at block 910 to test the validity of the data and verify whether a sensor may have malfunctioned. If depth and velocity data points are repeatable, it is assumed that the data is valid and it is stored. 14 If they are not repeatable, they are flagged as "bad" data. If the verified data points fall outside of expected curve limits, the alarm notification module 915 initiates an event call out. An optional "hydrograph function" 920 compares valid depth data with previously collected data, such as a "learned 24 hour" diurnal curve. The result of that comparison 5 typically indicates a quantity above or below the expected diurnal curve at a specific time of day. Any quantity plots above or below the expected diurnal curve may result in an alarm event at block 915. FIG. 10 is a block diagram 1000 that illustrates exemplary embodiments of 10 features of event management in the present inventive method 100 and system 500. Upon receiving an event notification 1003 from a flow monitor 505, the system 500 may plot the event depth and velocity points against an expected hydraulic signature curve at block 1005. The expected hydraulic signature curve is generated using a 24 hour data collection, followed by analysis and normalization of the data at block 1008. If the event depth and 15 velocity points fall inside a normal plot standard deviation, the system 500 considers the point to be valid. The system 500 may also plot the event depth points against an average weekday or weekend or holiday hydrograph at block 1010. Data is then saved in an event management store at block 1015. If an event depth point falls above or below the predetermined average daily hydrograph limits, the system 500 considers the event depth 20 point to be invalid and may trigger an alarm and/or recollect the data at 1020. Optionally, if a predetermined number of alarms occurs in a set period (such as three alarms in an eight hour shift), a high priority alarm may be triggered at 1020 in order to prompt a user of 15 system manager to investigate the problem. The system 500 includes several functions that a user may optionally see on a user display. For example, a log-on/log-off button may be provided to allow the user to 5 log on and off the system. A system overview button may allow the user to select a graphic view of the system that provides an overview of a geographic area, such as a county or river basin. The user may be provided with a select topic button that allow the user to select an area, such as a county or basin, or an individual site. Alarm summaries and communications summaries may also be made available to the user. Optionally, a weather button may allow 10 the user to view weather data, such as that collected by rain gauges or even as obtained from a weather service or weather web site. A site detail screen may allow the user to see-real time monitor data as well as scatterplots and time-lapse data. Such data may include, for example, flow volume, velocity, and depth, temperature, p-1, or even content such as dissolved oxygen. Further examples of such screens and plots are described in the materials 15 appended hereto, and made a part hereof, as Appendix A. It is to be understood that the invention is not limited in its application to the details of construction and to the arrangements of the components set forth herein the following or illustrated in the drawings. The invention is capable of other embodiments and 20 of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein, as well as the abstract included below, are for the purpose of description and should not be regarded as limiting. 16 APPENDIX A Network Plan Schematic I-SCAN Workstation #1 I-SCAN Workstation #2 Municipal Wastewater existing offce LAN ADS Flow Monitoring Network Flow * f~rMonitorTMonitor 17 1.0 Display/ Report Plan The ADS Intelliscan FMAS, utilizes an object oriented, Graphical User Interface (GUI) based on Wonderware Intouch and the Microsoft NT 4.0@ standard. This allows Intelliscan to scan and log remote flow sites, and gives the user the ability to visualize and analyze flow data graphically. The Intelliscan GUI Is comprised of several components that provide visualization, historical trending, event handling, alarm logging, reporting and analysis tools. These features combine to create a complex and powerful operator Interface, providing a point and click environment for ease of use. The following screen displays explain functionality associated with each particular screen in greater detail. 1.1 Navigation Template SOW Q Y"Il ry. Five. le Ame - L EGEND) RAIN GAUCE BASIN BOUNDARY COUNTY BOUNQAR INTERSTATE Navigation Template- located on left hand side of each screen * Log On /Log Off button allows the user to Log On and Log Off of the Intelliscan system - System Overview button selects a county overview screen - Select Topic button brings up a Select Topic window for Basin or Site selection * Alarm Summary button brings up the Alarm Summary screen * Comm Summary button brings up a Communications Summary screen * Weather button brings up an internet browser with weather web site connectivity. 18 2.2 County Map Overview Screen Iach-windowViewer- D:\NTELUISCAN\0EV' O CN.8. nP A|."' 15 a Fve le 1 urm L EGE ND RAIN GAUGE

WWTP

F-- BASIN BOUNDARY F--COUNTY BOUNDAR IN IERS rATE County Map Overview " This is the screen that is displayed upon initially logging into the intelliscan system " Provides an overview of all Basins in county " Basins with Green outline indicate all sites within that Basin are within normal operating ranges " Basins with flashing Red outlines indicate a site within in that Basin has an unacknowledged alarm " Basins with solid Red outlines indicate that a site within that Basin has an acknowledged alarm " Clicking on a particular Basin will bring up a Basin Overview screen 19 2.3 Basin Overview Screen vIITcc Widv Uiwr D NTL ISAIE FIE ADS u lia T Basin - Fivemile I Se etTopkv lelf AI C 4 U A~ previgos indo -ydro Plots oport Arche Slt6 D-cunients ut41ok Basin Overview " Provides a map showing each Flow Site and its status within a Basin. The operator can click on any of these active sites and drill down to the specific site detail screen. " Sites in an unacknowledged alarm condition will flash Red e Sites in an acknowledged alarm condition will show in solid Red e HydroPlots button launches HydroPlot Screen for ad hoc plotting * Reports button launches the Report menu with options to select specific reports for view, edit or creation. " Archive button launches a menu of databases for selection, view and editing. " Documents button launches a document menu for document selection, view and edit. e Outlook button launches Microsoft Outlook for E-Mail and other office functions. 20 2.4 Site Details a a -- &w te etalis 6 t 0aView peph Po St ar 24hu ie yro -3 12' 11. ' 115-ea 9 3 2 G E 3 ,!: 2 1 6 8 BM ' U p mDO Seide p Tpfs a Dsl O oxgpn 6p Selection of a site icon while in the Basin Overview screen displays the specific Site Detail Screeno * The Site Detail screen provides real time information about a specific site as well as a 24 hour site HydroPlot " Flow/Depth l e2sliders and integers provide site data from the most recent polling activity. * pHlTemp/DO Sliders and Integers provide pH, Temp and Dissolved Oxygen Information from the site ii implemented. Note: These Environmenfal Sliders will remained hidden unless the site selected is instrumented for these readings * Poll Site button launches a demand polling of the site. Upon Initiation of a demand poll, a telemetry icon will travel across the top of the screen indicating telemetry system activity at that site. The Flow, Depth and Velocity values are returned from the monitor and displayed on the sliders and integers graphics. * A graphical image of a sewer line with flow Instrumentation is shown on the screen. This Image provides current site depth visualization, alairm condition and contains a Hydroplot showIng the last 24 hours of site information. 21 2.5 Site Data Review FloW Site OetalI - ~ hr t Bro ae& Kot -- -B ; - EUt r t -Caution Possible silt bUild-Up - ydr' - - - - e eClicking on the Manhole Cover while In the Site Detail screen displays Site Data Review. Site Data Review screen provides the user with a thumbnail sketch of the flow performance and changing hydraulic conditions at each site. It also helps the user to assess flow monitor instrument health condition by displaying good points, flagged bad points and flow monitor battery health. .A Site Data Review window will be displayed With two scatter plots and one hydroplot. -Scatter plot #1 will display the relationship of site depth verses velocity. Thissite flow performance indicator is for the last 24 hours. This plot will contain good data points in green and flagged bad data points in red with a "Lease Squares Cur/e Fit" line. -Scatter plot #2 will display three "Lease Squares Curves" without the data points. Scatter plot #2 will display changing site hydraulic conditions comparing 24 hours ago with 48 hours ago and the month's average. -The Hydroplot display will show a graph of sewer depth for seven days. These plots can be used to analyze site hydraulics and performance. SSite pipe specifications will also be displayed in a Site Data Review wlndow for dimensional and correction factor references plus battery voltage. 22 2.6 Bypass Site Detail Screen 5.l gt110114 Sj _4S te D s - k -. & 20 471 OI 15 ndo * ydolts- ft/ cnhr te ~ oc 17 1 * While in the Basin Overview screen, selection of a Bypass Site will bring up the Bypass Site Detail Screen. - 3 graphics will be displayed: -The first graphic will display sliders and integers reflecting the real time condition within the Bypass Vault. These include flow rate, depth and velocity -The second graphic displays current rain activity as defined by any atAUCShed associated Rain Gauge -The third graphic displays the Bypass Outflow Rate and current River Depth if a stream gauge is atAUCShed - A graphical display of the Bypass Site providing sewer main depth in relation to the Weir Wall and flow monitor instrumentation are also displayed - Clicking on the Manhole Cover while in the Site Detaillscreen displays Site Data R view. The Site Data Review screen will be displayed showing Site Data Review Functions for that site. 23 2.7 Select Topic Function un F a Site Dqtar s.k e Selet To-pic S 9Ba -- ieY ) FUf .mary . U .. 4 -% -7 - * From the Navigation Template, located on the left-hand side of the screen, a Select Topic Button can be selected to display a topic selection menu. * This window menu allows the user to view all of the site or basin names that are selectable and allows the user to select either a Site or a Basin for screen display. - After selecting a specific topic from the menu, the user can either launch the specific topic screen using the "OK Button" or cancel the selection process by selecting the "Cancel Button". 24 2.8 Alarm Summary Screen __A_ I-Lq40II~ S. ~ o .F 6 m F F 4 j ._ _ . .. .I 7 .... e When the Alarm Summary screen is selected from the Navigation Template, the Alarm Summary Screen appears and displays the following: e Priority Window allows user to query Alarms by Priority. e Alarm Acknowledge Button allows the user to acknowledge a selected active alarm. e Alarm Group Button allows the user to query various alarm groups such as Basin or Lift Station Alarm Groups separately. - Operations Dispatch Button allows the user to send a copy of the selected alarm via E-Mail to an operations or maintenance dispatch group. * Event Manager Button displays the Event Manager pop-up window. " Event Log Button allows the user to display the Event Log, which displays a historical summary of all events and alarms to date. When the Alarm Summary screen is selected the IntelliHMI system will generate an Alarn Summary report and display it upon the screen. This report contains fields that provide the following alarm related information: -Date of alarm -Time of alarm -Type of alarm -Name of operator logged on whom acknowledges alarm -Alarm priority -Alarm name -Alarm group -Alarm value -Alarm limit 25 2.9 Event Manager Pop-Up Window Event Manager ScatterPlot Site Selection m Upper vel. threshold SDIA v (± at 10 FPS) SDIB A ~ SD1B SD1CM ] Lower vel. threshold SD1D - (± at 1 FPS) SD1E D SD1F SD2A Hydrograph High Depth Limit D- High ~-- ---------- 1- HLow % Daily Average 0 0-Low T SDR Enabled The Event Manager pop-up window provides the user with a point and click environment for: - Setting alarm limits for IntelliScan based alarm functionality * Enabling/Disabling Site Data Review for specific sites 26 2.10 Event Log Screen 0 O 7teEvtA -r V., ViI *i" I

-

V I .siitrjary, $50. .-. W 0 .4 -mt . ?anAm A --- - * When the Event Log Button is selected in the Alarm Summary Screen, the Event Log screen is displayed. * Event Log Priority Button allows the user to query events by priority for display. * Event Log Group Button allows the user to query specific event groups for display such as all alarms associated with a specific Basins or Lift Stations. * Print Button is provided to dump the Event Log to a printer on the network. * Clear button is provided to enable clearing of the Event Log with security password. * When the Event Log screen is selected the intelliHMI system will generate an Event Log report and display it upon the screen. This report contains field that provide the following event related information: -Date of event - Time of event - Event priority - Operator generated comments about the event - Event name - Event group - Event value - Event Limits 27 2.11 Communications Summary Screen .n APi ClaMufrbto spoiedt lo srcern ftComnctn ILb17"G~ T-d~ -1 -4 .~.4 Su m r buff t e r m uiainS m aysre sslce r mteN vg to Tpae AnACS(DSUira Communication s Server)bttn is proied. alwn ahicce orofiuraon dwnmmr of AC telemetry saitc for each site. - A CloeBuf button s provided t allow h user tolexig the Communicationmr screen e After a selected site is polled intelliscan provides a detailed analysis of communication characteristics between Intelliscan and the selected site. e A Telephone Test button is provided to allow testing of phone system attributes for landline communication systems. " A Radio Test button provides for testing of communications to any site connected to intelliscan via Spread Spectrum Radio. e An Alarm Setup button is provided to allow configuration of the Win91 1 Paging card. e A Monitor Setup Button Is provided to launch ADS QuadraScan for calling the flow monitor for instrument configuration, maintenance and analysis purposes. " An RTU Setup Button is provided to launch the ADS SCADA Interface Unit configuration and maintenance routine. Note this routine is not currently in the scope of work and will produce a pop-up stating "FUNCTION NOT IMPLEMENTED" 28 2.12 Weather Map Screen C u, -~~~~urAE - URETO U. ANA LSISW/RDA e)SE9 tA7. 1: ndow : *! :. 7 ., * When the Weather button is selected form the Navigation Template, a Microsoft Explorer Internet Browser screen will be launched within the IntelliHMI application. This browser screen will auto log-on through the City's ISP to IntelliCast.Com. The user will be able to navigate thru IntelliCast weather displays for the local and national region. 29 2.13 Document Screen A 3500 - Site Report rn S erv " '.b ;. |. ric. E.VAFD- FrMO - 1 .

STL.SU7-!. Ad ost-.- Ie~llcanecrteen)aDcmetMniilaperlheue ilbealwdt -valietweers.an 90 - W.5 17. comre etc. 350 ADSB SAFETYpor Walkre Trerric no,0n95 34. G..-Orim rBofe ro ng" -When the Document Button is selected from the Function Bar (at the bottom of most InteilliScan screens) a Document Menu will appear. The user will be allowed to select from a list of documents and launch specific documents with their editors or viewers. eThe Site Report contains detailed information regarding each specific flow site. This information Includes geographical location of the site, monitor type, serial number, installation date, installation details, phone number, ID number, field personnel comments, etc. 30 2.14 Report Screen Iir'inv nypw 1: i (I4. A hnteRpr Button4-* isseece fro th Fncio Bar aenup-upo -.5r p , - -. 24 K T.. Ir1it 41- moPP It; rA available reports is displayed. The user is allowed to select a report of choice and launch the report with it's Microsoft Excel Editor. e In the above graphic, a Site Performance Report is launched and the Microsoft E xcel editor starts building the report from the InteIiSQL Archive /Retrieval System. Once the report is fully constructed, the user can view the following: - Sheet #t 1 -- Site flow summary with graphics for last 24 hours. - Sheet # 2 - Site or Basin Summary Plots - Sheet # 3 - Site or Basin Raw Data in Spreadsheet format. Note this data can be edited, selected, copied or even linked to other spreadsheets automatically. 31 2.15 lntelliSQL Archive/ Retrieval System Enttes1Bb DatefTime FlowDepth Flow to FIewVe. niitvtIara -. -.--- 7 a LAxatmsT M amiyspee 10AnI999 12:28-27 19. - - 0.99528' nID 10,v6/1999 1228:291 32309 1 -)~4 1.@966 A02 999 1226:31 3,214789' 1.91321 1.003014 - 10t8999 12:28.33 1198024 1.53022 0 977834 10E/19 912'28:35

.

1[;9 10 /1999122:7 3.2251. 1.5084" - 1.0W974 10 8 99,2'53 3.3 3 6 5- 10171 1tE-/1 12-28;4163 27345 1 621.021947; 1000/199 12:29343 3.242931 - 1655 049 - - ~~10WM~n9 1 28:45 3244 1008I999 1228.473-95815 32 954 1 e When the Site Data Query Form is selected from the Archive / Retrieval Menu Pop up, IntelliScan launches the Microsoft Access County Database query editor. * This Site Data Query Form provides a pull down menu to select specific site locations for the query, date range and time range to be entered. * When the Site Data Query is Initiated the Archive/Retrieval system is accessed and a report with the following site data is generated; - Site queried -Date/Time of query -Flow Depth at selected site -Flow Rate at selected site -Flow Velocity at selected site 32 2.16 Outlook Screen lw-. -- ;ho -,W "t T*e d intsnams s em ed em on orcomes .c. w < C116 w.c 0, -mnw the vbtj > [Tye redpents* names. seperated by emlagns c, _Gvn e When the Outlook function is selected from the Function Bar, IntelliScan launches Microsoft Outlook. The user then has full control of Outlooks features for scheduling, phone directories, E-Mail functions and other office like personal productivity tools. 33 3.0 Archive / Retrieval System 3.1 Overview The Archive / Retrieval System allows a user, with appropriate access levels, to view and retrieve system data in multiple formats. These formats include but are not limited to alarm history data; minimum and maximum flow data for the entire system, basins or sites; flow data relative to'specific times or dates, etc. The Archive / Retrieval System is fully customizable to develop customer specific reports. This feature provides a powerful tool for analysis overall system performance, basin performance, or individual flow site performance. 3.2 Database Structure The Intelliscan System utilizes a Microsoft SQL@ database for Archive / Retrieval functions. This database is OBDC compliant and configured for asynchronous data transfer. Within IntelliscanTm, The IntelliCOM module, which facilitates communications with field sites, will be the primary mechanism that populates the database with field information. Site Data Review will also access the database and will populate certain fields during specific IntelliscanTM functions, as well. User access to the intelliscanTM database is gained through one of two workstations provided. 3.3 Site Data Logging Plan intelliscanTM will be accessing over sixty five flow/data sites for The City of San Diego. In addition to demand scans and timed scans of these assets, daily site logging will be accomplished. During site logging the Intelliscan T M server will dial each site within a basin via a modem mux and upload site data into the Archive / Retrieval System. This daily logging activity will be timed and coordinated to occur during minimum system usage hours. 3.4 Report Generation IntelliscanTM will access the Archive / Retrieval System for report generation. Reports will be displayed in a Microsoft Excel@ format. The report generation functions of IntelliscanTM are fully configurable to allow custom reports to be generated to support any user needs. The ability to custom configure data form the intelliscanTm database and present it in a user defined report structure provides a powerful analytical tool for proactively managing sewer and wastewater assets. 34 In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word "comprise" or variations such as "comprises" or "comprising" is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or 5 addition of further features in various embodiments of the invention. It is to be understood that, if any prior art publication is referred to herein, such reference does not constitute an admission that the publication forms a part of the common general knowledge in the art, in Australia or any other country. 35 2390801_1 (GHMatters) 31/08/10

Claims (31)

1. A method of monitoring and analyzing flow in a sewer system, comprising the steps of: s collecting, using a monitoring assembly, data representative of actual flow volume, flow velocity and depth in a first location and a detection time thereof; validating the data representative of actual flow volume, flow velocity and depth; storing the data representative of actual flow volume, flow velocity and depth in a memory; 10 maintaining, in the memory, previously stored data representative of previous flow volumes; determining a predicted flow volume, wherein the predicted flow volume is dependent upon data stored in the memory and the detection time associated with said data, wherein the detection time corresponds to both the data selected from the previously stored data and the data 15 representative of actual flow volume, flow velocity and depth; comparing the actual flow volume with the predicted flow volume to yield a difference value; computing a current threshold value on the basis of the predicted flow volume and the actual flow volume and periodically updating the current threshold value based on a 20 predetermined number of readings, and issuing an alarm when the actual flow volume is less than the periodically updated threshold value.

2. The method of claim 1, wherein the difference value exceeds a predetermined 25 variance value, and the method further comprises the step of issuing a flow loss notification.

3. The method of claim 2, wherein the method further comprises the step of communicating the flow loss notification by at least one of a cellular telephone means, a land line telephone means, a pager, an electronic mail means, and an Internet means. 30

4. The method of claim 1, wherein the difference value is equal to or less than a predetermined variance value, and the method further comprises storing the actual flow volume in the memory as stored calibration data. 35

5. The method of claim I , wherein the data representative of actual flow volume includes data representative of a rolling average flow volume. 36 2390801_4 (GHMatters) 311/010

6. The method of claim 1, wherein the data representative of actual flow volume includes at least one of flow velocity data and depth data.

7. The method of claim 1, wherein at least one of the determining step and the 5 comparing step is performed by the monitoring assembly.

8. The method of claim 1, wherein at least one of the determining step and the comparing step is performed by a computing device. 2.0

9. The method of claim 1, wherein the validating step is performed by the monitoring assembly.

10. The method of claim 1, wherein the predicted flow volume is further dependent upon additional data selected from the previously stored data, the additional data corresponding to a .5 rain event.

11. A flow monitoring system, comprising: a first monitoring assembly having at least one sensor, wherein the at least one sensor is operative to detect data representative of actual flow volume, flow velocity and depth of a 20 fluid substance at a first location, the data comprising at least one of flow velocity data and depth data; a processor in communication with the first monitoring assembly; a memory, wherein the memory is operative to store the data representative of actual flow volume, flow velocity, depth, and a detection time associated with said data; and 25 a central computing device in communication with the first monitoring assembly, wherein the processor is trained to validate the data representative of actual flow volume, flow velocity and depth, calculate an actual flow volume corresponding to the at least one of flow velocity data and depth data and compare the actual flow volume with a predicted flow volume to yield a difference value, the predicted flow volume being dependent upon the 30 data stored in the memory and the detection time associated with said data, and wherein the means for processing is trained to issue a notification if the difference value exceeds a predetermined variance amount.

12. The system of claim 11, further comprising an alarm device, the alarm device 35 responsive to the processor, and the alarm device being configured to selectively issue an alarm based on the difference value. 37 2390801_1 (GHMatters) 31/08/10

13. The system of claim 12, wherein a current threshold value is computed on the basis of the predicted flow volume and the actual flow volume, the current threshold value being updated periodically, and wherein the alarm device is configured to issue an alarm when the actual flow volume is less than the current threshold value. 5

14. The system of claim 13, wherein when an alarm is issued by the alarm device, the first monitoring assembly is configured to communicate the alarm.

15. The system of claim 14, wherein the first monitoring system is configured to 10 communicate the alarm via at least one of a cellular telephone means, a land line telephone means, a pager, an electronic mail means, and an Internet means.

16. The system of claim 11, wherein the processor is integral with the first monitoring assembly. 15

17. The system of claim 11, wherein the processor is integral with the central computing device.

18. The system of claim 11, further comprising a means for detecting a quantity of rain at 20 a location during a period of time.

19. The system of claim 18, wherein the means for detecting a quantity of rain includes at least one of a rain gauge, a weather service, and a weather web site. 25

20. The system of claim 11, wherein the central computing device is trained to predict at least one of an anticipated flow velocity, an anticipated depth, and an anticipated flow volume of the fluid substance at a second location.

21. An apparatus for monitoring and analyzing flow of a fluid substance in a sewer 30 system, the apparatus comprising: a first means for monitoring fluid flow having at least one means for sensing, wherein the at least one means for sensing is operative to detect data representative of actual flow volume, flow velocity and depth comprising at least one of flow velocity data and depth data at a first location; 35 a means for processing in communication with the first means for monitoring; a means for storing data, wherein the means for storing data is operative to store the data representative of actual flow volume, flow velocity and depth and a detection time 38 2390801_1 (GHPAetters) 31/08/10 associated with said data; and a means for computing in communication with the first means for monitoring, wherein the means for processing is trained to validate the data representative of actual flow volume, flow velocity and depth, 5 calculate an actual flow volume corresponding to the at least one of flow velocity data and depth data, compare the actual flow volume with a predicted flow volume to yield a difference value, compute a current threshold value on the basis of the predicted flow volume and the 10 actual flow volume and to periodically update the current threshold value, and wherein a means for alarming is configured to issue an alarm when the actual flow volume is less than the current threshold value, the predicted flow volume being dependent upon the data stored in the means for storing data and the detection time associated with said data, and issue a notification if the difference value exceeds a predetermined variance amount. 15

22. The apparatus of claim 21, wherein the means for processing is further trained to calculate an actual flow volume corresponding to the at least one of velocity data and depth data. 20

23. The apparatus of claim 21, further comprising a means for alarming responsive to the means for processing, and the means for alarming being configured to selectively issue an alarm based on the difference value.

24. The apparatus of claim 21, wherein when an alarm is issued by the means for 25 alarming, the first means for monitoring is configured to communicate the alarm.

25. The apparatus of claim 24, wherein the first means for monitoring is configured to communicate the alarm via at least one of a cellular telephone means, a land line telephone means, a pager, an electronic mail means, and an Internet means. 30

26. The apparatus of claim 21, wherein the means for processing is integral with the first means for monitoring.

27. The apparatus of claim 21, wherein the means for processing is integral with the 35 means for computing.

28. The apparatus of claim 21, wherein the first means for monitoring is further operative 39 2390801_1 (GHMatters) 31/08110 to detect data representative of flow velocity and depth, and to validate the data representative of flow velocity and depth.

29. The apparatus of claim 21, further comprising a means for detecting a quantity of rain 5 at a location during a period of time.

30. The apparatus of claim 29, wherein the means for detecting a quantity of rain includes at least one of a rain gauge, a weather service, and a weather web site. 10

31. The apparatus of claim 21, wherein the mean for computing is trained to predict at least one of an anticipated flow velocity, an anticipated depth, and an anticipated flow volume of the fluid substance at a second location. 40 2390801_1 (GHMatters) 31/08/10