CIM Issues #5345
Add attribute nextReadingSchedule to UsagePoint
61968-11
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 |
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.
Updated by Henry Dotson 12 months ago
- Project changed from WG14 Part 11 Issues to CIM Joint Issues
- Author/Contact Info deleted (
B. Iverson) - CIM Keywords deleted (
61968-Metering)
Updated by Eric Stephan 7 months 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.
Updated by Becky Iverson 7 months 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?