Business information models for
Measure
Introduction
Collect
Validate
Aggregate
Status:
draft
Version:
2.0
Revision: draft 01
Date:
September, 2009
ebIX Business information model for the exchange of metered data in the energy market
2
CONTENT
0.
1.
2.
About this document....................................................................................................................... 6
0.1.
Participants in the project ....................................................................................................... 6
0.2.
Comments to the ebIX© model ............................................................................................... 7
0.3.
References ............................................................................................................................... 8
0.4.
Main changes since last version .............................................................................................. 8
Introduction..................................................................................................................................... 9
1.1.
The energy market .................................................................................................................. 9
1.2.
About the ebIX© Model ........................................................................................................... 9
1.3.
National requirements ............................................................................................................ 9
1.4.
Business Domain Model ........................................................................................................ 10
1.5.
Objectives .............................................................................................................................. 10
1.6.
Limitations / prerequisites .................................................................................................... 11
1.7.
Scope ..................................................................................................................................... 11
1.8.
Actors, parties and roles........................................................................................................ 12
1.9.
Boundaries of the business domain Measure ....................................................................... 12
1.10.
Remark for all Class Diagrams ........................................................................................... 13
1.11.
Comments to the attributes in Class Diagrams: ................................................................ 13
1.12.
RSM annexes for mapping to technology of choice .......................................................... 13
1.12.1.
Core Components .............................................................................................................. 13
1.12.2.
Mapping to Edifact UNSM ................................................................................................. 13
1.12.3.
Mapping to XML ................................................................................................................ 14
1.12.4.
Web services...................................................................................................................... 14
1.13.
Harmonized Role Model section Metered Data................................................................ 15
Business Requirements View: Collect ........................................................................................... 16
2.1.
2.1.1.
ebIX©
Collect (Business Process UseCase) ....................................................................................... 16
Description ........................................................................................................................ 16
October 2009
ebIX Business information model for the exchange of metered data in the energy market
2.1.2.
Business Process ................................................................................................................ 16
2.1.3.
Data Collection (Business Process UseCase) ..................................................................... 17
2.1.3.1.
Description .................................................................................................................... 17
2.1.3.2.
Business Process ............................................................................................................ 17
2.1.3.3.
Read Register (Business Process UseCase).................................................................... 18
2.1.3.3.1.
Description .................................................................................................................... 18
2.1.3.3.2.
Business Process ............................................................................................................ 19
2.1.3.4.
Check Quality (Business Process UseCase).................................................................... 19
2.1.3.4.1.
Description .................................................................................................................... 19
2.1.3.4.2.
Business Process ............................................................................................................ 20
2.1.4.
Exchange Collected Data (Business Process UseCase) ...................................................... 21
2.1.4.1.
Description .................................................................................................................... 21
2.1.4.2.
Business Process ............................................................................................................ 22
2.1.5.
Request Collected Data (Business Process UseCase) ........................................................ 22
2.1.5.1.
Description .................................................................................................................... 22
2.1.5.2.
Business Process ............................................................................................................ 23
2.2.
Business Partner View ........................................................................................................... 24
2.2.1.
2.3.
Business Partners Collect .................................................................................................. 24
Business Entity View .............................................................................................................. 25
2.3.1.
Collected Data (Class Diagram) ......................................................................................... 25
2.3.1.1.
2.3.2.
3.
3
Collected Data (State Diagram) ..................................................................................... 26
Request Collected Data (Class Diagram) ........................................................................... 27
Business Choreography View: Collect ........................................................................................... 28
3.1.
Introduction........................................................................................................................... 28
3.2.
UseCase Exchange Collected Data (Business Realization) .................................................... 28
3.2.1.
3.2.1.1.
ebIX©
UseCase Exchange Collected Data (Business Collaboration) ............................................ 29
Description .................................................................................................................... 29
October 2009
ebIX Business information model for the exchange of metered data in the energy market
3.2.1.2.
Exchange Collected Data ............................................................................................... 29
3.2.1.3.
UseCase Exchange Collected Data (Business Transaction) ........................................... 29
3.2.1.3.1.
Description .................................................................................................................... 29
3.2.1.3.2.
Exchange Collected Data ............................................................................................... 30
3.3.
UseCase Request Collected Data (Business Realization)....................................................... 31
3.3.1.
4.
4
UseCase Request Collected Data (Business Collaboration)............................................... 31
3.3.1.1.
Description .................................................................................................................... 31
3.3.1.2.
Request Collected Data ................................................................................................. 32
3.3.1.3.
UseCase Request Collected Data (Business Transaction) ............................................. 32
3.3.1.3.1.
Description .................................................................................................................... 32
3.3.1.3.2.
Request Collected Data ................................................................................................. 33
Modeled Business Information: Collect (Business Information View) .......................................... 34
4.1.
Introduction........................................................................................................................... 34
4.2.
Brief explanation for the information model ........................................................................ 34
4.2.1.
Technology (syntax) independent information model...................................................... 34
4.2.2.
Mapping to Edifact ............................................................................................................ 34
4.2.3.
Core Components .............................................................................................................. 35
4.2.4.
Message Assembly ............................................................................................................ 35
4.2.5.
Linking attributes from Requirements View to attributes in Information View ............... 35
4.3.
Information model for Business Documents......................................................................... 36
4.3.1.
Collected Data (Business Information) .............................................................................. 37
4.3.1.1.
OCL constraints for CollectedData ................................................................................ 38
4.3.1.2.
OCL constraints for CollectedData <<InfEnvelope>> .................................................... 38
4.3.1.3.
OCL constraints for CollectedData <<MBIE>> 1 ............................................................ 39
4.3.1.4.
OCL constraints for CollectedData <<MBIE>> 2 ............................................................ 39
4.3.2.
4.3.2.1.
ebIX©
Request Collected Data (Business Information) ................................................................ 42
OCL constraints for RequestCollectedData ................................................................... 43
October 2009
ebIX Business information model for the exchange of metered data in the energy market
5
4.3.2.2.
OCL constraints for RequestCollectedData <<InfEnvelope>> ....................................... 43
4.3.2.3.
OCL constraints for RequestCollectedData 1 <<MBIE>> ............................................... 44
4.3.2.4.
OCL constraints for RequestCollectedData 2 <<MBIE>> ............................................... 44
Appendix A Remarks regarding Class Diagrams for Measure .............................................................. 46
A.
Direction .................................................................................................................................... 46
B.
Update procedures.................................................................................................................... 46
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
6
0. About this document
This document is a generic introduction to all ebIX© models for the exchange of metered data. The
document contains a general introduction to all models for metered data plus the generic model
elements that are not specific for a business process for the UseCases Collect, Validate and
Aggregate. The UseCase Collect will be completely described in this model, since the collection of
metered data is not specific for a business process.
The processes are described 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.
0.1.
Participants in the project
This part of the ebIX© Model for the European Energy Market is made in a project with the following
participants:
Members
Name
Company
Telephone
Mobile
E-mail
Rudolf Baumann1
Swiss Grid
+41585802120
+41763844444
rudolf.baumann@swissgrid.ch
Vlatka Cordes
RWE
+49 234 515-1638
+49 162 2519714
vlatka.cordes@rwe.com
Hugo Dekeyser2
UMIX
+32477558003
hugo.dekeyser@umix.info
Filip Drijkoningen3
UMIX
+3211266495
filip.drijkoningen@infrax.be
Adrian Fuchs4
Swissgrid
+41585802328
adrian.fuchs@swissgrid.ch
Joost de Geus5
TenneT
+31263732605
j.d.geus@tennet.org
Preben Høj Larsen
Energinet.dk
+45 76224247
phq@energinet.dk
Helmut Lebeau6
VDN
+4930726148110
+4915115741580
helmut.lebeau@vdn-berlin.de
Oscar Ludwigs
SvK
+4687397784
+46705397784
oscar.ludwigs@svk.se
1
Till November 2005
2
Till January 2007
3
From October 2006
4
From November 2005
5
From April 2009
6
Till January 2006
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
Lars Munter
SvK
+4687397850
Walter Müller7
TenneT
+31263731277
Christian Odgaard
Energinet.dk
+45 76 224463
Lucy Sarkisian8
EBO
+31263731631
Kees Sparreboom
ebIX©
+46705397850
7
lars.munter@svk.se
w.muller@tennet.org
+45 23 338555
cco@energinet.dk
l.sarkisian@tennet.org
+31 6 22667911
kees.sparreboom@capgemini.com
+4369912572511
peter.bauhofer@aundb.at
+4795783599
frode@elis.no
Observers
Peter Bauhofer
A&B
Frode Gjerde9
Elis
Juraj Horvat
VSE
+421(0) 55 610 29
51
+421 (0) 915 932
285
horvat_juraj@vse.sk
Jörg Flügge
SAP
+4962277-64558
+4916090823048
j.fluegge@sap.com
John Buckley
BGE
Ardo Ott
Eesti Energia
+372 511 7637
ardo.ott@energia.ee
Mare Tammisto
Eesti Energia
+372 511 8252
mare.tammisto@energia.ee
Anne-Gaelle LeSaout
EDF
0.2.
+435125708830
jbuckley@bge.ie
anne-gaelle.lesaout@distribution.edf.fr
Comments to the ebIX© model
If you have comments or suggestions to the model please contact any member of the project group
or directly to Kees Sparreboom, kees.sparreboom@capgemini.com .
7
Till January 2008
8
From January 2008 till April 2009
9
In 2005
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
0.3.
8
References10

UN/CEFACT Unified Modelling Methodology -TMWG/N090, see
http://webster.disa.org/cefact-groups/tmg/doc_bpwg.html

ebIX© model for Structuring of the European Energy Market (incl. Customer Switching), version
1.0.- see www.ebix.org

The Electricity Market Role Model – ETSO, ebIX and EFET, see www.edi.etso-net.org
0.4.
Main changes since last version
Old
New
Clarification
Date
Version 2.0.draft01
UML File name:/ D:/ksparreb/Documents/ebIX/Model for European Energy Market/European Energy
Market/EEM-Measure.mdzip
1.
2.
3.
4.
5.
10
Correctness of the links has to be checked.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
9
1. Introduction
1.1.
The energy market
Presently the energy market is going through a change process in most of the European countries.
These changes include new legislation and a deregulation of the market. Earlier the participants in
the market were in a monopoly situation. Today the participant companies are being split into
different companies with different roles (responsibilities), such as Metering Point Administrator,
Balance Supplier, Balance Responsible, etc. Furthermore national markets turn more and more into a
common European market.
The change in the structure of the market and the new legislation described above has increased the
need for electronic business tremendously (e.g. today the exchange of EDI documents in the energy
market in Sweden is about 40 million EDI documents a year). This includes both transaction data,
such as time series with production and consumption figures between the different parties, and
master data. The exchange of information regards a large number of participants in many to many
relationships. The number of actors which needs information exchange in the energy market may be
in the range of a few hundred companies per country (Germany has for instance about 900 Grid
operators).
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, after the modeling project has finished, 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 metered data 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
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.
National requirements
The requirements for the ebIX© model are based on mainly national procedural requirements. The
metered data needed for imbalance settlement as specified by ENTSO-E is also taken into account as
requirement.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
1.4.
10
Business Domain Model11
The exchange of metered data is a part of the overall processes in the energy market. To give a brief
introduction to where in the overall model the exchange processes belong, the introduction and the
business domain UseCase for the energy market is shown below. Please notice that these processes
are being discussed in several projects in the European power industry and might be changed in the
future.
In the various model documents the domain Measure from this Business Domain Model is broken
down into individual processes.
Structure
Plan
Structure
Trade
Plan
Operate
Trade
<<include>>
Operate
<<include>>
<<include>>
<<include>>
European Energy Market
<<include>>
<<include>>
Measure
Measure
Settle
Settle
<<include>>
Bill
Bill
1.5. Objectives
The vision of the project is to produce a model of the energy market. The work will be used to:

Provide a basis for facilitation and harmonization in planning, trade, settlement and other
processes important for the energy market.

Provide a basis for a common way of exchanging information in the energy market.

To make the models based on international accepted standards, so that the result can be
understood and used by as many as possible.

To make the deregulated energy market understandable for the participating parties.
11
Since the Business Domain Model is common for all European Energy Market models, this section may be
moved to a separate document in a next version of this document.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
11
1.6. Limitations / prerequisites
1. In the model documents for Measure the exchange of metered data for various purposes is
described.
2. A precondition for implementation of the “simple” solutions described in the ebIX© models is
that unique Metering Point ID’s are implemented12. If a unique Metering Point ID not is
implemented, other attributes must be added to the different documents exchanged on a
national basis (to assure the correct identification of the Metering Point).
3. Usage of the classes with a cardinality of “0..1” or “0..*” are dependent on national rules.
4. For the purposes of the EMD project meters have to be identified at least uniquely within one
Metering Point. Identification of physical meters can for this purpose be based on GS1 GSAI
(Global Serial Asset Identification for which identification scheme GS1 is the controlling agency).
1.7. Scope
The Measure part of the overall ebIX© model focuses on the exchange of metered data.
Within ebIX© the work group Customer Switching (CuS) is modeling the processes regarding the
exchange of master data within the energy sector.
The European Transmission System Operators model within their organization ENTSO-E various
processes where the TSO’s are directly involved. One of these processes being the imbalance
settlement for which ebIX© has modeled the exchange of metered data in cooperation with ENTSO-E.
The process of reconciliation is modeled by ebIX©.
Next to ENTSO-E also UCTE has described some processes in which information exchange between
TSO’s is required.
EFET has modeled some elements in the exchange between traders.
12
see ebIX© document: Recommended Identification Schemes for the European Energy Market (www.ebix.org)
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
12
1.8. Actors, parties and roles
In this document the term role originates from the ebIX©-EFET-ENTSO Harmonized Role Model. In
this model roles are mainly defined in terms of responsibility. The term party refers to the (legal)
entity performing the role. A party may combine more than one role. The term actor is reserved for
UML and will be avoided in the ebIX© methodology.
Some examples:
The traditional grid company (as a party) may perform the following roles:

Grid Access Provider

Metering Point Administrator

Metered Data Collector

Metered Data Responsible

Metered Data Aggregator local

Metering Administrator
The energy supplier as (a party) may perform the following roles:

Balance Supplier

Balance Responsible
o
Trade
o
Consumption
o
Production
For definitions of the different actors and roles, please see the ebIX©-EFET-ETSO Harmonized Role
Model, www.edi.etso-net.org or www.ebix.org
1.9. Boundaries of the business domain Measure
The domain Measure of the ebIX© model intends to cover all exchange of metered data in the energy
sector. In this document all modeling results with respect to the exchange of metered data are to be
found. Other modeling results as published by ebIX© are:

The maintenance and exchange of master data required in all processes (this part is modeled by
ebIX© CuS).

The reconciliation process and the exchange of the results of that process (as modeled by ebIX©
EMD).
The descriptions given in this document will be limited to the requirements for the exchange of
metered data only.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
13
1.10. Remark for all Class Diagrams
The Class Diagram follows the UN/Cefact Naming and Design Rules with respect to the relations and
the use of cardinality. The naming of elements has still to be checked. Mapping to Edifact follows the
ebIX Rules for Mapping.
Where possible the product-ID is specified explicitly because:

The ebIX rule is to specify products explicitly even if there is in an instance only one product
used;

ebIX intends to use generic re-usable elements (Core Components).
1.11. Comments to the attributes in Class Diagrams:

QuantityQuality: “estimated” is regarded as a higher quality (more precise) than “temporary”
1.12. RSM annexes for mapping to technology of choice
To all ebIX© EMD documents an annex is attached containing the information required to map the
Business Requirements for the information to be exchanged (as specified in the Class Diagrams) to
the desired technology. Originally ebIX© model documents provided only information for mapping to
an Edifact UNSM (like UTILTS). Present documents also provide the mapping to XML.
1.12.1.
Core Components
The mapping of the Business Requirements for the information to be exchanged to the required
technology as provided in the Requirements Specification Mapping (RSM) starts with the translation
of the data into re-usable Core Components in the Business Information View.
The Core components used in the present version of the EMD model documents are of provisional
nature, since the European energy sector is in the process of defining harmonised Core Components.
At the moment the ABIE’s and QDT’s used in the BIV are based on available UN/Cefact CC’s and CDT’s
or on ebIX© proposals for new CC’s or CDT’s. All ABIE’s and QDT’s will be harmonized within the
European energy market.
Notice: ebIX© together with ENTSO-E (and UN/Cefact) are still in the middle of the development
process for the use of Core Components for the specification of the information that is to
be exchanged. So the progress of this development will undoubtedly affect the Class
Diagrams as presented in the Business Information View (BIV) in this document.
1.12.2.
Mapping to Edifact UNSM
For the mapping to Edifact the UNSM’s for UTILTS and UTILMD from the UN/Cefact directory version
08.A are used.
Rules for mapping to Edifact are to be found in the ebIX document “ebIX Rules for mapping to
Edifact, version 0.1.-, d.d. July 2005”.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
1.12.3.
14
Mapping to XML
The mapping to XML is done by generating XML schema’s directly from the UML-model. The creation
of the XML schema’s follows the recommendations as published by UN/Cefact in the Naming and
Design Rules version 3.0.
ebIX EMD model documents contain the specification of the XML schema’s that are specific for the
information as described in that particular model document. Generic schema’s (code lists used, Core
Data Types (CDT), Business Data Types (BDT) and Reusable Aggregate Business Information (ABIE) are
published in separate documents.
As consequence one will find in this document only the XML specification for the information
exchanged in the processes regarding Collected Data plus for each document schema a schema that
specifies the Exchangeable Business Information used in that document schema and therefore
included in that document schema. Exchangeable Business Information specifies ABIE’s that are
customized for the use in one particular document.
1.12.4.
Web services
ebIX© wants the models to be prepared for implementation as web services. Therefore the clustering
of the information in the RSM is slightly modified compared to the BRS version.

The header information to be used in the batch exchange as individual documents or as
messages containing several documents is specifically split off from the definition of the Core
Business Data defined in the BIV.

For metered data ebIX© assumes that web services will be clustered per responsible role.
This implies that the attributes ReasonForTransaction, BusinessSector and Function are part
of the Core Business Data.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
15
1.13. Harmonized Role Model section Metered Data
Several roles are involved in the exchange of metered data process area. Below is shown a class diagram where the main relations for the roles involved are
shown.
package Harmonized Role Model [
Harmonized Role Model section Metered Data ]
<<Harmonized Role>>
<<Harmonized Role>>
<<Harmonized Role>>
Balance
Responsible
Producer
Consumer
<<Harmonized Role>>
Grid Access
Provider
must have
1..*
may be financially
responsible for
Controls
financially
<<Harmonized Role>>
Party Connected
to Grid
<<Harmonized Domain>>
<<Harmonized Domain>>
Balance Group
Functional Group
1..*
<<Harmonized Role>>
Provides access to
<<Harmonized Domain>>
1..*
Market Balance Area
Aggregates within
Operates
<<Harmonized Role>>
Imbalance Settlement
Responsible
Market Operator
nis composed of
Operates
Uses
1
Is composed of
1..*
<<Harmonized Role>>
Is financially accountable for
1..*
Reconciliation
Accountable
1..* 1..*
1..* 1..*
<<Harmonized Domain>> 1
Exchange Metering Point
<<Harmonized Domain>>
Local metering point
Connects
2
<<Harmonized Domain>>
Metering Grid Area
1..*
Controls
financially
<<Harmonized Role>>
Reconciliation
Responsible
1..*
Aggregates within
Supplies to
<<Harmonized Domain>>
<<Harmonized Role>>
administrates
1..*
Metering Point
Administrator
<<Harmonized Role>>
Balance Supplier
Metering point
1
1..*
1..*
Metered Data
Aggregator central
Metered Data
Aggregator local
has
Processes metered data for
0..*
<<Harmonized Role>>
Metered Data
Collector
Collects data from
1..*
<<Harmonized Installation>>
Register
1..*
Administrates
meter information for
<<Harmonized Role>>
Metered Data
Responsible
1..*
Administrates
has
<<Harmonized Role>>
Metered Data
Aggregator
1
<<Harmonized Installation>>
<<Harmonized Role>>
Meter
Meter Administrator
1..*
Operates and maintains
<<Harmonized Role>>
Billing Agent
<<Harmonized Role>>
Meter Operator
Class diagram – Metered data, Role model for Exchange Metered Data
(Based on ebIX©-EFET-ETSO version5.0, April 2008)
For definitions of the different actors and roles, please see the ebIX©-EFET-ETSO Role model, www.edi.etso-net.org or www.ebix.org
ebIX©
October 2009
2. Business Requirements View: Collect
2.1. Collect (Business Process UseCase)
use case
Collect [
Collect ]
<<participates>>
<<BusinessProcessUseCase>>
<<bPartner>>
Collect
Collector
<<include>>
<<include>>
<<BusinessProcessUseCase>>
Exchange Collected Data
<<include>>
<<BusinessProcessUseCase>>
<<BusinessProcessUseCase>>
Data Collection
Request Collected Data
2.1.1. Description
UseCase description: Collect
definition
Providing collected data by a Collector to other partners in the energy
sector.
beginsWhen
The Collector decides to or is requested to.
preCondition
Collector should know which register to read and therefore have access to
relevant master data
endsWhen
The distribution of the Collected Data has been acknowledged.
postCondition
Collected data have been exchanged.
Exceptions
actions

No data available

Collected data delivered to the wrong addressee
See Activity Diagrams
2.1.2. Business Process
activ ity Collect [
Collect ]
<<BusinessProcess>>
: Data Collection
[own initiative]
: Exchange
Collected Data
Initial
Success
<<BusinessProcess>>
[asked by other]
: Request Collected
Data
ebIX Business information model for the exchange of metered data in the energy market
17
2.1.3. Data Collection (Business Process UseCase)
use case
Data Collection [
Data Collection ]
<<participates>>
<<BusinessProcessUseCase>>
Data Collection
<<bPartner>>
Collector
<<include>>
<<include>>
<<BusinessProcessUseCase>>
<<BusinessProcessUseCase>>
Read Register
2.1.3.1.
Check Quality
Description
UseCase description: Data Collection
definition
A Collector collects and processes data in order to make these available to
others.
beginsWhen
The Collector decides to.
preCondition
Collector has knowledge about the register to read and the relevant quality
standards.
endsWhen
The checked data have been stored into a system.
postCondition
The checked data are available for others.
exceptions
None
actions
See Activity Diagram
2.1.3.2.
Business Process
activ ity Data Collection [
Initial
ebIX©
Data Collection ]
<<BusinessProcess>>
<<BusinessProcess>>
: Read Register
: Check Quality
Success
October 2009
ebIX Business information model for the exchange of metered data in the energy market
2.1.3.3.
use case
18
Read Register (Business Process UseCase)
Read Register [
Read Register ]
<<BusinessProcessUseCase>>
Read Register
<<participates>>
<<bPartner>>
Collector
<<include>>
<<participates>>
<<BusinessProcessUseCase>>
Use Master Data Register
2.1.3.3.1.
Description
UseCase description: Read Register
definition
A Collector reads one or more registers located at a metering point. The
Collector is physically represented by a person or by a data collection
system.
beginsWhen
The Collector decides to.
preCondition
Collector should know which register to read and have access to relevant
master data
endsWhen
The data have been collected and stored into a system.
postCondition
The collected data are available for quality check.
exceptions
actions
ebIX©

No data available

No connection available from the data collection system

No entry to the location of the physical register
See Activity Diagram
October 2009
ebIX Business information model for the exchange of metered data in the energy market
2.1.3.3.2.
19
Business Process
activ ity Read Register [
Read Register ]
Initial
<<BusinessProcess>>
<<BusinessProcessAction>>
Find Location
: Use Master Data
Register
<<BusinessProcessAction>>
Read Register
<<bEInternalState>>
: Collected Data
[Read]
Success
2.1.3.4.
use case
Check Quality (Business Process UseCase)
Check Quality [
Check Quality ]
<<participates>>
<<bPartner>>
<<BusinessProcessUseCase>>
Check Quality
Collector
2.1.3.4.1.
Description
UseCase description: Check Quality
definition
Check on read data whether these are within the plausibility limits derived
from historic data.
beginsWhen
Data have been read and stored into a system
preCondition
Availability of historic data
endsWhen
Data have passed the check
postCondition
Data have been checked and are available for exchange.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market

exceptions
actions
2.1.3.4.2.
20
Data beyond limits
See Activity Diagram
Business Process
activ ity Check Quality [
Check Quality ]
Initial
<<BusinessProcessAction>>
Retriev e Collected Data
<<BusinessProcessAction>>
Retriev e Historic Data
<<BusinessProcessAction>>
Compare Collected and
Historic Data
<<BusinessProcessAction>>
[beyond limits]
Improv e Collected Data
[within limits]
<<BusinessProcessAction>>
Approv e Collected Data
<<bEInternalState>>
: Collected Data
[Checked]
Success
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
21
2.1.4. Exchange Collected Data (Business Process UseCase)
use case
Exchange Collected Data [
Exchange Collected Data ]
<<participates>>
<<bPartner>>
<<BusinessProcessUseCase>>
<<participates>>
Collector
2.1.4.1.
<<bPartner>>
Exchange Collected Data
Metering Responsible
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 Activity Diagram
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
2.1.4.2.
22
Business Process
activ ity Exchange Collected Data [
Exchange Collected Data ]
<<bPartner>>
<<bPartner>>
Metering Responsible
Collector
Initial
<<BusinessProcessAction>>
Prepare Collected Data
<<BusinessProcessAction>>
<<SharedBusinessEntityState>>
<<BusinessProcessAction>>
: Collected Data
Receiv e Collected Data
Send Collected Data
[Exchanged]
Success
2.1.5. Request Collected Data (Business Process UseCase)
use case
Request Collected Data [
Request Collected Data ]
<<participates>>
<<BusinessProcessUseCase>>
<<bPartner>>
<<participates>>
Request Collected Data
Metering Responsible
2.1.5.1.
<<bPartner>>
Collector
Description
UseCase description: Request Collected Data
definition
Metering Responsible requests Collected Data from the Collector
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.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
postCondition
Collected Data are available for the Metering Responsible.
exceptions
No Collected Data available at the Collectors.
actions
See Activity Diagram
2.1.5.2.
23
Business Process
activ ity Request Collected Data [
Request Collected Data ]
<<bPartner>>
<<bPartner>>
Collector
Metering Responsible
<<BusinessProcessAction>>
Send Request
<<SharedBusinessEntityState>>
: Collected Data
[Requested]
<<BusinessProcessAction>>
Receiv e Request
[Data available]
Receiv e
Collected Data
<<SharedBusinessEntityState>>
: Collected Data
[Exchanged]
[Data not available]
<<BusinessProcessAction>>
Send Collected Data
Failure
Success
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
24
2.2. Business Partner View
2.2.1. Business Partners Collect
package
BusinessPartner [
BusinessPartner Collect ]
<<documentation>>
<<bPartner>>
Collector
A partner that provides collected data
to other partners in the sector
<<documentation>>
<<bPartner>>
Metering
Responsible
ebIX©
A partner that validates collected data
and provides the resulting validated
data to other partners in the sector
October 2009
2.3. Business Entity View
2.3.1. Collected Data (Class Diagram)
package
Collected Data [
Collected Data ]
<<bEntity>>
<<Assembled>>
{codeListAgencyID = 260
+Identifier [1]
+Reason : BusinessReasonCode [1]
+Sector : SectorAreaIdentificationCode [1]
+Observation period [0..1]
+Registration Date/Time [1]
+Resolution [0..1]
1
<<bEntity>>
MeteringPoint
+Identifier
<<Subset>>
BusinessReasonCode
Collected Data
,
name = "BusinessReasonCode"
status = draft
BusinessReasonCode
{codeListAgencyID = 260
,
,
UNCL = "9013"
originalCodeListAgencyID = 260
status = draft
<<comment>>
Used if
cardinality
Observation > 1
=
=
=
=
=
=
=
=
=
=
=
}
"Move; change of party connected to the grid"}
"Change of balance supplier"}
"End of supply"}
"Change of data from party connected to the grid"}
"Periodic metering"}
"Removal of meter"}
"Consumer move-in"}
"Consumer move-out"}
"Placement of meter"}
"Change of metering method"}
"End of metering"}
...
1..*
{codeListAgencyID = 260
+Identifier [1]
+Position [1]
+Quantity [0..1]
+Quantity quality : QuantityQualityCode [0..1]
{codeListAgencyID = 260
,
name = "SectorAreaIdentificationCode"
<<comment>>
Observation
SectorAreaIdentificationCode
SectorAreaIdentificationCode
Register
1..*
<<Subset>>
<<Assembled>>
<<bEntity>>
If no quantity
available,
quantity quality =
46
status = draft
,
origin = SectorAreaIdentificationCode
,
UNCL = "7293"
,
name = "SectorAreaIdentificationCode"
,
,
originalCodeListAgencyID =
}
status = draft
6,
,
UNCL = "7293"
}
23{codeName = "Electricity supply industry"}
...
<<Assembled>>
<<Subset>>
QuantityQualityCode
{codeListAgencyID = 260
name = "QuantityQualityCode"
status = draft
UNCL = "4405"
,
QuantityQualityCode
,
{codeListAgencyID = 260
,
name = "Quality
,
for volumes"
,
origin = StatusDescriptionCode
}
originalCodeListAgencyID =
status = draft
UNCL = "4405"
,
6,
,
}
46{codeName = "Does not exist"}
...
,
,
,
UNCL = "9013"
E01{codeName
E03{codeName
E20{codeName
E21{codeName
E23{codeName
E60{codeName
E65{codeName
E66{codeName
E67{codeName
E75{codeName
E77{codeName
1
Meter
,
origin = StatusReasonDescriptionCode
}
<<bEntity>>
+Identifier [1]
,
name = "BusinessReasonCode"
ebIX Business information model for the exchange of metered data in the energy market
2.3.1.1.
state machine
26
Collected Data (State Diagram)
Collected Data [
Collected Data ]
<<BusinessEntityState>>
Read
<<BusinessEntityState>>
<<bEState>>
Exchanged
Correct
Initial
Success
<<bEState>>
Incomplete
<<bEState>>
Values out of
limits
<<BusinessEntityState>>
Requested
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
27
2.3.2. Request Collected Data (Class Diagram)
package
Request Collected Data [
Request Collected Data ]
<<Assembled>>
<<bEntity>>
<<Subset>>
BusinessReasonCode
Request Collected Data
{codeListAgencyID = 260
+Identifier [1]
+Reason : ebix:org::Codes::ebIX Assembled::BusinessReasonCode [1]
+Sector : ebix:org::Codes::ebIX Assembled::SectorAreaIdentificationCode [1]
+Observation period [0..1]
<<use>>
,
{codeListAgencyID = 260
name = "BusinessReasonCode"
status = draft
BusinessReasonCode
,
,
1
MeteringPoint
+Identifier
UNCL = "9013"
}
originalCodeListAgencyID = 260
status = draft
E01{codeName
E03{codeName
E20{codeName
E21{codeName
E23{codeName
E65{codeName
E66{codeName
E67{codeName
E75{codeName
E77{codeName
0..*
Meter
=
=
=
=
=
=
=
=
=
=
}
"Move; change of party connected to the grid"}
"Change of balance supplier"}
"End of supply"}
"Change of data from party connected to the grid"}
"Periodic metering"}
"Consumer move-in"}
"Consumer move-out"}
"Placement of meter"}
"Change of metering method"}
"End of metering"}
...
+Identifier [1]
<<Assembled>>
<<Subset>>
SectorAreaIdentificationCode
<<bEntity>>
Register
{codeListAgencyID = 260
status = draft
UNCL = "7293"
SectorAreaIdentificationCode
,
name = "SectorAreaIdentificationCode"
{codeListAgencyID = 260
,
,
name = "SectorAreaIdentificationCode"
,
,
origin = SectorAreaIdentificationCode
}
originalCodeListAgencyID =
status = draft
+Identifier [1]
UNCL = "7293"
,
6,
,
}
23{codeName = "Electricity supply industry"}
...
ebIX©
October 2009
,
,
,
UNCL = "9013"
<<bEntity>>
1..*
,
origin = StatusReasonDescriptionCode
<<use>>
<<bEntity>>
,
name = "BusinessReasonCode"
ebIX Business information model for the exchange of metered data in the energy market
28
3. Business Choreography View: Collect
3.1. Introduction
This chapter contains the modeled business processes that regard the exchange of information.
Internal processes are not modeled here. The model is based on the business requirements (see
chapter Error! Reference source not found.).
Business processes are modeled bottom-up. The smallest elements are the Business Transactions.
Business Transactions are included in Business Collaborations. Smaller Collaborations may be
included in larger ones.
Finally a Collaborations is instantiated in a Business Realization. In the Realization the Business
Partners as specified in the requirements, is linked to this instance of a Collaboration.
Although the modeling has been done bottom-up, the resulting diagrams are presented in this
document top-down: first the Realization, then the Collaborations and finally the Transactions.
3.2. UseCase Exchange Collected Data (Business Realization)
use case
Exchange Collected Data [
Exchange Collected Data ]
<<bPartner>>
<<bPartner>>
Metering
Responsible
Collector
<<mapsTo>>
<<mapsTo>>
<<participates>>
<<Harmonized Role>>
Metered Data
Collector
<<bRealizationUC>>
Exchange
Collected Data
<<participates>>
<<Harmonized Role>>
Metered Data
Responsible
<<mapsTo>>
<<mapsTo>>
<<participates>>
<<AuthorizedRole>>
Collector
ebIX©
<<bCollaborationUC>>
Exchange Collected
Data
<<participates>>
<<AuthorizedRole>>
Metering Responsible
October 2009
ebIX Business information model for the exchange of metered data in the energy market
29
3.2.1. UseCase Exchange Collected Data (Business Collaboration)
use case
Exchange Collected Data [
Exchange Collected Data ]
<<bCollaborationUC>>
<<participates>>
<<participates>>
Exchange Collected
Data
<<AuthorizedRole>>
Collector
<<AuthorizedRole>>
Metering Responsible
<<include>>
<<bTransactionUC>>
Exchange
Collected Data
3.2.1.1.
Description
No detailed description for the Collaboration. For detailed description see Business Transaction.
3.2.1.2.
Exchange Collected Data
activ ity Exchange Collected Data [
Exchange Collected Data ]
<<bCPartition>>
<<bCPartition>>
Metering Responsible
Collector
<<bTransaction>>
<<initFlow>>
3.2.1.3.
use case
: Exchange
Collected Data
<<initFlow>>
UseCase Exchange Collected Data (Business Transaction)
Exchange Collected Data [
Exchange Collected Data ]
<<participates>>
<<AuthorizedRole>>
<<bTransactionUC>>
Exchange
Collected Data
Collector
3.2.1.3.1.
<<participates>>
<<AuthorizedRole>>
Metering Responsible
Description
UseCase description: Exchange Collected Data
definition
ebIX©
Collector sends collected data to Metering Responsible
October 2009
ebIX Business information model for the exchange of metered data in the energy market
30
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 Activity Diagram
3.2.1.3.2.
Exchange Collected Data
activ ity Exchange Collected Data [
Exchange Collected Data ]
<<bTPartition>>
<<bTPartition>>
Collector
Metering Responsible
Initial
<<ReqInfPin>>
<<ReqAction>>
send collected
data
CollectedData
<<ResAction>>
receiv e
collected data
ControlFailure
<<bESharedState>>
: Collected Data
[Exchanged]
BusinessSuccess
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
31
3.3. UseCase Request Collected Data (Business Realization)
use case
Request Collected Data [
Request Collected Data ]
<<bPartner>>
<<bPartner>>
Collector
Metering
Responsible
<<mapsTo>>
<<mapsTo>>
<<participates>>
<<Harmonized Role>>
Metered Data
Collector
<<bRealizationUC>>
Request
Collected Data
<<participates>>
<<Harmonized Role>>
Metered Data
Responsible
<<mapsTo>>
<<mapsTo>>
<<participates>>
<<AuthorizedRole>>
<<bCollaborationUC>>
Request Collected Data
Collector
<<participates>>
<<AuthorizedRole>>
Metering Responsible
3.3.1. UseCase Request Collected Data (Business Collaboration)
use case
Request Collected Data [
Request Collected Data ]
<<participates>>
<<AuthorizedRole>>
Metering Responsible
<<bCollaborationUC>>
Request Collected Data
<<participates>>
<<AuthorizedRole>>
Collector
<<include>>
<<bTransactionUC>>
Request Collected
Data
3.3.1.1.
Description
No detailed description for the Collaboration. For detailed description see Business Transaction.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
3.3.1.2.
Request Collected Data
activ ity Request Collected Data [
Request Collected Data ]
<<bCPartition>>
<<bCPartition>>
Collector
Metering Responsible
3.3.1.3.
use case
32
<<initFlow>>
<<bTransaction>>
<<reFlow>>
: Request
Collected Data
<<initFlow>>
<<reFlow>>
UseCase Request Collected Data (Business Transaction)
Request Collected Data [
Request Collected Data ]
<<participates>>
<<AuthorizedRole>>
<<bTransactionUC>>
Request Collected
Data
<<participates>>
<<AuthorizedRole>>
Metering Responsible
3.3.1.3.1.
Collector
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 Activity Diagram
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
3.3.1.3.2.
33
Request Collected Data
activ ity Request Collected Data [
Request Collected Data ]
<<bTPartition>>
Metering Responsible
Initial
<<bTPartition>>
Collector
<<ResInfPin>>
: CollectedData
<<bTransactionAction>>
<<bTransactionAction>>
Query
Respond
: RequestCollectedData
<<ReqInfPin>>
ControlFailure
BusinessSuccess
ebIX©
ControlFailure
October 2009
ebIX Business information model for the exchange of metered data in the energy market
34
4. Modeled Business Information: Collect (Business Information
View)
4.1. Introduction
Since UN/Cefact Modeling Methodology’s main focus is the modeling of processes and the
requirements on which these are based, the methodology for modeling information is its least
elaborated part. Till now it is assumed that UN/Cefact Core Component Technical Specification and
the UN/Cefact Core Components Message Assembly Guide cover the information modeling.
Unfortunately this is only partially the case.
So the assertion, that the information model in this chapter is completely in line with UMM-2, is
valid, but does not mean much. What may contribute more is a brief explanation in which account is
given for the way the business information has been modeled in ebIX documents regarding metered
data.
4.2. Brief explanation for the information model
4.2.1. Technology (syntax) independent information model
Key element in ebIX modeling is to model technology (syntax) independently. To this technology
independent model information may be added to enable the derivation of technology dependent
models or exchange formats from the technology independent information model.
Therefore in the Information View you will find the present version of the syntax independent
model. In Annex A you will find the representation of this model showing the necessary information
to enable the mapping to Edifact.
4.2.2. Mapping to Edifact
One of the purposes of the ebIX model for metered data is the creation of business documents
based on the UN/Cefact UNSM UTILTS (United Nations Standard Message “Utility Time Series”). This
means that a serious part of this document regards the mapping of the information model to UTILTS.
This mapping is in line with the ebIX recommendations for mapping to Edifact. The highlights of this
recommendation are:
1. Specify mapping information as a tagged value (for a tag definition that is a property for an UMLstereotype);
2. Remark: The format of a tagged value follows the ebIX format convention for specifying tagged
values.
3. Differentiate between the mapping of business data to a location in the UNSM and the mapping
of qualifying information;
4. For the package DocLibrary is specified:
4.1. QDT version used;
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
35
4.2. ABIE version used;
5. For the package BIELibrary is specified:
5.1. Edifact version used;
5.2. UNSM used;
5.3. QDT version used;
6. For the package QDTLibrary is specified:
6.1. Edifact version used;
7. Add information for mapping to Edifact segment and data element to the attributes of the
Qualified Data Types;
8. Add information for mapping to Edifact segment group to the BBIE;
9. Role specifications in the class diagrams contain the complete mapping information (both data
and qualifying + mapping to data element, segment and segment group).
4.2.3. Core Components
For the European Energy sector no Core Components (CC’s) have been defined yet. So approved
UN/Cefact CC’s cannot be used in the information models yet.
What has been done instead for the present ebIX models, is using the information clusters that
emerged from ebIX modeling over the past years as preliminary Core Components. These clusters
have been defined in line with the Core Components Technical Specification.
ebIX publishes the CC’s defined so far. In this publication the CC’s are documented and references
are made to either approved UN/Cefact CC’s (ACC, BCC or CDT) or to ebIX proposals for new CC’s
(ACC, BCC or CDT) to be approved.
4.2.4. Message Assembly
The UN/Cefact Core Components Message Assembly Guide is used in this model. The UN/Cefact
recommendation for the Standard Business Document Header is not used.
4.2.5. Linking attributes from Requirements View to attributes in
Information View
On request of some users in Annex B the links from data specified in the Business Requirements to
the resulting data in the Business Information View have been added. This is not a UMM-2
requirement.
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
36
4.3. Information model for Business Documents
See next page
ebIX©
October 2009
4.3.1. Collected Data (Business Information)
package
Exchange Collected Data [
Collected Data ]
<<ABIE>>
<<ASBIE>>
EnergyDocument
+Identification : un:unece:uncefact::CDTLibrary::Identifier [1]
+DocumentType : ebix:org::ebIX QDT::DocumentNameCodeType [1]
+Creation : un:unece:uncefact::CDTLibrary::DateTime [1]
+Header
<<ASBIE>>
<<ABIE>>
+Recipient
1
EnergyParty
+Sender
+Identification : ebix:org::ebIX QDT::PartyIdentifier [0..1]
+Role : ebix:org::ebIX QDT::BusinessRoleCodeType [0..1]
1
0..1
<<ABIE>>
<<bEntity>>
Service
Collected Data
<<MBIE>>
<<represents>>
1
+Process
<<ASMA>>
+TransactionReason : ebix:org::ebIX QDT::BusinessReasonCodeType [0..1]
+BusinessSectorCode : ebix:org::ebIX QDT::SectorAreaIdentificationCodeType [0..1]
+Role : ebix:org::ebIX QDT::BusinessRoleCodeType [1]
<<ABIE>>
{CD QDT Process}
TimeSeriesPeriod
+ResolutionDuration : ebix:org::ebIX QDT::IntegerMeasure [1]
+Start : un:unece:uncefact::CDTLibrary::DateTime [1]
+Observation +End : un:unece:uncefact::CDTLibrary::DateTime [1]
+Continuous : un:unece:uncefact::CDTLibrary::Indicator [0..1]
0..1
0..1
<<InfEnvelope>>
CollectedData
{CD QDT DOC,
CD STR DOC,
CD STR PLD}
<<ASMA>>
+Payload
1
<<ASBIE>>
<<MBIE>>
<<ABIE>>
2
EnergyTimeSeries
{CD DEP Payload,
CD QDT Payload,
CD STR Payload}
+Identification : un:unece:uncefact::PRIMLibrary::String [1] = Identification
+Currency : ebix:org::ebIX QDT::CurrencyIdentificationCodeType [0..1]
+Function : ebix:org::ebIX QDT::DocumentFunctionCodeType [0..1] = Function
+RegistrationDateTime : un:unece:uncefact::CDTLibrary::DateTime [0..1]
+LatestUpdateDate : un:unece:uncefact::CDTLibrary::Date [0..1]
<<ASBIE>>
<<ABIE>>
+Involved
EnergyParty
0..1
+Identification : ebix:org::ebIX QDT::PartyIdentifier [0..1]
+Role : ebix:org::ebIX QDT::BusinessRoleCodeType [0..1]
<<ASBIE>>
<<ABIE>>
ProductCharacteristic
+Included
0..1
+Identification : ebix:org::ebIX QDT::EnergyProductIdentificationCodeType [1]
+UnitType : ebix:org::ebIX QDT::MeasurementUnitCommonCodeType [0..1]
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
+MeteringGridArea 0..1
<<ASBIE>>
+BalanceGroup
0..1
+OutArea 0..1 +InArea 0..1 +MeteringPoint 0..1
<<ABIE>>
DomainLocation
+Identification : ebix:org::ebIX QDT::DomainIdentifierType [1]
<<ASBIE>>
+Register
0..1
+Interval 0..*
<<ABIE>>
<<ABIE>>
MeterFacility
+Register
+MeterIdentification : un:unece:uncefact::CDTLibrary::Identifier [0..1]
0..*
+RegisterIdentification : un:unece:uncefact::CDTLibrary::Identifier [0..1]
EnergyObservation
+Position : ebix:org::ebIX QDT::IntegerNumeric [0..1]
+EnergyQuantity : ebix:org::ebIX QDT::IntegerEnergyQuantity [0..*]
+EnergyPrice : ebix:org::ebIX QDT::SimpleAmount [0..*]
+QuantityQuality : ebix:org::Codes::ebIX Assembled::QuantityQualityCode [0..1]
+MeterTimeFrameType : ebix:org::ebIX QDT::MeterTimeFrameCodeType [0..*]
+QuantityMissing : un:unece:uncefact::CDTLibrary::Indicator [0..1]
+PriceMissing : un:unece:uncefact::CDTLibrary::Indicator [0..1]
<<ASBIE>>
4.3.1.1.
OCL constraints for CollectedData
4.3.1.2.
OCL constraints for CollectedData <<InfEnvelope>>
Name: CD STR DOC
-- Structure CollectedData Document
inv: self.Header->size()=1
inv: self.Header.Recipient.Identification->size()=1
inv: self.Header.Sender.Identification->size()=1
inv: self.Header.Recipient.Role->size()=0
inv: self.Header.Sender.Role->size()=0
inv: self.Process->size()=1
Name: CD STR PLD
-- Structure CollectedData Payload
inv: self.Header->size()=0
inv: self.Process->size()=0
Name: CD QDT DOC
-- QDT Instances Header
context CollectedData::Header::Identification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
context CollectedData::Header::DocumentType:DocumentNameTypeCode
inv: self.content=DocumentNameCode::E30
inv: self.codeListAgencyIdentifier=CodeListResponsibleAgencyCode::260
inv: self.codeListID->size()=0
context CollectedData::Header::Creation:DateTime
inv: formatText->size()=0
context CollectedData::Header::Recipient::Identification:PartyIdentifier
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9 or
identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::305
context CollectedData::Header::Sender::Identification:PartyIdentifier
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9 or
identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::305
ebIX Business information model for the exchange of metered data in the energy market
4.3.1.3.
39
OCL constraints for CollectedData <<MBIE>> 1
Name: CD QDT Process
-- QDT Instances Process
context Process::TransactionReason:BusinessReasonCodeType
inv: content = BusinessReasonCode::E01
inv: codeListResponsibleAgency = CodeListResponsibleAgencyCode::260
inv: codeListID->size()=0
context Process::BusinessSectorCode:SectorAreaIdentificationCodeType
inv: content = SectorAreaIdentificationCode::23
inv: codeListResponsibleAgency->size()=0
inv: codeListID->size()=0
context Process::Role:BusinessRoleCodeType
inv: content = BusinessRoleCode::MDR
inv: codeListResponsibleAgency->size()=0
inv: codeListID->size()=0
4.3.1.4.
OCL constraints for CollectedData <<MBIE>> 2
Name: CD STR Payload
-- Structure Payload
context EnergyTimeSeries
inv: self.Currency->size()=0
inv: self.Function->size()=1
inv: self.RegistrationDateTime->size()=1
inv: self.LastUpdateDate->size()=0
inv: self.Observation->size()=1
inv: self.Observation.Continuous->size()=0
inv: self.Involved->size()=0
inv: self.Included->size()=0
inv: self.MeteringPoint->size()=1
inv: self.InArea->size()=0
inv: self.OutArea->size()=0
inv: self.MeteringGridArea->size()=0
inv: self.BalanceGroup->size()=0
inv: self.Register->size()=1
inv: self.Interval->notEmpty()
inv: self.Interval.Position->size()=1
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
40
Name: CD QDT Payload
-- QDT Instances Payload
context EnergyTimeSeries::Function:DocumentFunctionCodeType
inv: content = DocumentFunctionCode::9
inv: codeListResponsibleAgency->size()=0
context EnergyTimeSeries::RegistrationDateTime:DateTime
inv: formatText->size()=0
context EnergyTimeSeries::Observation::ResolutionDuration:IntegerMeasure
inv: content=15
inv: measureUnitCode = MeasureUnitCommonCode::MIN
context EnergyTimeSeries::Observation::Start:DateTime
inv: formatText->size()=0
context EnergyTimeSeries::Observation::End:DateTime
inv: formatText->size()=0
context EnergyTimeSeries::MeteringPoint::Identification:DomainIdentifierType
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9
context EnergyTimeSeries::Register::MeterIdentification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
context EnergyTimeSeries::Register::RegisterIdentification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
context EnergyTimeSeries::Interval::Position:IntegerNumeric
init: 1
context EnergyTimeSeries::Interval::EnergyQuantity:IntegerEnergyQuantity
inv: measureUnitCode->size()=0
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
41
Name: CD DEP Payload
-- Dependency Payload
context EnergyTimeSeries
inv: self.Interval.EnergyQuantity->notEmpty implies self.Interval.EnergyQuantity->size=1
inv: self.Interval.EnergyQuantity->size()=1 implies self.Interval.QuantityMissing->size=0
inv: self.Interval.EnergyQuantity->isEmpty() implies self.Interval.QuantityMissing->size=1
inv: self.Interval.QuantityMissing->size=1 implies self.Interval.QuantityMissing = true
ebIX©
October 2009
4.3.2. Request Collected Data (Business Information)
package
Request Collected Data [
Request Collected Data ]
<<ABIE>>
<<ASBIE>>
EnergyDocument
<<ABIE>>
1
EnergyParty
+Identification : ebix:org::ebIX QDT::PartyIdentifier [0..1]
<<ASBIE>> +Recipient +Role : ebix:org::ebIX QDT::BusinessRoleCodeType [0..1]
+Identification : un:unece:uncefact::CDTLibrary::Identifier [1]
+DocumentType : ebix:org::ebIX QDT::DocumentNameCodeType [1]
+Creation : un:unece:uncefact::CDTLibrary::DateTime [1]
+Header
+Sender
1
0..1
<<ABIE>>
Service
<<MBIE>>
1
+ContextRequestCollectedData
<<InfEnvelope>>
<<ASMA>>
+TransactionReason : ebix:org::ebIX QDT::BusinessReasonCodeType [0..1]
+BusinessSectorCode : ebix:org::ebIX QDT::SectorAreaIdentificationCodeType [0..1]
+Role : ebix:org::ebIX QDT::BusinessRoleCodeType [1]
{RCD QDT Process}
<<ABIE>>
0..1
TimeSeriesPeriod
RequestCollectedData
{RCD QDT DOC,
RCD STR DOC,
RCD STR PLD}
+Payload
<<ASMA>>
1
<<MBIE>>
<<ABIE>>
2
EnergyTimeSeries
{RCD QDT Payload,
RCD STR Payload}
+Identification : un:unece:uncefact::PRIMLibrary::String [1] = Identification
+Currency : ebix:org::ebIX QDT::CurrencyIdentificationCodeType [0..1]
+Function : ebix:org::ebIX QDT::DocumentFunctionCodeType [0..1] = Function
+RegistrationDateTime : un:unece:uncefact::CDTLibrary::DateTime [0..1]
+LatestUpdateDate : un:unece:uncefact::CDTLibrary::Date [0..1]
<<ASBIE>>
+Observation
0..1
+ResolutionDuration : ebix:org::ebIX QDT::IntegerMeasure [1]
+Start : un:unece:uncefact::CDTLibrary::DateTime [1]
+End : un:unece:uncefact::CDTLibrary::DateTime [1]
+Continuous : un:unece:uncefact::CDTLibrary::Indicator [0..1]
<<ABIE>>
<<ASBIE>>
EnergyParty
+Involved
0..1
+Identification : ebix:org::ebIX QDT::PartyIdentifier [0..1]
+Role : ebix:org::ebIX QDT::BusinessRoleCodeType [0..1]
<<ASBIE>>
<<ABIE>>
ProductCharacteristic
+Included
0..1
+Identification : ebix:org::ebIX QDT::EnergyProductIdentificationCodeType [1]
+UnitType : ebix:org::ebIX QDT::MeasurementUnitCommonCodeType [0..1]
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
<<ASBIE>>
+MeteringGridArea 0..1
<<ASBIE>>
+BalanceGroup
0..1
+OutArea 0..1
+InArea 0..1 +MeteringPoint 0..1
<<ABIE>>
DomainLocation
+Identification : ebix:org::ebIX QDT::DomainIdentifierType [1]
<<ABIE>>
<<ASBIE>>
+Register
0..1
MeterFacility
+Register
+MeterIdentification : un:unece:uncefact::CDTLibrary::Identifier [0..1]
0..*
+RegisterIdentification : un:unece:uncefact::CDTLibrary::Identifier [0..1]
+Interval 0..*
<<ABIE>>
EnergyObservation
+Position : ebix:org::ebIX QDT::IntegerNumeric [0..1]
+EnergyQuantity : ebix:org::ebIX QDT::IntegerEnergyQuantity [0..*]
+EnergyPrice : ebix:org::ebIX QDT::SimpleAmount [0..*]
+QuantityQuality : ebix:org::Codes::ebIX Assembled::QuantityQualityCode [0..1]
+MeterTimeFrameType : ebix:org::ebIX QDT::MeterTimeFrameCodeType [0..*]
+QuantityMissing : un:unece:uncefact::CDTLibrary::Indicator [0..1]
+PriceMissing : un:unece:uncefact::CDTLibrary::Indicator [0..1]
<<ASBIE>>
4.3.2.1.
OCL constraints for RequestCollectedData
4.3.2.2.
OCL constraints for RequestCollectedData <<InfEnvelope>>
Name: RCD STR DOC <<Structure>> <<Document>>
-- Structure RequestCollectedData Document
inv: self.Header->size()=1
inv: self.Header.Recipient.Identification->size()=1
inv: self.Header.Sender.Identification->size()=1
inv: self.Header.Recipient.Role->size()=0
inv: self.Header.Sender.Role->size()=0
inv: self.Process->size()=1
Name: RCD STR PLD <<Structure>> <<Payload>>
-- Structure RequestCollectedData Payload
inv: self.Header->size()=0
inv: self.Process->size()=0
Name: RCD QDT DOC <<QDT>> <<Document>>
-- QDT Instances Header
context CollectedData::Header::Identification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
context CollectedData::Header::DocumentType:DocumentNameTypeCode
inv: self.content=DocumentNameCode::E72
inv: self.codeListAgencyIdentifier=CodeListResponsibleAgencyCode::260
inv: self.codeListID->size()=0
context CollectedData::Header::Creation:DateTime
inv: formatText->size()=0
context CollectedData::Header::Recipient::Identification:PartyIdentifier
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9 or
identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::305
context CollectedData::Header::Sender::Identification:PartyIdentifier
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9 or
identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::305
ebIX Business information model for the exchange of metered data in the energy market
4.3.2.3.
44
OCL constraints for RequestCollectedData 1 <<MBIE>>
Name: RCD QDT Process <<QDT>>
-- QDT Instances Process
context Process::TransactionReason:BusinessReasonCodeType
inv: content = BusinessReasonCode::E01
inv: codeListResponsibleAgency = CodeListResponsibleAgencyCode::260
inv: codeListID->size()=0
context Process::BusinessSectorCode:SectorAreaIdentificationCodeType
inv: content = SectorAreaIdentificationCode::23
inv: codeListResponsibleAgency->size()=0
inv: codeListID->size()=0
context Process::Role:BusinessRoleCodeType
inv: content = BusinessRoleCode::MDR
inv: codeListResponsibleAgency->size()=0
inv: codeListID->size()=0
4.3.2.4.
OCL constraints for RequestCollectedData 2 <<MBIE>>
Name: RCD STR Payload <<Payload>>
-- Structure Payload
context EnergyTimeSeries
inv: self.Currency->size()=0
inv: self.Function->size()=1
inv: self.RegistrationDateTime->size()=0
inv: self.LastUpdateDate->size()=0
inv: self.Observation->size()=1
inv: self.Observation.ResolutionDuration->size()=0
inv: self.Observation.Continuous->size()=0
inv: self.Involved->size()=0
inv: self.Included->size()=0
inv: self.MeteringPoint->size()=1
inv: self.InArea->size()=0
inv: self.OutArea->size()=0
inv: self.MeteringGridArea->size()=0
inv: self.BalanceGroup->size()=0
inv: self.Interval->isEmpty()
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy market
45
Name: CD QDT Payload <<QDT>>
-- QDT Instances Payload
context EnergyTimeSeries::Function:DocumentFunctionCodeType
inv: content = DocumentFunctionCode::9
inv: codeListResponsibleAgency->size()=0
context EnergyTimeSeries::Observation::Start:DateTime
inv: formatText->size()=0
context EnergyTimeSeries::Observation::End:DateTime
inv: formatText->size()=0
context EnergyTimeSeries::MeteringPoint::Identification:DomainIdentifierType
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeAgencyIdentifier = CodeListResponsibleAgencyCode::9
context EnergyTimeSeries::Register::MeterIdentification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
context EnergyTimeSeries::Register::RegisterIdentification:Identifier
inv: identificationSchemeIdentifier->size()=0
inv: identificationSchemeNameText->size()=0
inv: identificationSchemeAgencyIdentifier->size()=0
inv: identificationSchemeAgencyNameText->size()=0
inv: identificationSchemeVersionIdentifier->size()=0
inv: identificationSchemeDataURI->size()=0
inv: identificationSchemeURI->size()=0
Name: CD DEP Payload <<Dependency>>
-- Dependency Payload
context EnergyTimeSeries
inv: self.Interval.EnergyQuantity->notEmpty implies self.Interval.EnergyQuantity->size=1
inv: self.Interval.EnergyQuantity->size()=1 implies self.Interval.QuantityMissing->size=0
inv: self.Interval.EnergyQuantity->isEmpty() implies self.Interval.QuantityMissing->size=1
inv: self.Interval.QuantityMissing->size=1 implies self.Interval.QuantityMissing = true
ebIX©
October 2009
ebIX Business information model for the exchange of metered data in the energy domain
46
Appendix A REMARKS REGARDING CLASS DIAGRAMS FOR MEASURE
A.

Direction
ebIX models provide the opportunity to specify the directions explicitly:
o for exchange metering points by specifying the in- and/or out-area;
o for local metering points by specifying the type of metering point (production or
consumption)
o at least one attribute has to be specified (either out area or in area)

In case the direction is only specified implicitly, the convention for signs used to specify the
direction (also for combined metering point type):
o For metering grid area’s: the direction is always defined relative to the specified (own)
metering grid area
B.

a flow out of the own metering grid area is indicated as – (minus) according to ETSOebIX convention and as 1 according the OBIS-convention (Austria, Germany and
Switzerland according to IEC-standard)

a flow into the own metering grid area is indicated as + (plus) according to ETSOebIX convention and as 2 according the OBIS-convention (Austria, Germany and
Switzerland according to IEC-standard)
Update procedures
Update procedures may differ nationally. Below you find the overview over the update procedures
that are used per country.
Country
Update procedure
AT
update per business document (time series)
BE
update per business document (time series)
CH
update per business document (time series)
ebIX
September 2009
ebIX Business information model for the exchange of metered data in the energy domain
DE
update per business document (time series)
DK
update per business document (time series)
NL
update per business document (time series)
NO
update per business document (time series)
SE
update per business document (time series)
ebIX
47
September 2009