61970-301©1EC:2003 -26- 4.6.1.2 Changes to the CIM Standards Documents From a documentation perspective,when the CIM is extended,a decision must be made whether the changes constitute updates to existing CIM standards documents,or whether a new Part 3xx specification is required.In either case,the extensions will then become part of the IEC standard CIM 4.6.2 CIM Profiles An implementation of the CIM need not include all classes,attributes,or associations in the standard CIM specification to be compliant with the CIM standard.Profiles may be defined to specify which elements must be included (i.e.,mandatory elements)in a particular use of the CIM,as well as which are optional.These profiles will are defined in the Part 4xx series of standards An example is the profile for exchanging power system models,which is the subject of the draft Part 408 CIM Model Exchange Specification.This document specifies how the CIM is to be used for exchanging power system models in XML,and also specifies the mandatory and optional classes,attributes,and associations to be supported for this use of the CIM as required by NERC (North American Electric Reliability Council).The CIM version 10 ROSE model includes this profile information in the form of a special tab labeled "CIM"in the specification for each class, attribute,and association to indicate if the item is included or not in this profile.Under this tab for a given item is a list of the profiles currently defined and the value assigned to that item (i.e., included or not in the identified profile).For example,in the Measurement class,there is one entry "NercProfile"with the value "True",indicating that this class is mandatory for exchanging power system models that are based on the NERC Profile specification.As new profiles are defined,entries can be made for them as well. 4.7 User Implementation Conventions This section provides recommended user conventions when using the CIM in actual system implementations. 4.7.1 Naming The Naming class contained in the Core package is inherited by all PowerSystemResource classes.This class contains four attributes to be used for naming all PowerSystemResource objects.It is intended that values should be assigned to each attribute in a manner consistent with the attribute definitions The following are definitions and conventions recommended for naming attributes of PowerSystemResource classes: name:A local short name of the instance.Objects that are structured in a containment hierarchy have this name local to each level in the hierarchy.The name must be unique among objects contained by the same parent. pathName:Objects that are structured in a containment hierarchy have a pathName. The pathName is a concatenation of all names from each container,i.e.,from the leaf object up to the root of the containment hierarchy,similar to a file path name.For example,if node "A"contains node "B"that contains node "C",then the pathName for node "C"may look like "A.B.C".The type of delimiters used between names is not specified but is a local implementation issue. aliasName:A free text name of the instance.This attribute can also be used for localization description:A free format description of the instance
61970-301 IEC:2003 – 26 – 4.6.1.2 Changes to the CIM Standards Documents From a documentation perspective, when the CIM is extended, a decision must be made whether the changes constitute updates to existing CIM standards documents, or whether a new Part 3xx specification is required. In either case, the extensions will then become part of the IEC standard CIM. 4.6.2 CIM Profiles An implementation of the CIM need not include all classes, attributes, or associations in the standard CIM specification to be compliant with the CIM standard. Profiles may be defined to specify which elements must be included (i.e., mandatory elements) in a particular use of the CIM, as well as which are optional. These profiles will are defined in the Part 4xx series of standards. An example is the profile for exchanging power system models, which is the subject of the draft Part 408 CIM Model Exchange Specification. This document specifies how the CIM is to be used for exchanging power system models in XML, and also specifies the mandatory and optional classes, attributes, and associations to be supported for this use of the CIM as required by NERC (North American Electric Reliability Council). The CIM version 10 ROSE model includes this profile information in the form of a special tab labeled “CIM” in the specification for each class, attribute, and association to indicate if the item is included or not in this profile. Under this tab for a given item is a list of the profiles currently defined and the value assigned to that item (i.e., included or not in the identified profile). For example, in the Measurement class, there is one entry “NercProfile” with the value “True”, indicating that this class is mandatory for exchanging power system models that are based on the NERC Profile specification. As new profiles are defined, entries can be made for them as well. 4.7 User Implementation Conventions This section provides recommended user conventions when using the CIM in actual system implementations. 4.7.1 Naming The Naming class contained in the Core package is inherited by all PowerSystemResource classes. This class contains four attributes to be used for naming all PowerSystemResource objects. It is intended that values should be assigned to each attribute in a manner consistent with the attribute definitions. The following are definitions and conventions recommended for naming attributes of PowerSystemResource classes: - name: A local short name of the instance. Objects that are structured in a containment hierarchy have this name local to each level in the hierarchy. The name must be unique among objects contained by the same parent. - pathName: Objects that are structured in a containment hierarchy have a pathName. The pathName is a concatenation of all names from each container, i.e., from the leaf object up to the root of the containment hierarchy, similar to a file path name. For example, if node "A" contains node "B" that contains node "C", then the pathName for node "C" may look like "A.B.C". The type of delimiters used between names is not specified but is a local implementation issue. - aliasName: A free text name of the instance. This attribute can also be used for localization. - description: A free format description of the instance
61970-301©1EC:2003 -27- The following conventions are recommended for naming attributes for non- PowerSystemResource classes: name:Main classification of the instances.Example:Unit name for the units class, measurement type name for the measurementType class pathName:Optional second level classification of the instances - aliasName:A free text name of the instance.Can also be used for localization or for abbreviations description:A free format description of the instance 4.7.2 Use of Measurement-Related Classes A PowerSystemResource (PSR)may have zero to many measurements associated with it,either by containing a measurement directly or through one of its terminals.Each measurement may have one or more measurement values.Observing the following guidelines will enable applications to navigate and find the required measurement values in a consistent way (See Figure 11): 1)Measurements of a PowerSystemResource are classified by MeasurementType 2)MeasurementValues of a Measurement are classified by MeasurementValueSource. 3)MeasurementType1 inherits from Naming.The values to be used for MeasurementType.name,MeasurementType.aliasName,and MeasurementType.description are specified in Table 1,where: MeasurementType.name is the IEC 61970 name assigned MeasurementType.aliasName is the name assigned to the type in IEC 61850 MeasurementType.description defines the type 4)MeasurementValueSource also inherits from Naming.The values to be used for MeasurementValueSource.name and MeasurementValueSource.description are given in Table 2.This table provides a number of source names to be used where possible However,the exact names to be used for specific applications are defined in related IEC 61970 Component Interface Specifications (CIS). 5)The tables may be extended for proprietary needs.The names added must start with a unique name (e.g.the company name)and an underscore. Example: xyz AverageTemperature 1 MeasurementType is different from Unit,which is part of the Domain package described in Section 4.2.9.MeasurementType describes "what"is measured rather than the unit of measure including scaling,which is the purpose of Unit
61970-301 IEC:2003 – 27 – The following conventions are recommended for naming attributes for non- PowerSystemResource classes: - name: Main classification of the instances. Example: Unit name for the units class, measurement type name for the measurementType class - pathName: Optional second level classification of the instances - aliasName: A free text name of the instance. Can also be used for localization or for abbreviations - description: A free format description of the instance 4.7.2 Use of Measurement-Related Classes A PowerSystemResource (PSR) may have zero to many measurements associated with it, either by containing a measurement directly or through one of its terminals. Each measurement may have one or more measurement values. Observing the following guidelines will enable applications to navigate and find the required measurement values in a consistent way (See Figure 11): 1) Measurements of a PowerSystemResource are classified by MeasurementType 2) MeasurementValues of a Measurement are classified by MeasurementValueSource. 3) MeasurementType1 inherits from Naming. The values to be used for MeasurementType.name, MeasurementType.aliasName, and MeasurementType.description are specified in Table 1, where: MeasurementType.name is the IEC 61970 name assigned MeasurementType.aliasName is the name assigned to the type in IEC 61850 MeasurementType.description defines the type 4) MeasurementValueSource also inherits from Naming. The values to be used for MeasurementValueSource.name and MeasurementValueSource.description are given in Table 2. This table provides a number of source names to be used where possible. However, the exact names to be used for specific applications are defined in related IEC 61970 Component Interface Specifications (CIS). 5) The tables may be extended for proprietary needs. The names added must start with a unique name (e.g. the company name) and an underscore. Example: xyz_AverageTemperature 1 MeasurementType is different from Unit, which is part of the Domain package described in Section 4.2.9. MeasurementType describes “what” is measured rather than the unit of measure including scaling, which is the purpose of Unit
61970-301©1EC:2003 -28- ConductingEquipment (from Core) PowerSystemResource +ConductingEquipment 1 (from Core) +MemberOf_PSR 0..1 +Terminals 0.n Temminal +Temminal (from Core) 0.1 +Measurements +Contains_Measurements 0..n 0.n Measurement +MeasurementType +MemberOf_Measurement 0.n +Measurements 1 MeasurementType +Contain_MeasurementValues 1.n MeasurementValue 0.n +MeasurementValues +MeasurementValueSource MeasurementValueSource Figure 11-Navigating from PSR to MeasurementValue
61970-301 IEC:2003 – 28 – MeasurementValueSource PowerSystemResource (from Core) MeasurementValue 1 0..n +MeasurementValueSource 1 +MeasurementValues 0..n MeasurementType Measurement 0..1 0..n +MemberOf_PSR 0..1 +Contains_Measurements 0..n 1..n 1 +Contain_MeasurementValues 1..n +MemberOf_Measurement 1 0..n 1 +Measurements 0..n +MeasurementType 1 ConductingEquipment (from Core) Terminal (from Core) 0..n 0..1 +Measurements 0..n +Terminal 0..1 +ConductingEquipment +Terminals 0..n 1 Figure 11 – Navigating from PSR to MeasurementValue
61970-301©1EC:2003 -29- name aliasName description Current Amps Current I (rms)of a non-three phase circuit ThreePhaseCurrent TotAmps Total current I (rms)in a three phase circuit Frequency 也 Frequency (f) PowerFactor PwrFact Power Factor(pf) ThreePhasePowerFactor TotPF Average power factor(pf)in a three phase circuit ThreePhaseApparentPower TotVA Total apparent power (S)in a three phase circuit ThreePhaseReactivePower TotVAr Total reactive power(Q)in a three phase circuit ThreePhaseActivePower TotW Total real power (P)in a three phase circuit ApparentPower VoltAmp Apparent power(S)in a non-three phase circuit ReactivePower VoltAmpR Reactive power(Q)in a non-three phase circuit Voltage Volts Voltage (V)(rms) ActivePower Watts Real power (P)in a non-three phase circuit Pressure Pres Pressure Temperature Temp Temperature ThreePhaseAngle TotAng Angle (phi)Tin a three phase circuit] ApparentEnergy TotVAh Apparent energy ReactiveEnergy TotVArh Reactive energy ActiveEnergy TotWh Real energy Automatic Auto Automatic operation (not manual).automatic TRUE LocalOperation Loc Local operation (not remote).local =TRUE AutomaticControl LTCBIk Automatic control of LTC blocked (inhibited).blocked TRUE SwitchPosition Pos Switch position [2bits=intermediate,open,closed,ignore] TapPosition TapPos Tap position of power transformer or phaseshifter Operation Count OperCnt Operation count-typically for switches ParallelTransformers Parallel Transformers in parallel operating mode Table 1-MeasurementType Naming Conventions name description SCADA Telemetered values received from a local SCADA system CCLink Value received from a remote control center via TASE.2 or other control center protocol Operator Operator entered value (always manually maintained,PSR is not connected to an RTU) Estimated Value updated by a state estimator PowerFlow Value updated as result of a Powerflow Calculated Calculated from other measurement values (e.g.,a sum) Allocated Calculated by a load allocator Table 2-MeasurementValueSource Naming Conventions Following these conventions: Each Measurement instance represents a technological quantity of a PowerSystemResource Each MeasurementValue of a Measurement represents a current value for the technological quantity,as supplied from a single source
61970-301 IEC:2003 – 29 – name aliasName description Current Amps Current I (rms) of a non-three phase circuit ThreePhaseCurrent TotAmps Total current I (rms) in a three phase circuit Frequency Hz Frequency (f) PowerFactor PwrFact Power Factor (pf) ThreePhasePowerFactor TotPF Average power factor (pf) in a three phase circuit ThreePhaseApparentPower TotVA Total apparent power (S) in a three phase circuit ThreePhaseReactivePower TotVAr Total reactive power (Q) in a three phase circuit ThreePhaseActivePower TotW Total real power (P) in a three phase circuit ApparentPower VoltAmp Apparent power (S) in a non-three phase circuit ReactivePower VoltAmpR Reactive power (Q) in a non-three phase circuit Voltage Volts Voltage (V) (rms) ActivePower Watts Real power (P) in a non-three phase circuit Pressure Pres Pressure Temperature Temp Temperature ThreePhaseAngle TotAng Angle (phi) [in a three phase circuit] ApparentEnergy TotVAh Apparent energy ReactiveEnergy TotVArh Reactive energy ActiveEnergy TotWh Real energy Automatic Auto Automatic operation (not manual). automatic = TRUE LocalOperation Loc Local operation (not remote). local =TRUE AutomaticControl LTCBlk Automatic control of LTC blocked (inhibited). blocked = TRUE SwitchPosition Pos Switch position [2bits = intermediate,open,closed,ignore] TapPosition TapPos Tap position of power transformer or phaseshifter Operation Count OperCnt Operation count - typically for switches ParallelTransformers Parallel Transformers in parallel operating mode Table 1 – MeasurementType Naming Conventions name description SCADA Telemetered values received from a local SCADA system CCLink Value received from a remote control center via TASE.2 or other control center protocol Operator Operator entered value (always manually maintained, PSR is not connected to an RTU) Estimated Value updated by a state estimator PowerFlow Value updated as result of a Powerflow Calculated Calculated from other measurement values (e.g., a sum) Allocated Calculated by a load allocator Table 2 – MeasurementValueSource Naming Conventions Following these conventions: Each Measurement instance represents a technological quantity of a PowerSystemResource Each MeasurementValue of a Measurement represents a current value for the technological quantity, as supplied from a single source
61970-301©1EC:2003 -30- The source attribute in MeasurementValueQuality then indicates whether the source actually provided the current value,or whether it had been substituted or defaulted. 4.7.2.1 Attachment of Measurements As mentioned in the previous section and as shown in Figure 11,Measurements can be attached to equipment in two ways: 1.contained by a PowerSystemResource 2.via a Terminal part of a ConductingEquipment. The first option is used for Measurements that are not related to connectivity,e.g.temperature, weight,size. The second option is used for connectivity-related Measurements,e.g.power flows,voltages, currents.Voltages have no direction and can be attached wherever appropriate in relation to the sensor placement.Flows have direction and must be attached such the flow direction is evident from the placement.Figure 12 shows two examples of the placement of Measurements. Ji P12(KV) BR10 BB13 CN2 DC12 CNI P11(MW) BB22 Temp(C) CN3 DC21 Figure 12 Measurement placement Measurement P12 is a voltage Measurement that measures the voltage at the Junction J1. Measurement P12 is topologically related to the ConnectivityNode CN1 via the Terminal in Junction J1.Measurement_P11 is-a-Measurement that-measures the flow through Breaker BR10 at the side connected to the ConnectivityNode CN1.Measurement P11 is topologically related to the ConnectivityNode CN1 via the left Terminal in Breaker BR10.Temp is a Measurement that measures the Breaker temperature.As a temperature is not related to connectivity,it has no relation to a Terminal-it just belongs to the Breaker BR10. 4.7.3 Number of Terminals for ConductingEquipment Objects The following ConductingEquipment classes have two terminals:ACLineSegment, DCLineSegment,Jumper,Fuse,Breaker,Disconnector,LoadBreakSwitch.All other ConductingEquipment leaf classes have a single terminal,except for the Compensator class, which has one terminal if of compensatorType shunt,and two terminals if of compensatorType series For instances of ConductingEquipment that are not electrically connected to other equipment (i.e.,as when treated as an Asset in inventory),it is acceptable to have no terminals specified
61970-301 IEC:2003 – 30 – The source attribute in MeasurementValueQuality then indicates whether the source actually provided the current value, or whether it had been substituted or defaulted. 4.7.2.1 Attachment of Measurements As mentioned in the previous section and as shown in Figure 11, Measurements can be attached to equipment in two ways: 1. contained by a PowerSystemResource 2. via a Terminal part of a ConductingEquipment. The first option is used for Measurements that are not related to connectivity, e.g. temperature, weight, size. The second option is used for connectivity-related Measurements, e.g. power flows, voltages, currents. Voltages have no direction and can be attached wherever appropriate in relation to the sensor placement. Flows have direction and must be attached such the flow direction is evident from the placement. Figure 12 shows two examples of the placement of Measurements. BB22 BR10 DC12 CN1 DC21 CN2 CN3 BB13 J1 P11 (MW) P12 (KV) Temp (°C) Figure 12 Measurement placement Measurement P12 is a voltage Measurement that measures the voltage at the Junction J1. Measurement P12 is topologically related to the ConnectivityNode CN1 via the Terminal in Junction J1. Measurement P11 is a Measurement that measures the flow through Breaker BR10 at the side connected to the ConnectivityNode CN1. Measurement P11 is topologically related to the ConnectivityNode CN1 via the left Terminal in Breaker BR10. Temp is a Measurement that measures the Breaker temperature. As a temperature is not related to connectivity, it has no relation to a Terminal - it just belongs to the Breaker BR10. 4.7.3 Number of Terminals for ConductingEquipment Objects The following ConductingEquipment classes have two terminals: ACLineSegment, DCLineSegment, Jumper, Fuse, Breaker, Disconnector, LoadBreakSwitch. All other ConductingEquipment leaf classes have a single terminal, except for the Compensator class, which has one terminal if of compensatorType shunt, and two terminals if of compensatorType series. For instances of ConductingEquipment that are not electrically connected to other equipment (i.e., as when treated as an Asset in inventory), it is acceptable to have no terminals specified