CIM Model Comparison ·18v15 baseline → 18v16 destination
Scope: Grid · compared 2026-11-04 14:03:33 · 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 changed
Classes37 added5 moved67 changed
Diagrams126 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)
▶Gridi
Package notes
This top package includes the CIM model related to the grid.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{21D32832-FF64-4213-B81C-55ACE35EEBFF}
Package notes
This top package includes the CIM model related to the grid.
▶Basei
Package notes
Content of the base CIM. The information in the entire clause "Common Information Model Base Package" is reproduced from the UML with the permission of UCAIug.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{20A2C6D8-4765-466f-AD75-5E1B3CAF4E8D}
Package notes
Content of the base CIM. The information in the entire clause "Common Information Model Base Package" is reproduced from the UML with the permission of UCAIug.
▶Controli
Package notes
The package contains classes related to control.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{E4988A5C-BF54-48c4-8232-CE533FD8BB23}
Package notes
The package contains classes related to control.
Package 'Control' has no changes to the 48 classes it contains.
Changed diagrams (3)
▶▦DocDirectCurrentControlrenamed from DocDirectCurentControli
Diagram notes
The diagram contains classes related to direct current control.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:43:322026-04-21 12:01:00
NameDocDirectCurentControlDocDirectCurrentControl
CHANGED{4700B37E-D4BB-4ad0-9F6B-99407FF13498}
Diagram notes
The diagram contains classes related to direct current control.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:43:322026-04-21 12:01:00
NameDocDirectCurentControlDocDirectCurrentControl
Diagram 'DocDirectCurrentControl' has no other changes. The shows its notes and every changed property.
▶▦DocEquipmentControlleri
Diagram notes
The diagram contains classes and association related to equipment control.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{1980A549-CE27-4f4f-AEE0-461A8BC047BC}
Diagram notes
The diagram contains classes and association related to equipment control.
▦Diagram
changed
Baseline
DocEquipmentController (baseline)
Destination
DocEquipmentController (destination)
Connectors 1 removedhover a connector to outline the elements it joins
removedStaticVarCompensator – RegulatingCondEq
▶▦DocPowerElectronicsControli
Diagram notes
The diagram contains classes and association related to power electronics control.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{4825BA06-F341-4549-B2E9-CA61AB2BE2FA}
Diagram notes
The diagram contains classes and association related to power electronics control.
▦Diagram
changed
Baseline
DocPowerElectronicsControl (baseline)
Destination
DocPowerElectronicsControl (destination)
▶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.
Added classes (2)
▶⚙NameKind«enumeration»i
Class notes
A standardised classification of name values used to refer to an IdentifiedObject in different contexts. NameKind values are intended to be stable and directly usable in profiles and implementation guidance without requiring external reference data.
Class metadata — changes
BaselineDestination
Abstractfalse
Authordomagoj.peharda
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNameKind
ParentPackageCore
Phase1.0
Scopepublic
StatusProposed
Stereotypeenumeration
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{190808A3-21BD-4b6c-8337-16A8384247F5}
Class notes
A standardised classification of name values used to refer to an IdentifiedObject in different contexts. NameKind values are intended to be stable and directly usable in profiles and implementation guidance without requiring external reference data.
▤Metadata
BaselineDestination
Abstractfalse
Authordomagoj.peharda
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNameKind
ParentPackageCore
Phase1.0
Scopepublic
StatusProposed
Stereotypeenumeration
TypeClass
Version1.0
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
aliasi{F9DC1A02-F831-45d2-8A40-7A7AAA16D13F}show detailsdid not exist [1..1]An alternative name used by a system, project, or user community that differs from the default or preferred name.
Attribute notes
An alternative name used by a system, project, or user community that differs from the default or preferred name.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namealias
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
devicei{93B6D6C3-4034-4163-BAEB-48DD192223E3}show detailsdid not exist [1..1]A name used to identify a device, component, or object instance within a vendor system, device platform, or operational system. Such names are typically assigned by manufacturers, device firmware, automation systems, metering systems, or enterprise applications (e.g., ERP, asset management, monitoring platforms) and are used for configuration, monitoring, or asset tracking. Note: Device names are often defined within the scope of a particular vendor, system, or installation and are therefore typically unique only within that system context. Example: "IED_BAY3_01", "Meter_102394", "SAP_EQ_000457812"
Attribute notes
A name used to identify a device, component, or object instance within a vendor system, device platform, or operational system. Such names are typically assigned by manufacturers, device firmware, automation systems, metering systems, or enterprise applications (e.g., ERP, asset management, monitoring platforms) and are used for configuration, monitoring, or asset tracking. Note: Device names are often defined within the scope of a particular vendor, system, or installation and are therefore typically unique only within that system context. Example: "IED_BAY3_01", "Meter_102394", "SAP_EQ_000457812"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namedevice
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
eici{FCF21086-192A-43aa-BE76-AB29C18810CE}show detailsdid not exist [1..1]An Energy Identification Code name, typically used in European energy market and interoperability contexts. Example: "10YNO-0--------C"
Attribute notes
An Energy Identification Code name, typically used in European energy market and interoperability contexts. Example: "10YNO-0--------C"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Nameeic
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
iec61850i{B3F83D03-1CA2-4c48-8B8E-5B3955D0028C}show detailsdid not exist [1..1]A name used in IEC 61850 contexts (e.g., IED name, logical node naming, object references, or related 61850 naming forms as specified by the profile).Example: "LD0/XCBR1.Pos.stVal"
Attribute notes
A name used in IEC 61850 contexts (e.g., IED name, logical node naming, object references, or related 61850 naming forms as specified by the profile).Example: "LD0/XCBR1.Pos.stVal"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Nameiec61850
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
labeli{B094413D-CB11-4fbb-AB92-5EA8CE716CF5}show detailsdid not exist [1..1]A short name primarily intended for local display, compact user interfaces, and single-line diagrams. A label is generally preferred to be short and readable rather than globally unique. Example: "T1", "Bay3"
Attribute notes
A short name primarily intended for local display, compact user interfaces, and single-line diagrams. A label is generally preferred to be short and readable rather than globally unique. Example: "T1", "Bay3"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namelabel
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
locali{FA364C1A-C75D-465d-A6F6-E0DCF4AB3443}show detailsdid not exist [1..1]A name used within a local naming scope (site, system, organisation, or sub-hierarchy) where meaning is derived from the local context. The name shall be unique inside the container, e.g. substation.
Attribute notes
A name used within a local naming scope (site, system, organisation, or sub-hierarchy) where meaning is derived from the local context. The name shall be unique inside the container, e.g. substation.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namelocal
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
pathi{0FBB7809-BD6C-4aca-9F31-B6345C5EE91E}show detailsdid not exist [1..1]A hierarchical name constructed from a sequence of name segments representing containment, structure, or functional decomposition. Example: "SubstationA/Bay3/Breakder1"
Attribute notes
A hierarchical name constructed from a sequence of name segments representing containment, structure, or functional decomposition. Example: "SubstationA/Bay3/Breakder1"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namepath
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
rdsi{84174F58-EEAD-4b3a-A561-B719CD5605C8}show detailsdid not exist [1..1]A name following the Reference Designation System (RDS) defined in IEC 81346, used to uniquely identify systems, functions, and equipment within engineering documentation and technical installations. RDS names express the position or role of an object within a structured engineering hierarchy and are widely used in electrical engineering documentation, drawings, and plant documentation. Note: The Reference Designation System (RDS) provides a structured identification scheme where each segment represents an aspect of an object such as function ("="), product ("-"), or location ("+").Example: "=N01+SA1-Q01"
Attribute notes
A name following the Reference Designation System (RDS) defined in IEC 81346, used to uniquely identify systems, functions, and equipment within engineering documentation and technical installations. RDS names express the position or role of an object within a structured engineering hierarchy and are widely used in electrical engineering documentation, drawings, and plant documentation. Note: The Reference Designation System (RDS) provides a structured identification scheme where each segment represents an aspect of an object such as function ("="), product ("-"), or location ("+").Example: "=N01+SA1-Q01"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namerds
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
urni{6069EBFC-69EA-445a-BC89-1F72E55EAD73}show detailsdid not exist [1..1]A name expressed as a Uniform Resource Name (URN), a persistent identifier defined using a registered namespace according to IETF RFC 8141.URN namespaces provide globally unique identifiers without requiring a resolvable URL and are commonly defined by standards bodies, industry communities, or organisations. Note: URN identifiers use the general structure: "urn:<namespace>:<identifier>" where <namespace> identifies a registered namespace and <identifier> is the value assigned within that namespace. Example: Object Identifier (OID) "urn:oid:1.3.6.1.4.1.4555", UUID namespace "urn:uuid:550e8400-e29b-41d4-a716-446655440000", EIC namespace "urn:eic:10YNO-0--------C"
Attribute notes
A name expressed as a Uniform Resource Name (URN), a persistent identifier defined using a registered namespace according to IETF RFC 8141.URN namespaces provide globally unique identifiers without requiring a resolvable URL and are commonly defined by standards bodies, industry communities, or organisations. Note: URN identifiers use the general structure: "urn:<namespace>:<identifier>" where <namespace> identifies a registered namespace and <identifier> is the value assigned within that namespace. Example: Object Identifier (OID) "urn:oid:1.3.6.1.4.1.4555", UUID namespace "urn:uuid:550e8400-e29b-41d4-a716-446655440000", EIC namespace "urn:eic:10YNO-0--------C"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Nameurn
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
uuidi{2A263A27-A329-4023-916D-E288389864BA}show detailsdid not exist [1..1]A designation expressed as a Universally Unique Identifier (UUID) as defined in IETF RFC 4122 (and its successor RFC 9562). UUIDs are 128-bit identifiers designed to be globally unique without requiring a central registration authority. UUID names are commonly used in software systems and data exchanges to provide stable identifiers across distributed systems. Note: A UUID is typically represented as a 36-character string consisting of hexadecimal digits grouped in five sections separated by hyphens. Example: "550e8400-e29b-41d4-a716-446655440000"
Attribute notes
A designation expressed as a Universally Unique Identifier (UUID) as defined in IETF RFC 4122 (and its successor RFC 9562). UUIDs are 128-bit identifiers designed to be globally unique without requiring a central registration authority. UUID names are commonly used in software systems and data exchanges to provide stable identifiers across distributed systems. Note: A UUID is typically represented as a 36-character string consisting of hexadecimal digits grouped in five sections separated by hyphens. Example: "550e8400-e29b-41d4-a716-446655440000"
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Nameuuid
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙NameTypeAuthorityi
Class notes
Authority responsible for creation and management of names of a given type; typically an organization or an enterprise system.
Class metadata — changes
BaselineDestination
Abstractfalse
AuthorT. Kostic
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNameTypeAuthority
ParentPackageCore
Phase1.0
Scopepublic
StatusProposed
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{F4E2C3FE-B480-46c9-8840-DF8D3F3BD6CC}
Class notes
Authority responsible for creation and management of names of a given type; typically an organization or an enterprise system.
▤Metadata
BaselineDestination
Abstractfalse
AuthorT. Kostic
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNameTypeAuthority
ParentPackageCore
Phase1.0
Scopepublic
StatusProposed
TypeClass
Version1.0
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
descriptioni{90C20513-82B6-4090-89AE-2FE6E6F81954}show detailsdid not existString [0..1]Description of the name type authority.
Attribute notes
Description of the name type authority.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
Namedescription
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
namei{3D2A9B24-AB04-454f-BD8E-01ECCEAE4103}show detailsdid not existString [0..1]Name of the name type authority.
Attribute notes
Name of the name type authority.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
Namename
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
Baselinedid not exist
→
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNameTypeAuthority
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Baselinedid not exist
→
DestinationNameType role NameTypes [0..*] → NameTypeAuthority role NameTypeAuthority [0..1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndNameType
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameTypes
RoleNoteAll name types managed by this authority.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndNameTypeAuthority
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameTypeAuthority
RoleNoteAuthority responsible for managing names of this type.
Scopepublic
TargetScopeinstance
Moved classes (1)
▶⚙Seasoni
Class notes
A specified time period of the year.
Class metadata — changes
BaselineDestination
ParentPackageLoadModelCore
Tagged values — changes
BaselineDestination
no changes
MOVEDfrom LoadModel{34DC6AAA-A359-4408-9348-0305AB9E9E9A}
Class notes
A specified time period of the year.
▤Metadata
BaselineDestination
ParentPackageLoadModelCore
⇄Links
Baselinedid not exist
→
DestinationSeason role Season [0..1] → OperationalLimitSet role OperationalLimitSet [0..*]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndSeason
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleSeason
RoleNoteThe season for this operational limit set.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndOperationalLimitSet
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleOperationalLimitSet
RoleNoteThe operational limit set that has a season.
Scopepublic
TargetScopeinstance
Changed classes (13)
▶⚙BaseVoltagei
Class notes
Defines a system base voltage which is referenced. This may be different than the rated voltage.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{2E70DC9D-AEAE-46cc-B20A-C20A636AE9B0}
Class notes
Defines a system base voltage which is referenced. This may be different than the rated voltage.
⇄Links
Baselinedid not exist
→
DestinationBaseVoltage role BaseVoltage [0..1] → ConnectivityNode role ConnectivityNode [0..*]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndBaseVoltage
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleBaseVoltage
RoleNoteThe base voltage for the connectivity node. The association end ConnectivityNode.BaseVoltage is used only if the ConnectivityNode is not contained in a VoltageLevel. Otherwise use the association end VoltageLevel.BaseVoltage and disregard the relation ConnectivityNode.BaseVoltage. It is not required that the BaseVoltage of connected equipment is the same.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
RoleNoteThe connectivity node that has this base voltage.
Scopepublic
TargetScopeinstance
▶⚙Bayi
Class notes
A collection of power system resources (within a given substation) including conducting equipment, protection relays, measurements, and telemetry. A bay typically represents a physical grouping related to modularization of equipment.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{45910062-D4E8-40ee-99EB-FEC14DD9FAB0}
Class notes
A collection of power system resources (within a given substation) including conducting equipment, protection relays, measurements, and telemetry. A bay typically represents a physical grouping related to modularization of equipment.
⇄Links
BaselineCircuit role Circuit [0..1] → Bay role EndBay [0..*]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
Stereotypeinformative
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndCircuit
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleCircuit
RoleNoteCircuit containing the bay.
Scopepublic
Stereotypeinformative
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndBay
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleEndBay
Scopepublic
Stereotypeinformative
TargetScopeinstance
▶⚙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
→
DestinationBaseVoltage role BaseVoltage [0..1] → ConnectivityNode role ConnectivityNode [0..*]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndBaseVoltage
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleBaseVoltage
RoleNoteThe base voltage for the connectivity node. The association end ConnectivityNode.BaseVoltage is used only if the ConnectivityNode is not contained in a VoltageLevel. Otherwise use the association end VoltageLevel.BaseVoltage and disregard the relation ConnectivityNode.BaseVoltage. It is not required that the BaseVoltage of connected equipment is the same.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndConnectivityNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleConnectivityNode
RoleNoteThe connectivity node that has this base voltage.
Scopepublic
TargetScopeinstance
▶⚙Feederi
Class notes
A collection of equipment for organizational purposes, used for grouping distribution resources. The organization a feeder does not necessarily reflect connectivity or current operation state.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{FE6F802E-8B23-470b-B678-A29A27235CA8}
Class notes
A collection of equipment for organizational purposes, used for grouping distribution resources. The organization a feeder does not necessarily reflect connectivity or current operation state.
⇄Links
BaselineFeeder role NormalHeadFeeder [0..1] → Terminal role NormalHeadTerminal [1..*]
→
DestinationFeeder role NormalHeadFeeder [0..1] → Terminal role NormalHeadTerminal [1..*]
Source end
no changes
Target end — NormalHeadTerminal
BaselineDestination
RoleNoteThe normal head terminal or terminals of the feeder.The normal head terminal (or terminals) of the feeder. The tracing is done towards the conducting equipment associated with the head terminal (or terminals).
▶⚙IdentifiedObjecti
Class notes
This is a class that provides 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 class that provides common identification for all classes needing identification and naming attributes.
⇄Links
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndTransformerEnd
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentifiedObject
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineName role AlternativeIdentifier [0..*] → IdentifiedObject role UniqueIdentifiedObject [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndName
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleAlternativeIdentifier
RoleNoteAll alternative identifiers of this identified object. No two identified objects can have the same alternative identifier.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndIdentifiedObject
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleUniqueIdentifiedObject
RoleNoteIdentified object that this alternative identifier designates.
Scopepublic
TargetScopeinstance
▶⚙Identityi
Class notes
This is a root class to provide common identification for all classes.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{FB5C07D4-FC5D-4da8-8D12-4AA323CC74AA}
Class notes
This is a root class to provide common identification for all classes.
⇄Links
Baselinedid not exist
→
DestinationIdentity → NamingAuthority
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNamingAuthority
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Baselinedid not exist
→
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNameTypeAuthority
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Baselinedid not exist
→
DestinationIdentity → Name
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndName
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Baselinedid not exist
→
DestinationIdentity → NameType
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNameType
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙Namei
Class notes (destination, redlined)
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. The Name class allows for the introduction of one of more alternative names or alternative identifiers for an object identified by association to IdentifiedObject, which need to have associated NameType or nameKind. Example: display label such as “T1”; alternative mRID; alternative address text; serial number of the device; etc.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{D6F3DF4E-3363-48d2-AB61-7872E337C422}
Class notes (destination, redlined)
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. The Name class allows for the introduction of one of more alternative names or alternative identifiers for an object identified by association to IdentifiedObject, which need to have associated NameType or nameKind. Example: display label such as “T1”; alternative mRID; alternative address text; serial number of the device; etc.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
languagei{7BD54A11-2123-495f-8BEB-2BF5554B6892}show detailsString [0..1]removed from model
Attribute notes (baseline)
Shall be specified as an IETF BCP 47 language tag (e.g. en-US). Applies to the Name.name attribute. IETF language tags combine subtags from other standards such as ISO 639, ISO 15924, ISO 3166-1, and UN M.49. The tag structure has been standardized by the IETF in Best Current Practice (BCP) 47; the subtags are maintained by the IANA Language Subtag Registry.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namelanguage
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
mRIDi{0C279D18-CE6D-4582-A80C-5C3CDB3EC4DE}show detailsString [0..1]removed from model
Attribute notes (baseline)
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemRID
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
nameKindi{76EC6112-5179-405c-8C70-E355C1097244}show detailsdid not existNameKind [0..1]NameKind provides standardised categories that profile restrictions and validations can reference directly in profiles. Different profiles can use NameKind enumerations to restrict name differently (for example local enumeration can be 32 characters long in one profile and 16 in another). Additional constraints or specialisations may be defined through NameType.
Attribute notes
NameKind provides standardised categories that profile restrictions and validations can reference directly in profiles. Different profiles can use NameKind enumerations to restrict name differently (for example local enumeration can be 32 characters long in one profile and 16 in another). Additional constraints or specialisations may be defined through NameType.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamenameKind
Scale0
Scopepublic
Staticfalse
TypeNameKind
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
Baselinedid not exist
→
DestinationIdentity → Name
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndName
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineNameType role NameType [0..1] → Name role Name [0..*]
→
DestinationNameType role NameType [0..1] → Name role NameNames [0..*]
Source end
no changes
Target end — Names
BaselineDestination
RoleNameNames
BaselineName role AlternativeIdentifier [0..*] → IdentifiedObject role UniqueIdentifiedObject [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndName
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleAlternativeIdentifier
RoleNoteAll alternative identifiers of this identified object. No two identified objects can have the same alternative identifier.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndIdentifiedObject
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleUniqueIdentifiedObject
RoleNoteIdentified object that this alternative identifier designates.
Scopepublic
TargetScopeinstance
▶⚙NameTypei
Class notes (destination, redlined)
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. A specification that defines a non-standard name type used to classify and constrain Name object beyond the standardised NameKind enumeration. NameType provides constraints on name object and its relationships. NameType attributes carry constraints that can be used for restriction and validation of Name objects. It is not possible to use profiles to validate Name objects that are not using NameKind enumeration so NameType carries attributes that can provide restrictions on Name objects.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{666F94BF-13E3-4947-830F-3A2D4E7CC9FC}
Class notes (destination, redlined)
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. A specification that defines a non-standard name type used to classify and constrain Name object beyond the standardised NameKind enumeration. NameType provides constraints on name object and its relationships. NameType attributes carry constraints that can be used for restriction and validation of Name objects. It is not possible to use profiles to validate Name objects that are not using NameKind enumeration so NameType carries attributes that can provide restrictions on Name objects.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
languagei{211868A3-0099-4efb-8AA9-4FBB38A84558}show detailsdid not existString [0..1]The language attribute specifies the natural language of the Name.name string and shall conform to ISO 639-1. The language attribute does not participate in identity or uniqueness and is provided for information only.
Attribute notes
The language attribute specifies the natural language of the Name.name string and shall conform to ISO 639-1. The language attribute does not participate in identity or uniqueness and is provided for information only.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namelanguage
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
mRIDi{CE8AA2CE-299B-4977-885F-1808B22794B6}show detailsString [0..1]removed from model
Attribute notes (baseline)
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemRID
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
maxNameLengthi{A242DF30-D230-41f7-922E-1110FC1F7544}show detailsdid not existInteger [1..1]Maximum length of the characters (not bytes) of the Name.name string.
Attribute notes
Maximum length of the characters (not bytes) of the Name.name string.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound1
NamemaxNameLength
Scale0
Scopepublic
Staticfalse
TypeInteger
UpperBound1
Tagged values — changes
BaselineDestination
none
regularExpressioni{353BA96C-FE0E-4ac3-BC31-740C22B9A49D}show detailsdid not existString [1..1]Regular expression pattern restricting Name.name string. The regular expression syntax shall conform to POSIX Extended Regular Expressions (ERE) as defined in IEEE Std 1003.1.
Attribute notes
Regular expression pattern restricting Name.name string. The regular expression syntax shall conform to POSIX Extended Regular Expressions (ERE) as defined in IEEE Std 1003.1.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound1
NameregularExpression
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
singleNamePerIdentifiedObjecti{4D70BF04-BEA5-4f3c-BF66-3D1C5D964749}show detailsdid not existBoolean [1..1]If true requires that all Name.IdentifiedObject associations are unique for all Name objects of the same NameType.
Attribute notes
If true requires that all Name.IdentifiedObject associations are unique for all Name objects of the same NameType.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound1
NamesingleNamePerIdentifiedObject
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
typeRefi{93A1F813-1729-46b3-881B-386A07C149FA}show detailsdid not existURI [1..1]URI of the NameType.
Attribute notes
URI of the NameType.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound1
NametypeRef
Scale0
Scopepublic
Staticfalse
TypeURI
UpperBound1
Tagged values — changes
BaselineDestination
none
uniqueNamePerNameTypei{3662FBF2-AC25-4c85-9AFB-44A27D3C7C08}show detailsdid not existBoolean [1..1]If true requires that the Name.name strings are unique for all Name objects of the same NameType.
Attribute notes
If true requires that the Name.name strings are unique for all Name objects of the same NameType.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound1
NameuniqueNamePerNameType
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
Baselinedid not exist
→
DestinationIdentity → NameType
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNameType
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Baselinedid not exist
→
DestinationNameType role NameTypes [0..*] → NameTypeAuthority role NameTypeAuthority [0..1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndNameType
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameTypes
RoleNoteAll name types managed by this authority.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndNameTypeAuthority
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameTypeAuthority
RoleNoteAuthority responsible for managing names of this type.
Scopepublic
TargetScopeinstance
BaselineNameType role NameType [0..1] → Name role Name [0..*]
→
DestinationNameType role NameType [0..1] → Name role NameNames [0..*]
Source end
no changes
Target end — Names
BaselineDestination
RoleNameNames
BaselineNameType role NameType [0..*] → NamingAuthority role NamingAuthority [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndNameType
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameType
RoleNoteAll name types managed by this authority.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndNamingAuthority
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNamingAuthority
RoleNoteAuthority responsible for managing this name type.
Scopepublic
TargetScopeinstance
▶⚙NamingAuthorityi
Class notes (destination, redlined)
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 (destination, redlined)
Authority responsible for creation and management of names of a given name type and/or name; typically an organization or an enterprise system.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
mRIDi{272201FC-E663-4924-98B0-719B7F305C60}show detailsString [0..1]removed from model
Attribute notes (baseline)
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemRID
Scale0
Scopepublic
Staticfalse
TypeString
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
Baselinedid not exist
→
DestinationIdentity → NamingAuthority
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentity
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndNamingAuthority
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineNameType role NameType [0..*] → NamingAuthority role NamingAuthority [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndNameType
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNameType
RoleNoteAll name types managed by this authority.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndNamingAuthority
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleNamingAuthority
RoleNoteAuthority responsible for managing this name type.
Scopepublic
TargetScopeinstance
▶⚙OperatingParticipanti
Class notes
An operator of multiple power system resource objects. Note multiple operating participants may operate the same power system resource object. This can be used for modeling jointly owned units where each owner operates as a contractual share.
Class metadata — changes
BaselineDestination
Stereotype(empty)deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{04AAF1AE-4A67-4130-8259-DEA85BBCD65F}
Class notes
An operator of multiple power system resource objects. Note multiple operating participants may operate the same power system resource object. This can be used for modeling jointly owned units where each owner operates as a contractual share.
▤Metadata
BaselineDestination
Stereotype(empty)deprecated
Class 'OperatingParticipant' has no other changes. The shows its notes and every changed property.
▶⚙OperatingSharei
Class notes
Specifies the operations contract relationship between a power system resource and a contract participant.
Class metadata — changes
BaselineDestination
Stereotype(empty)deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{D615EDD6-6E2D-40b3-8190-3555A34BF9FF}
Class notes
Specifies the operations contract relationship between a power system resource and a contract participant.
▤Metadata
BaselineDestination
Stereotype(empty)deprecated
Class 'OperatingShare' has no other changes. The shows its notes and every changed property.
▶⚙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
Baselinedid not exist
→
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndTransformerEnd
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndPowerSystemResource
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙Terminali
Class notes
An AC electrical connection point to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{1A0F8321-5E77-4d68-BE29-B36FA31549DC}
Class notes
An AC electrical connection point to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes.
⇄Links
BaselineFeeder role NormalHeadFeeder [0..1] → Terminal role NormalHeadTerminal [1..*]
→
DestinationFeeder role NormalHeadFeeder [0..1] → Terminal role NormalHeadTerminal [1..*]
Source end
no changes
Target end — NormalHeadTerminal
BaselineDestination
RoleNoteThe normal head terminal or terminals of the feeder.The normal head terminal (or terminals) of the feeder. The tracing is done towards the conducting equipment associated with the head terminal (or terminals).
BaselineCircuit role Circuit [0..1] → Terminal role EndTerminal [0..*]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
Stereotypeinformative
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndCircuit
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleCircuit
Scopepublic
Stereotypeinformative
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndTerminal
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleEndTerminal
Scopepublic
Stereotypeinformative
TargetScopeinstance
Changed diagrams (6)
▶▦DocCoreMaini
Diagram notes
This diagram shows the main classes needed for any application of the CIM for modelling transmission and generation systems.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 10:44:142025-12-05 12:57:54
CHANGED{F791662C-7488-4578-88E1-21352F9799CF}
Diagram notes
This diagram shows the main classes needed for any application of the CIM for modelling transmission and generation systems.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 10:44:142025-12-05 12:57:54
▦Diagram
changedmoved or resized
Baseline
DocCoreMain (baseline)
Destination
DocCoreMain (destination)
Connectors 1 added · 1 reroutedhover a connector to outline the elements it joins
added(not in this model) – ConnectivityNode
rerouted(not in this model) – (not in this model)
▶▦DocCurveSchedulei
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
DocCurveSchedule (baseline)
Destination
DocCurveSchedule (destination)
▶▦DocFeederContainmenti
Diagram notes
This diagram shows feeder containment.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:44:112025-04-08 00:52:42
CHANGED{154626B0-2984-494a-B7D0-A92371728DC2}
Diagram notes
This diagram shows feeder containment.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:44:112025-04-08 00:52:42
▦Diagram
Baseline
DocFeederContainment (baseline)
Destination
DocFeederContainment (destination)
Connectors 2 rerouted · 5 labels movedhover a connector to outline the elements it joins
reroutedEquipmentContainer – Equipment
reroutedEquipmentContainer – Equipment
labels movedFeeder – Substation
labels movedFeeder – Substation
labels movedFeeder – Substation
labels movedFeeder – Terminal
labels movedTerminal – ConductingEquipment
▶▦DocNamesAndIdentityi
Diagram notes
This diagram shows classes related to identity and classes used to assign names to identified objects.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:43:532026-04-22 09:35:56
CHANGED{E0451A91-94B6-4771-AA2F-2F1E5235FDE5}
Diagram notes
This diagram shows classes related to identity and classes used to assign names to identified objects.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:43:532026-04-22 09:35:56
▦Diagram
addedchangedmoved or resized
Baseline
DocNamesAndIdentity (baseline)
Destination
DocNamesAndIdentity (destination)
Connectors 7 added · 2 removed · 3 reroutedhover a connector to outline the elements it joins
addedIdentity – Name
addedIdentity – NameType
addedIdentity – NameTypeAuthority
addedIdentity – NamingAuthority
addedName – ExtName
addedNameType – ExtNameType
addedNameType – NameTypeAuthority
removedName – IdentifiedObject
removedNameType – NamingAuthority
reroutedIdentifiedObject – Identity
reroutedName – NamingAuthority
reroutedNameType – Name
▶▦DocOperatingSharei
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
DocOperatingShare (baseline)
Destination
DocOperatingShare (destination)
▶▦DocReportingi
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
DocReporting (baseline)
Destination
DocReporting (destination)
▶Domaini
Package notes
The domain package defines primitive datatypes that are used by classes in other packages. Stereotypes are used to describe the datatypes. The following stereotypes are defined: <<enumeration>> A list of permissible constant values. <<Primitive>> The most basic data types used to compose all other data types. <<CIMDatatype>> A datatype that contains a value attribute, an optional unit of measure and a unit multiplier. The unit and multiplier may be specified as a static variable initialized to the allowed value. <<Compound>> A composite of Primitive, enumeration, CIMDatatype or other Compound classes, as long as the Compound classes do not recurse. For all datatypes both positive and negative values are allowed unless stated otherwise for a particular datatype.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{0134E45C-F32A-4522-A725-E07B0AE4CB57}
Package notes
The domain package defines primitive datatypes that are used by classes in other packages. Stereotypes are used to describe the datatypes. The following stereotypes are defined: <<enumeration>> A list of permissible constant values. <<Primitive>> The most basic data types used to compose all other data types. <<CIMDatatype>> A datatype that contains a value attribute, an optional unit of measure and a unit multiplier. The unit and multiplier may be specified as a static variable initialized to the allowed value. <<Compound>> A composite of Primitive, enumeration, CIMDatatype or other Compound classes, as long as the Compound classes do not recurse. For all datatypes both positive and negative values are allowed unless stated otherwise for a particular datatype.
Added classes (34)
▶⚙Binary«ConstrainedPrimitive»i
Class notes
Represents binary data in textual formats that require a consistent encoding mechanism for interoperability across systems. Used in scenarios where non-textual data needs to be represented in structured data formats such as JSON-LD and XML. Example: A binary file converted into a textual format for storage or transmission.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameBinary
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{663538DF-CC64-46e2-B7E4-A3CB34B29C51}
Class notes
Represents binary data in textual formats that require a consistent encoding mechanism for interoperability across systems. Used in scenarios where non-textual data needs to be represented in structured data formats such as JSON-LD and XML. Example: A binary file converted into a textual format for storage or transmission.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameBinary
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Binary' has no other changes. The shows its notes and every changed property.
▶⚙CurrencyExchangeRate«Compound»i
Class notes
Rate that expresses the value of one currency in terms of another currency. E.g. 1.10 USD per EUR.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameCurrencyExchangeRate
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{9B996382-B8DE-4257-9CC2-38B24CA2C397}
Class notes
Rate that expresses the value of one currency in terms of another currency. E.g. 1.10 USD per EUR.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameCurrencyExchangeRate
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
baseCurrencyi{1648BF92-1DBF-4c10-A5ED-98ACCE53F0C1}show detailsdid not existCurrency [0..1]Currency that is being priced or evaluated in an exchange rate.
Attribute notes
Currency that is being priced or evaluated in an exchange rate.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamebaseCurrency
Scale0
Scopepublic
Staticfalse
TypeCurrency
UpperBound1
Tagged values — changes
BaselineDestination
none
quoteCurrencyi{D90F170E-0DEA-48bf-9929-E220A857EDAB}show detailsdid not existCurrency [0..1]Currency used to express the value of the base currency.
Attribute notes
Currency used to express the value of the base currency.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamequoteCurrency
Scale0
Scopepublic
Staticfalse
TypeCurrency
UpperBound1
Tagged values — changes
BaselineDestination
none
valuei{55C20877-168E-46e5-92AF-ABAA49F99CEE}show detailsdid not existDecimal [0..1]Numerical value that expresses the amount of quote currency equivalent to one unit of the base currency.
Attribute notes
Numerical value that expresses the amount of quote currency equivalent to one unit of the base currency.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namevalue
Scale0
Scopepublic
Staticfalse
TypeDecimal
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙DateTZ«ConstrainedPrimitive»i
Class notes
A restriction on Date that explicitly requires a time zone reference to ensure consistency across different regions and avoid ambiguity in global contexts. Without a time zone, a date might refer to different 24-hour periods depending on the location, potentially causing misinterpretation in scheduling, record-keeping, and historical data. Example: 2024-12-25Z (Coordinated Universal Time) or 2024-12-25+02:00 (UTC+2).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDateTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{BFAB7CFA-9A4E-4929-97C1-5EF179393B74}
Class notes
A restriction on Date that explicitly requires a time zone reference to ensure consistency across different regions and avoid ambiguity in global contexts. Without a time zone, a date might refer to different 24-hour periods depending on the location, potentially causing misinterpretation in scheduling, record-keeping, and historical data. Example: 2024-12-25Z (Coordinated Universal Time) or 2024-12-25+02:00 (UTC+2).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDateTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'DateTZ' has no other changes. The shows its notes and every changed property.
▶⚙Day«Primitive»i
Class notes
A datatype representing a specific day of a month. Example: 5th day of the month.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorkdemaree
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDay
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{623E630F-1C4F-43c3-9EC2-89DC17A95223}
Class notes
A datatype representing a specific day of a month. Example: 5th day of the month.
▤Metadata
BaselineDestination
Abstractfalse
Authorkdemaree
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDay
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Class 'Day' has no other changes. The shows its notes and every changed property.
▶⚙DayTZ«ConstrainedPrimitive»i
Class notes
A restriction on Day that explicitly requires a time zone reference to maintain consistency in date-sensitive applications such as legal documentation, historical records, and global event coordination. Example: ---05Z (UTC) or ---05+03:00 (UTC+3).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDayTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{2712C894-B2A7-4c9d-BB80-D626FF2ACB2A}
Class notes
A restriction on Day that explicitly requires a time zone reference to maintain consistency in date-sensitive applications such as legal documentation, historical records, and global event coordination. Example: ---05Z (UTC) or ---05+03:00 (UTC+3).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDayTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'DayTZ' has no other changes. The shows its notes and every changed property.
▶⚙Decimal-totalDigits-fractionDigits«ConstrainedPrimitive»i
Class notes
Represents decimal numbers with a specified total number of digits (totalDigits) and a fixed number of decimal places (fractionDigits). totalDigits defines the maximum number of digits allowed in the number, including both integer and fractional parts. fractionDigits specifies how many of those digits must be after the decimal point. Example: Decimal-18-2: Allows a total of 18 digits, with 2 reserved for fractional values. 1234567890123456.78 (Valid)9999999999999999.99 (Valid, max precision allowed) 100.1 (Valid) 100.123 (Invalid, exceeds two decimal places).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDecimal-totalDigits-fractionDigits
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{E243FD53-1938-4d93-9A87-1074CA1AE5C8}
Class notes
Represents decimal numbers with a specified total number of digits (totalDigits) and a fixed number of decimal places (fractionDigits). totalDigits defines the maximum number of digits allowed in the number, including both integer and fractional parts. fractionDigits specifies how many of those digits must be after the decimal point. Example: Decimal-18-2: Allows a total of 18 digits, with 2 reserved for fractional values. 1234567890123456.78 (Valid)9999999999999999.99 (Valid, max precision allowed) 100.1 (Valid) 100.123 (Invalid, exceeds two decimal places).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDecimal-totalDigits-fractionDigits
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Decimal-totalDigits-fractionDigits' has no other changes. The shows its notes and every changed property.
▶⚙Double«ConstrainedPrimitive»i
Class notes
Represents positive and negative real numbers with double precision, offering greater accuracy compared to Float. Unlike Float, Double supports special symbols such as NaN (Not a Number), positive infinity, and negative infinity, making it suitable for scientific and engineering applications where such values are required. These special values are essential for handling undefined or unrepresentable mathematical results, such as division by zero (1.0 / 0.0 results in positive infinity) or the square root of a negative number (sqrt(-1.0) results in NaN). Example: 3.141592653589793, 1.79E+308 (maximum positive double), NaN (Not a Number).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{86998E16-6758-4a89-AB81-4DE07C331849}
Class notes
Represents positive and negative real numbers with double precision, offering greater accuracy compared to Float. Unlike Float, Double supports special symbols such as NaN (Not a Number), positive infinity, and negative infinity, making it suitable for scientific and engineering applications where such values are required. These special values are essential for handling undefined or unrepresentable mathematical results, such as division by zero (1.0 / 0.0 results in positive infinity) or the square root of a negative number (sqrt(-1.0) results in NaN). Example: 3.141592653589793, 1.79E+308 (maximum positive double), NaN (Not a Number).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Double' has no other changes. The shows its notes and every changed property.
▶⚙Email«ConstrainedPrimitive»i
Class notes
Represents an email address as a textual constraint that includes a domain component. Email follows local-part@domain where the domain is a registered and valid host. Example: user@example.com.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameEmail
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{6D877184-6191-4326-B363-740E2DFFFDFD}
Class notes
Represents an email address as a textual constraint that includes a domain component. Email follows local-part@domain where the domain is a registered and valid host. Example: user@example.com.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameEmail
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Email' has no other changes. The shows its notes and every changed property.
▶⚙FiniteFloat«ConstrainedPrimitive»i
Class notes
Represents positive and negative real numbers with single precision, typically using 32-bit floating-point representation. It is constrained to finite numbers and does not support special symbols like NaN, positive infinity, or negative infinity due to backward compatibility concerns. Example: 3.14, -27.89, 1.2345E2 (scientific notation for 123.45).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameFiniteFloat
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{039CAB38-2A23-4dfa-8AEA-1C1B7B63E9CE}
Class notes
Represents positive and negative real numbers with single precision, typically using 32-bit floating-point representation. It is constrained to finite numbers and does not support special symbols like NaN, positive infinity, or negative infinity due to backward compatibility concerns. Example: 3.14, -27.89, 1.2345E2 (scientific notation for 123.45).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameFiniteFloat
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'FiniteFloat' has no other changes. The shows its notes and every changed property.
▶⚙Integer|min|max«ConstrainedPrimitive»i
Class notes
Represents whole numbers with a defined range, where minimum(min) and maximum (max) values are <b>inclusive</b>. Ensuring a bounded range helps prevent overflow errors, maintains consistency in datasets, and enforces domain-specific constraints. Example: Integer|-50|50 (Minimum -50, Maximum 50).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameInteger|min|max
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{857C77A5-08FB-42e9-976C-C778E9D692B3}
Class notes
Represents whole numbers with a defined range, where minimum(min) and maximum (max) values are <b>inclusive</b>. Ensuring a bounded range helps prevent overflow errors, maintains consistency in datasets, and enforces domain-specific constraints. Example: Integer|-50|50 (Minimum -50, Maximum 50).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameInteger|min|max
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Integer|min|max' has no other changes. The shows its notes and every changed property.
▶⚙IntPhoneNumber«ConstrainedPrimitive»i
Class notes
Represents an international phone number as a textual constraint that includes a country code prefixed by + to ensure global uniqueness. The + symbol is required to indicate an international dialling format. Example: +14155552671 (US number), +477911123456 (Norwegian number).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameIntPhoneNumber
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{7C275401-6913-43fb-9BDB-7A7D404AC0EA}
Class notes
Represents an international phone number as a textual constraint that includes a country code prefixed by + to ensure global uniqueness. The + symbol is required to indicate an international dialling format. Example: +14155552671 (US number), +477911123456 (Norwegian number).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameIntPhoneNumber
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'IntPhoneNumber' has no other changes. The shows its notes and every changed property.
▶⚙LangString-language«ConstrainedPrimitive»i
Class notes
Represents textual values constrained to a single allowed language, ensuring data consistency in multilingual environments. This constraint helps prevent ambiguity by enforcing language-specific content, making data easier to process and interpret across applications including automatic translation. Example: LangString-en-GB (British English only).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameLangString-language
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{F9631631-2CDB-4c49-B54D-9636B7677E25}
Class notes
Represents textual values constrained to a single allowed language, ensuring data consistency in multilingual environments. This constraint helps prevent ambiguity by enforcing language-specific content, making data easier to process and interpret across applications including automatic translation. Example: LangString-en-GB (British English only).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameLangString-language
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'LangString-language' has no other changes. The shows its notes and every changed property.
▶⚙Language«ConstrainedPrimitive»i
Class notes
Represents textual values that identifier a language based on a structured format that includes language codes, optional region codes, and script subtags. This ensures consistency in multilingual data processing, localization, metadata tagging, and content negotiation. Example: Valid examples: "en", "fr", "es-ES", "zh-Hans", "nb-NO". Not valid examples: "english", "Français", "norwegian", "zh-hant-cn" (invalid format).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameLanguage
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{32CBE21C-559C-4994-8797-AD3E7466B1E5}
Class notes
Represents textual values that identifier a language based on a structured format that includes language codes, optional region codes, and script subtags. This ensures consistency in multilingual data processing, localization, metadata tagging, and content negotiation. Example: Valid examples: "en", "fr", "es-ES", "zh-Hans", "nb-NO". Not valid examples: "english", "Français", "norwegian", "zh-hant-cn" (invalid format).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameLanguage
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Language' has no other changes. The shows its notes and every changed property.
▶⚙MonetaryAmount«Compound»i
Class notes
A monetary value expressed as a number in a specified currency.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonetaryAmount
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{092F5359-9D6D-418d-AAFD-3F9C5469A6C2}
Class notes
A monetary value expressed as a number in a specified currency.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonetaryAmount
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
currencyi{E91BD65D-0B62-4c95-A867-6CE55A356C46}show detailsdid not existCurrency [0..1]Currency code for the monetary amount (e.g., "EUR", "USD", "NOK").
Attribute notes
Currency code for the monetary amount (e.g., "EUR", "USD", "NOK").
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namecurrency
Scale0
Scopepublic
Staticfalse
TypeCurrency
UpperBound1
Tagged values — changes
BaselineDestination
none
valuei{BD141BA4-4E2F-4ce0-8BE7-D7C1FEC01232}show detailsdid not existDecimal [0..1]Numeric value of the monetary amount, typically expressed with a fixed precision (e.g., 2 decimals for most currencies).
Attribute notes
Numeric value of the monetary amount, typically expressed with a fixed precision (e.g., 2 decimals for most currencies).
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namevalue
Scale0
Scopepublic
Staticfalse
TypeDecimal
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙MonetaryRate«Compound»i
Class notes
Rate expressing a monetary amount per unit of a measurable quantity, such as energy, mass, or volume. E.g. 60 EUR per MWh.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonetaryRate
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{9BAF3E06-4CE4-4841-967E-733EFD6C988E}
Class notes
Rate expressing a monetary amount per unit of a measurable quantity, such as energy, mass, or volume. E.g. 60 EUR per MWh.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonetaryRate
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeCompound
TypeClass
Version1.0
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
currencyi{216025AF-0B57-47e1-B3F4-28A4FBDDEFD0}show detailsdid not existCurrency [0..1]The currency associated with the value.
Attribute notes
The currency associated with the value.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namecurrency
Scale0
Scopepublic
Staticfalse
TypeCurrency
UpperBound1
Tagged values — changes
BaselineDestination
none
multiplieri{4834B4A1-64C8-42d7-BB39-FCD58DC90B21}show detailsdid not existUnitMultiplier [0..1]This attribute specifies the unit multiplier of the perUnit attribute (UnitSymbol). For example, USD/MWh; where currency is "USD", multiplier is "M" for mega-1000000 and perUnit is "Wh".
Attribute notes
This attribute specifies the unit multiplier of the perUnit attribute (UnitSymbol). For example, USD/MWh; where currency is "USD", multiplier is "M" for mega-1000000 and perUnit is "Wh".
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namemultiplier
Scale0
Scopepublic
Staticfalse
TypeUnitMultiplier
UpperBound1
Tagged values — changes
BaselineDestination
none
perUniti{EE4A6B37-8B19-432c-BCAC-ADF6BC883645}show detailsdid not existUnitSymbol [0..1]This attribute specifies the unit of the per unit rate. For example, USD/MWh; where currency is "USD", multiplier is "M" for mega-1000000 and perUnit is "Wh".
Attribute notes
This attribute specifies the unit of the per unit rate. For example, USD/MWh; where currency is "USD", multiplier is "M" for mega-1000000 and perUnit is "Wh".
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameperUnit
Scale0
Scopepublic
Staticfalse
TypeUnitSymbol
UpperBound1
Tagged values — changes
BaselineDestination
none
valuei{FA7CE7F4-44B0-430c-940C-C78077000DE7}show detailsdid not existDecimal [0..1]The amount of the currency in the monetary rate. For example, 100 USD/MWh, the value is 100.
Attribute notes
The amount of the currency in the monetary rate. For example, 100 USD/MWh, the value is 100.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namevalue
Scale0
Scopepublic
Staticfalse
TypeDecimal
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙Month«Primitive»i
Class notes
A datatype representing a specific month in a year. Example: November.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorselaost1
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonth
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{0C7613D9-FE0D-4234-ABF5-3C5E20D18498}
Class notes
A datatype representing a specific month in a year. Example: November.
▤Metadata
BaselineDestination
Abstractfalse
Authorselaost1
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonth
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Class 'Month' has no other changes. The shows its notes and every changed property.
▶⚙MonthDayTZ«ConstrainedPrimitive»i
Class notes
A restriction on MonthDay that explicitly requires a time zone reference to ensure consistency for recurring events, anniversaries, and time-sensitive records across different locations. Helps prevent misalignment of significant dates when used in international applications. Example: --12-25Z (UTC) or --12-25-04:00 (UTC-4).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonthDayTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{4E5A0B41-4C28-4d16-A467-186212C40C2D}
Class notes
A restriction on MonthDay that explicitly requires a time zone reference to ensure consistency for recurring events, anniversaries, and time-sensitive records across different locations. Helps prevent misalignment of significant dates when used in international applications. Example: --12-25Z (UTC) or --12-25-04:00 (UTC-4).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameMonthDayTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'MonthDayTZ' has no other changes. The shows its notes and every changed property.
▶⚙NegativeDouble«ConstrainedPrimitive»i
Class notes
Represents a double-precision value strictly less than zero. Suitable for contexts like temperature deviation or loss quantities. Example: -0.01, -273.15, -1.2e3.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNegativeDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{A671FD8F-B6E6-4f2a-A393-EE0161B9FDC1}
Class notes
Represents a double-precision value strictly less than zero. Suitable for contexts like temperature deviation or loss quantities. Example: -0.01, -273.15, -1.2e3.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNegativeDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'NegativeDouble' has no other changes. The shows its notes and every changed property.
▶⚙NegativeInteger«Primitive»i
Class notes
A datatype representing whole numbers less than zero. Examples: -3, -2, -1.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNegativeInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Tagged values — changes
BaselineDestination
none
ADDED{B07539DC-C148-49fe-A9E9-2DE6BF4E225D}
Class notes
A datatype representing whole numbers less than zero. Examples: -3, -2, -1.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNegativeInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Class 'NegativeInteger' has no other changes. The shows its notes and every changed property.
▶⚙NonNegativeDouble«ConstrainedPrimitive»i
Class notes
Represents a double-precision value greater than or equal to zero. Used where zero is valid but negative values are not (e.g., energy consumption). Example: 0.0, 12.75, 1.2e3.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonNegativeDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{ABA0690F-9320-4319-BB34-E5FBADFA44D6}
Class notes
Represents a double-precision value greater than or equal to zero. Used where zero is valid but negative values are not (e.g., energy consumption). Example: 0.0, 12.75, 1.2e3.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonNegativeDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'NonNegativeDouble' has no other changes. The shows its notes and every changed property.
▶⚙NonNegativeInteger«Primitive»i
Class notes
A datatype representing whole numbers greater than or equal to zero. Examples: 0, 1, 2.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonNegativeInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Tagged values — changes
BaselineDestination
none
ADDED{29C910A5-70E0-4b52-A6D3-5B182C76660A}
Class notes
A datatype representing whole numbers greater than or equal to zero. Examples: 0, 1, 2.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonNegativeInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Class 'NonNegativeInteger' has no other changes. The shows its notes and every changed property.
▶⚙NonPositiveDouble«ConstrainedPrimitive»i
Class notes
Represents a double-precision value less than or equal to zero. Example: 0.0, -1.0, -100.25.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonPositiveDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{C0ACA74F-7699-4ad8-AA5F-416E73BAEABF}
Class notes
Represents a double-precision value less than or equal to zero. Example: 0.0, -1.0, -100.25.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonPositiveDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'NonPositiveDouble' has no other changes. The shows its notes and every changed property.
▶⚙NonPositiveInteger«Primitive»i
Class notes
A datatype representing whole numbers less than or equal to zero. Examples: -2, -1, 0.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonPositiveInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Tagged values — changes
BaselineDestination
none
ADDED{43A43822-BDF5-4e32-800B-C5F8627E5F8B}
Class notes
A datatype representing whole numbers less than or equal to zero. Examples: -2, -1, 0.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNonPositiveInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Class 'NonPositiveInteger' has no other changes. The shows its notes and every changed property.
▶⚙Normalised«ConstrainedPrimitive»i
Class notes
Represents textual values where leading and trailing whitespace, line breaks, tab characters, and carriage returns are prohibited. This constraint ensures consistency in data processing, avoiding unintended mismatches in validation, duplicate detection. Example: " example ", "example " (leading/trailing spaces), "example\ttext" (tab character), "example\ntext" (line break) are not allowed, but "This is an example." is allowed.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNormalised
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{548A350B-1EC0-4d64-8A67-D7165A2E3A90}
Class notes
Represents textual values where leading and trailing whitespace, line breaks, tab characters, and carriage returns are prohibited. This constraint ensures consistency in data processing, avoiding unintended mismatches in validation, duplicate detection. Example: " example ", "example " (leading/trailing spaces), "example\ttext" (tab character), "example\ntext" (line break) are not allowed, but "This is an example." is allowed.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameNormalised
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Normalised' has no other changes. The shows its notes and every changed property.
▶⚙PositiveDouble«ConstrainedPrimitive»i
Class notes
Represents a double-precision floating-point value strictly greater than zero. Used where only positive real numbers are valid (e.g., distances, rates). Example: 0.0001, 3.14, 1.0e5.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NamePositiveDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{0A53A19F-F74D-4998-94FD-7F557177EC6B}
Class notes
Represents a double-precision floating-point value strictly greater than zero. Used where only positive real numbers are valid (e.g., distances, rates). Example: 0.0001, 3.14, 1.0e5.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NamePositiveDouble
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'PositiveDouble' has no other changes. The shows its notes and every changed property.
▶⚙PositiveInteger«Primitive»i
Class notes
A datatype representing whole numbers greater than zero. Examples: 1, 2, 3.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NamePositiveInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Tagged values — changes
BaselineDestination
none
ADDED{1F93FB25-3F90-4c4a-B587-29B8679536B0}
Class notes
A datatype representing whole numbers greater than zero. Examples: 1, 2, 3.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NamePositiveInteger
ParentPackageDomain
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Class 'PositiveInteger' has no other changes. The shows its notes and every changed property.
▶⚙String-min-max«ConstrainedPrimitive»i
Class notes
Represents textual values with enforced minimum and maximum length constraints to ensure data consistency and prevent unexpected input variations. Useful in scenarios where text fields have expected character limits, such as code list, names, descriptions, or identifiers. Example: String-0-128 (Minimum 0, Maximum 128), String-128-128 (Exactly 128).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameString-min-max
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{A24E41B1-2BE9-424a-9779-F802BA9F0B0E}
Class notes
Represents textual values with enforced minimum and maximum length constraints to ensure data consistency and prevent unexpected input variations. Useful in scenarios where text fields have expected character limits, such as code list, names, descriptions, or identifiers. Example: String-0-128 (Minimum 0, Maximum 128), String-128-128 (Exactly 128).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameString-min-max
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'String-min-max' has no other changes. The shows its notes and every changed property.
▶⚙TimeTZ«ConstrainedPrimitive»i
Class notes
A restriction on Time that explicitly requires a time zone reference to ensure consistency across different regions and avoid ambiguity in global contexts. Without a time zone, a time might refer to different moments depending on the location, leading to potential misinterpretation in scheduling, real-time processing, and event tracking. Example: 14:30:00Z (UTC) or 14:30:00+05:30 (UTC+5:30).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameTimeTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{E8C41DB9-BC6A-4f8a-8C5F-6B72FF562690}
Class notes
A restriction on Time that explicitly requires a time zone reference to ensure consistency across different regions and avoid ambiguity in global contexts. Without a time zone, a time might refer to different moments depending on the location, leading to potential misinterpretation in scheduling, real-time processing, and event tracking. Example: 14:30:00Z (UTC) or 14:30:00+05:30 (UTC+5:30).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameTimeTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'TimeTZ' has no other changes. The shows its notes and every changed property.
▶⚙Token«ConstrainedPrimitive»i
Class notes
Represents textual values where leading and trailing white space, line breaks, tab characters, and carriage returns are prohibited. In addition, it is not allowed to have multiple internal white space characters. Additionally, multiple consecutive internal white space characters are not valid and should be collapsed into a single space. This constraint ensures consistency in data processing, preventing unintended mismatches in validation and duplicate detection. Unlike Normalised, Token is designed to avoid issues when values are embedded in URIs, filenames, or query strings, where multiple spaces could cause encoding or interpretation problems. Example: "This is an example." is allowed for a Normalised string but not allowed for Token. "This is an example." is allowed for both Token and Normalised.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameToken
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{E637B884-22EF-4249-AB2C-DB01AEECFAB6}
Class notes
Represents textual values where leading and trailing white space, line breaks, tab characters, and carriage returns are prohibited. In addition, it is not allowed to have multiple internal white space characters. Additionally, multiple consecutive internal white space characters are not valid and should be collapsed into a single space. This constraint ensures consistency in data processing, preventing unintended mismatches in validation and duplicate detection. Unlike Normalised, Token is designed to avoid issues when values are embedded in URIs, filenames, or query strings, where multiple spaces could cause encoding or interpretation problems. Example: "This is an example." is allowed for a Normalised string but not allowed for Token. "This is an example." is allowed for both Token and Normalised.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameToken
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Token' has no other changes. The shows its notes and every changed property.
▶⚙URN«ConstrainedPrimitive»i
Class notes
Represents a Uniform Resource Name (URN), which is a type of URI that serves as a persistent, location-independent resource identifier, URN follow the pattern: urn:namespace:identifier. Unlike URLs, URNs do not specify a retrieval mechanism but instead uniquely name a resource within a particular namespace. Example: urn:isbn:0451450523.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameURN
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{13FE3506-96F9-4016-9558-466135E7E05D}
Class notes
Represents a Uniform Resource Name (URN), which is a type of URI that serves as a persistent, location-independent resource identifier, URN follow the pattern: urn:namespace:identifier. Unlike URLs, URNs do not specify a retrieval mechanism but instead uniquely name a resource within a particular namespace. Example: urn:isbn:0451450523.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameURN
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'URN' has no other changes. The shows its notes and every changed property.
▶⚙Version«ConstrainedPrimitive»i
Class notes
Represents a version identifier that is a textual constraint following Semantic Versioning (SemVer 2.0.0) principles: MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]. The version consists of a sequence of numbers and optional alphanumeric identifiers that indicate changes in a system, model, or software over time. Example: 1.0.0, 0.9.3-beta.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameVersion
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{74A5770E-FF2A-4cd0-A5F6-7C4EA7AFF01A}
Class notes
Represents a version identifier that is a textual constraint following Semantic Versioning (SemVer 2.0.0) principles: MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]. The version consists of a sequence of numbers and optional alphanumeric identifiers that indicate changes in a system, model, or software over time. Example: 1.0.0, 0.9.3-beta.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameVersion
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'Version' has no other changes. The shows its notes and every changed property.
▶⚙Year«Primitive»i
Class notes
A datatype representing a calendar year. Example: 2025.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorkdemaree
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYear
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{6F171080-CD35-44ec-AECD-A7BC6E8A5835}
Class notes
A datatype representing a calendar year. Example: 2025.
▤Metadata
BaselineDestination
Abstractfalse
Authorkdemaree
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYear
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Class 'Year' has no other changes. The shows its notes and every changed property.
▶⚙YearMonth«Primitive»i
Class notes
A datatype representing a combination of year and month. Example: November 2024.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorselaost1
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYearMonth
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{A9F297DD-200B-435e-913E-21A6C57A443F}
Class notes
A datatype representing a combination of year and month. Example: November 2024.
▤Metadata
BaselineDestination
Abstractfalse
Authorselaost1
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYearMonth
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypePrimitive
TypeClass
Version1.0
Class 'YearMonth' has no other changes. The shows its notes and every changed property.
▶⚙YearTZ«ConstrainedPrimitive»i
Class notes
A restriction on Year that explicitly requires a time zone reference to maintain accuracy in multi-time zone datasets and historical records. Enforcing a time zone allows correct alignment of events and reports across different geographical regions. Example: 2025Z (UTC) or 2025+01:00 (UTC+1).
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYearTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Tagged values — changes
BaselineDestination
none
ADDED{D8967DB4-5566-4cd7-910D-68590300DCE2}
Class notes
A restriction on Year that explicitly requires a time zone reference to maintain accuracy in multi-time zone datasets and historical records. Enforcing a time zone allows correct alignment of events and reports across different geographical regions. Example: 2025Z (UTC) or 2025+01:00 (UTC+1).
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
GenTypeJava
IsLeaffalse
IsRootfalse
IsSpecfalse
NameYearTZ
ParentPackageDomain
Phase1.0
Scopepublic
StatusProposed
StereotypeConstrainedPrimitive
TypeClass
Version1.0
Class 'YearTZ' has no other changes. The shows its notes and every changed property.
Moved classes (3)
▶⚙DateTimeStamp«Primitive»i
Class notes (destination, redlined)
Position of an instant, expressed using xsd:dateTimeStamp, in which the time-zone field is mandatory. A datatype representing a specific moment in time, including date and time components. Unlike DateTime it requires a time zone to be specified, ensuring absolute reference in time-sensitive applications such as logging, distributed systems, and time-series data. Example: 25 of December 2024 at 7 a.m Coordinated Universal Time (UTC).
Class metadata — changes
BaselineDestination
ParentPackageExtHeaderMetadataDomain
StereotypePrimitive, eumdPrimitive
Tagged values — changes
BaselineDestination
no changes
MOVEDfrom ExtHeaderMetadata{7EE9A266-0002-46a7-872C-A98966C79BE8}
Class notes (destination, redlined)
Position of an instant, expressed using xsd:dateTimeStamp, in which the time-zone field is mandatory. A datatype representing a specific moment in time, including date and time components. Unlike DateTime it requires a time zone to be specified, ensuring absolute reference in time-sensitive applications such as logging, distributed systems, and time-series data. Example: 25 of December 2024 at 7 a.m Coordinated Universal Time (UTC).
▤Metadata
BaselineDestination
ParentPackageExtHeaderMetadataDomain
StereotypePrimitive, eumdPrimitive
Class 'DateTimeStamp' has no other changes. The shows its notes and every changed property.
▶⚙IRI«Primitive»i
Class notes
An IRI (Internationalized Resource Identifier) within an RDF graph is a Unicode string that conforms to the syntax defined in RFC 3987. The primitive is serialized as rdf:resource in RDFXML. IRIs in the RDF abstract syntax must be absolute, and may contain a fragment identifier. IRI equality: Two IRIs are equal if and only if they are equivalent under Simple String Comparison according to section 5.1 of [RFC3987]. Further normalization must not be performed when comparing IRIs for equality. IRIs are a generalization of URIs [RFC3986] that permits a wider range of Unicode characters. Every absolute URI and URL is an IRI, but not every IRI is an URI. When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in section 3.1 of [RFC3987]. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names.
Class metadata — changes
BaselineDestination
ParentPackageDetailedModelDescriptionDomain
Tagged values — changes
BaselineDestination
no changes
MOVEDfrom DetailedModelDescription{2914BE52-8A86-4707-A235-5765C6E105FF}
Class notes
An IRI (Internationalized Resource Identifier) within an RDF graph is a Unicode string that conforms to the syntax defined in RFC 3987. The primitive is serialized as rdf:resource in RDFXML. IRIs in the RDF abstract syntax must be absolute, and may contain a fragment identifier. IRI equality: Two IRIs are equal if and only if they are equivalent under Simple String Comparison according to section 5.1 of [RFC3987]. Further normalization must not be performed when comparing IRIs for equality. IRIs are a generalization of URIs [RFC3986] that permits a wider range of Unicode characters. Every absolute URI and URL is an IRI, but not every IRI is an URI. When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in section 3.1 of [RFC3987]. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names.
▤Metadata
BaselineDestination
ParentPackageDetailedModelDescriptionDomain
Class 'IRI' has no other changes. The shows its notes and every changed property.
▶⚙LangString«Primitive»i
Class notes (destination, redlined)
According to RDF 1.1 and RDF 1.2 the rdf:langString returns the given value and language tag. The rdf:langString type extends xs:string, and represents a language tagged string in RDF. A datatype representing a string with an associated language tag.
Class metadata — changes
BaselineDestination
ParentPackageExtHeaderMetadataDomain
StereotypePrimitive, rdfPrimitive
Tagged values — changes
BaselineDestination
no changes
MOVEDfrom ExtHeaderMetadata{84335C9F-E255-4535-9ED9-FEA98F83DBE7}
Class notes (destination, redlined)
According to RDF 1.1 and RDF 1.2 the rdf:langString returns the given value and language tag. The rdf:langString type extends xs:string, and represents a language tagged string in RDF. A datatype representing a string with an associated language tag.
▤Metadata
BaselineDestination
ParentPackageExtHeaderMetadataDomain
StereotypePrimitive, rdfPrimitive
Class 'LangString' has no other changes. The shows its notes and every changed property.
Changed classes (18)
▶⚙Boolean«Primitive»i
Class notes (destination, redlined)
A type with the value space "true" and "false". A logical datatype representing binary values: {true, false}.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{9F8964F1-6C32-465b-A83D-F5A201A291C3}
Class notes (destination, redlined)
A type with the value space "true" and "false". A logical datatype representing binary values: {true, false}.
Class 'Boolean' has no other changes. The shows its notes and every changed property.
▶⚙CostPerEnergyUnit«CIMDatatype»i
Class notes
Cost, in units of currency, per quantity of electrical energy generated.
Class metadata — changes
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{781B4357-DF24-4f4f-BBE3-8C8CE1C0F2E5}
Class notes
Cost, in units of currency, per quantity of electrical energy generated.
▤Metadata
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Class 'CostPerEnergyUnit' has no other changes. The shows its notes and every changed property.
▶⚙CostPerHeatUnit«CIMDatatype»i
Class notes
Cost, in units of currency, per quantity of heat generated.
Class metadata — changes
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{E1913AA6-E24F-4b45-BB9B-946567FC7AF6}
Class notes
Cost, in units of currency, per quantity of heat generated.
▤Metadata
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Class 'CostPerHeatUnit' has no other changes. The shows its notes and every changed property.
▶⚙CostPerVolume«CIMDatatype»i
Class notes
Cost per unit volume.
Class metadata — changes
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{56D3E01F-B21E-4f00-A8F1-CBC80D384B3B}
Class notes
Cost per unit volume.
▤Metadata
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Class 'CostPerVolume' has no other changes. The shows its notes and every changed property.
▶⚙CostRate«CIMDatatype»i
Class notes
Cost, in units of currency, per elapsed time.
Class metadata — changes
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{A8B9F2B7-69E6-4698-8492-D6A8E70D8755}
Class notes
Cost, in units of currency, per elapsed time.
▤Metadata
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Class 'CostRate' has no other changes. The shows its notes and every changed property.
▶⚙Date«Primitive»i
Class notes (destination, redlined)
Date as "yyyy-mm-dd", which conforms with ISO 8601. UTC time zone is specified as "yyyy-mm-ddZ". A local timezone relative UTC is specified as "yyyy-mm-dd(+/-)hh:mm". A datatype representing a calendar date in the Gregorian system. Example: 25 of December 2024.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{C724EF94-9D38-4673-A889-46E7C5C6321C}
Class notes (destination, redlined)
Date as "yyyy-mm-dd", which conforms with ISO 8601. UTC time zone is specified as "yyyy-mm-ddZ". A local timezone relative UTC is specified as "yyyy-mm-dd(+/-)hh:mm". A datatype representing a calendar date in the Gregorian system. Example: 25 of December 2024.
Class 'Date' has no other changes. The shows its notes and every changed property.
▶⚙DateTime«Primitive»i
Class notes (destination, redlined)
Date and time as "yyyy-mm-ddThh:mm:ss.sss", which conforms with ISO 8601. UTC time zone is specified as "yyyy-mm-ddThh:mm:ss.sssZ". A local timezone relative UTC is specified as "yyyy-mm-ddThh:mm:ss.sss-hh:mm". The second component (shown here as "ss.sss") could have any number of digits in its fractional part to allow any kind of precision beyond seconds. A datatype representing a specific moment in time, including date and time components. Example: 25 of December 2024 at 7 a.m.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{EEAE6E83-944C-489c-8E25-CFB85F80C3EB}
Class notes (destination, redlined)
Date and time as "yyyy-mm-ddThh:mm:ss.sss", which conforms with ISO 8601. UTC time zone is specified as "yyyy-mm-ddThh:mm:ss.sssZ". A local timezone relative UTC is specified as "yyyy-mm-ddThh:mm:ss.sss-hh:mm". The second component (shown here as "ss.sss") could have any number of digits in its fractional part to allow any kind of precision beyond seconds. A datatype representing a specific moment in time, including date and time components. Example: 25 of December 2024 at 7 a.m.
Class 'DateTime' has no other changes. The shows its notes and every changed property.
▶⚙Decimal«Primitive»i
Class notes (destination, redlined)
Decimal is the base-10 notational system for representing real numbers. A datatype representing rational numbers using a decimal representation. Unlike Float, which uses binary floating-point representation and can introduce rounding errors, Decimal maintains exact precision and is typically used for financial and scientific calculations requiring high accuracy.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{9CD33DFD-D5FD-46a0-A320-11DFA5341F73}
Class notes (destination, redlined)
Decimal is the base-10 notational system for representing real numbers. A datatype representing rational numbers using a decimal representation. Unlike Float, which uses binary floating-point representation and can introduce rounding errors, Decimal maintains exact precision and is typically used for financial and scientific calculations requiring high accuracy.
Class 'Decimal' has no other changes. The shows its notes and every changed property.
▶⚙Duration«Primitive»i
Class notes (destination, redlined)
Duration as "PnYnMnDTnHnMnS" which conforms to ISO 8601, where nY expresses a number of years, nM a number of months, nD a number of days. The letter T separates the date expression from the time expression and, after it, nH identifies a number of hours, nM a number of minutes and nS a number of seconds. The number of seconds could be expressed as a decimal number, but all other numbers are integers. A datatype representing a time duration using six dimensions: year, month, day, hour, minute, and second. It provides a canonical representation that ensures consistent interpretation across systems. Unlike DateTime, which represents a fixed point in time, Duration expresses a length of time independent of any starting or ending point.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{D19C4E05-3FD5-484f-A4D2-CBD48E5A34D0}
Class notes (destination, redlined)
Duration as "PnYnMnDTnHnMnS" which conforms to ISO 8601, where nY expresses a number of years, nM a number of months, nD a number of days. The letter T separates the date expression from the time expression and, after it, nH identifies a number of hours, nM a number of minutes and nS a number of seconds. The number of seconds could be expressed as a decimal number, but all other numbers are integers. A datatype representing a time duration using six dimensions: year, month, day, hour, minute, and second. It provides a canonical representation that ensures consistent interpretation across systems. Unlike DateTime, which represents a fixed point in time, Duration expresses a length of time independent of any starting or ending point.
Class 'Duration' has no other changes. The shows its notes and every changed property.
▶⚙Float«Primitive»i
Class notes (destination, redlined)
A floating point number. The range is unspecified and not limited. A datatype representing positive and negative real numbers with varying precision, including special values such as NaN, positive infinity, and negative infinity. NaN (Not a Number) is useful for representing undefined or unrepresentable values, such as the result of dividing by zero or taking the square root of a negative number. Floating-point numbers are widely used in scientific computing, engineering simulations, and graphics rendering where approximate calculations are sufficient.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{921A00A7-D33C-43ea-9DE4-70A026CBA70F}
Class notes (destination, redlined)
A floating point number. The range is unspecified and not limited. A datatype representing positive and negative real numbers with varying precision, including special values such as NaN, positive infinity, and negative infinity. NaN (Not a Number) is useful for representing undefined or unrepresentable values, such as the result of dividing by zero or taking the square root of a negative number. Floating-point numbers are widely used in scientific computing, engineering simulations, and graphics rendering where approximate calculations are sufficient.
Class 'Float' has no other changes. The shows its notes and every changed property.
▶⚙Integer«Primitive»i
Class notes (destination, redlined)
An integer number. The range is unspecified and not limited. A datatype representing whole numbers, including zero, positive, and negative values. Examples: -1, 0, 1.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{5F6B613B-C31A-4476-8050-E600FBD5F789}
Class notes (destination, redlined)
An integer number. The range is unspecified and not limited. A datatype representing whole numbers, including zero, positive, and negative values. Examples: -1, 0, 1.
Class 'Integer' has no other changes. The shows its notes and every changed property.
▶⚙Money«CIMDatatype»i
Class notes
Amount of money.
Class metadata — changes
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{5E4B6DE1-9115-4fce-9859-6714580E5C66}
Class notes
Amount of money.
▤Metadata
BaselineDestination
StereotypeCIMDatatypeCIMDatatype, deprecated
Class 'Money' has no other changes. The shows its notes and every changed property.
▶⚙MonthDay«Primitive»i
Class notes (destination, redlined)
MonthDay format as "--mm-dd", which conforms with XSD data type gMonthDay. A datatype representing a specific day and month in the Gregorian calendar. Example: 25 of December.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{06EEB33A-0F70-4c8c-A932-3836A0BF6872}
Class notes (destination, redlined)
MonthDay format as "--mm-dd", which conforms with XSD data type gMonthDay. A datatype representing a specific day and month in the Gregorian calendar. Example: 25 of December.
Class 'MonthDay' has no other changes. The shows its notes and every changed property.
▶⚙String«Primitive»i
Class notes (destination, redlined)
A string consisting of a sequence of characters. The character encoding is UTF-8. The string length is unspecified and unlimited. A datatype representing a sequence of characters.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{E50DF78B-84CE-42e9-A275-A956DEF45490}
Class notes (destination, redlined)
A string consisting of a sequence of characters. The character encoding is UTF-8. The string length is unspecified and unlimited. A datatype representing a sequence of characters.
Class 'String' has no other changes. The shows its notes and every changed property.
▶⚙Time«Primitive»i
Class notes (destination, redlined)
Time as "hh:mm:ss.sss", which conforms with ISO 8601. UTC time zone is specified as "hh:mm:ss.sssZ". A local timezone relative UTC is specified as "hh:mm:ss.sss±hh:mm". The second component (shown here as "ss.sss") could have any number of digits in its fractional part to allow any kind of precision beyond seconds. A datatype representing a specific time of day. Example: 7 a.m.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{09171B95-287D-44b3-8E93-1376FDF0E55A}
Class notes (destination, redlined)
Time as "hh:mm:ss.sss", which conforms with ISO 8601. UTC time zone is specified as "hh:mm:ss.sssZ". A local timezone relative UTC is specified as "hh:mm:ss.sss±hh:mm". The second component (shown here as "ss.sss") could have any number of digits in its fractional part to allow any kind of precision beyond seconds. A datatype representing a specific time of day. Example: 7 a.m.
Class 'Time' has no other changes. The shows its notes and every changed property.
▶⚙UnitSymbol«enumeration»i
Class notes
The derived units defined for usage in the CIM. In some cases, the derived unit is equal to an SI unit. Whenever possible, the standard derived symbol is used instead of the formula for the derived unit. For example, the unit symbol Farad is defined as "F" instead of "CPerV". In cases where a standard symbol does not exist for a derived unit, the formula for the unit is used as the unit symbol. For example, density does not have a standard symbol and so it is represented as "kgPerm^3". With the exception of the "kg", which is an SI unit, the unit symbols do not contain multipliers and therefore represent the base derived unit to which a multiplier can be applied as a whole. Every unit symbol is treated as an unparseable text as if it were a single-letter symbol. The meaning of each unit symbol is defined by the accompanying descriptive text and not by the text contents of the unit symbol. To allow the widest possible range of serializations without requiring special character handling, several substitutions are made which deviate from the format described in IEC 80000-1. The division symbol "/" is replaced by the letters "Per". Exponents are written in plain text after the unit as "m^3". The letters "deg" are used instead of the degree symbol. Any clarification of the meaning for a substitution is included in the description for the unit symbol. Non-SI units are included in list of unit symbols to allow sources of data to be correctly labelled with their non-SI units (for example, a GPS sensor that is reporting numbers that represent feet instead of meters). This allows software to use the unit symbol information correctly convert and scale the raw data of those sources into SI-based units. The integer values are used for harmonization with IEC 61850.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{80012160-A038-43b5-BA6F-9862E525518C}
Class notes
The derived units defined for usage in the CIM. In some cases, the derived unit is equal to an SI unit. Whenever possible, the standard derived symbol is used instead of the formula for the derived unit. For example, the unit symbol Farad is defined as "F" instead of "CPerV". In cases where a standard symbol does not exist for a derived unit, the formula for the unit is used as the unit symbol. For example, density does not have a standard symbol and so it is represented as "kgPerm^3". With the exception of the "kg", which is an SI unit, the unit symbols do not contain multipliers and therefore represent the base derived unit to which a multiplier can be applied as a whole. Every unit symbol is treated as an unparseable text as if it were a single-letter symbol. The meaning of each unit symbol is defined by the accompanying descriptive text and not by the text contents of the unit symbol. To allow the widest possible range of serializations without requiring special character handling, several substitutions are made which deviate from the format described in IEC 80000-1. The division symbol "/" is replaced by the letters "Per". Exponents are written in plain text after the unit as "m^3". The letters "deg" are used instead of the degree symbol. Any clarification of the meaning for a substitution is included in the description for the unit symbol. Non-SI units are included in list of unit symbols to allow sources of data to be correctly labelled with their non-SI units (for example, a GPS sensor that is reporting numbers that represent feet instead of meters). This allows software to use the unit symbol information correctly convert and scale the raw data of those sources into SI-based units. The integer values are used for harmonization with IEC 61850.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
VAi{D3EB929D-C57F-40a8-86DC-2F5CAACB6A71}show details [1..1] [1..1]Apparent power in volt amperes. See also active (real) power unit W and reactive power unit var.
Attribute notes (destination, redlined)
Apparent power in volt amperes. See also active (real) power unit W and reactive power unit var.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
VAri{F38DF57D-7E97-4af9-984E-40820470C5EC}show details [1..1] [1..1]Reactive power in volt amperes reactive. The "reactive" or "imaginary" component of electrical power (V*I*sin(phi)). (See also active (real power and apparent power). Note: Different meter designs use different methods to arrive at their results. Some meters may compute reactive power asunit anW arithmetic value, while others compute the value vectorially. The data consumer should determine the method in use and theapparent suitabilitypower ofunit the measurement for the intended purposeVA.
Attribute notes (destination, redlined)
Reactive power in volt amperes reactive. The "reactive" or "imaginary" component of electrical power (V*I*sin(phi)). (See also active (real power and apparent power). Note: Different meter designs use different methods to arrive at their results. Some meters may compute reactive power asunit anW arithmetic value, while others compute the value vectorially. The data consumer should determine the method in use and theapparent suitabilitypower ofunit the measurement for the intended purposeVA.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
VPerVAri{F205CACD-712B-46f0-B7D7-170EEF3B59A3}show details [1..1] [1..1]Power factor, PF, the ratio of the active power to the apparent power. Note: The sign convention used for power factor will differ between IEC meters and EEI (ANSI) meters. It is assumed that the data consumers understand the type of meter being used and agree on the sign convention in use at any given utility. Volt per volt-ampere-reactive (var). Units for voltage regulation slope of static VAR compensators.
Attribute notes (destination, redlined)
Power factor, PF, the ratio of the active power to the apparent power. Note: The sign convention used for power factor will differ between IEC meters and EEI (ANSI) meters. It is assumed that the data consumers understand the type of meter being used and agree on the sign convention in use at any given utility. Volt per volt-ampere-reactive (var). Units for voltage regulation slope of static VAR compensators.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Wi{41B0F1BC-E69B-4ca1-A565-ECBC27B49095}show details [1..1] [1..1]RealActive power in watts (J/s). Also known as Real power. Electrical power may have realactive and reactive components. The realactive portioncomponent of electrical power (I^2*R or V*I*cos(phi)), is expressed in Watts. See also apparent power and reactive power.
Attribute notes (destination, redlined)
RealActive power in watts (J/s). Also known as Real power. Electrical power may have realactive and reactive components. The realactive portioncomponent of electrical power (I^2*R or V*I*cos(phi)), is expressed in Watts. See also apparent power and reactive power.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
WPerVAirenamed from VPerVA{F5914562-B809-455b-98A8-CECAA59EE125}show details [1..1] [1..1]Power factor, PF, the ratio of the active power to the apparent power. Note: The sign convention used for power factor will differ between IEC meters and EEI (ANSI) meters. It is assumed that the data consumers understand the type of meter being used and agree on the sign convention in use at any given utility. Power factor, PF, the ratio of the active power to the apparent power.
Attribute notes (destination, redlined)
Power factor, PF, the ratio of the active power to the apparent power. Note: The sign convention used for power factor will differ between IEC meters and EEI (ANSI) meters. It is assumed that the data consumers understand the type of meter being used and agree on the sign convention in use at any given utility. Power factor, PF, the ratio of the active power to the apparent power.
Attribute metadata — changes
BaselineDestination
NameVPerVAWPerVA
Tagged values — changes
BaselineDestination
no changes
Whi{D0065D4C-31BE-42b1-9588-806157D3000D}show details [1..1] [1..1]Real energy in watt hours. Active energy in watt hours. Also known as Real energy. Integral of active power.
Attribute notes (destination, redlined)
Real energy in watt hours. Active energy in watt hours. Also known as Real energy. Integral of active power.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
cosPhii{3FF3E24E-53F5-45ae-8408-47C453D360C2}show details [1..1] [1..1]Power factor, dimensionless. Note 1: This definition of power factor is only holdsvalid when voltage and current forhave balancedno systemsharmonics. See the alternative definition under code 153. Note 2  : Beware of differing sign conventions in use between the IEC and EEI. It is assumed that the data consumer understands the type of meter in use and the sign convention in use by the utility.
Attribute notes (destination, redlined)
Power factor, dimensionless. Note 1: This definition of power factor is only holdsvalid when voltage and current forhave balancedno systemsharmonics. See the alternative definition under code 153. Note 2  : Beware of differing sign conventions in use between the IEC and EEI. It is assumed that the data consumer understands the type of meter in use and the sign convention in use by the utility.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
mimetadata changed - hovermetadata changed{5D4DDF01-7840-42a2-9106-C5CA5D41D1F2}show details [1..1] [1..1]Length in metres.
Attribute notes
Length in metres.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
61850-skos(no tag)exactMatch
qudt-skos(no tag)exactMatch
qudt(no tag)meter
61850(no tag)2
▶⚙URI«Primitive»i
Class notes (destination, redlined)
Uniform Resource Identifier Reference (URI). The value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be a URI Reference). This type should be used to specify the intention that the value fulfills the role of a URI as defined by [RFC 2396], as amended by [RFC 2732]. A datatype representing a Uniform Resource Identifier (URI) or URI Reference, which may be absolute or relative and may contain a fragment identifier.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{A6B135DC-C04F-421d-AD13-64CB535E8F6F}
Class notes (destination, redlined)
Uniform Resource Identifier Reference (URI). The value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be a URI Reference). This type should be used to specify the intention that the value fulfills the role of a URI as defined by [RFC 2396], as amended by [RFC 2732]. A datatype representing a Uniform Resource Identifier (URI) or URI Reference, which may be absolute or relative and may contain a fragment identifier.
Class 'URI' has no other changes. The shows its notes and every changed property.
▶⚙UUID«ConstrainedPrimitive»i
Class notes (destination, redlined)
A UUID as defined by IEC/ISO 9348-8. Represents a Universally Unique Identifier (UUID) as a textual constraint. Follows the pattern: 8-4-4-4-12. Capital letters are accepted, but lowercase should be used. Example: 550e8400-e29b-41d4-a716-446655440000.
Class metadata — changes
BaselineDestination
StereotypePrimitiveConstrainedPrimitive
Tagged values — changes
BaselineDestination
no changes
CHANGED{0CD5C8BB-2BBD-4fe2-A369-68CE8CF2CE5F}
Class notes (destination, redlined)
A UUID as defined by IEC/ISO 9348-8. Represents a Universally Unique Identifier (UUID) as a textual constraint. Follows the pattern: 8-4-4-4-12. Capital letters are accepted, but lowercase should be used. Example: 550e8400-e29b-41d4-a716-446655440000.
▤Metadata
BaselineDestination
StereotypePrimitiveConstrainedPrimitive
Class 'UUID' has no other changes. The shows its notes and every changed property.
Changed diagrams (4)
▶▦DocBasicDatatypesi
Diagram notes
This diagram shows basic datatypes that are the basis for all other datatypes.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{DB3006EC-40EF-48f9-AE0B-54A4590505A4}
Diagram notes
This diagram shows basic datatypes that are the basis for all other datatypes.
▦Diagram
changed
Baseline
DocBasicDatatypes (baseline)
Destination
DocBasicDatatypes (destination)
▶▦DocEnumeratedUnitDatatypesi
Diagram notes
This diagram shows enumerated data types related to the SI unit system.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{6FF3E444-BAE2-4338-BD38-5A4CBCC6F7AB}
Diagram notes
This diagram shows enumerated data types related to the SI unit system.
▦Diagram
changed
Baseline
DocEnumeratedUnitDatatypes (baseline)
Destination
DocEnumeratedUnitDatatypes (destination)
▶▦DocGeneralDatatypesi
Diagram notes
This diagram shows general data types.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{9478D0BE-F328-4c54-BE7D-DE95D8744E6B}
Diagram notes
This diagram shows general data types.
▦Diagram
changed
Baseline
DocGeneralDatatypes (baseline)
Destination
DocGeneralDatatypes (destination)
▶▦DocMonetaryDatatypesi
Diagram notes
This diagram shows monetary related data types.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{B1E74B17-8731-44a6-8CBA-D14D923EFC11}
Diagram notes
This diagram shows monetary related data types.
▦Diagram
changed
Baseline
DocMonetaryDatatypes (baseline)
Destination
DocMonetaryDatatypes (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.
Added classes (1)
▶⚙AsynchronousMachineOperatingMode«enumeration»i
Class notes
Asynchronous machine operating mode.
Class metadata — changes
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameAsynchronousMachineOperatingMode
ParentPackageWires
Scopepublic
StatusProposed
Stereotypeenumeration
TypeClass
Tagged values — changes
BaselineDestination
none
ADDED{62D923E1-828D-4383-8E0B-07C7F4D7613D}
Class notes
Asynchronous machine operating mode.
▤Metadata
BaselineDestination
Abstractfalse
Authorchiva
Complexity1
IsLeaffalse
IsRootfalse
IsSpecfalse
NameAsynchronousMachineOperatingMode
ParentPackageWires
Scopepublic
StatusProposed
Stereotypeenumeration
TypeClass
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
generatori{BCA4EDFB-5DB0-48e7-BB33-F65DA1C36ED0}show detailsdid not exist [1..1]Operating as generator.
Attribute notes
Operating as generator.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound1
Namegenerator
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
motori{8A145E83-4847-4450-8AF0-FD8036741BB6}show detailsdid not exist [1..1]Operating as motor.
Attribute notes
Operating as motor.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound1
Namemotor
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
Changed classes (10)
▶⚙AsynchronousMachinei
Class notes
A rotating machine whose shaft rotates asynchronously with the electrical field. Also known as an induction machine with no external connection to the rotor windings, e.g. squirrel-cage induction machine.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{EC5FCEFF-1274-4771-9D92-C0FF7A100AB8}
Class notes
A rotating machine whose shaft rotates asynchronously with the electrical field. Also known as an induction machine with no external connection to the rotor windings, e.g. squirrel-cage induction machine.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
operatingModei{84208052-94BB-4425-BE3C-F8CA9E2681CE}show detailsdid not existAsynchronousMachineOperatingMode [0..1]Current mode of operation.
Attribute notes
Current mode of operation.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameoperatingMode
Scale0
Scopepublic
Staticfalse
TypeAsynchronousMachineOperatingMode
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙BusSegmenti
Class notes
A two terminal and power conducting device of negligible impedance and length represented as zero impedance device that can be used to represent the conductor between connection points to substation conducting equipment on a substation bus.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{6298C3DC-580A-436c-96DA-018A10359AE7}
Class notes
A two terminal and power conducting device of negligible impedance and length represented as zero impedance device that can be used to represent the conductor between connection points to substation conducting equipment on a substation bus.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
normalRetainedirenamed from retained{0883C557-12C4-40e0-930E-C8B4A90B3051}show detailsBoolean [0..1]Boolean [0..1]Bus segment is normally retained in the topological solution. The flow through retained bus sections will normally be calculated in power flow.
Attribute notes (destination, redlined)
Bus segment is normally retained in the topological solution. The flow through retained bus sections will normally be calculated in power flow.
Attribute metadata — changes
BaselineDestination
NameretainednormalRetained
Tagged values — changes
BaselineDestination
no changes
retainedi{19D86E64-54F6-4ca6-9F37-FC29E7E365BF}show detailsdid not existBoolean [0..1]Bus segment is retained in the topological solution. The flow through retained bus sections will normally be calculated in power flow.
Attribute notes
Bus segment is retained in the topological solution. The flow through retained bus sections will normally be calculated in power flow.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsLiteralfalse
IsOrderedfalse
LowerBound0
Nameretained
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙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.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
maxEconomicPi{F0ABA24B-B894-4791-B2FA-B40282245984}show detailsdid not existActivePower [0..1]Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute notes
Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamemaxEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
minEconomicPi{AFD4727A-2DF0-4a69-941C-16BF0E17BACA}show detailsdid not existActivePower [0..1]Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute notes
Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameminEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalParticipationFactori{674DD3F3-EA60-46ce-AE5B-54098EDD6A95}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamenormalParticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
participationFactori{33A034D4-1A38-4194-9474-32C81C1153D4}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameparticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
BaselineEnergyConsumer → ExtEnergyConsumer
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndEnergyConsumer
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndExtEnergyConsumer
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙ImpedanceTapChangerTablePointi
Class notes
Describes each tap step in the impedance tap changer tabular curve.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{CCFFDF9E-EDBF-4340-8452-58D69D2621EF}
Class notes
Describes each tap step in the impedance tap changer tabular curve.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
ratioi{0889E8C9-58CD-470f-8209-F1FBEDBE7EBB}show detailsFloat [0..1]Float [0..1]The voltage at the tap step divided by rated voltage of the transformer end having the tap changer. Hence this is a value close to one. For example, if the ratio at step 1 is 1.01, and the rated voltage of the transformer end is 110kV, then the voltage obtained by setting the tap changer to step 1 to is 111.1kV. The attribute shall be a positive value.
Attribute notes (destination, redlined)
The voltage at the tap step divided by rated voltage of the transformer end having the tap changer. Hence this is a value close to one. For example, if the ratio at step 1 is 1.01, and the rated voltage of the transformer end is 110kV, then the voltage obtained by setting the tap changer to step 1 to is 111.1kV. The attribute shall be a positive value.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
▶⚙Linei
Class notes
Contains equipment beyond a substation belonging to a power transmission line.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{43D9D2B8-DA1E-45c4-B99D-EC28FCAB742B}
Class notes
Contains equipment beyond a substation belonging to a power transmission line.
⇄Links
BaselineCircuit → Line
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndCircuit
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndLine
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙PhaseImpedanceDatai
Class notes (destination, redlined)
Per length phase impedance matrix entry describes impedance and conductance matrix element values forwith either a (row, column) or a specific(fromPhase, toPhase) pair. If using a (row, and column) ofpair the matrix. The phases to which each entry applies can be determined by means of the row and column attributes which bindrefer to a sequence number provided in either ACLineSegmentPhase or WirePosition (whichwhere phase is bound to alsothe specifysequence phasenumber). If using a (fromPhase, toPhase) pair, neither ACLineSegmentPhase nor WirePosition are required to support the interpretation of the phase impedance matrix. Due to physical symmetry that is reflected in the matrix, only the lower triangle of the matrix is populated with both methods. In the (row, andcolumn) columnapproach, method.this Thatmeans is,that the column attribute is always less than or equal to the row attribute.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{8D8D03C8-6278-4397-9EFA-EDC98D359BBC}
Class notes (destination, redlined)
Per length phase impedance matrix entry describes impedance and conductance matrix element values forwith either a (row, column) or a specific(fromPhase, toPhase) pair. If using a (row, and column) ofpair the matrix. The phases to which each entry applies can be determined by means of the row and column attributes which bindrefer to a sequence number provided in either ACLineSegmentPhase or WirePosition (whichwhere phase is bound to alsothe specifysequence phasenumber). If using a (fromPhase, toPhase) pair, neither ACLineSegmentPhase nor WirePosition are required to support the interpretation of the phase impedance matrix. Due to physical symmetry that is reflected in the matrix, only the lower triangle of the matrix is populated with both methods. In the (row, andcolumn) columnapproach, method.this Thatmeans is,that the column attribute is always less than or equal to the row attribute.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
fromPhasei{646B3E5A-C5E4-45c7-A651-19A709CD164E}show detailsSinglePhaseKind [0..1]SinglePhaseKind [0..1]Refer to the class description. The matrix entry's 'from' phase. Must be used in conjunction with .toPhase to describe to which phase (for diagonal entries) or phases (for off-diagonal entries) this entry refers.
Attribute notes (destination, redlined)
Refer to the class description. The matrix entry's 'from' phase. Must be used in conjunction with .toPhase to describe to which phase (for diagonal entries) or phases (for off-diagonal entries) this entry refers.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
toPhasei{D2DEE1A9-B280-4f3e-95A7-B5DA24493D9E}show detailsSinglePhaseKind [0..1]SinglePhaseKind [0..1]Refer to the class description. The matrix entry's 'to' phase. Must be used in conjunction with .toPhase to describe to which phases (for diagonal entries) or phases (for off-diagonal entries) this entry refers.
Attribute notes (destination, redlined)
Refer to the class description. The matrix entry's 'to' phase. Must be used in conjunction with .toPhase to describe to which phases (for diagonal entries) or phases (for off-diagonal entries) this entry refers.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
▶⚙RatioTapChangeri
Class notes
A tap changer that changes the voltage ratio impacting the voltage magnitude but not the phase angle across the transformer. Angle sign convention (general): Positive value indicates a positive phase shift from the winding where the tap is located to the other winding (for a two-winding transformer).
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{09909286-00A6-451c-B420-2E52ABEB2667}
Class notes
A tap changer that changes the voltage ratio impacting the voltage magnitude but not the phase angle across the transformer. Angle sign convention (general): Positive value indicates a positive phase shift from the winding where the tap is located to the other winding (for a two-winding transformer).
⇄Links
BaselineTransformerEnd role TransformerEnd [0..1] → RatioTapChanger role AdditionalRatioTapChanger [0..1]
→
DestinationTransformerEnd role TransformerEndTransformerEndOfAdditionalRatioTapChanger [0..1] → RatioTapChanger role AdditionalRatioTapChanger [0..1]
Source end — TransformerEndOfAdditionalRatioTapChanger
BaselineDestination
RoleTransformerEndTransformerEndOfAdditionalRatioTapChanger
Target end
no changes
▶⚙Switchi
Class notes
A generic device designed to close, or open, or both, one or more electric circuits. All switches are two terminal devices including grounding switches. The ACDCTerminal.connected at the two sides of the switch shall not be considered for assessing switch connectivity, i.e. only Switch.open, .normalOpen and .locked are relevant.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{ACE2DDBB-536E-489a-A3A8-22589256302D}
Class notes
A generic device designed to close, or open, or both, one or more electric circuits. All switches are two terminal devices including grounding switches. The ACDCTerminal.connected at the two sides of the switch shall not be considered for assessing switch connectivity, i.e. only Switch.open, .normalOpen and .locked are relevant.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
normalRetainedirenamed from retained{5E9C873C-F052-49f6-9247-D7274CDA570A}show detailsBoolean [0..1]Boolean [0..1]BranchSwitch is normally retained in the topological solution. The flow through retained switches will normally be calculated in power flow.
Attribute notes (destination, redlined)
BranchSwitch is normally retained in the topological solution. The flow through retained switches will normally be calculated in power flow.
Attribute metadata — changes
BaselineDestination
NameretainednormalRetained
Tagged values — changes
BaselineDestination
no changes
retainedi{9D667DF8-D78A-44ac-A2E4-319B9B2E1E20}show detailsdid not existBoolean [0..1]Switch is retained in the topological solution. The flow through retained switches will normally be calculated in power flow.
Attribute notes
Switch is retained in the topological solution. The flow through retained switches will normally be calculated in power flow.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsLiteralfalse
IsOrderedfalse
LowerBound0
Nameretained
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙TapChangerTablePointi
Class notes
Describes each tap step in the tabular curve. Note that the upper boundary is not constrained to 100 percent.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{199B695F-644C-4cbf-AB67-76AB51EE5078}
Class notes
Describes each tap step in the tabular curve. Note that the upper boundary is not constrained to 100 percent.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
ratioi{4357132D-9216-46a0-A5B0-6C3F0DCC7876}show detailsFloat [0..1]Float [0..1]The voltage at the tap step divided by rated voltage of the transformer end having the tap changer. Hence this is a value close to one. For example, if the ratio at step 1 is 1.01, and the rated voltage of the transformer end is 110kV, then the voltage obtained by setting the tap changer to step 1 to is 111.1kV. The attribute shall be a positive value.
Attribute notes (destination, redlined)
The voltage at the tap step divided by rated voltage of the transformer end having the tap changer. Hence this is a value close to one. For example, if the ratio at step 1 is 1.01, and the rated voltage of the transformer end is 110kV, then the voltage obtained by setting the tap changer to step 1 to is 111.1kV. The attribute shall be a positive value.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
▶⚙TransformerEndi
Class notes
A conducting connection point of a power transformer. It corresponds to a physical transformer winding terminal. In earlier CIM versions, the TransformerWinding class served a similar purpose, but this class is more flexible because it associates to terminal but is not a specialization of ConductingEquipment.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{6E6AF445-8CD5-434b-8E74-08970A4E6D95}
Class notes
A conducting connection point of a power transformer. It corresponds to a physical transformer winding terminal. In earlier CIM versions, the TransformerWinding class served a similar purpose, but this class is more flexible because it associates to terminal but is not a specialization of ConductingEquipment.
⇄Links
Baselinedid not exist
→
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndTransformerEnd
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndPowerSystemResource
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndTransformerEnd
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndIdentifiedObject
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
BaselineTransformerEnd role TransformerEnd [0..1] → RatioTapChanger role AdditionalRatioTapChanger [0..1]
→
DestinationTransformerEnd role TransformerEndTransformerEndOfAdditionalRatioTapChanger [0..1] → RatioTapChanger role AdditionalRatioTapChanger [0..1]
Source end — TransformerEndOfAdditionalRatioTapChanger
BaselineDestination
RoleTransformerEndTransformerEndOfAdditionalRatioTapChanger
Target end
no changes
Changed diagrams (16)
▶▦DocCutsAndJumpersi
Diagram notes
The diagram show the cuts and jumpers data model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{56C8D23C-C73A-4bea-870E-5C920A3F1066}
Diagram notes
The diagram show the cuts and jumpers data model.
▦Diagram
changed
Baseline
DocCutsAndJumpers (baseline)
Destination
DocCutsAndJumpers (destination)
▶▦DocDatatypesi
Diagram notes
This diagram shows the data types specific to the Wires package.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{7F25DAE7-CB22-4224-AFEB-7F0BD8317D69}
Diagram notes
This diagram shows the data types specific to the Wires package.
▦Diagram
removed
Baseline
DocDatatypes (baseline)
Destination
DocDatatypes (destination)
▶▦DocEarthFaultCompensatori
Diagram notes
Shows earth fault compensating devices.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{F1B3790B-5C3D-4307-8195-39D740D2D197}
Diagram notes
Shows earth fault compensating devices.
▦Diagram
changed
Baseline
DocEarthFaultCompensator (baseline)
Destination
DocEarthFaultCompensator (destination)
▶▦DocInheritanceHierarchyi
Diagram notes
This diagram describes inheritance between classes in and related to the Wires package.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:45:362025-09-28 18:55:37
CHANGED{D2B8C355-D454-4084-9966-12E8D7FF6875}
Diagram notes
This diagram describes inheritance between classes in and related to the Wires package.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:45:362025-09-28 18:55:37
▦Diagram
changedmoved or resized
Baseline
DocInheritanceHierarchy (baseline)
Destination
DocInheritanceHierarchy (destination)
Connectors 1 removed · 1 labels movedhover a connector to outline the elements it joins
removed(not in this model) – (not in this model)
labels moved(not in this model) – (not in this model)
▶▦DocLineModeli
Diagram notes
This diagram shows all classes related to the transmission line model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:45:412025-04-07 01:43:08
CHANGED{1BE27117-9963-472a-99ED-71A231B36808}
Diagram notes
This diagram shows all classes related to the transmission line model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:45:412025-04-07 01:43:08
▦Diagram
changed
Baseline
DocLineModel (baseline)
Destination
DocLineModel (destination)
▶▦DocMutualCouplingi
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
DocMutualCoupling (baseline)
Destination
DocMutualCoupling (destination)
▶▦DocNamingHierarchyPart1i
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
DocNamingHierarchyPart1 (baseline)
Destination
DocNamingHierarchyPart1 (destination)
▶▦DocNamingHierarchyPart2i
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
DocNamingHierarchyPart2 (baseline)
Destination
DocNamingHierarchyPart2 (destination)
Connectors 1 removedhover a connector to outline the elements it joins
removed(not in this model) – (not in this model)
▶▦DocRegulatingEquipmenti
Diagram notes
The diagram shows all classes related to equipment regulation and reactive power compensation.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{F857266A-1599-4d8c-8AC8-29B416B63FA2}
Diagram notes
The diagram shows all classes related to equipment regulation and reactive power compensation.
▦Diagram
changed
Baseline
DocRegulatingEquipment (baseline)
Destination
DocRegulatingEquipment (destination)
Connectors 1 removedhover a connector to outline the elements it joins
removed(not in this model) – RegulatingCondEq
▶▦DocSchedulesi
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
DocSchedules (baseline)
Destination
DocSchedules (destination)
▶▦DocSwitchingEquipmenti
Diagram notes
Shows switching equipment inheritance structure.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{252E3FAB-DD51-437d-886F-5F699257FD4C}
Diagram notes
Shows switching equipment inheritance structure.
▦Diagram
changed
Baseline
DocSwitchingEquipment (baseline)
Destination
DocSwitchingEquipment (destination)
▶▦DocTapChangeri
Diagram notes
This diagram shows all classes related to the transformer tap model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:46:112026-02-03 20:52:28
CHANGED{E6AB0688-D20A-4495-802A-28F4BC2E446D}
Diagram notes
This diagram shows all classes related to the transformer tap model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:46:112026-02-03 20:52:28
▦Diagram
changed
Baseline
DocTapChanger (baseline)
Destination
DocTapChanger (destination)
Connectors 1 added · 1 reroutedhover a connector to outline the elements it joins
addedTransformerEnd – RatioTapChanger
reroutedTransformerEnd – RatioTapChanger
▶▦DocTapChangerTabulari
Diagram notes
This diagram shows all classes related to the transformer tap changer tabular model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:46:152026-02-03 20:52:28
CHANGED{E070BC38-F64B-4133-8B83-B9AF4E60D81E}
Diagram notes
This diagram shows all classes related to the transformer tap changer tabular model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:46:152026-02-03 20:52:28
▦Diagram
changed
Baseline
DocTapChangerTabular (baseline)
Destination
DocTapChangerTabular (destination)
Connectors 1 labels movedhover a connector to outline the elements it joins
labels movedTransformerEnd – RatioTapChanger
▶▦DocTransformeri
Diagram notes
This diagram shows classes related to the core transformer model, but does not show the tap changer details.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{FA8E6B7F-EAD2-40df-956C-D26D5A54BFC7}
Diagram notes
This diagram shows classes related to the core transformer model, but does not show the tap changer details.
▦Diagram
changed
Baseline
DocTransformer (baseline)
Destination
DocTransformer (destination)
▶▦DocVoltageControli
Diagram notes
This diagram shows all classes related to area voltage control.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{6F7167AF-C91B-4203-9D17-9A5924B5ADB7}
Diagram notes
This diagram shows all classes related to area voltage control.
▦Diagram
changed
Baseline
DocVoltageControl (baseline)
Destination
DocVoltageControl (destination)
▶▦DocWiresPhaseModeli
Diagram notes
Show the phase connection detail when modelling devices down to the phase components within a conducting equipment.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{5957C2C3-427B-4740-952A-594EF9E660D0}
Diagram notes
Show the phase connection detail when modelling devices down to the phase components within a conducting equipment.
▦Diagram
changed
Baseline
DocWiresPhaseModel (baseline)
Destination
DocWiresPhaseModel (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 15 classes it contains.
Changed diagrams (1)
▶▦DocLoadi
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
DocLoad (baseline)
Destination
DocLoad (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.
▶GenerationTrainingSimulationi
Package notes
The GenerationTrainingSimululation package contains prime movers, such as turbines and boilers, which are needed for simulation and educational purposes.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{D3C36399-A1D6-4491-A975-06B94A5A1258}
Package notes
The GenerationTrainingSimululation package contains prime movers, such as turbines and boilers, which are needed for simulation and educational purposes.
Package 'GenerationTrainingSimulation' has no changes to the 15 classes it contains.
Changed diagrams (1)
▶▦DocTrainingSimulationi
Diagram notes
This diagram shows all classes included in the GenerationDynamics package as well as the key external classes that have associations with these classes.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3EEDCDC2-25C8-4c66-BC1B-A70CE13B5D22}
Diagram notes
This diagram shows all classes included in the GenerationDynamics package as well as the key external classes that have associations with these classes.
▦Diagram
changed
Baseline
DocTrainingSimulation (baseline)
Destination
DocTrainingSimulation (destination)
▶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.
Changed classes (3)
▶⚙GeneratingUniti
Class notes
A single or set of synchronous machines for converting mechanical power into alternating-current power. For example, individual machines within a set may be defined for scheduling purposes while a single control signal is derived for the set. In this case there would be a GeneratingUnit for each member of the set and an additional GeneratingUnit corresponding to the set.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{A4C4D1F8-0359-44b1-8F2A-521D3F9F3C28}
Class notes
A single or set of synchronous machines for converting mechanical power into alternating-current power. For example, individual machines within a set may be defined for scheduling purposes while a single control signal is derived for the set. In this case there would be a GeneratingUnit for each member of the set and an additional GeneratingUnit corresponding to the set.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
coolDownTimei{99D63C32-B24D-4b3e-9C20-DC179B2F4F34}show detailsdid not existDuration [0..1]Time it takes from a unit shutdown until it is considered cold.
Attribute notes
Time it takes from a unit shutdown until it is considered cold.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamecoolDownTime
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeDuration
UpperBound1
Tagged values — changes
BaselineDestination
none
maxEconomicPi{4CF1283B-D69A-4545-91A9-BC27B2D17846}show detailsdid not existActivePower [0..1]Maximum high economic active power limit, that should not exceed the maximum operating active power limit. The value of the attribute and its sign convention depends on the operating mode of the equipment.
Attribute notes
Maximum high economic active power limit, that should not exceed the maximum operating active power limit. The value of the attribute and its sign convention depends on the operating mode of the equipment.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamemaxEconomicP
Scale0
Scopepublic
Staticfalse
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
maxStartupLoadi{A068A5E7-BE6C-411e-B51F-BCA65ECEB7F8}show detailsdid not existActivePower [0..1]Maximum consumption by the generating unit as part of the startup process.
Attribute notes
Maximum consumption by the generating unit as part of the startup process.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemaxStartupLoad
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
minimumUpTimei{3DDFB2C0-5AE6-4302-BD7C-D964535E41A1}show detailsdid not existDuration [0..1]The time that a generating unit has to stay running after it has been switched on by the Remedial Action Optimizer.
Attribute notes
The time that a generating unit has to stay running after it has been switched on by the Remedial Action Optimizer.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameminimumUpTime
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeDuration
UpperBound1
Tagged values — changes
BaselineDestination
none
mustRuni{A27DCF15-2F10-41c6-8997-5E657AB62F7F}show detailsdid not existBoolean [0..1]Identifies if the generating unit is a must-run unit. This means that it cannot be instructed to shutdown due to other obligation. e.g. Providing heat. If true, the generating unit is must-run. If false, it is not.
Attribute notes
Identifies if the generating unit is a must-run unit. This means that it cannot be instructed to shutdown due to other obligation. e.g. Providing heat. If true, the generating unit is must-run. If false, it is not.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemustRun
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
mustRunPi{6669B825-5540-46e0-AEA6-396B1AC3CAE9}show detailsdid not existActivePower [0..1]Minimum active power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute notes
Minimum active power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemustRunP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
mustRunQi{4F53DFBD-4075-4872-A64A-CAE7F2EC3D51}show detailsdid not existReactivePower [0..1]Minimum reactive power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute notes
Minimum reactive power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamemustRunQ
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeReactivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalMaxEconomicPirenamed from maxEconomicP{62CC5B01-6098-4901-B00D-F5455C940661}show detailsActivePower [0..1]ActivePower [0..1]MaximumNormal maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute notes (destination, redlined)
MaximumNormal maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute metadata — changes
BaselineDestination
NamemaxEconomicPnormalMaxEconomicP
Tagged values — changes
BaselineDestination
no changes
normalMustRunPi{92C6D698-1584-44a3-936C-287814448788}show detailsdid not existActivePower [0..1]Normal minimum active power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute notes
Normal minimum active power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamenormalMustRunP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalMustRunQi{4379EA5C-8A31-44e7-A135-961C50316DCF}show detailsdid not existReactivePower [0..1]Normal minimum reactive power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute notes
Normal minimum reactive power injection that is needed to meet must-run requirement. This value can be higher or equal to minimum operational limit. Load sign convention is used, i.e. positive sign means flow out from a node.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamenormalMustRunQ
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeReactivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalStartupCosti{59B80CA4-145C-4140-817B-1D5477C15BF0}show detailsdid not existMoney [0..1]The normal initial startup cost incurred for each start of the GeneratingUnit.
Attribute notes
The normal initial startup cost incurred for each start of the GeneratingUnit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamenormalStartupCost
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeMoney
UpperBound1
Tagged values — changes
BaselineDestination
none
normalWarmStartupCosti{CB8372E6-B49E-4a8b-9AD5-38D3723A6EC9}show detailsdid not existMoney [0..1]The normal warm startup cost incurred for each start of the GeneratingUnit.
Attribute notes
The normal warm startup cost incurred for each start of the GeneratingUnit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamenormalWarmStartupCost
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeMoney
UpperBound1
Tagged values — changes
BaselineDestination
none
participationFactori{501633F9-17C7-4835-BD0B-4B6056839587}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameparticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
runningLeadTimei{76988F51-C5FB-46d1-AF96-8BE0C95BE870}show detailsdid not existDuration [0..1]Time it takes to change the schedule when the unit is operating due to technical configuration of a supporting system, e.g. gas pipeline.
Attribute notes
Time it takes to change the schedule when the unit is operating due to technical configuration of a supporting system, e.g. gas pipeline.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamerunningLeadTime
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeDuration
UpperBound1
Tagged values — changes
BaselineDestination
none
shutdownCosti{AF86D019-43C1-4538-BC75-CD5241FC4C3F}show detailsdid not existMoney [0..1]The shutdown cost incurred for each shutdown of the GeneratingUnit.
Attribute notes
The shutdown cost incurred for each shutdown of the GeneratingUnit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameshutdownCost
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeMoney
UpperBound1
Tagged values — changes
BaselineDestination
none
shutdownTimei{E7712FE9-1B2C-4c79-8180-6D18D01F0AB0}show detailsdid not existDuration [0..1]Time it takes to shutdown the unit.
Attribute notes
Time it takes to shutdown the unit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameshutdownTime
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeDuration
UpperBound1
Tagged values — changes
BaselineDestination
none
startupRampRatei{150C4462-8278-4762-81DE-E5572B38E43D}show detailsdid not existActivePowerChangeRate [0..1]The startup ramp rate of the generating unit which describes the speed of change of active power from zero to the minimum active power. When the ramp is not provided, the optimisation process shall consider the change as an instant change of active power from zero to minimum active power.
Attribute notes
The startup ramp rate of the generating unit which describes the speed of change of active power from zero to the minimum active power. When the ramp is not provided, the optimisation process shall consider the change as an instant change of active power from zero to minimum active power.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamestartupRampRate
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePowerChangeRate
UpperBound1
Tagged values — changes
BaselineDestination
none
warmStartupCosti{E98A65FD-B362-422d-B1B6-C59D5CB42499}show detailsdid not existMoney [0..1]The warm startup cost incurred for each start of the GeneratingUnit.
Attribute notes
The warm startup cost incurred for each start of the GeneratingUnit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamewarmStartupCost
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeMoney
UpperBound1
Tagged values — changes
BaselineDestination
none
warmStartupTimei{BF51EC09-0C0A-445e-858F-D0D263366EBB}show detailsdid not existDuration [0..1]Time it takes to startup the unit when it is warm.
Attribute notes
Time it takes to startup the unit when it is warm.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NamewarmStartupTime
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeDuration
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
BaselineGeneratingUnit → ExtGeneratingUnit
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndGeneratingUnit
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndExtGeneratingUnit
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙HydroPumpi
Class notes
A synchronous motor-driven pump, typically associated with a pumped storage plant.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{4C4342EA-F3E1-469a-ACB4-CA80A2524FFE}
Class notes
A synchronous motor-driven pump, typically associated with a pumped storage plant.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
maxEconomicPi{8EBE9483-F7A9-4f65-AF30-D85A35AA9539}show detailsdid not existActivePower [0..1]Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute notes
Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamemaxEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
maxOperatingPi{E2A4565F-6E13-488a-9973-2312510DD5B3}show detailsdid not existActivePower [0..1]This is the maximum operating active power limit the dispatcher can enter for this unit.
Attribute notes
This is the maximum operating active power limit the dispatcher can enter for this unit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamemaxOperatingP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
minEconomicPi{7A5EB81E-9382-460d-A00E-8E72D0C6570B}show detailsdid not existActivePower [0..1]Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute notes
Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameminEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
minOperatingPi{B536C628-2375-4a8f-94C2-D2DDCC7CFD8F}show detailsdid not existActivePower [0..1]This is the minimum operating active power limit the dispatcher can enter for this unit.
Attribute notes
This is the minimum operating active power limit the dispatcher can enter for this unit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
NameminOperatingP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalParticipationFactori{D743A43C-C00C-4700-9248-1EB97A2E8BBD}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamenormalParticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
participationFactori{A9170B9E-F3A4-4702-A2B7-A46F69C06FDE}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameparticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
BaselineHydroPump → ExtHydroPump
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndHydroPump
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndExtHydroPump
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
▶⚙PowerElectronicsUniti
Class notes
A generating unit or battery or aggregation that connects to the AC network using power electronics rather than rotating machines.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{EC401F21-E818-46dc-88CE-2CFD1E60B76C}
Class notes
A generating unit or battery or aggregation that connects to the AC network using power electronics rather than rotating machines.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
maxEconomicPi{CA02F321-0DB7-46cc-9BDF-79BECFE155EF}show detailsdid not existActivePower [0..1]Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute notes
Maximum high economic active power limit, that should not exceed the maximum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamemaxEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
minEconomicPi{3192CD69-341A-460c-965A-F97DC7919280}show detailsdid not existActivePower [0..1]Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute notes
Low economic active power limit that shall be greater than or equal to the minimum operating active power limit.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameminEconomicP
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
normalParticipationFactori{251BBBB5-40B4-47ed-8D9F-EFE1B5930C46}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamenormalParticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
pi{E3567430-1481-4436-9EE0-2AE3B7DFF109}show detailsdid not existActivePower [0..1]Active power injection. Load sign convention is used, i.e. positive sign means flow out from a node. Starting value for a steady state solution.
Attribute notes
Active power injection. Load sign convention is used, i.e. positive sign means flow out from a node. Starting value for a steady state solution.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namep
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeActivePower
UpperBound1
Tagged values — changes
BaselineDestination
GUIDBasedOn(no tag){792C720E-AF6B-47ed-84D7-C08A882047CD}
participationFactori{3C6900F4-AF54-416d-8F5B-1AF1595F9CEA}show detailsdid not existFloat [0..1]Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute notes
Participation factor describing the entity part of the active power provided by a collection of entities (e.g. an active power forecast to a collection of entities is divided to each of the member entity according to the participation factor). Must be a positive value. In the case of a sharing strategy, the distribution is following entities value (V) equals aggregated value (T) divided by sum of participation factors (PF), i.e. V=T/sum(PF). In the case of priority strategy, the item with the lowest number gets allocated energy first.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameparticipationFactor
Scale0
Scopepublic
Staticfalse
StereotypeNC
TypeFloat
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
BaselinePowerElectronicsUnit → ExtPowerElectronicsUnit
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndPowerElectronicsUnit
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndExtPowerElectronicsUnit
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Changed diagrams (7)
▶▦DocDatatypesi
Diagram notes
This diagram show the data types specific to the Production package.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{E179110A-3FB3-43a0-93EB-EEB87DC510CE}
Diagram notes
This diagram show the data types specific to the Production package.
▦Diagram
changed
Baseline
DocDatatypes (baseline)
Destination
DocDatatypes (destination)
▶▦DocHydroi
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
DocHydro (baseline)
Destination
DocHydro (destination)
▶▦DocMaini
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
DocMain (baseline)
Destination
DocMain (destination)
▶▦DocNucleari
Diagram notes
This diagram shows nuclear generation inheritance.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{60810DF7-9CDB-4150-81FB-BA2C6709E9D2}
Diagram notes
This diagram shows nuclear generation inheritance.
▦Diagram
changed
Baseline
DocNuclear (baseline)
Destination
DocNuclear (destination)
▶▦DocPowerElectronicsi
Diagram notes
This diagram shows power electronics classes and inheritance.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:47:342025-04-08 01:21:49
CHANGED{A720762E-6E84-4af2-A047-9DA9F13F29AE}
Diagram notes
This diagram shows power electronics classes and inheritance.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:47:342025-04-08 01:21:49
▦Diagram
changedmoved or resized
Baseline
DocPowerElectronics (baseline)
Destination
DocPowerElectronics (destination)
Connectors 1 rerouted · 1 labels movedhover a connector to outline the elements it joins
reroutedGeneratingUnit – Equipment
labels movedPowerElectronicsConnection – PowerElectronicsUnit
▶▦DocProductioni
Diagram notes
The diagram contains classes related to production.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:47:412025-04-08 01:35:49
CHANGED{D0D3D5E4-58BB-44b1-A6A9-590DEDC8F57F}
Diagram notes
The diagram contains classes related to production.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:47:412025-04-08 01:35:49
▦Diagram
removedchangedmoved or resized
Baseline
DocProduction (baseline)
Destination
DocProduction (destination)
Connectors 1 added · 1 removed · 1 labels movedhover a connector to outline the elements it joins
addedNuclearGeneratingUnit – GeneratingUnit
removedPowerElectronicsUnit – ExtPowerElectronicsUnit
labels movedFuelStorage – FossilFuel
▶▦DocThermali
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
DocThermal (baseline)
Destination
DocThermal (destination)
Package 'Generation' has no changes to the 1 diagrams it contains.
▶DCi
Package notes
This package contains model for direct current equipment and controls.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{6CA575E7-020B-40d8-B841-027BF8B51BE9}
Package notes
This package contains model for direct current equipment and controls.
Changed classes (2)
▶⚙DCTopologicalIslandi
Class notes
An electrically connected subset of the network. DC topological islands can change as the current network state changes, e.g. due to: - disconnect switches or breakers changing state in a SCADA/EMS. - manual creation, change or deletion of topological nodes in a planning tool. Only energised TopologicalNode-s shall be part of the topological island.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{85B3B225-BD9B-4689-8878-0CEE3E06231B}
Class notes
An electrically connected subset of the network. DC topological islands can change as the current network state changes, e.g. due to: - disconnect switches or breakers changing state in a SCADA/EMS. - manual creation, change or deletion of topological nodes in a planning tool. Only energised TopologicalNode-s shall be part of the topological island.
⇄Links
Baselinedid not exist
→
DestinationDCTopologicalNode role DCTopologicalNodes [1..*] → DCTopologicalIsland role DCTopologicalIsland [0..1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndDCTopologicalNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalNodes
RoleNoteThe DC topological nodes in a DC topological island.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndDCTopologicalIsland
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalIsland
RoleNoteA DC topological node belongs to a DC topological island.
Scopepublic
TargetScopeinstance
BaselineDCTopologicalNode role DCTopologicalNodes [1..*] → DCTopologicalIsland role DCTopologicalIsland [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAggregation
Source end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndDCTopologicalNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalNodes
RoleNoteThe DC topological nodes in a DC topological island.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndDCTopologicalIsland
IsAggregationshared
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalIsland
RoleNoteA DC topological node belongs to a DC topological island.
Scopepublic
TargetScopeinstance
▶⚙DCTopologicalNodei
Class notes
DC bus.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{36E96930-3FAF-4844-91D4-7103E3D68EAA}
Class notes
DC bus.
⇄Links
Baselinedid not exist
→
DestinationDCTopologicalNode role DCTopologicalNodes [1..*] → DCTopologicalIsland role DCTopologicalIsland [0..1]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndDCTopologicalNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalNodes
RoleNoteThe DC topological nodes in a DC topological island.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndDCTopologicalIsland
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalIsland
RoleNoteA DC topological node belongs to a DC topological island.
Scopepublic
TargetScopeinstance
BaselineDCTopologicalNode role DCTopologicalNodes [1..*] → DCTopologicalIsland role DCTopologicalIsland [0..1]
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAggregation
Source end
BaselineDestination
Cardinality1..*
ContainmentUnspecified
EndDCTopologicalNode
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalNodes
RoleNoteThe DC topological nodes in a DC topological island.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndDCTopologicalIsland
IsAggregationshared
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleDCTopologicalIsland
RoleNoteA DC topological node belongs to a DC topological island.
Scopepublic
TargetScopeinstance
Changed diagrams (2)
▶▦DocACDCConnectivityModeli
Diagram notes
This diagram shows connectivity and topology model for both AC and DC networks.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:49:452025-09-28 19:44:35
CHANGED{43531300-1039-4de2-880E-A73AFC65A581}
Diagram notes
This diagram shows connectivity and topology model for both AC and DC networks.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:49:452025-09-28 19:44:35
▦Diagram
moved or resized
Baseline
DocACDCConnectivityModel (baseline)
Destination
DocACDCConnectivityModel (destination)
Connectors 1 added · 1 removedhover a connector to outline the elements it joins
addedDCTopologicalNode – DCTopologicalIsland
removedDCTopologicalNode – DCTopologicalIsland
▶▦DocDirectCurrenti
Diagram notes
The diagram contains classes related to direct current.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{7EEA9E63-B76B-4f4f-A146-435BAFE4EC68}
Diagram notes
The diagram contains classes related to direct current.
▦Diagram
changed
Baseline
DocDirectCurrent (baseline)
Destination
DocDirectCurrent (destination)
▶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 7 classes it contains.
Changed diagrams (1)
▶▦DocEquivalentsi
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
DocEquivalents (baseline)
Destination
DocEquivalents (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 (2)
▶⚙MeasurementValueQualityi
Class notes
Measurement quality flags. Bits 0-10 are defined for substation automation in IEC 61850-7-3. Bits 11-15 are reserved for future expansion by that document. Bits 16-31 are reserved for EMS applications.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{D45A5712-F5C6-410e-8799-A6EEBD3DAEA2}
Class notes
Measurement quality flags. Bits 0-10 are defined for substation automation in IEC 61850-7-3. Bits 11-15 are reserved for future expansion by that document. Bits 16-31 are reserved for EMS applications.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
estimatorReplacedi{9651C2C0-48A7-406b-9F1A-C133AB46E01C}show detailsdid not existBoolean [0..1]The value has been replaced (substituted) by a State Estimator application.
Attribute notes
The value has been replaced (substituted) by a State Estimator application.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
NameestimatorReplaced
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
suspecti{9C60C191-0EA2-4dd6-ABE4-BA5C644837E9}show detailsdid not existBoolean [0..1]A correlation function has detected that the value is not consistent with other values. Typically set by a network State Estimator.
Attribute notes
A correlation function has detected that the value is not consistent with other values. Typically set by a network State Estimator.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsOrderedfalse
LowerBound0
Namesuspect
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙Quality61850i
Class notes (destination, redlined)
Quality flags in this class are as defined in IEC 61850, except for estimatorReplaced, which has been included in this class for convenience. Quality flags in this class are as defined in IEC 61850-7-2:2010+AMD1:2020. The source attribute has additional enumeration values.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{3561961B-F3BD-41f7-B693-9D9F77C613A0}
Class notes (destination, redlined)
Quality flags in this class are as defined in IEC 61850, except for estimatorReplaced, which has been included in this class for convenience. Quality flags in this class are as defined in IEC 61850-7-2:2010+AMD1:2020. The source attribute has additional enumeration values.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
estimatorReplacedi{11CA6A0B-FEAC-41a0-AF45-AE159D352461}show detailsBoolean [0..1]removed from model
Attribute notes (baseline)
Value has been replaced by State Estimator. estimatorReplaced is not an IEC 61850 quality bit but has been put in this class for convenience.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameestimatorReplaced
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
inaccuratei{6E21A6FB-9282-4837-A628-D8F5003175F7}show detailsdid not existBoolean [0..1]If true, the value does not meet the stated accuracy of the source. For example, the measured value of power factor may be inaccurate when the current is very small.
Attribute notes
If true, the value does not meet the stated accuracy of the source. For example, the measured value of power factor may be inaccurate when the current is very small.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
Nameinaccurate
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
inconsistentirenamed from oldData{4E74DF87-D586-4fdb-AFBC-968BDCC024A1}show detailsBoolean [0..1]Boolean [0..1]Measurement value is old and possibly invalid, as it has not been successfully updated during a specified time interval. If true, an evaluation function has detected an inconsistency. Typically set within the measurement device or substation automation system.
Attribute notes (destination, redlined)
Measurement value is old and possibly invalid, as it has not been successfully updated during a specified time interval. If true, an evaluation function has detected an inconsistency. Typically set within the measurement device or substation automation system.
Attribute metadata — changes
BaselineDestination
NameoldDatainconsistent
Tagged values — changes
BaselineDestination
no changes
oldDatai{CD8D6987-88CA-4b99-ADBD-AAFE98FCF382}show detailsdid not existBoolean [0..1]Measurement value is old and possibly invalid, as it has not been successfully updated during a specified time interval.
Attribute notes
Measurement value is old and possibly invalid, as it has not been successfully updated during a specified time interval.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
NameoldData
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
sourcei{E4D6FE8C-2979-4ab1-92C8-705335298653}show detailsSource [0..1]Source [0..1]Source gives information related to the origin of a value. The value may be acquired from the process, defaulted or substituted. Defines the source (origin) of a value. The value may be acquired from the process, defaulted or substituted. For values acquired through IEC 61850 based systems, the source can be "process" or "substituted". Substitution may be done in the acquisition device, in a communication device or within a CIM application.
Attribute notes (destination, redlined)
Source gives information related to the origin of a value. The value may be acquired from the process, defaulted or substituted. Defines the source (origin) of a value. The value may be acquired from the process, defaulted or substituted. For values acquired through IEC 61850 based systems, the source can be "process" or "substituted". Substitution may be done in the acquisition device, in a communication device or within a CIM application.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
suspecti{F925B417-2665-40e7-89ED-F22698B8207E}show detailsBoolean [0..1]removed from model
Attribute notes (baseline)
A correlation function has detected that the value is not consistent with other values. Typically set by a network State Estimator.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
Namesuspect
Scale0
Scopepublic
Staticfalse
TypeBoolean
UpperBound1
Tagged values — changes
BaselineDestination
none
validityi{C5A711E6-F0C4-47c1-B00E-1FF68CD1B4F8}show detailsValidity [0..1]Validity [0..1]Validity of the measurement value. Validity of the value, as condensed information for the client. In case this value is not 'good', some reasons may be found in other attributes. 'invalid' means that the value cannot be used. 'questionable' means that the value may or may not be used by the receiving application. For example a switch position measurement with oldData = true, may still be used by topology processing. The reason for an invalid or questionable value of an attribute may be specified in more detail with further quality identifiers. If one of these identifiers {overflow, outOfRange, badReference, oscillatory, oldData, inconsistent, inaccurate, failure} is set then validity shall be set to invalid or questionable. Reference: Table D.1 IEC 61850-7-2:2010+AMD1:2020.
Attribute notes (destination, redlined)
Validity of the measurement value. Validity of the value, as condensed information for the client. In case this value is not 'good', some reasons may be found in other attributes. 'invalid' means that the value cannot be used. 'questionable' means that the value may or may not be used by the receiving application. For example a switch position measurement with oldData = true, may still be used by topology processing. The reason for an invalid or questionable value of an attribute may be specified in more detail with further quality identifiers. If one of these identifiers {overflow, outOfRange, badReference, oscillatory, oldData, inconsistent, inaccurate, failure} is set then validity shall be set to invalid or questionable. Reference: Table D.1 IEC 61850-7-2:2010+AMD1:2020.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Changed diagrams (4)
▶▦DocControli
Diagram notes
This diagram shows all classes included in the Meas package.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3289B12E-C4E6-473f-880A-706F56AB1751}
Diagram notes
This diagram shows all classes included in the Meas package.
▦Diagram
changed
Baseline
DocControl (baseline)
Destination
DocControl (destination)
▶▦DocMeasurementi
Diagram notes
This diagram shows classes central to the Measurement package and connections to some external classes.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{8013CE5A-1E8B-43a7-8A3D-29DA0B40602A}
Diagram notes
This diagram shows classes central to the Measurement package and connections to some external classes.
▦Diagram
changed
Baseline
DocMeasurement (baseline)
Destination
DocMeasurement (destination)
▶▦DocMeasurementInheritancei
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
DocMeasurementInheritance (baseline)
Destination
DocMeasurementInheritance (destination)
▶▦DocQualityi
Diagram notes
This diagram shows the details of the quality codes. The quality flags can be used also in other packages not only specific to MeasurementValues. A generalized Quality class is added and inherited into MeasurementValueQuality.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:51:002025-04-08 00:24:18
CHANGED{A84E42BC-B21D-4fa5-B7DC-006CE50BB19C}
Diagram notes
This diagram shows the details of the quality codes. The quality flags can be used also in other packages not only specific to MeasurementValues. A generalized Quality class is added and inherited into MeasurementValueQuality.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:51:002025-04-08 00:24:18
▦Diagram
changed
Baseline
DocQuality (baseline)
Destination
DocQuality (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)
▶▦DocDiagramLayouti
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
DocDiagramLayout (baseline)
Destination
DocDiagramLayout (destination)
▶FACTSi
Package notes
This package contains the classes related to the FACTS.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{14140B90-7738-458e-8E74-6CD8AC373787}
Package notes
This package contains the classes related to the FACTS.
Moved classes (1)
▶⚙StaticVarCompensatori
Class notes (destination, redlined)
A facility for providing variable and controllable shunt reactive power. The SVC typically consists of a stepdown transformer, filter, thyristor-controlled reactor, and thyristor-switched capacitor arms. The SVC may operate in fixed MVar output mode or in voltage control mode. When in voltage control mode, the output of the SVC will be proportional to the deviation of voltage at the controlled bus from the voltage setpoint. The SVC characteristic slope defines the proportion. If the voltage at the controlled bus is equal to the voltage setpoint, the SVC MVar output is zero.
Class metadata — changes
BaselineDestination
ParentPackageWiresFACTS
Tagged values — changes
BaselineDestination
no changes
MOVEDfrom Wires{B540EF99-8CE4-4da6-9E4D-D22E867F8BAE}
Class notes (destination, redlined)
A facility for providing variable and controllable shunt reactive power. The SVC typically consists of a stepdown transformer, filter, thyristor-controlled reactor, and thyristor-switched capacitor arms. The SVC may operate in fixed MVar output mode or in voltage control mode. When in voltage control mode, the output of the SVC will be proportional to the deviation of voltage at the controlled bus from the voltage setpoint. The SVC characteristic slope defines the proportion. If the voltage at the controlled bus is equal to the voltage setpoint, the SVC MVar output is zero.
▤Metadata
BaselineDestination
ParentPackageWiresFACTS
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
capacitiveRatingi{E35F733F-7F1A-4124-8539-BE6FEE250CCD}show detailsReactance [0..1]removed from model
Attribute notes (baseline)
Capacitive reactance at maximum capacitive reactive power. Shall always be positive.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NamecapacitiveRating
Scale0
Scopepublic
Staticfalse
TypeReactance
UpperBound1
Tagged values — changes
BaselineDestination
none
inductiveRatingi{3F4C093D-2CC5-4ee5-A225-31D4B7AFD3AC}show detailsReactance [0..1]removed from model
Attribute notes (baseline)
Inductive reactance at maximum inductive reactive power. Shall always be negative.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
NameinductiveRating
Scale0
Scopepublic
Staticfalse
TypeReactance
UpperBound1
Tagged values — changes
BaselineDestination
none
qi{EAA3BC8D-A193-4c4e-BE22-F45A9C2A491C}show detailsReactivePower [0..1]removed from model
Attribute notes (baseline)
Reactive power injection. Load sign convention is used, i.e. positive sign means flow out from a node. Starting value for a steady state solution.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
Nameq
Scale0
Scopepublic
Staticfalse
TypeReactivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
sVCControlModei{5D29151B-3D23-4964-BE66-3C58A2D84411}show detailsSVCControlMode [0..1]removed from model
Attribute notes (baseline)
SVC control mode.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
NamesVCControlMode
Scale0
Scopepublic
Staticfalse
TypeSVCControlMode
UpperBound1
Tagged values — changes
BaselineDestination
none
slopei{71A799EF-C590-4631-A53A-EC207BFFC113}show detailsVoltagePerReactivePower [0..1]removed from model
Attribute notes (baseline)
The characteristics slope of an SVC defines how the reactive power output changes in proportion to the difference between the regulated bus voltage and the voltage setpoint. The attribute shall be a positive value or zero.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteralfalse
IsOrderedfalse
LowerBound0
Nameslope
Scale0
Scopepublic
Staticfalse
TypeVoltagePerReactivePower
UpperBound1
Tagged values — changes
BaselineDestination
none
voltageSetPointi{170589DF-9B85-487a-BC91-4BC8ECB1D88C}show detailsVoltage [0..1]removed from model
Attribute notes (baseline)
The reactive power output of the SVC is proportional to the difference between the voltage at the regulated bus and the voltage setpoint. When the regulated bus voltage is equal to the voltage setpoint, the reactive power output is zero.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
IsOrderedfalse
LowerBound0
NamevoltageSetPoint
Scale0
Scopepublic
Staticfalse
TypeVoltage
UpperBound1
Tagged values — changes
BaselineDestination
none
⇄Links
Source end
no changes
Target end — FACTSEquipment
BaselineDestination
EndRegulatingCondEqFACTSEquipment
Changed classes (1)
▶⚙FACTSEquipmenti
Class notes
Flexible Alternating Current Transmission System regulating equipment.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{F56B565C-861C-4d65-B669-27B53B232261}
Class notes
Flexible Alternating Current Transmission System regulating equipment.
⇄Links
Source end
no changes
Target end — FACTSEquipment
BaselineDestination
EndRegulatingCondEqFACTSEquipment
→
Destinationremoved from model
Link metadata
BaselineDestination
DirectionSource -> Destination
TypeGeneralization
Source end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndStaticVarCompensator
IsAggregation0
IsChangeablenone
IsNavigablefalse
Orderingfalse
ScopePublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0
ContainmentUnspecified
EndFACTSEquipment
IsAggregation0
IsChangeablenone
IsNavigabletrue
Orderingfalse
ScopePublic
TargetScopeinstance
Changed diagrams (2)
▶▦DocFACTSi
Diagram notes
The diagram contains association related to FACTS.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:51:302025-04-07 02:38:07
CHANGED{35F0B3A0-975C-45e2-946E-47D65F59C6E8}
Diagram notes
The diagram contains association related to FACTS.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:51:302025-04-07 02:38:07
▦Diagram
removedchanged
Baseline
DocFACTS (baseline)
Destination
DocFACTS (destination)
Connectors 1 removed · 1 rerouted · 3 labels movedhover a connector to outline the elements it joins
removedStaticVarCompensator – FACTSEquipment
reroutedStaticVarCompensator – FACTSEquipment
labels movedEquipmentController – RegulatingCondEq
labels movedLossCurve – FACTSEquipment
labels movedTCSCCompensationPoint – ThyristorControlledSeriesCompensator
▶▦DocSSSCi
Diagram notes
The diagram shows necessary classes related to the model controls of SSSC controller.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{55CE0DC3-8F66-40b8-AFC2-ABADF49F0273}
Diagram notes
The diagram shows necessary classes related to the model controls of SSSC controller.
▦Diagram
changed
Baseline
DocSSSC (baseline)
Destination
DocSSSC (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.
Changed classes (4)
▶⚙BranchGroupi
Class notes
A group of branch terminals whose directed flow summation is to be monitored. A branch group need not form a cutset of the network.
Class metadata — changes
BaselineDestination
Stereotype(empty)deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{A795B546-34EE-419f-B392-039926A2C6E3}
Class notes
A group of branch terminals whose directed flow summation is to be monitored. A branch group need not form a cutset of the network.
▤Metadata
BaselineDestination
Stereotype(empty)deprecated
Class 'BranchGroup' has no other changes. The shows its notes and every changed property.
▶⚙BranchGroupTerminali
Class notes
A specific directed terminal flow for a branch group.
Class metadata — changes
BaselineDestination
Stereotype(empty)deprecated
Tagged values — changes
BaselineDestination
no changes
CHANGED{B0C18CF1-75AE-44f3-9466-ABD95FE287EC}
Class notes
A specific directed terminal flow for a branch group.
▤Metadata
BaselineDestination
Stereotype(empty)deprecated
Class 'BranchGroupTerminal' has no other changes. The shows its notes and every changed property.
▶⚙LimitKind«enumeration»i
Class notes
Limit kinds.
Class metadata — changes
BaselineDestination
Stereotypeenumeration, Europeanenumeration
Tagged values — changes
BaselineDestination
no changes
CHANGED{C6901289-57C7-41a3-AF87-9AA5E788E1CF}
Class notes
Limit kinds.
▤Metadata
BaselineDestination
Stereotypeenumeration, Europeanenumeration
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
emergencyi{F54CEF19-470A-4dcd-9BA9-2CFA3FB019BC}show detailsdid not exist [1..1]The rating as defined by the equipment owner that specifics the level of electrical loading or output, usually expressed in megawatts (MW) or Mvar, or other appropriate units, that a system, facility, or element can support, procedure, or withstand for a finite period. The rating assumes acceptable loss of equipment life or other physical or safety limitations for the equipment involved.
Attribute notes
The rating as defined by the equipment owner that specifics the level of electrical loading or output, usually expressed in megawatts (MW) or Mvar, or other appropriate units, that a system, facility, or element can support, procedure, or withstand for a finite period. The rating assumes acceptable loss of equipment life or other physical or safety limitations for the equipment involved.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Nameemergency
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
loadSheddingi{18391040-E4A5-4d56-9737-4EC11F5BBB83}show detailsdid not exist [1..1]A kind of emergency rating that typically has a shorter duration.
Attribute notes
A kind of emergency rating that typically has a shorter duration.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
NameloadShedding
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
normali{CCC21F40-B583-4f91-985C-80A26886D9A8}show detailsdid not exist [1..1]The rating as defined by the equipment owner that specifies the level of electrical loading, usually expressed in megawatts (MW) or other appropriate units that a system, facility, or element can support or withstand through the daily demand cycles without loss of equipment life.
Attribute notes
The rating as defined by the equipment owner that specifies the level of electrical loading, usually expressed in megawatts (MW) or other appropriate units that a system, facility, or element can support or withstand through the daily demand cycles without loss of equipment life.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
Namenormal
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
▶⚙OperationalLimitSeti
Class notes
A set of limits associated with equipment. Sets of limits might apply to a specific temperature, or season for example. A set of limits may contain different severities of limit levels that would apply to the same equipment. The set may contain limits of different types such as apparent power and current limits or high and low voltage limits that are logically applied together as a set.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{B0D1133E-CFA4-467d-81D1-75719BF02976}
Class notes
A set of limits associated with equipment. Sets of limits might apply to a specific temperature, or season for example. A set of limits may contain different severities of limit levels that would apply to the same equipment. The set may contain limits of different types such as apparent power and current limits or high and low voltage limits that are logically applied together as a set.
⇄Links
Baselinedid not exist
→
DestinationSeason role Season [0..1] → OperationalLimitSet role OperationalLimitSet [0..*]
Link metadata
BaselineDestination
DirectionUnspecified
IsLeaffalse
IsRootfalse
TypeAssociation
Source end
BaselineDestination
Cardinality0..1
ContainmentUnspecified
EndSeason
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleSeason
RoleNoteThe season for this operational limit set.
Scopepublic
TargetScopeinstance
Target end
BaselineDestination
Cardinality0..*
ContainmentUnspecified
EndOperationalLimitSet
IsAggregationnone
IsChangeablenone
IsNavigabletrue
Orderingfalse
RoleOperationalLimitSet
RoleNoteThe operational limit set that has a season.
Scopepublic
TargetScopeinstance
Changed diagrams (2)
▶▦DocBranchGroupi
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
DocBranchGroup (baseline)
Destination
DocBranchGroup (destination)
▶▦DocOperationalLimitsi
Diagram notes
This diagram shows operational limits as they tie back into the core model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:51:432025-04-08 01:03:14
CHANGED{6B0E5843-FA70-4495-BB16-CD2B0CAA01B5}
Diagram notes
This diagram shows operational limits as they tie back into the core model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:51:432025-04-08 01:03:14
▦Diagram
addedchangedmoved or resized
Baseline
DocOperationalLimits (baseline)
Destination
DocOperationalLimits (destination)
Connectors 1 added · 5 rerouted · 1 labels movedhover a connector to outline the elements it joins
addedSeason – OperationalLimitSet
reroutedOperationalLimit – OperationalLimitSet
reroutedOperationalLimitSet – (not in this model)
reroutedOperationalLimitSet – ACDCTerminal
reroutedTerminal – ACDCTerminal
reroutedVoltageAngleLimit – OperationalLimit
labels movedVoltageAngleLimit – Terminal
▶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 7 classes it contains.
Changed diagrams (2)
▶▦DocControlAreai
Diagram notes
This diagram shows control area specification and some related classes. The Terminal to AnalogValue linkages are shown for clarity in understanding the control area specification. The GeneratingUnit to Terminal linkages are also shown to illustrate how generation flows are specifically tied to the network.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{EA9DC05C-2FC2-4b1f-BD10-55E43A2EEDD7}
Diagram notes
This diagram shows control area specification and some related classes. The Terminal to AnalogValue linkages are shown for clarity in understanding the control area specification. The GeneratingUnit to Terminal linkages are also shown to illustrate how generation flows are specifically tied to the network.
▦Diagram
changed
Baseline
DocControlArea (baseline)
Destination
DocControlArea (destination)
▶▦DocControlAreaInheritancei
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
DocControlAreaInheritance (baseline)
Destination
DocControlAreaInheritance (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)
▶▦DocContingencyi
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
DocContingency (baseline)
Destination
DocContingency (destination)
▶StateVariablesi
Package notes
State variables for analysis solutions such as powerflow.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{968842F7-ED9B-4b20-A08E-C8ECAAC5DB25}
Package notes
State variables for analysis solutions such as powerflow.
Package 'StateVariables' has no changes to the 10 classes it contains.
Changed diagrams (1)
▶▦DocStateVariablesi
Diagram notes
The state solution variables as derived from base StateVariable class. Note that specialized state variables are associated with objects derived from IdentifiedObject, but StateVariable does not derive from IdentifiedObject.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{98328D29-4518-4d82-93D9-EC1421E6E8BF}
Diagram notes
The state solution variables as derived from base StateVariable class. Note that specialized state variables are associated with objects derived from IdentifiedObject, but StateVariable does not derive from IdentifiedObject.
▦Diagram
changed
Baseline
DocStateVariables (baseline)
Destination
DocStateVariables (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.
▶62361Drafti
Package notes
No notes defined in the model.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{C122135C-616C-493f-A00E-82A3B7468341}
Package notes
No notes defined in the model.
Changed classes (1)
▶⚙ProgrammingLanguageKind«enumeration»i
Class notes
Enumeration of programming languages.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{2066CA6A-41E9-4706-AB1E-370990C9D0C6}
Class notes
Enumeration of programming languages.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
Ci{F1D9D906-F781-436c-9CB7-1C9B0CE8838F}show details [1..1] [1..1]C programming language.
Attribute notes (destination, redlined)
C programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CPlusPlusirenamed from C++{8D2C731A-2311-411f-9A23-0A405FF16A69}show details [1..1] [1..1]C++ programming language.
Attribute notes (destination, redlined)
C++ programming language.
Attribute metadata — changes
BaselineDestination
NameC++CPlusPlus
Tagged values — changes
BaselineDestination
no changes
CSharpirenamed from C#{8771C069-D671-445b-A6CB-F1B2C93BD6E9}show details [1..1] [1..1]C# programming language.
Attribute notes (destination, redlined)
C# programming language.
Attribute metadata — changes
BaselineDestination
NameC#CSharp
Tagged values — changes
BaselineDestination
no changes
Delphii{0821CE79-D703-468f-B66D-11066AF639FB}show details [1..1] [1..1]Dephi programming language.
Attribute notes (destination, redlined)
Dephi programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Fortrani{3E80B0DC-CB76-4486-80C9-D8088C1E15F9}show details [1..1] [1..1]Fortran programming language.
Attribute notes (destination, redlined)
Fortran programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Goi{05158D9C-FA1B-43bc-9C84-0CE1C210FF92}show details [1..1] [1..1]Go programming language.
Attribute notes (destination, redlined)
Go programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Javai{537435B3-F794-4a10-9DB6-142437E6B5DA}show details [1..1] [1..1]Java programming language.
Attribute notes (destination, redlined)
Java programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
JavaScripti{E62BAACA-749A-4e16-B7C5-F195B39BFFC4}show details [1..1] [1..1]JavaScript programming language.
Attribute notes (destination, redlined)
JavaScript programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Juliai{51766AF0-7816-420d-8E7C-E61D23B2D6AA}show details [1..1] [1..1]Julia dynamic programming language.
Attribute notes (destination, redlined)
Julia dynamic programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Luai{C3CE804E-74F8-4099-A305-1075318F7B77}show details [1..1] [1..1]Lua scripting programming language.
Attribute notes (destination, redlined)
Lua scripting programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Matlabi{25058307-7C1C-4049-9618-3ED30007CF8B}show details [1..1] [1..1]Matlab programming language.
Attribute notes (destination, redlined)
Matlab programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
PHPi{5ECE264E-A503-4a13-94FC-2D92DB83A1EB}show details [1..1] [1..1]PHP scripting programming language.
Attribute notes (destination, redlined)
PHP scripting programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Pascali{9C0E808A-6D9C-414b-84F0-3CCC38759938}show details [1..1] [1..1]Pascal programming language.
Attribute notes (destination, redlined)
Pascal programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Perli{52B0A0AF-9C49-4ccf-BCFD-8073ED0F5188}show details [1..1] [1..1]Perl scripting programming language.
Attribute notes (destination, redlined)
Perl scripting programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Pythoni{F8BB1F84-26C2-408b-90D7-BC59572D2E35}show details [1..1] [1..1]Python programming language.
Attribute notes (destination, redlined)
Python programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Ri{A0A9FF8A-CC32-4917-8201-22ABA6861247}show details [1..1] [1..1]R functional programming language.
Attribute notes (destination, redlined)
R functional programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Rusti{94349994-7F16-4dc9-AE8F-9D36956660EE}show details [1..1] [1..1]Rust programming language.
Attribute notes (destination, redlined)
Rust programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
SPARQLi{9A384D23-68C8-4ae5-A49C-EEB81A0493BB}show detailsdid not exist [1..1]SPARQL, a query language for RDF data.
Attribute notes
SPARQL, a query language for RDF data.
Attribute metadata — changes
BaselineDestination
AllowDuplicatesfalse
Collectionfalse
Constfalse
ContainmentNot Specified
IsLiteraltrue
IsOrderedfalse
LowerBound1
NameSPARQL
Scale0
Scopepublic
Staticfalse
Stereotypeenum
UpperBound1
Tagged values — changes
BaselineDestination
none
SQLi{4EF128C7-6E8A-45fb-A9A8-A82AB2C29F27}show details [1..1] [1..1]SQL is a structured query language for relational databases.
Attribute notes (destination, redlined)
SQL is a structured query language for relational databases.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Swifti{2CFB9F59-2D12-4154-B9E9-515F955D2CC1}show details [1..1] [1..1]Swift programming language.
Attribute notes (destination, redlined)
Swift programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
VBAi{4539F9FF-D750-443a-BC52-8E78ED67EC76}show details [1..1] [1..1]VBA scripting programming language.
Attribute notes (destination, redlined)
VBA scripting programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
otheri{39033FB0-88A2-4e9e-B496-76B8E10F7148}show details [1..1] [1..1]Other programming language.
Attribute notes (destination, redlined)
Other programming language.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
Package 'Protection' has no changes to the 54 classes it contains.
Changed diagrams (14)
▶▦DocEPRIProposedUpdates1i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:282024-12-08 16:17:36
CHANGED{70EC2267-19ED-48a1-973A-CD797502D5A8}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:282024-12-08 16:17:36
▦Diagram
restyled
Baseline
DocEPRIProposedUpdates1 (baseline)
Destination
DocEPRIProposedUpdates1 (destination)
Connectors 2 rerouted · 1 restyledhover a connector to outline the elements it joins
reroutedProtectionFunctionBlock – FunctionBlock
reroutedProtectionRelatedFunctionBlock – ProtectionSettingsGroup
restyledProtectionRelatedFunctionBlock – FunctionBlock
▶▦DocEPRIProposedUpdates2i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:332024-12-08 16:17:36
CHANGED{02D1EB9B-1566-40a0-8E72-DACDC06DC998}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:332024-12-08 16:17:36
▦Diagram
removedchangedmoved or resized
Baseline
DocEPRIProposedUpdates2 (baseline)
Destination
DocEPRIProposedUpdates2 (destination)
Connectors 1 removed · 15 rerouted · 4 labels movedhover a connector to outline the elements it joins
removed(not in this model) – ProtectionSettingsGroup
reroutedAuxiliaryEquipment – Terminal
reroutedBreaker – ProtectedSwitch
reroutedCurrentTransformer – Sensor
reroutedLoadBreakSwitch – ProtectedSwitch
reroutedPotentialTransformer – Sensor
reroutedProtectionFunction – ProtectedSwitch
reroutedProtectionFunctionBlock – CurrentTransformer
reroutedProtectionFunctionBlock – ProtectedSwitch
reroutedProtectionRelatedFunctionBlock – CurrentTransformer
reroutedProtectionRelatedFunctionBlock – PotentialTransformer
reroutedProtectionRelatedFunctionBlock – ProtectedSwitch
reroutedProtectionRelatedFunctionBlock – ProtectionEquipment
reroutedProtectionRelatedFunctionBlock – ProtectionSettingsGroup
reroutedRecloser – ProtectedSwitch
reroutedSwitch – ConductingEquipment
labels movedProtectionEquipment – ProtectedSwitch
labels movedProtectionFunction – ConductingEquipment
labels movedProtectionFunctionBlock – PotentialTransformer
labels movedTerminal – ConductingEquipment
▶▦DocEPRIProposedUpdates3i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:372024-12-08 16:17:36
CHANGED{22C82B31-4654-4d0a-BB15-00DB968378DA}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:372024-12-08 16:17:36
▦Diagram
changedmoved or resizedrestyled
Baseline
DocEPRIProposedUpdates3 (baseline)
Destination
DocEPRIProposedUpdates3 (destination)
Connectors 19 reroutedhover a connector to outline the elements it joins
reroutedAutoreclosingFunctionBlock – ProtectionRelatedFunctionBlock
reroutedBreakerFailureFunctionBlock – ProtectionRelatedFunctionBlock
reroutedCurrentProtectionFunctionBlock – FaultClearanceProtectionFunctionBlock
reroutedFrequencyProtectionFunctionBlock – WideAreaProtectionFunctionBlock
reroutedImpedanceLocusTypeFunctionBlock – DistanceProtectionFunctionBlock
reroutedImpedanceLocusTypeFunctionBlock – OutOfStepProtectionFunctionBlock
reroutedOutOfStepProtectionFunctionBlock – WideAreaProtectionFunctionBlock
reroutedOverCurrentProtectionFunctionBlock – CurrentProtectionFunctionBlock
reroutedOverCurrentTypeFunctionBlock – OverCurrentProtectionFunctionBlock
reroutedOverLoadProtectionFunctionBlock – WideAreaProtectionFunctionBlock
reroutedProprietarySettingValue – IdentifiedObject
reroutedProprietarySettingValue – ProtectionRelatedFunctionBlock
reroutedProtectionFunctionBlock – ProprietarySettingValue
reroutedProtectionTripConditioningFunctionBlock – ProtectionFunctionBlock
reroutedSynchrocheckFunctionBlock – ProtectionRelatedFunctionBlock
reroutedUnderCurrentProtectionFunctionBlock – CurrentProtectionFunctionBlock
reroutedUnderPowerDirectionProtectionFunctionBlock – DirectionalProtectionFunctionBlock
reroutedVoltagePhaseComparisontypeFunctionBlock – OutOfStepProtectionFunctionBlock
reroutedWideAreaProtectionFunctionBlock – ProtectionFunctionBlock
▶▦DocEPRIProposedUpdates4i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:402024-12-08 16:17:36
CHANGED{A876811A-B2AD-4368-9ABB-7F0DE9F03727}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:402024-12-08 16:17:36
▦Diagram
changedmoved or resized
Baseline
DocEPRIProposedUpdates4 (baseline)
Destination
DocEPRIProposedUpdates4 (destination)
Connectors 6 reroutedhover a connector to outline the elements it joins
reroutedCurrentProtectionFunctionBlock – FaultClearanceProtectionFunctionBlock
reroutedFaultClearanceProtectionFunctionBlock – ProtectionFunctionBlock
reroutedOverCurrentProtectionFunctionBlock – CurrentProtectionFunctionBlock
reroutedProprietarySettingValue – IdentifiedObject
reroutedProtectionTripConditioningFunctionBlock – ProtectionFunctionBlock
reroutedWideAreaProtectionFunctionBlock – ProtectionFunctionBlock
▶▦DocEPRIProposedUpdates5i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:452024-12-08 16:17:36
CHANGED{6A23CE15-5F8D-4452-8DEB-5DBEF5CD7D15}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:452024-12-08 16:17:36
▦Diagram
changedmoved or resized
Baseline
DocEPRIProposedUpdates5 (baseline)
Destination
DocEPRIProposedUpdates5 (destination)
Connectors 10 reroutedhover a connector to outline the elements it joins
reroutedAutoreclosingFunctionBlock – ProtectionRelatedFunctionBlock
reroutedBreakerFailureFunctionBlock – ProtectionRelatedFunctionBlock
reroutedProprietarySettingValue – IdentifiedObject
reroutedProprietarySettingValue – ProtectionRelatedFunctionBlock
reroutedProprietaryThresholdvalue – ProprietarySettingValue
reroutedProprietaryTimerValue – ProprietarySettingValue
reroutedProtectionFunctionBlock – ProprietarySettingValue
reroutedRecloseSequence – AutoreclosingFunctionBlock
reroutedRecloseSequence – IdentifiedObject
reroutedSynchrocheckFunctionBlock – ProtectionRelatedFunctionBlock
▶▦DocEPRIProposedUpdates6i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:492024-12-08 16:17:36
CHANGED{01725690-E614-4e42-8361-8BDC5B6C73A6}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:492024-12-08 16:17:36
▦Diagram
changedmoved or resizedrestyled
Baseline
DocEPRIProposedUpdates6 (baseline)
Destination
DocEPRIProposedUpdates6 (destination)
Connectors 7 rerouted · 5 labels movedhover a connector to outline the elements it joins
rerouted(not in this model) – TransformerCharacteristicCurve
reroutedConductorCharacteristicCurve – TimeCurrentCurve
reroutedFuseCharacteristicCurve – TimeCurrentCurve
reroutedProtectionOperationCharacteristicCurve – TimeCurrentCurve
reroutedTimeCurrentCurve – Curve
reroutedTransformerCharacteristicCurve – TimeCurrentCurve
reroutedTransformerEnd – TransformerCharacteristicCurve
labels movedCurveData – Curve
labels movedFuseCharacteristicCurve – Fuse
labels movedFuseCharacteristicCurve – FuseInfo
labels movedFuseCharacteristicCurve – FuseInfo
labels movedProtectionOperationCharacteristicCurve – ProtectionFunctionBlock
▶▦DocEPRIProposedUpdates7i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:542024-12-08 16:17:36
CHANGED{34CB592E-E86B-4fe2-9CEB-0392B6CDD066}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:542024-12-08 16:17:36
▦Diagram
changedmoved or resizedrestyled
Baseline
DocEPRIProposedUpdates7 (baseline)
Destination
DocEPRIProposedUpdates7 (destination)
Connectors 11 rerouted · 1 labels movedhover a connector to outline the elements it joins
reroutedBooleanLogic – FunctionBlock
reroutedConstantFunctionBlock – FunctionBlock
reroutedDelayTimer – FunctionBlock
reroutedEdgeDetector – FunctionBlock
reroutedFlipFlop – FunctionBlock
reroutedFunctionBlock – FunctionBlockType
reroutedFunctionBlock – FunctionFunctionLink
reroutedFunctionTypeOutput – FunctionBlockType
reroutedLogicalOperation – FunctionBlock
reroutedNumericOperation – FunctionBlock
reroutedUpDownCounter – FunctionBlock
labels movedFunctionTypeInput – FunctionBlockType
▶▦DocEPRIProposedUpdates8i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:52:572024-12-08 16:17:36
CHANGED{990917BC-4BB4-4902-9520-05124571C938}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:52:572024-12-08 16:17:36
▦Diagram
moved or resizedrestyled
Baseline
DocEPRIProposedUpdates8 (baseline)
Destination
DocEPRIProposedUpdates8 (destination)
Connectors 2 reroutedhover a connector to outline the elements it joins
reroutedProtectionFunctionBlock – FunctionBlock
reroutedProtectionRelatedFunctionBlock – FunctionBlock
▶▦DocMaini
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
ModifiedDate2024-12-06 19:53:022024-12-08 16:17:36
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.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:022024-12-08 16:17:36
▦Diagram
changed
Baseline
DocMain (baseline)
Destination
DocMain (destination)
▶▦DocProtectionCharacteristicCurvei
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:53:062024-12-08 16:17:36
CHANGED{1CE4A273-E241-4659-BFF1-F18EF8DB1EE2}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:062024-12-08 16:17:36
▦Diagram
moved or resized
Baseline
DocProtectionCharacteristicCurve (baseline)
Destination
DocProtectionCharacteristicCurve (destination)
▶▦DocProtectionFunctionInheritance1i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:53:102024-12-08 16:17:36
CHANGED{AC6BF8BA-E146-42ff-B709-16F2054E8AFD}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:102024-12-08 16:17:36
▦Diagram
moved or resized
Baseline
DocProtectionFunctionInheritance1 (baseline)
Destination
DocProtectionFunctionInheritance1 (destination)
Connectors 4 labels movedhover a connector to outline the elements it joins
labels movedAutomationBlockGroup – FunctionBlock
labels movedAutomationFunction – AutomationBlockGroup
labels movedAutomationFunction – AutomationFunction
labels movedFunctionBlock – AutomationFunction
▶▦DocProtectionFunctionInheritance2i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:53:142024-12-08 16:17:36
CHANGED{B938F3F4-3A0A-4f13-AF78-806C55F0BC81}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:142024-12-08 16:17:36
▦Diagram
changed
Baseline
DocProtectionFunctionInheritance2 (baseline)
Destination
DocProtectionFunctionInheritance2 (destination)
▶▦DocProtectionFunctionInheritance3i
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:53:172024-12-08 16:17:36
CHANGED{E2177516-8145-4e9c-93D6-B56FBB650E6A}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:172024-12-08 16:17:36
▦Diagram
changed
Baseline
DocProtectionFunctionInheritance3 (baseline)
Destination
DocProtectionFunctionInheritance3 (destination)
▶▦DocProtectionFunctionLogicDescriptioni
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
ModifiedDate2024-12-06 19:53:212024-12-08 16:17:36
CHANGED{1896FFDF-EE51-49c6-8C5D-C17AA3255910}
Diagram notes
No notes defined in the model.
▤Metadata
BaselineDestination
ModifiedDate2024-12-06 19:53:212024-12-08 16:17:36
Diagram 'DocProtectionFunctionLogicDescription' has no other changes. The shows its notes and every changed property.
▶Supervisoryrenamed from SCADAi
Package notes (destination, redlined)
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. Contains entities to model information used for operational supervision, control, and data acquisition in power system applications function. Supervision involves real-time monitoring and decision support, enabling operator and automated control of equipment such as opening or closing a breaker. Data acquisition gathers real-time measurements from various sources, independent of the underlying communication technology.
Package metadata — changes
BaselineDestination
NameSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{C397A471-682D-4757-89C3-C65DCE1842A7}
Package notes (destination, redlined)
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. Contains entities to model information used for operational supervision, control, and data acquisition in power system applications function. Supervision involves real-time monitoring and decision support, enabling operator and automated control of equipment such as opening or closing a breaker. Data acquisition gathers real-time measurements from various sources, independent of the underlying communication technology.
Changed classes (7)
▶⚙CommunicationLinki
Class notes
The connection to remote units is through one or more communication links. Reduntant links may exist. The CommunicationLink class inherits PowerSystemResource. The intention is to allow CommunicationLinks to have Measurements. These Measurements can be used to model link status as operational, out of service, unit failure etc.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{7F2B8FC0-FCB8-4dfb-9C1C-AF982DA0ABCC}
Class notes
The connection to remote units is through one or more communication links. Reduntant links may exist. The CommunicationLink class inherits PowerSystemResource. The intention is to allow CommunicationLinks to have Measurements. These Measurements can be used to model link status as operational, out of service, unit failure etc.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
⇄Links
BaselineCommunicationLink role CommunicationLink [0..n] → BilateralExchangeActor role BilateralExchangeActor [0..1]
→
DestinationCommunicationLink role CommunicationLink [0..n0..*] → BilateralExchangeActor role BilateralExchangeActor [0..1]
Source end — CommunicationLink
BaselineDestination
Cardinality0..n0..*
Target end
no changes
▶⚙RemoteControli
Class notes
Remote controls are outputs that are sent by the remote unit to actuators in the process.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{5B096850-E749-4b88-AC9B-AB0EFD66A72F}
Class notes
Remote controls are outputs that are sent by the remote unit to actuators in the process.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'RemoteControl' has no other changes. The shows its notes and every changed property.
▶⚙RemotePointi
Class notes
For an RTU, remote points correspond to telemetered values or control outputs. Other units (e.g. control centres) usually also contain calculated values.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{4628091D-2315-459f-9E5F-2CFECA557F1C}
Class notes
For an RTU, remote points correspond to telemetered values or control outputs. Other units (e.g. control centres) usually also contain calculated values.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'RemotePoint' has no other changes. The shows its notes and every changed property.
▶⚙RemoteSourcei
Class notes
Remote sources are state variables that are telemetered or calculated within the remote unit.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{CC135E99-5C6E-41ad-8FE4-E7EBEC8E0D8C}
Class notes
Remote sources are state variables that are telemetered or calculated within the remote unit.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'RemoteSource' has no other changes. The shows its notes and every changed property.
▶⚙RemoteUniti
Class notes
A remote unit can be an RTU, IED, substation control system, control centre, etc. The communication with the remote unit can be through various standard protocols (e.g. IEC 61870, IEC 61850) or non standard protocols (e.g. DNP, RP570, etc.). A remote unit contains remote data points that might be telemetered, collected or calculated. The RemoteUnit class inherits PowerSystemResource. The intention is to allow RemoteUnits to have Measurements. These Measurements can be used to model unit status as operational, out of service, unit failure, etc.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{93AA36A5-8421-432f-89ED-64774D6A10A3}
Class notes
A remote unit can be an RTU, IED, substation control system, control centre, etc. The communication with the remote unit can be through various standard protocols (e.g. IEC 61870, IEC 61850) or non standard protocols (e.g. DNP, RP570, etc.). A remote unit contains remote data points that might be telemetered, collected or calculated. The RemoteUnit class inherits PowerSystemResource. The intention is to allow RemoteUnits to have Measurements. These Measurements can be used to model unit status as operational, out of service, unit failure, etc.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'RemoteUnit' has no other changes. The shows its notes and every changed property.
▶⚙RemoteUnitType«enumeration»i
Class notes
Type of remote unit.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{C956444A-A2E6-4f96-B6F0-DCCF81B934BF}
Class notes
Type of remote unit.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'RemoteUnitType' has no other changes. The shows its notes and every changed property.
▶⚙Source«enumeration»i
Class notes
Source gives information related to the origin of a value.
Class metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
Tagged values — changes
BaselineDestination
no changes
CHANGED{2DDE9E7D-6C38-4e8d-83FD-E0CE637A0E37}
Class notes
Source gives information related to the origin of a value.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
Class 'Source' has no other changes. The shows its notes and every changed property.
Changed diagrams (2)
▶▦DocDatatypesi
Diagram notes
Shows datatypes for SCADA model.
Diagram metadata — changes
BaselineDestination
ParentPackageSCADASupervisory
CHANGED{0B3B79B7-3576-4779-86CD-25393DC86CDF}
Diagram notes
Shows datatypes for SCADA model.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
▦Diagram
changed
Baseline
DocDatatypes (baseline)
Destination
DocDatatypes (destination)
▶▦DocSCADAi
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
ParentPackageSCADASupervisory
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.
▤Metadata
BaselineDestination
ParentPackageSCADASupervisory
▦Diagram
changed
Baseline
DocSCADA (baseline)
Destination
DocSCADA (destination)
▶ICCPConfigurationi
Package notes
This package models configuration of ICCP required for bilateral exchanges.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{423B82DE-E83D-40a8-A4C8-8EA08513C297}
Package notes
This package models configuration of ICCP required for bilateral exchanges.
Changed classes (1)
▶⚙BilateralExchangeActori
Class notes
BilateralExchangeActor describes an actor that provides ICCP data, consumes ICCP data or both. The ICCP data provider lists the data it makes available to an ICCP data consumer. This data is described by ProvidedBilateralPoints. The relation between an ICCP data provider and a consumer is established by a BilateralExchangeAgreement. It is up to the ICCP data consumer to select what ProvidedBilateralPoints to use. The selection made is not described in this information model.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{C4C36CA2-2418-4e2f-A0FD-F819DCBC8DE6}
Class notes
BilateralExchangeActor describes an actor that provides ICCP data, consumes ICCP data or both. The ICCP data provider lists the data it makes available to an ICCP data consumer. This data is described by ProvidedBilateralPoints. The relation between an ICCP data provider and a consumer is established by a BilateralExchangeAgreement. It is up to the ICCP data consumer to select what ProvidedBilateralPoints to use. The selection made is not described in this information model.
⇄Links
BaselineCommunicationLink role CommunicationLink [0..n] → BilateralExchangeActor role BilateralExchangeActor [0..1]
→
DestinationCommunicationLink role CommunicationLink [0..n0..*] → BilateralExchangeActor role BilateralExchangeActor [0..1]
Source end — CommunicationLink
BaselineDestination
Cardinality0..n0..*
Target end
no changes
Changed diagrams (2)
▶▦DocGenericBilateralExchangei
Diagram notes
Classes used to model bilateral ICCP exchange.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{0805DA3F-AF10-47ec-9559-F9FBA8892063}
Diagram notes
Classes used to model bilateral ICCP exchange.
▦Diagram
changed
Baseline
DocGenericBilateralExchange (baseline)
Destination
DocGenericBilateralExchange (destination)
Connectors 1 labels changedhover a connector to outline the elements it joins
labels changedCommunicationLink – BilateralExchangeActormultiplicity 0..n → 0..*
▶▦DocICCPi
Diagram notes
Classes used to model ICCP configuration.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{BFA123BC-1A2D-467d-93BA-F9A00DF00B6D}
Diagram notes
Classes used to model ICCP configuration.
▦Diagram
changed
Baseline
DocICCP (baseline)
Destination
DocICCP (destination)
Connectors 1 labels changedhover a connector to outline the elements it joins
labels changedCommunicationLink – BilateralExchangeActormultiplicity 0..n → 0..*
▶DocBasei
Package notes
This package contains example documentation diagrams not intended to be documented with the rest of the normative packages. The diagrams within this package are individually included in this document.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{9595963E-B478-4f81-8DE5-EBF73E630358}
Package notes
This package contains example documentation diagrams not intended to be documented with the rest of the normative packages. The diagrams within this package are individually included in this document.
Changed diagrams (1)
▶▦DocumentationExampleInheritancei
Diagram notes
This shows an example of inheritance in UML. This diagram is only to support figures in the documentation.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{8097D8D7-E05E-4885-982D-57E94DBA4BCD}
Diagram notes
This shows an example of inheritance in UML. This diagram is only to support figures in the documentation.
▦Diagram
changed
Baseline
DocumentationExampleInheritance (baseline)
Destination
DocumentationExampleInheritance (destination)
▶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). The information in the entire clause "Common Information Model Dynamics package" is reproduced from the UML with the permission of UCAIug.
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). The information in the entire clause "Common Information Model Dynamics package" is reproduced from the UML with the permission of UCAIug.
▶StandardInterconnectionsi
Package notes
This subclause describes the standard interconnections for various types of equipment. These interconnections are understood by the application programs and can be identified based on the presence of one of the key classes with a relationship to the static power flow model: SynchronousMachineDynamics, AsynchronousMachineDynamics, EnergyConsumerDynamics or WindTurbineType3or4Dynamics. The relationships between classes expressed in the interconnection diagrams are intended to support dynamic behaviour described by either standard models or user-defined models. In the interconnection diagrams, boxes which are black in colour represent function blocks whose functionality can be provided by one of many standard models or by a user-defined model. Blue boxes represent specific standard models. A dashed box means that the function block or specific standard model is optional.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{9E32B79D-9C05-4fe4-9518-A32B1C67637A}
Package notes
This subclause describes the standard interconnections for various types of equipment. These interconnections are understood by the application programs and can be identified based on the presence of one of the key classes with a relationship to the static power flow model: SynchronousMachineDynamics, AsynchronousMachineDynamics, EnergyConsumerDynamics or WindTurbineType3or4Dynamics. The relationships between classes expressed in the interconnection diagrams are intended to support dynamic behaviour described by either standard models or user-defined models. In the interconnection diagrams, boxes which are black in colour represent function blocks whose functionality can be provided by one of many standard models or by a user-defined model. Blue boxes represent specific standard models. A dashed box means that the function block or specific standard model is optional.
▶WindModelsi
Package notes
Standard interconnections included in this package are according to IEC 61400-27-1:2015.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{6319640C-8A7E-4aae-A1DA-A6DB83723377}
Package notes
Standard interconnections included in this package are according to IEC 61400-27-1:2015.
Changed diagrams (2)
▶▦StandardWindType1and2Interconnectioni
Diagram notes
This diagram shows the classes necessary for wind type 1 and type 2 interconnection models. Standard IEC wind turbines type 1 and 2 interconnection models all have a single instance of an AsynchronousMachineDynamics child class and a single instance of the WindGenTurbineType1aIEC class, the WindGenTurbineType1bIEC class, or the WindGenTurbineType2IEC class as appropriate. A valid IEC wind type 1A interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindAeroConstIEC; - WindProtectionIEC. A valid IEC wind type 1B interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindProtectionIEC; - WindPitchContPowerIEC. A valid IEC wind type 2 interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindContRotorRIEC; - WindProtectionIEC; - WindPitchContPowerIEC. The WindProtectionIEC class and the WindContRotorRIEC class use the WindDynamicsLookupTable class.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{92C68727-B7DF-4926-871E-3156A89CC82A}
Diagram notes
This diagram shows the classes necessary for wind type 1 and type 2 interconnection models. Standard IEC wind turbines type 1 and 2 interconnection models all have a single instance of an AsynchronousMachineDynamics child class and a single instance of the WindGenTurbineType1aIEC class, the WindGenTurbineType1bIEC class, or the WindGenTurbineType2IEC class as appropriate. A valid IEC wind type 1A interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindAeroConstIEC; - WindProtectionIEC. A valid IEC wind type 1B interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindProtectionIEC; - WindPitchContPowerIEC. A valid IEC wind type 2 interconnection model also shall have one instance of each of the following classes (and no others): - WindMechIEC; - WindContRotorRIEC; - WindProtectionIEC; - WindPitchContPowerIEC. The WindProtectionIEC class and the WindContRotorRIEC class use the WindDynamicsLookupTable class.
▦Diagram
changed
Baseline
StandardWindType1and2Interconnection (baseline)
Destination
StandardWindType1and2Interconnection (destination)
▶▦StandardWindType3and4Interconnectioni
Diagram notes
This diagram shows the classes necessary for wind type 3 and type 4 interconnection models, including the wind plant model. Standard IEC wind types 3, 4A, 4B and plant interconnection models all have a single instances as follows: IEC wind type 3: - WindTurbineType3IEC; - WindAeroOneDimIEC or WindAeroTwoDimIEC; - WindMechIEC; - WindGenType3aIEC or WindGenType3bIEC; - WindContPType3IEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindContPitchAngleIEC; - WindProtectionIEC. IEC wind type 4A: - WindTurbineType4aIEC; - WindGenType4IEC or WindGenType3aIEC; - WindContPType4aIEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindProtectionIEC. IEC wind type 4B: - WindTurbineType4bIEC; - WindMechIEC; - WindGenType4IEC or WindGenType3aIEC; - WindContPType4bIEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindProtectionIEC.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{0E374383-A1C7-4ecb-A4C4-5889C2D6D200}
Diagram notes
This diagram shows the classes necessary for wind type 3 and type 4 interconnection models, including the wind plant model. Standard IEC wind types 3, 4A, 4B and plant interconnection models all have a single instances as follows: IEC wind type 3: - WindTurbineType3IEC; - WindAeroOneDimIEC or WindAeroTwoDimIEC; - WindMechIEC; - WindGenType3aIEC or WindGenType3bIEC; - WindContPType3IEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindContPitchAngleIEC; - WindProtectionIEC. IEC wind type 4A: - WindTurbineType4aIEC; - WindGenType4IEC or WindGenType3aIEC; - WindContPType4aIEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindProtectionIEC. IEC wind type 4B: - WindTurbineType4bIEC; - WindMechIEC; - WindGenType4IEC or WindGenType3aIEC; - WindContPType4bIEC; - WindContQIEC; - WindContCurrLimIEC; - WindContQLimIEC or WindContQPQULimIEC; - WindProtectionIEC.
▦Diagram
changed
Baseline
StandardWindType3and4Interconnection (baseline)
Destination
StandardWindType3and4Interconnection (destination)
Package 'StandardInterconnections' has no changes to the 2 classes it contains.
Changed diagrams (4)
▶▦StandardAsynchronousMachineInterconnectioni
Diagram notes
This diagram shows the classes necessary for the asynchronous machine interconnection model. A standard asynchronous machine interconnection has a single instance of an AsynchronousMachineDynamics child class. A valid standard asynchronous machine interconnection model also reflects the following rules. It can have: - one instance of TurbineGovernorDynamics child class, but only if AsynchronousMachine.asynchronousMachineType = generator; - one instance of MechanicalLoadDynamics child class, but only if AsynchronousMachine.asynchronousMachineType = motor.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{EEC3EEE6-B14D-4a4d-ACA6-86603C0764C4}
Diagram notes
This diagram shows the classes necessary for the asynchronous machine interconnection model. A standard asynchronous machine interconnection has a single instance of an AsynchronousMachineDynamics child class. A valid standard asynchronous machine interconnection model also reflects the following rules. It can have: - one instance of TurbineGovernorDynamics child class, but only if AsynchronousMachine.asynchronousMachineType = generator; - one instance of MechanicalLoadDynamics child class, but only if AsynchronousMachine.asynchronousMachineType = motor.
▦Diagram
changed
Baseline
StandardAsynchronousMachineInterconnection (baseline)
Destination
StandardAsynchronousMachineInterconnection (destination)
▶▦StandardLoadInterconnectioni
Diagram notes
This diagram shows the classes necessary for a load interconnection model. A standard load interconnection model has a single instance of an EnergyConsumerDynamics child class plus a related instance of a LoadDynamics child class.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{33C2E7D0-74C1-41cc-A2D0-FD0D05FD9A07}
Diagram notes
This diagram shows the classes necessary for a load interconnection model. A standard load interconnection model has a single instance of an EnergyConsumerDynamics child class plus a related instance of a LoadDynamics child class.
▦Diagram
changed
Baseline
StandardLoadInterconnection (baseline)
Destination
StandardLoadInterconnection (destination)
▶▦StandardStaticVarCompensatorInterconnectioni
Diagram notes
This diagram shows the classes necessary for a static var compensator (SVC) interconnection model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{4EFB908C-5452-4b3b-A521-8C8B72F709CE}
Diagram notes
This diagram shows the classes necessary for a static var compensator (SVC) interconnection model.
▦Diagram
changed
Baseline
StandardStaticVarCompensatorInterconnection (baseline)
Destination
StandardStaticVarCompensatorInterconnection (destination)
▶▦StandardSynchronousMachineInterconnectioni
Diagram notes
This diagram shows the classes necessary for both of the two types of synchronous machine interconnection models: standard synchronous machine and standard synchronous generator cross-compound. A standard synchronous machine interconnection has a single instance of a SynchronousMachineDynamics child class whereas a generator cross-compound connection has multiple instances of SynchronousMachineDynamics child classes related by a single instance of a TurbineGovernorDynamics child class. A valid standard synchronous machine interconnection model reflects the following rules. - It can have: + one instance of TurbineGovernorDynamics child class, but only if SynchronousMachine.operatingMode = generator; + one instance of MechanicalLoadDynamics child class, but only if SynchronousMachine.operatingMode = motor or SynchronousMachine.operatingMode = condenser. - It cannot have any instance of GenICompensationForGenJ. A generator cross-compound interconnection model reflects the following rules. - It can have: + multiple instances of SynchronousMachineDynamics child classes, each of which has its related SynchronousMachine.operatingMode = generator; + one instance of TurbineGovernorDynamics child class. - It shall have two or more instances of GenICompensationForGenJ associated with each instance of a SynchronousMachineDynamics child class.
Diagram metadata — changes
BaselineDestination
ModifiedDate2022-03-18 21:36:042026-02-02 21:24:21
CHANGED{EC9A727C-9695-44d0-BDFE-9C76CF1CF162}
Diagram notes
This diagram shows the classes necessary for both of the two types of synchronous machine interconnection models: standard synchronous machine and standard synchronous generator cross-compound. A standard synchronous machine interconnection has a single instance of a SynchronousMachineDynamics child class whereas a generator cross-compound connection has multiple instances of SynchronousMachineDynamics child classes related by a single instance of a TurbineGovernorDynamics child class. A valid standard synchronous machine interconnection model reflects the following rules. - It can have: + one instance of TurbineGovernorDynamics child class, but only if SynchronousMachine.operatingMode = generator; + one instance of MechanicalLoadDynamics child class, but only if SynchronousMachine.operatingMode = motor or SynchronousMachine.operatingMode = condenser. - It cannot have any instance of GenICompensationForGenJ. A generator cross-compound interconnection model reflects the following rules. - It can have: + multiple instances of SynchronousMachineDynamics child classes, each of which has its related SynchronousMachine.operatingMode = generator; + one instance of TurbineGovernorDynamics child class. - It shall have two or more instances of GenICompensationForGenJ associated with each instance of a SynchronousMachineDynamics child class.
▤Metadata
BaselineDestination
ModifiedDate2022-03-18 21:36:042026-02-02 21:24:21
▦Diagram
addedchangedmoved or resized
Baseline
StandardSynchronousMachineInterconnection (baseline)
Destination
StandardSynchronousMachineInterconnection (destination)
Connectors 2 added · 1 labels movedhover a connector to outline the elements it joins
addedStatorCurrentLimiterDynamics – DynamicsFunctionBlock
addedStatorCurrentLimiterDynamics – ExcitationSystemDynamics
labels movedVoltageCompensatorDynamics – ExcitationSystemDynamics
▶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.
Changed classes (1)
▶⚙SynchronousMachineDetailedi
Class notes
All synchronous machine detailed types use a subset of the same data parameters and input/output variables. The several variations differ in the following ways: - the number of equivalent windings that are included; - the way in which saturation is incorporated into the model; - whether or not “subtransient saliency” (<i>X''q</i> not = <i>X''d</i>) is represented. It is not necessary for each simulation tool to have separate models for each of the model types. The same model can often be used for several types by alternative logic within the model. Also, differences in saturation representation might not result in significant model performance differences so model substitutions are often acceptable.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{B272216C-A098-436d-80C8-02AD11F5B97F}
Class notes
All synchronous machine detailed types use a subset of the same data parameters and input/output variables. The several variations differ in the following ways: - the number of equivalent windings that are included; - the way in which saturation is incorporated into the model; - whether or not “subtransient saliency” (<i>X''q</i> not = <i>X''d</i>) is represented. It is not necessary for each simulation tool to have separate models for each of the model types. The same model can often be used for several types by alternative logic within the model. Also, differences in saturation representation might not result in significant model performance differences so model substitutions are often acceptable.
≡Attributes
AttributeBaselineDestinationNotes (destination, redlined)
saturationFactor120i{E4937370-1EC7-4358-8FC2-3A6D3AF17808}show detailsFloat [0..1]Float [0..1]Saturation factor at 120 % of rated terminal voltage (<i>S12</i>) (>= RotatingMachineDynamicsSynchronousMachineDetailed.saturationFactor). Defined by <i>S</i>(<i>E2</i>) in the SynchronousMachineSaturationParameters diagram. Typical value = 0,12.
Attribute notes (destination, redlined)
Saturation factor at 120 % of rated terminal voltage (<i>S12</i>) (>= RotatingMachineDynamicsSynchronousMachineDetailed.saturationFactor). Defined by <i>S</i>(<i>E2</i>) in the SynchronousMachineSaturationParameters diagram. Typical value = 0,12.
Attribute metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
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
ModifiedDate2022-03-18 21:42:002026-02-02 20:43:14
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.
▤Metadata
BaselineDestination
ModifiedDate2022-03-18 21:42:002026-02-02 20:43:14
▦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.
Changed classes (1)
▶⚙AsynchronousMachineTimeConstantReactancei
Class notes (destination, redlined)
Parameter details: <ol> <li>If <i>X'' </i>=<i> X'</i>, a single cage (one equivalent rotor winding per axis) is modelled.</li> <li>The “<i>p</i>” in the attribute names is a substitution for a “prime” in the usual parameter notation, e.g. <i>tpo</i> refers to <i>T'o</i>.</li> </ol> The parameters used for models expressed in time constant reactance form include: - RotatingMachine.ratedS (<i>MVAbase</i>); - RotatingMachineDynamics.damping (<i>D</i>); - RotatingMachineDynamics.inertia (<i>H</i>); - RotatingMachineDynamics.saturationFactor (<i>S1</i>); - RotatingMachineDynamics.saturationFactor120 (<i>S12</i>); - RotatingMachineDynamics.statorLeakageReactance (<i>Xl</i>); - RotatingMachineDynamics.statorResistance (<i>Rs</i>); - .xs (<i>Xs</i>); - .xp (<i>X'</i>); - .xpp (<i>X''</i>); - .tpo (<i>T'o</i>); - .tppo (<i>T''o</i>).
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{20220E3A-DD4F-41fc-B00D-188C7FDCE8D9}
Class notes (destination, redlined)
Parameter details: <ol> <li>If <i>X'' </i>=<i> X'</i>, a single cage (one equivalent rotor winding per axis) is modelled.</li> <li>The “<i>p</i>” in the attribute names is a substitution for a “prime” in the usual parameter notation, e.g. <i>tpo</i> refers to <i>T'o</i>.</li> </ol> The parameters used for models expressed in time constant reactance form include: - RotatingMachine.ratedS (<i>MVAbase</i>); - RotatingMachineDynamics.damping (<i>D</i>); - RotatingMachineDynamics.inertia (<i>H</i>); - RotatingMachineDynamics.saturationFactor (<i>S1</i>); - RotatingMachineDynamics.saturationFactor120 (<i>S12</i>); - RotatingMachineDynamics.statorLeakageReactance (<i>Xl</i>); - RotatingMachineDynamics.statorResistance (<i>Rs</i>); - .xs (<i>Xs</i>); - .xp (<i>X'</i>); - .xpp (<i>X''</i>); - .tpo (<i>T'o</i>); - .tppo (<i>T''o</i>).
Class 'AsynchronousMachineTimeConstantReactance' has no other changes. The shows its notes and every changed property.
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
ModifiedDate2022-03-18 21:47:022026-02-02 20:50:36
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.
▤Metadata
BaselineDestination
ModifiedDate2022-03-18 21:47:022026-02-02 20:50:36
▦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 58 classes it contains.
Changed diagrams (3)
▶▦GasTurbineGovernorDynamicsi
Diagram notes
This diagram shows dynamic standard model gaz turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3639F204-9BE3-448b-A437-52099DA95456}
Diagram notes
This diagram shows dynamic standard model gaz turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
▦Diagram
changed
Baseline
GasTurbineGovernorDynamics (baseline)
Destination
GasTurbineGovernorDynamics (destination)
▶▦HydroTurbineGovernorDynamicsi
Diagram notes
This diagram shows dynamic standard model hydro turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{5DD835FF-3AB1-450d-9050-A786FC349923}
Diagram notes
This diagram shows dynamic standard model hydro turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
▦Diagram
changed
Baseline
HydroTurbineGovernorDynamics (baseline)
Destination
HydroTurbineGovernorDynamics (destination)
▶▦SteamTurbineGovernorDynamicsi
Diagram notes
This diagram shows dynamic standard model steam 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 steam turbine-governor classes and their inheritance from the TurbineGovernorDynamics class.
▦Diagram
changed
Baseline
SteamTurbineGovernorDynamics (baseline)
Destination
SteamTurbineGovernorDynamics (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 Annex E of 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 Annex E of 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.
Changed classes (1)
▶⚙ExcitationSystemDynamicsi
Class notes
Excitation system function block whose behaviour is described by reference to a standard model <font color="#0f0f0f">or by definition of a user-defined model.</font>
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{F119E4EC-2DC8-4801-B68B-A282AF621324}
Class notes
Excitation system function block whose behaviour is described by reference to a standard model <font color="#0f0f0f">or by definition of a user-defined model.</font>
⇄Links
BaselineVoltageCompensatorDynamics role VoltageCompensatorDynamics [1] → ExcitationSystemDynamics role ExcitationSystemDynamics [1]
→
DestinationVoltageCompensatorDynamics role VoltageCompensatorDynamics [10..1] → ExcitationSystemDynamics role ExcitationSystemDynamics [1]
Source end — VoltageCompensatorDynamics
BaselineDestination
Cardinality10..1
Target end
no changes
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 10 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 7 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 26 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 and IEEE 421.5-2016, 14.</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 and IEEE 421.5-2016, 14.</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> The signal excitation limiter status should come from the excitation systems.<font color="#0f0f0f"> </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11 and IEEE 421.5-2016, 13.</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> The signal excitation limiter status should come from the excitation systems.<font color="#0f0f0f"> </font> <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11 and IEEE 421.5-2016, 13.</font>
Package 'PFVArControllerType1Dynamics' has no changes to the 5 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)
▶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> The signal excitation limiter status should come from the excitation systems <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11 and IEEE 421.5-2016, 13.</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> The signal excitation limiter status should come from the excitation systems <font color="#0f0f0f">For additional information please refer to IEEE 421.5-2005, 11 and IEEE 421.5-2016, 13.</font> <font color="#0f0f0f"> </font>
Package 'PFVArControllerType2Dynamics' has no changes to the 6 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)
▶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 3 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)
▶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 and IEEE 421.5-2016, 5.</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 and IEEE 421.5-2016, 5.</font> <font color="#0f0f0f"> </font>
Changed classes (1)
▶⚙VoltageCompensatorDynamicsi
Class notes
Voltage compensator function block whose behaviour is described by reference to a standard model <font color="#0f0f0f">or by definition of a user-defined model.</font>
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{E0CF51AF-D694-4e22-8FBA-9E7B9A78FA31}
Class notes
Voltage compensator function block whose behaviour is described by reference to a standard model <font color="#0f0f0f">or by definition of a user-defined model.</font>
⇄Links
BaselineVoltageCompensatorDynamics role VoltageCompensatorDynamics [1] → ExcitationSystemDynamics role ExcitationSystemDynamics [1]
→
DestinationVoltageCompensatorDynamics role VoltageCompensatorDynamics [10..1] → ExcitationSystemDynamics role ExcitationSystemDynamics [1]
Source end — VoltageCompensatorDynamics
BaselineDestination
Cardinality10..1
Target end
no changes
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)
▶LoadDynamicsi
Package notes
Dynamic load models are used to represent the dynamic real and reactive load behaviour of a load from the static power flow model. Dynamic load models can be defined as applying either to a single load (energy consumer) or to a group of energy consumers. Large industrial motors or groups of similar motors can be represented by a synchronous machine model (SynchronousMachineDynamics) or an asynchronous machine model (AsynchronousMachineDynamics), which are usually represented as generators with negative active power output in the static (power flow) data.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{4B245477-75CE-4d8d-BBFE-0471D2D7A63D}
Package notes
Dynamic load models are used to represent the dynamic real and reactive load behaviour of a load from the static power flow model. Dynamic load models can be defined as applying either to a single load (energy consumer) or to a group of energy consumers. Large industrial motors or groups of similar motors can be represented by a synchronous machine model (SynchronousMachineDynamics) or an asynchronous machine model (AsynchronousMachineDynamics), which are usually represented as generators with negative active power output in the static (power flow) data.
Package 'LoadDynamics' has no changes to the 8 classes it contains.
Changed diagrams (1)
▶▦LoadDynamicsi
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to modelling of load for dynamics. An association between the EnergyConsumerDynamics class and the EnergyConsumer class provides a means for relating the dynamics model to the static model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{B8726148-86EB-4fef-BF84-CD31B15B3DD8}
Diagram notes
This diagram shows static power system model classes and dynamics model classes related to modelling of load for dynamics. An association between the EnergyConsumerDynamics class and the EnergyConsumer class provides a means for relating the dynamics model to the static model.
▦Diagram
changed
Baseline
LoadDynamics (baseline)
Destination
LoadDynamics (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 4 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 6 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)
▶ShuntCompensatorDynamicsi
Package notes
Shunt compensator dynamics models.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{18A7B5F9-12C2-4073-A382-477CC64A3B54}
Package notes
Shunt compensator dynamics models.
Package 'ShuntCompensatorDynamics' has no changes to the 1 classes it contains.
Changed diagrams (1)
▶▦ShuntCompensatorDynamicsi
Diagram notes
This diagram shows the dynamics model classes related to modelling of the shunt compensator models.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{45969194-3222-46b2-8857-D0136EDA95F6}
Diagram notes
This diagram shows the dynamics model classes related to modelling of the shunt compensator models.
▦Diagram
changed
Baseline
ShuntCompensatorDynamics (baseline)
Destination
ShuntCompensatorDynamics (destination)
▶StatcomDynamicsi
Package notes
STATCOM models.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{5AD5A535-9FB0-44fb-A314-694B39EEE13C}
Package notes
STATCOM models.
Package 'StatcomDynamics' has no changes to the 2 classes it contains.
Changed diagrams (1)
▶▦StatcomDynamicsi
Diagram notes
This diagram shows the dynamics model classes related to modelling of the STATCOM models.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{A998EE9B-CBD5-486f-AA2A-9D8C5A945295}
Diagram notes
This diagram shows the dynamics model classes related to modelling of the STATCOM models.
▦Diagram
changed
Baseline
StatcomDynamics (baseline)
Destination
StatcomDynamics (destination)
▶WECCDynamicsi
Package notes
This subclause contains WECC dynamics models.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{979495FD-1EE1-43c7-879D-50024B1F055B}
Package notes
This subclause contains WECC dynamics models.
Package 'WECCDynamics' has no changes to the 28 classes it contains.
Changed diagrams (1)
▶▦WeccDynamicsi
Diagram notes
This diagram contains WECC dynamics models.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3B1CB32E-892D-454a-8128-64FD2C4499AF}
Diagram notes
This diagram contains WECC dynamics models.
▦Diagram
changed
Baseline
WeccDynamics (baseline)
Destination
WeccDynamics (destination)
▶IEEE1547Dynamicsi
Package notes
This clause contains IEEE 1547-2018 dynamics models. The IEEE 1547-2018 standard models advanced features on DER, like smart features to solar Photovoltaic (PV) inverters. Smart solar PV inverter features comprise, at minimum, the following: voltage ride-through, frequency ride-through, voltage support, frequency support, and ramp rates. Both voltage and frequency support can be achieved by various means. These features can minimize solar PV inverters generation potential negative impacts due to remote or local system grid events, voltage and/or frequency. The IEEE 1547-2018 standard enables new DER to have the capabilities for grid-supportive functionality, and the applicable authorities governing interconnection requirements can utilize these advanced features to provide more reliable and resilient energy to their customers as the power system continues to evolve. More details are available in the IEEE standard and IEEE Technical report PES-TR67.r1, 2020.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{A09B5CEC-743C-4cfb-B78F-2A74FA4B121D}
Package notes
This clause contains IEEE 1547-2018 dynamics models. The IEEE 1547-2018 standard models advanced features on DER, like smart features to solar Photovoltaic (PV) inverters. Smart solar PV inverter features comprise, at minimum, the following: voltage ride-through, frequency ride-through, voltage support, frequency support, and ramp rates. Both voltage and frequency support can be achieved by various means. These features can minimize solar PV inverters generation potential negative impacts due to remote or local system grid events, voltage and/or frequency. The IEEE 1547-2018 standard enables new DER to have the capabilities for grid-supportive functionality, and the applicable authorities governing interconnection requirements can utilize these advanced features to provide more reliable and resilient energy to their customers as the power system continues to evolve. More details are available in the IEEE standard and IEEE Technical report PES-TR67.r1, 2020.
Package 'IEEE1547Dynamics' has no changes to the 18 classes it contains.
Changed diagrams (1)
▶▦IEEE1547Dynamicsi
Diagram notes
This diagram contains IEEE 1547-2018 dynamics models.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{BB05C937-26D8-4a98-BFE3-025B228DDF1C}
Diagram notes
This diagram contains IEEE 1547-2018 dynamics models.
▦Diagram
changed
Baseline
IEEE1547Dynamics (baseline)
Destination
IEEE1547Dynamics (destination)
Package 'StandardModels' has no changes to the 2 classes it contains.
▶SimulationResulti
Package notes
This clause contains classes needed to describe dynamics simulation settings and results.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{F46BFE09-1F7D-4908-90ED-4A9799CF92B0}
Package notes
This clause contains classes needed to describe dynamics simulation settings and results.
Package 'SimulationResult' has no changes to the 14 classes it contains.
Changed diagrams (1)
▶▦SimulationResulti
Diagram notes
The diagram presents the classes used in the part of the model used to exchange dynamics simulation results.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3B18EC92-2D46-4747-85A5-7D1957304C6D}
Diagram notes
The diagram presents the classes used in the part of the model used to exchange dynamics simulation results.
▦Diagram
changed
Baseline
SimulationResult (baseline)
Destination
SimulationResult (destination)
▶InfGridi
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. It should not be used to generate any formal documentation as this is an informative portion of the model. All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
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. It should not be used to generate any formal documentation as this is an informative portion of the model. All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
▶InfExtEUNetworkCodesi
Package notes
Extensions approved ny ENTSO-E on 10 May 2023 as part of the Network Codes related work, so called Network Codes extensions and profiles. All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{56A4E199-F4A6-4a6f-8DB7-B1A9E475213B}
Package notes
Extensions approved ny ENTSO-E on 10 May 2023 as part of the Network Codes related work, so called Network Codes extensions and profiles. All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
▶ExtNetworkCodesi
Package notes
This package contains the extensions defined for the need of Network codes (NC) data exchanges.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{87163B9E-DAB8-4fef-AC8B-445DA4276796}
Package notes
This package contains the extensions defined for the need of Network codes (NC) data exchanges.
▶ExtAreai
Package notes
This package contains the extensions related to the areas.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{50F54530-FF88-4cc0-83FB-47DCD4A05B46}
Package notes
This package contains the extensions related to the areas.
Package 'ExtArea' has no changes to the 20 classes it contains.
Changed diagrams (1)
▶▦ExtEnergyAreai
Diagram notes
The diagram contains classes related to energy area.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{FFBF0C30-2B65-45a5-84C6-10D14BA56470}
Diagram notes
The diagram contains classes related to energy area.
▦Diagram
changed
Baseline
ExtEnergyArea (baseline)
Destination
ExtEnergyArea (destination)
▶ExtPowerShiftKeyi
Package notes
This package contains the extensions related to the generation and load shift keys (GLSKs).
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{8B666B78-C9A2-4a77-9992-219AB8F4BE61}
Package notes
This package contains the extensions related to the generation and load shift keys (GLSKs).
Package 'ExtPowerShiftKey' has no changes to the 13 classes it contains.
Changed diagrams (6)
▶▦ExtBiddingZonei
Diagram notes
The diagram contains classes related to bidding zone.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{927D0AB9-2114-44de-AE65-BEB4F321695E}
Diagram notes
The diagram contains classes related to bidding zone.
▦Diagram
changed
Baseline
ExtBiddingZone (baseline)
Destination
ExtBiddingZone (destination)
▶▦ExtEnergyComponenti
Diagram notes
The diagram contains classes related to GLSK.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{71A48C84-1525-4bbf-9BC3-2FAEF3C391C0}
Diagram notes
The diagram contains classes related to GLSK.
▦Diagram
removedchanged
Baseline
ExtEnergyComponent (baseline)
Destination
ExtEnergyComponent (destination)
Connectors 4 removedhover a connector to outline the elements it joins
removedEnergyConsumer – ExtEnergyConsumer
removedGeneratingUnit – ExtGeneratingUnit
removedHydroPump – ExtHydroPump
removedPowerElectronicsUnit – ExtPowerElectronicsUnit
▶▦ExtPowerElectronicsi
Diagram notes
The diagram contains classes related to power electronics.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{0E247B0E-B12D-455b-BB19-8FD708508A3E}
Diagram notes
The diagram contains classes related to power electronics.
▦Diagram
removedchanged
Baseline
ExtPowerElectronics (baseline)
Destination
ExtPowerElectronics (destination)
Connectors 1 removedhover a connector to outline the elements it joins
removedPowerElectronicsUnit – ExtPowerElectronicsUnit
▶▦ExtPowerShiftKeyi
Diagram notes
The diagram contains classes related to GLSK schedule.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{C5B49A74-A676-4439-937E-64F1C5BA66C2}
Diagram notes
The diagram contains classes related to GLSK schedule.
▦Diagram
changed
Baseline
ExtPowerShiftKey (baseline)
Destination
ExtPowerShiftKey (destination)
▶▦ExtPowerShiftKeyDistributioni
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{E0536000-7ED2-4870-B61F-93347898F316}
Diagram notes
No notes defined in the model.
▦Diagram
changed
Baseline
ExtPowerShiftKeyDistribution (baseline)
Destination
ExtPowerShiftKeyDistribution (destination)
▶▦ExtScheduleResourcei
Diagram notes
The diagram contains classes related to schedule resource.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{F2F179F0-28B8-4cd3-A238-B5D41060CC31}
Diagram notes
The diagram contains classes related to schedule resource.
▦Diagram
changed
Baseline
ExtScheduleResource (baseline)
Destination
ExtScheduleResource (destination)
▶ExtObjectRegistryi
Package notes
This package contains the extensions related to the object registry.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{E32C1533-1D51-45d4-BC05-394688598E18}
Package notes
This package contains the extensions related to the object registry.
Package 'ExtObjectRegistry' has no changes to the 5 classes it contains.
Changed diagrams (1)
▶▦ExtObjectRegistryi
Diagram notes
The diagram contains classes related to the object registry extension.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{2FD38458-3E6B-4dd3-88C4-F7140BF9626F}
Diagram notes
The diagram contains classes related to the object registry extension.
▦Diagram
changed
Baseline
ExtObjectRegistry (baseline)
Destination
ExtObjectRegistry (destination)
Connectors 1 labels changedhover a connector to outline the elements it joins
labels changedName – NameTyperole name Name → Names
▶ExtRemedialActioni
Package notes
This package contains the extensions related to the remedial action.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{93850D50-740E-4bab-B4BF-C14A90688DA0}
Package notes
This package contains the extensions related to the remedial action.
Package 'ExtRemedialAction' has no changes to the 56 classes it contains.
Changed diagrams (2)
▶▦GridStateAlterationPart1i
Diagram notes
This diagram contains extended classes for the purpose of the remedial action data exchange.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{334FA661-A972-4248-8459-DD53CED813C4}
Diagram notes
This diagram contains extended classes for the purpose of the remedial action data exchange.
▦Diagram
changed
Baseline
GridStateAlterationPart1 (baseline)
Destination
GridStateAlterationPart1 (destination)
▶▦GridStateAlterationPart2i
Diagram notes
This diagram contains extended classes for the purpose of the remedial action data exchange.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{5EB152ED-F7A1-4e55-AC72-AF472974E2BC}
Diagram notes
This diagram contains extended classes for the purpose of the remedial action data exchange.
▦Diagram
changed
Baseline
GridStateAlterationPart2 (baseline)
Destination
GridStateAlterationPart2 (destination)
▶ExtSchedulei
Package notes
This package contains the extensions related to the schedule.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{F7770C9A-4F37-45d0-B44B-846FADA47DBC}
Package notes
This package contains the extensions related to the schedule.
Package 'ExtSchedule' has no changes to the 115 classes it contains.
Changed diagrams (6)
▶▦ExtMustRunSchedulei
Diagram notes
The diagram contains classes related to must run schedule.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{E9EE39DD-2FB7-42a0-BDAF-46179F9BC3CB}
Diagram notes
The diagram contains classes related to must run schedule.
▦Diagram
changed
Baseline
ExtMustRunSchedule (baseline)
Destination
ExtMustRunSchedule (destination)
▶▦ExtPowerSchedulei
Diagram notes
The diagram contains classes related to schedule.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{FEF02341-6A06-4969-850E-D1B2482AB39F}
Diagram notes
The diagram contains classes related to schedule.
▦Diagram
changed
Baseline
ExtPowerSchedule (baseline)
Destination
ExtPowerSchedule (destination)
▶▦ExtPowerShiftKeySchedulei
Diagram notes
The diagram contains classes related to GLSK schedule.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{784E0AC3-1FCA-4473-B001-2B14311C8D8D}
Diagram notes
The diagram contains classes related to GLSK schedule.
▦Diagram
changed
Baseline
ExtPowerShiftKeySchedule (baseline)
Destination
ExtPowerShiftKeySchedule (destination)
▶▦ExtRegularSchedulei
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{255597F5-B1F0-43a4-AB5B-4878228ACF85}
Diagram notes
No notes defined in the model.
▦Diagram
changed
Baseline
ExtRegularSchedule (baseline)
Destination
ExtRegularSchedule (destination)
▶▦ExtSSHIrregularSchedulei
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{15A3EC50-A9E3-4d86-AB4C-5A0A3FB215D9}
Diagram notes
No notes defined in the model.
▦Diagram
changed
Baseline
ExtSSHIrregularSchedule (baseline)
Destination
ExtSSHIrregularSchedule (destination)
▶▦ExtSSHRegularSchedulei
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{88796D31-00FD-4638-80B1-E33FBE45CC3D}
Diagram notes
No notes defined in the model.
▦Diagram
changed
Baseline
ExtSSHRegularSchedule (baseline)
Destination
ExtSSHRegularSchedule (destination)
Package 'ExtNetworkCodes' has no changes to the 1 classes it contains.
▶ExtHeaderMetadatai
Package notes
This package contains the extensions defined for the need of header and metadata.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{603E96F8-AA94-4235-AB77-1934F48D4194}
Package notes
This package contains the extensions defined for the need of header and metadata.
Package 'ExtHeaderMetadata' has no changes to the 2 classes it contains.
Changed diagrams (1)
▶▦ExtHeaderMetadatai
Diagram notes
The diagram contains classes related to header metadata in compact form.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{3F85DA74-85C0-493e-B9E6-82EAA549F759}
Diagram notes
The diagram contains classes related to header metadata in compact form.
▦Diagram
changed
Baseline
ExtHeaderMetadata (baseline)
Destination
ExtHeaderMetadata (destination)
Package 'InfExtEUNetworkCodes' has no changes to the 1 diagrams it contains.
▶DocExtGridi
Package notes
All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{87BF140B-6CF8-43f6-9C7B-B6DBDBA9C10E}
Package notes
All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
Changed diagrams (2)
▶▦ConnectivityNodeContainmenti
Diagram notes
This diagram shows the allowed container of ConnectivityNode-s.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{AE187CCD-34D7-4fdb-A27C-B74407DF0828}
Diagram notes
This diagram shows the allowed container of ConnectivityNode-s.
▦Diagram
changed
Baseline
ConnectivityNodeContainment (baseline)
Destination
ConnectivityNodeContainment (destination)
▶▦EMFIPi
Diagram notes
No notes defined in the model.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{A3923AC5-4D07-44b7-B262-CA1282ECB554}
Diagram notes
No notes defined in the model.
▦Diagram
changed
Baseline
EMFIP (baseline)
Destination
EMFIP (destination)
▶Metadatai
Package notes
All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
Package metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
{500389E9-5C8C-40f4-9EB4-19613576509E}
Package notes
All informative UML modelling that is contained within the Informative packages (packages beginning with Inf*) is considered work under development and is subject to change or removal at any time. Therefore, this content should be used at your own risk. Users are encouraged to participate in and/or submit use cases to the respective UCA Task Force for additions and/or features not yet covered by the CIM.
▶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.
Package 'GenericDataSet' has no changes to the 10 classes it contains.
Changed diagrams (1)
▶▦GenericDataSeti
Diagram notes
Shows the generic dataset core classes.
Diagram metadata — changes
BaselineDestination
no changes
CHANGED{A5A07B09-93CB-423d-8595-8653C21E725B}
Diagram notes
Shows the generic dataset core classes.
▦Diagram
changed
Baseline
GenericDataSet (baseline)
Destination
GenericDataSet (destination)
▶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 'InfGrid' has no changes to the 1 diagrams it contains.
Changed classes (1)
▶⚙GridCIMVersioni
Class notes
This is the release version number assigned to Grid part of the CIM model. It is a point-in-time snapshot of the state of the CIM UML model that reflects a formal release of the CIM. This release version is distinct from the unique version (e.g. http://ucaiug.org/CIM/Base/1.0) associated with each package in the UML.
Class metadata — changes
BaselineDestination
no changes
Tagged values — changes
BaselineDestination
no changes
CHANGED{990AB50C-5CF8-46d2-B5FF-887BBBD3346F}
Class notes
This is the release version number assigned to Grid part of the CIM model. It is a point-in-time snapshot of the state of the CIM UML model that reflects a formal release of the CIM. This release version is distinct from the unique version (e.g. http://ucaiug.org/CIM/Base/1.0) associated with each package in the UML.
≡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
Default2025-01-222025-04-07
Tagged values — changes
BaselineDestination
no changes
versionimetadata changed - hovermetadata changed{B4E0B1B6-8794-406a-A4C6-CBB395E37A52}show detailsString [0..1]String [0..1]Form is XXvYY where XX is the major CIM release version and the YY is the minor version. For example 18v03.
Attribute notes
Form is XXvYY where XX is the major CIM release version and the YY is the minor version. For example 18v03.
Attribute metadata — changes
BaselineDestination
Default18v1518v16
Tagged values — changes
BaselineDestination
no changes
Changed diagrams (1)
▶▦BaseDependenciesi
Diagram notes
This diagram shows all base packages and their logical dependencies.
Diagram metadata — changes
BaselineDestination
ModifiedDate2025-01-22 17:14:332025-01-22 22:27:40
CHANGED{FB07D92D-5F4D-4fdc-AD82-2376FAF51037}
Diagram notes
This diagram shows all base packages and their logical dependencies.
▤Metadata
BaselineDestination
ModifiedDate2025-01-22 17:14:332025-01-22 22:27:40
▦Diagram
moved or resized
Baseline
BaseDependencies (baseline)
Destination
BaseDependencies (destination)
Connectors 1 reroutedhover a connector to outline the elements it joins
rerouted(not in this model) – (not in this model)