System and method for automated configuration of meters

A number of meters to be configured according to a particular billing rate. Multiple billing rates may be defined, named, and stored for use. Each such billing rate may include time of use (TOU) configuration parameters and/or demand configuration parameters. Alternatively, a billing rate may include strictly consumption based parameters. Each billing rate is “meter independent”, meaning that it is not specific to any particular meter configuration format. The billing rate is defined in a format that is convenient for the operator and then translated into a format that is specific to each meter on which it is implemented. Thus, to configure a number of different parameters on a number of differently formatted meters, only a single billing rate need be defined and propagated to the meters.

FIELD OF THE INVENTION

The present invention relates to wireless networks for collecting data, and more particularly, to systems and methods for automated configuration of meters.

BACKGROUND OF THE INVENTION

The collection of meter data from electrical energy, water, and gas meters has traditionally been performed by human meter-readers. The meter-reader travels to the meter location, which is frequently on the customer's premises, visually inspects the meter, and records the reading. The meter-reader may be prevented from gaining access to the meter as a result of inclement weather or, where the meter is located within the customer's premises, due to an absentee customer. This methodology of meter data collection is labor intensive, prone to human error, and often results in stale and inflexible metering data.

Some meters have been enhanced to include a one-way radio transmitter for transmitting metering data to a receiving device. A person collecting meter data that is equipped with an appropriate radio receiver need only come into proximity with a meter to read the meter data and need not visually inspect the meter. Thus, a meter-reader may walk or drive by a meter location to take a meter reading. While this represents an improvement over visiting and visually inspecting each meter, it still requires human involvement in the process.

An automated means for collecting meter data involves a fixed wireless network. Devices such as, for example, repeaters and gateways are permanently affixed on rooftops and pole-tops and strategically positioned to receive data from enhanced meters fitted with radio-transmitters. Typically, these transmitters operate in the 902-928 MHz range and employ Frequency Hopping Spread Spectrum (FHSS) technology to spread the transmitted energy over a large portion of the available bandwidth.

Data is transmitted from the meters to the repeaters and gateways and ultimately communicated to a central location. While fixed wireless networks greatly reduce human involvement in the process of meter reading, such systems require the installation and maintenance of a fixed network of repeaters, gateways, and servers. Identifying an acceptable location for a repeater or server and physically placing the device in the desired location on top of a building or utility pole is a tedious and labor-intensive operation. When a portion of the network fails to operate as intended, human intervention is typically required to test the effected components and reconfigure the network to return it to operation.

Another drawback of a conventional fixed wireless networks is that each meter within the network needs to be manually configured one at a time to communicate with a particular portion of the established network. This process is particularly cumbersome because many of the meter parameters must be configured independently of one another. For example, meter parameters such as time of use (TOU) switch times and demand configuration must be independently configured. Furthermore, each meter's display must be independently programmed to display items relevant to the meter's individual configuration.

Thus, while existing fixed wireless networks have reduced the need for human involvement in the daily collection of meter data, such networks require substantial human investment in planning, installation, configuration, and maintenance and are relatively inflexible and difficult to manage. Therefore, there is a need for a systems and methods for automated configuration of meters.

SUMMARY OF THE INVENTION

The present invention is directed to systems and methods for automated configuration of meters. The present invention enables a number of meters to be configured according to a particular billing rate. The present invention also enables multiple billing rates may be defined, named, and stored for use. Each such billing rate may include time of use (TOU) configuration parameters and/or demand configuration parameters. Alternatively, a billing rate may also include strictly consumption based parameters. Each billing rate is “meter independent”, meaning that it is not specific to any particular meter configuration format. The billing rate is defined in a format that is convenient for the operator and then translated into a format that is specific to each meter on which it is implemented. Thus, to configure a number of different parameters on a number of differently formatted meters, only a single billing rate need be defined and propagated to the meters.

According to an aspect of the invention, a billing rate may be assigned to one or more meters either manually or programmatically. Upon assigning a billing rate to the meters, the configuration parameters corresponding to the billing rate are retrieved and analyzed to determine whether the meters are capable of implementing the parameters. If any of the meters are unable to implement the parameters or if the system cannot configure any of the meters, then the assigned billing rate may be refused for those meters.

According to another aspect of the invention, each meter may be configured to display information relevant to its assigned billing rate in its meter display area. Each meter may be configured to display such relevant information even if the assigned billing rate differs from the meter's underlying configuration.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Exemplary systems and methods for gathering meter data are described below with reference toFIGS. 1-3. It will be appreciated by those of ordinary skill in the art that the description given herein with respect to those figures is for exemplary purposes only and is not intended in any way to limit the scope of potential embodiments.

Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, are operable to wirelessly communicate with each other. A collector is operable to automatically identify and register meters for communication with the collector. When a meter is installed, the meter becomes registered with the collector that can provide a communication path to the meter. The collectors receive and compile metering data from a plurality of meter devices via wireless communications. A communications server communicates with the collectors to retrieve the compiled meter data.

FIG. 1provides a diagram of an exemplary metering system110. System110comprises a plurality of meters114, which are operable to sense and record usage of a service or commodity such as, for example, electricity, water, or gas. Meters114may be located at customer premises such as, for example, a home or place of business. Meters114comprise an antenna and are operable to transmit data, including service usage data, wirelessly. Meters114may be further operable to receive data wirelessly as well. In an illustrative embodiment, meters114may be, for example, a electrical meters manufactured by Elster Electricity, LLC.

System110further comprises collectors116. Collectors116are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. Collectors116comprise an antenna and are operable to send and receive data wirelessly. In particular, collectors116are operable to send data to and receive data from meters114. In an illustrative embodiment, meters114may be, for example, an electrical meter manufactured by Elster Electricity, LLC.

A collector116and the meters114for which it is configured to receive meter data define a subnet/LAN120of system110. As used herein, meters114and collectors116maybe considered as nodes in the subnet120. For each subnet/LAN120, data is collected at collector116and periodically transmitted to a data collection server206. The data collection server206stores the data for analysis and preparation of bills. The data collection server206may be a specially programmed general purpose computing system and may communicate with collectors116wirelessly or via a wire line connection such as, for example, a dial-up telephone connection or fixed wire network.

Generally, collector116and meters114communicate with and amongst one another using any one of several robust wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS). As illustrated, meters114aare “first level” meters that communicate with collector116, whereas meters114bare higher level meters that communicate with other meters in the network that forward information to the collector116.

Referring now toFIG. 2, there is illustrated a system200in which the present invention may be embodied. The system200includes a network management server202, a network management system (NMS)204and a data collection server206that together manage one or more subnets/LANs120and their constituent nodes. The NMS204tracks changes in network state, such as new nodes registering/unregistering with the system200, node communication paths changing, etc. This information is collected for each subnet/LAN120and are detected and forwarded to the network management server202and data collection server206.

In accordance with an aspect of the invention, communication between nodes and the system200is accomplished using the LAN ID, however it is preferable for customers to query and communicate with nodes using their own identifier. To this end, a marriage file208may be used to correlate a customer serial number and LAN ID for each node (e.g., meters114a) in the subnet/LAN120. A device configuration database210stores configuration information regarding the nodes. For example, in the metering system110, the device configuration database may the time of use (TOU) program assignment for the meters114acommunicating to the system200. A data collection requirements database212contains information regarding the data to be collected on a per node basis. For example, a user may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s)114a. Reports214containing information on the network configuration may be automatically generated or in accordance with a user request.

The network management system (NMS)204maintains a database describing the current state of the global fixed network system (current network state220) and a database describing the historical state of the system (historical network state222). The current network state220contains data regarding current meter to collector assignments, etc. for each subnet/LAN120. The historical network state222is a database from which the state of the network at a particular point in the past can be reconstructed. The NMS204is responsible for, amongst other things, providing reports214about the state of the network. The NMS204may be accessed via an API220that is exposed to a user interface216and a Customer Information System (CIS)218. Other external interfaces may be implemented in accordance with the present invention. In addition, the data collection requirements stored in the database212may be set via the user interface216or CIS218.

The data collection server206collects data from the nodes (e.g., collectors116) and stores the data in a database224. The data includes metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.

The network management server202, network management system204and data collection server206communicate with the nodes in each subnet/LAN120via a communication system226. The communication system226may be a Frequency Hopping Spread Spectrum radio network, a mesh network, a Wi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS) network, etc., or any combination of the above and enables the system200to communicate with the metering system110.

The present invention enables multiple billing rates to be defined, named, and stored. Each such billing rate may include time of use (TOU) configuration parameters and/or demand configuration parameters. Alternatively, a billing rate may include strictly consumption based parameters. The billing rates may also include display settings for meter display areas. The billing rates may be defined and named via UI216and may be stored within device configuration database210.

Each billing rate is “meter independent”, meaning that it is not specific to any particular meter configuration format. The billing rate is defined in a format that is convenient for the operator and then translated into a format that is specific to each meter on which it is implemented. Each billing rate may, at any time, be displayed in a meter independent format so that it can be easily evaluated by an operator. The billing rates may be displayed via UI216.

A particular billing rate may be assigned to one or more selected meters either manually or programmatically. The billing rate may be assigned programmatically using, for example, a CIS software package. The billing rate may be assigned manually by, for example, selecting the billing rate by name from a set of available billing rates stored at configuration database210.FIG. 3illustrates an exemplary sequence of events when a billing rate is assigned to selected meters. At step310, the assigned billing rate is received by NMS204. If assigned manually, the billing rate may be received via UI216, or, if assigned programmatically, the billing rate may be received via CIS import218. As should be appreciated, each selected meter may be assigned the billing rate as its initial billing rate or, at any time, one or more meters may have their assignment changed from one billing rate to another.

At step312, the configuration parameters associated with the billing rate are retrieved. The configuration parameters may be retrieved from configuration database210. The configuration parameters are originally assigned when the billing rate is defined, but may be subsequently updated. As discussed previously, the configuration parameters may include TOU and/or demand parameters or, alternatively, consumption based parameters. The configuration parameters may also include meter display settings.

At step314, it is determined whether the selected meters are capable of implementing the retrieved configuration parameters. Specifically, the meters may have limited capabilities with respect to TOU and demand parameters. For example, the configuration parameters of the billing rate may require more tiers or more seasons than a particular meter is capable of implementing. System200may also be otherwise incapable of configuring a meter due to another problem such as, for example, a network communications problem. If any of the selected meters are unable to implement the parameters or if they cannot otherwise be configured, then, at step316, the assigned billing rate may be refused for those meters.

For those meters that are configurable, at step318, the billing rate parameters are translated from the meter independent format into a format that is specific to each meter. At step320, the meters are configured to implement the billing rate parameters. Each meter may be configured according to its particular limitations and requirements. For example, configuration calls used to deliver TOU parameters, demand parameters, and/or display settings may be made using a device specific communications protocol. In the case of telephone connected devices, the allowable time windows for device configuration calls can be manually set. For each meter, the configuration operation may be repeatedly retried until it is successful. At any stage of the configuration process, reports may be requested and generated to indicate the progress of the process. Specifically, such reports may indicate which meters are to be configured, the progress of TOU and/or demand configurations, and which meters could not be configured.

Each of the selected meters may be programmed to display items related to its assigned billing rate, even if the underlying configuration of the meter is not exactly identical to the rate. For example, if the rate defines three tiers, but the meter, because of its programming limitations, must be programmed to implement four tiers, then the meter will be configured to only display the three tiers of the billing rate. In one embodiment, a meter may be configured to display time and date only if the meter is assigned to a TOU rate. In another embodiment, demand items may be displayed only if there is a demand component in the rate, even if a meter's underlying configuration always computes demands.

During the TOU configuration process, a meter's summation registers may optionally be cleared if the meter supports and the operator has enabled this functionality. Additionally, during the demand and TOU configuration process, a meter's demand registers can optionally be reset if the meter supports and the operator has enabled this functionality. Furthermore, each configured meter may be logged for auditing purposes.

While systems and methods have been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles described above and set forth in the following claims. Accordingly, reference should be made to the following claims as describing the scope of disclosed embodiments.