CIM Issues #4941
Equipment.aggregate on GeneratingUnitonly to avoid redunda
Status:
Review
Priority:
Low
Author/Contact Info:
ENTSO-E N6
Base Release:
61970cim16v21
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
05/29/2013
Origination ID:
13_161
Originally Assigned To:
Description
Equipment.aggregate on GeneratingUnit
only to avoid redundant data at SynchronousMachine.
IOP agree to open WG13 discussion on this issue. What may need to be changed is to have change in UML that will forbid having multiple SynchronousMachines associated with one GeneratingUnit.
Proposed Solution
Move the aggregate attribute to ConductingEquipment.
Decision
It was decided not to move aggregated to ConductingEquipment.
Related issue 13_98.
Svein will start on a white paper, Jay and Lars-Ola will contribute.
2013-06-05/LOO
Updated by Chavdar Ivanov 4 months ago
- Subject changed from Equipment.aggregate on GeneratingUnit only to avoid redunda to Equipment.aggregate on GeneratingUnitonly to avoid redunda
- Status changed from Open to Review
- Decision updated (diff)
WG13 to discuss and agree what we do here. We need to consider potential impact on teh usage of aggregate.