IEC TS 61970-2:2004

Energy management system application program interface (EMS-API) - Part 2: Glossary

Provides a glossary for the volume of work produced as part of the IEC 61970 series of publications. Supplies terms and abbreviations that are either specific to the series, or that require explanation because of the way that they are used.
This publication is of core relevance for Smart Grid.

General Information

• Status: Published
• Publication Date: 27-Jul-2004
• ICS: 01 - GENERALITIES. TERMINOLOGY. STANDARDIZATION. DOCUMENTATION
• ICS: 33.200 - Telecontrol. Telemetering
• Technical Committee: TC 57 - Power systems management and associated information exchange
• Drafting Committee: WG 13 - TC 57/WG 13
• Current Stage: PPUB - Publication issued
• Start Date: 15-Sep-2004
• Completion Date: 28-Jul-2004

Standards Content (Sample)

TECHNICAL IEC
SPECIFICATION TS 61970-2
First edition
2004-07
Energy management system application
program interface (EMS-API) –
Part 2:
Glossary
Reference number
IEC/TS 61970-2:2004(E)
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.
Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:

Email: [e-mail]
Tel: [phone]
Fax: [phone]
TECHNICAL IEC
SPECIFICATION TS 61970-2
First edition
2004-07
Energy management system application
program interface (EMS-API) –
Part 2:
Glossary
” IEC 2004  Copyright - all rights reserved
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 the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: [phone] Telefax: [phone] E-mail: [e-mail] Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale
R
International Electrotechnical Commission
ɆɟɠɞɭɧɚɪɨɞɧɚɹɗɥɟɤɬɪɨɬɟɯɧɢɱɟɫɤɚɹɄɨɦɢɫɫɢɹ
For price, see current catalogue

– 2 – TS 61970-2 ” IEC:2004(E)
CONTENTS
FOREWORD.3
INTRODUCTION.5
1 Scope .6
2 Normative references .6
3 Terms and definitions .6
4 Glossary of abbreviations .11

TS 61970-2 ” IEC:2004(E) – 3 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENERGY MANAGEMENT SYSTEM APPLICATION
PROGRAM INTERFACE (EMS-API) –
Part 2: Glossary
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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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.
The main task of IEC technical committees is to prepare International Standards. In
exceptional circumstances, a technical committee may propose the publication of a technical
specification when
• the required support cannot be obtained for the publication of an International Standard,
despite repeated efforts, or
• the subject is still under technical development or where, for any other reason, there is the
future but no immediate possibility of an agreement on an International Standard.
Technical specifications are subject to review within three years of publication to decide
whether they can be transformed into International Standards.
IEC 61970-2, which is a technical specification, has been prepared by IEC Technical
Committee 57: Power systems management and associated information exchange.

– 4 – TS 61970-2 ” IEC:2004(E)
The specific standards documents for which this glossary applies are listed in IEC 61970-1 .
The text of this technical specification is based on the following documents:
Enquiry draft Report on voting
57/666/CDV 57/725/RVC
Full information on the voting for the approval of this technical specification can be found in
the report on voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
IEC 61970 consists of the following parts, under the general title Energy Management System
Application Program Interface (EMS-API):
Part 1: Guidelines and general requirements
Part 2: Glossary
Part 301: Common Information Model (CIM) Base
Part 302: Common information model (CIM) financial, energy scheduling and reservations
Part 401: Component Interface Specification (CIS) framework
Part 402: Component Interface Specification (CIS) – Common services
Part 403: Component Interface Specification (CIS) – Generic data access
Part 404: Component Interface Specification (CIS) – High speed data access
Part 405: Component Interface Specification (CIS) – Generic eventing and subscription
Part 407: Component Interface Specification (CIS) – Time series data access
Part 453: Exchange of graphics schematics definitions (common graphics exchange)
Part 501: Common Information Model (CIM) XML codification for programmable reference
and model data exchange
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result 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
• transformed into an International standard,
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this Technical Specification may be issued at a later date.
___________
Under consideration.
Under consideration.
TS 61970-2 ” IEC:2004(E) – 5 –
INTRODUCTION
This Technical specification is part of the IEC 61970 series, which defines an Application
Program Interface (API) for an Energy Management System (EMS). This standard is based
upon the work of the EPRI Control Center API (CCAPI) research project (RP-3654-1). The
principle objectives of the EPRI CCAPI project are to:
– reduce the cost and time needed to add new applications to an EMS;
– protect the investment in existing applications that are working effectively in an EMS.
The principal task of the CCAPI project is to develop a set of guidelines, or specifications, to
enable the creation of “plug-in” applications in the control center environment.
This part of the IEC 61970 series provides a glossary of terms and abbreviations that are
specific to the IEC 61970 series or may require interpretation as to how they were used in it.
___________
A plug-in application is defined to be a piece of software that may be installed on a system with minimal effort
and no modification of source code; i. e., the way software packages are installed on a desktop computer. The
CCAPI Project goal is to at least approach that ideal by reducing the often significant efforts currently required
to install third-party applications in an EMS.

– 6 – TS 61970-2 ” IEC:2004(E)
ENERGY MANAGEMENT SYSTEM APPLICATION
PROGRAM INTERFACE (EMS-API) –
Part 2: Glossary
1 Scope
This Technical specification provides a glossary for the volume of work produced as part of
the IEC 61970 series of documents. Terms and abbreviations that are either specific to the
series, or that require explanation because of the way that they are used in it, are supplied.
2 Normative references
The following referenced documents are indispensable for the application 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 61970-1, Energy Management System Application Program Interface (EMS-API) – Part 1:
Guidelines and general requirements
3 Terms and definitions
For the purposes of this Technical specification, the terms and definitions given below apply.
3.1
aggregation
special case of association
3.2
application
piece of software that comprises one or more components that perform some business
function in a given domain. The important aspect is the functionality performed and not the
packaging of the software. An example would be a word processor. It has a fairly well
understood functionality but the components that are actually installed can look very different
depending on the vendor.
3.3
application context
collection of applications working together as an organizational unit to accomplish some high-
level objective
3.4
Application Program Interface
API
set of public functions provided by an executable application component for use by other
executable application components
3.5
association
connection between classes that can be assigned a role

TS 61970-2 ” IEC:2004(E) – 7 –
3.6
cardinality from
multiplicity from the class that is being described, ‘0’ is an optional association and ‘n’ means
that an unspecified number of associations are allowed
3.7
cardinality to
multiplicity and cardinality of the class on the other side of the association
3.8
Common Information Model
CIM
abstract model that represents all of the major objects in an electric utility enterprise that are
typically contained in an Energy Management System (EMS) information model. By providing
a standard way of representing power system resources as object classes and attributes
along with their relationships, the CIM facilitates the integration of EMS applications
developed independently by different vendors, between entire EMS’s developed
independently or between an EMS and other systems concerned with different aspects of
power operations, such as generation or distribution management.
3.9
CIM context
run-time environment within which all application instances operate to achieve a common
objective
3.10
class
description of an object found in the real world that needs to be represented as part of the
overall power system model or a set of resources to which a given set of properties apply
3.11
communication profiles
particular protocols and protocol services that are to be used for information exchange
between separate server platforms in a component execution system
3.12
component
reusable software building block: a pre-built piece of encapsulated application code that can
be combined with other components and with handwritten code to rapidly produce a custom
application. In ord
...