Project

General

Profile

CIM Issues #5345

Add attribute nextReadingSchedule to UsagePoint

Added by Becky Iverson almost 3 years ago. Updated about 2 years ago.

Status:
Open
Priority:
Normal
Author/Contact Info:
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG14, WG16
Requestor:
Standard(s):

61968-11

Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

This new attribute will inform the Energy supplier when the (next) reading is done. Could be a date, or a string with a format "MMDD". Example 0704 informing that regular readings are done yearly July 4th. Typically used for yearly read market evaluation points. Description of the new attribute can be "The indication of when the next meter reading is scheduled." The datatype is String (to allow different use cases; 2022, July, 0704). Implementation would specify the rules as to the format of the expected next reading schedule.

Files

UCA TF13 TF14 TF16 meeting February 2023 Issue 5345.pdf View UCA TF13 TF14 TF16 meeting February 2023 Issue 5345.pdf 497 KB Jan Owe, 02/09/2023 10:42 AM

Decision

At the Richland meeting. Agreed upon using three fields: nextReadingYear, nextReadingMonth, nextReadingDate would allow for anyone to use any combo of the elements. For example, only nextReadingMonth=3 is March. Replace the null/missing nextReadingDate=15, it becomes March 15. Same format for any implementation.

Recommend integer for fields.

AI: Clarify all descriptions and sign off in a TF14/TF16 meeting.

Related issues

Related to WG16 Issues - CIM Issues #5802: Add scheduledMeterReadingDate attribute (String) in the MarketEvaluationPoint classClosedActions

Also available in: Atom PDF