Field Device Integration (FDI) - Part 6: Technology Mapping (IEC 62769-6:2021

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.

Feldgeräteintegration (FDI) - Teil 6: FDI-Technologieabbildungen (IEC 62769-6:2021)

Intégration des appareils de terrain (FDI) - Partie 6: Mapping de technologies (IEC 62769-6:2021)

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.

Integracija procesne naprave (FDI) - 6. del: Preslikava tehnologije FDI (IEC 62769-6:2021)

General Information

Status
Published
Publication Date
25-May-2021
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
31-Mar-2021
Due Date
05-Jun-2021
Completion Date
26-May-2021

RELATIONS

Buy Standard

Standard
SIST EN IEC 62769-6:2021 - BARVE na PDF-str 16,26
English language
30 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day
Draft
oSIST prEN 62769-6:2018 - BARVE na PDF-str 22
English language
25 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN IEC 62769-6:2021
01-julij-2021
Nadomešča:
SIST EN 62769-6:2015

Integracija procesne naprave (FDI) - 6. del: Preslikava tehnologije FDI (IEC 62769-

6:2021)
Field Device Integration (FDI) - Part 6: Technology Mapping (IEC 62769-6:2021

Feldgeräteintegration (FDI) - Teil 6: FDI-Technologieabbildungen (IEC 62769-6:2021)

Intégration des appareils de terrain (FDI) - Partie 6: Mapping de technologies (IEC 62769

-6:2021)
Ta slovenski standard je istoveten z: EN IEC 62769-6:2021
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
SIST EN IEC 62769-6:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN IEC 62769-6:2021
---------------------- Page: 2 ----------------------
SIST EN IEC 62769-6:2021
EUROPEAN STANDARD EN IEC 62769-6
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2021
ICS 25.040.40; 35.100.05 Supersedes EN 62769-6:2015 and all of its amendments
and corrigenda (if any)
English Version
Field Device Integration (FDI) - Part 6: Technology Mapping
(IEC 62769-6:2021)

Intégration des appareils de terrain (FDI) - Partie 6: Feldgeräteintegration (FDI) - Teil 6: FDI-

Mapping de technologies Technologieabbildungen
(IEC 62769-6:2021) (IEC 62769-6:2021)

This European Standard was approved by CENELEC on 2021-03-12. CENELEC members are bound to comply with the CEN/CENELEC

Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC

Management Centre or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation

under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the

same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,

Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the

Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,

Turkey and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels

© 2021 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.

Ref. No. EN IEC 62769-6:2021 E
---------------------- Page: 3 ----------------------
SIST EN IEC 62769-6:2021
EN IEC 62769-6:2021 (E)
European foreword

The text of document 65E/763(F)/FDIS, future edition 2 of IEC 62769-6, prepared by SC 65E “Devices

and integration in enterprise systems” of IEC/TC 65 “Industrial-process measurement, control and

automation” was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as

EN IEC 62769-6:2021.
The following dates are fixed:

• latest date by which the document has to be implemented at national (dop) 2021-12-12

level by publication of an identical national standard or by endorsement

• latest date by which the national standards conflicting with the (dow) 2024-03-12

document have to be withdrawn

This document supersedes EN 62769-6:2015 and all of its amendments and corrigenda (if any).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.

Endorsement notice

The text of the International Standard IEC 62769-6:2021 was approved by CENELEC as a European

Standard without any modification.
---------------------- Page: 4 ----------------------
SIST EN IEC 62769-6:2021
EN IEC 62769-6:2021 (E)
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments)

applies.

NOTE 1 Where an International Publication has been modified by common modifications, indicated by (mod), the

relevant EN/HD applies.

NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available

here: www.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61804 series Function blocks (FB) for process control EN IEC 61804 series
and electronic device description language
(EDDL)
IEC 62541 series OPC Unified Architecture EN IEC 62541 series
IEC 62769-1 - Field Device Integration (FDI) - Part 1:EN IEC 62769-1 -
Overview
IEC 62769-2 - Field Device Integration (FDI) - Part 2: FDI EN IEC 62769-2 -
Client
IEC 62769-4 - Field Device Integration (FDI) - Part 4: FDI EN IEC 62769-4 -
Packages
ISO/IEC 19505-1 - Information technology - Object - -
Management Group Unified Modeling
Language (OMG UML) – Part 1:
Infrastructure
ISO/IEC 29500 series Information technology - Document - -
description and processing languages -
Office Open XML File Formats
---------------------- Page: 5 ----------------------
SIST EN IEC 62769-6:2021
---------------------- Page: 6 ----------------------
SIST EN IEC 62769-6:2021
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 Commission
Marque déposée de la Commission Electrotechnique Internationale
---------------------- Page: 7 ----------------------
SIST EN IEC 62769-6:2021
– 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: 8 ----------------------
SIST EN IEC 62769-6:2021
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: 9 ----------------------
SIST EN IEC 62769-6:2021
– 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: 10 ----------------------
SIST EN IEC 62769-6:2021
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 correct

understanding of its contents. Users should therefore print this document using a

colour printer.
---------------------- Page: 11 ----------------------
SIST EN IEC 62769-6:2021
– 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: 12 ----------------------
SIST EN IEC 62769-6:2021
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 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
---------------------- Page: 13 ----------------------
SIST EN IEC 62769-6:2021
– 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 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.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: 14 ----------------------
SIST EN IEC 62769-6:2021
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: 15 ----------------------
SIST EN IEC 62769-6:2021
– 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: 16 ----------------------
SIST EN IEC 62769-6:2021
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 Windows
Presentation 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 sta
...

SLOVENSKI STANDARD
oSIST prEN 62769-6:2018
01-julij-2018

1DSUDYHLQLQWHJUDFLMDYSURL]YRGQLKVLVWHPLKLQWHJUDFLMDSURFHVQHQDSUDYH

GHO1DþUWRYDQMHWHKQRORJLMH )',
Field Device Integration (FDI) - Part 6: FDI Technology Mapping
Feldgeräteintegration (FDI) - Teil 6: FDI-Technologieabbildungen

Intégration des dispositifs de terrain (FDI) - Partie 6: Mapping de technologies FDI

Ta slovenski standard je istoveten z: prEN 62769-6:2018
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN 62769-6:2018 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 62769-6:2018
---------------------- Page: 2 ----------------------
oSIST prEN 62769-6:2018
65E/593/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-6 ED2
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2018-05-18 2018-08-10
SUPERSEDES DOCUMENTS:
65E/537/RR
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
Other TC/SCs are requested to indicate their interest, if
any, in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY

SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING

Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft
for Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.

This document is still under study and subject to change. It should not be used for reference purposes.

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of

which they are aware and to provide supporting documentation.
TITLE:
Field Device Integration (FDI) - Part 6: FDI Technology Mapping
PROPOSED STABILITY DATE: 2021
NOTE FROM TC/SC OFFICERS:

Copyright © 2018 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this

electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.

You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without

permission in writing from IEC.
---------------------- Page: 3 ----------------------
oSIST prEN 62769-6:2018
---------------------- Page: 4 ----------------------
oSIST prEN 62769-6:2018
– 2 – IEC CDV 62769-6  IEC:2018
CONTENTS

FOREWORD ........................................................................................................................... 2

INTRODUCTION ..................................................................................................................... 4

1 Scope .............................................................................................................................. 5

2 Normative references ...................................................................................................... 5

3 Terms, definitions, abbreviated terms, acronyms and conventions ................................... 5

3.1 Terms and definitions.............................................................................................. 5

3.2 Abbreviated terms and acronyms ............................................................................ 6

3.3 Symbols .................................................................................................................. 6

4 Technical concepts .......................................................................................................... 6

4.1 General ................................................................................................................... 6

4.1.1 Overview ......................................................................................................... 6

4.1.2 Platforms ......................................................................................................... 6

4.1.3 FDI Type Library .............................................................................................. 7

4.2 UIP representation .................................................................................................. 8

4.3 UIP executable representation ................................................................................ 8

4.4 UIP executable compatibility rules .......................................................................... 9

4.5 Allowed .NET Common Language Run-time versions .............................................. 9

4.5.1 General ........................................................................................................... 9

4.5.2 CLR compatibility strategy ............................................................................... 9

4.5.3 How to identify the .NET target platform of a UIP ........................................... 10

4.6 UIP Deployment .................................................................................................... 10

4.7 UIP Life-cycle ....................................................................................................... 10

4.7.1 General ......................................................................................................... 10

4.7.2 UIP Assembly activation steps ....................................................................... 11

4.7.3 UIP Assembly deactivation steps ................................................................... 13

4.8 Interaction between an FDI Client and a UIP ......................................................... 13

4.8.1 Handling of standard UI elements .................................................................. 13

4.8.2 Non-blocking service execution ..................................................................... 14

4.8.3 Blocking service execution ............................................................................ 15

4.8.4 Cancel service execution ............................................................................... 15

4.8.5 Threading ...................................................................................................... 16

4.8.6 Timeout ......................................................................................................... 16

4.8.7 Exception handling ........................................................................................ 17

4.8.8 Type safe interfaces ...................................................................................... 17

4.8.9 Globalization and localization ........................................................................ 18

4.8.10 WPF Control handling .................................................................................... 18

4.8.11 Win Form handling......................................................................................... 18

4.9 Security ................................................................................................................ 18

4.9.1 General ......................................................................................................... 18

4.9.2 Access permissions ....................................................................................... 18

4.9.3 Code identity concept .................................................................................... 19

5 Interface definition ......................................................................................................... 19

Figure 1 – FDI Type Library structure...................................................................................... 8

Figure 2 – .NET surrogate process ....................................................................................... 10

---------------------- Page: 5 ----------------------
oSIST prEN 62769-6:2018
IEC CDV 62769-6  IEC:2018 – 3 –

Figure 3 – Identification of Run-time Version ........................................................................ 10

Figure 4 – IAsyncPattern based asynchronous service execution example............................ 14

Figure 5 – Blocking service execution example using IAsyncResult based pattern ................ 15

Figure 6 – Cancel service processing sequence example ..................................................... 15

Figure 7 – Exception source ................................................................................................. 17

Table 1 – Technology edition reference .................................................................................. 7

Table 2 – Base Property Services ......................................................................................... 20

Table 3 – Device Model Services .......................................................................................... 20

Table 4 – Access Control Services ........................................................................................ 20

Table 5 – Direct Access Services .......................................................................................... 20

Table 6 – Hosting Services ................................................................................................... 21

Table 7 – UIP Services ......................................................................................................... 22

Table 8 – Base Data Types ................................................................................................... 22

Table 9 – Special Types ....................................................................................................... 22

---------------------- Page: 6 ----------------------
oSIST prEN 62769-6:2018
– 2 – IEC CDV 62769-6  IEC:2018
1 INTERNATIONAL ELECTROTECHNICAL COMMISSION
2 ____________
4 FIELD DEVICE INTEGRATION (FDI) –
6 Part 6: Technology Mapping
10 FOREWORD

11 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising

12 all national electrotechnical committees (IEC National Committees). The object of IEC is to promote

13 international co-operation on all questions concerning standardization in the electrical and electronic fields. To

14 this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,

15 Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC

16 Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested

17 in the subject dealt with may participate in this preparatory work. International, governmental and non-

18 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely

19 with the International Organization for Standardization (ISO) in accordance with conditions determined by

20 agreement between the two organizations.

21 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international

22 consensus of opinion on the relevant subjects since each technical committee has representation from all

23 interested IEC National Committees.

24 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National

25 Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC

26 Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any

27 misinterpretation by any end user.

28 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications

29 transparently to the maximum extent possible in their national and regional publications. Any divergence

30 between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in

31 the latter.

32 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity

33 assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any

34 services carried out by independent certification bodies.

35 6) All users should ensure that they have the latest edition of this publication.

36 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and

37 members of its technical committees and IEC National Committees for any personal injury, property damage or

38 other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and

39 expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC

40 Publications.

41 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is

42 indispensable for the correct application of this publication.

43 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of

44 patent rights. IEC shall not be held responsible for identifying any or all such patent rights.

45 International Standard IEC 62769 has been prepared by subcommittee 65E: Devices and

46 integration in enterprise systems, of IEC technical committee 65: Industrial-process

47 measurement, control and automation.

48 This second edition cancels and replaces the first edition published in: 2015. This edition

49 constitutes a technical revision.

50 This edition includes the following significant technical changes with respect to the previous

51 edition:

52 a) Support for generic protocol extension for faster adoption of other technologies

53 b) Support for Package Developers to build EDDs targeted for today’s EDD bases system

54 under a single development tool.

55 c) Digital signature now include trusted timestamping for long term validation of FDI

56 Package
---------------------- Page: 7 ----------------------
oSIST prEN 62769-6:2018
IEC CDV 62769-6  IEC:2018 – 3 –
58 d) Running UIPs in a sandbox
59 e) Time stamp for device package signature
60 f) Support of new protocols

61 g) Generic protocol extension to allow adoption of other communication protocols

62 h) Based on generic protocol extension: Modbus RTU;
64 The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/XXX/FDIS 65E/XXX/RVD

66 Full information on the voting for the approval of this International Standard can be found in

67 the report on voting indicated in the above table.

68 This document has been drafted in accordance with the ISO/IEC Directives, Part 2.

69 The committee has decided that the contents of this document will remain unchanged until the

70 stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to

71 the specific document. At this date, the document will be
72 • reconfirmed,
73 • withdrawn,
74 • replaced by a revised edition, or
75 • amended.

77 The National Committees are requested to note that for this document the stability date

78 is 2022.

79 THIS TEXT IS INCLUDED FOR THE INFORMATION OF THE NATIONAL COMMITTEES AND WILL BE

80 DELETED AT THE PUBLICATION STAGE.

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 correct

understanding of its contents. Users should therefore print this document using a

colour printer.
---------------------- Page: 8 ----------------------
oSIST prEN 62769-6:2018
– 4 – IEC CDV 62769-6  IEC:2018
83 INTRODUCTION

84 The IEC 62769 series has the general title "Field Device Integration (FDI)" and the following

85 parts:
86 – Part 1: Overview
87 – Part 2: FDI Client
88 – Part 3: FDI Server
89 – Part 4: FDI Packages
90 – Part 5: FDI Information Model
91 – Part 6: FDI Technology Mapping
92 – Part 7: FDI Communication Devices
93 – Part 100: Profiles – Generic Protocol Extensions
94 – Part 101-1: Profiles – Foundation Fieldbus H1
95 – Part 101-2: Profiles – Foundation Fieldbus HSE
96 – Part 103-1: Profiles – PROFIBUS
97 – Part 103-4: Profiles – PROFINET
98 – Part 109-1: Profiles – HART and WirelessHART
99 – Part 115-2: Profiles – Protocol-specific Definitions for Modbus RTU
100 – Part 150-1: Profiles – ISA 100.11a
101
---------------------- Page: 9 ----------------------
oSIST prEN 62769-6:2018
IEC CDV 62769-6  IEC:2018 – 5 –
102 FIELD DEVICE INTEGRATION (FDI) –
103
104 Part 6: Technology Mapping
105
106
107 1 Scope

108 This part of IEC 62769 specifies the technology mapping for the concepts described in the

109 Field Device Integration (FDI) standard. The technology mapping focuses on implementation

110 regarding the components FDI Client and User Interface Plug-in (UIP) that are specific only to

111 the WORKSTATION platform / .NET as defined in IEC 62769-4.
112 2 Normative references

113 The following documents are referred to in the text in such a way that some or all of their

114 content constitutes requirements of this document. For dated references, only the edition

115 cited applies. For undated references, the latest edition of the referenced document (including

116 any amendments) applies.

117 IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device

118 Description Language (EDDL)
119 IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
120 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
121 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
122 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model
123 IEC 62541 (all parts), OPC Unified Architecture

124 ISO/IEC 19505-1, Information technology – Object Management Group Unified Modeling

125 Language (OMG UML) – Part 1: Infrastructure

126 ISO/IEC 29500, (all parts) Information technology - Document description and processing

127 languages - Office Open XML File Formats
128 3 Terms, definitions, abbreviated terms, acronyms and conventions
129 3.1 Terms and definitions

130 For the purposes of this document, the terms and definitions given in IEC 62769-1 as well as

131 the following apply.

132 ISO and IEC maintain terminological databases for use in standardization at the following

133 addresses:
134 • IEC Electropedia: available at http://www.electropedia.org/
135 • ISO Online browsing platform: available at http://www.iso.org/obp
136 3.1.1
137 application domain
138 isolated environment where applications execute
139 3.1.2
140 assembly

141 reusable, version information providing, and self-describing building block of a CLR

142 application
---------------------- Page: 10 ----------------------
oSIST prEN 62769-6:2018
– 6 – IEC CDV 62769-6  IEC:2018
143 3.1.3
144 FDI type library

145 assembly that contains the interfaces and data types that are used for the data exchange and

146 interaction between a UIP and an FDI Client
147 3.1.4
148 global assembly cache

149 machine-wide code cache that stores Assemblies specifically designated to be shared by

150 several applications
151 3.1.5
152 windows registry

153 system-defined database in which applications and system components store and retrieve

154 configuration data
155 3.2 Abbreviated terms and acronyms

156 For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1

157 as well as the following apply.
CLR Common Language Run-time
MSI Microsoft Installer
WPF Windows Presentation Foundation
UML Unified Modeling Language
158
159 3.3 Symbols

160 Figures in this document use the graphical symbols according to ISO/IEC 19505 (UML 2.0).

161 4 Technical concepts
162 4.1 General
163 4.1.1 Overview

164 In 4.1.2, 4.2, 4.3, 4.4, and 4.5, this document describes first the technology base for UIP

165 implementation, the hardware and software environment including the related implementation

166 rules. Clause 4 follows a life-cycle (use case) oriented approach.

167 Subclause 4.6 describes the copy deployment procedures and related implementation rules

168 for the UIP and the FDI Client. UIP executable instantiation and termination is described in

169 4.7. Subclause 4.8 defines the rules about interaction between the FDI Client and the UIP.

170 Security related definitions are written in 4.9. The service interface definitions for the FDI

171 Client and the UIP are found in Clause 5.
172 4.1.2 Platforms

173 The UIP and FDI Client shall be built upon the Microsoft .NET Framework and executed in

174 the .NET Common Language Run-time.

175 The minimum set of workstation supported I/O devices is: mouse, keyboard, and color screen

176 resolution of 1024 x 768 pixels.

177 The following Table 1 lists all the technologies and their editions that are consistent with FDI

178 components.
---------------------- Page: 11 ----------------------
oSIST prEN 62769-6:2018
IEC CDV 62769-6  IEC:2018 – 7 –
179 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 2011
Extensible Markup Language (XML) N/A W3C, 1.0 (fifth edition)
180
181 4.1.3 FDI Type Library

182 The Device Access Services and the UIP Services can be modelled as .NET interfaces

183 passing .NET data type arguments. These interfaces and data types are used for the data

184 exchange and interaction between the UIP and the FDI Client. For runtime error handling

185 purposes during interface method calls .NET exceptions classes are defined.

186 The FDI .NET interfaces, data types, and exception classes are defined in a single FDI Type

187 Library. The FDI Type Library is a strong named Assembly. The file name of this Assembly

188 shall be ‘fdi.dll’. The fdi.dll shall be versioned as per

189 IEC 62769-1 —, 8.1. The FDI Type Library is part of the FDI Core Technology as per

190 IEC 62769-1 —, 8.3.2.1. and therefore directly influences the FDI Technology Version. All

191 Compatible changes of the fdi.dll lead to an increase of the minor portion of the FDI

192 Technology Version. Incompatible changes lead to an increase of the major portion of the FDI

193 Technology Version (see
194 IEC 62769-1 —,8.3.2.2).

195 The FDI Type Library is signed with a single unique key by the issuer of the file. The FDI Type

196 Library shall be installed separately as part of every FDI Client installation. User Interface

197 Plug-Ins (UIP) and the FDI Client Application shall use this instance of the fdi.dll. UIPs shall

198 not carry or deploy the FDI Type Library. The FDI Client is responsible to provide means to

199 allow updates of this type library over time.
200
---------------------- Page: 12 ----------------------
oSIST prEN 62769-6:2018
– 8 – IEC CDV 62769-6  IEC:2018
201 Figure 1 shows the FDI Type Library structure.
202
203 Figure 1 – FDI Type Library structure

204 NOTE The composite structure diagram shows only the core interfaces that implement the interfaces defined in

205 IEC 62769-2.
206 4.2 UIP representation

207 The UIP Variant can contain either a single or multiple runtime modules (.NET Assembly) and

208 their related supplementary files (for example: resource files). The runtime module of the UIP

209 Variant is called UIP executable. The supplementary file(s) of the UIP Variant is/are called

210 UIP supplement(s).

211 UIP supplement(s) is/are stored under (a) subfolder(s) of the UIP executable installation

212 directory

213 EXAMPLE Examples of UIP supplementary data files include resource files and application configuration data.

214 The RuntimeId of a UIP Variant shall be ".NET Framework CLR4", see IEC 62769-4. FDI

215 Clients supporting this RuntimeId shall support the .NET Framework 4.6.1 or higher using the

216 CLR4 and UIPs with this RuntimeId shall use the .NET Framework 4.6.1 or lower supporting

217 the CLR4 (meaning .NET Framework 4.0 up to .NET Framework 4.6.1).

218 The UIP Variant shall be self-contained. All UIP required libraries (.NET Assemblies) required

219 by a UIP Variant are stored within the same Folder.
220 4.3 UIP executable representation

221 The implementation of the UIP depends on the type of user interface elements that can be

222 embedded into the user interface hosting environment of the FDI Client. UIP shall be

223 implemented as a .NET System.Windows.Forms class UserControl or a Windows
224 Presentation Foundation (WPF) System.Windows.Controls class UserControl.
---------------------- Page: 13 ----------------------
oSIST prEN 62769-6:2018
IEC CDV 62769-6  IEC:2018 – 9 –

225 UIP executables and their required libraries shall have strong names. The signing of a strong

226 named Assembly can be done using a self-generated key.

227 NOTE The identity of strong named Assemblies consists of a name, version, culture, public key token and digital

228 signature.

229 UIP executables and their required libraries shall be shipped with file containing the public

230 key in order to enable Assembly verification.
231 4.4 UIP executable compatibility rules

232 The compatibility rules for different versions of the UIP component are specified in

233 IEC 62769-4.

234 The compilation target platform for the UIP shall be “anyCPU”. If this is not feasible the UIP

235 shall be shipped in two variants. One UIP variant shall be compiled for target platform “x86”.

236 The second UIP variant shall be compiled for target platform “x64”. The compilation platform

237 target shall be described in the catalog.xml file which is defined in IEC 62769-4. This

238 catalog.xml file contains an xml element “CpuInformation” that describes the User Interface

239 Plug-in variant. The allowed values that shall be used in the xml element “CpuInformation” are

240 “anyCPU”, “x86” or “x64”.
241 4.5 Allowed .NET Common Language Run-time versions
242 4.5.1 General

243 Specific CLR (Common Language Run-time) versions are released for the execution of

244 software components built with specific .NET Framework versions. The .NET CLR version 4.0

245 is used to execute software components built with .NET Framework 4.0. .NET Components

246 are built for one CLR version only but can be capable to run also under a newer CLR version.

247 FDI Clients can be built based on CLR version 4.0 or future versions. An FDI Client has to

248 realize the following situations when starting a UIP.

249 • When the UIP to be started was built for the same run-time, the UIP can be started by the

250 FDI Client as usual.

251 • When the UIP to be started was built with another CLR version and is not compiled for the

252 current running CLR version, the FDI Client shall start the UIP in a surrogate process with

253 the adequate CLR version. (More details are described in 4.5.2.)

254 Taking this behavior in account, a UIP shall be developed for CLR version 4.0 or any future

255 version. In case the CLR versions do not match, the UIP shall be started in a separate

256 process. The UIP will then not be displayed as an integrated module within the FDI Client. It

257 is up to the FDI Client to realize the surrogate process.
258 4.5.2 CLR compatibility strategy

259 In the future, FDI Clients and UIPs will be permitted to be built on different incompatible

260 versions of the CLR.

261 If an FDI Client detects that a UIP requires a CLR that is not compatible with the FDI Client,

262 the FDI Client can use a proxy class that enables interaction with the UIP built using a

263 different version of the CLR.

264 The FDI Client loads a proxy UIP executable, creates an instance of the proxy class, and

265 delegates the execution of the UIP to this proxy. The proxy starts a process with the required

266 CLR and executes the UIP in this surrogate process. The proxy classes provide the standard

267 FDI interfaces. The FDI Client can use these interfaces to interact with the UIP executed in

268 the surrogate process.
---------------------- Page: 14 ----------------------
oSIST prEN 62769-6:2018
– 10 – IEC CDV 62769-6  IEC:2018
FDI Client Process
«library»
UIP Interface Proxy
.NET CLR Surrogate Process
«library»
UIP Interface Stub
«executable»
UIP
269
270 Figure 2 – .NET surrogate process
271 4.5.3 How to identify the .NET target platform of a UIP

272 The .NET target platform CLR version information for which a certain Assembly is compiled

273 can be extracted by means of .NET Framework library functions (see Figure 3).

clrVersion = Assembly.LoadFrom().ImageRuntimeVersion;
274
275 Figure 3 – Identification of Run-time Version

276 NOTE The Visual Studio 2008 and 2010 IDE allow developers to select the .NET Framework target. The

277 selection of a .NET Framework target older than the base for the current Visual Studio IDE automatically creates a

278 configuration file listed as “app.config” within the solution explorer. This file only reflects the current complier

279 setting. The compiler does not read that file.
280 4.6 UIP Deployment

281 The general UIP installation rules are outlined in IEC 62769-2. The UIP executable shall not

282 be registered within the Global Assembly Cache.

283 The “strong-name” rule ensures that related Assemblies of different versions of the

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.