Project

General

Profile

CIM Issues #6745

Need for consistent approach for Market Products

Added by Scott Coe 10 months ago. Updated 15 days ago.

Status:
Open
Priority:
High
Author/Contact Info:
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG16
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
03/28/2024
Origination ID:
Originally Assigned To:

Description

Market Products are not used consistently in the CIM because market products are not really consistent across markets...

Energy is the universal commodity; however, even when considering universal grid support products the names vary. In the North America, they call the load frequency control the Regulation product, but in Europe is is Secondary Reserve. Standby/emergency reserve products are more varied. Tertiary Reserve in Europe is split into Synchronous and Non-Synchronous Reserve in the North America. But in even in North America, there is inconsistent usage. PJM calls it Synchronized/Non-Synchronized, MISO and SPP have Spinning and Supplemental, NYISO/ISO-NE/CAISO use Spinning and Non-Spinning, and finally ERCOT has Responsive and Non-Spinning.

One of the oldest market enumerations, MarketProductType does not follow the typical format. We have: EN, RU, RD, SR, NR, RC, LFU, LFD, REG, RPU, CO2e, RMU, and RMD. Changing to Energy, RegulationUp, RegulationDown, SynchronousReserve or SpinningReserve, NonSynchronousReserve or NonSpinningReserve, ReliabibilityUnitCommitment, LoadFollowingUp, LoadFollowingDown, CarbonDioxideEquivalent, RegulationMileageUp, and RegulationMileageDown would break things.

Then we have a similar enumeration: ResourceCapacityType. RU, RD, SR, NR, MO, FO, RA, RMR which map to RegulationUp, RegulationDown, SynchronousReserve or SpinningReserve, NonSynchronousReserve or NonSpinningReserve, MustOffer, FlexibleOffer, ResourceAdequacy, and ReliabilityMustRun. Clearly a different use, but some of the concepts here overlap.

Finally, the most recent is ResourceCertificationKind which allows us to flag when a resource is certified to provide a service. Here the enumeration is properly formatted (all but one entry, that is) and again have a strong correlation to products: RegulationUp, RegulationDown, SpinningReserve, NonSpinningReserve, ReliabilityMustRun, BLACKSTART, DemandSideResponse, SynchronousCondenser, ReliabilityUnitCommittment, Energy, Capacity.


Related issues

Related to Market Management - CIM Issues #6293: Add energyFlowCategory (string) to the AccountingPoint classOpenActions
#1

Updated by Scott Coe 10 months ago

Updates:

- Europe has changed their terminology and moved away from the Primary, Secondary, Tertiary terms stated above. But this actually solidifies the point I am making.

- Several of my "direction" options listed above are informational (RelativeDirectionKind and BidDirectionKind) so need to be reviewed before using. This will also be discussion on the Grid side related the emerging ENTSO-E and EU Network Codes (perhaps Balancing Network Code?)

#2

Updated by Becky Iverson 10 months ago

  • Related to CIM Issues #6293: Add energyFlowCategory (string) to the AccountingPoint class added
#3

Updated by Becky Iverson 10 months ago

  • Status changed from New to Open
#4

Updated by Becky Iverson 15 days ago

  • Project changed from WG16 Issues to CIM Joint Issues
  • Author/Contact Info deleted (Scott Coe)
  • Proposed Solution updated (diff)
  • CIM Impacted Groups WG13, WG14, WG21 added
#5

Updated by Becky Iverson 15 days ago

  • Project changed from CIM Joint Issues to WG16 Issues
#6

Updated by Becky Iverson 15 days ago

  • CIM Impacted Groups deleted (WG13, WG14, WG21)

Also available in: Atom PDF