Project

General

Profile

CIM Issues #6511

Support gas metering with additional event codes and measurements

Added by David Haynes 8 months ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Author/Contact Info:
dhaynes@hubbell.com
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
61968-Metering
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG14
Requestor:
Standard(s):

61968-9

Version:
4
Clause:
Annex E
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
08/29/2023
Origination ID:
Originally Assigned To:

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".

Also available in: Atom PDF