IEC/TC 65 - IEC_TC_65

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.

IEC 62382:2024 defines procedures and specifications for loop check, which comprises the activities between the completion of the loop construction (including installation and point-to-point checks) and the beginning of cold commissioning. This document is applicable for the construction of new plants and for expansion or retrofits (i.e. revamping) of electrical and instrument (E&I) installations in existing plants (including PLC, DCS, panel-mounted and field instrumentation). It does not include a detailed checkout of power distribution systems, except as they relate to the loops being checked (i.e. a motor starter or a power supply to a four-wire transmitter). Loop checks can be performed throughout the lifecycle of the plant. This document is also applicable when loop checks are performed after commissioning. This document describes what is intended to be tested but not how the test is performed, due to the wide range of technologies and equipment available. The intent of this document is to provide a means for all parties, including the owner, the installer and the vendor, to clearly establish and agree on the scope of activities and responsibilities involved in performing these tests in order to achieve a timely delivery and acceptance of the automation system. The activities described in this document can be taken as a guideline and adapted to the specific requirements of the process, plant or equipment. This edition includes the following significant technical changes with respect to the previous edition: a) general re-organization of the content of the previous edition, moving informative content to the annexes; b) replacing the forms based on I/O type in IEC 62382:2012, Annex A to Annex E with an example of a generic loop check form; c) providing additional references to other applicable standards.

IEC 63303:2024 defines general structures and functions of HMI systems. An HMI life cycle example for HMI systems is included. This document specifies requirements and recommendations for activities in each stage of the life cycle including designing, using, and maintaining the HMI system. It also provides requirements and recommendations for functions and performance of HMI systems. The requirements and recommendations in this document are applicable to any controlled process using an HMI to interface to a control system. There can be differences in implementation to meet the specific needs based on the application and controlled process type.

IEC 63082-2:2024 specifies requirements and recommendations for establishing and maintaining intelligent device management (IDM) as outlined in IEC TR 63082-1 in an enterprise having one or more facilities. The following topics are included in the scope of this document: - optimizing functionality and performance of intelligent devices for their use; - managing information related to IDM; - integrating intelligent devices into industrial automation and control systems (IACS) in facilities; - exchanging information between stakeholders that achieve and sustain IDM; - coordinating multiple asynchronous IDM life cycles. The following topics are outside the scope of this document: - defining and determining the function and performance of intelligent devices; - defining and specifying technologies and tools that provide, preserve and manage information related to IDM such as FDT, FDI, portable on-line and off-line tools, configuration tools, historians, and maintenance planning tools; - defining and specifying technologies and tools that are used to design intelligent devices; - defining and specifying communication network architecture, communication technologies, cybersecurity requirements, and network management requirements.

IEC 62381:2024 defines requirements and checklists for the factory acceptance test (FAT), the factory integration test (FIT), the site acceptance test (SAT), and the site integration test (SIT). These tests are carried out to demonstrate that the automation system meets the requirements of the applicable specification. This document provides a means for all parties, including the owner, the buyer, and the vendor, to clearly establish and agree on the scope of activities and responsibilities involved in performing these tests in order to achieve a timely delivery and acceptance of the automation system. The activities specified in this document can be used to develop test plans adapted to the specific requirements of the process/plant/equipment. The annexes of this document contain checklists which are available for consideration when preparing specific test procedures and documentation for a specific automation system. This edition includes the following significant technical changes with respect to the previous edition: a) General re-organization of the standard; b) Current technology incorporated; c) Optional factory integration test (FIT) added; d) Replaced the forms in the annexes with detailed checklists of activities which can be used to develop project-specific test plans; and e) Provided additional references to other applicable standards.

IEC 61987-32:2024 This part of IEC 61987 provides an operating list of properties (OLOP) for the description of the operating parameters and the collection of requirements for I/O modules and a device list of properties (DLOP) for the description of a range of I/O module types. The structures of the OLOP and the DLOPs correspond to the general structures defined in IEC 61987-11 and agree with the fundamentals for the construction of LOPs defined in IEC 61987-10. Aspects other than the OLOP, needed in different electronic data exchange processes and described in IEC 61987-10 and IEC 61987-11, are published in IEC 61987-92. The locations of the libraries of properties and of blocks used in the LOPs concerned are listed in Annex C and Annex D.

IEC 61406-2:2024 complements IEC 61406-1 by providing additional requirements for those cases where data elements are encoded within the Structured Identification Link string with standardized syntax and semantics. In addition, this document covers cases where the uniqueness relates to product types/models or lots/batches. The default assumption is that the Identification Link identifies unique objects such as unique serialized products, assets, persons or packages, unless otherwise identified.

IEC 61784-5-19:2024 is available as IEC 61784-5-19:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 61784-5-19:2024 specifies the installation profile for CPF 19 (MECHATROLINKTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024. [1] MECHATROLINKTM and Σ-LINKTM II are trade names of YASKAWA ELECTRIC CORPORATION. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade names holder or any of its products. Compliance to this profile does not require use of the trade names. Use of the trade name requires permission of the trade name holder.

IEC 61784-5-8:2024 is available as IEC 61784-5-8:2024 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 61784-5-8:2024 specifies the installation profiles for CPF 8 (CC-LinkTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024. [1] CC-Link™, CC-Link/LT™ and CC‑Link IE™ are trade names of Mitsubishi Electric Co., control of trade name use is given to CCLink Partner Association. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 61784-5-22:2024 specifies the installation profile for CPF 22 (AUTBUSTM [1]). The installation profile is specified in Annex A. This annex is read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024. [1] AUTBUSTM is the trade name of the Kyland Technology Co., Ltd. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of Kyland Technology Co., Ltd.

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.

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.

Communication Profile Family 2 (commonly known as CIPTM1) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNetTM2), CP 2/2 (EtherNet/IPTM3), and CP 2/3 (DeviceNetTM1) are defined in IEC 61784-1 and IEC 61784-2. An additional communication profile (CompoNetTM1), also based on CIPTM, is defined in [15]. This part of IEC 62453 provides information for integrating the CIPTM technology into the FDT interface specification (IEC 62453-2). This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it.

IEC 62453-71:2023 specifies an OPC UA Information Model to represent the device information based on FDT-defined device integration.

IEC 61139-3:2023 specifies a wireless single-drop digital communication interface (SDCI wireless). This is an extension to the single-drop digital communication interface (SDCI) technology that is specified in IEC 61131-9. This document specifies the wireless communication services and protocol (physical layer, data link layer and application layer in accordance with the ISO/OSI reference model) for W‑Masters and W‑Devices. NOTE This document does not cover the integration into higher level systems such as fieldbuses.

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.

IEC 60534-1:2023 is available as IEC 60534-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 60534-1:2023 applies to all types of industrial-process control valves (hereinafter referred to as control valves). This document establishes a partial basic terminology list and provides guidance on the use of all other parts of IEC 60534.

IEC 61784-2 (all parts) defines additional Communication Profiles (CPs) for the existing Communication Profile Families (CPFs) of IEC 61784-1 (all parts) and additional CPFs with one or more CPs. These additional CPs are based on the IEC 61158 series, IEC 61784-1 (all parts) and use provisions from ISO/IEC/IEEE 8802-3 (commonly known as Ethernet) for the lower communication stack layers. These Real-Time Ethernet (RTE) communication profiles provide Real-Time Ethernet communication solutions able to coexist with ISO/IEC/IEEE 8802-3 based applications. NOTE 1 All CPs are based on standards or draft standards or International Standards published by the IEC or from standards or International Standards established by other standards bodies or open standards processes. NOTE 2 The RTE communication profiles use ISO/IEC/IEEE 8802-3 communication networks and its related network components or IEC 61588 and may in some cases amend those standards to obtain RTE features. This document defines: - a common terminology for all CPFs in IEC 61784-2 (all parts) (see 3.1 to 3.3); - conventions to be used in the specification of the RTE communication profiles (see 3.4); - how conformance of a device to a CPF or a CP should be stated (see Clause 4). This document also specifies: - basic principles of performance indicators expressing RTE performance of a CP (see 5.1); - how an application-dependent class could be used to find out a suitable CP to meet application requirements (see 5.2); - characteristics of RTE performance indicators (see 5.3); - the methodology of a conformance test for an RTE end device for one or more CPs (see Clause 6).

IEC 62769-6-200:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) for the Runtime HTML5. [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-6-100:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) using the Runtime .NET. This runtime is specific only to the WORKSTATION platform as defined in IEC 62769‑4. [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-102-2:2023 defines the protocol-specific definitions (PSDs) as defined in IEC 62769‑100 (annex on generic protocol extensions) for the Ethernet/IP protocol.

IEC 62769-101-1:2023 is available as IEC 62769-101-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62769-101-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784‑1_CP 1/1 (Foundation™ Fieldbus H1)[2]. [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder. [2] Foundation™ Fieldbus is the trade name of the non-profit consortium Fieldbus Foundation. This information is given for the convenience of users of this standard and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-101-2:2023 is available as IEC 62769-101-2:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-101-2:2023 specifies the IEC 62769 profile for IEC 61784‑1, CP 1/2 (Foundation™ Fieldbus HSE)[1]. [1] Foundation™ Fieldbus is the trade name of the non-profit consortium Fieldbus Foundation. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-150-1:2023 is available as IEC 62769-150-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-150-1:2023 specifies an FDI profile of IEC 62769 for IEC 62734 (ISA100.11a)[1]. [1] ISA100 WIRELESSTM is a trade name of the non-profit consortium Wireless Compliance Institute. This information is given for the convenience of users of this standard and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-103-4:2023 is available as IEC 62769-103-4:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-103-4:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784-2_CP 3/4, IEC 61784-2_CP3/5 and IEC 61784-2_CP3/6 (PROFINET[2]). [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder. [2] PROFINET is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-103-1:2023 is available as IEC 62769-103-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-103-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784-1_CP 3/1 (PROFIBUS DP)[2] and IEC 61784-1_CP3/2 (PROFIBUS PA). [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder. [2] PROFIBUS is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-109-1:2023 is available as IEC 62769-109-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62769-109-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784‑1_CP 9/1 (HART®)[2] and IEC 61784‑1_CP 9/2 (WirelessHART®)[3]. [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder. [2] HART is the trade name of the non-profit consortium FieldComm Group. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder. [3] WirelessHART is the trade name of the non-profit consortium FieldComm Group. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-151-1:2023 defines the protocol-specific definitions (PSDs) as defined in IEC 62769‑7 for the OPC UA protocol.

IEC 62769-8:2023 specifies how the internal view of a device model represented by the EDD can be transferred into an external view as an OPC-UA information model by mapping EDD constructs to OPC-UA objects.

IEC 62769-4:2023 is available as IEC 62769-4:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-4:2023 specifies the FDI®[1] Packages. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in Architecture diagram figure. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-7:2023 is available as IEC 62769-7:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-7:2023 specifies the elements implementing communication capabilities called Communication Devices. The overall FDI®[1] architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this illustration. The document scope with respect to FDI® Packages is limited to Communication Devices. The Communication Server shown in Figure 1 is an example of a specific Communication Device. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-5:2023 is available as IEC 62769-5:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-5:2023 defines the FDI®[1] Information Model. One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore, it represents the devices of the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them. The types in the AddressSpace of the FDI® Server constitute some kind of catalogue, which is built from FDI® Packages. The fundamental types for the FDI® Information Model are well defined in OPC UA for Devices (IEC 62541‑100). The FDI® Information Model specifies extensions for a few special cases and otherwise explains how these types are used and how the contents are built from elements of DevicePackages. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-100:2023 is available as IEC 62769-100:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-100:2023 specifies an FDI®[1] profile of IEC 62769 for Generic Protocols. That means that all interfaces are defined and a host can add support for more protocols without changing its implementation. Nevertheless, there are some protocol specific definitions (PSD) that need to be specified per protocol using this profile. Annex C specifies what PSD need to be defined per protocol so that FDI® Device Packages, FDI® Communication Packages for Gateways and FDI® Communication Servers, FDI® Communication Server, Gateways and Devices supporting such a protocol can work together in a host not aware about this specific protocol.

IEC 62769-6:2023 is available as IEC 62769-6:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-6:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation of the components FDI® Client and User Interface Plug-in (UIP) in the specified technologies for the WORKSTATION platform and the MOBILE platform as defined in IEC 62769-4. There are individual subparts for the currently supported technologies .NET and HTML5.

IEC 62769-3:2023 is available as IEC 62769-3:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-3:2023 specifies the FDI®[1] Server. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this figure. Annex A provides a functional description of the FDI® Server. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-2:2023 is available as IEC 62769-2:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62769-2:2023 specifies the FDI®[1] Client. See Annex C for some typical FDI® Client use cases. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in Figure 1. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-1:2023 is available as IEC 62769-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62769-1:2023 describes the concepts and overview of the Field Device Integration (FDI®[1]) specifications. The detailed motivation for the creation of this technology is also described . Reading this document is helpful to understand the other parts of this multi-part standard. [1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 61158-6-28:2023 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 28 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window can cause failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.

IEC 61784-1 (all parts) defines several Communication Profile Families (CPF). Each CPF specifies a set of protocol specific communication profiles (CPs) based primarily on the IEC 61158 series, to be used in the design of devices involved in communications in factory manufacturing and process control. This document defines a common terminology for all CPFs and conventions to be used in the specification of the CPs. It also provides a conformance statement and an overview of the structure and contents of the CPFs in IEC 61784-1 (all parts).

1.1 General The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs." This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). 1.2 Specifications The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-2. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. 1.3 Conformance This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.

1.1 General The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs." This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 27 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service, c) the parameters associated with each primitive action and event, and the form which they take, and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this International Standard is to define the services provided to a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This International Standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 289 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this International Standard to provide access to the FAL to control certain aspects of its operation. 1.2 Specifications [...] 1.3 Conformance [...]

IEC 61558-5-28:2023 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 28 fieldbus. The term "time-critical" is used to represent the presence of a time-window, in which one or more specified actions are required to be completed with some defined level of certainty.

1.1 General The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs." This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible service provided by the Type 2 fieldbus application layer in terms of: a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this document is to define the services provided to: a) the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and b) Systems Management at the boundary between the application layer and Systems Management of the fieldbus reference model. This document specifies the structure and services of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented application service elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 318 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation. 1.2 Specifications [...] 1.3 Conformance [...]

IEC 61158-1:2023 specifies the generic concept of fieldbuses. This document also presents an overview and guidance for the IEC 61158 eries by: explaining the structure and content of the IEC 61158 series; relating the structure of the IEC 61158 series to the ISO/IEC 7498-1 OSI Basic Reference Model; showing the logical structure of the IEC 61784 series; showing how to use parts of the IEC 61158 series in combination with the IEC 61784 series; providing explanations of some aspects of the IEC 61158 series that are common to the type specific parts of the IEC 61158‑5 series including the application layer service description concepts and the generic fieldbus data types.

This document defines Communication Profile Family 22 (CPF 22). CPF 22 specifies a protocol specific communication profile (CP) based on the IEC 61158 series (Type 28) and other standards, to be used in the design of devices involved in communications in factory manufacturing and process control. NOTE All CPs are based on standards or draft standards or International Standards published by the IEC or from standards or International Standards established by other standards bodies or open standards processes. Each CP selects an appropriate consistent and compatible subset of services and protocols from the relevant set that is defined and modelled in the IEC 61158 series. For the selected subset of services and protocols, the profile also describes any possible or necessary constraints in parameter values.

IEC 61158-5-27:2023 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 27 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.

IEC 61158-3-2:2023 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the "three-layer" fieldbus reference model described in IEC 61158‑1. Throughout the set of fieldbus standards, the term "service" refers to the abstract capability provided by one layer of the OSI Basic Reference Model to the layer immediately above. Thus, the data-link layer service defined in this document is a conceptual architectural service, independent of administrative and implementation divisions.