Project

General

Profile

CIM Issues #5851

AggregatedRegisteredResoure self association update

Added by Herbert Falk over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Becky
Base Release:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v09
Solution to be Applied To:
Solution Version:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v14
Solution Applied By:
BLI
Completion Date:
04/14/2022
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
None
Requestor:
Standard(s):
Version:
Clause:
AggregatedRegisteredResoure
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
02/10/2022
Origination ID:
16_0135
Originally Assigned To:

Description

Self association on RegisteredResource is RegisteredResource 0..many -> 0..1 AggregatedRegisteredResource. Request to change the cardinality on the AggregatedRegisteredResource end to 0..many.

Proposed Solution

There are cases where a resource could be in multiple aggregations, and not just transitioning from one to another (overlapping in time) for example could be an aggregation for energy service and another for reserve. Also Tetsuo Otanis use case with different profiles with resources assembled differently for different reasons will also require the multiple aggregations

Decision

2/24/2022: Further discussions necessary to understand the details of the use case. Plan to invite Tetsuo to a one-off earlier call.
4/7/2022: International market has a need for RegisteredResources to belong to more than one AggregatedRegisteredResource. Agree to change the cardinality from 0..1 to 0..many. Added the end role association descriptions.
Agg: "RegisteredResource which represents a collection of individual RegisteredResources."
Reg: "RegisteredResource which represents a member of a collection of RegisteredResources."

#1

Updated by Becky Iverson over 2 years ago

  • Status changed from New to Closed
  • Decision updated (diff)

Also available in: Atom PDF