Project

General

Profile

CIM Issues #6507

Support IoT sensors by adding durations of time in the seconds range.

Added by David Haynes 8 months ago. Updated 7 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:
David Haynes
Standard(s):

61968-9

Version:
4
Clause:
Annex C
Sub-Clause:
C.2.4
Paragraph:
Table:
C.3
Originally Closed in Version:
Origination Date:
08/17/2023
Origination ID:
Originally Assigned To:

Description

Annex C Attribute #3 contains measuringPeriod enumerations -- most of which are sized in "minutes". However, some applications require seconds, and others hours.

Proposed Solution

Propose adding:
1,2,3,4,5,6,10,12,15,20, and 30 seconds.
4,6 min
8h

existing:
1, 2, 3, 5, 10, 12, 15, 20, 30, 60 min
(1), 2, 3, 4, 6, 12, 24h

Decision

Proposal accepted in the Part 9 team meeting on 8/17/23.

#1

Updated by David Haynes 8 months ago

  • Origination Date set to 08/17/2023
  • CIM Keywords 61968-Metering added
  • CIM Impacted Groups WG14 added
  • CIM Impacted Groups deleted (None)
#2

Updated by David Haynes 8 months ago

  • Decision updated (diff)
#3

Updated by David Haynes 8 months ago

Part 9 document, 4th edition CD1 updated on 8/17/23.

#4

Updated by David Haynes 8 months ago

If we add a few more sizes in the millisecond range we can create the means to represent digitized waveform samples. These could be "instantaneous" or "deltaData". Suggest adding: 100, 10, 1 ms. Perhaps also 100, 10, and 1 microsecond. It would also be good to add a paragraph to the document narrative to explain the use of these various sizes.

#5

Updated by David Haynes 7 months ago

Proposal to add a series of smaller time intervals accepted during a team meeting on 9/21.

Also available in: Atom PDF