Project

General

Profile

CIM Issues #5820

MarketEvaluationPoint association to RegisteredResource

Added by Herbert Falk almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Alvaro
Base Release:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v07
Solution to be Applied To:
Solution Version:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v08
Solution Applied By:
Becky Iverson
Completion Date:
11/04/2021
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
None
Requestor:
Standard(s):
Version:
Clause:
MarketEvaluationPoint
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
03/26/2021
Origination ID:
16_0104
Originally Assigned To:

Description

Within Clean Energy Package it is required to have a resource capacity registry. The design of the tool is based on Methodologies for cross-border participation in resource capacity mechanisms. For information, a resource capacity mechanism means a temporary measure to ensure the achievement of the necessary level of resource adequacy by remunerating resources for their availability, excluding measures relating to ancillary services or congestion management
Within the registry, (generation and consumption) resources are aggregated in Resource Capacity Market Units (RCMU). The RCMUs are used by the resource provider to fulfil its capacity commitment and upon which availability is checked.
One of the requirements of the project is to provide the metering point of the units (registeredResource) within the RCMU. Currently project is using aggregateNode class to make the reference to the metering point. However, that is not a good modelling approach.
ebIX is also interested in this new association. Energy suppliers may be interested to know the technology and the fuel behind the resources connected to Market Evaluation Point which the supplier is associated with.


Proposed Solution

It is proposed to link MarketEvaluationPoint class and RegisteredResource class in MarketManagement package. Cardinality should be 0..* at both ends. We understand that there can be several resources linked to a metering point.


Decision

Agreed to add new association.

#1

Updated by Becky Iverson over 1 year ago

  • Status changed from New to Closed

Also available in: Atom PDF