CIM Model Comparison Β·IEC61970CIM18v00 baseline β†’ IEC61970CIM18v01 destination
Scope: IEC61970 Β· compared 2026-11-04 11:39:59 Β· cim-compare 2.3.1
Print or save as PDFOpens your browser’s print dialog (or press Ctrl+P, ⌘P on a Mac).β€’ To save a PDF, choose Save as PDF (or Microsoft Print to PDF) as the printer.β€’ Choose Landscape if the browser doesn’t pick it.β€’ Turn off Headers and footers for a cleaner page.β€’ Leave Background graphics on so the change colours print.Wait for diagram images to load in large reports.
Packages1 moved
Classes24 changed
Diagrams43 changed
Click a count to show only those itemsp
Added β€” only in destinationDeleted β€” only in baselineMoved β€” same GUID, different packageChanged β€” same GUID and package; properties or members differIdenticalPackage (unchanged itself)struckinserted β€” destination text with baseline wording struck (notes, role notes, role names, multiplicities); the shows the notes and every changed propertyBlue β€” a changed attribute type (the new type)
β–ΆIEC61970i
Package notes
Top package for IEC 61970.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{21D32832-FF64-4213-B81C-55ACE35EEBFF}
Package notes
Top package for IEC 61970.
β–ΆBasei
Package notes
Content of the base CIM published as IEC 61970-301.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{20A2C6D8-4765-466f-AD75-5E1B3CAF4E8D}
Package notes
Content of the base CIM published as IEC 61970-301.
β–ΆCorei
Package notes
Contains the core PowerSystemResource and ConductingEquipment entities shared by all applications plus common collections of those entities. Not all applications require all the Core entities. This package does not depend on any other package except the Domain package, but most of the other packages have associations and generalizations that depend on it.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{6A503B72-6E15-4cd1-B92D-DDF6D14DBE29}
Package notes
Contains the core PowerSystemResource and ConductingEquipment entities shared by all applications plus common collections of those entities. Not all applications require all the Core entities. This package does not depend on any other package except the Domain package, but most of the other packages have associations and generalizations that depend on it.
Changed classes (9)
β–Άβš™ConductingEquipmenti
Class notes
The parts of the AC power system that are designed to carry current or that are conductively connected through terminals.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{7C5F19FB-5253-430c-8E53-BDCF7EBCE4C1}
Class notes
The parts of the AC power system that are designed to carry current or that are conductively connected through terminals.
⇄Links
BaselineOutage role Outage [0..1] β†’ ConductingEquipment role OutageIsolationEquipment [0..*]
β†’
DestinationOutage role Outage [0..1] β†’ ConductingEquipment role OutageIsolationEquipment [0..*]
Source end β€” Outage
BaselineDestination
RoleNote(empty)The outage that is isolated by the outage isolation equipment.
Target end β€” OutageIsolationEquipment
BaselineDestination
RoleNote(empty)The equipment that isolates this outage
β–Άβš™ConnectivityNodei
Class notes
Connectivity nodes are points where terminals of AC conducting equipment are connected together with zero impedance.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{8BCACC36-B2DD-4c2a-A2AE-CFDF43731FC2}
Class notes
Connectivity nodes are points where terminals of AC conducting equipment are connected together with zero impedance.
⇄Links
Baselinedid not exist
β†’
DestinationRegisteredResource role RegisteredResource [0..*] β†’ ConnectivityNode role ConnectivityNode [0..1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndRegisteredResource
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleRegisteredResource
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
Scopepublic
TargetScopeinstance
Baselinedid not exist
β†’
DestinationIndividualPnode role IndividualPnode [0..1] β†’ ConnectivityNode role ConnectivityNode [1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndIndividualPnode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleIndividualPnode
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality1
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
Scopepublic
TargetScopeinstance
Baselinedid not exist
β†’
DestinationCnodeDistributionFactor role CnodeDistributionFactor [0..*] β†’ ConnectivityNode role ConnectivityNode [1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndCnodeDistributionFactor
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleCnodeDistributionFactor
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality1
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
Scopepublic
TargetScopeinstance
Baselinedid not exist
β†’
DestinationNodeConstraintTerm role NodeConstraintTerm [0..*] β†’ ConnectivityNode role ConnectivityNode [1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndNodeConstraintTerm
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNodeConstraintTerm
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality1
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
Scopepublic
TargetScopeinstance
β–Άβš™IdentifiedObjecti
Class notes
This is a root class to provide common identification for all classes needing identification and naming attributes.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{055C5806-E9D8-4a7a-9307-DAF7C31763C7}
Class notes
This is a root class to provide common identification for all classes needing identification and naming attributes.
⇄Links
BaselineResourcePerformanceGlobalFactor β†’ IdentifiedObject
β†’
DestinationResourcePerformanceEvaluationFactor β†’ IdentifiedObject
Source end β€” ResourcePerformanceEvaluationFactor
BaselineDestination
EndResourcePerformanceGlobalFactorResourcePerformanceEvaluationFactor
Target end
no changes
BaselineMarketActualEvent β†’ IdentifiedObject
β†’
DestinationMarketEvent β†’ IdentifiedObject
Source end β€” MarketEvent
BaselineDestination
EndMarketActualEventMarketEvent
Target end
no changes
Baselinedid not exist
β†’
DestinationMarketOccurrence β†’ IdentifiedObject
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndMarketOccurrence
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentifiedObject
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineMarketPlan β†’ IdentifiedObject
β†’
DestinationMarketCollection β†’ IdentifiedObject
Source end β€” MarketCollection
BaselineDestination
EndMarketPlanMarketCollection
Target end
no changes
BaselineMarketRun β†’ IdentifiedObject
β†’
DestinationMarketCase β†’ IdentifiedObject
Source end β€” MarketCase
BaselineDestination
EndMarketRunMarketCase
Target end
no changes
BaselineMarket β†’ IdentifiedObject
β†’
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndMarket
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentifiedObject
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselinePlannedMarketEvent β†’ IdentifiedObject
β†’
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndPlannedMarketEvent
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentifiedObject
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineName role name [0..*] β†’ IdentifiedObject role IdentifiedObject [0..1]
β†’
DestinationName role nameName [0..*] β†’ IdentifiedObject role IdentifiedObject [0..1]
Source end β€” Name
BaselineDestination
RolenameName
Target end
no changes
β–Άβš™Namei
Class notes
The Name class, in possible combination with a name type and a naming authority provides the means to define any number of names or alternative identifiers for an object.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{D6F3DF4E-3363-48d2-AB61-7872E337C422}
Class notes
The Name class, in possible combination with a name type and a naming authority provides the means to define any number of names or alternative identifiers for an object.
⇄Links
BaselineName role name [0..*] β†’ IdentifiedObject role IdentifiedObject [0..1]
β†’
DestinationName role nameName [0..*] β†’ IdentifiedObject role IdentifiedObject [0..1]
Source end β€” Name
BaselineDestination
RolenameName
Target end
no changes
BaselineName role Name [0..*] β†’ NameType role NameType [0..1]
β†’
DestinationNameType role NameNameType [0..*0..1] β†’ Name role NameTypeName [0..10..*]
Source end β€” NameType
BaselineDestination
Cardinality0..*0..1
EndNameNameType
RoleNameNameType
RoleNoteAll names of this type.AllType names of this typename.
Target end β€” Name
BaselineDestination
Cardinality0..10..*
EndNameTypeName
RoleNameTypeName
RoleNoteType of this name.TypeAll names of this nametype.
BaselineNamingAuthority role NamingAuthority [0..1] β†’ Name role Name [0..*]
β†’
DestinationName role NamingAuthorityName [0..10..*] β†’ NamingAuthority role NameNamingAuthority [0..*0..1]
Source end β€” Name
BaselineDestination
Cardinality0..10..*
EndNamingAuthorityName
RoleNamingAuthorityName
Target end β€” NamingAuthority
BaselineDestination
Cardinality0..*0..1
EndNameNamingAuthority
RoleNameNamingAuthority
β–Άβš™NameTypei
Class notes
Type of name. Possible values for attribute 'name' are implementation dependent but standard profiles may specify types. An enterprise may have multiple IT systems each having its own local name for the same object, e.g. a planning system may have different names from an EMS. An object may also have different names within the same IT system, e.g. localName as defined in CIM version 14. The definition from CIM14 is: The localName is a human readable name of the object. It is a free text name local to a node in a naming hierarchy similar to a file directory structure. A power system related naming hierarchy may be: Substation, VoltageLevel, Equipment etc. Children of the same parent in such a hierarchy have names that typically are unique among them.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{666F94BF-13E3-4947-830F-3A2D4E7CC9FC}
Class notes
Type of name. Possible values for attribute 'name' are implementation dependent but standard profiles may specify types. An enterprise may have multiple IT systems each having its own local name for the same object, e.g. a planning system may have different names from an EMS. An object may also have different names within the same IT system, e.g. localName as defined in CIM version 14. The definition from CIM14 is: The localName is a human readable name of the object. It is a free text name local to a node in a naming hierarchy similar to a file directory structure. A power system related naming hierarchy may be: Substation, VoltageLevel, Equipment etc. Children of the same parent in such a hierarchy have names that typically are unique among them.
⇄Links
BaselineNamingAuthority role NamingAuthority [0..1] β†’ NameType role NameType [0..*]
β†’
DestinationNameType role NamingAuthorityNameType [0..10..*] β†’ NamingAuthority role NameTypeNamingAuthority [0..*0..1]
Source end β€” NameType
BaselineDestination
Cardinality0..10..*
EndNamingAuthorityNameType
RoleNamingAuthorityNameType
Target end β€” NamingAuthority
BaselineDestination
Cardinality0..*0..1
EndNameTypeNamingAuthority
RoleNameTypeNamingAuthority
BaselineName role Name [0..*] β†’ NameType role NameType [0..1]
β†’
DestinationNameType role NameNameType [0..*0..1] β†’ Name role NameTypeName [0..10..*]
Source end β€” NameType
BaselineDestination
Cardinality0..*0..1
EndNameNameType
RoleNameNameType
RoleNoteAll names of this type.AllType names of this typename.
Target end β€” Name
BaselineDestination
Cardinality0..10..*
EndNameTypeName
RoleNameTypeName
RoleNoteType of this name.TypeAll names of this nametype.
β–Άβš™NamingAuthorityi
Class notes
Authority responsible for creation and management of names of a given name type and/or name; typically an organization or an enterprise system.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{DB6818FE-9B52-4c48-8D64-82133875B67E}
Class notes
Authority responsible for creation and management of names of a given name type and/or name; typically an organization or an enterprise system.
⇄Links
BaselineNamingAuthority role NamingAuthority [0..1] β†’ NameType role NameType [0..*]
β†’
DestinationNameType role NamingAuthorityNameType [0..10..*] β†’ NamingAuthority role NameTypeNamingAuthority [0..*0..1]
Source end β€” NameType
BaselineDestination
Cardinality0..10..*
EndNamingAuthorityNameType
RoleNamingAuthorityNameType
Target end β€” NamingAuthority
BaselineDestination
Cardinality0..*0..1
EndNameTypeNamingAuthority
RoleNameTypeNamingAuthority
BaselineNamingAuthority role NamingAuthority [0..1] β†’ Name role Name [0..*]
β†’
DestinationName role NamingAuthorityName [0..10..*] β†’ NamingAuthority role NameNamingAuthority [0..*0..1]
Source end β€” Name
BaselineDestination
Cardinality0..10..*
EndNamingAuthorityName
RoleNamingAuthorityName
Target end β€” NamingAuthority
BaselineDestination
Cardinality0..*0..1
EndNameNamingAuthority
RoleNameNamingAuthority
β–Άβš™ObjectTypei
Class notes
Identifies the specialised type of an object when the instance object is serialised using a generalised class. It may be useful when the object type is not otherwise included in the exchange. For example, a Meter may be serialised as an EndDevice in message exchanges and need to have the ObjectType.type be specified as 'Meter' to provide context to the message receiver.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{DD569691-4FED-4775-8631-C48D2192912A}
Class notes
Identifies the specialised type of an object when the instance object is serialised using a generalised class. It may be useful when the object type is not otherwise included in the exchange. For example, a Meter may be serialised as an EndDevice in message exchanges and need to have the ObjectType.type be specified as 'Meter' to provide context to the message receiver.
≑Attributes
AttributeBaselineDestinationNotes (destination, redlined)
typei{70E04254-C620-4108-9F63-0A1DF9C9295F}show detailsString [0..1]String [0..1]The specialised type of an object when the instance object is serialised using a generalised class. For example, a Meter being serialised as an EndDevice in a message exchange should have the type attribute specified as 'Meter'.
Attribute notes (destination, redlined)
The specialised type of an object when the instance object is serialised using a generalised class. For example, a Meter being serialised as an EndDevice in a message exchange should have the type attribute specified as 'Meter'.
Attribute metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
β–Άβš™PowerSystemResourcei
Class notes
A power system resource (PSR) can be an item of equipment such as a switch, an equipment container containing many individual items of equipment such as a substation, or an organisational entity such as sub-control area. Power system resources can have measurements associated.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{0340C084-3759-40cc-AAF2-386101DE842F}
Class notes
A power system resource (PSR) can be an item of equipment such as a switch, an equipment container containing many individual items of equipment such as a substation, or an organisational entity such as sub-control area. Power system resources can have measurements associated.
⇄Links
BaselinePowerSystemResource role PowerSystemResource [0..1] β†’ ConfigurationEvent role ConfigurationEvent [0..*]
β†’
DestinationPowerSystemResource role PowerSystemResource [0..1] β†’ ConfigurationEvent role ConfigurationEvent [0..*]
Link metadata
BaselineDestination
StereotypePart 3 Ext(empty)
Source end β€” PowerSystemResource
BaselineDestination
RoleNote(empty)Power system resource whose change resulted in this configuration event.
StereotypePart 3 Ext(empty)
Target end β€” ConfigurationEvent
BaselineDestination
RoleNote(empty)All configuration events created for this Power System resource.
StereotypePart 3 Ext(empty)
BaselineVerificationAction role VerificationAction [0..*] β†’ PowerSystemResource role PowerSystemResource [0..1]
β†’
DestinationVerificationAction role VerificationAction [0..*] β†’ PowerSystemResource role PowerSystemResource [0..1]
Source end β€” VerificationAction
BaselineDestination
RoleNote(empty)The verification action that is performed on the power system resource
Target end β€” PowerSystemResource
BaselineDestination
RoleNote(empty)The power system resource that the verification action is performed on
BaselineGenericAction role GenericAction [0..*] β†’ PowerSystemResource role PowerSystemResource [0..1]
β†’
DestinationGenericAction role GenericAction [0..*] β†’ PowerSystemResource role PowerSystemResource [0..1]
Source end β€” GenericAction
BaselineDestination
RoleNote(empty)The generic action that is performed on the power system resource
Target end β€” PowerSystemResource
BaselineDestination
RoleNote(empty)The power system resource that the generic action is performed on
β–Άβš™RegularIntervalSchedulei
Class notes
The schedule has time points where the time between them is constant.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{A2B1A5C3-6129-4e3b-A1B5-1AC417DEF3AA}
Class notes
The schedule has time points where the time between them is constant.
⇄Links
BaselineResourcePerformanceTimeSeriesFactor β†’ RegularIntervalSchedule
β†’
DestinationResourceTimeSeries β†’ RegularIntervalSchedule
Source end β€” ResourceTimeSeries
BaselineDestination
EndResourcePerformanceTimeSeriesFactorResourceTimeSeries
Target end
no changes
Changed diagrams (4)
β–Άβ–¦CurveSchedulei
Diagram notes
This diagram shows the common model for curves and time dependent schedules.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{7DCA2E11-355A-47f2-9EF8-BEAEBD619E5D}
Diagram notes
This diagram shows the common model for curves and time dependent schedules.
β–¦Diagram
changed
Baseline
CurveSchedule (baseline)
Destination
CurveSchedule (destination)
β–Άβ–¦Namesi
Diagram notes
This diagram shows classes used to assign names to identified objects.
Diagram metadata β€” changes
BaselineDestination
ModifiedDate2021-08-09 10:40:322021-10-08 16:00:17
CHANGED{E0451A91-94B6-4771-AA2F-2F1E5235FDE5}
Diagram notes
This diagram shows classes used to assign names to identified objects.
β–€Metadata
BaselineDestination
ModifiedDate2021-08-09 10:40:322021-10-08 16:00:17
β–¦Diagram
changed
Baseline
Names (baseline)
Destination
Names (destination)
Connectors 3 rerouted Β· 2 labels movedhover a connector to outline the elements it joins
reroutedName – NamingAuthority
reroutedNameType – Name
reroutedNameType – NamingAuthority
labels movedName – IdentifiedObject
labels movedObjectType – IdentifiedObject
β–Άβ–¦OperatingSharei
Diagram notes
This diagram shows the common model for operating share.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{88289F74-ECDD-42e8-A693-6744785B1A0C}
Diagram notes
This diagram shows the common model for operating share.
β–¦Diagram
changed
Baseline
OperatingShare (baseline)
Destination
OperatingShare (destination)
β–Άβ–¦Reportingi
Diagram notes
This diagram shows the common model for ad-hoc reporting.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{25B521B8-89DF-4043-A8D0-B37B0F772597}
Diagram notes
This diagram shows the common model for ad-hoc reporting.
β–¦Diagram
changed
Baseline
Reporting (baseline)
Destination
Reporting (destination)
β–ΆWiresi
Package notes
An extension to the Core and Topology package that models information on the electrical characteristics of Transmission and Distribution networks. This package is used by network applications such as State Estimation, Load Flow and Optimal Power Flow.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{6C99E9CA-2035-4035-B77F-9217E17D86F4}
Package notes
An extension to the Core and Topology package that models information on the electrical characteristics of Transmission and Distribution networks. This package is used by network applications such as State Estimation, Load Flow and Optimal Power Flow.
Changed classes (5)
β–Άβš™ACLineSegmenti
Class notes
A wire or combination of wires, with consistent electrical characteristics, building a single electrical system, used to carry alternating current between points in the power system. For symmetrical, transposed three phase lines, it is sufficient to use attributes of the line segment, which describe impedances and admittances for the entire length of the segment. Additionally impedances can be computed by using length and associated per length impedances. The BaseVoltage at the two ends of ACLineSegments in a Line shall have the same BaseVoltage.nominalVoltage. However, boundary lines may have slightly different BaseVoltage.nominalVoltages and variation is allowed. Larger voltage difference in general requires use of an equivalent branch.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{625BD764-3907-4d65-8497-7FD09708BD8E}
Class notes
A wire or combination of wires, with consistent electrical characteristics, building a single electrical system, used to carry alternating current between points in the power system. For symmetrical, transposed three phase lines, it is sufficient to use attributes of the line segment, which describe impedances and admittances for the entire length of the segment. Additionally impedances can be computed by using length and associated per length impedances. The BaseVoltage at the two ends of ACLineSegments in a Line shall have the same BaseVoltage.nominalVoltage. However, boundary lines may have slightly different BaseVoltage.nominalVoltages and variation is allowed. Larger voltage difference in general requires use of an equivalent branch.
⇄Links
BaselineACLineSegment role ACLineSegment [0..*] β†’ WireSpacingInfo role WireSpacingInfo [0..1]
β†’
DestinationACLineSegment role ACLineSegment [0..*] β†’ WireSpacingInfo role WireSpacingInfo [0..1]
Source end β€” ACLineSegment
BaselineDestination
RoleNote(empty)The AC line segment defined by the wire spacing information
Target end β€” WireSpacingInfo
BaselineDestination
RoleNote(empty)The wire spacing information that applies to this AC line segment
β–Άβš™ACLineSegmentPhasei
Class notes
Represents a single wire of an alternating current line segment.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{84627F88-F666-4f07-890A-62622070CD0F}
Class notes
Represents a single wire of an alternating current line segment.
⇄Links
BaselineACLineSegmentPhase role ACLineSegmentPhase [0..*] β†’ WireInfo role WireInfo [0..1]
β†’
DestinationACLineSegmentPhase role ACLineSegmentPhase [0..*] β†’ WireInfo role WireInfo [0..1]
Source end β€” ACLineSegmentPhase
BaselineDestination
RoleNote(empty)AC line segment phase information associated with this wire information.
Target end β€” WireInfo
BaselineDestination
RoleNote(empty)Wire information contributing to this AC line segment phase information.
β–Άβš™Clampi
Class notes
A Clamp is a galvanic connection at a line segment where other equipment is connected. A Clamp does not cut the line segment. A Clamp is ConductingEquipment and has one Terminal with an associated ConnectivityNode. Any other ConductingEquipment can be connected to the Clamp ConnectivityNode.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{7B0758AF-6E8E-438e-BD69-A838A56F256D}
Class notes
A Clamp is a galvanic connection at a line segment where other equipment is connected. A Clamp does not cut the line segment. A Clamp is ConductingEquipment and has one Terminal with an associated ConnectivityNode. Any other ConductingEquipment can be connected to the Clamp ConnectivityNode.
⇄Links
BaselineClamp role Clamp [0..1] β†’ JumperAction role JumperAction [0..1]
β†’
DestinationClamp role Clamp [0..1] β†’ JumperAction role JumperAction [0..1]
Source end β€” Clamp
BaselineDestination
RoleNote(empty)Clamp on which this action is taken.
Target end β€” JumperAction
BaselineDestination
RoleNote(empty)Action taken with this jumper.
BaselineClamp role Clamp [0..1] β†’ ClampAction role ClampAction [0..1]
β†’
DestinationClamp role Clamp [0..1] β†’ ClampAction role ClampAction [0..1]
Source end β€” Clamp
BaselineDestination
RoleNote(empty)The clamp that the clamp action is performed on
Target end β€” ClampAction
BaselineDestination
RoleNote(empty)The clamp action that is performed on the clamp
β–Άβš™EnergyConsumeri
Class notes
Generic user of energy - a point of consumption on the power system model. EnergyConsumer.pfixed, .qfixed, .pfixedPct and .qfixedPct have meaning only if there is no LoadResponseCharacteristic associated with EnergyConsumer or if LoadResponseCharacteristic.exponentModel is set to False.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{BCEC7EE8-7294-4b50-8216-0286C31A035C}
Class notes
Generic user of energy - a point of consumption on the power system model. EnergyConsumer.pfixed, .qfixed, .pfixedPct and .qfixedPct have meaning only if there is no LoadResponseCharacteristic associated with EnergyConsumer or if LoadResponseCharacteristic.exponentModel is set to False.
⇄Links
BaselineEnergyConsumer role EnergyConsumer [0..1] β†’ EnergyConsumerAction role EnergyConsumerAction [0..1]
β†’
DestinationEnergyConsumer role EnergyConsumer [0..1] β†’ EnergyConsumerAction role EnergyConsumerAction [0..1]
Source end β€” EnergyConsumer
BaselineDestination
RoleNote(empty)The energy consumer that the energy consumer action is performed on
Target end β€” EnergyConsumerAction
BaselineDestination
RoleNote(empty)The energy consumer action that is performed on the energy consumer
β–Άβš™ShuntCompensatori
Class notes
A shunt capacitor or reactor or switchable bank of shunt capacitors or reactors. A section of a shunt compensator is an individual capacitor or reactor. A negative value for bPerSection indicates that the compensator is a reactor. ShuntCompensator is a single terminal device. Ground is implied.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{92B30569-5ED0-4fc0-B796-984D9BF75453}
Class notes
A shunt capacitor or reactor or switchable bank of shunt capacitors or reactors. A section of a shunt compensator is an individual capacitor or reactor. A negative value for bPerSection indicates that the compensator is a reactor. ShuntCompensator is a single terminal device. Ground is implied.
⇄Links
BaselineShuntCompensator role ShuntCompensator [0..1] β†’ ShuntCompensatorAction role ShuntCompensatorAction [0..1]
β†’
DestinationShuntCompensator role ShuntCompensator [0..1] β†’ ShuntCompensatorAction role ShuntCompensatorAction [0..1]
Source end β€” ShuntCompensator
BaselineDestination
RoleNote(empty)The shunt compensator that the shunt compensator action is performed on
Target end β€” ShuntCompensatorAction
BaselineDestination
RoleNote(empty)The shunt compensator action that is performed on the shunt compensator
Changed diagrams (5)
β–Άβ–¦InheritanceHierarchyi
Diagram notes
This diagram describes inheritance between classes in and related to the Wires package.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{D2B8C355-D454-4084-9966-12E8D7FF6875}
Diagram notes
This diagram describes inheritance between classes in and related to the Wires package.
β–¦Diagram
changed
Baseline
InheritanceHierarchy (baseline)
Destination
InheritanceHierarchy (destination)
β–Άβ–¦MutualCouplingi
Diagram notes
Shows mutual coupling models.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{7CE6A094-D43D-4851-8A1F-D1B06FA7B538}
Diagram notes
Shows mutual coupling models.
β–¦Diagram
changed
Baseline
MutualCoupling (baseline)
Destination
MutualCoupling (destination)
β–Άβ–¦NamingHierarchyPart1i
Diagram notes
The diagram shows the upper part of the naming hierarchy. The hierarchy is a way to organize and name equipment. Hence it is tightly related to the IdentifiedObject and it's attributes. The Equipment class is further specialized into many subtypes that are all contained by subclasses of the EquipmentContainer.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{422FB39E-1D47-45c4-8623-BADEED124BF6}
Diagram notes
The diagram shows the upper part of the naming hierarchy. The hierarchy is a way to organize and name equipment. Hence it is tightly related to the IdentifiedObject and it's attributes. The Equipment class is further specialized into many subtypes that are all contained by subclasses of the EquipmentContainer.
β–¦Diagram
changed
Baseline
NamingHierarchyPart1 (baseline)
Destination
NamingHierarchyPart1 (destination)
β–Άβ–¦NamingHierarchyPart2i
Diagram notes
The diagram shows the lower part of the naming hierarchy. It shows how the Equipment class is further specialized into many subtypes that are all contained by subclasses of the EquipmentContainer. For the subclasses of equipment container refer to part 1 of the diagram.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{3A72A435-5BA5-4809-A5DC-560573D58582}
Diagram notes
The diagram shows the lower part of the naming hierarchy. It shows how the Equipment class is further specialized into many subtypes that are all contained by subclasses of the EquipmentContainer. For the subclasses of equipment container refer to part 1 of the diagram.
β–¦Diagram
changed
Baseline
NamingHierarchyPart2 (baseline)
Destination
NamingHierarchyPart2 (destination)
β–Άβ–¦Schedulesi
Diagram notes
Shows schedules of wires model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{18FA35BC-A253-4a57-A387-6D36B189A250}
Diagram notes
Shows schedules of wires model.
β–¦Diagram
changed
Baseline
Schedules (baseline)
Destination
Schedules (destination)
β–ΆLoadModeli
Package notes
This package is responsible for modelling the energy consumers and the system load as curves and associated curve data. Special circumstances that may affect the load, such as seasons and day types, are also included here. This information is used by Load Forecasting and Load Management.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{427D9D64-CDA2-4070-AAC6-04A32F290872}
Package notes
This package is responsible for modelling the energy consumers and the system load as curves and associated curve data. Special circumstances that may affect the load, such as seasons and day types, are also included here. This information is used by Load Forecasting and Load Management.
Package 'LoadModel' has no changes to the 16 classes it contains.
Changed diagrams (1)
β–Άβ–¦Maini
Diagram notes
This diagram shows all classes included in the LoadModel package as well as the key external classes that have associations with LoadModel classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{E25D676B-3E4F-482f-B0D7-4B7A0ADFFFEB}
Diagram notes
This diagram shows all classes included in the LoadModel package as well as the key external classes that have associations with LoadModel classes.
β–¦Diagram
changed
Baseline
Main (baseline)
Destination
Main (destination)
β–ΆGenerationi
Package notes
This package contains packages that have information for Unit Commitment and Economic Dispatch of hydro and thermal generating units, Load Forecasting, Automatic Generation Control, and unit modeling for Training Simulation.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{6B50A1FD-22E9-4abc-B0B7-F46BBD8B33AE}
Package notes
This package contains packages that have information for Unit Commitment and Economic Dispatch of hydro and thermal generating units, Load Forecasting, Automatic Generation Control, and unit modeling for Training Simulation.
β–ΆProductioni
Package notes
The production package is responsible for classes which describe various kinds of generators. These classes also provide production costing information which is used to economically allocate demand among committed units and calculate reserve quantities.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{39719C4D-64F6-4704-8202-8CAEF5179709}
Package notes
The production package is responsible for classes which describe various kinds of generators. These classes also provide production costing information which is used to economically allocate demand among committed units and calculate reserve quantities.
Package 'Production' has no changes to the 49 classes it contains.
Changed diagrams (3)
β–Άβ–¦Hydroi
Diagram notes
This diagram shows all classes included in the Hydro package as well as the key external classes that have associations with Hydro classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{DE303E99-315E-416c-906A-2195D7E5C62A}
Diagram notes
This diagram shows all classes included in the Hydro package as well as the key external classes that have associations with Hydro classes.
β–¦Diagram
changed
Baseline
Hydro (baseline)
Destination
Hydro (destination)
β–Άβ–¦Maini
Diagram notes
This diagram shows all classes included in the Production package that are needed by both Hydro and Thermal generation. It also shows key external classes that have associations with Production classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{F9C40197-0210-4574-A263-DF81545A755B}
Diagram notes
This diagram shows all classes included in the Production package that are needed by both Hydro and Thermal generation. It also shows key external classes that have associations with Production classes.
β–¦Diagram
changed
Baseline
Main (baseline)
Destination
Main (destination)
β–Άβ–¦Thermali
Diagram notes
This diagram shows all classes included in the Thermal package as well as the key external classes that have associations with Thermal classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{93E625AE-B174-4d96-B127-8B8086E6BE1F}
Diagram notes
This diagram shows all classes included in the Thermal package as well as the key external classes that have associations with Thermal classes.
β–¦Diagram
changed
Baseline
Thermal (baseline)
Destination
Thermal (destination)
Package 'Generation' has no changes to the 1 diagrams it contains.
β–ΆEquivalentsi
Package notes
The equivalents package models equivalent networks.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{32F75AB7-7839-4933-BE8C-F162A464FE41}
Package notes
The equivalents package models equivalent networks.
Package 'Equivalents' has no changes to the 5 classes it contains.
Changed diagrams (1)
β–Άβ–¦Maini
Diagram notes
Shows model for equivalent networks.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{15613B15-ECE0-47f2-B5D5-CBA4AA111746}
Diagram notes
Shows model for equivalent networks.
β–¦Diagram
changed
Baseline
Main (baseline)
Destination
Main (destination)
β–ΆMeasi
Package notes
Contains entities that describe dynamic measurement data exchanged between applications.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{6B58A5C3-5CC1-4320-A9D3-2CABB8F9399E}
Package notes
Contains entities that describe dynamic measurement data exchanged between applications.
Changed classes (3)
β–Άβš™Controli
Class notes
Control is used for supervisory/device control. It represents control outputs that are used to change the state in a process, e.g. close or open breaker, a set point value or a raise lower command.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{4EEEE27D-42CD-4efc-8F74-3655BF703F4E}
Class notes
Control is used for supervisory/device control. It represents control outputs that are used to change the state in a process, e.g. close or open breaker, a set point value or a raise lower command.
⇄Links
BaselineControlAction role ControlAction [0..1] β†’ Control role Control [0..1]
β†’
DestinationControlAction role ControlAction [0..1] β†’ Control role Control [0..1]
Source end β€” ControlAction
BaselineDestination
RoleNote(empty)The control action that is performed on the control
Target end β€” Control
BaselineDestination
RoleNote(empty)The control that the control action is performed on.
β–Άβš™Measurementi
Class notes
A Measurement represents any measured, calculated or non-measured non-calculated quantity. Any piece of equipment may contain Measurements, e.g. a substation may have temperature measurements and door open indications, a transformer may have oil temperature and tank pressure measurements, a bay may contain a number of power flow measurements and a Breaker may contain a switch status measurement. The PSR - Measurement association is intended to capture this use of Measurement and is included in the naming hierarchy based on EquipmentContainer. The naming hierarchy typically has Measurements as leaves, e.g. Substation-VoltageLevel-Bay-Switch-Measurement. Some Measurements represent quantities related to a particular sensor location in the network, e.g. a voltage transformer (VT) or potential transformer (PT) at a busbar or a current transformer (CT) at the bar between a breaker and an isolator. The sensing position is not captured in the PSR - Measurement association. Instead it is captured by the Measurement - Terminal association that is used to define the sensing location in the network topology. The location is defined by the connection of the Terminal to ConductingEquipment. If both a Terminal and PSR are associated, and the PSR is of type ConductingEquipment, the associated Terminal should belong to that ConductingEquipment instance. When the sensor location is needed both Measurement-PSR and Measurement-Terminal are used. The Measurement-Terminal association is never used alone.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{AB1758FA-3A4D-478f-BE4F-ADC8E2F886CC}
Class notes
A Measurement represents any measured, calculated or non-measured non-calculated quantity. Any piece of equipment may contain Measurements, e.g. a substation may have temperature measurements and door open indications, a transformer may have oil temperature and tank pressure measurements, a bay may contain a number of power flow measurements and a Breaker may contain a switch status measurement. The PSR - Measurement association is intended to capture this use of Measurement and is included in the naming hierarchy based on EquipmentContainer. The naming hierarchy typically has Measurements as leaves, e.g. Substation-VoltageLevel-Bay-Switch-Measurement. Some Measurements represent quantities related to a particular sensor location in the network, e.g. a voltage transformer (VT) or potential transformer (PT) at a busbar or a current transformer (CT) at the bar between a breaker and an isolator. The sensing position is not captured in the PSR - Measurement association. Instead it is captured by the Measurement - Terminal association that is used to define the sensing location in the network topology. The location is defined by the connection of the Terminal to ConductingEquipment. If both a Terminal and PSR are associated, and the PSR is of type ConductingEquipment, the associated Terminal should belong to that ConductingEquipment instance. When the sensor location is needed both Measurement-PSR and Measurement-Terminal are used. The Measurement-Terminal association is never used alone.
⇄Links
BaselineAsset role Asset [0..1] β†’ Measurement role Measurements [0..*]
β†’
DestinationAsset role Asset [0..1] β†’ Measurement role Measurements [0..*]
Source end β€” Asset
BaselineDestination
RoleNote(empty)Asset that has a measurement
Target end
no changes
BaselineMeasurementAction role MeasurementAction [0..1] β†’ Measurement role Measurement [0..1]
β†’
DestinationMeasurementAction role MeasurementAction [0..1] β†’ Measurement role Measurement [0..1]
Source end β€” MeasurementAction
BaselineDestination
RoleNote(empty)The measurement action that is performed on the measurement
Target end β€” Measurement
BaselineDestination
RoleNote(empty)The measurement that the measurement action is performed on
BaselineLocation role Locations [0..*] β†’ Measurement role Measurements [0..*]
β†’
DestinationLocation role Locations [0..*] β†’ Measurement role Measurements [0..*]
Source end β€” Locations
BaselineDestination
RoleNote(empty)Location of this measurement.
Target end β€” Measurements
BaselineDestination
RoleNote(empty)All measurements at this location.
β–Άβš™MeasurementValuei
Class notes
The current state for a measurement. A state value is an instance of a measurement from a specific source. Measurements can be associated with many state values, each representing a different source for the measurement.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{E6D7B57A-456A-43b5-838B-3CFB466EE4C4}
Class notes
The current state for a measurement. A state value is an instance of a measurement from a specific source. Measurements can be associated with many state values, each representing a different source for the measurement.
⇄Links
BaselineProcedureDataSet role ProcedureDataSet [0..*] β†’ MeasurementValue role MeasurementValue [0..*]
β†’
DestinationProcedureDataSet role ProcedureDataSet [0..*] β†’ MeasurementValue role MeasurementValue [0..*]
Source end β€” ProcedureDataSet
BaselineDestination
RoleNote(empty)Procedure data set that applies to this mesurement value.
Target end β€” MeasurementValue
BaselineDestination
RoleNote(empty)Measurement value related to this procedure data set.
Changed diagrams (1)
β–Άβ–¦MeasurementInheritancei
Diagram notes
This diagram shows the measurement classes inheritance.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{5DF6F48B-1076-4edf-9F46-0132E1D9A930}
Diagram notes
This diagram shows the measurement classes inheritance.
β–¦Diagram
changed
Baseline
MeasurementInheritance (baseline)
Destination
MeasurementInheritance (destination)
β–ΆDiagramLayouti
Package notes
This package describes diagram layout. This describes how objects are arranged in a coordinate system rather than how they are rendered.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{BD6471E7-9929-4251-A731-BB65A6ABD2BF}
Package notes
This package describes diagram layout. This describes how objects are arranged in a coordinate system rather than how they are rendered.
Package 'DiagramLayout' has no changes to the 9 classes it contains.
Changed diagrams (1)
β–Άβ–¦DiagramLayouti
Diagram notes
Shows model for diagram layout.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{99E05246-80CF-4712-8EDF-605446BBFADE}
Diagram notes
Shows model for diagram layout.
β–¦Diagram
changed
Baseline
DiagramLayout (baseline)
Destination
DiagramLayout (destination)
β–ΆOperationalLimitsi
Package notes
This package models a specification of limits associated with equipment and other operational entities.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{CCAAF4EA-4C50-4438-86F9-63852950B3CA}
Package notes
This package models a specification of limits associated with equipment and other operational entities.
Package 'OperationalLimits' has no changes to the 10 classes it contains.
Changed diagrams (1)
β–Άβ–¦BranchGroupi
Diagram notes
This diagram shows the model for monitoring combined flows on groups of branches.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{DE2F00E8-B731-43ce-B01C-7267ED3D9F4E}
Diagram notes
This diagram shows the model for monitoring combined flows on groups of branches.
β–¦Diagram
changed
Baseline
BranchGroup (baseline)
Destination
BranchGroup (destination)
β–ΆControlAreai
Package notes
The ControlArea package models area specifications which can be used for a variety of purposes. The package as a whole models potentially overlapping control area specifications for the purpose of actual generation control, load forecast area load capture, or powerflow based analysis.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{3A4198A2-F8DC-4ff1-B669-3064688AF4DD}
Package notes
The ControlArea package models area specifications which can be used for a variety of purposes. The package as a whole models potentially overlapping control area specifications for the purpose of actual generation control, load forecast area load capture, or powerflow based analysis.
Package 'ControlArea' has no changes to the 6 classes it contains.
Changed diagrams (1)
β–Άβ–¦ControlAreaInheritancei
Diagram notes
Shows the inheritance of classes in this package.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{AA2D75EA-1B1C-41b5-8C61-999912681F91}
Diagram notes
Shows the inheritance of classes in this package.
β–¦Diagram
changed
Baseline
ControlAreaInheritance (baseline)
Destination
ControlAreaInheritance (destination)
β–ΆContingencyi
Package notes
Contingencies to be studied.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{5AFF4730-5CFE-48e6-961A-077143DE2082}
Package notes
Contingencies to be studied.
Package 'Contingency' has no changes to the 4 classes it contains.
Changed diagrams (1)
β–Άβ–¦Contingencyi
Diagram notes
This diagram shows contingency model inheritance and associations.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{F06848B5-DB6D-4a40-91C8-00E7BC6F1823}
Diagram notes
This diagram shows contingency model inheritance and associations.
β–¦Diagram
changed
Baseline
Contingency (baseline)
Destination
Contingency (destination)
β–ΆProtectioni
Package notes
An extension to the Core and Wires packages that models information for protection equipment such as relays. These entities are used within training simulators and distribution network fault location applications.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{3F02E213-ECF8-4f14-9AD5-D4A252FE300A}
Package notes
An extension to the Core and Wires packages that models information for protection equipment such as relays. These entities are used within training simulators and distribution network fault location applications.
Package 'Protection' has no changes to the 4 classes it contains.
Changed diagrams (1)
β–Άβ–¦Maini
Diagram notes
This diagram shows all classes included in the Protection package as well as the key external classes that have associations with Protection classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{9AF2AFF5-A5C5-487d-BE22-9DADEDA9929E}
Diagram notes
This diagram shows all classes included in the Protection package as well as the key external classes that have associations with Protection classes.
β–¦Diagram
changed
Baseline
Main (baseline)
Destination
Main (destination)
β–ΆFaultsi
Package notes
The package describes faults that may happen to conducting equipment, e.g. tree falling on a power line.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{59BC9A2E-B8E4-4c5f-B1D8-2C6502296346}
Package notes
The package describes faults that may happen to conducting equipment, e.g. tree falling on a power line.
Changed classes (2)
β–Άβš™Faulti
Class notes
Abnormal condition causing current flow through conducting equipment, such as caused by equipment failure or short circuits from objects not typically modelled (for example, a tree falling on a line).
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{73ABECF2-4B28-4c55-8665-0882A2C8BCA4}
Class notes
Abnormal condition causing current flow through conducting equipment, such as caused by equipment failure or short circuits from objects not typically modelled (for example, a tree falling on a line).
⇄Links
BaselineFault role Fault [0..*] β†’ Location role Location [0..1]
β†’
DestinationFault role Fault [0..*] β†’ Location role Location [0..1]
Source end β€” Fault
BaselineDestination
RoleNote(empty)All faults at this location.
Target end β€” Location
BaselineDestination
RoleNote(empty)Location of this fault.
β–Άβš™FaultCauseTypei
Class notes
Type of cause of the fault.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{FA0CB393-8E7C-411c-B4F1-14073D940EED}
Class notes
Type of cause of the fault.
⇄Links
BaselineConfigurationEvent role ConfigurationEvent [0..*] β†’ FaultCauseType role FaultCauseType [1]
β†’
DestinationConfigurationEvent role ConfigurationEvent [0..*] β†’ FaultCauseType role FaultCauseType [1]
Link metadata
BaselineDestination
StereotypePart 3 Ext(empty)
Source end β€” ConfigurationEvent
BaselineDestination
RoleNote(empty)All configuration events created for this fault cause type.
StereotypePart 3 Ext(empty)
Target end β€” FaultCauseType
BaselineDestination
RoleNote(empty)Fault cause type whose change resulted in this configuration event.
StereotypePart 3 Ext(empty)
Package 'Faults' has no changes to the 1 diagrams it contains.
β–ΆSCADAi
Package notes
Contains entities to model information used by Supervisory Control and Data Acquisition (SCADA) applications. Supervisory control supports operator control of equipment, such as opening or closing a breaker. Data acquisition gathers telemetered data from various sources. The subtypes of the Telemetry entity deliberately match the UCA and IEC 61850 definitions. This package also supports alarm presentation but it is not expected to be used by other applications.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{C397A471-682D-4757-89C3-C65DCE1842A7}
Package notes
Contains entities to model information used by Supervisory Control and Data Acquisition (SCADA) applications. Supervisory control supports operator control of equipment, such as opening or closing a breaker. Data acquisition gathers telemetered data from various sources. The subtypes of the Telemetry entity deliberately match the UCA and IEC 61850 definitions. This package also supports alarm presentation but it is not expected to be used by other applications.
Package 'SCADA' has no changes to the 7 classes it contains.
Changed diagrams (1)
β–Άβ–¦Maini
Diagram notes
This diagram shows all classes included in the SCADA package as well as the key external classes that have associations with SCADA classes.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{DCCD95DF-1D4D-4a31-ADC9-82410B121566}
Diagram notes
This diagram shows all classes included in the SCADA package as well as the key external classes that have associations with SCADA classes.
β–¦Diagram
changed
Baseline
Main (baseline)
Destination
Main (destination)
β–ΆPart303i
Package notes
Part of the canonical CIM published as IEC 61970-303.
Package metadata β€” changes
BaselineDestination
ParentPackageInfIEC61970IEC61970
Tagged values β€” changes
BaselineDestination
no changes
MOVEDfrom InfIEC61970{097BFA4A-EAE9-4618-B4D1-896C3B3BB77D}
Package notes
Part of the canonical CIM published as IEC 61970-303.
β–ΆGenericDataSeti
Package notes
Contains classes used for generic dataset modelling.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{8FF85768-B48A-4be5-9113-0DD28B347634}
Package notes
Contains classes used for generic dataset modelling.
Changed classes (4)
β–Άβš™ChangeSeti
Class notes
Describes a set of changes that can be applied in different situations. A given registered target object MRID may only be referenced once by the contained change set members.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{EDB0ACC9-0CE3-439f-ADC6-2D753A220486}
Class notes
Describes a set of changes that can be applied in different situations. A given registered target object MRID may only be referenced once by the contained change set members.
⇄Links
BaselineChangeSetMember role ChangeSetMember [0..*] β†’ ChangeSet role Changeset [0..1]
β†’
DestinationChangeSetMember role ChangeSetMember [0..*] β†’ ChangeSet role ChangesetChangeSet [0..1]
Source end
no changes
Target end β€” ChangeSet
BaselineDestination
RoleChangesetChangeSet
β–Άβš™ChangeSetMemberi
Class notes
A CRUD-style data object.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{B579C575-1165-4e6c-AFEF-991BBA193E2B}
Class notes
A CRUD-style data object.
⇄Links
BaselineChangeSetMember role ChangeSetMember [0..*] β†’ ChangeSet role Changeset [0..1]
β†’
DestinationChangeSetMember role ChangeSetMember [0..*] β†’ ChangeSet role ChangesetChangeSet [0..1]
Source end
no changes
Target end β€” ChangeSet
BaselineDestination
RoleChangesetChangeSet
β–Άβš™DataSeti
Class notes
A generic container of a version of instance data. The MRID can be used in an audit trail, not in reusable script intended to work with new versions of data. A dataset could be serialized multiple times and in multiple technologies, yet retain the same identity.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{28D05F59-6B53-4c1f-A18D-EE6B9CC533F9}
Class notes
A generic container of a version of instance data. The MRID can be used in an audit trail, not in reusable script intended to work with new versions of data. A dataset could be serialized multiple times and in multiple technologies, yet retain the same identity.
≑Attributes
AttributeBaselineDestinationNotes (destination, redlined)
descriptioni{14F272FF-25AE-4d6a-9BFE-FF46458C9848}show detailsString [0..1]removed from model
Attribute notes (baseline)
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
Attribute metadata β€” changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namedescription
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values β€” changes
BaselineDestination
none
namei{4DFBBA72-867F-4d84-8F39-69AFECF9990E}show detailsString [0..1]removed from model
Attribute notes (baseline)
The name is any free human readable and possibly non unique text naming the object.
Attribute metadata β€” changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namename
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values β€” changes
BaselineDestination
none
⇄Links
BaselineDataSet role DataSet [0..*] β†’ Profile role Profile [1..*]
β†’
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndDataSet
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDataSet
RoleNoteThe data sets that make use of the profile.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndProfile
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleProfile
RoleNoteThe profiles that describe the contents of the data set and the rules governing the contents of the data set.
Scopepublic
TargetScopeinstance
β–Άβš™Profilei
Class notes
Describes the existence of a profile. The MRID is usually defined as a static value by the document or artifact that defines the contents of the profile and the rules for using the profile.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{BC499E60-2398-46aa-A340-8421A864B0C1}
Class notes
Describes the existence of a profile. The MRID is usually defined as a static value by the document or artifact that defines the contents of the profile and the rules for using the profile.
⇄Links
BaselineDataSet role DataSet [0..*] β†’ Profile role Profile [1..*]
β†’
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndDataSet
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDataSet
RoleNoteThe data sets that make use of the profile.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndProfile
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleProfile
RoleNoteThe profiles that describe the contents of the data set and the rules governing the contents of the data set.
Scopepublic
TargetScopeinstance
Changed diagrams (1)
β–Άβ–¦GenericDataSeti
Diagram notes
Shows the generic dataset core classes.
Diagram metadata β€” changes
BaselineDestination
ModifiedDate2019-03-08 20:18:202021-09-29 10:41:05
CHANGED{A5A07B09-93CB-423d-8595-8653C21E725B}
Diagram notes
Shows the generic dataset core classes.
β–€Metadata
BaselineDestination
ModifiedDate2019-03-08 20:18:202021-09-29 10:41:05
β–¦Diagram
removedchanged
Baseline
GenericDataSet (baseline)
Destination
GenericDataSet (destination)
Connectors 2 removed Β· 2 rerouted Β· 1 labels moved Β· 1 labels changedhover a connector to outline the elements it joins
removedDataSet – Profile
removedProfile – IdentifiedObject
reroutedChangeSet – DataSet
reroutedInstanceSet – DataSet
labels movedChangeSetMember – IdentifiedObject
labels changedChangeSetMember – ChangeSetrole name Changeset β†’ ChangeSet
β–ΆDynamicsi
Package notes
The CIM dynamic model definitions reflect the most common IEEE or, in the case of wind models, IEC, representations of models as well as models included in some of the transient stability software widely used by utilities. These dynamic models are intended to ensure interoperability between different vendors’ software products currently in use by electric utility energy companies, utilities, Transmission System Operators (TSOs), Regional Transmission Organizations (RTOs), and Independent System Operators (ISOs). It is important to note that each vendor is free to select its own internal implementation of these models. Differences in vendor results, as long as they are within accepted engineering practice, caused by different internal representations, are acceptable. Unless explicitly stated otherwise, the following modelling conventions are followed: - limited integrators are of the non-windup type; - it shall be possible to enter a time constant of zero (where it makes sense).
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{A71B9185-6D48-40f4-B618-485C08C4F269}
Package notes
The CIM dynamic model definitions reflect the most common IEEE or, in the case of wind models, IEC, representations of models as well as models included in some of the transient stability software widely used by utilities. These dynamic models are intended to ensure interoperability between different vendors’ software products currently in use by electric utility energy companies, utilities, Transmission System Operators (TSOs), Regional Transmission Organizations (RTOs), and Independent System Operators (ISOs). It is important to note that each vendor is free to select its own internal implementation of these models. Differences in vendor results, as long as they are within accepted engineering practice, caused by different internal representations, are acceptable. Unless explicitly stated otherwise, the following modelling conventions are followed: - limited integrators are of the non-windup type; - it shall be possible to enter a time constant of zero (where it makes sense).
β–ΆStandardModelsi
Package notes
This subclause contains standard dynamic model specifications grouped into packages by standard function block (type of equipment being modelled). In the CIM, standard dynamic models are expressed by means of a class named with the standard model name and attributes reflecting each of the parameters necessary to describe the behaviour of an instance of the standard model.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{1BEB429C-BFD0-49c6-9556-AC7BA58C2202}
Package notes
This subclause contains standard dynamic model specifications grouped into packages by standard function block (type of equipment being modelled). In the CIM, standard dynamic models are expressed by means of a class named with the standard model name and attributes reflecting each of the parameters necessary to describe the behaviour of an instance of the standard model.
β–ΆSynchronousMachineDynamicsi
Package notes
For conventional power generating units (e.g., thermal, hydro, combustion turbine), a synchronous machine model represents the electrical characteristics of the generator and the mechanical characteristics of the turbine-generator rotational inertia. Large industrial motors or groups of similar motors can be represented by individual motor models which are represented as generators with negative active power in the static (power flow) data. The interconnection with the electrical network equations can differ among simulation tools. The tool only needs to know the synchronous machine to establish the correct interconnection. The interconnection with the motor’s equipment could also differ due to input and output signals required by standard models.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{448F8675-D39C-4fe0-9450-2791AE603EFC}
Package notes
For conventional power generating units (e.g., thermal, hydro, combustion turbine), a synchronous machine model represents the electrical characteristics of the generator and the mechanical characteristics of the turbine-generator rotational inertia. Large industrial motors or groups of similar motors can be represented by individual motor models which are represented as generators with negative active power in the static (power flow) data. The interconnection with the electrical network equations can differ among simulation tools. The tool only needs to know the synchronous machine to establish the correct interconnection. The interconnection with the motor’s equipment could also differ due to input and output signals required by standard models.
Package 'SynchronousMachineDynamics' has no changes to the 8 classes it contains.
Changed diagrams (1)
β–Άβ–¦SynchronousMachineDynamicsi
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to the synchronous machine dynamics model. An association between the SynchronousMachineDynamics class and the SynchronousMachine class provides a means for relating the dynamics model to the static model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{54E9C659-8B6C-4948-A2ED-1F2B84C0A17C}
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to the synchronous machine dynamics model. An association between the SynchronousMachineDynamics class and the SynchronousMachine class provides a means for relating the dynamics model to the static model.
β–¦Diagram
changed
Baseline
SynchronousMachineDynamics (baseline)
Destination
SynchronousMachineDynamics (destination)
β–ΆAsynchronousMachineDynamicsi
Package notes
An asynchronous machine model represents a (induction) generator or motor with no external connection to the rotor windings, e.g. a squirrel-cage induction machine. The interconnection with the electrical network equations can differ among simulation tools. The program only needs to know the terminal to which this asynchronous machine is connected in order to establish the correct interconnection. The interconnection with the motor’s equipment could also differ due to input and output signals required by standard models. The asynchronous machine model is used to model wind generators type 1 and type 2. For these, normal practice is to include the rotor flux transients and neglect the stator flux transients.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{5D284657-A8B5-4b22-A1BE-60220021422B}
Package notes
An asynchronous machine model represents a (induction) generator or motor with no external connection to the rotor windings, e.g. a squirrel-cage induction machine. The interconnection with the electrical network equations can differ among simulation tools. The program only needs to know the terminal to which this asynchronous machine is connected in order to establish the correct interconnection. The interconnection with the motor’s equipment could also differ due to input and output signals required by standard models. The asynchronous machine model is used to model wind generators type 1 and type 2. For these, normal practice is to include the rotor flux transients and neglect the stator flux transients.
Package 'AsynchronousMachineDynamics' has no changes to the 3 classes it contains.
Changed diagrams (1)
β–Άβ–¦AsynchronousMachineDynamicsi
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to the asynchronous machine dynamics model. An association between the AsynchronousMachineDynamics class and the AsynchronousMachine class provides a means for relating the dynamics model to the static model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{25AB5834-2B99-4846-9C8F-855D6A80D650}
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to the asynchronous machine dynamics model. An association between the AsynchronousMachineDynamics class and the AsynchronousMachine class provides a means for relating the dynamics model to the static model.
β–¦Diagram
changed
Baseline
AsynchronousMachineDynamics (baseline)
Destination
AsynchronousMachineDynamics (destination)
β–ΆTurbineGovernorDynamicsi
Package notes
The turbine-governor model is linked to one or two synchronous generators and determines the shaft mechanical power (<i>Pm</i>) or torque (<i>Tm</i>) for the generator model. Unlike IEEE standard models for other function blocks, the three IEEE turbine-governor standard models (GovHydroIEEE0, GovHydroIEEE2, and GovSteamIEEE1) are documented in IEEE Transactions, not in IEEE standards. For that reason, diagrams are supplied for those models. A 2012 IEEE report, <i><u>Dynamic Models for Turbine-Governors in Power System Studies</u></i>, provides updated information on a variety of models including IEEE, vendor and reliability authority models. Fully incorporating the results of that report into the CIM dynamics model is a future effort.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{40DA7439-D5DD-4608-85C0-87CF5444B24E}
Package notes
The turbine-governor model is linked to one or two synchronous generators and determines the shaft mechanical power (<i>Pm</i>) or torque (<i>Tm</i>) for the generator model. Unlike IEEE standard models for other function blocks, the three IEEE turbine-governor standard models (GovHydroIEEE0, GovHydroIEEE2, and GovSteamIEEE1) are documented in IEEE Transactions, not in IEEE standards. For that reason, diagrams are supplied for those models. A 2012 IEEE report, <i><u>Dynamic Models for Turbine-Governors in Power System Studies</u></i>, provides updated information on a variety of models including IEEE, vendor and reliability authority models. Fully incorporating the results of that report into the CIM dynamics model is a future effort.
Package 'TurbineGovernorDynamics' has no changes to the 38 classes it contains.
Changed diagrams (1)
β–Άβ–¦TurbineGovernorDynamicsi
Diagram notes
This diagram shows dynamic standard model turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{D646BBA5-04C5-4745-9D16-606392088DF9}
Diagram notes
This diagram shows dynamic standard model turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
β–¦Diagram
changed
Baseline
TurbineGovernorDynamics (baseline)
Destination
TurbineGovernorDynamics (destination)
β–ΆTurbineLoadControllerDynamicsi
Package notes
A turbine load controller acts to maintain turbine power at a set value by continuous adjustment of the turbine governor speed-load reference.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{F0E43C7F-6E03-4b93-B0AF-2111023CA155}
Package notes
A turbine load controller acts to maintain turbine power at a set value by continuous adjustment of the turbine governor speed-load reference.
Package 'TurbineLoadControllerDynamics' has no changes to the 2 classes it contains.
Changed diagrams (1)
β–Άβ–¦TurbineLoadControllerDynamicsi
Diagram notes
This diagram shows dynamic standard model turbine load controller classes and their inheritance from the TurbineLoadControllerDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{EA37FCB1-4727-4ecd-94F5-0C25650651A1}
Diagram notes
This diagram shows dynamic standard model turbine load controller classes and their inheritance from the TurbineLoadControllerDynamics class.
β–¦Diagram
changed
Baseline
TurbineLoadControllerDynamics (baseline)
Destination
TurbineLoadControllerDynamics (destination)
β–ΆMechanicalLoadDynamicsi
Package notes
A mechanical load represents the variation in a motor's shaft torque or power as a function of shaft speed.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{54ED4DD8-2593-43f5-9A32-43679D605D36}
Package notes
A mechanical load represents the variation in a motor's shaft torque or power as a function of shaft speed.
Package 'MechanicalLoadDynamics' has no changes to the 2 classes it contains.
Changed diagrams (1)
β–Άβ–¦MechanicalLoadDynamicsi
Diagram notes
This diagram shows dynamic standard model mechanical load classes and their inheritance from the MechanicalLoadDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{5653B8A5-52C9-401e-811E-69E155E17018}
Diagram notes
This diagram shows dynamic standard model mechanical load classes and their inheritance from the MechanicalLoadDynamics class.
β–¦Diagram
changed
Baseline
MechanicalLoadDynamics (baseline)
Destination
MechanicalLoadDynamics (destination)
β–ΆExcitationSystemDynamicsi
Package notes
The excitation system model provides the field voltage (<i>Efd</i>) for a synchronous machine model. It is linked to a specific generator (synchronous machine). The representation of all limits used by the models (not including IEEE standard models) shall comply with the representation defined in the Annex E of the IEEE 421.5-2005, unless specified differently in the documentation of the model. The parameters are different for each excitation system model; the same parameter name can have different meaning in different models.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{829F67E7-F698-4aa7-95C2-13C616AB6B78}
Package notes
The excitation system model provides the field voltage (<i>Efd</i>) for a synchronous machine model. It is linked to a specific generator (synchronous machine). The representation of all limits used by the models (not including IEEE standard models) shall comply with the representation defined in the Annex E of the IEEE 421.5-2005, unless specified differently in the documentation of the model. The parameters are different for each excitation system model; the same parameter name can have different meaning in different models.
Package 'ExcitationSystemDynamics' has no changes to the 62 classes it contains.
Changed diagrams (1)
β–Άβ–¦ExcitationSystemDynamicsi
Diagram notes
This diagram shows dynamic standard model excitation system classes and their inheritance from the ExcitationSystemDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{6F433799-BA80-4d4a-ABD1-BD898279F311}
Diagram notes
This diagram shows dynamic standard model excitation system classes and their inheritance from the ExcitationSystemDynamics class.
β–¦Diagram
changed
Baseline
ExcitationSystemDynamics (baseline)
Destination
ExcitationSystemDynamics (destination)
β–ΆOverexcitationLimiterDynamicsi
Package notes
Overexcitation limiters (OELs) are also referred to as <i>maximum excitation limiters </i>and <i>field current limiters. </i>The possibility of voltage collapse in stressed power systems increases the importance of modelling these limiters in studies of system conditions that cause machines to operate at high levels of excitation for a sustained period, such as voltage collapse or system-islanding. Such events typically occur over a long time frame compared with transient or small-signal stability simulations.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{CB5C7172-23DD-4cc0-ACF3-557E0496AFCD}
Package notes
Overexcitation limiters (OELs) are also referred to as <i>maximum excitation limiters </i>and <i>field current limiters. </i>The possibility of voltage collapse in stressed power systems increases the importance of modelling these limiters in studies of system conditions that cause machines to operate at high levels of excitation for a sustained period, such as voltage collapse or system-islanding. Such events typically occur over a long time frame compared with transient or small-signal stability simulations.
Package 'OverexcitationLimiterDynamics' has no changes to the 5 classes it contains.
Changed diagrams (1)
β–Άβ–¦OverexcitationLimiterDynamicsi
Diagram notes
This diagram shows dynamic standard model overexcitation limiter classes and their inheritance from the OverexcitationLimiterDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{FC47C181-4791-474a-AB30-CF1D0E20F49F}
Diagram notes
This diagram shows dynamic standard model overexcitation limiter classes and their inheritance from the OverexcitationLimiterDynamics class.
β–¦Diagram
changed
Baseline
OverexcitationLimiterDynamics (baseline)
Destination
OverexcitationLimiterDynamics (destination)
β–ΆUnderexcitationLimiterDynamicsi
Package notes
Underexcitation limiters (UELs) act to boost excitation. The UEL typically senses either a combination of voltage and current of the synchronous machine or a combination of real and reactive power. Some UELs utilize a temperature or pressure recalibration feature, in which the UEL characteristic is shifted depending upon the generator cooling gas temperature or pressure.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{6601D8F5-D2D3-4743-A9D8-51CADC84A53A}
Package notes
Underexcitation limiters (UELs) act to boost excitation. The UEL typically senses either a combination of voltage and current of the synchronous machine or a combination of real and reactive power. Some UELs utilize a temperature or pressure recalibration feature, in which the UEL characteristic is shifted depending upon the generator cooling gas temperature or pressure.
Package 'UnderexcitationLimiterDynamics' has no changes to the 6 classes it contains.
Changed diagrams (1)
β–Άβ–¦UnderexcitationLimiterDynamicsi
Diagram notes
This diagram shows dynamic standard model underexcitation limiter classes and their inheritance from the UnderexcitationLimiterDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{02C1E27A-FA01-4b4b-B496-F6BEDA3C6717}
Diagram notes
This diagram shows dynamic standard model underexcitation limiter classes and their inheritance from the UnderexcitationLimiterDynamics class.
β–¦Diagram
changed
Baseline
UnderexcitationLimiterDynamics (baseline)
Destination
UnderexcitationLimiterDynamics (destination)
β–ΆPowerSystemStabilizerDynamicsi
Package notes
The power system stabilizer (PSS) model provides an input (<i>Vs</i>) to the excitation system model to improve damping of system oscillations. A variety of input signals can be used depending on the particular design.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{15788FE9-6C55-412c-8AB7-F3F1EB004BDF}
Package notes
The power system stabilizer (PSS) model provides an input (<i>Vs</i>) to the excitation system model to improve damping of system oscillations. A variety of input signals can be used depending on the particular design.
Package 'PowerSystemStabilizerDynamics' has no changes to the 20 classes it contains.
Changed diagrams (1)
β–Άβ–¦PowerSystemStabilizerDynamicsi
Diagram notes
This diagram shows dynamic standard model power system stabilizer classes and their inheritance from the PowerSystemStabilizerDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{38DA7CE6-AE51-4221-B943-C23D17DBDE6B}
Diagram notes
This diagram shows dynamic standard model power system stabilizer classes and their inheritance from the PowerSystemStabilizerDynamics class.
β–¦Diagram
changed
Baseline
PowerSystemStabilizerDynamics (baseline)
Destination
PowerSystemStabilizerDynamics (destination)
β–ΆDiscontinuousExcitationControlDynamicsi
Package notes
In certain system configurations, continuous excitation control with terminal voltage and power system stabilizing regulator input signals does not ensure that the potential of the excitation system for improving system stability is fully exploited. For these situations, discontinuous excitation control signals can be employed to enhance stability following large transient disturbances. <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 12.</font>
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{510FA576-60DA-4709-96D0-60C754D1875E}
Package notes
In certain system configurations, continuous excitation control with terminal voltage and power system stabilizing regulator input signals does not ensure that the potential of the excitation system for improving system stability is fully exploited. For these situations, discontinuous excitation control signals can be employed to enhance stability following large transient disturbances. <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 12.</font>
Package 'DiscontinuousExcitationControlDynamics' has no changes to the 4 classes it contains.
Changed diagrams (1)
β–Άβ–¦DiscontinuousExcitationControlDynamicsi
Diagram notes
This diagram shows dynamic standard model discontinuous excitation control classes and their inheritance from the DiscontinuousExcitationControlDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{93B7D510-DFD1-470f-A764-E40D53B3F93A}
Diagram notes
This diagram shows dynamic standard model discontinuous excitation control classes and their inheritance from the DiscontinuousExcitationControlDynamics class.
β–¦Diagram
changed
Baseline
DiscontinuousExcitationControlDynamics (baseline)
Destination
DiscontinuousExcitationControlDynamics (destination)
β–ΆPFVArControllerType1Dynamicsi
Package notes
<font color="#0f0f0f">Excitation systems for synchronous machines are sometimes supplied with an optional means of automatically adjusting generator output reactive power (VAr) or power factor (PF) to a user-specified value. This can be accomplished with either a reactive power or power factor controller or regulator. A reactive power or power factor controller is defined as a PF/VAr controller in IEEE 421.1 as β€œa control function that acts through the reference adjuster to modify the voltage regulator set point to maintain the synchronous machine steady-state power factor or reactive power at a predetermined value.” </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font>
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{DB4B66D7-C753-481b-9C15-D0753561B765}
Package notes
<font color="#0f0f0f">Excitation systems for synchronous machines are sometimes supplied with an optional means of automatically adjusting generator output reactive power (VAr) or power factor (PF) to a user-specified value. This can be accomplished with either a reactive power or power factor controller or regulator. A reactive power or power factor controller is defined as a PF/VAr controller in IEEE 421.1 as β€œa control function that acts through the reference adjuster to modify the voltage regulator set point to maintain the synchronous machine steady-state power factor or reactive power at a predetermined value.” </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font>
Package 'PFVArControllerType1Dynamics' has no changes to the 3 classes it contains.
Changed diagrams (1)
β–Άβ–¦PFVArControllerType1Dynamicsi
Diagram notes
This diagram shows dynamic standard model power factor or VAr controller type 1 classes and their inheritance from the PFVArControllerType1Dynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{E5E56E46-8B1A-43d6-88B0-4C85E096AD7B}
Diagram notes
This diagram shows dynamic standard model power factor or VAr controller type 1 classes and their inheritance from the PFVArControllerType1Dynamics class.
β–¦Diagram
changed
Baseline
PFVArControllerType1Dynamics (baseline)
Destination
PFVArControllerType1Dynamics (destination)
β–ΆVoltageAdjusterDynamicsi
Package notes
<font color="#0f0f0f">A voltage adjuster is a reference adjuster that uses inputs from a reactive power or power factor controller to modify the voltage regulator set point to maintain the synchronous machine steady-state power factor or reactive power at a predetermined value. </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font>
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{35B78447-A031-4927-A915-5C69304A72D2}
Package notes
<font color="#0f0f0f">A voltage adjuster is a reference adjuster that uses inputs from a reactive power or power factor controller to modify the voltage regulator set point to maintain the synchronous machine steady-state power factor or reactive power at a predetermined value. </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font>
Package 'VoltageAdjusterDynamics' has no changes to the 2 classes it contains.
Changed diagrams (1)
β–Άβ–¦VoltageAdjusterDynamicsi
Diagram notes
This diagram shows dynamic standard model voltage adjuster classes and their inheritance from the VoltageAdjusterDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{98EECFEA-7320-4d23-A006-FB39CEBEC0AE}
Diagram notes
This diagram shows dynamic standard model voltage adjuster classes and their inheritance from the VoltageAdjusterDynamics class.
β–¦Diagram
changed
Baseline
VoltageAdjusterDynamics (baseline)
Destination
VoltageAdjusterDynamics (destination)
β–ΆPFVArControllerType2Dynamicsi
Package notes
<font color="#0f0f0f">A var/pf regulator is defined as β€œa synchronous machine regulator that functions to maintain the power factor or reactive component of power at a predetermined value.” </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font> <font color="#0f0f0f"> </font>
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{9AF74EDB-FFF5-4083-A7D5-48644244A045}
Package notes
<font color="#0f0f0f">A var/pf regulator is defined as β€œa synchronous machine regulator that functions to maintain the power factor or reactive component of power at a predetermined value.” </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11.</font> <font color="#0f0f0f"> </font>
Package 'PFVArControllerType2Dynamics' has no changes to the 4 classes it contains.
Changed diagrams (1)
β–Άβ–¦PFVArControllerType2Dynamicsi
Diagram notes
This diagram shows dynamic standard model power factor or VAr controller type 2 classes and their inheritance from the PFVArControllerType2Dynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{99C16D20-6A74-4483-A25E-34444E865297}
Diagram notes
This diagram shows dynamic standard model power factor or VAr controller type 2 classes and their inheritance from the PFVArControllerType2Dynamics class.
β–¦Diagram
changed
Baseline
PFVArControllerType2Dynamics (baseline)
Destination
PFVArControllerType2Dynamics (destination)
β–ΆVoltageCompensatorDynamicsi
Package notes
<font color="#0f0f0f">Synchronous machine terminal voltage transducer and current compensator models</font> adjust the terminal voltage feedback to the excitation system by adding a quantity that is proportional to the terminal current of the generator. It is linked to a specific generator (synchronous machine). <font color="#0f0f0f">Several types of compensation are available on most excitation systems. Synchronous machine active and reactive current compensation are the most common. Either reactive droop compensation and/or line-drop compensation can be used, simulating an impedance drop and effectively regulating at some point other than the terminals of the machine. The impedance or range of adjustment and type of compensation should be specified for different types. </font> <font color="#0f0f0f">Care shall be taken to ensure that a consistent PU system is utilized for the compensator parameters and the synchronous machine current base.</font> <font color="#0f0f0f">For further information see IEEE 421.5-2005, 4.</font> <font color="#0f0f0f"> </font>
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{7FD04580-1444-4ea3-A69D-D2D00000A4A9}
Package notes
<font color="#0f0f0f">Synchronous machine terminal voltage transducer and current compensator models</font> adjust the terminal voltage feedback to the excitation system by adding a quantity that is proportional to the terminal current of the generator. It is linked to a specific generator (synchronous machine). <font color="#0f0f0f">Several types of compensation are available on most excitation systems. Synchronous machine active and reactive current compensation are the most common. Either reactive droop compensation and/or line-drop compensation can be used, simulating an impedance drop and effectively regulating at some point other than the terminals of the machine. The impedance or range of adjustment and type of compensation should be specified for different types. </font> <font color="#0f0f0f">Care shall be taken to ensure that a consistent PU system is utilized for the compensator parameters and the synchronous machine current base.</font> <font color="#0f0f0f">For further information see IEEE 421.5-2005, 4.</font> <font color="#0f0f0f"> </font>
Package 'VoltageCompensatorDynamics' has no changes to the 4 classes it contains.
Changed diagrams (1)
β–Άβ–¦VoltageCompensatorDynamicsi
Diagram notes
This diagram shows dynamic standard model voltage compensator classes and their inheritance from the VoltageCompensatorDynamics class.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{107B566B-D071-4cc9-B058-F986EB9B14D5}
Diagram notes
This diagram shows dynamic standard model voltage compensator classes and their inheritance from the VoltageCompensatorDynamics class.
β–¦Diagram
changed
Baseline
VoltageCompensatorDynamics (baseline)
Destination
VoltageCompensatorDynamics (destination)
β–ΆHVDCDynamicsi
Package notes
High voltage direct current (HVDC) models.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{7C62349B-D355-4ba0-BE12-91068427292A}
Package notes
High voltage direct current (HVDC) models.
Package 'HVDCDynamics' has no changes to the 3 classes it contains.
Changed diagrams (1)
β–Άβ–¦HVDCDynamicsi
Diagram notes
This diagram shows the dynamics model classes related to modelling of the HVDC.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{CE7EEDFF-0F31-40bd-A1D7-85C44EC39CDE}
Diagram notes
This diagram shows the dynamics model classes related to modelling of the HVDC.
β–¦Diagram
changed
Baseline
HVDCDynamics (baseline)
Destination
HVDCDynamics (destination)
β–ΆStaticVarCompensatorDynamicsi
Package notes
Static var compensator (SVC) models.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{97871C31-9D61-4b9b-A49A-F63A7DC2DBA5}
Package notes
Static var compensator (SVC) models.
Package 'StaticVarCompensatorDynamics' has no changes to the 1 classes it contains.
Changed diagrams (1)
β–Άβ–¦StaticVarCompensatorDynamicsi
Diagram notes
This diagram shows the dynamics model classes related to modelling of the static var compensator (SVC) models.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{94AF0B28-6DC7-475c-9559-0CAC69363500}
Diagram notes
This diagram shows the dynamics model classes related to modelling of the static var compensator (SVC) models.
β–¦Diagram
changed
Baseline
StaticVarCompensatorDynamics (baseline)
Destination
StaticVarCompensatorDynamics (destination)
Package 'StandardModels' has no changes to the 2 classes it contains.
β–ΆInfIEC61970i
Package notes
This package and its subpackages contain informative (unstable) elements of the model, expected to evolve a lot or to be removed, and not published as IEC document yet. Some portions of it will be reworked and moved to normative packages as the need arises, and some portions may be removed. WG13 does not generate documentation for this informative portion of the model.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{D2DD87AA-AF0C-477c-8E65-69D543D76521}
Package notes
This package and its subpackages contain informative (unstable) elements of the model, expected to evolve a lot or to be removed, and not published as IEC document yet. Some portions of it will be reworked and moved to normative packages as the need arises, and some portions may be removed. WG13 does not generate documentation for this informative portion of the model.
β–ΆInfSIPSi
Package notes
System Integrity Protection Schemes (SIPS) (IEC terminology). Other names used are: Remedial Action Schemes (RAS) or System Protection Schemes (SPS).
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{BB903AB3-D08C-4d30-A5AE-E3FA868711FA}
Package notes
System Integrity Protection Schemes (SIPS) (IEC terminology). Other names used are: Remedial Action Schemes (RAS) or System Protection Schemes (SPS).
Package 'InfSIPS' has no changes to the 26 classes it contains.
Changed diagrams (1)
β–Άβ–¦RASInheritancei
Diagram notes
No notes defined in the model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{35E945F1-DE75-4233-9318-EA2DCCB57A18}
Diagram notes
No notes defined in the model.
β–¦Diagram
changed
Baseline
RASInheritance (baseline)
Destination
RASInheritance (destination)
β–ΆInfPart303i
Package notes
No notes defined in the model.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{500389E9-5C8C-40f4-9EB4-19613576509E}
Package notes
No notes defined in the model.
β–ΆNetworkModelFramesi
Package notes
No notes defined in the model.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{2C9E3B69-563C-4663-96DD-0E1074BE5F73}
Package notes
No notes defined in the model.
Package 'NetworkModelFrames' has no changes to the 14 classes it contains.
Changed diagrams (1)
β–Άβ–¦Framesi
Diagram notes
No notes defined in the model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{9AE9BC65-CE60-4818-BCA9-8D6A8511D1C7}
Diagram notes
No notes defined in the model.
β–¦Diagram
changed
Baseline
Frames (baseline)
Destination
Frames (destination)
Connectors 1 removedhover a connector to outline the elements it joins
removedDataSet – Profile
β–ΆNetworkModelProjectsi
Package notes
Defining meta-data for a change set in the functional Power System model.
Package metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
{0090ED2A-A4A9-40f2-B6AC-02BBFADFE48D}
Package notes
Defining meta-data for a change set in the functional Power System model.
Package 'NetworkModelProjects' has no changes to the 19 classes it contains.
Changed diagrams (2)
β–Άβ–¦InfPowerSystemProjectsPJMi
Diagram notes
No notes defined in the model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{AAA4A8EE-D7BF-41c1-8611-15C1D784E506}
Diagram notes
No notes defined in the model.
β–¦Diagram
changed
Baseline
InfPowerSystemProjectsPJM (baseline)
Destination
InfPowerSystemProjectsPJM (destination)
β–Άβ–¦PowerSystemProjectDiscussioni
Diagram notes
No notes defined in the model.
Diagram metadata β€” changes
BaselineDestination
no changes
CHANGED{4BA9AD4C-A0FC-4df6-B473-0BDF19FA1F70}
Diagram notes
No notes defined in the model.
β–¦Diagram
changed
Baseline
PowerSystemProjectDiscussion (baseline)
Destination
PowerSystemProjectDiscussion (destination)
Package 'InfIEC61970' has no changes to the 1 diagrams it contains.
Changed classes (1)
β–Άβš™IEC61970CIMVersioni
Class notes
This is the IEC 61970 CIM version number assigned to this UML model.
Class metadata β€” changes
BaselineDestination
no changes
Tagged values β€” changes
BaselineDestination
no changes
CHANGED{990AB50C-5CF8-46d2-B5FF-887BBBD3346F}
Class notes
This is the IEC 61970 CIM version number assigned to this UML model.
≑Attributes
AttributeBaselineDestinationNotes (destination, redlined)
dateimetadata changed - hovermetadata changed{8DADB97F-283D-40c7-A25A-D75E4C0D8507}show detailsDate [0..1]Date [0..1]Form is YYYY-MM-DD for example for January 5, 2009 it is 2009-01-05.
Attribute notes
Form is YYYY-MM-DD for example for January 5, 2009 it is 2009-01-05.
Attribute metadata β€” changes
BaselineDestination
Default2020-06-152021-09-15
Tagged values β€” changes
BaselineDestination
no changes
versionimetadata changed - hovermetadata changed{B4E0B1B6-8794-406a-A4C6-CBB395E37A52}show detailsString [0..1]String [0..1]Form is IEC61970CIMXXvYY where XX is the major CIM package version and the YY is the minor version. For example IEC61970CIM13v18.
Attribute notes
Form is IEC61970CIMXXvYY where XX is the major CIM package version and the YY is the minor version. For example IEC61970CIM13v18.
Attribute metadata β€” changes
BaselineDestination
DefaultIEC61970CIM18v00IEC61970CIM18v01
Tagged values β€” changes
BaselineDestination
no changes
Changed diagrams (1)
β–Άβ–¦IEC61970Dependenciesi
Diagram notes
This diagram shows all 61970-301 packages and their logical dependencies.
Diagram metadata β€” changes
BaselineDestination
ModifiedDate2019-09-21 20:26:392021-09-29 11:05:23
CHANGED{FB07D92D-5F4D-4fdc-AD82-2376FAF51037}
Diagram notes
This diagram shows all 61970-301 packages and their logical dependencies.
β–€Metadata
BaselineDestination
ModifiedDate2019-09-21 20:26:392021-09-29 11:05:23
β–¦Diagram
addedmoved or resized
Baseline
IEC61970Dependencies (baseline)
Destination
IEC61970Dependencies (destination)
Connectors 1 added Β· 1 reroutedhover a connector to outline the elements it joins
added(not in this model) – (not in this model)
rerouted(not in this model) – (not in this model)