Communication networks and systems for power utility automation - Part 90-10: Models for scheduling

IEC TR 61850-90-10:2017(E) describes scheduling for devices using IEC 61850.

General Information

Publication Date
Current Stage
PPUB - Publication issued
Start Date
Completion Date
Ref Project

Buy Standard

Technical report
IEC TR 61850-90-10:2017 - Communication networks and systems for power utility automation - Part 90-10: Models for scheduling
English language
42 pages
sale 15% off
sale 15% off

Standards Content (Sample)

IEC TR 61850-90-10

Edition 1.0 2017-10


Communication networks and systems for power utility automation –
Part 90-10: Models for scheduling
IEC TR 61850-90-10:2017-10(en)

---------------------- Page: 1 ----------------------
Copyright © 2017 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 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 16 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 ----------------------
IEC TR 61850-90-10


Edition 1.0 2017-10





Communication networks and systems for power utility automation –

Part 90-10: Models for scheduling




ICS 33.200 ISBN 978-2-8322-4917-8

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

® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 3 ----------------------
– 2 – IEC TR 61850-90-10:2017 © IEC 2017

1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviated terms . 8
3.1 Terms and definitions . 8
3.2 Abbreviated terms . 8
4 Requirements for schedules . 8
4.1 Schedules for establishing time-based behaviour . 8
4.2 Relation between schedules and directly set values and parameters of the
DER system . 9
5 Principles for modelling schedules . 9
5.1 Schedule controllers and their schedules . 9
5.2 Scheduling and direct control / setting . 10
5.2.1 General . 10
5.2.2 Case when the scheduled entity is of type "controllable data object" . 10
5.2.3 Case when the scheduled entity is of type "setting" . 10
5.3 Schedule behaviour . 11
5.4 Schedule structure . 13
5.5 Managing schedules . 14
5.5.1 Overview . 14
5.5.2 The state machine of the schedule . 14
5.5.3 The role of the schedule controller . 17
5.5.4 Relations between schedule controller, schedule and scheduled entity . 18
5.6 Configuration of schedules . 19
6 IEC 61850 LNs and CDCs . 19
6.1 CDCs of supported scheduled entities . 19
6.2 Package CommonDataClasses_90_10 . 20
6.2.1 General . 20
6.2.2 Package CDCStatusInfo . 21
6.3 Logical node classes . 23
6.3.1 General . 23
6.3.2 Package LNGroupF . 24
6.4 Enumerated data attribute types . 28
6.4.1 General . 28
6.4.2 Schedule states (ScheduleStateKind enumeration) . 28
6.4.3 Schedule states (ScheduleEnablingErrorKind enumeration) . 28
6.5 SCL enumerations (from DOEnums_90_10) . 29
6.6 Schedule implementation examples . 29
Annex A (informative) Impact of Mode (Mod) on the schedule status and on the
controllable entity . 30
Annex B (informative) Conditions for element presence . 31
Annex C (informative) Abstract classes used as a basis for new LNs/CDCs . 33
C.1 General . 33
C.2 <> Common attributes for primitive CDC (BasePrimitiveCDC) . 33
C.3 <> LN: Domain  Name: DomainLN . 33
Annex D (informative) Time setting related CDC and attributes . 35

---------------------- Page: 4 ----------------------
IEC TR 61850-90-10:2017 © IEC 2017 – 3 –
D.1 General . 35
D.2 Calendar time definition (CalendarTime) . 35
D.3 Time setting CDC (TSG) . 36
D.3.1 General . 36
D.3.2 <> Time setting (TSG) . 37
D.3.3 Time setting (FC=SP) (TSG_SP) . 37
D.3.4 Time setting (FC=SG) (TSG_SG) . 37
D.3.5 Time setting (FC=SE) (TSG_SE) . 38
D.3.6 Month (MonthKind enumeration) . 38
D.4 Occurrence (OccurrenceKind enumeration) . 39
D.5 Period (PeriodKind enumeration) . 39
D.6 Week day (WeekdayKind enumeration) . 40
Annex E (informative) Scheduling example . 41

Figure 1 – Scheduling principle . 10
Figure 2 – State diagram for schedule . 15
Figure 3 – Flow chart for transition out of running state . 16
Figure 4 – Handling priorities of schedules to determine the Active one . 18
Figure 5 – Relation between schedule controller, schedules and entity controlled . 19
Figure 6 – Class diagram CDCStatusInfo::CDCStatusInfo90_10 . 21
Figure 7 – Class diagram LogicalNodes_90_10::LogicalNodes_90_10 . 23
Figure 8 – Class diagram LNGroupF::LNGroupF . 24
Figure 9 – Class diagram DOEnums_90_10::DOEnums_90_10 . 28
Figure D.1 – Interpretation of calendar time settings . 35
Figure D.2 – Class diagram TSG::TSG . 36
Figure E.1 – LN instances and relationships involved in the implementation of the
schedule example . 41
Figure E.2 – Timelines associated to the example . 42

Table 1 – Normative abbreviations for data object names . 8
Table 2 – Expected behaviour of a schedule . 13
Table 3 – Structure of a schedule . 14
Table 4 – Attributes of TCS . 22
Table 5 – Attributes of ORS . 22
Table 6 – Data objects of FSCC . 25
Table 7 – Data objects of FSCH . 26
Table 8 – Literals of ScheduleStateKind. 28
Table 9 – Literals of ScheduleEnablingErrorKind . 28
Table B.1 – Conditions for presence of elements within a context . 31
Table C.1 – Attributes of BasePrimitiveCDC . 33
Table C.2 – Data objects of DomainLN . 34
Table D.1 – Attributes of CalendarTime . 36
Table D.2 – Attributes of TSG . 37
Table D.3 – Attributes of TSG_SP . 37
Table D.4 – Attributes of TSG_SG . 38

---------------------- Page: 5 ----------------------
– 4 – IEC TR 61850-90-10:2017 © IEC 2017
Table D.5 – Attributes of TSG_SE . 38
Table D.6 – Literals of MonthKind . 39
Table D.7 – Literals of OccurrenceKind . 39
Table D.8 – Literals of PeriodKind . 40
Table D.9 – Literals of WeekdayKind . 40

---------------------- Page: 6 ----------------------
IEC TR 61850-90-10:2017 © IEC 2017 – 5 –


Part 90-10: Models for scheduling

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
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. However, a
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".
IEC TR 61850-90-10, which is a technical report, has been prepared by IEC technical
committee 57: Power systems management and associated information exchange.

---------------------- Page: 7 ----------------------
– 6 – IEC TR 61850-90-10:2017 © IEC 2017
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
57/1762/DTR 57/1902/RVDTR

Full information on the voting for the approval of this technical report 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 parts in the IEC 61850 series, published under the general title Communication
networks and systems for power utility automation, 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 "" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.

A bilingual version of this publication may be issued at a later date.

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: 8 ----------------------
IEC TR 61850-90-10:2017 © IEC 2017 – 7 –

Part 90-10: Models for scheduling

1 Scope
This part of IEC 61850, which is a Technical Report, describes scheduling for devices using
IEC 61850.
The parameters, which identify this new namespace, are:
• Namespace Version: 2017
• Namespace Revision: A
• UML model file which reflects this namespace edition: wg10uml02v17-wg18uml02v11b-
wg17uml02v18-jwg25uml02v04c.eap, UML model version WG17UML02v18
• Namespace release date: 2017-06-12
• Namespace name: "(Tr)IEC61850-90-10:2017A"
The namespace "(Tr)IEC61850-90-10:2017A" is considered as "transitional" since the models
are expected to be included in the next editions of IEC 61850-7-4xx and IEC 61850-7-3.
Potential extensions/modifications may happen if/when the models are moved to International
Standard status. Only the new data objects and CDCs that are not said inherited from existing
LNs will be tagged with this namespace name. The others should still refer to the namespace
where they are primarily defined.
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 61850-2, Communication networks and systems in substations – Part 2: Glossary
IEC 61850-7-1:2011, Communication networks and systems for power utility automation –
Part 7-1: Basic communication structure – Principles and models
IEC 61850-7-2:2010, Communication networks and systems for power utility automation –
Part 7-2: Basic information and communication structure – Abstract communication service
interface (ACSI)
IEC 61850-7-3:2010, Communication networks and systems for power utility automation –
Part 7-3: Basic communication structure – Common data classes
IEC 61850-7-4:2010, Communication networks and systems for power utility automation –
Part 7-4: Basic communication structure – Compatible logical node classes and data object

---------------------- Page: 9 ----------------------
– 8 – IEC TR 61850-90-10:2017 © IEC 2017
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TS 61850-2
IEC 61850-7-2 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
• IEC Electropedia: available at
• ISO Online browsing platform: available at
3.1.1 scheduled entity
data object of one of the following common data classes APC, ASG, INS, ING SPC, SPG,
ENC or ENG where the control output or the value of the setting may be determined by the
scheduling system
3.1.2 scheduling system
collection containing a schedule controller and the schedules to which the schedule controller
Note 1 to entry: The scheduling system is associated to a scheduled entity (by reference in the schedule
controller) and determines the behaviour of the scheduled entity.
3.2 Abbreviated terms
Clause 4 of IEC 61850-7-4:2010 defines abbreviated terms for building concatenated data
For the purposes of this document, some new abbreviations have been introduced as
presented in this table.
Table 1 shows normative terms that are combined to create data object names.
Table 1 – Normative abbreviations for data object names
Term Description
Dsa Disable, disabled
Entr Entry, entries
Prio Priority
Req Requested
Reuse Reuse
Schd Schedule

NOTE Abbreviated terms used for the identification of the common data classes and as names of the attributes
are specified in the relevant clauses of this document and are not repeated here.
4 Requirements for schedules
4.1 Schedules for establishing time-based behaviour
Schedules establish which behaviour (for example, tariff 1 or 2, mode 1 or 3) is applied during
specified time periods. A schedule consists of a series of entries. Entries of a schedule
represent the value of a setpoint, the activation value of a particular mode or the value of a
parameter for a mode. All the entries of a single schedule refer to a same data object which is

---------------------- Page: 10 ----------------------
IEC TR 61850-90-10:2017 © IEC 2017 – 9 –
a controllable object, a setpoint or a setting and which is called "scheduled entity" in this
One of the most common uses of schedules is for scheduling real power output. In that case,
DER systems that directly manage their power output, such as reciprocating engines and
energy storage systems, may use schedules to determine the time and level of power output.
However, many other controllable entities may also be scheduled. Larger inverter-based DER
systems and large aggregations of small inverter-based DER systems have significant
influence on the distribution system and have local Volt-VAr characteristics that may vary
throughout the day. As a result, a single function or operational mode such as a specific Volt-
VAr curve may not be suitable at all times. Yet sending many control commands every few
hours to many different DER systems may impact bandwidth-limited communications systems
or may not be received in a timely manner, leading to inadequate DER system responses.
However, if schedules are established that the DER systems will follow autonomously, then
these communication impacts will be minimized.
Schedules may be used to allow even more autonomous control of the behaviour of DER
equipment. They are usually sent ahead of time, and then activated at the appropriate time or
by an external trigger event. There are different applications for schedules:
• schedules for direct values (e.g. setpoints for P/Q/cosphi);
• schedules for constraints (e.g. do not exceed the maximum value of P/Q/cosphi at a
certain time);
• schedules for pricing information (act on constraints);
• schedules for activation of modes (e.g. Volt-VAr curves);
• schedules for parameters of modes.
4.2 Relation between schedules and directly set values and parameters of the DER
As has been mentioned before, schedules are an alternate way to determine the behaviour
compared to direct control possibilities (i.e. using setpoints or activate and configure a
selected mode of operation). Therefore, it is important to describe how schedules and direct
control possibilities interact.
5 Principles for modelling schedules
5.1 Schedule controllers and their schedules
Within an electrical system, multiple entities may be scheduled in parallel. For example, it is
possible to schedule active power and reactive power. For each of the scheduled entities (see
4.1 and 6.1), there will be, as depicted in Figure 1, at most one schedule controller and
potentially several schedules referenced (used) by the schedule controller. One given
schedule may be referenced by multiple schedule controllers.
An entity is a data object that exists in the IEC 61850 data model which is either a data object
supporting control services (e.g. binary control or setpoint) or it is a setting (data object that
includes attributes of FC=SP). The schedule controller has a data object which is a reference
to the scheduled data object (see 6.3). For instance, a schedule controller could be
associated with WMax (setting of the maximum real power output of a DER – namespace "(TR)
IEC 61850-90-7:2012"). Another schedule controller could be associated with OpModVVAr
which enables/disables the volt/var mode (namespace "(TR) IEC 61850-90-7:2012").
The description in this subclause applies to one scheduled entity (i.e. one schedule controller
and multiple schedules).

---------------------- Page: 11 ----------------------
– 10 – IEC TR 61850-90-10:2017 © IEC 2017

Figure 1 – Scheduling principle
5.2 Scheduling and direct control / setting
5.2.1 General
As mentioned in 5.1, scheduling applies to scheduled entities which are data objects in the
IEC 61850 data model which may be controlled through control services (controllable data
object) or which are settings where the value may be written.
5.2.2 Case when the scheduled entity is of type "controllable data object"
For controllable data objects a new data object will be added in IEC 61850-7-4 for each
logical node which will indicate if direct settings control shall be used or if scheduling shall be
The behaviour, if scheduling is used and the schedule controller has no valid output (e.g. no
schedule is active), shall be the same behaviour as when a setpoint has never been initialized,
or when a controllable object has not received any control yet. It depends on the scheduled
entity and shall be defined by user requirements or declared in the MICS of the device.
NOTE As an example, a photovoltaic system may feed in as much power as possible into the grid if no schedule
is active. A pump may not operate anymore if no schedule is active. A valve may stay at the position it has last
If the scheduled entity is of type "controllable object" and is used as a setpoint (data objects
of the CDC APC that are not controlling equipment), the value applied shall be reflected in the
data attribute mxVal. If the schedule controller has no valid output, the quality of mxVal of the
scheduled entity shall be set to invalid.
5.2.3 Case when the scheduled entity is of type "setting"
For settings, the DO Mod of the schedule controller shall be set to "off" to indicate that the
direct settings shall be used.
1 Extension under

Questions, Comments and Discussion

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