Project

General

Profile

CIM Issues #6758

Measurement issues

Added by Chavdar Ivanov about 1 month ago. Updated 3 days ago.

Status:
New
Priority:
High
Author/Contact Info:
Chavdar Ivanov
Base Release:
CIM18
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
61970-Meas
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

There are 3 Meas related issues

1) Voltage Telemetries at terminal of Switches
452 constraint
• C:452:OP:Measurement.Terminal:requiredCases
The association Measurement.Terminal shall reference a Terminal of the Equipment referenced by Measurement.PowerSystemResource except in cases where Measurement.measurementType is either “TapPosition” or “SwitchPosition” in which the association is not exchanged.

What should be done in the following case: the Voltage Telemetries are exported as Analog, but many of the them are associated with Switch Terminal since no other devices over there at the measurement position. Also, there is a Discrete Measurement for the SwitchPosition. Can we associate Terminal for Discrete of SwitchPosition?
Removing the association Measurement.Terminal solves the issue, but is this the right approach?

2) Name for MeasurementValueSource
452 constraint
• C:452:OP:MeasurementValueSource:name
For MeasurementValueSource, attribute IdentifiedObject.name is restricted to the following strings for MeasurementValueSource: ICCP, SCADA.

What a vendor should do if want to communicate other, for example LSE (Linear State Estimation) or other potential names? DO we do this with extension or we have enum for ICCP and SCADA and we have other types as a string that vendors can freely use?

3) Analog vs Discrete units
Table 3 in 452 and various constraints resulting from it define that

- Tap Position is Analog and not allowed for discrete (see constraint C:452:OP:Measurement.measurementType:analogValues and C:452:OP:Measurement.measurementType:discreteValues)
- UnitSymbol have different restriction for Analog and Discrete. None is not allowed for Analog (see constraints C:452:OP:Measurement.unitSymbol:analogValues and C:452:OP:Measurement.unitSymbol:discreteValues)

Questions:
- Is it OK that TapPosition is analog and not discrete? Is Discrete only boolean values or it could be also integers?
- if all is good, don't we need to add UnitSymbol.none in the Analog so that we solve the case for TapPosition which is unitless?

• C:452:OP:Measurement.measurementType:analogValues
For Analog, Measurement.measurementType is restricted to the following valid values: ThreePhasePower, ThreePhaseActivePower, ThreePhaseReactivePower, LineCurrent, PhaseVoltage, Voltage, Angle, Frequency and TapPosition.
• C:452:OP:Measurement.measurementType:discreteValues
For Discrete, Measurement.measurementType is restricted to the following valid values: SwitchPosition.
• C:452:OP:Measurement.unitSymbol:analogValues
For Analog, Measurement.unitSymbol is restricted to the following valid values: W, deg, VA, A, VAr, V, Hz.
• C:452:OP:Measurement.unitSymbol:discreteValues
For Discrete, Measurement.unitSymbol is restricted to the following valid values: none.


Decision

15 May 2024
on item 1) the recommendation is that the measurementType should be Voltage and the association is required.
There is no point to have the association to the Terminal for the Switch position.

2) exchange of MeasurementValueSource is only for legacy implementations and new approaches are not yet supported. There are other issues open on the measurement.

3)
- Is it OK that TapPosition is analog and not discrete? yes
Is Discrete only boolean values or it could be also integers? No, Discrete means integer for tap position,
- if all is good, don't we need to add UnitSymbol.none in the Analog so that we solve the case for TapPosition which is unitless?
yes, we need to add it to 452

Follow up tasks
- check measurement issues
- fix 452 to add UnitSymbol.none for Analog


Related issues

Related to WG13 Issues - CIM Issues #6610: Multiple issue Measurement and ControlNewActions
#1

Updated by Chavdar Ivanov 3 days ago

  • Decision updated (diff)
#2

Updated by Svein Olsen 3 days ago

Also available in: Atom PDF