IEC 62769-6:2021 pdf download

IEC 62769-6:2021 pdf download.Field device integration (FDI) – Part 6: Technology Mapping
1 Scope
This part of IEC 62769 specifies the technology mapping for the concepts described in the Field Device Integration (FDI) standard. The technology mapping focuses on implementation regarding the components FDI Client and User Interface Plug-in (UIP) that are specific only to the WORKSTATION platform/.NET as defined in IEC 62769-4.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device Description Language (EDDL)
IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
IEC 62541 (all parts), OPC Unified Architecture
ISO/IEC 19505-1, Information technology – Object Management Group Unified Modeling Language (OMG UML) – Part 1: Infrastructure
ISO/IEC 29500, (all parts) Information technology – Document description and processing languages – Office Open XML File Formats
3 Terms, definitions, abbreviated terms, symbols and conventions
3.1 Terms and definitions  For the purposes of this document, the terms and definitions given in IEC 62769-1 as well as the following apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC Electropedia: available at http://www.electropedia.org/ ISO Online browsing platform: available at http://www.iso.org/obp 3.1.1 Application Domain isolated environment where applications execute 3.1.2 FDI Type Library assembly that contains the interfaces and data types that are used for the data exchange and interaction between a UIP and an FDI Client 3.1.3 Global Assembly Cache machine-wide code cache that stores Assemblies specifically designated to be shared by several applications 3.1.4 Windows Registry system-defined database in which applications and system components store and retrieve configuration data 3.3 Symbols Figures in this document use graphical symbols in accordance with ISO/IEC 19505-1 (UML 2.0). 3.4 Conventions For the purposes of this document, the conventions given in IEC 62769-1 apply. The description of Non-blocking service execution in 4.8.2 uses italics to identify a generic operation name the internal function is being applied to.
4 Technical concepts
4.1 General  4.1.1 Overview In 4.1.2, 4.2, 4.3, 4.4, and 4.5, this document describes first the technology base for UIP implementation, the hardware and software environment including the related implementation rules. Clause 4 follows a life-cycle (use case) oriented approach. Subclause 4.6 describes the copy deployment procedures and related implementation rules for the UIP and the FDI Client. UIP executable instantiation and termination is described in 4.7. Subclause 4.8 defines the rules about interaction between the FDI Client and the UIP. Security related definitions are written in 4.9. The service interface definitions for the FDI Client and the UIP are found in Clause 5.4.1.2 Platforms The UIP and FDI Client shall be built upon the Microsoft .NET Framework and executed in the .NET Common Language Run-time. The minimum set of workstation-supported I/O devices is: mouse, keyboard, and color screen resolution of 1024 × 768 pixels. The following Table 1 lists all the technologies and their editions that are consistent with FDI components.4.1.3 FDI Type Library The Device Access Services and the UIP Services can be modelled as .NET interfaces passing .NET data type arguments. These interfaces and data types are used for the data exchange and interaction between the UIP and the FDI Client. For runtime error handling purposes during interface method calls, .NET exceptions classes are defined. The FDI .NET interfaces, data types, and exception classes are defined in a single FDI Type Library. The FDI Type Library is a strong-named Assembly. The file name of this Assembly shall be ‘fdi.dll’. The fdi.dll shall be versioned as per IEC 62769-1:2020, 8.1. The FDI Type Library is part of the FDI Core Technology as per IEC 62769-1:2020, 8.3.2.1 and therefore directly influences the FDI Technology Version. All Compatible changes of the fdi.dll lead to an increase of the minor portion of the FDI Technology Version. Incompatible changes lead to an increase of the major portion of the FDI Technology Version (see IEC 62769-1:2020, 8.3.2.2). The FDI Type Library is signed with a single unique key by the issuer of the file. The FDI Type Library shall be installed separately as part of every FDI Client installation. User Interface Plug-Ins (UIP) and the FDI Client Application shall use this instance of the fdi.dll. UIPs shall not carry or deploy the FDI Type Library. The FDI Client is responsible to provide means to allow updates of this type library over time. Figure 1 shows the FDI Type Library structure.