25.040.01 - Industrial automation systems in general
ICS 25.040.01 Details
Industrial automation systems in general
Industrielle Automatisierungssysteme im allgemeinen
Systemes d'automatisation industrielle en général
Sistemi za avtomatizacijo v industriji na splošno
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 25.040.01 - Industrial automation systems in general
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
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 languagesale 10% offe-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 languagesale 10% offe-Library read for1 day
IEC 62014-4:2025 describes an eXtensible Markup Language (XML) schema for meta-data documenting intellectual property (IP) used in the development, implementation, and verification of electronic systems. This schema provides both a standard method to document IP that is compatible with automated integration techniques and a standard method (generators) for linking tools into a system development framework, enabling a more flexible, optimized development environment. Tools compliant with this standard will be able to interpret, configure, integrate, and manipulate IP blocks that comply with the IP meta-data description. The standard is independent of any specific design processes. It does not cover behavioral characteristics of the IP that are not relevant to integration. This standard enables the creation and exchange of IP in a highly automated design environment.
This standard is published as a double logo IEC-IEEE standard.
- Standard750 pagesEnglish languagesale 15% off
IEC 61967-7:2025 defines SystemC® with Transaction Level Modeling (TLM) as an ISO standard C++ class library for system and hardware design. SystemC®1 as an ANSI standard C++ class library for system and hardware design.
The general purpose of this standard is to provide a C++-based standard for designers and architects who need to address complex systems that are a hybrid between hardware and software. The specific purpose of this standard is to provide a precise and complete definition of the SystemC class library including a TLM library so that a SystemC implementation can be developed with reference to this standard alone. This standard is not intended to serve as a user’s guide or to provide an introduction to SystemC, but it does contain useful information for end users.
The changes with respect to the previous edition are provided in Annex D.
This standard is published as a double logo IEC-IEEE standard.
- Standard618 pagesEnglish languagesale 15% off
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 file format supports the following information: — facet information (triangles), stored with geometry compression techniques; — visual attributes such as lights, textures and materials; — product manufacturing information, such as dimensions, tolerances and other attributes; — boundary representation (b-rep) solid model shape representations. Several alternatives are available, including a representation based on the geometry standard defined in ISO 10303; — configuration representations; — delivery methods such as asynchronous streaming of content. The document does not specify the implementation of, or definition of a run-time architecture for viewing or processing of the file format.
- Standard664 pagesEnglish languagesale 15% off
This document uses a meta-modelling approach to identify commonalities among ten smart manufacturing reference models. Each reference model is placed into the context of the meta-model to facilitate analysis of both common and distinct features. Major smart manufacturing reference model topics are identified, and the reference models compared within each topic. As part of the meta-modelling approach development, a collection of models differing in extent of abstraction characterizes the evolution of a particular smart manufacturing system from the meta-model through a unifying smart manufacturing reference model and successively less abstract domain models to a model for system implementation. This document presents a range of issues and challenges for further work to specify a high-level smart manufacturing reference model that unifies the concepts and practices identified using the meta-model approach analysis of the smart manufacturing reference models.
- Technical report153 pagesEnglish languagesale 15% off
IEC 63206:2024 specifies the characterization, the classification (e.g.: analogue chart recorder, digital recorder, X-Y recorder, paperless recorder, event recorder, data logger, and data acquisition device, etc.) and performance evaluation methods of recorders. It covers type tests as well as routine tests.
This document is applicable to recorder devices and recorder modules for control systems.
IEC 63206 is intended for use by manufacturers to determine the performance of their products and by users or independent testing bodies to verify manufacturers’ performance specifications.
IEC 63206 has fully covered IEC 60873-1 and IEC 60873-2 which are withdrawn.
- Standard42 pagesEnglish languagesale 10% offe-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 languagesale 10% offe-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.
- Standard91 pagesEnglish and French languagesale 15% off
This part of IEC 62443 specifies the evaluation methodology to support interested parties (e.g.
during conformity assessment activities) to achieve repeatable and reproducible evaluation
results against IEC 62443-2-4 requirements. This document is intended for first-party, secondparty
or third-party conformity assessment activity, for example by product suppliers, service
providers, asset owners and conformity assessment bodies.
NOTE 1 62443-2-4 specifies requirements for security capabilities of an IACS service provider. These security
capabilities can be offered as a security program during integration and maintenance of an automation solution.
NOTE 2 The term “conformity assessment” and the terms first-party conformity assessment activity, second-party
conformity assessment activity and third-party conformity assessment activity are defined in ISO/IEC 17000.
- Technical specification135 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63339:2024 specifies the unified reference model for smart manufacturing (URMSM) using a terminology and structure, and establishes criteria for creating reference models, as specializations, that support smart manufacturing. The terminology and structure comprise a set of common modelling elements, their associations, and conformance criteria. These common modelling elements address aspects and perspectives of products and production and their lifecycle considerations.
The URMSM enables an approach for creating multiple models based upon a reference model that is sufficient for understanding significant relationships among entities involved in smart manufacturing (SM) and for the development of standards and other specifications.
The URMSM specifications in this document accommodate consistent, coherent, compatible specializations for relevant aspects of manufacturing systems consisting of equipment, products, and services within the domain of manufacturing. Provisions of this document are applicable for a new smart manufacturing reference model (SMRM) or elaboration of existing SMRM capabilities, for example, improving capabilities for analysis of opportunities and synthesis of technological advances, and improving interoperability of new and existing systems.
This document is not intended to prescribe interoperability considerations or data schemas of models. Standardization of content relative to models will be the subject of other standards and texts specific to those model domains.
- Standard101 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a vocabulary for industrial data that defines generic terms for things that exist in more than one industrial domain. The following are within the scope of this document: — definition of terms for generic types of industrial thing; EXAMPLE 1 Definitions of the terms “material object”, “artefact” and “product” are within the vocabulary. — definition of terms relevant to assemblies, systems and their breakdown structures; — definition of terms relevant to activities and participation in activities; — definition of terms relevant to positions and roles in organizations; — definition of terms relevant to behaviour, capability and function; — definition of terms relevant to state and condition; — definition of terms relevant to specifications, designs and plans; — definition of terms relevant to versions, alternatives and configurations for specifications, designs and plans; — definition of terms relevant to signals and other carriers of information and to devices that process signals and information; — definition of terms relevant to physical quantities and properties. The following are outside the scope of this document: — definition of terms that are relevant to data themselves, rather than the things that data are about; EXAMPLE 2 Definitions of the terms “data” and “information” are not within the vocabulary. — definition of terms that are relevant to representations. EXAMPLE 3 Definitions of the terms “representation” and “model” are not within the vocabulary.
- Technical specification39 pagesEnglish languagesale 15% off
IEC 62443-2-1:2024 specifies asset owner security program (SP) policy and procedure requirements for an industrial automation and control system (IACS) in operation. This document uses the broad definition and scope of what constitutes an IACS as described in IEC TS 62443‑1‑1. In the context of this document, asset owner also includes the operator of the IACS.
This document recognizes that the lifespan of an IACS can exceed twenty years, and that many legacy systems contain hardware and software that are no longer supported. Therefore, the SP for most legacy systems addresses only a subset of the requirements defined in this document. For example, if IACS or component software is no longer supported, security patching requirements cannot be met. Similarly, backup software for many older systems is not available for all components of the IACS. This document does not specify that an IACS has these technical requirements. This document states that the asset owner needs to have policies and procedures around these types of requirements. In the case where an asset owner has legacy systems that do not have the native technical capabilities, compensating security measures can be part of the policies and procedures specified in this document.
This edition includes the following significant technical changes with respect to the previous edition:
a) revised requirement structure into SP elements (SPEs),
b) revised requirements to eliminate duplication of an information security management system (ISMS), and
c) defined a maturity model for evaluating requirements.
- Standard93 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63339:2024 specifies the unified reference model for smart manufacturing (URMSM) using a terminology and structure, and establishes criteria for creating reference models, as specializations, that support smart manufacturing. The terminology and structure comprise a set of common modelling elements, their associations, and conformance criteria. These common modelling elements address aspects and perspectives of products and production and their lifecycle considerations. The URMSM enables an approach for creating multiple models based upon a reference model that is sufficient for understanding significant relationships among entities involved in smart manufacturing (SM) and for the development of standards and other specifications. The URMSM specifications in this document accommodate consistent, coherent, compatible specializations for relevant aspects of manufacturing systems consisting of equipment, products, and services within the domain of manufacturing. Provisions of this document are applicable for a new smart manufacturing reference model (SMRM) or elaboration of existing SMRM capabilities, for example, improving capabilities for analysis of opportunities and synthesis of technological advances, and improving interoperability of new and existing systems. This document is not intended to prescribe interoperability considerations or data schemas of models. Standardization of content relative to models will be the subject of other standards and texts specific to those model domains.
- Draft89 pagesEnglish languagesale 15% off
This document defines a set of environmental performance evaluation (EPE) data classes, including their properties. It is applicable to entire manufacturing facilities or to parts of a manufacturing facility. This document applies to manufacturing systems including discrete, batch and continuous control, which are defined in IEC 62264-1. The following are outside the scope of this document: — syntax of EPE data and data models; — protocols to exchange EPE data; — functions that can be enabled by the use of EPE data; — product life cycle assessment; — EPE data that are specific to a particular industry sector, manufacturer or machinery; — acquisition of EPE data.
- Standard90 pagesEnglish languagesale 15% off
This document defines a set of environmental performance evaluation (EPE) data classes, including their properties.
It is applicable to entire manufacturing facilities or to parts of a manufacturing facility.
This document applies to manufacturing systems including discrete, batch and continuous control, which are defined in IEC 62264-1.
The following are outside the scope of this document:
- syntax of EPE data and data models;
- protocols to exchange EPE data;
- functions that can be enabled by the use of EPE data;
- product life cycle assessment;
- EPE data that are specific to a particular industry sector, manufacturer or machinery;
- acquisition of EPE data.
- Standard90 pagesEnglish languagesale 15% off
This document defines terms relating to the JT file format specification for 3D visualization.
- Standard6 pagesEnglish languagesale 15% off
This document provides an overview and defines the purpose and fundamental principles of the ISO 14306 series as well as the structure of the various parts within the series and an overview of the conformance for files created consistent with the standard. The ISO 14306 series defines a binary file format description that is a representation of product information with the definitions necessary to enable 3D visualization among different computer systems and environments associated with a complete product lifecycle.
- Standard5 pagesEnglish languagesale 15% off
This technical specification identifies the relevant aspects of the IEC 62443 series related to security threats and vulnerabilities that are considered for the design and implementation of safety-related control systems (SCS) which can lead to the loss of the ability to maintain safe operation of a machine.
Typical security aspects related to the machine with potential relation to SCS are:
– vulnerabilities of the SCS either directly or indirectly through the other parts of the machine which can be exploited by security threats that can result in security attacks (security breach);
– influence on the safety characteristics and ability of the SCS to properly perform its function(s);
– typical use case definition and application of a corresponding threat model.
Non-safety-related aspects of security threats and vulnerabilities are not considered in this document.
The focus of this document is on intentional malicious actions. However, intentional hardware manipulation (e.g. wiring, exchange of components) or foreseeable misuse by physical manipulation of SCS (e.g. physical bypass) is not considered in this document.
This document does not cover security requirements for information technology (IT) products and for the design of devices used in the SCS (e.g., product specific standards can be available, such as IEC TS 63208).
- Technical specification33 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the structure of a standardized digital representation of an asset, called Asset Administration Shell. The Asset Administration Shell gives uniform access to information and services.
The purpose of the Asset Administration Shell is to enable two or more software applications to exchange information and to mutually use the information that has been exchanged in a trusted and secure way.
This document focusses on Asset Administration Shells representing assets of manufacturing enterprises including products produced by those enterprises and the full hierarchy of industrial equipment. It defines the related structures, information, and services.
The Asset Administration Shell applies to:
- any type of industrial process (discrete manufacturing, continuous process, batch process, hybrid production);
- any industrial sector applying industrial-process measurement, control and automation;
- the entire life cycle of assets from idea to end of life treatment;
- assets which are physical, digital, or intangible entities.
- Standard76 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62443-2:2023 specifies a comprehensive set of requirements for security-related processes that IACS service providers can offer to the asset owner during integration and maintenance activities of an Automation Solution. Because not all requirements apply to all industry groups and organizations, Subclause 4.1.4 provides for the development of "profiles" that allow for the subsetting of these requirements. Profiles are used to adapt this document to specific environments, including environments not based on an IACS.
NOTE 1 The term "Automation Solution" is used as a proper noun (and therefore capitalized) in this document to prevent confusion with other uses of this term. Collectively, the security processes offered by an IACS service provider are referred to as its Security Program (SP) for IACS asset owners. In a related specification, IEC 62443-2-1 describes requirements for the Security Management System of the asset owner.
NOTE 2 In general, these security capabilities are policy, procedure, practice and personnel related. Figure 1 illustrates the integration and maintenance security processes of the asset owner, service provider(s), and product supplier(s) of an IACS and their relationships to each other and to the Automation Solution. Some of the requirements of this document relating to the safety program are associated with security requirements described in IEC 62443-3-3 and IEC 62443-4-2.
NOTE 3 The IACS is a combination of the Automation Solution and the organizational measures necessary for its design, deployment, operation, and maintenance.
NOTE 4 Maintenance of legacy system with insufficient security technical capabilities, implementation of policies, processes and procedures can be addressed through risk mitigation.
- Standard94 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62529:2024 provides the means to define and describe signals used in testing. It provides a set of common basic signal definitions, built upon formal mathematical specifications, so that signals can be combined to form complex signals usable across all test platforms. The standard provides support for structural textual languages and programming language interfaces for interoperability. This second edition cancels and replaces the first edition, published in 2007, and constitutes a technical revision.
- Standard352 pagesEnglish languagesale 15% off
This document provides requirements and recommendations on how to construct an equipment instance model using an equipment behaviour catalogue (EBC) item.
- Standard24 pagesEnglish languagesale 15% off
This document specifies the functions and the information flows of industrial Facility Energy Management System (FEMS). Generic functions are defined for the FEMS, to enable upgrading traditional Energy Management System (EMS) from visualization of the status of energy consumption to automation of energy management defining a closer relation with other management and control systems. A generic method to classify the FEMS functions will be explained. The information exchange between the FEMS and other systems such as Manufacturing Operations Management (MOM), Manufacturing Execution System (MES) and Enterprise Resource Planning (ERP) will be outlined.
- Standard73 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61523-4:2023 defines the syntax and semantics of a format used to express power intent in energy-aware electronic system design. Power intent includes the concepts and information required for specification and validation, implementation and verification, and modeling and analysis of power-managed electronic systems. This standard also defines the relationship between the power intent captured in this format and design intent captured via other formats (e.g., standard hardware description languages and cell libraries). This is an IEC/IEEE dual logo standard.
- Standard10 pagesEnglish languagesale 15% off
This document specifies a formal structure and building rules for an equipment behaviour catalogue (EBC) template. The formal structure of an EBC template represents a schema for descriptions of behaviour and related entities. Building rules for an EBC template provide required processes and compliance criteria to construct an EBC template.
- Standard50 pagesEnglish languagesale 15% off
IEC 63501-2416:2023 describes a parameterized and abstracted power model enabling system, software, and hardware intellectual property (IP)-centric power analysis and optimization. It defines concepts for the development of parameterized, accurate, efficient, and complete power models for systems and hardware IP blocks usable for system power analysis and optimization. These concepts include, but are not limited to, process, voltage, and temperature (PVT) independence; power and thermal management interface; and workload and architecture parameterization. This standard also defines the necessary requirements for the information content of parameterized, accurate, efficient, and complete power models to help guide development and usage of other related power, workload, and functional modeling standards. This standard is published as a double logo IEC-IEEE standard.
- Standard62 pagesEnglish languagesale 15% off
IEC 63504-2804:2023 defines an architecture description standard from the software design perspective - this provides a common interface that abstracts the hardware properties that are critical to enable multicore tools. The standard includes performance estimation accuracy for complex processors like Very Long Instruction Word (VLIW) core and complex contention scenarios, description of caches to include uncached memory regions and caches for subsets of memories, properties for coarse power consumption estimation, and reusability by separating eXtensible Markup Language (XML) files for processor description and other memory/communication-related information. This is an IEC/IEEE dual logo standard.
- Standard83 pagesEnglish languagesale 15% off
IEC 62530-2:2023 establishes the Universal Verification Methodology (UVM), a set of application programming interfaces (APIs) that defines a base class library (BCL) definition used to develop modular, scalable, and reusable components for functional verification environments. The APIs and BCL are based on the IEEE standard for SystemVerilog, IEEE Std 1800™.1. This is an IEC/IEEE dual logo standard.
- Standard457 pagesEnglish languagesale 15% off
IEC 61523-1:2023 focuses on delay and power calculation for integrated circuit design with support for modeling logical behavior and signal integrity.
The standard specifications covered in this document are as follows:
- Description language for timing and power modeling, called the “delay calculation language” (DCL)
- Software procedural interface (PI) for communications between EDA applications and compiled libraries of DCL descriptions
- Standard file exchange format for parasitic information about the chip design: Standard Parasitic Exchange Format (SPEF)
- Informative usage examples
- Informative notes.
This is an IEC/IEEE dual logo standard.
- Standard640 pagesEnglish languagesale 15% off
IEC 61523-4:2023 defines the syntax and semantics of a format used to express power intent in energy-aware electronic system design. Power intent includes the concepts and information required for specification and validation, implementation and verification, and modeling and analysis of power-managed electronic systems. This standard also defines the relationship between the power intent captured in this format and design intent captured via other formats (e.g., standard hardware description languages and cell libraries). This is an IEC/IEEE dual logo standard.
The contents of the corrigendum 1 (2024-02) have been included in this copy.
- Standard547 pagesEnglish languagesale 15% off
IEC 61691-1-1:2023 defines the syntax and semantics of the VHSIC Hardware Description Language (VHDL). The acronym VHSIC (Very High Speed Integrated Circuits) in the language’s name comes from the U.S. government program that funded early work on the standard. This is an IEC/IEEE dual logo standard.
- Standard672 pagesEnglish languagesale 15% off
IEC SRD 63456:2023 This document proposes external requirements for IT tools dedicated to smart manufacturing, to assist the development of manufacturing systems with international standards through linking reference models, use cases, architecture, and standards.
- Standardization document35 pagesEnglish languagesale 15% off
- Corrigendum5 pagesEnglish languagesale 10% offe-Library read for1 day
- Corrigendum12 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62682:2022 specifies general principles and processes for the management of alarm systems based on controls system and human-machine interfaces (HMI) for facilities in the process industries. It covers all alarms to be presented to the operator through the control system, which includes alarms from basic process control systems, annunciators, packaged systems, and safety instrumented systems.
The practices in this document are applicable to continuous, batch, and discrete processes. There can be differences in implementation to meet the specific needs based on process type.
The primary function within the alarm system is to notify operators of abnormal process conditions or equipment malfunctions and support the response. The alarm systems can include both the basic process control system (BPCS) and the safety instrumented system (SIS), each of which uses measurements of process conditions and logic to generate alarms. Figure 1 illustrates the concepts of alarm and response dataflow through the alarm system. The alarm system also includes a mechanism for communicating the alarm information to the operator via an HMI, usually a computer screen or an annunciator. Additional functions of the alarm system are an alarm and event log, an alarm historian, and the generation of performance metrics for the alarm system. There are external systems that can use the data from the alarm system.
- Standard84 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61636-2:2023 (E) provides the definition of an exchange format, utilizing XML, for exchanging maintenance action information (MAI) associated with the removal, repair, and replacement of system components to maintain/support an operational system. This standard is published as a double log IEC-IEEE standard.
- Standard25 pagesEnglish languagesale 15% off
IEC Corrected Version
- Corrigendum3 pagesFrench languagesale 10% offe-Library read for1 day
IEC 62872-2:2022 presents an IoT application framework for industrial facility demand response energy management (FDREM) for the smart grid, enabling efficient information exchange between industrial facilities using IoT related communication technologies. This document specifies:
- an overview of the price-based demand response program that serves as basic knowledge backbone of the IoT application framework;
- a IoT-based energy management framework which describes involved functional components, as well as their relationships;
- detailed information exchange flows that are indispensable between functional components;
- existing IoT protocols that need to be identified for each protocol layer to support this kind of information exchange;
- communication requirements that guarantee reliable data exchange services for the application framework.
- Standard56 pagesEnglish languagesale 10% offe-Library read for1 day
1.1 General
The IEC 62439 series is applicable to high-availability automation networks based on the Ethernet technology.
This document:
- specifies PRP and HSR as two related redundancy protocols designed to provide seamless recovery in case of single failure of an inter-bridge link or bridge in the network, which are based on the same scheme: parallel transmission of duplicated information;
- specifies the operation of the precision time protocol (PTP) in networks that implement the two redundancy protocols (Annex A);
- specifies PTP profiles with performance suitable for power utilty automation (Annex B) and industrial automation (Annex C);
- includes for better understanding a tutorial (Annex D) on the PTP features effectively used in high-availability automation networks;
- includes a management information base for PTP (Annex E);
- defines a conformance test suite for the above protocols (Annex F).
1.2 Code component distribution
This document is associated with Code components. Each Code Component is a ZIP package containing at least the electronic representation of the Code Component itself and a file describing the content of the package (IECManifest.xml).
The IECManifest contains different sections giving information on:
- the copyright notice;
- the identification of the code component;
- the publication related to the code component;
- the list of the electronic files which compose the code component;
- an optional list of history files to track changes during the evolution process of the code component.
The Code Components associated with this IEC standard are a set of SNMP MIBs. The Code Component IEC-62439-3-MIB.mib is a file containing the MIBs for PRP/HSR and PTP_SNMP. It is available in a full version, which contains the MIBs defined in this document with the documentation associated and access is restricted to purchaser of this document.
The Code Components are freely accessible on the IEC website for download at: https://www.iec.ch/sc65c/supportingdocuments/IEC_62439-3.MIB.{VersionStateInfo}.full.zip but the usage remains under the licensing conditions.
- Standard249 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62439-2:2021 is applicable to high-availability automation networks based on the ISO/IEC/IEEE 8802-3 (IEEE Std 802.3) (Ethernet) technology.
The IEC 62439-2:2021 specifies a recovery protocol based on a ring topology, designed to react deterministically on a single failure of an inter-switch link or switch in the network, under the control of a dedicated media redundancy manager node.
- Standard178 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a technology independent model for a set of abstract services that is
located above the application layer of the OSI model, and that is used for exchanging
transaction messages based on the transaction models defined in IEC 62264-5. The model,
which is called the Messaging Service Model (MSM), is intended for interoperability between
manufacturing operations domain applications and applications in other domains.
NOTE It is recognized that other sets of services not defined in accordance with this document are possible for the
exchange of MOM information and are not deemed invalid as a result of this document.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
Engineering processes of technical systems and their embedded automation systems have to be executed with increasing efficiency and quality. Especially since the project duration tends to increase as the complexity of the engineered system increases. To solve this problem, the engineering process is more often being executed by exploiting software based engineering tools exchanging engineering information and artefacts along the engineering process related tool chain. Communication systems establish an important part of modern technical systems and, especially, of automation systems embedded within them. Following the increasing decentralisation of automation systems and the application of fieldbus and Ethernet technology connecting automation devices and further interacting entities have to fulfil special requirements on communication quality, safety and security. Thus, within the engineering process of modern technical systems, engineering information and artefacts relating to communication systems also have to be exchanged along the engineering process tool chain. In each phase of the engineering process of technical systems, communication system related information can be created which can be consumed in later engineering phases. A typical application case is the creation of configuration information for communication components of automation devices including communication addresses and communication package structuring within controller programming devices during the control programming phase and its use in a device configuration tool. Another typical application case is the transmission of communication device configurations to virtual commissioning tools, to documentation tools, or to diagnosis tools. At present, the consistent and lossless transfer of communication system engineering information along the complete engineering chain of technical systems is unsolved. While user organisations and companies have provided data exchange formats for parts of the relevant information like FDCML, EDDL, and GSD the above named application cases cannot be covered by a data exchange format. Notably the networking related information describing communication relations and their properties and qualities cannot be modelled by a data exchange format.
- Standard58 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62714-5:2022 Engineering processes of technical systems and their embedded automation systems are executed with increasing efficiency and quality. Especially since the project duration tends to increase as the complexity of the engineered system increases. To solve this problem, the engineering process is more often being executed by exploiting software based engineering tools exchanging engineering information and artefacts along the engineering process related tool chain.
- Standard112 pagesEnglish and French languagesale 15% off
This document lists smart manufacturing related standards with their characteristics as specified in ISO/IEC TR 63306-1.
- Technical report9 pagesEnglish languagesale 15% off
ISO/IEC TR 63306-2:2021 lists smart manufacturing related standards with their characteristics as specified in ISO/IEC TR 63306-1.
- Technical report9 pagesEnglish languagesale 15% off
IEC 62530:2021(E) provides the definition of the language syntax and semantics for the IEEE 1800™ SystemVerilog language, which is a unified hardware design, specification, and verification language. The standard includes support for behavioral, register transfer level (RTL), and gate-level hardware descriptions; testbench, coverage, assertion, object-oriented, and constrained random constructs; and also provides application programming interfaces (APIs) to foreign programming languages.
This edition corrects errors and clarifies aspects of the language definition in IEEE Std 1800-2012.1 This revision also provides enhanced features that ease design, improve verification, and enhance cross-language interactions.
This publication has the status of a double logo IEEE/IEC standard.
- Standard1315 pagesEnglish languagesale 15% off
IEC 62530-2:2021(E) establishes the Universal Verification Methodology (UVM), a set of application programming
interfaces (APIs) that defines a base class library (BCL) definition used to develop modular, scalable, and reusable components for functional verification environments. The APIs and BCL are based on the IEEE standard for SystemVerilog, IEEE Std 1800™. This publication has the status of a double logo IEC/IEEE standard.
- Standard471 pagesEnglish languagesale 15% off
IEC 61691-8:2021(E) defines the Analog/Mixed-Signal extensions for SystemC®, as an ANSI standard C++ class
library based on SystemC for system and hardware design including analog/mixed-signal elements. The general purpose of the SystemC AMS extensions is to provide a C++ standard for designers and architects, who need to address complex heterogeneous systems that are a hybrid between hardware and software. This standard is built on the IEEE Std 1666™-2011 (SystemC Language Reference Manual) and extends it to create analog/mixed-signal, multi-disciplinary models to simulate continuous-time, discrete-time, and discrete-event behavior simultaneously.
This standard is published as a double logo IEC-IEEE standard.
- Standard221 pagesEnglish languagesale 15% off
IEC 61636:2021 (E) is an implementation-independent specification for a software interface to information systems containing data pertinent to the diagnosis and maintenance of complex systems consisting of hardware, software, or any combination thereof. These interfaces support service definitions for creating application programming interfaces (API) for the access, exchange, and analysis of historical diagnostic and maintenance information. This standard is published as a double logo IEC-IEEE standard.
- Standard45 pagesEnglish languagesale 15% off