CIM Issues #5285: Addition of value3 attributes in BasicIntervalSchedule and RegularTimePoint (possibly IrregularTimePoint as well to be consistent?) - WG13 Issues - UCAIug Issue Tracking System

CIM Issues #5285

Addition of value3 attributes in BasicIntervalSchedule and RegularTimePoint (possibly IrregularTimePoint as well to be consistent?)

Added by Becky Iverson over 2 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Author/Contact Info:

Becky Iverson

Base Release:

IEC61970cim18

Solution to be Applied To:

CIM18

Solution Version:

CIM18v02

Solution Applied By:

Todd Viegut

Completion Date:

06/21/2022

CIM Keywords:

61970-Core

Breaking Change:

Breaking Change Description:

CIM Impacted Groups:

WG13, WG14, WG16, WG21

Requestor:

Becky Iverson

Standard(s):

61970-301

Version:

CIMv18

Clause:

Sub-Clause:

Paragraph:

Table:

Originally Closed in Version:

CIM18

Origination Date:

Origination ID:

Originally Assigned To:

Description

Currently the RegularIntervalSchedule class allows for the definition of 2 values to be specified for a specific time frame with a regular time step. In WG21 we have a use case requirement to publish a set of three values. These values are typically published together against the same time duration and time step. The values are the maximum, the minimum and the expected value. We are proposing to add a value3 set of attributes to the BasicIntervalSchedule and RegularTimePoint classes.
BasicIntervalSchedule.value3Multiplier (UnitMultiplier)
BasicIntervalSchedule.value3Unit (UnitSymbol)
BasicIntervalSchedule.value3Description (String)
RegularTimePoint.value3 (Float)

We do not foresee a need for more values and feel that the addition of the value3 will satisfy our current requirement. This would keep inline with the current modeling alternatives for Curve/CurveData as well which allow for up to three yvalues (y1-y3).

To be consistent, IrregularTimePoint could have the value3 added as well, although our use case does not require the value3 use in an IrregularIntervalSchedule.

Proposed Solution

We are proposing to add a value3 set of attributes to the BasicIntervalSchedule and RegularTimePoint classes.
BasicIntervalSchedule.value3Multiplier (UnitMultiplier)
BasicIntervalSchedule.value3Unit (UnitSymbol)
BasicIntervalSchedule.value3Description (String)
RegularTimePoint.value3 (Float)

To be consistent, IrregularTimePoint could have the value3 added as well, although our use case does not require the value3 use in an IrregularIntervalSchedule.

Note that Issue 5151 is related and should be applied at the same time. This would result in consistent "sets or pairs" of value1*, value2*, value3* attributes.

Release Notes

A third set of value related attributes have been added to the BasicIntervalSchedule , RegularTimePoint , and IrregularTimePoint classes where applicable. The specific changes included:

BasicIntervalSchedule.value3Multiplier (UnitMultiplier)
BasicIntervalSchedule.value3Unit (UnitSymbol)
BasicIntervalSchedule.value3Description (String)
RegularTimePoint.value3 (Float)
IrregularTimePoint.value3 (Float)

Related issues