SIST EN 62325-451-5:2015

Framework for energy market communications - Part 451-5: Problem statement and status request business processes, contextual and assembly models for European market

IEC 62325-451-5:2015 is based on the European style market profile (IEC 62325-351) and specifies a package for the problem statement and status request business processes and the associated document contextual models, assembly models and XML schema for use within European style markets. The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualised into aggregated business information entities (ABIEs) to satisfy the requirements of this business process.

Kommunikation im Energiemarkt - Teil 451-5: Problemstellungs- und Status-Anfragen-Geschäftsprozesse, kontextbezogene Modelle und Einbindungsmodelle für den europäischen Markt

Cadre pour les communications pour le marché de l’énergie - Partie 451-5: Processus métier d’énoncé de problème et de demande de position, modèles contextuels et modèles d’assemblage pour le marché européen

L'IEC 62325-451-5:2015 est basée sur le profil de marché de style européen (IEC 62325-351) et spécifie un paquetage pour les processus métier d'information suite à problème et de demande de position et les modèles contextuels de document, modèles d'assemblage et schéma XML associés à utiliser sur les marchés de style européen. Les composants de base agrégés pertinents définis dans l'IEC 62325-351 ont été contextualisés en entités d'information métier agrégées afin de satisfaire aux exigences de ce processus métier.

Okvir za komunikacije na trgu z električno energijo - 451- 5. del: Poslovni proces za določitev problema in zajemanje stanja, kontekstni in združevalni modeli evropskega trga (IEC 62325-451-5:2015)

Na podlagi profila za evropski trg (IEC 62325-351) ta del standarda IEC 62325-451 določa paket poslovnih procesov za določitev problema in zajemanje stanja ter povezani dokument kontekstnih modelov, združevalnih modelov in sheme XML za uporabo na evropskih trgih.
Ustrezne združene osrednje komponente (ACC), opredeljene v standardu IEC 62325-351, so bile kontekstualizirane v združene entitete poslovnih informacij (ABIE), da ustrezajo zahtevam za ta poslovni proces. Te kontekstualizirane entitete so bile zbrane v zadevni dokument kontekstnih modelov. Ustrezni združevalni modeli in shema XML za izmenjavo informacij med udeleženci na trgu se samodejno ustvarijo iz zbranih dokumentov kontekstnih modelov.

General Information

• Status: Published
• Publication Date: 23-Apr-2015
• ICS: 29.240.30 - Control equipment for electric power systems
• ICS: 33.200 - Telecontrol. Telemetering
• Technical Committee: PSE - Power systems management
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 09-Apr-2015
• Due Date: 14-Jun-2015
• Completion Date: 24-Apr-2015
• Mandate: M/490 - Standardisation mandate to the European Standardisation Organisations (ESOs) to support European Smart Grid deployment
• Ref Project: EN 62325-451-5:2015 - Framework for energy market communications - Part 451-5: Problem statement and status request business processes, contextual and assembly models for European market

Standards Content (Sample)

SLOVENSKI STANDARD
01-maj-2015
2NYLU]DNRPXQLNDFLMHQDWUJX]HOHNWULþQRHQHUJLMRGHO3RVORYQLSURFHV
]DGRORþLWHYSUREOHPDLQ]DMHPDQMHVWDQMDNRQWHNVWQLLQ]GUXåHYDOQLPRGHOL
HYURSVNHJDWUJD,(&
Framework for energy market communications - Part 451-5: Problem statement and
status request business processes, contextual and assembly models for European
market
Ta slovenski standard je istoveten z: EN 62325-451-5:2015
ICS:
29.240.30 Krmilna oprema za Control equipment for electric
elektroenergetske sisteme power systems
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 62325-451-5

NORME EUROPÉENNE
EUROPÄISCHE NORM
April 2015
ICS 33.200
English Version
Framework for energy market communications - Part 451-5:
Problem statement and status request business processes,
contextual and assembly models for European market
(IEC 62325-451-5:2015)
Cadre pour les communications pour le marché de l'énergie Kommunikation im Energiemarkt - Teil 451-5:
- Partie 451-5: Processus métier d'énoncé de problème et Problemstellungs- und Status-Anfragen-
de demande de position, modèles contextuels et modèles Geschäftsprozesse, kontextbezogene Modelle und
d'assemblage pour le marché européen Einbindungsmodelle für den europäischen Markt
(IEC 62325-451-5:2015) (IEC 62325-451-5:2015)
This European Standard was approved by CENELEC on 2015-03-24. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62325-451-5:2015 E

Foreword
The text of document 57/1518/FDIS, future edition 1 of IEC 62325-451-5, prepared by IEC/TC 57
"Power systems management and associated information exchange" was submitted to the IEC-
CENELEC parallel vote and approved by CENELEC as EN 62325-451-5:2015.
The following dates are fixed:
– latest date by which the document has to be implemented at (dop) 2015-12-24
national level by publication of an identical national
standard or by endorsement
– latest date by which the national standards conflicting with (dow) 2018-03-24
the document have to be withdrawn

Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
Endorsement notice
The text of the International Standard IEC 62325-451-5:2015 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards
indicated:
IEC 61968-11 NOTE Harmonized as EN 61968-11.
IEC 61970-301 NOTE Harmonized as EN 61970-301.
IEC 62325-451-2 NOTE Harmonized as EN 62325-451-2.
IEC 62325-451-3 NOTE Harmonized as EN 62325-451-3.

- 3 - EN 62325-451-5:2015
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant
EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Publication Year Title EN/HD Year

IEC TS 61970-2 -  Energy management system application - -
program interface (EMS-API) -
Part 2: Glossary
IEC 62325-301 -  Framework for energy market EN 62325-301 -
communications --
Part 301: Common Information Model
(CIM) extensions for markets
IEC 62325-351 -  Framework for energy market EN 62325-351 -
communications --
Part 351: CIM European market model
exchange profile
IEC 62325-450 -  Framework for energy market EN 62325-450 -
communications --
Part 450: Profile and context modelling
rules
IEC 62325-451-1 -  Framework for energy market EN 62325-451-1 -
communications --
Part 451-1: Acknowledgement business
process and contextual model for CIM
European market
IEC 62361-100 -  Power systems managment and - -
associated information exchange -
Interoperability in the long term --
Part 100: CIM profiles to XML schema
mapping
IEC 62325-451-5 ®
Edition 1.0 2015-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Framework for energy market communications –

Part 451-5: Problem statement and status request business processes,

contextual and assembly models for European market

Cadre pour les communications pour le marché de l’énergie –

Partie 451-5: Processus métier d’énoncé de problème et de demande de

position, modèles contextuels et modèles d’assemblage pour le marché

européen
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200 ISBN 978-2-8322-2224-9

– 2 – IEC 62325-451-5:2015 © IEC 2015
CONTENTS
FOREWORD . 6
INTRODUCTION . 8
1 Scope . 9
2 Normative references . 9
3 Terms and definitions . 10
4 Document contextual model and message assembly model basic concepts . 11
4.1 Overview. 11
4.2 European style market package structure . 12
4.3 From the European style market profile to the document contextual model . 14
4.4 From the document contextual model to the message assembly model . 14
4.5 From the assembly model to the XML schema . 14
5 The problem statement and status request business process . 14
5.1 Business context for the problem statement process . 14
5.2 Business context for the status request process. 15
5.2.1 Overview of the status request process . 15
5.2.2 Use case for the status request process . 15
5.2.3 Sequence diagrams for the status request process . 16
5.3 Business rules . 18
5.3.1 General . 18
5.3.2 Business rules for the problem statement process . 18
5.3.3 Business rules for the status request process . 18
6 Contextual and assembly models. 18
6.1 Problem statement contextual model. 18
6.1.1 Overview of the model . 18
6.1.2 IsBasedOn relationships from the European style market profile . 19
6.1.3 Detailed Problem statement contextual model . 19
6.2 Problem statement assembly model . 25
6.2.1 Overview of the model . 25
6.2.2 IsBasedOn relationships from the European style market profile . 25
6.2.3 Detailed Problem statement assembly model . 25
6.2.4 Datatypes . 28
6.2.5 Enumerations . 32
6.3 Status request contextual model . 32
6.3.1 Overview of the model . 32
6.3.2 IsBasedOn relationships from the European style market profile . 33
6.3.3 Detailed Status request contextual model . 33
6.4 Status request assembly model . 36
6.4.1 Overview of the model . 36
6.4.2 IsBasedOn relationships from the European style market profile . 36
6.4.3 Detailed Status request assembly model . 36
6.4.4 Datatypes . 38
6.4.5 Enumerations . 40
7 XML schema . 41
7.1 XML schema URN namespace rules . 41
7.2 Code list URN namespace rules . 41

IEC 62325-451-5:2015 © IEC 2015 – 3 –
7.3 URI rules for model documentation . 41
7.3.1 Datatype . 41
7.3.2 Class . 42
7.3.3 Attribute . 42
7.3.4 Association end role name . 42
7.4 ProblemStatement_MarketDocument schema . 43
7.4.1 Schema Structure . 43
7.4.2 Schema description . 44
7.5 StatusRequest_MarketDocument schema . 47
7.5.1 Schema Structure . 47
7.5.2 Schema description . 48
Bibliography . 50

Figure 1 – IEC 62325-450 modelling framework . 12
Figure 2 – Overview of European style market profile dependency . 13
Figure 3 – Problem statement business case . 14
Figure 4 – Status request business case . 16
Figure 5 – Status request scenario 1 . 17
Figure 6 – Status request scenario 2 . 17
Figure 7 – Problem statement contextual model . 19
Figure 8 – Problem statement assembly model . 25
Figure 9 – Status request contextual model . 33
Figure 10 – Status request assembly model . 36
Figure 11 – ProblemStatement_MarketDocument XML schema structure . 43
Figure 12 – StatusRequest_MarketDocument XML schema structure . 47

Table 1 – IsBasedOn dependency. 19
Table 2 – Attributes of Problem statement contextual
model::ProblemStatement_MarketDocument . 20
Table 3 – Association ends of Problem statement contextual
model::ProblemStatement_MarketDocument with other classes . 20
Table 4 – Attributes of Problem statement contextual
model::Delivery_MarketDocument . 21
Table 5 – Attributes of Problem statement contextual model::Domain . 21
Table 6 – Attributes of Problem statement contextual model::MarketDocument . 22
Table 7 – Association ends of Problem statement contextual model::MarketDocument
with other classes . 22
Table 8 – Attributes of Problem statement contextual model::MarketParticipant . 22
Table 9 – Association ends of Problem statement contextual model::MarketParticipant
with other classes . 23
Table 10 – Attributes of Problem statement contextual model::MarketRole. 23
Table 11 – Attributes of Problem statement contextual model::Process . 23
Table 12 – Attributes of Problem statement contextual model::Reason . 24
Table 13 – Attributes of Problem statement contextual model::Time_Period . 24
Table 14 – IsBasedOn dependency . 25

– 4 – IEC 62325-451-5:2015 © IEC 2015
Table 15 – Attributes of Problem statement assembly
model::ProblemStatement_MarketDocument . 26
Table 16 – Association ends of Problem statement assembly
model::ProblemStatement_MarketDocument with other classes . 27
Table 17 – Attributes of Problem statement assembly model::Reason . 27
Table 18 – Attributes of ESMPDataTypes::ESMP_DateTimeInterval . 28
Table 19 – Attributes of ESMPDataTypes::AreaID_String. 28
Table 20 – Restrictions of attributes for ESMPDataTypes::AreaID_String . 28
Table 21 – Attributes of ESMPDataTypes::ESMP_DateTime . 28
Table 22 – Restrictions of attributes for ESMPDataTypes::ESMP_DateTime . 29
Table 23 – Attributes of ESMPDataTypes::ESMPVersion_String . 29
Table 24 – Restrictions of attributes for ESMPDataTypes::ESMPVersion_String . 29
Table 25 – Attributes of ESMPDataTypes::ID_String . 30
Table 26 – Restrictions of attributes for ESMPDataTypes::ID_String . 30
Table 27 – Attributes of ESMPDataTypes::MarketRoleKind_String . 30
Table 28 – Attributes of ESMPDataTypes::MessageKind_String . 30
Table 29 – Attributes of ESMPDataTypes::PartyID_String . 31
Table 30 – Restrictions of attributes for ESMPDataTypes::PartyID_String . 31
Table 31 – Attributes of ESMPDataTypes::ProcessKind_String . 31
Table 32 – Attributes of ESMPDataTypes::ReasonCode_String. . 31
Table 33 – Attributes of ESMPDataTypes::ReasonText_String . 31
Table 34 – Restrictions of attributes for ESMPDataTypes::ReasonText_String . 32
Table 35 – Attributes of ESMPDataTypes::YMDHM_DateTime . 32
Table 36 – Restrictions of attributes for ESMPDataTypes::YMDHM_DateTime . 32
Table 37 – IsBasedOn dependency . 33
Table 38 – Attributes of Status request contextual
model::StatusRequest_MarketDocument . 33
Table 39 – Association ends of Status request contextual
model::StatusRequest_MarketDocument with other classes . 34
Table 40 – Attributes of Status request contextual model::AttributeInstanceComponent . 34
Table 41 – Attributes of Status request contextual model::MarketParticipant . 35
Table 42 – Association ends of Status request contextual model::MarketParticipant
with other classes . 35
Table 43 – Attributes of Status request contextual model::MarketRole . 35
Table 44 – IsBasedOn dependency . 36
Table 45 – Attributes of Status request assembly
model::StatusRequest_MarketDocument . 37
Table 46 – Association ends of Status request assembly
model::StatusRequest_MarketDocument with other classes . 37
Table 47 – Attributes of Status request assembly model::AttributeInstanceComponent . 38
Table 48 – Attributes of ESMPDataTypes::AttributeValue_String . 38
Table 49 – Restrictions of attributes for ESMPDataTypes::AttributeValue_String . 38
Table 50 – Attributes of ESMPDataTypes::ESMP_DateTime . 38
Table 51 – Restrictions of attributes for ESMPDataTypes::ESMP_DateTime . 39
Table 52 – Attributes of ESMPDataTypes::ID_String . 39

IEC 62325-451-5:2015 © IEC 2015 – 5 –
Table 53 – Restrictions of attributes for ESMPDataTypes::ID_String . 39
Table 54 – Attributes of ESMPDataTypes::MarketRoleKind_String . 40
Table 55 – Attributes of ESMPDataTypes::MessageKind_String . 40
Table 56 – Attributes of ESMPDataTypes::PartyID_String . 40
Table 57 – Restrictions of attributes for ESMPDataTypes::PartyID_String . 40

– 6 – IEC 62325-451-5:2015 © IEC 2015
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FRAMEWORK FOR ENERGY MARKET COMMUNICATIONS –

Part 451-5: Problem statement and status request business processes,
contextual and assembly models for European market

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62325-451-5 has been prepared by IEC technical committee 57:
Power systems management and associated information exchange.
The text of this standard is based on the following documents:
FDIS Report on voting
57/1518/FDIS 57/1543/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

IEC 62325-451-5:2015 © IEC 2015 – 7 –
A list of all parts in the IEC 62325 series, published under the general title Framework for
energy market communications, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 8 – IEC 62325-451-5:2015 © IEC 2015
INTRODUCTION
This standard is one of the IEC 62325 series which define protocols for deregulated energy
market communications.
The principal objective of the IEC 62325 series of standards is to produce standards which
facilitate the integration of market application software developed independently by different
vendors into a market management system, between market management systems and
market participant systems. This is accomplished by defining message exchanges to enable
these applications or systems access to public data and exchange information independent of
how such information is represented internally.
The common information model (CIM) specifies the basis for the semantics for this message
exchange.
The European style market profile is based on different parts of the CIM IEC standard. The
CIM is defined through a series of standards, i.e. IEC 62325-301, IEC 61970-301 and
IEC 61968-11 standards.
This document provides for the European style market profile the problem statement and
status request business processes that can be used throughout a European style market. This
standard was originally based upon the work of the European Transmission System Operators
(ETSO) Task Force EDI (Electronic Data Interchange) and then on the work of the European
Network of Transmission System Operators (ENTSO-E) Working Group EDI.

IEC 62325-451-5:2015 © IEC 2015 – 9 –
FRAMEWORK FOR ENERGY MARKET COMMUNICATIONS –

Part 451-5: Problem statement and status request business processes,
contextual and assembly models for European market

1 Scope
Based on the European style market profile (IEC 62325-351), this part of IEC 62325-451
specifies a package for the problem statement and status request business processes and the
associated document contextual models, assembly models and XML schema for use within
European style markets.
The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been
contextualised into aggregated business information entities (ABIEs) to satisfy the
requirements of this business process. The contextualised ABIEs have been assembled into
the relevant document contextual models. Related assembly models and XML schema for the
exchange of information between market participants are automatically generated from the
assembled document contextual models.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC TS 61970-2, Energy management system application program interface (EMS-API) –
Part 2: Glossary
IEC 62325-301, Framework for energy market communications – Part 301: Common
information model (CIM) extensions for markets
IEC 62325-351, Framework for energy market communications – Part 351: CIM European
market model exchange profile
IEC 62325-450, Framework for energy market communications – Part 450: Profile and context
modelling rules
IEC 62325-451-1, Framework for energy market communications – Part 451-1:
Acknowledgement business process and contextual model for CIM European market
IEC 62361-100 , Power systems management and associated information exchange –
Interoperability in the long term – Part 100: CIM profiles to XML schema mapping
______________
Under consideration.
– 10 – IEC 62325-451-5:2015 © IEC 2015
3 Terms and definitions
For the purposes of this document, the terms and definitions of IEC 61970-2 apply, as well as
the following.
NOTE Refer to IEC 60050, International Electrotechnical Vocabulary, for general glossary definitions.
3.1
aggregate business information entity
ABIE
re-use of an aggregate core component (ACC) in a specified business
[SOURCE: ISO/TS 15000-5:2005, Clause 9, modified (modification of the definition)]
3.2
aggregate core component
ACC
collection of related pieces of business information that together convey a distinct business
meaning, independent of any specific business context
Note 1 to entry: Expressed in modelling terms, this is the representation of an object class, independent of any
specific business context.
[SOURCE: ISO/TS 15000-5:2005, Clause 9, modified (modification of the definition)]
3.3
application program interface
API
set of public functions provided by an executable application component for use by other
executable application components
3.4
assembly model
model that prepares information in a business context for assembly into electronic documents
for data interchange
3.5
based on
IsBasedOn
use of an artefact that has been restricted according to the requirements of a specific
business context
[SOURCE: IEC 62325-450:2013, 3.4]
3.6
business context
formal description of a specific business circumstance as identified by the values of a set of
context categories, allowing different business circumstances to be uniquely distinguished
[SOURCE: UN/Cefact, Unified Context Methodology Technical Specification]
3.7
European style market profile
ESMP
the European style market profile, the object of this International Standard

IEC 62325-451-5:2015 © IEC 2015 – 11 –
3.8
information model
representation of concepts, relationships, constraints, rules, and operations to specify data
semantics for a chosen domain of discourse
Note 1 to entry: It can provide shareable, stable, and organized structure of information requirements for the
domain context.
3.9
market management system
MMS
computer system comprised of a software platform providing basic support services and a set
of applications providing the functionality needed for the effective management of the
electricity market
Note 1 to entry: These software systems in an electricity market may include support for capacity allocation,
scheduling energy, ancillary or other services, real-time operations and settlements.
3.10
message business information entity
MBIE
aggregation of a set of ABIEs that respects a define set of assembly rules
4 Document contextual model and message assembly model basic concepts
4.1 Overview
IEC 62325-450 defines a set of CIM profiles that follows a layered modelling framework as
outlined in Figure 1 going from the common information model (CIM; IEC 61968-11,
IEC 61970-301 and IEC 62325-301), to different regional contextual models and their
subsequent contextualized documents for information exchange; the final step being the
message specifications for information interchange.

– 12 – IEC 62325-451-5:2015 © IEC 2015

IEC
Figure 1 – IEC 62325-450 modelling framework
The regional contextual models are the basic core components that are necessary to build
electronic documents for information interchange. This is defined in the European style
market contextual model (IEC 62325-351). These core components are also termed
aggregate core components (ACCs).
A document contextual model is based upon a specific business requirements specification
and is constructed from the contextualisation of the ACCs that can be found in the European
style market contextual model. The contextualised ACCs at this stage are terms aggregate
business information entities (ABIEs) These ABIEs are the constructs that are assembled
together into a specific electronic document to satisfy the information requirements outlined in
the business requirements specification. The transformation from an ACC to an ABIE shall
respect the rules defined in IEC 62325-450.
Once a document contextual model has been built that satisfactorily meets the business
requirements, a message assembly model can be automatically generated from it.
XML schema then may be automatically generated from the message assembly model. If
necessary specific mapping can take place at this stage to transform the CIM class and
attribute names into more market legacy names.
4.2 European style market package structure
Figure 2 describes the main package structure of the European style market profile.

IEC 62325-451-5:2015 © IEC 2015 – 13 –

IEC
Figure 2 – Overview of European style market profile dependency
For each business process, a business process package is described in an IEC 62325-451-x
(x from 1 to n) standard. A business process package contains:
• The document contextual model (ABIE) and the automatically generated message
assembly model (MBIE) for each electronic document required to enable the completion of
the business process. Each document is a sub contextual model derived by restriction
from the European style market profile.
• The XML schema of the business document that is automatically generated from the
message assembly model.
The European style market profile (ESMP), as defined in IEC 62325-351, provides the core
components permitted for use in an IEC 62325-451-x standard as all ABIEs shall be “based
on” the IEC 62325-351 core components:
• ESMPClasses: Defining all the semi-contextual classes of the European style market
profile derived by restriction from the CIM model.
• ESMPDataTypes: Defining all the core datatypes used within the ESMP classes.
All the core components that are used in every electronic document structure have been
harmonized and centralized in the European style market profile. These core components are
consequently the basic building blocks from which all electronic document ABIEs are derived.

– 14 – IEC 62325-451-5:2015 © IEC 2015
4.3 From the European style market profile to the document contextual model
The document contextual model for a given business process is constructed by an information
analyst who identifies all the information requirements necessary to satisfy the business
process.
Once the information requirements have been identified the information analyst identifies the
related ACCs that are available in the European style market profile and contextualises them
to meet the information requirements. This contextualisation step creates a set of aggregate
business information entities (ABIEs).
In a final step the information analyst assembles together into a specific document contextual
model package the ABIEs to form a document model satisfying the business requirements.
4.4 From the document contextual model to the message assembly model
Once the document contextual model has been finalised, the message assembly model may
be automatically generated.
All document contextual models share the same core components and core datatypes. These
are defined in the European style market profile (IEC 62325-351) and are contextualised and
refined in all document contextual models (IEC 62325-451-x series) respecting the rules as
described in IEC 62325-450.
4.5 From the assembly model to the XML schema
The final modelling step applies a standardized set of criteria in order to generate a uniform
XML schema from the assembly model. This transformation process respects the rules
defined in IEC 62361-100.
5 The problem statement and status request business process
5.1 Business context for the problem statement process
The objective of the problem statement process is to provide:
• a means of informing a party that a document could not be issued by the expected time
and thus will be delayed (the approval of this delay depends upon the rules that have been
established between the parties);
• an automated support in the case where an escalation procedure has to be put into place
when an expected event does not occur or a critical situation has to be resolved.
Figure 3 displays the two parties involved in this kind of data exchange:
uc Problem statement business case
Trigger escalation in
the absence of a
specific event
Party responsible
Party expecting an
for initiating an
ev ent
(from
(from
ev ent
Actors)
Actors)
IEC
Figure 3 – Problem statement business case

IEC 62325-451-5:2015 © IEC 2015 – 15 –
In a normal document exchange the “party responsible for initiating an event” such as the
transmission of a document transmits this within a specified time period. The “party expecting
an event” is waiting for the reception of the document in question within the agreed timeframe.
The problem statement business process has a two-fold purpose hereafter described.
• The first is in case where the “party responsible for initiating an event” is not in a position
(IT problems, etc.) to transmit an electronic document at the expected time. This party
may issue to the other party a trouble shooting document stating when he will be in a
position to send the expected document. In such a case, this specific exchange is for
information and depending upon the rules agreed between the parties, other data
exchanges may occur such as confirmation of the time delay, etc.
• The second is in the case where the expected document does not arrive by the time
specified; the “party expecting an event” triggers the transmission of an escalation
document to inform the “party responsible for initiating an event” to initiate an escalation
procedure instead of sending the expected document.
5.2 Business context for the status request process
5.2.1 Overview of the status request process
Within the European style market, processes/markets are normally not instantaneous, thus
there is a lapse of time between the initial transmission for a business process and its
conclusion. During this time the initiator of the process is unaware of the status of his
situation. For example in the case of the scheduling process matching information shall be
received in order to conclude the transaction and a time limit is imposed on its successful
conclusion. The initiator could be able to expedite the transmission of the matching
information if he was aware that it had not yet been received.
In other cases it may be that a participating party would like to have a global overview of his
situation at a given point in time.
To facilitate to the market participant the establishment of his overall position an harmonized
requesting mechanism was developed enabling a market participant to make an electronic
request for information to his counterparties. This requesting mechanism shall also be used
as a web services interface.
The recipient may then acknowledge the request as per IEC 62325-451-1 and then transmit
the requested information providing he has the capacity to do so.
The nature of the information that is sent in reply to a request is dependent on the context in
which the request is made. It is through bilateral agreement that such a service is provided.
The agreement will also define the structure of the answering information flow.
5.2.2 Use case for the status request process
In the general context the two principal actors participate in some mainline business process,
e.g. the scheduling (IEC 62325-451-2) or the transmission capacity auctioning process
(IEC 62325-451-3). The business process is composed of a number of transactions that are
initialised, processed and concluded. In the context of the use case in Figure 4 it is assumed
that the responsible operator (e.g. system operator, transmission capacity allocator, capacity
coordinator, etc.) carries out the principal processing. However the roles may be inversed.

– 16 – IEC 62325-451-5:2015 © IEC 2015
uc Status request business case
Participate in a
mainline business
pr ocess
Market participant Responsible
oper ator
(from (from
Actors) Actors)
Request status
infor mation
IEC
Figure 4 – Status request business case
Between the initialisation where the initial submission and acknowledgement is carried out
and the conclusion where the business process is terminated, there is a processing activity.
Generally it is during this period that the initiator has little or no insight into his position in
respect to the ongoing transaction.
It is during this phase where a status request use case may be applied. This process will
enable the initiator to receive the status of his transaction prior to its terminat
...