CIM Issues #5950

How is readCycle used, should the definition be updated?

Added by Jan Owe 3 months ago.

Author/Contact Info:
Jan Owe
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG14, WG16

61968-9, 61968-11

Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:


In UsagePoint there is an attribute readCycle with the definition:
Cycle day on which the meter for this usage point will normally be read. Usually correlated with the billing cycle.

The datatype is string, so it is not obvious how it is used. Perhaps it is used to tell the date in a month. Or? How is it implemented?
In WG16 it has been suggested to add an attribute called meterReadingResolution in a class inheriting from UsagePoint with the definition ”The length of time between the regular meter readings.” The datatype will be Duration. See issue
The idea is to inform the Energy supplier if he will get metered values per 5 minutes, 15 minutes, 60 minutes (1 hour), once a day, once a month or once a year.
If readCycle would tell how often you read the meter, then WG16 would not need to add the attribute meterReadingResolution, but could use the inherited attribute from UsagePoint instead.
But then the definition of Read cycle would need to be changed since it describes a “day”, perhaps then to something like:
Read Cycle for when the meter for this usage point will normally be read. May be correlated with the billing cycle.
In connection with this, we could also look at the issue, a suggestion to add an attribute “nextReadingSchedule”. That is currently implemented (outside CIM) telling the date or month when the (next) reading will occur. This might be similar to how readCycle is implemented.

No data to display

Also available in: Atom PDF