IEEE Power & Energy Magazine - January/February 2016 - 74

Node-Switch Profile
EnergyConsumer
+ mRID : String
+ name : String
+ p : ActivePower
+ q : ActivePower

Switch
+ mRID : String
+ name : String
+ normalOpen : Boolean
+ open : Boolean
+ retained : Boolean

ACLineSegment
+ mRID : String
+ name : String
+ length : Length
+ b0ch : Susceptance
+ bch : Susceptance
+ g0ch : Conductance
+ gch : Conductance
+ r : Resistance
+ r0 : Resistance
+ x : Reactance
+ x0 : Reactance

ConnectivityNode
+ mRID : String
+ name : String

ConductingEquipment
1

ConnectivityNode
1
Terminals
1
Terminals
2
ConductingEquipment
1
Terminals
2

Terminals
1..*
Terminal
+ mRID : String
+ name : String
+ connected : Boolean
+ sequenceNumber : Integer
+ phases : PhaseCode

ConductingEquipment
1

figure 5. A subset for a node-switch profile.

profile. all association multiplicities have been tightened
so they are no longer optional. for some associations, the
minimum and maximum multiplicities are the same, so the
energyconsumer must have one terminal association while
the aclinesegment must now have two. other classes
have a restricted minimum and unrestricted maximum, so
the Topologicalnode must have at least one terminal. The
direction of the association is also defined at the profile such
that an implementation knows which side of the association
should be serialized.
a second profile is shown in figure 5 that is similar to that
of the Bus-Branch profile, reusing three of the four classes
with the addition of the switch and connectivitynode. while
the terminal and energyconsumer class attributes are the
same, the aclinesegment also includes the zero-sequence
attributes, and the switch class from the canonical model is
included with a subset of its attributes. In this profile, the
Terminal-connectivitynode association is used rather than
the Terminal-Topologicalnode, requiring the inclusion of
the connectivitynode class and the corresponding relationship to Terminal and the removal of the Topologicalnode.
moving outside of the functional model exchange, a simple end-device profile example is shown in figure 6. This uses
the endDevice and UsagePoint classes with a small subset of
74

ieee power & energy magazine

their attributes. The energyconsumer class is reused with
some additional attributes added from the canonical model.
The general UsagePoint-equipments relationship has been
restricted to only apply to energyconsumer (a subclass of
equipment), and, as with the other profiles, the multiplicities
have all been restricted and the direction defined.

How IEC Uses CIM Profiling
The Iec has standardized certain profiles using selected
technologies and different options within the flexibility of
the profiling process. These techniques are available for any
organization using cIm standards and are often employed
where specific business processes need exchange implementations that have not been standardized and may include local
cIm canonical model extensions as discussed in the "cIm
model management" document.
Tables 1-3 show the relevant Iec and world wide web
consortium (w3c) standards involved in profiling. These
standards describe the domain models and companion profiling standards that have been developed to date. It is anticipated that additional standards will be developed as new use
cases or requirements are defined.
Profiles can be derived from any part of the canonical
model from any cIm package and, in the case of project
january/february 2016
Table of Contents for the Digital Edition of IEEE Power & Energy Magazine - January/February 2016
