Measure...ebIX® Business Information Model for Measure for Billing page 6 ebIX® September, 2015...

Business information model

for

Measure

for

Billing

Status: approved

Version: 2014

Release: A

Revision:

Date: September, 2015

ebIX® Business Information Model for Measure for Billing page 2

ebIX® September, 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 ....................................................................................................... 6

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

1.4. Scope .......................................................................................................................................... 7

1.5. Actors, parties and roles ............................................................................................................ 8

1.6. Mapping to technology of choice .............................................................................................. 8

2. Business Choreography View: Measure for Billing ............................................................................ 9

2.1. Exchange Validated Data for Billing Energy (Business Realization) ........................................... 9

2.2. Exchange Validated Data for Billing Energy (Business Collaboration) ..................................... 10

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

2.2.2. Exchange Validated Data for Billing Energy ......................................................................... 10

2.3. Exchange Validated Data for Billing Energy (Business Transaction) ........................................ 11

2.3.1. Description ........................................................................................................................... 11

2.3.2. Exchange Validated Data for Billing Energy ......................................................................... 12

2.4. Exchange Validated Data for Billing Grid Cost (Business Realization) ..................................... 13

2.5. Exchange Validated Data for Billing Grid Cost (Business Collaboration) ................................. 13

2.5.1. Description ........................................................................................................................... 13

2.5.2. Exchange Validated Data for Billing Grid Cost ..................................................................... 14

2.6. Exchange Validated Data for Billing Grid Cost (Business Transaction) .................................... 15

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



2.6.2. Exchange Validated Data for Billing Grid Cost, Supplier Centric .......................................... 16

2.7. Exchange Validated Data for Billing Grid Cost, Supplier Centric (Business Realization) .......... 17

2.8. Exchange Validated Data for Billing Grid Cost, Supplier Centric (Business Collaboration)...... 17

2.8.1. Description ........................................................................................................................... 17


2.9. Exchange Validated Data for Billing Grid Cost, Supplier Centric (Business Transaction) ........ 19

2.9.1. Description ........................................................................................................................... 19


2.10. Exchange Validated Data for Billing Grid Cost (Business Transaction) ................................ 20

2.11. Request Validated Data for Billing Energy (Business Realization) ....................................... 21

2.12. Request Validated Data for Billing Energy (Business Collaboration) ................................... 21

2.12.1. Description ........................................................................................................................... 21

2.12.2. Request Validated Data for Billing Energy ........................................................................... 22

2.13. Request Validated Data for Billing Energy (Business Transaction) ...................................... 22

2.13.1. Description ........................................................................................................................... 22

2.13.2. Request Validated Data for Billing Energy ........................................................................... 23

2.14. Request Validated Data for Billing Grid Cost by Supplier (Business Realization) ................ 24

2.15. Request Validated Data for Billing Grid Cost by Supplier (Business Collaboration) ............ 24

2.15.1. Description ........................................................................................................................... 24

2.15.2. Request Validated Data for Billing Grid Cost by Supplier .................................................... 25

2.16. Request Validated Data for Billing Grid Cost by Supplier (Business Transaction) ............... 25

2.16.1. Description ........................................................................................................................... 25

2.16.2. Request Validated Data for Billing Grid Cost by Supplier .................................................... 26

2.17. Request Validated Data for Billing Grid Cost by Grid Company (Business Realization) ....... 27

2.18. Request Validated Data for Billing Grid Cost by Grid Company (Business Collaboration) .. 27

2.18.1. Description ........................................................................................................................... 27

2.18.2. Request Validated Data for Billing Grid Cost by Grid Company........................................... 28



2.19. Request Validated Data for Billing Grid Cost by Grid Company (Business Transaction) ..... 28

2.19.1. Description ........................................................................................................................... 28

2.19.2. Request Validated Data for Billing Grid Cost by Grid Company........................................... 29

3. Modeled Business Information: Measure for Billing (Business Information View) ......................... 30

3.1. Validated Data for Billing Energy (Business Information) ........................................................ 31

3.1.1. OCL constraints for ValidatedDataForBillingEnergy <<MA>> .............................................. 32

3.1.2. Mapping BRS-BIM for Validated Data for Billing Energy...................................................... 37

3.2. Validated Data for Billing Grid Cost (Business Information) .................................................... 38

3.2.1. OCL constraints for ValidatedDataForBillingGridCost <<MA>> ........................................... 39

3.2.2. Mapping BRS-BIM for Validated Data for Billing Grid Cost .................................................. 45

3.3. Request Validated Data for Billing Energy (Business Information) .......................................... 46

3.3.1. OCL constraints for RequestValidatedDataForBillingEnergy <<MA>> ................................. 47

3.3.2. Mapping BRS-BIM for Request Validated Data for Billing Energy ....................................... 53

3.4. Request Validated Data for Billing Grid Cost (Business Information) ...................................... 54

3.4.1. OCL constraints for RequestValidatedDataForBillingGridCost <<MA>> .............................. 55

3.4.2. Mapping BRS-BIM for Request Validated Data for Billing Grid Cost .................................... 61

3.5. Negative Response Request Validated Data for Billing (Business Information) ...................... 62

3.5.1. OCL constraints for NegativeResponseRequestValidatedDataForBilling <<MA>> .............. 63

3.5.2. Mapping BRS-BIM for Negative Response Request Validated Data for Billing .................... 66

3.6. Response Request Validated Data for Billing Energy (Business Information) ......................... 67

3.6.1. OCL constraints for Response Request Validated Data For Billing Energy <<InfEnvelope>>

67

3.7. Response Request Validated Data for Billing Grid Cost (Business Information) ..................... 68

3.7.1. OCL constraints for Response Request Validated Data For Billing Grid Cost

<<InfEnvelope>> .................................................................................................................................. 68



A. About this document This document contains the Business Information Model for Measure for Billing energy and/or grid

cost. This model is based on the ebIX® Business Requirements for Measure for Billing [9] version 2r0B.

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

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/



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

[9] Business Requirements for Measure for Billing (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

End of Version 2014.A

ValidatedDataf

orBillingEnerg

y and

ValidatedDataf

orBillingGridC

ost,

constraints for

Structure

Energy_TimeS

eries

Cardinality

Meter_Read

(in

MeteringInstal

lation)

specifically

stated as

notEmpty

This line in the constraint

was defined as text (and

therefore ignored).

11-8-2014

NegativeRespo

nsetoRequest

ValidatedDataf

orBilling,

constraints for

Structure

Response_Eve

nt

The constraint has not

been changed, since it is

correctly specifying the

cardinality for

ResponseReason_Type

as 1. But for some

unclear reason the

resulting XML schema

has cardinality 1..n

(probably because the

constraint is ignored).

For the time being I

update the schema

manually.

11-8-2014

End of Version 2014.A for approval with one issue remaining

http://www.ebix.org/






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 Validated Data for Billing

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 Billing are specified in a separate document [9].

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

Measure for Billing.

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 exchange of validated data for billing as

business information in line with the ebIX® business requirements for the exchange of validated data

for billing [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

validated data for billing energy and grid cost.



1.5. Actors, parties and roles In the model actors are either presented as <<Business Partner>>, <<AuthorizedRole>> or as <<Harmonized Role>>. A business partner is an organization type, an organizational unit type or a person type that participates in a business process [2]. An authorized role is a concept which is more generic than a business partner and allows the reuse of collaborations by mapping an authorized role to a business partner within a given scenario[2]. A harmonized role represents a specific responsibility in the European Energy Market related to the exchange of information [10]. In ebIX® models the business partner is mapped to the authorized role through a harmonized role. In this document the following <<BusinessPartner>>’s are taken from the business requirements:

Energy Supplier

Grid Company

Validator

In the model the business partner is to be mapped to a <<Harmonized Role>> from the Role Model. In

this document the following <<HarmonizedRole>>’s are used:

Balance Supplier

Grid Access Provider

Metered Data Responsible

In this document the following <<AuthorizedRole>>’s are used:

Supplier

Grid Company

Validator

1.6. Mapping to technology of choice Information on the available mappings to technology of choice (XML, Edifact, web service) is to be

found in the document “ebIX® Introduction to Business Requirements and Information Models” [8].



2. Business Choreography View: Measure for Billing

2.1. Exchange Validated Data for Billing Energy (Business Realization)

Figure 1 Realization: Exchange Validated Data for Billing Energy



2.2. Exchange Validated Data for Billing Energy (Business Collaboration)

Figure 2 Collaboration: Exchange Validated Data for Billing Energy

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

2.2.2. Exchange Validated Data for Billing Energy

Figure 3 Collaboration: Exchange Validated Data for Billing Energy



2.3. Exchange Validated Data for Billing Energy (Business Transaction)

Figure 4 Transaction: Exchange Validated Data for Billing Energy

2.3.1. Description

UseCase description: Exchange Validated Data for Billing Energy

definition Validator sends validated data to Supplier

beginsWhen Validator decides to.

preCondition Checked Collected Data are available for Validator and

Validation process has been completed.

endsWhen The reception of the validated data has been acknowledged by the Supplier.

postCondition Validated Data are available for the Supplier.

exceptions none

actions See 2.3.2



2.3.2. Exchange Validated Data for Billing Energy

Figure 5 Transaction: Exchange Validated Data for Billing Energy



2.4. Exchange Validated Data for Billing Grid Cost (Business Realization)

Figure 6 Realization: Exchange Validated Data for Billing Grid Cost

2.5. Exchange Validated Data for Billing Grid Cost (Business Collaboration)

Figure 7 Collaboration: Exchange Validated Data for Billing Grid Cost




2.5.2. Exchange Validated Data for Billing Grid Cost

Figure 8 Collaboration: Exchange Validated Data for Billing Grid Cost



2.6. Exchange Validated Data for Billing Grid Cost (Business Transaction)

Figure 9 Transaction: Exchange Validated Data for Billing Grid Cost

2.6.1. Description

UseCase description: Exchange Validated Data for Billing Grid Cost

definition Validator sends validated data to Grid Company




endsWhen The reception of the validated data has been acknowledged by the Grid

Company.

postCondition Validated Data are available for the Grid Company

exceptions none

actions See 2.6.2



2.6.2. Exchange Validated Data for Billing Grid Cost, Supplier Centric

Figure 10 Transaction: Exchange Validated Data for Billing Grid Cost, Supplier Centric



2.7. Exchange Validated Data for Billing Grid Cost, Supplier Centric

(Business Realization)

Figure 11 Realization: Exchange Validated Data for Billing Grid Cost, Supplier Centric


(Business Collaboration)

Figure 12 Collaboration: Exchange Validated Data for Billing Grid Cost, Supplier Centric





Figure 13 Collaboration: Exchange Validated Data for Billing Grid Cost, Supplier Centric




(Business Transaction)


2.9.1. Description UseCase description: Exchange Validated Data for Billing Grid Cost, Supplier Centric

definition Validator sends validated data to Supplier





postCondition Validated Data are available for the Supplier

exceptions none

actions See 2.9.22.3.2





2.10. Exchange Validated Data for Billing Grid Cost (Business Transaction) See 2.6 Exchange Validated Data for Billing Grid Cost (Business Transaction)



2.11. Request Validated Data for Billing Energy (Business Realization)

Figure 16 Realization: Request Validated Data for Billing Energy

2.12. Request Validated Data for Billing Energy (Business Collaboration)

Figure 17 Collaboration: Request Validated Data for Billing Energy




2.12.2. Request Validated Data for Billing Energy

Figure 18 Collaboration: Request Validated Data for Billing Energy

2.13. Request Validated Data for Billing Energy (Business Transaction)

Figure 19 Transaction: Request Validated Data for Billing Energy

2.13.1. Description UseCase description: Request Validated Data for Billing Energy

definition Supplier receives Validated Data from the Validator on request.

beginsWhen Supplier decides to.

preCondition Relation between Validator and Supplier.



exceptions No Validated Data available at the Validator.

actions See 2.13.2



2.13.2. Request Validated Data for Billing Energy

Figure 20 Transaction: Request Validated Data for Billing Energy



2.14. Request Validated Data for Billing Grid Cost by Supplier (Business

Realization)

Figure 21 Realization: Request Validated Data for Billing Grid Cost by Supplier


Collaboration)

Figure 22 Collaboration: Request Validated Data for Billing Grid Cost by Supplier




2.15.2. Request Validated Data for Billing Grid Cost by Supplier

Figure 23 Collaboration: Request Validated Data for Billing Grid Cost by Supplier


Transaction)

Figure 24 Transaction: Request Validated Data for Billing Grid Cost by Supplier

2.16.1. Description UseCase description: Request Validated Data for Billing Grid Cost by Supplier

definition Supplier receives Validated Data from the Validator on request.

beginsWhen Supplier decides to.

preCondition Relation between Validator and Supplier.




actions See 2.16.2



2.16.2. Request Validated Data for Billing Grid Cost by Supplier

Figure 25 Transaction: Request Validated Data for Billing Grid Cost by Supplier



2.17. Request Validated Data for Billing Grid Cost by Grid Company

(Business Realization)

Figure 26 Realization: Request Validated Data for Billing Grid Cost by Grid Company


(Business Collaboration)

Figure 27 Collaboration: Request Validated Data for Billing Grid Cost by Grid Company




2.18.2. Request Validated Data for Billing Grid Cost by Grid Company

Figure 28 Collaboration: Request Validated Data for Billing Grid Cost by Grid Company


(Business Transaction)

Figure 29 Transaction: Request Validated Data for Billing Grid Cost by Grid Company

2.19.1. Description UseCase description: Request Validated Data for Billing Grid Cost by Grid Company

definition Grid Company receives Validated Data from the Validator on request.

beginsWhen Grid Company decides to.

preCondition Relation between Validator and Grid Company.

endsWhen The reception of the validated data has been acknowledged by the Grid

Company.

postCondition Validated Data are available for the Grid Company.


actions See 2.19.2



2.19.2. Request Validated Data for Billing Grid Cost by Grid Company

Figure 30 Transaction: Request Validated Data for Billing Grid Cost by Grid Company



3. Modeled Business Information: Measure for Billing (Business

Information View)

See next page



3.1. Validated Data for Billing Energy (Business Information)

Figure 31 Validated Data for Billing Energy



3.1.1. OCL constraints for ValidatedDataForBillingEnergy <<MA>>

# Specification Constrained Element Applied Stereotype

1 -- Structure Energy_TimeSeries

-- Validated Data for Billing Energy

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ValidatedDataForBillingEnergy invariant [Constraint]

abie [Constraint]

document [Constraint]

payload [Constraint]

bdt [Constraint]




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

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

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

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

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

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

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

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

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

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

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

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1 xor Quantity_Missing->size()=1)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1 implies Quantity_Missing->size()=0)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Missing->size()=1 implies Energy_Quantity->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Generated_Quantity->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Missing->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Price->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Price_Missing->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Quality->size()=0)

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

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type->size()<=1)

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

/*

because in Nordic countries a customer meter read may be linked only to a Metering Point (and not to a meter/register)

this set of statements can be used for national customization replacing the statement above

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

inv: self.Payload.MeteringPoint_Read->notEmpty() implies self.Payload.Metering_Installation->size()=0

inv: self.Payload.Metering_Installation->size()=1 implies self.Payload.MeteringPoint_Read->isEmpty()

*/

2 -- BDT Energy_TimeSeries


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

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

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


bdt [Constraint]





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

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

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

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.Product_Included.Identification.content=EnergyProductIdentifier::8716867000030 or

self.Payload.Product_Included.Identification.content=EnergyProductIdentifier::5410000100016

inv: self.Payload.Product_Included.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9


inv: self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::KWH or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::NM3 or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::SM3

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

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

inv: self.Payload.Product_Included.Unit_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

inv: self.Payload.MP_Detail.MeteringPoint_Type.content=MeteringPointTypeCode::E17 or

self.Payload.MP_Detail.MeteringPoint_Type.content=MeteringPointTypeCode::E18

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

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

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

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)

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

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_DateTime.timeZoneCode->size()=0)



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

(MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27 or

MeterReadingOrigin_Type.content=MeterReadingOriginCode::E28)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (MeterReadingOrigin_Type.listIdentifier->size()=0)


(MeterReadingOrigin_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260)





inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity.unitCode->size()=0)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or

MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27 or MeterReadingOrigin_Type.content=MeterReadingOriginCode::E28)

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

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll


inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type.content=MeterTimeFrameCode::E10 or

MeterTimeFrame_Type.content=MeterTimeFrameCode::E11)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type.listIdentifier->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll

(MeterTimeFrame_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260)

3 -- Structure Energy_Document


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

ValidatedDataForBillingEnergy abie [Constraint]


invariant [Constraint]

4 -- BDT Energy_Document


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

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

ValidatedDataForBillingEnergy bdt [Constraint]






5 -- Structure Energy_Context


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

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

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




6 -- BDT Energy_Context


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

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=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


self.Header->size()=1

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



8 -- Structure Payload




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





3.1.2. Mapping BRS-BIM for Validated Data for Billing Energy



3.2. Validated Data for Billing Grid Cost (Business Information)

Figure 32 Validated Data for Billing Grid Cost



3.2.1. OCL constraints for ValidatedDataForBillingGridCost <<MA>>


1 -- Structure Energy_TimeSeries

-- Validated Data for Billing Grid Cost



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


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

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

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.MP_Detail->size()=1










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

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



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

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

ValidatedDataForBillingGridCost invariant [Constraint]

abie [Constraint]



bdt [Constraint]




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

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

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

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

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

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



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

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

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

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

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1 xor Quantity_Missing->size()=1)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1 implies Quantity_Missing->size()=0)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Missing->size()=1 implies Energy_Quantity->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity->size()=1)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Generated_Quantity->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Missing->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Price->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Price_Missing->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Quantity_Quality->size()=0)

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

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type->size()<=1)

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

/*

because in Nordic countries a customer meter read may be linked only to a Metering Point (and not to a meter/register)

this set of statements can be used for national customization replacing the statement above

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

inv: self.Payload.MeteringPoint_Read->notEmpty() implies self.Payload.Metering_Installation->size()=0

inv: self.Payload.Metering_Installation->size()=1 implies self.Payload.MeteringPoint_Read->isEmpty()

*/

2 -- BDT Energy_TimeSeries


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


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


bdt [Constraint]








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


self.Payload.Product_Included.Identification.content=EnergyProductIdentifier::8716867000030 or







inv: self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::KWH or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::KWT or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::K3 or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::NM3 or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::SM3 or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::Q39 or

self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::Q40

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

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

inv: self.Payload.Product_Included.Unit_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260


self.Payload.MP_Detail.MeteringPoint_Type.content=MeteringPointTypeCode::E18 or






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


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

inv: self.Payload.InArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.InArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

inv: self.Payload.OutArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or





self.Payload.OutArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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)

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

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (Read_DateTime.timeZoneCode->size()=0)




(MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27 or

MeterReadingOrigin_Type.content=MeterReadingOriginCode::E28)

inv: self.Payload.Metering_Installation.Register_Installation.Meter_Read->forAll (MeterReadingOrigin_Type.listIdentifier->size()=0)



inv: self.Payload.Observation_Interval.Observation_Detail->forAll (Energy_Quantity.unitCode->size()=0)

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterReadingOrigin_Type.content=MeterReadingOriginCode::E26 or

MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27 or MeterReadingOrigin_Type.content=MeterReadingOriginCode::E28)

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

--inv: self.Payload.Observation_Interval.Observation_Detail->forAll


inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type.content=MeterTimeFrameCode::E10 or

MeterTimeFrame_Type.content=MeterTimeFrameCode::E11)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll (MeterTimeFrame_Type.listIdentifier->size()=0)

inv: self.Payload.Observation_Interval.Observation_Detail->forAll

(MeterTimeFrame_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260)










ValidatedDataForBillingGridCost abie [Constraint]


















ValidatedDataForBillingGridCost bdt [Constraint]
















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

self.Process.Energy_BusinessProcessRole.content=BusinessRoleCode::DDM



























3.2.2. Mapping BRS-BIM for Validated Data for Billing Grid Cost



3.3. Request Validated Data for Billing Energy (Business Information)

Figure 33 Request Validated Data for Billing Energy



3.3.1. OCL constraints for RequestValidatedDataForBillingEnergy <<MA>>


1 -- Structure MeasuredData_Request

-- Request Validated Data for Billing Energy




inv: self.Payload.BusinessProcess_Reference->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.MP_Detail->size()<=1














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

RequestValidatedDataForBillingEnergy invariant [Constraint]

abie [Constraint]






2 -- BDT MeasuredData_Request


--self.Payload.Function.content=DocumentFunctionCode::9

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

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


MeterReadingOrigin_Type.content=MeterReadingOriginCode::E27



--inv: self.Payload.Request_Period.Resolution_Duration.content="PT15M"

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

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

--inv: self.Payload.Request_Period.Continuous.content="true"

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

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

--inv: self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

--inv: self.Payload.BalanceResponsible_Involved.Role.content=BusinessRoleCode::DDK

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

--inv: self.Payload.BalanceResponsible_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.BalanceResponsible_Involved.Name.languageCode="EN"

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

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

--inv:

self.Payload.TransportCapacityResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


--inv: self.Payload.TransportCapacityResponsible_Involved.Role.content=BusinessRoleCode::TCR

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

--inv: self.Payload.TransportCapacityResponsible_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.TransportCapacityResponsible_Involved.Name.languageCode="EN"

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

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


bdt [Constraint]






--inv: self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

--inv: self.Payload.BalanceSupplier_Involved.Role.content=BusinessRoleCode::DDQ

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

--inv: self.Payload.BalanceSupplier_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.BalanceSupplier_Involved.Name.languageCode="EN"




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

--inv: self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::KWH

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

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

--inv: self.Payload.Product_Included.Unit_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260






--inv: self.Payload.MP_Detail.MeteringMethod_Type.content=MeteringMethodCode::E13

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

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

--inv: self.Payload.MP_Detail.VoltageLevel_Type.content=VoltageLevelCode::E04

--inv: 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.StandardLoadProfile_Type.content=StandardLoadProfileCode::1A

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

--inv: self.Payload.MP_Detail.StandardLoadProfile_Type.listIdentifier=CodeListIdentificationCode::DPO

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




--inv: self.Payload.MP_Detail.StandardLoadProfile_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.MP_Detail.MeterReadingFrequency_Duration.content="P1M"


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

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

--inv: self.Payload.MeteringGridArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.MeteringGridArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

--inv: self.Payload.InArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


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

--inv: self.Payload.OutArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


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

--inv: self.Payload.BalanceGroup_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.BalanceGroup_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

--inv: self.Payload.MarketBalanceArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


--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 (Meter_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)

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

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

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

(Register_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)





RequestValidatedDataForBillingEnergy abie [Constraint]























RequestValidatedDataForBillingEnergy bdt [Constraint]










abie [Constraint]






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



RequestValidatedDataForBillingEnergy bdt [Constraint]













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













3.3.2. Mapping BRS-BIM for Request Validated Data for Billing Energy



3.4. Request Validated Data for Billing Grid Cost (Business Information)

Figure 34 Request Validated Data for Billing Grid Cost



3.4.1. OCL constraints for RequestValidatedDataForBillingGridCost <<MA>>


1 -- Structure MeasuredData_Request

-- Request Validated Data for Billing Grid Cost





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.MP_Detail->size()<=1














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

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

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

RequestValidatedDataForBillingGridCost invariant [Constraint]

abie [Constraint]






2 -- BDT MeasuredData_Request


--self.Payload.Function.content=DocumentFunctionCode::9

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

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





--inv: self.Payload.Request_Period.Resolution_Duration.content="PT15M"

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

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

--inv: self.Payload.Request_Period.Continuous.content="true"

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

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

--inv: self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


--inv: self.Payload.BalanceResponsible_Involved.Role.content=BusinessRoleCode::DDK

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

--inv: self.Payload.BalanceResponsible_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.BalanceResponsible_Involved.Name.languageCode="EN"

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

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

--inv:

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

or self.Payload.BalanceResponsible_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

--inv: self.Payload.TransportCapacityResponsible_Involved.Role.content=BusinessRoleCode::TCR

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

--inv: self.Payload.TransportCapacityResponsible_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.TransportCapacityResponsible_Involved.Name.languageCode="EN"

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

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


bdt [Constraint]






--inv: self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.BalanceSupplier_Involved.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

--inv: self.Payload.BalanceSupplier_Involved.Role.content=BusinessRoleCode::DDQ

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

--inv: self.Payload.BalanceSupplier_Involved.Role.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.BalanceSupplier_Involved.Name.languageCode="EN"








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

--inv: self.Payload.Product_Included.Unit_Type.content=MeasurementCommonCode::KWH

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

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

--inv: self.Payload.Product_Included.Unit_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260






--inv: self.Payload.MP_Detail.MeteringMethod_Type.content=MeteringMethodCode::E13

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

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

--inv: self.Payload.MP_Detail.VoltageLevel_Type.content=VoltageLevelCode::E04

--inv: 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.StandardLoadProfile_Type.content=StandardLoadProfileCode::1A

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

--inv: self.Payload.MP_Detail.StandardLoadProfile_Type.listIdentifier=CodeListIdentificationCode::DPO

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

--inv: self.Payload.MP_Detail.StandardLoadProfile_Type.listAgencyIdentifier=CodeListResponsibleAgencyCode::260

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

--inv: self.Payload.MP_Detail.MeterReadingFrequency_Duration.content="P1M"


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

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

--inv: self.Payload.MeteringGridArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.MeteringGridArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

--inv: self.Payload.InArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


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

--inv: self.Payload.OutArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or


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

--inv: self.Payload.BalanceGroup_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.BalanceGroup_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

--inv: self.Payload.MarketBalanceArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9 or

self.Payload.MarketBalanceArea_Used.Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::305

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

(Meter_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)

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

--inv: self.Payload.Metering_Installation.Register_Installation->forAll (Register_Identification.schemeAgencyIdentifier-

>size()=1)

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

(Register_Identification.schemeAgencyIdentifier=CodeListResponsibleAgencyCode::9)













RequestValidatedDataForBillingGridCost abie [Constraint]















RequestValidatedDataForBillingGridCost bdt [Constraint]










abie [Constraint]


-- Request Validated Data for Billing Grid Cost RequestValidatedDataForBillingGridCost bdt [Constraint]

































3.4.2. Mapping BRS-BIM for Request Validated Data for Billing Grid Cost



3.5. Negative Response Request Validated Data for Billing (Business Information)

Figure 35 Negative Response Request Validated Data for Billing



3.5.1. OCL constraints for NegativeResponseRequestValidatedDataForBilling <<MA>>


1 -- Structure Response_Event

-- NegativeResponseRequestValidatedDataForBilling


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

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

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

NegativeResponseRequestValidatedDataForBilling 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.content=ResponseReasonDescriptionCode::E10 or



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

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

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

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

--inv:


bdt [Constraint]








-- NegativeRequestRequestValidatedDataForBilling








NegativeResponseRequestValidatedDataForBilling abie [Constraint]





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










NegativeResponseRequestValidatedDataForBilling bdt [Constraint]
















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















-- NegativeResponseValidatedDataForBilling



NegativeResponseRequestValidatedDataForBilling document [Constraint]











3.5.2. Mapping BRS-BIM for Negative Response Request Validated Data for

Billing



3.6. Response Request Validated Data for Billing Energy (Business Information)

Figure 36 Response Request Validated Data for Billing Energy

3.6.1. OCL constraints for Response Request Validated Data For Billing Energy <<InfEnvelope>>


1 -- Dependency Response Request Validated Data for Billing Energy

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

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

Response Request Validated Data for Billing Energy dependency [Constraint]


Remark:

The mapping from BRS to BIM is included in the specification of the associated <<MA>>’s (see 3.1.2 and 3.5.2)



3.7. Response Request Validated Data for Billing Grid Cost (Business Information)

Figure 37 Response Request Validated Data for Billing Grid Cost

3.7.1. OCL constraints for Response Request Validated Data For Billing Grid Cost <<InfEnvelope>>


1 -- Dependency Response Request Validated Data For Billing Grid Cost

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

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

Response Request Validated Data for Billing Grid Cost dependency [Constraint]


Remark:

The mapping from BRS to BIM is included in the specification of the associated <<MA>>’s (see 3.2.2 and 3.5.2)

Date post:	10-Jun-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Measure...ebIX® Business Information Model for Measure for Billing page 6 ebIX® September, 2015...

Documents