CIM Issues #5851
AggregatedRegisteredResoure self association update
Self association on RegisteredResource is RegisteredResource 0..many -> 0..1 AggregatedRegisteredResource. Request to change the cardinality on the AggregatedRegisteredResource end to 0..many.
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
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."