Agenda - kth.se · Slide 1 Agenda Standards development ... IEC 61850 Substation control interfaces ... Areva, EDF, ABB, PTI, Siemens, Sisco, Xtensible Solutions

Slide 1

Agenda

Standards development – CIM

Standards development – Driving forces and network codes

Standards development – CIM and CGMES specifications

Standards development – Data Exchange and partitioning

Standards development – Profile development

UML overview

CIM UML

Data examples

CIMXML exchange format

CIM Lecture 2017-04-04 by Lars-Ola Österlund

April 26, 2017

Slide 2

CIM Common Information Model (for power systems)

ISO Independent System Operator, exist in US

TSO Transmission System Operator

DSO Distribution System Operator

EPRI Electric Power Research Institute, an ISO/TSO sponsored research institute in US

CCAPI Control Center API

CME CIM for Market data Exchange

IOP Interoperability Test

IEC International Electrotechnical Committee

TCxx Technical Committee xx

WGxx Working Group xx

ENTSO-E European Network of TSOs of electricity, formed by merging UCTE and ETSO

CGMES Common Grid Model Exchange Standard

UCTE Union for the Coordination of the Transmission of Electricity

ETSO European Transmission System Operators

Standards Development

April 26, 2017

Some Abbreviations

Slide 3

EPRI had a need to integrate software developed for them by contractors

Power utilities (ISO, TSO, DSO…) has an increasing need to exchange data

1994-1996 CCAPI EPRI project 3654-01 published the report TR-106324

1996 IEC work started, IEC 61970 for transmission and IEC 61968 for distribution

1998 Move to UML

2000 First IOP, annual IOPs from then on, NERC mandate the use of CIM

- many US users still on CIM10

2003 CME EPRI ISO/RTO sponsored market extension project, resulted in IEC 62325

2005 First edition of IEC 61970-301 CIM base document

2008 UCTE start to use CIM (IEC 61970) for DACF

2009 NIST identifies CIM as a Smart Grid standard

2010 First ENTSO-E IOP

2014 ENTSO-E Conformance test published


April 26, 2017

How CIM Started

Slide 4

An information model in UML

An agreed canonical information model

The information model is large

• Not practical to use as is

• Subsets or profiles used for actual exchanges

Data is exchanged as XML documents

• XML Schema based documents

• RDF/XML documents

• RDF is described by RDFS and OWL

• RDF and OWL designed for the semantic web


April 26, 2017

What CIM Is

Slide 5

Working groups and standards

WG3 and WG7 Communication protocols

WG10 – IEC 61850 Substation control interfaces

WG13 – IEC 61970 CIM - EMS API *

WG14 – IEC 61968 CIM - System interfaces for electrical distribution *

WG15 – IEC 62210 Data and communication security

WG16 – IEC 62325 CIM - Deregulated energy market communications

WG17 Communication system for distributed energy resources (DER)

WG18 Hydro electric power plants

WG19 coordination of TC57 standards, in particular CIM and IEC 61850

* Scope is currently changing for CIM

61970 – network model for both transmission and distribution

61968 – utility related IT/OT work processes


April 26, 2017

IEC TC57

Slide 6

Drivers

Common energy markets

Increased trade increase flows across market boundaries

Large increase in renewable power generation

Increasing difficulty in predicting power flows

Huge power flows over congested network boundaries

Old generation units being decommissioned

Decreasing system stability

Results in increased need for network model exchange between TSOs and DSOs

In Europe legislation, the Network Codes (NC), push TSOs to increase data exchange

Legislation developed by ACER (Agency for Cooperation of Energy Regulators)

ENTSO-E implement the Network Codes and developed CGMES CIM profiles to support it


April 26, 2017

Current Drivers Resulting In Standardization In Europe

Slide 7

Renewable energy production increase

• Wind

• Solar

• During sunny and windy days the renewable

production is substantial, regionally > 25%!

Old fossil fuel plants being decommissioned

Large power flows across EU

Power flow congestion an issue

• Hinder free market

• Threaten stability stability


April 26, 2017

Energy Production And Flows in EU

Slide 8


April 26, 2017

Overview ENTSO-E Network Codes

Slide 9

Requirements from the Network Codes CACM and Operational security and planning

• Congestion management (NC CACM)

• Intra Day Congestion Forecast (IDCF)

• Day Ahead Congestion Forecast (DACF)

• Capacity Allocation two days ahead

• Need to exchange network models and schedules for Europe

• Old DEF format needed development

• CIM was investigated as an alternative


April 26, 2017

ENTSO-E CGMES

Slide 10

Three versions

• CGMES 1 based on CIM 14

• CGMES 2.4 based on CIM 16

• CGMES 2.5

Consist of

• CIM Canonical UML

• ENTSO-E Canonical UML extensions

• ENTSO-E profile in UML

• ENTSO-E profile in RDFS

• ENTSO-E main document

• Several additional guideline documents


April 26, 2017

ENTSO-E CGMES

Slide 11

Canonical CIM

• UML package iec61970cim16v33b_iec61968cim12v08_iec62325cim03v01a.eap

• CIM Base IEC 61970-301

• Dynamics IEC 61970-302

Profile documents

EQ – Network equipment IEC 61970-452

TP – Topology IEC 61970-456

SV – State Variables IEC 61970-456

SSH – Steady State Hypothesis (power flow input) IEC 61970-456

DL – Display Layout IEC 61970-453

GL – Geographical Location

DY – Dynamics data IEC 61970-457

CIM RDF schema, profile information model IEC 61970-501

CIMXML data exchange format IEC 61970-552


April 26, 2017

IEC 61970/CGMES Documents

The canonical CIM is big and cannot be used as is

A profile is a subset of CIM for a dedicated information exchange, e.g.

• Basic Network model describing equipment, connectivity parameters etc; EQ core – IEC 61970-452

• Short circuit data; EQ SC – IEC 61970-452

• Operational parameters for EMS; EQ OP – IEC 61970-452

• Dynamics parameters; DY – IEC 61970-457

• Display layout; DL – IEC 61970-453

• Geographical location; GL

• Power flow initial values; SSH – IEC 61970-456

• Electrical nodes or power flow busses; TP – IEC 61970-456

• Power flow solution; SV – IEC 61970-456

• Frames; IEC 61970-459, in progress

• Network model projects; IEC 61970-460, in progress

• Generic dataset; IEC 61970-452, intended to replace header information in IEC 61970-552


April 26, 2017

Profile Documents

Slide 13

Network applications calculate with bus-branch data

Real power system has breakers and measurements,

they are node-breaker based

Two types of network models

• Bus-branch (BB)

• Node-breaker (NB)

BB models can be derived from NB models

Existing standards for application data is BB

• IEEE

• PSS/E

• PSLF

• DEF

•...

CIM is both NB and BB


April 26, 2017

Network Applications Data Exchange

G

NB

to

BB

Slide 14


April 26, 2017

Use of Profiles with Network Applications, Power Flow

Power

Flow

Network

Model

Builder

TP Busses

Retained Sw.

SSH Out of service

Switch Status

Data Modeller/Engineering

SSH Injection, active/reactive

Voltage set point

Tap position

Limits

SV Islands

Voltage, amplitude/angle

Injection, active/reactive

Power flow, active/reactive

Tap position

Switch status

EQ

BB

EQ

NB

Slide 15


April 26, 2017

Use of Profiles with Network Applications, Details

SSH

Device Status

Initialization/Edit

Topology &

Network Solution

Algorithm

Energy

Forecasts &

Schedules

SV

Energy Injection

Initialization/Edit

Control Setting

Initialization/Edit

Physical Model

Select / Edit

Monitoring

Initialization/Edit

Planned

Construction

Projects

EQ

Outage

Schedules

Network As-Built

Model Parts

- Status

- Switch status

- In Service

- Branch end

- Tap positions

- Control settings

- Voltage regulation

- Flow regulation

- SIPS

- Monitoring

- Operating limits

- Other

- Energy Injections

- Bulk generation

- Solar

- Wind

- Storage

- Traditional Load

- DR

- etc,

TP- TopologyNodes

- association to

conducting equipment

- Energized State

- Island Topology

- BusVoltage

- Bus Injections

- Terminal flows

- Controls

- Violations

Datasets

Described by

CIM Profiles

Model Parts

Diagram Layout

Dynamics

DL

DY

GLGeo Locations

Contingency List CL

- Equipment

- Containment

- Connectivity

- Controls

- SIPS

- Equipment Rating

- Normal operations

- Energy allocation

External

Sources

Case Parts

Case Parts

Repository

Measurement

Sources

Slide 16


April 26, 2017

Modularisation Of Network Models In Areas (Frames)

TSO A My TSO

DSO C

~

DSO D

~

TSO E TSO F ~

~

Slide 17


April 26, 2017

Modularization Of Network Application Model Exchange

Modularization Of Data Sets

Frames and Model Authority Sets

Type of data, Profiles

Modularization In Time

Power System Projects

Croatia

Hungary

Bosnia

Herzegovina

Serbia Slovenia Italy

Austria

Equipment EQ

Steady State Hypothesis (Power flow inputs) SSH

Topology TP

State Variables SV…


April 26, 2017

Profile Development

CIM UML

Canonical Information and Semantic Models

Context

Message Syntax

Profile

Message

XML Schema

CIM/XML

XML Schema

Rules CIM/XML

Rules

Message Assembly


April 26, 2017

Profile Dependency

61970-453

Profiles

61970-452

Profiles

61970-456

Profiles

State

Variables

Profile

Topology

Profile

Equipment

Model

Profile

Schematic

Layouts

Profile

61970-451

Profiles

Analog

Measurements

Profile

Discrete

Measurements

Profile


April 26, 2017

IEC Method

UML toolEA

Profile tool

Profile*.html

CIM UML tool

Model*.doc

Validation

Statistics

61970-45261970-45661968-13

61970-30161968-1162325-301

Validation Report

Profile*.owl

*.xmi*.eap

Profile*.doc

Manualediting

Model template*.doc

Profile*.xsd

Profile*.rdf

Manualinsert file

Part*.doc 61968-3 through 61968-9

Profiledefinition

Model*.xml

(web publishing)

Model *xmi11.xml*xmi21.xml

*cimtool.xml

(automating EA function)

Canonical

Model in UML

Profiling tools

- EA

- CIMTool

Canonical model

Enable interoperability

Slide 21


April 26, 2017

CIM Tool Demo

Slide 22

Interoperability and conformance tests has been organized by EPRI and ENTSO-E

Interoperability tests

Purpose is to verify

‒ The CIM standard enables interoperability

‒ Vendor products interoperate

Conformance tests

Purpose is to verify vendor products conforms with the standard

Currently ENTSO-E host a conformance procedure for CGMES 2.4.15, three levels of conformance

Bronze, Silver and Gold

ENTSO-E TSO are expected to be conformant to CGMES 2.4.15 during 2017.

Interoperability tests are being planned summer 2017 for next ENTSO-E profile CGMES 2.5


April 26, 2017

Interoperability And Conformance

Slide 23

18-19/12 2000 1th test in Orlando

ABB, ALSTOM (and Langdale), Siemens, PsyCor, CIM-Logic, SISCO

29/4-1/5 2001 2nd test in Las Vegas

ABB, ALSTOM, Siemens, CIM-Logic, SISCO

26-28/9 2001 3rd test in Monterey

ABB, ALSTOM, Siemens, PsyCor, SISCO

14-17/7 2002 4th test in San Francisco

ABB, PTI(PsyCor), Langdale, GE Harris

2 August 2002 Beijing

NEPDCC, CEPRI, NARI, Tsinghua, Luneng, Dongfang

18-20/11 2003 5th test in San Francisco

Alstom, Shaw PTI, SISCO, SNC Lavalin

19/7 2004 6th test at CAISO in Folsom

Areva, EDF, Incremental Systems, PTI, Siemens, Sisco

26-30/9 2005 7th test at CAISO in Folsom

Areva, EDF, ABB, PTI, Siemens, Sisco, Xtensible Solutions


April 26, 2017

Interoperability Tests 1

Slide 24

30 March 2006 8th test in San Francisco

Areva, EDF, PTI, SNC Lavalin, ABB (remote)

1 Oct 2006 9th test in Washington DC

ABB, EDF, GE, Siemens-PTI, Sisco

17 Sept 2007 10th test in San Francisco

ABB, Areva, GE, Siemens, Siemens-PTI, SNC

13 October 2008 11th test in Washington DC

Areva, GE, Siemens, Siemens PTI, SNC, SISCO

2009-2014 July by ENTSO-E

2016 July by ENTSO-E

2017 Being planned by ENTSO-E


April 26, 2017

Interoperability Tests 2

Slide 25

Organized by ENTSO-E starting 2014

CGMES 2.4.15 conformance documents

• Application process, application and comments documents

• Function category description

• Use case description

• Function category matrix

• Report template

Test configurations

• Micro grid

• Mini grid

• Small grid

• Real grid


April 26, 2017

Conformance Tests

Slide 26


April 26, 2017

NL_Busbar__4u=102.33 %

Uang=-3.48874 °

NL-Busbar_3u=101.70 %

Uang=-1.71291 °


Uang=-3.48874 °

NL-_Busbar_1u=102.15 %

Uang=-6.35443 °


Uang=0.00000 °

NL-Line_4

P=28.628 MW

Q=-3.961 Mvar

NL-Line_2

P=50.565 MW

Q=-87.950 Mvar

NL-Line_1

P=51.922 MW

Q=-102.183 Mvar

NL-Line_5

P=95.994 MW

Q=-158.287 Mvar

NL-Line_3

P=28.045 MW

Q=-1.486 Mvar

NL_TR2_3

Tap=5NL-TR2_1

Tap=-2

NL_TR2_2

Tap=17

busbarcoupler 1B1

NL-G2

P=-140.000 MW

Q=26.681 Mvar

NL-G3

P=-150.000 MW

Q=26.681 Mvar

NL-G1

P=-556.714 MW

Q=-249.198 Mvar

NL-Load_3

P=488.265 MW

Q=231.608 Mvar

NL-Load_2

P=10.000 MW

Q=10.000 Mvar

NL-Load_1

P=90.000 MW

Q=280.000 Mvar

NL-S1

P=0.000 MW

Q=-52.178 Mvar

P=-298.481 MW

Q=110.598 Mvar

P=290.000 MW

Q=-53.361 Mvar

P=-288.964 MW

Q=69.869 Mvar

P=299.369 MW

Q=-93.418 Mvar

P=-232.291 MW

Q=64.421 Mvar

P=232.291 MW

Q=-64.421 Mvar

P=556.714 MW

Q=249.198 Mvar

P=-555.343 MW

Q=-202.611 Mvar

BoundaryNL MAS

XCA_AL11u=102.79 %

Uang=-6.58811 °

XZE_ST23u=102.50 %

Uang=-5.58021 °

BE-Busbar_6u=105.00 %

Uang=-9.39133 °


Uang=-6.65080 °


Uang=-7.05718 °


Uang=-8.77012 ° XZE_ST24u=102.26 %

Uang=-5.63853 °BE-Busbar_2u=99.94 %

Uang=-7.62490 °

XWI_GY11u=102.72 %

Uang=-6.57644 °


Uang=-6.78071 °

XKA_MA11u=103.15 %

Uang=-6.74695 °

BE-Line_5

P=82.840 MW

Q=-138.451 Mvar

BE-Line_4

P=36.859 MW

Q=-80.683 Mvar

BE-Line_3

P=36.590 MW

Q=-54.186 Mvar

BE-Line_7

P=26.805 MW

Q=-1.490 Mvar

BE-Line_1

P=27.365 MW

Q=-0.426 MvarBE-Line_2

P=27.875 MW

Q=2.748 Mvar

BE-Line_6

P=11.222 MW

Q=1.076 Mvar

BE-TR2_2

Tap=10

BE-TR2_3

Tap=18

BE-TR2_1

Tap=16

BE-TR3_1

Tap=17

BE-G2

P=-118.000 MW

Q=-92.612 Mvar

BE-G1

P=-90.000 MW

Q=51.116 Mvar

BE-Load_2

P=200.000 MW

Q=50.000 Mvar

BE-Load_1

P=200.000 MW

Q=90.000 Mvar

BE_S2

P=1.181 MW

Q=-59.058 Mvar

BE_S1

P=0.000 MW

Q=-330.750 Mvar

P=55.296 MW

Q=39.192 Mvar

P=90.000 MW

Q=-51.116 Mvar

P=-89.686 MW

Q=57.132 Mvar

P=-55.088 MW

Q=221.867 MvarP=55.890 MW

Q=-217.566 Mvar

P=-55.226 MW

Q=-38.250 Mvar

P=-216.198 MW

Q=-85.368 Mvar

P=99.218 MW

Q=3.304 Mvar

BE MAS

Micro Grid Base Case

L-1230804819

P=1.000 MW

Q=0.000 Mvar

BE_TR_BUS1u=105.00 %

Uang=-9.39133 °

BE_Breaker_1

P=-55.088 MW

Q=221.867 Mvar

P=55.088 MW

Q=-221.867 Mvar

BE_Breaker_2

P=55.890 MW

Q=-217.566 Mvar


Uang=-6.78071 °

P=-55.890 MW

Q=217.566 Mvar


Uang=-9.39133 °

BE_Breaker_3

P=55.226 MW

Q=38.250 Mvar

P=-55.226 MW

Q=-38.250 Mvar

BE_TR_BUS4u=99.70 %

Uang=-8.77012 °

BE_Breaker_4

P=55.296 MW

Q=39.192 Mvar

P=-55.296 MW

Q=-39.192 Mvar


Uang=-9.39133 °

BE_Breaker_5P=89.686 MW

Q=-57.132 Mvar

P=-89.686 MW

Q=57.132 Mvar

BE_Breaker_10

P=118.000 MW

Q=92.612 Mvar

BE_BUSBAR_10u=104.70 %

Uang=-6.65080 °

P=-118.000 MW

Q=-92.612 MvarP=118.000 MW

Q=92.612 Mvar

BE_BUSBAR_12u=108.68 %

Uang=-6.78071 °

BE_Breaker_12

P=99.218 MW

Q=3.304 Mvar

P=-99.218 MW

Q=-3.304 Mvar

NL_TR_BUS1u=102.33 %

Uang=-3.48874 °

NL_TR_BUS2u=101.80 %

Uang=0.00000 °

NL_BREAKER_1P=-555.343 MW

Q=-202.611 Mvar

P=555.343 MW

Q=202.611 Mvar

NL_BREAKER_1

P=-556.714 MW

Q=-249.198 Mvar

P=556.714 MW

Q=249.198 Mvar

N1230822396u=102.33 %

Uang=-3.48874 °

NL_BREAKER_3

P=-288.964 MW

Q=69.869 Mvar

P=288.964 MW

Q=-69.869 Mvar

N1230822413u=101.70 %

Uang=-1.71291 °

NL_BREAKER_4

P=-290.000 MW

Q=53.361 Mvar

P=290.000 MW

Q=-53.361 Mvar

CIRCB-1230991526

N1230991529u=99.94 %

Uang=-7.62490 °

P=23.838 MW

Q=-1.271 Mvar

P=-23.838 MW

Q=1.271 Mvar

CIRCB-1230991544

P=-25.773 MW

Q=-2.828 Mvar

N1230991550u=99.94 %

Uang=-7.62490 °

P=25.773 MW

Q=2.828 Mvar

CIRCB-1230991718

P=-82.840 MW

Q=138.451 Mvar

N1230991724u=108.68 %

Uang=-6.78071 °

P=82.840 MW

Q=-138.451 Mvar

CIRCB-1230991736

N1230991739u=108.68 %

Uang=-6.78071 °

P=-36.590 MW

Q=54.186 Mvar

P=36.590 MW

Q=-54.186 Mvar

CIRCB-1230992174

CIRCB-1230992183

CIRCB-1230992192

N1230992195u=102.15 %

Uang=-6.35443 °

N1230992198u=102.15 %

Uang=-6.35443 °

N1230992201u=102.15 %

Uang=-6.35443 °

P=-95.994 MW

Q=158.287 Mvar

P=95.994 MW

Q=-158.287 Mvar

P=-51.922 MW

Q=102.183 Mvar

P=51.922 MW

Q=-102.183 Mvar

P=-50.565 MW

Q=87.950 Mvar

P=50.565 MW

Q=-87.950 Mvar

N1230992228u=102.33 %

Uang=-3.48874 °

N1230992231u=102.33 %

Uang=-3.48874 °

CIRCB-1230992240

CIRCB-1230992249

P=-28.628 MW

Q=3.961 Mvar

P=28.628 MW

Q=-3.961 Mvar

P=-28.045 MW

Q=1.486 Mvar

P=28.045 MW

Q=-1.486 Mvar

CIRCB-1230992276

CIRCB-1230992285

N1230992288u=99.70 %

Uang=-8.77012 °

N1230992291u=99.70 %

Uang=-8.77012 °

P=27.875 MW

Q=2.748 Mvar

P=11.222 MW

Q=1.076 Mvar

P=-27.875 MW

Q=-2.748 Mvar

P=-11.222 MW

Q=-1.076 Mvar

CIRCB-1230992399

CIRCB-1230992408

N1230992411u=99.94 %

Uang=-7.62490 °

N1230992414u=99.94 %

Uang=-7.62490 °

P=-31.314 MW

Q=-1.205 MvarP=31.314 MW

Q=1.205 Mvar

P=-17.296 MW

Q=-0.353 MvarP=17.296 MW

Q=0.353 Mvar

Micro Grid Test Network Example

Slide 27


April 26, 2017

ENTSO-E CGMES 2.4.15 Conformance Matrix

Slide 28

UML diagram types

• Class

• Sequence

UML elements

• Package

• Class inheritance

• Class

• Attribute

• Roles

• Association

• Roles

• Objects


April 26, 2017

Unified Modelling Language - UML

class LineModel

Conductor

+ length: Length [0..1]

DCLineSegmentACLineSegment

+ b0ch: S usceptance [0..1]

+ bch: S usceptance [0..1]

+ g0ch: Conductance [0..1]

+ gch: Conductance [0..1]

+ r: Resistance [0..1]

+ r0: Resistance [0..1]

+ x: Reactance [0..1]

+ x0: Reactance [0..1]

PerLengthSequenceImpedance

+ b0ch: S usceptancePerLength [0..1]

+ bch: S usceptancePerLength [0..1]

+ g0ch: ConductancePerLength [0..1]

+ gch: ConductancePerLength [0..1]

+ r: ResistancePerLength [0..1]

+ r0: ResistancePerLength [0..1]

+ x: ReactancePerLength [0..1]

+ x0: ReactancePerLength [0..1]

+S equenceImpedance0..1

+LineS egments

0..*

Slide 29

Technologies

• General purpose language, e.g. Java, C#, C++, C …

• Relational database, query language is SQL

• Class -> Table

• ID -> Table row

• Attribute -> Column

• Role -> Column and foreign key

• Value Row/Column crossing

• Graph database, query language is SPARQL

• Class -> rdf:type Predicate

• ID -> Subject

• Attribute/Role -> Predicate

• Value -> Object


April 26, 2017

Implementing CIM

Col1 Col2

27ad07c9-.. 34e5b362-..

…

#1

#..

Table

Subject

Object

Predicate

Slide 30

UML Basics

April 26, 2017

Classes and Attributes

A Class – a collection of instances with same characteristics, e.g.

- ACLineSegment

- PowerTransformer

- Substation

An attribute – a characteristic value, e.g.

- ACLineSegment r – series resistance

- ACLineSegment x – series reactance

Implementation mapping;

- Class - Relational table, Subject in triple

- Attribute - Relational table column, Predicate in triple

- Attribute value - Relational table column value, Object in triple

class LineModel

ACLineSegment









urn:uuid:34e5b3…

2,05 ACLineSegmen.r Subject

Object

Slide 31

UML Basics

April 26, 2017

Roles

Relations between classes, a pair of Roles

Cardinalities specify number of instances

1 exactly one

0..1 one instance may exist

0..* any number of instances

1..* at least one


Role – Relational foreign key, Predicate in triple

class LineModel

ACLineSegment


















+S equenceImpedance 0..1

+LineS egments

0..*

An ACLineSegment

may have a

SequenceImpedance

urn:uuid:34e5b3…

urn:uuid:5b334e…

ACLineSegment.

SequenceImpedance Subject

Object

Roles

Slide 32

UML Basics

April 26, 2017

Inheritance

class LineModel

Conductor


DCLineSegmentACLineSegment


















+S equenceImpedance0..1

+LineS egments

0..*

A subclass inherits its superclass characteristics

- A superclass class not affected by subclass

- A subclass class get all attributes and

relations from the superclass


- Relational typically a mix of

- Separate tables

- Superclass merged into subclass table

- Triples

- A dedicated Predicate “rdfs:subClassOf”

Superclass

Subclass

Cim:ACLineSegment

cim:Conductor

rdfs:subClassOf Subject

Slide 33


April 26, 2017

Implementing CIM, Example

Relational tables Graph subject-predicate-object triples

34e5b362-..

cim:ACLineSegment

rdf:type

2,05 cim:ACLinesegment.r

27ad07c9-..

cim:Terminal

rdf:type

Terminal.ConductingEquipment

ID r

34e5b362-.. 2,05

…

#1

#..

ID ConductingEquipment

27ad07c9-.. 34e5b362-..

…

#1

#..

ACLineSegment

Terminal

<cim:ACLineSegment rdf:about="17086487-..">

<cim:ACLineSegment.r>2.200000</cim:ACLineSegment.r>

</cim:ACLineSegment>

<cim:Terminal rdf:about="1ef0715a-..">

<cim:Terminal.ConductingEquipment rdf:resource="urn:uuid:17086487-.."/>

</cim:Terminal>

Slide 34

Canonical CIM

April 26, 2017

IEC Top Level

Canonical CIM

April 26, 2017

Top Level Package Dependencies

class PackageDependencies

IEC61970

(from TC57CIM)

PackageDependenciesCIMVer sion

+ date: Date [0..1] = 2014-11-13 {readOnly}

+ version: String [0..1] = 7 {readOnly}

IEC61968

(from TC57CIM)

IEC62325

(from TC57CIM)

PackageDependencies

(from TC57CIM)

IEC62325::IEC62325CIMVer sion


+ version: String [0..1] = IEC62325CIM03v02 {readOnly}







Base

(from IEC61970) TC57CIMVer sion

+ majorVersion: String = 2016

+ minorVersion: String = 01

+ publishedDate: Date

Dy namics

(from IEC61970)

TC57CIM

(from Model)

tags

nsprefix = cim

nsuri = http://iec.ch/TC57/2016/CIM-schema-cim#

Canonical CIM

April 26, 2017

IEC 61970 Base Modularization cla ss IEC61970Dependencies

Equiv a lents

(from Base)

P r otect ion

(from Base)

SCADA

(from Base)

Gener a t ion

(from Base)

LoadModel

(from Base)

Topology

(from Base)Meas

(from Base)

W ir es

(from Base)

Doma in

(from Base)

Cor e

(from Base)

Oper a t iona lLimits

(from Base)

Contr olAr ea

(from Base)

Gener a t ionTr a iningSimula t ion

(from Generation) P r oduct ion

(from Generation)

Cont ingency

(from Base)

Auxi l ia r y Equipment

(from Base)

Sta teVa r iables

(from Base)

Diagr amLay out

(from Base)

DC

(from Base)

Canonical CIM

April 26, 2017

Core cla ss Ma in

Bay

Equipment

IdentifiedObject

PSRTy pe

IdentifiedObject

Power Sy stemResour ce

IdentifiedObject

BasePower

ACDCTerminal

Ter mina l

EquipmentConta iner

IdentifiedObject

BaseVoltage

Connect iv ity NodeConta iner

VoltageLev el

Substa t ion

IdentifiedObject

SubGeogr aphica lRegion

IdentifiedObject

Geogr aphica lRegion

Conduct ingEquipment

This is an AC diagram

IdentifiedObject

BaseFr equency

+BaseVoltage 0..1

+ConductingEquipment

0..*

+Region 0..1

+Substations 0..*

+VoltageLevel

0..* +BaseVoltage 1

+Terminals

0..*


1

+EquipmentContainer

0..1

+Equipments

0..*

+Region 0..1

+Regions 0..*

+VoltageLevel 0..1

+Bays 0..*

+Substation 1

+VoltageLevels 0..*

+PowerSystemResources

0..*

+PSRType

0..1

+Bays

0..*

+Substation

0..1

Canonical Model

April 26, 2017

Generic Data Set cla ss Gener icDa taSet

Cor e::Ident if iedObject

Da taSetMember

InstanceSet

+ version: Integer

+ minorVersion: Integer

ObjectCr ea t ionObjectDelet ionObjectModif ica t ion

ChangeSetMemberChangeSet

ObjectRev er seModif ica t ion

Da taSet

InstanceSetMember

P r of i le

Gener icDa taSetVer sion

+ majorVersion: String = 2016

+ minorVersion: String = 01

+ published: Date

Gener icDa taset

(from Base)

tags

nsprefix = gds

nsuri = http://iec.ch/TC57/2016/CIM-schema-gds#

+ObjectChange

0..*+Changeset

0..1

+ObjectReverseModification

0..1

+ObjectModification

0..1

+Profileset

0..*

+Profile 1..*

+AlternateCIMDataObject

0..*

+Dataset

1

+TargetingCIMDataObject

0..*

+TargetObject

1

+PropertiesCIMDataObject

0..1

+PropertiesObject

0..1

Canonical Model

April 26, 2017

Topology

Bus

Branch

Detailed

Substation

class Main

Core::

ConnectivityNode

Core::

ConnectivityNodeContainer

Core::

Terminal

TopologicalNode

Meas::

Measurement

Core::

ConductingEquipment

StateVariables::

TopologicalIsland

Core::

PowerSystemResource

Core::

IdentifiedObject

BusNameMarker

Core::

Equipment

+BusNameMarker

0..1

+Terminal1..*

+AngleRef_TopologicalIsland0..1

+AngleRef_TopologicalNode

0..1

+Measurements 0..*

+Terminal0..1

+TopologicalNode

0..*

+ConnectivityNodeContainer 0..1

+Terminals

0..*

+ConductingEquipment 1+Terminals

0..*

+ConnectivityNode 0..1

+Terminal0..*

+TopologicalNode

0..1

+ConnectivityNodes 0..*

+ConnectivityNodeContainer

1+ConnectivityNodes 0..*

+TopologicalNode 0..1

+TopologicalNodes 1..*

+TopologicalIsland 1

Canonical CIM

April 26, 2017

Wires, Equipment class Inher itanceHier a r chy

Cor e::

Power Sy stemResour ce

VoltageContr olZone

Cor e::VoltageLev el

TapChanger

Cor e::

Ident if iedObject

P lantLine

Cor e::Bay

Cor e::

Connect iv ity NodeConta iner

Cor e::Substa t ion

Cor e::


Cor e::

Equipment

Cor e::

EquipmentConta inerCompositeSwitch

Canonical CIM

April 26, 2017

Wires,

Conducting

Equipment

class Inher itanceHier a r chy

Busba r Sect ion

ShuntCompensa tor

ACLineSegment

Sta t icVa r Compensa tor

Regula t ingCondEq

Junct ion

Gr ound

Conductor

Ener gy Sour ce

Ser iesCompensa tor

Fr equency Conv er ter

Connector

Switch

Ener gy Consumer

Cor e::


Sy nchr onousMachine

For subclasses of Switch

refer to diagram

SwitchingEquipment

Rota t ingMachine

Asy nchr onousMachine

Power Tr ansfor mer

Clamp

Ear thFaultCompensa tor

Gr oundingImpedance

Peter senCoil

Exter na lNetwor kInject ion

Canonical CIM

April 26, 2017

Wires,

Switch

Equipment

class SwitchingEquipment

LoadBr eakSwitch

Fuse

Jumper

Disconnector

P r otectedSwitch

+ breakingCapacity: CurrentFlow [0..1]

ConductingEquipment

Switch

+ normalOpen: Boolean [0..1]

+ ratedCurrent: CurrentFlow [0..1]

+ switchOnCount: Integer [0..1]

+ switchOnDate: DateTime [0..1]

+ retained: Boolean [0..1]

+ open: Boolean [0..1]

Gr oundDisconnector

Br eaker

+ inTransitTime: Seconds [0..1]

Sect iona l iser

Recloser

Canonical CIM

April 26, 2017

Wires,

Line Model

class LineModel

Ser iesCompensa tor





+ varistorPresent: Boolean [0..1]

+ varistorRatedCurrent: CurrentFlow [0..1]

+ varistorVoltageThreshold: Voltage [0..1]

IdentifiedObject

Cor e::

SubGeogr aphica lRegion

Line

PowerSystemResource

Cor e::Equipment

ConnectivityNodeContainer

Cor e::

EquipmentConta iner

Conductor


Cor e::


ACLineSegment

+ b0ch: Susceptance [0..1]

+ bch: Susceptance [0..1]





+ shortCircuitEndTemperature: Temperature [0..1]



Per LengthPhaseImpedance

+ conductorCount: Integer [0..1]

Per LengthSequenceImpedance

+ b0ch: SusceptancePerLength [0..1]

+ bch: SusceptancePerLength [0..1]







PhaseImpedanceDa ta

+ b: SusceptancePerLength [0..1]


+ sequenceNumber: Integer [0..1]


Per LengthImpedanceIdentifiedObject

Per LengthLinePa r ameter

+PerLengthImpedance 0..1

+ACLineSegments 0..*

+EquipmentContainer

0..1 +Equipments

0..*

+Region

0..1

+Lines

0..*

+PhaseImpedance 1

+PhaseImpedanceData 1..*

Canonical CIM

April 26, 2017

Wires,

Transformer

class Tr ansfor mer

Equipment

Tr ansfor mer Tank

IdentifiedObject

Tr ansfor mer End

+ bmagSat: PerCent [0..1]

+ endNumber: Integer [0..1]

+ grounded: Boolean [0..1]

+ magBaseU: Voltage [0..1]

+ magSatFlux: PerCent [0..1]

+ rground: Resistance [0..1]

+ xground: Reactance [0..1]

Power Tr ansfor mer

+ beforeShCircuitHighestOperatingCurrent: CurrentFlow [0..1]

+ beforeShCircuitHighestOperatingVoltage: Voltage [0..1]

+ beforeShortCircuitAnglePf: AngleDegrees [0..1]

+ highSideMinOperatingU: Voltage [0..1]

+ isPartOfGeneratorUnit: Boolean [0..1]

+ operationalValuesConsidered: Boolean [0..1]

+ vectorGroup: String [0..1]

Equipment

Cor e::


IdentifiedObject

Tr ansfor mer Sta r Impedance





ACDCTerminal

Cor e::Ter mina l

+ phases: PhaseCode [0..1]

«enumeration»

WindingConnect ion

D

Y

Z

Yn

Zn

A

I

Power Tr ansfor mer End

+ b: Susceptance [0..1]

+ b0: Susceptance [0..1]

+ connectionKind: WindingConnection [0..1]

+ g: Conductance [0..1]

+ g0: Conductance [0..1]

+ phaseAngleClock: Integer [0..1]



+ ratedS: ApparentPower [0..1]

+ ratedU: Voltage [0..1]


+ x0: Reactance [0..1]Tr ansfor mer TankEnd

+ phases: PhaseCode [0..1]

IdentifiedObject

Tr ansfor mer MeshImpedance





IdentifiedObject

Tr ansfor mer Cor eAdmit tance

+ b: Susceptance [0..1]

+ b0: Susceptance [0..1]

+ g: Conductance [0..1]

+ g0: Conductance [0..1]

IdentifiedObject

Cor e::

BaseVoltage

+Terminals

0..*


1

+TransformerTanks0..*

+PowerTransformer

0..1

+BaseVoltage

0..1


0..*

+ToMeshImpedance 0..*

+ToTransformerEnd

1..*

+TransformerEnd

0..*

+StarImpedance

0..1

+TransformerEnd 0..*

+Terminal 0..1

+PowerTransformer0..1

+PowerTransformerEnd 0..*

+CoreAdmittance

0..1

+TransformerEnd

0..*

+FromMeshImpedance 0..*

+FromTransformerEnd

1

+TransformerTankEnds 1..*

+TransformerTank 0..1

+TransformerEnds

0..*

+BaseVoltage 0..1

Canonical CIM

April 26, 2017

Wires,

TapChanger

cla ss TapChanger

PowerSystemResource

TapChanger

+ controlEnabled: Boolean [0..1]

+ highStep: Integer [0..1]

+ initialDelay: Seconds [0..1]

+ lowStep: Integer [0..1]

+ ltcFlag: Boolean [0..1]

+ neutralStep: Integer [0..1]

+ neutralU: Voltage [0..1]

+ normalStep: Integer [0..1]

+ subsequentDelay: Seconds [0..1]

+ step: Float [0..1]

SeasonDayTypeSchedule

Regula t ionSchedule

PowerSystemResource

Cor e::Equipment

Cor e::


PowerSystemResource

Regula t ingContr ol

+ discrete: Boolean [0..1]

+ enabled: Boolean [0..1]

+ mode: RegulatingControlModeKind [0..1]

+ monitoredPhase: PhaseCode [0..1]

+ targetDeadband: Float [0..1]

+ targetValue: Float [0..1]

+ targetValueUnitMultiplier: UnitMultiplier [0..1]

PhaseTapChanger

Ra t ioTapChanger

+ stepVoltageIncrement: PerCent [0..1]

+ tculControlMode: TransformerControlMode [0..1]


TapSchedulePower Tr ansfor mer

Power Tr ansfor mer End

IdentifiedObject

Tr ansfor mer End

TapChanger Contr ol

+ limitVoltage: Voltage [0..1]

+ lineDropCompensation: Boolean [0..1]

+ lineDropR: Resistance [0..1]

+ lineDropX: Reactance [0..1]

+ reverseLineDropR: Resistance [0..1]

+ reverseLineDropX: Reactance [0..1]

PhaseTapChanger NonLinea r

+ voltageStepIncrement: PerCent [0..1]

+ xMax: Reactance [0..1]

+ xMin: Reactance [0..1]

PhaseTapChanger Linea r

+ stepPhaseShiftIncrement: AngleDegrees [0..1]

+ xMax: Reactance [0..1]

+ xMin: Reactance [0..1]

PhaseTapChanger Sy mmetr ica l PhaseTapChanger Asy mmetr ica l

+ windingConnectionAngle: AngleDegrees [0..1]

IdentifiedObject

PhaseTapChanger Table

PhaseTapChanger TablePoint

+ angle: AngleDegrees [0..1]

IdentifiedObject

Ra t ioTapChanger Table

Ra t ioTapChanger TablePoint

TapChanger TablePoint

+ b: PerCent [0..1]

+ g: PerCent [0..1]

+ r: PerCent [0..1]

+ ratio: Float [0..1]

+ step: Integer [0..1]

+ x: PerCent [0..1]

PhaseTapChanger Tabula r

«enumeration»

Regula t ingContr olModeK ind

voltage

activePower

reactivePower

currentFlow

admittance

timeScheduled

temperature

powerFactor

+TransformerEnd1

+PhaseTapChanger

0..1

+TransformerEnd

1

+RatioTapChanger

0..1

+RegulationSchedule

0..*

+RegulatingControl

1

+RatioTapChanger

0..*

+RatioTapChangerTable

0..1

+TapChanger

0..*

+TapChangerControl 0..1

+RatioTapChangerTablePoint

1..*

+RatioTapChangerTable

1

+TapSchedules

0..*

+TapChanger

1

+PhaseTapChangerTable

0..1

+PhaseTapChangerTabular0..*

+PowerTransformer0..1

+PowerTransformerEnd

0..*

+PhaseTapChangerTablePoint1..*

+PhaseTapChangerTable

1

Canonical CIM

April 26, 2017

Wires,

Regulating

Control

class Regula t ingEquipment

ACDCTerminal

Cor e::

Ter mina l

PowerSystemResource

TapChanger

ConductingEquipment

Regula t ingCondEq

+ controlEnabled: Boolean [0..1]


Regula t ionSchedule

IOPoint

Meas::Contr ol

Fr equency Conv er terCurve

React iv eCapabil i ty Cur v e

Sy nchr onousMachine

Sta t icVa r Compensa tor

ShuntCompensa tor

PowerSystemResource

Regula t ingContr ol

+ discrete: Boolean [0..1]

+ enabled: Boolean [0..1]

+ mode: RegulatingControlModeKind [0..1]

+ monitoredPhase: PhaseCode [0..1]

+ targetDeadband: Float [0..1]

+ targetValue: Float [0..1]

+ targetValueUnitMultiplier: UnitMultiplier [0..1]

«enumeration»

Regula t ingContr olModeK ind

voltage

activePower

reactivePower

currentFlow

admittance

timeScheduled

temperature

powerFactor

TapChanger Contr ol

+ limitVoltage: Voltage [0..1]

+ lineDropCompensation: Boolean [0..1]

+ lineDropR: Resistance [0..1]

+ lineDropX: Reactance [0..1]

+ reverseLineDropR: Resistance [0..1]

+ reverseLineDropX: Reactance [0..1]


TapSchedule

Rota t ingMachine

Exter na lNetwor kInject ion

+ governorSCD: ActivePowerPerFrequency [0..1]

+ ikSecond: Boolean [0..1]

+ maxInitialSymShCCurrent: CurrentFlow [0..1]

+ maxP: ActivePower [0..1]

+ maxQ: ReactivePower [0..1]

+ maxR0ToX0Ratio: Float [0..1]

+ maxR1ToX1Ratio: Float [0..1]

+ maxZ0ToZ1Ratio: Float [0..1]

+ minInitialSymShCCurrent: CurrentFlow [0..1]

+ minP: ActivePower [0..1]

+ minQ: ReactivePower [0..1]

+ minR0ToX0Ratio: Float [0..1]

+ minR1ToX1Ratio: Float [0..1]

+ minZ0ToZ1Ratio: Float [0..1]

+ referencePriority: Integer [0..1]

+ voltageFactor: PU [0..1]

+ p: ActivePower [0..1]

+ q: ReactivePower [0..1]

+TapSchedules 0..*

+TapChanger 1

+RegulatingCondEq

0..*

+RegulatingControl

0..1

+Terminal 0..1

+RegulatingControl0..*

+ReactiveCapabilityCurves

0..*

+SynchronousMachines

1..*

+RegulationSchedule 0..*

+RegulatingControl 1

+TapChanger

0..*

+TapChangerControl 0..1

+InitialReactiveCapabilityCurve0..1

+InitiallyUsedBySynchronousMachines1..*

Slide 47


April 26, 2017

Enterprize Architect Demo

Slide 48


April 26, 2017

Network Model Node-Breaker Example

Slide 49


April 26, 2017

Network Model Example In CIM

Slide 50

CIMXML – IEC 61970-552

• Based on RDF triples, a semantic web technology

• But has custom extensions no longer needed with OWL, a revision is worked on

• Formatting rules based on canonical UML

• Generic, no adaptation needed for profiles

• Has lots of empty space, compress from 20 to 1

XML Schema – IEC 61968-100

• XML Schema manually generated from rules in IEC 61968-100

There are interoperability issues between IEC 61970-552 and IEC 61968-100, e.g.

• Object IDs

Data Exchange Formats

April 26, 2017

Two Main Types

Slide 51

CIMXML is based on RDF/XML

<cim:ClassName rdf:about=“mRID”>

‒ <cim:ClassName.AttributeName>value</cim:ClassName.AttributeName>

‒ <cim:ClassName.RoleName rdf:resource=“mRID”/>

</cim:ClassName>

CIMXML can with a few minor changes be used with the semantic web


April 26, 2017

CIMXML – IEC 61970-552

Subject:

mRID

Object:

cim:ClassName

Object:

value or mRID

Predicate:

rdf:type

Predicate:

cim:ClassName.AttributeName or

cim:ClassName.RoleName

Slide 52

RDF/XML template

<cim:ClassName rdf:about=“mRID”>

‒ <cim:ClassName.AttributeName>value</cim:ClassName.AttributeName>

‒ <cim:ClassName.RoleName rdf:resource=“mRID”/>

</cim:ClassName>

Example data

<cim:ACLineSegment rdf:about=" urn:uuid:27ad07c9-033f-3d4a-925b-106304ae…">

‒ <cim:IdentifiedObject.name>AMHE400MARC LINE</cim:IdentifiedObject.name>

‒ <cim:ACLineSegment.x>27.749</cim:ACLineSegment.x>

‒ <cim:ACLineSegment.r>3.416</cim:ACLineSegment.r>

‒ <cim:ACLineSegment.bch>0.0002914</cim:ACLineSegment.bch>

‒ <cim:Equipment.EquipmentContainer rdf:resource="urn:uuid:bfcfb9c8-b1…"/>

‒ …


April 26, 2017

CIMXML – IEC 61970-552 Example

Slide 53


April 26, 2017

CIMXML – IEC 61970-552, Header

class Pa r t552

Sta tements Ful lModelDif fer enceModel

Model

+ created: DateTime

+ scenarioTime: DateTime

+ description: String

+ modelingAuthoritySet: URI [0..1]

+ profile: URI [1..*]

+ version: Integer

«Primitive»

URI

{root}

+Depending 0..*

+DependentOn 0..*

+reverseDifferences

0..1

+forwardDifferences

0..1

+SupersededBy 0..*

+Supersedes

0..*

Slide 54


April 26, 2017

CIMXML – IEC 61970-552, Dependencies Example

S1

S2

S3

S4

S5

S6

E1

E2Time

Equipment

T1

Profile

FullModel

DifferenceModel

DependentOn

Supersedes

T2

T4

Topology

T3

StateVariables

E3E3

E4

Slide 55

<md:FullModel rdf:about="urn:uuid:34e5b362-7771-4a8f-a5a8-571f76de9f41">

<md:Model.created>2014-10-24T14:26:47</md:Model.created>

<md:Model.scenarioTime>2014-10-24T12:02:49</md:Model.scenarioTime>

<md:Model.version>2</md:Model.version>

<md:Model.DependentOn rdf:resource="urn:uuid:2399cbd0-9a39-11e0-aa80-0800200c9a66"/>

<md:Model.description>CGMES Conformity Assessment: …. <md:Model.description>

<md:Model.modelingAuthoritySet>http://elia.be/CGMES/2.4.15</md:Model.modelingAuthoritySet>

<md:Model.profile>http://entsoe.eu/CIM/EquipmentCore/3/1</md:Model.profile>

<md:Model.profile>http://entsoe.eu/CIM/EquipmentShortCircuit/3/1</md:Model.profile>

<md:Model.profile>http://entsoe.eu/CIM/EquipmentOperation/3/1</md:Model.profile>

<md:Model.Supersedes rdf:resource="urn:uuid:d400c631-75a0-4c30-8aed-832b0d282e73"/>

</md:FullModel>


April 26, 2017

CIMXML – IEC 61970-552, Header Example

Slide 56


April 26, 2017

XML Spy Demo

Slide 57

The XMI format for exchange of UML models

• Is a weak standard resulting in poor tool interoperability

• Is described by an XML Schema so it a format description that lacks semantic capability

• Has a complex hierarchical structure making it difficult to process

The CIM RDF Schema (IEC 61970-501) for profile exchange

• Is not fully supported by all profiling tools, e.g. CIM Tool can’t import it

• Has several custom extensions not compatible with ontology specifications (RDF, RDFS, OWL)

• Cannot be read by ontology tools

Making CIM An Ontology

April 26, 2017

Issues

Slide 58

The semantic web architecture support

• Information resources distributed over the web

• Federation of distributed information resources

• Knowledge based reasoning with federated information resources, OWL2

CIM models are managed by Model Authorities, e.g. EU TSOs and DSOs

• Each Model Authority is responsible for is own CIM models

• But a Model Authority is heavily dependent on its neighbors CIM models

• So a complex exchange of CIM models is needed

CIM models available as semantic web information resources will greatly simplify sharing


April 26, 2017

Why Making CIM An Ontology?

Slide 59


April 26, 2017

Converting Canonical CIM to Ontologies

Ontology data Data and meta data

M2, UML

M1, CIM

M0, Data

UML IM as

XMI data

Translate UML IM as

OWL

Instances

Derive UML IM as

Ontology

Describe

CIM as

XMI data

Translate CIM as

OWL

Instances

Derive CIM as

Ontology

Describe

CIMXML

Instances

Describe

IM = Information Model

Slide 60


April 26, 2017

Converting Profiles to Ontologies

Ontology data Data and meta data

M2, UML

M1, CIM

Profile IM

as XMI

Translate Profile IM

as OWL

Instances

Derive Profile IM

as

Ontology

Profile

OWL

Instances

CIM as

OWL

Instances Create

Profiled

CIM as

OWL

Instances

Profiled

CIM as

Ontology

Derive

Describe

IM = Information Model

Slide 61


April 26, 2017

Ontology for UML

class xmi_uml

ModelE

PackageE

Element

+ documentation: string

+ pathName: string

+ scope: ScopeValues

+ stereotype: string

ClassEPropertyE

+ defaultValue: IdentifiedValueE

+ highCardinality: IdentifiedValueE

+ lowCardinality: IdentifiedValueE

AssociationE

EnumEEnumLiteralE

DependencyE

ClassElementPropertyElement

«xsd»

string

«xsd»

nonNegativeInteger«xsd»

integer«xsd»

positiveIntegerIdentifiedValueE

+ value: any

«enumeration»

ScopeValues

package

protected

public

private

GeneralizationE

Id

+ name: string

+ toolId: string

0..*

+supplier1

0..*

+domain

1

0..*

+superClass

10..*

+client1

+container 0..1

0..*

0..*

+domain

1

0..1

+side2

1

0..*

+container

0..1

1+inverse

0..1

0..*

+range

1

+subClass

1 0..*

0..1

+side1

1

0..*

+model 0..1

Slide 62


April 26, 2017

Protege Demo