CIM Issues #6511
Support gas metering with additional event codes and measurements
61968-9
Description
Gas metering is a bit different than electricity metering.
Some of the commands and measurements defined in previous editions for electricity carry over and work for gas, but more are needed to support it better.
Proposed Solution
Add to EndDeviceType "valve". This valve may (or may not) be part of a gas meter.
Add to EndDeviceDomain "open" and "closure". These are actions the valve might take. We must also explain in the narrative how "open" relates to "connected" and "closed" to "disconnected.
Add to EndDeviceSubDomain elements such as "communication", "battery", metrology", "leakage", and others. While "battery exists at the domain level, we want to be able to say things like "valve.closure.battery.criticalLevel" to mean that the valve had an autonomous closure event because its battery reached a critical level. (Batteries can have other levels besides critical.)
Add to EndDeviceEventOrAction a few more fields such as "criticalLevel" and "Detected".
Updated by David Haynes 8 months ago
The alternative to adding these lower fields at higher levels in the four part structure is to have more parts. We could avoid duplication of codes at different levels if we had more levels. This of course would create a breaking change and hardly seems worth it. It seems like a better idea to just pick and choose the codes we need to provide the context we want in the event we are describing.