SIST EN 60870-6-702:2000
(Main)Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.2 application service in end systems (IEC 60870-6-702:1998)
Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.2 application service in end systems (IEC 60870-6-702:1998)
Is a functional profile (FP) and defines the provision of the TASE.2 communications services between two control centre end systems. This FP also defines the provision of the OSI connection-mode presentation and session services between the end systems.
Fernwirkeinrichtungen und -systeme -- Teil 6-702: Fernwirkprotokolle, die mit ISO-Normen und ITU-T-Empfehlungen kompatibel sind - Funktionsprofil für den TASE.2-Anwendungsdienst in Endsystemen
Matériels et systèmes de téléconduite -- Partie 6-702: Protocoles de téléconduite compatibles avec les normes ISO et les recommandations de l'UIT-T - Profil fonctionnel pour fournir le service d'application TASE.2 dans des systèmes terminaux
Est un profil fonctionnel (PF) et définit la prestation des services de communication TASE.2 entre deux systèmes finals d'un centre de conduite. Ce PF définit également la prestation de services de présentation et de session en mode connexion OSI entre les systèmes finals.
Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing TASE.2 application service in end system (IEC 60870-6-702:1998)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 60870-6-702:2000
01-februar-2000
Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible
with ISO standards and ITU-T recommendations - Functional profile for providing
TASE.2 application service in end system (IEC 60870-6-702:1998)
Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with
ISO standards and ITU-T recommendations - Functional profile for providing the TASE.2
application service in end systems (IEC 60870-6-702:1998)
Fernwirkeinrichtungen und -systeme -- Teil 6-702: Fernwirkprotokolle, die mit ISO-
Normen und ITU-T-Empfehlungen kompatibel sind - Funktionsprofil für den TASE.2-
Anwendungsdienst in Endsystemen
Matériels et systèmes de téléconduite -- Partie 6-702: Protocoles de téléconduite
compatibles avec les normes ISO et les recommandations de l'UIT-T - Profil fonctionnel
pour fournir le service d'application TASE.2 dans des systèmes terminaux
Ta slovenski standard je istoveten z: EN 60870-6-702:1998
ICS:
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
SIST EN 60870-6-702:2000 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
NORME
CEI
INTERNATIONALE
IEC
60870-6-702
INTERNATIONAL
Première édition
STANDARD
First edition
1998-10
Matériels et systèmes de téléconduite –
Partie 6-702:
Protocoles de téléconduite compatibles avec les
normes ISO et les recommandations de l’UIT-T –
Profil fonctionnel pour fournir le service
d’application TASE.2 dans les systèmes finals
Telecontrol equipment and systems –
Part 6-702:
Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
Functional profile for providing the TASE.2
application service in end systems
IEC 1998 Droits de reproduction réservés Copyright - all rights reserved
Aucune partie de cette publication ne peut être reproduite ni No part of this publication may be reproduced or utilized in
utilisée sous quelque forme que ce soit et par aucun any form or by any means, electronic or mechanical,
procédé, électronique ou mécanique, y compris la photo- including photocopying and microfilm, without permission in
copie et les microfilms, sans l'accord écrit de l'éditeur. writing from the publisher.
International Electrotechnical Commission 3, rue de Varembé Geneva, Switzerland
Telefax: +41 22 919 0300 e-mail: inmail@iec.ch IEC web site http: //www.iec.ch
CODE PRIX
Commission Electrotechnique Internationale
PRICE CODE U
International Electrotechnical Commission
Pour prix, voir catalogue en vigueur
For price, see current catalogue
---------------------- Page: 2 ----------------------
60870-6-702 © IEC:1998 – 3 –
CONTENTS
Page
FOREWORD . 5
INTRODUCTION . 7
Clause
1 Scope. 9
2 Normative references. 11
3 Definitions. 11
4 Abbreviations. 11
5 Profile protocol stacks . 11
6 Conformance requirements. 13
6.1 TASE.2 requirements. 13
6.2 MMS requirements. 13
6.3 Upper layers requirements . 13
Annex A (normative) ISPICS requirements lists. 15
A.1 General. 15
A.2 Classification of requirements . 15
A.2.1 Base column . 15
A.2.2 F/S column. 17
A.2.3 Status column . 17
A.2.4 Profile column . 19
A.3 TASE.2 . 19
A.4 MMS . 31
A.4.1 Supported MMS PDUs. 31
A.4.2 PDU-specific requirements . 41
A.5 ACSE. 41
A.5.1 Supported functions . 41
A.5.2 Initiator/responder capability. 43
A.5.3 Supported APDUs . 45
A.5.4 Supported APDU parameters . 47
A.5.5 Supported parameter forms. 49
A.6 Presentation. 51
A.7 Session. 53
Annex B (informative) Future developments . 55
Annex C (informative) Bibliography . 57
---------------------- Page: 3 ----------------------
60870-6-702 © IEC:1998 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
_________
TELECONTROL EQUIPMENT AND SYSTEMS –
Part 6-702: Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
Functional profile for providing the TASE.2
application service in end systems
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 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-702 has been prepared by IEC technical committee 57:
Power system control and associated communications.
The text of this standard is based on the following documents:
FDIS Report on voting
57/368/FDIS 57/377/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 forms an integral part of this standard.
Annexes B and C are for information only.
---------------------- Page: 4 ----------------------
60870-6-702 © IEC:1998 – 7 –
INTRODUCTION
This part of IEC 60870 is one of the IEC 60870-6 series defining functional profiles to be used
in telecommunication networks for electric power systems. It is largely based on existing
ISO/IEC International Standards and International Standardized Profiles (ISP).
The notion of functional profiles is fundamental in the organization of the IEC 60870-6 series. A
description of functional profiles, their classification scheme and the manner of defining them
are laid down in IEC 60870-6-1.
This profile for telecontrol application service element (TASE.2, also known as inter-control
centre communications protocol, ICCP) is an application-class profile (A-profile) providing
communications capabilities to control centre applications. The TASE.2 in the application layer
is specified in IEC 60870-6-503. The present standard refines the application layer protocol to
meet interoperability requirements and specifies requirements on the presentation and session
layers support for TASE.2. TASE.2 operates in a connection mode, so this A-profile needs to
interface to a transport-class profile of the T-profile variety.
Since the TASE.2 is an MMS-based protocol, this functional profile (FP) is based on MMS profiles.
In the OSI international standardized profile taxonomy there is a category for MMS A-profiles.
The present standard makes frequent use of the AMM11 profile.
---------------------- Page: 5 ----------------------
60870-6-702 © IEC:1998 – 9 –
TELECONTROL EQUIPMENT AND SYSTEMS –
Part 6-702: Telecontrol protocols compatible with
ISO standards and ITU-T recommendations –
Functional profile for providing the TASE.2
application service in end systems
1 Scope
This part of IEC 60870 is a functional profile (FP) and defines the provision of the TASE.2
communications services between two control centre end systems. It is supported by the
transport services implemented in accordance with transport-profiles defined for the type of
network that interconnects the control centre end systems. This is demonstrated in figure 1.
This FP also defines the provision of the OSI connection-mode presentation and session
services between the end systems.
ISO/ISP 14226 specifies the AMM11 profiles for MMS. The parts of ISO/ISP 14226 that cover
the profile that are used as a basis for this FP are ISO/ISP 14226-1 and ISO/ISP 14226-2.
This FP is in alignment with ISO/ISP 14226, as far as possible, and maintains this compatibility
by reference. There are TASE.2 requirements in addition to ISO/ISP 14226. These
requirements are specified in this FP.
Control Control
centre centre
applications applications
TASE.2/MMS
Application
Application
Presentation protocol
Presentation
Presentation
Session protocol
Session Session
4 4
3 3
2 2
1 1
Figure 1 – Applicability of functional profile
---------------------- Page: 6 ----------------------
60870-6-702 © IEC:1998 – 11 –
2 Normative references
The following normative documents contain provisions which, through reference in this text,
constitute provisions of this part of IEC 60870. At the time of publication, the editions indicated
were valid. All normative documents are subject to revision, and parties to agreements based
on this part of IEC 60870 are encouraged to investigate the possibility of applying the most
recent editions of the normative documents indicated below. Members of IEC and ISO maintain
registers of currently valid International Standards.
IEC 60870-6-503:1997, Telecontrol equipment and systems – Part 6: Telecontrol protocols
compatible with ISO standards and ITU-T recommendations – Section 503: TASE.2 Services
and protocol
ISO/IEC 8327-2:1996, Information technologies – Open Systems interconnection – Connection-
oriented session protocol – Part 2: Protocol implementation conformance statement (PICS)
proforma
ISO/IEC 8650-2:1997, Information technology – Open Systems Interconnection – Protocol
specification for the Association Control Service Element – Part 2: Protocol Implementation
Conformance Statement (PICS) proforma
ISO/IEC 8823-2:1997, Information technology – Open Systems Interconnection – Connection-
oriented presentation protocol – Part 2: Protocol Implementation Conformance Statement
(PICS) Proforma
ISO/ISP 14226-1:1996, Industrial automation systems – International Standardized Profile
AMM11: MMS General Applications Base Profile – Part 1: Specification of ACSE, Presentation
and Session protocols for the use by MMS
ISO/ISP 14226-2:1996, Industrial automation systems – International Standardized Profile
AMM11: MMS General Applications Base Profile – Part 2: Common MMS requirements
3 Definitions
All the terms used in this standard are as defined in the above-referenced standards.
4 Abbreviations
All the abbreviations used in this standard are as defined in the above-referenced standards.
5 Profile protocol stacks
As shown in figure 1, the TASE.2 profile includes the TASE.2, MMS and ACSE elements in the
TASE.2 protocol, the connection-mode presentation protocol, and the connection-mode
session protocol.
---------------------- Page: 7 ----------------------
60870-6-702 © IEC:1998 – 13 –
6 Conformance requirements
The TASE.2 application profile can be referred to as a TASE.2 MMS application profile. It shall
follow the same rules and regulations governing MMS ISPs. Requirements of the TASE.2 MMS
application profile to support TASE.2 are separated into upper layer requirements, MMS
requirements, and TASE.2 requirements.
The ISPICS requirements lists for TASE.2, MMS, ACSE, presentation and session are given in
annex A. Annex A makes mandatory some features that were optional in ISO/ISP 14226-1 and
ISO/ISP 14226-2.
For each implementation claiming conformance to this part of IEC 60870 an appropriate set of
PICSs shall be made available stating support or non-support of each option identified in
this part.
6.1 TASE.2 requirements
There are no TASE.2 requirements besides those specified in the conformance statement
given in IEC 60870-6-503.
6.2 MMS requirements
The MMS conformance requirements are specified in IEC 60870-6-503. A data structure
nesting level parameter value of greater than 1 shall be supported.
6.3 Upper layers requirements
Upper layer requirements for TASE.2 shall be as defined by ISO/ISP 14226-1 for the AMM11
profile. In addition, the presentation protocol shall be able to support the default context
negotiation, default context name and simply encoded data options.
The TASE.2 MMS application profile requires that there be a mechanism for the application
association performance/quality attributes to be conveyed to the transport (and thus network)
service. The mechanism employed is implementation-defined, but the TASE.2 and transport
profile implementations must be compatible.
When an association is requested, if there is a priority class agreed for it, the value agreed
between the control centres is given to the transport layer. Every data unit that is sent on this
association is treated according to the priority class in the transport service. If no priority value
is agreed, then none is expressed and a default value is assumed.
---------------------- Page: 8 ----------------------
60870-6-702 © IEC:1998 – 15 –
Annex A
(normative)
ISPICS requirements lists
A.1 General
This annex describes the TASE.2, ACSE, presentation and session requirements in terms of
tables which reference the base standard PICS proforma. The MMS requirements are also
described in terms of tables which were derived from the base standard. The tables are
intended to give a precise specification of requirements. In case of arbitration or dispute, this
annex takes precedence over clause 6.
In the PICS proforma reference column of the tables in A.3 and A.5 to A.7, and in the lists of
conditional expressions underneath the tables, tables within the base standard PICS proformas
are referenced. The first letter identifies the specific PICS proforma:
I – TASE.2 – IEC 60870-6-503;
A – ACSE – ISO/IEC 8650-2;
P – Presentation – ISO/IEC 8823-2;
S – Session – ISO/IEC 8327-2.
The characters from the second character to the solidus (/) form a reference to the specific
subclause in annex A of that PICS proforma which contains the table in question. The number
after the solidus references the row number in the table.
Coupling between layers is accounted for in this standard. Optional "o" items can be chosen
without regard to the affect on another layer.
A.2 Classification of requirements
Throughout this annex, to specify the level of support for each feature, the following
classification is used.
Client-CR: Client conformance requirement
Server-CR: Server conformance requirement
A.2.1 Base column
The "Base" column reflects the definitions and specifications in the appropriate base standard.
Each entry in this column is chosen from the following list:
mandatory; m: this feature shall be supported, i.e. its syntax and procedures shall be im-
plemented as specified in the base standard. However, it is not a requirement that the feature
shall be used in all instances of communication, unless mandated by the base standard;
optional; o: any feature denoted by "o" is left to the implementation as to whether that feature is
implemented or not. If a parameter is optionally supported, then the syntax shall be implemented,
but it is left to each implementation whether the procedures are implemented or not.
Where the base entry contains two classifications separated by a comma, these reference the
sending and receiving capabilities, respectively.
---------------------- Page: 9 ----------------------
60870-6-702 © IEC:1998 – 17 –
A.2.2 F/S column
The "F/S" column reflects the requirements of this Functional Standard. Each entry in this
column is chosen from the following terminology:
supported; m: any feature denoted by "m" is mandatory or optional in the base standard. This
feature shall be supported, i.e. its syntax and procedures shall be implemented as specified in
the base standard or in this ISP by all implementations claiming conformance to this standard.
However, it is not a requirement that the feature shall be used in all instances of
communication, unless mandated by the base standard or stated otherwise in this profile;
optionally supported; o: any feature denoted by "o" is left to the implementation as to
whether that feature is implemented or not. If a parameter is optionally supported, then the
syntax shall be implemented, but it is left to each implementation whether the procedures are
implemented or not;
conditionally supported; c: any feature denoted by "c" shall be supported under the
conditions specified in this standard. If these conditions are not met, the feature is outside the
scope of this standard;
excluded; x: any feature denoted by "x" is excluded in this profile, i.e. an implementation shall
behave as if the feature were not implemented;
outside of scope; i: any feature denoted by "i" is outside the scope of this standard, i.e. it may
be ignored, and will therefore not be subject to a profile conformance test. However, the syntax
of all parameters of supported PDUs shall be implemented, even if the procedures are not (i.e.
the receiver shall be able to decode the PDU);
not applicable; –: any feature denoted by "–" is not defined in the context where it is
mentioned, e.g. a parameter which is not part of the respective PDU. The occurrence of "not
applicable" features is mainly due to the format of the tables in the ISPICS requirements list.
Where the F/S entry contains two classifications separated by a comma, these reference the
sending and receiving capabilities, respectively.
A.2.3 Status column
The status column reflects the classification to be found in the base standard PICS proforma:
o: optional;
c: conditional;
o.n: optional with at least one of the marked items being selected.
The definitions of conditional items may be found in the respective PICS proformas.
Where the status entry contains two classifications separated by a comma, these reference the
sending and receiving capabilities, respectively.
---------------------- Page: 10 ----------------------
60870-6-702 © IEC:1998 – 19 –
A.2.4 Profile column
The profile column reflects the requirement of this profile. Each entry in this column is chosen
from the following list:
m: mandatory support;
c: conditional support;
o.n: optional with at least one of the marked items being selected;
i: outside the scope;
–: not applicable.
Where the profile entry contains two classifications, separated by a comma, these reference
the sending and receiving capabilities, respectively.
A.3 TASE.2
n
Throughout this clause, the entry m denotes that the item is mandatory for conformance to
block n.
Table A.1 – Client/Server capability
PICS Capability Base F/S
proforma
reference
I. /1 Client control centre o.1
I. /2 Server control centre o.1
Table A.2 – TASE.2 CBBs
PICS Conformance Base F/S
proforma building
reference block
Client-CR Server-CR
I. /1 Basic Services m m m
I. /2 Extended Conditions o o o
I. /3 Blocked Transfers o o o
I. /4 Information Message o o o
I. /5 SBO Device Control o o o
I. /6 Programs o o o
I. /7 Events o o o
I. /8 Accounts o o o
I. /9 Time Series o o o
---------------------- Page: 11 ----------------------
60870-6-702 © IEC:1998 – 21 –
Table A.3 – Association management
PICS Association management Base F/S
proforma
reference
Client-CR Server-CR
1 1 1
I. /1 Supported Features m m m
I. /2 QOS o o o
1 1 1
I. /3 Associate Operation m m m
1 1 1
I. /4 Conclude Operation m m m
1 1 1
I. /5 Abort Operation m m m
Table A.4 – Data value
PICS Data values Base F/S
proforma
reference
Client-CR Server-CR
1 1 1
I. /1 Data Value Model m m m
1
I. /2 VCC-specific scope (see note) o m o
1
I. /3 ICC-specific scope (see note) o m o
1 1
I. /4 Get Data Value Operation o, m om
1 1
I. /5 Set Data Value Operation o, m om
1 1
I. /6 Get Data Value Names Operation o, m om
1 1
I. /7 Get Data Value Type Operation o, m om
1 1 1 1
I. /8 IndicationPoint Object m , m m m
5 5 5 5
I. /9 ControlPoint Object m , m m m
I. /10 ProtectionEquipmentEvent Object o, o o o
NOTE – Either VCC-specific or ICC-specific scope must be supported by servers for block 1.
Table A.5 – Data sets
PICS Data sets Base F/S
proforma
reference
Client-CR Server-CR
1 1 1
I. /1 Data Set Model m m m
1
I. /2 VCC-specific scope (see note) o m o
1
I. /3 ICC-specific scope (see note) o m o
I. /4 Create Data Set Operation o o o
I. /5 Delete Data Set Operation o o o
1 1
I. /6 Get Data Set Element Values Operation o, m om
1 1
I. /7 Set Data Set Element Values Operation o, m om
1 1
I. /8 Get Data Set Names Operation o, m om
1 1
I. /9 Get Data Set Element Names Operation o, m om
NOTE – Either VCC-specific or ICC-specific scope must be supported by servers for block 1.
---------------------- Page: 12 ----------------------
60870-6-702 © IEC:1998 – 23 –
Table A.6 – Accounts
PICS Accounts Base F/S
proforma
reference
Client-CR Server-CR
8 8 8
I. /1 Account Model m m m
8 8 8
I. /2 Query Operation m m m
8 8 8
I. /3 TransferAccount Object m m m
8 8 8
I. /4 TransmissionSegment Object m m m
8 8 8
I. /5 ProfileValue Object m m m
I. /6 AccountRequest Object o o o
I. /7 DeviceOutage Object o o o
I. /8 AvailabilityReport Object o o o
I. /9 RealTimeStatus Object o o o
I. /10 ForecastSchedule Object o o o
I. /12 Curve Object o o o
I. /13 Power System Dynamic Objects o o o
Table A.7 – DS transfer sets
PICS DS transfer sets Base F/S
proforma
reference
Client-CR Server-CR
1 1 1
I. /1 Data Set Transfer Set Model m m m
1 1 1
I. /2 Start Transfer Operation m m m
1 1 1
I. /3 Stop Transfer Operation m m m
1 1 1
I. /4 Get Next DSTransfer Set Operation m m m
1 1
I. /5 IntervalTimeOut o, m om
2 2
I. /6 ObjectChange o, m om
1 1
I. /7 OperatorRequest (see note) o, m om
2 2
I. /8 IntegrityTimeout o, m om
1 1
I. /9 OtherExternalEvent (see note) o, m om
1 1
I. /10 EventCodeRequested (see note) o, m om
1 1 1
I. /11 Start Time m m m
1 1 1
I. /12 Interval m m m
2 2
I. /13 TLE o, m om
2 2
I. /14 Buffer Time o, m om
2 2
I. /15 Integrity Check o, m om
1 1
I. /16 DSConditions Requested o, m om
3 3
I. /17 Block Data o, m om
2 2
I. /18 Critical o, m om
2 2
I. /19 RBE o, m om
NOTE – Servers must support the processing of these parameters. This does not imply the presence
of the application.
---------------------- Page: 13 ----------------------
60870-6-702 © IEC:1998 – 25 –
Table A.8 – Time series transfer set objects
PICS Time series transfer set objects Base F/S
proforma
reference
Client-CR Server-CR
9 9 9
I. /1 Time Series Transfer Set Model m m m
9 9 9
I. /2 Get Next TSTransfer Set Operation m m m
9 9
I. /3 EndTimeArrived o,m om
9 9
I. /4 ReportIntervalTimeOut o,m om
9 9
I. /5 OperatorRequest o,m om
Table A.9 – Transfer account transfer set objects
PICS Transfer account transfer set objects Base F/S
proforma
reference
Client-CR Server-CR
8 8 8
I. /1 Transfer Account Transfer Set Model m m m
8 8
I. /2 BeforeTheHour o,m om
8 8
I. /3 DispatchUpdate o,m om
8 8
I. /4 DuringTheHour o,m om
8 8
I. /5 AfterTheHour o,m om
8 8
I. /6 ActualDataUpdate o,m om
8 8
I. /7 PastHours o,m om
8 8
I. /8 ObjectChange o,m om
8 8
I. /9 OperatorRequest o,m om
Table A.10 – Information message objects
PICS Information message objects Base F/S
proforma
reference
Client-CR Server-CR
4 4 4
I. /1 Information Message Transfer Set Model m m m
4 4 4
I. /1 InformationBuffer Object m m m
Table A.11 – Special transfer set objects
PICS Special transfer set objects Base F/S
proforma
reference
Client-CR Server-CR
1 1
I. /1 Transfer Set Name o,m om
I. /2 Next DSTransfer Set o o o
I. /3 Next TSTransfer Set o o o
1 1
I. /4 Event Code o,m om
1 1
I. /5 DS ConditionsDetected o,m om
1 1
I. /6 TS ConditionsDetected o,m om
1 1
I. /7 TA ConditionsDetected o,m om
1 1
I. /8 Transfer Set Time Stamp o,m om
---------------------- Page: 14 ----------------------
60870-6-702 © IEC:1998 – 27 –
Table A.12 – SBO devices
PICS Devices Base F/S
proforma
reference
Client-CR Server-CR
5 5 5
I. /1 Device Model m m m
5 5 5
I. /2 Select Operation m m m
5 5 5
I. /3 Operate Operation m m m
I. /4 Get Tag o o o
I. /5 Set Tag o o o
7 7
I. /6 Timeout Action o,m om
I. /7 Local Reset Action o o o
7 7
I. /8 Success Action o,m om
7 7
I. /9 Failure Action o,m om
Table A.13 – Programs
PICS Programs Base F/S
proforma
reference
Client-CR Server-CR
6 6 6
I. /1 Program Model m m m
6 6 6
I. /2 Start Operation m m m
6 6 6
I. /3 Stop Operation m m m
6 6 6
I. /4 Resume Operation m m m
6 6 6
I. /5 Reset Operation m m m
6 6 6
I. /6 Reset Operation m m m
6 6 6
I. /7 Kill Operation m m m
6 6
I. /8 Get Program Attributes Operation o,m om
Table A.14 – Event enrollments
PICS Event enrollments Base F/S
proforma
reference
Client-CR Server-CR
7 7 7
I. /1 Event Enrollment Model m m m
7 7 7
I. /2 Create Event Enrollment Operation m m m
7 7
I. /3 Delete Event Enrollment Operation o,m om
7 7
I. /5 Get Event Enrollment Attributes Operation o,m om
---------------------- Page: 15 ----------------------
60870-6-702 © IEC:1998 – 29 –
Table A.15 – Event conditions
PICS Event conditions Base F/S
proforma
reference
Client-CR Server-CR
7 7 7
I. /1 Event Condition Model m m m
7 7 7
I. /2 Event Notification Action m m m
1)
Table A.16 – Object models
PICS Object models Base F/S
proforma
reference
Client-CR Server-CR
1 1 1
I. /1 IndicationPoint Object m m m
5 5 5
I. /2 ControlPoint Object m m m
I. /3 ProtectionEquipmentEvent Object o o o
8 8 8
I. /4 TransferAccount Object m m m
8 8
I. /5 TransmissionSegment Object m ,o m o
8 8
I. /6 ProfileValue Object m ,o m o
I. /7 AccountRequest Object o o o
I. /8 DeviceOutage Object o o o
4 4 4
I. /9 InformationBuffer Object m m m
I. /10 AvailabilityReport Object o o o
I. /11 RealTimeStatus Object o o o
I. /12 ForecastSchedule Object o o o
I. /13 Curve Object o o o
I. /14 Power System Dynamic Objects o o o
________
1)
The object models shown here are defined in IEC 60870-6-802.
---------------------- Page: 16 ----------------------
60870-6-702 © IEC:1998 – 31 –
A.4 MMS
A.4.1 Supported MMS PDUs
Table A.17 – Environment and general management
Table A.17a
Reference MMS PDU Client-CR
Sending Receiving
Base F/S Base F/S
1 InitiateRequest o m o –
2 InitiateResponse o – o m
3 InitiateError o – o m
4 Conclud
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.