IT and ICT infrastructure of Smart Grids...Outlines • Demonstration environment of Smart Grid...

IT and ICT infrastructure of Smart Grids

Shengye Lu [email protected]

26.04.2012

1

*Oma nimi ja esityksen aihe vaihdettava alatunnisteeseen 25/04/2012

Outlines

•  Demonstration environment of Smart Grid applications in TUT.

•  The CIM and its applications

2


Demonstration environment of Smart Grid applications in TUT

3


Aggregator as one component in Smart Grid ICT system

!T Electric

vehicle DG DERAMI

Electricity market Electricity networkMonitoring of reservesOverload managementEtc.

Operation on regulation marketBalance managementProduction followingEtc.

Frequency dependent load sheddingElectric vehicle chargingConnection point peak load reductionEtc.

End customer user interface

Home automation(ThereGate)

User interface Aggregator(Open EMS Suite)

T Electricvehicle DG DERAMI

Electricity market Electricity networkMonitoring of reservesOverload managementEtc.

Operation on regulation marketBalance managementProduction followingEtc.

Frequency dependent load sheddingElectric vehicle chargingConnection point peak load reductionEtc.

End customer user interface

Home automation(ThereGate)

User interface Aggregator(Open EMS Suite)

4


Demonstration environment in lab

!

5


Frequency dependent load shedding application demonstration

!

•  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.

6


Demonstration result

Screenshot on ABB DMS600:

7


!

The CIM and its applications

8


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

9


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.

10


1. Introduction of CIM 11


•  The CIM standards constitute layered reference architecture.

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

12


Relationships in CIM classes 13


•  Generalization:

•  Association:

•  Aggregation:

2. The CIM model 14


Fig: Example Circuit as a single line diagram Fig: Example Circuit with full CIM Mapping

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.

15



•  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 61970-501 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.

16


Snippet of CIM RDF XML <?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cim="http://iec.ch/TC57/2008/CIM-schema-cim14#"> <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>-.0000025625</cim:TransformerWinding.b> <cim:TransformerWinding.r>.9648</cim:TransformerWinding.r> <cim:TransformerWinding.x>44.7896</cim:TransformerWinding.x> <cim:TransformerWinding.ratedU>15</cim:TransformerWinding.ratedU> <cim:TransformerWinding.ratedS>100</cim:TransformerWinding.ratedS> <cim:TransformerWinding.windingType rdf:resource="http://iec.ch/TC57/2008/CIM-schema-cim13#WindingType.primary"/> <cim:TransformerWinding.connectionType rdf:resource="http://iec.ch/TC57/2008/CIM-schema-cim13#WindingConnection.Y"/> <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>

17



•  CIM XML •  To be used for generating message payloads for application

interfaces in system integration use cases. •  Elements are contained within each other.

18


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>

19


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 61970-452: Equipment Model Profile •  IEC 61970-456: 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.

20


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 61968 based integration.

•  “IEC 61968 is intended to support applications that need to exchange data on an event-driven basis. IEC 61968 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”.

21


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 •  …

22


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.

23


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 61968 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.

24


Example use case: AMI alarm delivery

AMI DMS CIS Field Force MS

alarms

query: user data

user data

command

result

25



26


Semantically Consistent ESB

AMI DMS CIS

Field Force MS


AMI DMS CIS Field Force MSESB

Created (Alarm)

Created (Alarm)

Create (user data)

Create (user data)

Reply

Reply

Create (Command)

Create (Command)

Reply

Reply

27


6. Using CIM with load flow calculation tool

•  Load flow calculation tool: InterPSS OpenCIM

28


6. Using CIM with load flow calculation tool

•  Our Java software can parse a CIM RDF XML file, simplify it to bus-branch model.

29


Questions?

30


Date post:	14-Mar-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

IT and ICT infrastructure of Smart Grids...Outlines • Demonstration environment of Smart Grid...

Documents