Project

General

Profile

CIM Issues #6890

Addition of Permission class to MarketManagement

Added by Jan Owe 3 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Author/Contact Info:
Bhagyashree Wahie, Jan Owe
Base Release:
Grid18v10_Enterprise14v03_Market04v16a
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
62325-MarketManagement
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG16
Requestor:
ENTSO-E
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
03/27/2024
Origination ID:
BW_20230615_01
Originally Assigned To:

Description

In order to fulfil the EU regulation 2023/1162 we would like to have a class Permission, inherited from Document, that can handle the permissions given by the "Permission administrator" regarding providing access (could be limited in time) to metered data by eligable parties.

Files

MR for IEC 62325-301 and 351 ENTSO-E Addition of_PermissionClass_20240327 .pdf View MR for IEC 62325-301 and 351 ENTSO-E Addition of_PermissionClass_20240327 .pdf 807 KB Jan Owe, 08/29/2024 09:53 AM
MR for IEC 62325-301 and 351 ENTSO-E Addition of_PermissionClass_20240919.pdf View MR for IEC 62325-301 and 351 ENTSO-E Addition of_PermissionClass_20240919.pdf 1.76 MB Jan Owe, 10/01/2024 01:49 AM

Proposed Solution

This MR suggests adding the Permission class to MarketManagment, inheriting from Document. It should be associated with e.g. TimePeriod, MktActivityRecord, MarketEvaluationPoint. See further attached PDF file.

#1

Updated by Jan Owe 2 months ago

The EU Implementing regulation for accessing metering and consumption data (https://eur-lex.europa.eu/eli/reg_impl/2023/1162/oj) sets out some rules related to permissions getting the access. One of these rules involves sending master data when someone asks for permission to do certain tasks or activities. This master data serves a few purposes: first, it confirms that permission is being requested. Second, it grants permission to the party who wants to access validated historical consumption data as stated in the permission request. Third, it responds to the permission request, letting the requester know if it's valid or not. If the request is valid, it communicates the validation result, but if it's invalid, it indicates that too. Additionally, it informs the concerned party when permission has been successfully established, and it also grants permission to transfer data. So, it's essentially about confirming, granting, responding, communicating results, informing about success, and allowing data transfer as per the permission request.

Also available in: Atom PDF