GB/T 42151.5-2022 Communication networks and systems for power utility automation—Part 5:Communication requirements for functions and device models
GB/T 42151.5-2022 Communication networks and systems for power utility automation—Part 5:Communication requirements for functions and device models
Basic Information
Scope
This document specifies the communication between intelligent electronic devices (IEDs) and the related system requirements that are supported. This document applies to power automation systems centered on substation automation systems (SAS). The technical specifications in this document pertain to the communication requirements of various functions in power automation systems. Most of the functions and their communication requirements in this document originate from the field of substation automation. If applicable, they can be reused or expanded in other areas of power automation. It should be noted that the term "substation field" is sometimes used to replace the term "substation automation professional field," particularly when considering switchyard equipment (primary systems) and automation systems (secondary systems) simultaneously. The descriptions of the functions are not intended to standardize the functions themselves, but rather to identify the communication requirements between intelligent electronic devices within power systems (e.g., power plants and substations), between substations (e.g., line protection between substations), between power plants or substations and upper-level remote operation centers (e.g., grid control centers), and between maintenance centers. Additionally, the interface with remote technical services (e.g., maintenance centers) is also considered. The general scope of this document is the communication requirements of power automation systems, with the fundamental goal of achieving interoperability in all interactions and providing a seamless communication system for the entire power system management. The standardization of functions and their implementation is beyond the scope of this document. Therefore, it cannot be assumed that there is a single strategy for assigning functions to devices. To support the requirements arising from the free assignment of functions, this document defines the appropriate decomposition of functi