BS EN IEC 62769-5:2021
$198.66
Field Device Integration (FDI) – Information Model
Published By | Publication Date | Number of Pages |
BSI | 2021 | 70 |
This part of IEC 62769 defines the FDI Information Model. One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore, it represents the devices of the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them. The types in the AddressSpace of the FDI Server constitute a catalogue, which is built from FDI Packages. The fundamental types for the FDI Information Model are well defined in OPC UA for Devices (IEC 62541-100). The FDI Information Model specifies extensions for a few special cases and otherwise explains how these types are used and how the contents are built from elements of DevicePackages. The overall FDI architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this illustration. [Figure 1 – FDI architecture diagram]
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
7 | English CONTENTS |
12 | FOREWORD |
14 | INTRODUCTION |
15 | 1 Scope Figures Figure 1 – FDI architecture diagram |
16 | 2 Normative references 3 Terms, definitions, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Abbreviated terms |
17 | 3.3 Conventions 3.4 Conventions for graphical notation Figure 2 – OPC UA Graphical Notation for NodeClasses Figure 3 – OPC UA Graphical Notation for References |
18 | Figure 4 – OPC UA Graphical Notation Example Figure 5 – Optimized Type Reference |
19 | 4 Overview of OPC Unified Architecture 4.1 General 4.2 Overview of OPC UA Devices |
20 | Figure 6 – OPC UA Devices Example: Functional Groups |
21 | 5 Concepts 5.1 General 5.2 Device topology Figure 7 – OPC UA Devices example: Configurable components |
22 | Figure 8 – Example of an automation system |
23 | 5.3 Online/offline Figure 9 – Example of a Device topology |
24 | 5.4 Catalogue (Type Definitions) 5.5 Communication 6 AddressSpace organization Figure 10 – Example Device Types representing a catalogue |
25 | 7 Device Model for FDI 7.1 General 7.2 Online/offline |
26 | 7.3 Device health 7.3.1 DeviceHealth Mapping Figure 11 – Online component for access to device data |
27 | 7.3.2 DeviceHealth Diagnostics Tables Table 1 – DeviceHealth Mapping Table 2 – DeviceType definition (excerpt applicable to this clause) |
28 | 7.4 User interface elements 7.4.1 General Table 3 – DeviceType definition with DeviceHealth and DeviceHealthDiagnostics |
29 | 7.4.2 UI Description Type 7.4.3 UI Plug-in Type Figure 12 – Hierarchy of user interface Types Table 4 – UIDescriptionType Definition |
30 | Table 5 – UIPlugInType Definition |
31 | 7.5 Type-specific support information |
32 | 7.6 Actions 7.6.1 Overview 7.6.2 Action Type Figure 13 – Integration of Actions within a TopologyElement |
33 | 7.6.3 ActionService Type 7.6.4 ActionService Object Table 6 – ActionType Definition Table 7 – ActionServiceType Definition |
34 | 7.6.5 InvokeAction Method Figure 14 – Action Service |
35 | 7.6.6 RespondAction Method Table 8 – InvokeAction Method Arguments Table 9 – InvokeAction Method AddressSpace Definition |
36 | 7.6.7 AbortAction Method Table 10 – RespondAction Method Arguments Table 11 – RespondAction Method AddressSpace Definition Table 12 – AbortAction Method Arguments |
37 | 8 Network and connectivity 9 Utility functions 9.1 Overview 9.2 Locking Table 13 – AbortAction Method AddressSpace Definition |
38 | 9.3 EditContext 9.3.1 Overview 9.3.2 EditContext Type 9.3.3 EditContext Object Table 14 – EditContextType Definition |
39 | 9.3.4 GetEditContext Method Figure 15 – EditContext type and instance Table 15 – GetEditContext Method Arguments |
40 | 9.3.5 RegisterNodes Method Table 16 – GetEditContext Method AddressSpace Definition Table 17 – RegisterNodes Method Arguments Table 18 – RegisterNodes Method AddressSpace Definition |
41 | 9.3.6 Apply Method Table 19 – RegistrationParameters DataType Structure Table 20 – RegisterNodesResult DataType Structure |
42 | 9.3.7 Reset Method Table 21 – Apply Method Arguments Table 22 – Apply Method AddressSpace Definition Table 23 – ApplyResult DataType Structure |
43 | 9.3.8 Discard Method Table 24 – Reset Method Arguments Table 25 – Reset Method AddressSpace Definition Table 26 – Discard Method Arguments |
44 | 9.4 Direct Device Access 9.4.1 General 9.4.2 DirectDeviceAccess Type Figure 16 – DirectDeviceAccessType Table 27 – Discard Method AddressSpace Definition |
45 | 9.4.3 DirectDeviceAccess Object Figure 17 – DirectDeviceAccess instance Table 28 – DirectDeviceAccessType Definition |
46 | 9.4.4 InitDirectAccess Method 9.4.5 EndDirectAccess Method Table 29 – DirectDeviceAccess Instance Definition Table 30 – InitDirectAccess Method Arguments Table 31 – InitDirectAccess Method AddressSpace Definition |
47 | 9.4.6 Transfer Method Table 32 – EndDirectAccess Method Arguments Table 33 – EndDirectAccess Method AddressSpace Definition Table 34 – Transfer Method Arguments |
48 | 10 Parameter Types 10.1 General Table 35 – Transfer Method AddressSpace Definition |
49 | 10.2 ScalingFactor Property 10.3 Min_Max_Values Property Figure 18 – OPC UA VariableTypes including OPC UA DataAccess Table 36 – ScalingFactor Property Definition |
50 | 11 FDI StatusCodes Table 37 – Min_Max_Values Property Definition Table 38 – Variant_Range DataType Structure Table 39 – Variant_Range Definition |
51 | 12 Specialized topology elements Table 40 – Good operation level result codes Table 41 – Uncertain operation level result codes Table 42 – Bad operation level result codes |
52 | 13 Auditing 13.1 General 13.2 FDI Client-provided context information 13.3 LogAuditTrailMessage Method |
53 | 14 FDI Server Version 15 Mapping FDI Package information to the FDI Information Model 15.1 General Table 43 – LogAuditTrailMessage Method Arguments Table 44 – LogAuditTrailMessage Method AddressSpace Definition Table 45 – FDIServerVersion Property Definition |
54 | 15.2 Localization 15.2.1 Localized text 15.2.2 Engineering units 15.3 Device 15.3.1 General 15.3.2 Mapping to Attributes to a specific DeviceType Node 15.3.3 Mapping to Properties |
55 | 15.3.4 Mapping to ParameterSet 15.3.5 Mapping to Functional Groups 15.3.6 Mapping to DeviceTypeImage 15.3.7 Mapping to Documentation 15.3.8 Mapping to ProtocolSupport Table 46 – DeviceType Property Mapping |
56 | 15.3.9 Mapping to ImageSet 15.3.10 Mapping to ActionSet 15.3.11 Mapping to MethodSet 15.4 Modular Device 15.5 Block 15.5.1 General 15.5.2 Mapping to Attributes |
57 | 15.5.3 Mapping to ParameterSet 15.5.4 Mapping to Functional Groups 15.5.5 Mapping to ActionSet 15.5.6 Mapping to MethodSet 15.5.7 Instantiation rules 15.6 Parameter 15.6.1 General |
58 | Table 47 – Setting OPC UA Variable Attributes from EDDL variable attributes |
59 | Table 48 – Correspondence between EDDL and OPC UA standard data types |
61 | 15.6.2 Private Parameters |
62 | 15.6.3 MIN_Value and MAX_Value 15.6.4 Engineering units 15.6.5 Enumerated Parameters 15.6.6 Bit-enumerated Parameters 15.6.7 Representation of records |
63 | 15.6.8 Representation of arrays, and lists of Parameters with simple data types Figure 19 – Example: Complex variable representing a RECORD |
64 | 15.6.9 Representation of values arrays, and lists of RECORD Parameters 15.6.10 Representation of COLLECTION and REFERENCE ARRAY Figure 20 – Complex variable representing a VALUE_ARRAY of RECORDs |
65 | 15.6.11 SCALING_FACTOR 15.7 Functional Groups |
66 | 15.8 AXIS elements in UIDs 15.9 Actions 15.10 UIPs 15.11 Protocols, Networks and Connection Points |
67 | 16 Profiles Table 49 – FDI Server Facet Definition Table 50 – FDI Client Facet Definition |
68 | Annex A (normative) Namespace and Mappings |
69 | Bibliography |