35 - INFORMATION TECHNOLOGY
ICS 35 Details
INFORMATION TECHNOLOGY
INFORMATIONSTECHNIK. BUROTECHNIK
TECHNOLOGIES DE L'INFORMATION. MACHINES DE BUREAU
INFORMACIJSKA TEHNOLOGIJA
General Information
Frequently Asked Questions
ICS 35 is a classification code in the International Classification for Standards (ICS) system. It covers "INFORMATION TECHNOLOGY". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 18263 standards classified under ICS 35 (INFORMATION TECHNOLOGY). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35 - INFORMATION TECHNOLOGY
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies the requirements and provides guidance for establishing, implementing, maintaining and continually improving an AI (artificial intelligence) management system within the context of an organization.
This document is intended for use by an organization providing or using products or services that utilize AI systems. This document is intended to help the organization develop, provide or use AI systems responsibly in pursuing its objectives and meet applicable requirements, obligations related to interested parties and expectations from them.
This document is applicable to any organization, regardless of size, type and nature, that provides or uses products or services that utilize AI systems.
- Standard62 pagesEnglish languagee-Library read for1 day
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
support of each claimed BACnet service, either as an initiator, executor, or both,
support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(support of the BACnet network layer protocol,
support of each claimed data link option, and
support of all claimed special functionality.
- Standard1052 pagesEnglish languagee-Library read for1 day
This document specifies: protocols and commands; other parameters required to initialize communications between a vicinity integrated circuit card and a vicinity coupling device; methods to detect and communicate with one card among several cards ("anticollision"); optional means to ease and speed up the selection of one among several cards based on application criteria. This document does not preclude the addition of other existing card standards on the vicinity integrated circuit card (VICC), such as ISO/IEC 7816-6 or others listed in this document.
- Standard66 pagesEnglish languagesale 15% off
This document reports on data structure for the video data, image recording device and related clinical information. This document includes data from endoscopic video and clinical information, but not static single images or audio data that can also be recorded through these types of devices. This document does not cover the remaining data processing for data delivery to users. Figure 2 illustrates the scope of the document.
- Technical report8 pagesEnglish languagesale 15% off
This document specifies: logical data structures for a Biometric System-on-Card (BSoC); enrolment procedures; and usage of commands and data structures defined in other International Standards for BSoC. This document does not define requirements for: commands and data structures that apply to devices external to a BSoC; commands and data structures that apply to logical interfaces inside a BSoC.
- Standard20 pagesEnglish languagesale 15% off
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.
- Standard53 pagesEnglish languagee-Library read for1 day
This document describes a visualization framework for data quality in analytics and machine learning (ML). The aim is to enable stakeholders using visualization methods to assess the results of data quality measures. This visualization framework supports data quality goals.
- Technical report19 pagesEnglish languagesale 15% off
IEC 63316:2026 prescribes safeguards, test methods and compliance requirements intended to reduce the risk of electrical shock and fire associated with voltage and current at voltages greater than 60 V DC and 60 V AC. This document applies to equipment ports intended to supply and receive operating power from communications equipment ports using communication wires and cables. It covers particular requirements for circuits that are designed to transfer AC or DC power from a power sourcing equipment (PSE) (3.1.2) to a powered device (PD) (3.1.3), including repeaters, amplifiers, Optical Network Units, Remote DSLAMs, service provider terminating equipment, remote telecommunications cabinets and equipment, and midspan passive equipment connected to the PSE (3.1.2) and PD (3.1.3). The power transfer of equipment ports covered by this document uses non-mains AC voltage or non-mains DC voltage above 60 V DC classified as ES2 according to 5.2.1.2 of IEC 62368-1:2023 or, in some very controlled cases, classified as ES3 according to IEC 62368-1:2023. EXAMPLES - DC power transfer using voltages above 60 V DC but ≤ 120 V DC, classified as ES2; - Some telecommunications networks where the voltage was formerly called TNV-3 (see IEC 62368-1:2023, Table W.3), typically used for line, span or express powering outside North America, Long Range Reverse Power Feeding, HDSLx line powering ISDN, Line Powering Primary Rate E1; - Some North American telecommunications networks between the utility service providers´ PSE (3.1.2) and service providers side of the PD (3.1.3) at the PNI (3.1.8); - For DC power transfer using voltages ≥ 120 V DC at ES3: RFT circuits and the associated telecommunications network equipment and cabling used by communications service providers and communications utilities (for example, line powered E1/T1, HDSLx, SHDSLx, xDSL, repeaters, and telecommunications line powering up or line powering down converters as applicable), Optical Network Units, remote DSLAMs, etc. These RFT circuits are used between the utility service providers PSE (3.1.2) and service providers side of the PD (3.1.3) at the PNI (3.1.8). The customer facing ports of this equipment are at voltage not exceeding 60 V DC and are covered by IEC 62368-1:2023, see Annex A for deployment topologies; - For AC/DC remote powering voltage above ES1 over coaxial cable in circuits used by cable television utility service providers for repeaters, amplifiers, Optical Network Units. The customer facing ports of this equipment are at voltage not exceeding 60 V DC that are covered by IEC 62368-1:2023. NOTE 1 Any communications cable that permits power transfer between communication equipment is considered a communication cable even if communication does not take place. For example, a line powering up or line powering down converters as applicable used to power remote telecommunications equipment, can provide limited communications RFT power and not necessarily any superimposed data or signalling. This document does not cover equipment interfaces within the scope of IEC 63315. NOTE 2 IEC 63315 covers equipment intended to either supply or receive charging, or operating power from ICT interfaces using ICT wires and cables such as PoE, USB, HDMI, etc, or any of these combined. This document does not cover ringing signals that are in the scope of IEC 62368-1 or in the scope of IEC 62949:2017. This document does not cover traditional telecommunications technologies which operate at voltages not exceeding 60 V DC (circuits classified as ES1 according to 5.2.1.1 of IEC 62368-1:2023 and Tabl
- Draft36 pagesEnglish languagee-Library read for1 day
This document provides requirements and recommendations related to the concepts required to associate pharmaceutical products or groups of pharmaceutical products with an appropriate set of PhPID(s) in accordance with ISO 11616. Pharmaceutical product identifiers and the related elements are intended to represent pharmaceutical products as defined within a medicinal product by a medicines regulatory authority. While the ISO standards on IDMP can be applied to off-label usage of medicinal products, such applications are currently outside of the scope of this document. Reference to ISO 11238, ISO 11239, ISO 11240, ISO 11615, HL7 V3 messaging standards (HL7 Reference Information Model (RIM)[8], HL7 Common Product Model (CPM)[9] and HL7 V3 Structured Product Labelling (SPL)[10], and HL7 FHIR[11] can be applied for pharmaceutical product information in the context of this document.
- Technical specification66 pagesEnglish languagesale 15% off
This document establishes a common framework for software life cycle processes. Its terminology can be referenced and applied across the software industry. It contains processes, activities and tasks that can be applied during the acquisition of a software system, product, or service and during the supply, development, operation, maintenance, and disposal of software products and services. This is accomplished through the involvement of stakeholders, with the goal of achieving customer satisfaction. This document includes those aspects of system definition needed to provide the context for software systems and services. This document also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project. This document is applicable to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customised, adaptable software systems. Software includes the software portion of firmware. It applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger more complex and complete systems of systems (SoS). The processes, activities, and tasks of this document can also be applied during the acquisition of a system that contains software. This document applies to the full life cycle of software systems, products, and services, including conception, development, operations, support, and retirement, and to their acquisition and supply, whether performed internally or externally to an organization. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document can be applied in organizations and software projects using a variety of formal engineering approaches. It is applicable for agile approaches and methods, which are most widely used for software development, sustainment, and maintenance, and which are believed to be more affordable and to deliver usable products more quickly. This document does not identify or require any specific software life cycle model, development methodology, method, modelling approach, or techniques for selecting a life cycle model for the organization or project and mapping the processes, activities, and tasks in this document into that model. Using engineering judgment to help achieve the desired level of quality is also outside the scope of this document. This document does not detail information items in terms of name, format, explicit content, and recording media. ISO/IEC/IEEE 15289 identifies the content for life cycle process information items (documentation).
- Standard140 pagesEnglish languagesale 15% off
This document provides a reference model intended to support the analysis and design of B2B electronic transactions utilizing smart contracts. The model identifies and defines five core components that constitute the foundational elements for such transactions, as follows: authentication and responsibility of transaction parties; transaction procedure and execution; transaction consensus mechanism; transaction verification mechanism; security controls.
- Technical report17 pagesEnglish languagesale 15% off
This document specifies container file formats for JPEG AI codestreams as specified in Rec. ITU-T T.840.1 | ISO/IEC 6048-1 and Rec. ITU-T T.840.2 | ISO/IEC 6048-2. It defines file formats for working with image and motion sequence files on computer platforms, allowing Internet-based and other communications. This document uses already existing specifications for file formats and extends them for the embedding of JPEG AI codestreams.
- Standard11 pagesEnglish languagesale 15% off
This document provides packages of security assurance and security functional requirements that are intended to be useful in support of common usage by stakeholders. The users of this document can include consumers, developers and evaluators of secure IT products.
- Standard27 pagesEnglish languagesale 15% off
- Standard28 pagesFrench languagesale 15% off
This document specifies the basic brain–computer interface (BCI) data format including the definition of basic data elements, technology-specific information and metadata, design of an extensible and modular data structure, specification of metadata and annotation information, and the development of a standardized data format and naming convention for BCI data. This document is applicable to non-invasive BCI technologies, such as electroencephalography (EEG), magnetoencephalography (MEG), functional near-infrared spectroscopy (fNIRS) and functional magnetic resonance imaging (fMRI), and provides a comprehensive approach to BCI metadata formats in the product development environment. It takes into consideration various applications, ranging from neurological rehabilitation to human–computer interaction.
- Technical specification15 pagesEnglish languagesale 15% off
This document specifies the ISO base media file format, which is a general format forming the basis for a number of other more specific file formats. This format contains the timing, structure, and media information for timed sequences of media data, such as audio-visual presentations.
- Standard285 pagesEnglish languagesale 15% off
ISO/IEC TS 27571:2026 specifies the basic brain–computer interface (BCI) data format including the definition of basic data elements, technology-specific information and metadata, design of an extensible and modular data structure, specification of metadata and annotation information, and the development of a standardized data format and naming convention for BCI data. This document is applicable to non-invasive BCI technologies, such as electroencephalography (EEG), magnetoencephalography (MEG), functional near-infrared spectroscopy (fNIRS) and functional magnetic resonance imaging (fMRI), and provides a comprehensive approach to BCI metadata formats in the product development environment. It takes into consideration various applications, ranging from neurological rehabilitation to human-computer interaction.
- Technical specification18 pagesEnglish languagesale 15% off
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.
- Draft204 pagesEnglish languagee-Library read for1 day
This document specifies the structure of ISO/IEC 11179-3:2013 representation in W3C XML Schema suitable for communication of content between compliant registries. The schema described in this document will implement a class and attribute vocabulary that matches the conceptual model presented in ISO/IEC 11179-3:2013 in W3C XML Schema format. The purpose of the schema is for the exchange of compliant metadata, and to support the validation of messages exchanged between registries. It is not intended for the communication of data element metadata alongside the data to which the metadata refers. The document specifes the schema and the principles and conventions that were followed to map classes, attributes, and associations of the conceptual model into an acyclic, directed graph suitable for an unambiguous document-based representation.
- Standard50 pagesEnglish languagesale 15% off
This document specifies the cloud computing reference architecture (CCRA).
- Standard67 pagesEnglish languagee-Library read for1 day
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.
- Standard44 pagesEnglish languagee-Library read for1 day
This document defines terms used in the field of cloud computing.
- Standard25 pagesEnglish languagee-Library read for1 day
IEC 62264-2:2026 specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation. Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations. The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1. This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3): a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model. b) operations location model and spatial definition attribute added to allow the description of operation locations. c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions. d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document. e) updated hierarchy scope model. f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models. g) object model was added for the operations segment capability as a collection of resources related to other operations models. h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables. i) updated all objects’ relationship role table with explicit source and target names. j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables. k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models. l) added an annex explanation for implementation options for specifying values in unit of measurement a
- Draft476 pagesEnglish languagee-Library read for1 day
IEC 62541-9:2026 specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). 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 "Comment" parameter to Alarm shelving methods;
b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms;
c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived);
d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled;
e) addition of optional severities for limit alarms;
f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics;
g) addition of SupportsFilterRetain property to improve Client filtering;
h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
- Standard337 pagesEnglish languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
- Draft97 pagesEnglish languagee-Library read for1 day
The CEN/TS 18212 series specifies a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered, and are adapted to each scenario, through the definition of a variety of application profiles (APs).
This series of standards are expected to provide the evaluation methodology, the individual tests, and the APs (with their particular requirements).
This document specifies:
- tests for evaluating the interoperability of all biometric input data (received or read);
- test for evaluating the interoperability of all biometric output data (stored or transmitted);
- test for evaluating the interoperability of all exchange of information between the TOE and external components or devices.
NOTE 1 Additional parts are provided covering the specifics of each biometric mode. For each of these modalities, application-independent tests are defined, as well as a set of APs, that detail the applicable tests, the evaluation parameters, and the passing criteria.
The Technical Specifications within this series can be taken by any certification body and/or sector, to define and evaluate the requirements for their biometric products within their selected applications.
NOTE 2 Regarding biometrics for public sector applications, see also BSI TR 03121 [2] which can apply.
NOTE 3 For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881.
NOTE 4 This part defines all potential tests that could be applicable when evaluating the interoperability of a biometric product. It will be the relevant AP, the one that will specify which of these tests are applicable.
- Draft12 pagesEnglish languagee-Library read for1 day
This Technical Specification (TS) series provide a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered, and are adapted to each scenario, through the definition of a variety of application profiles (APs). In addition, this TS series provides the definition of the individual tests that can be applied to a biometric product.
This document specifies the context for the evaluation of biometric products within the context of the European Union, as well as the general requirements for such evaluation. This will be defined in a biometric mode-independent point of view, as well as not being biased by the particular application which is the target of the biometric product to be assessed.
This first part defines the following items:
- biometric evaluation process;
- biometric evaluation phases;
- how to define each particular biometric test;
- how to define the profiling for a particular application.
NOTE 1 Future parts of the CEN/TS series are planned to address the specifics of each biometric mode. For each of these modalities, this document specifies application-independent tests, as well as a set of APs, that detail the applicable tests, the evaluation parameters, and the passing criteria.
NOTE 2 Regarding biometrics for public sector applications, see also BSI TR 03121 [7] which can apply.
NOTE 3 For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881.
- Draft24 pagesEnglish languagee-Library read for1 day
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
support of each claimed BACnet service, either as an initiator, executor, or both,
support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(support of the BACnet network layer protocol,
support of each claimed data link option, and
support of all claimed special functionality.
- Standard1052 pagesEnglish languagee-Library read for1 day
This document specifies the transport and container formats for JPEG XL codestreams as specified in ISO/IEC 18181-1. This document specifies how to add metadata and extensions to JPEG XL codestreams. A file as described by this document is called a JPEG XL file.
- Standard19 pagesEnglish languagesale 15% off
IEC 62541-16:2025 defines an Information Model. The Information Model describes the basic infrastructure to model state machines.
NOTE State Machines were dealt with in IEC 62541‑5:2020, Annex B. In newer versions of IEC 62541‑5 this Annex B was removed and replaced by this document
- Standard39 pagesEnglish languagee-Library read for1 day
IEC 62541-1:2025 presents the concepts and overview of the OPC Unified Architecture (OPC UA). Reading this document is helpful to understand the remaining parts of the IEC 62541 series. Each of the other parts is briefly explained along with a suggested reading order. This first edition cancels and replaces IEC TR 62541-1 published in 2020
- Standard33 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification732 pagesEnglish languagee-Library read for1 day
IEC 62541-21:2026 defines the life cycle of Devices and Composites and mechanisms to verify their authenticity, set up their security and maintain their configuration.
The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the NamespaceUri for all NodeIds and the actual NodeIds.
- Standard58 pagesEnglish languagee-Library read for1 day
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition:
a) Annex B has been removed and used to create IEC 62451-16;
b) Annex C has been removed and used to create IEC 62451-20;
c) currency information model has been added;
d) information model for Interfaces and AddIns has been added;
e) information model for Method Metadata has been added;
f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities;
g) information model for ordered list of objects has been added;
h) PortableQualifiedName and PortableNodeId DataTypes have been added;
i) UriString DataType has been added;
j) SemanticVersionString DataType has been added;
k) AssociatedWith Reference Type has been added;
l) ConfigurationVersion Property has been added to NamespaceMetadataType;
m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added;
n) ModelVersion has been added to NamespaceMetadataType;
o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case;
p) BitFieldType and BitFieldDefinitionType have been added.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard193 pagesEnglish languagee-Library read for1 day
The document gives guidance to organizations on the incorporation of sustainability aspects for IT asset management (ITAM). This document is applicable to any organization, regardless of size, type and nature, and applies to the sustainability aspects that an organization has implemented or will implement in its IT asset management system (ITAMS) in accordance with the scope definition of ISO/IEC 19770-1. This document also addresses what is material from the perspective of the organization and of its stakeholders.
- Technical specification51 pagesEnglish languagesale 15% off
This part of IEC 62541 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates.
Programmatically produced aggregate examples are listed in Annex A.
- Standard68 pagesEnglish languagee-Library read for1 day
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.
- Standard165 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour.
The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541-3. The services to detect and access data are specified in IEC 62541-4.
Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model.
- Standard96 pagesEnglish languagee-Library read for1 day
IEC 62541-19: 2025 defines an Information Model of the OPC Unified Architecture. The Information Model describes the basic infrastructure to reference from an OPC UA Information Model to external dictionaries like IEC Common Data Dictionary or ECLASS.
- Standard19 pagesEnglish languagee-Library read for1 day
This part of IEC 62541, the IEC standards series dedicated to the OPC Unified Architecture, defines an Information Model. The Information Model describes the basic infrastructure to model file transfers.
NOTE In the previous version, File Transfer was in IEC 62541-5:2020, Annex C.
- Standard30 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 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.
- Standard46 pagesEnglish languagee-Library read for1 day
IEC 62541-24:2026 specifies an OPC UA information model to expose information, at what dates and times specific actions are executed by the OPC UA Server. Those schedules can optionally also be manipulated via the information model.
The schedule defines on which dates they are active, and can also reference global calendars representing specific dates, for example public holidays. In addition, the schedule defines times and actions that will be executed at that time. The model defines writing Variables and calling Methods but can be extended to other actions as well.
The NamespaceUri for all NodeIds defined in this document is defined in Annex A.
- Standard34 pagesEnglish languagee-Library read for1 day
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.
- Standard156 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to 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.
- Standard249 pagesEnglish languagee-Library read for1 day
IEC 62541-22:2025 specifies an OPC UA Information Model for a basic set of network related components used in other Information Models.
The initial version of this document defines parameter sets for TSN Talkers and Listeners as well as network interfaces and ports as shown in Figure 1. A future version of this document is expected to have a broader scope of other network technologies than Ethernet only.
- Standard43 pagesEnglish languagee-Library read for1 day
IEC 62541-12:2025 specifies how OPC Unified Architecture (OPC UA) Clients and Servers interact with DiscoveryServers when used in different scenarios. It specifies the requirements for the LocalDiscoveryServer, LocalDiscoveryServer-ME and GlobalDiscoveryServer. It also defines information models for Certificate management, KeyCredential management and AuthorizationServices.
Annex A informatively discusses deployment and configuration aspects.
Annex B defines NodeSet and numeric NodeIds.
Annex F provides installation rules for the LDS.
Annex H compares the Certificate management defined in this document with IETF RFC 7030.
This second edition cancels and replaces the first 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 a "Quantity Model" which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them;
b) addition of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• additional rules when ValuePrecision has negative values.
- Standard147 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses.
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
This document consists of
• a general introduction of the PubSub concepts,
• a definition of the PubSub configuration parameters,
• mapping of PubSub concepts and configuration parameters to messages and transport protocols,
• and a PubSub configuration model.
This second edition cancels and replaces the first 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 a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) Addion of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• rules have been added when ValuePrecision has negative values.
- Standard320 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. 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 the concept and modelling elements for Interfaces and AddIns;
b) addition of Currency;
c) addition of Method Meta Data to define additional attributes for Method Arguments;
d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType;
e) addition of a Non-Volatile Storage bit to AccessLevelExType;
f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType;
g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it;
h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node;
i) NamingRules have become deprecated;
j) addition of AssociatedWith ReferenceType.
- Standard143 pagesEnglish languagee-Library read for1 day
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.
- Technical specification104 pagesEnglish languagesale 15% off
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 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 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 support for ECC to UA Secure Conversation;
b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists;
c) enhancement of JSON mapping of Unions;
d) addition of Decimal data type encoding.
e) description of ECC keyUsage rules;
f) addition of Media assigned by IANA to UANodeSet definition;
g) addition of requirements for user and issuer Certificates;
h) addition of rules which specify what happens when DateTime precision is lost;
i) addition of rules to allow for the truncation of strings containing embedded nulls.
J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping.
k) requirement that TAI times be converted to UTC;
l) new possibility to omit Symbol if unknown in JSON encoding;
m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard144 pagesEnglish languagee-Library read for1 day
This document provides terminology, concepts and a description of mechanisms in the field of data exchange focusing on trusted data transactions.
Those elements can be used in the development of standards in support of trusted data transactions and constitute a basis to identify key dimensions and criteria that contribute to the trust in a data transaction between interested parties.
Therefore, those elements constitute a foundational understanding on which trusted data transactions can be based, independently of any architectural choices or technical implementation.
- Standard13 pagesEnglish languagee-Library read for1 day