IEC 62769-6:2021
(Main)Field Device Integration (FDI) - Part 6: Technology Mapping
Field Device Integration (FDI) - Part 6: Technology Mapping
IEC 62769-6:2021 is available as IEC 62769-6:2021 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:2021 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.
Intégration des appareils de terrain (FDI) - Partie 6: Mapping de technologies
IEC 62769-6:2021 est disponible sous forme de IEC 62769-6:2021 RLV qui contient la Norme internationale et sa version Redline, illustrant les modifications du contenu technique depuis l'édition précédente .
L'IEC 62769-6:2021 spécifie le mapping de technologies pour les concepts décrits dans la norme d'intégration des appareils de terrain (FDI). Le mapping de technologies porte essentiellement sur la mise en œuvre relative aux composants: Client FDI et Plugiciel d'Interface Utilisateur (UIP) qui ne sont spécifiques qu'à la plate-forme WORKSTATION (Poste de travail)/.NET telle que définie dans l'IEC 62769-4.
General Information
Standards Content (sample)
IEC 62769-6
Edition 2.0 2021-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device integration (FDI) –
Part 6: Technology Mapping
Intégration des appareils de terrain (FDI) –
Partie 6: Mapping de technologies
IEC 62769-6:2021-02(en-fr)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2021 IEC, Geneva, Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.
IEC Central Office Tel.: +41 22 919 02 113, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.IEC publications search - webstore.iec.ch/advsearchform IEC online collection - oc.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always
committee, …). It also gives information on projects, replaced have access to up to date content tailored to your needs.
and withdrawn publications.Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 000 terminological entries in English
details all new publications released. Available online and
and French, with equivalent terms in 18 additional languages.
once a month by email.
Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or
need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.
A propos des publications IECLe contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.Recherche de publications IEC - IEC online collection - oc.iec.ch
webstore.iec.ch/advsearchform Découvrez notre puissant moteur de recherche et consultez
La recherche avancée permet de trouver des publications IEC gratuitement tous les aperçus des publications. Avec un
en utilisant différents critères (numéro de référence, texte, abonnement, vous aurez toujours accès à un contenu à jour
comité d’études, …). Elle donne aussi des informations sur adapté à vos besoins.les projets et les publications remplacées ou retirées.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
Le premier dictionnaire d'électrotechnologie en ligne au
Restez informé sur les nouvelles publications IEC. Just
monde, avec plus de 22 000 articles terminologiques en
Published détaille les nouvelles publications parues.
anglais et en français, ainsi que les termes équivalents dans
Disponible en ligne et une fois par mois par email.
16 langues additionnelles. Egalement appelé Vocabulaire
Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc
Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
---------------------- Page: 2 ----------------------
IEC 62769-6
Edition 2.0 2021-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device integration (FDI) –
Part 6: Technology Mapping
Intégration des appareils de terrain (FDI) –
Partie 6: Mapping de technologies
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-9312-6
Warning! Make sure that you obtained this publication from an authorized distributor.
Attention! Veuillez vous assurer que vous avez obtenu cette publication via un distributeur agréé.
® Registered trademark of the International Electrotechnical CommissionMarque déposée de la Commission Electrotechnique Internationale
---------------------- Page: 3 ----------------------
– 2 – IEC 62769-6:2021 © IEC 2021
CONTENTS
FOREWORD ........................................................................................................................... 4
INTRODUCTION ..................................................................................................................... 6
1 Scope .............................................................................................................................. 7
2 Normative references ...................................................................................................... 7
3 Terms, definitions, abbreviated terms, symbols and conventions ..................................... 7
3.1 Terms and definitions .............................................................................................. 7
3.2 Abbreviated terms ................................................................................................... 8
3.3 Symbols .................................................................................................................. 8
3.4 Conventions ............................................................................................................ 8
4 Technical concepts .......................................................................................................... 8
4.1 General ................................................................................................................... 8
4.1.1 Overview ......................................................................................................... 8
4.1.2 Platforms ......................................................................................................... 9
4.1.3 FDI Type Library .............................................................................................. 9
4.2 UIP representation ................................................................................................ 10
4.3 UIP executable representation .............................................................................. 11
4.4 UIP executable compatibility rules ........................................................................ 11
4.5 Allowed .NET Common Language Run-time versions ............................................ 11
4.5.1 General ......................................................................................................... 11
4.5.2 CLR compatibility strategy ............................................................................. 11
4.5.3 How to identify the .NET target platform of a UIP ........................................... 12
4.6 UIP Deployment .................................................................................................... 12
4.7 UIP Lifecycle......................................................................................................... 13
4.7.1 General ......................................................................................................... 13
4.7.2 UIP Assembly activation steps ....................................................................... 13
4.7.3 UIP Assembly deactivation steps ................................................................... 15
4.8 Interaction between an FDI Client and a UIP ......................................................... 16
4.8.1 Handling of standard UI elements .................................................................. 16
4.8.2 Non-blocking service execution ..................................................................... 16
4.8.3 Blocking service execution............................................................................. 17
4.8.4 Cancel service execution ............................................................................... 18
4.8.5 Threading ...................................................................................................... 19
4.8.6 Timeout ......................................................................................................... 19
4.8.7 Exception handling ........................................................................................ 20
4.8.8 Type safe interfaces ...................................................................................... 21
4.8.9 Globalization and localization ........................................................................ 21
4.8.10 WPF Control handling .................................................................................... 21
4.8.11 Win Form handling ......................................................................................... 21
4.9 Security ................................................................................................................ 21
4.9.1 General ......................................................................................................... 21
4.9.2 Access permissions ....................................................................................... 22
4.9.3 Code identity concept .................................................................................... 22
5 Interface definition ......................................................................................................... 23
Figure 1 – FDI Type Library structure .................................................................................... 10
---------------------- Page: 4 ----------------------IEC 62769-6:2021 © IEC 2021 – 3 –
Figure 2 – .NET surrogate process ....................................................................................... 12
Figure 3 – Identification of Run-time Version......................................................................... 12
Figure 4 – IAsyncPattern based asynchronous service execution example ............................ 17
Figure 5 – Blocking service execution example using IAsyncResult based pattern ................ 18
Figure 6 – Cancel service processing sequence example ..................................................... 18
Figure 7 – Exception source ................................................................................................. 20
Table 1 – Technology edition reference .................................................................................. 9
Table 2 – Base Property Services ......................................................................................... 23
Table 3 – Device Model Services .......................................................................................... 23
Table 4 – Access Control Services ........................................................................................ 24
Table 5 – Direct Access Services .......................................................................................... 24
Table 6 – Hosting Services ................................................................................................... 24
Table 7 – UIP Services ......................................................................................................... 26
Table 8 – Base Data Types ................................................................................................... 26
Table 9 – Special Types ....................................................................................................... 27
---------------------- Page: 5 ----------------------– 4 – IEC 62769-6:2021 © IEC 2021
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –
Part 6: Technology Mapping
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC
Publication(s)"). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62769-6 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.This second edition cancels and replaces the first edition published in 2015. This edition
constitutes a technical revision.This edition includes the following significant technical changes with respect to the previous
edition:a) redesign of the security concept for UIP execution.
---------------------- Page: 6 ----------------------
IEC 62769-6:2021 © IEC 2021 – 5 –
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/763/FDIS 65E/773/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62769 series, published under the general title Field Device
Integration (FDI), can be found on the IEC website.The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correctunderstanding of its contents. Users should therefore print this document using a
colour printer.---------------------- Page: 7 ----------------------
– 6 – IEC 62769-6:2021 © IEC 2021
INTRODUCTION
The IEC 62769 series has the general title Field Device Integration (FDI) and the following
parts:– Part 1: Overview
– Part 2: FDI Client
– Part 3: FDI Server
– Part 4: FDI Packages
– Part 5: FDI Information Model
– Part 6: FDI Technology Mapping
– Part 7: FDI Communication Devices
– Part 100: Profiles – Generic Protocol Extensions
– Part 101-1: Profiles – Foundation Fieldbus H1
– Part 101-2: Profiles – Foundation Fieldbus HSE
– Part 103-1: Profiles – PROFIBUS
– Part 103-4: Profiles – PROFINET
– Part 109-1: Profiles – HART and WirelessHART
– Part 115-2: Profiles – Protocol-specific Definitions for Modbus RTU
– Part 150-1: Profiles – ISA 100.11a
---------------------- Page: 8 ----------------------
IEC 62769-6:2021 © IEC 2021 – 7 –
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 anyamendments) 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: InfrastructureISO/IEC 29500, (all parts) Information technology – Document description and processing
languages – Office Open XML File Formats3 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
---------------------- Page: 9 ----------------------
– 8 – IEC 62769-6:2021 © IEC 2021
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 Client3.1.3
Global Assembly Cache
machine-wide code cache that stores Assemblies specifically designated to be shared by
several applications3.1.4
Windows Registry
system-defined database in which applications and system components store and retrieve
configuration data3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in IEC 62769-1 as well as the
following apply.CLR Common Language Run-time
MSI Microsoft Installer
WPF Windows Presentation Foundation
UML Unified Modeling Language
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.---------------------- Page: 10 ----------------------
IEC 62769-6:2021 © IEC 2021 – 9 –
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.Table 1 – Technology edition reference
Technology Standard Edition
.NET N/A CLR4 for UIP Implementation
EDDL IEC 61804 2016
OPC UA (Parts 1-8) IEC 62541 2015
Open Packaging Convention ISO/IEC 29500 2016
Extensible Markup Language (XML) N/A W3C, 1.0 (fifth edition)
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.
---------------------- Page: 11 ----------------------
– 10 – IEC 62769-6:2021 © IEC 2021
NOTE The composite structure diagram shows only the core interfaces that implement the interfaces defined in
IEC 62769-2.Figure 1 – 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.---------------------- Page: 12 ----------------------
IEC 62769-6:2021 © IEC 2021 – 11 –
4.3 UIP executable representation
The implementation of the UIP depends on the type of user interface elements that can be
embedded into the user interface hosting environment of the FDI Client. UIP shall be
implemented as a .NET System.Windows.Forms class UserControl or a WindowsPresentation Foundation (WPF) System.Windows.Controls class UserControl.
UIP executables and their required libraries shall have strong names. The signing of a strong-
named Assembly can be done using a self-generated key.NOTE The identity of strong-named Assemblies consists of a name, version, culture, public key token and digital
signature.UIP executables and their required libraries shall be shipped with file containing the public
key in order to enable Assembly verification.4.4 UIP executable compatibility rules
The compatibility rules for different versions of the UIP component are specified in
IEC 62769-4.The compilation target platform for the UIP shall be "anyCPU". If this is not feasible, the UIP
shall be shipped in two variants. One UIP variant shall be compiled for target platform "x86".
The second UIP variant shall be compiled for target platform "x64". The compilation platform
target shall be described in the catalog.xml file, which is defined in IEC 62769-4. This
catalog.xml file contains an xml element "CpuInformation" that describes the User Interface
Plug-in variant. The allowed values that shall be used in the xml element "CpuInformation" are
"anyCPU", "x86" or "x64".4.5 Allowed .NET Common Language Run-time versions
4.5.1 General
Specific CLR (Common Language Run-time) versions are released for the execution of
software components built with specific .NET Framework versions. The .NET CLR version 4.0
is used to execute software components built with .NET Framework 4.0. .NET Components
are built for one CLR version only but can be capable to run also under a newer CLR version.
FDI Clients can be built based on CLR version 4.0 or future versions. An FDI Client has to
realize the following situations when starting a UIP.• When the UIP to be started was built for the same run-time, the UIP can be started by the
FDI Client as usual.• When the UIP to be started was built with another CLR version and is not compiled for the
current running CLR version, the FDI Client shall start the UIP in a surrogate process with
the adequate CLR version. (More details are described in 4.5.2.)Taking this behavior in account, a UIP shall be developed for CLR version 4.0 or any future
version. If the CLR versions do not match, the UIP shall be started in a separate process. The
UIP will then not be displayed as an integrated module within the FDI Client. It is up to the
FDI Client to realize the surrogate process.4.5.2 CLR compatibility strategy
In the future, FDI Clients and UIPs will be permitted to be built on different incompatible
versions of the CLR.If an FDI Client detects that a UIP requires a CLR that is not compatible with the FDI Client,
the FDI Client can use a proxy class that enables interaction with the UIP built using a
different version of the CLR.---------------------- Page: 13 ----------------------
– 12 – IEC 62769-6:2021 © IEC 2021
The FDI Client loads a proxy UIP executable, creates an instance of the proxy class, and
delegates the execution of the UIP to this proxy. The pro...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.