IEC 61968-100:2013

Application integration at electric utilities - System interfaces for distribution management - Part 100: Implementation profiles

IEC 61968-100:2013 specifies an implementation profile for the application of the other parts of IEC 61968 using common integration technologies, including JMS and web services. This International Standard also provides guidance with respect to the use of Enterprise Service Bus (ESB) technologies. This provides a means to derive interoperable implementations of IEC 61968-3 to IEC 61968-9. At the same time, this International Standard can be leveraged beyond information exchanges defined by IEC 61968, such as for the integration of market systems or general enterprise integration.

Intégration d'applications pour les services électriques - Interfaces système pour la gestion de distribution - Partie 100: Profils de mise en oeuvre

La CEI 61968-100:2013 spécifie un profil de mise en oeuvre pour l'application des autres parties de la CEI 61968 avec des technologies d'intégration communes, dont JMS et les services Web. La présente Norme internationale fournit également des lignes directrices pour l'utilisation des technologies Enterprise Service Bus (ESB). Cela fournit un moyen de dériver les mises en oeuvre interopérables de la CEI 61968-3 à la CEI 61968-9. Dans le même temps, la présente Norme internationale peut être utilisée au-delà des échanges d'informations définis par la CEI 61968, par exemple pour l'intégration des systèmes du marché ou l'intégration générale d'entreprise.

General Information

• Status: Published
• Publication Date: 25-Jul-2013
• ICS: 33.180.20 - Fibre optic interconnecting devices
• ICS: 33.200 - Telecontrol. Telemetering
• Technical Committee: TC 57 - Power systems management and associated information exchange
• Drafting Committee: WG 14 - TC 57/WG 14
• Current Stage: DELPUB - Deleted Publication
• Start Date: 16-Feb-2022
• Completion Date: 29-Jan-2021

Relations

• Revised: IEC 61968-100:2022 - Application integration at electric utilities - System interfaces for distribution management - Part 100: IEC implementation profiles for application integration
• Effective Date: 05-Sep-2023

Overview

IEC 61968-100:2013 is an essential International Standard developed by the International Electrotechnical Commission (IEC) focusing on application integration at electric utilities. Specifically, it addresses system interfaces for distribution management by defining implementation profiles. This part of the IEC 61968 series specifies how to apply integration technologies such as Java Messaging Service (JMS) and web services to enable seamless interoperability between distribution management systems and other utility applications.

This standard also offers guidance for using Enterprise Service Bus (ESB) technologies, which facilitate complex messaging and integration patterns in utility IT environments. By implementing IEC 61968-100, utilities can realize interoperable exchanges based on IEC 61968 parts 3 through 9 and extend integration beyond distribution management to areas like market systems and general enterprise applications.

Key Topics

• Common Integration Technologies: Includes detailed exploration of JMS, SOAP, REST, Web Services, WSDL, XML Schema, and ESB frameworks.
• Use Cases and Messaging Patterns: Covers synchronous request/reply, asynchronous messaging, event-driven architectures, transactions, callbacks, and complex orchestration.
• Message Organization: Defines common message envelopes, verbs, nouns, payload structures, and strong typing to ensure consistent and unambiguous data exchange.
• Interface Specifications: Detailed design of web service and JMS interfaces supporting standard implementation and extension.
• Security and Version Control: Addresses security best practices for interface implementations and versioning to maintain compatibility over time.
• Enterprise Service Bus (ESB) Guidance: Provides insights into ESB messaging patterns, adapters, and bus perspectives to enhance flexible, scalable integration solutions.

Applications

IEC 61968-100:2013 is particularly useful for electric utility companies aiming to adopt standardized, interoperable integration solutions between:

• Distribution Management Systems (DMS) and enterprise applications.
• Market Systems Integration for trading, settlements, and demand response.
• General Utility Enterprise Systems such as billing, asset management, and customer information systems.
• IT Infrastructure Modernization using SOA (Service-Oriented Architecture) and ESB platforms.
• Event-Driven Data Exchange enabling near real-time monitoring and control.

By following this standard, utilities can reduce integration complexity, enable vendor neutrality, and improve the flexibility and maintainability of their IT landscapes. It supports both automated data flows and human-in-the-loop operations, ensuring robust and scalable system interfaces.

Related Standards

IEC 61968-100:2013 forms part of the broader IEC 61968 series which addresses system interfaces for distribution management:

• IEC 61968-3 to IEC 61968-9: Define detailed data models and messages for specific utility processes, including network operations, asset management, and maintenance.
• IEC 61970 series: Focused on energy management system application program interfaces (EMS-API) complementing distribution management.
• IEC 62325: Standardizes market communications for deregulated electricity markets, which can be integrated with IEC 61968 protocols.
• IEC 61850: Covers communication networks and systems for power utility automation, often interfaced with IEC 61968 implementations.
• Industry standards for JMS, SOAP, REST, and SOA that complement IEC 61968-100’s integration profiles.

---

By implementing IEC 61968-100:2013, electric utilities can achieve efficient and standardized system integration that supports complex workflows, enhances interoperability, and promotes the adoption of modern IT architectures in the power distribution domain. This ensures reliable, scalable, and future-proof electric utility IT infrastructures.

Standards Content (Sample)

IEC 61968-100 ®
Edition 1.0 2013-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Application integration at electric utilities – System interfaces for distribution
management –
Part 100: Implementation profiles

Intégration d'applications pour les services électriques – Interfaces système
pour la gestion de distribution –
Partie 100: Profils de mise en oeuvre

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni
utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les
microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: [e-mail].

A propos de la CEI
La Commission Electrotechnique Internationale (CEI) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.

Liens utiles:
Recherche de publications CEI - www.iec.ch/searchpub Electropedia - www.electropedia.org
La recherche avancée vous permet de trouver des Le premier dictionnaire en ligne au monde de termes
publications CEI en utilisant différents critères (numéro de électroniques et électriques. Il contient plus de 30 000
référence, texte, comité d’études,…). termes et définitions en anglais et en français, ainsi que
Elle donne aussi des informations sur les projets et les les termes équivalents dans les langues additionnelles.
publications remplacées ou retirées. Egalement appelé Vocabulaire Electrotechnique
International (VEI) en ligne.
Just Published CEI - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications de la CEI.
Just Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur
Disponible en ligne et aussi une fois par mois par email. cette publication ou si vous avez des questions
contactez-nous: [e-mail].
IEC 61968-100 ®
Edition 1.0 2013-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Application integration at electric utilities – System interfaces for distribution

management –
Part 100: Implementation profiles

Intégration d'applications pour les services électriques – Interfaces système

pour la gestion de distribution –

Partie 100: Profils de mise en oeuvre

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XE
ICS 33.200 ISBN 978-2-8322-1007-9

– 2 – 61968-100 © IEC:2013
CONTENTS
FOREWORD . 6
INTRODUCTION . 8
1 Scope . 9
2 Normative References . 10
3 Terms, definitions and abbreviations . 10
3.1 Terms and definitions . 10
3.2 Abbreviations . 10
3.3 Terminology for common integration technologies . 11
3.3.1 General . 11
3.3.2 Enterprise Service Bus (ESB) . 12
3.3.3 Java Messaging Service (JMS) . 12
3.3.4 Service-Oriented Architecture (SOA) . 12
3.3.5 Event-Driven Architecture (EDA) . 12
3.3.6 Simple Object Access Protocol (SOAP) . 12
3.3.7 Web Services (WS) . 13
3.3.8 Web Services Definition Language (WSDL) . 13
3.3.9 XML Schema (XSD) . 13
3.3.10 Representational State Transfer (REST) . 14
3.3.11 Queue . 14
3.3.12 Topic . 14
3.3.13 Message Destination . 14
3.3.14 Request . 14
3.3.15 Response . 14
3.3.16 Query . 15
3.3.17 Transaction . 15
3.3.18 Event . 15
4 Use Cases . 15
4.1 General . 15
4.2 Simple request/reply . 16
4.3 Request/reply using an ESB . 16
4.4 Events . 17
4.5 Transactions . 18
4.6 Callback . 19
4.7 Adapters. 20
4.8 Complex messaging . 21
4.9 Orchestration . 22
4.10 Application-level use cases . 22
5 Integration Patterns . 23
5.1 General . 23
5.2 Client and server perspectives . 23
5.2.1 General . 23
5.2.2 Basic web service pattern . 24
5.2.3 Basic JMS request/reply pattern . 24
5.2.4 Event listeners . 26
5.2.5 Asynchronous request/reply pattern . 27
5.3 Bus perspective . 27

61968-100 © IEC:2013 – 3 –
5.3.1 General . 27
5.3.2 ESB messaging pattern using JMS . 28
5.3.3 ESB messaging patterns using web service request . 29
5.3.4 ESB request handling to web service . 29
5.3.5 ESB request handling via adapter . 30
5.3.6 Custom integration patterns . 31
6 Message organization . 32
6.1 General . 32
6.2 IEC 61968 messages . 32
6.2.1 General . 32
6.2.2 Verbs . 33
6.2.3 Nouns . 34
6.2.4 Payloads . 35
6.3 Common message envelope . 36
6.3.1 General . 36
6.3.2 Message header structure . 37
6.3.3 Request message structures . 40
6.3.4 Response Message Structures . 43
6.3.5 Event message structures . 48
6.3.6 Fault message structures . 49
6.4 Payload structures. 50
6.5 Strongly-typed payloads . 53
6.6 SOAP message envelope . 54
6.7 Request processing . 55
6.8 Event processing . 56
6.9 Message correlation . 57
6.10 Complex transaction processing using OperationSet . 57
6.10.1 General . 57
6.10.2 OperationSet Element . 59
6.10.3 Patterns . 61
6.10.4 OperationSet example . 63
6.11 Representation of time . 65
6.12 Other conventions and best practices . 65
6.13 Technical interoperability . 65
6.14 Service level agreements . 66
6.15 Auditing, monitoring and management . 66
7 Payload specifications . 66
8 Interface specifications . 70
8.1 General . 70
8.2 Application-level specifications . 70
8.3 Web service interfaces . 72
8.3.1 General . 72
8.3.2 WSDL Structure . 72
8.3.3 Document style SOAP binding . 73
8.3.4 Strongly-typed web services . 74
8.4 JMS . 76
8.4.1 General . 76
8.4.2 Topic and queue naming . 77
8.4.3 JMS message fields . 78

– 4 – 61968-100 © IEC:2013
9 Security . 78
10 Version control . 79
Annex A (normative) XML schema for common message envelope . 81
Annex B (normative) Verbs . 91
Annex C (normative) Procedure for strongly typed WSDL generation . 93
Annex D (normative) Generic WSDL . 106
Annex E (informative) AMQP . 108
Annex F (informative) Payload Compression Example . 109
Annex G (informative) XMPP . 111
Bibliography . 112

Figure 1 – Overview of Scope . 9
Figure 2 – Simple Request/Reply . 16
Figure 3 – Request/reply using intermediaries . 17
Figure 4 – Events. 18
Figure 5 – Point-to-Point (One Way) Pattern . 19
Figure 6 – Transaction Example. 19
Figure 7 – Callbacks . 20
Figure 8 – Use of Adapters . 21
Figure 9 – Complex messaging . 22
Figure 10 – Application-level use case example . 23
Figure 11 – Basic request/reply using web services . 24
Figure 12 – Basic request/reply using JMS . 25
Figure 13 – Event listeners using JMS . 26
Figure 14 – Asynchronous request/reply pattern . 27
Figure 15 – ESB content-based routing . 28
Figure 16 – ESB with smart proxy and content-based routing. 29
Figure 17 – ESB with proxies, routers and adapters . 30
Figure 18 – ESB Integration to non-compliant resources . 31
Figure 19 – Messaging between clients, servers and an ESB . 33
Figure 20 – Example payload schema . 35
Figure 21 – Common message envelope . 37
Figure 22 – Common message header structure . 39
Figure 23 – Request message structure . 41
Figure 24 – XML for example RequestMessage . 42
Figure 25 – Example 'Get' profile . 43
Figure 26 – ResponseMessage structure . 44
Figure 27 – Reply message states . 45
Figure 28 – Error structure . 46
Figure 29 – XML for example ResponseMessage . 47
Figure 30 – XML example of payload compression . 47
Figure 31 – XML example for error ResponseMessage . 48
Figure 32 – EventMessage structure . 48

61968-100 © IEC:2013 – 5 –
Figure 33 – XML example for EventMessage . 49
Figure 34 – Fault message structure . 50
Figure 35 – Message payload container – Generic . 51
Figure 36 – Message payload container – Type specific example . 54
Figure 37 – SOAP bindings . 54
Figure 38 – SOAP envelope example for strong typing . 55
Figure 39 – Message OperationSet Element . 58
Figure 40 – OperationSet details . 60
Figure 41 – Transactional Request/Response (non-OperationSet) . 61
Figure 42 – Published events (non-OperationSet) . 62
Figure 43 – Transactional Request/Response (OperationSet) . 62
Figure 44 – Published event (OperationSet) . 63
Figure 45 – Information Models, Profiles and Messages . 67
Figure 46 – Contextual Profile Design in CIMTool . 67
Figure 47 – Example message payload schema . 68
Figure 48 – Example payload XML schema . 69
Figure 49 – Example message XML . 70
Figure 50 – Example complex business process . 72
Figure 51 – WSDL structure . 73
Figure 52 – Web service usage example . 76
Figure 53 – Example Organization of Topics and Queues . 77
Figure C.1 – Process for WSDL Generation . 93
Figure C.2 –Example sequence diagram . 94
Figure C.3 – WSDL folder structure . 94
Figure C.4 – WSDL type definitions . 95
Figure D.1 – Generic WSDL structure . 106

Table 1 – Verbs and their Usage . 34
Table 2 – Payload usages . 53
Table B.1 – Normative definitions of verbs . 91

– 6 – 61968-100 © IEC:2013
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
APPLICATION INTEGRATION AT ELECTRIC UTILITIES –
SYSTEM INTERFACES FOR DISTRIBUTION MANAGEMENT –

Part 100: Implementation profiles

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 61968-100 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/1358/FDIS 57/1382/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.
A list of all parts in the IEC 61968 series, published under the general title Application
integration at electric utilities – System interfaces for distribution management, can be found
on the IEC website.
61968-100 © IEC:2013 – 7 –
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site 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 – 61968-100 © IEC:2013
INTRODUCTION
This part of IEC 61968 defines a set of implementation profiles for IEC 61968 using
technologies commonly used for enterprise integration. More specifically, this document
describes how message payloads defined by parts 3-9 of IEC 61968 are conveyed using web
services and the Java Messaging System. Guidance is also provided with respect to the use
of Enterprise service Bus (ESB) technologies. The goal is to provide details that would be
sufficient to enable implementations of IEC 61968 to be interoperable. In addition, this
document is intended to describe integration patterns and methodologies that can be
leveraged using current and future integration technologies.
The IEC 61968 series of standards is intended to facilitate inter-application integration as
opposed to intra-application integration. Intra-application integration is aimed at programs in
the same application system, usually communicating with each other using middleware that is
embedded in their underlying runtime environment, and tends to be optimised for close, real-
time, synchronous connections and interactive request/reply or conversation communication
models. IEC 61968, by contrast, is intended to support the inter-application integration of a
utility enterprise that needs to connect disparate applications that are already built or new
(legacy or purchased applications), each supported by dissimilar runtime environments.
Therefore, these interface standards are relevant to loosely coupled applications with more
heterogeneity in languages, operating systems, protocols and management tools. This series
of standards, which are intended to be implemented with middleware services that exchange
messages among applications, will complement, not replace utility data warehouses,
database gateways, and operational stores.
This standard is based upon the EPRI Technical Report 1018795 and other contributed works.
The IEC 61968 series, taken as a whole, defines interfaces for the major elements of an
interface architecture for distribution systems within a utility enterprise. Part 1: Interface
Architecture and General Recommendations, identifies and establishes requirements for
standard interfaces based on an Interface Reference Model (IRM). Parts 3 through 9 of
IEC 61968 define interfaces relevant to each of the major business functions described by the
Interface Reference Model.
As described in IEC 61968, there are a variety of distributed application components used by
the utility to manage electrical distribution networks. These capabilities include monitoring and
control of equipment for power delivery, management processes to ensure system reliability,
voltage management, demand-side management, outage management, work management,
automated mapping, meter reading, meter control and facilities management. This set of
standards is limited to the definition of interfaces and is implementation independent. It
provides for interoperability among different computer systems, platforms, and programming
languages. Methods and technologies used to implement functionality conforming to these
interfaces are considered outside of the scope of these standards; only the interface itself is
specified in these standards.
61968-100 © IEC:2013 – 9 –
APPLICATION INTEGRATION AT ELECTRIC UTILITIES –
SYSTEM INTERFACES FOR DISTRIBUTION MANAGEMENT –

Part 100: Implementation profiles

1 Scope
This part of IEC 61968 specifies an implementation profile for the application of the other
parts of IEC 61968 using common integration technologies, including JMS and web services.
This International Standard also provides guidance with respect to the use of Enterprise
Service Bus (ESB) technologies. This provides a means to derive interoperable
implementations of IEC 61968-3 to IEC 61968-9. At the same time, this International Standard
can be leveraged beyond information exchanges defined by IEC 61968, such as for the
integration of market systems or general enterprise integration.
Figure 1 attempts to provide an overview of scope, where IEC 61968 compliant messages are
conveyed using web services or JMS. Through the use of an ESB integration layer, the
initiator of an information exchange could use web services, where the receiver could use
JMS, and vice versa. The integration layer also provides support for one to many information
exchanges using publish/subscribe integration patterns and key functionality such as delivery
guarantees.
WS - Direct Interaction w/o Integration Layer
Web Service Web Service
Client Service
WS WS
Client or Server
Client or Server
ESB
??? ???
using another
using another
integration
Integration
integration
technology
technology
Layer
JMS JMS
Application Application
using JMS using JMS
JMS – Direct integration using a JMS server

IEC  1769/13
Figure 1 – Overview of Scope
The scope of this document specifically includes the following:
• integration patterns that support IEC 61968 information exchanges
• design of interfaces for use of strongly typed web services
• design of interfaces for use of generically typed web services
• design of interfaces using JMS

– 10 – 61968-100 © IEC:2013
• definition of standard design artefacts and related templates
• recognition that technologies other than JMS and web services may be used for
integration leveraging this standard (with some specific examples and associated
recommendations described in appendices)
This profile can also be applied to integration problems outside the scope of IEC 61968.
It is important to note that other implementation profiles can potentially be defined for
IEC 61968, and that this is not intended to be the only possible implementation profile. In
addition, this profile can be adapted to meet specific needs of specific integration projects.
It is also not within the scope of this document to prescribe those implementation details as
required for security.
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 60050-300, International Electrotechnical Vocabulary – Electrical and electronic
measurements and measuring instruments – Part 311: General terms relating to
measurements – Part 312: General terms relating to electrical measurements – Part 313:
Types of electrical measuring instruments – Part 314: Specific terms according to the type of
instrument
IEC 61968-1, Application integration at electric utilities – System interfaces for distribution
management – Part 1: Interface architecture and general recommendations
IEC/TS 61968-2, Application integration at electric utilities – System interfaces for distribution
management – Part 2: Glossary
IEC 61968-11, Application integration at electric utilities – System interfaces for distribution
management – Part 11: Common information model (CIM) extensions for distribution
IEC 61970-301, Energy management system application program interface (EMS-API) –
Part 301: Common information model (CIM) base
IEC 61970-552, Energy management system application program interface (EMS-API) –
Part 552: CIM XML Model Exchange Format
ISO 8601, Data elements and interchange formats – Information interchange –
Representation of dates and times
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this specification, the terms and definitions given in IEC 60050-300,
IEC/TS 61968-2, IEC 62051, IEC 62055-31 apply.
3.2 Abbreviations
The following terms and abbreviations are used within this document:

61968-100 © IEC:2013 – 11 –
API Application Programming Interface
AMQP Advanced Message Queue Protocol
CIM Common Information Model
CME Common Message Envelope
CRUD Create, Read, Update, Delete
EDA Event Driven Architecture
ESB Enterprise Service Bus
IEC International Electrotechnical Commission
IETF RFC Internet Engineering Task Force Request For Comments
ISO International Standards organization
JEE Java Enterprise Edition
JMS Java Message Service
JSR Java Specification Request
mRID CIM master resource identifier
OASIS Organization for the Advancement of Structured Information Standards
RDF Resource Description Framework
REST REpresentational State Transfer
RFC Request for Comments
SOA Service Oriented Architecture
SOAP Simple Object Access Protocol
SSL Secured Socket Layer
TLS Transport Layer Security
UML Unified Modelling Language
URL Uniform Resource Locators
UUID Universal Unique Identifier
W3C World-Wide Web Consortium
WS Web Services
WS-* Web Services standards
WS-I Web Services Interoperability
WSDL Web Services Definition Language
XML eXtensible Markup Language
XSD XML Schema
XSL XML Stylesheet Language
3.3 Terminology for common integration technologies
3.3.1 General
Where there is a difference between the definitions in this standard and those contained in
other referenced IEC standards, then those defined in IEC/TS 61968-2 shall take precedence
over the others listed, and those defined in this document shall take precedence over those
defined in IEC/TS 61968-2.
– 12 – 61968-100 © IEC:2013
3.3.2 Enterprise Service Bus (ESB)
An Enterprise Service Bus (ESB) refers to a software architecture construct that is used as an
integration layer. This construct is typically implemented by technologies found in a category
of middleware infrastructure products, usually based on recognized standards, which provide
foundational services for more complex architectures via an event-driven and standards-
based messaging engine (the bus).
An ESB generally provides an abstraction layer on top of an implementation of an enterprise
messaging system, which allows integration architects to exploit the value of messaging
without writing code. Contrary to the more classical enterprise application integration (EAI)
approach of a monolithic stack in a hub and spoke architecture, the foundation of an
enterprise service bus is built of base functions broken up into their constituent parts, with
distributed deployment where needed, working in harmony as necessary.
An ESB does not implement a service-oriented architecture (SOA) but provides the features
with which one may be implemented.
3.3.3 Java Messaging Service (JMS)
The Java Message Service (JMS) API is a Java Message Oriented Middleware API for
sending messages between two or more clients. JMS supports request/reply,
publish/subscribe and point to point messaging patterns. JMS is a part of the Java Platform,
Enterprise Edition, and is defined by a specification developed under the Java Community
Process as JSR 914.It is important to note that some ESB product vendors provide language
bindings for JMS using C, C++ and/or C#, making the term JMS a misnomer. Where the wire
protocol is different between different JMS implementations it is often trivial to bridge between
different JMS implementations.
3.3.4 Service-Oriented Architecture (SOA)
Service Oriented Architecture (SOA) is a computer systems architectural style for creating
and using business processes, packaged as services, throughout their lifecycle. SOA also
defines and provisions the IT infrastructure to allow different applications to exchange data
and participate in business processes. These functions are loosely coupled with the operating
systems and programming languages underlying the applications. SOA separates functions
into distinct units (services), which can be distributed over a network and can be combined
and reused to create business applications. These services communicate with each other by
passing data from one service to another, or by coordinating an activity between two or more
services. SOA concepts are often seen as built upon and evolving from older concepts of
distributed computing and modular programming.
3.3.5 Event-Driven Architecture (EDA)
Event-Driven Architecture (EDA) is a software architecture pattern that promotes the
production, detection and consumption of events. An event is any change of state of potential
interest. Within an EDA, events are transmitted between loosely coupled software
components and services, typically using publish/subscribe messaging patterns. EDA is
complementary to SOA, to the extent that SOA 2.0 is also known as ‘event-driven’ SOA. EDA
is fundamental to a variety of business intelligence patterns, including complex event
processing patterns.
3.3.6 Simple Object Access Protocol (SOAP)
The Simple Object Access Protocol (SOAP) is a standard that defines the formatting of XML
messages. SOAP serves as a foundation layer of the web services protocol stack. SOAP is
also commonly used within JMS. Common transports for SOAP include HTTP, HTTPS and
proprietary JMS transports. SOAP is also now sometimes referred to as ‘Service-Oriented
Architecture Protocol’. SOAP is a W3C Recommendation.

61968-100 © IEC:2013 – 13 –
Two versions that are in common use include SOAP 1.1 and SOAP 1.2. New integrations or
interfaces should use SOAP 1.2 when applicable.
3.3.7 Web Services (WS)
A Web Service is defined by the W3C as ‘a software system designed to support
interoperable Machine to Machine interaction over a network.’ Web services are frequently
just Web APIs that can be accessed over a network, such as the Internet, and executed on a
remote system hosting the requested services.
The W3C Web service definition encompasses many d
...