Alignment of Master Data for Metering Point and of Measured Data in the deregulated Energy Market
other
| Submitted date | Last Update Date | Version | Approval Status | Project Page |
|---|---|---|---|---|
| 1.0 |
Draft
|
Project Purpose
The project regards the common requirements for the processes that directly involve the alignment of Master Data Metering Point (MP) and Measured Data between parties in the deregulated Energy Market. The purpose of the project is to derive specifications for Core Components from the process requirements and data structures regarding the alignment of Master Data Metering Point and Measured Data between parties in the deregulated Energy Market and publish these resulting specifications.Project Scope
• Specifications for Core Components for information exchange regarding • data alignment between parties (including initial data exchange), • within the deregulated Energy Market, • for Master Data Metering Point and for Measured Data. The results will be UN/CEFACT deliverables for information (category D).Project Deliverables
The project deliverables are: • Business Requirements for the various processes; These Business requirements (BRS) are created in line with UN/CEFACT Modeling Methodology 2.0 and will be delivered both as an XMI-formatted UML-model file and as a text based document. The UML model is the source for all other documentation. The Business requirements are submitted as a basis for the understanding of the need for the proposed Core Components (BIE’s and some CC’s). • Business Information Models as based on the above mentioned Business Requirements; These information models are created in line with UN/CEFACT Modeling Methodology 2.0. The models will be delivered both as an XMI-formatted UML-model file and as text based documents. The UML model is the source for all other documentation. The Business Information Models (BIM) specify the information exchange as created from the proposed Core Components (ABIE’s). • Business Information Entities and Business Data Types as used in the above mentioned Business Information Models; These business information entities and business data types are created in line with UN/CEFACT Core Component Technical Specification 3.0. The entities and data types will be delivered both as an XMI-formatted UML-model file, as an Excel spreadsheet and as XML schema’s based on UN/CEFACT Naming and Design Rules 3.0. The UML model is the source for all other documentation. • Aggregated Core Components and Core Data Types for some specific Business Information Entities and some Business Data Types to be based on; These Core Components and Core Data Types are created in line with UN/CEFACT Core Component Technical Specification 3.0. The core components and data types will be delivered both as an XMI-formatted UML-model file and as an Excel spreadsheet. The UML model is the source for all other documentation. • Specification of the payload for the information to be exchanged between the specified processes for the data alignment with regard to Master Data Metering Point and to Measured Data; These payloads are assembled from business information entities in line with UN/CEFACT Core Component Technical Specification 3.0. The payloads are specified in the Business Information Model. The payloads will be delivered both as an XMI-formatted UML-model file and as XML schema’s based on UN/CEFACT Naming and Design Rules 3.0. The UML model is the source for all other documentation.Exit Criteria
The exit criteria that when met will indicate the deliverable has been completed, are specified in the table below. Deliverable Criteria Supporting documentation Business requirements (BRS) Approval by project group In line with UN/CEFACT UMM-2 Business Information Model (BIM) Approval by project group In line with UN/CEFACT UMM-2 In line with relevant business requirements Specification of the payload Approval by project group In line with UN/CEFACT UMM-2 and in line with UN/CEFACT Naming and Design Rules 3.0 Actual deliverable Business Information Entities and Business Data Types Approval by project group In line with UN/CEFACT Core Component Technical Specification 3.0 Aggregated Core Components and Core Data Types Approval by project group In line with UN/CEFACT Core Component Technical Specification 3.0Project Team Membership and Required Functional Expertise
Head of Delegation Support
Geographical Focus
Initial Contributions
Resource Requirements
Project Leadership
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date |
| YES | YES | YES | YES | YES | YES | YES | ||||||||
| YES | YES | YES | YES | YES | YES | YES | ||||||||
| YES | YES | YES | YES | YES | YES | YES |
Project Proposal Files