CN103038606B - Intelligent core engine - Google Patents

Intelligent core engine Download PDF

Info

Publication number
CN103038606B
CN103038606B CN201180037442.8A CN201180037442A CN103038606B CN 103038606 B CN103038606 B CN 103038606B CN 201180037442 A CN201180037442 A CN 201180037442A CN 103038606 B CN103038606 B CN 103038606B
Authority
CN
China
Prior art keywords
management system
data
power network
network management
central power
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
Application number
CN201180037442.8A
Other languages
Chinese (zh)
Other versions
CN103038606A (en
Inventor
R·多德里
P·G·英格尔
H·R·多克
M·拉尔瓦尼
V·M·玛哈简
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Accenture Global Services GmbH
Original Assignee
Accenture Global Services GmbH
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Accenture Global Services GmbH filed Critical Accenture Global Services GmbH
Publication of CN103038606A publication Critical patent/CN103038606A/en
Application granted granted Critical
Publication of CN103038606B publication Critical patent/CN103038606B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J13/00—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network
    • H02J13/00006—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network characterised by information or instructions transport means between the monitoring, controlling or managing units and monitored, controlled or operated power network element or electrical equipment
    • H02J13/00028—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network characterised by information or instructions transport means between the monitoring, controlling or managing units and monitored, controlled or operated power network element or electrical equipment involving the use of Internet protocols
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J13/00—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network
    • H02J13/00032—Systems characterised by the controlled or operated power network elements or equipment, the power network elements or equipment not otherwise provided for
    • H02J13/00034—Systems characterised by the controlled or operated power network elements or equipment, the power network elements or equipment not otherwise provided for the elements or equipment being or involving an electric power substation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
    • G01D2204/00—Indexing scheme relating to details of tariff-metering apparatus
    • G01D2204/40—Networks; Topology
    • G01D2204/45—Utility meters networked together within a single building
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2209/00—Arrangements in telecontrol or telemetry systems
    • H04Q2209/60—Arrangements in telecontrol or telemetry systems for transmitting utility meters data, i.e. transmission of data from the reader of the utility meter
    • 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
    • Y02B90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
    • Y02B90/20—Smart grids as enabling technology in buildings sector
    • 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
    • Y04S20/00—Management or operation of end-user stationary applications or the last stages of power distribution; Controlling, monitoring or operating thereof
    • Y04S20/30—Smart metering, e.g. specially adapted for remote reading

Abstract

Disclose the central authority for such as power utility system.Central authority is with multiple meter data management system and communicate with multiple head-end system, and this meter data management system generates order, and head-end system communicates with one or more instrument (such as one or more intelligent instrument).Central authority comprises gateway layer and core layer.Gateway layer comprises multiple input connector routine to communicate with each in multiple out connector routine with described multiple origin system, to communicate with each in described multiple goal systems.Core layer comprises multiple core adapter, and core adapter performs the conversion one to one from the described multiple meter data management system to the communication of described multiple head-end system generating order.

Description

Intelligent core engine
comparatively early the quoting of related application
This application claims the right of priority of the applying date of the Indian patent application 2171/CHE/2010 that on July 30th, 2010 submits to, it is openly integrally attached to herein by reference.
Technical field
1. the field of invention
A kind of system and method for managing industrial network of relate generally to of the present invention, and relate more particularly to a kind of for collecting data from the different sections of power network and/or analyzing collected/route data so that the system and method for managing power net to its route data.
Background technology
2. correlation technique
Power network can comprise one or all in the following: generating, transmission and disttrbution.Power house can be used to produce electricity, such as coal-burning power plant, nuclear power station etc.For efficiency object, the electric power of generation is incrementally increased to very high voltage (such as 345K volt) and is transmitted by transmission line.Transmission line can through-put power over long distances, and such as across state circle or across international boundary, until it arrives its wholesale client, this wholesale client can be the company having local distribution network.Transmission line can stop at transmission transformer station (transmissionsubstation) place, and very high voltage progressively can be reduced to medium voltage (such as 138K volt) by this transmission transformer station.From transmission transformer station, less transmission line (such as secondary transmission line) transmits medium voltage to distribution substation (distributionsubstation).At distribution substation place, again medium voltage progressively can be reduced to " middle pressure " (such as from 4K volt to 23K volt).One or more feed circuit can send from distribution substation.Such as, four to ten feed circuits can send from distribution substation.Feed circuit be comprise 4 wires 3 circuitry phases (three wires be used for 3 mutually in each and a wire is used for the neutral line).Can on the ground (on electric pole) or at provided underground feed circuit.Can use substation transformer periodically by the voltage tap on feed circuit out, this makes voltage progressively be reduced to consumption voltage (such as 120V) from " middle pressure ".Then consumption voltage can be used by consumer.
One or more Utilities Electric Co. can managing power net, comprises the management fault relevant with power network, maintenance and upgrading.But the management of power network is usually poor efficiency and costliness.Such as, the Utilities Electric Co. managing local power distribution network can manage in feed circuit or divide the fault be called the circuit of lateral circuit of out branch from feed circuit.The management of local power distribution network usually depends on the call that comes from consumer when there is power-off or depends on field personnel analyzes local power distribution network.
Utilities Electric Co. has attempted the digital technology that use is sometimes referred to as " intelligent grid " and has been upgraded by power network.Such as, more intelligent instrument (being sometimes referred to as " intelligent instrument ") is a kind of senior instrument identifying consumption than conventional instrument in more detail.Then this information for supervision and billing purpose (remote measurement), can be sent back to local utility company via certain network by this intelligent instrument.
Even if there are these in power network progressive, for power network analysis with communicate be still complicated.Utilities Electric Co. can have multiple system, such as (it can analyze load and share energy management system, and correspondingly issue an order), outage management system (it can analyze power-off, and correspondingly issue an order), demand response system, charge system etc.These multiple systems can be mutually mutual, makes the management of power network become complicated.In addition, these multiple systems can serve as multiple sources of the various target issue an orders to power network.Described multiple system usually communicates in a different format, makes communication become complicated.Therefore, need the analysis of the multiple systems in managing power net better and communicate.
Summary of the invention
Disclose the central authority for the such as system of power utility system.Central authority is with multiple meter data management system and communicate with multiple head-end system (headendsystem), this meter data management system generates order, and head-end system communicates with one or more instrument (such as one or more intelligent instrument).Comprise central authority and an example that can manage the framework of intelligent grid is intelligent network data enterprise (hereinafter referred to as INDE) frame of reference.
Central authority comprises gateway layer and core layer.Gateway layer comprises multiple input connector routine and multiple out connector routine.Described multiple input connector routine comprises at least one the independent input connector routine for communicating with each in multiple origin system, and described multiple origin system sends data (such as sending the meter data management system of connect/disconnect order from central authority) to central authority.Described multiple out connector routine comprises at least one the independent out connector routine communicated with each in goal systems, and described multiple goal systems receives the data (such as sending the head-end system of connect/disconnect order from central authority) sent from central authority.
The core layer of central authority comprises multiple core adapter, and this core adapter performs the conversion one to one from the multiple meter data management system to the communication of multiple head-end system producing order.
After studying following figure and detailed description, other system, method, feature and advantage will be or will become and it will be apparent to those skilled in the art that.Intention be this type of spare systems all, method, feature and advantage be included in this describe in, within the scope of the invention and the protection of the claim that is subject to enclosing.
Accompanying drawing explanation
Fig. 1 illustrates the example of senior INDE framework.
Fig. 2 illustrates the high level flow chart between MDM system, INDE core and head-end system.
Fig. 3 is the example of the detail flowchart for disconnecting or reconnect request.
Fig. 4 is the example of the detail flowchart for periodic meter reading.
Fig. 5 is the example for the detail flowchart of (OnDemand) meter read request as required.
Fig. 6 A-6C is used for the block scheme of an example of the general frame of power network.
Embodiment
In the mode of general introduction, following preferred embodiment relates to the method and system for managing power net.Some aspect relates to structure and/or the Functional Capability of the central management of power network.Intelligent network data enterprise (INDE) is intelligent grid integrated platform, as in U.S. Patent Application No. 12/378, in 102 (announcing as U.S. Patent Application No. 2009-0281674A1), in U.S. Patent Application No. 12/378, 091 (as U.S. Patent Application No. 2009-0281673A1 announce) and PCT number of patent application PCT/US2009/000888 (as WO2009/136975 announce) disclosed in, INDE provides highly scalable, configurable application integration solution, and there is the built-in intelligent grid business procedure of core, such as senior metering framework, demand response, fault and power-off intelligence, transformer station analyzes, it can be used by utility company widely.
INDE framework is divided into core and gateway layer, INDE core provides some to serve, such as Intelligent Service route, synchronous and asynchronous service exhalation, data transformation and auditability, and INDE gateway provides the service of application connector, and it can utilize widely used industrial communication protocol to build.Such as, INDE gateway can comprise multiple input connector routine and multiple out connector routine, described multiple input connector routine comprises the independent input connector routine for communicating with each in multiple instrument data managing (MDM) system, and described multiple out connector routine comprises the independent out connector routine for communicating with each in described multiple head-end system.
INDE core provides multiple benefit with being separated of INDE gateway, includes but not limited to, INDE framework is to known and the better adaptation of unknown system, better scalability and better security.Disclose the example of high level architecture 50 in FIG.As shown in fig. 1, INDE core 50 is separated with INDE gateway 60.In addition, INDE gateway 60 provides INDE core 50 and the interface between origin system (such as origin system 1 (65) and origin system 2 (70)) and goal systems (such as goal systems (75) and goal systems 2 (80)).Fig. 1 illustrates two origin systems and two goal systems.But, it is expected to less or more origin system and goal systems.As hereafter discussed in more detail, INDE gateway is comprising the connector layer various source and target system connected.
Origin system sends for the information request of taking action or order, and goal systems responds information request or by order action.An example of order can comprise and disconnects/reconnect action for instrument, and it can be produced by MDM system.MDM system can comprise for the one or more function in the following: Data Collection and communication system (comprising automatic instrument to read) and senior measurement basis facility (AMI); And instrument data managing and related software application.In typical utility system, multiple MDM system can be there is, make one in multiple different MDM system can serve as origin system.The example of business MDM system comprises LodeStar and Itron.Further, different MDM systems can stem from the different sellers and follow different forms.Like this, the data in order can comprise similar information (such as the ID# of intelligent instrument and the order in order to connect/disconnect), but take different forms.
Such as, can send order based in multiple different procotol, this procotol is file transfer protocol (FTP) (FTP), java messenger service (JMS) and HTML (Hypertext Markup Language) (HTTP) such as.FTP is the computer network with standard network protocol that can be used for being copied to by file main frame by the network based on TCP/IP of such as the Internet another.FTP sets up on client-server architecture, and utilizes the independent control between client and server application program and data cube computation, which solves the problem of different terminals host configuration (that is, operating system, filename).FTP is used to based on the password authentication of user or with anonymous user access.JMSAPI is Java Message Oriented Middleware (MOM) API for sending message between two or more clients.JMS is a part for Java platform, enterprise version, and is defined by the specification developed according to the Java community process as JSR914.It sends standard for the message allowing application program parts and create, send, receive and read message based on Java2 platform, enterprise version (J2EE).It allows communication between the different parts of distributed application program by loosely coupling, reliable and asynchronous.Finally, HTTP is for application layer protocol that is distributed, cooperative Hypermedia Information System.
This order (sending via any one in different network protocol) can be routed to head-end system, it disconnects/reconnects action to the instrument transmission be arranged in HAN (HAN).Again, in typical utility system, multiple head-end system can be there is, such as Secure or Current, make one in multiple different head-end system can serve as goal systems.
Different head-end system can with different types of meter communication.Such as, based on the following, instrument can be classified: industrial instrument, family's instrument, house instrument, vehicle correlate meter etc.Different types of instrument can be handled by different head-end system (such as industrial head-end system, house head-end system and vehicle head-end system).Order is sent to each head-end system, and it sends connect/disconnect order to intelligent instrument then.
Various head-end system can be different in many aspects, comprise different forms, dissimilar be managed load (such as, high density head-end system contrast low-density head-end system).As discussed in more detail, multiple output connection can serve used different head-end system.
Can instrument order be published in bus, one such as in bus disclosed in Fig. 6 A-6C.Such as, multiple subscribers of " publisher " and order can be there are.As another example, multiple publisher and multiple subscriber can be there is.Based on the design, there is the restriction about particular technology.Further, the design makes it possible to be suitable for any publisher or subscriber.As relative to Fig. 3 discuss, do not need publisher and subscriber to know " common format ".Alternatively, INDE gateway can make communication be suitable for the combination of each publisher/subscriber, this eliminates the needs at least common format of certain type.
In addition, as current disclosed publisher-subscriber's model can run in many ways.Such as, publisher-subscriber's model can operate as " propelling movement ", wherein, and publisher's " propelling movement " data (such as order) and subscriber " pulls " data.As another example, publisher-subscriber's model makes it possible to " propelling movement " and " pulling " that realize for publisher and subscriber.Especially, the one or more connectors in INDE gateway can be configured to " pulling " data and/or " propelling movement " data.Such as, GMS connector (or FTP connector) can be configured to " pull " data from origin system.Or, the connector of in the connector in INDE gateway can be configured to network service, make origin system can call network service and propelling data.In addition, input connector and out connector can side by side be supported push and pull method.
Another example of order can comprise instrument as required and read.The MDM system of such as LodeStar, Itron can send in the multiple different head-end system of such as Secure or Current the request being used for meter information.
Origin system can also send information to goal systems.One of them example is that periodic meter reads.The head-end system of such as Secure or Current can send instrumented data in multiple MDM system.
Like this, the design can overcome and makes the format of order and routing variable obtain complicated multiple origin system and multiple goal systems.INDE gateway makes it possible to realize complicated route/format its being separated and designing in two with INDE core, and allows to be adapted to different sources or goal systems.For serving as the MDM system of origin system and serve as the head-end system of goal systems, INDE gateway can adjust connector (such as with each input connector communicated in described multiple origin system and with each out connector communicated in described multiple goal systems).Make, INDE gateway can comprise for the multiple input connectors of each in described multiple MDM system, and can comprise the multiple out connectors for each in described multiple head-end system, as discussed in more detail in Fig. 3 and 5.For serving as the MDM system of origin system and serve as the MDM system of goal systems, INDE gateway can adjust connector (such as with each input connector communicated in described multiple origin system and with each out connector communicated in described multiple goal systems).Make, INDE gateway can comprise the multiple input connectors for each in described multiple head-end system, and can comprise for the multiple out connectors of each in described multiple MDM system, as discussed in more detail in the diagram.And, for following system, (wherein MDM system is served as origin system in portion of time and is served as goal systems in portion of time, and wherein head-end system is served as origin system in portion of time and is served as goal systems in portion of time), INDE gateway can be included in Fig. 3 and 5 open and disclosed two connector types in the diagram.More specifically, INDE gateway can comprise for the multiple input connector of each in described multiple MDM system and multiple out connector, and multiple input connector that can comprise for each in described multiple head-end system and multiple out connector.
INDE core similarly can adjust its operation, such as adjusts its core adapter, as hereafter discussed in more detail.Such as, for serving as the MDM system of origin system and serving as the head-end system of goal systems, INDE core can comprise the core adapter being transformed into each head-end system from each MDM system.For example, in the system with a MDM system and the 2nd MDM system and the first head-end system and the second head-end system, four core adapters can be there are and change one to one to perform.Especially, following core adapter can be there is: from the conversion of MDM system to the first head-end system; From the conversion of MDM system to the second head-end system; From the conversion of the 2nd MDM system to the first head-end system; And from the conversion of the 2nd MDM system to the second head-end system.
As another example, for serving as the head-end system of origin system and serving as the MDM system of goal systems, INDE core can comprise the core adapter being transformed into each MDM system from each head-end system.Such as, in the system with a MDM system and the 2nd MDM system and a MDM system and the 2nd MDM system, four core adapters can be there are and change one to one to perform.Especially, following core adapter can be there is: from the first head-end system to the conversion of a MDM system; From the first head-end system to the conversion of the 2nd MDM system; From the second head-end system to the conversion of a MDM system; And from the second head-end system to the conversion of the 2nd MDM head-end system.
And, for following system, (wherein MDM system is served as origin system in portion of time and is served as goal systems in portion of time, and wherein head-end system is served as origin system in portion of time and is served as goal systems in portion of time), INDE core can be included in disclosed in Fig. 3 and 5 and disclosed two type of adapters in the diagram.More specifically, INDE core can be from each conversion one to one to each in described multiple head-end system described multiple MDM system, and from each described multiple head-end system to the conversion one to one of each in described multiple MDM system.
With reference to figure 2, show and ask relevant high level flow chart with disconnecting or reconnect.MDM system sends to INDE core and disconnects or reconnect request.The request of INDE core accepts, conversion requests, and by converted request forward in head-end system, as discussed in more detail below.Head-end system receiving conversion request, performs institute's request action, and sends confirmation to INDE core.The confirmation of receipt then of INDE core, conversion confirms, and converted confirmation is forwarded to MDM system.
With reference to figure 3, show and ask the relevant detail flowchart for 7 layers with disconnecting or reconnect.For disconnecting/reconnecting request, origin system is MDM system.As discussed above, the business example of MDM system includes but not limited to LodeStar and Itron.Similarly, for disconnecting/reconnecting request, goal systems is head-end system.As discussed above, public utility system can have one in the head-end system of multiple type, such as Secure and Current.
Derive/import connector service layer and comprise the connector being connected to one or more origin system and one or more goal systems.These connections can by being used to specify and can the creating by effective language (such as business procedure effective language (BPEL)) of mutual any type of Web service.
As shown in Figure 3, derive/import connector service layer and there is the input connector (such as IPConnector1 to IPConnector6) and out connector (such as OPConnector1 to OPConnector6) that are respectively used to origin system and goal systems.IPC_DisconnectReconnect_LodeStarFTP (shown in IPConnector1) can be used, carry out the FTP position acquisition request from LodeStar system, and send it to connector service interface (INDE core).IPC_DisconnectReconnect_LodeStar_HTTP (shown in IPConnector3) can be used, obtain request on the http protocol from LodeStar system, and be sent to connector service interface (INDE core).IPC_DisconnectReconnect_LodeStar_JMS (shown in IPConnector2) can be used, come to obtain request from the JMS queue of LodeStar system, and send it to connector service interface (INDE core).Similarly, IPC_DisconnectReconnect_Itron_FTP (shown in IPConnector4) can be used, carry out the FTP position acquisition request from Itron system, and send it to connector service interface (INDE core).IPC_DisconnectReconnect_Itron_HTTP (shown in IPConnector6) can be used, obtain request on the http protocol from Itron service system, and send it to connector service interface (INDE core).IPC_DisconnectReconnect_Itron_JMS (shown in IPConnector5) can be used, come to obtain request from the JMS queue of Itron system, and send it to connector service interface (INDE core).
OPC_DisconnectReconnect_Secure_FTP (shown in OPConnector2) disconnects/reconnects request msg from OSB connector service reception, and sends it to Secure system in configured FTP position.OPC_DisconnectReconnect_Secure_HTTP (shown in OPConnector1) disconnects/reconnects request from OSB connector service reception, and sends it to Secure system by HTTP.OPC_DisconnectReconnect_Secure_JMS (shown in OPConnector3) disconnects/reconnects request from OSB connector service reception, and sends it to Secure system in JMS queue.Similarly, OPC_DisconnectReconnect_Current_FTP (shown in OPConnector5) disconnects/reconnects request msg from OSB connector service reception, and sends it to Current system in configured FTP position.OPC_DisconnectReconnect_Current_HTTP (shown in OPConnector4) disconnects/reconnects request from OSB connector service reception, and sends it to Current system by HTTP.OPC_DisconnectReconnect_Current_JMS (shown in OPConnector6) disconnects/reconnects request from OSB connector service reception, and sends it to Current system in JMS queue.
As shown in Figure 3, for each terminal system (comprising origin system and goal systems), derive/import the connector that connector service layer can provide multiple type.Such as, Fig. 3 illustrates three different connectors that derivation/importing connector service layer comprises support three different agreements, i.e. HTTP, FTP and JMS.In this interface, MDM system can send file via the agreement of in multiple different agreement.Depicted in figure 3 in example, MDM system sends file via File Transfer Protocol.Therefore, in the mode of fading out, other two connectors are shown.Further, depicted in figure 3 in example, goal systems (goal systems 1 (Current)) expects the data of HTTP form.Therefore, be highlighted the OPConnector4 using Http, and show other connectors in the mode of fading out.These connectors can be used in the data structure checking the input data received.When making a mistake, its call error handler service.To reside in INDE gateway owing to deriving/importing the function of connector service layer and to be separated with INDE core, thus derive/import connector service layer can according to client requirements in a plurality of ways in one configure or adjust.
Connector service interface (INDE core) layer comprises the core component calling OSB service.When making a mistake, its call error process is served.Owing to designing the reason of (INDE core component is separated with INDE gateway), do not need to revise connector service interface (INDE core) layer based on client requirements.
OSB (INDE core) layer reference " lookup.config " file is to judge the proper transformation based on terminal system.After transformation, data are sent to distributor by OSBINDE core layer.Distributor is distributed asynchronously and will be sent to the data of goal systems.When making a mistake, its call error handler service.
OSB (INDE core) layer comprises OSB core component, and it comprises agency service with the message format of based target system to perform data transformation.PS_AMI_DisconnectReconnect can comprise agency service, it accepts input from connector service interface (INDE core), and arranges at least one routing parameter (such as arriving the route header of the input request of " disconnect/reconnect ").When asking, routing parameter is passed to PS_Foundation_TransformAndDispatch_Sync by PS_AMI_DisconnectReconnect further.When asking, routing parameter is passed to connector service interface (INDE core) by PS_AMI_DisconnectReconnect.
PS_Foundation_TransformAndDispatch_Sync can comprise agency service, and it receives request from PS_AMI_ConnectDisconnect and performs conversion based on Request routing header and AMI_Lookup.config.This conversion can comprise such as LodeStar to head end, head end to Itron etc.Transform data can be sent to PS_Foundation_SynchronousRouter together together with such as one or more header (such as two headers, namely for " routingservice " and " invokingoperation " of the dynamic routing activity in the router of PS_Foundation_SynchronousRouter).
PS_Foundation_SynchronousRouter is from user's header retrieval " routingservice " name arranged among PS_Foundation_TransformAndDispatch_Sync and " invokingoperation " name.Then PS_FoundationSynchronous_Router is dynamically routed to the business service as specified in routingservice header.
OSB (INDE core) layer comprises one or more INDE core adapter.As shown in Figure 3, list for not homologous system to the INDE core adapter of different target system changeover.Especially, Fig. 3 illustrate as Srcl_to_tgtl.xq, convert from the XQuery of origin system 1 to goal systems 1.Specific XQuery is selected to convert based on AMI_Lookup.conFig.Such as, LodeStar_to_Secure.xq is the conversion from LodeStar request format to Secure request format.Secure to LodeStar.xq is the conversion from Secure response format to LodeStar response format.Itron_To_Secure.xq is the conversion from Itron request format to Secure request format.Secure_To_Itron.xq is the conversion from Secure response format to Itron response format.LodeStar_To_Current is the conversion from LodeStar request format to Current request format.Current_To_LodeStar is the conversion from Current response format to LodeStar response format.Itron_To_Current is the conversion from Itron request format to Current request format.Current_To_Itron.xq is the conversion from Current response format to Itron response format.Except never homologous system to the conversion of different target system, except INDE core, the self-defined core adapter for additional transformations can be comprised.Such as, CustomXquery_Req.xq can comprise request Xquery file, and it performs from the mapping one to one inputing to output, and can develop for IDNE extension layer.CustomXquery_Res.xq can comprise response Xquery file, and it carries out the mapping one to one from inputing to output, and can develop for IDNE extension layer.
OSB connector service (INDE gateway) layer comprises OSB business service.This layer receives data from distributor and sends it to out connector (such as OPConnector1 to OPConnector6).As described in figure 3, there is a business service in each out connector.Such as, OSB connector service (INDE gateway) comprises BS_AMI_DisconnectReconnect_Secure_FTP, and it can comprise from distributor receipt of call (according to message header) and call the business service of OPC_DisconnectReconnect_Secure_FTP (deriving/importing description connector service (INDE gateway)).BS_AMI_DisconnectReconnect_Secure_HTTP can comprise from distributor receipt of call (according to message header) and call the business service of OPC_DisconnectReconnect_Secure_HTTP (deriving/importing description connector service (INDE gateway)).BS_AMI_DisconnectReconnect_Secure_JMS is from distributor receipt of call (according to message header) and calls the business service of OPC_DisconnectReconnect_Secure_JMS (deriving/importing description connector service (INDE gateway)).BS_AMI_DisconnectReconnect_Current_FTP is from distributor receipt of call (according to message header) and calls the business service of OPC_DisconnectReconnect_Current_FTP (deriving/importing description connector service (INDE gateway)).BS_AMI_DisconnectReconnect_Current_HTTP is from distributor receipt of call (according to message header) and calls the business service of OPC_DisconnectReconnect_Current_HTTP (deriving/importing description connector service (INDE gateway)).BS_AMI_DisconnectReconnect_Current_JMS is from distributor receipt of call (according to message header) and calls the business service of OPC_DisconnectReconnect_Current_JMS (deriving/importing description connector service (INDE gateway)).Finally, BS_AMI_DisconnectReconnect_Extn can call the out connector (such as OPConnector4) for remote data base (DB), and it can be extension layer database.
OSB (INDE expansion) layer utilizes unknown message format to provide self-defined conversion to terminal system.This ability can be connected to remote data base, as shown in FIG. 3.PS_AMI_DisconnectReconnect_Extn can comprise the agency service from OSB (INDE expansion) layer.PS_AMI_DisconnectReconnect_Extn can apply multiple queries, such as two self-defined Xqueries, and it is designed to the query set of XML data.Two self-defined Xqueries may be used for request and for response.Such as, conversion requests can be sent to the business service of extension layer by application request Xquery, PS_AMI_DisconnectReconnect_Extn, such as, BS_AMI_DisconnectReconnect_Extn.
Error handler service can comprise can by other process transfers in different layers to process the single process of various exception.
Fig. 3 illustrates the example of flow process.In step 1 place, derive importing connector service (INDE gateway) and disconnect by the MDM system acceptance of File Transfer Protocol from such as origin system 1 or origin system 2 or reconnect request.In step 2 place, this request is forwarded to connector service interface (INDE core) by IPConnector.In step 3 place, connector service interface (INDE core) calls OSB (INDE core).In step 4 place, OSB (INDE core) performs and searches.In step 5 place, OSB (INDE core) converts by using INDE core adapter according to target head-end system.In step 6 place, OSB (INDE core) is distributed to OSB connector service (INDE gateway).In step 7 place, transmission is sent to derivation/importing connector service (INDE gateway) by the service of OSB connector.In step 8 place, derive/import connector service (INDE gateway) and send it to head-end system, such as Secure or Current, with perform an action (such as disconnect or reconnect).After successfully disconnecting/reconnecting, to be sent in the mode contrary with MDM system by all said process and respond (step 7 is to step 1).
Fig. 4 illustrates and reads relevant detail flowchart with periodic meter.In this case, origin system comprises one in head-end system, such as Current or Secure, and goal systems comprises one in MDM system, such as LodeStar or Itron.
Be similar to Fig. 3, derivation/importing connector service (INDE gateway) layer comprises the different routines for dissimilar origin system and different-format at input layer, such as IPC_PeriodicMeterRead_Secure_Http, IPC_PeriodicMeterRead_Secure_JMS, IPC_PeriodicMeterRead_Secure_FTP, IPC_PeriodicMeterRead_Current_Http, IPC_PeriodicMeterRead_Current_JMS and IPC_PeriodicMeterRead_Current_FTP.In addition, derivation/importing connector service (INDE gateway) layer comprises the different routines for dissimilar goal systems and different-format at outgoing side, such as OPC_PeriodicMeterRead_LodeStar_Http, OPC_PeriodicMeterRead_LodeStar_JMS, OPC_PeriodicMeterRead_LodeStar_FTP, OPC_PeriodicMeterRead_Itron_Http, OPC_PeriodicMeterRead_Itron_JMS and OPC_PeriodicMeterRead_Itron_FTP.
Connection Service interface (IDNE core) layer receives and inputs from derivation/importing connector service (INDE gateway) layer and call OSB (INDE core).Particularly, BP_AMI_PeriodicMeterRead calls OSB, checks whether to there is synchronous mark.If existed, then determine whether there is repeated plant ID.If there is no, then INDE database (DB) is upgraded by device id being inserted INDEDB.
OSB (INDE core) layer in Fig. 4 and OSB connector service (INDE gateway) are served (INDE gateway) with OSB (INDE core) layer discussed in 3 and OSB connector and are operated similarly.
Fig. 5 illustrates and reads relevant detail flowchart with instrument as required.In this case, origin system comprises one (such as LodeStar or Itron) in MDM system, and goal systems comprises one (such as Current or Secure) in head-end system.
Fig. 6 A-6C is used for the block scheme of an example of the general frame of power network.The framework comprising the INDE core 55 combined with INDE gateway 60 makes it possible to realize the function that possibility is important for intelligent grid, and can comprise: (1) data-gathering process; (2) Data classification and time-continuing process; And (3) observability process.As hereafter discussed in more detail, using these processes to allow people's " observation " electrical network, analyzing data and deriving the information about electrical network.
The framework described in Fig. 6 A-6C is only for illustrated object, and can serve as reference model, and it provides the end of intelligent grid data to holding collection, transmission, storing and management; It can also provide integrated in public utilities process and system of analysis and analysis management and the former.Therefore, the framework of enterprise-wide can be regarded as.The operational administrative of such as electrical network itself and some element of aspect are discussed in more detail below.
The framework described in Fig. 6 A-6C can comprise nearly four data and Integration Bus: (1) height sensors data bus 146 (it can comprise operation and non-operational data); (2) specific event process bus 147 (it can comprise event data); (3) operate services bus 130 (it may be used for providing information about intelligent grid to public utilities back office application posts program); And (4) are for the ESB (showing in Fig. 6 A-6C for the enterprise's the integration environment bus 114 for serving enterprise IT115) of Back office IT system.Independent data bus can be realized in one or more mode.Such as, two or more in the data bus of such as height sensors data bus 146 and event handling bus 147 can be the different sections in individual data bus.Particularly, bus can have segmental structure or platform.As hereafter discussed in more detail, the hardware of such as one or more switch and/or the next different section routing of data at data bus of software can used.
As another example, two or more in data bus can in independent bus, with regard to the hardware needed for independent bus transmitting data, and such as physical bus separately.Particularly, each bus can comprise separated cable.In addition, some or all independent buses can be same types.Such as, one or more in bus can comprise LAN (Local Area Network) (LAN), such as by the Ethernet of unmasked twisted-pair cable and Wi-Fi as hereafter discussed in more detail, the hardware of such as router and/or the next bus routing of data among different physical bus of software can used.
As another example, two or more in bus can in the different sections in individual data structure, and one or more bus can on independent physical bus.Particularly, height sensors data bus 146 and event handling bus 147 can be difference short in individual data bus, and in the bus that enterprise's the integration environment bus 114 can be separated physically.
Although Fig. 6 A-6C depicts four buses, the bus of less or more number can be used to carry the data of four listed types.Such as, single non-segmented bus can be used to transmit sensing data and event handling data (what make bus adds up to three), as discussed below.Further, system can operate when not having operate services bus 130 and/or enterprise's the integration environment bus 114.
IT environment can be SOA compatibility.Service-Oriented Architecture Based (SOA) is for being encapsulated as the computer system architecture style of the business procedure of service running through in its life cycle to create and use.SOA also defines and provides IT infrastructure exchange data to allow different application programs and participate in business procedure.However, the use of SOA and ESB is optional.
The figure shows the different elements in general frame, such as the following: (1) INDE core 55; (2) INDE transformer station 180; And (3) INDE equipment 188.This division of element in general frame is for diagram object.Other divisions of element can be used.INDE framework can be used for supporting the distributed and centralized approach of electrical network intelligence, and is used to provide the mechanism for the treatment of extensive embodiment.
INDE frame of reference is an example of the Technical Architecture that can realize.Such as, it can be the example of first framework, is used to provide the starting point of the particular technology framework for developing any number, each for a public utilities solution, as discussed below.Therefore, can comprise for specific utility particular solution one in the element in INDE frame of reference, some or all.Further, INDE frame of reference can be provided for the standardization starting point of solution development.Hereafter discussed is the method for particular technology framework for determining particular power net.
INDE frame of reference can be the framework of enterprise-wide.The end that its object can be to provide for electric network data manages with these to the integrated framework in public utility system and process to end.Because intelligent power grid technology affects each aspect of utility service process, so people should note not only in electrical network, operation and client (customerpremise) level place but also the effect at Back office and enterprise level place.Therefore, INDE frame of reference can and really with reference to enterprise level SOA, such as, to support SOA environment for interface object.This should be considered as public utilities must can build with use intelligent grid before its existing IT context conversion become the requirement of SOA.ESB is the useful mechanism for promoting IT integrated, but be not to realize intelligent grid solution remainder required by.Discussion hereafter concentrates on the different parts of INDE intelligent grid element.
INDE parts group
As discussed above, the different parts in IDNE frame of reference can comprise such as: (1) INDE core 55; (2) INDE transformer station 180; And (3) INDE equipment 188.
INDE core 55 is the parts of the INDE frame of reference that may reside in operational control center, as shown in Fig. 6 A-6C.INDE core 55 can comprise the uniform data framework that stores for electric network data and for the intergration model analyzed to operate these data.This data framework can use International Electrotechnical Commission (IEC) common information model (CIM) as its top pattern.IECCIM is the standard developed by power industry, is adopted by IEC official, and object is to allow application software to exchange about the configuration of power network and the information of state.
In addition, this data framework can utilize associating middleware 134 to connect the utility data of other types (such as, such as instrumented data, operation and historical data, daily record and incident file) and to the connectivity in individual data framework and meta data file, this individual data framework can have the single entrance accessed for advanced application (comprising enterprise application).Real-time system can also visit critical data via high speed data bus and store, and multiple data storage can receiving real-time data.Dissimilar data can be transmitted in one or more buses in intelligent grid.As below in INDE transformer station 180 trifle discuss, can substation data be collected, and by its with local mode be stored in transformer station place.Particularly, can be associated with transformer station and database close to transformer station can store substation data.The analysis relevant with transformer station level can also be performed at transformer substation computer place, and be stored in substation data storehouse place, and all or part of of data can be transferred to control center.
Transmit data type can comprise operation and non-operational data, event, electrical network connectivity data and network location data.Service data can include but not limited to switch status, loop state, capacitor status, sector status, meter status, FCI state, line sensor state, voltage, electric current, real power, reactive power etc.Non-operational data can include but not limited to power quality, power reliability, assets health, stress data etc.Operation/non-operational data bus 146 can be used to transmit operation and non-operational data.Transmission of electricity in power network and/or the data collection application in distribution can be responsible for some or all of data to be sent to operation/non-operational data bus 146.Like this, need the application program of this information may can by subscribe to this information or by call make these data can service obtain data.
Event can comprise and stems from as the various equipment of a part for intelligent grid and the message of sensor and/or alarm, as discussed below.Event can directly generate from the equipment intelligent grid and sensor, and is generated based on the measurement data from these sensors and equipment by various analysis application.The example of event can comprise instrument power-off, instrument alarm, transformer power-off etc.Be similar to grid equipment (intelligent power sensor (such as there is the sensor that can be programmed the flush bonding processor having obtained digital processing capabilities) temperature sensor etc.), the electric system parts comprising additional embedded processing (RTU etc.), intelligent instrument network (instrument health, meter reading etc.) and the electrical network parts of mobile field processing equipment (power cut-off incident, work order complete) and event data, operation and non-operational data can be generated.The event data generated in intelligent grid can be transmitted via event bus 147.
Electrical network connectivity data can define the layout of utility power grid.The physical layout of definition electrical network parts (transformer station, section, loop, transformer, switch, automatic switch, instrument, sensor, public utilities electric pole etc.) and the basic layout of interconnectivity when mounted thereof can be there is.Based on the event (unit failure, maintenance etc.) in electrical network, electrical network connectivity can change continuously.As hereafter discussed in more detail, the combination of the structure and data that how to store data is making it possible to realize rebuilding in the history of the electrical network layout of various time in the past point.Periodically can extract electrical network connection data from Geographic Information System (GIS) along with modifying to utility power grid, and upgrade this information in GIS application program.
Network location data can comprise the information about the electrical network parts on communication network.This information can be used for sending message and information to certain electric net means.Manually network location data can be input in intelligent grid database along with the installation of new intelligent grid parts, if or this information kept in outside, then extract from the asset management system.
Data can be sent from the various parts (such as INDE transformer station 180 and/or INDE equipment 188) electrical network.Can by these data wirelessly, wired mode or both combinations be sent to INDE core 55.These data can be received by public utilities communication network 160, and data can be sent to routing device 190 by it.Routing device 190 can comprise for management data upper or to the software of the route in independent bus and/or hardware to a section (when bus comprises segmented bus structural formula) of bus.Routing device can comprise one or more switch or router.Routing device 190 can comprise networked devices, and its software and hardware is by data route and/or to be forwarded in bus one or more.Such as, operation and non-operational data can be routed to operation/non-operational data bus 146 by routing device 190.Event data can also be routed to event bus 147 by router.
Routing device 190 can determine how route data based on one or more method.Such as, routing device 190 can check the one or more headers in transmitted data, determining to route data to for operating/and the section of non-operational data bus 146 is still for the section of event bus 147.Particularly, the one or more headers in data can indicate: whether whether data are operation/non-operational data (making routing device 190 route data to operation/non-operational data bus 146) or data is event data (making routing device 190 routing-events bus 147).Alternatively, routing device 190 can check that the Payload of data is to determine the type (such as, routing device 190 can check that the form of data is to determine whether data are operation/non-operational data or event data) of data.
In the storehouse of the service data warehouse of such as store operands certificate (not shown in Fig. 6 A-6C) one can be embodied as true distributed data base.Another in storehouse, history library can be embodied as distributed data base.Other " terminals " in these two databases can be arranged in 180 groups, INDE transformer station.In addition, can via the event handling bus of complexity event is directly stored into multiple data store in any one.Particularly, can be stored in event log by event, it can be the storage vault of all events for being published to event bus 147.Event log can store in the following one, some or all: event id; Event type; Event source; Event Priority; And the event rise time.Event bus 147 does not need to store event chronically, is provided for the persistence of all events.
The storage of data can make data can be close to source as much as possible or when feasible.In one implementation, this can comprise and such as substation data is stored in place of INDE transformer station 180.But place also can not need these data in operational control center level 116, to consider the dissimilar judgement of electrical network in very meticulous level.Combine with distributed intelligence method, distributed data method has been used to the use by applicable database link and data, services, promotes the availability of data at the solution place of all levels.In this way, the solution for history data store (it can be addressable at operational control center level 116 place) can similar with operation data stornge.Data locally can be stored in the database link place that the storage vault example at transformer station and heart place in the controlling configures, the access to the data that independent transformer station locates is provided.Local datastore can be used locally to perform transformer station at place of transformer station analyze.The data at example place of local transformer station can be visited by the link of usage data storehouse, and at operational control center level 116 place executive director/group analysis.Alternatively, locally data can be stored at INDE core 55 place.But the given amount will transmitting the data that may need from INDE equipment 188, the storage of the data at INDE equipment 188 place can be preferred.Particularly, if there is thousands of or ten hundreds of transformer station'ss (this may occur in power network), then the amount of the data being transferred to INDE core 55 is needed to produce communication performance bottleneck.
Finally, INDE core 55 can in the INDE transformer station 180 in power network or INDE equipment 188, some or all programmes or controls.Such as, INDE core 55 can be revised programming (such as downloading refresh routine) or provide control command with any aspect (control of such as sensor or analysis) of control INDE transformer station 180 or INDE equipment 188.Other elements in INDE core 55 can comprise various integrated element to support this logical architecture.
Table 1 describes some element of INDE core 55.
Table 1:INDE core element
As in Table 1 discuss, real time data bus 146 (its transfer operation and non-operational data) and real-time Complex event processing bus 147 (it transmits event handling data) can be combined into single bus 346.
As shown in Fig. 6 A-6C, bus for performance object but separate.For CEP process, low latency is important for some application standing very large message bursts.On the other hand, except Digital fault recorders file, most of electric network data stream is constant more or less, but these can controllably be retrieved usually, and event burst is asynchronous and random.
Fig. 6 A-6C illustrates the additional elements in the operational control center 116 be separated with INDE core 55 further.Particularly, Fig. 6 A-6C illustrates that instrumented data collects head end 153 further, that is system (such as from wherein collecting data and collected data being supplied to public utilities) that is responsible and meter communication.Demand response management system 154 is the systems with the devices communicating that can be controlled by public utilities at one or more client place.Outage management system 155 is following systems, its by follow the tracks of power-off position, what is being distributed or how to be fixed by it helping public utility management power-off by management.Energy management system 156 is the transmission system level-regulating systems of the equipment controlled in the transformer station's (such as) on power transmission network.Distribution Management System 157 is the distribution system level-regulating systems controlling the equipment in transformer station and the feed equipment (such as) for power distribution network.IP network service 158 is in the set supporting the service that one or more servers of IP type communication (such as DHCP and FTP) operate.Distribution mobile data system 159 is the systems to the mobile data terminal transmission/reception message in scene.The analysis of circuit & load flow, planning, lightning analysis and electrical network simulation tool 152 are the set of the instrument used by public utilities in for the design and analysis of electrical network and planning.IVR (integrated speech response) and call manager 151 are the systems processing customer call (automatically or by attendant).Can automatically or manually input the input call about power-off and be forwarded to outage management system 155.Work management system 150 is systems of supervision and management work instruction.Geographic Information System 149 comprises to be positioned at where and assets geographically by the database how to link together about assets.If environment has Service-Oriented Architecture Based (SOA), then operate the set that SOA support 148 is the services supporting SOA environment.
One or more traditional product systems being public utilities and can having in system in operational control center 116 outside INDE core 55.The example of these traditional product systems comprises operation SOA support 148, Geographic Information System 149, Work management system 150, call manager 151, the analysis of circuit & load flow, planning, lightning analysis and electrical network simulation tool 152, instrumented data and collects head end 153, demand response management system 154, outage management system 155, energy management system 156, Distribution Management System 157, IP network service 158 and distribute mobile data system 159.But these traditional product systems may not process or operate the data received from intelligent grid.INDE core 55 may can receive data from intelligent grid, process the data from intelligent grid, and in the operable mode of traditional product system (such as special formatting specific to traditional product system), reduced data is transferred to one or more traditional product system.Like this, INDE core 55 can be considered as middleware.
The operational control center 116 comprising INDE core 55 can communicate with enterprise IT115.Generally speaking, the function in enterprise IT115 comprises Back office operation.Particularly, enterprise IT115 can use enterprise's the integration environment bus 114, data are sent to the various systems in enterprise IT115, comprise business datum warehouse 104, business intelligence application program 105, Enterprise Resources Planning 106, various financial sector 107, customer information system 108, human resource system 109, the asset management system 110, enterprise SOA support 111, network management system 112 and enterprise message and send service 113.Enterprise IT115 can also comprise the door 103 communicated with the Internet 101 via fire wall 102.
The particular example of the function in INDE core
As shown in Fig. 6 A-6C, comprise various function (with box indicating) in INDE core 55, wherein two can comprise instrument data managing service and quantitative analysis and service.Due to the modularity of framework, can in conjunction with the various functions of such as instrument data managing service and quantitative analysis and service.
INDE transformer station
Substation control room place on one or more servers of jointly locating with transformer station's electronic installation and system, INDE transformer station 180 can comprise the element of in fact manipulation in transformer station 170.
Following table 2 is listed and is described some INDE transformer station 180 group element.Data security service 171 can be a part for substation; Alternatively, can be attached in 180 groups, INDE transformer station.
Table 2
Table 2INDE transformer station element
As discussed above, the different elements in intelligent grid can comprise additional function, comprise additional treatments/analysis ability and database resource.The use of this additional function in the various elements in intelligent grid makes it possible to realize having the centralized management of application program and network performance and the distributed structure/architecture of supervision.Due to function, performance and scalability reason, relate to thousands of INDE transformer stations 180 and ten hundreds of intelligent grid of grid equipment to 1,000,000 can comprise distributed treatment, data management and procedure communication.
INDE transformer station 180 can comprise one or more processor and one or more memory device (such as transformer station's non-operational data 181 and Substation Operating data 182).Non-operational data 181 and Substation Operating data 182 can be made to be associated with transformer station and close to transformer station, be such as arranged in INDE transformer station 180 or on.INDE transformer station 180 can also comprise the intelligent grid parts of the observability of the intelligent grid at level place of responsible transformer station.INDE transformer station 180 parts can provide three major functions: the service data during distributed operation data store obtains and stores; The acquisition of non-operational data and the storage in historical data base; And the local analytics process of real-time (such as submicrosecond).Process can comprise the digital signal processing of voltage and current system, detection and classification process, comprises flow of event place; And result is to the transmission of local system and equipment and the system to operational control center 116 place.Communication between other equipment in INDE transformer station 180 and electrical network can be wired, wireless or wired and wireless combination.Such as, it can be wired for transmitting from the data of INDE transformer station 180 to operational control center 116.The data of such as operation/non-operational data or event data can be transferred to operational control center 116 by INDE transformer station 180.Transmission data can be routed to one in operation/non-operational data bus 146 or event bus 147 by routing device 190.
The demand response optimization for distribution loss management can also be performed here.This framework is according to previous discussed Distributed Application framework.
Such as, connection data can be copied at operational control center 116 place, even if thus also allow transformer station 170 to operate independently when running to the data communication network of operational control center 116 at place of transformer station 170.When this information (connectivity) is locally stored, even if be not exercisable to the communication link of operational control center, also locally can perform transformer station and analyze.
Similarly, can at operational control center 116 place with in place of transformer station 170 replicate run data.The data from the equipment be associated with particular substation and sensor can be collected, and nearest measurement result can be stored in these data storage at place of transformer station.The data structure of operation data stornge can be identical, and therefore database link can be used for the example of the operation data stornge located by control center, provides seamless access to the data be present in transformer station.This provide many advantages, comprise and alleviate Data duplication and make the substation data analysis of time-sensitive more can when local and occur when not relying on the availability of communications exceeding transformer station.The data analysis at operational control center level 116 place may be not so time-sensitive (because operational control center 116 can check that historical data is to distinguish the pattern more having predictability instead of reaction usually), and may be able to work around network problem (if any).
Finally, historical data locally can be stored in place of transformer station, and the copy of data can be stored in heart place in the controlling.Or, can link by configuration database on the storage vault example at operational control center 116 place, the access of the data of operational control center to independent transformer station locates is provided.Local datastore can be used at place of transformer station 170 locally to perform transformer station analyze.Particularly, use additional intelligence and the storage capacity at place of transformer station, make transformer station can analyze itself when the input not from central authority and also revise itself.Alternatively, the data at example place of local transformer station can also be visited by the link of usage data storehouse, and perform history/group analysis at operational control center level 116 place.
INDE equipment
INDE equipment 188 can comprise the equipment of any kind in intelligent grid, comprises the various sensors in intelligent grid, such as the instrument 163 etc. at various distrbution network equipment 189 (line sensor such as, on line of electric force), client place.INDE equipment 188 can comprise the equipment (such as comprising the intelligent remote terminal unit (RTU) of special programming) with specific function being added to electrical network, or the existing equipment (existing open architecture head of the mast RTU such as in place in electrical network, it can be programmed to produce intelligent line sensor or intelligent grid equipment) with added function that can comprise in electrical network.INDE equipment 188 can also comprise one or more processor and one or more memory device.
Existing grid equipment can not be open from software viewpoint, and may not provide too many support in modern networked or software service.Existing grid equipment may be designed to obtain and store data, for the accidental unloading of certain other equipment to such as laptop computer, or via PSTN line, autoexec is transferred to distance host as required.These equipment may not be designed to the operation in real-time digital network environment.In these cases, how to design according to existing communication network, grid equipment can be obtained at transformer station's level 170 place or at operational control center level 116 place.When meter network, regular situation will be collect engine from instrumented data to obtain data, because meter network is closed usually, and instrument may by directly address.Along with these e-learning quality, instrument and other electrical networks can be separately addressable, make it possible to data to be directly transferred to the place needing it, and it may not necessarily operational control center 116, but can be on electrical network Anywhere.
Equipment and the wireless network interface card that can make such as to be coupled with faulted circuit indicator match, for the connection by medium speed (such as 100kbps) wireless network.These equipment by exception reporting state, and can perform fixing preprogrammed functions.Can by the intelligence using local intelligent RTU to increase many grid equipments.The masthead RTU be designed to fixed function as having, closing framework equipment substitutes, and RTU can be used as being programmed by third party, and can serve as the open architecture equipment of the INDE equipment 188 in INDE frame of reference.Further, the instrument at client place can be used as sensor.Such as, instrument can measure consumption (such as the object of charging, consuming how many energy), and can measuring voltage (using in volt/VAr optimization).
Fig. 6 A-6C further depict client 179, and it can comprise one or more intelligent instrument 163, Home display 165, one or more sensor 166 and one or more control gear 167.In fact, sensor 166 can be deposited with the data at one or more equipment places at client 179 place.Such as, sensor 166 can be deposited with the data at the various main apparatus place in client 179, such as boiler, hot-water heater, air-conditioning etc.Data from one or more sensor 166 can be sent to intelligent instrument 163, its can encapsulation of data for via public utilities communication network 160 transmission to operational control center 116.Home display 165 can provide output device to watch the data of collecting from intelligent instrument 163 and one or more sensor 166 in real time for the client at client place.In addition, input equipment (such as keyboard) can be made to be associated with Home display 165, client can be communicated with operational control center 116.In one embodiment, Home display 165 can comprise the computing machine being present in client place.
Client 165 can also comprise the control gear 167 of one or more equipment that can control client 179 place.The various apparatuses at client 179 place can be controlled, such as well heater, air-conditioning etc. according to the order from operational control center 116.
As in Fig. 6 A-6C describe, client 169 can communicate in many ways, such as via the Internet 168, public switch telephone network (PSTN) 169 or via dedicated line (such as via gatherer 164).Via any one in listed communication channel, the data from one or more client 179 can be sent.As shown in Fig. 6 A-6C, one or more client 179 can comprise intelligent instrument network 178 (comprising multiple intelligent instrument 163), sends data to be transferred to operational control center 116 via public utility management network 160 to gatherer 164.In addition, each provenance (such as solar panels etc.) that distributed energy produced/stored 162 can send data to communicate with operational control center 116 via public utility management network 160 to monitor control gear 161.
As discussed above, the equipment in the power network outside operational control center 116 can comprise process and/or storage capacity.This equipment can comprise INDE transformer station 180 and INDE equipment 188.Except the specific installation in the power network comprising additional intelligence, specific installation can with other devices communicatings in power network, to exchange information (comprise sensing data and/or analyze data (such as event data)), to analyze the state (such as determining fault) of power network and to change the state (such as revising fault) of power network.Particularly, specific installation can use the following: (1) intelligence (such as processing power); (2) (all distributed storage as discussed above) is stored; And (3) communication (use of all one or more buses as discussed above).Like this, the specific installation in power network can intercom mutually when the supervision not from operational control center 116 and cooperate.
Such as, above-disclosed INDE framework can comprise the equipment of at least one parameter on sensing feed circuit.This equipment can also comprise the institute's sensor parameter monitored on feed circuit, and analyzes institute's sensor parameter to determine the processor of the state of feed circuit.Such as, the analysis of sensor parameter can comprise comparing and/or can comprising trend analysis of institute's sensor parameter and predetermined threshold.An institute like this sensor parameter can comprise sense waveform, and this alanysis can comprise and determines whether institute's sense waveform indicates the fault on feed circuit.This equipment can also with one or more transformer substation communication.Such as, particular substation can to specific feed circuit supply power.This equipment can sense the state of specific feed circuit, and determines whether there is fault on specific feed circuit.This equipment can with transformer substation communication.Transformer station can analyze the fault determined by equipment, and can take corrective action (such as reducing the power being supplied to feed circuit) according to fault.In the device examples of data sending indication fault (analysis based on waveform), transformer station can change when the input not from operational control center 116 power being supplied to feed circuit.Or, transformer station can by the data of indication fault with from the information combination of other sensors, to improve the analysis of fault further.Transformer station can also communicate with operational control center 116, such as power-off intelligent application and/or intelligent fault application program.Therefore, operational control center 116 can determine fault, and can determine the degree (such as by the number of the family of fault effects) of power-off.Like this, the equipment sensing the state of feed circuit can work with transformer station, collaboratively to revise incipient fault when requiring or do not require that operational control center 116 is got involved.
As another example, comprise and use the line sensor of additional intelligence of process and/or memory capabilities can produce electric network state data in a part (such as feed circuit) for electrical network.Electric network state data can be shared with the demand response management system 155 at operational control center 116 place.Demand response management system 155 in response to the electric network state data from line sensor, can control one or more equipment at the customer rs site place on feed circuit.Especially, demand response management system 155 can order energy management system 156 and/or distribution management system 157, turned off the apparatus of the customer rs site from feed circuit received power by the line sensor in response to the power-off on instruction feed circuit, reduce the load on feed circuit.Like this, the line sensor combined with demand response management system 155 can automatically make the load of own failured feeder circuit to be shifted, and then isolates this fault.
As another example, the one or more relays in power network can have microprocessor associated therewith.These relays can with other equipment be present in power network and/or database communication so that determine fault and/or control power network.
Aforementioned exemplary concentrates on power utility application.Disclosed INDE framework also can be applied to different industries.Such as, disclosed INDE framework can customize, and be applied to one or more industry, include but not limited to vehicles travel industry (such as air travel industry, the network that travels by railway, motoring network, bus tour network etc.), communication network and energy exploration (such as oil well network, gasser network etc.).
Although illustrate and describe the present invention in conjunction with the preferred embodiments, it is evident that, according to essential characteristic of the present invention, some can carrying out in addition to those described changes and amendment.In addition, there is the many dissimilar computer software and hardware that can utilize when implementing of the present invention, and the invention is not restricted to above-mentioned example.Represent with reference to the action of operation performed by one or more electronic equipment and symbol and describe the present invention.Also, it is to be understood that this type of action and operation comprise the manipulation representing the electric signal of data with structured form undertaken by the processing unit of electronic equipment.This operation converts data and holds it in the position in the accumulator system of electronic equipment, and it is reshuffled in the mode that those skilled in the art understands well or changes the operation of electronic equipment.The data structure of data is wherein kept to be the physical locations of the storer with the special properties defined by the form of data.Although describe the present invention in the preceding article, it is not intended to be restrictive, as skilled in the art will recognize, can also realize described action and operation with hardware.Therefore, applicant be intended that all change of protection in effective range of the present invention and amendment.Intention is by comprising the following claim of all equivalents to limit the present invention.

Claims (18)

1. a central power network management system, for managing power net at least partially and for communicating with multiple head-end system with multiple meter data management system, described meter data management system generates order and described head-end system and one or more meter communication, and described central power network management system comprises:
Gateway layer, comprise multiple input connector routine and multiple out connector routine, described multiple input connector routine comprise for send each in multiple origin systems of data at least one independent input connector routine of communicating to central power network management system, described origin system comprises multiple meter data management system, it sends data to central power network management system, described multiple out connector routine comprises at least one the independent out connector routine separately for communicating with each in multiple goal systems, described goal systems comprises the described multiple head-end system receiving data from central power network management system, and
Core layer, do not communicate with described goal systems with described origin system with the communication of described gateway layer, described core layer comprises multiple core adapter, described core adapter be arranged to perform by by be adapted to be received by described multiple goal systems, the conversion one to one of the communication of described multiple goal systems that received from described multiple origin system by described gateway layer.
2. central power network management system according to claim 1, wherein, the data being sent to described central power network management system comprise the connect/disconnect order sent by described multiple meter data management system.
3. central power network management system according to claim 1, wherein, the data being sent to described central power network management system comprise the reading order of instrument as required sent by described multiple meter data management system.
4. central power network management system according to claim 1, wherein, described multiple input connector routine comprises the multiple independent input connector routine for communicating with described multiple meter data management system; And
Wherein, described multiple out connector routine comprises the multiple independent out connector routine for communicating with described multiple head-end system.
5. central power network management system according to claim 4, wherein, each in described meter data management system is associated with multiple independent input connector routine; And
Wherein, each in described head-end system is associated with multiple independent out connector routine.
6. central power network management system according to claim 5, wherein, comprises different procotols from the described multiple independent input connector routine that each described meter data management system is associated.
7. central power network management system according to claim 6, wherein, described different network protocol is selected from by the following group formed: file transfer protocol (FTP) (FTP), java messenger service (JMS) and HTML (Hypertext Markup Language) (HTTP).
8. central power network management system according to claim 4, wherein, described multiple input connector routine also comprises: at least one the independent input connector routine communicated with each in described multiple head-end system; And
Wherein, described multiple out connector routine also comprises at least one the out connector routine for communicating with each in described multiple meter data management system.
9. central power network management system according to claim 8, wherein, each in described head-end system is associated with independent input connector routine; And
Wherein, each in described meter data management system is associated with independent out connector routine.
10. central power network management system according to claim 1, also comprise: at described gateway layer and the connector service interface layer docked between described core layer, described connector service interface layer calls described core layer in response to the communications reception by described gateway layer.
11. central power network management systems according to claim 1, wherein, described core adapter is also configured to perform from each described multiple origin system to the conversion one to one of the communication of each in described multiple goal systems.
12. central power network management systems according to claim 11,
Wherein, described core adapter is configured to perform from each described multiple meter data management system to the conversion one to one of the communication of each in described multiple head-end system.
13. central power network management systems according to claim 12, wherein, described core adapter is also configured to perform from each described multiple head-end system to the conversion one to one of the communication of each in described multiple meter data management system.
14. 1 kinds of central power network management systems, for managing power net at least partially and for communicating with multiple head-end system with multiple meter data management system, described meter data management system generates order and described head-end system and one or more meter communication, and described central power network management system comprises:
Gateway layer, comprise multiple input connector routine and multiple out connector routine, described multiple input connector routine comprise for send each in multiple origin systems of data at least one independent input connector routine of communicating to central power network management system, described origin system comprises multiple head-end system, it sends data to central power network management system, described multiple out connector routine comprises at least one the independent out connector routine separately for communicating with each in multiple goal systems, described goal systems comprises the described multiple meter data management system receiving data from central power network management system, and
Core layer, do not communicate with described goal systems with described origin system with the communication of described gateway layer, described core layer comprises multiple core adapter, described core adapter be arranged to perform by by be adapted to be received by described multiple goal systems, the conversion one to one of the communication of described multiple goal systems that received from described multiple origin system by described gateway layer.
15. central power network management systems according to claim 14, also comprise: at described gateway layer and the connector service interface layer docked between described core layer, described connector service interface layer calls described core layer in response to the communications reception by described gateway layer.
16. central power network management systems according to claim 14, wherein, described core adapter is also configured to perform from each described multiple origin system to the conversion one to one of the communication of each in described multiple goal systems.
17. central power network management systems according to claim 14, wherein, the described data being sent to described central power network management system comprise the periodic meter reading sent by described multiple head-end system.
18. central power network management systems according to claim 14, wherein, described multiple input connector routine comprises the multiple independent input connector routine for communicating with described multiple head-end system; And
Wherein, described multiple out connector routine comprises the multiple independent out connector routine for communicating with described multiple meter data management system.
CN201180037442.8A 2010-07-30 2011-07-22 Intelligent core engine Active CN103038606B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
IN2171CH2010 2010-07-30
IN2171/CHE/2010 2010-07-30
PCT/IB2011/001712 WO2012014039A2 (en) 2010-07-30 2011-07-22 Intelligent core engine

Publications (2)

Publication Number Publication Date
CN103038606A CN103038606A (en) 2013-04-10
CN103038606B true CN103038606B (en) 2016-03-30

Family

ID=44677968

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201180037442.8A Active CN103038606B (en) 2010-07-30 2011-07-22 Intelligent core engine

Country Status (11)

Country Link
US (1) US8676388B2 (en)
EP (1) EP2598845B1 (en)
JP (1) JP5925774B2 (en)
CN (1) CN103038606B (en)
AU (1) AU2011284471B2 (en)
CA (1) CA2807007C (en)
MY (1) MY167307A (en)
NZ (1) NZ607733A (en)
RU (1) RU2541911C2 (en)
SG (1) SG187229A1 (en)
WO (1) WO2012014039A2 (en)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8924033B2 (en) 2010-05-12 2014-12-30 Alstom Grid Inc. Generalized grid security framework
US8965590B2 (en) 2011-06-08 2015-02-24 Alstom Grid Inc. Intelligent electrical distribution grid control system data
US9641026B2 (en) 2011-06-08 2017-05-02 Alstom Technology Ltd. Enhanced communication infrastructure for hierarchical intelligent power distribution grid
US20120316688A1 (en) * 2011-06-08 2012-12-13 Alstom Grid Coordinating energy management systems and intelligent electrical distribution grid control systems
US9281689B2 (en) 2011-06-08 2016-03-08 General Electric Technology Gmbh Load phase balancing at multiple tiers of a multi-tier hierarchical intelligent power distribution grid
US9397521B2 (en) * 2012-01-20 2016-07-19 Salesforce.Com, Inc. Site management in an on-demand system
US10679131B2 (en) * 2012-07-12 2020-06-09 Eaton Intelligent Power Limited System and method for efficient data collection in distributed sensor measurement systems
CN103679306A (en) * 2012-08-31 2014-03-26 国际商业机器公司 Method and system for saving building energy consumption
US9644991B2 (en) 2012-10-01 2017-05-09 Cooper Technologies Company System and method for support of one-way endpoints in two-way wireless networks
US9085958B2 (en) 2013-09-19 2015-07-21 Sas Institute Inc. Control variable determination to maximize a drilling rate of penetration
US9729678B2 (en) * 2013-10-03 2017-08-08 Duke Energy Corporation Methods of processing data corresponding to a device that corresponds to a gas, water, or electric grid, and related devices and computer program products
US9163497B2 (en) * 2013-10-22 2015-10-20 Sas Institute Inc. Fluid flow back prediction
CN110233788B (en) * 2013-11-12 2021-06-18 艾思玛太阳能技术股份公司 Method for communicating a system control unit with a plurality of power generation devices
US9407324B2 (en) 2013-12-23 2016-08-02 Duke Energy Corporation Communication nodes and sensor devices configured to use power line communication signals, and related methods of operation
US9699708B2 (en) 2014-01-17 2017-07-04 Cooper Technologies Company Dynamically-selectable multi-modal modulation in wireless multihop networks
FR3024563B1 (en) * 2014-08-01 2017-12-08 Novawatt SYSTEM FOR DISTRIBUTING ENERGY SUCH AS ELECTRIC OR HEAT ENERGY
CN105320113B (en) * 2015-10-19 2018-04-10 国家电网公司 The information interacting method of power network spatial Information Service platform and electrical power distribution automatization system
CN105243217B (en) * 2015-10-19 2019-04-16 国家电网公司 PMS system and the information interacting method at module
RU2638632C1 (en) * 2016-12-07 2017-12-14 Федеральное государственное автономное образовательное учреждение высшего образования "Национальный исследовательский Томский политехнический университет" Complex for decision support by dispatch office personnel of electric power systems
CN107526630A (en) * 2017-07-31 2017-12-29 杭州安恒信息技术有限公司 A kind of method for solving Distributed engine communication
CA3088171A1 (en) 2018-01-12 2019-07-18 Insight Energy Ventures, Llc Systems and methods of capturing usage data from an amr device
EP3791277A4 (en) * 2018-05-11 2022-01-26 JPMorgan Chase Bank, N.A. Function as a service gateway
US11553447B2 (en) * 2020-06-16 2023-01-10 Landis+Gyr Innovations, Inc. Registering an endpoint with multiple headend systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101689277A (en) * 2007-03-23 2010-03-31 Bpl环球有限公司 System and method for adaptive islanding for stored/distributed energy devices
US8672273B2 (en) * 2008-01-09 2014-03-18 International Business Machines Corporation Rail car sensor network

Family Cites Families (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5455776A (en) 1993-09-08 1995-10-03 Abb Power T & D Company Inc. Automatic fault location system
CA2200862C (en) * 1994-09-27 2002-02-26 Alastair Montgomerie Remote access systems
WO1998010394A1 (en) * 1996-09-06 1998-03-12 Innovatec Corporation Automatic meter reading data communication system
US7046682B2 (en) 1997-02-12 2006-05-16 Elster Electricity, Llc. Network-enabled, extensible metering system
US5923269A (en) * 1997-06-06 1999-07-13 Abb Power T&D Company Inc. Energy meter with multiple protocols for communication with local and wide area networks
US7650425B2 (en) * 1999-03-18 2010-01-19 Sipco, Llc System and method for controlling communication between a host computer and communication devices associated with remote devices in an automated monitoring system
AU2001284759A1 (en) * 2000-08-09 2002-02-18 Statsignal Systems, Inc. Automated monitoring system between a host computer and remote devices
SE519943C2 (en) 2000-12-14 2003-04-29 Abb Ab Method for fault location in a transmission line
US7062359B2 (en) 2000-12-29 2006-06-13 Abb Ab Substation control system
US20020103772A1 (en) 2001-01-31 2002-08-01 Bijoy Chattopadhyay System and method for gathering of real-time current flow information
ES2364451T3 (en) 2001-05-21 2011-09-02 Abb Research Ltd. STABILITY FORECAST FOR AN ELECTRICAL POWER NETWORK.
ITMI20012726A1 (en) * 2001-12-20 2003-06-20 Enel Distribuzione Spa SYSTEM OF REMOTE CONSUMPTION OF CONSUMPTION AND REMOTE MANAGEMENT OF USERS ALSO DISTRIBUTED OF A DOMESTIC TYPE
ATE326073T1 (en) 2001-12-21 2006-06-15 Abb Schweiz Ag DETERMINATION OF THE OPERATING LIMIT VALUES IN AN ENERGY DISTRIBUTION NETWORK
WO2003073312A1 (en) 2002-02-25 2003-09-04 General Electric Company Method and apparatus for minimally invasive network monitoring
US6667610B2 (en) 2002-03-11 2003-12-23 Gregory Hubert Piesinger Apparatus and method for identifying cable phase in a three-phase power distribution network
US7031859B2 (en) 2002-03-11 2006-04-18 Piesinger Gregory H Apparatus and method for identifying cable phase in a three-phase power distribution network
US6662124B2 (en) 2002-04-17 2003-12-09 Schweitzer Engineering Laboratories, Inc. Protective relay with synchronized phasor measurement capability for use in electric power systems
ITFI20020144A1 (en) * 2002-08-01 2004-02-02 Menarini Farma Ind STABILIZED TOPICAL FORMULATIONS CONTAINING KETOPROFENE.
US6819098B2 (en) * 2002-10-01 2004-11-16 Poweronedata, Inc. Utility power meter database
EP1408595B1 (en) 2002-10-10 2017-06-14 ABB Research Ltd. Determining parameters of an equivalent circuit representing a transmission section of an electrical network
US7689323B2 (en) 2003-05-13 2010-03-30 Siemens Aktiengesellschaft Automatic generation control of a power distribution system
US7739138B2 (en) 2003-05-19 2010-06-15 Trimble Navigation Limited Automated utility supply management system integrating data sources including geographic information systems (GIS) data
US7233843B2 (en) 2003-08-08 2007-06-19 Electric Power Group, Llc Real-time performance monitoring and management system
GB2407927B (en) * 2003-11-07 2006-03-01 Responsiveload Ltd Responsive electricity grid substation
US8108184B2 (en) 2004-01-15 2012-01-31 Bruce Fardanesh Methods and systems for power systems analysis: a non-iterative state solver/estimator for power systems operation and control
CA2455689A1 (en) * 2004-01-23 2005-07-23 Stuart Energy Systems Corporation System for controlling hydrogen network
GB0402739D0 (en) 2004-02-09 2004-03-10 Saviso Group Ltd Methods and apparatus for routing in a network
US20060259255A1 (en) 2005-04-05 2006-11-16 Anderson James C Method of visualizing power system quantities using a configurable software visualization tool
US20060224336A1 (en) 2005-04-05 2006-10-05 Charles Petras System and method for transmitting power system data over a wide area network
US7657924B2 (en) * 2005-04-06 2010-02-02 International Business Machines Corporation Method and system for implementing authorization policies for web services
US7444248B2 (en) 2005-04-29 2008-10-28 General Electric Company System and method for synchronized phasor measurement
JP4729969B2 (en) * 2005-05-09 2011-07-20 パナソニック電工株式会社 Gateway device
US7480580B2 (en) 2005-10-18 2009-01-20 Schweitzer Engineering Laboratories, Inc. Apparatus and method for estimating synchronized phasors at predetermined times referenced to an absolute time standard in an electrical system
US7545285B2 (en) * 2006-02-16 2009-06-09 Elster Electricity, Llc Load control unit in communication with a fixed network meter reading system
US20090043520A1 (en) * 2006-08-10 2009-02-12 V2Green, Inc. User Interface and User Control in a Power Aggregation System for Distributed Electric Resources
US7630863B2 (en) 2006-09-19 2009-12-08 Schweitzer Engineering Laboratories, Inc. Apparatus, method, and system for wide-area protection and control using power system data having a time component associated therewith
US8332567B2 (en) 2006-09-19 2012-12-11 Fisher-Rosemount Systems, Inc. Apparatus and methods to communicatively couple field devices to controllers in a process control system
US7472026B2 (en) 2006-12-22 2008-12-30 General Electric Company Multi-ended fault location system
US20080177678A1 (en) * 2007-01-24 2008-07-24 Paul Di Martini Method of communicating between a utility and its customer locations
US7853417B2 (en) * 2007-01-30 2010-12-14 Silver Spring Networks, Inc. Methods and system for utility network outage detection
US7620517B2 (en) 2007-02-05 2009-11-17 Abb Research Ltd. Real-time power-line sag monitoring using time-synchronized power system measurements
CN101682179B (en) * 2007-03-14 2015-09-16 佐尼特结构解决方案有限责任公司 Nema outlets and the network be associated of intelligence
JP2008250834A (en) * 2007-03-30 2008-10-16 Nippon Telegraph & Telephone West Corp Statistical tabulating system, statistic device and computer program
GB0711770D0 (en) * 2007-06-18 2007-07-25 Domia Ltd Off site monitoring/control of electrical equipment
US7693609B2 (en) * 2007-09-05 2010-04-06 Consolidated Edison Company Of New York, Inc. Hybrid vehicle recharging system and method of operation
US9270552B2 (en) * 2007-09-07 2016-02-23 Power Measurement Ltd. Energy monitoring system using network management protocols
WO2009067259A1 (en) * 2007-11-25 2009-05-28 Trilliant Networks, Inc. Transport layer and model for an advanced metering infrastructure (ami) network
US8731732B2 (en) * 2008-02-25 2014-05-20 Stanley Klein Methods and system to manage variability in production of renewable energy
US8892375B2 (en) * 2008-05-09 2014-11-18 Accenture Global Services Limited Power grid outage and fault condition management
US8121741B2 (en) * 2008-05-09 2012-02-21 International Business Machines Corporation Intelligent monitoring of an electrical utility grid
SG10201606766QA (en) * 2008-05-09 2016-10-28 Accenture Global Services Ltd Method and system for managing a power grid
US7953519B2 (en) * 2008-10-15 2011-05-31 International Business Machines Corporation Energy usage monitoring and balancing method and system
US8269649B2 (en) * 2009-01-29 2012-09-18 Itron, Inc. Relative time system
US8310341B2 (en) * 2009-04-20 2012-11-13 Itron, Inc. Endpoint classification and command processing
EP2290328B1 (en) * 2009-08-24 2015-03-04 Accenture Global Services Limited Utility management system
US8121743B2 (en) * 2009-11-23 2012-02-21 International Business Machines Corporation Power restoration management method and system
KR101644432B1 (en) * 2009-12-16 2016-08-10 엘지전자 주식회사 A measuring method for consumption quantity of electricity of an electric appliance
KR101611296B1 (en) * 2010-02-09 2016-04-12 엘지전자 주식회사 Method and apparatus for controlling power using a smart device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101689277A (en) * 2007-03-23 2010-03-31 Bpl环球有限公司 System and method for adaptive islanding for stored/distributed energy devices
US8672273B2 (en) * 2008-01-09 2014-03-18 International Business Machines Corporation Rail car sensor network

Also Published As

Publication number Publication date
WO2012014039A3 (en) 2013-01-03
JP5925774B2 (en) 2016-05-25
CA2807007C (en) 2018-07-17
MY167307A (en) 2018-08-16
NZ607733A (en) 2014-09-26
EP2598845A2 (en) 2013-06-05
RU2541911C2 (en) 2015-02-20
AU2011284471A1 (en) 2013-03-21
US20120029710A1 (en) 2012-02-02
RU2013108972A (en) 2014-09-10
CA2807007A1 (en) 2012-02-02
AU2011284471B2 (en) 2014-11-06
EP2598845B1 (en) 2016-01-27
JP2013536666A (en) 2013-09-19
SG187229A1 (en) 2013-02-28
WO2012014039A2 (en) 2012-02-02
CN103038606A (en) 2013-04-10
BR112013003660A2 (en) 2020-08-25
US8676388B2 (en) 2014-03-18

Similar Documents

Publication Publication Date Title
CN103038606B (en) Intelligent core engine
Pau et al. A cloud-based smart metering infrastructure for distribution grid services and automation
US10833532B2 (en) Method and system for managing a power grid
CN102209074B (en) All-digital dynamic simulation system of power system
JP5932668B2 (en) Utility grid command filter system
CN108924233A (en) Electric power collection copies group system and method
Pau et al. A service oriented architecture for the digitalization and automation of distribution grids
CN112015813A (en) Data sharing method, system and device of power distribution network and computer equipment
Thesing Integrating electric meter data with distribution automation applications
Alberto et al. OpenNode: A smart secondary substation node and its integration in a distribution grid of the future
Bhattarai et al. Prototypical communication systems for electrical distribution system analysis: Design basis and exemplification through co‐simulation
Cejka et al. Integrating Smart Building Energy Data into Smart Grid Applications in the Intelligent Secondary Substations
AU2015230786A1 (en) Method and system for managing a power grid
Mashlakov et al. Integrated business platform of distributed energy resources–HEILA
CN117578459A (en) Distributed control method and system for low-voltage intelligent equipment in power distribution network
WANG et al. ZHAO LI, FANG YANG, ZHENYUAN WANG, AND YANZHU YE
Palmlund Wahlgren Internet-of-Things in Low Voltage Electricity Grids
BEENKEN et al. AN OVERVIEW OF RECOMMENDATIONS FOR A TECHNICAL SMART GRID INFRASTRUCTURE
Li et al. Advanced metering infrastructure and its integration with the distribution management system
BR112013003660B1 (en) CENTRAL POWER INSTALLATION SYSTEM
Ozansoy et al. A review of substation automation communication protocols
Bolla et al. The Role of ICT in the Evolution Towards Smart Grids

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant