IT and ICT infrastructure of Smart Grids

Transkriptio

1 1 IT and ICT infrastructure of Smart Grids Shengye Lu

2 2 Outlines Demonstration environment of Smart Grid applications in TUT. The CIM and its applications

3 3 Demonstration environment of Smart Grid applications in TUT

4 Aggregator as one component in Smart Grid ICT system 4 Operation on regulation market Balance management Production following Etc. Electricity market Electricity network Monitoring of reserves Overload management Etc. User interface Aggregator (Open EMS Suite) End customer user interface Home automation (ThereGate) Frequency dependent load shedding Electric vehicle charging Connection point peak load reduction Etc.! AMI T Electric vehicle DG DER

5 Demonstration environment in lab 5!

6 Frequency dependent load shedding application demonstration 6 Three loads: one resistor load (EV), two electric heaters. Algorithm: Ø Freq <= 49.8 Hz, disconnect one electric heater. Ø Freq <= 49.7 Hz, disconnect another heater. Ø Freq <= 49.6 Hz, disconnect EV charging.!

7 7 Demonstration result Screenshot on ABB DMS600:!

8 8 The CIM and its applications

9 9 Table of Contents 1. Introduction of CIM 2. The CIM model 3. Serialize CIM with XML 4. CIM profiles 5. Enterprise Integration with CIM 6. Using CIM with load flow calculation tool

10 10 1. Introduction of CIM The IEC Common Information Model (CIM) is a set of standards that enable system integration and information exchange in power electrical domain. It utilizes Unified Modeling Language(UML) based information model to represent real-world objects and information entities. It is not tied to a particular application s view of the world. It permits the same model to be used by all applications to facilitate information sharing between applications. CIM standards: IEC 61970, Energy Management Systems Application Program Interfaces (API) IEC 61968, Application Integration at Electric Utilities System Interfaces for Distribution Management IEC 62325, Standards related to energy market models & communications.

11 11 1. Introduction of CIM The CIM standards constitute layered reference architecture.

12 12 2. The CIM model CIM uses Object-Oriented modeling It describes power system resources and services by using classes, attributes, and relationships between them. It is expressed in UML notation. CIM classes are related with each other via relationship. There are three types of relationships. Generalization Association Aggregation

13 13 Relationships in CIM classes Generalization: Association: Aggregation:

14 14 2. The CIM model Fig: Example Circuit as a single line diagram Fig: Example Circuit with full CIM Mapping

15 15 3. Serialize CIM with XML XML (Extensible Markup Language) XML is a markup language defined by W3C. It is designed for storing machine-readable data in a structured, extensible format. XML documents store data in a tree structure. XML Schema used to express a set of rules to which an XML document must conform in order to be considered valid according to that schema. RDF (Resource Description Framework) a standard model designed for describing resources An RDF model is usually expressed in an XML document, and the XML language used by RDF is called RDF/XML. RDF Schema RDF Schema is RDF s vocabulary description language.

16 16 3. Serialize CIM with XML With RDF Schema language, users can define RDF resources (including properties and relationships) in application-specific RDF vocabularies. CIM RDF Schema The RDF Schema version of the CIM model provides the metadata or vocabulary, with which systems can create RDF/XML model files with descriptions of actual networks. IEC specifies the CIM RDF Schema. CIM RDF XML To be used for exchanging power system models Each CIM object is an independent XML element that is then linked using the rdf:id and rdf:resource attributes.

17 Snippet of CIM RDF XML 17 <?xml version="1.0" encoding="utf-8"?> <rdf:rdf xmlns:rdf=" xmlns:cim=" <cim:powertransformer rdf:id="_id_powerxfr_tr1"> <cim:identifiedobject.name>tr1</cim:identifiedobject.name> <cim:identifiedobject.localname>tr1</cim:identifiedobject.localname> <cim:equipment.memberof_equipmentcontainer rdf:resource="#_id_substation1"/> </cim:powertransformer> <cim:transformerwinding rdf:id="_id_tr1_w1"> <cim:transformerwinding.g>0</cim:transformerwinding.g> <cim:transformerwinding.b> </cim:transformerwinding.b> <cim:transformerwinding.r>.9648</cim:transformerwinding.r> <cim:transformerwinding.x> </cim:transformerwinding.x> <cim:transformerwinding.ratedu>15</cim:transformerwinding.ratedu> <cim:transformerwinding.rateds>100</cim:transformerwinding.rateds> <cim:transformerwinding.windingtype rdf:resource=" <cim:transformerwinding.connectiontype rdf:resource=" <cim:identifiedobject.name>tr1_w1</cim:identifiedobject.name> <cim:identifiedobject.localname>tr1_w1</cim:identifiedobject.localname> <cim:transformerwinding.memberof_powertransformer rdf:resource="#_id_powerxfr_tr1"/> <cim:conductingequipment.basevoltage rdf:resource="#_id_basevoltage_15kv"/> </cim:transformerwinding> <cim:transformerwinding rdf:id="_id_tr1_w2"> </cim:transformerwinding>... </rdf:rdf>

18 18 3. Serialize CIM with XML CIM XML To be used for generating message payloads for application interfaces in system integration use cases. Elements are contained within each other.

19 19 Snippet of CIM XML <cim:powertransformer> < cim:identifiedobject.name>transformer SGT1</cim:IdentifiedObject.name> <cim:powertransformer.contains_transformerwindings> <cim:transformerwinding.r>0.23</cim:transformerwinding.r> <cim:transformerwinding.x>0.78</cim:transformerwinding.x> <cim:transformerwinding.windingtype>windingtype.primary </cim:transformerwinding.windingtype> <cim:conductingequipment.basevoltage> <cim:basevoltage.nominavoltage>400</cim:basevoltage.nominalvoltage> </cim:conductingequipment.basevoltage> </cim:powertransformer.contains_transformerwindings> <cim:powertransformer.contains_transformerwindings> <cim:transformerwinding.r>0.46</cim:transformerwinding.r> <cim:transformerwinding.x>0.87</cim:transformerwinding.x> <cim:transformerwinding.windingtype>windingtype.secondary </cim:transformerwinding.windingtype> <cim:conductingequipment.basevoltage> <cim:basevoltage.nominavoltage>275</cim:basevoltage.nominalvoltage> </cim:conductingequipment.basevoltage> </cim:powertransformer.contains_transformerwindings> </cim:powertransformer>

20 20 4. CIM profiles A profile specifies the mandatory and optional classes, attributes and associations, as well as constraints, that an application need implement for a certain use of the CIM. IEC : Equipment Model Profile IEC : Solved Power System State Interface Topology profile: for exchanging the bus-branch result as is produced by a topology processor. State Variable profile: for exchanging the result of a state estimator or power flow, or the starting conditions of state variables. Status Measurement profile: for exchanging a set of switch states at a given points in time. Analog Measurement profile: for exchanging a set of analog measurements at a given points in time.

21 21 5. Enterprise Integration with CIM The scalability issue of Inter-application communication in utility company: Traditional point-to-point integration does not scale well. A more scalable solution is IEC based integration. IEC is intended to support applications that need to exchange data on an event-driven basis. IEC is intended to be implemented with middleware services that broker messages among applications, and will complement, but not replace utility data warehouses, database gateways, and operational stores.

22 22 SOA, ESB Service Oriented Architecture (SOA) A computer system architectural style - software resources in an enterprise are packaged as well-defined services, available and discoverable on network. loose coupling: independent services with defined interfaces can be called to perform their tasks in a standard way, and do not depend on the context or state of the other services. Implementation technologies include Web Services, REST, etc. Message exchange patterns for SOA Request-Response Request-Response via Service Registry Subscribe-push Data push

23 23 SOA, ESB Enterprise Service Bus (ESB) ESB is an infrastructure that facilitates SOA through virtualization and management of service interactions between communication participants. multitude of features: routing, accepting and delivering messages message format transformation managing the descriptions and definition of the messages and their formats through accessible metadata Plenty of ESB implementations: Commercial software - IBM WebSphere ESB, Microsoft BizTalk server, Oracle Enterprise Service Bus (BEA Logic), etc.; Open Source - Apache ServiceMix, JBoss ESB, Mule, etc.

24 24 Implementation steps Using ESB technology to integrate applications: 1. Applications define and publish service interfaces. Service interfaces are defined using e.g., WSDL, XML Schema. IEC defines message envelops. Message contains Verb, Noun, payload. A payload is typically conveyed using an XML document that conforms to an XML Schema. The structure of the payload is typically defined as a contextual profile from a CIM UML model. 2. Applications start exchanging messages. The sender and receiver are decoupled from each other. ESB will take care of message routing and mapping.

25 Example use case: AMI alarm delivery 25 AMI DMS CIS Field Force MS alarms query: user data user data command result

26 Example use case: AMI alarm delivery 26 AMI DMS CIS Semantically Consistent ESB Field Force MS

27 Example use case: AMI alarm delivery 27 AMI DMS ESB CIS Field Force MS Created (Alarm) Created (Alarm) Create (user data) Create (user data) Reply Reply Create (Command) Create (Command) Reply Reply