SIST EN 62325-451-1:2017

SLOVENSKI STANDARD
01-september-2017
1DGRPHãþD
SIST EN 62325-451-1:2014
2NYLU]DNRPXQLNDFLMHQDWUJX]HOHNWULþQRHQHUJLMRGHO3RVORYQLSURFHV
SRWUMHYDQMDLQNRQWHNVWXDOQLPRGHO]D&,0]DHYURSVNLWUJ
Framework for energy market communications - Part 451-1: Acknowledgement business
process and contextual model for CIM European market
Kommunikation im Energiemarkt - Teil 451-1: Geschäftsprozessnachweis und
kontextbezogenes CIM-Modell für den europäischen Markt
Cadre pour les communications pour le marché de l'énergie - Partie 451-1: Processus
métier d'accusé de réception et modèle contextuel pour le marché européen CIM
Ta slovenski standard je istoveten z: EN 62325-451-1:2017
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-1

NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2017
ICS 33.200 Supersedes EN 62325-451-1:2013
English Version
Framework for energy market communications -
Part 451-1: Acknowledgement business process and contextual
model for CIM European market
(IEC 62325-451-1:2017)
Cadre pour les communications pour le marché de l'énergie - Kommunikation im Energiemarkt -
Partie 451-1: Processus métier d'accusé de réception et Teil 451-1: Geschäftsprozessnachweis und
modèle contextuel pour le marché européen CIM kontextbezogenes CIM-Modell für den europäischen Markt
(IEC 62325-451-1:2017) (IEC 62325-451-1:2017)
This European Standard was approved by CENELEC on 2017-03-06. 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, Serbia, 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
© 2017 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62325-451-1:2017 E

European foreword
The text of document 57/1789/FDIS, future edition 2 of IEC 62325-451-1, 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-1:2017.
The following dates are fixed:
(dop) 2017-12-06
• latest date by which the document has to be implemented at
national level by publication of an identical national
standard or by endorsement
(dow) 2020-03-06
• latest date by which the national standards conflicting with
the document have to be withdrawn

This document supersedes EN 62325-451-1:2013
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.
Endorsement notice
The text of the International Standard IEC 62325-451-1:2017 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-301 NOTE Harmonized as EN 62325-301.
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 CLC/TS 61970-2 -
program interface (EMS-API) - Part 2:
Glossary
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 62361-100 -  Power systems management and EN 62361-100 -
associated information exchange -
Interoperability in the long term -
Part 100: CIM profiles to XML schema
mapping
IEC 62325-451-1 ®
Edition 2.0 2017-01
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Framework for energy market communications –

Part 451-1: Acknowledgement business process and contextual model for CIM

European market
Cadre pour les communications pour le marché de l'énergie –

Partie 451-1: Processus métier d'accusé de réception et modèle contextuel

pour le marché européen CIM
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200 ISBN 978-2-8322-3862-2

– 2 – IEC 62325-451-1:2017 © IEC 2017
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 8
4 Document contextual model and message assembly model basic concepts . 10
4.1 Overview. 10
4.2 European style market package structure . 11
4.3 From the European style market profile to the document contextual model . 12
4.4 From the document contextual model to the message assembly model . 12
4.5 From the assembly model to the XML schema . 12
5 The acknowledgment business process . 12
5.1 Business process definition . 12
5.1.1 General . 12
5.1.2 Technical acknowledgment . 13
5.1.3 Application acknowledgment . 13
5.2 Business rules for the acknowledgment document . 14
5.2.1 General . 14
5.2.2 Time . 14
5.2.3 Reason . 14
6 Contextual and assembly models. 15
6.1 Acknowledgement contextual model . 15
6.1.1 Overview of the model . 15
6.1.2 IsBasedOn relationships from the European style market profile . 16
6.1.3 Detailed Acknowledgement contextual model . 17
6.2 Acknowledgement assembly model . 23
6.2.1 Overview of the model . 23
6.2.2 IsBasedOn relationships from the European style market profile . 23
6.2.3 Detailed Acknowledgement assembly model . 24
6.2.4 Primitives . 28
6.2.5 Datatypes . 28
6.2.6 Enumerations . 33
7 XML schema . 33
7.1 XML schema URN namespace rules . 33
7.2 Code list URN namespace rules . 34
7.3 URI rules for model documentation . 34
7.3.1 Datatype . 34
7.3.2 Class . 34
7.3.3 Attribute . 34
7.3.4 Association end role name . 35
7.4 Acknowledgement_MarketDocument schema . 35
7.4.1 Schema structure . 35
7.4.2 Schema description . 37
Bibliography . 41

Figure 1 – IEC 62325-450 modelling framework . 10

IEC 62325-451-1:2017 © IEC 2017 – 3 –
Figure 2 – Overview of European style market profile dependency . 11
Figure 3 – Acknowledgement process . 13
Figure 4 – Acknowledgement contextual model . 16
Figure 5 – Acknowledgement assembly model . 23
Figure 6 – Acknowledgement_MarketDocument general XML schema structure . 36
Figure 7 – Acknowledgement_MarketDocument TimeSeries XML schema structure . 37

Table 1 – Codes used at the document header level . 14
Table 2 – Codes used at the TimeSeries level when there is a Reason code of A03 at
the document header level . 15
Table 3 – Codes used at the Period level when there is a Reason code A03 at the
document header level and a code A21 at the TimeSeries level . 15
Table 4 – IsBasedOn dependency. 17
Table 5 – Attributes of Acknowledgement contextual
model::Acknowledgement_MarketDocument . 17
Table 6 – Association ends of Acknowledgement contextual
model::Acknowledgement_MarketDocument with other classes . 18
Table 7 – Attributes of Acknowledgement contextual model::MarketParticipant . 19
Table 8 – Association ends of Acknowledgement contextual model:: MarketParticipant
with other classes . 19
Table 9 – Attributes of Acknowledgement contextual model::MarketRole . 19
Table 10 – Attributes of Acknowledgement contextual model::Process . 19
Table 11 – Attributes of Acknowledgement contextual model::Reason . 20
Table 12 – Attributes of Acknowledgement contextual
model::Received_MarketDocument . 20
Table 13 – Association ends of Acknowledgement contextual
model::Received_MarketDocument with other classes . 20
Table 14 – Attributes of Acknowledgement contextual
model::Receiver_MarketParticipant . 21
Table 15 – Association ends of Acknowledgement contextual
model::Receiver_MarketParticipant with other classes . 21
Table 16 – Attributes of Acknowledgement contextual model::Time_Period . 21
Table 17 – Association ends of Acknowledgement contextual model:: Time_Period with
other classes . 22
Table 18 – Attributes of Acknowledgement contextual model::TimeSeries . 22
Table 19 – Association ends of Acknowledgement contextual model:: TimeSeries with
other classes . 22
Table 20 – IsBasedOn dependency . 24
Table 21 – Attributes of Acknowledgement assembly
model::Acknowledgement_MarketDocument . 24
Table 22 – Association ends of Acknowledgement assembly
model::Acknowledgement_MarketDocument with other classes . 26
Table 23 – Attributes of Acknowledgement assembly model::Reason . 26
Table 24 – Attributes of Acknowledgement assembly model::Time_Period . 26
Table 25 – Association ends of Acknowledgement assembly model:: Time_Period with
other classes . 27
Table 26 – Attributes of Acknowledgement assembly model::TimeSeries . 27

– 4 – IEC 62325-451-1:2017 © IEC 2017
Table 27 – Association ends of Acknowledgement assembly model:: TimeSeries with
other classes . 27
Table 28 – Attributes of ESMPDataTypes::ESMP_DateTimeInterval . 28
Table 29 – Attributes of ESMPDataTypes::ESMP_DateTime . 28
Table 30 – Restrictions of attributes for ESMPDataTypes::ESMP_DateTime . 29
Table 31 – Attributes of ESMPDataTypes::ESMPVersion_String . 29
Table 32 – Restrictions of attributes for ESMPDataTypes::ESMPVersion_String . 29
Table 33 – Attributes of ESMPDataTypes::ID_String . 30
Table 34 – Restrictions of attributes for ESMPDataTypes::ID_String . 30
Table 35 – Attributes of ESMPDataTypes::MarketRoleKind_String . 30
Table 36 – Attributes of ESMPDataTypes::MessageKind_String . 30
Table 37 – Attributes of ESMPDataTypes::PartyID_String . 31
Table 38 – Restrictions of attributes for ESMPDataTypes::PartyID_String . 31
Table 39 – Attributes of ESMPDataTypes::PayloadId_String . 31
Table 40 – Restrictions of attributes for ESMPDataTypes::PayloadId_String . 31
Table 41 – Attributes of ESMPDataTypes::ProcessKind_String . 31
Table 42 – Attributes of ESMPDataTypes::ReasonCode_String . 32
Table 43 – Attributes of ESMPDataTypes::ReasonText_String . 32
Table 44 – Restrictions of attributes for ESMPDataTypes::ReasonText_String . 32
Table 45 – Attributes of ESMPDataTypes::YMDHM_DateTime . 32
Table 46 – Restrictions of attributes for ESMPDataTypes::YMDHM_DateTime . 33

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

Part 451-1: Acknowledgement business process
and contextual model for CIM 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-1 has been prepared by IEC technical committee 57:
Power systems management and associated information exchange.
This second edition cancels and replaces the first edition published in 2013. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) Addition of an optional attribute ProcessType to the acknowledgement document to ease
routing of incoming acknowledgement document instances to the appropriate application.
b) Clarification of the activity diagram for the acknowledgement process.
c) Addition of the list of constraints on datatypes.

– 6 – IEC 62325-451-1:2017 © IEC 2017
The text of this International Standard is based on the following documents:
FDIS Report on voting
57/1789/FDIS 57/1819/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all the 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 document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document 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.
IEC 62325-451-1:2017 © IEC 2017 – 7 –
INTRODUCTION
This document is one part of the IEC 62325 series for deregulated energy market
communications.
The principal objective of the IEC 62325 series 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 allow these applications or
systems access to public data and exchange information independent of how such information
is represented internally.
The common information model (CIM), i.e. IEC 62325-301, IEC 61970-301 and IEC 61968-11,
specifies the basis for the semantics for message exchange.
This European style market profile is based on different parts of the CIM IEC standard and
specifies the content of the messages exchanged.
This document provides for the European style market profile the generic technical and
application acknowledgement document that can be used in all European style market
processes. These market processes are based on the European regulations, and on the
concepts of third party access and zonal markets.
This document was originally based upon the work of the European Transmission System
Operators (ETSO) and then on the work of the European Network of Transmission System
Operators (ENTSO-E) on electronic data interchange.

– 8 – IEC 62325-451-1:2017 © IEC 2017
FRAMEWORK FOR ENERGY MARKET COMMUNICATIONS –

Part 451-1: Acknowledgement business process
and contextual model for CIM European market

1 Scope
Based on the European style market contextual model (IEC 62325-351), this part of
IEC 62325 specifies a UML package for the acknowledgment business process and its
associated document contextual model, assembly model and XML schema for use within the
European style electricity markets.
The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been
contextualized into aggregated business information entities (ABIEs) to satisfy the
requirements of the European style market acknowledgment business process.
The contextualized ABIEs have been assembled into the acknowledgment document
contextual model.
A related assembly model and an XML schema for the exchange of acknowledgement
information between market participants is automatically generated from the assembled
document contextual model.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. 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-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 62361-100, Power systems management and associated information exchange –
Interoperability in the long term – Part 100: CIM profiles to XML schema mapping
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TS 61970-2 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp

IEC 62325-451-1:2017 © IEC 2017 – 9 –
3.1
aggregate business information entity
ABIE
re-use of an aggregate core component (ACC) in a specified business
Note 1 to entry: This note applies to the French language only.
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.
Note 2 to entry: This note applies to the French language only.
[SOURCE: ISO 15000-5:2014, 3.2]
3.3
based on
IsBasedOn
use of an artefact that has been restricted according to the requirements of a specific
business context
Note 1 to entry: This note applies to the French language only.
[SOURCE: IEC 62325-450:2013, 3.4]
3.4
business context
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.5
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.6
internal European market
IEM
market of any commodity, service, etc. within the European Community
Note 1 to entry: In particular, European Directives and Regulations define the energy IEM.
Note 2 to entry: These software systems in an electricity market may include support for capacity allocation,
energy scheduling, ancillary or other services, real-time operations and settlements.
Note 3 to entry: This note applies to the French language only.
3.7
profile
basic outline of all the information that is required to satisfy a specific environment

– 10 – IEC 62325-451-1:2017 © IEC 2017
4 Document contextual model and message assembly model basic concepts
4.1 Overview
IEC 62325-450 defines how to develop 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.
CIM
Information model
Based on
Profiling
derivation
Regional contextual Rules defined in IEC 62325-450
model
ACC
• Contextual model Based on
parent model with possible
restrictions
Based on
Document contextual • No additions possible to the
model parent model
ABIE
Implementation
derivation
Message assembly
Message conceptual
model
model
MBIE
Message
implementation
XSD
syntactic model
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 contextualization of the ACCs that can be found in the European
style market contextual model. The contextualized ACCs at this stage are termed 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.
The 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.

IEC 62325-451-1:2017 © IEC 2017 – 11 –
4.2 European style market package structure
Figure 2 describes the main package structure of the European style market profile.

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.

– 12 – IEC 62325-451-1:2017 © IEC 2017
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.
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 contextualizes them
to meet the information requirements. This contextualization step creates a set of aggregate
business information entities (ABIEs).
In a final step the information analyst assembles the ABIEs together in a specific document
contextual model package 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 finalized, 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 contextualized 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 acknowledgment business process
5.1 Business process definition
5.1.1 General
The acknowledgment business process is generic and can be used in all the electricity market
business processes at two levels:
• system level – to detect syntax errors (XML parsing errors, etc.);
• application level – to detect semantic errors (invalid data, wrong process, etc.).
If there is a problem encountered at the first level, then a technical acknowledgement may be
sent to inform the originator of the problem.
If errors are encountered at the second level or if the application can successfully process the
information, then an application acknowledgement may be sent to inform the originator of the
situation. Figure 3 provides the activity diagram of the acknowledgement process.

IEC 62325-451-1:2017 © IEC 2017 – 13 –

IEC
Figure 3 – Acknowledgement process
5.1.2 Technical acknowledgment
A technical acknowledgement occurs when an XML document is received that cannot be
correctly processed for submission to the application. Such an error could occur for example
whenever the XML parser cannot correctly parse the incoming document. Other instances
could be the incapacity to correctly identify the originator of the document in relation to the
process requested.
In such a case a technical acknowledgement can be sent to the document originator providing
the information that the XML document in question cannot be correctly processed by the
system.
5.1.3 Application acknowledgment
Within each business process of European style markets, business rules shall state whether
or not an application acknowledgment is to be sent upon reception of an electronic document.
In particular, where the originator is in an “operator” type role (system operator, market
operator, interconnection capacity allocator, etc.) and the recipient is in a “market participant”
type role, all electronic documents sent by entities in the role of an operator shall be
considered as received and correct, and the acknowledgement process is not required unless
an acknowledgment document is required by a specific process.
Otherwise, upon reception, checks are to be carried out at the application level to assess that
the received document can be correctly processed by the application. The originator is
informed that:
• its document, which is stated as valid after this verification, is ready to be processed by
the reception of an acknowledgement document accepting the document in question;

– 14 – IEC 62325-451-1:2017 © IEC 2017
• its document is rejected for processing by the reception of an acknowledgement document
rejecting the document in question with details on the level of errors.
5.2 Business rules for the acknowledgment document
5.2.1 General
All the business rules described in IEC 62325-351 are also valid for this document. Additional
rules are provided hereafter.
5.2.2 Time
For all time intervals, the start date and time is included in the scope of the interval whereas
the end date and time is excluded from the scope of the interval, i.e. [start date and time, end
date and time[.
5.2.3 Reason
5.2.3.1 General
There shall be at least one Reason class at the document header level that provides the
information to either accept or reject the document.
If there are errors at the TimeSeries level, as many Reason classes as necessary may be
used to provide the details of the error. Specifically it shall be used:
• to identify a TimeSeries which has been completely rejected;
• to identify a TimeSeries where there are selective errors at the Time_Period level.
A timeInterval that is in error shall be identified in relation to its position in the incoming
document.
If there are errors at the Time_Period level, as many Reason classes as necessary shall be
used to identify the error.
5.2.3.2 Reason code examples
Table 1, Table 2 and Table 3 provide examples of the possible combinations of the use of
reason codes. These tables do not contain the whole set of reason codes.
Table 1 – Codes used at the document header level
Code Reason
A01 Message fully accepted
A02 Message fully rejected
A03 Message contains errors at the time series level
A51 Message identification or version conflict
A52 Time series missing from new version of message
A53 Receiving party incorrect
A94 Document cannot be processed by receiving system

IEC 62325-451-1:2017 © IEC 2017 – 15 –
Table 2 – Codes used at the TimeSeries level when there is a Reason code
of A03 at the document header level
Code Reason
A20 Time series fully rejected
A21 Time series accepted with specific time interval errors
A41 Resolution inconsistency
A50 Senders time series version conflict
A54 Global position not in balance
A55 Time series identification conflict
A56 Corresponding Time series not netted
A57 Deadline limit exceeded
A59 Not compliant with local market rules

Table 3 – Codes used at the Period level when there is a Reason code A03
at the document header level and a code A21 at the TimeSeries level
Code Reason
A42 Quantity inconsistency
A46 Quantities must not be signed values
A49 Position inconsistency
A59 Not compliant with local market rules

6 Contextual and assembly models
6.1 Acknowledgement contextual model
6.1.1 Overview of the model
Figure 4 shows the model.
– 16 – IEC 62325-451-1:2017 © IEC 2017

IEC
Figure 4 – Acknowledgement contextual model
6.1.2 IsBasedOn relationships from the European style market profile
Table 4 shows the traceability dependency of the classes used in this package towards the
upper level.
IEC 62325-451-1:2017 © IEC 2017 – 17 –
Table 4 – IsBasedOn dependency
Name Complete IsBasedOn Path
Acknowledgement_MarketDocument T C57CIM::IEC62325::MarketManagement::MarketDocument
MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant
MarketRole TC57CIM::IEC62325::MarketCommon::MarketRole
Process TC57CIM::IEC62325::MarketManagement::Process
Reason TC57CIM::IEC62325::MarketManagement::Reason
Received_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument
Receiver_MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant
Time_Period TC57CIM::IEC62325::MarketManagement::Period
TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

6.1.3 Detailed Acknowledgement contextual model
6.1.3.1 Acknowledgement_MarketDocument root class
An electronic document that is used to acknowledge the reception of a document and to
provide information concerning its basic validity.
Table 5 shows all attributes of Acknowledgement_MarketDocument.
Table 5 – Attributes of Acknowledgement contextual
model::Acknowledgement_MarketDocument
Order mu lt. Attribute name / Description
Attribute type
0 [1.1] mRID The unique identification of the document being exchanged within a business
process flow.
ID_String
1 [1.1] createdDateTime The date and time of the creation of the document.
ESMP_DateTime
Table 6 shows all association ends of Acknowledgement_MarketDocument with other classes.

– 18 – IEC 62325-451-1:2017 © IEC 2017
Table 6 – Association ends of Acknowledgement contextual
model::Acknowledgement_MarketDocument with other classes
Order mu lt. Class name / Role Description
2 [1.1] MarketParticipant The identification of the party that is the originator of the
acknowledgement.
Sender_MarketParticipant
The originator
...