M/490 - Smart Grid

The purpose of this document is to provide technical guidance for tests on generating units and interface protection to evaluate their electrical characteristics.
NOTE 1    Mechanical issues are taken into account as far as they influence the electrical characteristics.
The evaluation results are intended to be used to demonstrate conformity of generating units to technical requirements for grid connection. In this context the evaluation results can also be used as part of a certification programme.
NOTE 2    Besides the type test results of the generating unit all additional elements for connection to the grid (e.g. transformer, cabling, multiple units) are considered in the evaluation of the final installation of a generating plant.
The requirements to be evaluated are covered in the following standardization documents:
–   EN 50549 1:2019: Requirements for generating plants to be connected in parallel with distribution networks - Part 1: connection to a LV distribution network - Generating plants up to and including Type B
–   EN 50549 2:2019: Requirements for generating plants to be connected in parallel with distribution networks - Part 2: Connection to a MV distribution network - Generating plants up to and including Type B
If grid connection requirements are dealt with in other documents or for other generating module types, where no specific testing procedure is provided, testing methods of this document can be used if applicable.
This document provides evaluation criteria for the conformity assessment of generating units with respect to the above mentioned standardization documents, based on type testing. However, some requirements are applicable on the generating plant level. The assessment of the conformity to these plant requirements are out of the scope of this document. Nevertheless, this document may be used to show the capabilities of a generating unit to be used in a plant.
As a consequence, it is possible that the conformity assessment of a generating unit does not cover all aspects of the above-mentioned standardization documents, typically when a requirement is evaluated on a plant level. Therefore, the conformity assessment report indicates clearly which clauses of this document are covered and which clauses are not covered.
This document recognizes the existence of specific technical test requirements within several member states that must be complied with.

The purpose of this document is to provide technical guidance for tests on generating units and interface protection to evaluate their electrical characteristics. NOTE 1 Mechanical issues are taken into account as far as they influence the electrical characteristics. The evaluation results are intended to be used to demonstrate conformity of generating units to technical requirements for grid connection. In this context the evaluation results can also be used as part of a certification programme. NOTE 2 Besides the type test results of the generating unit all additional elements for connection to the grid (e.g. transformer, cabling, multiple units) are considered in the evaluation of the final installation of a generating plant. The requirements to be evaluated are covered in the following standardization documents: – EN 50549 1:2019: Requirements for generating plants to be connected in parallel with distribution networks - Part 1: connection to a LV distribution network - Generating plants up to and including Type B – EN 50549 2:2019: Requirements for generating plants to be connected in parallel with distribution networks - Part 2: Connection to a MV distribution network - Generating plants up to and including Type B If grid connection requirements are dealt with in other documents or for other generating module types, where no specific testing procedure is provided, testing methods of this document can be used if applicable. This document provides evaluation criteria for the conformity assessment of generating units with respect to the abovementioned standardization documents, based on type testing. However, some requirements are applicable on the generating plant level. The assessment of the conformity to these plant requirements are out of the scope of this document. Nevertheless, this document may be used to show the capabilities of a generating unit to be used in a plant. As a consequence, it is possible that the conformity assessment of a generating unit does not cover all aspects of the above-mentioned standardization documents, typically when a requirement is evaluated on a plant level. Therefore, the conformity assessment report indicates clearly which clauses of this document are covered and which clauses are not covered. This document recognizes the existence of specific technical test requirements within several member states that must be complied with.

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.

This part of IEC 61000 focuses on emission and immunity test methods for electrical and
electronic equipment using various types of transverse electromagnetic (TEM) waveguides.
These types include open structures (for example striplines and electromagnetic pulse
simulators) and closed structures (for example TEM cells). These structures can be further
classified as one-port, two-port, or multi-port TEM waveguides. The frequency range depends
on the specific testing requirements and the specific TEM waveguide type.
The object of this document is to describe
– TEM waveguide characteristics, including typical frequency ranges and equipment-undertest (EUT) size limitations;
– TEM waveguide validation methods for electromagnetic compatibility (EMC) tests;
– the EUT (i.e. EUT cabinet and cabling) definition;
– test set-ups, procedures, and requirements for radiated emission measurements in TEM
waveguides; and
– test set-ups, procedures, and requirements for radiated immunity testing in TEM
waveguides.
NOTE Test methods are defined in this document to measure the effects of electromagnetic radiation on equipment
and the electromagnetic emissions from the equipment concerned. The simulation and measurement of
electromagnetic radiation is not adequately exact for the quantitative determination of effects for all end-use
installations. The test methods defined are structured for a primary objective of establishing adequate reproducibility
of results at various test facilities for qualitative analysis of effects.
This document does not intend to specify the tests to be applied to any particular apparatus or
system(s). The main intention of this document is to provide a general basic reference for all
interested product committees of the IEC. For radiated emission measurements, product
committees select emission limits and measurement methods in consultation with CISPR
standards. For radiated immunity testing, product committees remain responsible for the
appropriate choice of immunity tests and immunity test limits to be applied to equipment within
their scope. This document describes test methods that are separate from those of
IEC 61000‑4‑3 [34].1

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

IEC 61000-4-20:2022 focuses on emission and immunity test methods for electrical and electronic equipment using various types of transverse electromagnetic (TEM) waveguides. These types include open structures (for example striplines and electromagnetic pulse simulators) and closed structures (for example TEM cells). These structures can be further classified as one-port, two-port, or multi-port TEM waveguides. The frequency range depends on the specific testing requirements and the specific TEM waveguide type. The object of this document is to describe  TEM waveguide characteristics, including typical frequency ranges and equipment-under-test (EUT) size limitations; TEM waveguide validation methods for electromagnetic compatibility (EMC) tests; the EUT (i.e. EUT cabinet and cabling) definition; test set-ups, procedures, and requirements for radiated emission measurements in TEM waveguides; and test set-ups, procedures, and requirements for radiated immunity testing in TEM waveguides.  NOTE Test methods are defined in this document to measure the effects of electromagnetic radiation on equipment and the electromagnetic emissions from the equipment concerned. The simulation and measurement of electromagnetic radiation is not adequately exact for the quantitative determination of effects for all end-use installations. The test methods defined are structured for a primary objective of establishing adequate reproducibility of results at various test facilities for qualitative analysis of effects. This document does not intend to specify the tests to be applied to any particular apparatus or system(s). The main intention of this document is to provide a general basic reference for all interested product committees of the IEC. For radiated emission measurements, product committees select emission limits and measurement methods in consultation with CISPR standards. For radiated immunity testing, product committees remain responsible for the appropriate choice of immunity tests and immunity test limits to be applied to equipment within their scope. This document describes test methods that are separate from those of IEC 61000‑4‑3. This third edition cancels and replaces the second edition published in 2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:  provide information on the testing of large EUTs (including cables); apply the work on measurement uncertainties by adapting the work completed in CISPR and TC 77 (for emissions and immunity); update the validation procedure for the test volume regarding field uniformity and TEM mode verification; provide information concerning two-port and four-port TEM waveguides; add a new informative annex (Annex I) dealing with transient TEM waveguide characterization; and add information dealing with dielectric test stands for EUTs.

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.

IEC Corrected version

IEC 61970-456:2021 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. This third edition cancels and replaces the second edition published in 2018. This edition constitutes a technical revision. It is based on the IEC 61970 UML version ‘IEC61970CIM17v40’, dated 2020-08-24. This edition includes the following significant technical changes with respect to the previous edition: a) Updated to support CIM17 (IEC 61970-301:2020+AMD1) and align with IEC 61970‑452:ED4. b) The classes PowerElectronicsConnection, PowerElectronicsUnit and PowerElectronicsWindUnit are added to the Steady State Hypothesis (SSH) profile to match the changes done for Edition 4 of IEC 61970-452 , Core Equipment profile. c) Added relevant terms used in this document. d) Clarified use of Equipment.inService and Equipment.normallyInService.

IEC Corrected version

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

The contents of the corrigendum of January 2022 have been included in this copy.

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. [...]

The contents of the corrigendum of January 2022 have been included in this copy.

This part of IEC 62056 describes two sets of profiles: the first set of profiles allows a
bidirectional communication between a client and a server. This set of profiles is made of three
profiles allowing local bus data exchange with stations either energized or not. For nonenergized
stations, the bus supplies energy for data exchange. Three different profiles are
supported:
• base profile: this three-layer profile provides remote communication services;
NOTE 1 This first profile was published in IEC 61142:1993 and became known as the Euridis standard.
• profile with DLMS: this profile allows using DLMS services as specified in IEC 61334-4-41;
NOTE 2 This second profile was published in IEC 62056-31:1999.
• profile with DLMS/COSEM: this profile allows using the DLMS/COSEM Application layer and
the COSEM object model as specified in IEC 62056-5-3 and in IEC 62056-6-2 respectively.
The three profiles use the same physical layer and they are fully compatible, meaning that
devices implementing any of these profiles can be operated on the same bus. The transmission
medium is twisted pair using carrier signalling and it is known as the Euridis Bus.
The second set of profiles allows unidirectional communication between a given Energy
Metering device and a Customer Energy Management System. This second set is made up of
three profiles.
Subclause 4.2.1 to Clause 8 included specify the bidirectional communication using twisted pair
signalling and Clause 9 to 9.5 the unidirectional communication using twisted pair signalling.

IEC 62056-3-1:2021 is available as IEC 62056-3-1:2021 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62056-3-1:2021 describes two sets of profiles: the first set of profiles allows a bidirectional communication between a client and a server. This set of profiles is made of three profiles allowing local bus data exchange with stations either energized or not. For non-energized stations, the bus supplies energy for data exchange. Three different profiles are supported: • base profile: this three-layer profile provides remote communication services; NOTE 1 This first profile was published in IEC 61142:1993 and became known as the Euridis standard. • profile with DLMS: this profile allows using DLMS services as specified in IEC 61334 4 41; NOTE 2 This second profile was published in IEC 62056-31:1999. • profile with DLMS/COSEM: this profile allows using the DLMS/COSEM Application layer and the COSEM object model as specified in IEC 62056 5 3 and in IEC 62056 6 2 respectively. The three profiles use the same physical layer and they are fully compatible, meaning that devices implementing any of these profiles can be operated on the same bus. The transmission medium is twisted pair using carrier signalling and it is known as the Euridis Bus. The second set of profiles allows unidirectional communication between a given Energy Metering device and a Customer Energy Management System. This second set is made up of three profiles. Subclause 4.2.1 to Clause 8 included specify the bidirectional communication using twisted pair signalling and Clause 9 to 9.5 the unidirectional communication using twisted pair signalling. This second edition cancels and replaces the first edition of IEC 62056-3-1, issued in 2013, and constitutes a technical revision. The main technical changes with regard to the previous edition are as follows: • addition of a profile which makes use of the IEC 62056 DLMS/COSEM Application layer and COSEM object model; • review of the data link layer which is split into two parts: – a pure Data Link layer; – a "Support Manager" entity managing the communication media; • ability to negotiate the communication speed, bringing baud rate up to 9 600 bauds.

Per the IEC 61968 Interface Reference Model, the Network Operations function defined in this part of IEC 61968 provides utilities the means to supervise main substation topology (breaker and switch state), feeder topology and control equipment status through SCADA, AMI and other data sources. It also provides the means for handling network connectivity and loading conditions. Finally, it makes it possible for utilities to locate customer telephone complaints and coordinate activities of field crews with respect to planned and unplanned outages.
IEC 61968-3 specifies the information content of a set of message payloads that can be used to support many of the business functions related to network operations. Typical uses of the message payloads defined in IEC 61968-3 include data acquisition by external systems, fault isolation, fault restoration, trouble management and coordination of the real-time state of the network.
The scope diagram shown in [Figure 1] illustrates the possibility of implementing IEC 61968-3 functionality 51 as either a single integrated advanced distribution management system or as a set of separate functions - OMS, DMS and SCADA. Utilities may chose to buy these systems from different vendors and integrate them using the IEC 61968-3 messages. Alternatively, a single vendor could provide two or all of these components as a single integrated system. In the case of more than one system being provided by the same vendor, the vendor may chose to use either extensions of the IEC 61968- messages or a proprietary integration mechanism to provide enhanced functionality over and above what is required/supported by the IEC 61968-3 specification. While this is a possible implementation, clause 4.3 defines the scope in terms of business functions that are implemented in common vendor offerings.
Annexes in this standard document integration scenarios or use cases, which are informative examples showing typical ways of using the message payloads defined in this document as well as message payloads to be defined in other parts of the IEC 61968 series.

Per the IEC 61968 Interface Reference Model, the Network Operations function defined in this part of IEC 61968 provides utilities with the means to supervise main substation topology (breaker and switch state), feeder topology and control equipment status through SCADA, AMI and other data sources. It also provides the means for handling network connectivity and loading conditions. Finally, it makes it possible for utilities to locate customer telephone complaints and coordinate activities of field crews with respect to planned and unplanned outages. IEC 61968-3 specifies the information content of a set of message payloads that can be used to support many of the business functions related to network operations. Typical uses of the message payloads defined in IEC 61968-3 include data acquisition by external systems, fault isolation, fault restoration, trouble management and coordination of the real-time state of the network. The scope diagram shown in Figure 1 illustrates the possibility of implementing IEC 61968-3 functionality as either a single integrated advanced distribution management system or as a set of separate functions - OMS, DMS and SCADA. Utilities may choose to buy these systems from different vendors and integrate them using the IEC 61968-3 messages. Alternatively, a single vendor could provide two or all of these components as a single integrated system. In the case of more than one system being provided by the same vendor, the vendor may choose to use either extensions of the IEC 61968 messages or a proprietary integration mechanism to provide enhanced functionality over and above what is required/supported by the IEC 61968-3 specification. While this is a possible implementation, Subclause 4.3 defines the scope in terms of business functions that are implemented in common vendor offerings. Annexes in this document detail integration scenarios or use cases, which are informative examples showing typical ways of using the message payloads defined in this document as well as message payloads to be defined in other parts of the IEC 61968 series.

This part of IEC 61968 specifies profiles that can be used to exchange Network Models in a
Utility or between a Utility and external applications to the utility. This document provides a list
of profiles which allow to model balanced and unbalanced distribution networks in order to
conduct network analysis (Power flow calculation). Therefore, it leverages already existing
profiles (IEC 61970-45x based on IEC 61970-301 (CIM base) or profiles based on
IEC 6196811
CIM extension for Distribution). This document reuses some profiles without any
change, or eventually extends them or restricts them. Moreover, it proposes other profiles to
reflect Distribution needs.
Use of CIM in Distribution is not a new topic. Several documents can be of interest
[13][17][18][19][20]. This document includes informative parts, as CIM model extensions, which
could be integrated in future versions of the IEC CIM Model. These extensions have been used
by some utilities for utility internal information exchange use cases and to support information
exchanges between different market participants like Transmisstion System Operators (TSO),
Distributed System Operators (DSO), Distributed Network Operators (DNO) and Significant Grid
Users (SGU) including generators and industry (see Annex J for example).

IEC 61000-6-3:2020 is a generic EMC emission standard applicable only if no relevant dedicated product or product family EMC emission standard has been published. This part of IEC 61000 for emission requirements applies to electrical and electronic equipment intended for use at residential (see 3.1.14) locations. This part of IEC 61000 also applies to electrical and electronic equipment intended for use at other locations that do not fall within the scope of IEC 61000-6-8 or IEC 61000-6-4. The intention is that all equipment used in the residential, commercial and light-industrial environments are covered by IEC 61000-6-3 or IEC 61000-6-8. If there is any doubt the requirements in IEC 61000-6-3 apply. The conducted and radiated emission requirements in the frequency range up to 400 GHz are considered essential and have been selected to provide an adequate level of protection of radio reception in the defined electromagnetic environment. Not all disturbance phenomena have been included for testing purposes but only those considered relevant for the equipment intended to operate within the locations included within this document. The emission requirements in this document are not intended to be applicable to the intentional transmissions and their harmonics from a radio transmitter as defined by the ITU. This third edition cancels and replaces the second edition published in 2006 and its Amendment 1:2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) alternative method for measuring conducted emissions on DC ports;
b) limits and requirements applicable only to equipment intended to be used in residential locations;
c) more stringent limits for DC power ports.
NOTE 1 Safety considerations are not covered by this document.
NOTE 2 In special cases, situations will arise where the levels specified in this document will not offer adequate protection; for example where a sensitive receiver is used in close proximity to an equipment. In these instances, special mitigation measures can be employed. NOTE 3 Disturbances generated in fault conditions of equipment are not covered by this document.
NOTE 4 As the requirements in this document are more stringent or equivalent to those requirements in IEC 61000-6-4 and IEC 61000-6-8, equipment fulfilling the requirements of this document comply with the requirements of IEC 61000-6-4 and IEC 61000-6-8.

IEC 61968-13:2021 specifies profiles that can be used to exchange Network Models in a Utility or between a Utility and external applications to the utility. This document provides a list of profiles which allow to model balanced and unbalanced distribution networks in order to conduct network analysis (Power flow calculation). Therefore it leverages already existing profiles (IEC 61970-45x based on IEC 61970-301 (CIM base) or profiles based on IEC 61968­11 CIM extension for Distribution). This document reuses some profiles without any change, or eventually extends them or restricts them. Moreover it proposes other profiles to reflect Distribution needs. Use of CIM in Distribution is not a new topic. This document includes informative parts, as CIM model extensions, which could be integrated in future versions of the IEC CIM Model. These extensions have been used by some utilities for utility internal information exchange use cases and to support information exchanges between different market participants like Transmisstion System Operators (TSO), Distributed System Operators (DSO), Distributed Network Operators (DNO) and Significant Grid Users (SGU) including generators and industry. This second edition cancels and replaces the first edition published in 2008. This edition constitutes a technical revision. This edition was pre-tested during 2016 ENTSO-E interoperability tests. The interoperability test report mentions: "Some vendors demonstrated that the transformation between distribution network and CGMES is possible. This is a first step towards the efforts to have closer integration between CGMES and profiles for exchanging distribution data (CDPSM)."

IEC 61000-6-3:2020 is a generic EMC emission standard applicable only if no relevant dedicated product or product family EMC emission standard has been published. This part of IEC 61000 for emission requirements applies to electrical and electronic equipment intended for use at residential (see 3.1.14) locations. This part of IEC 61000 also applies to electrical and electronic equipment intended for use at other locations that do not fall within the scope of IEC 61000-6-8 or IEC 61000-6-4. The intention is that all equipment used in the residential, commercial and light-industrial environments are covered by IEC 61000-6-3 or IEC 61000-6-8. If there is any doubt the requirements in IEC 61000-6-3 apply. The conducted and radiated emission requirements in the frequency range up to 400 GHz are considered essential and have been selected to provide an adequate level of protection of radio reception in the defined electromagnetic environment. Not all disturbance phenomena have been included for testing purposes but only those considered relevant for the equipment intended to operate within the locations included within this document. The emission requirements in this document are not intended to be applicable to the intentional transmissions and their harmonics from a radio transmitter as defined by the ITU. This third edition cancels and replaces the second edition published in 2006 and its Amendment 1:2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) alternative method for measuring conducted emissions on DC ports; b) limits and requirements applicable only to equipment intended to be used in residential locations; c) more stringent limits for DC power ports. NOTE 1 Safety considerations are not covered by this document. NOTE 2 In special cases, situations will arise where the levels specified in this document will not offer adequate protection; for example where a sensitive receiver is used in close proximity to an equipment. In these instances, special mitigation measures can be employed. NOTE 3 Disturbances generated in fault conditions of equipment are not covered by this document. NOTE 4 As the requirements in this document are more stringent or equivalent to those requirements in IEC 61000-6-4 and IEC 61000-6-8, equipment fulfilling the requirements of this document comply with the requirements of IEC 61000-6-4 and IEC 61000-6-8.

This part of IEC 61000 is applicable to the immunity requirements of electrical and electronic
equipment to radiated electromagnetic energy. It establishes test levels and the required test
procedures.
The object of this document is to establish a common reference for evaluating the immunity of
electrical and electronic equipment when subjected to radiated, radio-frequency
electromagnetic fields. The test method documented in this part of IEC 61000 describes a
consistent method to assess the immunity of an equipment or system against RF
electromagnetic fields from RF sources not in close proximity to the EUT. The test environment
is specified in Clause 6.
NOTE 1 As described in IEC Guide 107, this is a basic EMC publication for use by product committees of the IEC.
As also stated in Guide 107, the IEC product committees are responsible for determining whether this immunity test
standard should be applied or not, and if applied, they are responsible for determining the appropriate test levels
and performance criteria. TC 77 and its sub-committees are prepared to co-operate with product committees in the
evaluation of the value of particular immunity tests for their products.
NOTE 2 Immunity testing against RF sources in close proximity to the EUT is defined in IEC 61000-4-39.
Particular considerations are devoted to the protection against radio-frequency emissions from
digital radiotelephones and other RF emitting devices.
NOTE 3 Test methods are defined in this part for evaluating the effect that electromagnetic radiation has on the
equipment concerned. The simulation and measurement of electromagnetic radiation is not adequately exact for
quantitative determination of effects. The test methods defined in this basic document have the primary objective of
establishing an adequate reproducibility of testing configuration and repeatability of test results at various test
facilities.
This document is an independent test method. It is not possible to use other test methods as
substitutes for claiming compliance with this document.

This part of IEC 62451 defines the information model associated with Programs in the OPC
Unified Architecture. This includes the description of the NodeClasses, standard Properties,
Methods and Events and associated behaviour and information for Programs.
The complete Address Space model including all NodeClasses and Attributes is specified in
IEC 62541‑3. The Services such as those used to invoke the Methods used to manage
Programs are specified in IEC 62541‑4.

This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Services. The
Services defined are the collection of abstract Remote Procedure Calls (RPC) that are
implemented by OPC UA Servers and called by OPC UA Clients. All interactions between
OPC UA Clients and Servers occur via these Services. The defined Services are considered
abstract because no particular RPC mechanism for implementation is defined in this
document. IEC 62541‑6 specifies one or more concrete mappings supported for
implementation. For example, one mapping in IEC 62541‑6 is to XML Web Services. In that
case the Services described in this document appear as the Web service methods in the
WSDL contract.
Not all OPC UA Servers will need to implement all of the defined Services. IEC 62541‑7
defines the Profiles that dictate which Services need to be implemented in order to be
compliant with a particular Profile.

This part of IEC 62541 defines the Information Model of the OPC Unified Architecture. The
Information Model describes standardized Nodes of a Server’s AddressSpace. These Nodes
are standardized types as well as standardized instances used for diagnostics or as entry
points to server-specific Nodes. Thus, the Information Model defines the AddressSpace of an
empty OPC UA Server. However, it is not expected that all Servers will provide all of these
Nodes.

This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) AddressSpace and its
Objects. This document is the OPC UA meta model on which OPC UA information models are
based.

This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series
and defines the information model associated with Data Access (DA). It particularly includes
additional VariableTypes and complementary descriptions of the NodeClasses and Attributes
needed for Data Access, additional Properties, and other information and behaviour.
The complete address space model, including all NodeClasses and Attributes is specified in
IEC 62541-3. The services to detect and access data are specified in IEC 62541-4.

This part of IEC 62541 is part of the OPC Unified Architecture standard series and defines the
information model associated with Historical Access (HA). It particularly includes additional
and complementary descriptions of the NodeClasses and Attributes needed for Historical
Access, additional standard Properties, and other information and behaviour.
The complete AddressSpace Model including all NodeClasses and Attributes is specified in
IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to
detect and access historical data and events, and description of the ExtensibleParameter
types are specified in IEC 62541-4.
This document includes functionality to compute and return Aggregates like minimum,
maximum, average etc. The Information Model and the concrete working of Aggregates are
defined in IEC 62541-13.

This part of IEC 62541 is part of the overall OPC Unified Architecture specification series and
defines the information model associated with Aggregates.

This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Profiles. The Profiles
in this document are used to segregate features with regard to testing of OPC UA products
and the nature of the testing (tool based or lab based). This includes the testing performed by
the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation
provided Independent certification test labs. This could equally as well refer to test tools
provided by another organization or a test lab provided by another organization. What is
important is the concept of automated tool-based testing versus lab-based testing. The scope
of this standard includes defining functionality that can only be tested in a lab and defining the
grouping of functionality that is to be used when testing OPC UA products either in a lab or
using automated tools. The definition of actual TestCases is not within the scope of this
document, but the general categories of TestCases are within the scope of this document.
Most OPC UA applications will conform to several, but not all, of the Profiles.

This part of IEC 62541 specifies the OPC Unified Architecture (OPC UA) mapping between
the security model described in IEC TR 62541‑2, the abstract service definitions specified in
IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols
that can be used to implement the OPC UA specification.

This part of IEC 62541 specifies the representation of Alarms and Conditions in the OPC
Unified Architecture. Included is the Information Model representation of Alarms and
Conditions in the OPC UA address space. Other aspects of alarm systems such as alarm
philosophy, life cycle, alarm response times, alarm types and many other details are captured
in documents such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model
in this specification is designed in accordance with IEC 62682 and ISA 18.2.

IEC 61000-4-3:2020 is applicable to the immunity requirements of electrical and electronic equipment to radiated electromagnetic energy. It establishes test levels and the required test procedures. The object of this document is to establish a common reference for evaluating the immunity of electrical and electronic equipment when subjected to radiated, radio-frequency electromagnetic fields. The test method documented in this part of IEC 61000 describes a consistent method to assess the immunity of an equipment or system against RF electromagnetic fields from RF sources not in close proximity to the EUT. The test environment is specified in Clause 6. NOTE 1 As described in IEC Guide 107, this is a basic EMC publication for use by product committees of the IEC. As also stated in Guide 107, the IEC product committees are responsible for determining whether this immunity test standard should be applied or not, and if applied, they are responsible for determining the appropriate test levels and performance criteria. TC 77 and its sub-committees are prepared to co-operate with product committees in the evaluation of the value of particular immunity tests for their products. NOTE 2 Immunity testing against RF sources in close proximity to the EUT is defined in IEC 61000-4-39. Particular considerations are devoted to the protection against radio-frequency emissions from digital radiotelephones and other RF emitting devices. NOTE 3 Test methods are defined in this part for evaluating the effect that electromagnetic radiation has on the equipment concerned. The simulation and measurement of electromagnetic radiation is not adequately exact for quantitative determination of effects. The test methods defined in this basic document have the primary objective of establishing an adequate reproducibility of testing configuration and repeatability of test results at various test facilities. This document is an independent test method. It is not possible to use other test methods as substitutes for claiming compliance with this document. This fourth edition cancels and replaces the third edition published in 2006, Amendment 1:2007 and Amendment 2:2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: - testing using multiple test signals has been described; - additional information on EUT and cable layout has been added; - the upper frequency limitation has been removed to take account of new services; - the characterization of the field as well as the checking of power amplifier linearity of the immunity chain are specified.

The common information model (CIM) is an abstract model that represents all the major objects
in an electric utility enterprise typically involved in utility operations. By providing a standard
way of representing power system resources as object classes and attributes, along with their
relationships, the CIM facilitates the integration and interoperability of network applications
developed independently by different vendors, between entire systems running network
applications developed independently, or between a system running network applications and
other systems concerned with different aspects of power system operations, such as generation
or distribution management. SCADA is modelled to the extent necessary to support power
system simulation and inter-control centre communication. The CIM facilitates integration by
defining a common language (i.e. semantics) based on the CIM to enable these applications or
systems to access public data and exchange information independent of how such information
is represented internally.
The object classes represented in the CIM are abstract in nature and can be used in a wide
variety of applications. The use of the CIM goes far beyond its application in an EMS. This
document should be understood as a tool to enable integration in any domain where a common
power system model is needed to facilitate interoperability and plug compatibility between
applications and systems independent of any particular implementation.
Due to the size of the complete CIM, the object classes contained in the CIM are grouped into
several logical Packages, each of which represents a certain part of the overall power system
being modelled. Collections of these Packages are progressed as separate International
Standards. This document specifies a Base set of packages which provide a logical view of the
functional aspects of Energy Management System (EMS) and power system modelling
information within the electric utility enterprise that is shared between all applications. Other
standards specify more specific parts of the model that are needed by only certain applications.
Subclause 4.3 of this document provides the current grouping of packages into standards
documents.

IEC 62541-5:2020 is available as IEC 62541-5:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-5:2020 defines the Information Model of the OPC Unified Architecture. The Information Model describes standardized Nodes of a Server’s AddressSpace. These Nodes are standardized types as well as standardized instances used for diagnostics or as entry points to server-specific Nodes. Thus, the Information Model defines the AddressSpace of an empty OPC UA Server. However, it is not expected that all Servers will provide all of these Nodes. This third edition cancels and replaces the second 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) Added Annex F on User Authentication. Describes the Role Information Model that also allows configuration of Roles. b) Added new data types: "Union", "Decimal", "OptionSet", "DateString", "TimeString", "DurationString", NormalizedString", "DecimalString", and "AudioDataType". c) Added Method to request a state change in a Server. d) Added Method to set Subscription to persistent mode. e) Added Method to request resending of data from a Subscription. f) Added concept allowing to temporarily create a file to write to or read from a server in C.4. g) Added new Variable type to support Selection Lists. h) Added optional properties to FiniteStateMachineType to expose currently available states and transitions. i) Added UrisVersion Property to ServerType. This version information can be used for session-less service invocation.

IEC 62541-4:2020 is available as IEC 62541-4:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-4:2020 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to XML Web Services. In that case the Services described in this document appear as the Web service methods in the WSDL contract. Not all OPC UA Servers will need to implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services need to be implemented in order to be compliant with a particular Profile This third edition cancels and replaces the second 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) Added ability to resend all data of monitored items in a Subscription using the ResendData Method. b) Added support for durable Subscriptions (lifetime of hours or days). c) Added Register2 and FindServersOnNetwork Services to support network-wide discovery using capability filters. d) Removed definition of software certificates. Will be defined in a future edition. e) Extended and partially revised the redundancy definition. Added sub-range definitions for ServiceLevel and added more terms for redundancy. f) Added a section on how to use Authorization Services to request user access tokens. g) Added JSON Web Tokens (JWTs) as a new user token. h) Added the concept of session-less service invocation. i) Added a generic structure that allows passing any number of attributes to the AddNodes Service. j) Added requirement to protect against user identity token attacks. k) Added new EncryptedSecret format for user identity tokens.

IEC 62541-6:2020 is available as IEC 62541-6:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-6:2020 specifies the OPC Unified Architecture (OPC UA) mapping between the security model described in IEC TR 62541-2, the abstract service definitions specified in IEC 62541-4, the data structures defined in IEC 62541-5 and the physical network protocols that can be used to implement the OPC UA specification. This third edition cancels and replaces the second 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) Encodings: • added JSON encoding for PubSub (non-reversible); • added JSON encoding for Client/Server (reversible); • added support for optional fields in structures; • added support for Unions. b) Transport mappings: • added WebSocket secure connection – WSS; • added support for reverse connectivity; • added support for session-less service invocation in HTTPS. c) Deprecated Transport (missing support on most platforms): • SOAP/HTTP with WS-SecureConversation (all encodings). d) Added mapping for JSON Web Token. e) Added support for Unions to NodeSet Schema. f) Added batch operations to add/delete nodes to/from NodeSet Schema. g) Added support for multi-dimensional arrays outside of Variants. h) Added binary representation for Decimal data types. i) Added mapping for an OAuth2 Authorization Framework.

IEC 62541-3:2020 is available as IEC 62541-3:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-3:2020 defines the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This document is the OPC UA meta model on which OPC UA information models are based. This third edition cancels and replaces the second edition published in 2015. This edition includes the following significant technical changes with respect to the previous edition: a) Added new improved approach for exposing structure definitions. An Attribute on the DataType Node now simply contains a binary description. b) Added new flags for Variables to indicate atomicity when reading or writing. c) Added Roles and Permissions to allow configuration of a role-based authorization. d) Added new data types: “Union”, “Decimal”, “OptionSet”, “DateString”, “TimeString”, “DurationString”, NormalizedString”, “DecimalString”, and “AudioDataType”. e) Added definition on how to use the ModellingRules OptionalPlaceHolder and MandatoryPlaceHolder for Methods. f) Added optional Properties “MaxCharacters” and “MaxByteStringLength” to Variable Nodes.

IEC 62541-10:2020 is available as IEC 62541-10:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-10:2020 defines the information model associated with Programs in the OPC Unified Architecture. This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete Address Space model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541 4. This third edition cancels and replaces the second edition published in 2015. This edition includes several clarifications and in addition the following significant technical changes with respect to the previous edition: a) Changed ProgramType to ProgramStateMachineType. This is in line with the NodeSet (and thus implementations). In ProgramDiagnosticDataType: changed the definition of lastInputArguments and lastOutputArguments and added two additional fields for the argument values. Also changed StatusResult into StatusCode. Created new version of the type to ProgramDiagnostic2DataType. b) Changed Optional modelling rule to OptionalPlaceHolder for Program control Methods. Following the clarification in IEC 62541-3, this now allows subtypes (or instances) to add arguments.

IEC 61970-301:2020 (E) lays down the common information model (CIM), which is an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of network applications developed independently by different vendors, between entire systems running network applications developed independently, or between a system running network applications and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modeled to the extent necessary to support power system simulation and inter-control centre communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. This edition reflects the model content version ‘IEC61970CIM17v38’, dated ‘2020-01-21’, and includes the following significant technical changes with respect to the previous edition: a) Added Feeder modelling; b) Added ICCP configuration modelling; c) Correction of issues found in interoperability testing or use of the standard; d) Improved documentation; e) Updated Annex A with custom extensions; f) Added Annex B Examples of PST transformer modelling; g) Added Annex C HVDC use cases.

IEC 62541-11:2020 is available as IEC 62541-11:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-11:2020 is part of the OPC Unified Architecture standard series and defines the information model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour. The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4. This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13. This third edition cancels and replaces the second 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) a new method for determining the first historical point has been added; b) added clarifications on how to add, insert, modify, and delete annotations.

IEC 62541-7:2020 is available as IEC 62541-7:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-7:2020 defines the OPC Unified Architecture (OPC UA) Profiles. The Profiles in this document are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed by the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation provided Independent certification test labs. This could equally as well refer to test tools provided by another organization or a test lab provided by another organization. What is important is the concept of automated tool-based testing versus lab-based testing. The scope of this standard includes defining functionality that can only be tested in a lab and defining the grouping of functionality that is to be used when testing OPC UA products either in a lab or using automated tools. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are within the scope of this document. Most OPC UA applications will conform to several, but not all, of the Profiles. This third edition cancels and replaces the second 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) new functional Profiles: • profiles for global discovery and global certificate management; • profiles for global KeyCredential management and global access token management; • facet for durable subscriptions; • standard UA Client Profile; • profiles for administration of user roles and permissions. b) new transport Profiles: • HTTPS with JSON encoding; • secure WebSockets (WSS) with binary or JSON encoding; • reverse connectivity. c) new security Profiles: • transportSecurity – TLS 1.2 with PFS (with perfect forward secrecy); • securityPolicy [A] – Aes128-Sha256-RsaOaep (replaces Base128Rsa15); • securityPolicy – Aes256-Sha256-RsaPss adds perfect forward secrecy for UA TCP); • user Token JWT (Jason Web Token). d) deprecated Security Profiles (due to broken algorithms): • securityPolicy – Basic128Rsa15 (broken algorithm Sha1); • securityPolicy – Basic256 (broken algorithm Sha1); • transportSecurity – TLS 1.0 (broken algorithm RC4); • transportSecurity – TLS 1.1 (broken algorithm RC4). e) deprecated Transport (missing support on most platforms): • SOAP/HTTP with WS-SecureConversation (all encodings).

IEC 62541-8:2020 is available as IEC 62541-8:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-8:2020 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour. The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541-3. The services to detect and access data are specified in IEC 62541-4. This third edition cancels and replaces the second 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) added new VariableTypes for AnalogItems; b) added an Annex that specifies a recommended mapping of OPC UA Dataccess to OPC COM DataAccess; c) changed the ambiguous description of "Bad_NotConnected"; d) updated description for EUInformation to refer to latest revision of UNCEFACT units.

IEC 62541-9:2020 is available as IEC 62541-9:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-9:2020 specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. Other aspects of alarm systems such as alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in documents such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this specification is designed in accordance with IEC 62682 and ISA 18.2. This third edition cancels and replaces the second 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) added optional engineering units to the definition of RateOfChange alarms; b) to fulfill the IEC 62682 model, the following elements have been added: - AlarmConditionType States: Suppression, Silence, OutOfService, Latched; - AlarmConditionType Properties: OnDelay, OffDelay, FirstInGroup, ReAlarmTime; - New alarm types: DiscrepencyAlarm, DeviationAlarm, InstrumentDiagnosticAlarm, SystemDiagnosticAlarm. c) added Annex that specifies how the concepts of this OPC UA part maps to IEC 62682 and ISA 18.2; d) added new ConditionClasses: Safety, HighlyManaged, Statistical, Testing, Training; e) added CertificateExpiration AlarmType; f) added Alarm Metrics model.

IEC 62541-13:2020 is available as IEC 62541-13:2020 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-13:2020 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates. This second edition cancels and replaces the first edition of IEC 62541-13, published in 2015. No technical changes but numerous clarifications. Also some corrections to the examples.