IEC 61850 4 Edition 2 0 2011 04 INTERNATIONAL STANDARD NORME INTERNATIONALE Communication networks and systems for power utility automation – Part 4 System and project management Réseaux et systèmes d[.]
Overview
The engineering of a utility automation system is based on a system requirement specification, which defines the scope, functions, boundaries and additional restrictions and requirements for the system, and includes:
The necessary hardware configuration of Unmanned Aerial Systems (UAS) involves defining the Interconnected Electronic Devices (IEDs) and their interfaces with each other and the surrounding environment, as illustrated in Figure 1 Additionally, it is essential to adapt functionality and signal quantities to meet specific operational requirements through the use of tailored parameters.
– the documentation of all specific definitions (i.e parameter set, terminal connections, etc.)
Primary equipment and auxiliaries Teleprotection
IED n IED x IED y IED 1 IED 2
Figure 1 – Structure of the UAS and its environment
The UAS, illustrated in Figure 1, comprises various IEDs that communicate through designated channels to perform tasks related to their interactions with the automation system's environment.
– the human as a local operator;
– process environment (PE) like switchgear, transformer, auxiliaries
– for the human machine interface (HMI):
• other IEDs with integrated HMIs;
– for the process environment (PE):
Categories and types of parameters
Classification
Parameters are data, which control and support the operation of:
– hardware configuration (composition of IEDs);
– process environment (primary equipment and auxiliaries);
– HMI with different supporting tools; and
– telecommunication environment in an automation system and its IEDs in such a way that the operations of the plant and cus- tomer specific requirements are fulfilled
The total set of parameters and configuration data of an UAS is termed the UAS-parameter set
It consists of the used parts of the parameter sets of all participating IEDs
With respect to handling methods and input procedure, parameter set contents is divided into two categories:
With respect to origin and function, the parameters are divided into types:
In Figure 2, the overview of the parameter structure is given
IED 1 - parameter set IED n - parameter set
System parameters Process parameters Functional parameters
Switchable parameters Non-switchable parameters
Figure 2 – Structure of UAS and IED parameters
The categories and types of parameters in Figure 2 are described below.
Parameter categories
The configuration parameters establish the overall behavior of the Unmanned Aerial System (UAS) and its Intelligent Electronic Devices (IEDs) Typically, these parameters are assigned values only during the initial setup, but they must be updated when the UAS is extended or undergoes functional changes.
Configuration parameters should be generated and modified offline, separate from the automation system's operation A temporary restriction on system operation is permissible during the input of these parameters.
In a more specific context, the term "parameter" refers to variables that determine desired behavior However, configuring systems and Intelligent Electronic Devices (IEDs) often requires more than just setting values To distinguish between these types of configurations, we use the term "configuration data" to describe more complex parameterizations, while "configuration parameters" refer solely to adjustments made through value settings.
The configuration parameters of an Intelligent Electronic Device (IED) encompass both system and process parameters Notably, the UAS configuration parameters are generally established at the system level, detailing or specifying the IED-related system parameters.
The operating parameters dictate the behavior of the system's partial functions and must be adjustable online during normal operations Modifications can be made without disrupting system functionality, provided they remain within specified parameter value ranges Additionally, protection functions integrated within Intelligent Electronic Devices (IEDs) should remain unaffected during the parameterization of other functions.
The initial parameterization or modification stage establishes the range and basic settings of these parameters, independent of the system's operation The operating parameters can be integrated into the system online.
– integrated service interface of the IEDs
The operating parameters usually include process and functional parameters, for example limit values, target values, command output times, delay times in switching sequences, etc.
Parameter types
System parameters are essential configuration data that dictate the operation of Intelligent Electronic Devices (IEDs), encompassing the system's internal structures and procedures in accordance with its technological capabilities and available components.
The system configuration data defines the hardware components' setup, including IEDs and their physical connections, outlines the communication procedures between IEDs such as protocol and baud rate, and specifies the necessary and available functions in the IED software at the station level.
Additionally, the system configuration data describes data flow relations between functions on different IEDs, for example interlocking, visualization of information in the substation single line diagram and others
Furthermore, the system configuration data includes the assignment of texts to events at the station level and the determination of data flows in the system, for example to
– telecommunication with network control centre or further substations
To ensure optimal performance, system parameter values must remain consistent across all components and Intelligent Electronic Devices (IEDs) This consistency should be upheld and verified using a comprehensive system configuration and parameterization tool at the system level.
Process parameters describe all types of information that is exchanged between the PE and the UAS
Process parameters significantly influence qualitative features at the process interface, including command output times, transient event suppression (filter time), measured value damping (threshold value), and the overall process characteristics, such as switch run times.
Furthermore, the process parameters include the assignment of texts to events for visualization at the IED-level
Functional parameters describe the qualitative and quantitative features of functionality used by the customer Normally, the functional parameters are changeable on-line
Functional parameters play a crucial role in defining the target values (set points) for controllers, as well as the starting and tripping conditions for protection relays They govern automatic sequences, such as operations triggered by measurement overflow or specific event commands Additionally, these parameters are essential for the algorithms that manage automatic control, protection, blocking, and adjustment processes.
The functional parameters are divided into switchable and non-switchable parameter value groups
An Intelligent Electronic Device (IED) can store multiple sets of functional parameter values simultaneously, but only one set is active at any given time It is essential to enable online switching between these sets of functional parameters.
Engineering tools
Engineering process
The system engineering process establishes the framework for designing and configuring an automation system tailored to the specific needs of a plant, such as a substation, while aligning with the customer's operational philosophy and system requirements specification.
Within the engineering process, we can distinguish different actor roles:
The project requirement engineer establishes the project's scope, boundaries, interfaces, functions, and specific requirements, including environmental conditions, reliability, and availability They outline the desired application and operational methods through a project requirement specification, ultimately accepting the delivered system.
The project design engineer establishes the system's architecture and specifications based on the requirements, detailing how the products will function together to meet the necessary criteria This process culminates in the creation of the system design specification.
– The manufacturer supplies the products from which the system is built If necessary, he supplies a project specific IED configuration
The system integrator is responsible for constructing the system by engineering the interaction between its components according to the design specifications and the available products from manufacturers, ultimately integrating these products into a functional system This process culminates in a detailed system configuration description.
The IED parameterizing engineer tailors the system and device configuration to optimize the process, functional, and system parameters of an IED, ensuring alignment with the specific characteristics of the project.
The testing and commissioning engineer evaluates the system according to its configuration description, design, requirements specification, and supplementary documentation, ultimately facilitating the system's operational launch.
A single individual or organization can assume multiple roles, such as a manufacturer also acting as a system integrator, or a customer performing system integration independently While this duality affects the packaging and formal structure, it does not alter the fundamental tasks that must be carried out.
The concrete engineering process relies on the responsibilities of various system components and their interrelations Even if a system integrator is also a manufacturer, they may need to incorporate products from other manufacturers Customers often require systems that interface with those of other clients, necessitating standardized data exchange across organizational boundaries.
A project typically begins with the project requirement engineer developing a project requirement specification that outlines the project's scope, including single line diagrams, device ratings, and other essential data This specification aims to establish a comprehensive set of technical requirements for tendering and engineering, applicable whether the design and installation are conducted in-house or outsourced It encompasses general interfacing requirements, such as naming conventions for primary and secondary equipment, as well as necessary communication addresses for system integration Additionally, it must detail redundancy needs, response times, availability, and safety measures, all while considering the project's environmental, physical, and geographical constraints.
IEC 61850-6 establishes a formal framework for defining single line diagrams that incorporate customer-specific functional names and the intended automation system functionalities for primary equipment outlined in the system specification description (SSD) This formal description adheres to the hierarchical structure of IEC 81346-1, allowing for customer-specific identifications and descriptive text instead of solely relying on IEC 81346-2 identifications Additionally, it provides a standardized method for exchanging function and communication-related interface descriptions between different systems and projects through a system exchange description (SED).
The project design engineer creates the functional and physical system architecture, including the communication system, to ensure required response times and reliability, producing a system design specification approved by the project requirement engineer This specification serves as a foundation for the product manufacturer to deliver the necessary products with the specified configuration It may include a formal description of Intelligent Electronic Devices (IEDs) and their functions, as outlined in IEC 61850-6 (SCD) The system integrator utilizes this specification to procure suitable products and construct the system Additionally, the manufacturer provides IEDs with a formal description of their functional and communication capabilities (ICD), which is essential for engineering the system configuration.
During the tendering process, the project design engineer typically creates an initial system design specification This preliminary specification, along with the system requirement specification, serves as the foundation for the project's system design.
The basic engineering process shown in Figure 3 starts with producing the system design specification (system design) based on the tender specification already approved by the project requirements engineer:
Figure 3 – Engineering tasks and their relationship
System design involves defining the technological framework necessary to address automation system tasks This includes selecting the appropriate structure, choosing the type of Intelligent Electronic Device (IED), configuring the IED, and establishing the interfaces between the IEDs and the Protection Equipment (PE) The outcome of this process is the system design specification.
During the configuration process, essential system functions are established or activated within a chosen group of Intelligent Electronic Devices (IEDs) This results in a collection of parameters that include both system and IED configuration data Depending on the capabilities of the IEDs, this task can be carried out in a pre-engineering phase by the manufacturer, the IED parameterization engineer, or the project design engineer.
Parameterization, often called detail engineering, is the generation of the parameter set for the
UAS The system configuration data (system parameter set) is produced by the system integra- tor The IED configuration data (IED parameter set) is produced by the IED parameterizing engineer
Documentation is the description of all project and parameterization agreements about the fea- tures of the system and its link to the PE according to the required standards
Engineering tools play a crucial role in efficiently managing engineering tasks To enhance interoperability among tools from various Intelligent Electronic Devices (IEDs) and manufacturers, the standard outlines three distinct types of tools.
– system specification tool: allows specifying the system and device requirements regarding the needed system functional and process capabilities;
System specification tool
During the project requirement phase, a system specification tool is utilized to formally describe the components of the process to be controlled, including process-related names and necessary functions This structured description aids in evaluating required products and serves as input for a system configuration tool in the design phase Typically, the tool relies on a template database that includes standardized functions, their required signals, and common process components.
The standard language defined in IEC 61850-6 offers a standardized description of a part of the system requirements specification.
System configuration tool
The system configuration tool facilitates the selection of components with specific functional assignments during the design phase of an automation system project Primarily based on an IED or solution database, it requires minimal input, such as the necessary functions and process signals Initial results are generated through tables and checklists, which must be validated by both the project requirements engineer and the project design engineer Consequently, the system structure and configuration, including interfaces to the PE, are established In the subsequent step, the system integrator configures the communication connections between the IEDs to ensure the desired system functionality is achieved.
The standard SCL language outlined in IEC 61850-6 facilitates the exchange of configuration data between system configuration tools and IED configuration tools, as well as among different projects of system configuration tools Additionally, it encompasses the functions and communication capabilities of IEDs, which can serve as external inputs for product selection within the system configuration tool.
This standard aims to facilitate the implementation of IED type and manufacturer-independent tools, allowing system configuration tasks to be performed regardless of the IEDs used It ensures that engineering results can be transferred to the respective IED tools in a standardized format To achieve this, a system configuration tool must be capable of importing IED descriptions and system interface descriptions in SCL, as well as exporting system configuration descriptions in SCL.
IED configuration tool
The IED configuration tool enables the creation of a consistent parameter set for a specific IED within the system, tailored to manufacturer or IED type It imports basic IED function specifications and system-related configuration data from the system configuration description generated by the system configuration tool To facilitate this, the IED configuration tool supports the import of system configuration descriptions in SCL language, as outlined in IEC 61850-6 Additionally, it allows for the implementation of special functions, settings, and IED-specific parameters.
The tool is designed to generate process data lists based on the IED parameter set while ensuring secure management of these lists Additionally, it must be capable of reading the current parameter values effectively.
Additionally, the tool supports the management, archiving and documentation of the IED pa- rameter set
Essential components of the tool are shown in Figure 4
IED configuration tool Input module Data management Output module
Process data lists for input into the UAS
IED parameter set for archive and modification management
The tool's data input module allows for both interactive parameter input and the import of system descriptions generated by the system configuration tool Input data must be organized in a technically structured manner that aligns with the substation architecture, following a hierarchical approach based on substation, voltage level, bay, equipment, and function.
To enhance efficiency and reduce redundancy, it is essential to minimize the repeated input of similar information This can be achieved by utilizing templates for standard solutions or employing copy functions, such as duplicating switch, bay, and busbar sections.
A parameter should only need to be entered once, with its assignment to other processes handled automatically to ensure consistent parameter usage at all times.
The data management module checks the entered parameter values with respect to their con- sistency and plausibility Parameters with multiple use will be assigned to the respective pro- cesses
Furthermore, the data management module includes the system information management with respect to the IED parameter set The system information contains a unique identification of the parameter set, including
– document identification and version identification;
– software releases of the IEDs and the parameterization tool;
– IED instance name in the project
The data management module creates process data lists that serve as the foundation for the automation system's behavior, aligning with both substation specifications and customer requirements.
The output module facilitates the transfer of process data lists to either an internal or external archive, or allows for direct input into the system and its Intelligent Electronic Devices (IEDs) It also enables users to recall and view source parameters stored in the archive, ensuring that the necessary source parameters are available for documentation purposes.
Documentation tool
The documentation tool generates uniform, project specific documentation in accordance with the required standards (IEC 61175, IEC 60848, IEC 81346 series, IEC 61082 series) The doc- umentation consists of:
– hardware documentation for the representation of all external connections between the system components and the PE which are defined in the project design process;
– software documentation in form of (principle) function charts, sequence diagrams, flow charts as needed;
– parameter documentation for the representation of all internal qualitative and quantitative relations, which are agreed in the parameterization process
The documentation tool should be capable of creating a “revision history”, documenting all changes known to the tool itself.
Flexibility and expandability
The flexibility and expandability of an automation system hinge on both the hardware and software configurations, as well as the functional and physical architecture Additionally, the interdependencies among the system's functional components play a crucial role in determining its overall adaptability.
To ensure the system's flexibility and expandability, it is essential to have a hardware configuration that can be easily extended with additional Intelligent Electronic Devices (IEDs) or IEDs that offer different functionalities.
The flexibility and expandability of automation systems are significantly influenced by engineering tools, particularly the IED configuration tool This essential tool manages various parameter sets related to the Intelligent Electronic Device (IED) and is often specific to a manufacturer or IED type Consequently, projects involving IEDs from multiple manufacturers may require several different IED configuration tools.
The functionality, compatibility, and expandability of the IED configuration tool are crucial for the system's future enhancements It must, at a minimum, support compatibility features for various versions of the standard outlined in IEC 61850-6 and all sections of IEC 61850-7.
The manufacturer's IED configuration tool must ensure backward compatibility, allowing users to parameterize all existing IEDs within the same family using the latest parameterization tool.
All configuration tools must operate on standard commercial hardware and operating systems They should facilitate flexible and consistent updates to existing parameter sets, complete with version identification.
The system configuration tool must offer open interfaces for seamless data exchange with various configuration tools, including those from dispatching centers and other manufacturers At a minimum, it should support the import and export of SCL files as specified in IEC 61850-6.
Scalability
The system configuration tool must support all standard UAS applications Typically, UAS systems are designed to encompass a wide array of applications through a modular device system.
– task (transmission or distribution network) and voltage range (medium, high or ultra high voltage) of the substation;
– completion level of the application (simple centralized telecontrol unit or integrated substation control, monitoring and protection with distributed artificial intelligence);
The functionality of systems ranges from basic SCADA operations to advanced automation tasks, highlighting their complexity Additionally, these systems incorporate telecommunication functions, which can vary from simple communication with a single dispatching center to more intricate node functionalities that utilize various telecommunication protocols Furthermore, they operate in a master mode, allowing for seamless integration with other substations.
The system configuration tool must enable scalability, allowing configuration tasks for various application levels to be performed efficiently with minimal resources and costs At the lowest level, it requires only basic parameter input for a simple telecommunication unit, while the highest level necessitates comprehensive management of all available system options.
Furthermore, the system configuration tool should support the engineering rationalization by using, for example, templates, macros and copy functions.
Automatic project documentation
General
The documentation of an UAS consists of two project specific components (see Figure 5)
Parameter documentation tool Configuration list
Function diagrams for internal features
Function diagrams for external equipment
Figure 5 – Project related documentation of UAS
The hardware documentation consists of:
– circuit diagrams for the link between the UAS components and for their connection with the PE;
– function diagrams for external schemes;
– cubicle layouts and wiring / cabling lists
The system and IED parameter documentation consists of:
– graphical representation of all displays and operation menu sequences;
– function diagrams or function descriptions
Engineering tools must generate documentation that includes: a) hardware documentation derived from the input values of the planning tool within a CAD or similar system; b) parameter documentation utilizing the IED parameter set from the parameterization tool; and c) system configuration documentation based on the system parameter set from the system configuration tool as required.
Signal lists serve as the critical interfaces between hardware and parameter documentation, necessitating uniform and unique signal identifiers in both documents It is recommended that these identifiers adhere to the semantically standardized definitions established in other sections of this standard.
The documentation generated from the planning and parameterization tool must maintain consistency with project checklists, IED parameter sets, and process data lists.
Hardware documentation
The hardware documentation of the system should be carried out according to the same struc- ture as the documentation of the other substation equipment
Concerning the identification and the structure of the hardware documentation the use of inter- national standards (for example, IEC 61175, IEC 81346 series) is recommended.
Parameter documentation
Parameter documentation is usually presented in lists and tables, accompanied by figures illustrating key solutions For improved clarity, it is advisable to create documentation for standard objects and functions, followed by a comprehensive list of object instances for each documented type.
The configuration list and the single line diagram of the substation are the starting point for the parameter documentation The configuration list consists of:
– an overview of IEDs and components of the system with identification of the hardware and software releases;
– identification of the software release of the configuration tool(s);
– identification of the parameter sets according to the requirements in 5.3.4
The parameter documentation is carried out in different ways for the different parameter types
The system parameters for the IEDs can be selected from the manufacturer's standard documentation and incorporated into the project-specific documentation These project-specific parameter sets are created using the system configuration tool, which also facilitates their documentation.
The documentation of process parameters includes a comprehensive description of all signals at the system boundary, along with details on their management and marshalling within the system Typically, this documentation set encompasses various descriptive documents related to process parameters.
Signal lists serve as the foundation for subsequent process parameter lists, providing a comprehensive overview of all analog and binary signals They detail the assignment of these signals to the inputs and outputs of the Intelligent Electronic Devices (IEDs) within the system, as well as their correlation to specific sections of the documentation.
– telecontrol mapping lists determine the assignment of individual signals to the addresses of the telecontrol protocol;
– message texts can be defined by the customer and assigned to the binary signals for representation in different reports;
– characteristic curves can be assigned to the analogue values;
– HMI lists describe the presentation features of signals on displays and printers;
– archiving lists cover all information about values of which signals have been archived under which conditions and with which attributes;
– acquisition lists include all information about qualitative attributes of signal acquisition such as filter times of binary inputs or command times
The functional parameters should be documented as parameter lists and graphically as func- tion diagrams
To provide greater clarity, and in accordance with the rules of circuit diagrams, the function diagrams should be structured as follows:
– control (automatic single and double commands, group commands, switching sequences); – position indication (assignment to commands, parallel work of transformers, voltage definition for busbar section);
– event/alarm indication (group information, automatic operation);
– algorithms for closed loop control;
The operation sequences and the structure and symbols of the overview and detail displays should be documented graphically
The number and type of report lists and protocols should be documented as a parameter list
Requirements concerning the design and the structure of the function diagrams are defined in international and national standards (for example, IEC 61082 series)
Document the operating parameters in a parameter list, including their value ranges and basic settings Additionally, record any values modified by the customer in the operations report.
Requirements of the documentation tool
The documentation tool utilizes the IED parameter set generated by the parameterization tool to create comprehensive parameter documentation This documentation is formatted as a book and includes an automatically generated table of contents.
The parameter documentation tool should be able to generate partial documentation according to different sorting criteria with practical benefit, for example:
– reference lists for telecontrol information;
– message lists, sorted by IED addresses;
All changes of parameters must be flagged in the documentation The parameter documenta- tion tool should be able to support the requirements with respect to such modification services.
Standard documentation
The standard documentation provides a universal description of the device and the functions of an Intelligent Electronic Device (IED) or the UAS product family from a manufacturer, remaining consistent and unchanged for specific projects.
As a general rule, the standard documentation includes:
– fault detection and maintenance instruction;
– user manual for the engineering tools
The standard documentation should complete the project specific documentation for each in- stalled system.
System integrator's support
In most cases, the engineering tasks are included in the system integrator’s offer for the UAS project
The system integrator must provide essential engineering tools for system maintenance and offer suitable customer training to ensure that clients can effectively maintain and expand their system installations.
The system integrator should support this process with consultative services, training and regu- lar information regarding updates and extended functionality of the system installation and the engineering tools
Requirements of product versions
The life cycles of an UAS and its IEDs are subject to differences of the manufacturer’s and the customer’s point of view, as shown in Figure 6:
– the manufacturer’s product life cycle contains the period between the start of production and the discontinuation of the UAS product family;
The customer’s system life cycle encompasses the duration from the initial commissioning of the first system installation, typically involving various UAS product families, to the decommissioning of the most recent system installation This installation process may be executed by a system integrator that is distinct from the product manufacturer.
Figure 6 – Two meanings of the system life cycle
During the manufacturer’s life cycle of the UAS and its IEDs, a number of changes and exten- sions are required for various reasons:
– technology changes in the hardware;
These changes lead to updated IED versions of hardware, software and supporting tools
A new version of an IED can produce different impacts:
The new version of the IED necessitates updates to the configuration compatibility list of the UAS-product family, as it requires version changes in other IEDs or the engineering tool to support new overarching functions Consequently, a system test involving the relevant IEDs is essential, resulting in an updated system configuration list.
The IED operates independently and is compatible with the existing configuration list It is essential to conduct a system test to ensure compatibility with other IEDs in the system Only the version of the IED will be updated, necessitating a modification of the system's configuration list version.
The manufacturer is obliged to provide identification of the IED versions:
– in the case of IED software or the supporting tools software, the version information is available in a self identifying manner (for example, on display or PC);
The hardware version information can be found at both the board and device levels In cases where functionality has changed or a feature has been removed, a new configuration compatibility list will be provided.
To ensure seamless coordination between the manufacturer’s and customer’s life cycles, new versions of IEDs with the same model numbers must adhere to specific guidelines Firstly, hardware compatibility is essential, requiring all interfaces to function identically and occupy the same locations, with uniform board and device sizes Secondly, any functional changes in the product software from previous versions must be clearly communicated Lastly, supporting tools must maintain downward compatibility, ensuring that new versions can support all existing iterations within the same product family.
The manufacturer has to inform the customer about all of the functional changes and exten- sions that are carried out between the last delivery and a new offer
From a UAS system maintenance standpoint, it is advisable to use identical or backward-compatible products for replacing failed components If functionally compatible but not engineering-compatible products are utilized, re-engineering of certain UAS parts may be required.
Announcement of product discontinuation
The manufacturer is to inform all customers of the product discontinuation in time to ensure that the customers have the option to order spare products or to prepare extensions
In the case where the product discontinuation will be carried out without a subsequent func- tionally compatible product, the required notice shall be published in a defined period in ad- vance
If a functionally compatible product is set to be released, the notice can be published with a shorter lead time A minimum overlap period for the delivery of both products is necessary, as illustrated in Annex A.
Support after discontinuation
Throughout the lifecycle of a system and its Intelligent Electronic Devices (IEDs), various changes, extensions, and maintenance challenges arise The manufacturer is responsible for providing support even after the UAS product family and its compatible IEDs are discontinued, as stipulated in the agreement between the system integrator, the customer, and the manufacturer Examples of such agreements can be referenced for clarity.
– special customer agreement for further supply with a minimum annual order with special agreed prices and delivery conditions in an agreed time period;
– supply of the same or compatible IEDs (from the point of view of functionality, mounting and wiring) for extensions under specific delivery conditions for an agreed time period;
– supply of spare parts and repair service under specific delivery conditions for an extended time period;
The administration, maintenance, and delivery of all versions of the IED software and service tool software are conducted in line with the manufacturer's agreed delivery conditions Customers are responsible for maintaining parameter sets, while support is provided for the integration of new products through adaptive interfaces.
An example for the corresponding time conditions is shown in Annex B
The above requirements concerning the “system life cycle” exclude the use of commercially available computing products (for example, PCs, CD ROMs)
In the case where the manufacturer and the system integrator are different, the support after discontinuation shall be agreed in relevant contracts
Division of responsibility
General
Quality assurance in a system involves collaboration between the system integrator or manufacturer and the customer, each having distinct responsibilities When multiple parties are involved, it is essential to clearly define the responsibilities of each party during the procurement process.
Responsibility of the manufacturer and system integrator
The manufacturer and the system integrator should establish and maintain a quality system in accordance with ISO 9001
The stages of quality assurance as a responsibility of the manufacturer and system integrator are shown in Figure 7
Market approval Delivery and putting online
Pr oduc t r eal iz at ion C ust om er 's l ife cyc le
Figure 7 – Stages of quality assurance – Responsibility of manufacturer and system integrator
The manufacturer must ensure proper handling of type tests and system tests for their products, as these tests are essential prerequisites for initiating regular deliveries.
All IEDs have to pass device specific routine tests defined by the manufacturer to ensure quali- ty before the products are handed over for delivery
Customer-specific verifications and approvals are essential and should align with the customer's philosophy, requiring negotiation between the system integrator and the customer These verifications may occur at both the product and system levels.
The system integrator must conduct specific investigations for both individual products and the overall system, ensuring compliance with technical requirements and performance criteria Additionally, an IED conformance test mitigates risks for the system integrator.
The system integrator is tasked with ensuring that all functions are thoroughly tested during the optional factory acceptance test (FAT) and the mandatory site acceptance test (SAT), involving both the integrator and customer representatives Prior to these tests, the system integrator must complete the necessary integration and commissioning phases Successful completion of the FAT is essential for equipment delivery and the subsequent SAT at the customer's location The specifics of the FAT and SAT, including their content, should be mutually agreed upon by the customer and the system integrator.
The system integrator is typically responsible for the on-site commissioning of the system prior to the Site Acceptance Test (SAT) Following commissioning, a trial operation phase, usually lasting one month, takes place The duration of this phase and specific conditions, such as whether the trial operation occurs before or after the SAT, should be negotiated between the customer and the system integrator.
Manufacturers must implement a quality assurance process to ensure that any product-related errors identified during project testing are addressed in subsequent product versions, as outlined in section 6.1.
7.1.2.3 Warranty and after sales service
After the site commissioning, the warranty begins in accordance with the agreed conditions for
During the warranty phase, any product faults identified that could affect other projects must be reported to the relevant system integrators and customers It is the customer's responsibility to determine whether to install a new version of the product.
After the warranty, the system integrator or the manufacturer should provide after sales ser- vice:
– the supply of spare parts for an agreed period;
– the support in diagnosing failures;
– the mandatory provision of urgent information to the customers about malfunctions;
– the correction of detected software errors and hardware defects;
– the offer and introduction of software updates
The manufacturer should develop and offer special diagnostic tools for
– failure definition inside or outside the system;
– failure localization inside the system and the individual IED’s
The diagnostic tools should be designed to be used remotely, if appropriate
The technical documentation of the system and its individual products shall include the recom- mended preventive maintenance (for example, for batteries, capacitors).
Responsibility of the customer
Customers must ensure that the environmental and operational conditions of the system align with the specifications outlined in the technical documentation for both the system and its individual components.
The customer has to carry out preventive maintenance for service or exchange of maintainable parts in accordance with the instructions of the manufacturer
Regular inspection and checks of individual products and their interconnected functions, such as protection circuit breakers, are essential These evaluations should be conducted periodically, following the guidelines set by the manufacturer or relevant standards organizations like IEE, VDEW, and IEEE.
Corrective maintenance should be carried out immediately after detection of defects, to obtain the highest possible availability.
Test equipment
General
Test equipment encompasses all necessary tools for acceptance testing and commissioning It is essential for verifying the inputs and outputs of primary equipment, ensuring communication with the network control center, and assessing the functionality of individual Intelligent Electronic Devices (IEDs) within the automation system, such as protection devices.
Test equipment is essential for demonstrating the behavior and performance characteristics of a system It is categorized into three types based on functionality and performance requirements.
– transient and fault process simulation;
Normal process test equipment
The test equipment must effectively deliver all alarms and position indications for the substation control system, simulate measured values (including over range), and display all commands from the UAS.
Advanced test equipment is essential for real-time simulation of switchgear reactions, enabling the assessment of dynamic processes like switching sequences and synchronization This equipment must generate diverse conditions, such as intermediate switchgear positions or simulating an earth fault on a busbar section during a switching sequence.
Test equipment should also be capable of generating a large quantity of data traffic in a short time or intermittent data traffic on a regular basis.
Transient and fault test equipment
The test equipment must be able to inject programmable voltage and current transients in a three-phase power system, effectively simulating various faults and abnormal processes, including power swings and current transformer saturation Additionally, it should generate simulated faults to create disturbance records.
Communication test equipment
This test equipment is used for performing tests at all communication channels for:
– internal links of the system;
The communication test system must serve as a convenient and efficient tool, facilitating essential functions across all necessary levels, including the network control center, substation, bay, and process level.
– simulation of a server, simulation of a client, monitoring of the data traffic;
– quality analysis of the data traffic (for example, the quality of electrical signals, time breaks, etc.).
Classification of quality tests
Basic test requirements
The manufacturer must deliver a comprehensive test concept that encompasses all activities, starting from prototype functional tests during the development phase to final type and system tests It is essential to define the scope and objectives of the tests, along with the test procedures and criteria for passing.
All tests shall be documented in such a way that the results are reproducible, if required
All tests must be conducted by a qualified internal team within the manufacturer’s organization, ensuring they have the independence to determine a product's compliance, or by an accredited external organization recognized by a third party.
System test
The system test verifies the correct functionality and performance of each Intelligent Electronic Device (IED) under various application conditions, including different configurations and parameters It also assesses the cooperation of IEDs within the overall UAS product families, utilizing all necessary tools for parameterization and diagnostics.
Function of each IED with various parameterization
Compatibility with other IEDs using various configuration and parameterization
Performance of single IED and the overall system
Figure 8 – Contents of system test
A successfully finished system test is the precondition for starting the type test.
Type test
The "fitness for use" of a newly designed product must be demonstrated through a type test conducted on samples from the manufacturing process This type test serves to verify the product against specified technical data.
Series product Approved firmware (system test)
Figure 9 – Contents of type test
The type test shall be carried out by the use of system tested software
The type test shall be passed before regular production delivery can be started.
Routine test
The routine test consists of special hardware and functionality tests as shown in Figure 10
Figure 10 – Contents of routine test
The routine tests should be carried out for each product before leaving the manufacturer.
Conformance test
The conformance tests are performed on the communication channels of IEDs and include the verification of the communication procedure in accordance with the standard or its parts (see IEC 61850-10).
Factory Acceptance Test (FAT)
The factory acceptance test (FAT) serves to validate and verify a system and its functions from the customer’s point of view The factory acceptance test is optional
The scope and objectives of the Factory Acceptance Test (FAT) must be collaboratively defined and documented in checklists by both the system integrator and the customer, with these checklists forming an integral part of the contract.
The result of the FAT should be documented and signed by both the system integrator and the customer
A Factory Acceptance Test (FAT) aims to evaluate standard solutions and their performance under both normal and abnormal conditions Additionally, process simulations enable testing for unusual process scenarios and potential failure situations.
Site Acceptance Test (SAT)
The primary objective of the Site Acceptance Test (SAT) is to verify the proper installation and connection of all system components This test is conducted on fully installed equipment and is performed in a series of individual steps.
Testing stage: process – network control centre
Process - bay control level Station control level – network control centre Bay control level – station control level
NOTE This is not a communication structure
Figure 11 – Testing stages for site acceptance test
Figure 11 shows four stages of SAT: a) process – bay control level; b) bay control level – station control level; c) station control level – network control centre(s); d) process – network control centre(s)
The stages are carried out according to a commissioning plan, which must cover the verifica- tion of all information exchanges and functions
The SAT procedure has to document the results of each step and summarizes the customer’s acceptance for putting the system into operation
Figure A.1.a – Without subsequent functionally compatible product
Figure A.1.b – Functionally compatible product follows
Delivery obligations after discontinuation (example)
Figure B.1 – Periods for delivery obligations
IEC 61850-10, Communication networks and systems in substations – Part 10: Conformance testing
ISO 9001:2008, Quality management systems – Requirements
The article outlines five key requirements related to the study, beginning with an overview and followed by a classification of parameters, which includes categories and types It discusses various study tools, detailing the study process and specifying system configuration tools, including the IED configuration tool and documentation tools The importance of flexibility, extensibility, and scalability in the study is emphasized, along with the need for automatic project documentation covering general aspects, hardware documentation, parameter documentation, and specific requirements for documentation tools Finally, it addresses standard documentation and the support provided by system integrators.
6 Cycle de vie du système 62 6.1 Exigences liées aux versions des produits 62 6.2 Annonce de l’arrêt de fabrication du produit 63 6.3 Support après l’arrêt de fabrication 64
Quality assurance involves a clear distribution of responsibilities among stakeholders, including the constructor, system integrator, and client Testing equipment plays a crucial role, encompassing general testing equipment, normal process testing, transient and fault testing, and communication testing Quality testing is classified into several categories, including basic testing requirements, system testing, type testing, individual series testing, and compliance testing.
7.3.6 Essai de réception usine (ERU) 70 7.3.7 Essai de réception sur site (ERS) 70 Annexe A (informative) Annonce de l’arrêt de la fabrication (exemple) 72 Annexe B (informative) Obligations de livraison après l’arrêt de la fabrication
The article presents a comprehensive overview of the Unmanned Aerial System (UAS) and its environment, detailing the structure of UAS parameters and Integrated Electronic Devices (IED) It outlines the study tasks and their interrelations, as well as the configuration process for IEDs Additionally, it includes project documentation for UAS and discusses the dual meanings of the system lifecycle The article emphasizes the quality assurance steps, highlighting the responsibilities of both the manufacturer and the system integrator It also covers the content of system testing, type testing, individual series testing, and the stages of site acceptance testing, along with conditions for announcements and delivery obligations.
RÉSEAUX ET SYSTÈMES DE COMMUNICATION POUR
Partie 4: Gestion du système et gestion de projet
1) La Commission Electrotechnique Internationale (CEI) est une organisation mondiale de normalisation composée de l'ensemble des comités électrotechniques nationaux (Comités nationaux de la CEI) La CEI a pour objet de favoriser la coopération internationale pour toutes les questions de normalisation dans les domaines de l'électricité et de l'électronique A cet effet, la CEI – entre autres activités – publie des Normes internationales, des Spécifications techniques, des Rapports techniques, des Spécifications accessibles au public (PAS) et des Guides (ci-après dénommés "Publication(s) de la CEI") Leur élaboration est confiée à des comités d'études, aux travaux desquels tout Comité national intéressé par le sujet traité peut participer Les organisations internationales, gouvernementales et non gouvernementales, en liaison avec la CEI, participent également aux travaux La CEI collabore étroitement avec l'Organisation Internationale de Normalisation (ISO), selon des conditions fixées par accord entre les deux organisations
2) Les décisions ou accords officiels de la CEI concernant les questions techniques représentent, dans la mesure du possible, un accord international sur les sujets étudiés, étant donné que les Comités nationaux de la CEI intéressés sont représentés dans chaque comité d’études
3) Les Publications de la CEI se présentent sous la forme de recommandations internationales et sont agréées comme telles par les Comités nationaux de la CEI Tous les efforts raisonnables sont entrepris afin que la CEI s'assure de l'exactitude du contenu technique de ses publications; la CEI ne peut pas être tenue responsable de l'éventuelle mauvaise utilisation ou interprétation qui en est faite par un quelconque utilisateur final
4) Dans le but d'encourager l'uniformité internationale, les Comités nationaux de la CEI s'engagent, dans toute la mesure possible, à appliquer de faỗon transparente les Publications de la CEI dans leurs publications nationales et régionales Toutes divergences entre toutes Publications de la CEI et toutes publications nationales ou régionales correspondantes doivent être indiquées en termes clairs dans ces dernières
5) La CEI elle-même ne fournit aucune attestation de conformité Des organismes de certification indépendants fournissent des services d'évaluation de conformité et, dans certains secteurs, accèdent aux marques de conformité de la CEI La CEI n'est responsable d'aucun des services effectués par les organismes de certification indépendants
6) Tous les utilisateurs doivent s'assurer qu'ils sont en possession de la dernière édition de cette publication
7) Aucune responsabilité ne doit être imputée à la CEI, à ses administrateurs, employés, auxiliaires ou mandataires, y compris ses experts particuliers et les membres de ses comités d'études et des Comités nationaux de la CEI, pour tout préjudice causé en cas de dommages corporels et matériels, ou de tout autre dommage de quelque nature que ce soit, directe ou indirecte, ou pour supporter les cỏts (y compris les frais de justice) et les dépenses découlant de la publication ou de l'utilisation de cette Publication de la CEI ou de toute autre Publication de la CEI, ou au crédit qui lui est accordé
8) L'attention est attirée sur les références normatives citées dans cette publication L'utilisation de publications référencées est obligatoire pour une application correcte de la présente publication
9) L’attention est attirée sur le fait que certains des éléments de la présente Publication de la CEI peuvent faire l’objet de droits de brevet La CEI ne saurait être tenue pour responsable de ne pas avoir identifié de tels droits de brevets et de ne pas avoir signalé leur existence
La Norme internationale CEI 61850-4 a été établie par le comité d’études 57 de la CEI: Gestion des systèmes de puissance et échanges d'informations associés
The second edition supersedes the first edition published in 2002, featuring a technical revision that aligns more closely with other parts of the IEC 61850 standards series Its scope extends beyond substation automation systems to encompass all automation systems for electric utility companies.
Le texte de la présente Norme est issu des documents suivants:
Le rapport de vote indiqué dans le tableau ci-dessus donne toute information sur le vote ayant abouti à l’approbation de la présente Norme
La présente publication a été rédigée selon les Directives ISO/CEI, Partie 2
A comprehensive list of all parts of the IEC 61850 series, titled "Communication Networks and Systems for Power Utility Automation," is available on the IEC website.
The committee has determined that the content of this publication will remain unchanged until the stability date specified on the IEC website at "http://webstore.iec.ch" in relation to the sought publication On that date, the publication will be updated.
• remplacée par une édition révisée, ou
RÉSEAUX ET SYSTÈMES DE COMMUNICATION POUR
Partie 4: Gestion du système et gestion de projet