IEC 60870-6-802:2002

INTERNATIONAL IEC
STANDARD
60870-6-802
Second edition
2002-04
Telecontrol equipment and systems –
Part 6-802:
Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
TASE.2 Object models
Matériels et systèmes de téléconduite –
Partie 6-802:
Protocoles de téléconduite compatibles avec les
normes ISO et les recommandations de l'UIT-T –
Modèles d'objets TASE.2
Reference number
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/catlg-e.htm) 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/JP.htm) 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: custserv@iec.ch
Tel: +41 22 919 02 11
Fax: +41 22 919 03 00
INTERNATIONAL IEC
STANDARD
60870-6-802
Second edition
2002-04
Telecontrol equipment and systems –
Part 6-802:
Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
TASE.2 Object models
Matériels et systèmes de téléconduite –
Partie 6-802:
Protocoles de téléconduite compatibles avec les
normes ISO et les recommandations de l'UIT-T –
Modèles d'objets TASE.2
 IEC 2002  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: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch  Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale
XC
International Electrotechnical Commission
Международная Электротехническая Комиссия
For price, see current catalogue

– 2 – 60870-6-802  IEC:2002(E)
CONTENTS
FOREWORD.4
INTRODUCTION.5
1 Scope.6
2 Normative references.6
3 Definitions .6
4 Abbreviations.6
5 Object models .7
5.1 Supervisory Control and Data Acquisition.7
5.1.1 IndicationPoint Object .7
5.1.2 ControlPoint Object.10
5.1.3 Protection Equipment Event Object Model.11
5.2 Transfer Accounts .14
5.2.1 TransferAccount Object .14
5.2.2 TransmissionSegment Object .17
5.2.3 ProfileValue Object .18
5.2.4 AccountRequest Object.19
5.3 Device Outage Object.20
5.4 InformationBuffer Object.22
5.5 Power Plant Objects .23
5.5.1 Availability Report Object .23
5.5.2 Real Time Status Object .26
5.5.3 Forecast Schedule Object .29
5.5.4 Curve Object .30
5.5.5 Power System Dynamics Objects .31
5.6 General Data Report Object.31
5.6.1 Abstract Object Model.31
5.7 General Data Response Object.34
5.7.1 Abstract Object Model.34
6 MMS Types for Object Exchange .35
6.1 Supervisory Control and Data Acquisition Types.35
6.1.1 IndicationPoint Type Descriptions .35
6.1.2 ControlPoint Type Descriptions .38
6.1.3 Protection Equipment Type Descriptions .39
6.2 Transfer Account Types.40
6.2.1 TransferAccount Type Descriptions.40
6.2.2 TransmissionSegment Type Descriptions .41
6.2.3 Transmission Segment Type Descriptions .42
6.2.4 ProfileValue Type Descriptions.42
6.2.5 Account Request Type Descriptions .42
6.3 Device Outage Type Descriptions .42
6.4 InformationBuffer Type Descriptions .44

60870-6-802 © IEC:2002(E) – 3 –
6.5 Power Plant Type Descriptions .44
6.5.1 Availability Report Type Descriptions.45
6.5.2 Real Time Status Type Descriptions.46
6.5.3 Forecast Type Descriptions.46
6.5.4 Curve Type Descriptions .47
6.6 Power System Dynamics.47
6.7 Matrix Data Types.47
6.8 GeneralDataReport Type Descriptions .49
6.9 GeneralDataResponse Type Descriptions .49
7 Mapping of Object Models to MMS Types.50
7.1 Supervisory Control and Data Mapping .50
7.1.1 Indication Object Mapping.50
7.1.2 ControlPoint Object Mapping.51
7.1.3 Protection Event Mapping .53
7.2 Transfer Accounts Mapping .55
7.2.1 TransferAccount Mapping .55
7.2.2 TransmissionSegment Mapping .59
7.2.3 ProfileValue Mapping .61
7.2.4 AccountRequest Mapping .62
7.3 Device Outage Mapping.62
7.4 Information Buffer Mapping.64
7.5 Power Plant Mapping .64
7.5.1 Availability Report Mapping .64
7.5.2 Real Time Status Mapping .67
7.5.3 Forecast Mapping .69
7.5.4 Curve Mapping .70
7.6 General Data Report Mapping.71
7.7 General Data Response Mapping.75
8 Use of Supervisory Control Objects.75
8.1 Use of IndicationPoint Model.76
8.2 Use of ControlPoint Model .76
9 Conformance.77
Annex A (informative) Transfer account examples .78

– 4 – 60870-6-802  IEC:2002(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
__________
TELECONTROL EQUIPMENT AND SYSTEMS –
Part 6-802: Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
TASE.2 Object models
FOREWORD
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of the 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, the IEC publishes International Standards. 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. The 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 the 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 National Committees.
3) The documents produced have the form of recommendations for international use and are published in the form
of standards, technical specifications, technical reports or guides and they are accepted by the National
Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International
Standards transparently to the maximum extent possible in their national and regional standards. Any
divergence between the IEC Standard and the corresponding national or regional standard shall be clearly
indicated in the latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with one of its standards.
6) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject
of patent rights. The IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 60870-6-802 has been prepared by IEC technical committee 57:
Power system control and associated communications.
This second edition cancels and replaces the first edition published in 1997 and constitutes a
technical revision.
The text of this standard is based on the following documents:
FDIS Report on voting
57/575/FDIS 57/583/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.
Annex A is for information only.
The committee has decided that the contents of this publication will remain unchanged
until 2004. At this date, the publication will be:
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
60870-6-802 © IEC:2002(E) – 5 –
INTRODUCTION
The primary purpose of Telecontrol Application Service Element (TASE.2) is to transfer data
between control systems and to initiate control actions. Data is represented by object
instances. This part of IEC 60870 proposes object models from which to define object
instances. The object models represent objects for transfer. The local system may not maintain
a copy of every attribute of an object instance.
The object models presented herein are specific to "control centre" or "utility" operations and
applications; objects required to implement the TASE.2 protocol and services are found in
IEC 60870-6-503. Since needs will vary, the object models presented here provide only a base;
extensions or additional models may be necessary for two systems to exchange data not
defined within this standard.
It is by definition that the attribute values (i.e. data) are managed by the owner (i.e. source) of
an object instance. The method of acquiring the values are implementation dependent;
therefore accuracy is a local matter.
The notation of the object modelling used for the objects specified in clause 5 is defined in
IEC 60870-6-503. It should be noted that this part of IEC 60870 is based on the TASE.2
services and protocol. To understand the modelling and semantics of this standard, some basic
knowledge of IEC 60870-6-503 is recommended.
Clause 5 describes the control centre-specific object models and their application. They are
intended to provide information to explain the function of the data.
Clause 6 defines a set of MMS type descriptions for use in exchanging the values of instances
of the defined object models. It is important to note that not all attributes of the object models
are mapped to types. Some attributes are described simply to define the processing required
by the owner of the data and are never exchanged between control centres. Other attributes
are used to determine the specific types of MMS variables used for the mapping, and therefore
do not appear as exchanged values themselves. A single object model may also be mapped
onto several distinct MMS variables, based on the type of access and the TASE.2 services
required.
Clause 7 describes the mapping of instances of each object type MMS variables and named
variable lists for implementing the exchange.
Clause 8 describes device-specific codes and semantics to be used with the general objects.
An informative annex is included which describes some typical interchange scheduling
scenarios, along with the use of TASE.2 objects to implement the schedule exchange.

– 6 – 60870-6-802  IEC:2002(E)
TELECONTROL EQUIPMENT AND SYSTEMS –
Part 6-802: Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
TASE.2 Object models
1 Scope
This part of IEC 60870 specifies a method of exchanging time-critical control centre data
through wide-area and local-area networks using a full ISO compliant protocol stack. It
contains provisions for supporting both centralized and distributed architectures. The standard
includes the exchange of real-time data indications, control operations, time series data,
scheduling and accounting information, remote program control and event notification.
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 60870-5-101:1995, Telecontrol equipment and systems – Part 5: Transmission protocols –
Section 101: Companion standard for basic telecontrol tasks
IEC 60870-6-503:2002, Telecontrol equipment and systems – Part 6: Telecontrol protocols
compatible with ISO standards and ITU-T recommendations – Section 503: TASE.2 Services
and protocol
ISO 9506-1:2000, Industrial automation systems – Manufacturing message specification –
Part 1: Service definition
ISO 9506-2:2000, Industrial automation systems – Manufacturing message specification –
Part 2: Protocol specification
3 Definitions
For the purposes of this part of IEC 60870, the definitions in the above referenced standards
apply.
4 Abbreviations
For the purposes of this part of IEC 60870, all the abbreviations defined in the above
referenced standards apply.
60870-6-802 © IEC:2002(E) – 7 –
5 Object models
Object models are required for various functions within a system. This clause delineates
abstract object models based on functionality. Object models within one functional area may be
used in another functional area.
5.1 Supervisory Control and Data Acquisition
The object models in this clause are derived from the historical perspective of Supervisory
Control and Data Acquisition (SCADA) systems. The following text presents the context within
which the object models are defined.
Fundamental to SCADA systems are two key functions: control and indication. The control
function is associated with the output of data whereas the indication function is associated with
the input of data. A more recent concept that is finding usage is the control and indication
function where data output may also be input (i.e. bi-directional).
The previous identified functions within SCADA systems are mapped to point equipment
(point). The primary attribute of a point is the data value. SCADA systems define three types of
data for points: analog, digital and state.
The association of one or more points together is used to represent devices. For example, a
breaker device may be represented by a control point and an indication point. The control point
represents the new state that one desires for the breaker device. The indication point
represents the current state of the breaker device. For SCADA to SCADA data exchange (e.g.
control centre to control centre, control centre to SCADA master, etc.), additional data is often
associated with point data. Quality of point data is often exchanged to defined whether the data
is valid or not. In addition, for data that may be updated from alternate sources, quality often
identifies the alternate source. Select-Before-Operate control is associated with Control Points
for momentary inhibiting access except from one source. Two other informative data values
are: time stamp and change of value counter. The time stamp, when available, details when a
data value last changed. The change of value counter, when available, details the number of
changes to the value.
From the context presented, the primary object models required are: Indication Point, and
Control Point. The attributes Point Value, Quality, Select-Before-Operate, Time Stamp, and
Change of Value Counter are required to meet the desired functionality for data exchange. The
Indication Point and Control Point models may be logically combined to a single model to
represent a device which implements a control function with a status indication as to its
success/failure. The combined logical model will result in the same logical attributes, and map
onto the same MMS types as the independent models.
5.1.1 IndicationPoint Object
An IndicationPoint object represents an actual input point.
Object: IndicationPoint (Read Only)
Key Attribute: PointName
Attribute: PointType (REAL, STATE, DISCRETE)
Constraint PointType=REAL
Attribute: PointRealValue
Constraint PointType=STATE
Attribute:PointStateValue
Constraint PointType=DISCRETE
Attribute: PointDiscreteValue
Attribute: QualityClass: (QUALITY, NOQUALITY)

– 8 – 60870-6-802  IEC:2002(E)
Constraint: QualityClass = QUALITY
Attribute: Validity (VALID, HELD, SUSPECT, NOTVALID)
Attribute: CurrentSource (TELEMETERED, CALCULATED, ENTERED, ESTIMATED)
Attribute: NormalSource (TELEMETERED, CALCULATED, ENTERED, ESTIMATED)
Attribute: NormalValue (NORMAL,ABNORMAL)
Attribute: TimeStampClass: (TIMESTAMP, TIMESTAMPEXTENDED, NOTIMESTAMP)
Constraint: TimeStampClass = TIMESTAMP
Attribute: TimeStamp
Attribute: TimeStampQuality: (VALID, INVALID)
Constraint: TimeStampClass = TIMESTAMPEXTENDED
Attribute: TimeStampExtended
Attribute: TimeStampQuality: (VALID, INVALID)
Attribute: COVClass: (COV, NOCOV)
Constraint: COVClass = COV
Attribute: COVCounter
PointName
The PointName attribute uniquely identifies the object.
PointType
The PointType attribute identifies the type of input point, and must be one of the following:
REAL, STATE, DISCRETE.
PointRealValue
The current value of the IndicationPoint, if the PointType attribute is REAL.
PointStateValue
The current value of the IndicationPoint, if the PointType attribute is STATE.
PointDiscreteValue
The current value of the IndicationPoint, if the PointType attribute is DISCRETE.
QualityClass
The QualityClass has the value QUALITY if the object instance has any of the quality attributes
(Validity, CurrentSource, or NormalValue), and takes the value NOQUALITY if none of the
attributes are present.
Validity
The Validity attribute specifies the validity or quality of the PointValue data it is associated with.
These are based on the source system's interpretation as follows:
Validity Description
VALID Data value is valid
HELD Previous data value has been held over. Interpretation is local
SUSPECT Data value is questionable. Interpretation is local
NOTVALID Data value is not valid

60870-6-802 © IEC:2002(E) – 9 –
CurrentSource
The CurrentSource attribute specifies the current source of the PointValue data it is associated
with as follows:
CurrentSource Description
TELEMETERED The data value was received from a telemetered site
CALCULATED The data value was calculated based on other data values
ENTERED The data value was entered manually
ESTIMATED The data value was estimated (State Estimator, etc.)
NormalSource
The NormalSource attribute specifies the normal source of the PointValue data it is associated
with as follows:
NormalSource Description
TELEMETERED The data value is normally received from a telemetered site
CALCULATED The data value is normally calculated based on other data values
ENTERED The data value is normally entered manually
ESTIMATED The data value is normally estimated (State Estimator, etc.)
NormalValue
The NormalValue attribute reports whether value of the PointValue attribute is normal. Only
one bit is set, it is defined as follows:
NormalValue Description
NORMAL The point value is that which has been configured as normal for the point
ABNORMAL The point value is not that which has been configured as normal for the point
TimeStampClass
The TimeStampClass attribute has the value TIMESTAMP or TIMESTAMPEXTENDED if the
IndicationPoint is time stamped, and has the value NOTIMESTAMP if the IndicationPoint
contains no TimeStamp attribute.
TimeStamp
The TimeStamp attribute provides a time stamp (with a minimum resolution of one second) of
when the value (attribute PointRealValue, PointStateValue or PointDiscreteValue) of the
IndicationPoint was last changed. It is set at the earliest possible time after collection of the
IndicationPoint value from the end device.
TimeStampExtended
The TimeStampExtended attribute provides a time stamp (with a resolution of one millisecond)
of when the value (attribute PointRealValue, PointStateValue or PointDiscreteValue) of the
IndicationPoint was last changed. It is set at the earliest possible time after collection of the
IndicationPoint value from the end device.
TimeStampQuality
The TimeStampQuality attribute has the value VALID if the current value of the TimeStamp
attribute contains the time stamp of when the value was last changed, and has the value
INVALID at all other times.
COVClass
The COVClass (Change Of Value Counter) attribute has the value COV if the IndicationPoint
contains a COVCounter attribute, otherwise it has the value NOCOV.
COVCounter
The COVCounter attribute specifies the number of times the value (attribute PointRealValue,
PointStateValue, or PointDiscreteValue) of the IndicationPoint has changed. It is incremented
each time the owner sets a new value for the IndicationPoint.

– 10 – 60870-6-802  IEC:2002(E)
5.1.2 ControlPoint Object
A ControlPoint Object is an integral part of the services provided by TASE.2. It is used to
represent values of various types of data typical of SCADA and energy management systems.
Typically, a ControlPoint object will be associated with some real world object.
Object: ControlPoint (Write Only, except for attributes CheckBackName, Tag, State and Reason)
Key Attribute: ControlPointName
Attribute: ControlPointType: (COMMAND, SETPOINT)
Constraint: ControlPointType = COMMAND
Attribute: CommandValue
Constraint: ControlPointType = SETPOINT
Attribute: SetPointType: (REAL, DISCRETE)
Constraint SetpointType=REAL
Attribute: SetpointRealValue
Constraint SetpointType=DISCRETE
Attribute: SetpointDiscreteValue
Attribute: DeviceClass: (SBO, NONSBO)
Constraint: DeviceClass = SBO
Attribute: CheckBackName
Attribute: State: (SELECTED, NOTSELECTED)
Attribute: Timeout
Attribute: TagClass: (TAGGABLE, NONTAGGABLE)
Constraint: TagClass = TAGGABLE
Attribute: Tag: (NO-TAG, OPEN-AND-CLOSE-INHIBIT, CLOSE-ONLY-INHIBIT)
Attribute: State: (IDLE, ARMED)
Attribute: Reason
ControlPointName
The ControlPointName attribute uniquely identifies the object.
ControlPointType
The value of the ControlPointType attribute for an instance of a ControlPoint will be COMMAND
or SETPOINT, indicating the type of controlled device.
CommandValue
The CommandValue attribute indicates the command for a device.
SetPointType
The value of the SetPointType attribute for an instance of a ControlPoint of ControlPointType
SETPOINT will be REAL or DISCRETE, indicating the type of setpoint.
SetPointRealValue
The SetPointRealValue attribute may be set with the floating point value requested for the
setpoint control.
SetPointDiscreteValue
The SetPointDiscreteValue attribute may be set with the integer value requested for the
setpoint control.
DeviceClass
The DeviceClass attribute of an instance of a ControlPoint has the value SBO if the device
requires a Select operation before being operated, and the value NONSBO otherwise.

60870-6-802 © IEC:2002(E) – 11 –
CheckBackName
The CheckBackName attribute contains a symbolic description of the physical object being
controlled. This data is returned by the system operating the physical object to the system
requesting the operation so that the person or system requesting the operation can be assured
the proper object has been selected.
State
The State attribute indicates whether the ControlPoint is SELECTED or NOTSELECTED.
Timeout
The Timeout attribute of an instance of a ControlPoint has the value of the maximum allowed
time for which the ControlPoint of DeviceClass SBO may remain SELECTED before operation.
TagClass
The TagClass attribute of an instance of a ControlPoint has the value TAGGABLE if the
instance contains a Tag attribute, and otherwise has the value NONTAGGABLE.
Tag
The Tag attribute indicates whether or not the ControlPoint is tagged, and if it is, what the level
of tagging is. The Tag attribute can take on the values NO-TAG, OPEN-AND-CLOSE-INHIBIT,
CLOSE-ONLY-INHIBIT.
Reason
The Reason attribute contains a message that indicates the reason for tagging.
5.1.3 Protection Equipment Event Object Model
The following object model represents the events generated in the operation of protection
equipment. Start events are generated by the protection equipment when it detects faults. Trip
events report commands to output circuits which are generated by the protection equipment
when it decides to trip the circuit-breaker. Both events are transient information. The protection
event models are based on IEC 60870-5-101.
Object: ProtectionEvent
KeyAttribute: Name
Attribute: ElapsedTimeValidity (VALID, INVALID)
Attribute: Blocked (NOTBLOCKED, BLOCKED)
Attribute: Substituted (NOTSUBSTITUTED, SUBSTITUTED)
Attribute: Topical (TOPICAL, NOTTOPICAL)
Attribute: EventValidity (VALID, INVALID)
Attribute: ProtectionClass (SINGLE, PACKED)
Constraint: ProtectionClass = SINGLE
Attribute: EventState (INDETERMINATE, OFF, ON)
Attribute: EventDuration
Attribute: EventTime
Constraint: ProtectionClass = PACKED
Attribute: EventClass (START, TRIP)
Constraint: EventClass = START
Attribute: StartGeneral (NOSTART, START)
Attribute: StartPhase1 (NOSTART, START)
Attribute: StartPhase2 (NOSTART, START)
Attribute: StartPhase3 (NOSTART, START)
Attribute: StartEarth (NOSTART, START)
Attribute: StartReverse (NOSTART, START)
Attribute: DurationTime
Attribute: StartTime
– 12 – 60870-6-802  IEC:2002(E)
Constraint: EventClass = TRIP
Attribute: TripGeneral (NOTRIP, TRIP)
Attribute: TripPhase1 (NOTRIP, TRIP)
Attribute: TripPhase2 (NOTRIP, TRIP)
Attribute: TripPhase3 (NOTRIP, TRIP)
Attribute: OperatingTime
Attribute: TripTime
Name
The Name attribute uniquely identifies the protection event.
ElapsedTimeValidity
The elapsed time (attribute EventDuration, DurationTime, or OperatingTime depending on the
event type) is valid if it was correctly acquired. If the acquisition function detects invalid
conditions, the ElapsedTimeValidity attribute is INVALID, otherwise it is VALID.
Blocked
The Blocked attribute is BLOCKED if the value of protection event is blocked for transmission,
and is NOTBLOCKED otherwise. The value remains in the state that was acquired before it
was blocked. Blocking and deblocking may be initiated by a local lock or by a local automatic
cause.
Substituted
The Substituted attribute takes the value SUBSTITUTED if the event was provided by input of
an operator (dispatcher) or by an automated source.
Topical
The Topical attribute is TOPICAL if the most recent update was successful, and is
NOTTOPICAL if it was not updated successfully during a specified time interval or is
unavailable.
EventValidity
The EventValidity attribute takes the value INVALID if the acquisition function recognizes
abnormal conditions of the information source, otherwise it is VALID.
ProtectionClass
The ProtectionClass attribute identifies the type of protection event, and must be one of the
following: SINGLE or PACKED.
EventState
The EventState attribute of a SINGLE protection event takes the value of the protection event:
OFF, ON or INDETERMINATE.
EventDuration
The EventDuration attribute takes the value of the event duration (total time the fault was
detected) or operation time (time between start of operation and trip command execution).
EventTime
The EventTime attribute signifies the time of the start of the operation.
EventClass
The type of protection event being reported. The value START signifies a start event, and TRIP
signifies a trip event.
60870-6-802 © IEC:2002(E) – 13 –
StartGeneral
The value NOSTART signifies no general start of operation, and START signifies that the event
includes a general start of operation.
StartPhase1
The value NOSTART for StartPhase1 implies that Phase L1 was not involved in the event,
START implies that it was involved.
StartPhase2
The value NOSTART for StartPhase2 implies that Phase L2 was not involved in the event,
START implies that it was involved.
StartPhase3
The value NOSTART for StartPhase3 implies that Phase L3 was not involved in the event,
START implies that it was involved.
StartEarth
The value NOSTART for StartEarth implies that earth current was not involved in the event,
START implies that it was involved.
StartReverse
The value NOSTART for StartReverse implies that reverse direction was not involved in the
event, START implies that it was involved.
DurationTime
Time in milliseconds from the start of operation until the end of operation.
StartTime
Time of the start of operation of the protection equipment.
TripGeneral
The TripGeneral attribute takes on the value of TRIP if a general command to the output circuit
was issued during the operation, NOTRIP otherwise.
TripPhase1
The TripPhase1 attribute takes on the value of TRIP if a command to output circuit Phase L1
command was issued during the operation, NOTRIP otherwise.
TripPhase2
The TripPhase2 attribute takes on the value of TRIP if a command to output circuit Phase L2
command was issued during the operation, NOTRIP otherwise.
TripPhase3
The TripPhase3 attribute takes on the value of TRIP if a command to output circuit Phase L3
command was issued during the operation, NOTRIP otherwise.
OperatingTime
The time in milliseconds from the start of operation until the first command to an output circuit
was issued.
TripTime
Time of the start of the operation.

– 14 – 60870-6-802  IEC:2002(E)
5.2 Transfer Accounts
One of the key control centre application requirements is the ability to exchange "scheduling"
and "accounting" information. In the utility world, "schedules" is a term that generally means an
amount of electrical energy transferred from one system to another on a periodic basis for a
certain interval of time under the restrictions of a formal agreement. From a data exchange
standpoint, exchanging "schedules" has been expanded to include the exchange of any
periodic or profile data for control centre energy scheduling, accounting or monitoring
applications. Thus exchanging schedules may also mean exchanging generation, actual inter-
change, loads, price information, memo accounts, etc. Again, any information may be
exchanged if it can be modelled as periodic or profile data.
Schedule accounts and accounting information accounts specify a list of quantities (energy,
capacity or some other user-defined quantity) to be exchanged during sequential time periods.
These transactions may be specified either as flat periodic values or as ramped profiles. In
addition, schedule accounts may contain a list of transmission segments defining the paths
used to implement the transaction.
The subclauses below discuss the object models for transfer accounts.
5.2.1 TransferAccount Object
A Transfer Account object represents what, where, when, and how much is transferred
between two utilities in a particular account. It may also represent generation schedules and
other energy delivery schedules within a utility. It is a container for a number of different
attributes and objects which together define the entire transfer account definition, i.e. which
account, when is the effective time frame, and what are the periodic or profile values of the
data. Refer to annex A for more information concerning how these object definitions relate to
each other.
Object: TransferAccount
Key Attribute: TransferAccountReference
Attribute: SendUtility
Attribute: ReceiveUtility
Attribute: SellingAgent
Attribute: BuyingAgent
Attribute: TimeStamp
Attribute: TransactionCode
Attribute: NumberOfLocalReference
Attribute: ListOfLocalReference
Attribute: Name
Attribute: TransmissionSegmentOption (INCLUDED, NOTINCLUDED)
Constraint: TransmissionSegmentOption=INCLUDED
Attribute: NumberOfTransSegments
Attribute: ListOfTransmissionSegment
Attribute: DataType (PERIODIC, PROFILE)
Constraint: DataType = PERIODIC
Attribute: StartTime
Attribute: PeriodResolution
Attribute: NumberOfPeriods
Attribute: ListOfPeriodicValues
Constraint: DataType = PROFILE
Attribute: NumberOfProfiles
Attribute: ListOfProfileValues

60870-6-802 © IEC:2002(E) – 15 –
TransferAccountReference
The TransferAccountReference attribute specifies a unique reference value between the
sender and the receiver to identify this particular transfer account.
SendUtility
The SendUtility attribute specifies the utility initially delivering the energy or service.
ReceiveUtility
The ReceiveUtility attribute specifies the utility ultimately receiving the energy or service.
SellingAgent
Currently, the seller is almost always the same as SendUtility. However, as a result of
deregulation and open access, it is likely in the future that the seller may be an independent
power producer within the area serviced by the SendUtility. Obviously, in such cases it is
necessary to distinguish between the seller and the sending utility; this attribute allows such a
distinction.
BuyingAgent
Currently, the buyer is almost always the same as ReceiveUtility. However, as a result of
deregulation and open access, it is likely in the future that the buyer may be a municipality or
cooperative within the area serviced by the ReceiveUtility. Obviously, in such cases it is
necessary to distinguish between the buyer and the receiving utility; this attribute allows such a
distinction.
TimeStamp
The TimeStamp attribute provides a means for the receiver to know when the sender sent this
message. The time stamp indicates when the application created the Transfer Account data for
the purpose of transmitting the data. It is not related to the time to which the Transfer Account
data itself applies. If the applications providing data to TASE.2 include a transmission (or
object creation) time stamp, that time stamp is used. Otherwise, TASE.2 provides the time
stamp prior to passing the Transfer Account object to MMS.
TransactionCode
The TransactionCode attribute provides status on the TransferAccount transaction. The values
are shown below:
TransactionCode Description
NEW Original submittal of a newly proposed
schedule or of a report
REQUESTED Report or schedule is requested via the
Account Request operation
REVISED Revised version of previously sent schedule
or report
CONFIRMED Schedule or report has now been scheduled
for actual implementation and is not subject
to further approval cycles. A curtailment,
halt, revision, or deletion after this stage
requires a new schedule or report to be sent
DELETED Any time the originator of the schedule or
report cancels the transaction (for example,
due to equipment failure)
– 16 – 60870-6-802  IEC:2002(E)
NumberOfLocalReference
This attribute contains the count of entries in the ListOfLocalReference.
ListOfLocalReference
The ListOfLocalReference contains locally defined parameters that specify how the Transfer
Account Object is to be treated as a whole. For example, it might specify that the schedule or
transaction applies to all Mondays during Summer. The meaning of the parameter list is a local
matter and is agreed upon among the participating parties for each type of Transfer Account
object, for all Transfer Account objects, or for a combination of the two as needed.
Name
The Name attribute provides an option for the user application to include string related
information associated with the Transfer Account object. For example, a schedule may need to
identify a generating unit by name. Whether or not this attribute is used and its semantics are a
local implementation matter.
TransmissionSegmentOption
The TransmissionSegmentOption indicates whether or not a ListOfTransmissionSegments is
included in the Transfer Account object. Transmission segments may be included in a Transfer
Account object independently of the kind of data the Transfer Account object represents, i.e. it
does not have to be included only for energy buy-sell transactions between utilities where
wheeling is involved. Transmission segments can be used in any Transfer Account object to
convey any information between multiple parties when some of the information is unique to
each party and it is desired to provide all of the information in the account to all parties.
NumberOfTransSegments
This attribute defines the number of transmission segments to be included in the report.
ListOfTransmissionSegments
The ListOfTransmissionSegments attribute describes the various transmission paths (or
segments) that an interchange schedule may take to get from the SendUtility to the
ReceiveUtility, or to describe other information that is significant to intermediate parties of any
transaction. Each TransmissionSegment object provided describes one component of the path,
or data for one intermediate party. As many or as few TransmissionSegment Objects as
required may be added to the list.
DataType
The data contained in a Transfer Account object can be periodic as is the case of most of the
data for generation schedules, energy transactions, and billing. The data can also define a
series of ramping requirements which together result in an energy (or price) profile. The
DataType attribute indicates which of these two types of data the Transfer Account object
contains. Note that a Transfer Account object cannot contain both periodic and profile data.
However, there is no restriction on the use of the TransferAccountReference attribute with
respect to the object’s data type. Therefore, two Transfer Account objects could be transmitted
with the same TransferAccountReference; the first would convey periodic type information
while the other would convey profile type data.
StartTime
For a Transfer Account object containing periodic data, StartTime specifies the UTC time to
which the first time period in the sequence applies.
PeriodResolution
For a Transfer Account object containing periodic data, PeriodResolution specifies the quantity
of time to which each entry in the sequence applies.
NumberOfPeriods
This attribute defines the number of time periods being specified in the sequence defined by
the Transfer Account object. Together with StartTime and PeriodResolution, it also defines the
maximum time frame covered by the Transfer Account.

60870-6-802 © IEC:2002(E) – 17 –
Li
...