35.240 - Applications of information technology
ICS 35.240 Details
Applications of information technology
Anwendungen der Informationstechnik
Applications des technologies de l'information
Uporabniške rešitve informacijske tehnike in tehnologije
General Information
Frequently Asked Questions
ICS 35.240 is a classification code in the International Classification for Standards (ICS) system. It covers "Applications of 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 7630 standards classified under ICS 35.240 (Applications of 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.240 - Applications of information technology
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
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 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 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 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
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
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 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 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
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
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
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 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
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
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
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
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
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-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
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-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
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
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-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-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
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.
- Technical specification26 pagesEnglish languagesale 15% off
IEC 62541-23:2025 defines ReferenceTypes commonly used in industrial Information Models. They are more specific than the ReferenceTypes in IEC 62541‑3 which are an inherent part of the OPC UA Address Space Model.
- Standard28 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
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 part of IEC 62541 belongs to the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour.
The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4.
This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13.
Conventions for Historical Access Clients are informatively provided in Annex A.
- Standard77 pagesEnglish languagee-Library read for1 day
IEC 62541-17:2025 provides a definition of AliasNames functionality. AliasNames provide a manner of configuring and exposing an alternate well-defined name for any Node in the system. This is analogous to the way domain names are used as an alias to IP addresses in IP networks. Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related Node on a Server. An aggregating Server can collect these AliasNames from multiple Servers and provide a lookup Method to allow Client applications to discover NodeIds on a system wide basis. An aggregating Server could also define AliasNames for Nodes in other Servers that do not support AliasNames. A GDS can be constructed that would automatically aggregate all AliasNames that are defined on any Server that has registered with the GDS. In this case, the GDS also provides the lookup mechanism for Clients at a well-known endpoint and address.
- Standard28 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 specification518 pagesEnglish languagee-Library read for1 day
This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However, as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12), ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
This document specifies the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE, NR and their successors) as:
1) In-Vehicle System (IVS)/vehicle,
2) Mobile Network Operator (MNO),
3) Public Safety Answering Point (PSAP),
and to provide conformance tests for actor groups 1) – 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.
NOTE 3 These conformance tests are based on the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and
revise Conformance Test Procedures (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 112-eCall (Pan European eCall) tests provided in EN 16454 are
specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO’s, and PSAPs, required to ensure and demonstrate compliance to EN 17184.
The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Standard188 pagesEnglish languagee-Library read for1 day
This document defines the concepts and definitions and is the first part of a set of standards to define the framework for digital twins in the built environment. It includes the terms and definitions, the relation with building information modelling and addresses the lack of standards for the qualitative specification of a digital twin, which can include geometric, attributive, structural and infrastructural quality, as applicable.
This document is based on the experiences obtained in use cases [1] and documents from other technical committees, including ISO/IEC 30173.
This document can be used in the development of other standards and in support of communications among diverse, interested parties or stakeholders. This initiative aims to define an ecosystem of digital twins opening the opportunity to release even greater value, using data for the public good.
- Standard13 pagesEnglish languagee-Library read for1 day
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.
- Draft36 pagesEnglish languagee-Library read for1 day
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.
- Standard479 pagesEnglish languagesale 15% off
This document defines the policy, functional and security requirements on (qualified) trust services for electronic ledger. This includes requirements to ensure:
- their provision by one or more trust service providers;
- the establishment of the origin of data records in the ledger;
- the unique sequential chronological ordering of data records in the ledger;
- the recording of data in such a way that any subsequent change to the data is immediately detectable, ensuring their integrity over time.
- Technical specification18 pagesEnglish languagee-Library read for1 day
This document specifies the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM) and performed with a scientific computational tool (SCT).
This document is applicable to the thermal and mechanical finite element analysis (FEA) of arc, laser and electron beam welding processes for the purpose of calculating the effects of welding processes, and in particular, residual stresses and distortion, in support of structural integrity assessment.
- Standard56 pagesEnglish languagee-Library read for1 day
In respect of pan European eCall (operating requirements defined in EN 16072), this document defines
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to
automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102.
This document makes reference to those provisions but does not duplicate them.
- Standard38 pagesEnglish languagee-Library read for1 day
1.1 In Scope
From Clause 8 to Clause 15, the scope includes:
- Management Information;
- Product Design;
- Change Management;
- Documents;
- Application of PDM-specific metadata (see EN 9300-21);
- Definition of PDM-specific metadata for Archive Information Packages (AIP).
Common Meta Data archive package requirements defined in EN 9300-21.
A visual representation of the scope of this document can be seen in Figure 1. An overview of the various parts in the EN 9300-200 series is provided in Table 1.
[Figure 1 - Scope of EN 9300-210 As Designed]
[Table 1 - EN 9300 Part 200 series]
This document does not attempt to specify how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). Integration of PDM metadata with other domain and common metadata will be in EN 9300-021.
The scope of EN 9300-210 is same as the EN 9300-001.
1.2 Out of scope
This document does not attempt to describe how to create an OAIS/LOTAR information package. Nor does it address common issues in the archive domain, such as: snapshot vs. incremental archival methods (which are determined as part of the implementation of an archive system), or package-to-package linkages (Meta Data WG) or how to identify metadata for an archival package (Meta Data WG). For integration of PDM metadata with other domain and common metadata, see EN 9300-21.
- Standard38 pagesEnglish languagee-Library read for1 day
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 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.
- Draft43 pagesEnglish languagee-Library read for1 day
ISO/IEC 15067-5:2026 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.
- Standard18 pagesEnglish languagesale 15% off
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.
- Technical specification32 pagesEnglish languagesale 15% off