35.100 - Open systems interconnection (OSI)
ICS 35.100 Details
Open systems interconnection (OSI)
Verbund offener Systeme (OSI)
Interconnexion des systemes ouverts (modele OSI)
Medsebojno povezovanje odprtih sistemov (OSI)
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.100 - Open systems interconnection (OSI)
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard152 pagesEnglish languagesale 15% off
- Standard158 pagesFrench languagesale 15% off
- Standard310 pagesEnglish and French languagesale 15% off
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard160 pagesEnglish languagesale 15% off
- Standard173 pagesFrench languagesale 15% off
- Standard333 pagesEnglish and French languagesale 15% off
IEC 62541-13:2025 is available as IEC 62541-13:2025 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:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard64 pagesEnglish languagesale 15% off
- Standard64 pagesFrench languagesale 15% off
- Standard128 pagesEnglish and French languagesale 15% off
IEC 62541-10:2025 is available as IEC 62541-10:2025 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:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace 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. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.
- Standard42 pagesEnglish languagesale 15% off
- Standard45 pagesFrench languagesale 15% off
- Standard87 pagesEnglish and French languagesale 15% off
IEC 62541-4:2025 is available as IEC 62541-4:2025 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:2025 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 UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard245 pagesEnglish languagesale 15% off
- Standard257 pagesFrench languagesale 15% off
- Standard502 pagesEnglish and French languagesale 15% off
This document specifies the requirements of parameters for the physical and the link layer for systems using radio to remotely read meters. The primary focus is to use the Short Range Device (SRD) unlicensed bands. This document encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this document can be applied to various Application Layers.
- Draft104 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test (SUT) that implements an electric-vehicle communication controller (EVCC) or a supply-equipment communication controller (SECC) for all common requirements specified in ISO 15118-20 that are independent of a particular charging type (AC, DC, ACD, WPT charging). These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118-20 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements specified in ISO 15118-20. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements specified in ISO 15118-20 and within the capabilities of the SUT.
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format covering the ISO/OSI layer 3 to 7 (network to application layers).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118-20. This document additionally refers to specific tests for requirements on referenced standards (e.g. IETF RFCs, W3C Recommendation, etc.) if they are relevant in terms of conformance for implementations according to ISO 15118-20. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118-20. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, or the environment of the protocol implementation. Furthermore, the abstract test cases specified in this document only consider the communication protocol and the system's behaviour specified in ISO 15118-20. Power flow between the EVSE and the EV is no prerequisite for the test cases specified in this document.
- Standard331 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It • explains the structure and content of the IEC 62453 series (see Clause 5); • provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series; • describes the relationship to some other standards; • provides definitions of terms used in other parts of the IEC 62453 series. This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) introduction of a new implementation technology (defined in IEC TS 62453-43); b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62657-2:2025 specifies:
– the fundamental assumptions, concepts, parameters, and procedures for wireless communication coexistence;
– specifies coexistence parameters and how they are used in an application requiring wireless coexistence;
– provides guidelines, requirements, and best practices for wireless communication's availability and performance in an industrial automation plant; it covers the life‑cycle of wireless communication coexistence;
– helps the work of all persons involved with the relevant responsibilities to cope with the critical aspects at each phase of life-cycle of the wireless communication coexistence management in an industrial automation plant. Life-cycle aspects include: planning, design, installation, implementation, operation, maintenance, administration and training;
– provides a common point of reference for wireless communication coexistence for industrial automation sites as a homogeneous guideline to help the users assess and gauge their plant efforts;
– deals with the operational aspects of wireless communication coexistence regarding both the static human/tool-organization and the dynamic network self-organization.
This document provides a major contribution to national and regional regulations by supporting to fulfil the requirements using coexistence management.
This edition includes the following significant technical changes with respect to the previous edition:
a) alignment of some definitions and specifications of coexistence parameters in order to facilitate their future inclusion in the IEC Common Data Dictionary (IEC CDD) maintained by the IEC;
b) alignment of some definitions and specifications to be consistent with the new IEC 62657-3 and IEC 62657-4;
c) edition 3 of this document was published in June 2022. Some comments were made in the last development stages of this document asking for explanations on how the parts of the IEC 62657 series were structured and how they were related to each other. Resolution of these comments was deferred until a next edition, which means this edition.
- Standard118 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides guidance on how to prepare new and old protocols for cryptographic algorithm migration and defines auxiliary cryptographic algorithms to be used for migration purposes. This document specifies a general wrapper protocol that provides authentication, integrity and confidentiality (encryption) protection for other protocols. This wrapper protocol includes a migration path for cryptographic algorithms allowing for smooth migration to stronger cryptographic algorithms as such requirements evolve. This will allow migration to quantum-safe cryptographic algorithms. Protected protocols can then be developed without taking security and cryptographic algorithms into consideration. This document also includes some protocols to be protected by the wrapper protocol primarily for support of public-key infrastructure (PKI). Other specifications, e.g., Recommendations or International Standards, may also develop protocols designed to be protected by the wrapper protocol.
- Standard120 pagesEnglish languagesale 15% off
This part 8 specifies the physical layer of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed on board vehicles that are operating as part of a public transport network, i.e. in operation under public service contracts. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The use of IEEE 802.11 Wireless LAN communications is excluded from the scope of this Technical Specification; its use is not recommended for the service-based approach of CEN/TS 13149.
Equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake systems, door opening systems, etc.) are excluded from the scope of this Technical Specification and are dealt with in other standardization bodies. Interfaces to such equipment or safety-critical networks can be provided through dedicated gateways.
This document covers the following:
— The link between equipment inside vehicles consisting of one carriage only, e.g. buses and trolleybuses, as well as a set of carriages, e.g. trams and trains;
— The Physical Layer for IP-communication networks onboard PT vehicles;
— The cables, connectors and other equipment including pin assignment and environmental requirements.
This document specifies wired communication networks onboard PT vehicles which are based on the Ethernet specification ISO/IEC/IEEE 8802-3-10 Base T, 100 Base Tx and 1000 Base T.
- Technical specification19 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification20 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard107 pagesEnglish languagesale 15% off
- Standard42 pagesEnglish languagesale 15% off
- Standard2 pagesEnglish languagesale 15% off
This Recommendation | International Standard supplements Rec. ITU-T X.509 | ISO/IEC 9594-8 and Rec. ITU-T X.510 | ISO/IEC 9594-11 by providing an extended description of cryptographic algorithms and guidance in establishment and maintenance of a public-key infrastructure (PKI). It is outside the scope of this Recommendation | International Standard to define new cryptographic algorithms, but it is within scope to discuss already-defined cryptographic algorithms that provide optimal protection, including future protection against attacks using powerful quantum computers. This Recommendation | International Standard specifies how public-key infrastructure (PKI) may be adapted to support machine-to-machine (M2M) communication, e.g., smart grid and Internet of things (IoT), to allow interworking. This Recommendation | International Standard specifies the procedures for establishment and maintenance of a PKI supporting new areas, such as intelligent electricity network (smart grid) and industrial Internet of things.
- Standard102 pagesEnglish languagesale 15% off
- Standard34 pagesEnglish languagesale 15% off
IEC TS 62453-53-90:2025 provides information for integrating the HART®[1] technology into the CLI-based implementation of FDT interface specification (IEC TS 62453-43).
This document specifies implementation of communication and other services based on IEC 62453‑309.
This document neither contains the FDT specification nor modifies it.
[1] HART® and WirelessHART® are trade names of products supplied by FieldComm Group. This information is given for convenience of users of this document and does not constitute an endorsement by IEC of the product named. Equivalent products may be used if they can be shown to lead to the same results.
- Technical specification41 pagesEnglish languagesale 15% off
This document specifies transport and security services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies secure communication capabilities by design and supports the building of a secure system architecture.
This document is applicable to the protection of consumer data to ensure privacy.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard91 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies application services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies application protocols, especially the M-Bus application protocol.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62657-2:2025 specifies: – the fundamental assumptions, concepts, parameters, and procedures for wireless communication coexistence; – specifies coexistence parameters and how they are used in an application requiring wireless coexistence; – provides guidelines, requirements, and best practices for wireless communication's availability and performance in an industrial automation plant; it covers the life‑cycle of wireless communication coexistence; – helps the work of all persons involved with the relevant responsibilities to cope with the critical aspects at each phase of life-cycle of the wireless communication coexistence management in an industrial automation plant. Life-cycle aspects include: planning, design, installation, implementation, operation, maintenance, administration and training; – provides a common point of reference for wireless communication coexistence for industrial automation sites as a homogeneous guideline to help the users assess and gauge their plant efforts; – deals with the operational aspects of wireless communication coexistence regarding both the static human/tool-organization and the dynamic network self-organization. This document provides a major contribution to national and regional regulations by supporting to fulfil the requirements using coexistence management. This edition includes the following significant technical changes with respect to the previous edition: a) alignment of some definitions and specifications of coexistence parameters in order to facilitate their future inclusion in the IEC Common Data Dictionary (IEC CDD) maintained by the IEC; b) alignment of some definitions and specifications to be consistent with the new IEC 62657-3 and IEC 62657-4; c) edition 3 of this document was published in June 2022. Some comments were made in the last development stages of this document asking for explanations on how the parts of the IEC 62657 series were structured and how they were related to each other. Resolution of these comments was deferred until a next edition, which means this edition.
- Standard118 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies application services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies application protocols, especially the M-Bus application protocol.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies transport and security services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies secure communication capabilities by design and supports the building of a secure system architecture.
This document is applicable to the protection of consumer data to ensure privacy.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard91 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the physical and data link layer of high-level communication (HLC) between electric vehicles (EV) and electric vehicle supply equipment (EVSE) based on single-pair Ethernet communication. Single-pair Ethernet communication uses differential twisted pair wires that are dedicated and balanced. This document applies to 10BASE-T1S only.
This document covers the overall information exchange between all actors involved in electrical energy exchange. The ISO 15118 series applies to charging between EV and EVSE.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
IEC PAS 62443-2-2: 2025 provides guidance on the development, validation, operation, and maintenance of a set of technical, physical, and process security measures called Security Protection Scheme (SPS). The document’s goal is to provide the asset owner implementing an IACS Security Program (SP) with mechanisms and procedures to ensure that the design, implementation and operation of an SPS manage the risks resulting from cyberthreats to each of the IACS included in its operating facility.
The document is based on contents specified in other documents of the IEC 62443 series and explains how these contents can be used to support the development of technical, physical, and process security measures addressing the risks to the IACS during the operation phase.
- Technical specification44 pagesEnglish languagesale 15% off
IEC TS 62453-53-31:2025 provides information for integrating the PROFIBUS[1] technology into the CLI-based implementation of FDT interface specification (IEC TS 62453-43).
This document specifies implementation of communication and other services based on IEC 62453‑303-1.
This document neither contains the FDT specification nor modifies it.
[1] PROFIBUS™ is a trade name of the non-profit organization PROFIBUS Nutzerorganisation e.V. (PNO). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade name holder or any of its products. Compliance to this document does not require use of the registered logos for PROFIBUS™. Use of the registered logos for PROFIBUS™ requires permission of PNO.
- Technical specification68 pagesEnglish languagesale 15% off
IEC 62657-2:2025 specifies:
– the fundamental assumptions, concepts, parameters, and procedures for wireless communication coexistence;
– specifies coexistence parameters and how they are used in an application requiring wireless coexistence;
– provides guidelines, requirements, and best practices for wireless communication's availability and performance in an industrial automation plant; it covers the life‑cycle of wireless communication coexistence;
– helps the work of all persons involved with the relevant responsibilities to cope with the critical aspects at each phase of life-cycle of the wireless communication coexistence management in an industrial automation plant. Life-cycle aspects include: planning, design, installation, implementation, operation, maintenance, administration and training;
– provides a common point of reference for wireless communication coexistence for industrial automation sites as a homogeneous guideline to help the users assess and gauge their plant efforts;
– deals with the operational aspects of wireless communication coexistence regarding both the static human/tool-organization and the dynamic network self-organization.
This document provides a major contribution to national and regional regulations by supporting to fulfil the requirements using coexistence management.
This edition includes the following significant technical changes with respect to the previous edition:
a) alignment of some definitions and specifications of coexistence parameters in order to facilitate their future inclusion in the IEC Common Data Dictionary (IEC CDD) maintained by the IEC;
b) alignment of some definitions and specifications to be consistent with the new IEC 62657-3 and IEC 62657-4;
c) edition 3 of this document was published in June 2022. Some comments were made in the last development stages of this document asking for explanations on how the parts of the IEC 62657 series were structured and how they were related to each other. Resolution of these comments was deferred until a next edition, which means this edition.
- Standard235 pagesEnglish and French languagesale 15% off
IEC 61784-3-19:2024 specifies a safety communication layer (services and protocol) based on IEC 61784‑1-19, IEC 61784-2-19 and the IEC 61158 series (Type 24 and Type 27). It identifies the principles for functional safety communications defined in IEC 61784‑3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only.
NOTE 1 It does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres.
This document defines mechanisms for the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of the IEC 61508 series for functional safety. These mechanisms can be used in various industrial applications such as process control, manufacturing automation and machinery.
This document provides guidelines for both developers and assessors of compliant devices and systems.
NOTE 2 The resulting SIL claim of a system depends on the implementation of the selected functional safety communication profile within this system – implementation of a functional safety communication profile according to this document in a standard device is not sufficient to qualify it as a safety device.
- Standard80 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61784-3-19:2024 specifies a safety communication layer (services and protocol) based on IEC 61784‑1-19, IEC 61784-2-19 and the IEC 61158 series (Type 24 and Type 27). It identifies the principles for functional safety communications defined in IEC 61784‑3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only. NOTE 1 It does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres. This document defines mechanisms for the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of the IEC 61508 series for functional safety. These mechanisms can be used in various industrial applications such as process control, manufacturing automation and machinery. This document provides guidelines for both developers and assessors of compliant devices and systems. NOTE 2 The resulting SIL claim of a system depends on the implementation of the selected functional safety communication profile within this system – implementation of a functional safety communication profile according to this document in a standard device is not sufficient to qualify it as a safety device.
- Standard80 pagesEnglish languagesale 10% offe-Library read for1 day
IEC TS 62453-43:2024 specifies how the common FDT principles are implemented based on the CLI technology and web technologies for graphical user interfaces. The specification includes the object behaviour and object interaction via. NET Standard interfaces and JavaScript APIs. Emphasis has been placed on support of distributed Frame Application architectures.
This document specifies FDT version 3.0.
- Technical specification361 pagesEnglish languagesale 15% off
IEC 61784-3-19:2024 specifies a safety communication layer (services and protocol) based on IEC 61784‑1-19, IEC 61784-2-19 and the IEC 61158 series (Type 24 and Type 27). It identifies the principles for functional safety communications defined in IEC 61784‑3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only.
NOTE 1 It does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres.
This document defines mechanisms for the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of the IEC 61508 series for functional safety. These mechanisms can be used in various industrial applications such as process control, manufacturing automation and machinery.
This document provides guidelines for both developers and assessors of compliant devices and systems.
NOTE 2 The resulting SIL claim of a system depends on the implementation of the selected functional safety communication profile within this system – implementation of a functional safety communication profile according to this document in a standard device is not sufficient to qualify it as a safety device.
- Standard155 pagesEnglish and French languagesale 15% off
This document specifies test methods for ISO/IEC 21481 in addition to applicable test methods specified in ISO/IEC 10373-6, ISO/IEC 10373-7 and ISO/IEC 23917.
- Standard6 pagesEnglish languagesale 15% off
IEC 61784-5-12:2024 is available as IEC 61784-5-12:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 61784-5-12:2024 specifies the installation profile for CPF 12 (EtherCAT™).
The installation profile is specified in Annex A. This annex is read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
EtherCAT™ is a trade name of Beckhoff, Verl. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
- Standard24 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment10 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61784-5-6:2024 is available as IEC 61784-5-6:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 61784-5-6:2024 specifies the installation profiles for CPF 6 (INTERBUSTM)[1]. The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] INTERBUSTM is a trade name of INTERBUS Club, an independent organisation of users and vendors of INTERBUS products. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name INTERBUS. Use of the trade name INTERBUS requires permission of the trade name holder.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61784-5-8:2024 is available as IEC 61784-5-8:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 61784-5-8:2024 specifies the installation profiles for CPF 8 (CC-LinkTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] CC-Link™, CC-Link/LT™ and CC‑Link IE™ are trade names of Mitsubishi Electric Co., control of trade name use is given to CCLink Partner Association. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
- Standard88 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment10 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61784-5-19:2024 is available as IEC 61784-5-19:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 61784-5-19:2024 specifies the installation profile for CPF 19 (MECHATROLINKTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] MECHATROLINKTM and Σ-LINKTM II are trade names of YASKAWA ELECTRIC CORPORATION. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade names holder or any of its products. Compliance to this profile does not require use of the trade names. Use of the trade name requires permission of the trade name holder.
- Standard81 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment11 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment16 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61784-5-22:2024 specifies the installation profile for CPF 22 (AUTBUSTM [1]).
The installation profile is specified in Annex A. This annex is read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] AUTBUSTM is the trade name of the Kyland Technology Co., Ltd. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of Kyland Technology Co., Ltd.
- Standard23 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62443-2:2023 specifies a comprehensive set of requirements for security-related processes that IACS service providers can offer to the asset owner during integration and maintenance activities of an Automation Solution. Because not all requirements apply to all industry groups and organizations, Subclause 4.1.4 provides for the development of "profiles" that allow for the subsetting of these requirements. Profiles are used to adapt this document to specific environments, including environments not based on an IACS.
NOTE 1 The term "Automation Solution" is used as a proper noun (and therefore capitalized) in this document to prevent confusion with other uses of this term. Collectively, the security processes offered by an IACS service provider are referred to as its Security Program (SP) for IACS asset owners. In a related specification, IEC 62443-2-1 describes requirements for the Security Management System of the asset owner.
NOTE 2 In general, these security capabilities are policy, procedure, practice and personnel related. Figure 1 illustrates the integration and maintenance security processes of the asset owner, service provider(s), and product supplier(s) of an IACS and their relationships to each other and to the Automation Solution. Some of the requirements of this document relating to the safety program are associated with security requirements described in IEC 62443-3-3 and IEC 62443-4-2.
NOTE 3 The IACS is a combination of the Automation Solution and the organizational measures necessary for its design, deployment, operation, and maintenance.
NOTE 4 Maintenance of legacy system with insufficient security technical capabilities, implementation of policies, processes and procedures can be addressed through risk mitigation.
- Standard94 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62443-2-1:2024 specifies asset owner security program (SP) policy and procedure requirements for an industrial automation and control system (IACS) in operation. This document uses the broad definition and scope of what constitutes an IACS as described in IEC TS 62443‑1‑1. In the context of this document, asset owner also includes the operator of the IACS.
This document recognizes that the lifespan of an IACS can exceed twenty years, and that many legacy systems contain hardware and software that are no longer supported. Therefore, the SP for most legacy systems addresses only a subset of the requirements defined in this document. For example, if IACS or component software is no longer supported, security patching requirements cannot be met. Similarly, backup software for many older systems is not available for all components of the IACS. This document does not specify that an IACS has these technical requirements. This document states that the asset owner needs to have policies and procedures around these types of requirements. In the case where an asset owner has legacy systems that do not have the native technical capabilities, compensating security measures can be part of the policies and procedures specified in this document.
This edition includes the following significant technical changes with respect to the previous edition:
a) revised requirement structure into SP elements (SPEs),
b) revised requirements to eliminate duplication of an information security management system (ISMS), and
c) defined a maturity model for evaluating requirements.
- Standard189 pagesEnglish and French languagesale 15% off
- Amendment11 pagesEnglish languagesale 10% offe-Library read for1 day