IEC TR 60663:1980
(Main)Planning of (single-sideband) power line carrier systems
General Information
- Abstract
Planning of (single-sideband) power line carrier systems
- Status
- Replaced
- Publication Date
- 31-Dec-1979
- Technical Committee
- TC 57 - Power systems management and associated information exchange
- Current Stage
- DELPUB - Deleted Publication
- Start Date
- 26-Apr-2021
- Completion Date
- 29-Jun-2018
Relations
- Effective Date
- 05-Sep-2023
- Effective Date
- 05-Sep-2023
- Effective Date
- 05-Sep-2023
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
IEC TR 60663:1980 is a standard published by the International Electrotechnical Commission (IEC). Its full title is "Planning of (single-sideband) power line carrier systems". This standard covers: Planning of (single-sideband) power line carrier systems
Planning of (single-sideband) power line carrier systems
IEC TR 60663:1980 is classified under the following ICS (International Classification for Standards) categories: 33.200 - Telecontrol. Telemetering. The ICS classification helps identify the subject area and facilitates finding related standards.
IEC TR 60663:1980 has the following relationships with other standards: It is inter standard links to IEC 62488-3:2021, IEC 62488-2:2017, IEC 62488-1:2012. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
IEC TR 60663:1980 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-avgust-1997
Planning of (single-sideband) power line carrier systems
Planning of (single-sideband) power line carrier systems
&RQFHSWLRQGHVV\VWþPHVĚFRXUDQWVSRUWHXUV ĚEDQGHODWpUDOHXQLTXH VXUOLJQHV
G
pQHUJLH
Ta slovenski standard je istoveten z: IEC 60663 Ed. 1.0
ICS:
29.240.20 Daljnovodi Power transmission and
distribution lines
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
----------------
...
This May Also Interest You
IEC PAS 61850-90-19:2026 document takes over the IEC 61850 data model specific definitions such as the definition of permissions and their assignment to roles from IEC 62351-8.
The general requirements for Role-Based Access Control (RBAC) are defined in IEC 62351-8. This part of IEC 61850, which is a Publicly Available Specification, applies those requirements to the IEC 61850 environment, including the RBAC modelling considerations, the impacts on IEC 61850 models and protocols, and the resulting engineering process requirements.
Additionally, the binding of permissions to objects is defined to allow an interoperable implementation regarding the semantic of roles. This is achieved by an assignment to unique data objects based on the SCL description. Note that for this, IEC 61850-6:2009+AMD1:2018+AMD2:2024 is a prerequisite as it defined a unique identification of objects in SCL.
- Technical specification70 pagesEnglish languagesale 15% off
- Standard4 pagesEnglish and French languagesale 15% off
IEC 62351-8:2026 is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (collectively called "subjects" in this document) to specified "roles", and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or-nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts' termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC thus provides a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user, a local and automated computer agent, or a built-in human machine interface (HMI) or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g., another object at another substation, a distributed energy resource at an end-user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document. This is achieved by defining two different encoding approaches to handle the definition of custom roles, either based on specific permissions or based on constraints to existing permissions. The definition on handling custom based roles was started in IEC 62351-90-1 and taken over into the IEC 62351-8:2020. Moreover, additionally to the definition of custom roles based on associated permissions, this document also includes options how to assign permissions to objects in a general way. Referencing documents will provide a mapping to a concrete data model to ensure an interoperability for standard roles used in different data models as well as for custom defined roles. Referencing documents might be standards such as IEC PAS 61850-90-19 or IEC 60870-5-7:2025 or also definitions by an operator.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks, such as:
– definition of usernames and password definitions/policies;
– management of keys and/or key exchange;
– engineering process of roles;
– assignment of roles;
– selection of trusted certification authorities issuing credentials (access tokens);
– defining the tasks of a security officer;
– integrating local policies in RBAC.
Existing standards (see ANSI INCITS 359-2004,
- Standard117 pagesEnglish languagesale 15% off
- Standard125 pagesFrench languagesale 15% off
IEC 61850-7-410:2026 specifies the logical node classes for use in the domain of hydroelectric power stations, steam and gas turbines.
This IEC61850 domain information model standard utilizes the existing Logical Node (LN) classes defined in IEC 61850-7-4, Basic communication structure – Compatible logical node classes and data object classes where possible, while defining new and extended domain specific LN classes to provide the necessary data objects for application to functions and systems in the domain of hydroelectric power stations, steam and gas turbines. The domain information model includes the interface towards a central operator centre’s control functions.
The Scope of this document, related to steam and gas turbine specifics, is limited to overall control functions and generator and turbine control functions. For hydroelectric power, the scope includes the entire power station automation system.
Edition 3 is intended to form a basis for extensions in local implementations. Such extensions may be defined in profiles. Many of the Logical Nodes defined in this document are designed to be suitable for use in domains beyond the scope of hydro power plants and steam and gas turbines. A suggested structure of the Logical Nodes into packages for integration with other domains is provided in Annex G (informative), Migration of this document to the future edition of IEC 61850.
This third edition cancels and replaces the second edition published in 2012 and Amendment 1:2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) New concepts and constructs for modelling of large power generation;
b) Addition of new Logical Nodes to cover systems and details of the power generation domain previously not modelled in a sufficient way;
c) Review of existing Logical Nodes concerning structure, use of Common Data Classes and naming;
d) Fixes and improvements of some names and descriptions of Data Objects;
e) Improvements of the structure and enumerations within the Domain Logical Nodes;
f) Addition of new Logical Nodes with respect to maintenance and supervision functionality;
g) Updating of Logical Nodes for PSS functionality (LNs: APSS, APST and APSF) reflecting the updated PSS standard IEEE 421.5:2016;
h) Incorporation of Amendment 1, including among other things the Group E Logical Nodes;
i) Resolutions to all known UML Issues related to IEC 61850-7-410;
j) This 3rd edition is autogenerated from the UML file;
k) Upon publication the updated IEC 61850-7-410 NameSpace will be made available as a Code Component on the TC57 web page.
In the Edition 3 of this document, a new modelling approach is applied. In order to achieve greater efficiency and harmonization of the IEC 61850 information model by streamlining the Namespaces it is divided into, the structure of the latest revisions of the Namespaces related to the power generation domain, aims to:
– share common concepts, approaches, and models in the generation domains,
– increase the modularity of the model itself and enable its extension.
This edition hence introduces a new modeling approach, which is further explained in Clause 5. The pillars upon which the new approach is founded are as follows:
– a layered architecture for the power station model, in accordance with the control hierarchy concepts defined in IEC 60050-351-55;
– a comprehensive review of the models considering the approach outlined in IEC 61850-7-420:2021, aimed at harmonizing fundamental concepts in the power generation domain;
– a systematic alignment with the concepts outlined in IEC 61850-7-500:2017.
Specific aspects typical of the large power generation domain are also addressed in the present document. The relationship between concepts described in this document and the ones of related standards can be found in Annex B and Annex C.
In addition to this objective, Edition 3 provides c
- Standard803 pagesFrench languagesale 15% off
- Standard1484 pagesEnglish and French languagesale 15% off
IEC 61850-80-5:2026, which is a Technical Report, specifies the mapping framework for building and configuring a system using both IEC 61850 and IEC 61158-6-15 (Industrial communication networks – Fieldbus specification, CPF Type 15, Modbus) protocols by utilizing gateways between IEC 61850 and IEC 61158-6-15 IEDs / subsystems. The objective is to enable operational run-time data exchange among these IEDs / subsystems, and to automate the configuration of a gateway as much as possible.
Please note that for the purposes of this document, "Modbus" is used to represent both serial Modbus (Modbus RTU) and IEC 61158-6-15 (Modbus TCP).
Within the capability of each protocol, some configuration attributes (IEC 61850-7-3:2010 and IEC 61850-7-3:2010/AMD1:2020 attributes with functional constraint CF) are also mapped in addition to the operational real-time data.
The frameworks specified in this document are based on the published standards and do not make any proposed changes to IEC 61850 or 61158-6-15. This standard does not specify any framework for an IEC 61850 IED to directly communicate with a Modbus IED and vice versa, except through a gateway.
This document does not mandate which data items that a particular IED will be supporting, regardless of whether the implementation uses Modbus or IEC 61850. Instead, this document provides a framework specifying how a gateway maps any given data item from Modbus into an IEC 61850 substation, including the control direction.
Similarly, this document does not mandate which mapping framework a given gateway will be supporting. When this document is republished as a Technical Specification, conformance requirements will be identified.
This document recognizes that there will be situations in which a user will require that a gateway perform non-standard protocol mappings. Non-standard mappings are outside the scope of this document.
This document also recognizes that gateways typically manipulate the data passing through them in a variety of ways. Some of these functions include alarm trigger grouping, data suppression, interlocking and command blocking. Conformance to this document does not preclude a gateway from performing such functions, even though this document primarily specifies "straight through" mapping of Modbus data to IEC 61850-7-3:2010 and IEC 61850-7-3:2010/AMD1:2020 data. Subclause 7.5 of this document describes how some of these functions can be specified to a gateway by a mapping tool using XML representations of conversion functions.
The mapping architecture for the exchange of the run-time information consists of four parts:
a) Conceptual architecture of a gateway and associated use case
b) Mapping of the information model (Assign semantic to the Modbus data)
c) Mapping of the data (which is in fact part of the information model)
d) Mapping of the services (out of scope for this document)
This second edition cancels and replaces the first edition published in 2024. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) deficiencies / missing text in Edition 1 corrected.
- Technical report49 pagesEnglish languagesale 15% off
CORRECTED VERSION 2026-02
IEC TR 61850-1-1:2026 which is a technical report, is applicable to power utility automation systems (PUAS). It defines the communication between intelligent electronic devices (IEDs) in such a system, and the related system requirements. This part gives an introduction and overview of the standard series. It refers to and might include text and figures coming from other parts of the standard series.
This document replaces the second edition of IEC TR 61850-1 published in 2013. The number has been changed from IEC TR 61850-1 to IEC TR 61850-1-1, as in the meantime there is also a document with the number IEC 61850-1-2. This edition constitutes a technical revision.
This edition includes the following significant changes with respect to the previous edition:
Updates to the TISSUE process.
Descriptions of the namespace concepts.
Renumbering the document from IEC 61850-1 to 61850-1-1.
This corrected version of IEC TR 61850-1-1:2026 incorporates the following correction:
– Addition of bibliographic reference numbers in the content
- Technical report32 pagesEnglish languagesale 15% off
IEC TR 63353:2026 provides the general architecture and system components for applying the IoT technology in power distribution networks. It describes the system architecture, system components and several typical applications in integration and intelligent management of power distribution networks.
- Technical report62 pagesEnglish languagesale 15% off
IEC 62351-7:2025 defines network and system management (NSM) data object models that are specific to power system operations. These NSM data objects will be used to monitor the health of networks and systems, to detect possible security intrusions, and to manage the performance and reliability of the information infrastructure. The goal is to define a set of abstract objects that will allow the remote monitoring of the health and condition of IEDs (Intelligent Electronic Devices), RTUs (Remote Terminal Units), DERs (Distributed Energy Resources) systems and other systems that are important to power system operations.
Power systems operations are increasingly reliant on information infrastructures, including communication networks, IEDs, and self-defining communication protocols. Therefore, management of the information infrastructure has become crucial to providing the necessary high levels of security and reliability in power system operations.
The telecommunication infrastructure that is in use for the transport of telecontrol and automation protocols is already subject to health and condition monitoring control, using the concepts developed in the IETF Simple Network Management Protocol (SNMP) standards for network management. However, power system specific devices (like teleprotection, telecontrol, substation automation, synchrophasors, inverters and protections) need instead a specific solution for monitoring their health.
The NSM objects provide monitoring data for IEC protocols used for power systems (IEC 61850, IEC 60870-5-104) and device specific environmental and security status. As a derivative of IEC 60870-5-104, IEEE 1815 DNP3 is also included in the list of monitored protocols. The NSM data objects use the naming conventions developed for IEC 61850, expanded to address NSM issues. For the sake of generality these data objects, and the data types of which they are comprised, are defined as abstract models of data objects.
In addition to the abstract model, in order to allow the integration of the monitoring of power system devices within the NSM environment in this part of IEC 62351, a mapping of objects to the SNMP protocol of Management Information Base (MIBs) is provided.
The objects that are already covered by existing MIBs are not defined here but are expected to be compliant with existing MIB standards. For example protocols including EST, SCEP, RADIUS, LDAP, GDOI are not in scope.
This edition of IEC 62351-7 cancels and replaces IEC 62351-7 published in 2017. This new edition constitutes a technical revision and includes the following significant technical changes with respect to IEC 62351-7:
a) Reviewed and enriched the NSM object data model;
b) UML model adopted for NSM objects description;
c) SNMP protocol MIBs translation included as Code Components
- Standard130 pagesEnglish languagesale 15% off
- Standard130 pagesEnglish languagesale 15% off
- Standard140 pagesFrench languagesale 15% off
- Standard140 pagesFrench languagesale 15% off
- Standard270 pagesEnglish and French languagesale 15% off
- Standard270 pagesEnglish and French languagesale 15% off
IEC TR 62746-2:2025, which is a technical report, describes the main pillars of interoperability to assist different IEC Technical Committees in defining their interfaces and messages covering the whole chain between a Smart Grid and Smart Home/Building/Industrial area.
The main topics of this document are:
– To describe an architecture model from a logical point of view;
– To describe a set of user stories that describe a number of situations related to energy flexibility and demand side management as well as an outline of potential upcoming Smart Building and Smart Home scenarios. The set of user stories does not have the ambition to list all home and building (energy) management possibilities, but is meant as a set of examples that are used as input in use cases and to check that the set of use cases is complete;
– To describe a set of use cases based on the user stories and architecture. The use cases describe scenarios in which the communication between elements of the architecture are identified;
– To further detail the communication, identified in the use cases, by describing the messages and information to be exchanged.
This document can also be used as a blueprint for further smart home solutions like remote control, remote monitoring, ambient assistant living and so forth.
This technical report will be regularly revised by introducing new use cases and updating the current use cases. The use cases presented in this document are not going to be included in the IEC Use Case Management Repository (UCMR). The data models of some use cases presented here are defined in the second edition of IEC 62746-4 . The smart grid architecture model presented in this document is created in coordination with IEC TC13, SC23, and TC57
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) The Architecture Model of the Smart Grid Coordination Group (Figure 6) has been replaced with the draft Architecture Model of TC57 in collaboration with SC23K and TC13;
b) The use cases from Edition 1 (2015) with the following IDs have been removed from the current document: JWG2000, JWG2001, JWG2010, JWG202x, JWG2041, JWG2042, JWG1111, WGSP2120, JWG30xx;
c) The use cases from Edition 1 (2015) with the following IDs: JWG1100, JWG1101, JWG-SPUC1102, and JWG1103 have been replaced with the use case JWG1100;
d) The following use cases have been added to the current document: JWG3000, JWG3001, JWG3002, JWG3003, JWG3004, JWG3005, JWG3006, JWG4000.
- Technical report229 pagesEnglish languagesale 15% off
IEC TR 61850-90-20:2025, which is a technical report, describes use cases of redundancy in systems.
This document considers use cases of duplication of function and devices and covers redundancy of information flow at message level. Functional safety is out of scope of this document. To keep focus on details relevant for this document, some figures and drawings do not show electrical wiring, redundant coils, etc, where this is not important for the use case.
This document is not a guideline on the design of redundancy systems; guidance on designing redundancy systems can be found in textbooks
- Technical report31 pagesEnglish languagesale 15% off