Change of Balance Responsible Party - Microsoft · ebIX® Business Information Model for Change of Balance Responsible Party 7 ebIX® November 2015 1. Introduction 1.1. Place in the

Business information model

for

Change of Balance Responsible Party

Status: Approval by ETC Version: 2015 Release: A Revision: - Date: November 2015

ebIX® Business Information Model for Change of Balance Responsible Party 2

ebIX® November 2015

C O N T E N T

A. About this document ................................................................................................................................... 5

A.1. References ............................................................................................................................................... 5

A.1.1. International open standards used ...................................................................................................... 5

A.1.2. ebIX® Document references ................................................................................................................ 5

A.2. Main changes since last version ............................................................................................................... 6

1. Introduction ................................................................................................................................................. 7

1.1. Place in the overall model for the European Energy Market .................................................................. 7

1.2. About the ebIX® Model ............................................................................................................................ 7

1.3. Objectives................................................................................................................................................. 8

1.4. Scope ........................................................................................................................................................ 8

1.5. Actors, parties and roles .......................................................................................................................... 9

1.6. Annexes for mapping to technology of choice ........................................................................................ 9

2. Business Choreography View: Change of Balance Responsible Party ....................................................... 10

2.1. UseCase Change of Balance Responsible Party (Business Realization) ................................................. 10

2.1.1. UseCase Change of Balance Responsible Party (Business Collaboration) ..................................... 10

2.1.1.1. Description ................................................................................................................................. 11

2.1.2. Change of Balance Responsible Party (Business Collaboration Protocol) ..................................... 12

2.2. UseCase Request Change of Balance Responsible Party ....................................................................... 12

2.2.1. UseCase Request Change of Balance Responsible Party (Business Collaboration) ....................... 12

2.2.1.1. Description ................................................................................................................................. 13

2.2.1.2. Request Change of Balance Responsible Party (Business Collaboration Protocol) ................... 13

2.2.1.3. UseCase Request Change of Balance Responsible Party (Business Transaction) ...................... 13

2.2.1.3.1. Description ................................................................................................................................. 13

2.2.1.3.2. Request Change of Balance Responsible Party (Business Transaction) ..................................... 15

2.3. Notify Change of Balance Responsible Party ......................................................................................... 16

2.3.1. UseCase Notify Change of Balance Responsible Party to old affected role (Business

Collaboration) ................................................................................................................................................ 16



2.3.1.1. Description ................................................................................................................................. 16

2.3.1.2. Notify Change of Balance Responsible Party to old affected role (Business Collaboration

protocol) 16

2.3.1.3. UseCase Notify Change of Balance Responsible Party (Business Transaction) ......................... 17

2.3.1.3.1. Description ................................................................................................................................. 17

2.3.1.3.2. Notify Change of Balance Responsible Party to old affected role (Business Transaction) ........ 18

2.3.2. UseCase Notify Change of Balance Responsible Party to new affected role (Business

Collaboration) ................................................................................................................................................ 18

2.3.2.1. Description ................................................................................................................................. 19

2.3.2.2. Notify Change of Supplier to new affected role (Business Collaboration protocol) .................. 19

2.3.2.3. UseCase Notify Change of Balance Responsible Party (Business Transaction) ......................... 19

2.3.2.3.1. Description ................................................................................................................................. 19

2.3.2.3.2. Notify Change of Balance Responsible Party to new affected role (Business Transaction) ...... 20

3. Business Information View: Change of Balance Responsible Party ........................................................... 21

3.1. Request Change of Balance Responsible Party (Business Information) ................................................ 21

3.1.1. OCL constraints for Request Change of Balance Responsible Party <<MA>> ............................... 22

3.1.2. Mapping BRS-BIM for Request Change of Balance Responsible Party .......................................... 27

3.2. Response Change of Balance Responsible Party (Business Information) .............................................. 28

3.2.1. OCL constraints for Response Change of Balance Responsible Party <<InfEnvelope>> ................ 28

3.2.2. Confirm Change of Balance Responsible Party (Business Information) ........................................ 29

3.2.3. OCL constraints for Confirm Change of Balance Responsible Party <<MA>> ................................ 30

3.2.4. Mapping BRS-BIM for Confirm Change of Balance Responsible Party .......................................... 34

3.2.5. Reject Change of Balance Responsible Party (Business Information) ........................................... 35

3.2.6. OCL constraints for Reject Change of Balance Responsible Party <<MA>>................................... 36

3.2.7. Mapping BRS-BIM for Reject Change of Balance Responsible Party ............................................. 40

3.3. Notify Change of Balance Responsible Party (Business Information) ................................................... 41

3.3.1. OCL constraints for Notify Change of Balance Responsible Party <<InfEnvelope>> ..................... 41

3.3.2. Notify Change of Balance Responsible Party to new affected role (Business Information) .......... 42



3.3.3. OCL constraints for Notify Change of Balance Responsible Party to new affected role <<MA>> . 43

3.3.4. Mapping BRS-BIM for Notify Change of Balance Responsible Party to new affected role ........... 48

3.3.5. Notify Change of Balance Responsible Party to old affected role (Business Information) ............ 49

3.3.6. OCL constraints for Notify Change of Balance Responsible Party to old affected role <<MA>> ... 50

3.3.7. Mapping BRS-BIM for Notify Change of Balance Responsible Party to old affected role ............. 55



A. About this document This document contains the Business Information Model for Change of Balance Responsible Party. This

model is based on the ebIX® Business Requirements for Change of Balance Responsible Party [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 Modeling Methodology (UMM), Base Module, Candidate for 2.0. Draft

for IMPLEMENTATION VERIFICATION, 2010‐01‐29 (http://www.untmg.org/specifications/)

[2] UML Profile for UN/CEFACT’s Modeling Methodology (UMM), Foundation Module, Candidate for 2.0.

Draft for IMPLEMENTATION VERIFICATION, 2010‐01‐29 (http://www.untmg.org/specifications/)

[3] UN/CEFACT Core Components Technical Specification Version 3.0, 29 September 2009

(http://www.unece.org/cefact/codesfortrade/CCTS/CCTS-Version3.pdf)

[4] UN/CEFACT UML Profile for Core Components Technical Specification 3.0 Open Development Process

Step 5 “Public Review” NOT FOR IMPLEMENTATION 2010‐01‐29

[5] UN/CEFACT XML Naming and Design Rules Technical Specification Version 3.0, 17 December 2009

(http://www.unece.org/fileadmin/DAM/cefact/xml/UNCEFACT+XML+NDR+V3p0.pdf)

[6] UN/CEFACT Core Components Data Type Catalogue Version 3.0, 29 September 2009

(http://www.unece.org/cefact/codesfortrade/CCTS/CCTS-DataTypeCatalogueVersion3p0.pdf)

[7] Object Constraint Language, OMG Available Specification Version 2.0 formal, 1 May 2006

(http://www.omg.org/spec/OCL/2.0/)

A.1.2. ebIX® Document references [8] Introduction to ebIX® Business Requirements and Information Models (www.ebix.org)

[9] Business Requirements for Change of Balance Responsible Party (www.ebix.org)

[10] The Harmonized Role Model (for the Electricity Market) by ebIX®, ENTSO-E, and EFET (www.ebix.org)

http://www.untmg.org/specifications/

http://www.untmg.org/specifications/

http://www.unece.org/cefact/codesfortrade/CCTS/CCTS-Version3.pdf

http://www.unece.org/fileadmin/DAM/cefact/xml/UNCEFACT+XML+NDR+V3p0.pdf

http://www.unece.org/cefact/codesfortrade/CCTS/CCTS-DataTypeCatalogueVersion3p0.pdf

http://www.omg.org/spec/OCL/2.0/

http://www.ebix.org/





A.2. Main changes since last version Subject Old New Clarification Date

Version 2014.A

First version 20151109



1. Introduction

1.1. Place in the overall model for the European Energy Market This document contains the Business Information Model for the Change of Balance Responsible Party 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.

1.2. 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 Request Change of Balance Responsible Party are specified in a separate

document, see [9].

This document contains the Business Choreography View and the Business Information View for the Change

of Balance Responsible Party 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.



1.3. Objectives This ebIX® Business Information Model shall specify the Change of Balance Responsible Party business

information in line with the ebIX® business requirements for the Change of Balance Responsible Party

processes, see [9], in line with the UN/CEFACT Modelling Methodology version 2.0, see [1] 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®.

1.4. Scope This model belongs to the Structure domain of the overall ebIX® model and focuses on Change of Balance

Responsible Party.



1.5. Actors, parties and roles In the model actors are either presented as <<Business Partner>> 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 (see [2]).

A harmonized role represents a specific responsibility in the European Energy Market related to the exchange of information (see [10]).

In this document the following <<Business Partners>> are taken from the business requirements:

New Balance Responsible Party

Old Balance Responsible Party

Metering Point Administrator

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 Supplier

Balance Responsible Party

Metering Point Administrator

1.6. Annexes for mapping to technology of choice Information on available mapping to technology of choice (XML, EDIFACT, web services) can be found in the

document Introduction to ebIX® Business Requirements and Information Models (www.ebix.org) [8].



2. Business Choreography View: Change of Balance Responsible Party

2.1. UseCase Change of Balance Responsible Party (Business Realization)

Figure 1 Realization: Change of Balance Responsible Party

2.1.1. UseCase Change of Balance Responsible Party (Business Collaboration)

Figure 2 Collaboration UC: Change of Balance Responsible Party

Notes to the diagram:

The Use Case Notify MP characteristics and can be found in separate Business information models,

see www.ebix.org.




2.1.1.1. Description UseCase description: Change of Balance Responsible Party

definition This is the process where a New Balance Responsible Party will be registered

in the Metering Point register at the request of the Balance Supplier for the

Metering Point. The Metering Point Administrator makes all necessary

updates for the change, including distribution of master data for alignment

of the business partner data bases.

beginsWhen When the Balance Supplier decides to change the Balance Responsible Party

for the Metering Point.

preCondition The Balance Supplier supplies the Metering Point and the New Balance

Responsible Party must be authorised.

endsWhen When the change of Balance Responsible Party is confirmed or rejected, and

if confirmed then all relevant parties have been notified and have received

master data.

postCondition The New Balance Responsible Party is linked to the Metering Point and all

relevant parties have aligned master data or (in case of rejection) nothing is

changed in the Metering Point register.

exceptions The change of Balance Responsible Party may at a national level be handled

by other roles than the Balance Supplier, such as the Balance Responsible

Party itself or the Party Connected To Grid.

actions See 2.1.2



2.1.2. Change of Balance Responsible Party (Business Collaboration Protocol)

Figure 3 Collaboration: Change of Balance Responsible Party

2.2. UseCase Request Change of Balance Responsible Party

2.2.1. UseCase Request Change of Balance Responsible Party (Business

Collaboration)

Figure 4 Business Collaboration UC: Request Change of Balance Responsible Party



2.2.1.1. Description No detailed description for the Collaboration. For detailed description see 2.2.1.3.1.

2.2.1.2. Request Change of Balance Responsible Party (Business

Collaboration Protocol)

Figure 5 Collaboration: Request Change of Balance Responsible Party

2.2.1.3. UseCase Request Change of Balance Responsible Party (Business

Transaction)

Figure 6 Transaction: Request Change of Balance Responsible Party

2.2.1.3.1. Description

UseCase description: Request Change of Balance Responsible Party

definition In this process the Balance Supplier will request Change of Balance

Responsible Party at a Metering point and the Metering Point

Administrator confirms or rejects it. During the business process the

change is confirmed and the Metering point register will be updated,

or the change is rejected.



beginsWhen When the Balance Supplier decides to send a request for Change of

Balance Responsible Party in order to achieve the intended start of

supply date for the new supply contract, to the Metering Point

Administrator.

preCondition A supply contract is in place

A start of supply date has been agreed with the Energy consumer.

The requirements from Make supply contract and Identify and

obtain critical change of balance responsible party information

have been satisfied

endsWhen The request for Change of Balance Responsible Party is confirmed or

rejected

postCondition The Change of Balance Responsible Party process has been accepted

or rejected by the Metering Point Administrator to the Balance

Supplier.

exceptions None

actions See 0



2.2.1.3.2. Request Change of Balance Responsible Party (Business Transaction)

Figure 7 Business transaction: Request Change of Balance Responsible Party



2.3. Notify Change of Balance Responsible Party

2.3.1. UseCase Notify Change of Balance Responsible Party to old affected role

(Business Collaboration)

Figure 8 Collaboration: Notify Change of Balance Responsible Party to old affected role

2.3.1.1. Description No detailed description for the Collaboration. For detailed description see 2.3.1.3.1.

2.3.1.2. Notify Change of Balance Responsible Party to old affected role

(Business Collaboration protocol)

Figure 9 Collaboration: Notify Change of Balance Responsible Party to old affected role



2.3.1.3. UseCase Notify Change of Balance Responsible Party (Business

Transaction)

Figure 10 Business transaction UC: Notify Change of Balance Responsible Party to old affected role

2.3.1.3.1. Description

Definition In this process the Metering Point Administrator will notify the old affected

roles (the old BRP/TRP) of the Change of Balance Responsible Party in the

Metering point and the related changing date.

Begins when Defined by national rules after the change has been effectuated by the

Metering Point Administrator.

Preconditions The Request Change of Balance Responsible Party process has been

confirmed by the Metering Point Administrator

The Metering point register has been updated with the New Balance

Responsible Party

Ends when The affected roles have received the notification

Post condition The Change of Balance Responsible Party is notified to the affected roles.

Exceptions If required by national rules the (old and new) Balance Responsible Party or

the Transport Capacity Responsible Party may not be notified.

Actions See 2.3.1.3.2



2.3.1.3.2. Notify Change of Balance Responsible Party to old affected role

(Business Transaction)

Figure 11 Transaction: Notify Change of Balance Responsible Party to old affected role

2.3.2. UseCase Notify Change of Balance Responsible Party to new affected role

(Business Collaboration)

Figure 12 Collaboration: Notify Change of Balance Responsible Party to new affected role



2.3.2.1. Description No detailed description for the Collaboration. For detailed description, see 2.3.2.3.1.

2.3.2.2. Notify Change of Supplier to new affected role (Business

Collaboration protocol)

Figure 13 Collaboration: Notify Change of Balance Responsible Party to new affected role

2.3.2.3. UseCase Notify Change of Balance Responsible Party (Business

Transaction)

Figure 14 Business transaction UC: Notify change of Balance Responsible Party to new affected role

2.3.2.3.1. Description Definition In this process the Metering Point Administrator will notify the new affected

role (the new BRP) of the Change of Balance Responsible Party in the

Metering point and the related changing date.



Begins when Defined by national rules after the Metering Point Administrator has

effectuated the change.

Preconditions The Request Change of Balance Responsible Party process has been

confirmed by the Metering Point Administrator

The Metering point register has been updated with the New Balance

Responsible Party

Ends when The new affected role have received the notification

Post condition The Change of Balance Responsible Party is notified to the affected roles.

Exceptions If required by national rules the (old and new) Balance Responsible Party or

the Transport Capacity Responsible Party may not be notified.

Actions See 0

2.3.2.3.2. Notify Change of Balance Responsible Party to new affected role

(Business Transaction)

Figure 15 Transaction: Notify Change of Balance Responsible Party to new affected role



3. Business Information View: Change of Balance Responsible Party

3.1. Request Change of Balance Responsible Party (Business Information)

Figure 16 Class diagram: Request Change of Balance Responsible Party



3.1.1. OCL constraints for Request Change of Balance Responsible Party <<MA>>

# Specification Constrained Element Applied Stereotype

1 -- Structure Document

-- Request change of balance responsible party

self.Header->size()=1

inv: self.Process->size()=1

RequestChangeofBalanceResponsibleP

arty

abie [Constraint]

document

[Constraint]

invariant

[Constraint]

2 -- Structure Energy_Document


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


arty

abie [Constraint]

document

[Constraint]

invariant

[Constraint]

3 -- BDT Energy_Document


self.Header.Document_Type.content=DocumentNameCode::434

inv: self.Header.Document_Type.listIdentifier->size()=0

inv: self.Header.Document_Type.listAgencyIdentifier->size()=0

inv: self.Header.Creation.timeZoneCode->size()=0

inv: self.Header.Sender.Identification.schemeIdentifier->size()=0


arty

bdt [Constraint]

document

[Constraint]

invariant

[Constraint]




inv:

self.Header.Sender.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9

or


inv: self.Header.Sender.Role.content=BusinessRoleCode::DDQ

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.Recipient.Identification.schemeIdentifier->size()=0

inv:

self.Header.Recipient.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9

or


5

inv: self.Header.Recipient.Role.content=BusinessRoleCode::MDR

inv: self.Header.Recipient.Role.listIdentifier->size()=0

inv: self.Header.Recipient.Role.listAgencyIdentifier->size()=0

inv: self.Header.Recipient.Name.languageCode->size()=0

4 -- Structure Energy_Context


self.Process.Energy_BusinessProcess->size()=1

inv: self.Process.Energy_BusinessProcessRole->size()=1

inv: self.Process.Energy_IndustryClassification->size()=1


arty

abie [Constraint]

invariant

[Constraint]

document

[Constraint]




5 -- BDT Energy_Context


self.Process.Energy_BusinessProcess.content=BusinessReasonCode::E56

inv: self.Process.Energy_BusinessProcess.listIdentifier->size()=0

inv:

self.Process.Energy_BusinessProcess.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

inv: self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::DDQ

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()=0


arty

bdt [Constraint]

invariant

[Constraint]

document

[Constraint]

6 -- Structure Payload





arty

invariant

[Constraint]

payload

[Constraint]

abie [Constraint]

7 --Structure MP_Event

--Request change of balance responsible party

self.Payload.StartOfOccurrence->size()=1

inv: self.Payload.EndOfOccurrence->size()=0

inv: self.Payload.MeteringPoint_Used->size()=1

inv: self.Payload.BalanceSupplier_Involved->size()=1

inv: self.Payload.BalanceSupplier_Involved.Role->size()=0

inv: self.Payload.BalanceSupplier_Involved.Name->size()=0


arty

invariant

[Constraint]

abie [Constraint]

document

[Constraint]

payload

[Constraint]




inv: self.Payload.TransportCapacityResponsible_Involved->size()=0

inv: self.Payload.BalanceResponsible_Involved->size()=1

inv: self.Payload.BalanceResponsible_Involved.Name->size()=0

inv: self.Payload.BalanceResponsible_Involved.Role->size()=0

inv: self.Payload.Consumer_Involved->size()=0

inv: self.Payload.MeteredDataResponsible_Involved->size()=0

inv: self.Payload.BusinessProcess_Reference->size()=0

inv: self.Payload.OriginalBusinessDocument_Reference->size()=0

8 -- BDT MP_Event


self.Payload.StartOfOccurrence.timeZoneCode->size()=0

inv: self.Payload.EndOfOccurrence.timeZoneCode->size()=0


inv: self.Payload.MeteringPoint_Used.Identification.schemeIdentifier->size()=0

inv:

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgenc

yCode::9

inv: self.Payload.BalanceResponsible_Involved.Identification->size()=1

inv: self.Payload.BalanceResponsible_Involved.Identification.schemeIdentifier->size()=0

inv:

self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRespons

ibleAgencyCode::9

or

Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::305

inv: self.Payload.BalanceSupplier_Involved.Identification->size()=1

inv: self.Payload.BalanceSupplier_Involved.Identification.schemeIdentifier->size()=0


arty

invariant

[Constraint]

bdt [Constraint]

document

[Constraint]

payload

[Constraint]




inv:

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::9

or

Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAge

ncyCode::305



3.1.2. Mapping BRS-BIM for Request Change of Balance Responsible Party

Figure 17 Mapping BRS-BIM for Request Change of Balance Responsible Party



3.2. Response Change of Balance Responsible Party (Business Information)

Figure 18 Class diagram: Response Change of Balance Responsible Party

3.2.1. OCL constraints for Response Change of Balance Responsible Party <<InfEnvelope>>


1 -- Dependency Response change of balance responsible party

self.Positive->size()=1 implies self.Negative->size()=0

inv: self.Negative->size()=1 implies self.Positive->size()=0

Response Change of Balance Responsible Party invariant [Constraint]

dependency [Constraint]



3.2.2. Confirm Change of Balance Responsible Party (Business Information)

Figure 19 Class diagram: Confirm Change of Balance Responsible Party



3.2.3. OCL constraints for Confirm Change of Balance Responsible Party <<MA>>



-- Confirm change of balance responsible party



ConfirmChangeofBalanceResponsibleP

arty

abie [Constraint]

document

[Constraint]

invariant

[Constraint]













arty

abie [Constraint]

document

[Constraint]

invariant

[Constraint]








inv: self.Header.Sender.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9


arty

bdt [Constraint]

document

[Constraint]

invariant

[Constraint]




or


inv: self.Header.Sender.Role.content=BusinessRoleCode::MDR





inv:


or


inv: self.Header.Recipient.Role.content=BusinessRoleCode::DDQ










arty

abie [Constraint]

invariant

[Constraint]

document

[Constraint]





inv:



arty

bdt [Constraint]

invariant

[Constraint]

document

[Constraint]







inv: self.Process.Energy_IndustryClassification.content=SectorAreaIdentificationCode::23

or self.Process.Energy_IndustryClassification.content=SectorAreaIdentificationCode::27







arty

invariant

[Constraint]

payload

[Constraint]

abie [Constraint]

7 --Structure Response_Event

--Confirm change of balance responsible party



inv: self.Payload.Status_Type->size()=0

inv: self.Payload.ResponseReason_Type->size()=0










arty

invariant

[Constraint]

abie [Constraint]

document

[Constraint]

payload

[Constraint]





8 -- BDT Response_Event




inv:

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgenc

yCode::9



inv:

self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRespons

ibleAgencyCode::9

or

Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::305



inv:

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::9

or

Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAge

ncyCode::305


arty

invariant

[Constraint]

bdt [Constraint]

document

[Constraint]

payload

[Constraint]



3.2.4. Mapping BRS-BIM for Confirm Change of Balance Responsible Party

Figure 20 Mapping BRS-BIM for Confirm Change of Balance Responsible Party



3.2.5. Reject Change of Balance Responsible Party (Business Information)

Figure 21 Class diagram: Reject Change of Balance Responsible Party



3.2.6. OCL constraints for Reject Change of Balance Responsible Party <<MA>>



-- Reject change of balance responsible party



RejectChangeofBalanceResponsiblePart

y

abie [Constraint]

document

[Constraint]

invariant

[Constraint]













y

abie [Constraint]

document

[Constraint]

invariant

[Constraint]








inv:


y

bdt [Constraint]

document

[Constraint]

invariant

[Constraint]





or


5






inv:


or


05











y

abie [Constraint]

invariant

[Constraint]

document

[Constraint]








inv:









y

bdt [Constraint]

invariant

[Constraint]

document

[Constraint]






y

invariant

[Constraint]

payload

[Constraint]

abie [Constraint]

7 --Structure Response_Event

--Reject change of balance responsible party

self.Payload.EndOfOccurrence->size()=0

inv: self.Payload.StartOfOccurrence->size()=1

inv: self.Payload.Status_Type->size()=0

inv: self.Payload.ResponseReason_Type->notEmpty()

inv: self.Payload.BusinessProcess_Reference->size()=0




y

invariant

[Constraint]

abie [Constraint]

document

[Constraint]

payload

[Constraint]






8 -- BDT Response_Event


self.Payload.ResponseReason_Type.content=ResponseReasonDescriptionCode::E10

or Payload.ResponseReason_Type.content=ResponseReasonDescriptionCode::E16




inv: self.Payload.ResponseReason_Type.listIdentifier->size()=0

inv:

self.Payload.ResponseReason_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260



inv:

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAge

ncyCode::9


y

invariant

[Constraint]

bdt [Constraint]

document

[Constraint]

payload

[Constraint]



3.2.7. Mapping BRS-BIM for Reject Change of Balance Responsible Party

Figure 22 Mapping BRS-BIM for Reject Change of Balance Responsible Party



3.3. Notify Change of Balance Responsible Party (Business Information)

Figure 23 Class diagram: Notify Change of Balance Responsible Party

3.3.1. OCL constraints for Notify Change of Balance Responsible Party <<InfEnvelope>>


1 -- Dependency Notify change of balance responsible party

self.Old->size()=1 implies self.New->size()=0

inv: self.New->size()=1 implies self.Old->size()=0

Notify Change of Balance Responsible Party invariant [Constraint]

dependency [Constraint]



3.3.2. Notify Change of Balance Responsible Party to new affected role (Business Information)

Figure 24 Class diagram: Notify Change of Balance Responsible Party to new affected role



3.3.3. OCL constraints for Notify Change of Balance Responsible Party to new affected role <<MA>>

# Specification Constrained Element Applied

Stereotype


-- Notify change of balance responsible party to new affected role



NotifyChangeofBalanceResponsiblePartytoNe

wAffectedRole

abie

[Constraint]

document

[Constraint]

invariant

[Constraint]













wAffectedRole

abie

[Constraint]

document

[Constraint]

invariant

[Constraint]





inv: self.Header.Document_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260



wAffectedRole

bdt

[Constraint]

document

[Constraint]

invariant

[Constraint]




Stereotype


inv:

self.Header.Sender.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::

9

or

self.Header.Sender.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::

305







inv:

self.Header.Recipient.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode:

:9

or


:305


or self.Header.Recipient.Role.content=BusinessRoleCode::TCR








Stereotype







wAffectedRole

abie

[Constraint]

invariant

[Constraint]

document

[Constraint]





inv:


60

inv: self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::DDK

or self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::TCR







wAffectedRole

bdt

[Constraint]

invariant

[Constraint]

document

[Constraint]


--Notify change of balance responsible party to new affected role




wAffectedRole

invariant

[Constraint]

payload

[Constraint]




Stereotype

abie

[Constraint]











inv: self.Payload.TransportCapacityResponsible_Involved.Role->size()=0

inv: self.Payload.TransportCapacityResponsible_Involved.Name->size()=0







wAffectedRole

invariant

[Constraint]

abie

[Constraint]

document

[Constraint]

payload

[Constraint]

8 -- BDT MP_Event

-- -- Notify change of balance responsible party to new affected role





inv:


wAffectedRole

invariant

[Constraint]

bdt

[Constraint]

document

[Constraint]

payload

[Constraint]




Stereotype

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleA

gencyCode::9



inv:

self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRes

ponsibleAgencyCode::9 or

Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRespon

sibleAgencyCode::305



inv:

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListRespon

sibleAgencyCode::9 or

Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::305

inv: self.Payload.TransportCapacityResponsible_Involved.Identification->size()=0

inv: self.Payload.TransportCapacityResponsible_Involved.Identification.schemeIdentifier-

>size()=0

inv:

self.Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=C

odeListResponsibleAgencyCode::9 or

Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=CodeL

istResponsibleAgencyCode::305



3.3.4. Mapping BRS-BIM for Notify Change of Balance Responsible Party to new affected role

Figure 25 Mapping BRS-BIM for Notify Change of Balance Responsible Party to new affected role



3.3.5. Notify Change of Balance Responsible Party to old affected role (Business Information)

Figure 26 Class diagram: Notify Change of Balance Responsible Party to old affected role



3.3.6. OCL constraints for Notify Change of Balance Responsible Party to old affected role <<MA>>


Stereotype


-- Notify change of balance responsible party to old affected role



NotifyChangeofBalanceResponsiblePartytoOld

AffectedRole

abie

[Constraint]

document

[Constraint]

invariant

[Constraint]













AffectedRole

abie

[Constraint]

document

[Constraint]

invariant

[Constraint]





AffectedRole

bdt

[Constraint]

document




Stereotype


inv: self.Header.Document_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260



inv:


or


05







inv:


:9

or


:305


or self.Header.Recipient.Role.content=BusinessRoleCode::DDK

or self.Header.Recipient.Role.content=BusinessRoleCode::TCR



[Constraint]

invariant

[Constraint]




Stereotype









AffectedRole

abie

[Constraint]

invariant

[Constraint]

document

[Constraint]





inv:


60

inv: self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::DDK

or self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::DDQ

or self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::TCR







AffectedRole

bdt

[Constraint]

invariant

[Constraint]

document

[Constraint]




Stereotype






AffectedRole

invariant

[Constraint]

payload

[Constraint]

abie

[Constraint]











inv: self.Payload.TransportCapacityResponsible_Involved.Role->size()=0

inv: self.Payload.TransportCapacityResponsible_Involved.Name->size()=0







AffectedRole

invariant

[Constraint]

abie

[Constraint]

document

[Constraint]

payload

[Constraint]

8 -- BDT MP_Event

-- -- Notify change of balance responsible party to old affected role




AffectedRole

invariant

[Constraint]

bdt

[Constraint]

document




Stereotype



inv:

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleA

gencyCode::9



inv:

self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRes

ponsibleAgencyCode::9 or

Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListRespons

ibleAgencyCode::305



inv:

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListRespon

sibleAgencyCode::9 or

Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsible

AgencyCode::305

inv: self.Payload.TransportCapacityResponsible_Involved.Identification->size()=0

inv: self.Payload.TransportCapacityResponsible_Involved.Identification.schemeIdentifier-

>size()=0

inv:

self.Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=C

odeListResponsibleAgencyCode::9 or

Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=CodeLi

stResponsibleAgencyCode::305

[Constraint]

payload

[Constraint]



3.3.7. Mapping BRS-BIM for Notify Change of Balance Responsible Party to old affected role

Figure 27 Mapping BRS-BIM for Notify Change of Balance Responsible Party to old affected role

Documents

Change of Balance Responsible Party - Microsoft · ebIX® Business Information Model for Change of Balance Responsible Party 7 ebIX® November 2015 1. Introduction 1.1. Place in the