BS EN 61850-8-1:2011+A1:2020

This standard BS EN 61850-8-1:2011+A1:2020 Communication networks and systems for power utility automation is classified in these ICS categories:

• 33.200 Telecontrol. Telemetering

1.1 General

This part of IEC 61850 specifies a method of exchanging time-critical and non-time-critical data through local-area networks by mapping ACSI to MMS and ISO/IEC 8802-3 frames.

MMS services and protocol are specified to operate over an OSI-A-Profile and TCP T-Profile. The use of MMS allows provisions for supporting both centralized and distributed architectures. This standard includes the exchange of real-time data indications, control operations, report notification.

It specifies the mapping of the objects and services of the ACSI (Abstract Communication Service Interface, IEC 61850-7-2) to MMS (Manufacturing Message Specification, ISO 9506) and ISO/IEC 8802-3 frames.

This standard also specifies the mapping of time-critical information exchanges to non-MMS protocol. The protocol semantics are defined in IEC 61850-7-2. It contains the protocol syntax, definition, mapping to ISO/IEC 8802-3 frame formats and any relevant procedures specific to the use of ISO/IEC 8802-3.

This mapping of ACSI to MMS defines how the concepts, objects, and services of the ACSI are to be implemented using MMS concepts, objects, and services. This mapping allows interoperability across functions implemented by different manufacturers.

This part of IEC 61850 defines a standardized method of using the ISO 9506 services to implement the exchange of data. For those ACSI services defined in IEC 61850-7-2 that are not mapped to MMS, this part defines additional protocols. It describes real utility devices with respect to their external visible data and behaviour using an object oriented approach. The objects are abstract in nature and may be used to a wide variety of applications. The use of this mapping goes far beyond the application in the utility communications.

This part of IEC 61850 provides mappings for the services and objects specified within IEC 61850-7-2, IEC 61850-7-3, and IEC 61850-7-4.

1.2 Namespace name and version

This new section is mandatory for any IEC 61850 namespace (as defined by IEC 61850-7-1).

The parameters which identify this new release of this namespace are:

• Namespace Version: 2003

• Namespace Revision: A

• Namespace name: “IEC 61850-8-1:2003”

Edition	Publication date	Webstore	Namespace
Edition 1.0	2004-05	IEC 61850-8-1:2004	IEC 61850-8-1:2003
Edition 2.0	2011-06	IEC 61850-8-1:2011	IEC 61850-8-1:2003
Amendment 1 of Edition 2.0	2020-02	IEC 61850-8-1:2011/AMD1:2020	IEC 61850-8-1:2003
Edition 2.1	2020-02	IEC 61850-8-1:2011+AMD1:2020 CSV	IEC 61850-8-1:2003

1.3 Code Component distribution

The Code Component will be available in light and full version:

• Full version will contain definition of the whole types and functional constrains defined in this standard with the documentation associated and access will be restricted to purchaser of this part. The code component package name will be IEC 61850-8-1.NSD.2003A2.full.zip

• Light version will not contain the documentation but will contain the whole definition of the types functional constrains as per full version, and this light version will be freely accessible on the IEC website for download, but the usage remains under the licensing conditions.

The link for downloading the light version of this code component is:

http://www.iec.ch/tc57/supportdocuments/IEC 61850-8-1.NSD.2003A2.light.zip

The Code Components for IEC 61850 data models (like the mapping of the control service parameter in this document) are available as the file format NSD defined by IEC 61850-7-7.

The Code Component included in this IEC standard are potentially subject to maintenance works and user shall select the latest release in the repository located at:

http://www.iec.ch/tc57/supportdocuments

The latest version/release of the document will be found by selecting the file IEC 61850-8-1.NSD.{VersionStateInfo}.light.zip with the filled VersionStateInfo of the highest value.

Each Code Component is a ZIP package containing the electronic representation of the Code Component itself, with a file describing the content of the package (IECManifest.xml).

The IECManifest contains different sections giving information on:

• The copyright notice

• The identification of the code component

• The publication related to the code component

• The list of the electronic files which compose the code component

• An optional list of history files to track changes during the evolution process of the code component

The life cycle of a code component is not restricted to the life cycle of the related publication. The publication life cycle goes through two stages, Version (corresponding to an edition) and Revision (corresponding to an amendment). A third publication stage (Release) allow publication of Code Component without need to publish an amendment.

This is useful when InterOp Tissues need to be fixed. Then a new release of the Code Component will be released, which supersedes the previous release, and distributed through the IEC TC57 website.