IEC 62769-6 pdf – Field device integration (FDI) – Part 6: Technology Mapping
1 scope
This part of lEC 62769 specifies the technology mapping for the concepts described in theField Device Integration (FDl) standard. The technology mapping focuses on implementationregarding the components FDI Client and User Interface Plug-in(UiP) that are specific only to
the WORKSTATION platform/.NET as defined in lEC 62769-4.
2Normative 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. Forundated’references, the latest edition of the referenced document(includinganyamendments) applies.
IEC 61804(all parts)，Function blocks (FB) for process control and Electronic DeviceDescription Language (EDDL)
IEC 62769-1，Field Device lntegration (FDI) – Part 1: OverviewIEC 62769-2，Field Device Integration(FDl) – Part 2: FDI ClientIEC 62769-4，Field Device Integration (FDI) – Part 4: FDI PackagesIEC 62541(all parts),OPC Unified Architecture
ISO/IEC 19505-1,Information technology – Object Management Group Unified ModelingLanguage (OMG UML) – Part 1: Infrastructure
ISOIEC 29500，(all parts)Information technology – Document description and processinglanguages – 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 lEC 62769-1 as well asthe following apply.
ISO and IEC maintain terminological databases for use in standardization at the followingaddresses:
·IEC Electropedia: available at http://www.electropedia.orgl
.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 andinteraction between a UIPand an FDI Client
3.1.3
Global Assembly Cache
machine-wide code cache that stores Assemblies specifically designated to be shared byseveral applications
3.1.4
Windows Registry
system-defined database in which applications and system components store and retrieveconfiguration data
3.2Abbreviated terms
For the purposes of this document, the abbreviated terms given in lEC 62769-1 as well as thefollowing apply.
CLRCommon Language Run-timeMSI Microsoft lnstaller
wPF Windows Presentation FoundationUML
Unified Modeling Language
3.3Symbols
Figures in this document use graphical symbols in accordance with ISOIEC19505-1(UML 2.0).
3.4Conventions
For the purposes of this document, the conventions given in lEC 62769-1 apply.
The description of Non-blocking service execution in 4.8.2 uses italics to identify a genericoperation name the internal function is being applied to.
4Technical concepts
4.1General
4.1.1overview
Iln 4.1.2，4.2，4.3，4.4, and 4.5, this document describes first the technology base for uIPimplementation, the hardware and software environment including the related implementationrules.Clause 4 follows a life-cycle (use case) oriented approach.
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.3FDI Type Library
The Device Access Services and the UlP Services can be modelled as .NET interfacespassing .NET data type arguments. These interfaces and data types are used for the dataexchange and interaction between the UlP and the FDl Client. For runtime error handlingpurposes during interface method calls,.NET exceptions classes are defined.
The FDI .NET interfaces, data types, and exception classes are defined in a single FDlTypeLibrary. The FDl Type Library is a strong-named Assembly. The file name of this Assemblyshall be ‘fdi.dll”. The fdi.dl shall be versioned as per lEC 62769-1:2020,8.1.The FDl TypeLibrary is part of the FDl Core Technology as per IEC 62769-1:2020, 8.3.2.1 and thereforedirectly influences the FDl Technology Version. All Compatible changes of the fdi.dll lead toan increase of the minor portion of the FDl Technology Version. Incompatible changes lead to an increase of the major portion of the FDl Technology Version (see IEc 62769-1:2020,8.3.2.2).
The FDl Type Library is signed with a single unique key by the issuer of the file. The FDl Type
Library shall be installed separately as part of every FDl Client installation. User InterfacePlug-Ins (UIP) and the FDI Client Application shall use this instance of the fdi.dl. UIPs shallnot carry or deploy the FDl Type Library. The FDI Client is responsible to provide means toallow updates of this type library over time.
Figure 1 shows the FDI Type Library structure.