Business information model for. Notify MP. (Metering Point) characteristics

Size: px

Start display at page:

Download "Business information model for. Notify MP. (Metering Point) characteristics"

Leo Walsh
5 years ago
Views:

1 Business information model for Notify MP (Metering Point) characteristics Status: Approved by ETC Version: 2014 Release: A Revision: - Date: November 2015

2 ebix Business information model for Notify MP characteristics in the energy domain 2 C O N T E N T A. About this document... 3 A.1. References... 3 A.1.1. International open standards used... 3 A.1.2. ebix Document references... 3 A.2. Main changes since last version Introduction Place in the overall model for the European Energy Market About the ebix Model Objectives Scope Actors, parties and roles Annexes for mapping to technology of choice Business Choreography View: Notify MP characteristics Notify MP characteristics (Business Realization) Notify MP Characteristics (Business Collaboration) Description Notify MP characteristics (Business Collaboration Protocol) UseCase Notify MP characteristics (Business Transaction) Notify MP characteristics (Business Transaction) Business Information View: Notify MP characteristics Notify MP characteristics (Business Information) OCL constraints for Notify MP characteristics <<MA>> Mapping BRS-BIM for Notify MP characteristics... 18

3 ebix Business information model for Notify MP characteristics in the energy domain 3 A. About this document This document contains the Business Information Model for Notify MP characteristics. This model is based on the ebix Business Requirements for Notify MP characteristics [9]. The model is drafted using the ebix Rules for the use of UN/CEFACT Modeling Methodology version 2.0 (UMM-2). UMM-2 uses UML as the Modeling Language. This part of the ebix Model for the European Energy Market is made by ebix ETC and is based on business requirements as specified by ebix CuS (Change of Supplier) working group. If you have comments or suggestions to the model please contact any member of the project group (see ebix website). A.1. References A.1.1. International open standards used [1] UML Profile for UN/CEFACT s Modelling Methodology (UMM), Base Module 2.0, ( [2] UML Profile for UN/CEFACT s Modelling Methodology (UMM), Foundation Module ( [3] UN/CEFACT Core Components Technical Specification Version 3.0, ( p5_draft_ _3rd_iteration.pdf) [4] UN/CEFACT UML Profile for Core Components Technical Specification 3.0, ( [5] UN/CEFACT XML Naming and Design Rules Technical Specification Version 3.0, ( [6] UN/CEFACT Core Components Data Type Catalogue, ( [7] Object Constraint Language, OMG Available Specification Version 2.0 formal, ( A.1.2. ebix Document references [8] Introduction to ebix Models ( [9] ebix Business Requirements, especially Business Requirements for Notify MP Characteristics ( [10] ebix Business Information Models for other business areas ( [11] The Harmonized Role Model (for the Electricity Market) by ebix, ENTSO-E, and EFET (

4 ebix Business information model for Notify MP characteristics in the energy domain 4 [12] ebix Rules for the use of OCL statements ( ) A.2. Main changes since last version Subject Old New Clarification Date Version 2011.A Minor textual clarifications and update of web addresses Update of OCL st version, changes not tracked Version 2014.A Restructured the entire document

5 ebix Business information model for Notify MP characteristics in the energy domain 5 1. Introduction 1.1. Place in the overall model for the European Energy Market This document contains the Business Information Model for the Notify MP characteristics in the European Energy Market. This model is part of the overall ebix business domain for Structure, including change of consumer and maintenance of master data About the ebix Model The documents for the domain Structure describe a model for the exchange of master data in the European Energy Market. The model will, when the modelling project have been completed, be a part of a common ebix model for the European Energy Market. The model is important for having a common and agreed understanding on how the exchange of business information in the European Energy Market works. In line with UMM-2 the ebix model contains 3 main parts: 1. Business Requirements View 2. Business Choreography View 3. Business Information View The Business Requirements for Notify MP characteristics are specified in a separate document [9]. This document contains the Business Choreography View and the Business Information View for the Notify MP characteristics processes. In the annexes to this model document you will find the technology dependent specifications that are derived from the UML-model and that are required for actual implementations Objectives This ebix Business Information Model shall specify the Notify MP characteristics business information in line with the ebix business requirements for the Notify MP characteristics processes [9], in line with the UN/CEFACT Modelling Methodology version 2.0 Error! Reference source not found. and [2]. From the information specification in the Business Information View syntax dependent exchange formats are derived for publication as recommendation by ebix. From the process specifications in the Business Choreography View web service definitions are derived for publication as recommendation by ebix Scope This model belongs to the Structure domain of the overall ebix model and focuses on Notify MP characteristics.

6 ebix Business information model for Notify MP characteristics in the energy domain Actors, parties and roles In the modelled processes (UseCases and Activity diagrams) specified in the next paragraphs, actors are either presented as <<BusinessPartner>> or as <<Harmonized Role>>. A business partner type is an organization type, an organisational unit type or a person type that participates in a business process [2]. A harmonized role represents a specific responsibility in the European Energy Market related to the exchange of information [11]. In this document the following business partners («BusinessPartner») are taken from the business requirements: Balance Responsible Party Balance Supplier Grid Access Provider Metered Data Aggregator Metered Data Responsible Metering Point Administrator Reconciliation Responsible Transport Capacity Responsible Party In the model the business partner is to be mapped to a <<Harmonized Role>> from the Role Model. In this document the following harmonized roles are used: Balance Responsible Party Balance Supplier Grid Access Provider Metered Data Aggregator Metered Data Responsible Metering Point Administrator Reconciliation Responsible Transport Capacity Responsible Party 1.6. Annexes for mapping to technology of choice Information on available mapping to technology of choice can be found in the document Introduction to ebix Models ( [8].

7 ebix Business information model for Notify MP characteristics in the energy domain 7 2. Business Choreography View: Notify MP characteristics 2.1. Notify MP characteristics (Business Realization) Figure 1 Realization: Notify MP characteristics Notify MP Characteristics (Business Collaboration) Figure 2 Collaboration UC: Notify MP characteristics Description UseCase description: Notify MP characteristics Definition In this process the Metering Point Administrator distributes Metering Point Characteristics to Linked parties: Balance Responsible Party Balance Supplier

8 ebix Business information model for Notify MP characteristics in the energy domain 8 Grid Access Provider Metered Data Aggregator Metered Data Responsible Reconciliation Responsible Transport Capacity Responsible Party after update of one or more of these characteristics Begins when Preconditions Ends when Post condition Exceptions Actions When there have been changes to the Metering Point Characteristics One or more parties linked to a Metering Point and registered in the Metering Point register are entitled to receive Metering Point Characteristics One or more Metering Point Characteristics have been changed When the Linked parties have received the notification The Metering Point Characteristics have been notified by the Metering point Administrator to the Linked parties None See Error! Reference source not found Notify MP characteristics (Business Collaboration Protocol) Figure 3 Collaboration protocol: Notify MP characteristics

9 ebix Business information model for Notify MP characteristics in the energy domain UseCase Notify MP characteristics (Business Transaction) Figure 4 Business transaction UC: Notify MP characteristics Notify MP characteristics (Business Transaction) Figure 5 Business transaction: Notify MP characteristics

ebix Business information model for Notify MP characteristics in the energy domain 10 3.

10 ebix Business information model for Notify MP characteristics in the energy domain Business Information View: Notify MP characteristics 3.1. Notify MP characteristics (Business Information) Figure 6 Class diagram: Notify MP characteristics

11 ebix Business information model for Notify MP characteristics in the energy domain OCL constraints for Notify MP characteristics <<MA>> # Specification Constrained Element Applied Stereotype 1 -- Structure Document -- Notify MP characteristics self.header->size()=1 inv: self.process->size()=1 NotifyMPChar acteristics abie document invariant 2 -- Structure Energy_Document -- Notify MP characteristics self.header.identification->size()=1 inv: self.header.creation->size()=1 inv: self.header.document_type->size()=1 inv: self.header.sender.identification->size()=1 inv: self.header.sender.role->size()=0 inv: self.header.sender.name->size()=0 inv: self.header.recipient.identification->size()=1 inv: self.header.recipient.role->size()=0 inv: self.header.recipient.name->size()=0 NotifyMPChar acteristics abie document invariant 3 -- Structure Energy_Context -- Notify MP characteristics self.process.energy_businessprocess->size()=1 inv: self.process.energy_businessprocessrole->size()=1 NotifyMPChar acteristics abie invariant document

12 ebix Business information model for Notify MP characteristics in the energy domain 12 # Specification Constrained Element Applied Stereotype 4 -- BDT Energy_Document -- Notify MP characteristics self.header.document_type.content=documentnamecode::e07 inv: self.header.document_type.listidentifier->size()=0 inv: self.header.document_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.header.creation.timezonecode->size()=0 NotifyMPChar acteristics bdt document invariant inv: self.header.sender.identification.schemeidentifier->size()=0 inv: self.header.sender.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or self.header.sender.identification.schemeagencyidentifier=codelistresponsibleagencycode::305 inv: self.header.sender.role.content=businessrolecode::mdr inv: self.header.sender.role.listidentifier->size()=0 inv: self.header.sender.role.listagencyidentifier->size()=0 inv: self.header.sender.name.languagecode->size()=0 inv: self.header.sender.name.languagecode->size()=0 inv: self.header.recipient.identification.schemeidentifier->size()=0 inv: self.header.recipient.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or self.header.recipient.identification.schemeagencyidentifier=codelistresponsibleagencycode::305 inv: self.header.recipient.role.content=businessrolecode::ddk or self.header.recipient.role.content=businessrolecode::ddq or self.header.recipient.role.content=businessrolecode::ddm or self.header.recipient.role.content=businessrolecode::dea or self.header.recipient.role.content=businessrolecode::mdr or self.header.recipient.role.content=businessrolecode::tcr or self.header.recipient.role.content=businessrolecode::z06 inv: self.header.recipient.role.listidentifier->size()=0 inv: self.header.recipient.role.listagencyidentifier->size()=0 inv: self.header.recipient.name.languagecode->size()=0 inv: self.header.recipient.name.languagecode->size()=0

13 ebix Business information model for Notify MP characteristics in the energy domain 13 # Specification Constrained Element Applied Stereotype 5 -- BDT Energy_Context -- Notify MP characteristics self.process.energy_businessprocess.content=businessreasoncode::e03 or self.process.energy_businessprocess.content=businessreasoncode::e20 or self.process.energy_businessprocess.content=businessreasoncode::e32 or self.process.energy_businessprocess.content=businessreasoncode::e56 or self.process.energy_businessprocess.content=businessreasoncode::e57 or self.process.energy_businessprocess.content=businessreasoncode::e65 or self.process.energy_businessprocess.content=businessreasoncode::e66 or self.process.energy_businessprocess.content=businessreasoncode::e68 inv: self.process.energy_businessprocess.listidentifier->size()=0 inv: self.process.energy_businessprocess.listagencyidentifier=codelistresponsibleagencycode::260 NotifyMPChar acteristics bdt invariant document inv: self.process.energy_businessprocessrole.content=businessrolecode::ddk or self.process.energy_businessprocessrole.content=businessrolecode::tcr inv: self.process.energy_businessprocessrole.listidentifier->size()=0 inv: self.process.energy_businessprocessrole.listagencyidentifier->size()=0 inv: self.process.energy_industryclassification.content=sectorareaidentificationcode::23 or self.process.energy_industryclassification.content=sectorareaidentificationcode::27 inv: self.process.energy_industryclassification.listagencyidentifier->size()= Structure Payload -- Notify MP characteristics self.header->size()=0 inv: self.process->size()=0 NotifyMPChar acteristics invariant payload abie

14 ebix Business information model for Notify MP characteristics in the energy domain 14 # Specification Constrained Element Applied Stereotype 7 --Structure MasterDataMP_Event -- Notify MP characteristics self.payload.occurrence->size()=1 inv: self.payload.originalbusinessdocument_reference->size()=0 inv: self.payload.meteringpoint_used->size()=1 inv: self.payload.mp_address.identification->size()=0 inv: self.payload.metereddatacollector_involved->size()=0 inv: self.payload.mp_detail.meteringgridarea_used->size()=1 inv: self.payload.mp_detail.tax_type->size()=0 inv: self.payload.mp_detail.energygenerationtechnologytype_code->size()=0 inv: self.payload.mp_detail.contractedconnection_included.identification->size()=1 inv: self.payload.snapshot_occurrence->size()=0 inv: self.payload.consumer_involved.identification->size()=1 inv: self.payload.consumer_involved.name->size()=1 inv: self.payload.reconciliation_detail.annual_period->notempty() inv: self.payload. Reconciliation_Detail.Annual_Period.Total ->size()=1 NotifyMPChar acteristics invariant abie document payload 8 -- BDT MasterDataMP_Event -- Notify MP characteristics self.payload.occurrence.timezonecode->size()=0 inv: self.payload.meteringpoint_used.identification.schemeidentifier->size()=0 inv: self.payload.meteringpoint_used.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 inv: self.payload.balanceresponsible_involved.identification.schemeidentifier->size()=0 inv: self.payload.balanceresponsible_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 NotifyMPChar acteristics invariant bdt document payload inv: self.payload.balancesupplier_involved.identification.schemeidentifier->size()=0 inv: self.payload.balancesupplier_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.transportcapacityresponsible_involved.identification.schemeidentifier->size()=0 inv: self.payload.transportcapacityresponsible_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9

15 ebix Business information model for Notify MP characteristics in the energy domain 15 # Specification Constrained Element Applied Stereotype or Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.consumer_involved.identification.schemeidentifier->size()=0 inv: self.payload.consumer_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.Consumer_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.metereddataresponsible_involved.identification.schemeidentifier->size()=0 inv: self.payload.metereddataresponsible_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.MeteredDataResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.gridaccessprovider_involved.identification.schemeidentifier->size()=0 inv: self.payload.gridaccessprovider_involved.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.GridAccessProvider_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.mp_detail.meteringpoint_type.content=meteringpointtypecode::e17 or self.payload.mp_detail.meteringpoint_type.content=meteringpointtypecode::e18 or self.payload.mp_detail.meteringpoint_type.content=meteringpointtypecode::e19 inv: self.payload.mp_detail.meteringpoint_type.listidentifier->size()=0 inv: self.payload.mp_detail.meteringpoint_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.meteringpoint_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.meteringmethod_type.content=meteringmethodcode::e13 or self.payload.mp_detail.meteringmethod_type.content=meteringmethodcode::e14 or self.payload.mp_detail.meteringmethod_type.content=meteringmethodcode::e16 or self.payload.mp_detail.meteringmethod_type.content=meteringmethodcode::e24 inv: self.payload.mp_detail.meteringmethod_type.listidentifier->size()=0 inv: self.payload.mp_detail.meteringmethod_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.meteringmethod_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.settlementmethod_type.content=settlementmethodcode::e01 or self.payload.mp_detail.settlementmethod_type.content=settlementmethodcode::e02 or self.payload.mp_detail.settlementmethod_type.content=settlementmethodcode::e15 inv: self.payload.mp_detail.settlementmethod_type.listidentifier->size()=0 inv: self.payload.mp_detail.settlementmethod_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.settlementmethod_type.listagencyidentifier=codelistresponsibleagencycode::260

16 ebix Business information model for Notify MP characteristics in the energy domain 16 # Specification Constrained Element Applied Stereotype inv: self.payload.mp_detail.gridconnectioncontract_type.content=gridagreementtypedescriptioncode::e01 or self.payload.mp_detail.gridconnectioncontract_type.content=gridagreementtypedescriptioncode::e02 inv: self.payload.mp_detail.gridconnectioncontract_type.listidentifier->size()=0 inv: self.payload.mp_detail.gridconnectioncontract_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.gridconnectioncontract_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e03 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e04 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e05 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e06 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e07 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e08 or self.payload.mp_detail.voltagelevel_type.content=voltagelevelcode::e09 or self.payload.mp_detail.voltagelevel_type.listidentifier->size()=0 inv: self.payload.mp_detail.voltagelevel_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.voltagelevel_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.pressurelevel_type.content=pressurelevelcode::e10 or self.payload.mp_detail.pressurelevel_type.content=pressurelevelcode::e11 inv: self.payload.mp_detail.pressurelevel_type.listidentifier->size()=0 inv: self.payload.mp_detail.pressurelevel_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.pressurelevel_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.administrativestatus_type.listidentifier->size()=0 inv: self.payload.mp_detail.administrativestatus_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.administrativestatus_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.physicalstatus_type.listidentifier->size()=0 inv: self.payload.mp_detail.physicalstatus_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.physicalstatus_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_detail.standardloadprofile_type->size()=0 inv: self.payload.mp_detail.scheduledmeterreading_date.timezonecode->size()=0 inv: self.payload.mp_detail.balancegroup_used.identification.schemeidentifier->size()=0

17 ebix Business information model for Notify MP characteristics in the energy domain 17 # Specification Constrained Element Applied Stereotype inv: self.payload.mp_detail.balancegroup_used.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 or Payload.MP_Detail.BalanceGroup_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305 inv: self.payload.mp_detail.contractedconnection_included.identification.content=energyproductidentifier:: inv: self.payload.mp_detail.contractedconnection_included.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 inv: self.payload.mp_detail.contractedconnection_included.unit_type->size()=1 inv: self.payload.mp_detail.contractedconnection_included.unit_type.content=measurementcommoncode::kwt inv: self.payload.mp_detail.contractedconnection_included.unit_type.content=measurementcommoncode::maw inv: self.payload.mp_detail.contractedconnection_included.unit_type.content=measurementcommoncode::mqh inv: self.payload.mp_detail.contractedconnection_included.unit_type.listidentifier->size()=0 inv: self.payload.mp_detail.contractedconnection_included.unit_type.listagencyidentifier->size()=1 inv: self.payload.mp_detail.contractedconnection_included.unit_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.reconciliation_detail.reconciliation_included.identification.content=energyproductidentifier:: or self.payload.reconciliation_detail.reconciliation_included.identification.content=energyproductidentifier:: or self.payload.reconciliation_detail.reconciliation_included.identification.content=energyproductidentifier:: or self.payload.reconciliation_detail.reconciliation_included.identification.content=energyproductidentifier:: or self.payload.reconciliation_detail.reconciliation_included.identification.content=energyproductidentifier:: inv: self.payload.reconciliation_detail.reconciliation_included.identification.schemeagencyidentifier=codelistresponsibleagencycode::9 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type->size()=1 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.content=measurementcommoncode::kwh inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.content=measurementcommoncode::k3 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.content=measurementcommoncode::mtq inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.content=measurementcommoncode::d90 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.listidentifier->size()=0 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.listagencyidentifier->size()=1 inv: self.payload.reconciliation_detail.reconciliation_included.unit_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.reconciliation_detail.direction_type.content=meteringpointtypecode::e17 or self.payload.reconciliation_detail.direction_type.content=meteringpointtypecode::e18 inv: self.payload.reconciliation_detail.annual_period.total.unitcode->size()=0 inv: self.payload.reconciliation_detail.annual_period.metertimeframe_type.content=metertimeframecode::e10 or self.payload.reconciliation_detail.annual_period.metertimeframe_type.content=metertimeframecode::e11 or self.payload.reconciliation_detail.annual_period.metertimeframe_type.content=metertimeframecode::e12 or self.payload.reconciliation_detail.annual_period.metertimeframe_type.content=metertimeframecode::e29

18 ebix Business information model for Notify MP characteristics in the energy domain 18 # Specification Constrained Element Applied Stereotype inv: self.payload.reconciliation_detail.annual_period.metertimeframe_type.listidentifier->size()=0 inv: self.payload.reconciliation_detail.annual_period.metertimeframe_type.listagencyidentifier=codelistresponsibleagencycode::260 inv: self.payload.mp_address.identification->size()=0 inv: self.payload.mp_address.postofficebox->size()=0 inv: self.payload.mp_address.citysubdivisionname->size()=0 inv: self.payload.mp_address.streetcode->size()=0 inv: self.payload.mp_address.buildingnumberextension->size()=0 inv: self.payload.mp_address.municipalitycode->size()= Mapping BRS-BIM for Notify MP characteristics

19 ebix Business information model for Notify MP characteristics in the energy domain 19

Business Requirements. for. cancellation of business documents

Business Requirements. for. cancellation of business documents Business Requirements for cancellation of business documents Status: Approved by ebix Forum Version/release: 2.0 Revision: A Date: December 2015 ebix Business requirements for cancellation of business