Infrastructure monitoring devices, systems, and methods

Information

  • Patent Grant
  • 9861848
  • Patent Number
    9,861,848
  • Date Filed
    Tuesday, December 2, 2014
    9 years ago
  • Date Issued
    Tuesday, January 9, 2018
    6 years ago
Abstract
A leak detection assembly includes a leak detection sensor mountable on a surface of a component of a water infrastructure system; and a communications device mountable on the component, the leak detection sensor connected to the communications device, the communications device including an antenna, wherein the communications device is a component of an infrastructure monitoring system. A leak detection system includes a component of a water infrastructure system; a leak detection sensor mounted on a surface of the component; and a communications device positioned in proximity to the component and connected to the leak detection sensor, the communications device including an antenna, wherein the communications device is a component of an infrastructure monitoring system.
Description
FIELD

The disclosure is directed to devices, systems, and methods related to monitoring and controlling an infrastructure such as, but not limited to, the supply and use of commercial, industrial or residential water, gas and/or electric utilities, and, in particular, to devices, methods, and systems for monitoring and controlling a municipality and alerting a user to potential faults and actions required.


BACKGROUND

Municipalities administer and/or outsource numerous utility and safety systems within each municipality. Such systems are usually complex infrastructures and include but are not limited to water distribution, gas distribution, electricity distribution, waste management, traffic control, fire departments, police departments, and emergency response departments. Each of these systems needs to be monitored for use (authorized or unauthorized), faults, tampering, events, interruptions or blockages, leaks, contamination, and/or other issues.


To obtain an understanding of the state of any one system, or for ordinary use, billing or repair purposes, personnel must typically be sent into the municipality to check for problems within the system manually. This process is slow, is labor-intensive, and can lead to overlooked problems. Furthermore, preferred aspects of the system may be evaluated irregularly or infrequently, thereby allowing a problem to go unchecked for long periods of time. By way of example, a leak in a water main may cost a water company a significant amount of money in lost water, energy usage, and chemical treatment, particularly if the leak is not discovered for a relatively long period of time. Furthermore, a leak can lead to underground structural erosion. Interference with a system may go unnoticed unless it is reported to a central location.


Another problem and disadvantage associated with current systems is the lack of property rights sufficient to maintain a network of monitors and device controllers capable of creating a transmission infrastructure that can adapt to multiple monitors and controllers and form an information network for providing information about the system to the utility monitoring the network. For example, some networks require that new poles or towers be erected for placement of the communication devices. Municipalities may have to rent space on a utility company's poles for placement of such devices.


Furthermore, an issue in one system may cause an issue in another system. For example, a fire reported to the fire department may require the gas company to turn off gas flow to the vicinity of the fire and may require the water company to redirect water or additional water pressure to the vicinity. However, many current systems are not interoperable.


It is, therefore, desirable to have a single system that can monitor different aspects of at least one municipality system continuously and communicate with several entities at the same time.


SUMMARY

The disclosed methods, systems, and devices overcome the problems and disadvantages associated with current strategies and systems and provides new systems and methods of monitoring municipality infrastructure.


One embodiment is directed to an infrastructure monitoring system. The system includes an operations center and two or more communications devices communicatively coupled to the operations center. At least one communications device of the plurality of communications devices is coupled to a component of the infrastructure, and at least two communications devices are monitoring devices. The first monitoring device monitors a first aspect or location of the infrastructure and the second monitoring device monitors a second aspect or location of the infrastructure.


In one embodiment each monitoring device includes at least one sensor sensing at least one condition within the infrastructure, at least one data storage device storing data sensed by the at least one sensor, at least one transceiver device adapted to transmit and receive data, and at least one processor communicatively coupled to at least one sensor, data storage device, and transceiver device.


In one embodiment, the operations center and the plurality of communications devices are wirelessly communicatively coupled. At least one communications device is an output device. The output device includes a transceiver device adapted to receive or to transmit data, at least one output port, and a processor communicatively coupled to at least one of the transceiver device and at least one output port.


In one embodiment, the operations center and at least one output device are wirelessly communicatively coupled. Each communications device is adapted to receive transmissions for a second communications device and to retransmit the transmission to the second communications device. Each communications device is adapted to receive transmissions for the operations center and to retransmit the transmission to the operations center.


In one embodiment, at least one output device is coupled to at least one of an actuator control device, an alarm, a Radio-Frequency Identification device and a tamper prevention device.


In one embodiment, a monitoring device and an output device are contained within the same unit. The monitoring device and the output device share at least one of a power source, a transceiver device, and a processor.


The infrastructure can be at least one of a water distribution system, an electricity distribution system, a gas distribution system, a traffic control system, and an emergency response system. The system can monitor for at least one of use of gas, use of water, use of electricity, tampering, leaks, GPS location, proximity, tilt, smoke, temperature, rust, corrosion, fluid flow, pressure, water quality, air quality, contamination, radiation, pH, infrastructure status, and motion.


In one embodiment, the system produces an alert when at least one monitoring device registers an event. In one embodiment, at least one monitoring device is coupled to a visual or acoustical device. The operations center may include multiple operations centers. Each operations center is uniquely located. The operations center can monitor a plurality of infrastructures concurrently.


The plurality of infrastructures are selected from the group consisting of water systems, electrical systems, gas systems, emergency response systems, traffic control systems, and combinations thereof. A component of the infrastructure is one of a fire hydrant, a utility meter, a manhole cover, a utility pole, a valve, a pipe, a traffic light, water tower, water tank, valve box, valve box cover, meter box, meter box cover, and a smoke detector. In various embodiments where the component of the infrastructure is a fire hydrant, the communications device coupled to the fire hydrant is a repeater. At least one portion of the fire hydrant can be comprised of a material that does not interfere with the communications of the communications device. Moreover, the communications device coupled to the fire hydrant may be positioned within one of a nozzle cap, a pumper nozzle, a hose nozzle, a fire truck hookup, and a bonnet.


Another embodiment is directed to another infrastructure monitoring system. The system includes an operations center and a plurality of communications devices communicatively coupled to the operations center. At least one communications device of the plurality of communications devices is coupled to a fire hydrant, a valve, a valve box, a valve box cover, a meter, a meter box, a meter box cover, a water tower, a water tank, a pumper nozzle, a hose nozzle, or a manhole cover.


In one embodiment, the communications device coupled to the fire hydrant is one of a monitoring device, an output device, and a repeater. At least one portion of the fire hydrant is comprised of a material that does not interfere with the communications. In one embodiment, the communications device coupled to the fire hydrant is positioned within one of the nozzle cap, the pumper nozzle, the hose nozzle, the fire truck hookup, and the bonnet.


Another embodiment is directed to a fire hydrant. The fire hydrant includes a bonnet and a communications device coupled to the bonnet. The communications device is an element of an infrastructure monitoring system.


Other embodiments and advantages are set forth in part in the description, which follows, and in part, may be obvious from this description, or may be learned from practice.





DESCRIPTION OF THE DRAWINGS

The figures shown and described in greater detail are provided by way of example only.



FIG. 1 is a schematic of one embodiment of the disclosed system.



FIG. 2 is a schematic of one embodiment of a monitoring device.



FIG. 3 is a schematic of one embodiment of a control device.



FIG. 4A is an exploded view of one embodiment of a device of the disclosure as housed within a fire hydrant.



FIG. 4B is a perspective view of a device of the disclosure attached to a fire hydrant



FIG. 5A is a perspective view of one embodiment of an insulation device for sealing the bonnet of the fire hydrant from the water within the fire hydrant.



FIG. 5B is a perspective view of one embodiment of an insulation device and bonnet.



FIG. 6A is a perspective view of one embodiment of a nozzle cap for attachment to a fire hydrant.



FIG. 6B is a sectional view of one embodiment of the nozzle cap of FIG. 6A.



FIG. 6C is a sectional view of one embodiment of the nozzle cap of FIG. 6A.





DESCRIPTION

As embodied and broadly described herein, the disclosures herein provide exemplary embodiments of the disclosed systems, methods, and devices. Features may be embodied in various and alternative forms. Therefore, there is no intent that specific structural and functional details should be limiting, but rather the intention is that they provide a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure.


A problem in the art capable of being solved by the embodiments disclosed is monitoring and maintaining an infrastructure. It has been discovered that monitoring devices with one or two way communication abilities can be used to detect faults in the municipality's systems and provide on-demand, real time, or near real time device status, maintenance, and control over the systems.


A network of monitoring devices is capable of providing a system administrator with a full picture of the current state of the system. The network includes an array of different monitoring devices each capable of sensing at least one condition. The monitoring devices may be capable of sending data to and of receiving data from at least one operations center. Communication from the remote monitoring device may be directed to a central monitoring facility, to one of a number of regional monitoring centers, to a user, and/or to a research facility. Furthermore, the system includes at least one control device. Each control device is adapted to control a different aspect of the system. The control devices may be part of the monitoring devices or may be separate units. Communication is over the Internet, but may be over a private network, a local area network, or a wide area network. The communication involves a wireless component, such as from the remote monitoring device and/or control device to a regional monitoring facility or to distributed monitors. Also, the communications are secured or encrypted such that the communications system cannot be monitored by another unknown party. Access to the system is granted through user names and passwords, although additional and/or alternate encryption methods can be employed.


One embodiment is directed to water infrastructure systems. In such systems, monitoring devices can be located throughout the system, for example, as attachments to component parts, for feedback to a network that can provide real-time information to the utility operating the network. The network operators can use the information transmitted to activate controlling devices on the network, or to dispatch repair or other services as directed by the information provided by the network. For example, if water pressure monitors on a water meter indicate a variance between locations, a water leak can be reported using the network, and controlling devices can divert water. Pressure meters can be attached to fire hydrants to monitor and report pressure losses throughout the system, providing real-time information to benefit the users of the fire hydrants (fire departments who need to be assured of adequate pressure), the users of the system (water consumers who will be affected by lower pressure), and the operators of the system (who suffer asset loss as a result of lack of real-time information about losses).



FIG. 1 depicts a system 100 for monitoring, controlling, and communicating with at least one monitoring device 110 and/or at least one control device 111. System 100 includes an operations center 105 in communication with at least one monitoring device 110 and/or one control device 111. In the preferred embodiment, there is bi-directional communication between operations center 105 and devices 110 and 111. Communications can be simplex or duplex. Communication can occur over any communications network 115 known in the art, including but not limited to wired networks, wireless networks, Zigbee networks, Bluetooth networks, Z-wave networks, WiFi networks, WiMax networks, RF networks, local area networks (LAN), internet networks, wide area networks (WAN), cellular telephone network, hardwired telephone networks, 900 MHz wireless networks, and satellite networks. In one embodiment, the network is a fixed network. For example, the fixed network can be a mesh network or a star network. Additionally, devices 110 and 111 and operations center 105 can be in direct communication or can communicate through an intermediary device, such as a relay, a repeater, a gateway, or other device capable of receiving and retransmitting a message.


Each monitoring device 110 monitors at least one aspect of the infrastructure. The monitored aspect can be one or more of the components of the infrastructure (e.g. pipe conditions, valve conditions, fire hydrant conditions, service line conditions, meter conditions, power line conditions, and battery conditions), commodity conditions (e.g. fluid or gas flow, fluid or gas pressure, fluid or gas temperature, and fluid or gas contaminants), or combinations thereof. Additionally, each monitoring device 110 can be self monitoring. For example the monitoring devices 110 determine if there is a loss of communication, low battery levels, and/or internal damage (e.g. short circuits due to water damage). Additionally, each monitoring device 110 can be structurally stable (e.g. fixed to a valve, pipe, utility pole, a hydrant, a valve box, a valve box cover, a meter, a meter box, a meter box cover, a water tower, a water tank, a pumper nozzle, a hose nozzle, or an manhole cover) or movable (e.g. allowed to move with or within the flow of water or gas in the pipes).


For example, a monitoring device 110 or 111 can be coupled to a fire hydrant 405, a seen in FIG. 4B. The monitoring device 110 or 111 can be located within a nozzle cap 600 (i.e. in the pumper nozzle, the hose nozzle, or in the fire truck hook up), within a body of the fire hydrant, within a bonnet, attached to an outside of the fire hydrant, or at another location on or within the fire hydrant. A housing for the monitoring device 110 or 111 is made of plastic, nylon, other synthetic or natural materials, or any other material that does not block transmissions to and from the monitoring device 110 or 111. For example, as shown in FIG. 4A, the fire hydrant bonnet 400 can contain a monitoring device 110 and a waterproof container 420 for the monitoring device 110. In some embodiments the fire hydrant bonnet 400 can also contain a power source 425. In another example, as shown in FIG. 4B, the monitoring device 110 can comprise an antenna extending outside of the monitoring device 110. The antenna can be covered by an antenna cover 410. The monitoring device 110 can be coupled to the outside of a fire hydrant 405. In another embodiment, shown in FIGS. 5A and 5B, the bonnet 500 of a fire hydrant 505 can be isolated from the flow of water within the fire hydrant 505. For example, there can be a plastic, metal, or other material disc 530 that seals off a portion of the fire hydrant 505 to prevent water from reaching the interior regions of the bonnet 500.


In another embodiment, a monitoring device 110 or control device 111 is positioned within a nozzle cap 600 of a fire hydrant. A fire hydrant nozzle cap 600 is a device attached to an outlet nozzle and covers a nozzle opening. The nozzle cap 600 is furnished with a nut 605 or other device to permit the application of force to firmly attach the nozzle cap 600 to or to remove it from the outlet nozzle. FIG. 6A depicts an isometric view of an embodiment of the nozzle cap 600. In one embodiment, nozzle cap 600 is made of a composite, plastic, nylon, other synthetic or natural materials, or any other material that does not block transmissions to and from the monitoring device 110 or control device 111. The material has the same fading characteristics of the paint used on the exterior of the fire hydrant. For example, the material can have the same resistance to water, UV rays, corrosion, oxidation, or other causes of fading. Thereby, the paint and the nozzle cap 600 appear to be of the same material.



FIGS. 6B and 6C depict cutaway views of an embodiment of the nozzle cap 600. The nozzle cap 600 has an enclosure 610 which creates a cavity into which monitoring device 110 or control device 111 may be located. The cavity is enclosed by a cover 615. The enclosure 610 and cover 615 create a water tight seal able to withstand water pressures in excess of 400 psi. In various embodiments, other pressures may be utilized. Additionally, in one embodiment, nozzle cap 600 has an antenna cover 620. Antenna cover 620 can be made of the same material as nozzle cap 600 or of a different material. The location of the antenna is kept away from metal to achieve greater efficiency.


Nozzle hydrant threading 625 is provided as a connection means between the nozzle cap 600 and the fire hydrant. The nozzle cap 600 also includes enclosure threading 630 as a connection means for the enclosure 610 to connect to the nozzle cap 600. The enclosure 610 also includes connection threading 640 designed to mate with the enclosure threading 630. An antenna 650 is shown.


Each node in the network 115 detects errors in transmissions. Error detection can use cyclic redundancy codes using a table based on a defined polynomial or another method of error detection. In alternative embodiments, transmissions can be rerouted if the primary route is blocked or otherwise unavailable. Furthermore, devices 110 and 111 can confirm receipt of a message, e.g. via a hand shake protocol. In instances where confirmation is not received, the message can be resent along the same route or rerouted.


In various embodiments, each monitoring device 110 and each control device 111 is assigned a unique identifier. The unique identifier can be related to the devices' geographical locations, street addresses, order of installation, or any other method of identifying the devices 110,111. Furthermore, different types of devices 110 and 111 can have unique identifiers that include keys that are unique to that type of device. For example, the identifier for all water meters may begin with a WM, while the identifier for all leak detectors may begin with an LD. Each communication to and from a monitoring device 110 and control device 111 may include the unique identifier so that the message is received by the correct monitoring device 110 or control device 111, or so that operations center 105 can determine from where the message was sent.


Each monitoring device 110 and each control device 111 can be retrofitted to an existing system 100 or device 110,111, can be coupled to a new system 100 or device 110,111, or can be integrated into a new system 100 or device 110,111. For example, the system 100 can be connected to, work with, or work independently of a Supervisory Control and Data Acquisition (SCADA) network. In one embodiment, each monitoring device 110 and each control device 111 has a set of adapters to facilitate coupling the monitoring device 110 or control device 111 to a new or existing system 100 or device 110,111.


In one embodiment, system 100 is divided into sectors with each sector having at least one monitoring device 110 and/or at least one control device 111. Each sector can communicate directly with operations center 105 or each sector can have at least one intermediary communications device that is in communication with the monitoring device 110 and/or control device 111 and operations center 105. In one embodiment, the sectors are divided up by geographical location. For example, all of the devices in one neighborhood can be in a single sector and there is one sector for each neighborhood. In one embodiment, one intermediary communications device can service multiple sectors.


In alternative embodiments, each monitoring device 110 and/or control device 111 can communicate with adjacent monitoring devices 110 and/or control devices 111. In such embodiments, each monitoring device 110 and/or control device 111 can act as a transceiver or relay by receiving messages intended for another device 110,111 or for the operations center 105 and forwarding the message. In embodiments where the system 100 is divided into sectors, monitoring devices 110 and control devices 111 can communicate only within their sector. In other embodiments, monitoring device 110 and control device 111 can communicate with devices 110,111 in other sectors. Each monitoring device 110, control device 111, and/or the operations center 105 may be able to determine if a transmitted message was received by the intended device 110,111 and, if not, may be able to reroute the message until the message is properly received. Additionally, relay devices can be implemented in the system to further extend the range of communications. For example, relay devices can be placed on utility poles, on municipal buildings, within fire hydrants, and/or under manhole covers. In alternative embodiments, devices 110 and 111 communicate over a mesh network. In the mesh network, devices 110 and 111 can communicate with other devices 110 and 111 within the mesh network. Operations center 105 can set specified communications pathways derived from routing tables.


Operations center 105 can be located at a municipality office, a private or public company, a fire station, a police station, or any other entity that monitors operations center 105. In other embodiments, operations center 105 can be remotely hosted and accessible by the Internet. In such embodiments, operations center 105 can take advantage of cloud computing (e.g. a network of remotely hosted computers, servers, and data storage devices). Compared to non-remotely hosted computer networks, cloud computing can increase ease of use, increase access, increase security, decrease costs, be custom tailored, and provide an unrestricted expansion of storage space. Additionally, in various embodiments, there is a plurality of operations centers 105. One or more operations centers 105 can be located at different entities and each operations center 105 can monitor a different aspect of system 100. For example, in embodiments where one monitoring device 110 monitors water usage and another monitors gas leaks, the water usage aspect can be monitored by a water utility company and the gas leaks can be monitored by the gas utility company and/or the fire department. In some embodiments, there are redundant operations centers 105, where at least two operations centers 105 monitor the same aspect of system 100. Operations center 105 can send transmissions to update the firmware of devices 110 and 111.



FIG. 2 is a schematic of a monitoring device unit 200. Monitoring device unit 200 includes a processor 205. Processor 205 is coupled to at least one input port 210 for receiving data from sensors 215. Processor 205 is also coupled to a transceiver 220 for sending and receiving signals. Processor 205 is coupled to a data storage unit 230. Data storage unit 230 can hold a predetermined amount of data received from the sensors 215. For example, data storage unit 230 can hold data for a predetermined amount of time (e.g. one day, one week, or one month), can hold a predetermined number of readings (e.g. 10 readings, 100 readings, 1000 readings), or can hold data until directed to purge the data by the operations center 105. Additionally, data storage unit 230 can hold instructions for processor 205 to execute upon prompting from the operations center 105. Processor 205 compiles at least some of the data stored in data storage unit 230 for transmitting to the operations center 105.


Each monitoring device unit 200 may collect data and/or transmit data continuously, at specific intervals, or randomly. In embodiments where the monitoring device unit 200 collects and transmits data in a non-continuous configuration, monitoring device unit 200 may turn off or reduce power consumption during the non-data collecting periods to save energy. Processor 205 is coupled to a power source 235. Power source 235 can be a unit capable of powering processor 205 and devices attached to processor 205. For example, power source 235 can be a battery, solar panel array, wind turbine, water turbine, electrical lines, or combinations thereof. In preferred embodiments, there is also a backup power source, such as a battery. The power may derive from the operation of the system 100.


In one embodiment, processor 205 is coupled to at least one sensor 215 that monitors at least one condition associated with the monitoring device. Sensors 215 can determine the status of a device. Sensors 215 can be directly wired to processor 205 or can use wireless communication to send and receive signals from processor 205. Sensors 215 can be positioned within the monitoring device or be external to the monitoring device. In alternative embodiments, sensors 215 are positioned remote from the monitoring device. For example a sensor can be positioned in a fire hydrant, on a nearby building, or on a utility pole. In the embodiments in which sensors 215 and processor 205 communicate wirelessly, the same communications protocol can be used in the sensor/processor communication as in the processor/operations center communication, or different communications protocols can be used in the sensor/processor communication from in the processor/control center communication. For example, the sensor/processor communications can use RF protocols while the processor/control center communications can be over a wired network.


In one embodiment, sensor 215 is a use monitor. In such embodiment, the use monitor records the amount of water, gas, electricity, or other commodity that is used by a customer over a specified period of time. The use monitor can continuously record the amount of the commodity used or the use monitor can provide a signal to processor 205 that the commodity is in use. Processor 205 can transmit a signal to the operations control to alert the operations center 105 that the monitoring device 110 is being used and/or how much of the commodity is flowing through the sensor 215. The operations center 105 can request a reading from the use monitor on demand. The processor 205 or the operations center 105 can determine based on the use, if there is unauthorized use of the commodity. Upon detection of unauthorized use, at least one of processor 205 or the operations center 105 can generate an alarm that there is unauthorized use. For example, in embodiments where the use monitor is coupled to a fire hydrant 405, if the use monitor indicates that the fire hydrant 405 is in use, however no fire is reported, the operations center 105 can disseminate an alert that there is potential misuse of the fire hydrant 405.


In various embodiments, at least one sensor 215 is a tamper sensor. The tamper sensor can be a motion detector, a contact sensor, a rotation sensor, a touch sensor, a proximity sensor, a biofeedback sensor, a temperature sensor, a capacitance sensor, a resistance sensor, or any other sensor that is able to detect the presence of an object. The tamper sensor can send a message to processor 205 when the tamper sensor detects an event. The processor 205 will then evaluate the event to determine if a device being monitored is being tampered with or will relay the message to the operations center 105 for evaluation. The monitored device can be a fire hydrant, utility meter, valve, manhole cover, pump, or any other device that may be tampered with. Upon detection of a tamper event, at least one of processor 205 and the operations center 105 can generate an alarm that the device is being tampered with. The monitoring device may activate a tamper prevention device (described below). The operations center 105 will send a transmission to processor 205 telling processor 205 to disregard messages from the tamper sensor for a predetermined period of time or until another message is received from the operations center 105 telling processor 205 to resume monitoring for tamper events. For example, if a fire department needs to use a fire hydrant, the operations center 105 will send a message to processor 205 to temporarily disregard any tamper events. Once the fire department is finished using the fire hydrant the operations center 105 will send a message to processor 205 to start monitoring for tamper events again.


In some embodiments at least two of sensors 215 are leak detectors. Each leak detector can include an in-pipe leak detector and/or an exterior leak detector. In gas applications, the leak detectors are vapor sensors. While in liquid applications, the leak detectors use acoustic monitoring to determine presence and location of a leak. The energy generated from a leak is transmitted within a pipe through the commodity as well as through the pipe wall. Each leak detector can detect the vibrations made by the leak in the commodity or the pipe wall, joint or service line. To determine the location of a leak, at least two detectors must detect the same leak. Based on the velocity of the sound traveling along the pipe (V), the distance between the two detectors (D) and the delay between the times each detector detects the sound (T), the location of the leak (L) can be determined by the following equation:

L=(D−(V×T))/2


When using the above equation, the typical velocity of sound in water is about 1500 m/s while the typical speed of sound through an iron pipe is 5100 m/s. The velocity can be measured empirically. For example, if the leak is exactly midway between the two detectors the sound would reach both detectors at the same time. Each detector may monitor continuously or at predetermined periods of time. The leak detectors can send a message to processor 205 when the leak detectors detect an event. The processor 205 can then evaluate the event to determine if there is a leak and how severe the leak is or can relay the message to the operations center 105 for evaluation. Upon detection of a leak event, at least one of processor 205 or the operations center 105 can generate an alert that there is a leak if the leak is determined to be severe enough to warrant attention.


In various embodiments, at least one sensor 215 is a smoke detector. The smoke detector can be a photoelectric detector, an ionization detector, or any other device that can detect the presence of smoke. The smoke detector can be located within the monitoring device or exterior to the monitoring device. The smoke detector monitors continuously for smoke. The smoke detector can send a message to processor 205 when the smoke detector detects an event. The processor 205 can then evaluate the event to determine if there is smoke or can relay the message to the operations center 105 for evaluation. Upon detection of smoke, at least one of processor 205 or the operations center 105 can generate an alert that there is smoke.


In some embodiments, at least one sensor 215 is a temperature sensor. The temperature sensor can be a contact sensor (e.g. thermocouples, thermistors, liquid-in-glass thermometers, resistance temperature detectors, filled system thermometers, bimetallic thermometers, semiconductor temperature sensors, and phase change indicators) or a non-contact sensor (e.g. radiation thermometers, thermal imagers, ratio thermometers, optical pyrometers, and fiber optic thermometers). The temperature sensor can be located within the monitoring device or exterior to the monitoring device. In one embodiment, the temperature sensor monitors continuously for the temperature to rise above or drop below a predetermined threshold. The temperature sensor can send a message to processor 205 when the temperature sensor detects a temperature beyond the thresholds. The processor 205 can then evaluate the event to determine if there the temperature is a problem (such as freezing pipes or fire) or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable temperatures, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable temperature condition.


In various embodiments, at least one sensor 215 is a rust and/or corrosion sensor. The corrosion sensor can detect rust and/or corrosion using any method known in the art, including but not limited to liquid penetration inspection, magnetic particle inspection, radiographic inspection, visual inspection, eddy current inspection, ultrasonic inspection, and thermographic inspection. The corrosion sensor can send a message to processor 205 when the corrosion sensor detects a rust or corrosion beyond a threshold value. The processor 205 can then evaluate the rust or corrosion to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable rust or corrosion, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable amount of rust or corrosion.


In various embodiments, at least one sensor 215 is a fluid flow sensor. The fluid flow sensor can be used either in gas systems or liquid systems. The fluid flow sensor can detect direction of the flow, turbidity of the flow, velocity of the flow, density of the flow, viscosity of the flow, and/or any other aspect of the flow. The fluid flow sensor may be a velocimeter, a laser-based interferometer, a vane, a rotary potentiometer, a Hall effect sensor, a device to measure heat transfer caused by the flowing fluid, or any other device know in the art to measure the flow of fluid. The fluid flow sensor can send a message to processor 205 when the fluid flow sensor detects a flow anomaly. The processor 205 can then evaluate the event to determine if the anomaly is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of an anomaly, at least one of processor 205 and the operations center 105 can generate an alert that there is an anomaly.


In various embodiments, at least one sensor 215 is a pressure sensor. In one embodiment, the pressure sensor is positioned within the flow of fluid or area in which the pressure is being sensed. For example, the pressure sensor can be positioned at the base of a fire hydrant and in the water to determine the water pressure within water system, in a pipe to determine gas or water pressure within a gas or water system, or in a room to determine air pressure within the room. The pressure sensor can be a piezoresistive strain gauge, a capacitive gauge, an electromagnetic gauge, a piezoelectric device, or any other device know in the art to measure pressure. The pressure sensor can send a message to processor 205 when the pressure sensor detects a pressure anomaly. The processor 205 can then evaluate the event to determine if the anomaly is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of an anomaly, at least one of processor 205 or the operations center 105 can generate an alert that there is an anomaly.


In various embodiments, at least one sensor 215 is a water quality monitor. The water quality monitor can monitor a single aspect of water flowing through the system 100 or multiple aspects of the water. For example, the water quality monitor can monitor one or more of the water's bacteria levels, pharmaceutical levels, alkalinity, chlorine and/or chloramine levels, hardness, pH levels, peroxide content, iron levels, nitrate levels, nitrite levels, arsenic levels, pollution levels, oxygen levels, biomass levels, and/or any of the other contaminants regulated by the Environmental Protection Agency (EPA). In embodiments where there are multiple monitoring devices, all the devices can monitor the same aspects, each device can monitor a different aspect, or a combination thereof. In one embodiment, the water quality monitors test the water continuously, however, in alternative embodiments, the water quality monitors test the water at predetermined time intervals (e.g. once a hour, once a day, once a week, etc.). Each water quality monitor relays data to processor 205. Processor 205 can store the data on data storage unit 230 or transmit the data to the operations center 105. Either processor 205 or the operations center 105 can monitor the data received from the water quality monitors to determine if there is a change in the levels of the contaminants or if the levels of the contaminants rise above a threshold level. Upon detection of unsafe contamination levels, at least one of processor 205 or the operations center 105 can generate an alert that there is contamination in the water system.


In the embodiments where at least two monitoring devices are monitoring the same aspect of the water, the operations center 105 can determine if there is a change in the aspect of the water from the location of one monitoring device to the location of the other. If there is a change, the operations center 105 can generate an alert that there is a change in the water system and output the approximate location of the change in the water system.


In various embodiments, at least one sensor 215 is an air quality monitor. The air quality monitor can monitor a single aspect of the air or multiple aspects of the air. Furthermore, the air quality monitor can monitor the air within a facility or ambient air. For example, the air quality monitor can monitor one or more of the air's benzene levels, carbon disulfide levels, urethane levels, formaldehyde levels, phosphorus levels, naphthalene levels, parathion levels, quinoline levels, trifluralin levels, and/or any of the other contaminants whose acceptable levels have been set by the Environmental Protection Agency. In embodiments where there are multiple monitoring devices, all the devices can monitor the same aspects or each device can monitor a different aspect, or a combination thereof. In one embodiment, the air quality monitors test the air continuously, however, in preferred embodiments, the air quality monitors test the air at predetermined time intervals (e.g. once a hour, once a day, once a week, etc.). Each air quality monitor relays data to processor 205. Processor 205 can store the data on data storage unit 230 or transmit the data to the operations center 105. Either processor 205 or the operations center 105 can monitor the data received from the air quality monitors to determine if there is a change in the levels of the contaminants or if the levels of the contaminants rise above a threshold level. Upon detection of unsafe contamination levels, at least one of processor 205 or the operations center 105 can generate an alert that there is contamination in the air.


In the embodiments where at least two monitoring devices are monitoring the same aspect of the air, the operations center 105 can determine if there is a change in the aspect of the air from the location of one monitoring device to the location of the other. If there is a change, the operations center 105 can generate an alert that there is a change in the air and output the approximate location of the change in the aspect of the air. Furthermore, in embodiments where there is a time stamp associated with each reading, the operations center 105 can determine the approximate direction and speed at which the contaminant is moving.


In various embodiments, at least one sensor 215 is a radiation detector. The radiation detector can distinguish between natural sources of radiation and artificial sources of radiation or can distinguish between normal levels of radiation and abnormal levels of radiation. The radiation detector detects ionizing radiation. Ionizing radiation consists of subatomic particles or electromagnetic waves that are energetic enough to detach electrons from atoms or molecules, ionizing them. Examples of ionizing particles are energetic alpha particles, beta particles, and neutrons. The ability of an electromagnetic wave (photons) to ionize an atom or molecule depends on its frequency. Radiation on the short-wavelength end of the electromagnetic spectrum—high frequency ultraviolet, x-rays, and gamma rays—is ionizing. The radiation detector is one of a dosimeter, a Geiger counters, or a scintillation counters. Dosimeters measure an absolute dose received over a period of time. Ion-chamber dosimeters resemble pens, and can be clipped to one's clothing. Film-badge dosimeters enclose a piece of photographic film, which will become exposed as radiation passes through it. Ion-chamber dosimeters must be periodically recharged, and the result logged. Film-badge dosimeters must be developed as photographic emulsion so the exposures can be counted and logged; once developed, they are discarded. Another type of dosimeter is the TLD (Thermoluminescent Dosimeter). These dosimeters contain crystals that emit visible light when heated, in direct proportion to their total radiation exposure. Like ion-chamber dosimeters, TLDs can be re-used after they have been ‘read’. Geiger counters and scintillation counters measure the dose rate of ionizing radiation directly. Preferably, the radiation detector is a solid-state device.


Upon detecting radiation, the radiation detector can relay the detection to processor 205. Processor 205 can save the detection on data storage unit 230 or transmit a message regarding the detection to the operations center 105. Processor 205 or the operations center 105 can evaluate the detection and act in accordance with the purpose of the radiation detector. For example, if the radiation detector detects radiation over a threshold level, processor 205 or the operations center 105 can generate an alert that there are unsafe radiation levels.


In various embodiments, at least one sensor 215 is a motion detector. The motion detector can be a radar-based motion detector, a photo-sensor motion detector, a passive infrared motion detector, a magnetic motion detector, a pressure sensitive motion detector, or any other device capable of detecting the motion of objects. The motion detector can be used, for example, to count the number of cars passing through an intersection to control a traffic light, for tamper prevention as described above, for security purposes, and/or to control street lights. The motion detector can be placed within the monitoring device or exterior to the monitoring device. Upon detecting motion, the motion detector can relay the detection to processor 205. Processor 205 can save the detection on data storage unit 230 or transmit a message regarding the detection to the operations center 105. Processor 205 or the operations center 105 can evaluate the detection and act in accordance with the purpose of the motion detector. For example, if the motion detector detects a predetermined number of vehicles have passed the monitoring device, processor 205 or the operations center 105 can cause a traffic light to switch from green to red. As a second example, if the motion detector detects a motion after a predetermined time, e.g. after sunset, processor 205 or the operations center 105 can cause the street lights near the monitoring device to illuminate for a predetermined period of time.


In various embodiments, at least one sensor 215 is a tiltmeter. The tiltmeter can be a pendulum, a water tube, a bubble-level meter, and/or a MEMS electronic meter. The tiltmeter can be located on devices within the system, such as, but not limited to, pipes, fire hydrants, meters, valves, utility poles, manhole covers, and light posts. The tiltmeter can send a message to processor 205 when the sensor detects a tilt beyond a threshold value. The processor 205 can then evaluate the tilt to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable tilt, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable tilt. For example, if a utility pole is struck by a car, the tiltmeter will indicate that the utility pole is tilting at an undesirable level and the operations center 105 can alert the municipality to send out a repair crew to assess the situation and repair the utility pole.


In various embodiments, at least one sensor 215 is a proximity sensor. The proximity sensor can use electromagnetic technology, electrostatic technology, infrared technology, or a touch switch. The proximity sensor can detect if devices are properly closed or if devices are improperly touching. The proximity sensor can send a message to processor 205 when the proximity sensor detects proximity beyond a threshold value. The processor 205 can then evaluate the proximity to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable proximity, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable proximity. For example, if a valve is improperly closed, the proximity sensor will indicate that the valve is not closed and processor 205 can alert the municipality to take proper actions to close the valve.


In various embodiments, at least one sensor 215 is a visual or audio device. The device can be an infrared camera, a video camera, a still camera, a digital camera, a film camera, a mobile vision device, a microphone, a vibration detector, combinations thereof, or any other device capable of acquiring an image or sound. In one embodiment, the device is a digital video camera that takes video images continuously. In another embodiment, the device is a digital still camera that takes still images at regular intervals or upon command from processor 205. In alternative embodiments, the device can be a traffic camera and take a picture when instructed to by processor 205, for example upon determination that a vehicle is running a red light. In other embodiments, the device is used to perform visual inspections of the system infrastructure. For example, the field of view of the device can include a device within the system that is apt to corrode and the camera can provide an easy method to visually inspect any degradation of the device. The device can send image data to processor 205 where the data is stored on data storage unit 230 or is transmitted to the operations center 105. In various embodiments, image or sound data is streamed continuously from the device to processor 205 and from processor 205 to the operations center 105. The data stream can either be live or delayed. The device can be located on the monitoring device, near the monitoring device, or within the monitoring device with a portion of the device extending outside the monitoring device or with a hole in the monitoring device through which the device can obtain images or sounds. In some embodiments, the device is positioned on an actuator. The actuator can move to reposition the field of view of the device. The actuator can move upon demand from processor 205 or can move autonomously. In the embodiments where the actuator moves autonomously, the movement can be continuous or sporadic.


In various embodiments, at least one sensor 215 is a Global Positioning System (GPS) receiver. In one embodiment, the GPS receiver is located on devices within the system 100, such as, but not limited to, pipes, fire hydrants, meters, valves, utility poles, manhole covers, and light posts. The GPS receiver can send a message to processor 205 indicating GPS location. The processor 205 can then relay the message to the operations center 105 for evaluation, conformation, and documenting. Upon detection of unexpected GPS location, at least one of processor 205 or the operations center 105 can generate an alert that the GPS receiver has moved, possibly indicating that the device has been dislodged, tampered with, or stolen. Additionally, the GPS location can be used, for example, by emergency responders to locate fire hydrants, or repair crews to determine the location of a buried device. In such embodiments, the operations center 105 can disseminate information to the emergency responders or repair crews to easily locate the device. The dissemination can occur by any method, including but not limited to, verbally, over a telecommunications network (e.g. to a smart phone or portable computer), or over a shortwave radio. In embodiments where the monitoring device is moving with the flow of fluid, the sensor can provide updated locations of the monitoring device to track, for example, the flow or contamination levels within the flow.


Other possible sensors 215 connected to monitoring device unit 200 can include, but are not limited to, flow rate meters, backflow meters, system status monitors, and power level monitors.



FIG. 3 is a schematic of a control device 300. Control device 300 includes a processor 305. Processor 305 is coupled to at least one output port 310 for controlling an output device 340. Processor 305 is also coupled to a transceiver 320 for sending and receiving signals. Processor 305 is communicatively coupled to output port 310. Output port 310 is connected to at least one output device 340. Each output device 340 can have the same purpose or each output device 340 can have a different purpose, or combinations thereof. Output devices 340 can be located within control device 300 or external to control device 300, as shown. Furthermore, output devices 340 can be attached to control device 300 or can be remote from control device 300. Output devices 340 communicate with output port 310 through wired or wireless communication channels. In various embodiments, output devices 340 are capable of bidirectional communication. In various embodiments, control device 300 is an integral part of a monitoring device. In such embodiments, the control device 300 and the monitoring device can share the same processor and/or transceiver.


In various embodiments, processor 305 is coupled to a data storage unit 330 that may be a database in some embodiments. Data storage unit 330 may store instructions for processor 305 of how to control output devices 340. In various embodiments, processor 305 is coupled to a power source 335. Power source 335 can be any device capable of powering processor 305 and any devices attached to processor 305. For example, power source 335 can be a battery, solar panel array, wind turbine, water turbine, electrical lines, or combinations thereof. In various embodiments, there is also a backup power source, such as a battery.


In various embodiments, at least one output device 340 is an actuator control device. The actuator control device can control any type of actuator, including but not limited to, a tamper prevention device, a locking device, a camera motion device, a fire hydrant nut opening device, or a valve. The actuator control device can control the actuator autonomously or upon demand from processor 305. For example, upon receiving a signal that a particular event has been sensed, processor 305 may send a command to the actuator control device to act in a particular manner. Likewise, in some embodiments the control signal may come from the operations center 105. The actuator can be mechanical, electrical, or a combination thereof


In various embodiments, at least one output device 340 is an alarm. The alarm can be a visual alarm, an audible alarm, a tactile (i.e. vibration) alarm, or a combination thereof. The alarm can be located within the monitoring device, exterior to the monitoring device, at the operations center 105, remote from the system, or any other location sufficient to alert. Furthermore, there can be more than one alarm at different locations. For example, in the embodiments where there is a smoke detector, there can be an audible alarm located within the fire detector to alert people around the monitoring device of a potential fire, there can be an audible alarm at the fire station to alert the fire department of the potential fire, and there can be a visual alarm at the gas utility company to indicate that the flow gas in the vicinity of the potential fire should be shut off. In various embodiments the alarm is controlled by the processor 305, while in other embodiments the alarm is controlled by the operations center 105. In various embodiments, the alarm has an on/off switch controllable locally.


In various embodiments, at least one output device 340 is a tamper prevention device. The tamper prevention device can be a mechanical lock, an alarm, a light, an electrical shock generator, a retaining device, an electrical lock, or any other device capable of preventing tampering. The tamper prevention device may merely deter tampering or may incapacitate a person who is trying to tamper with the device, depending on the level of security. In some embodiments the tamper prevention device is controlled by the processor 305, while in other embodiments the tamper prevention device is controlled by the operations center 105.


In various embodiments, at least one output device 340 is a Radio-Frequency Identification (RFID) device. The RFID device can broadcast information about the device to which it is attached. For example, the RFID device may broadcast manufacturer information, location information, last service date, device information (e.g. make, model, and/or year), current status (e.g. a valve can broadcast if it is open or closed), etc. In some embodiments the RFID device is updateable by the processor 305 or by the operations center 105. The RFID device can be either an active (e.g. battery powered) or passive (e.g. require an external source to provoke signal transmission) device.


EXAMPLES

A system of the disclosure is monitoring a water distribution infrastructure. The system is used to automatically control the water pressure within the system. Such a system includes a number of water meters disbursed throughout the infrastructure relaying real time use information to a control center. Upon a determination by the operations center that there is low usage of the system (e.g. at night) based on information received by a predetermined number of the water meters, the operations center causes pumps supplying pressure within the system to reduce or cease pumping. Thereby cutting down on the electricity used by the pumps while maintaining enough pressure throughout the infrastructure to satisfy any water needs. The determination to reduce or cease pumping can be also based on information received from pressure sensors disbursed throughout the infrastructure. For example, if the pressure within the infrastructure exceeds a threshold value, the operations center causes the pumps to reduce or cease pumping.


In another example, the system is used to assist in maintaining the infrastructure. Water pipes and valves are often buried underground making it difficult to locate, assess the status of the devices, and repair them if necessary. Using an example of the above described system, each device is equipped with a monitoring the device. The monitoring device, for example, may monitor for corrosion using a corrosion monitor, geographical location using a GPS receiver, and leaks using a leak detector. Upon detection of corrosion and/or a leak, the monitoring device sends a message to the operations center where the information is analyzed. The operations center is able to make a determination if the corrosion and/or leak is severe enough to warrant fixing, if the corrosion and/or leak should be watched to determine if it worsens, or if the corrosion and/or leak can be ignored. The operations center will also alert a person of the situation for further assessment.


If it is determined that the corrosion and/or leak should be fixed, the operations center disseminates information to a repair crew and redirects water flow away from the device. Such information can include location of the device, based on data received the GPS receiver, problem associated with the device, device information (e.g. make, model, and/or year), etc. The monitoring device can also be equipped with a RFID transmitter, which transmits at least some of the above information. The repair crew receives the information on a smart phone, a portable computer, or other device capable of receiving such information. Upon completion of the repair, the operations center updates the system to indicate a new last repaired date for the device.


In another Example, the system is monitored by several entities within a municipality at the same time. For example, a fire department, a gas utility, a water utility, an electric utility, and traffic control center all monitor the system concurrently. Upon detection of smoke by a monitoring device, the control center alerts each entity of a potential fire. The location of the potential fire is determined by cross-referencing the ID number of the monitoring device with a lookup table or based on information received from a GPS receiver. The fire department uses the location information to send out emergency response personnel to the vicinity of the potential fire. The gas utility uses the location information to divert or shut off gas flow to the vicinity of the potential fire. The water utility uses the location information to divert water to or increase water pressure in the vicinity of the potential fire as well as determines if any fire hydrants in the vicinity of the potential fire are potentially damaged (e.g. are tilted at an unusual angle, are receiving no or little water pressure, or have been tampered with) based on information received from monitoring devices attached to the fire hydrants. The location of the fire hydrants is determined by cross-referencing the ID number of the monitoring device with a lookup table or based on information received from a GPS receiver. The water utility automatically alerts the fire department as to which fire hydrants to use. The water utility also disables any tamper prevention devices associated with the fire hydrants. The electric utility receives a signal that additional pressure may be needed within the water system and provides an increased electrical load to the water pumps. Additionally, the traffic control center adjusts traffic lights en route from the fire station to the vicinity of the potential fire to assist the fire trucks in arriving quickly and safely.


In another example, the system is used to monitor contamination of the fluid flowing through the system. The system includes pressure sensors, leak detectors and contamination detectors. Leaks within the system can cause a pressure drop throughout the system which can lead to contaminants being drawn into the system. For example, if a pipe is under water and the pressure inside the pipe drops below the pressure outside the pipe, the exterior water will flow into the pipe. Therefore, the system has several monitoring devices to check for such potential or actual contamination. The pressure sensors will indicate if the pressure within the system drops below a threshold level at which contaminants can be drawn into the system. The leak detectors will indicate that there is a leak through which contaminants can enter the system. While the contamination detectors will indicate if there is contamination within the system, indicating a possible breach of the infrastructure of the system.


Other embodiments and uses of the disclosed systems, methods, and devices will be apparent to those skilled in the art from consideration of the specification and practice disclosed herein. All references cited herein, including all publications, U.S. and foreign patents and patent applications, are specifically and entirely incorporated by reference. It is intended that the specification and examples be considered exemplary only with the true scope and spirit of the disclosure indicated by the following claims. Furthermore, the term “comprising of” includes the terms “consisting of” and “consisting essentially of” All examples illustrate possible embodiments but should not be viewed as limiting the scope of the disclosure.

Claims
  • 1. A leak detection assembly comprising: a leak detection sensor;a watertight housing enclosing the leak detection sensor and configured to isolate the leak detection sensor from any fluid exterior to the housing;a bracket comprising a bracket hole and configured to mount the leak detection sensor on an exterior surface of a component of a water infrastructure system by a first flange defined by the exterior surface, the component comprising a plurality of fasteners, the bracket secured to the component by at least one of the plurality of fasteners extending thru the first flange and the bracket hole, each fastener configured to connect to a second flange defined by the water infrastructure system; anda communications device configured to be mounted on the exterior surface of the component, the leak detection sensor connected to the communications device, the communications device including an antenna, wherein the communications device is a component of an infrastructure monitoring system.
  • 2. The leak detection assembly of claim 1, wherein the communications device is insulated from water, wherein the component of the water infrastructure system includes at least one portion comprised of a material that does not interfere with communications of the communications device.
  • 3. The leak detection assembly of claim 2, wherein the at least one portion of the component of the water infrastructure system is comprised of a composite material.
  • 4. The leak detection assembly of claim 3, wherein the composite material has a color that fades at a rate that is the same as a rate of fading of a color of paint.
  • 5. The leak detection assembly of claim 3, wherein the composite material does not interfere with wireless signals.
  • 6. The leak detection assembly of claim 1, wherein the component of the water infrastructure system is a hydrant including a nozzle cap.
  • 7. The leak detection assembly of claim 1, wherein the leak detection sensor is coupled to the housing.
  • 8. The leak detection assembly of claim 1, wherein the housing defines a cavity, wherein the housing comprises a cover sealing the cavity.
  • 9. The leak detection assembly of claim 1, further comprising an antenna cover, at least a portion of the antenna situated within the antenna cover.
  • 10. The leak detection assembly of claim 1, wherein the component is a hydrant comprising a bonnet, wherein the leak detection sensor is mounted to the bonnet of the hydrant.
  • 11. A leak detection system comprising: a first component and a second component of a water infrastructure system, each component comprising a flange and a plurality of fasteners configured to extend thru the flange;a first leak detection sensor and a second leak detection sensor;a first watertight housing enclosing the first leak detection sensor and configured to isolate the first leak detection sensor from any fluid exterior to the first watertight housing;a second watertight housing enclosing the second leak detection sensor and configured to isolate the second leak detection sensor from any fluid exterior to the second watertight housing;a first bracket mounting the first leak detection sensor on an exterior surface of the first component, the first bracket comprising a bracket hole and secured to the first component by at least one of the plurality of fasteners of the first component by extending thru the bracket hole and the flange of the first component;a second bracket mounting the second leak detection sensor on an exterior surface of the second component, the second bracket comprising a bracket hole and secured to the second component by at least one of the plurality of fasteners of the second component by extending thru the bracket hole and the flange of the second component;a first communications device positioned on the exterior surface of the first component and connected to the first leak detection sensor; anda second communications device positioned on the exterior surface of the second component and connected to the second leak detection sensor, each communications device comprising an antenna, wherein each communications device is a component of an infrastructure monitoring system.
  • 12. The leak detection system of claim 11, wherein the first communications device and the second communications device are insulated from water.
  • 13. The leak detection system of claim 11, wherein each component of the water infrastructure system includes at least one portion comprised of a material that does not interfere with communications of each communications device.
  • 14. The leak detection system of claim 13, wherein the at least one portion of each component of the water infrastructure system is comprised of a composite material, wherein the composite material does not interfere with wireless signals.
  • 15. The leak detection system of claim 11, wherein each component of the water infrastructure system is a hydrant including a nozzle cap.
  • 16. The leak detection system of claim 11, wherein each communications device is configured to communicate with an operations center, the operations center configured to determine a location of a water leak based on a velocity of a sound traveling along a pipe, a distance between each leak detection sensor, and a delay between times each leak detection sensor detects the sound.
  • 17. The leak detection system of claim 11, wherein the first leak detection sensor is coupled to the first watertight housing.
  • 18. The leak detection system of claim 11, wherein each of the first watertight housing and the second watertight housing defines a cavity, wherein each of the first watertight housing and the second watertight housing comprises a cover sealing the respective cavity of each housing.
  • 19. The leak detection system of claim 11, further comprising a first antenna cover and a second antenna cover, at least a portion of the antenna of the first communications device situated within the first antenna cover, at least a portion of the antenna of the second communications device situated within the second antenna cover.
  • 20. The leak detection system of claim 11, wherein the first component is a first hydrant, wherein the second component is a second hydrant.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/101,235, filed May 5, 2011, which claims priority to U.S. Provisional Application No. 61/355,468 filed Jun. 16, 2010, both of which are hereby specifically incorporated by reference herein in their entireties.

US Referenced Citations (632)
Number Name Date Kind
691904 Hallbergh Jan 1902 A
1165429 Mass Dec 1915 A
1738094 Caldwell Dec 1929 A
1788618 Cover Jan 1931 A
1808209 Earl Jun 1931 A
1808212 Earl Jun 1931 A
2171173 Coyer Aug 1939 A
2302529 Cornell et al. Nov 1942 A
3254528 Michael Jun 1966 A
3254660 Ray Jun 1966 A
3592967 Harris Jul 1971 A
3593957 Dolter et al. Jul 1971 A
3612922 Furnival Oct 1971 A
3653261 Feldman Apr 1972 A
3672233 Hjermstad Jun 1972 A
3673856 Panigati Jul 1972 A
3705385 Batz Dec 1972 A
3731534 Painley et al. May 1973 A
3795144 Marchesi Mar 1974 A
3815129 Sweany Jun 1974 A
4056970 Sollish Nov 1977 A
4083229 Anway Apr 1978 A
4093997 Germer Jun 1978 A
4120031 Kincheloe et al. Oct 1978 A
4126338 Coel Nov 1978 A
4291375 Wolf Sep 1981 A
4333028 Panton Jun 1982 A
4388690 Lumsden Jun 1983 A
4414633 Churchill Nov 1983 A
4431873 Dunn et al. Feb 1984 A
4442492 Karlsson et al. Apr 1984 A
4462249 Adams Jul 1984 A
4465970 DiMassimo et al. Aug 1984 A
4467236 Kolm et al. Aug 1984 A
4516213 Gidden May 1985 A
4542469 Brandberry et al. Sep 1985 A
4543817 Sugiyama Oct 1985 A
4591988 Klima et al. May 1986 A
4707852 Jahr et al. Nov 1987 A
4727900 Dooling et al. Mar 1988 A
4778204 Berger Oct 1988 A
4792946 Mayo Dec 1988 A
4803632 Frew et al. Feb 1989 A
4833618 Verma et al. May 1989 A
4844396 Norton Jul 1989 A
4868566 Strobel et al. Sep 1989 A
4881070 Burrowes et al. Nov 1989 A
4901751 Story et al. Feb 1990 A
4930358 Motegi et al. Jun 1990 A
4940976 Gastouniotis et al. Jul 1990 A
4953403 Springer Sep 1990 A
4967996 Sonoda et al. Nov 1990 A
4984498 Fishman Jan 1991 A
4989830 Ratnik Feb 1991 A
5038614 Bseisu et al. Aug 1991 A
5052215 Lewis Oct 1991 A
5056107 Johnson et al. Oct 1991 A
5075792 Brown et al. Dec 1991 A
5078006 Maresca et al. Jan 1992 A
5079715 Venkataraman et al. Jan 1992 A
5085082 Cantor et al. Feb 1992 A
5090234 Maresca et al. Feb 1992 A
5117676 Chang Jun 1992 A
5118464 Richardson et al. Jun 1992 A
5121344 Laage et al. Jun 1992 A
5163314 Maresca et al. Nov 1992 A
5165280 Sternberg et al. Nov 1992 A
5170657 Maresca et al. Dec 1992 A
5174155 Sugimoto Dec 1992 A
5187973 Kunze et al. Feb 1993 A
5189904 Maresca et al. Mar 1993 A
5201226 John et al. Apr 1993 A
5203202 Spencer Apr 1993 A
5205173 Allen Apr 1993 A
5209125 Kalinoski et al. May 1993 A
5218859 Stenstrom et al. Jun 1993 A
5239575 White et al. Aug 1993 A
5243862 Latimer Sep 1993 A
5251480 Brunson, IV et al. Oct 1993 A
5254944 Holmes et al. Oct 1993 A
5261275 Davis Nov 1993 A
5267587 Brown Dec 1993 A
5272646 Farmer Dec 1993 A
5279160 Koch Jan 1994 A
5287884 Cohen Feb 1994 A
5298894 Cerny et al. Mar 1994 A
5303592 Livingston Apr 1994 A
5319956 Bogle et al. Jun 1994 A
5333501 Okada et al. Aug 1994 A
5335547 Nakajima et al. Aug 1994 A
5343737 Baumoel Sep 1994 A
5349568 Kupperman et al. Sep 1994 A
5351655 Nuspl Oct 1994 A
5361636 Farstad et al. Nov 1994 A
5367911 Jewell et al. Nov 1994 A
5381136 Powers et al. Jan 1995 A
5385049 Hunt et al. Jan 1995 A
5396800 Drinon et al. Mar 1995 A
5408883 Clark, Jr. et al. Apr 1995 A
5416724 Savic May 1995 A
5434911 Gray et al. Jul 1995 A
5437481 Spears et al. Aug 1995 A
5438329 Gastounioulis et al. Aug 1995 A
5451938 Brennan, Jr. Sep 1995 A
5459459 Lee Oct 1995 A
5461906 Bogle et al. Oct 1995 A
5481259 Bane Jan 1996 A
5493287 Bane Feb 1996 A
5509567 Lindahl Apr 1996 A
5519184 Umlas May 1996 A
5519387 Besier et al. May 1996 A
5525898 Lee et al. Jun 1996 A
5526691 Latimer et al. Jun 1996 A
5531099 Russo Jul 1996 A
5548530 Baumoel Aug 1996 A
5553094 Johnson et al. Sep 1996 A
5581037 Kwun et al. Dec 1996 A
5590179 Shincovich et al. Dec 1996 A
5591912 Spisak et al. Jan 1997 A
5594740 LaDue Jan 1997 A
5594776 Dent Jan 1997 A
5602327 Torizuka et al. Feb 1997 A
5611948 Hawkins Mar 1997 A
5617084 Sears Apr 1997 A
5619423 Scrantz Apr 1997 A
5623203 Hosohara et al. Apr 1997 A
5631554 Briese et al. May 1997 A
5633467 Paulson May 1997 A
5639958 Lange Jun 1997 A
5654692 Baxter, Jr. et al. Aug 1997 A
5655299 Lindahl Aug 1997 A
5655561 Wendel et al. Aug 1997 A
5666655 Ishikawa et al. Sep 1997 A
5673252 Johnson et al. Sep 1997 A
5686828 Peterman et al. Nov 1997 A
5708195 Kurisu et al. Jan 1998 A
5708211 Jepson et al. Jan 1998 A
5714931 Petite Feb 1998 A
5746344 Syler et al. May 1998 A
5748104 Argyroudis et al. May 1998 A
5751797 Saadeh May 1998 A
5754101 Tsunetomi et al. May 1998 A
5760306 Wyatt, III et al. Jun 1998 A
5767790 Jovellana Jun 1998 A
5787358 Takahashi Jul 1998 A
5789720 LaGally et al. Aug 1998 A
5798457 Paulson Aug 1998 A
5801643 Williams et al. Sep 1998 A
5815086 Ivie et al. Sep 1998 A
5838633 Sinha Nov 1998 A
5852658 Knight et al. Dec 1998 A
5866820 Camplin et al. Feb 1999 A
5877703 Bloss et al. Mar 1999 A
5892163 Johnson Apr 1999 A
5892441 Woolley et al. Apr 1999 A
5892758 Argyroudis Apr 1999 A
5907100 Cook May 1999 A
5907491 Canada et al. May 1999 A
5924051 Provost et al. Jul 1999 A
5926103 Petite Jul 1999 A
5926531 Petite Jul 1999 A
5940009 Loy et al. Aug 1999 A
5963146 Johnson et al. Oct 1999 A
5963557 Eng Oct 1999 A
5965818 Wang Oct 1999 A
5970434 Brophy et al. Oct 1999 A
5971011 Price Oct 1999 A
5974862 Lander et al. Nov 1999 A
5979863 Lousberg Nov 1999 A
5986573 Franklin et al. Nov 1999 A
5987990 Worthington et al. Nov 1999 A
5994892 Turino et al. Nov 1999 A
5996608 Hunter et al. Dec 1999 A
6000277 Smith Dec 1999 A
6000288 Kwun et al. Dec 1999 A
6003376 Burns et al. Dec 1999 A
6006212 Schleich et al. Dec 1999 A
6023986 Smith et al. Feb 2000 A
6028522 Petite Feb 2000 A
6028855 Hirsch Feb 2000 A
6031455 Grube et al. Feb 2000 A
6031466 Leshets et al. Feb 2000 A
6035717 Carodiskey Mar 2000 A
6044062 Brownrigg et al. Mar 2000 A
6058374 Guthrie et al. May 2000 A
6060994 Chen May 2000 A
6069571 Tell May 2000 A
6076407 Levesque et al. Jun 2000 A
6081204 Lavoie et al. Jun 2000 A
6082193 Paulson Jul 2000 A
6115677 Perthold et al. Sep 2000 A
6125703 MacLauchlan et al. Oct 2000 A
6127823 Atherton Oct 2000 A
6138512 Roberts et al. Oct 2000 A
6138514 Iwamoto et al. Oct 2000 A
6150955 Tracy et al. Nov 2000 A
6152173 Makowan Nov 2000 A
6163276 Irving et al. Dec 2000 A
6164137 Hancock et al. Dec 2000 A
6170334 Paulson Jan 2001 B1
6172616 Johnson et al. Jan 2001 B1
6175380 Van Den Bosch Jan 2001 B1
6178816 Katzman et al. Jan 2001 B1
6192352 Alouani et al. Feb 2001 B1
6195018 Ragle et al. Feb 2001 B1
6208266 Lyons et al. Mar 2001 B1
6218953 Petite Apr 2001 B1
6233327 Petite May 2001 B1
6243657 Tuck et al. Jun 2001 B1
6246677 Nap et al. Jun 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6267000 Harper et al. Jul 2001 B1
6276213 Lee et al. Aug 2001 B1
6288641 Casais Sep 2001 B1
6296066 Terry Oct 2001 B1
6317051 Cohen Nov 2001 B1
6333975 Brunn et al. Dec 2001 B1
6363788 Gorman et al. Apr 2002 B1
6373399 Johnson et al. Apr 2002 B1
6389881 Yang et al. May 2002 B1
6392538 Shere May 2002 B1
6401525 Jamieson Jun 2002 B1
6404343 Andou et al. Jun 2002 B1
6405047 Moon Jun 2002 B1
6424270 Ali Jul 2002 B1
6426027 Scarborough et al. Jul 2002 B1
6430268 Petite Aug 2002 B1
6437692 Petite et al. Aug 2002 B1
6442999 Baumoel Sep 2002 B1
6453247 Hunaidi Sep 2002 B1
6456197 Lauritsen et al. Sep 2002 B1
6470749 Han et al. Oct 2002 B1
6470903 Reyman Oct 2002 B2
6493377 Schilling et al. Dec 2002 B2
6512463 Campbell et al. Jan 2003 B1
6528957 Luchaco Mar 2003 B1
6530263 Chana Mar 2003 B1
6536469 Dilger et al. Mar 2003 B2
6538577 Ehrke et al. Mar 2003 B1
6560543 Wolfe et al. May 2003 B2
6561032 Hunaidi May 2003 B1
6564159 Lavoie et al. May 2003 B1
6567006 Lander et al. May 2003 B1
6568416 Tucker et al. May 2003 B2
6577961 Hubbard et al. Jun 2003 B1
6578422 Lam et al. Jun 2003 B2
6581458 Hathaway et al. Jun 2003 B1
6595038 Williams et al. Jul 2003 B2
6618578 Petite Sep 2003 B1
6618709 Sneeringer Sep 2003 B1
6624628 Kwun et al. Sep 2003 B1
6624750 Marman et al. Sep 2003 B1
6628207 Hemminger et al. Sep 2003 B1
6628764 Petite Sep 2003 B1
6633781 Lee et al. Oct 2003 B1
6647762 Roy Nov 2003 B1
6651503 Bazarov et al. Nov 2003 B2
6653945 Johnson et al. Nov 2003 B2
6657552 Belski et al. Dec 2003 B2
6666095 Thomas et al. Dec 2003 B2
6667709 Hansen et al. Dec 2003 B1
6675071 Griffin, Jr. et al. Jan 2004 B1
6677861 Henry et al. Jan 2004 B1
6701956 Berger Mar 2004 B1
6707762 Goodman et al. Mar 2004 B1
6710600 Kopecki et al. Mar 2004 B1
6710721 Holowick Mar 2004 B1
6725705 Huebler et al. Apr 2004 B1
6734674 Struse May 2004 B1
6745136 Lam et al. Jun 2004 B2
6747557 Petite et al. Jun 2004 B1
6751560 Tingley et al. Jun 2004 B1
6772636 Lam et al. Aug 2004 B2
6772637 Bazarov et al. Aug 2004 B2
6772638 Matney et al. Aug 2004 B2
6781369 Paulson et al. Aug 2004 B2
6782751 Linares et al. Aug 2004 B2
6789427 Batzinger et al. Sep 2004 B2
6791318 Paulson et al. Sep 2004 B2
6798352 Holowick Sep 2004 B2
6799466 Chinn Oct 2004 B2
6813949 Masaniello et al. Nov 2004 B2
6813950 Glascock et al. Nov 2004 B2
6816072 Zoratti Nov 2004 B2
6820016 Brown et al. Nov 2004 B2
6822742 Kalayeh et al. Nov 2004 B1
6836737 Petite et al. Dec 2004 B2
6843131 Graff et al. Jan 2005 B2
6847300 Yee et al. Jan 2005 B2
6848303 Oeder et al. Feb 2005 B2
6848313 Krieg et al. Feb 2005 B2
6851319 Ziola et al. Feb 2005 B2
6880567 Klaver et al. Apr 2005 B2
6889703 Bond May 2005 B2
6891838 Petite et al. May 2005 B1
6904818 Harthorn et al. Jun 2005 B2
6912472 Mizushina Jun 2005 B2
6914533 Petite Jul 2005 B2
6914893 Petite Jul 2005 B2
6920792 Flora et al. Jul 2005 B2
6931445 Davis Aug 2005 B2
6931931 Graff et al. Aug 2005 B2
6935178 Prause Aug 2005 B2
6945113 Siverling et al. Sep 2005 B2
6946972 Mueller et al. Sep 2005 B2
6952970 Furmidge et al. Oct 2005 B1
6954701 Wolfe Oct 2005 B2
6954814 Leach Oct 2005 B1
6957157 Lander Oct 2005 B2
6968727 Kwun et al. Nov 2005 B2
6972677 Coulthard Dec 2005 B2
6978210 Suter et al. Dec 2005 B1
6978832 Gardner et al. Dec 2005 B2
6980079 Shintani et al. Dec 2005 B1
6982651 Fischer Jan 2006 B2
7008239 Ju Mar 2006 B1
7009530 Zigdon et al. Mar 2006 B2
7012546 Zigdon et al. Mar 2006 B1
7042368 Patterson et al. May 2006 B2
7051577 Komninos May 2006 B2
7053767 Petite et al. May 2006 B2
7054271 Brownrigg May 2006 B2
7061924 Durrant et al. Jun 2006 B1
7072945 Nieminen Jul 2006 B1
7079810 Petite et al. Jul 2006 B2
7080557 Adnan Jul 2006 B2
7088239 Basinger et al. Aug 2006 B2
7089125 Sonderegger Aug 2006 B2
7099781 Heidl et al. Aug 2006 B1
7103511 Petite Sep 2006 B2
7111516 Bazarov et al. Sep 2006 B2
7111817 Teti et al. Sep 2006 B2
7117051 Landry et al. Oct 2006 B2
7123628 Hwang Oct 2006 B1
7124184 Chung et al. Oct 2006 B2
7137550 Petite Nov 2006 B1
7140253 Merki et al. Nov 2006 B2
7142107 Kates Nov 2006 B2
7143645 Benson et al. Dec 2006 B2
7143659 Stout et al. Dec 2006 B2
7171854 Nagashima et al. Feb 2007 B2
7228726 Kates Jun 2007 B2
7231331 Davis Jun 2007 B2
7234355 Dewangan et al. Jun 2007 B2
7240574 Sapelnikov Jul 2007 B2
7248179 Smit Jul 2007 B2
7248181 Patterson et al. Jul 2007 B2
7250874 Mueller et al. Jul 2007 B2
7255007 Messer et al. Aug 2007 B2
7256704 Yoon et al. Aug 2007 B2
7261002 Gysling et al. Aug 2007 B1
7263073 Petite et al. Aug 2007 B2
7266992 Shamout et al. Sep 2007 B2
7267014 Winter Sep 2007 B2
7272635 Longtin et al. Sep 2007 B1
7274996 Lapinski Sep 2007 B2
7284433 Ales et al. Oct 2007 B2
7292143 Drake et al. Nov 2007 B2
7293461 Girndt Nov 2007 B1
7295128 Petite Nov 2007 B2
7299697 Siddu et al. Nov 2007 B2
7301456 Han Nov 2007 B2
7304587 Boaz Dec 2007 B2
7310877 Cao et al. Dec 2007 B2
7315257 Patterson et al. Jan 2008 B2
7328618 Hunaidi et al. Feb 2008 B2
7331215 Bond Feb 2008 B2
7342504 Crane et al. Mar 2008 B2
7346030 Cornwall Mar 2008 B2
7349766 Rodgers Mar 2008 B2
7353280 Chiles et al. Apr 2008 B2
7356444 Blemel Apr 2008 B2
7356614 Kim et al. Apr 2008 B2
7360462 Nozaki et al. Apr 2008 B2
7363031 Aisa Apr 2008 B1
7373808 Zanker et al. May 2008 B2
7380466 Deeg Jun 2008 B2
7383721 Parsons et al. Jun 2008 B2
7385524 Orlosky Jun 2008 B1
7392709 Eckert Jul 2008 B2
7397907 Petite Jul 2008 B2
7405391 Ogisu et al. Jul 2008 B2
7412882 Lazar et al. Aug 2008 B2
7412890 Johnson et al. Aug 2008 B1
7414395 Gao et al. Aug 2008 B2
7417557 Osterloh et al. Aug 2008 B2
7423985 Hill Sep 2008 B1
7424527 Petite Sep 2008 B2
7426879 Nozaki et al. Sep 2008 B2
7443313 Davis et al. Oct 2008 B2
7444401 Keyghobad et al. Oct 2008 B1
7453373 Cumeralto et al. Nov 2008 B2
D583692 Ball et al. Dec 2008 S
7458267 McCoy Dec 2008 B2
7468661 Petite et al. Dec 2008 B2
7475596 Hunaidi et al. Jan 2009 B2
7478108 Townsend et al. Jan 2009 B2
7480501 Petite Jan 2009 B2
7493817 Germata Feb 2009 B2
7523666 Thompson et al. Apr 2009 B2
7526539 Hsu Apr 2009 B1
7526944 Sabata et al. May 2009 B2
7530270 Nozaki et al. May 2009 B2
7533693 Colton et al. May 2009 B2
7543500 Litzenberg et al. Jun 2009 B2
7549439 Kimura et al. Jun 2009 B2
7554345 Vokey Jun 2009 B2
7564540 Paulson Jul 2009 B2
7587942 Smith et al. Sep 2009 B2
7590496 Blemel Sep 2009 B2
7596458 Lander Sep 2009 B2
7604216 Gebler Oct 2009 B2
7607351 Allison et al. Oct 2009 B2
7623427 Jann et al. Nov 2009 B2
7647829 Junker et al. Jan 2010 B2
7650425 Davis Jan 2010 B2
7650790 Wright Jan 2010 B2
7657403 Stripf et al. Feb 2010 B2
7668670 Lander Feb 2010 B2
7671480 Pitchford et al. Mar 2010 B2
7680625 Trowbridge et al. Mar 2010 B2
7690258 Minagi et al. Apr 2010 B2
7690393 Nagle et al. Apr 2010 B2
7694564 Brignac et al. Apr 2010 B2
7694934 Irwin Apr 2010 B2
7696940 MacDonald Apr 2010 B1
7697492 Petite Apr 2010 B2
7711217 Takahashi et al. May 2010 B2
7739378 Petite Jun 2010 B2
7740024 Brodeur et al. Jun 2010 B2
7746246 Salser Jun 2010 B2
7751989 Owens et al. Jul 2010 B2
7752309 Keyghobad et al. Jul 2010 B2
7756086 Petite Jul 2010 B2
7760703 Kubler et al. Jul 2010 B2
7775422 Winter et al. Aug 2010 B2
7783738 Keyghobad et al. Aug 2010 B2
7792946 Keyghobad et al. Sep 2010 B2
7806382 Palumbo et al. Oct 2010 B1
7810378 Hunaidi et al. Oct 2010 B2
7817063 Hawkins et al. Oct 2010 B2
7825793 Spillman et al. Nov 2010 B1
7843379 Menzer et al. Nov 2010 B2
7854165 Ball Dec 2010 B2
7870080 Budike, Jr. Jan 2011 B2
7880641 Parris et al. Feb 2011 B2
7962101 Vaswani et al. Jun 2011 B2
7980317 Preta et al. Jul 2011 B1
8014791 Guigne et al. Sep 2011 B2
8047072 Ball Nov 2011 B2
8109131 Winter Feb 2012 B2
8140667 Keyghobad et al. Mar 2012 B2
8249042 Sparr et al. Aug 2012 B2
8281654 Ball Oct 2012 B2
8300626 Thubert et al. Oct 2012 B2
8319508 Vokey Nov 2012 B2
8351409 Albert et al. Jan 2013 B2
8391177 Picard Mar 2013 B2
8407333 Keyghobad Mar 2013 B2
8549131 Keyghobad et al. Oct 2013 B2
8660134 Splitz Feb 2014 B2
8674830 Lanham et al. Mar 2014 B2
8823509 Hyland Sep 2014 B2
8833390 Ball et al. Sep 2014 B2
8855569 Splitz Oct 2014 B2
8931337 Renoud Jan 2015 B2
8931505 Hyland et al. Jan 2015 B2
9202362 Hyland Dec 2015 B2
9291520 Fleury, Jr. et al. Mar 2016 B2
9593999 Fleury Mar 2017 B2
9772250 Richarz et al. Sep 2017 B2
20010010032 Ehlers et al. Jul 2001 A1
20010013488 Fukunaga et al. Aug 2001 A1
20010024163 Petite Sep 2001 A1
20010045129 Williams et al. Nov 2001 A1
20010048030 Sharood et al. Dec 2001 A1
20020013679 Petite Jan 2002 A1
20020019725 Petite Feb 2002 A1
20020031101 Petite Mar 2002 A1
20020043549 Taylor et al. Apr 2002 A1
20020051546 Bizjak May 2002 A1
20020062392 Nishikawa et al. May 2002 A1
20020067717 Raschke et al. Jun 2002 A1
20020073183 Yoon et al. Jun 2002 A1
20020089802 Beckwith Jul 2002 A1
20020124633 Yang Sep 2002 A1
20020130768 Che et al. Sep 2002 A1
20020159434 Gosior et al. Oct 2002 A1
20020159584 Sindalovsky et al. Oct 2002 A1
20020169643 Petite et al. Nov 2002 A1
20020190956 Klein et al. Dec 2002 A1
20030009515 Lee et al. Jan 2003 A1
20030018733 Yoon et al. Jan 2003 A1
20030018776 Yoon et al. Jan 2003 A1
20030034900 Han Feb 2003 A1
20030036810 Petite Feb 2003 A1
20030046377 Daum et al. Mar 2003 A1
20030074109 Jeong et al. Apr 2003 A1
20030076241 Middleton Apr 2003 A1
20030093484 Petite May 2003 A1
20030107485 Zoratti Jun 2003 A1
20030174070 Garrod et al. Sep 2003 A1
20040010561 Kim et al. Jan 2004 A1
20040054747 Breh et al. Mar 2004 A1
20040129312 Cuzzo et al. Jul 2004 A1
20040139210 Lee et al. Jul 2004 A1
20040158333 Ha et al. Aug 2004 A1
20040183687 Petite et al. Sep 2004 A1
20050005680 Anderson Jan 2005 A1
20050067022 Istre Mar 2005 A1
20050072214 Cooper Apr 2005 A1
20050078631 Cornwall Apr 2005 A1
20050084418 Hill et al. Apr 2005 A1
20050096753 Arling et al. May 2005 A1
20050104747 Silic et al. May 2005 A1
20050121880 Santangelo Jun 2005 A1
20050159823 Hayes et al. Jul 2005 A1
20050190784 Stine Sep 2005 A1
20050195768 Petite et al. Sep 2005 A1
20050195775 Petite et al. Sep 2005 A1
20050201379 Zhang et al. Sep 2005 A1
20050201397 Petite Sep 2005 A1
20050203647 Landry et al. Sep 2005 A1
20050246295 Cameron Nov 2005 A1
20050251367 Kahn et al. Nov 2005 A1
20050279169 Lander Dec 2005 A1
20060012491 Mahowald Jan 2006 A1
20060028355 Patterson et al. Feb 2006 A1
20060041655 Holloway et al. Feb 2006 A1
20060046664 Paradiso et al. Mar 2006 A1
20060098576 Brownrigg et al. May 2006 A1
20060158347 Roche et al. Jul 2006 A1
20060174707 Zhang Aug 2006 A1
20060181414 Bandy et al. Aug 2006 A1
20060201550 Blyth et al. Sep 2006 A1
20060218266 Matsumoto et al. Sep 2006 A1
20060273896 Kates Dec 2006 A1
20060283251 Hunaidi Dec 2006 A1
20060284784 Smith et al. Dec 2006 A1
20070051187 McDearmon Mar 2007 A1
20070059986 Rockwell Mar 2007 A1
20070063866 Webb Mar 2007 A1
20070091825 Budampati et al. Apr 2007 A1
20070113618 Yokoi et al. May 2007 A1
20070130317 Lander Jun 2007 A1
20070284293 Pitchford et al. Dec 2007 A1
20070293221 Hwang et al. Dec 2007 A1
20070298779 Wolman et al. Dec 2007 A1
20080030319 McKenna et al. Feb 2008 A1
20080043637 Rahman Feb 2008 A1
20080061769 Junk et al. Mar 2008 A1
20080078567 Miller et al. Apr 2008 A1
20080084260 Swartzentruber et al. Apr 2008 A1
20080086560 Monier et al. Apr 2008 A1
20080095403 Benhammou Apr 2008 A1
20080109090 Esmaili et al. May 2008 A1
20080149180 Parris et al. Jun 2008 A1
20080150750 Parris Jun 2008 A1
20080169910 Greene et al. Jul 2008 A1
20080186898 Petite Aug 2008 A1
20080189056 Heidl et al. Aug 2008 A1
20080195329 Prince et al. Aug 2008 A1
20080240078 Thubert Oct 2008 A1
20080281534 Hurley Nov 2008 A1
20080291054 Groft Nov 2008 A1
20080307623 Furukawa Dec 2008 A1
20080314122 Hunaidi et al. Dec 2008 A1
20090044628 Lotscher Feb 2009 A1
20090058676 Orlosky Mar 2009 A1
20090066524 Yukawa et al. Mar 2009 A1
20090068947 Petite Mar 2009 A1
20090121860 Kimmel et al. May 2009 A1
20090133887 Garcia et al. May 2009 A1
20090153357 Bushman et al. Jun 2009 A1
20090182099 Noro et al. Jul 2009 A1
20090188313 Ball Jul 2009 A1
20090214941 Buck et al. Aug 2009 A1
20090215424 Petite Aug 2009 A1
20090243840 Petite et al. Oct 2009 A1
20090255346 Hendey et al. Oct 2009 A1
20090271045 Savelle et al. Oct 2009 A1
20090278293 Yoshinaka et al. Nov 2009 A1
20090287838 Keyghobad et al. Nov 2009 A1
20090301571 Ruhs Dec 2009 A1
20090309755 Williamson et al. Dec 2009 A1
20090322453 Kawaguchi Dec 2009 A1
20100017465 Brownrigg et al. Jan 2010 A1
20100039984 Brownrigg Feb 2010 A1
20100060479 Salter Mar 2010 A1
20100077234 Das Mar 2010 A1
20100156632 Hyland et al. Jun 2010 A1
20100194582 Petite Aug 2010 A1
20100250054 Petite Sep 2010 A1
20100265909 Petite et al. Oct 2010 A1
20100290201 Takeuchi et al. Nov 2010 A1
20100295672 Hyland et al. Nov 2010 A1
20100312881 Davis et al. Dec 2010 A1
20100329232 Tubb et al. Dec 2010 A1
20110018762 Walley et al. Jan 2011 A1
20110030482 Meeusen et al. Feb 2011 A1
20110044276 Albert et al. Feb 2011 A1
20110063172 Podduturi Mar 2011 A1
20110079402 Darby et al. Apr 2011 A1
20110108136 Margalit et al. May 2011 A1
20110140909 Olson et al. Jun 2011 A1
20110308638 Hyland et al. Dec 2011 A1
20120007743 Solomon Jan 2012 A1
20120007744 Pal Jan 2012 A1
20120068476 Bradfield Mar 2012 A1
20120068477 Bradfield Mar 2012 A1
20120106518 Albert et al. May 2012 A1
20120169560 Lee et al. Jul 2012 A1
20120271686 Silverman Oct 2012 A1
20120296580 Barkay Nov 2012 A1
20120305084 Ball Dec 2012 A1
20130036796 Fleury Feb 2013 A1
20130041601 Dintakurti et al. Feb 2013 A1
20130049968 Fleury, Jr. et al. Feb 2013 A1
20130083722 Bhargava et al. Apr 2013 A1
20130094537 Hui et al. Apr 2013 A1
20130107772 Splitz et al. May 2013 A1
20130109319 Splitz et al. May 2013 A1
20130145826 Richarz et al. Jun 2013 A1
20130181848 Picard Jul 2013 A1
20130214883 Yano Aug 2013 A1
20130321231 Flores-Cuadras Dec 2013 A1
20160001114 Hyland Jan 2016 A1
20160013565 Ortiz Jan 2016 A1
20160018283 Fleury Jan 2016 A1
20170121949 Fleury May 2017 A1
20170237158 Gibson Aug 2017 A1
20170237165 Ortiz et al. Aug 2017 A1
Foreign Referenced Citations (70)
Number Date Country
2009308949 May 2010 AU
2010249499 May 2015 AU
2011265675 May 2015 AU
2014259545 Nov 2015 AU
2154433 Jan 1997 CA
2476119 Feb 2005 CA
2397174 Aug 2008 CA
2650174 Jul 2012 CA
2634739 Jun 2015 CA
DE 19757581 Jul 1998 CH
1185838 Jun 1998 CN
4211038 Oct 1993 DE
0711986 May 1996 EP
1052492 Nov 2000 EP
1077370 Feb 2001 EP
1077371 Feb 2001 EP
2439990 May 1980 FR
2250820 Jun 1992 GB
2269900 Feb 1994 GB
2305333 Apr 1997 GB
2367362 Apr 2002 GB
2421311 Jun 2006 GB
59170739 Sep 1984 JP
60111132 Jun 1985 JP
62-295674 Dec 1987 JP
05-253316 Oct 1993 JP
06-223279 Aug 1994 JP
6300606 Oct 1994 JP
07231363 Oct 1994 JP
07-116285 May 1995 JP
08250777 Sep 1996 JP
H10-2744 Jan 1998 JP
H102744 Jan 1998 JP
11-046254 Feb 1999 JP
11201859 Jul 1999 JP
H11210028 Aug 1999 JP
2000131179 May 2000 JP
2000285356 Oct 2000 JP
2002206965 Jul 2002 JP
2002310840 Oct 2002 JP
2002352361 Dec 2002 JP
2005315663 Nov 2005 JP
2005321935 Nov 2005 JP
2006062414 Mar 2006 JP
2006062716 Mar 2006 JP
2006285645 Oct 2006 JP
2007047139 Feb 2007 JP
2008198044 Aug 2008 JP
2010068017 Mar 2010 JP
2012507090 Mar 2012 JP
2012527706 Nov 2012 JP
2013528732 Jul 2013 JP
H5654124 Nov 2014 JP
9810299 Mar 1998 WO
9810394 Mar 1998 WO
9850771 Nov 1998 WO
0151904 Jul 2001 WO
2008087911 Jul 2008 WO
2009057214 May 2009 WO
2010051287 May 2010 WO
2010135587 Nov 2010 WO
2011021039 Feb 2011 WO
2011058561 May 2011 WO
2011159403 Dec 2011 WO
2012000088 Jan 2012 WO
2012153147 Nov 2012 WO
2013025526 Feb 2013 WO
2014016625 Jan 2014 WO
2017139029 Aug 2017 WO
2017139030 Aug 2017 WO
Non-Patent Literature Citations (281)
Entry
Ball, Marty Scott, Notice of Allowance for U.S. Appl. No. 12/326,240, filed Jan. 20, 2009, dated Aug. 9, 2010, 10 pgs.
Ball, Marty Scott; Issue Notification for U.S. Appl. No. 12/356,240, filed Jan. 20, 2009, dated Dec. 1, 2010; 1 pg.
Ball, Marty Scott; U.S. Patent Application Entitled: Plastic Water Metwr With Metal Threads under U.S. Appl. No. 12/356,240, filed Jan. 20, 2009; 17 pgs.
Ball, Marty Scott; Issue Notification for U.S. Appl. No. 12/947,272, filed Nov. 16, 2010, dated Oct. 12, 2011; 1 pg.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 12/947,272, filed Nov. 16, 2010, dated May 2, 2011; 11 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 12/947,272, filed Nov. 16, 2010, dated Aug. 10, 2011; 5 pgs.
Ball, Marty Scott; U.S. Patent Application Entitled: Plastic Water Meter With Metal Threads under U.S. Appl. No. 12/947,272, filed Nov. 16, 2010; 15 pgs.
Ball, Marty Scott, Notice of Allowance for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated May 7, 2012; 10 pgs.
Ball, Marty Scott; Issue Notification for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated Sep. 19, 2012; 1 pg.
Ball, Marty Scott; Miscellaneous Communication to Applicant for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated Jun. 14, 2012; 4 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated Feb. 17, 2012; 5 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated Aug. 23, 2012; 9 pgs.
Ball, Marty Scott; U.S. Patent Application Entitled: Plastic Water Meter With Metal Threads; under U.S. Appl. No. 13/220,739, filed Aug. 30, 2011; 14 pgs.
Ball; Non-Final Office Action for U.S. Appl. No. 13/220,739, filed Aug. 30, 2011, dated Nov. 15, 2011, 7 pgs.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 13/646,892, filed Oct. 8, 2012, dated Jun. 7, 2013; 10 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 13/646,892, filed Oct. 8, 2012, dated Sep. 17, 2013, 6 pgs.
Ball, Marty Scott; U.S. Continuation Application entitled: Non-Metallic Enclusure With Metal Threads, U.S. Appl. No. 13/646,892, filed Oct. 8, 2012, 14 pgs.
Hyland, Gregory E.; Issue Notification for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Nov. 11, 2015, 1 pg.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Oct. 13, 2015, 4 pgs.
Hyland, Gregory E.; U.S. Continuation Application entitled: Infrastructure Monitoring System and Method having U.S. Appl. No. 14/928,725, filed Oct. 30, 2015, 28 pgs.
Ball, Marty Scott, Office Action from Canadian Intellectual Property Office for U.S. Pat. No. 2,650,174, filed Jan. 19, 2009, dated Sep. 8, 2011, 3 pgs.
Ball, Marty Scott, Office Action from Canadian Intellectual Property Office for U.S. Pat. No. 2,650,174, filed Jan. 19, 2009, dated Dec. 7, 2010; 2 pages.
Ball, Marty Scott; Canadian Office Action for U.S. Pat. No. 2,777,585, filed Jan. 19, 2009, dated Oct. 21, 2013, 2 pgs.
Hyland, Gregory E.; Australian Patent Examination report for serial No. 2015202223, filed May 20, 2010, dated Nov. 4, 2015, 4 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2014-234642, filed May 5, 2011, dated Nov. 4, 2015,9 pgs.
Ball, Marty Scott; U.S. Provisional Patent Application Entitled: Plastic Water Meter, under U.S. Appl. No. 61/022,088, filed Jan. 18, 2008, 10 pgs.
McCraven, Jeremy; Non-Final Office Action for U.S. Appl. No. 14/273,823, filed May 9, 2014, dated Dec. 8, 2015, 18 pgs.
McCraven, Jeremy; U.S. Patent Application Entitled: Mechanical Stop for Actuator and Orifice, U.S. Appl. No. 14/273,823, filed May 9, 2014, 40 pgs.
Dukes, Brent; International Search Report and Written Opinion for application No. PCT/US15/44140, filed Aug. 7, 2015, dated Dec. 30, 2015, 15 pgs.
Article entitled, “GF Piping Systems' New Metal-to-Plastic Transition Fittings Provide Strong, Leak-Proof Seals”, Nov. 13, 2007, pp. 1-6; http://news.thomasnet.com/fullstory/536342.
Brochure entitled, “DoubleSafe tm Transition Fillings from GF Piping Systems” Georg Fischer Piping Systems; date unknown when published: accessed on Oct. 1, 2008; pp. 1-2 http://www.us.piping.georgefischer.com/go/F017C7DA19993E1D340739AFBC4B677E?action=GF—Docu.
Brochure entitled, “Polyrac and Polyfast”, date unknown when published; accessed on Jun. 1, 2009; pp. 1-8; http://www.cn.piping.georgfischer.com/doc/doc—download.cfm?B81010EAD60EB5F06E54F6B04231161F.
Brochure entitled, “Section 1, Schedule 80 PVC Piping System,” Mar. 27, 2006, pp. 1.1-1.32; http://web.archive.org/web/20060816045129/http://www.gfpiping.com/downloads/vinyls/01-Sch80PVC.pdf.
Brochure entitled, “Section 2, Schedule 80 CPVC Piping System,” Mar. 27, 2006, pp. 2.1-2.28; http://web.archive.org/web/20060816045129/http://www.gfpiping.com/downloads/vinyls/02-Sch80CPVC.pdf.
Brochure entitled, “The World Needs Solutions, We Have Them!,” date unknown when published' accessed on Oct. 1, 2008; pp. 1-12; http://www.plasticsystems.co.nz/booklets/Civil%20Infrastructure/+GF+%20Utilities%20Brochure.pdf.
Brochure entitled, “Transition Fittings, Strong and Reliable Metal-to-Plastic Transitions”, BR-2-0305; date unknown when published; accessed on Oct. 1, 2008; pp. 1-2 http://plascowelding.com/pdf2007/PVC&CPVCPipeandFittings/Thermoplastic-Fittings/PVC&CPVC-Metal.
Hyland, Gregory E.; Canadian Office Action for serial No. 2,741,843, filed Oct. 27, 2009, dated Dec. 8, 2015, 5 pgs.
Hyland, Gregory E.; Issue Notification for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Dec. 23, 2014, 1 pg.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Apr. 16, 2015, 47 pgs.
Ball, Marty Scott; Mexico Office Action for serial No. MX/a/2012/00609, filed May 25, 2012, dated Mar. 19, 2015, 3 pgs.
Splitz, David Edwin; Extended European Search Report for serial No. 12844451.0, filed Jan. 20, 2012, dated Apr. 21, 2015, 8 pgs.
Ball, Marty Scott; Mexico Office Action for serial No. MX/a/2012/00609, filed May 25, 2012, dated May 26, 2015, 5 pgs.
Hyland, Gregory E.; Australian Examination Report for serial No. 2014259545, filed Oct. 27, 2009, dated Jun. 10, 2015; 2 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2014-234642, filed May 5, 2011, dated Jul. 7, 2015, 9 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Jul. 27, 2015, 19 pgs.
Hyland, Gregory; U.S. Continuation Application entitled: Infrastructure Monitoring Devices, Systems, and Methods having U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, 29 pgs.
Dukes, Brent; PCT Application entitled: Dunamic Ruoting in a Mesh Network having serial No. PCT/US15/44140, filed Aug. 7, 2015, 41 pgs.
Hyland, Gregory; Japanese Office Action for serial No. 2012-512048, filed May 20, 2010, dated Oct. 22, 2013, 51 pgs.
Hyland, Gregory; Decision of Rejection for Japanese serial No. 2012-512048, filed May 20, 2010, dated Apr. 22, 2014, 10 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Dec. 19, 2012, dated Jun. 13, 2013, 4 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Dec. 19, 2012, dated Oct. 3, 2013, 8 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Dec. 19, 2012, dated Dec. 3, 2013, received by foreign associate on Jan. 9, 2014, 4 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US2011/035374, filed May 5, 2011, dated Sep. 13, 2011; 7 pgs.
Hyland; PCT Application Entitled: Infrastructure Monitoring Devices, Systems, and Methods having serial No. PCT/US11/35374, filed May 5, 2011, 28 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2011/035374, filed May 5, 2011, dated Dec. 19, 2012; 5 pgs.
Hyland, Gregory E.; Australian Patent Examination Report for serial No. 2011265675, filed Jan. 21, 2012, dated Oct. 1, 2014, 3 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2013515338, filed Jan. 30, 2012, dated Jun. 10, 2014, 8 pgs.
Hyland; U.S. Provisional Patent Application entitled: Water Supply Infrastructure Monitoring System and Method, having U.S. Appl. No. 61/108,770, filed Oct. 27, 2008, 11 pgs.
Hyland; U.S. Provisional Patent Application entitled: Water Supply Infrastructure Monitoring System and Method, having U.S. Appl. No. 61/180,600, filed May 22, 2009, 14 pgs.
Hyland; U.S. Provisional Patent Application entitled: Infrastructure Monitoring Devices, Systems, and Methods, having U.S. Appl. No. 61/355,468, filed Jun. 16, 2010; 31 pgs.
Splitz, David. E.; U.S. Patent Application Entitled: Systems and Methods for Time-Based Hailing of Radio Frequency Devices assigned U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, 51 pages.
Splitz, David Edwin; Non-Final Office Action for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, dated Jun. 18, 2013, 67 pgs.
Splitz, David Edwin; Notice of Allowance for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, dated Oct. 9, 2013, 16 pgs.
Splitz, David Edwin; Issue Notification for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, dated Feb. 5, 2014, 1 pg.
Splitz, David E.; U.S. Patent Application Entitled: Systems and Methods for Dynamic Squelching in Radio Frequency Devices assigned U.S. Appl. No. 13/339,655, filed Dec. 29, 2011; 50 pgs.
Splitz, David Edwin; Non-Final Office Action for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, dated Sep. 16, 2013, 57 pgs.
Splitz, David Edwin; Non-Final Office Action for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, dated Mar. 5, 2014, 18 pgs.
Splitz, David Edwin; Notice of Allowance for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, dated May 23, 2014, 41 pgs.
Splitz, David Edwin; Issue Notification for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, dated Sep. 17, 2014, 1 pg.
Splitz, David Edwin; U.S. Patent Application entitled: Systems and Methods for Recovering an Out-of-Service Node in a Hierarchical Network, U.S. Appl. No. 14/490,081, filed Sep. 18, 2014, 51 pgs.
Dukes, Brent; U.S. Application entitled: Dynamic Routing in a Mesh Network, having U.S. Appl. No. 14/475,050, filed Sep. 2, 2014, 42 pgs.
Splitz, David; International Search Report and Written Opinion for serial No. PCT/US11/58260, filed Oct. 28, 2011, dated Feb. 7, 2012, 8 pgs.
Splitz, David; PCT Application entitled: Systems and Methods for Time-Based Hailing of Radio Frequency having serial No. PCT/US11/058260, filed Oct. 28, 2011, 51 pgs.
Splitz, David; International Preliminary Report on Patentability for serial No. PCT/US11/58260, filed Oct. 28, 2011, dated May 8, 2014, 7 pgs.
Splitz, David; International Search Report and Written Opinion for serial No. PCT/US12/22060, filed Jan. 20, 2012, dated Mar. 29, 2012, 8 pgs.
Splitz, David; PCT Application entitled: Systems and Methods for Dynamic Squelching in Radio Frequency Devices having serial No. PCT/US12/022060, filed Jan. 20, 2012, 50 pgs.
Splitz, David; International Preliminary Report on Patentability for serial No. PCT/US12/22060, filed Jan. 20, 2012, dated May 8, 2014, 6 pgs.
Splitz, David Edwin; U.S. Provisional Patent Application entitled: Automatic Discovery of Nodes in a Mesh Network, U.S. Appl. No. 61/779,892, filed Mar. 13, 2013; 110 pgs.
Ball, Marty Scott; Issue Notification for U.S. Appl. No. 13/149,720, filed May 31, 2011, dated Aug. 27, 2014, 1 pg.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 13/149,720, filed May 31, 2011, dated Mar. 11, 2014, 75 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 13/149,720, filed May 31, 2011, dated Jun. 24, 2014, 29 pgs.
Ball, Marty Scott; Supplemental Notice of Allowability for U.S. Appl. No. 13/149,720, filed May 31, 2011, dated Aug. 12, 2014, 4 pgs.
Ball, Marty Scott; U.S. Patent Application Entitled: Valve Meter Assembly and Method under U.S. Appl. No. 13/149,720, filed May 31, 2011; 56 pgs.
Ball, Marty Scott; U.S. Patent Application Entitled: Valve Meter Assembly and Method, U.S. Appl. No. 14/451,896, filed Aug. 5, 2014; 56 pgs.
Hyland, Gregory E.; Applicant Initiated Interview Summary for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Feb. 18, 2014, 4 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Dec. 17, 2013, 54 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Apr. 10, 2013, 80 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Sep. 22, 2014, 49 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Oct. 18, 2012; 44 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Apr. 8, 2014, 43 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, dated Sep. 6, 2013; 53 pgs.
Hyland; U.S. Patent Application entitled: Infrastructure Monitoring System and Method, having U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, 30 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Feb. 11, 2014; 44 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated May 29, 2013, 71 pgs.
Hyland, Gregory E.; Issue Notification for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Aug. 13, 2014. 1 pg.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Sep. 10, 2012, 35 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Sep. 24, 2013; 37 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Apr. 23, 2014, 20 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 12/784,300, filed May 20, 2010, dated Aug. 1, 2014, 4 pgs.
Hyland; U.S. Application entitled: Infrastructure Monitoring Devices, Systems, and Methods, having U.S. Appl. No. 12/784,300, filed May 20, 2010, 32 pgs.
Hyland, Gregory E.; U.S. Continuation Application entitled: Infrastructure Monitoring Devices, Systems, and Methods, having U.S. Appl. No. 14/450,452, filed Aug. 4, 2014, 32 pgs.
Keyghobad, Seyamak; Requirement for Restriction/ Election for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Feb. 9, 2006; 11 pages.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/243,452, filed Oct. 1, 2008 dated Jun. 16, 2010; 1 pg.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, dated Feb. 29, 2012; 1 pg.
Keyghobad, Seyamak; Non Final Rejection for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, dated Mar. 21, 2011; 9 pgs.
Keyghobad, Seyamak; Non Final Rejection for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, dated Oct. 4, 2010; 13 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,867, filed Jun. 24, 2006, dated Sep. 7, 2011; 6 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, dated Nov. 2, 2011; 17 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,867, filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009; dated Aug. 18, 2010; 1 pg.
Keyghobad, Seyamak; Non-final office action for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009; dated Dec. 23, 2009; 17 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009, dated Aug. 2, 2010, 8 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,957, filed Jun. 24, 2009; dated Aug. 4, 2010; 1 pg.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,957, filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012, dated Mar. 6, 2013, 1 pg.
Keyghobad, Seyamak; Non-final Office Action for U.S. Appl. No. 13/372,408, filed Feb. 23, 2012; dated May 25, 2012; 17 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012, dated Jul. 27, 2012; 11 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; dated Nov. 1, 2012; 18 pgs.
Keyghobad, Seyamak; Supplemental Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; dated Aug. 2, 2012; 7 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 10/298,300, filed Nov. 18, 2002, dated Oct. 8, 2008; 1 pg.
Keyghobad, Seyamak, Issue Notification for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, dated Sep. 11, 2013, 1 pg.
Keyghobad, Seyamak; Non-Final Office Action for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, dated Dec. 13, 2012; 39 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, dated Mar. 21, 2013, 22 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, dated Jul. 9, 2013, 21 pgs.
Keyghobad, Seyamak; U.S. Patent Application entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, 35 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; 34 pgs.
Hyland, Gregory E., Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Jul. 31, 2013; 57 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Feb. 20, 2014; 29 pgs.
Vonroll Hydro—Hydrojournal, pp. 1-16, May 2008.
English Translation: Vonroll Hydro—Hyrdojournal, Technology with a Future for Shut-off Systems—p. 4, VonRoll Hydro (shop) GmbH—New Concepts for Apprentice Training—p. 12, May 2008.
Von Roll Hydro—Hydrojournal, pp. 1-16, Nov. 2008.
English Translation: Von Roll Hydro—Hyrdojournal,VonRoll Hydroalert—Provides a Warning in the Event of Any Tampering with the Water Supply, p. 3, Nov. 2008.
Keyghobad, Seyamak; Examiner Interview Summary Record for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Feb. 5, 2008; 2 pages.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Oct. 26, 2007; 35 pages.
Keyghobad, Seyamak; Requirement for Restriction/ Election for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Feb. 27, 2006; 17 pages.
Keyghobad,Seyamak; U.S. Patent Application entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; 40 pages.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated May 18, 2006; 13 pages.
Keyghobad, Seyamak; Non-Final Rejection or U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Jun. 6, 2007; 32 pages.
Keyghobad, Seyamak; Certificate of Correction for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Mar. 31, 2009; 1 page.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; dated Jul. 14, 2008; 4 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; dated Mar. 22, 2010; 8 pages.
Keyghobad, Seyamak; Examiner Interview Summary Record for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; dated Dec. 7, 2009; 3 pages.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; dated Sep. 14, 2009; 12 pages.
Keyghobad,Seyamak; Non-Final Rejection for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; dated May 1, 2009; 5 pages.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliancesl under U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; 33 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; dated Jul. 19, 2010; 8 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; dated Jun. 28, 2010; 10 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,957; filed Jun. 24, 2009; dated Jun. 24, 2010; 10 pgs.
Keyghobad,Seyamak; Non-Final Rejection for U.S. Appl. No. 12/490,957; filed Jun. 24, 2009; dated Dec. 23, 2009; 17 pgs.
Young et al. “Real-Time Intranet-Controlled Virtual Instrument Multiple-Circuit Power Monitoring,” IEEE Transactions on Instrumentation and Measurement, Jun. 2000. vol. 49, No. 3, p. 570. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?.
De Almeida et al. “Advanced Monitoring Technologies for the Evaluation of Demand-Side Management Programs,” IEEE Transactions on Power Systems, Aug. 1994. vol. 9, No. 3. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=336086.
Dolezilek. “Microprocessor Based Relay Information Improves the Power System,” Rural Electric Power Conference, May 1999. p. B5/1-B5/9. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=768685.
Gehami et al. “Electronic Control System I Salient Feature in Substation,” Transmission & Distrubition, Mar. 1991. vol. 43, No. 3, p. 48. [Accessed Dec. 29, 2011 —ProQuest].
Horlent. “New Metering and Reading Techniques Based on a Modular Design Concept,” 10th International Conference on Electricity Distribution, May 1989. vol. 5, p. 455-459. [Accessed Dec. 29, 2011—IEEExplore].
“In Brief,” Land Mobile Radio News, Jan. 16, 1998. vol. 52, No. 3, p. 1. [Accessed Dec. 29, 2011—ProQuest] http://proquest.umi.com/pqdweb?did=25435781&sid=1&Fmt=3&clientId=31810&RQT=309&VName%20=PQD.
“Landis & Gyr Utilities: Service Partnership Helps Utilities Use Available Resources More Effectively,” www.landisgyr.com/utilities/e/fr—press1—e.htm (archived Feb. 6, 1998) http://web.archive.org/web/19980206060801/http://www.landisgyr.com/utilities.
Tamarkin. “Automated Meter Reading”, Sep.-Oct. 1992, vol. 50, No. 5/ [Accessed Dec. 29, 2011] http://www.usclcorp.com/news/Automatic—Power—reading.pdf.
ANSI; “Protocol Specification for ANSI Type 2 Optical Port”, American National Standard, ANSI C.12.18/2006, 11 pgs.
Federal Communications Commission; “Understanding the FCC Regulations for Low-Power, Non-Licensed Transmitters”, Office of Engineering and Technology; Oct. 1993; 34 pgs.
Semtech; “TN1200.4, Calculating Radiated Power and Field Strength for Conducted Power Measurements”, Semtech Corporation, Camarillo, CA, 2007, 9 pgs.
RFM; “HX 2000 Datasheet: 916.5 MHz: Hybrid Transmitter”, RF Monolithics, Inc., Dallas, TX, USA, 1998; 2 pgs.
General Electric; “GEH-5081 kV Meter Product Manual”, Nov. 1997, 137 pgs.
General Electric; “kV RSX—RS232/RS485 Communications Options: Instructions Manual”; Mar. 1999, 33 pgs.
Orfield; “Badger® ORION® System Helps Lemmon, South Dakota Reduce Read Time, Billing Cycles”, Badger Connect Publication, 2004, 2 pgs.
AMCO; “Pit Water-Meter Transponder (PWT)”; AMCO Automated Systems, LLC; PDB-14611; Sep. 2002; 2 pgs.
AMCO; “Short-Range Programmer (SRP) VRT”; AMCO Automated Systems, LLC; PDB-14555.1; Sep. 2002; 2 pgs.
AMCO; Remote Water-Meter Transponder (RWT); AMCO Automated Systems, LLC; PDB-14610; Sep. 2002; 2 pgs.
Article entitled: “Remote Meter Reading”, http://www.meter.co.uk/RMR.html; accessed on Jul. 30, 2012, 2 pgs.
Article entitled: “Datamatic, Badger Connect for AMR Solutions”, http://www.datamatic.com/badger—partnership.html; accessed on Jul. 27, 2012, 1 pg.
Patterson, Tim; Request for Ex Parte Reexamination under U.S. Appl. No. 90/012,468, filed Sep. 6, 2012; 52 pgs.
Patterson, Tim; Request for Ex Parte Reexamination under U.S. Appl. No. 90/012,449, filed Aug. 23, 2012; 51 pgs.
Trace; “Pit Water-Meter Transponder”; User Guide; Jan. 2003 16 pgs.
Hyland; U.S. Patent Application Entitled: Infrastructure Monitoring Devices, Systems and Methods under U.S. Appl. No. 13/101,235, filed May 5, 2011; 28 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Jun. 5, 2014, 29 pgs.
Antenna. Merriam-Webster Dictionary, 2014 [retrieved on Jun. 1, 2014]. Retrieved from the Internet: <URL: www.merriam-webster.com/dictionary/antenna>.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Sep. 11, 2014, 11 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Nov. 25, 2014, 5 pgs.
Hyland; PCT Application entitled: Infrastructure Monitoring System and Method having serial No. PCT/US09/62247, filed Oct. 27, 2009, 30 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2009/062247, filed Oct. 27, 2009, dated May 3, 2011, 7 pgs.
International Search Report for serial No. PCT/US2009/062247, filed on Oct. 27, 2009, dated Dec. 18, 2009, 2 pgs.
Hyland, Gregory;Mexico Office Action for serial No. MX/a/2011/004330, filed Apr. 25, 2011, dated Mar. 21, 2013, 7 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2011/004330, filed Apr. 25, 2011, dated Jul. 18, 2013, 6 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2011/004330, filed Apr. 25, 2011, dated Oct. 3, 2013, 6 pgs.
Hyland; European Search Report for serial No. EP09824079.9, filed Oct. 27, 2009, dated May 8, 2012; 38 pages.
Hyland, Gregory; Australian Patent Examination Report for serial No. 2009308949, filed Oct. 27, 2009, dated Nov. 12, 2013, 3 pgs.
Hyland, Gregory E.;Japanese Office Action for serial No. 2011-533427, filed Oct. 27, 2009, dated Apr. 30, 2013, 15 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2011-533427, filed Oct. 27, 2009, dated Feb. 4, 2014, 50 pgs.
Hyland, Gregory E.; Decision of Rejection for Japanese serial No. 2011-533427, filed Oct. 27, 2009, dated Sep. 16, 2014, 4 pgs.
Hyland; PCT Appplication entitled: Infrastructure Monitoring Devices, Systems, and Methods having serial No. PCT/US2010/035666, filed May 20, 2010; 31 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US2010/035666, filed May 20, 2010, dated Jul. 16, 2010, 7 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2010/035666, filed May 20, 2010, dated Nov. 22, 2011, 6 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2011/012383, filed May 20, 2010, dated Oct. 8, 2012, 3 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/A/2011/012383, filed May 20, 2010, dated May 9, 2013, 8 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/A/2011/012383, filed May 20, 2010, dated Sep. 3, 2013, 10 pgs.
Hyland, Gregory E.; Mexico Final Office Action for serial No. MX/A/2011/012383, filed May 20, 2010, dated Jan. 9, 2014, 9 pgs.
European Search Report for serial No. EP2433440, filed Nov. 18, 2011, dated Nov. 21, 2012, 6 pgs.
Hyland, Gregory E.; Australian Patent Examination report for serial No. 2010249499, filed Nov. 17, 2011, dated Jun. 16, 2014, 5 pgs.
Hyland, Gregory E.; Australian Patent Examination report for serial No. 2010249499, filed Nov. 17, 2011, dated Nov. 21, 2014, 5 pgs.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 14/451,896, filed Aug. 5, 2014, dated Mar. 18, 2016, 98 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 14/450,452, filed Aug. 4, 2014, dated Feb. 17, 2016, 98 pgs.
Hyland, Gregory; Non-Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Mar. 4, 2016, 94 pgs.
Hyland; European Examination Report for serial No. EP09824079.9, filed Oct. 27, 2009, dated Nov. 13, 2015; 6 pgs.
McCraven, Jeremy; Applicant Interview Summary for U.S. Appl. No. 14/273,823, filed May 9, 2014, dated Jan. 12, 2016, 3 pgs.
Article entitled: “OET Exhibits List”, https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application—id=194044&fcc—id=; Feb. 20, 2001, 2 pgs.
Fleury Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Nov. 5, 2014, 30 pgs.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Jul. 9, 2014, 3 pgs.
Hyland, Gregory E; Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Aug. 19, 2016; 20 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Mar. 12, 2014; 19 pgs.
Fleury, Jr., Leo W.; Issue Notification for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Mar. 2, 2016, 1 pg.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Sep. 12, 2013; 37 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Feb. 2, 2016, 9 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated May 12, 2015, 9 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Sep. 23, 2015, 11 pgs.
Ortiz, Jorge Isaac; U.S. Patent Application entitled: Nozzle Cap Multi-Band Antenna Assembly having U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, 44 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Oct. 20, 2014, 17 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 8, 2016, 36 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Nov. 6, 2013, 39 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 10, 2015, 20 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Jun. 4, 2014, 24 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Feb. 27, 2015, 15 pgs.
Richarz, Werner Guenther; Restriction Requirement for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 27, 2013; 5 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Mar. 8, 2016, 27 pgs.
Chou, et al.; Article entitled: “Non-invasive Acceleration-based Methodology for Damage Detection and Assessment of Water Distribution System”, Mar. 2010, 17 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated May 17, 2016, 48 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Jan. 16, 2015, 60 pgs.
Fleury Jr, Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Sep. 23, 2013; 35 pgs.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Jun. 18, 2014, 4 pgs.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Sep. 9, 2015, 3 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Apr. 23, 2014, 19 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated May 22, 2015, 28 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Oct. 21, 2014, 37 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Mar. 1, 2016, 42 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,795, filed Sep. 8, 2012, dated Sep. 21, 2016, 18 pgs.
Hyland, Gregory E.; Australian Examination Report for serial No. 2015202550, filed May 5, 2011, dated Aug. 12, 2016, 4 pgs.
Fleury, Leo W.; International Preliminary Report on Patentability for serial No. PCT/US12/50390 filed Aug. 10, 2012, dated Feb. 18, 2014, 14 pgs.
Fleury, Leo W.; International Search Report and Written Opinion for serial No. PCT/US12/50390 filed Aug. 10, 2012, dated Dec. 17, 2012, 18 pgs.
Gibson, Daryl Lee; U.S Patent Application entitled: Nozzle Cap Multi-band Antenna Assembly, having U.S. Appl. No. 15/255,795, filed Sep. 2, 2016, 65 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated Aug. 31, 2016, 4 pgs.
Fleury Jr., Leo W.; European Search Report for serial No. 12823594, filed Aug. 10, 2012, dated Jun. 8, 2015, 11 pgs.
Fleury, Leo W., U.S. Provisional Patent Application Entitled: Hydrant Leak Detector Communication Device, System, and Method under U.S. Appl. No. 61/523,274, filed Aug. 12, 2011; 35 pgs.
Hunaidi, Osama; Issue Notification for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Sep. 22, 2010, 1 pg.
Hunaidi, Osama; Non-Final Office Action for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Jan. 20, 2010, 50 pgs.
Hunaidi, Osama; Notice of Allowance for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Jun. 24, 2010, 8 pgs.
Non-Patent Literature Murata (entitled “Piezoelectric Sounds Components”), accessed at http://web.archive.org/web/20030806141815/http://www.murata.com/catalog/p37e17.pdf, archived on Aug. 6, 2003.
Non-Patent Literature NerdKits, accessed at http://web.archive.org/web/20090510051850/http://www.nerdkits.com/videos/sound—meter/, archived on May 10, 2009.
Non-Patent Literature Bimorph (entitled “Bimorph actuators”), accessed at http://web.archive.org/web/20080122050424/http://www.elpapiezo.ru/eng/curve—e.shtml, archived on Jan. 22, 2008.
Gibson, Daryl Lee; U.S. Provisional Application entitled: Nozzle Cap Multi-Band Antenna Assembly having U.S. Appl. No. 62/294,973, filed Feb. 12, 2016, 54 pgs.
Fleury, et al.; Supplemental European Search Report for application No. 12823594.2, filed Aug. 20, 2012, dated Feb. 18, 2015, 6 pgs.
J. A. Gallego-Juarez, G. Rodriguez-Corral and L. Gaete-Garreton, An ultrasonic transducer for high power applications in gases, Nov. 1978, Ultrasonics, published by IPC Business Press, p. 267-271.
Non-Patent Literature “Radiodetection Water Leak Detection Products”, 2008, Radiodetection Ltd.—SPX Corporation.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 14/451,896; filed Aug. 5, 2014, dated May 12, 2016; 15 pages.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated May 30, 2016, 4 pgs.
Dukes, Brent; Non-Final Office Action for U.S. Appl. No. 14/475,050, filed Sep. 2, 2014, dated May 19, 2016, 119 pgs.
McCraven, Jeremy; Non-Final Office Action for U.S. Appl. No. 14/273,823, filed May 9, 2014, dated Apr. 12, 2016, 86 pgs.
Fleury, Jr., Leo W.; Corrected Notice of Allowability for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Feb. 14, 2017; 8 pgs.
Fleury, Jr., Leo W.; Issue Notification for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Feb. 22, 2017; 1 page.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated Dec. 13, 2016, 5 pgs.
Hyland, Gregory E.; Australian Examination Report for serial No. 2015202550, filed May 5, 2011, dated Feb. 9, 2017, 4 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Dec. 13, 2016, 52 pgs.
Dintakurti, Ganapathi Deva Varma; Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Nov. 8, 2016, 31 pgs.
Fleury, Jr., Leo W..; Notice of Allowability for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Oct. 24, 2016, 13 pgs.
Hyland, Gregory; Extended European Search Report for serial No. 11796120.1, filed May 5, 2011, dated Nov. 4, 2016, 8 pgs.
Fleury, Jr., Leo W.; Supplemental Notice of Allowance for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Nov. 22, 2016; 8 pgs.
Hyland, Gregory; Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Jun. 7, 2017, 25 pgs.
Richarz, Werner Guenther; Notice of Allowance for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Jun. 13, 2017, 31 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Mar. 16, 2017, 30 pgs.
Hyland, Gregory E..; Office Action for Canadian Patent Application No. 2,766,850, filed May 5, 2011, dated Mar. 13, 2017, 4 pgs.
Hyland, Gregory E.; Australian Examination Report for Serial No. 2015202550, filed May 5, 2011, dated May 16, 2017, 5 pgs.
Fleury Jr., Leo W.; European Search Report for Serial No. 12823594, filed Aug. 10, 2012, dated May 10, 2017, 4 pgs.
Hunaidi, Osama; Non-final Office Action for U.S. Appl. No. 09/482,317, filed Jan. 14, 2000, dated Dec. 17, 2001, 6 pgs.
Hunaidi, Osama; Notice of Allowance for U.S. Appl. No. 09/482,317, filed Jan. 14, 2000, dated May 13, 2002, 4 pgs.
Peter, Russo Anthony; European Search Report for Patent Application No. EP95307807, filed Nov. 1, 1995, dated Jul. 22, 1998, 5 pgs.
Ortiz, Jorge; International Search Report and Written Opinion for PCT/US16/67689, filed Dec. 20, 2016, dated Mar. 8, 2017, 9 pgs.
Gibson, Daryl Lee; International Search Report and Written Opinion for PCT Application No. PCT/US2016/067692, filed Dec. 20, 2016, dated Mar. 2, 2017,10 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Sep. 6, 2017, 12 pgs.
Fleury, Leo; Non-Final Office Action for U.S. Appl. No. 14/870,070, filed Sep. 30, 2015, dated Jun. 21, 2017, 88 pgs.
Richarz, Werner Guenther; Corrected Notice of Allowability for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Aug. 29, 2017, 6 pgs.
Richarz, Werner Guenther; Issue Notification for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 6, 2017, 1 pg.
Hyland, Gregory E.; Australian Examination Report for U.S. Appl. No. 2015202550, filed May 5, 2011, dated Jul. 5, 2017, 4 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Sep. 19, 2017, 8 pgs.
Related Publications (1)
Number Date Country
20150082868 A1 Mar 2015 US
Provisional Applications (1)
Number Date Country
61355468 Jun 2010 US
Continuations (1)
Number Date Country
Parent 13101235 May 2011 US
Child 14557754 US