Information service
35 Information technology
New standards
EVS-EN 9300-100:2026
Aerospace series - LOTAR LOng-Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 100: Common concepts for long-term archiving and retrieval of 3D mechanical CAD information
Scope: This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
Base documents: EN 9300-100:2026
Replaces: EVS-EN 9300-100:2018
EVS-EN ISO 16791:2026
Health informatics - Requirements for international machine-readable coding of medicinal product package identifiers (ISO 16791:2026)
Scope: This document provides requirements on identification and labelling of medicinal products from the point of manufacturing of packaged medicinal product to the point of dispensing the product.
This document outlines commonly accepted international practices for automatic identification and data capture (AIDC) barcoding solutions for applications and applies to manufacturers, distributors, healthcare facilities and all parties involved in labelling and distribution of packaged medicinal products. These users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. radio frequency identification (RFID); that technology is not addressed in this document except as for information.
This document outlines commonly accepted international practices for automatic identification and data capture (AIDC) barcoding solutions for applications and applies to manufacturers, distributors, healthcare facilities and all parties involved in labelling and distribution of packaged medicinal products. These users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. radio frequency identification (RFID); that technology is not addressed in this document except as for information.
Base documents: ISO 16791:2026; EN ISO 16791:2026
Replaces: CEN ISO/TS 16791:2020
EVS-EN IEC 62680-1-2:2026
Universal serial bus interfaces for data and power - Part 1-2: Common components - USB power delivery specification
Scope: IEC 62680-1-2:2026, the USB Power Delivery specification defines a power delivery system covering all elements of a USB system including USB Hosts, USB Devices, Hubs, Chargers and cable assemblies. This specification describes the architecture, protocols, power supply behavior, connectors and cabling necessary for managing power delivery over USB at up to 100W in SPR Mode and 240W in EPR Mode. This specification is intended to be fully compatible with and extend the existing USB infrastructure. It is intended that this specification will allow system OEMs, power supply and Peripheral developers adequate flexibility for product versatility and market differentiation without losing backwards compatibility.
IEC 62680-1-2:2026 cancels and replaces the seventh edition published in 2024 and constitutes a technical revision.
Extended Power Range (EPR) including Adjustable Voltage Supply (AVS) has been added. This document is the USB-IF publication Universal Serial Bus Power Delivery Specification Revision 3.2, Version 1.1.
IEC 62680-1-2:2026 cancels and replaces the seventh edition published in 2024 and constitutes a technical revision.
Extended Power Range (EPR) including Adjustable Voltage Supply (AVS) has been added. This document is the USB-IF publication Universal Serial Bus Power Delivery Specification Revision 3.2, Version 1.1.
Base documents: EN IEC 62680-1-2:2026; IEC 62680-1-2:2026
Replaces: EVS-EN IEC 62680-1-2:2025
EVS-EN IEC 62680-1-3:2026
Universal serial bus interfaces for data and power - Part 1-3: Common components - USB type-c® cable and connector specification
Scope: IEC 62680-1-3:2026, this specification, defines the USB Type-C® receptacles, plug and cables. The USB Type-C Cable and Connector Specification is guided by the following principles: - Enable new and exciting host and device form-factors where size, industrial design and style are important parameters - Work seamlessly with existing USB host and device silicon solutions - Enhance ease of use for connecting USB devices with a focus on minimizing user confusion for plug and cable orientation The USB Type-C Cable and Connector Specification defines a receptacle, plug, cable, and detection mechanisms that are compatible with existing USB interface electrical and functional specifications. This specification covers the following aspects that are needed to produce and use this new USB cable/connector solution in newer platforms and devices, and that interoperate with existing platforms and devices: - USB Type-C receptacles, including electro-mechanical definition and performance requirements - USB Type-C plugs and cable assemblies, including electro-mechanical definition and performance requirements - USB Type-C to legacy cable assemblies and adapters - USB Type-C-based device detection and interface configuration, including support for legacy connections - USB Power Delivery optimized for the USB Type-C connector. IEC 62680-1-3:2026 cancels and replaces the sixth edition published in 2024 and constitutes an editorial revision. This standard is the USB-IF publication Universal Serial Bus Type-C Cable and Connector Specification Revision 2.4. New release primarily includes incorporation of all approved ECNs as of the revision date plus editorial clean-up.
Base documents: IEC 62680-1-3:2026; EN IEC 62680-1-3:2026
Replaces: EVS-EN IEC 62680-1-3:2025
EVS-EN ISO/IEC 22123-1:2026
Information technology - Cloud computing - Part 1: Vocabulary (ISO/IEC 22123-1:2023)
Scope: ISO/IEC 22123-1:2023 defines terms used in the field of cloud computing.
Base documents: ISO/IEC 22123-1:2023; EN ISO/IEC 22123-1:2026
Replaces: EVS-ISO/IEC 22123-1:2025
EVS-EN ISO/IEC 22123-2:2026
Information technology - Cloud computing - Part 2: Concepts (ISO/IEC 22123-2:2023)
Scope: This document specifies concepts used in the field of cloud computing. These concepts expand upon the cloud computing vocabulary defined in ISO/IEC 22123-1 and provide a foundation for other documents that are associated with cloud computing.
Base documents: ISO/IEC 22123-2:2023; EN ISO/IEC 22123-2:2026
Replaces: EVS-ISO/IEC 22123-2:2025
EVS-EN ISO/IEC 22123-3:2026
Information technology - Cloud computing - Part 3: Reference architecture (ISO/IEC 22123-3:2023)
Scope: This document specifies the cloud computing reference architecture (CCRA).
Base documents: ISO/IEC 22123-3:2023; EN ISO/IEC 22123-3:2026
Replaces: EVS-ISO/IEC 22123-3:2025
CEN ISO/TS 21405:2026
Health informatics - Identification of medicinal products - Methodology and framework for the development and representation of IDMP ontology (ISO/TS 21405:2026)
Scope: This document describes a standardized methodology and framework for the development and representation of an ontology that supports a global, open-source approach to implementing the ISO standards on the identification of medicinal products (IDMP) (ISO 11615, ISO/TS 20443, ISO/TS 20451, ISO 11238; ISO/TS 19844, ISO 11239, ISO/TS 20440, and ISO 11240). Realization of the full potential of IDMP requires fully self-describing data. For this purpose, this document describes a methodology and framework that complements the existing conceptual and logical models in the ISO documents on IDMP with an IDMP ontology that enables deep, semantic interoperability based on findable, accessible, interoperable and reusable (FAIR) data principles. This methodology and framework enhance the usage of the IDMP data model as the foundation of medicinal product identification and will ultimately enable collaboration towards drug safety and overall operational efficiency.
This document also describes a methodology for the agile adaptation of the ISO documents on IDMP in connection with cross-jurisdictional IDMP-related legislation and initiatives. This document is intended to be complementary to and independent from formal regulatory guidance. Thus, it enables cross-jurisdictional consistency and supports stakeholders in their regional implementations of IDMP standards. This document does not mandate any specific ontology as an implementation tool, nor is it an instructional guideline on how to build ontologies, which is out of scope of this document.
This document includes key use cases described in the ISO documents on IDMP ISO 11615, ISO 11238 and ISO/TS 19844, as well as further use cases arising from the comprehensive deployment of the ISO documents on IDMP via an ontological framework. Thus, an ontology that represents the IDMP standards aims to cover the complete collection of ISO standards on IDMP regarding key interoperability issues that implementing stakeholders are facing.
This document also describes a methodology for the agile adaptation of the ISO documents on IDMP in connection with cross-jurisdictional IDMP-related legislation and initiatives. This document is intended to be complementary to and independent from formal regulatory guidance. Thus, it enables cross-jurisdictional consistency and supports stakeholders in their regional implementations of IDMP standards. This document does not mandate any specific ontology as an implementation tool, nor is it an instructional guideline on how to build ontologies, which is out of scope of this document.
This document includes key use cases described in the ISO documents on IDMP ISO 11615, ISO 11238 and ISO/TS 19844, as well as further use cases arising from the comprehensive deployment of the ISO documents on IDMP via an ontological framework. Thus, an ontology that represents the IDMP standards aims to cover the complete collection of ISO standards on IDMP regarding key interoperability issues that implementing stakeholders are facing.
Base documents: ISO/TS 21405:2026; CEN ISO/TS 21405:2026
ISO/IEC 15067-5:2026
Information technology — Home Electronic System (HES) application model — Part 5: A safety framework and guidelines for control and data communication messages
Scope: This document addresses the safety of persons and premises when using devices and appliances ("products") with interfaces to a communications network in a home or building ("premises"). Such products are called "networked appliances" and "networked products." This document specifies basic requirements for safer operation of products that can be controlled remotely via a connection to a communications network. The network can enable such products to form integrated applications. These products can interact via the premises network and can be controlled remotely from within the premises and from a wide area network outside connected to the premises network via a communications gateway.
Recommendations and methods for remote-control message screening and guidelines for selecting messages to minimize risk are specified. These specifications can enhance safety in a home control system (hcs).
The safety requirements specified in this document apply together with any relevant product safety standards.
NOTE 1 ISO/IEC HES standards are identified by HES or "Home Electronic System" in the title.
NOTE 2 This document addresses conditions of normal use and fault conditions throughout the lifetime of a product. Sabotage, force majeure, and intentional damage are not addressed in this document.
NOTE 3 This document is not intended for safety-related equipment such a fire-detection and suppression system.
NOTE 4 "Networked applications" and "networked products" describe the same category of devices and are used interchangeably in this document.
Recommendations and methods for remote-control message screening and guidelines for selecting messages to minimize risk are specified. These specifications can enhance safety in a home control system (hcs).
The safety requirements specified in this document apply together with any relevant product safety standards.
NOTE 1 ISO/IEC HES standards are identified by HES or "Home Electronic System" in the title.
NOTE 2 This document addresses conditions of normal use and fault conditions throughout the lifetime of a product. Sabotage, force majeure, and intentional damage are not addressed in this document.
NOTE 3 This document is not intended for safety-related equipment such a fire-detection and suppression system.
NOTE 4 "Networked applications" and "networked products" describe the same category of devices and are used interchangeably in this document.
Base documents:
ISO/IEC TS 23220-2:2026
Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 2: Data objects and encoding rules for generic eID systems
Scope: This document specifies data objects and encoding rules of generic eID-Systems in terms of building blocks for mobile document system infrastructures, and standardizes generic data models for data exchanges between mdoc apps and verification applications.
This document is applicable to entities involved in specifying, architecting, designing, testing, maintaining, administering, and operating a mobile eID-System in parts or as a whole.
This document is applicable to entities involved in specifying, architecting, designing, testing, maintaining, administering, and operating a mobile eID-System in parts or as a whole.
Base documents:
Replaces: ISO/IEC TS 23220-2:2024
ISO 14306-4:2026
Industrial automation systems and integration — JT file format specification for 3D visualization — Part 4: Version 3
Scope: This document defines the syntax and semantics of a file format for the 3D visualization and interrogation of lightweight geometry and product manufacturing information derived from CAD systems, using visualization software tools that do not need the full capability of a CAD system.
This document has been adopted as a 3D visualization capability in addition to the ISO 10303 series.
The ISO 10303 series are the ISO standards adopted for the engineering data exchange, sharing and long-term archiving of product definition information throughout the product lifecycle.
In this document 3D visualization is defined as the visual presentation on a screen or another media of graphical and textual 3-dimensional representations of a set of data representing an object, information or results of a computational process in order to enable decision process by a human looking at the data visualized in a medium.
The ISO 14306 file format specification for 3D visualization includes data descriptions that can represent the following data:
facet information (triangles), stored with geometry compression techniques;
visual attributes such as lights, textures and materials;
product manufacturing information (PMI);
boundary representation (b-rep) solid model shape representation and associated metadata;
configuration representations; and
delivery methods such as asynchronous streaming of content.
The file format specification for 3D visualization does not specify the implementation of, or definition of a run-time architecture for viewing and/or processing ISO 14306 data.
This document has been adopted as a 3D visualization capability in addition to the ISO 10303 series.
The ISO 10303 series are the ISO standards adopted for the engineering data exchange, sharing and long-term archiving of product definition information throughout the product lifecycle.
In this document 3D visualization is defined as the visual presentation on a screen or another media of graphical and textual 3-dimensional representations of a set of data representing an object, information or results of a computational process in order to enable decision process by a human looking at the data visualized in a medium.
The ISO 14306 file format specification for 3D visualization includes data descriptions that can represent the following data:
facet information (triangles), stored with geometry compression techniques;
visual attributes such as lights, textures and materials;
product manufacturing information (PMI);
boundary representation (b-rep) solid model shape representation and associated metadata;
configuration representations; and
delivery methods such as asynchronous streaming of content.
The file format specification for 3D visualization does not specify the implementation of, or definition of a run-time architecture for viewing and/or processing ISO 14306 data.
Base documents:
Replaces: ISO 14306:2017
ISO/IEC TS 23220-4:2026
Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 4: Protocols and services for operational phase
Scope: This document specifies building blocks for the implementation of the operational phase of mobile eID systems and any other mdoc for national bodies or document-specific standards to create profiles according to their needs.
This document specifies the interface between the mdoc app and mdoc reader and the interface between the mdoc reader and the issuing authority infrastructure.
More specifically, this document defines transport protocols for various RF solutions and for over the internet. It defines the application layers, such as the request-response protocols between an mdoc app and mdoc reader and between an mdoc reader and issuing authority.
It further defines the security mechanism for issuer authentication, mdoc authentication and credential holder verification.
This document also specifies mechanisms enabling parties other than the issuing authority to:
use a machine to obtain the mdoc data;
bind the mdoc to the mdoc holder;
authenticate the origin of the mdoc data;
verify the integrity of the mdoc data.
The following items are out of scope for this document:
provisioning of the mdoc data (this is covered by ISO/IEC TS 23220-3);
how holder’s consent to share data is obtained;
requirements on storage of mdoc data and mdoc private keys.
Finally, it provides information to create a conformant profile.
This document specifies the interface between the mdoc app and mdoc reader and the interface between the mdoc reader and the issuing authority infrastructure.
More specifically, this document defines transport protocols for various RF solutions and for over the internet. It defines the application layers, such as the request-response protocols between an mdoc app and mdoc reader and between an mdoc reader and issuing authority.
It further defines the security mechanism for issuer authentication, mdoc authentication and credential holder verification.
This document also specifies mechanisms enabling parties other than the issuing authority to:
use a machine to obtain the mdoc data;
bind the mdoc to the mdoc holder;
authenticate the origin of the mdoc data;
verify the integrity of the mdoc data.
The following items are out of scope for this document:
provisioning of the mdoc data (this is covered by ISO/IEC TS 23220-3);
how holder’s consent to share data is obtained;
requirements on storage of mdoc data and mdoc private keys.
Finally, it provides information to create a conformant profile.
Base documents:
Replaced standards
CLC/TR 50173-99-1:2007
Cabling guidelines in support of 10 GBASE-T
Scope: This Technical Report a) specifies the transmission performance for channels to support 10 GBASE-T as specified in IEEE 802.3an, b) specifies the methods to assess whether installed Class E and Class F channels meet IEEE 802.3an requirements, c) provides mitigation techniques to improve the performance of an existing installation to meet the IEEE 802.3an requirements.
Base documents: CLC/TR 50173-99-1:2007
EVS-EN 9300-100:2018
Aerospace series - LOTAR - Long Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 100: Common concepts for Long term archiving and retrieval of CAD 3D mechanical information
Scope: 1.1 Introduction
This European Standard defines common fundamental concepts for Long Term Archiving and Retrieval of CAD mechanical information for elementary parts and assemblies. It details the "fundamentals and concepts" of EN 9300-003 in the specific context of Long Term Archiving of CAD mechanical models.
CAD mechanical information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, Geometric Dimensioning and Tolerancing with Form Features.
The EN 9300-1XX family is organized as a sequence of parts, each building on the previous in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX family.
As technology matures additional parts will be released in order to support new requirements within the aerospace community.
1.2 In scope
The present part describes:
- the fundamentals and concepts for Long Term Archiving and Retrieval of CAD 3D mechanical information;
- the document structure of the EN 9300-1XX family, and the links between all these parts;
- the qualification methods for long term preservation of archived CAD mechanical information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of Archive Information Packages for CAD data.
1.3 Out of Scope
The following are out of scope for this part:
- Long Term Archiving of CAD 2D drawings;
- other CAD business disciplines, such as piping, tubing, electrical harnesses, composite, sheet metal design, kinematics.
This version does not include:
- fundamental and concepts for parts EN 9300-120 version 2, EN 9300-125, 1 EN 9300-130.
This European Standard defines common fundamental concepts for Long Term Archiving and Retrieval of CAD mechanical information for elementary parts and assemblies. It details the "fundamentals and concepts" of EN 9300-003 in the specific context of Long Term Archiving of CAD mechanical models.
CAD mechanical information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, Geometric Dimensioning and Tolerancing with Form Features.
The EN 9300-1XX family is organized as a sequence of parts, each building on the previous in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX family.
As technology matures additional parts will be released in order to support new requirements within the aerospace community.
1.2 In scope
The present part describes:
- the fundamentals and concepts for Long Term Archiving and Retrieval of CAD 3D mechanical information;
- the document structure of the EN 9300-1XX family, and the links between all these parts;
- the qualification methods for long term preservation of archived CAD mechanical information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of Archive Information Packages for CAD data.
1.3 Out of Scope
The following are out of scope for this part:
- Long Term Archiving of CAD 2D drawings;
- other CAD business disciplines, such as piping, tubing, electrical harnesses, composite, sheet metal design, kinematics.
This version does not include:
- fundamental and concepts for parts EN 9300-120 version 2, EN 9300-125, 1 EN 9300-130.
Base documents: EN 9300-100:2018
Replaced: EVS-EN 9300-100:2026
CEN ISO/TS 16791:2020
Health informatics - Requirements for international machine-readable coding of medicinal product package identifiers (ISO/TS 16791:2020)
Scope: This document provides guidelines on identification and labelling of medicinal products from the point of manufacture of packaged medicinal product to the point of dispensing the product.
This document outlines best practice for AIDC barcoding solutions for applications. Users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. Radio Frequency Identification (RFID).
This document outlines best practice for AIDC barcoding solutions for applications. Users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. Radio Frequency Identification (RFID).
Base documents: ISO/TS 16791:2020; CEN ISO/TS 16791:2020
Replaced: EVS-EN ISO 16791:2026
CLC IEC/TR 62541-2:2021
OPC unified architecture - Part 2: Security Model
Scope: This part of IEC 62541 describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware, and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It provides definition of common security terms that are used in this and other parts of the OPC UA specification. It gives an overview of the security features that are specified in other parts of the OPC UA specification. It references services, mappings, and Profiles that are specified normatively in other parts of the OPC UA Specification. It provides suggestions or best practice guidelines on implementing security. Any seeming ambiguity between this part and one of the other normative parts does not remove or reduce the requirement specified in the other normative part.
Base documents: IEC/TR 62541-2:2020; CLC IEC/TR 62541-2:2021
Replaced: EVS-EN IEC 62541-2:2026
ISO/IEC TS 23220-2:2024
Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 2: Data objects and encoding rules for generic eID systems
Scope: This document specifies data objects and encoding rules of generic eID-Systems in terms of building blocks for mobile document system infrastructures, and standardizes generic data models for data exchanges between mdoc apps and verification applications.
This document is applicable to entities involved in specifying, architecting, designing, testing, maintaining, administering, and operating a mobile eID-System in parts or as a whole.
This document is applicable to entities involved in specifying, architecting, designing, testing, maintaining, administering, and operating a mobile eID-System in parts or as a whole.
Base documents:
Replaced: ISO/IEC TS 23220-2:2026
EVS-EN IEC 62680-1-2:2025
Universal serial bus interfaces for data and power - Part 1-2: Common components - USB power delivery specification
Scope: The USB Power Delivery specification defines a power delivery system covering all elements of a USB system including Hosts, Devices, Hubs, Chargers and cable assemblies. This specification describes the architecture, protocols, power supply behavior, connectors and cabling necessary for managing power delivery over USB at up to 100W. This specification is intended to be fully compatible and extend the existing USB infrastructure. It is intended that this specification will allow system OEMs, power supply and peripheral developers adequate flexibility for product versatility and market differentiation without losing backwards compatibility. IEC 62680-1-2:2024 cancels and replaces the sixth edition published in 2022 and constitutes a technical revision. Extended Power Range (EPR) including Adjustable Voltage Supply (AVS) has been added. This document is the USB-IF publication Universal Serial Bus Power Delivery Specification Revision 3.2, Version 1.0.
Base documents: IEC 62680-1-2:2024; EN IEC 62680-1-2:2025
Replaced: EVS-EN IEC 62680-1-2:2026
EVS-EN IEC 62680-1-3:2025
Universal serial bus interfaces for data and power - Part 1-3: Common components - USB type-C cable and connector specification
Scope: This specification defines the USB Type-C® receptacles, plug and cables. The USB Type-C Cable and Connector Specification is guided by the following principles: - Enable new and exciting host and device form-factors where size, industrial design and style are important parameters - Work seamlessly with existing USB host and device silicon solutions - Enhance ease of use for connecting USB devices with a focus on minimizing user confusion for plug and cable orientation The USB Type-C Cable and Connector Specification defines a receptacle, plug, cable, and detection mechanisms that are compatible with existing USB interface electrical and functional specifications. This specification covers the following aspects that are needed to produce and use this new USB cable/connector solution in newer platforms and devices, and that interoperate with existing platforms and devices: - USB Type-C receptacles, including electro-mechanical definition and performance requirements - USB Type-C plugs and cable assemblies, including electro-mechanical definition and performance requirements - USB Type-C to legacy cable assemblies and adapters - USB Type-C-based device detection and interface configuration, including support for legacy connections - USB Power Delivery optimized for the USB Type-C connector The USB Type-C Cable and Connector Specification defines a standardized mechanism that supports Alternate Modes, such as repurposing the connector for docking-specific applications. IEC 62680-1-3:2024 cancels and replaces the fifth edition published in 2022 and constitutes a technical revision. This standard is the USB-IF publication Universal Serial Bus Type-C Cable and Connector Specification Revision 2.3. New release primarily for deprecating the Audio Adapter Accessory Mode and replacing it with the Liquid Corrosion Mitigation Mode, and for updating the Multi-port Charger Shared Capacity definition and behaviors. Also includes incorporation of all approved ECNs as of the revision date plus editorial clean-up.
Base documents: IEC 62680-1-3:2024; EN IEC 62680-1-3:2025
Replaced: EVS-EN IEC 62680-1-3:2026
EVS-ISO/IEC 22123-1:2025
Information technology — Cloud computing — Part 1: Vocabulary (ISO/IEC 22123-1:2023, identical)
Scope: This document defines terms used in the field of cloud computing.
Base documents: ISO/IEC 22123-1:2023
Replaced: EVS-EN ISO/IEC 22123-1:2026
EVS-ISO/IEC 22123-2:2025
Information technology — Cloud computing — Part 2: Concepts (ISO/IEC 22123-2:2023, identical)
Scope: This document specifies concepts used in the field of cloud computing. These concepts expand upon the
cloud computing vocabulary defined in ISO/IEC 22123-1 and provide a foundation for other documents
that are associated with cloud computing.
This document also provides detailed descriptions on the application of these concepts in cloud
computing.
cloud computing vocabulary defined in ISO/IEC 22123-1 and provide a foundation for other documents
that are associated with cloud computing.
This document also provides detailed descriptions on the application of these concepts in cloud
computing.
Base documents: ISO/IEC 22123-2:2023
Replaced: EVS-EN ISO/IEC 22123-2:2026
EVS-ISO/IEC 22123-3:2025
Information technology — Cloud computing — Part 3: Reference architecture (ISO/IEC 22123-3:2023, identical)
Scope: This document specifies the cloud computing reference architecture (CCRA).
Base documents: ISO/IEC 22123-3:2023
Replaced: EVS-EN ISO/IEC 22123-3:2026
Drafts
prEN ISO 11615
Health informatics - Identification of medicinal products - Data elements and structures for the unique identification and exchange of regulated medicinal product information (ISO/DIS 11615:2026)
Scope: ISO 11615:2017 establishes definitions and concepts and describes data elements and their structural relationships, which are required for the unique identification and the detailed description of Medicinal Products. Taken together, the standards listed in the Introduction define, characterise and uniquely identify regulated Medicinal Products for human use during their entire life cycle, i.e. from development to authorisation, post-marketing and renewal or withdrawal from the market, where applicable. Furthermore, to support successful information exchange in relation to the unique identification and characterisation of Medicinal Products, the use of other normative IDMP messaging standards is included, which are to be applied in the context of ISO 11615:2017.
Base documents: prEN ISO 11615; ISO/DIS 11615:2026
prEN ISO 16484-5
Building automation and control systems (BACS) - Part 5: Data communication protocol (ISO/DIS 16484-5:2026)
Scope: The purpose of this document is to define data communication services and protocols for computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.
Base documents: ISO/FDIS 16484-5; prEN ISO 16484-5
EN 50716:2023/prA1:2026
Railway Applications - Requirements for software development
Scope: The amendment will address misunderstandings on provisions for AI/ML by providing additional guidance and clarifications without changing the fundamental technical requirements and recommendations of the standard. The amendment and its limitation to broadly editorial changes is based on following considerations:
• Limited Standardization for AI: While AI/ML holds promise for various applications, current standardization efforts specific to AI/ML in safety-critical domains like railway are still in their early stages. This lack of mature and widely accepted standards for verifying and validating AI/ML systems in these contexts makes it challenging to reference or directly incorporate such technologies into the scope of EN 50716 (with less restrictive provisions) at this time.
• Promoting Flexibility and Innovation: By clarifying the existing provisions and adding guidance without imposing new requirements, the amendment allows for flexibility and encourages developers to explore the potential of AI/ML (where is safe to do so).
The following areas have already been identified by WG28 for the amendment:
• Explicitly remind the scope of Table A.3: State that the table's techniques and measures are primarily intended for the design of the software architecture for safety-related functions (e.g. does not strictly apply to support tools).
• Provide guidance on AI/ML usage: Explicitly acknowledge the potential of AI/ML in non-safety-critical areas and offer examples of possible applications (complementary to current recommendation for Basic Integrity, “-”, in Table A.3 for 13. Artificial Intelligence and Machine Learning).
• Guidance on Support Tools: Ensure a consistent understanding of the AI/ML provisions related to support tools (& programming languages).
This represent current view on potential changes - other areas may be identified during the amendment drafting, keeping into account the above mentioned limitations to broadly editorial changes.
• Limited Standardization for AI: While AI/ML holds promise for various applications, current standardization efforts specific to AI/ML in safety-critical domains like railway are still in their early stages. This lack of mature and widely accepted standards for verifying and validating AI/ML systems in these contexts makes it challenging to reference or directly incorporate such technologies into the scope of EN 50716 (with less restrictive provisions) at this time.
• Promoting Flexibility and Innovation: By clarifying the existing provisions and adding guidance without imposing new requirements, the amendment allows for flexibility and encourages developers to explore the potential of AI/ML (where is safe to do so).
The following areas have already been identified by WG28 for the amendment:
• Explicitly remind the scope of Table A.3: State that the table's techniques and measures are primarily intended for the design of the software architecture for safety-related functions (e.g. does not strictly apply to support tools).
• Provide guidance on AI/ML usage: Explicitly acknowledge the potential of AI/ML in non-safety-critical areas and offer examples of possible applications (complementary to current recommendation for Basic Integrity, “-”, in Table A.3 for 13. Artificial Intelligence and Machine Learning).
• Guidance on Support Tools: Ensure a consistent understanding of the AI/ML provisions related to support tools (& programming languages).
This represent current view on potential changes - other areas may be identified during the amendment drafting, keeping into account the above mentioned limitations to broadly editorial changes.
Base documents: EN 50716:2023/prA1:2026