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 18020 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 identifies the sections of the keyboard and specifies the general shape and relative placement of the sections. Spacing of keys and physical characteristics are covered, as are the principles governing the placement of characters and symbols on keys. It specifies a key numbering system which applies to all types of numeric, alphanumeric and composite keyboards of information technology equipment (ITE). It specifies the principles governing the placement of characters and symbols on keys used on all types of numeric, alphanumeric and composite keyboards of ITE. Although the keyboard defined by the ISO/IEC 9995 series can be used for different languages, the specifications are written as applying to Latin languages with a character path from left to right and a line progression from top to bottom. It defines characteristics related to interface 1 in Figure 1.
- Standard16 pagesEnglish languagesale 15% off
This document provides the minimum requirements for the knowledge and skills of assessment body testers and validators performing testing activities and validating activities for a conformance scheme using ISO/IEC 19790 and ISO/IEC 24759.
- Standard17 pagesEnglish languagesale 15% off
- Standard17 pagesFrench languagesale 15% off
This document specifies power usage effectiveness (PUE) as a key performance indicator (KPI) to quantify the efficient use of energy. This document: a) defines the PUE of a data centre; b) introduces PUE measurement categories; c) describes the relationship of this KPI to a data centre’s infrastructure, information technology equipment and information technology operations; d) defines the measurement, the calculation and the reporting of the parameter; e) provides information on the correct interpretation of the PUE. PUE derivatives are described in Clause 9.
- Standard35 pagesEnglish languagesale 15% off
This document defines the functionality of dead keys and repertoires of characters entered by dead keys within the general scope described in ISO/IEC 9995-1. This document is primarily intended for word-processing and text-processing applications.
- Standard9 pagesEnglish languagesale 15% off
This document defines general information and use cases for providing road safety enhancement services to all types of road users with a nomadic device in urban localized areas by sharing status or intent messages between nomadic device users and conventional ITS stations. The road users in this document include all type of road users with nomadic device such as vulnerable road users (VRU) including pedestrians, bicyclists, kickboard users, as well as connected automated mobility users including conventional vehicles, automated or connected driving system equipped vehicles. In addition, this document considers a sensor-equipped roadside ITS station with AI-supported road user behaviour detection function to support overall road safety enhancement services by sharing status or intents information of all type of road users such as VRUs without a nomadic device and road vehicles without equipped ITS stations. This document also specifies general information, such as category of nomadic device supported road safety service, overall access technology in nomadic device, actors, and communication architecture to support use cases. This document also defines safety enhancement use cases to enhance overall road safety of all types of road users with nomadic device as well as road users without nomadic device with a connectivity of sensor-equipped roadside ITS station. The use cases are applicable to provide road safety enhancement service in a specific urban localized area such as an un-signalized intersection, T-intersection, roundabout, low speed zone, school zone, no turn on red zone, weaving area, etc.
- Technical report42 pagesEnglish languagesale 15% off
This document prescribes:
— how to document a use case with an associated business context and exchange requirements;
— a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets.
This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange.
The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Standard41 pagesEnglish languagee-Library read for1 day
This document defines the conceptual framework and mechanisms for mapping information elements from building information modelling (BIM) to geographic information systems (GIS) to access the required information based on specific user requirements.
The conceptual framework for mapping BIM information to GIS is defined with the following three mapping mechanisms:
— BIM to GIS perspective definition (B2G PD);
— BIM to GIS element mapping (B2G EM);
— BIM to GIS level of detail (LOD) mapping (B2G LM).
This document does not describe physical schema integration or mapping between BIM and GIS models because the physical schema integration or mapping between two heterogeneous models is very complex and can cause a variety of ambiguity problems (see Annex D). Developing a unified information model between BIM and GIS is a desirable goal, but it is out of the scope of this document.
This document is applicable to the following concepts:
— definition for BIM to GIS conceptual mapping requirement description;
— definition of BIM to GIS conceptual mapping framework and component;
— definition of mapping for export from one schema into another.
This document does not apply to the following concepts:
— definition of any particular mapping application requirement and mechanism;
— bi-directional mapping method between BIM and GIS;
— definition of physical schema mapping between BIM and GIS;
— definition of coordinate system mapping between BIM and GIS;
— definition of relationship mapping between BIM and GIS;
— implementation of the application schema.
NOTE For cases involving requirements related to geo-referencing for providing the position and orientation of the BIM model based on GIS, other standards exist such as ISO 19111 and the Information Delivery Manual (IDM) from buildingSMART on Geo-referencing BIM.
- Technical specification32 pagesEnglish languagee-Library read for1 day
This document covers heavy rail rolling stock.
This document does not cover urban rail rolling stock.
NOTE 1 EN 17355 covers communication device requirements for urban rail rolling stock.
This document specifies:
- the functional requirements for a call for aid system and communication device system;
- the dynamic analysis of the call for aid system.
NOTE 2 "Dynamic analysis" is understood here as a sequence of actions.
NOTE 3 In a formation of vehicles where one complies with this document with one that does not, it is possible that the call for aid system is not fully functional.
NOTE 4 The call for aid system function is separate from the Passenger Alarm System (PAS) function, which is provided to deal with emergency situations. The PAS is described in EN 16334-1:2014+A1:2022.
NOTE 5 The communication device system can be different from the PAS, but it can share some or all parts of the PAS to achieve its functionalities.
NOTE 6 The PAS is regarded as a safety relevant system whereas the CFA system and communication device system are non-safety relevant aids to passengers.
- Standard21 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.
- Standard316 pagesEnglish languagesale 15% off
- Standard331 pagesFrench languagesale 15% off
- Standard647 pagesEnglish and French languagesale 15% off
This document defines biometric services used for identity assurance that are invoked over a services-based framework. It provides a generic set of biometric and identity-related functions and associated data definitions to allow remote access to biometric services. The binding of these services to specific frameworks is not included in this document but is the subject of other parts of the ISO/IEC 30108 series. Although focused on biometrics, this document includes support for other related identity assurance mechanisms such as biographic and document capabilities. IAVS is intended to be compatible with and used in conjunction with other biometric standards as described in Clause 6. Specification of biometric functionality is limited to remote (backend) services. Services between a client-side application and biometric capture devices are not within the scope of this document. Integration of biometric services as part of an authentication service or protocol is not within the scope of this document.
- Standard79 pagesEnglish languagesale 15% off
This document presents a case study of a quality management process to support the integration of medical information storage within a hierarchical storage structure, across multiple medical sites. This case study examines how it was used within the MID-NET® Project,[5] utilizing the hierarchical storage structure conformant with ISO/TS 24289. This document does not address issues related to the protection of patient privacy, network security, or the management of patient identifiers and information processes.
- Technical report16 pagesEnglish languagesale 15% off
This document specifies systems and methods for the inspection and testing of installed optical fibre cabling designed in accordance with premises cabling standards including the EN 50173 series. The test methods refer to existing standards-based procedures where they exist.
- Standard87 pagesEnglish languagee-Library read for1 day
- Standard5 pagesEnglish languagesale 15% off
The present document defines baseline security requirements for AI models and systems. The present document includes in its scope systems that incorporate deep neural networks, such as generative AI. For consistency, the term "AI systems" is used throughout the present document when framing the scope of provisions and the term "AI security", which is considered a subset of cybersecurity, is used when addressing any cybersecurity issues in the scope of the provisions. The present document is not designed for academics who are creating and testing AI systems only for research purposes (AI systems which are not going to be deployed).
- Standard16 pagesEnglish languagesale 15% off
- Standard16 pagesEnglish languagesale 15% off
- Standard16 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.
- Standard189 pagesEnglish languagesale 15% off
- Standard191 pagesFrench languagesale 15% off
- Standard380 pagesEnglish and French languagesale 15% off
This document specifies a methodology for describing and managing interactions and a format for digital communication between actors in any use case associated with the management of an asset during all life cycle stages.
It provides:
— a methodology that describes an interaction framework for a use case;
— an appropriate way to map responsibilities and interactions that provides a process context for information flow;
— a format in which the interaction framework is specified and executed.
This document is intended to promote secure, verifiable, traceable and high-quality digital IDM communication between actors during all phases of the life cycle of assets, facilitate interoperability between software applications used, and to provide a basis for data- and process-driven information exchange and traceability of communication.
- Draft95 pagesEnglish languagee-Library read for1 day
The eighth edition of ICAO Doc 9303 progresses from using the first edition of the ISO/IEC 19794 series for encoding biometric reference data in electronic machine-readable travel documents to using the ISO/IEC 39794 series for this purpose. This document specifies how to use ISO/IEC 39794-4 for fingerprint image data stored in electronic machine-readable travel documents.
- Draft26 pagesEnglish languagee-Library read for1 day
This document specifies the requirements of parameters for the physical and the link layer for systems using radio to remotely read meters. The primary focus is to use the Short Range Device (SRD) unlicensed bands. This document encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this document can be applied to various Application Layers.
- Standard104 pagesEnglish languagee-Library read for1 day
The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks.
The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.
- Standard64 pagesEnglish languagesale 15% off
- Technical specification64 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
- Standard138 pagesEnglish languagesale 15% off
- Standard150 pagesFrench languagesale 15% off
- Standard288 pagesEnglish and French languagesale 15% off
IEC 62541-8:2025 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. 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 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.
- rules have been added when ValuePrecision has negative values.
- Standard92 pagesEnglish languagesale 15% off
- Standard281 pagesEnglish languagesale 15% off
- Standard94 pagesFrench languagesale 15% off
- Standard186 pagesEnglish and French languagesale 15% off
IEC 62541-11: 2025 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.
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) a functionality has been added to support retrieving of modified events;
b) an Event has been added to indicate when a backfill occurred;
c) a new ReferenceType that can be used to indicate an external node has been defined;
d) the text has been improved to better explain the concept of annotation and remove conflicting explanations;
e) a default historian configuration (and where to find it) has been defined;
f) HistoricalEventConfigurationType, which provides general configuration information about the historical Event storage, has been added;
g) the text has been updated and optional fields have been added to HA configuration object to allow configuration to be defined for periodic data collection, not just for exception-based collection;
h) an ObjectType that can be used for external event collection has been provided as well as an example how historians can be configured.
- Standard229 pagesEnglish languagesale 15% off
- Technical specification1 pageEnglish languagesale 15% off
- Technical specification4 pagesEnglish languagesale 15% off
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.
- Standard427 pagesEnglish languagesale 15% off
- Technical specification1 pageEnglish languagesale 15% off
- Technical specification4 pagesEnglish languagesale 15% off
This document specifies considerations that can be of use to implementers and developers that elect to participate in work around updates to ISO/IEC TS 18013-7 . These considerations are intended to support the improvements, to maximize backward compatibility and to, at minimum, maintain the security and privacy properties already embodied in ISO/IEC TS 18013-7 . This document also provides additional information related to these considerations.
- Technical report3 pagesEnglish languagesale 15% off
This document provides information security controls, including implementation guidance, for health organizations. It is based on ISO/IEC 27002:2022 In addition to generic ICT equipment and software used in many other environments, the scope of this document includes software and systems specifically for healthcare, such as electronic health record systems and medical devices incorporating health software. Such medical devices can be programmed or programmable and can contain software, firmware or both. Other digital equipment (such as that for environmental and infection control, building management, and physical security), which can be used in premises where healthcare is provided, is also in scope. This document applies to information in all its aspects, whatever form the information takes (including text and numbers, sound recordings, drawings, images and video), by whatever means it has been acquired or captured, whatever means are used to store it (such as printing or writing on paper or storage electronically), and whatever means are used to transfer or exchange it (orally, by hand, by post, movement of storage media, direct links or networking). This document is for organizations of all types and sizes that provide healthcare or are custodians of personal health information for other reasons. The information that they are responsible for can be stored and processed in many possible ways and locations, including on premises or in the cloud, but remains in scope. This document applies to all physical settings where healthcare is intended to be delivered, such as hospitals, clinics and other locations or facilities designated for healthcare purposes such as ambulances and mobile imaging or diagnostic units. It also applies to care provided elsewhere, such as in residential premises. In addition to the range of settings, this document applies to all methods of service provision including remote or virtual healthcare.
- Standard72 pagesEnglish languagesale 15% off
- Standard82 pagesFrench languagesale 15% off
This document specifies the abstract class of a media thing (MThing), a basic component to construct the Internet of media things. The MThing class contains the basic APIs to: - discover other MThing(s) in the network; - connect/disconnect MThing(s); and, - support transactions (e.g. payments) using media tokens between MThings.
- Standard13 pagesEnglish languagesale 15% off
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Draft31 pagesEnglish languagee-Library read for1 day
This document specifies requirements and gives guidelines for designing accessible software for people with the widest range of physical, sensory and cognitive abilities, including those who are temporarily or situationally disabled, and the elderly. It addresses software considerations for accessibility that complement general design for usability as addressed by parts of the ISO 9241 series, especially ISO 9241-11 and ISO 9241-210.
This document is applicable to the accessibility of interactive systems. It addresses a wide range of software (e.g. home, mobile, office, web, learning support and library systems). It promotes the increased usability of systems for a wider range of users in the widest range of contexts of use.
This document does not apply to the behaviour of, or requirements for, assistive technologies (including assistive software), but it does address the use of assistive technologies as an integrated component of interactive systems.
It is intended for use by those responsible for the specification, design, development, evaluation and procurement of software platforms and software applications.
- Draft110 pagesEnglish languagee-Library read for1 day
This document provides guidelines on assistive technologies and functionalities that are to be included in accessible virtual keyboards. This document underlines which kinds of interaction modes can be embedded, which kinds of assistive technologies can be easily bound to virtual keyboards, and which kinds of functionalities are to be taken into account within virtual keyboards. This document does not apply to physical keyboards that use real physical keys or adaptable keys, which can be customized to user needs, for example with LCD display.
- Standard16 pagesEnglish languagesale 15% off
This document defines assurance-related terms and establishes an organized set of concepts to form a basis for shared understanding in the field of assurance. It benefits users of ISO/IEC/IEEE 15026-2, ISO/IEC/IEEE 15026-3 and ISO/IEC/IEEE 15026-4. Vocabulary and concepts for assurance of a service being operated and managed on an ongoing basis is not covered in this document. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered.
- Standard24 pagesEnglish languagesale 15% off
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b) the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard152 pagesEnglish languagesale 15% off
- Standard158 pagesFrench languagesale 15% off
- Standard310 pagesEnglish and French languagesale 15% off
IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard64 pagesEnglish languagesale 15% off
- Standard64 pagesFrench languagesale 15% off
- Standard128 pagesEnglish and French languagesale 15% off
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard160 pagesEnglish languagesale 15% off
- Standard173 pagesFrench languagesale 15% off
- Standard333 pagesEnglish and French languagesale 15% off
IEC 62541-10:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541-4. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.
- Standard42 pagesEnglish languagesale 15% off
- Standard45 pagesFrench languagesale 15% off
- Standard87 pagesEnglish and French languagesale 15% off
This document defines the calibration and validation of Earth observing (EO) data acquired by synthetic aperture radar (SAR) sensors and products derived from SAR data. The specified SAR sensors include general working modes and advanced working modes. In this document, calibration addresses the process to correct the data, not only geometrically and radiometrically, but also characteristically for qualitative and quantitative applications. Validation addresses an evaluation of the quality and accuracy of the calibrated data and derived products. This document also addresses the associated metadata related to calibration and validation that has not been defined in other geographic information International Standards. This document does not apply to the calibration of SAR sensors and validation of SAR sensor calibration, which are covered by ISO/TS 19159-3. However, the calibration and validation procedure can be also applied and referenced among others.
- Technical specification39 pagesEnglish languagesale 15% off
IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard245 pagesEnglish languagesale 15% off
- Standard257 pagesFrench languagesale 15% off
- Standard502 pagesEnglish and French languagesale 15% off
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains:
— subject kinds that allow to distinguish:
— product subjects representing products in product catalogues;
— catalogue subjects comprising meta data of product catalogues;
— various kinds of blocks that collect properties of complex product features, including ports and in/outlets;
— relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock;
— property kinds to distinguish between:
— static properties describing products by providing property values in product catalogues;
— dynamic properties that describe the behaviour of products;
— external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties.
This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level.
Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements.
This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard34 pagesEnglish languagee-Library read for1 day
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems.
This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary.
In scope of this document are:
— processes for the provision and exchange of product catalogues;
— rules for the geometrical representation of products;
— representation of products, product classes, ports, in/outlets, components and accessories by using IFC;
— representation of properties in IFC and the use of IFC constraints for the representation of product variants;
— representation of parametric geometry and the generation of IFC geometries for selected variants;
— calculation of article number.
The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system.
The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools.
Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard98 pagesEnglish languagee-Library read for1 day
- Standard2 pagesEnglish languagesale 15% off
This document gives guidance relating to successful, secure and usable implementation of biometric enrolment processes, while indicating risk factors that organizations which use biometric technologies can address during procurement, design, deployment and operation. Much of this document is generic to many types of applications, e.g. from national scale commercial and government applications, to closed systems for in-house operations, and to consumer applications. However, the intended application and its purpose often have influence on the necessary enrolment data quality and are taken into account when specifying an enrolment system and process. This document specifies the differences in operation relating to specific types of application, e.g. where self-enrolment is more appropriate than attended enrolment. This document focuses on mandatory, attended enrolment at fixed locations. It ultimately consolidates information relating to better practices for the implementation of biometric enrolment capability in various business contexts including considerations of process, function (system), and technology, as well as legal/privacy and policy aspects. This document provides guidance on collection and storage of biometric enrolment data and the impact on dependent processes of verification and identification. This document does not include material specific to forensic and law enforcement applications.
- Technical specification48 pagesEnglish languagesale 15% off
This document provides a mapping between the ISO/IEC 11179-34 metamodel for computable data registration and the IEEE 2791 standard for bioinformatics analyses generated by high-throughput sequencing (HTS), to facilitate the production of IEEE 2791 objects from instances of ISO/IEC 11179-34 metamodel and the registration of IEEE 2791 objects as computable data within an MDR conforming to ISO/IEC 11179-34. This document is applicable to those who are submitting data to organizations that require metadata submissions in IEEE 2791 compliant format, as well as those aiming to register IEEE 2791 objects into an MDR that conforms to ISO/IEC 11179-34.
- Standard50 pagesEnglish languagesale 15% off
This document specifies systems and methods for the inspection and testing of installed optical fibre cabling designed in accordance with premises cabling standards including the EN 50173 series. The test methods refer to existing standards-based procedures where they exist.
- Standard87 pagesEnglish languagee-Library read for1 day
This document establishes a framework for age assurance systems and describes their core characteristics, including privacy and security, for enabling age-related eligibility decisions.
- Standard29 pagesEnglish languagesale 15% off