IEC 62769-6-2021 Field device integration (FDI) – Part 6: Technology Mapping.
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 1 024 × 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, 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,
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.
4.2 UIP representation
The UIP Variant can contain either a single or multiple runtime modules (.NET Assembly) and their related supplementary files (for example: resource files). The runtime module of the UIP
Variant is called “UIP executable”. The supplementary file(s) of the UIP Variant is/are called “UIP supplement(s)”.
UIP supplement(s) is/are stored under (a) subfolder(s) of the UIP executable installation directory.
EXAMPLE Resource files and application configuration data.
The RuntimeId of a UIP Variant shall be “.NET Framework CLR4”, see IEC 62769-4. FDI Clients supporting this RuntimeId shall support the .NET Framework 4.6.1 or higher using the CLR4 and UIPs with this RuntimeId shall use the .NET Framework 4.6.1 or lower supporting the CLR4 (meaning .NET Framework 4.0 up to .NET Framework 4.6.1 ).
The UIP Variant shall be self-contained. All UIP required libraries (.NET Assemblies) required by a UIP Variant are stored within the same Folder.IEC 62769-6 pdf download.