Infoteenus
25 TOOTMISTEHNOLOOGIA
Uued standardid
EVS-EN IEC 62541-1:2026
OPC unified architecture - Part 1: Overview and concepts
Käsitlusala:
IEC 62541-1:2025 presents the concepts and overview of the OPC Unified Architecture (OPC UA). Reading this document is helpful to understand the remaining parts of the IEC 62541 series. Each of the other parts is briefly explained along with a suggested reading order. This first edition cancels and replaces IEC TR 62541-1 published in 2020
Alusdokumendid:
IEC 62541-1:2025; EN IEC 62541-1:2026
EVS-EN IEC 62541-17:2026
OPC unified architecture - Part 17: Alias names
Käsitlusala:
This specification provides a definition of AliasNames functionality. AliasNames provide a manner of configuring and exposing an alternate well-defined name for any Node in the system. This is analogous to the way domain names are used as an alias to IP addresses in IP networks. Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related Node on a Server. An aggregating Server can collect these AliasNames from multiple Servers and provide a lookup Method to allow Client applications to discover NodeIds on a system wide basis. An aggregating Server might also define AliasNames for Nodes in other Servers that do not support AliasNames. A GDS may be constructed that would automatically aggregate all AliasNames that are defined on any Server that has registered with the GDS. In this case the GDS also provides the lookup mechanism for Clients at a well-known endpoint and address.
The GDS functionality for AliasNames is formally defined in Annex B.
The GDS functionality for AliasNames is formally defined in Annex B.
Alusdokumendid:
EN IEC 62541-17:2026; IEC 62541-17:2025
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
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
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 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
IEC 62841-2-24:2026
Electric motor-operated hand-held tools, transportable tools and lawn and garden machinery - Safety - Part 2-24: Particular requirements for hand-held oscillating multifunction tools
Käsitlusala:
IEC 62841-2-24:2026 applies to oscillating multifunction tools.
This document is to be used in conjunction with IEC 62841-1:2014 and IEC 62841-1:2014/AMD1:2025.
This document supplements or modifies the corresponding clauses in IEC 62841-1, so as to convert it into the IEC Standard: Particular requirements for hand-held oscillating multifunction tools.
Where a particular subclause of IEC 62841-1 is not mentioned in this document, that subclause applies as far as reasonable. Where this document states "addition", "modification" or "replacement", the relevant text in IEC 62841-1 is to be adapted accordingly.
The attention of National Committees is drawn to the fact that equipment manufacturers and testing organizations may need a transitional period following publication of a new, amended or revised IEC publication in which to make products in accordance with the new requirements and to equip themselves for conducting new or revised tests.
It is the recommendation of the committee that the content of this publication be adopted for implementation nationally not earlier than 36 months from the date of publication.
This document is to be used in conjunction with IEC 62841-1:2014 and IEC 62841-1:2014/AMD1:2025.
This document supplements or modifies the corresponding clauses in IEC 62841-1, so as to convert it into the IEC Standard: Particular requirements for hand-held oscillating multifunction tools.
Where a particular subclause of IEC 62841-1 is not mentioned in this document, that subclause applies as far as reasonable. Where this document states "addition", "modification" or "replacement", the relevant text in IEC 62841-1 is to be adapted accordingly.
The attention of National Committees is drawn to the fact that equipment manufacturers and testing organizations may need a transitional period following publication of a new, amended or revised IEC publication in which to make products in accordance with the new requirements and to equip themselves for conducting new or revised tests.
It is the recommendation of the committee that the content of this publication be adopted for implementation nationally not earlier than 36 months from the date of publication.
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
IEC 62841-4-9:2026
Electric motor-operated hand-held tools, transportable tools and lawn and garden machinery - Safety - Part 4-9: Particular requirements for battery-powered chain saws for tree service
Käsitlusala:
IEC 62841-4-9:2026 applies to rechargeable battery-powered motor-operated chain saws for tree service, hereinafter referred to as chain saws or machines, having a maximum mass of 5,0 kg. The mass includes the heaviest detachable battery pack(s), if any, as described in IEC 62841-1:2014, K.8.14.2 e) 2), but excludes the guide bar, saw chain and saw chain lubricant. Chain saws covered by this document are intended to be used for pruning and dismantling standing tree crowns.
The chain saws covered by this document are designed only to be operated with the right hand on the rear handle and the left hand on the front handle.
This document does not apply to
– chain saws supplied by mains power or power from non-isolated sources that permit the machine to be used while connected to such power supplies; or
– chain saws supplied by integral batteries; or
– chain saws for cutting wood as covered by IEC 62841-4-1; or
– chain saws designed for use in conjunction with a guide-plate and riving knife or in any other way such as with a support or as a stationary or transportable machine; or
– pole-mounted pruners; or
NOTE 1 Pole-mounted pruners are covered by IEC 62841-4-10.
– pruning saws.
NOTE 2 Pruning saws will be covered by a future part of IEC 62841-4.
The maximum rated voltage for machines and battery packs is 75 V d.c.
Battery machines covered by this document are not considered to be class I tools, class II tools or class III tools and therefore are not required to have basic insulation, supplementary insulation or reinforced insulation. Electric shock hazard is considered to exist only between parts of opposite polarity.
This document deals with the hazards presented by machines which are encountered by all persons in the normal use and reasonably foreseeable misuse of the machines.
When evaluating a rechargeable battery pack for protection against electric shock during charging, creepage distances, clearances and distances through insulation, the relevant requirements of this document are applicable with the battery pack fitted to the intended charger.
Since rechargeable battery packs for machines are submitted to different use patterns (such as rough use, high charging and discharging currents), their safety can be evaluated only by this document and not by using other standards for rechargeable battery packs, such as IEC 62133-1:2017 or IEC 62133-2:2017, unless otherwise indicated in this document. All relevant aspects related to the safety of rechargeable batteries are addressed in this document, such that the requirements of IEC 62133-1:2017 or IEC 62133-2:2017 are not required to be separately applied.
When evaluating the risk of fire associated with rechargeable battery packs for machines, consideration has been given to the fact that these battery packs are unattended energy sources and have been evaluated as such in this document. Requirements in other standards regarding the risk of fire due to the charging of these battery packs are therefore considered to be fulfilled.
This document also addresses requirements covering the use of lithium-ion cells employed in battery systems in machines. The following is considered within the context of these requirements:
– These requirements address the risk of fire or explosion of these batteries and not any possible hazards associated with toxicity nor potential hazards associated with transportation or disposal.
NOTE 3 IEC 62281:2019 covers the safety aspects of lithium-ion batteries during transport.
– Battery systems covered by these requirements are not intended to be serviced by the end user.
– These requirements are intended to provide comprehensive evaluation of a battery only if used in products covered by this document.
– These requirements address the safety of lithium-ion battery systems during storage and use including discharge and charge. These requirements are only considered to be supplementary requirements in regard to battery charger fire and electric shock.
– These requirements refer to and require parameters supplied in reference to th
The chain saws covered by this document are designed only to be operated with the right hand on the rear handle and the left hand on the front handle.
This document does not apply to
– chain saws supplied by mains power or power from non-isolated sources that permit the machine to be used while connected to such power supplies; or
– chain saws supplied by integral batteries; or
– chain saws for cutting wood as covered by IEC 62841-4-1; or
– chain saws designed for use in conjunction with a guide-plate and riving knife or in any other way such as with a support or as a stationary or transportable machine; or
– pole-mounted pruners; or
NOTE 1 Pole-mounted pruners are covered by IEC 62841-4-10.
– pruning saws.
NOTE 2 Pruning saws will be covered by a future part of IEC 62841-4.
The maximum rated voltage for machines and battery packs is 75 V d.c.
Battery machines covered by this document are not considered to be class I tools, class II tools or class III tools and therefore are not required to have basic insulation, supplementary insulation or reinforced insulation. Electric shock hazard is considered to exist only between parts of opposite polarity.
This document deals with the hazards presented by machines which are encountered by all persons in the normal use and reasonably foreseeable misuse of the machines.
When evaluating a rechargeable battery pack for protection against electric shock during charging, creepage distances, clearances and distances through insulation, the relevant requirements of this document are applicable with the battery pack fitted to the intended charger.
Since rechargeable battery packs for machines are submitted to different use patterns (such as rough use, high charging and discharging currents), their safety can be evaluated only by this document and not by using other standards for rechargeable battery packs, such as IEC 62133-1:2017 or IEC 62133-2:2017, unless otherwise indicated in this document. All relevant aspects related to the safety of rechargeable batteries are addressed in this document, such that the requirements of IEC 62133-1:2017 or IEC 62133-2:2017 are not required to be separately applied.
When evaluating the risk of fire associated with rechargeable battery packs for machines, consideration has been given to the fact that these battery packs are unattended energy sources and have been evaluated as such in this document. Requirements in other standards regarding the risk of fire due to the charging of these battery packs are therefore considered to be fulfilled.
This document also addresses requirements covering the use of lithium-ion cells employed in battery systems in machines. The following is considered within the context of these requirements:
– These requirements address the risk of fire or explosion of these batteries and not any possible hazards associated with toxicity nor potential hazards associated with transportation or disposal.
NOTE 3 IEC 62281:2019 covers the safety aspects of lithium-ion batteries during transport.
– Battery systems covered by these requirements are not intended to be serviced by the end user.
– These requirements are intended to provide comprehensive evaluation of a battery only if used in products covered by this document.
– These requirements address the safety of lithium-ion battery systems during storage and use including discharge and charge. These requirements are only considered to be supplementary requirements in regard to battery charger fire and electric shock.
– These requirements refer to and require parameters supplied in reference to th
Alusdokumendid:
Asendatud standardid
ISO/TS 18166:2016
Numerical welding simulation -- Execution and documentation
Käsitlusala:
ISO/TS 18166:2016 provides a workflow for the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM). As such, it primarily addresses thermal and mechanical finite element analysis (FEA) of the fusion welding (see ISO/TR 25901:2007, 2.165) of metal parts and fabrications.
CWM is a broad and growing area of engineering analysis.
ISO/TS 18166:2016 covers the following aspects and results of CWM, excluding simulation of the process itself:
- heat flow during the analysis of one or more passes;
- thermal expansion as a result of the heat flow;
- thermal stresses;
- development of inelastic strains;
- effect of temperature on material properties;
- predictions of residual stress distributions;
- predictions of welding distortion.
ISO/TS 18166:2016 refers to the following physical effects, but these are not covered in depth:
- physics of the heat source (e.g. laser or welding arc);
- physics of the melt pool (and key hole for power beam welds);
- creation and retention of non-equilibrium solid phases;
- solution and precipitation of second phase particles;
- effect of microstructure on material properties.
The guidance given by this Technical Specification has not been prepared for use in a specific industry. CWM can be beneficial in design and assessment of a wide range of components. It is anticipated that it will enable industrial bodies or companies to define required levels of CWM for specific applications.
This Technical Specification is independent of the software and implementation, and therefore is not restricted to FEA, or to any particular industry.
It provides a consistent framework for-primary aspects of the commonly adopted methods and goals of CWM (including validation and verification to allow an objective judgment of simulation results).
Through presentation and description of the minimal required aspects of a complete numerical welding simulation, an introduction to computational welding mechanics (CWM) is also provided. (Examples are provided to illustrate the application of this Technical Specification, which can further aid those interested in developing CWM competency).
Clause 4 of this Technical Specification provides more detailed information relating to the generally valid simulation structure and to the corresponding application. Clause 5 refers to corresponding parts of this Technical Specification in which the structure for the respective application cases is put in concrete terms and examples are given. Annex A presents a documentation template to promote the consistency of the reported simulation results.
CWM is a broad and growing area of engineering analysis.
ISO/TS 18166:2016 covers the following aspects and results of CWM, excluding simulation of the process itself:
- heat flow during the analysis of one or more passes;
- thermal expansion as a result of the heat flow;
- thermal stresses;
- development of inelastic strains;
- effect of temperature on material properties;
- predictions of residual stress distributions;
- predictions of welding distortion.
ISO/TS 18166:2016 refers to the following physical effects, but these are not covered in depth:
- physics of the heat source (e.g. laser or welding arc);
- physics of the melt pool (and key hole for power beam welds);
- creation and retention of non-equilibrium solid phases;
- solution and precipitation of second phase particles;
- effect of microstructure on material properties.
The guidance given by this Technical Specification has not been prepared for use in a specific industry. CWM can be beneficial in design and assessment of a wide range of components. It is anticipated that it will enable industrial bodies or companies to define required levels of CWM for specific applications.
This Technical Specification is independent of the software and implementation, and therefore is not restricted to FEA, or to any particular industry.
It provides a consistent framework for-primary aspects of the commonly adopted methods and goals of CWM (including validation and verification to allow an objective judgment of simulation results).
Through presentation and description of the minimal required aspects of a complete numerical welding simulation, an introduction to computational welding mechanics (CWM) is also provided. (Examples are provided to illustrate the application of this Technical Specification, which can further aid those interested in developing CWM competency).
Clause 4 of this Technical Specification provides more detailed information relating to the generally valid simulation structure and to the corresponding application. Clause 5 refers to corresponding parts of this Technical Specification in which the structure for the respective application cases is put in concrete terms and examples are given. Annex A presents a documentation template to promote the consistency of the reported simulation results.
Alusdokumendid:
Asendatud:
ISO 18166:2026
CEN ISO/TS 18166:2016
Numerical welding simulation - Execution and documentation (ISO/TS 18166:2016)
Käsitlusala:
ISO/TS 18166:2016 provides a workflow for the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM). As such, it primarily addresses thermal and mechanical finite element analysis (FEA) of the fusion welding (see ISO/TR 25901:2007, 2.165) of metal parts and fabrications.
CWM is a broad and growing area of engineering analysis.
ISO/TS 18166:2016 covers the following aspects and results of CWM, excluding simulation of the process itself:
- heat flow during the analysis of one or more passes;
- thermal expansion as a result of the heat flow;
- thermal stresses;
- development of inelastic strains;
- effect of temperature on material properties;
- predictions of residual stress distributions;
- predictions of welding distortion.
ISO/TS 18166:2016 refers to the following physical effects, but these are not covered in depth:
- physics of the heat source (e.g. laser or welding arc);
- physics of the melt pool (and key hole for power beam welds);
- creation and retention of non-equilibrium solid phases;
- solution and precipitation of second phase particles;
- effect of microstructure on material properties.
The guidance given by this Technical Specification has not been prepared for use in a specific industry. CWM can be beneficial in design and assessment of a wide range of components. It is anticipated that it will enable industrial bodies or companies to define required levels of CWM for specific applications.
This Technical Specification is independent of the software and implementation, and therefore is not restricted to FEA, or to any particular industry.
It provides a consistent framework for-primary aspects of the commonly adopted methods and goals of CWM (including validation and verification to allow an objective judgment of simulation results).
Through presentation and description of the minimal required aspects of a complete numerical welding simulation, an introduction to computational welding mechanics (CWM) is also provided. (Examples are provided to illustrate the application of this Technical Specification, which can further aid those interested in developing CWM competency).
Clause 4 of this Technical Specification provides more detailed information relating to the generally valid simulation structure and to the corresponding application. Clause 5 refers to corresponding parts of this Technical Specification in which the structure for the respective application cases is put in concrete terms and examples are given. Annex A presents a documentation template to promote the consistency of the reported simulation results.
CWM is a broad and growing area of engineering analysis.
ISO/TS 18166:2016 covers the following aspects and results of CWM, excluding simulation of the process itself:
- heat flow during the analysis of one or more passes;
- thermal expansion as a result of the heat flow;
- thermal stresses;
- development of inelastic strains;
- effect of temperature on material properties;
- predictions of residual stress distributions;
- predictions of welding distortion.
ISO/TS 18166:2016 refers to the following physical effects, but these are not covered in depth:
- physics of the heat source (e.g. laser or welding arc);
- physics of the melt pool (and key hole for power beam welds);
- creation and retention of non-equilibrium solid phases;
- solution and precipitation of second phase particles;
- effect of microstructure on material properties.
The guidance given by this Technical Specification has not been prepared for use in a specific industry. CWM can be beneficial in design and assessment of a wide range of components. It is anticipated that it will enable industrial bodies or companies to define required levels of CWM for specific applications.
This Technical Specification is independent of the software and implementation, and therefore is not restricted to FEA, or to any particular industry.
It provides a consistent framework for-primary aspects of the commonly adopted methods and goals of CWM (including validation and verification to allow an objective judgment of simulation results).
Through presentation and description of the minimal required aspects of a complete numerical welding simulation, an introduction to computational welding mechanics (CWM) is also provided. (Examples are provided to illustrate the application of this Technical Specification, which can further aid those interested in developing CWM competency).
Clause 4 of this Technical Specification provides more detailed information relating to the generally valid simulation structure and to the corresponding application. Clause 5 refers to corresponding parts of this Technical Specification in which the structure for the respective application cases is put in concrete terms and examples are given. Annex A presents a documentation template to promote the consistency of the reported simulation results.
Alusdokumendid:
ISO/TS 18166:2016; CEN ISO/TS 18166:2016
Asendatud:
EVS-EN ISO 18166: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
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-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
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
Kavandid
prEN IEC 63595-1:2026
Industrial networks - 5G Communication Technology - Part 1: Terms, definitions and fundamentals
Käsitlusala:
This Part 1 of the IEC 63595 series [1] provides fundamentals for the specification of wireless communication systems based on 5G and beyond technologies applicable for industrial process measurement, control and automation. The basic architecture of a 5G system is presented, which forms the basis of industrial 5G systems. Essential 5G terms are listed with references to 3GPP documents. Additional definitions of industrial applications terms are provided. These definitions are used in the IEC 63595 series [1].
The context of an industrial 5G system is described, from which the requirements for such a system can be derived. Based on that this document provides a description of the conceptual model of industrial 5G in the context of industrial production (process and manufacturing) including interfaces of an industrial 5G communication system to automation systems (reference interface, configuration interface, monitoring interface) and its parameters.
The context of an industrial 5G system is described, from which the requirements for such a system can be derived. Based on that this document provides a description of the conceptual model of industrial 5G in the context of industrial production (process and manufacturing) including interfaces of an industrial 5G communication system to automation systems (reference interface, configuration interface, monitoring interface) and its parameters.
Alusdokumendid:
prEN IEC 63595-1:2026; 65C/1381/CDV