Infoteenus
35 INFOTEHNOLOOGIA
Uued standardid
EVS-EN IEC 62541-13:2026
OPC Unified Architecture - Part 13: Aggregates
Käsitlusala:
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.
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.
Alusdokumendid:
IEC 62541-13:2025; EN IEC 62541-13:2026
Asendab:
EVS-EN IEC 62541-13:2020
ISO/IEC 8808:2026
Information technology for learning, education and training — Online course information model
Käsitlusala:
This document presents an online course information model, highlighting common elements and their descriptions. This document also describes online courses. Its purpose is to support conceptual understanding of online courses and instructional strategies in online education. This model can be used to inform about the design and development of online courses, and to support migration of online courses between different platforms under the premise of copyright transfer.
The information model of online courses can be extended based on metadata of learning resource (MLR) rules.
The information model of online courses can be extended based on metadata of learning resource (MLR) rules.
Alusdokumendid:
EVS-EN IEC 62541-10:2026
OPC Unified Architecture - Part 10: Programs
Käsitlusala:
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.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.
Alusdokumendid:
IEC 62541-10:2025; EN IEC 62541-10:2026
Asendab:
EVS-EN IEC 62541-10:2020
EVS-EN IEC 62541-100:2026
OPC unified architecture - Part 100: Devices
Käsitlusala:
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.
• 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.
Alusdokumendid:
IEC 62541-100:2025; EN IEC 62541-100:2026
Asendab:
EVS-EN 62541-100:2015
ISO/IEC 21134:2026
Information technology — Computer graphics, image processing and environmental data representation — Benchmarking of integrated indoor localization and tracking methods using dead reckoning
Käsitlusala:
This document specifies the reference framework for the benchmarking of integrated indoor localization and tracking methods (LTMs) using dead reckoning in areas of:
master sets and test environments;
benchmark metrics;
benchmarking process;
conformance.
master sets and test environments;
benchmark metrics;
benchmarking process;
conformance.
Alusdokumendid:
ISO/IEC 23008-3:2026
Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 3: 3D audio
Käsitlusala:
This document specifies technology that supports the efficient transmission of immersive audio signals and flexible rendering for the playback of immersive audio in a wide variety of listening scenarios. These include home theatre setups with 3D loudspeaker configurations, 22.2 loudspeaker systems, automotive entertainment systems and playback over headphones connected to a tablet or smartphone.
Alusdokumendid:
Asendab:
ISO/IEC 23008-3:2022
ISO 16484-6:2026
Building automation and control systems (BACS) — Part 6: Data communication conformance testing
Käsitlusala:
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.
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.
Alusdokumendid:
Asendab:
ISO 16484-6:2024
EVS-EN IEC 62541-4:2026
OPC unified architecture - Part 4: Services
Käsitlusala:
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.
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.
Alusdokumendid:
IEC 62541-4:2025; EN IEC 62541-4:2026
Asendab:
EVS-EN IEC 62541-4:2020
ISO 17090-4:2026
Health informatics — Public key infrastructure — Part 4: Digital signatures for healthcare documents
Käsitlusala:
This document supports interchangeability of digital signatures and the prevention of incorrect or illegal digital signatures by providing minimum requirements and formats for generating and verifying digital signatures and related certificates.
This document describes the common technical, operational, and policy requirements to enable digital certificates to be used in protecting the exchange of healthcare information within a single domain, between domains, and across jurisdictional boundaries. The purpose of this document is to create a platform for global interoperability. It specifically supports digital certificate enabled communication across borders but can also provide guidance for the national or regional deployment of digital certificates in healthcare.
This document defines the provable compliance with a public key infrastructure (PKI) policy necessary in the domain of healthcare. It specifies a method of adopting long-term signature formats to ensure integrity and non-repudiation in long-term electronic preservation of healthcare information.
This document provides healthcare-specific PKI (HPKI) profiles of digital signature based on the ISO/ETSI standard profiles specified in CAdES (CMS Advanced Electronic Signature)[1], XAdES (XML Advanced Electronic Signature), PAdES (PDF Advanced Electronic Signature)[2] and the ETSI standard specified in JAdES (JSON Advanced Electronic Signature)[13].
This document describes the common technical, operational, and policy requirements to enable digital certificates to be used in protecting the exchange of healthcare information within a single domain, between domains, and across jurisdictional boundaries. The purpose of this document is to create a platform for global interoperability. It specifically supports digital certificate enabled communication across borders but can also provide guidance for the national or regional deployment of digital certificates in healthcare.
This document defines the provable compliance with a public key infrastructure (PKI) policy necessary in the domain of healthcare. It specifies a method of adopting long-term signature formats to ensure integrity and non-repudiation in long-term electronic preservation of healthcare information.
This document provides healthcare-specific PKI (HPKI) profiles of digital signature based on the ISO/ETSI standard profiles specified in CAdES (CMS Advanced Electronic Signature)[1], XAdES (XML Advanced Electronic Signature), PAdES (PDF Advanced Electronic Signature)[2] and the ETSI standard specified in JAdES (JSON Advanced Electronic Signature)[13].
Alusdokumendid:
Asendab:
ISO 17090-4:2020
ISO/IEC TS 22237-31:2026
Information technology — Data centre facilities and infrastructures — Part 31: Key performance indicators for resilience
Käsitlusala:
This document:
defines metrics as key performance indicators (KPIs) for resilience, dependability, fault tolerance and availability tolerance for data centres;
covers the data centre infrastructure (DCI) of power distribution and supply, and environmental control;
can be referred to for covering further infrastructures, e.g. telecommunications cabling;
defines the measurement and calculation of the KPIs and resilience levels (RLs);
targets maintainability, recoverability and vulnerability;
provides examples for calculating these KPIs for the purpose of analytical comparison of different DCIs.
This document does not apply to IT equipment, cloud services, software or business applications.
defines metrics as key performance indicators (KPIs) for resilience, dependability, fault tolerance and availability tolerance for data centres;
covers the data centre infrastructure (DCI) of power distribution and supply, and environmental control;
can be referred to for covering further infrastructures, e.g. telecommunications cabling;
defines the measurement and calculation of the KPIs and resilience levels (RLs);
targets maintainability, recoverability and vulnerability;
provides examples for calculating these KPIs for the purpose of analytical comparison of different DCIs.
This document does not apply to IT equipment, cloud services, software or business applications.
Alusdokumendid:
Asendab:
ISO/IEC TS 22237-31:2023
CEN/CLC/ETSI/TR 101551:2026
Guidelines for public procurement of ICT products and services in the European Union: accessibility award criteria and conformity assessment
Käsitlusala:
This Technical Report (TR) provides guidance to contracting authorities on how to determine contract award criteria to meet the accessibility requirements of Directive (EU) 2019/882 (European Accessibility Act, EAA) and Directive (EU) 2016/2102 (Web Accessibility Directive, WAD); and on how to verify the conformance of publicly procured ICT products and services with these requirements. The present document describes how the accessibility requirements for the procured ICT should be specified, documented and assessed in the frame of the procurement process, under the EU Public Procurement Directives1. The different mechanisms for conformity assessment with the applicable accessibility requirements are explained. It is discussed how these mechanisms may be applied both in the pre-procurement research phase and when awarding a contract, as well as part of contract management in the post-award stage. This Technical Report also provides a useful guidance for bidders who prepare an offer for public procurement of ICT products and services, and others aiming to procure accessible ICT.
Alusdokumendid:
CEN/CLC/ETSI/TR 101551:2026
ISO/TR 25145:2026
Blockchain and distributed ledger technology (DLT) — Overview of DLT-based collections and collections management
Käsitlusala:
This document provides an overview of DLT-based collections of physical and digital items as well as collections management. This document discusses implementation considerations regarding DLT-based collections and collections management.
Alusdokumendid:
EVS-EN IEC 62541-7:2026
OPC Unified Architecture - Part 7: Profiles
Käsitlusala:
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.
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.
Alusdokumendid:
IEC 62541-7:2025; EN IEC 62541-7:2026
Asendab:
EVS-EN IEC 62541-7:2020
EVS-EN ISO/IEC 19896-2:2026
Information security, cybersecurity and privacy protection - Requirements for the competence of IT security conformance assessment body personnel - Part 2: Knowledge and skills requirements for testers and validators according to ISO/IEC 19790 and ISO/IEC 24759 (ISO/IEC 19896-2:2026)
Käsitlusala:
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.
Alusdokumendid:
ISO/IEC 19896-2:2026; EN ISO/IEC 19896-2:2026
Asendab:
EVS-EN ISO/IEC 19896-2:2023
EVS-EN ISO 18166:2026
Numerical welding simulation - Execution and documentation (ISO 18166:2026)
Käsitlusala:
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.
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.
Alusdokumendid:
ISO 18166:2026; EN ISO 18166:2026
Asendab:
CEN ISO/TS 18166:2016
EVS-ISO/IEC 18000-6:2026
Infotehnoloogia. Raadiosageduse tuvastaja üksuse haldamiseks. Osa 6: Üldised raadioliidese edastusparameetrid 860 MHz kuni 930 MHz juures
Käsitlusala:
See dokument täpsustab raadioliidest raadiosageduse tuvastamise (RFID) seadmetele, mis
töötavad 860 MHz kuni 930 MHz tööstusliku, teadusliku ja meditsiinilise (ISM) eesmärgiga
raadiosagedusalas, mida kasutatakse üksuste haldamise rakendustes. Selle dokumendi eesmärk
on võimaldada ühilduvust ja julgustada toodete koostalitlusvõimet kasvaval RFID
rahvusvahelisel turul.
See dokument defineerib edastus- ja tagasisidelingi tehniliste omaduste parameetrid,
sealhulgas, aga mitte ainult, töösageduse, töökanali täpsuse, kasutatava kanali ribalaiuse,
maksimaalse efektiivse isotroopse kiirgusvõimsuse (EIRP), vääremissioonid,
modulatsiooni, töötsükli, andmekodeerimise, bitikiiruse, bitikiiruse täpsuse, bittide
edastusjärjekorra ning vajadusel töökanalite, sageduse hüpitamise kiiruse, sagedushüpete
jada, levijada ja kiibikiiruse parameetrid. Lisaks määratleb see kommunikatsiooniprotokolli,
mida kasutatakse raadioliideses.
See dokument täpsustab füüsikalised ja loogikanõuded RFID-süsteemile
passiivtagasipeegeldaja, ülekuulaja-räägib-esimesena (ITF) või märgistatu-räägib-ainultpärast-
kuulamist (TOTAL).
See dokument koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-
63 ja ISO/IEC 18000-64 täpsustab 860 MHz kuni 930 MHz sagedusvahemiku jaoks
järgmist:
— ülekuulaja ja märgistatu vahelised (kommunikatsioonilingi signaali kihi) füüsikalised
sidemed;
— ülekuulaja ja märgistatu opereerimisprotseduurid ja käsud;
— põrkearbitraažiskeemi, mida kasutatakse spetsiifilise märgistatu identifitseerimiseks
mitmemärgistatulises keskkonnas.
töötavad 860 MHz kuni 930 MHz tööstusliku, teadusliku ja meditsiinilise (ISM) eesmärgiga
raadiosagedusalas, mida kasutatakse üksuste haldamise rakendustes. Selle dokumendi eesmärk
on võimaldada ühilduvust ja julgustada toodete koostalitlusvõimet kasvaval RFID
rahvusvahelisel turul.
See dokument defineerib edastus- ja tagasisidelingi tehniliste omaduste parameetrid,
sealhulgas, aga mitte ainult, töösageduse, töökanali täpsuse, kasutatava kanali ribalaiuse,
maksimaalse efektiivse isotroopse kiirgusvõimsuse (EIRP), vääremissioonid,
modulatsiooni, töötsükli, andmekodeerimise, bitikiiruse, bitikiiruse täpsuse, bittide
edastusjärjekorra ning vajadusel töökanalite, sageduse hüpitamise kiiruse, sagedushüpete
jada, levijada ja kiibikiiruse parameetrid. Lisaks määratleb see kommunikatsiooniprotokolli,
mida kasutatakse raadioliideses.
See dokument täpsustab füüsikalised ja loogikanõuded RFID-süsteemile
passiivtagasipeegeldaja, ülekuulaja-räägib-esimesena (ITF) või märgistatu-räägib-ainultpärast-
kuulamist (TOTAL).
See dokument koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-
63 ja ISO/IEC 18000-64 täpsustab 860 MHz kuni 930 MHz sagedusvahemiku jaoks
järgmist:
— ülekuulaja ja märgistatu vahelised (kommunikatsioonilingi signaali kihi) füüsikalised
sidemed;
— ülekuulaja ja märgistatu opereerimisprotseduurid ja käsud;
— põrkearbitraažiskeemi, mida kasutatakse spetsiifilise märgistatu identifitseerimiseks
mitmemärgistatulises keskkonnas.
Alusdokumendid:
ISO/IEC 18000-6:2025
Asendab:
EVS-ISO/IEC 18000-6:2013
ISO/IEC TS 27103:2026
Cybersecurity — Guidance on using ISO and IEC standards in a cybersecurity framework
Käsitlusala:
This document provides guidance on how to leverage existing ISO and IEC standards in a cybersecurity framework.
Alusdokumendid:
Asendab:
ISO/IEC TR 27103:2018
ISO 6029-2:2026
Intelligent transport systems — Seamless positioning for multimodal transportation in ITS stations — Part 2: Nomadic and mobile device dataset for positioning data fusion
Käsitlusala:
This document specifies the sensor data fusion applicable to the use cases of indoor and outdoor seamless positioning solutions for a mobile user (multimodal transportation) in intelligent transport system (ITS) stations.
This document provides technical requirements for data fusion between three domains:
nomadic device [e.g. personal intelligent transport system station (P-ITS-S)],
mobility [e.g. vehicle intelligent transport system station (V-ITS-S)], and
infrastructure [e.g. roadside intelligent transport system station (R-ITS-S)].
The data exchange between these domains is based on a standardized message and data format and this document identifies use cases for each different case of communication between domains.
This document provides technical requirements for data fusion between three domains:
nomadic device [e.g. personal intelligent transport system station (P-ITS-S)],
mobility [e.g. vehicle intelligent transport system station (V-ITS-S)], and
infrastructure [e.g. roadside intelligent transport system station (R-ITS-S)].
The data exchange between these domains is based on a standardized message and data format and this document identifies use cases for each different case of communication between domains.
Alusdokumendid:
ISO/TS 16601:2026
Health informatics — Patient, intervention, comparison and outcomes (PICO) information model of traditional Chinese medicine (TCM) clinical studies
Käsitlusala:
This document establishes the information model of traditional Chinese medicine (TCM) clinical studies by defining categories and their attributes designed to extract patient, intervention, comparison and outcomes (PICO) data elements from the reports of TCM clinical studies.
Alusdokumendid:
EVS-ISO/IEC 29794-5:2026
Infotehnoloogia. Biomeetriliste andmete kvaliteet. Osa 5: Näopiltide andmed
Käsitlusala:
See dokument kehtestab nõuded rakendustele, mis kvantifitseerivad, mil määral vastavad näopildi omadused kanoonilise näopildi omadustele – näiteks neile, mis on kirjeldatud standardi
ISO/IEC 39794-5:2019 jaotises D.1 – kolme kasutusjuhtumi puhul:
1) isikut tõendavate dokumentide jaoks viitenäidiste kogumine;
2) näidissüsteemi registreerimine; ning
3) päringupiltide kasutamine kohese vastuse saamiseks.
See dokument määratleb ka näopildi kvaliteedi kvantifitseerimisega seotud terminid ja määratlused ning sätestab meetodid näopiltide kvaliteedi kvantitatiivseks hindamiseks.
See dokument ei kehtesta nõudeid
— pildipaaride või pildijadade kvaliteedi hindamisele;
MÄRKUS See dokument kehtestab nõuded tarkvarale, mis analüüsib täpselt ühte pilti. See ei hõlma tarkvara, mis võrdleb kahte või enamat pilti (nt biomeetrilise isikutuvastuse tarkvara). Siiski võib selles dokumendis kirjeldatud arvutusi rakendada eraldi iga pildi kohta pildipaari või -jada korral.
— kolmemõõtmeliste (3D) jäädvustuste kvaliteedi hindamisele;
— näopildi kvaliteediandmete kodeeringule;
— näopildi kvaliteedi hindamise algoritmide jõudluse hindamisele.
Selle dokumendi käsitlusalasse kuuluvad kasutusjuhud käsitlevad eelkõige nende isikute näopiltide kvaliteedi hindamist, kes on andnud nõusoleku oma biomeetriliste andmete töötlemiseks või kelle biomeetriliste andmete jäädvustamine on tegevusena lubatud.
ISO/IEC 39794-5:2019 jaotises D.1 – kolme kasutusjuhtumi puhul:
1) isikut tõendavate dokumentide jaoks viitenäidiste kogumine;
2) näidissüsteemi registreerimine; ning
3) päringupiltide kasutamine kohese vastuse saamiseks.
See dokument määratleb ka näopildi kvaliteedi kvantifitseerimisega seotud terminid ja määratlused ning sätestab meetodid näopiltide kvaliteedi kvantitatiivseks hindamiseks.
See dokument ei kehtesta nõudeid
— pildipaaride või pildijadade kvaliteedi hindamisele;
MÄRKUS See dokument kehtestab nõuded tarkvarale, mis analüüsib täpselt ühte pilti. See ei hõlma tarkvara, mis võrdleb kahte või enamat pilti (nt biomeetrilise isikutuvastuse tarkvara). Siiski võib selles dokumendis kirjeldatud arvutusi rakendada eraldi iga pildi kohta pildipaari või -jada korral.
— kolmemõõtmeliste (3D) jäädvustuste kvaliteedi hindamisele;
— näopildi kvaliteediandmete kodeeringule;
— näopildi kvaliteedi hindamise algoritmide jõudluse hindamisele.
Selle dokumendi käsitlusalasse kuuluvad kasutusjuhud käsitlevad eelkõige nende isikute näopiltide kvaliteedi hindamist, kes on andnud nõusoleku oma biomeetriliste andmete töötlemiseks või kelle biomeetriliste andmete jäädvustamine on tegevusena lubatud.
Alusdokumendid:
ISO/IEC 29794-5:2025
ISO/IEC 19566-6:2026
Information technologies — JPEG systems — Part 6: JPEG 360
Käsitlusala:
This document specifies omnidirectional/360-degree image and motion contents using Rec. ITU-T T.81 | ISO/IEC 10918‑1, Rec. ITU-T T.800 (11/2015) | ISO/IEC 15444‑1, and ISO/IEC 18477-3.
Alusdokumendid:
ISO 19135:2026
Geographic information — Registration and register governance
Käsitlusala:
This document defines a framework for the extensible registration of information — an approach used to manage an information register.
This framework specifies the following requirements of an information register:
capability requirements that an information register uses to manage register content;
governance requirements that define a set of processes and rules used in the establishment, management, operation, content publication and use of an information register.
The following considerations are out of scope of this document:
implementation details for the realization of an information register;
content and related definitions that are managed within an information register.
This framework specifies the following requirements of an information register:
capability requirements that an information register uses to manage register content;
governance requirements that define a set of processes and rules used in the establishment, management, operation, content publication and use of an information register.
The following considerations are out of scope of this document:
implementation details for the realization of an information register;
content and related definitions that are managed within an information register.
Alusdokumendid:
ISO/IEC 25706:2026
Information technology — Security protocol and data model (SPDM) collection
Käsitlusala:
Alusdokumendid:
ISO/IEC 22460-3:2026
Cards and security devices for personal identification — ISO UAS licence and drone or UAS security module — Part 3: Digital UAS or drone licence
Käsitlusala:
The document specifies doctype, namespace and a set of data elements for digital UAS or drone licences (or training certificates) supporting mdoc data model specified in ISO/IEC 18013-5 and ISO/IEC TS 23220-2. This document is also applicable for any remote pilot licences or training certificates issued by aviation authorities.
This document does not specify either licence categories and licence conditions and is designed to define any domestic licences and training certificates by defining domestic namespaces in accordance with each region and/or state’s regulations.
The digital UAS or drone licence data specified in this document is applicable to mdoc application as defined in ISO/IEC 23220-1 and transmission protocol specified in ISO/IEC 18013-5, ISO/IEC TS 18013-7 and ISO/IEC TS 23220-4.
This document does not specify either licence categories and licence conditions and is designed to define any domestic licences and training certificates by defining domestic namespaces in accordance with each region and/or state’s regulations.
The digital UAS or drone licence data specified in this document is applicable to mdoc application as defined in ISO/IEC 23220-1 and transmission protocol specified in ISO/IEC 18013-5, ISO/IEC TS 18013-7 and ISO/IEC TS 23220-4.
Alusdokumendid:
ISO/IEC 29170-3:2026
Information technology — JPEG AIC Assessment of image coding — Part 3: Subjective quality assessment of high-fidelity images
Käsitlusala:
This document specifies a subjective image quality assessment methodology that covers a range from good quality up to mathematically lossless.
This document is applicable to the assessment of distortions due to image coding (i.e. lossy compression) and not necessarily other kinds of distortions (e.g. capture, sensor or rendering artefacts).
This document is applicable to the assessment of distortions due to image coding (i.e. lossy compression) and not necessarily other kinds of distortions (e.g. capture, sensor or rendering artefacts).
Alusdokumendid:
ISO 18166:2026
Numerical welding simulation — Execution and documentation
Käsitlusala:
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.
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.
Alusdokumendid:
Asendab:
ISO/TS 18166:2016
ISO 5909:2026
Business processes and data interchange of electronic bill of lading based on distributed ledger technology (DLT)
Käsitlusala:
This document outlines the business processes and data requirements for the implementation of electronic bill of lading (eBL). Its primary focus is the secure digital transfer of title documents via a trusted platform. Additionally, it specifies optional data elements that are essential for leveraging distributed ledger technology (DLT) to support the eBL workflow.
Alusdokumendid:
ISO/IEC 30113-62:2026
Information technology — Gesture-based interfaces across devices and methods — Part 62: Multi-point gestures for screen readers
Käsitlusala:
This document defines multi-point gestures for screen readers.
It specifies movements for clear and classified multi-point gestures recognized by the screen readers.
It describes multi-point gestures performed by multiple point of interest (POI) for the screen readers.
NOTE Multiple POI can be manipulated by using multiple objects such as fingertips, etc.
It specifies movements for clear and classified multi-point gestures recognized by the screen readers.
It describes multi-point gestures performed by multiple point of interest (POI) for the screen readers.
NOTE Multiple POI can be manipulated by using multiple objects such as fingertips, etc.
Alusdokumendid:
ISO/TR 32121:2026
Transaction assurance in E-commerce — Practices for developing terms of use for business-to-consumer (B2C) E-commerce platforms
Käsitlusala:
This document provides practices for developing terms of use for business-to-consumer (B2C) E-commerce platforms, including specific principles, key elements and developing processes.
This document is applicable to all parties involved in B2C E-commerce transactions and the development process of terms of use.
This document is applicable to all parties involved in B2C E-commerce transactions and the development process of terms of use.
Alusdokumendid:
ISO/IEC TR 9858:2026
Information technology — Use cases on advanced learning analytics services using emerging technologies
Käsitlusala:
This document provides a collection of use cases on advanced learning analytics services, which leverages emerging technologies such as cloud computing, blockchain, virtual reality, internet of things, artificial intelligence in K12 education, higher education, and vocational education and training (VET). This document also establishes a categorization of different groups of learning analytics services and outlines their interrelationships.
This document is applicable to the design and development of learning analytics activities.
This document is applicable to the design and development of learning analytics activities.
Alusdokumendid:
ISO/IEC 9995-3:2026
Information technology — Keyboard layouts for text and office systems — Part 3: Latin International keyboard layout
Käsitlusala:
Within the general scope described in ISO/IEC 9995-1, this document defines a specific keyboard layout for the Latin script.
This document is primarily intended for word-processing and text-processing applications.
This document is primarily intended for word-processing and text-processing applications.
Alusdokumendid:
Asendab:
ISO/IEC 9995-3:2010
ISO/IEC 4933:2026
Information technology — User interfaces — Unifying input actions across devices
Käsitlusala:
This document specifies a unification module for input actions, including its framework, requirements and recommendations, for consistently accessing the operations across multiple types of devices. This document recognizes the input actions as user behaviours that are commonly used to manipulate system or application operations (functions) through user interfaces. It also identifies the need and use cases of unifying input actions across devices.
This document does not specify parameter settings and details of the input actions. This document is applicable to all types of organizations.
This document does not specify parameter settings and details of the input actions. This document is applicable to all types of organizations.
Alusdokumendid:
Asendatud standardid
EVS-ISO/IEC 18000-6:2013
Infotehnoloogia. Raadiosageduse tuvastaja üksuse haldamiseks. Osa 6: Raadioliidese edastusparameetrid 860 MHz kuni 960 MHz juures. Üldist
Käsitlusala:
See ISO/IEC 18000 osa defineerib raadioliidese raadiosageduse tuvastamise (RFID) seadmetele, mis töötavad 860 MHz kuni 960 MHz tööstusliku, teadusliku ja meditsiinilise (ISM) eesmärgiga raadiosagedusalas, mida kasutatakse üksuse haldamise rakendustes. See pakub ühtset tehnilist kirjeldust RFID seadmetele, mida saavad kasutada RFID rakenduse standardeid arendavad ISO komisjonid. Selle ISO/IEC 18000 osa eesmärk on võimaldada ühilduvust ja julgustada toodete koostalitlusvõimet kasvaval RFID rahvusvahelisel turul. Standard defineerib edastus- ja tagasisidelingi tehniliste omaduste parameetrid, sealhulgas, aga mitte ainult, töösageduse, töökanali täpsuse, kasutatava kanali ribalaiuse, maksimaalse efektiivse isotroopse kiirgusvõimsuse (EIRP), vääremissiooni, modulatsiooni, töötsükli, andmekodeerimise, andmemahu, andmemahu täpsuse, andmete saatmise järjekorra ning vajadusel töökanalite, sageduse hüpitamise kiiruse, vahetamismeetodi, jaotusjada ja koodiedastuskiiruse parameetrid. Lisaks määratleb see kommunikatsiooniprotokolli, mida kasutatakse raadioliideses.
See ISO/IEC 18000 osa koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-63 ja ISO/IEC 18000-64 täpsustab füüsikalised ja loogikanõuded RFID süsteemile passiivtagasipeegeldaja, ülekuulaja-räägib-esimesena (ITF) ja märgistatu-räägib-ainult-pärast-kuulamist (TOTAL). Süsteem hõlmab Ülekuulajajaid, mis on tuntud ka kui lugejad, ning Märgistatuid, mis on tuntud ka kui sildid. Ülekuulaja saab Märgistatult informatsiooni, edastades püsiva laine (CW) RF signaali Märgistatule; Märgistatu vastab, moduleerides oma antenni peegelduse koefitsiendi ja seeläbi peegeldades informatsioonisignaali tagasi Ülekuulajale. Süsteem on ITF, tähendades seda, et Märgistatu moduleerib oma antenni peegelduse koefitsiendi koos infosignaaliga ainult pärast Ülekuulajalt või TOTAL-ilt saadud juhiseid, tähendades seda, et Märgistatu moduleerib oma antenni peegelduse koefitsiendi koos infosignaaliga pärast sisenemist Ülekuulaja alale pärast esimest Ülekuulaja modulatsiooni kuulmist, selgitamaks välja, kas süsteem on ITF või mitte.
See ISO/IEC 18000 osa sisaldab ühte neljatüübilist režiimi. Nelja tüübi detailsed tehnilised erinevused on esitatud parameetrite tabelis.
Tüübid A, B ja C on ITF. Tüüp A kasutab edastuslingis impulsisageduse kodeerimist (PIE) ning adaptiivset ALOHA põrkearbitraaži algoritmi. Tüüp B kasutab edastuslingis Manchesteri ja adaptiivset kahendpuu põrkearbitraaži algoritmi. Tüüp C kasutab edastuslingis PIE-t ja juhuslikku põrkearbitraaži algoritmi.
Tüüp D on TOTAL, põhinedes pulss-positsioonkodeeringul või Miller M=2 kodeeritud alakandjal.
See ISO/IEC 18000 osa koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-63 ja ISO/IEC 18000-64 täpsustab
ülekuulaja ja märgistatu vahelised (kommunikatsioonilingi signaali kihi) füüsikalised sidemed,
ülekuulaja ja märgistatu opereerimisprotseduurid ja käsud,
põrkearbitraaži skeemi, mida kasutatakse spetsiifilise märgi identifitseerimiseks mitmemärgilises keskkonnas.
See ISO/IEC 18000 osa koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-63 ja ISO/IEC 18000-64 täpsustab füüsikalised ja loogikanõuded RFID süsteemile passiivtagasipeegeldaja, ülekuulaja-räägib-esimesena (ITF) ja märgistatu-räägib-ainult-pärast-kuulamist (TOTAL). Süsteem hõlmab Ülekuulajajaid, mis on tuntud ka kui lugejad, ning Märgistatuid, mis on tuntud ka kui sildid. Ülekuulaja saab Märgistatult informatsiooni, edastades püsiva laine (CW) RF signaali Märgistatule; Märgistatu vastab, moduleerides oma antenni peegelduse koefitsiendi ja seeläbi peegeldades informatsioonisignaali tagasi Ülekuulajale. Süsteem on ITF, tähendades seda, et Märgistatu moduleerib oma antenni peegelduse koefitsiendi koos infosignaaliga ainult pärast Ülekuulajalt või TOTAL-ilt saadud juhiseid, tähendades seda, et Märgistatu moduleerib oma antenni peegelduse koefitsiendi koos infosignaaliga pärast sisenemist Ülekuulaja alale pärast esimest Ülekuulaja modulatsiooni kuulmist, selgitamaks välja, kas süsteem on ITF või mitte.
See ISO/IEC 18000 osa sisaldab ühte neljatüübilist režiimi. Nelja tüübi detailsed tehnilised erinevused on esitatud parameetrite tabelis.
Tüübid A, B ja C on ITF. Tüüp A kasutab edastuslingis impulsisageduse kodeerimist (PIE) ning adaptiivset ALOHA põrkearbitraaži algoritmi. Tüüp B kasutab edastuslingis Manchesteri ja adaptiivset kahendpuu põrkearbitraaži algoritmi. Tüüp C kasutab edastuslingis PIE-t ja juhuslikku põrkearbitraaži algoritmi.
Tüüp D on TOTAL, põhinedes pulss-positsioonkodeeringul või Miller M=2 kodeeritud alakandjal.
See ISO/IEC 18000 osa koos standarditega ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/IEC 18000-63 ja ISO/IEC 18000-64 täpsustab
ülekuulaja ja märgistatu vahelised (kommunikatsioonilingi signaali kihi) füüsikalised sidemed,
ülekuulaja ja märgistatu opereerimisprotseduurid ja käsud,
põrkearbitraaži skeemi, mida kasutatakse spetsiifilise märgi identifitseerimiseks mitmemärgilises keskkonnas.
Alusdokumendid:
ISO/IEC 18000-6:2013
Asendatud:
EVS-ISO/IEC 18000-6:2026
CEN/CLC/ETSI TR 101551:2014
Guidelines on the use of accessibility award criteria suitable for public procurement of ICT products and services in Europe
Käsitlusala:
The TR will give guidance to procurers on the award criteria relevant to each area of user needs in the procurement of ICT products and services
Alusdokumendid:
CEN/CLC/ETSI TR 101551:2014
Asendatud:
CEN/CLC/ETSI/TR 101551:2026
ISO 19135-1:2015
Geographic information -- Procedures for item registration -- Part 1: Fundamentals
Käsitlusala:
ISO 19135-1:2015 specifies procedures to be followed in establishing, maintaining, and publishing registers of unique, unambiguous, and permanent identifiers and meanings that are assigned to items of geographic information. In order to accomplish this purpose, ISO 19135-1:2015 specifies elements that are necessary to manage the registration of these items.
Alusdokumendid:
Asendatud:
ISO 19135:2026
EVS-EN 62541-100:2015
OPC unified architecture - Part 100: Device Interface
Käsitlusala:
IEC 62541-100:2015 is an extension of the overall OPC Unified Architecture standard series and defines the information model associated with Devices. This part of IEC 62541 describes three models which build upon each other:
- the (base) Device Model intended to provide a unified view of devices;
- the Device Communication Model which adds Network and Connection information elements so that communication topologies can be created;
- the Device Integration Host Model finally which adds additional elements and rules required for host systems to manage integration for a complete system. It allows reflecting the topology of the automation system with the devices as well as the connecting communication networks.
- the (base) Device Model intended to provide a unified view of devices;
- the Device Communication Model which adds Network and Connection information elements so that communication topologies can be created;
- the Device Integration Host Model finally which adds additional elements and rules required for host systems to manage integration for a complete system. It allows reflecting the topology of the automation system with the devices as well as the connecting communication networks.
Alusdokumendid:
IEC 62541-100:2015; EN 62541-100:2015
Asendatud:
EVS-EN IEC 62541-100:2026
EVS-EN IEC 62541-13:2020
OPC Unified Architecture - Part 13: Aggregates
Käsitlusala:
IEC 62541-13:2020 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates. This second edition cancels and replaces the first edition of IEC 62541-13, published in 2015. No technical changes but numerous clarifications. Also some corrections to the examples.
Alusdokumendid:
IEC 62541-13:2020; EN IEC 62541-13:2020
Asendatud:
EVS-EN IEC 62541-13:2026
EVS-EN IEC 62541-7:2020
OPC unified architecture - Part 7: Profiles
Käsitlusala:
IEC 62541-7:2020 defines the OPC Unified Architecture (OPC UA) Profiles. The Profiles in this document are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed by the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation provided Independent certification test labs. This could equally as well refer to test tools provided by another organization or a test lab provided by another organization. What is important is the concept of automated tool-based testing versus lab-based testing. The scope of this standard includes defining functionality that can only be tested in a lab and defining the grouping of functionality that is to be used when testing OPC UA products either in a lab or using automated tools. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are within the scope of this document.
Most OPC UA applications will conform to several, but not all, of the Profiles.
This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) new functional Profiles:
• profiles for global discovery and global certificate management;
• profiles for global KeyCredential management and global access token management;
• facet for durable subscriptions;
• standard UA Client Profile;
• profiles for administration of user roles and permissions.
b) new transport Profiles:
• HTTPS with JSON encoding;
• secure WebSockets (WSS) with binary or JSON encoding;
• reverse connectivity.
c) new security Profiles:
• transportSecurity – TLS 1.2 with PFS (with perfect forward secrecy);
• securityPolicy [A] – Aes128-Sha256-RsaOaep (replaces Base128Rsa15);
• securityPolicy – Aes256-Sha256-RsaPss adds perfect forward secrecy for UA TCP);
• user Token JWT (Jason Web Token).
d) deprecated Security Profiles (due to broken algorithms):
• securityPolicy – Basic128Rsa15 (broken algorithm Sha1);
• securityPolicy – Basic256 (broken algorithm Sha1);
• transportSecurity – TLS 1.0 (broken algorithm RC4);
• transportSecurity – TLS 1.1 (broken algorithm RC4).
e) deprecated Transport (missing support on most platforms):
• SOAP/HTTP with WS-SecureConversation (all encodings).
Most OPC UA applications will conform to several, but not all, of the Profiles.
This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) new functional Profiles:
• profiles for global discovery and global certificate management;
• profiles for global KeyCredential management and global access token management;
• facet for durable subscriptions;
• standard UA Client Profile;
• profiles for administration of user roles and permissions.
b) new transport Profiles:
• HTTPS with JSON encoding;
• secure WebSockets (WSS) with binary or JSON encoding;
• reverse connectivity.
c) new security Profiles:
• transportSecurity – TLS 1.2 with PFS (with perfect forward secrecy);
• securityPolicy [A] – Aes128-Sha256-RsaOaep (replaces Base128Rsa15);
• securityPolicy – Aes256-Sha256-RsaPss adds perfect forward secrecy for UA TCP);
• user Token JWT (Jason Web Token).
d) deprecated Security Profiles (due to broken algorithms):
• securityPolicy – Basic128Rsa15 (broken algorithm Sha1);
• securityPolicy – Basic256 (broken algorithm Sha1);
• transportSecurity – TLS 1.0 (broken algorithm RC4);
• transportSecurity – TLS 1.1 (broken algorithm RC4).
e) deprecated Transport (missing support on most platforms):
• SOAP/HTTP with WS-SecureConversation (all encodings).
Alusdokumendid:
IEC 62541-7:2020; EN IEC 62541-7:2020
Asendatud:
EVS-EN IEC 62541-7:2026
ISO/IEC TR 27103:2018
Information technology -- Security techniques -- Cybersecurity and ISO and IEC Standards
Käsitlusala:
ISO/IEC TR 27103:2018 provides guidance on how to leverage existing standards in a cybersecurity framework.
Alusdokumendid:
Asendatud:
ISO/IEC TS 27103:2026
ISO/IEC 19566-6:2019
Information technologies -- JPEG systems -- Part 6: JPEG 360
Käsitlusala:
This document specifies omnidirectional/360-degree image and motion contents using Rec. ITU-T T.81 | ISO/IEC 10918-1, Rec. ITU-T T.800 (11/2015) | ISO/IEC 15444-1, and ISO/IEC 18477-3.
Alusdokumendid:
Asendatud:
ISO/IEC 19566-6:2026
EVS-EN IEC 62541-10:2020
OPC Unified Architecture - Part 10: Programs
Käsitlusala:
IEC 62541-10:2020 defines the information model associated with Programs in the OPC Unified Architecture. This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete Address Space 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. This third edition cancels and replaces the second edition published in 2015. This edition includes several clarifications and in addition the following significant technical changes with respect to the previous edition:
a) Changed ProgramType to ProgramStateMachineType. This is in line with the NodeSet (and thus implementations). In ProgramDiagnosticDataType: changed the definition of lastInputArguments and lastOutputArguments and added two additional fields for the argument values. Also changed StatusResult into StatusCode. Created new version of the type to ProgramDiagnostic2DataType.
b) Changed Optional modelling rule to OptionalPlaceHolder for Program control Methods. Following the clarification in IEC 62541-3, this now allows subtypes (or instances) to add arguments.
a) Changed ProgramType to ProgramStateMachineType. This is in line with the NodeSet (and thus implementations). In ProgramDiagnosticDataType: changed the definition of lastInputArguments and lastOutputArguments and added two additional fields for the argument values. Also changed StatusResult into StatusCode. Created new version of the type to ProgramDiagnostic2DataType.
b) Changed Optional modelling rule to OptionalPlaceHolder for Program control Methods. Following the clarification in IEC 62541-3, this now allows subtypes (or instances) to add arguments.
Alusdokumendid:
IEC 62541-10:2020; EN IEC 62541-10:2020
Asendatud:
EVS-EN IEC 62541-10:2026
EVS-EN IEC 62541-4:2020
OPC Unified Architecture - Part 4: Services
Käsitlusala:
IEC 62541-4:2020 defines the OPC Unified Architecture (OPC UA)Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to XML Web Services. In that case the Services described in this document appear as the Web service methods in the WSDL contract. Not all OPC UA Servers will need to implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services need to be implemented in order to be compliant with a particular Profile. This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) Added ability to resend all data of monitored items in a Subscription using the ResendData Method.
b) Added support for durable Subscriptions (lifetime of hours or days).
c) Added Register2 and FindServersOnNetwork Services to support network-wide discovery using capability filters.
d) Removed definition of software certificates. Will be defined in a future edition.
e) Extended and partially revised the redundancy definition. Added sub-range definitions for ServiceLevel and added more terms for redundancy.
f) Added a section on how to use Authorization Services to request user access tokens.
g) Added JSON Web Tokens (JWTs) as a new user token.
h) Added the concept of session-less service invocation.
i) Added a generic structure that allows passing any number of attributes to the AddNodes Service.
j) Added requirement to protect against user identity token attacks.
k) Added new EncryptedSecret format for user identity tokens.
a) Added ability to resend all data of monitored items in a Subscription using the ResendData Method.
b) Added support for durable Subscriptions (lifetime of hours or days).
c) Added Register2 and FindServersOnNetwork Services to support network-wide discovery using capability filters.
d) Removed definition of software certificates. Will be defined in a future edition.
e) Extended and partially revised the redundancy definition. Added sub-range definitions for ServiceLevel and added more terms for redundancy.
f) Added a section on how to use Authorization Services to request user access tokens.
g) Added JSON Web Tokens (JWTs) as a new user token.
h) Added the concept of session-less service invocation.
i) Added a generic structure that allows passing any number of attributes to the AddNodes Service.
j) Added requirement to protect against user identity token attacks.
k) Added new EncryptedSecret format for user identity tokens.
Alusdokumendid:
EN IEC 62541-4:2020; IEC 62541-4:2020
Asendatud:
EVS-EN IEC 62541-4:2026
ISO/IEC 9995-3:2010
Information technology -- Keyboard layouts for text and office systems -- Part 3: Complementary layouts of the alphanumeric zone of the alphanumeric section
Käsitlusala:
ISO/IEC 9995 defines a framework for the layout of all alphanumeric and numeric keyboards across the widest spectrum of today's and upcoming applications using keyboards. The functions to be performed by keyboards are grouped into three categories that correspond to the main physical sections of the keyboard.
Application of ISO/IEC 9995 in the design of keyboards will provide the user with a unified, predictable user-machine interface by dividing the keyboard into functional areas and sections and allocating functions to keys.
lSO/IEC 9995-3:2010 defines the allocation on a keyboard of a set of graphic characters which, when used in combination with an existing national version keyboard layout or the complementary Latin group layout as defined in ISO/IEC 9995-3:2010, allows the input of a minimum character repertoire as defined by collection 281 (MES-1) specified in ISO/IEC 10646 and proposes extensions of this minimum repertoire.
Application of ISO/IEC 9995 in the design of keyboards will provide the user with a unified, predictable user-machine interface by dividing the keyboard into functional areas and sections and allocating functions to keys.
lSO/IEC 9995-3:2010 defines the allocation on a keyboard of a set of graphic characters which, when used in combination with an existing national version keyboard layout or the complementary Latin group layout as defined in ISO/IEC 9995-3:2010, allows the input of a minimum character repertoire as defined by collection 281 (MES-1) specified in ISO/IEC 10646 and proposes extensions of this minimum repertoire.
Alusdokumendid:
Asendatud:
ISO/IEC 9995-3:2026
ISO/IEC 19566-6:2019/Amd 1:2021
Information technologies — JPEG systems — Part 6: JPEG 360 — Amendment 1: Addition of new JPEG 360 image types and accelerated ROI rendering
Käsitlusala:
Amendment to ISO/IEC 19566-6:2019
Alusdokumendid:
Asendatud:
ISO/IEC 19566-6:2026
ISO 17090-4:2020
Health informatics -- Public key infrastructure -- Part 4: Digital signatures for healthcare documents
Käsitlusala:
This document supports interchangeability of digital signatures and the prevention of incorrect or illegal digital signatures by providing minimum requirements and formats for generating and verifying digital signatures and related certificates.
This document describes the common technical, operational, and policy requirements that need to be addressed to enable digital certificates to be used in protecting the exchange of healthcare information within a single domain, between domains, and across jurisdictional boundaries. Its purpose is to create a platform for global interoperability. It specifically supports digital certificate enabled communication across borders but could also provide guidance for the national or regional deployment of digital certificates in healthcare.
It defines the provable compliance with a PKI policy necessary in the domain of healthcare. This document specifies a method of adopting long-term signature formats to ensure integrity and non-repudiation in long-term electronic preservation of healthcare information.
This document provides Healthcare specific PKI (HPKI) profiles of digital signature based on the ETSI Standard and the profile of the ISO/ETSI Standard specified in CAdES, XAdES, and PAdES.
This document describes the common technical, operational, and policy requirements that need to be addressed to enable digital certificates to be used in protecting the exchange of healthcare information within a single domain, between domains, and across jurisdictional boundaries. Its purpose is to create a platform for global interoperability. It specifically supports digital certificate enabled communication across borders but could also provide guidance for the national or regional deployment of digital certificates in healthcare.
It defines the provable compliance with a PKI policy necessary in the domain of healthcare. This document specifies a method of adopting long-term signature formats to ensure integrity and non-repudiation in long-term electronic preservation of healthcare information.
This document provides Healthcare specific PKI (HPKI) profiles of digital signature based on the ETSI Standard and the profile of the ISO/ETSI Standard specified in CAdES, XAdES, and PAdES.
Alusdokumendid:
Asendatud:
ISO 17090-4:2026
EVS-EN ISO/IEC 19896-2:2023
IT security techniques - Competence requirements for information security testers and evaluators - Part 2: Knowledge, skills and effectiveness requirements for ISO/IEC 19790 testers (ISO/IEC 19896-2:2018)
Käsitlusala:
This document provides the minimum requirements for the knowledge, skills and effectiveness
requirements of individuals performing testing activities for a conformance scheme using ISO/IEC
19790:2012 and ISO/IEC 24759
requirements of individuals performing testing activities for a conformance scheme using ISO/IEC
19790:2012 and ISO/IEC 24759
Alusdokumendid:
ISO/IEC 19896-2:2018; EN ISO/IEC 19896-2:2023
Asendatud:
EVS-EN ISO/IEC 19896-2:2026
ISO 19135-1:2015/Amd 1:2021
Geographic information — Procedures for item registration — Part 1: Fundamentals — Amendment 1
Käsitlusala:
Amendment to ISO 19135-1:2015
Alusdokumendid:
Asendatud:
ISO 19135:2026
ISO/IEC 23008-3:2022
Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 3: 3D audio
Käsitlusala:
This document specifies technology that supports the efficient transmission of immersive audio signals and flexible rendering for the playback of immersive audio in a wide variety of listening scenarios. These include home theatre setups with 3D loudspeaker configurations, 22.2 loudspeaker systems, automotive entertainment systems and playback over headphones connected to a tablet or smartphone.
Alusdokumendid:
Asendatud:
ISO/IEC 23008-3:2026
ISO 16484-6:2024
Building automation and control systems (BACS) — Part 6: Data communication conformance testing
Käsitlusala:
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
(a) support of each claimed BACnet service, either as an initiator, executor, or both,
(b) support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c) support of the BACnet network layer protocol,
(d) support of each claimed data link option, and
(e) support of all claimed special functionality.
(a) support of each claimed BACnet service, either as an initiator, executor, or both,
(b) support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c) support of the BACnet network layer protocol,
(d) support of each claimed data link option, and
(e) support of all claimed special functionality.
Alusdokumendid:
Asendatud:
ISO 16484-6:2026
ISO/IEC 19566-6:2019/Amd 2:2025
Information technologies — JPEG systems — Part 6: JPEG 360 — Amendment 2: Revision to the equirectangular projection constraints
Käsitlusala:
Amendment to ISO/IEC 19566-6:2019
Alusdokumendid:
Asendatud:
ISO/IEC 19566-6:2026
ISO/IEC TS 22237-31:2023
Information technology — Data centre facilities and infrastructures — Part 31: Key performance indicators for resilience
Käsitlusala:
This document:
a) defines metrics as key performance indicators (KPIs) for resilience, dependability, fault tolerance and availability tolerance for data centres;
b) covers the data centre infrastructure (DCI) of power distribution and supply, and environmental control;
c) can be referred to for covering further infrastructures, e.g. telecommunications cabling;
d) defines the measurement and calculation of the KPIs and resilience levels (RLs);
e) targets maintainability, recoverability and vulnerability;
f) provides examples for calculating these KPIs for the purpose of analytical comparison of different DCIs.
This document does not apply to IT equipment, cloud services, software or business applications.
a) defines metrics as key performance indicators (KPIs) for resilience, dependability, fault tolerance and availability tolerance for data centres;
b) covers the data centre infrastructure (DCI) of power distribution and supply, and environmental control;
c) can be referred to for covering further infrastructures, e.g. telecommunications cabling;
d) defines the measurement and calculation of the KPIs and resilience levels (RLs);
e) targets maintainability, recoverability and vulnerability;
f) provides examples for calculating these KPIs for the purpose of analytical comparison of different DCIs.
This document does not apply to IT equipment, cloud services, software or business applications.
Alusdokumendid:
Asendatud:
ISO/IEC TS 22237-31:2026
Kavandid
prEN 17014-1
Electronic public procurement - Pre-award - Part 1: Choreographies
Käsitlusala:
This choreographies document specifies pre-award processes between Contracting Entities (Buyer) and Economic Operators (Seller) where the Contracting Entity wants to contract an Economic Operator. It specifies a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are specified.
The various possible behaviours of the Seller and Buyer subsequent to the communication are conveyed by variants of this choreography that are specified in Clause 6.
This document is linked to the directives on public procurement [7] and on procurement by entities operating in the water, energy, transport and postal services sectors [8] and on the award of concession contracts [9] and on the coordination of procedures for the award of contracts in the fields of defence and security [10]. Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices [eForms] [11] and Implementing Regulation (EU) 2016/7 establishing the standard form for the European Single Procurement Document [ESPD] [12] are supplementary regulations that are relevant to this document.
The identifier of this choreographies document is EN 17014-1:2026.
The corresponding transactions are described in prEN 17014-2:2025 [13].
How to claim conformance to this choreography is specified in 6.2.2.
The various possible behaviours of the Seller and Buyer subsequent to the communication are conveyed by variants of this choreography that are specified in Clause 6.
This document is linked to the directives on public procurement [7] and on procurement by entities operating in the water, energy, transport and postal services sectors [8] and on the award of concession contracts [9] and on the coordination of procedures for the award of contracts in the fields of defence and security [10]. Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices [eForms] [11] and Implementing Regulation (EU) 2016/7 establishing the standard form for the European Single Procurement Document [ESPD] [12] are supplementary regulations that are relevant to this document.
The identifier of this choreographies document is EN 17014-1:2026.
The corresponding transactions are described in prEN 17014-2:2025 [13].
How to claim conformance to this choreography is specified in 6.2.2.
Alusdokumendid:
prEN 17014-1
prEN ISO 25063
Systems and software engineering - Systems and software product Quality Requirements and Evaluation (SQuaRE) - Common Industry Format (CIF) for usability: Context of use description (ISO/DIS 25063:2026)
Käsitlusala:
This document specifies the contents of a context of use description for an interactive system to be designed for evaluated.
The context of use description is applicable to all kinds of interactive systems, products, services or a combination of these. The description of the context of use is intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210 and ISO/IEC JTC 1/SC 7 process standards.
This document does not prescribe any kind of method, life cycle or process.
The context of use information item can be integrated into any type of process model.
NOTE For the purpose of establishing process models, ISO/IEC TR 24774 specifies the format for process models.
In addition, ISO/IEC 15289 defines the types and content of information items developed and used in process models for system and software life cycle management. ISO 9241-220 provides guidance on processes for enabling, executing and assessing human-centred design.
This document also describes the purposes for which a context of use description is used.
While this document specifies the required content components of a context of use description, it does not prescribe any particular structure or layout for documenting the context of use.
The context of use description is applicable to all kinds of interactive systems, products, services or a combination of these. The description of the context of use is intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210 and ISO/IEC JTC 1/SC 7 process standards.
This document does not prescribe any kind of method, life cycle or process.
The context of use information item can be integrated into any type of process model.
NOTE For the purpose of establishing process models, ISO/IEC TR 24774 specifies the format for process models.
In addition, ISO/IEC 15289 defines the types and content of information items developed and used in process models for system and software life cycle management. ISO 9241-220 provides guidance on processes for enabling, executing and assessing human-centred design.
This document also describes the purposes for which a context of use description is used.
While this document specifies the required content components of a context of use description, it does not prescribe any particular structure or layout for documenting the context of use.
Alusdokumendid:
ISO/DIS 25063; prEN ISO 25063
prEN ISO/IEC 29134
Information technology - Security techniques - Guidelines for privacy impact assessment (ISO/IEC 29134:2023)
Käsitlusala:
This document gives guidelines for:
a process on privacy impact assessments, and
a structure and content of a PIA report.
It is applicable to all types and sizes of organizations, including public companies, private companies, government entities and not-for-profit organizations.
This document is relevant to those involved in designing or implementing projects, including the parties operating data processing systems and services that process PII.
a process on privacy impact assessments, and
a structure and content of a PIA report.
It is applicable to all types and sizes of organizations, including public companies, private companies, government entities and not-for-profit organizations.
This document is relevant to those involved in designing or implementing projects, including the parties operating data processing systems and services that process PII.
Alusdokumendid:
ISO/IEC 29134:2023; prEN ISO/IEC 29134
prEN 17014-2
Electronic public procurement - Pre-award - Part 2: Transactions
Käsitlusala:
The document describes the transactions for pre-award processes between Contracting Entities (Buyer) and Economic Operators (Seller), where the Buyer seeks to establish a contract for the procurement of products, services, or works. The various possible behaviours of Buyers and Sellers are represented through choreography variants as described in prEN 17014-2:2025 [7].
This document specifies the transactions described by the choreography variants and captures their specific functional and informational aspects. The transactions are grouped along the following collaborations which are applied in pre-award choreographies:
— Procurement procedure subscription
— Procurement documents access
— Tender submission
— Procurement documents questions and answers
— Tender clarification
— Tender withdrawal
— Notify awarding
— Tendering message response
— Tenderer qualification
— Qualification response
— Invitation to tender
For each transaction, the document specifies the underlying business and information requirements, including the functional and procedural objectives the transaction must fulfil, the structure and semantics of the related data, and the governing business rules ensuring valid execution. In addition, all defined data elements are aligned with the eProcurement Ontology (ePO) to achieve semantic interoperability and consistent representation across procurement systems.
This document is linked to Directive 2014/24/EC on public procurement [8], Directive 2014/25/EC on procurement by entities operating in the water, energy, transport and postal services sectors [9], Directive 2014/23/EC on the award of concession contracts [10] and Directive 2009 /81/EC on the coordination of procedures for the award of contracts in the fields of defence and security [11]. Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices [eForms] [12] and Implementing Regulation (EU) 2016/7 establishing the standard form for the European Single Procurement Document [ESPD] [13] are supplementary regulations that are relevant to this document.
The identifier of this choreographies document is EN 17014-1:2026.
This document specifies the transactions described by the choreography variants and captures their specific functional and informational aspects. The transactions are grouped along the following collaborations which are applied in pre-award choreographies:
— Procurement procedure subscription
— Procurement documents access
— Tender submission
— Procurement documents questions and answers
— Tender clarification
— Tender withdrawal
— Notify awarding
— Tendering message response
— Tenderer qualification
— Qualification response
— Invitation to tender
For each transaction, the document specifies the underlying business and information requirements, including the functional and procedural objectives the transaction must fulfil, the structure and semantics of the related data, and the governing business rules ensuring valid execution. In addition, all defined data elements are aligned with the eProcurement Ontology (ePO) to achieve semantic interoperability and consistent representation across procurement systems.
This document is linked to Directive 2014/24/EC on public procurement [8], Directive 2014/25/EC on procurement by entities operating in the water, energy, transport and postal services sectors [9], Directive 2014/23/EC on the award of concession contracts [10] and Directive 2009 /81/EC on the coordination of procedures for the award of contracts in the fields of defence and security [11]. Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices [eForms] [12] and Implementing Regulation (EU) 2016/7 establishing the standard form for the European Single Procurement Document [ESPD] [13] are supplementary regulations that are relevant to this document.
The identifier of this choreographies document is EN 17014-1:2026.
Alusdokumendid:
prEN 17014-2
prEN 17017-2
Electronic Public Procurement - Fulfilment - Part 2: Transactions
Käsitlusala:
This document describes the transaction information requirements of the transactions used in the basic collaborations described in EN 17017-1:2025, Electronic Public Procurement - Fulfillment - 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:
a) Despatch Advice;
b) Receipt Advice.
The identifier of this transactions document is CEN/EN 17017 2:20xx.
How to claim compliance to a transaction is described in Clause 6.
The document describes the following transactions:
a) Despatch Advice;
b) Receipt Advice.
The identifier of this transactions document is CEN/EN 17017 2:20xx.
How to claim compliance to a transaction is described in Clause 6.
Alusdokumendid:
prEN 17017-2