iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
CLC

EN 60870-5-101:2003/A1:2016

(Amendment)

Telecontrol equipment and systems - Part 5-101: Transmission protocols - Companion standard for basic telecontrol tasks

Telecontrol equipment and systems - Part 5-101: Transmission protocols - Companion standard for basic telecontrol tasks

Fernwirkeinrichtungen und -systeme - Teil 5-101: Übertragungsprotokolle - Anwendungsbezogene Norm für grundlegende Fernwirkaufgaben

Matériels et systèmes de téléconduite - Partie 5-101: Protocoles de transmission - Norme d'accompagnement pour les tâches élémentaires de téléconduite

Oprema in sistemi za daljinsko vodenje - 5-101. del: Protokoli prenosa - Spremljevalni standardi za osnovne naloge daljinskega vodenja - Dopolnilo A1

General Information

Status
Published
Publication Date
03-Mar-2016
Withdrawal Date
30-Dec-2018
ICS
33.200 - Telecontrol. Telemetering
Technical Committee
CLC/TC 57 - Power systems management and associated information exchange
Drafting Committee
IEC/TC 57 - IEC_TC_57
Current Stage
6060 - Document made available - Publishing
Start Date
04-Mar-2016
Completion Date
04-Mar-2016
Mandate
M/490 - Standardisation mandate to the European Standardisation Organisations (ESOs) to support European Smart Grid deployment
Ref Project
SIST EN 60870-5-101:2004/A1:2016 - Telecontrol equipment and systems - Part 5-101: Transmission protocols - Companion standard for basic telecontrol tasks

Relations

Amends
EN 60870-5-101:2003 - Telecontrol equipment and systems - Part 5-101: Transmission protocols - Companion standard for basic telecontrol tasks
Effective Date
03-Feb-2015

Buy Standard

EN 60870-5-101:2004/A1:2016EN 60870-5-101:2004/A1:2016
PreviousNext
Amendment
EN 60870-5-101:2004/A1:2016
English language
13 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-april-2016
Oprema in sistemi za daljinsko vodenje - 5-101. del: Protokoli prenosa -
Spremljevalni standardi za osnovne naloge daljinskega vodenja - Dopolnilo A1
Telecontrol equipment and systems - Part 5-101: Transmission protocols - Companion
standard for basic telecontrol tasks
Ta slovenski standard je istoveten z: EN 60870-5-101:2003/A1:2016
ICS:
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 60870-5-101:2003/A1

NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2016
ICS 33.200
English Version
Telecontrol equipment and systems -
Part 5-101: Transmission protocols - Companion standard for
basic telecontrol tasks
(IEC 60870-5-101:2003/A1:2015)
Matériels et systèmes de téléconduite -  Fernwirkeinrichtungen und -systeme -
Partie 5-101: Protocoles de transmission - Norme Teil 5-101: Übertragungsprotokolle - Anwendungsbezogene
d'accompagnement pour les tâches élémentaires de Norm für grundlegende Fernwirkaufgaben
téléconduite (IEC 60870-5-101:2003/A1:2015)
(IEC 60870-5-101:2003/A1:2015)
This amendment A1 modifies the European Standard EN 60870-5-101:2003; it was approved by CENELEC on 2015-12-31. CENELEC
members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this amendment the
status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This amendment exists in three official versions (English, French, German). A version in any other language made by translation under the
responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as
the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2016 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 60870-5-101:2003/A1:2016 E

European foreword
The text of document 57/1530/CDV, future IEC 60870-5-101:2003/A1, prepared by IEC/TC 57 "Power
system control and associated information exchange" was submitted to the IEC-CENELEC parallel
vote and approved by CENELEC as EN 60870-5-101:2003/A1:2016.

The following dates are fixed:
(dop) 2016-09-30
• latest date by which the document has to be
implemented at national level by
publication of an identical national
standard or by endorsement
• latest date by which the national (dow) 2018-12-31
standards conflicting with the
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.

Endorsement notice
The text of the International Standard IEC 60870-5-101:2003/A1:2015 was approved by CENELEC as
a European Standard without any modification.
IEC 60870-5-101 ®
Edition 2.0 2015-11
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
A MENDMENT 1
AM ENDEMENT 1
Telecontrol equipment and systems –

Part 5-101: Transmission protocols – Companion standard for basic telecontrol

tasks
Matériels et systèmes de téléconduite –

Partie 5-101: Protocoles de transmission – Norme d'accompagnement pour les

tâches élémentaires de téléconduite

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200 ISBN 978-2-8322-2996-5

– 2 – IEC 60870-5-101:2003/AMD1:2015
 IEC 2015
FOREWORD
This amendment has been prepared by IEC technical committee 57: Power systems
management and associated information exchange.
The text of this amendment is based on the following documents:
CDV Report on voting
57/1530/CDV 57/1592/RVC
Full information on the voting for the approval of this amendment can be found in the report
on voting indicated in the above table.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
_____________
IEC 60870-5-101:2003/AMD1:2015 – 3 –
 IEC 2015
4.3 Link layer
Replace the first sentence of the first paragraph of 4.3 with the following new text:
IEC 60870-5-2 defines a set of link transmission procedures using a control field and the
optional address field.
th
Replace the last sentence of the 5 paragraph of 4.3 with the following new text:
In addition a companion standard specifies the time-out interval (T ) of the primary station
o
(see A.1 of IEC 60870-5-2 for details of link timing).
Figure 5 – State transition diagram for unbalanced transmission primary to secondary
Replace (twice) in Figure 5 the phrase "Rx[error]/ and Trp not time out"
by the following new phrase:
"Rx[error and Trp not time out]"
Replace (twice) in Figure 5 the phrase "Rx[error]/Trp not time out/"
by the following new phrase:
"Rx[error and Trp not time out]"
Add, after Figure 6, the following new subclause heading:
6.2.1.2 Balanced transmission procedures
Replace the first sentence of the first paragraph of 6.2.1.2 by the following new text:
The request to the standardized function codes in primary direction (0 up to 3 and 9) have to
receive positive or negative responses.
7.1 Selections from IEC 60870-5-3: General structure of application data
rd
Add at the end of the 3 paragraph of 7.1, the following new text:
ASDU's containing no INFORMATION OBJECT are permitted too.
Additionally: In some cases the ASDU consist of the DATA UNIT IDENTIFIER only.
th
Replace the second sentence of the 6 paragraph of 7.1 by the following new text:
The COMMON ADDRESS is the station address, which permits the addressing of the whole
station or just a particular station sector.
7.2 Selections from IEC 60870-5-4: Definitions and coding of application information
elements
Add, at the end of 7.2, the following new text:
Mode 1 (least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively
in this companion standard.
– 4 – IEC 60870-5-101:2003/AMD1:2015
 IEC 2015
Table 9 – Semantics of TYPE IDENTIFICATION – Process information in control
direction
Replace the existing Note below Table 9 with the following new Note:
NOTE ASDUs marked (CON) in control direction are confirmed application services and have to be mirrored in
monitor direction with different causes of transmission. These mirrored ASDUs are used for positive/negative
acknowledgements (verifications). The causes of transmission are defined in 7.2.3.
Table 13 – Semantics of TYPE IDENTIFICATION – File transfer
Replace the existing Note below Table with the following new Note:
NOTE ASDUs marked (CON) in control direction are confirmed application services and have to be mirrored in
monitor direction with different causes of transmission. These mirrored ASDUs are used for positive/negative
acknowledgements (verifications). The causes of transmission are defined in 7.2.3.
7.2.3 Cause of transmission:
Replace the first sentence of the first paragraph of 7.2.3 with the following new text:
Octet 3 (and optionally Octet 4) of the DATA UNIT IDENTIFIER of the ASDU defines the
CAUSE OF TRANSMISSION field which is specified in the following.
7.2.3 Cause of transmission
Replace the subheading after Figure 14 with the following new numbered subheading:
7.2.3.1 Definition of the semantics of values of the CAUSE OF TRANSMISSION field
th
Replace the 6 paragraph of 7.2.3.1 with the following new text:
ASDUs marked (CON) in control direction are confirmed application services and shall be
mirrored in monitor direction with different CAUSES OF TRANSMISSION (see Tables 9, 11
and 12). The originator address directs these mirrored ASDUs and interrogated ASDUs in
monitor direction (e.g. interrogated by station interrogation) to the source that activated the
procedure.
th
Replace the 13 paragraph of 7.2.3.1 with the following new text:
ASDUs in the control direction and ASDUs defined for monitor direction used in reverse mode
(see clause 8. Interoperability) with not supported values in the data unit identifier (except the
variable structure qualifier) and the information object address are mirrored by the controlled
station with bit “P/N:= <1> negative confirm” and the following causes of transmission:
7.2.4 COMMON ADDRESS OF ASDUs:
Replace the first sentence of the first paragraph of 7.2.4 with the following new text:
Octet 4 and optionally Octet 5 (or – if the originator address is used – Octet 5 and optionally
Octet 6) of the DATA UNIT IDENTIFIER of the ASDU define the station address which is
specified in the following.
7.2.6.18 Seven octet binary time
Replace the paragraph beginning "The summer-time bit SU …" with the following new text:
The summer-time bit SU may optionally be used, but is not recommended. A time tag having
the SU flag set will indicate the same time value as time tag having the SU flag clear and
indicating a time value exactly one hour earlier. The use of the SU-Bit may be useful to assign

IEC 60870-5-101:2003/AMD1:2015 – 5 –
 IEC 2015
the correct hour to information objects which are generated during the first hour after
switching from summer-time to standard time.
7.2.6.21 Cause of initialization
Replace
COI := CP8{UI7[1.7],BS1[8]}   (Type 1.1)
UI7[1.7]<0.127>
with the following new text:
COI := CP8{UI7[1.7],BS1[8]}
UI7[1.7]<0.127>    (Type 1.1)
7.2.6.38 Status of file
Replace
SOF := CP8{STATUS,LFD,FOR,FA}
STATUS := UI5[1.5]<0.32>   (Type 1.1)
<0> := default
<1.15> := reserved for standard definitions of this companion standard
(compatible range)
<16.32>:= reserved for special use (private range)
with the following new text:
SOF := CP8{STATUS,LFD,FOR,FA}
STATUS := UI5[1.5]<0.31>   (Type 1.1)
<0> := default
<1.15> := reserved for standard definitions of this companion standard
(compatible range)
<16.31>:= reserved for special use (private range)
7.3.1.20 TYPE IDENT 20: M_PS_NA_1
Packed single-point information with status change detection
Add, at the end of 7.3.1.20, the following new Note:
NOTE OV within the QDS is not used in this Information Object and is always set to <0>.
Figure 50 – ASDU: M_PS_NA_1 Sequence of packed single-point information with status
change detection
Replace the description of Status change detection in Information Object j in Figure 50 with
the following new text:
SCD = Status + status change detection, 32 bit, defined in 7.2.6.40
Belongs to information object address A+16*(j-1)
7.3.4.2 TYPE IDENT 101:C_CI_NS_1
Counter interrogation command
Replace the following existing text:
CAUSE OF TRANSMISSION
in control direction:
– 6 – IEC 60870-5-101:2003/AMD1:2015
 IEC 2015
<6>:= activation
<8>:= deactivation
in monitor direction:
<7>:= activation confirmation
<9>:= deactivation confirmation
<10>:= activation termination
<44>:= unknown type identification
<45>:= unknown cause of transmission
<46>:= unknown common address of ASDU
<47>:= unknown information object address
with the following new text:
CAUSE OF TRANSMISSION
in control direction:
<6>:= activation
in monitor direction:
<7>:= activation confirmation
<10>:= activation termination
<44>:= unknown type identification
<45>:= unknown cause of transmission
<46>:= unknown common address of ASDU
<47>:= unknown information object address
Figure 79 – ASDU – P_ME_NA_1 Parameter of measured values, normalized value
Replace, in Figure 79 within the last Octet of the ASDU figure,"UI8" with "CP8".
Figure 80 – ASDU: P_ME_NB_1 Parameter of measured values, scaled value
Replace, in Figure 80 within the last Octet of the ASDU figure, "UI8" by "CP8"
7.4 Selections from IEC 60870-5-5: Basic application functions
st
Replace, in the 1 paragraph of 7.4, "General interrogation (6.6)" with "General interrogation,
Outstation interrogation (6.6)"
7.4.5 Selection from station interrogation, outstation interrogation
rd
Replace, in the 3 paragraph after Table 17, "general interrogation" with "station
interrogation"
7.4.6 Selections from clock synchronization
Replace the last sentence of the 3rd paragraph of 7.4.6 with the following new text:
The summer-time bit SU shall be set to <0> if summer-time is not used.
7.4.11.1 General addressing structure of file transfer
7.4.11.1.1 In
...

Questions, Comments and Discussion

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

This May Also Interest You

CLC
EN IEC 61968-9:2024(Main)
Enterprise business function interfaces for utility operations - Part 9: Interfaces for meter reading and control
SIST EN IEC 61968-9:2024

IEC 61968-9:2024 specifies the information content of a set of message types that can be used to support many of the business functions related to meter reading and control. Typical uses of the message types include meter reading, controls, events, customer data synchronization and customer switching. Although intended primarily for electrical distribution networks, IEC 61968-9 can be used for other metering applications, including non-electrical metered quantities necessary to support gas and water networks. The purpose of this document is to define a standard for the integration of metering systems (MS), which includes traditional manual systems, and (one or two-way) automated meter reading (AMR) systems, and meter data management (MDM) systems with other enterprise systems and business functions within the scope of IEC 61968. The scope of this document is the exchange of information between metering systems, MDM systems and other systems within the utility enterprise. The specific details of communication protocols those systems employ are outside the scope of this document. Instead, this document will recognize and model the general capabilities that can be potentially provided by advanced and/or legacy meter infrastructures, including two-way communication capabilities such as load control, dynamic pricing, outage detection, distributed energy resource (DER) control signals and on-request read. In this way, this document will not be impacted by the specification, development and/or deployment of next generation meter infrastructures either through the use of standards or proprietary means. The focus of IEC 61968-9 is to define standard messages for the integration of enterprise applications, these messages may be directly or indirectly related to information flows within a broader scope. Examples would include messaging between head end systems and meters or PAN devices. The various components described later in this document will typically fall into either the category of a metering system (MS) head end, an MDM or other enterprise application (e.g. OMS, DRMS, CIS). The capabilities and information provided by a meter reading and meter data management systems are important for a variety of purposes, including (but not limited to) interval data, time-based demand data, time-based energy data (usage and production), outage management, service interruption, service restoration, quality of service monitoring, distribution network analysis, distribution planning, demand response, customer billing and work management. This standard also extends the CIM (Common Information Model) to support the exchange of meter data. This third edition cancels and replaces the second edition published in 2013. This edition constitutes a technical revision. Please see the foreword of IEC 61968-9 for further details.

  • Standard
    359 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 61970-457:2024(Main)
Energy management system application program interface (EMS-API) - Part 457: Dynamics profile
SIST EN IEC 61970-457:2024

IEC 61970-457:2024 specifies a standard interface for exchanging dynamic model information needed to support the analysis of the steady state stability (small-signal stability) and/or transient stability of a power system or parts of it. The schema(s) for expressing the dynamic model information are derived directly from the CIM, more specifically from IEC 61970-302. The scope of this document includes only the dynamic model information that needs to be exchanged as part of a dynamic study, namely the type, description and parameters of each control equipment associated with a piece of power system equipment included in the steady state solution of a complete power system network model. Therefore, this profile is dependent upon other standard profiles for the equipment as specified in IEC 61970-452: CIM static transmission network model profiles, the topology, the steady state hypothesis and the steady state solution (as specified in IEC 61970-456: Solved power system state profiles) of the power system, which bounds the scope of the exchange. The profile information described by this document needs to be exchanged in conjunction with IEC 61970-452 and IEC 61970-456 profiles’ information to support the data requirements of transient analysis tools. IEC 61970-456 provides a detailed description of how different profile standards can be combined to form various types of power system network model exchanges. This document supports the exchange of the following types of dynamic models: • standard models: a simplified approach to exchange, where models are contained in predefined libraries of classes interconnected in a standard manner that represent dynamic behaviour of elements of the power system. The exchange only indicates the name of the model along with the attributes needed to describe its behaviour. • proprietary user-defined models: an exchange that would provide users the ability to exchange the parameters of a model representing a vendor or user proprietary device where an explicit description of the model is not described in this document. The connections between the proprietary models and standard models are the same as described for the standard models exchange. Recipient of the data exchange will need to contact the sender for the behavioural details of the model. This document builds on IEC 61970-302, CIM for dynamics which defines the descriptions of the standard dynamic models, their function block diagrams, and how they are interconnected and associated with the static network model. This type of model information is assumed to be pre-stored by all software applications hence it is not necessary to be exchanged in real-time or as part of a dynamics model exchange. This second edition cancels and replaces the first edition published in 2021. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) The majority of issues detected in IEC 61970-302:2018 and fixed in IEC 61970-302:2022 led to update of this document; b) IEEE 421.5-2016 on Excitation systems is fully covered; c) IEEE turbine report from 2013 was considered and as a result a number of gas, steam and hydro turbines/governors are added; d) IEC 61400-27-1:2020 on wind turbines is fully incorporated; e) WECC Inverter-Based Resource (IBR) models, Hybrid STATCOM models and storage models are added; f) The user defined models approach was enhanced in IEC 61970-302:2022 adding a model which enables modelling of a detailed dynamic model. This results in the creation of two additional pr

  • Standard
    780 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 61970-302:2024(Main)
Energy management system application program interface (EMS-API) - Part 302: Common information model (CIM) dynamics
SIST EN IEC 61970-302:2024

IEC 61970-302:2024 specifies a Dynamics package which contains part of the CIM to support the exchange of models between software applications that perform analysis of the steady-state stability (small-signal stability) or transient stability of a power system as defined by IEEE / CIGRE, Definition and classification of power system stability IEEE/CIGRE joint task force on stability terms and definitions. The model descriptions in this document provide specifications for each type of dynamic model as well as the information that needs to be included in dynamic case exchanges between planning/study applications. The scope of the CIM Dynamics package specified in this document includes: • standard models: a simplified approach to describing dynamic models, where models representing dynamic behaviour of elements of the power system are contained in predefined libraries of classes which are interconnected in a standard manner. Only the names of the selected elements of the models along with their attributes are needed to describe dynamic behaviour. • proprietary user-defined models: an approach providing users the ability to define the parameters of a dynamic behaviour model representing a vendor or user proprietary device where an explicit description of the model is not provided by this document. The same libraries and standard interconnections are used for both proprietary user-defined models and standard models. The behavioural details of the model are not documented in this document, only the model parameters. • A model to enable exchange of models’ descriptions. This approach can be used to describe user defined and standard models. • A model to enable exchange of simulation results. This second edition cancels and replaces the first edition published in 2018. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) The majority of issues detected in IEC 61970-302:2018 are addressed; b) IEEE 421.5-2016 on Excitation systems is fully covered; c) The IEEE turbine report from 2013 was considered and as a result a number of gas, steam and hydro turbines/governors are added; d) IEC 61400-27-1:2020 on wind turbines is fully incorporated; e) WECC Inverter-Based Resource (IBR) models, Hybrid STATCOM models and storage models are added; f) The user defined models are enhanced with a model which enables modelling of detailed dynamic model; g) A model to enable exchange of simulation results is added; h) The work on the HVDC models is not complete. The HVDC dynamics models are a complex domain in which there are no models that are approved or widely recognised on international level, i.e. there are only project-based models. At this stage IEC 61970-302:2022 only specifies some general classes. However, it is recognised that better coverage of HVDC will require a further edition of this document; i) Models from IEEE 1547-2018 "IEEE Standard for Interconnection and Interoperability of Distributed Energy Resources with Associated Electric Power Systems Interfaces" are added. j) Statements have been added to certain figures, tables, schemas, and enumerations throughout the document that indicate that they are reproduced with the permission of the UCA International User Group (UCAIug). These items are derived from the CIM.

  • Standard
    894 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN 60870-5-104:2006/A1:2016/AC:2023-09(Corrigendum)
Telecontrol equipment and systems - Part 5-104: Transmission protocols - Network access for IEC 60870-5-101 using standard transport profiles
SIST EN 60870-5-104:2007/A1:2017/AC:2024
  • Corrigendum
    3 pages
    English and French language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 62351-9:2023(Main)
Power systems management and associated information exchange - Data and communications security - Part 9: Cyber security key management for power system equipment
SIST EN IEC 62351-9:2023

IEC 62351-9:2023 specifies cryptographic key management, primarily focused on the management of long-term keys, which are most often asymmetric key pairs, such as public-key certificates and corresponding private keys. As certificates build the base this document builds a foundation for many IEC 62351 services (see also Annex A). Symmetric key management is also considered but only with respect to session keys for group-based communication as applied in IEC 62351-6. The objective of this document is to define requirements and technologies to achieve interoperability of key management by specifying or limiting key management options to be used. This document assumes that an organization (or group of organizations) has defined a security policy to select the type of keys and cryptographic algorithms that will be utilized, which may have to align with other standards or regulatory requirements. This document therefore specifies only the management techniques for these selected key and cryptography infrastructures. This document assumes that the reader has a basic understanding of cryptography and key management principles. The requirements for the management of pairwise symmetric (session) keys in the context of communication protocols is specified in the parts of IEC 62351 utilizing or specifying pairwise communication such as: • IEC 62351-3 for TLS by profiling the TLS options • IEC 62351-4 for the application layer end-to-end security • IEC TS 62351-5 for the application layer security mechanism for IEC 60870-5-101/104 and IEEE 1815 (DNP3) The requirements for the management of symmetric group keys in the context of power system communication protocols is specified in IEC 62351-6 for utilizing group security to protect GOOSE and SV communication. IEC 62351-9 utilizes GDOI as already IETF specified group-based key management protocol to manage the group security parameter and enhances this protocol to carry the security parameter for GOOSE, SV, and PTP. This document also defines security events for specific conditions which could identify issues which might require error handling. However, the actions of the organisation in response to these error conditions are beyond the scope of this document and are expected to be defined by the organizations security policy. In the future, as public-key cryptography becomes endangered by the evolution of quantum computers, this document will also consider post-quantum cryptography to a certain extent. Note that at this time being no specific measures are provided. This second edition cancels and replaces the first edition published in 2017. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Certificate components and verification of the certificate components have been added; b) GDOI has been updated to include findings from interop tests; c) GDOI operation considerations have been added; d) GDOI support for PTP (IEEE 1588) support has been added as specified by IEC/IEEE 61850-9-3 Power Profile; e) Cyber security event logging has been added as well as the mapping to IEC 62351-14; f) Annex B with background on utilized cryptographic algorithms and mechanisms has been added.

  • Standard
    147 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 62351-3:2023(Main)
Power systems management and associated information exchange - Data and communications security - Part 3: Communication network and system security - Profiles including TCP/IP
SIST EN IEC 62351-3:2023

IEC 62351-3:2023 specifies how to provide confidentiality, integrity protection, and message level authentication for protocols that make use of TCP/IP as a message transport layer and utilize Transport Layer Security when cyber-security is required. This may relate to SCADA and telecontrol protocols, but also to additional protocols if they meet the requirements in this document. IEC 62351-3 specifies how to secure TCP/IP-based protocols through constraints on the specification of the messages, procedures, and algorithms of Transport Layer Security (TLS) (TLSv1.2 defined in RFC 5246, TLSv1.3 defined in RFC 8446). In the specific clauses, there will be subclauses to note the differences and commonalities in the application depending on the target TLS version. The use and specification of intervening external security devices (e.g., "bump-in-the-wire") are considered out-of-scope. In contrast to previous editions of this document, this edition is self-contained in terms of completely defining a profile of TLS. Hence, it can be applied directly, without the need to specify further TLS parameters, except the port number, over which the communication will be performed. Therefore, this part can be directly utilized from a referencing standard and can be combined with further security measures on other layers. Providing the profiling of TLS without the need for further specifying TLS parameters allows declaring conformity to the described functionality without the need to involve further IEC 62351 documents. This document is intended to be referenced as a normative part of other IEC standards that have the need for providing security for their TCP/IP-based protocol exchanges under similar boundary conditions. However, it is up to the individual protocol security initiatives to decide if this document is to be referenced. The document also defines security events for specific conditions, which support error handling, security audit trails, intrusion detection, and conformance testing. Any action of an organization in response to events to an error condition described in this document are beyond the scope of this document and are expected to be defined by the organization’s security policy. This document reflects the security requirements of the IEC power systems management protocols. Should other standards bring forward new requirements, this document may need to be revised. This second edition cancels and replaces the first edition published in 2014, Amendment 1:2018 and Amendment 2:2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Inclusion of the TLSv1.2 related parameter required in IEC 62351-3 Ed.1.2 to be specified by the referencing standard. This comprises the following parameter: • Mandatory TLSv1.2 cipher suites to be supported. • Specification of session resumption parameters. • Specification of session renegotiation parameters. • Revocation handling using CRL and OCSP. • Handling of security events. b) Inclusion of a TLSv1.3 profile to be applicable for the power system domain in a similar way as for TLSv1.2 session.

  • Standard
    52 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    52 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN 62488-2:2017/AC:2023-03(Corrigendum)
Power line communication systems for power utility applications - Part 2: Analogue power line carrier terminals or APLC
SIST EN 62488-2:2017/AC:2023
  • Corrigendum
    3 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 62351-5:2023(Main)
Power systems management and associated information exchange - Data and communications security - Part 5: Security for IEC 60870-5 and derivatives
SIST EN IEC 62351-5:2023

This part of IEC 62351 defines the application authentication mechanism (A-profile) specifying messages, procedures and algorithms for securing the operation of all protocols based on or derived from IEC 60870-5: Telecontrol Equipment and Systems - Transmission Protocols. This Standard applies to at least those protocols listed in Table 1. [Table 1] The initial audience for this International Standard is intended to be the members of the working groups developing the protocols listed in Table 1. For the measures described in this standard to take effect, they must be accepted and referenced by the specifications for the protocols themselves. This document is written to enable that process. The working groups in charge of take this standard to the specific protocols listed in Table 1 may choose not to do so. The subsequent audience for this specification is intended to be the developers of products that implement these protocols. Portions of this standard may also be of use to managers and executives in order to understand the purpose and requirements of the work. This document is organized working from the general to the specific, as follows: - Clauses 2 through 4 provide background terms, definitions, and references. - Clause 5 describes the problems this specification is intended to address. - Clause 6 describes the mechanism generically without reference to a specific protocol. - Clauses 7 and 8 describe the mechanism more precisely and are the primary normative part of this specification. - Clause 9 define the interoperability requirements for this authentication mechanism. - Clause 10 describes the requirements for other standards referencing this specification Unless specifically labelled as informative or optional, all clauses of this specification are normative.

  • Standard
    126 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN IEC 61970-401:2022(Main)
Energy management system application program interface (EMS-API) - Part 401: Profile framework
SIST EN IEC 61970-401:2022

This document describes how IEC 61970-450 (all parts), IEC 61970-600 (all parts) profile specifications are structured and created. Profile specifications describe a subset of the Canonical CIM dedicated to a specific data exchange. The Canonical CIM is described in IEC 61970-300 (all parts) as well as in IEC 61968-11. Rules for creation or extension of Canonical CIM are outside the scope of this document. This document specifies the structure of a profile specification and the rules for selecting subsets of information from the Canonical CIM. It standardizes the operations used to create the profile elements from the Canonical CIM. As Canonical CIM is described in UML the operations are described in terms of UML classes, attributes, and roles. It is possible to map UML to RDFS or OWL, so any of the languages UML, RDFS or OWL can be used to describe the created profiles. Specification of languages (UML, RDFS or OWL) used to describe profiles as well as how profiles are presented and edited in user interfaces are outside the scope of this document. Languages used to describe profiles are specified in other specifications. Relevant specifications are referenced in Clause 2. UML supports adding free text that describes further restrictions on UML constructs, e.g. classes, attribute values, association roles and cardinalities. Languages such as OCL and SHACL are dedicated to describing constraints. OCL is used to describe constraints for object data described in UML while SHACL is used to describe constraints on graph data described by RDFS or OWL. OCL is within the scope of this document, but SHACL is not. This document supports profiles describing data exchanged as CIMXML datasets or messages. The exchange format within the scope is in accordance with IEC 61970-552 but other formats are possible. Tool interoperability and serialisation formats are outside the scope of this document.

  • Standard
    36 pages
    English language
    sale 10% off
    e-Library read for
    1 day
CLC
EN 61850-5:2013/A1:2022(Amendment)
Communication networks and systems for power utility automation - Part 5: Communication requirements for functions and device models
SIST EN 61850-5:2013/A1:2022

PUBLICATION EXPECTED BY 2022-04-27

  • Amendment
    80 pages
    English language
    sale 10% off
    e-Library read for
    1 day