IEC

IEC 62541-6:2020 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-4:2020 RLV contains both the official IEC International Standard and its Redline version. The Redline version is available in English only and provides you with a quick and easy way to compare all the changes between the official IEC Standard and its 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.

This document of IEC 63372 describes principles and methodologies, specifies requirements and provides guidance on quantification and communication of Carbon footprint (sum of GHG emissions and removals), emission reductions and avoided emissions from Electric and Electronic (EE) products and systems. This document is applicable to EE products and systems as a horizontal standard.

Specifies process requirements for the secure development of products used in industry automation and control systems. It defines a secure development life-cycle (SDL) including security requirements definition, secure design, secure implementation (including coding guidelines), verification and validation, defect management, patch management and product end-of-life. These requirements can be applied to new or existing processes for developing, maintaining and retiring hardware, software or firmware for new or existing products. These requirements apply to the developer and maintainer of the product, but not to the user of the product.

IEC/TR 62837:2013(E) provides to the technical committees a framework for the development and adaptation of documents in order to improve energy efficiency in manufacturing, process control and industrial facility management.

IEC 61406-1:2022 specifies minimum requirements for a globally unique identification of physical objects which also constitutes a link to its related digital information. This identification is designated hereinafter as "Identification Link" (IL), with the encoded data designated as IL string. The IL string has the data-format of a link (URL). The IL is machine-readable and is attached to the physical object in a 2D symbol or NFC tag. The requirements in this standard apply to physical objects: - that are provided by the manufacturer as an individual unit, - and that have already been given a unique identity by the manufacturer. This document does not specify any requirements on the content and the layout of nameplates/typeplates (e.g. spatial arrangement, content of the plain texts, approval symbols etc.).

IEC 61406-2 complements IEC 61406-1 with specific rules for encoding characteristics of marked physical objects when relevant. This includes cases where the uniqueness of the Identification Link string is not limited to relating only to an individual item but may alternatively relate to a product type, lot or batch. 

This part 3 of the IEC 63278 series aims at the secure and interoperable exchange of information between stakeholders in value chains. This includes how integrity, authenticity, and confidentiality are realized within the AAS information model. It refines AAS security requirements from IEC 63278-1 affecting the structure of the information model as defined in IEC 63278-2 NP and defines the respective security information model complementary to IEC 63278-2.

This document describes a framework of trust for the processing of multi-sourced data that includes data use obligations and controls, data provenance, chain of custody, security and immutable proof of compliance as elements of the framework.

Cloud computing data flow, data categories and data use: Fundamentals

Common technologies and techniques

Cloud Computing terminology