US9270552B2 - Energy monitoring system using network management protocols - Google Patents
Energy monitoring system using network management protocols Download PDFInfo
- Publication number
- US9270552B2 US9270552B2 US11851471 US85147107A US9270552B2 US 9270552 B2 US9270552 B2 US 9270552B2 US 11851471 US11851471 US 11851471 US 85147107 A US85147107 A US 85147107A US 9270552 B2 US9270552 B2 US 9270552B2
- Authority
- US
- Grant status
- Grant
- Patent type
- Prior art keywords
- network
- management
- ied
- system
- protocol
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing packet switching networks
- H04L43/08—Monitoring based on specific metrics
- H04L43/0805—Availability
- H04L43/0817—Availability functioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F1/00—Details of data-processing equipment not covered by groups G06F3/00 - G06F13/00, e.g. cooling, packaging or power supply specially adapted for computer application
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/28—Supervision thereof, e.g. detecting power-supply failure by out of limits supervision
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F1/00—Details of data-processing equipment not covered by groups G06F3/00 - G06F13/00, e.g. cooling, packaging or power supply specially adapted for computer application
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/30—Means for acting in the event of power-supply failure or interruption, e.g. power-supply fluctuations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance or administration or management of packet switching networks
- H04L41/02—Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
- H04L41/0213—Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization using standardized network management protocols, e.g. simple network management protocol [SNMP] or common management interface protocol [CMIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network-specific arrangements or communication protocols supporting networked applications
- H04L67/02—Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
- H04L67/025—Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP] for remote control or remote monitoring of the application
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S40/00—Communication or information technology specific aspects supporting electrical power generation, transmission, distribution or end-user application management
- Y04S40/10—Communication technology specific aspects
- Y04S40/16—Details of management of the overlaying communication network between the monitoring, controlling or managing units and monitored, controlled or operated electrical equipments
- Y04S40/168—Details of management of the overlaying communication network between the monitoring, controlling or managing units and monitored, controlled or operated electrical equipments for performance monitoring
Abstract
Description
Advancements in, and demands for, technology have increased. In particular, high technology industries have increased their demands on the electrical power supplier, requiring more power, increased reliability and lower costs. A typical computer data center may use several hundred watts of energy per square foot compared to an average of 15 watts per square foot for a typical commercial building. Accordingly, the monitoring of energy usage and the detection of power quality events may be necessary for high technology industries.
Complex networks of computer and communications equipment may use a network management system to manage this equipment. One or more network management stations obtain information from the attached network devices using a network management protocol that communicates with agent software running on each device. Although network devices may offer a variety of performance data via the network management protocol, they do not have the ability to measure key parameters of the power system they are attached to.
The network management system, such as a computer network, may utilize energy meters and/or Intelligent Electronic Devices (“IED's”) to monitor energy usage. The energy meters and/or IED's may be part of an energy management system that is independent of the network management system. The energy management system may communicate with a network protocol, such as the Modbus interface. The communication within the energy management system may be independent of the network management system that is being monitored.
The system and method may be better understood with reference to the following drawings and description. Non-limiting and non-exhaustive embodiments are described with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention. In the drawings, like referenced numerals designate corresponding parts throughout the different views.
By way of introduction, the embodiments described below include a system and method for the integration of Intelligent Electronic Devices (IED) into a network management system. The embodiments relate to IED's that are configured to communicate with a network management system by utilizing the network management protocol of that system. The IED's may be installed within a network management system to measure power system parameters, as well as to monitor power system equipment responsible for maintaining a reliable supply of power. The IED supports a network management protocol and can be configured to communicate power system parameters to a network management station. The IED may be configured to map the power system parameters to corresponding network protocol variables.
Other systems, methods, features and advantages will be, or will become, apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the following claims. Nothing in this section should be taken as a limitation on those claims. Further aspects and advantages are discussed below in conjunction with the embodiments.
The user 102 may be an operator of the user device 104. The user 102 may interface with the network management station 108 to manage, monitor, and/or control any components or devices coupled with the communications network 106. The user 102 may not only include any individual, but a business entity or group of people. In one embodiment, the user 102 may utilize the user device 104 coupled with the network management station 108 to manage the network. In an alternative embodiment, the user 102 may utilize the user device 104 to monitor the energy usage of the network management system 100 by the IED's 110 a-e and the gateway IED 111.
The user device 104 may be a computing device which allows a user to connect to the communications network 106. Examples of a user device include, but are not limited to, a personal computer, personal digital assistant (“PDA”), cellular phone, or other electronic device. The user device 104 may be configured to allow the user 102 to interact with the network management station 108 or other components of the network management system 100. The user device 104 may include a keyboard, keypad or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to allow interaction from the user 102.
Any of the network devices or components in the network management system 100 may be coupled with one another through a network, including but not limited to the communications network 106. Accordingly, any of the components in the network management system 100 may include communication ports configured to connect with a network.
The communications network 106 may connect any of the components in the network management system 100 to enable communication of data between the devices may include wired networks, wireless networks, or combinations thereof. The wireless network may be a cellular telephone network, a network operating according to a standardized protocol such as IEEE 802.11, 802.16, 802.20, published by the Institute of Electrical and Electronics Engineers, Inc., or WiMax network. Further, the communications network 106 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. The communications network 106 may include one or more of a local area network (LAN), a wide area network (WAN), a direct connection such as through a Universal Serial Bus (USB) port, and the like, and may include the set of interconnected networks that make up the Internet. The communications network 106 may include any communication method or employ any form of machine-readable media for communicating information from one device to another. For example, the network management station 108 may receive energy measurements and/or related data any of the IED's 110 a-e, or the gateway IED 111 over the communications network 106. As described, communication over the communications network 106 utilizes a network management protocol, such as Simple Network Management Protocol (SNMP) and/or Common Management Information Protocol (CMIP).
The IED's 110 a-e and the gateway IED 111 may be any intelligent electronic devices (“IED's”) such as programmable logic controllers (“PLC's”), Remote Terminal Units (“RTU's”), electric/watt hour meters, protection relays and fault recorders as described below. The IED's may make use of memory and microprocessors to provide increased versatility and additional functionality. Such functionality includes the ability to communicate with remote computing systems, either via a direct connection, e.g. modem or via a network, such as the communications network 106. For more detailed information regarding IED's capable of network communication, please refer to U.S. Pat. No. 6,961,641, entitled “INTRA-DEVICE COMMUNICATIONS ARCHITECTURE FOR MANAGING ELECTRICAL POWER DISTRIBUTION AND CONSUMPTION”, U.S. Pat. No. 6,751,562, entitled “COMMUNICATIONS ARCHITECTURE FOR INTELLIGENT ELECTRONIC DEVICES”, and U.S. Pat. No. 7,216,043, entitled “PUSH COMMUNICATIONS ARCHITECTURE FOR INTELLIGENT ELECTRONIC DEVICES,” each of which is hereby incorporated by reference. In particular, the monitoring of electrical power, especially the measuring and calculating of electrical parameters, may provide valuable information for power utilities and their customers. Monitoring of electrical power may be important to ensure that the electrical power is effectively and efficiently generated, distributed and utilized. The monitoring of electrical power in real time, and responding to the monitored results in real time, can provide for cost savings in today's marketplace.
Various different arrangements are presently available for monitoring, measuring, and controlling power parameters. Typically, an IED, such as an individual power measuring device, is placed on a given branch or line proximate to one or more loads which are coupled with the branch or line in order to measure/monitor power system parameters. In addition to monitoring power parameters of a certain load(s), such power monitoring devices have a variety of other applications. For example, power monitoring devices can be used in supervisory control and data acquisition (“SCADA”) systems such as the XA/21 Energy Management System manufactured by GE Harris Energy Control Systems located in Melbourne, Fla.
As used herein, Intelligent electronic devices (“IED's”) include Programmable Logic Controllers (“PLC's”), Remote Terminal Units (“RTU's”), electric power meters, protective relays, fault recorders and other devices which are coupled with power distribution networks to manage and control the distribution and consumption of electrical power. Such devices typically utilize memory and microprocessors executing software to implement the desired power management function. IED's include on-site devices coupled with particular loads or portions of an electrical power distribution system and are used to monitor and manage power generation, distribution and consumption. IED's may also be referred to as power management devices (“PMD's”).
A Remote Terminal Unit (“RTU”) is a field device installed on an electrical power distribution system at the desired point of metering. It is equipped with input channels (for sensing or metering), output channels (for control, indication or alarms) and a communications port. Metered information is typically available through a communication protocol via a serial communication port. An exemplary RTU is the XP Series, manufactured by Quindar Productions Ltd. in Mississauga, Ontario, Canada.
A Programmable Logic Controller (“PLC”) is a solid-state control system that has a user-programmable memory for storage of instructions to implement specific functions such as Input/output (I/O) control, logic, timing, counting, report generation, communication, arithmetic, and data file manipulation. A PLC consists of a central processor, input/output interface, and memory. A PLC is designed as an industrial control system. An exemplary PLC is the SLC 500 Series, manufactured by Allen-Bradley in Milwaukee, Wis.
A meter is a device that records and measures power events, power quality, current, voltage waveforms, harmonics, transients and other power disturbances. Revenue accurate meters (“revenue meter”) relate to revenue accuracy electrical power metering devices with the ability to detect, monitor, report, quantify and communicate power quality information about the power which they are metering. An exemplary meter is the model 8500 meter, manufactured by Power Measurement Ltd, in Saanichton, B.C. Canada.
A protective relay is an electrical device that is designed to interpret input conditions in a prescribed manner, and after specified conditions are met, to cause contact operation or similar abrupt change in associated electric circuits. A relay may consist of several relay units, each responsive to a specified input, with the combination of units providing the desired overall performance characteristics of the relay. Inputs are usually electric but may be mechanical, thermal or other quantity, or a combination thereof. An exemplary relay is the type N and KC, manufactured by ABB in Raleigh, N.C.
A fault recorder is a device that records the waveform and digital inputs, such as breaker status which resulting from a fault in a line, such as a fault caused by a break in the line. An exemplary fault recorder is the IDM, manufactured by Hathaway Corp in Littleton, Colo.
IED's can also be created from existing electromechanical meters or solid-state devices by the addition of a monitoring and control device which converts the mechanical rotation of the rotary counter into electrical pulses or monitors the pulse output of the meter. An exemplary electromechanical meter is the AB1 Meter manufactured by ABB in Raleigh, N.C. Such conversion devices are known in the art.
The network management system 100 may include Intelligent Electronic Devices (“IED's”) distributed throughout the system to monitor and control the flow of electrical power to any of the components of the system. The network management system 100 may be used for monitoring, protection and control of communication devices. The system may include electrical power distribution that is monitored by IED's. IED's may be positioned along the supplier's distribution path or within a customer's internal distribution system. IED's include revenue electric watt-hour meters, protection relays, programmable logic controllers, remote terminal units, fault recorders and other devices used to monitor and/or control electrical power distribution and consumption. IED's also include legacy mechanical or electromechanical devices which have been retrofitted with appropriate hardware and/or software so as to be able to integrate with the power management architecture. Typically an IED is associated with a particular load or set of loads which are drawing electrical power from the power distribution system. The IED may also be capable of receiving data from or controlling its associated load. Depending on the type of IED and the type of load it may be associated with, the IED implements a power management function such as measuring power consumption, controlling power distribution such as a relay function, monitoring power quality, measuring power parameters such as phasor components, voltage or current, controlling power generation facilities, or combinations thereof. For functions which produce data or other results, the IED can push the data onto the communications network 106, to another IED or back end server, automatically or event driven, (discussed in more detail below) or the IED can wait for a polling communication which requests that the data be transmitted to the requester.
In addition, the IED is also capable of implementing an application component of a power management application utilizing the network management system 100. The power management application may include power management application components which are implemented on different portions of the network management system and communicate with one another via the network management system. The operation of the power management application components and their interactions/communications implement the overall power management application. One or more power management applications may be utilizing the architecture at any given time and therefore, the IED may implement one or more power management application components at any given time.
Measurement data or other data recorded, measured or monitored with the IED may be referred to as IED variables. As discussed below, IED variables may be mapped to network management protocol variables. The network management protocol variables may include communication variables and metrics (e.g. variables tracked by the network management system), including any of the variables described by the MIB definitions, such as in the MIB-II specification (RFC 1213—Management Information Base for Network Management of TCP/IP-based internets: MIB-II, by the SNMP Working Group for the IAB Official Protocol Standards and dated March 1991, which is hereby incorporated by reference). Such variables may include descriptive information for the network device (such as the IED) like sysName, sysLocation and sysContact, as well as communications-related variables such as tcpInErrs and tcpOutRsts. The IED variables include energy system variables for the equipment being monitored by the IED. Energy system variables may include an indication of the current status of the equipment being monitored, and may include a state of digital inputs monitoring equipment contacts, a real-time measurement of voltage and current, and a counter value indicating the number of voltage sag/swell events that have occurred.
The generator 112, universal power supply (UPS) 114, communications equipment 116, and server racks 118 may be additional network devices or components in the network management system 100 that are managed by the user 102 and/or the network management station 108. The components may also be managed by the corresponding IED's 110 a-e and/or the gateway IED 111. In particular, the generator 112 may generate electricity for the network management system 100. The generator 112 may provide power for any of the components in the network management system 100. The energy and power quality from the generator 112 may be monitored and reported by the IED 110 a. The UPS 114 may be an alternative power supply for any of the components in the network management system 100. The energy and power quality from the UPS 114 may be monitored and reported by the IED 110 b. The communications equipment 116 may be monitored by the network management station 108. The communications equipment 116 may include computers, networking hardware, switching and transmission gear, base stations, or other components which may be used in the network management system 100 or other communications network. The energy and power quality from the communications equipment 116 may be monitored and reported by the IED 110 c.
The server racks 118 may be a hardware computer system component configured to receive and/or send data. The server racks 118 may be computers that provide a service, such as database access, file transfer, or remote access over a network, such as the communications network 106. In addition, the server racks 118 may provide resources, such as file space, over a network, such as the communications network 106. The server racks 118 may be configured to run a server application or provide network access, such as with the Internet. The server racks 118 may include a file server, database server, backup server, print server, mail server, web server, FTP server, application server, VPN server, DHCP server, DNS server, WINS server, SMTP server, CMIP server, logon server, security server, domain controller, backup domain controller, or a proxy server. The energy and power quality from the server racks 118 may be monitored and reported by the IED 110 d and/or the IED 110 e. In addition, a gateway IED 111 may be coupled with the IED's 110 d-e and/or the server racks 118.
The gateway IED 111 may be coupled with the other IED's 110 d-e to receive data measurements that are transmitted over the communications network 106. The gateway IED 111 may be configured with communication ports for communicating with the communications network 106, whereas, the IED's 110 d-e that are coupled with the gateway IED 111 may not be equipped to communicate with the communications network 106. In particular, the gateway IED 111 may be configured to communicate using the network management protocol, while the IED's 110 d-e are not configured to communicate using that protocol. Accordingly, the data measured by IED's 110 d-e may be transmitted to the gateway IED 111, which then transmits the data over the communications network 106 to the network management station 108 and/or the user device 104. In one embodiment, the gateway IED 111 may be referred to as a master IED and the IED's 110 d-e may be referred to as slave IED's.
In one embodiment, a gateway IED may be coupled with many IED's. The IED's 110 d-e may be less expensive than the gateway IED 111, so the network management system 100 may include one gateway IED 111 coupled with the other IED's 110 a-e to reduce costs, but still enable the IED's 110 a-e to communicate data over the communication network 106 using the network management protocol. As shown in
The network management station 108 may monitor and/or communicate with any of the components in the network management system 100. The network management station 108 may also be referred to as a manager and is configured to manage a plurality of managed devices. In particular, the network management station 108 communicates using a network management protocol. For example, the network management protocol communication may include the Simple Network Management Protocol (SNMP), the Common Management Information Protocol (CMIP), or any other network management protocol that is configured for communications in a network management system. As described, a network management system, such as system 100, includes devices that are coupled to a network that are monitored and managed by a manager (such as the network management station 108) using a network management protocol. The network management station 108 may collect and store information regarding any of the devices on the network. In one embodiment, the network management station 108 may be operated by a human network manager (not shown). The human network manager may interface with the network management station 108 to determine the status of the network management system 100 or to access any of the stored information regarding the devices on the network.
In order to communicate through a network management protocol, such as SNMP, the managed devices 202, 206 may include a first agent 204 and a second agent 208, respectively. The agents 204, 208 may be a network management software module that resides in the managed devices 202, 206, respectively. The agents 204, 208 may interpret network management protocol communications for communicating information about the managed devices 202, 206. In one embodiment, the agent is an interface between the network management station and the device that is being managed. In other words, the agents 204, 208 are interfaces for communication between the network management station 108 and the managed devices 202, 206, respectively. The agent in a managed device may be responsible for interpretation and handling of the network management station requests to the managed device and for the generation of properly-formatted responses (using the network management protocol) to the network management station.
An IED may be coupled with each of the managed devices 202, 206 for monitoring the energy usage of the managed devices as shown in
The gateway IED 111 may act as a gateway between the network management system and other devices, such as IED's 110 d-e. The IED's 110 d-e may report to and provide data to the gateway IED 111. Likewise, if the network management station 108 requests data from the IED's 110 d-e, then that request may be sent to the gateway IED 111 using the network management protocol. The gateway IED 111 then receives the data from the IED's 110 d-e using the IED's communication protocol and transmits that data to the network management station 108. In other words, the gateway IED 111 is a managed device that reports data and information for itself and for the IED's 110 d-e to the network management station 108. The data and information may include any energy or power parameters that are monitored by an IED as discussed.
The gateway IED 111 may be configured to translate network management system requests from the network management station 108 into a protocol supported by the coupled IED's 110 d-e. The gateway IED 111 then translates the response from the IED's 110 d-e back into the network management protocol to communicate the response to the network management station 108. In an alternative embodiment, the gateway IED 111 may poll the IED's 110 d-e and cache the acquired data. The gateway IED 111 may then provide the cached data to the network management system on request from the network management station 108. Alternatively, the gateway IED 111 may provide the cached data as an ad-hoc notification when preconfigured conditions are met.
Referring back to
The MIB 210 for each managed device stores management information that may be available to a manager, such as the network management station 108. The management information in an MIB may be related to the device using the MIB. In one embodiment, the MIB 210 is stored on the managed device. Alternatively, the MIB 210 may be accessible to the manager regardless of its storage. In one example, when an IED is a managed device, the managed objects stored in the IED's MIB may include energy measurements and power quality data measured by the IED. In one embodiment, the MIB 210 may be a structured text file that describes the variables available on a managed device to a network management station. In the case of an IED, the MIB may describe IED variables or parameters.
The MIB 210 may store network management variables that may be accessed by the network management station 108. In particular, the MIB 210 may describe a set of network management protocol variables that are available on a network device, and the network management station 108 may utilize the MIB 210 to determine which variables are available. In an alternative embodiment, one network device may have more than one MIB associated with it, and each MIB may describe a different set of variables offered by the network device. The network management variables may establish an alias for other variables from the managed device. For example, an IED managed device may include IED variables that are stored or referenced by the network management variables. A request for a network management variable would return the current value of the associated IED variable. The association of network management variables and IED variables is discussed further in
The management network protocol that is used for managing enables a manager to communicate with managed devices utilizing that managed device's MIB. The manager may perform management operations with a managed device based on that device's MIB. The accessing of a device's MIB may require communication by a network management protocol, such as SNMP.
A set of commands may be used to access the information or managed objects that are described in the MIB 210 of any device. The commands may be network management protocol operations 302 as shown in
The getRequest command 304 may be issued by the network management station 108 to request information for a particular variable or managed object from a managed device, such as the managed devices 202, 206. The variable or managed object from the managed device is described by the MIB of that managed device. Upon receiving the getRequest command 304, the agent of the managed device may issue a getResponse command 308 to the requester (the network management station 108) with the requested information or with an indication of an error, if the request cannot be processed.
In one embodiment, the getRequest command 304 may be used for the auto discovery of any IED's on the network, including IED's coupled with managed devices on the network. The auto-discovery getRequest command may be used by the network management station 108 to determine the locations and/or status of active IED's and/or managed devices, which may then be stored in a database of active devices.
The auto-discovery operation may also probe network devices for additional information. Auto-discovery may be used to provide information that differentiates IED's from other network devices within the network management system 100. In one embodiment, the network management station 108 may identify a network device as an IED when it receives a valid response after sending a probing request to a specific TCP/IP port uniquely supported by IED's. In an alternative embodiment, at least a portion of the contents of a network management protocol variable offered by IED's may be used to provide this differentiation. For example, some portion of the contents of the sysName variable defined by the MIB-II specification (referenced above) may contain an identifying string that would consistently be used by all IED's.
The getNextRequest command 306 may be sent by the network management station 108 for receiving sequentially specific management information from the managed device. The managed device may respond to the getNextRequest command 306 with a getResponse command 308 to the network management station 108 with the requested sequentially specific information or with an indication of an error.
The setRequest command 310 allows the network management station 108 to request a change to any variable or managed object stored with the managed object, such as within the MIB of the managed object. The managed device may respond to a setRequest command 310 with a setResponse command 312. The setResponse command 312 is sent from the managed device to the network management station 108 with an indication that the requested change has been made to the variable(s) or managed object(s) or with an indication of an error.
The trap command 314 may be sent from an agent of a managed device without being prompted by the manager. For example, the first agent 204 of the first managed device 202 may send a trap command 314 to the network management station 108 without being initiated to do so. The trap command 314 may be used as an alarm for notification of any problems by any of the managed devices. For example, in
As described,
The network management protocol variables 404 may be stored in management information base (MIB) of a device. The network management protocol variables 404 may be communicated using a network management protocol, such as SNMP. In one embodiment, the network management protocol variables 404 may be those variables used in the SNMP network management protocol. Additional variables are identified in the MIB-II specification mentioned above.
The IED variables 406 may include any energy measurement or power quality data. For example, the current, voltage, power, and corresponding time may be IED variables 406. IED variables may include the on/off status of IED digital inputs that are connected to output relays on the equipment being monitored, which is a configuration that is often used to monitor the operating status of the equipment. IED variables may further include counters that track the number of voltage sag/swell events or voltage transient events that the equipment being monitored has been subjected to since the time the counters were last reset.
The mapping described above may provide increased flexibility to a customer monitoring a network system. The IED's that monitor the energy usage of the network system equipment may be controlled and monitored using the same network communication protocol that is used to communicate with the network system equipment. The common protocol may allow the network administrator to also monitor the energy and power quality variables of the network equipment. The customer may be able to generate a mapping to monitor the energy and power quality variables that are important to that customer. The customer may be provided with a model of a potential mapping and be able to customize that mapping to identify different energy and power quality variables. The IED's then measure the relevant variables and are monitored by the customer using the customer-generated mapping. In addition, the mapping may be modified or adjusted to fit the changing needs of a customer. For example, a customer may have different energy needs and concerns as the network system grows in size.
In one embodiment, the mapping that is generated or developed by one customer may be used by other customers, even when the other customers have a different mapping. The defined variables that are mapped by a first customer may be translated into the defined variables that are mapped by a second customer. The MIB files for a customer may improve scalability. In particular, the MIB files of multiple customers may be translated, such that the customers may communicate using the same network communication protocol. In one embodiment, a first customer merging its network system (with a first MIB mapping) with a second network system (with a different MIB mapping) may be translated so that both MIB mappings may be unified and the combined system will have a single mapping that communicates with all the equipment and IED's in both of the network systems.
The methods discussed above may be encoded in a signal bearing medium, a computer readable medium such as a memory, programmed within a device such as one or more integrated circuits, one or more processors or processed by a controller or a computer. If the methods are performed by software, the software may reside in a memory resident to or interfaced to a storage device, synchronizer, a communication interface, or non-volatile or volatile memory in communication with a transmitter. A circuit or electronic device designed to send data to another location. The memory may include an ordered listing of executable instructions for implementing logical functions. A logical function or any system element described may be implemented through optic circuitry, digital circuitry, through source code, through analog circuitry, through an analog source such as an analog electrical, audio, or video signal or a combination. The software may be embodied in any computer-readable or signal-bearing medium, for use by, or in connection with an instruction executable system, apparatus, or device. Such a system may include a computer-based system, a processor-containing system, or another system that may selectively fetch instructions from an instruction executable system, apparatus, or device that may also execute instructions.
A “computer-readable medium,” “machine readable medium,” “propagated-signal” medium, and/or “signal-bearing medium” may comprise any device that contains, stores, communicates, propagates, or transports software for use by or in connection with an instruction executable system, apparatus, or device. The machine-readable medium may selectively be, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. A non-exhaustive list of examples of a machine-readable medium would include: an electrical connection “electronic” having one or more wires, a portable magnetic or optical disk, a volatile memory such as a Random Access Memory “RAM” (electronic), a Read-Only Memory “ROM” (electronic), an Erasable Programmable Read-Only Memory (EPROM or Flash memory) (electronic), or an optical fiber (optical). A machine-readable medium may also include a tangible medium upon which software is printed, as the software may be electronically stored as an image or in another format (e.g., through an optical scan), then compiled, and/or interpreted or otherwise processed. The processed medium may then be stored in a computer and/or machine memory.
While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein.
In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
In an alternative embodiment, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems. One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.
In accordance with various embodiments of the present disclosure, the methods described herein may be implemented by software programs executable by a computer system. Further, in an exemplary, non-limited embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement one or more of the methods or functionality as described herein.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.
The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. While various embodiments of the invention have been described, it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible within the scope of the invention. Accordingly, the invention is not to be restricted except in light of the attached claims and their equivalents.
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11851471 US9270552B2 (en) | 2007-09-07 | 2007-09-07 | Energy monitoring system using network management protocols |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11851471 US9270552B2 (en) | 2007-09-07 | 2007-09-07 | Energy monitoring system using network management protocols |
EP20080800268 EP2186258A4 (en) | 2007-09-07 | 2008-09-04 | Energy monitoring system using network management protocols |
PCT/CA2008/001559 WO2009030027A1 (en) | 2007-09-07 | 2008-09-04 | Energy monitoring system using network management protocols |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090070447A1 true US20090070447A1 (en) | 2009-03-12 |
US9270552B2 true US9270552B2 (en) | 2016-02-23 |
Family
ID=40428392
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11851471 Active 2030-09-07 US9270552B2 (en) | 2007-09-07 | 2007-09-07 | Energy monitoring system using network management protocols |
Country Status (3)
Country | Link |
---|---|
US (1) | US9270552B2 (en) |
EP (1) | EP2186258A4 (en) |
WO (1) | WO2009030027A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110213871A1 (en) * | 2010-03-01 | 2011-09-01 | Interdigital Patent Holdings, Inc. | Machine-to-machine gateway architecture and functionality |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1981245A1 (en) * | 2007-04-13 | 2008-10-15 | Liconic Ag | Method and product for controlling laboratory equipment |
US20090187579A1 (en) * | 2008-01-20 | 2009-07-23 | Brancaccio Daniel S | System, Method and Product for Processing Utility Data |
JP4748174B2 (en) * | 2008-03-25 | 2011-08-17 | ブラザー工業株式会社 | Network device management apparatus and network device management program |
US8180867B2 (en) * | 2008-07-29 | 2012-05-15 | Schneider Electric USA, Inc. | Configuration management system for power monitoring and protection system devices |
US8255932B1 (en) * | 2008-12-17 | 2012-08-28 | Cisco Technology, Inc. | Application of an embedded instrumentation interface definition language |
US8565119B2 (en) * | 2009-04-14 | 2013-10-22 | Schweitzer Engineering Laboratories Inc | Network discovery and data transfer using SNMP in an electric power transmission or distribution system |
US8509101B2 (en) * | 2009-10-14 | 2013-08-13 | Schweitzer Engineering Laboratories Inc | Systems and methods for a configurable communication device |
US8261357B2 (en) * | 2009-10-14 | 2012-09-04 | Schweitzer Engineering Laboratories, Inc. | Systems and methods for license entitlement key distribution |
WO2011064671A3 (en) | 2009-11-26 | 2011-09-01 | Lg Electronics Inc. | Network system for a component |
EP2514142B1 (en) * | 2009-12-17 | 2015-10-14 | LG Electronics Inc. | Network system and method of controlling network system |
US8693353B2 (en) * | 2009-12-28 | 2014-04-08 | Schneider Electric USA, Inc. | Intelligent ethernet gateway system and method for optimizing serial communication networks |
KR101425699B1 (en) * | 2010-05-07 | 2014-08-01 | 엘에스산전 주식회사 | Remote Communication Method for Digital Protective Relay |
JP5925774B2 (en) * | 2010-07-30 | 2016-05-25 | アクセンチュア グローバル サービスィズ リミテッド | Intelligent core engine |
US8527748B2 (en) * | 2010-10-01 | 2013-09-03 | Schneider Electric USA, Inc. | System and method for hosting encrypted monitoring data |
US8760258B2 (en) | 2011-05-16 | 2014-06-24 | Robert Bosch Gmbh | Energy monitoring and management security system |
US9049104B2 (en) | 2011-07-19 | 2015-06-02 | Telefonaktiebolaget L M Ericsson (Publ) | Coordination of M2M device operation by M2M device managers in a LAN |
WO2014022960A1 (en) * | 2012-08-06 | 2014-02-13 | 华为技术有限公司 | Method, apparatus, and network management system for acquiring energy efficiency parameter of overlapped coverage network |
US8793767B2 (en) * | 2012-08-30 | 2014-07-29 | Schweitzer Engineering Laboratories Inc | Network access management via a secondary communication channel |
US9310863B2 (en) * | 2012-09-12 | 2016-04-12 | Ati Technologies Ulc | Multi-purpose power controller and method |
CN102869032B (en) * | 2012-09-21 | 2015-06-03 | 中兴通讯股份有限公司 | Device and method for monitoring and alarming power supply of base station |
CN103929732A (en) * | 2013-01-11 | 2014-07-16 | 中兴通讯股份有限公司 | Method for managing terminal peripheral and M2M gateway |
US9823640B2 (en) * | 2013-03-14 | 2017-11-21 | Control Technology Corporation | Networked programmable industrial controllers |
CN103683515B (en) * | 2013-12-30 | 2015-11-18 | 国家电网公司 | Distribution Network optimization based control method and technique mas |
FR3017007B1 (en) * | 2014-01-27 | 2017-08-04 | Schneider Electric Ind Sas | Electric Fuel System securisee |
US9705305B2 (en) * | 2014-04-29 | 2017-07-11 | Schweitzer Engineering Laboratories, Inc. | Resilient communication for an electric power delivery system |
US9870476B2 (en) | 2014-09-23 | 2018-01-16 | Accenture Global Services Limited | Industrial security agent platform |
CN104954225A (en) * | 2015-06-11 | 2015-09-30 | 滁州市西控电子有限公司 | Energy monitoring management system |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020010801A1 (en) * | 2000-04-21 | 2002-01-24 | Meagher Patrick S. | Server to third party serial gateway in a power control management system |
US20020046246A1 (en) * | 2000-04-19 | 2002-04-18 | Wright Peter Michael | Electronic communications in intelligent electronic devices |
US20020173927A1 (en) * | 2001-05-21 | 2002-11-21 | Benton Vandiver | System for testing of intelligent electronic devices with digital communications |
US6671635B1 (en) | 2001-02-23 | 2003-12-30 | Power Measurement Ltd. | Systems for improved monitoring accuracy of intelligent electronic devices |
US6751562B1 (en) | 2000-11-28 | 2004-06-15 | Power Measurement Ltd. | Communications architecture for intelligent electronic devices |
US20050149484A1 (en) * | 2001-05-25 | 2005-07-07 | Joshua Fox | Run-time architecture for enterprise integration with transformation generation |
US20050206530A1 (en) * | 2004-03-18 | 2005-09-22 | Cumming Daniel A | Solar powered radio frequency device within an energy sensor system |
US6961641B1 (en) | 1994-12-30 | 2005-11-01 | Power Measurement Ltd. | Intra-device communications architecture for managing electrical power distribution and consumption |
US7072779B2 (en) | 2002-12-23 | 2006-07-04 | Power Measurement Ltd. | Power management integrated circuit |
US7085824B2 (en) | 2001-02-23 | 2006-08-01 | Power Measurement Ltd. | Systems for in the field configuration of intelligent electronic devices |
US20060238339A1 (en) * | 2003-04-14 | 2006-10-26 | Michael Primm | Extensible Sensor Monitoring, Alert Processing and Notification system and Method |
US20060238932A1 (en) | 2005-01-14 | 2006-10-26 | Westbrock William B Jr | Branch circuit monitor system |
US20070100504A1 (en) * | 2005-10-21 | 2007-05-03 | Moxley Roy E | System and method for detecting power system conditions |
US7216043B2 (en) | 1997-02-12 | 2007-05-08 | Power Measurement Ltd. | Push communications architecture for intelligent electronic devices |
US20070245012A1 (en) * | 1996-07-23 | 2007-10-18 | Server Technology, Inc. | Remote power control system with tickle capability |
US20080075019A1 (en) * | 2006-09-27 | 2008-03-27 | Petras Charles E | Data Mapping and Sorting Method in Network Communication |
US20080232271A1 (en) * | 2007-03-19 | 2008-09-25 | Kazuki Onishi | Remote management system |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003319433A (en) * | 2002-04-19 | 2003-11-07 | Fujitsu Ltd | Monitor for monitoring installing position of communication apparatus and monitor system |
US20040039812A1 (en) * | 2002-08-22 | 2004-02-26 | Connelly Stephen P. | Method of collecting data from heterogeneous test and measurement device and apparatus using same |
JP2005234851A (en) * | 2004-02-19 | 2005-09-02 | Mitsubishi Electric Corp | Communication system, management apparatus, information collecting apparatus and communication method |
EP1976218A1 (en) * | 2007-03-30 | 2008-10-01 | ABB Technology AG | Method of configuring an intelligent electronic device |
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6961641B1 (en) | 1994-12-30 | 2005-11-01 | Power Measurement Ltd. | Intra-device communications architecture for managing electrical power distribution and consumption |
US20070245012A1 (en) * | 1996-07-23 | 2007-10-18 | Server Technology, Inc. | Remote power control system with tickle capability |
US7216043B2 (en) | 1997-02-12 | 2007-05-08 | Power Measurement Ltd. | Push communications architecture for intelligent electronic devices |
US20020046246A1 (en) * | 2000-04-19 | 2002-04-18 | Wright Peter Michael | Electronic communications in intelligent electronic devices |
US20020010801A1 (en) * | 2000-04-21 | 2002-01-24 | Meagher Patrick S. | Server to third party serial gateway in a power control management system |
US6751562B1 (en) | 2000-11-28 | 2004-06-15 | Power Measurement Ltd. | Communications architecture for intelligent electronic devices |
US6671635B1 (en) | 2001-02-23 | 2003-12-30 | Power Measurement Ltd. | Systems for improved monitoring accuracy of intelligent electronic devices |
US7085824B2 (en) | 2001-02-23 | 2006-08-01 | Power Measurement Ltd. | Systems for in the field configuration of intelligent electronic devices |
US20020173927A1 (en) * | 2001-05-21 | 2002-11-21 | Benton Vandiver | System for testing of intelligent electronic devices with digital communications |
US20050149484A1 (en) * | 2001-05-25 | 2005-07-07 | Joshua Fox | Run-time architecture for enterprise integration with transformation generation |
US7072779B2 (en) | 2002-12-23 | 2006-07-04 | Power Measurement Ltd. | Power management integrated circuit |
US20060238339A1 (en) * | 2003-04-14 | 2006-10-26 | Michael Primm | Extensible Sensor Monitoring, Alert Processing and Notification system and Method |
US20050206530A1 (en) * | 2004-03-18 | 2005-09-22 | Cumming Daniel A | Solar powered radio frequency device within an energy sensor system |
US20060238932A1 (en) | 2005-01-14 | 2006-10-26 | Westbrock William B Jr | Branch circuit monitor system |
US20070100504A1 (en) * | 2005-10-21 | 2007-05-03 | Moxley Roy E | System and method for detecting power system conditions |
US20080075019A1 (en) * | 2006-09-27 | 2008-03-27 | Petras Charles E | Data Mapping and Sorting Method in Network Communication |
US20080232271A1 (en) * | 2007-03-19 | 2008-09-25 | Kazuki Onishi | Remote management system |
Non-Patent Citations (16)
Title |
---|
"Automated Monitoring of Substation Equipment Performance and Maintenance Needs Using Synchronized Sampling"-Kezunovic et al, Texas A&M Univ., Sep. 2006. * |
Common management information protocol, 2 pages from, http://www.en.wikipedia.org on Sep. 4, 2007 10:58 a.m. |
Individual SNMP Trap Support, Cisco Systems, 8 pages. |
Next-generation power quality meters, Eaton Cutler-Hammer, www.eatonelectrical.com, 12 pages. |
PCT Search Report and Written Opinion dated Dec. 22, 2008, PCT/CA2008/001559, filed Sep. 4, 2008. |
Power Chain Management(TM) Eaton Power Xpert Architecture, Capabilities Brochure, Eaton Corp., Mar. 2007, at www.eaton.com, 14 pages. |
Power Chain Management™ Eaton Power Xpert Architecture, Capabilities Brochure, Eaton Corp., Mar. 2007, at www.eaton.com, 14 pages. |
Power Xpert Architecture, Eaton Corp., 3 pgs, at http://www.eaton.com/EatonCom/Markets/Electrical/Products/PowerQualityManagement/Powe rXpertArchitecture/index.htm, visited Jul. 27, 2007. |
Power Xpert Meters, Power Xpert® 4000/600/8000 Meter Series, 4 pgs, at http://www.eaton.com/EatonCom/Markets/Electrical/Products/PowerQualityManagement/Powe rXpertArchitecture/PowerXpertMeters/index.htm, visited Jul. 27, 2007. |
Quick Start Guide, Cutler-Hammer, Power Xpert(TM) 4000/6000/8000 Meter 14 pages. |
Quick Start Guide, Cutler-Hammer, Power Xpert™ 4000/6000/8000 Meter 14 pages. |
Remote Power Panel, Eaton Cutler Hammer, 2 pages. |
Simple Network Management Protocol, http://www.en.wikipedia.org, 10 pages, on Sep. 4, 2007 10:57 a.m. |
Simple Network Management Protocol, Internetworking Technologies Handbook, 12 pages. |
SNMP Tutorial Part 1: An Introduction to SNMP, 5 pages taken from http://www.dpstele.com on Sep. 4, 2007 10:55 a.m. |
Technology Backgrounder, SNMP Environment, 4 pages. |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110213871A1 (en) * | 2010-03-01 | 2011-09-01 | Interdigital Patent Holdings, Inc. | Machine-to-machine gateway architecture and functionality |
Also Published As
Publication number | Publication date | Type |
---|---|---|
WO2009030027A1 (en) | 2009-03-12 | application |
EP2186258A1 (en) | 2010-05-19 | application |
US20090070447A1 (en) | 2009-03-12 | application |
EP2186258A4 (en) | 2013-09-04 | application |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6801865B2 (en) | Meter monitoring and tamper protection system and method | |
US6671654B1 (en) | Apparatus and method for measuring and reporting the reliability of a power distribution system | |
US7304586B2 (en) | On-line web accessed energy meter | |
US8238263B2 (en) | Network status detection | |
US20060007016A1 (en) | Utilities and communication integrator | |
US20090234512A1 (en) | Power distribution, management, and monitoring systems and methods | |
US20080219239A1 (en) | Policy-based utility networking | |
EP1976218A1 (en) | Method of configuring an intelligent electronic device | |
US6611773B2 (en) | Apparatus and method for measuring and reporting the reliability of a power distribution system with improved accuracy | |
Zhang et al. | Wide-area frequency monitoring network (FNET) architecture and applications | |
US20140025321A1 (en) | System and method for performing data transfers in an intelligent electronic device | |
US20130031201A1 (en) | Intelligent electronic device communication solutions for network topologies | |
US20120253540A1 (en) | Energy grid device commissioning method and system | |
US20090187344A1 (en) | System, Method, and Computer Program Product for Analyzing Power Grid Data | |
Rowe et al. | Sensor Andrew: Large-scale campus-wide sensing and actuation | |
US6944555B2 (en) | Communications architecture for intelligent electronic devices | |
US20110208366A1 (en) | Utility grid command filter system | |
US6961641B1 (en) | Intra-device communications architecture for managing electrical power distribution and consumption | |
US20070222636A1 (en) | System and method for a networked utility meter | |
US20130204450A1 (en) | Systems and methods for collecting, analyzing, billing, and reporting data from intelligent electronic devices | |
US8160824B2 (en) | Intelligent electronic device with enhanced power quality monitoring and communication capabilities | |
US20090281673A1 (en) | Method and system for managing a power grid | |
US20100328849A1 (en) | Power distribution apparatus with input and output power sensing and method of use | |
US20090281679A1 (en) | Intelligent monitoring of an electrical utility grid | |
Lien et al. | Power monitoring and control for electric home appliances based on power line communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: POWER MEASUREMENT LTD., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JUBINVILLE, JESSE;TEACHMAN, MIKE;ANDERSON, DAVID;REEL/FRAME:019796/0956 Effective date: 20070906 |