CIM Issues #5726
RegisteredGenerator association to MktGeneratingUnit
Description
Association from RegisteredGenerator to MktGeneratingUnit cannot support distribution to multiple MktGeneratingUnits
Proposed Solution
The direct association between RegisteredGenerator and MktGeneratingUnit does not currently allow for specifying distribution factors when the RegisteredGenerator is an aggregate and has associations to more than one MktGeneratingUnits.
This association supports the use case of a market that is not nodal based. If a market does not use the topology of the network model, there is a need to have an association to the generating unit(s) for which the RegisteredGenerator represents. Proposal has been made to add an additional class GeneratorDistributionFactor which will allow for the definition of the distribution factors for each GeneratingUnit that is included in the definition of an aggregated RegisteredGenerator.
Decision
Verify with NA subteam - is this a requirement? No
Verify with EU team - MktGeneratingUnit, should RegisteredGenerator be included in the MarketCommon package? How is MktGeneratingUnit used by the EU model? Inherited associations from RegisteredResource to MktPSRType and then from MktPSRType to MktGeneratingUnit. The association between RegisteredGenerator and MktGeneratingUnit is not used by the MarketManagement package.
10/22/2015: MktGeneratingUnit has been moved to MarketCommon package in iec62325cim03v02.
Remove association between RegisteredGenerator and MktGeneratingUnit.
Updated by Becky Iverson almost 2 years ago
- Status changed from New to Closed
- Base Release changed from iec61970cim16v21 iec61968cim12v07 iec62325cim03v01 to iec61970cim16v21iec61968cim12v07iec62325cim03v01
- Solution Version changed from iec61970cim17v04 iec61968cim12v09 iec62325cim03v07 to iec61970cim17v04iec61968cim12v09iec62325cim03v07
- Proposed Solution updated (diff)
- Decision updated (diff)