35.240.50 - IT applications in industry
ICS 35.240.50 Details
IT applications in industry
IT-Anwendungen in der Industrie
Applications des TI dans l'industrie
Uporabniške rešitve IT v industriji
General Information
Frequently Asked Questions
ICS 35.240.50 is a classification code in the International Classification for Standards (ICS) system. It covers "IT applications in industry". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 843 standards classified under ICS 35.240.50 (IT applications in industry). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.50 - IT applications in industry
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
IEC 63278-4:2026 assumes an application perspective of the Asset Administration Shell to develop a common understanding on how to use an Asset Administration Shell.
This document defines how the Asset Administration Shell can be used in the context of the related entities and how to represent assets using the Asset Administration Shell.
Due to the more detailed description compared to IEC 63278-1, additional requirements, recommendations, and permissions for the AAS are stated towards application of the AAS in selected scenarios.
- Standard238 pagesEnglish and French languagesale 15% off
- Standard238 pagesEnglish and French languagesale 15% off
This document specifies requirements, a framework, a general specification procedure, a guide for elaboration, and categorization of application methods of an equipment behaviour catalogue (EBC) in smart manufacturing.
- Standard21 pagesEnglish languagesale 15% off
This document specifies the interface architecture of industrial digital twin systems, which is structured around three key elements: the digital twin, the physical twin and the interface that links them. Together, these elements form the essential framework of an industrial digital twin. The following are within the scope of this document: Defining the elements of industrial digital twin systems that embody a distinct architecture. Analysing the interactions among the three core elements of industrial digital twin systems Identifying the characteristics that distinguish industrial digital twin systems from related concepts or technologies Examining typical use cases that implement the three-element interface architecture The following is outside the scope of this document: Detailed applications of industrial digital twin systems
- Technical specification28 pagesEnglish languagesale 15% off
This document specifies guidelines for smart manufacturing technologies applicable to smart plants in the iron and steel industry, together with the basic requirements for these technologies as defined in the application guidelines. This document covers three dimensions related to the steel production process: smart production process design, smart equipment, and smart production. This document provides an overview of the potential applications of smart manufacturing technology in these scenarios, as well as the specific technical requirements it needs to meet. This document provides reference guidelines for the iron and steel industry to formulate smart factory upgrading plans to improve productivity and product quality. It is intended for use by iron and steel manufacturing enterprises, smart manufacturing technology vendors, and relevant public sector organizations, and is applicable to steel plants regardless of manufacturing process route, equipment configuration, plant size, geographic location, or product type. This document is not intended to be used for any form of evaluation or grading of steel plants or companies.
- Standard17 pagesEnglish languagesale 15% off
This document specifies digital twin compositions in manufacturing by defining principles, describing methodologies and providing use-case examples of digital twin communication, aggregation and interoperation. This document identifies three kinds of digital twin composition (integrated, unified, and federated) and specifies requirements and step-by-step implementation guidelines for each kind. It provides structured approaches for composing multiple digital twins to support interoperability among digital twins developed by different parties, such as vendors, solution providers, and in-house developers. The document also includes illustrative use cases to demonstrate the practical application of the specified composition approaches.
- Standard31 pagesEnglish languagesale 15% off
This document specifies how a digital thread enables the creation, connectivity, management, and maintenance of manufacturing digital twins across the product life cycle, including design, planning, production, and testing by defining principles, presenting methodologies, and providing use case examples.
- Standard26 pagesEnglish languagesale 15% off
This document specifies a reference model and process for Collaborative Modeling and Simulation Environment (CMSE), which establishes a general framework of CMSE to provide guidance for implementation of joint simulation projects. The CMSE which is based on the reference process and the reference model including neutral interfaces and meta-models can enable service-oriented share-use of the infrastructure, integration of the software and collaboration of the business to improve collaboration among all kinds of stakeholders involved in a joint simulation project which needs on-demand simulation at any time and any place upon different manufacturing platforms owned by different enterprises or by different departments within an enterprise. This document can not only be applied to manufacturing enterprises but also be applied to other kinds of enterprises. It is intended for use by stakeholders who are concerned with developing and deploying solutions of the joint simulation project based on information and communication technology. It focuses on simulation activities related cross-platform simulation collaboration capability supporting business planning and logistics, manufacturing operations management and production control within or among enterprises, which can cover the levels from 2 to 4 of the functional hierarchy of manufacturing systems in IEC 62264-3[27]. This document specifies the following: the general framework of CMSE; the methodology of the joint simulation project analysis and realization by CMSE. This document does not relate to the simulation irrelevant collaboration environment, and does not specify the specific approach to implement CMSE in the solution formulation of joint simulation projects.
- Standard32 pagesEnglish languagesale 15% off
This document describes a digital twin system for monitoring and managing the robotic multilayer and multipass gas-shielded metal arc welding process.
- Technical report18 pagesEnglish languagesale 15% off
IEC 61512-1:2026 applies to systems, specifications, and their use for implementing batch and related procedure-oriented manufacturing controls in the process industries. This document establishes a reference model framework for procedure-oriented control, defines terms to help explain the model relationships and usage, and describes general criteria for evaluating conformance. This follows the principle of separation between recipe procedural elements and equipment procedural elements enabling operations to define recipes without the need of changes in equipment procedures.
This second edition cancels and replaces the first edition published in 1997. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Models and text are modified to provide more detail and clarity. Key clarifications are:
1) Two types of equipment modules are defined: generic and recipe-aware. All recipe-aware equipment modules contain procedural control and can be used as phases in the recipe.
2) Execution of all procedural control contained directly in units is part of the Unit Supervision activity.
3) The relationships between types of recipes, recipe components, and equipment control are more fully described and illustrated.
4) Entity relationship diagrams have been replaced with more intuitive UML instance diagrams, except for the equipment entity model.
5) The transition diagram for the procedural states example has been updated with a more intuitive and complete UML state diagram.
6) References to other standards in the series and to IEC 62264 are included to provide direction for further clarification of selected topics.
7) Activity names are capitalised to help prevent confusion with similar terms, such as their underlying functions.
b) Previous Clauses 4 through 6 (now Clauses 4 through 8) were rearranged to provide a clearer top-down organisation of the document. Key changes are:
1) Removing the lower levels of the physical (role-based equipment) model (see 4.4.2) to eliminate redundancy because their groupings are defined by the associated functionality in the equipment entity model and are not meaningful for batch control without those associations.
2) Describing equipment control and the equipment entity model immediately after the physical (role-based equipment) model and describing each level as completely as possible without excessive use of forward references (see 4.4.3).
3) Combining the descriptions of basic, procedural, and coordination control with their usage in each type of equipment entity, providing a single consolidated discussion of each type of control (see Clause 5)
4) Additional considerations to support application of the models have been grouped in Clause 7 to clarify their supporting relationship to the core models.
c) Clause 9 was added to define completeness, compliance, and conformance in relation to this document.
d) Annex B was added to provide a more expansive procedural state reference model. The model found in Clause 7 can be considered a collapsed version of this more general model.
e) Annex C was added to clarify a number of points concerning the models, their application, and the new Clause 9 on conformance and compliance.
f) Annex E was added to more fully describe the changes in this update to IEC 61512-1:1997.
- Standard132 pagesEnglish languagee-Library read for1 day
IEC 62541-2:2026 describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware, and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It provides definition of common security terms that are used in this and other parts of the IEC 62541 series. It gives an overview and concept of the security features that are specified in other parts of the series. It references services, mappings, and Profiles that are specified normatively in other parts of the 62541 series. It provides suggestions or best practice guidelines on implementing security. Any seeming ambiguity between this document and one of the other normative parts does not remove or reduce the requirement specified in the other normative part.
There are many different aspects of security that are addressed when developing applications. However, since OPC UA specifies a communication protocol, the focus is on securing the data exchanged between applications. This does not mean that an application developer can ignore the other aspects of security like protecting persistent data against tampering. It is important that the developers look into all aspects of security and decide how they can be addressed in the application. Common security features for industrial Controls are defined in IEC 62443-4-2 and OPC UA defined a relationship to them in Annex A.
This document is directed to readers who will develop OPC UA applications. It is also for end Users that wish to understand the various security features and functionality provided by OPC UA. It also offers some recommendations that can be applied when deploying systems. These recommendations are generic in nature since the details would depend on the actual implementation of the OPC UA applications and the choices made for the site security.
This edition cancels and replaces the third edition of IEC TR 62541-2, published in 2020.This edition constitutes a technical revision.
- Standard64 pagesEnglish languagee-Library read for1 day
IEC 62264-2:2026 specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation. Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations. The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1. This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3): a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model. b) operations location model and spatial definition attribute added to allow the description of operation locations. c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions. d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document. e) updated hierarchy scope model. f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models. g) object model was added for the operations segment capability as a collection of resources related to other operations models. h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables. i) updated all objects’ relationship role table with explicit source and target names. j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables. k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models. l) added an annex explanation for implementation options for specifying values in unit of measurement a
- Draft476 pagesEnglish languagee-Library read for1 day
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard165 pagesEnglish languagee-Library read for1 day
IEC 62541-24:2026 specifies an OPC UA information model to expose information, at what dates and times specific actions are executed by the OPC UA Server. Those schedules can optionally also be manipulated via the information model.
The schedule defines on which dates they are active, and can also reference global calendars representing specific dates, for example public holidays. In addition, the schedule defines times and actions that will be executed at that time. The model defines writing Variables and calling Methods but can be extended to other actions as well.
The NamespaceUri for all NodeIds defined in this document is defined in Annex A.
- Standard34 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP.
Not all OPC UA Servers implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile.
A BNF (Backus-Naur form) for browse path names is described in Annex A.
- Standard249 pagesEnglish languagee-Library read for1 day
IEC 62541-1:2025 presents the concepts and overview of the OPC Unified Architecture (OPC UA). Reading this document is helpful to understand the remaining parts of the IEC 62541 series. Each of the other parts is briefly explained along with a suggested reading order. This first edition cancels and replaces IEC TR 62541-1 published in 2020
- Standard33 pagesEnglish languagee-Library read for1 day
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard156 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs.
The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage
Programs are specified in IEC 62541-4.
An example for a DomainDownload Program is defined in Annex A.
- Standard46 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates.
Programmatically produced aggregate examples are listed in Annex A.
- Standard68 pagesEnglish languagee-Library read for1 day
This part of IEC 62541, the IEC standards series dedicated to the OPC Unified Architecture, defines an Information Model. The Information Model describes the basic infrastructure to model file transfers.
NOTE In the previous version, File Transfer was in IEC 62541-5:2020, Annex C.
- Standard30 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour.
The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541-3. The services to detect and access data are specified in IEC 62541-4.
Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model.
- Standard96 pagesEnglish languagee-Library read for1 day
IEC 62541-21:2026 defines the life cycle of Devices and Composites and mechanisms to verify their authenticity, set up their security and maintain their configuration.
The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the NamespaceUri for all NodeIds and the actual NodeIds.
- Standard58 pagesEnglish languagee-Library read for1 day
IEC 62541-19: 2025 defines an Information Model of the OPC Unified Architecture. The Information Model describes the basic infrastructure to reference from an OPC UA Information Model to external dictionaries like IEC Common Data Dictionary or ECLASS.
- Standard19 pagesEnglish languagee-Library read for1 day
IEC 62541-16:2025 defines an Information Model. The Information Model describes the basic infrastructure to model state machines.
NOTE State Machines were dealt with in IEC 62541‑5:2020, Annex B. In newer versions of IEC 62541‑5 this Annex B was removed and replaced by this document
- Standard39 pagesEnglish languagee-Library read for1 day
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition:
a) Annex B has been removed and used to create IEC 62451-16;
b) Annex C has been removed and used to create IEC 62451-20;
c) currency information model has been added;
d) information model for Interfaces and AddIns has been added;
e) information model for Method Metadata has been added;
f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities;
g) information model for ordered list of objects has been added;
h) PortableQualifiedName and PortableNodeId DataTypes have been added;
i) UriString DataType has been added;
j) SemanticVersionString DataType has been added;
k) AssociatedWith Reference Type has been added;
l) ConfigurationVersion Property has been added to NamespaceMetadataType;
m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added;
n) ModelVersion has been added to NamespaceMetadataType;
o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case;
p) BitFieldType and BitFieldDefinitionType have been added.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard193 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 belongs to the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour.
The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4.
This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13.
Conventions for Historical Access Clients are informatively provided in Annex A.
- Standard77 pagesEnglish languagee-Library read for1 day
IEC 62541-12:2025 specifies how OPC Unified Architecture (OPC UA) Clients and Servers interact with DiscoveryServers when used in different scenarios. It specifies the requirements for the LocalDiscoveryServer, LocalDiscoveryServer-ME and GlobalDiscoveryServer. It also defines information models for Certificate management, KeyCredential management and AuthorizationServices.
Annex A informatively discusses deployment and configuration aspects.
Annex B defines NodeSet and numeric NodeIds.
Annex F provides installation rules for the LDS.
Annex H compares the Certificate management defined in this document with IETF RFC 7030.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of a "Quantity Model" which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them;
b) addition of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• additional rules when ValuePrecision has negative values.
- Standard147 pagesEnglish languagee-Library read for1 day
IEC 62541-22:2025 specifies an OPC UA Information Model for a basic set of network related components used in other Information Models.
The initial version of this document defines parameter sets for TSN Talkers and Listeners as well as network interfaces and ports as shown in Figure 1. A future version of this document is expected to have a broader scope of other network technologies than Ethernet only.
- Standard43 pagesEnglish languagee-Library read for1 day
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 62541‑2, the abstract service definitions specified in IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols that can be used to implement the OPC UA specification.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of support for ECC to UA Secure Conversation;
b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists;
c) enhancement of JSON mapping of Unions;
d) addition of Decimal data type encoding.
e) description of ECC keyUsage rules;
f) addition of Media assigned by IANA to UANodeSet definition;
g) addition of requirements for user and issuer Certificates;
h) addition of rules which specify what happens when DateTime precision is lost;
i) addition of rules to allow for the truncation of strings containing embedded nulls.
J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping.
k) requirement that TAI times be converted to UTC;
l) new possibility to omit Symbol if unknown in JSON encoding;
m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard144 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses.
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
This document consists of
• a general introduction of the PubSub concepts,
• a definition of the PubSub configuration parameters,
• mapping of PubSub concepts and configuration parameters to messages and transport protocols,
• and a PubSub configuration model.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Addition of a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) Addion of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• rules have been added when ValuePrecision has negative values.
- Standard320 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of the concept and modelling elements for Interfaces and AddIns;
b) addition of Currency;
c) addition of Method Meta Data to define additional attributes for Method Arguments;
d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType;
e) addition of a Non-Volatile Storage bit to AccessLevelExType;
f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType;
g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it;
h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node;
i) NamingRules have become deprecated;
j) addition of AssociatedWith ReferenceType.
- Standard143 pagesEnglish languagee-Library read for1 day
IEC 62541-23:2025 defines ReferenceTypes commonly used in industrial Information Models. They are more specific than the ReferenceTypes in IEC 62541‑3 which are an inherent part of the OPC UA Address Space Model.
- Standard28 pagesEnglish languagee-Library read for1 day
IEC 62541-17:2025 provides a definition of AliasNames functionality. AliasNames provide a manner of configuring and exposing an alternate well-defined name for any Node in the system. This is analogous to the way domain names are used as an alias to IP addresses in IP networks. Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related Node on a Server. An aggregating Server can collect these AliasNames from multiple Servers and provide a lookup Method to allow Client applications to discover NodeIds on a system wide basis. An aggregating Server could also define AliasNames for Nodes in other Servers that do not support AliasNames. A GDS can be constructed that would automatically aggregate all AliasNames that are defined on any Server that has registered with the GDS. In this case, the GDS also provides the lookup mechanism for Clients at a well-known endpoint and address.
- Standard28 pagesEnglish languagee-Library read for1 day
This document defines the syntax and semantics of a file format for the 3D visualization and interrogation of lightweight geometry and product manufacturing information derived from CAD systems, using visualization software tools that do not need the full capability of a CAD system. This document has been adopted as a 3D visualization capability in addition to the ISO 10303 series. The ISO 10303 series are the ISO standards adopted for the engineering data exchange, sharing and long-term archiving of product definition information throughout the product lifecycle. In this document 3D visualization is defined as the visual presentation on a screen or another media of graphical and textual 3-dimensional representations of a set of data representing an object, information or results of a computational process in order to enable decision process by a human looking at the data visualized in a medium. The ISO 14306 file format specification for 3D visualization includes data descriptions that can represent the following data: facet information (triangles), stored with geometry compression techniques; visual attributes such as lights, textures and materials; product manufacturing information (PMI); boundary representation (b-rep) solid model shape representation and associated metadata; configuration representations; and delivery methods such as asynchronous streaming of content. The file format specification for 3D visualization does not specify the implementation of, or definition of a run-time architecture for viewing and/or processing ISO 14306 data.
- Standard479 pagesEnglish languagesale 15% off
This document specifies the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM) and performed with a scientific computational tool (SCT).
This document is applicable to the thermal and mechanical finite element analysis (FEA) of arc, laser and electron beam welding processes for the purpose of calculating the effects of welding processes, and in particular, residual stresses and distortion, in support of structural integrity assessment.
- Standard56 pagesEnglish languagee-Library read for1 day
This document specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation. Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations. The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1.
- Standard459 pagesEnglish languagesale 15% off
- Standard513 pagesFrench languagesale 15% off
IEC 62264-2:2026 specifies interface content exchanged between manufacturing control functions and other enterprise functions as interrelated information models. The information models are represented as an interrelated collection of conceptual object models which can be used for the implementation of applications with logical data and physical data models. The data exchanges in interfaces are scoped as between Level 3 manufacturing operations and Level 4 business systems in the hierarchical model defined in IEC 62264-1. The purpose of this document is to reduce the risk, cost, and errors associated with interface implementation.
Since this document covers many manufacturing operations and enterprise domains and there are many different standards for those domains, the semantics of this data exchange standard are described at a conceptual level intended to enable the other standards to be mapped to these semantics. To this end, this document defines a set of elements contained in the generic interface, together with a mechanism for extending the interface content for implementations.
The scope is limited to the definition of object models and attributes of the exchanged information defined in the IEC 62264-1.
This third edition cancels and replaces the second edition published in 2013. It is published as a double logo standard. This edition constitutes a technical revision. Due to the extent of the changes and updates, this document cannot ensure backward compatibility to implementations based on older editions. This edition includes the following significant technical changes with respect to the previous edition and ANSI/ISA 95.00.02-2018 (ED3):
a) object models are added for the use of interactive communications to notify subscribers about the occurrence of events and to provide context information about the event, making the information exchange more efficient and consistent. The added object models were the operations event model and operations record model.
b) operations location model and spatial definition attribute added to allow the description of operation locations.
c) operations test model added to define how test specifications and test results are related to testable objects, operations test requirements, actual resource, and work definitions.
d) definition of possible measurement uncertainty sub-attributes for all value, quantity and duration attributes defined in this document.
e) updated hierarchy scope model.
f) removed as separate models in this edition were the models for product definition, production schedule, production performance, and production capability. Their content is covered for all manufacturing operations management categories under operations models.
g) object model was added for the operations segment capability as a collection of resources related to other operations models.
h) updated relationship name and role name conventions established in 3.3.4 and implemented across all models and associated tables.
i) updated all objects’ relationship role table with explicit source and target names.
j) updated common header attributes for objects and property objects established in 4.5 and implemented across all models and associated tables.
k) updated explanation of the ‘relationships between resource reference objects in operations management information models and resource models. These additional resource relationships are added to all operations management models.
l) added an annex explanation for implementation options for specifying values in unit of measurement attribute.
m) added an annex explanation for implementation considerations for inheritance and persistence of data exchange object models.
- Standard474 pagesEnglish languagesale 15% off
- Standard1004 pagesEnglish and French languagesale 15% off
IEC 63430:2025 specifies a container format for sensing data and its system requirements. This document applies to edge computing devices such as smartphones, home gateways, multimedia coordinators, etc., and cloud systems.
This document describes the following technical specifications:
- container format for wearable sensor data;
- Schema Repository that defines the parameters and syntax of sensor data;
- communication and system requirements between the edge computing device and Schema Repository.
- Standard29 pagesEnglish languagee-Library read for1 day
IEC 62351-7:2025 defines network and system management (NSM) data object models that are specific to power system operations. These NSM data objects will be used to monitor the health of networks and systems, to detect possible security intrusions, and to manage the performance and reliability of the information infrastructure. The goal is to define a set of abstract objects that will allow the remote monitoring of the health and condition of IEDs (Intelligent Electronic Devices), RTUs (Remote Terminal Units), DERs (Distributed Energy Resources) systems and other systems that are important to power system operations.
Power systems operations are increasingly reliant on information infrastructures, including communication networks, IEDs, and self-defining communication protocols. Therefore, management of the information infrastructure has become crucial to providing the necessary high levels of security and reliability in power system operations.
The telecommunication infrastructure that is in use for the transport of telecontrol and automation protocols is already subject to health and condition monitoring control, using the concepts developed in the IETF Simple Network Management Protocol (SNMP) standards for network management. However, power system specific devices (like teleprotection, telecontrol, substation automation, synchrophasors, inverters and protections) need instead a specific solution for monitoring their health.
The NSM objects provide monitoring data for IEC protocols used for power systems (IEC 61850, IEC 60870-5-104) and device specific environmental and security status. As a derivative of IEC 60870-5-104, IEEE 1815 DNP3 is also included in the list of monitored protocols. The NSM data objects use the naming conventions developed for IEC 61850, expanded to address NSM issues. For the sake of generality these data objects, and the data types of which they are comprised, are defined as abstract models of data objects.
In addition to the abstract model, in order to allow the integration of the monitoring of power system devices within the NSM environment in this part of IEC 62351, a mapping of objects to the SNMP protocol of Management Information Base (MIBs) is provided.
The objects that are already covered by existing MIBs are not defined here but are expected to be compliant with existing MIB standards. For example protocols including EST, SCEP, RADIUS, LDAP, GDOI are not in scope.
This edition of IEC 62351-7 cancels and replaces IEC 62351-7 published in 2017. This new edition constitutes a technical revision and includes the following significant technical changes with respect to IEC 62351-7:
a) Reviewed and enriched the NSM object data model;
b) UML model adopted for NSM objects description;
c) SNMP protocol MIBs translation included as Code Components
- Standard135 pagesEnglish languagee-Library read for1 day
This document specifies the execution, validation, verification and documentation of a numerical welding simulation within the field of computational welding mechanics (CWM) and performed with a scientific computational tool (SCT).
This document is applicable to the thermal and mechanical finite element analysis (FEA) of arc, laser and electron beam welding processes for the purpose of calculating the effects of welding processes, and in particular, residual stresses and distortion, in support of structural integrity assessment.
- Standard56 pagesEnglish languagee-Library read for1 day
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.
- Standard47 pagesEnglish languagesale 15% off
- Standard49 pagesFrench languagesale 15% off
IEC 61131-2:2017 specifies functional and electromagnetic compatibility requirements and related verification tests for any product where the primary purpose is performing the function of industrial control equipment, including PLC and/or PAC, and/or their associated peripherals which have as their intended use the control and command of machines, automated manufacturing and industrial processes, e.g. discrete, batch and continuous control.
This fourth edition cancels and replaces the third edition published in 2007. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) removal of safety requirements and instead pointing to IEC 61010-2-201;
b) addition of negative logic digital inputs and outputs;
c) addition of Type 3-d digital input;
d) addition of 2,7 GHz to 6 GHz requirement for Radio-frequency electro-magnetic amplitude modulated immunity;
e) clarification of temperature testing;
f) clarification of type testing;
g) deprecation of certain technologies;
h) general update of multiple aspects of functionality and EMC;
i) reorganization of clauses to associate requirements and verifications more closely.
- Standard112 pagesEnglish languagee-Library read for1 day
IEC 61131-2:2017 specifies functional and electromagnetic compatibility requirements and related verification tests for any product where the primary purpose is performing the function of industrial control equipment, including PLC and/or PAC, and/or their associated peripherals which have as their intended use the control and command of machines, automated manufacturing and industrial processes, e.g. discrete, batch and continuous control. This fourth edition cancels and replaces the third edition published in 2007. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) removal of safety requirements and instead pointing to IEC 61010-2-201; b) addition of negative logic digital inputs and outputs; c) addition of Type 3-d digital input; d) addition of 2,7 GHz to 6 GHz requirement for Radio-frequency electro-magnetic amplitude modulated immunity; e) clarification of temperature testing; f) clarification of type testing; g) deprecation of certain technologies; h) general update of multiple aspects of functionality and EMC; i) reorganization of clauses to associate requirements and verifications more closely.
- Standard112 pagesEnglish languagee-Library read for1 day
IEC 62541-18: 2025 defines an Information Model. The Information Model describes the basic infrastructure to model role-based security.
NOTE In the previous version, Role-Based Security was in IEC 62541-5:2020, Annex F.
- Standard34 pagesEnglish languagee-Library read for1 day
IEC 63489:2025 specifies the definition of cross-domain product data concepts (classes and properties) in the context of smart manufacturing.
This document will be published as a set of concepts within cross-domain data dictionary "General Items (IEC 61360-7)” in the IEC CDD.
- Standard13 pagesEnglish languagee-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagee-Library read for1 day
IEC 61131-3:2025 specifies the syntax and semantics of programming languages for programmable controllers as defined in IEC 61131-1.
This document specifies the syntax and semantics of a unified suite of programming languages for programmable controllers (PCs). This suite consists of the textual language structured text (ST), and the graphical languages, ladder diagram (LD) and function block diagram (FBD).
An additional set of graphical and equivalent textual elements named sequential function chart (SFC) is defined for structuring the internal organization of programs and function blocks. Also, configuration elements are defined which support the installation of programmable controller programs into programmable controller systems.
In addition, features are defined which facilitate communication among programmable controllers and other components of automated systems.
This edition includes the following significant technical changes with respect to the previous edition:
a) inclusion of UTF-8 strings and their associated functions;
b) Annex B contains a comprehensive list of features that have been added, removed or deprecated in comparison to IEC 61131-3:2013.
- Standard256 pagesEnglish languagee-Library read for1 day
IEC 61987-41: 2025 provides:
• a characterization for the integration of process analysers in the Common Data Dictionary (CDD),
• generic structures for operating lists of properties (OLOP) and device lists of properties (DLOP) of measuring equipment in conformance with IEC 61987-10,
• generic structures for Dynamic Data, e.g. for condition monitoring of process analysers.
The generic structures for the OLOP and DLOP contain the most important blocks for process analysers. Blocks pertaining to a specific equipment type will be described in the corresponding part of the IEC 61987 standard series. Similarly, equipment properties are not part of this document. Thus, OLOP, DLOPs and LOPDs for selected process analysers families will be found in the IEC CDD.
- Standard25 pagesEnglish languagee-Library read for1 day
IEC 63270-1:2025 provides guidance on the functional structure model, procedure, method, interface of function blocks. It also offers guidance on data requirements for predictive maintenance of equipment, devices and systems for industrial automation applications.
Condition monitoring is not only within the scope of this document but can also be an important input for predictive maintenance.
- Standard47 pagesEnglish languagee-Library read for1 day
This document specifies interface requirements between charging infrastructure with dedicated contact line sections and electric traction units with onboard electric traction energy storages and current collectors.
The dedicated contact line section can be
- separated from other contact line systems of electrified railway lines and fed separately, or
- connected electrically and/or mechanically with contact line systems of electrified railway lines.
The charging infrastructure can be used for charging the traction units with onboard electric traction energy storages at a standstill and/or when moving.
This document covers the following aspects:
- supply voltages and frequencies,
- compatibility (e.g. avoidance of (unacceptable) unbalances) with the feeding grid (national 3 AC grid),
- interaction between the vehicle traction/charging system and the electric traction charging power supply system,
- transmitting required information towards driver and/or electric traction unit,
- contact line system,
- maximum load current,
- contact line protection principles,
- electrical safety,
- stray current protection (in case of DC electric traction power supply systems),
- protection against influence on signalling systems, and
- energy measurement and settlement.
This document applies to new charging infrastructure and/or new electric traction units with onboard electric traction energy storage.
Although this document is primarily applicable to railways it can also be partially applied to guided mass transport systems such as:
1) tramways, and
2) elevated and underground railways.
This document does not apply to charging with a plug or connector solution or inverted current collectors mounted on the infrastructure side.
This document does not apply to electric road systems with overhead contact line systems.
- Technical specification30 pagesEnglish languagee-Library read for1 day
IEC 61131-3:2025 specifies the syntax and semantics of programming languages for programmable controllers as defined in IEC 61131-1. This document specifies the syntax and semantics of a unified suite of programming languages for programmable controllers (PCs). This suite consists of the textual language structured text (ST), and the graphical languages, ladder diagram (LD) and function block diagram (FBD). An additional set of graphical and equivalent textual elements named sequential function chart (SFC) is defined for structuring the internal organization of programs and function blocks. Also, configuration elements are defined which support the installation of programmable controller programs into programmable controller systems. In addition, features are defined which facilitate communication among programmable controllers and other components of automated systems. This edition includes the following significant technical changes with respect to the previous edition: a) inclusion of UTF-8 strings and their associated functions; b) Annex B contains a comprehensive list of features that have been added, removed or deprecated in comparison to IEC 61131-3:2013.
- Standard256 pagesEnglish languagee-Library read for1 day