SIST HD 546.4 S1:1997
(Main)Telecontrol equipment and systems -- Part 4: Performance requirements
Telecontrol equipment and systems -- Part 4: Performance requirements
Deals with those characteristics which affect the performance of telecontrol systems and relates the characteristics to the application and processing functions. Establishes a set of rules to assess and specify the performance requirements of telecontrol systems; where feasible, performance classes have been specified for each of the properties covered.
Fernwirkeinrichtungen und Fernwirksysteme -- Teil 4: Anforderungen an die Leistungsmerkmale
Matériels et systèmes de téléconduite -- Partie 4: Prescriptions relatives aux performances
Traite des caractéristiques qui influencent les performances des systèmes de téléconduite et établit les rapports entre ces caractéristiques et les fonctions d'application et de traitement. Elle établit un ensemble de règles pour évaluer et spécifier les prescriptions relatives aux performances des systèmes de téléconduite; là où cela est possible, des classes de performances sont spécifiées.
Telecontrol equipment and systems - Part 4: Performance requirements (IEC 870-4:1990)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST HD 546.4 S1:1997
01-oktober-1997
Telecontrol equipment and systems - Part 4: Performance requirements (IEC 870-
4:1990)
Telecontrol equipment and systems -- Part 4: Performance requirements
Fernwirkeinrichtungen und Fernwirksysteme -- Teil 4: Anforderungen an die
Leistungsmerkmale
Matériels et systèmes de téléconduite -- Partie 4: Prescriptions relatives aux
performances
Ta slovenski standard je istoveten z: HD 546.4 S1:1992
ICS:
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve
...
This May Also Interest You
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.
- Standard52 pagesEnglish languagesale 10% offe-Library read for×1 day
- Corrigendum3 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 62325 specifies a UML package for the HVDC Link scheduling business
process and its associated document contextual models, assembly models and XML schemas
for use within the European style electricity markets.
This part of IEC 62325 is based on the European style market contextual model
(IEC 62325-351). The business process covered by this part of IEC 62325 is described in
Subclause 5.3.
The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been
contextualised into aggregated business information entities (ABIEs) to satisfy the requirements
of the European style market HVDC Link scheduling business process.
- Standard56 pagesEnglish languagesale 10% offe-Library read for×1 day
1.1 General
This International Standard is Part 100 of IEC 61968. It defines how messages may be exchanged between co-operating systems in order to facilitate the transfer of application-specific data. Such application-specific data include but are not limited to the message payloads defined in IEC 61968 (Parts 3-9 and Part 13), IEC 61970 and IEC 62325.
1.2 About This International Standard
This International Standard provides normative definitions for:
- a set of message archetypes (clause 5);
- a set of message exchange patterns that both sending and receiving systems are expected to implement (clause 6);
- the exact format of the messages that are to be transmitted over the various integration technologies including a precise description of the information that each message must contain (clause 7);
- a set of constraints and conventions to which applications must adhere in order to facilitate message exchange using IEC 61968-100 (clause 8);
- the details of how IEC 61968-100 messages should be implemented using various underlying transport mechanisms (clause 9).
1.3 What is not covered by this International Standard
Security considerations lie outside the scope of IEC 61968-100. This document defers to the IEC 62351 series for definitions and practices relating to the secure transmission of messages.
1.4 Future Considerations
1.4.1 Choice of Encoding Mechanisms
IEC 61968-100:2021 prescribes XML as the normative encoding mechanism for all messages defined by this International Standard.
Future editions of IEC 61968-100 may specify additional normative encoding methods including support for IEC 62361-104. The latter defines encodings to facilitate the exchange of information in the form of JSON documents whose semantics are defined by the IEC CIM and whose syntax is defined by an IETF JSON schema.
1.4.2 Choice of Web Service Technologies
IEC 61968-100:2021 provides normative definitions for the use of SOAP Web Services (clause 9.2) and Java Messaging Service (clause 9.3) for the transport of messages.
Future editions of IEC 61968-100 may specify additional normative web service technologies such as REST.
- Standard251 pagesEnglish languagesale 10% offe-Library read for×1 day
- Amendment9 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft530 pagesEnglish languagesale 10% offe-Library read for×1 day
The specifications of this document refer to general, respectively core, communication
requirements of the application functions in all domains of power utility automation systems.
Dedicated communication requirements and most examples of application functions in this
document are from the domain substation automation but may be reused in or extended to other
domains within power utility automation systems. Note that sometimes instead of the term
substation automation domain the term substation domain is used, especially if both the
switchyard devices (primary system) and the automation system (secondary system) are
regarded.
The description of the application functions is not used to standardize these functions, but to
identify communication requirements between Intelligent Electronic Devices (IEDs) hosting
these functions within plants and substations in the power system, between such stations (e.g.
between substation for line protection) and between the plant or substation and higher-level
remote operating places (e.g. network control centres) and maintenance places. In addition
interfaces to remote technical services (e.g. maintenance centres) are considered. The general
scope is the communication requirements for power utility automation systems. The basic goal
is interoperability for all interactions providing a seamless communication system for the overall
power system management. Another prerequisite for interoperability is a commonly defined
method for time synchronization.
Standardizing application functions and their implementation is completely outside the scope of
this document. Therefore, it cannot be assumed a single philosophy of allocating application
functions to devices. To support the resulting request for free allocation of these functions, a
proper breakdown of these functions into parts relevant for communication is defined. The
exchanged data and their required performance are defined.
The same or similar IEDs from substations like protective and control devices are found in other
domains like power plants also. Using this document for such devices in these plants facilitates
the system integration e.g. between the power plant control and the related substation
automation system. For some of such other application domains like wind power plants, hydro
power plants and distributed energy resources specific standard parts according to the
IEC 61850 series have been already defined and published.
- Amendment80 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 61970 belongs to the IEC 61970-450 to IEC 61970-499 series that, taken as a
whole, defines at an abstract level the content and exchange mechanisms used for data
transmitted between power system analyses applications, control centres and/or control centre
components.
The purpose of this document is to rigorously define the subset of classes, class attributes, and
roles from the CIM necessary to describe the result of state estimation, power flow and other
similar applications that produce a steady-state solution of a power network, under a set of use
cases which are included informatively in this document.
This document is intended for two distinct audiences, data producers and data recipients, and
can be read from those two perspectives. From the standpoint of model export software used
by a data producer, the document defines how a producer may describe an instance of a
network case in order to make it available to some other program. From the standpoint of a
consumer, the document defines what that importing software must be able to interpret in order
to consume power flow cases.
There are many different use cases for which use of this document is expected and they differ
in the way that the document will be applied in each case. Implementers are expected to
consider what use cases they wish to cover in order to know the extent of different options they
must cover. As an example, the profiles defined in this document will be used in some cases to
exchange starting conditions rather than solved conditions, so if this is an important use case,
it means that a consumer application needs to be able to handle an unsolved state as well as
one which has met some solution criteria
- Standard110 pagesEnglish languagesale 10% offe-Library read for×1 day
This document is one of the IEC 61970-450 to 499 series that, taken as a whole, defines at an abstract level the content and exchange mechanisms used for data transmitted between control centres and/or control centre components, such as power systems applications.
The purpose of this document is to define the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. The North American Electric Reliability Council (NERC) Data Exchange Working Group (DEWG) Common Power System Modelling group (CPSM) produced the original data requirements, which are shown in Annex E. These requirements are based on prior industry practices for exchanging power system model data for use primarily in planning studies. However, the list of required data has been extended starting with the first edition of this standard to facilitate a model exchange that includes parameters common to breaker-oriented applications. Where necessary this document establishes conventions, shown in Clause 6, with which an XML data file must comply in order to be considered valid for exchange of models.
This document is intended for two distinct audiences, data producers and data recipients, and may be read from two perspectives.
From the standpoint of model export software used by a data producer, the document describes a minimum subset of CIM classes, attributes, and associations which must be present in an XML formatted data file for model exchange. This standard does not dictate how the network is modelled, however. It only dictates what classes, attributes, and associations are to be used to describe the source model as it exists.
- Standard277 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 61850 defines the IEC 61850 information models to be used in the exchange
of information with distributed energy resources (DER) and Distribution Automation (DA)
systems. DERs include distribution-connected generation systems, energy storage systems,
and controllable loads, as well as facility DER management systems, including aggregated
DER, such as plant control systems, facility DER energy management systems (EMS), building
EMS, campus EMS, community EMS, microgrid EMS, etc. DA equipment includes equipment
used to manage distribution circuits, including automated switches, fault indicators, capacitor
banks, voltage regulators, and other power management devices.
The IEC 61850 DER information model standard utilizes existing IEC 61850-7-4 logical nodes
where possible, while defining DER and DA specific logical nodes to provide the necessary data
objects for DER and DA functions, including for the DER interconnection grid codes specified
by various countries and regions.
Although this document explicitly addresses distribution-connected resources, most of the
resource capabilities, operational functions, and architectures are also applicable to
transmission-connected resources
- Standard552 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 62488 applies to power line carrier terminals and networks used to transmit information over power networks including extra high, high and medium voltage (EHV/HV/MV) power lines using both digital and optionally analogue modulation systems in a frequency range between 16 kHz and 1 MHz (see also IEC 62488-1).
In many countries, power line carrier (PLC) channels represent a significant part of the utilityowned telecommunication system. A circuit normally routed via a PLC channel can also be routed via a channel using a different transmission medium such as point to point radio, optical fibre or open wire circuit.
It is therefore important that the input and output interfaces that are used between terminals in the communication system are standardised.
The issues requiring consideration of DPLC and/or APLC devices as parts of a telecommunication network can be found in IEC 62488-1.
Figure 1 shows the correspondence between the elements needed to implement PLC systems and the related International Standards.
- Standard80 pagesEnglish languagesale 10% offe-Library read for×1 day
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.