Information technology — Home Electronic System (HES) application model — Part 3-2: GridWise interoperability context-setting framework

ISO/IEC TR 15067-3-2:2016(E) This Technical Report is based on work done by the GridWise Architecture Council. It describes a framework for identifying and discussing interoperability issues to facilitate the integration of entities that interact with electric power systems.

Technologies de l'information — Modèles d'application du système électronique domotique (HES) — Partie 3-2: Titre manque

General Information

Publication Date
Current Stage
6060 - International Standard published
Completion Date
Ref Project

Buy Standard

Technical report
ISO/IEC TR 15067-3-2:2016 - Information technology -- Home Electronic System (HES) application model
English language
38 pages
sale 15% off
sale 15% off

Standards Content (Sample)

ISO/IEC TR 15067-3-2
Edition 1.0 2016-11

Information technology – Home electronic system application model –
Part 3-2: GridWise – Interoperability context-setting framework

ISO/IEC TR 15067-3-2:2016-11(en)

---------------------- Page: 1 ----------------------
Copyright © 2016 ISO/IEC, Geneva, Switzerland

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

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20

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.

IEC Catalogue - Electropedia -
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 15 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - IEC Glossary -
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

IEC Just Published -

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre -
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service

---------------------- Page: 2 ----------------------
ISO/IEC TR 15067-3-2

Edition 1.0 2016-11





Information technology – Home electronic system application model –

Part 3-2: GridWise – Interoperability context-setting framework




ICS 35.200 ISBN 978-2-8322-3722-9

  Warning! Make sure that you obtained this publication from an authorized distributor.

---------------------- Page: 3 ----------------------
– 2 – ISO/IEC TR 15067-3-2:2016
© ISO/IEC 2016
1 Executive Summary . 6
2 Introduction . 9
2.1 Why Develop a Framework? . 11
2.2 Multiple Viewpoints . 12
2.3 Background. 13
2.4 Scope . 13
2.5 Prerequisites. 14
2.6 Framework Progression . 14
2.7 Collaboration Terminology . 15
3 System Integration Philosophy . 17
3.1 Agreement at the Interface – A Contract . 17
3.2 Boundary of Authority . 17
3.3 Decision Making in Very Large Networks . 18
3.4 The Role of Standards . 19
4 High Level Categorization . 20
4.1 Technical Aspects . 21
4.1.1 Category 1: Basic Connectivity . 21
4.1.2 Category 2: Network Interoperability . 22
4.1.3 Category 3: Syntactic Interoperability . 22
4.2 Informational Aspects . 23
4.2.1 Category 4: Semantic Understanding . 23
4.2.2 Category 5: Business Context . 23
4.3 Organizational Aspects . 24
4.3.1 Category 6: Business Procedures . 24
4.3.2 Category 7: Business Objectives . 24
4.3.3 Category 8: Economic and Regulatory Policy . 25
5 Cross-Cutting Issues . 25
5.1 Shared Meaning of Content . 26
5.2 Resource Identification . 27
5.3 Time Synchronization and Sequencing. 27
5.4 Security and Privacy . 28
5.5 Logging and Auditing . 28
5.6 Transaction and State Management . 29
5.7 System Preservation . 29
5.8 Quality of Service . 29
5.9 Discovery and Configuration . 30
5.10 System Evolution and Scalability . 30
6 Examples of Applying the Framework . 31
7 Governance . 31
8 Acknowledgements . 32
9 References . 32
Appendix A Example Scenarios . 34
A.1 Residential Demand Response . 34
A.1.1 Mrs. Meg A. Watts Moves In . 34
A.1.2 A Critical Peak Occurs . 35

---------------------- Page: 4 ----------------------
ISO/IEC TR 15067-3-2:2016 – 3 –
© ISO/IEC 2016
A.1.3 An Emergency Occurs . 36
A.1.4 Meg and the Framework . 37
A.2 Commercial Building Demand Response . 39
A.3 Congestion Management Market . 41
Bibliography . 43

Figure S.1 – A Framework Provides High-Level Perspective . 7
Figure S.2 – Interoperability Framework Categories . 8
Figure S.3 – Interoperability Framework Companion Material . 9
Figure 1 – Distance to Integrate . 10
Figure 2 – Interoperability Framework Companion Material . 14
Figure 3 – Phases for Progressing Interoperability . 15
Figure 4 – Collaboration Model Elements . 16
Figure 5 – Interoperability Layered Categories . 21
Figure 6 – Interoperability Context-Setting Framework Diagram . 26

---------------------- Page: 5 ----------------------
– 4 – ISO/IEC TR 15067-3-2:2016
© ISO/IEC 2016

Part 3-2: GridWise – Interoperability context-setting framework

1) ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology,
ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
2) The formal decisions or agreements of IEC and ISO 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 and ISO member bodies.
3) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC National Committees and ISO member bodies in that sense. While all reasonable efforts are made to
ensure that the technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO 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 and ISO member bodies undertake to
apply IEC, ISO and ISO/IEC publications transparently to the maximum extent possible in their national and
regional publications. Any divergence between any ISO, IEC or ISO/IEC publication and the corresponding
national or regional publication should be clearly indicated in the latter.
5) ISO and IEC do not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. ISO or IEC are 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 ISO or its directors, employees, servants or agents including individual
experts and members of their technical committees and IEC National Committees or ISO member bodies 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 of, use of, or reliance upon, this
ISO/IEC publication or any other IEC, ISO or ISO/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 ISO/IEC publication may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
The main task of the joint technical committee is to prepare International Standards. However,
the joint technical committee may propose the publication of a Technical Report when it has
collected data of a different kind from that which is normally published as an International
Standard, for example "state of the art".
ISO/IEC TR 15067-3-2, which is a Technical Report, has been adopted and adapted by
subcommittee 25: Interconnection of information technology equipment, of ISO/IEC joint
technical committee 1: Information technology.
This Technical Report is closely based on the document GridWise® Interoperability Context-
Setting Framework (March 2008), prepared by The GridWise Architecture. Also, the original
structure of the technical part of this document has been maintained.
 GridWise® is a registered tradename by The GridWise Architecture Council.

---------------------- Page: 6 ----------------------
ISO/IEC TR 15067-3-2:2016 – 5 –
© ISO/IEC 2016
This Technical Report has been approved by vote of the member bodies, and the voting
results may be obtained from the address given on the second title page.

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.

---------------------- Page: 7 ----------------------
– 6 – ISO/IEC TR 15067-3-2:2016
© ISO/IEC 2016

Part 3-2: GridWise – Interoperability context-setting framework

1 Executive Summary
As the deployment of automation technology advances, it touches upon many areas of our
corporate and personal lives. A trend is emerging where automation systems are growing to
the extent that integration is taking place with other systems to provide even greater
capabilities more efficiently and effectively. GridWise provides a vision for this type of
integration as it applies to the electric system.
Imagine a time in the not too distant future when homeowners can offer the management of
their electricity demand to participate in a more efficient and environmentally friendly
operation of the electric power grid. They will do this using automation technology that acts on
their behalf in response to information from other automation components of the electric
system. This technology will recognize their preferences to parameters such as comfort and
the price of energy to form responses that optimize the local need to a signal that satisfies a
higher-level need in the grid.
For example, consider a particularly hot day with air stagnation in an area with a significant
dependence on wind generation. To manage the forecasted peak electricity demand, the bulk
system operator issues a critical peak price warning. Their automation systems alert electric
service providers who distribute electricity from the wholesale electricity system to
consumers. In response, the electric service providers use their automation systems to inform
consumers of impending price increases for electricity. This information is passed to an
energy management system at the premises, which acts on the consumer’s behalf, to adjust
the electricity usage of the onsite equipment (which might include generation from such
sources as a fuel cell). The objective of such a building automation system is to honor the
agreement with the electricity service provider and reduce the consumer’s bill while keeping
the occupants as comfortable as possible. This will include actions such as moving the
thermostat on the heating, ventilation, and air-conditioning (HVAC) unit up several degrees.
The resulting load reduction becomes part of an aggregated response from the electricity
service provider to the bulk power system operator who is now in a better position to manage
total system load with available generation.
Looking across the electric system, from generating plants, to transmission substations, to the
distribution system, to factories, office parks, and buildings, automation is growing, and the
opportunities for unleashing new value propositions are exciting. How can we facilitate this
change and do so in a way that ensures the reliability of electric resources for the wellbeing of
our economy and security? The GridWise Architecture Council (GWAC) mission is to enable
interoperability among the many entities that interact with the electric power system. A good
definition of interoperability is, “The capability of two or more networks, systems, devices,
applications, or components to exchange information between them and to use the
information so exchanged.” As a step in the direction of enabling interoperability, the GWAC
proposes a context-setting framework to organize concepts and terminology so that
interoperability issues can be identified and debated, improvements to address issues
articulated, and actions prioritized and coordinated across the electric power community.
By a context-setting framework, we mean something at a high, organizational level (see
Figure S.1), some neutral ground upon which a community of stakeholders can talk about
 “EICTA Interoperability White Paper,” European Industry Association, Information Systems Communication
Technologies Consumer Electronics, 21 June 2004.

---------------------- Page: 8 ----------------------
ISO/IEC TR 15067-3-2:2016 – 7 –
© ISO/IEC 2016
issues and concerns related to integrating parts of a large, complex system. Borrowing
concepts from the Australian National E-Health Transition Authority, a framework sits at a
broad, conceptual level and provides context for more detailed technical aspects of
interoperability. In contrast, “A model (or architecture) identifies a particular problem space
and defines a technology-independent analysis of requirements. The design maps model
requirements into a particular family of solutions based upon standards and technical
approaches. Finally a solution manifests a design into a particular vendor software
technology, ensuring adherence to designs, models, and frameworks.”

Figure S.1 – A Framework Provides High-Level Perspective
The intent of the interoperability framework is to provide the context for identifying and
debating interoperability issues to advance actions that make integration within this complex
system easier. The framework recognizes that interoperability is only achieved when
agreement is reached across many layers of concern. These layers span the details of the
technology involved to link systems together, to the understanding of the information
exchanged, to the business processes and organizational objectives that are represented in
business, economic, and regulatory policy.
Besides introducing new opportunities and benefits, the application of information technology
(IT) also introduces a new set of challenges. As they contribute to all economic sectors,
traditionally separate applications and infrastructures get more and more interconnected.
Effects and decisions within each critical infrastructure influence the other infrastructures
much more than before. The framework identifies the key interoperability issue areas and can
help resolve interdependencies within the electric system and with other infrastructures. It
reflects the increasingly important role of IT in the electric system, resulting in an electricity
plus information (E+I) infrastructure. The framework also enables the representation and
exchange of ideas with other critical infrastructure domains. It supports comparing, aligning,
and harmonizing technical approaches with accompanying management procedures and
business processes.
Figure S.2 summarizes the layered interoperability categories according to technical,
informational, and organizational groups. In addition to these categories of interoperability,
the framework proposes a classification of interoperability issues that cut across the layers.
This document introduces these issue areas with the intent to explore and articulate the
detailed nature of each issue area in separate documents engaging interested experts in their
creation. The cross-cutting issues represent the areas we believe should be focused on to
start improving interoperability across the web of electricity concerns.
 National E-Health Transition Authority (NEHTA), “Towards an Interoperability Framework, v 1.8,“ August 2005.

---------------------- Page: 9 ----------------------
– 8 – ISO/IEC TR 15067-3-2:2016
© ISO/IEC 2016
Political and Economic
Objectives as Embodied in
8: Economic/Regulatory Policy
Policy and Regulation
Strategic and Tactical
Objectives Shared
7: Business Objectives
between Businesses
Alignment between
Operational Business
6: Business Procedures
Processes and Procedures
Relevant Business Knowledge
that Applies Semantics with
5: Business Context
E + I
Process Workflow
Understanding of Concepts
Contained in the Message
4: Semantic Understanding
Data Structures
Understanding of Data Structure
in Messages Exchanged
3: Syntactic Interoperability
between Systems
Exchange Messages between
Systems across a
2: Network Interoperability
Variety of Networks
Mechanism to Establish
Physical and Logical I
1: Basic Connectivity
Connectivity of Systems

Figure S.2 – Interoperability Framework Categories
The audience for this document are system architects and integrators with the ability to
participate in establishing a technical foundation to discuss interoperability, articulate issues
to achieving interoperability, and develop proposals to improve the situation. It presumes the
reader is knowledgeable of complex system integration and the technical, informational, and
organizational issues that surround this area. This technical document lays the foundation for
future, companion material to targeted purposes and audiences. Ideally, the reader will
consider the application of the concepts presented in this material to their field of interest to
help address interoperability challenges as well as to provide suggestions on improvements to
this material.
The GWAC realizes that other versions of the framework should be tailored to speak to the
interests of other audiences, such as regulators, business decision-makers, system operators,
and system suppliers. This material may consist of white papers, checklists, or other forms of
To introduce this framework, we provide some background for this work in the context of past
GWAC activity and establish some basic concepts and terminology. We then state some
important points about the system-integration philosophy that influences the way automation
components are expected to interface and operate in a collaborative manner in something as
complex as the electric power system. These philosophical tenets are important because they
emphasize the needs of the system integrator and underlie many of the statements made
about the interoperability categories and the cross-cutting issues that are described in
subsequent sections. The set of layered interoperability categories and the cross-cutting
issues is followed by some clarifying examples.
The document closes with an acknowledgement that such a framework is a living concept,
and therefore, a process needs to be put in place to govern its evolution over time both in
terms of concepts and the material used to convey these concepts. If such a framework is to
be helpful to interoperability improvements, the diverse stakeholders in the electric system
should take ownership and have access to participate in its development. This then is the first
of an evolutionary series of documents to describe an interoperability framework and
articulate interoperability issues that assists discussions with participants at all levels.
Providing venues for participation in this work is an important aspect of engaging the
electricity community.

---------------------- Page: 10 ----------------------
ISO/IEC TR 15067-3-2:2016 – 9 –
© ISO/IEC 2016
The process to specify and develop future material requires the participation of the electricity
community. Figure S.3 provides a conceptual view of companion material envisaged to follow
from the framework. These works include executive summaries for targeted audiences,
technical papers that articulate interoperability issues and proposed approaches to address
them, checklists, tools, use case scenarios that provide examples of applying the framework,
and other similar documents.
Executive Summaries
(windows for targeted
audiences onto the
Interoperability Categories Cross-cutting Issues

8: Economic/Regulatory Policy
Organizational 7: Business Objectives
6: Business Procedures
5: Business Context
4: Semantic Understanding
Technical Papers
(technical expertise)
3: Syntactic Interoperability
2: Network Interoperability
1: Basic Connectivity
checklists tools scenarios …

Figure S.3 – Interoperability Framework Companion Material

2 Introduction
The Gridwise Architecture Council (GWAC) exists to enable automation among the many
entities that interact with the electric power infrastructure. Though we do not prejudge what
this automation will be used for, once it is enabled, we presume that, given opportunity, many
possibilities will be explored, and much economic and social good will result. The GWAC
mission is merely to enable. The goal is a concept called interoperability, which incorporates
the following characteristics:
• exchange of meaningful, actionable information between two or more systems across
organizational boundaries
• a shared understanding of the exchanged information
• an agreed expectation for the response to the information exchange
• a requisite quality of service: reliability, fidelity, and security.
The result of such interaction enables a larger interconnected system capability that
transcends the local perspective of each participating subsystem.
A commonly understood objective for interoperability is the concept of “plug-and-play”. With
plug-and-play, the system integrator is able to configure an automation component into the
system simply by “plugging” it in. Behind the scenes, automated processes determine the
Shared Meaning of Content
Resource Identification
Time Synch and Sequencing
Security and Privacy
Logging and Auditing
Transaction and State Mgt
System Preservation
Discovery and Configuration
System Evolution

---------------------- Page: 11 ----------------------
– 10 – ISO/IEC TR 15067-3-2:2016
© ISO/IEC 2016
nature of the newly connected automation component and the component determines the
nature of the system so that it is properly configured and can begin to operation properly. If
we consider the level of integration involved as a length or distance, then the “distance to
integrate” for plug-and-play is small [1] .
As attractive as this concept is, achieving plug-and-play is not easy and in many, complex
situations it is not practical to specify standard interfaces to this level of

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.