Project

General

Profile

CIM Issues #5345

Add attribute nextReadingSchedule to UsagePoint

Added by Becky Iverson almost 2 years ago. Updated about 1 year ago.

Status:
Open
Priority:
Normal
Solution Version:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG14, WG16
Requestor:
Standard(s):

61968-11

Version:
Clause:
Sub-Clause:
Paragraph:
Table:
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


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.

#1

Updated by Henry Dotson over 1 year ago

  • Project changed from WG14 Part 11 Issues to CIM Joint Issues
  • Author/Contact Info deleted (B. Iverson)
  • CIM Keywords deleted (61968-Metering)
#3

Updated by Eric Stephan about 1 year ago

  • Decision updated (diff)
#4

Updated by Eric Stephan about 1 year ago

  • Status changed from New to Open
#5

Updated by Eric Stephan about 1 year ago

Please refer to the latest standard data types https://www.w3.org/TR/xmlschema11-2/ that cover duration and derivations such as monthYearDuration and dayTimeDuration.

#6

Updated by Becky Iverson about 1 year ago

Since the nextReadingDate represents the "day" as an integer. Should the new attribute be nextReadingDay so that it is not confused with an actual "Date" datatype?

Also available in: Atom PDF