Measure - mwgstorage1.blob.core.windows.net · European Energy Market. This model is part of the...

Business information model

for

Measure

for

Collected Data

Status: approved

Version: 2014

Release: A

Revision: -

Date: July, 2015

ebIX® Business Information Model for Measure for Collected Data page 2

ebIX® July, 2015

C O N T E N T

A. About this document ......................................................................................................................... 4

A.1. References ..................................................................................................................................... 4

A.1.1. International open standards used: ........................................................................................... 4

A.1.2. ebIX® Document references ....................................................................................................... 4

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

1. Introduction ....................................................................................................................................... 8

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

1.2. About the ebIX® Model .............................................................................................................. 8

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

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

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

1.6. Mapping to technology of choice .............................................................................................. 9

2. Business Choreography View: Collect .............................................................................................. 10

2.1. Exchange Collected Data (Business Realization) ...................................................................... 10

2.2. Exchange Collected Data (Business Collaboration) .................................................................. 10

2.2.1. Description ........................................................................................................................... 10

2.2.2. Exchange Collected Data ...................................................................................................... 11

2.3. Exchange Collected Data (Business Transaction)..................................................................... 12

2.3.1. Description ........................................................................................................................... 12

2.3.2. Exchange Collected Data ...................................................................................................... 13

2.4. Request Collected Data (Business Realization) ........................................................................ 14

2.5. Request Collected Data (Business Collaboration) .................................................................... 14

2.5.1. Description ........................................................................................................................... 14

2.5.2. Request Collected Data ........................................................................................................ 15

2.6. Request Collected Data (Business Transaction) ....................................................................... 15

2.6.1. Description ........................................................................................................................... 15


ebIX® July, 2015

2.6.2. Request Collected Data ........................................................................................................ 16

3. Modeled Business Information: Collect (Business Information View) ............................................ 17

3.1. Collected Data (Business Information) .................................................................................... 18

3.1.1. Mapping BRS Collected Data to BIE’s ................................................................................... 19

3.1.2. OCL constraints for CollectedData <<MA>> ........................................................................ 20

3.2. Request Collected Data (Business Information) ...................................................................... 24

3.2.1. Mapping BRS Request Collected Data to BIE’s..................................................................... 25

3.2.2. OCL constraints for RequestCollectedData <<MA>> ........................................................... 26

3.3. Negative Response Request Collected Data (Business Information) ...................................... 29

3.3.1. Mapping BRS Negative Response Request Collected Data to BIE’s ..................................... 30

3.3.2. OCL constraints for NegativeResponseRequestCollectedData <<MA>> ............................. 31

3.4. Response Request Collected Data (Business Information) ...................................................... 34

3.4.1. OCL constraints for Response Request Collected Data <<InfEnvelope>> ........................... 34


ebIX® July, 2015

A. About this document This document contains the Business Information Model for Measure for Collected Data. This model is

based on the ebIX® Business Requirements for Measure for Collected Data [9] version 2r1.

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® EMD.

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 used1: [1] UML Profile for UN/CEFACT’s Modeling Methodology (UMM), Base Module,

(http://www.unece.org/cefact/umm/umm_index.html)

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

(http://www.unece.org/cefact/umm/umm_index.html)

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

(http://www.unece.org/tradewelcome/un-centre-for-trade-facilitation-and-e-business-

uncefact/outputs/technical-specifications.html)

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

(http://www.unece.org/tradewelcome/un-centre-for-trade-facilitation-and-e-business-

uncefact/outputs/technical-specifications.html)

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

(http://www.unece.org/cefact/xml/xml_index.html)

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

(http://www.unece.org/cefact/codesfortrade/unccl/ccl_index.html)

[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)

1 The versions and websites in the references reflect the status on the moment of creation of this document.

http://www.unece.org/cefact/umm/umm_index.html

http://www.unece.org/cefact/umm/umm_index.html

http://www.unece.org/tradewelcome/un-centre-for-trade-facilitation-and-e-business-uncefact/outputs/technical-specifications.html




http://www.unece.org/cefact/xml/xml_index.html

http://www.unece.org/cefact/codesfortrade/unccl/ccl_index.html

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

http://www.ebix.org/


ebIX® July, 2015

[9] Business Requirements for Measure Collected Data (www.ebix.org)

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

(www.ebix.org)

[11] ebIX® Rules for the use of OCL statements (www.ebix.org )

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

Version 0.1.B

Replace ABIE

used (§ 3.2)

Energy_TimeS

eries

MeasuredDa

ta_Request

During the modeling of

subsequent processes, the

need for a special ABIE for

requests for measured

data arose.

2010-09-19

Version 0.1.C

Introductory

chapters (0

and 1)

Textual changes in order

to make the chapters

more consistent and easier

to read

2010-09-27

Version 0.1.D

Numbering format for the

introductory part of the

document (§ A) has been

changed.

2010-10-05

Numbering format for the

referenced documents has

been changed ([..])

2010-10-05

Lay-out of bCollaborations

has been updated

2010-10-05

Response Request

Collected Data has been

added (§ 3.4)

2010-10-05

Version 2010.A

All class

diagrams

Based on ABIE

version 2010.A

Based on

ABIE version

ABIE’s have been updated

because of labeling

2011-01-28





ebIX® July, 2015

2010.B requirements

All class

diagrams

OCL-statements in

constraints have been

updated because of

updated ABIE’s

2011-01-28

Class diagrams

for Collected

Data, Request

Collected Data

and Negative

Response

Request

Collected Data

Added reason code for

labeling to OCL-

statements in constraints

2011-01-28

Version 2010.B

All <<MA>>’s Based on ABIE’s version

2011.A. OCL-statements in

constraints have been

updated accordingly.

2011-08-19

Version 2011.A

References References have been

brought up-to-date

September 2013

ebIX®

Document

references

ebIX® Rules

for the use

of OCL

statements

This document has been

added to the list of

references

September 2013

Business

partners and

authorized

roles

Authorized roles have

been added

September 2013

Class

diagrams,

payload

Cardinality changed into

1..* and as a consequence

in the constraint for the

structure of the payload a

statement has been added

to set the cardinality for

the payload to 1 (in the

document version it is

1..*)

September 2013


ebIX® July, 2015

OCL

statements

OCL statements have been

updated and brought in

line with updated Business

Requirements and

updated ABIE’s

September 2013

All class

diagrams

OCL statements are shown

now in tables that are

included in the UML

model.

March 2014

All class

diagrams

The root class (<<MA>>)

now inherits from a

standard <<MA>>-cluster

as opposed to composing

each <<MA>> individually

from ABIE’s.

March 2014

All class

diagrams

Tables containing mapping

information (BRS to BIM)

have been added.

March 2014

All class

diagrams

Based on ABIE

version 2011.A

Based on

ABIE version

2014.A

ABIE used for collected

data changed to

CollectedData_TimeSeries

April 2014

Version 2014.A


ebIX® July, 2015

1. Introduction

1.1. Place in the overall model for the European Energy Market This document contains the Business Information Model for the exchange of Collected Data in the

European Energy Market. This model is part of the overall ebIX® business domain for Measure.

1.2. About the ebIX® Model The documents for the domain Measure describe a model for the exchange of metered data in the

European Energy Market. The model will, when the modeling project will 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 Measure for Collected Data are specified in a separate document [9].

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

Measure for Collected Data.

1.3. Objectives This ebIX® Business Information Model shall specify the exchange of collected data as business

information in line with the ebIX® business requirements for the exchange of collected data [9] and in

line with the UN/Cefact Modeling Methodology version 2.0 ([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 Measure domain of the overall ebIX® model and focuses on the exchange of

collected data.


ebIX® July, 2015

1.5. Actors, parties and roles In the modeled 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 organizational 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 [10]. In this document the following business partners (<<BusinessPartner>>) are taken from the business requirements:

Collector

Validator

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:

Metered Data Collector

Metered Data Responsible

In the model the <<Harmonized Role>> from the Role Model is mapped to an <<AuthorizedRole>>. In

this document the following authorized roles (<<AuthorizedRole>>) are used:

Collector

Metering Responsible

1.6. Mapping to technology of choice Information on the available mappings to technology of choice is to be found in the document “ebIX®

Introduction to Business Requirements and Information Models” [8].


ebIX® July, 2015

2. Business Choreography View: Collect

2.1. Exchange Collected Data (Business Realization)

Figure 1 Realization: Exchange Collected Data

2.2. Exchange Collected Data (Business Collaboration)

Figure 2 Collaboration: Exchange Collected Data

2.2.1. Description No detailed description for the Collaboration. For detailed description see Business Transaction.

Exchang e Collected Data Exchang e Collected Datause case [ ]

«bCollaborationUC»

Exchange Collected

Data

«bRealizationUC»

Exchange

Collected Data

«bPartner»

Validator

«AuthorizedRole»


«Harmonized Role»

Metered Data

Collector

«Harmonized Role»

Metered Data

Responsible

«AuthorizedRole»

Collector

«bPartner»

Collector

«participates»«participates»

«participates»«participates»

«mapsTo»«mapsTo»«realizes»

«mapsTo» «mapsTo»


<<bCollaborationUC>>

Exchange Collected

Data

<<bTransactionUC>>

Exchange

Collected Data

<<AuthorizedRole>>

Metering Responsible<<AuthorizedRole>>

Collector

<<participates>> <<participates>>

<<include>>


ebIX® July, 2015

2.2.2. Exchange Collected Data

Figure 3 Collaboration: Exchange Collected Data

Exchang e Collected Data Exchang e Collected Dataactiv ity [ ]

«bCPartition»

Collector

«bCPartition»


«bTransactionAction»

: Exchange

Collected Data

BusinesSuccess

Initial

«initFlow» «initFlow»

[CollectedData.Exchanged]


ebIX® July, 2015

2.3. Exchange Collected Data (Business Transaction)

Figure 4 Transaction: Exchange Collected Data

2.3.1. Description

UseCase description: Exchange Collected Data

definition Collector sends collected data to Metering Responsible

beginsWhen Collector decides to.

preCondition Checked Collected Data are available.

endsWhen The reception of the collected data has been acknowledged by the Metering

Responsible.

postCondition Collected Data are available for the Metering Responsible.

exceptions none

actions See 2.3.2


<<bTransactionUC>>

Exchange

Collected Data<<AuthorizedRole>>

Metering Responsible<<AuthorizedRole>>

Collector



ebIX® July, 2015

2.3.2. Exchange Collected Data

Figure 5 Transaction: Exchange Collected Data

Exchang e Collected Data Exchang e Collected Dataactiv ity [ ]

BusinessSuccess

<<ResAction>>

receive

collected data

<<bTPartition>>

Collector

<<bTPartition>>


<<bESharedState>>

: Collected Data

[Exchanged]

<<ReqAction>>

send collected

data

<<ReqInfPin>>

CollectedData

Initial

ControlFailure


ebIX® July, 2015

2.4. Request Collected Data (Business Realization)

Figure 6 Realization: Request Collected Data

2.5. Request Collected Data (Business Collaboration)

Figure 7 Collaboration: Request Collected Data

2.5.1. Description No detailed description for the Collaboration. For detailed description see Business Transaction.

Req uest Collected Data Req uest Collected Datause case [ ]

«bCollaborationUC»

Request Collected Data

«bRealizationUC»

Request

Collected Data

«AuthorizedRole»


«Harmonized Role»

Metered Data

Collector

«Harmonized Role»

Metered Data

Responsible

«AuthorizedRole»

Collector

«bPartner»

Validator

«bPartner»

Collector

«participates»

«participates»

«participates»

«participates»

«realizes»«mapsTo» «mapsTo»

«mapsTo» «mapsTo»


<<bCollaborationUC>>

Request Collected Data

<<bTransactionUC>>

Request Collected

Data

<<AuthorizedRole>>


<<AuthorizedRole>>

Collector


<<include>>


ebIX® July, 2015

2.5.2. Request Collected Data

Figure 8 Collaboration: Request Collected Data

2.6. Request Collected Data (Business Transaction)

Figure 9 Transaction: Request Collected Data

2.6.1. Description UseCase description: Request Collected Data

definition Metering Responsible receives Collected Data from the Collector on request.

beginsWhen Metering Responsible decides to.

preCondition Relation between Collector and Metering Responsible.

endsWhen The reception of the collected data has been acknowledged by the Metering

Responsible.

postCondition Collected Data are available for the Metering Responsible.

exceptions No Collected Data available at the Collectors.

actions See 2.6.2

Req uest Collected Data Req uest Collected Dataactiv ity [ ]

«bCPartition»

Collector«bCPartition»


«bTransactionAction»

: Request Collected

Data

BusinessSuccess

Initial

BusinessFailure

«reFlow»

«initFlow»

«reFlow»

[CollectedData. Exchanged]

«initFlow»

[RequestCollectedData.Rejected]


<<bTransactionUC>>

Request Collected

Data<<AuthorizedRole>>


<<AuthorizedRole>>

Collector

<<participates>><<participates>>


ebIX® July, 2015

2.6.2. Request Collected Data

Figure 10 Transaction: Request Collected Data

Req uest Collected Data Req uest Collected Dataactiv ity [ ]

«ReqAction»

Query

«ReqInfPin»

: Req uest Collected Data

ControlFailure

Initial

«ResAction»

Respond

«ResInfPin»

: Response Req uest Collected Data

ControlFailure

«bTPartition»


«bTPartition»

Collector

«bESharedState»

: Collected Data

[Exchanged]

«bESharedState»

: Request Collected Data

[Rejected]

BusinessSuccess

BusinessFailure


ebIX® July, 2015

3. Modeled Business Information: Collect (Business Information View)

See next page


ebIX® July, 2015

3.1. Collected Data (Business Information)

Figure 11 Collected Data


ebIX® July, 2015

3.1.1. Mapping BRS Collected Data to BIE’s


ebIX® July, 2015

3.1.2. OCL constraints for CollectedData <<MA>>

# Specification Constrained

Element Applied Stereotype

1 -- Structure CollectedData_TimeSeries

-- Collected Data

self.Payload.Identification->size()<=1

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

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

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

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

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

inv: self.Payload.Observation_Period.Resolution_Duration->size()<=1

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

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

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

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

inv: self.Payload.Generation_Installation->isEmpty()

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

inv: self.Payload.Metering_Installation->forAll (Meter_Identification->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation->notEmpty()

inv: self.Payload.Metering_Installation.Register_Installation->forAll (Register_Identification->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation->forAll (Meter_Read->notEmpty())

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Sequence->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_DateTime-

>isEmpty())

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_Measure->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_Missing->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_Measure->size()=1

xor Read_Missing->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll

(MeterReadingOrigin_Type->size()=0)

CollectedData invariant [Constraint]

document [Constraint]

payload [Constraint]

abie [Constraint]

bdt [Constraint]

2 -- BDT CollectedData_TimeSeries

-- Collected Data

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

inv: self.Payload.Observation_Period.Resolution_Duration.content="PT15M"

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

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

inv: self.Payload.MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or


bdt [Constraint]




ebIX® July, 2015



self.Payload.MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27

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

inv: self.Payload.MeterReadingOrigin_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

inv:

self.Payload.MeteringPoint_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9

inv: self.Payload.Metering_Installation->forAll (Meter_Identification.schemeIdentifier->size()<=1)

inv: self.Payload.Metering_Installation->forAll (Meter_Identification.schemeAgencyIdentifier->size()<=1)

inv: self.Payload.Metering_Installation.Register_Installation->forAll

(Register_Identification.schemeIdentifier->size()=0)


(Register_Identification.schemeAgencyIdentifier->size()=0)

--inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll

(MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or

MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27)


(MeterReadingOrigin_Type.listIdentifier->size()=0)


(MeterReadingOrigin_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read.Read_Missing.content=true

3 -- Structure Energy_Document

-- Collected Data

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

CollectedData abie [Constraint]


invariant [Constraint]

4 -- BDT Energy_Document

-- Collected Data

CollectedData bdt [Constraint]



ebIX® July, 2015



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

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

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

inv: self.Header.Creation.timeZoneCode->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.Sender.Identification.schemeIdentifier->size()=0

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

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


5 -- Structure Energy_Context

-- Collected Data

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

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

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




6 -- BDT Energy_Context

-- Collected Data

self.Process.Energy_BusinessProcess.content=BusinessReasonCode::E01 or











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

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

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

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





ebIX® July, 2015



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

inv: self.Process.Energy_BusinessProcessRole.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

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

inv: self.Process.Energy_IndustryClassification.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

7 -- Structure Document

-- Collected Data

self.Header->size()=1

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



8 -- Structure Payload

-- Collected Data



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




ebIX® July, 2015

3.2. Request Collected Data (Business Information)

Figure 12 Request Collected Data


ebIX® July, 2015

3.2.1. Mapping BRS Request Collected Data to BIE’s


ebIX® July, 2015

3.2.2. OCL constraints for RequestCollectedData <<MA>>

# Specification Constrained Element Applied Stereotype

1 -- Structure MeasuredData_Request

-- Request Collected Data

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

inv: self.Payload.Metering_Installation.Meter_Identification->size()<=1

inv: self.Payload.Metering_Installation.Register_Installation->notEmpty()

inv: self.Payload.Metering_Installation.Register_Installation->forAll (Register_Identification->size()=1)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->isEmpty()

RequestCollectedData invariant [Constraint]

abie [Constraint]



2 -- BDT MeasuredData_Request


self.Payload.Request_Period.Start.timeZoneCode->size()=0

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


inv:


inv: self.Payload.Metering_Installation->forAll (Meter_Identification.schemeIdentifier->size()=0)

inv: self.Payload.Metering_Installation->forAll (Meter_Identification.schemeAgencyIdentifier->size()<=1)

inv: self.Payload.Metering_Installation->forAll


bdt [Constraint]




ebIX® July, 2015


(Meter_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)


(Register_Identification.schemeIdentifier->size()=0)


(Register_Identification.schemeAgencyIdentifier->size()<=1)


(Register_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)










RequestCollectedData abie [Constraint]





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










RequestCollectedData bdt [Constraint]







ebIX® July, 2015






abie [Constraint]




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









RequestCollectedData bdt [Constraint]







inv: self.Proposed->size()=0







inv: self.Proposed->size()=0




ebIX® July, 2015

3.3. Negative Response Request Collected Data (Business Information)

Figure 13 Negative Response Request Collected Data


ebIX® July, 2015

3.3.1. Mapping BRS Negative Response Request Collected Data to BIE’s


ebIX® July, 2015

3.3.2. OCL constraints for NegativeResponseRequestCollectedData <<MA>>


1 -- Structure Response_Event

-- NegativeResponseRequestCollectedData

self.Payload.Identification->size()<=1

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

NegativeResponseRequestCollectedData invariant [Constraint]

abie [Constraint]



2 -- BDT Response_Event


--self.Payload.Status_Type.content=ResponseConditionCode::41

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

--inv: self.Payload.Status_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

self.Payload.ResponseReason_Type-> forAll (content=ResponseReasonDescriptionCode::E10 or

content=ResponseReasonDescriptionCode::E11 or content=ResponseReasonDescriptionCode::E50 or

content=ResponseReasonDescriptionCode::E55 or content=ResponseReasonDescriptionCode::E61 or

content=ResponseReasonDescriptionCode::E62 or content=ResponseReasonDescriptionCode::E0H)

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

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


inv:


bdt [Constraint]




ebIX® July, 2015




-- Negative Request Request Collected Data








NegativeResponseRequestCollectedData abie [Constraint]





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










NegativeResponseRequestCollectedData bdt [Constraint]




-- Negative Response Request Collected Data








ebIX® July, 2015















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
















NegativeResponseRequestCollectedData document [Constraint]









ebIX® July, 2015

3.4. Response Request Collected Data (Business Information)

Figure 14 Response Request Collected Data

3.4.1. OCL constraints for Response Request Collected Data <<InfEnvelope>>


1 -- Dependency Response Request Collected Data

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

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

Response Request Collected Data dependency [Constraint]


Response Req uest Collected Data Response Req uest Collected Datapackage [ ]

«M A»

Negativ eResponseRequestCollectedData

«InfEnvelope»

Response Request Collected Data

«M A»

CollectedData+Positive

0..1

+Neg ative

0..1

Date post:	05-Jul-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Measure - mwgstorage1.blob.core.windows.net · European Energy Market. This model is part of the...

Documents