prEN 62769-150-1:2018

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.DField device Integration (FDI) - Part 150-1: Profiles - ISA100.11a35.240.50Uporabniške rešitve IT v industrijiIT applications in industry25.040.40Merjenje in krmiljenje industrijskih postopkovIndustrial process measurement and controlICS:Ta slovenski standard je istoveten z:prEN 62769-150-1:2018oSIST prEN 62769-150-1:2018en01-junij-2018oSIST prEN 62769-150-1:2018SLOVENSKI

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: SC 65C

Other TC/SCs are requested to indicate their interest, if any, in this CDV to the secretary. FUNCTIONS CONCERNED:

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.

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.

FOREWORD ........................................................................................................................... 4 1 Scope .............................................................................................................................. 6 2 Normative References ..................................................................................................... 6 3 Terms, definitions, abbreviated terms and acronyms ....................................................... 6 3.1 Terms and definitions.............................................................................................. 6 3.2 Abbreviated terms and acronyms ............................................................................ 6 4 Conventions .................................................................................................................... 7 4.1 EDDL syntax ........................................................................................................... 7 4.2 Capitalizations ........................................................................................................ 7 5 Profile for ISA100.11a ..................................................................................................... 7 5.1 General ................................................................................................................... 7 5.2 Catalog profile ........................................................................................................ 7 5.2.1 Protocol support file ......................................................................................... 7 5.2.2 CommunicationProfile definition....................................................................... 8 5.2.3 Profile device ................................................................................................... 8 5.2.4 Protocol version information ............................................................................ 8 5.3 Associating a Package with a device....................................................................... 8 5.3.1 Device type identification mapping ................................................................... 8 5.3.2 Device type revision mapping .......................................................................... 9 5.4 Information Model mapping ..................................................................................... 9 5.4.1 ProtocolType definition .................................................................................... 9 5.4.2 DeviceType mapping ..................................................................................... 10 5.4.3 FunctionalGroup identification definition ........................................................ 10 5.4.4 BlockType property mapping ......................................................................... 10 5.4.5 Mapping to Object ParameterSet ................................................................... 11 5.5 Topology elements ................................................................................................ 11 5.5.1 ConnectionPoint definition ............................................................................. 11 5.5.2 Communication Device definition ................................................................... 13 5.5.3 Communication service provider definition ..................................................... 14 5.5.4 Network definition .......................................................................................... 15 5.6 Methods ................................................................................................................ 15 5.6.1 Methods for FDI Communication Servers ....................................................... 15 5.6.2 Methods for Gateways ................................................................................... 20 Annex A (normative)

Topology Scan result schema ............................................................. 21 A.1 General ................................................................................................................. 21 A.2 Network ................................................................................................................ 21 A.3 ISA100_WirelessNetworkT .................................................................................... 21 A.4 ISA100_WirelessConnectionPointT ....................................................................... 21 A.5 ISA100_WirelessIdentificationT ............................................................................ 22 A.6 ISA100_WirelessAddressT .................................................................................... 23 A.7 ISA_WirelessObjIdentificationT ............................................................................. 23 Annex B (normative)

Transfer service parameters ................................................................ 24 B.1 General ................................................................................................................. 24 B.2 sendData .............................................................................................................. 24 B.3 receiveData .......................................................................................................... 24 oSIST prEN 62769-150-1:2018

B.4 TransferSendDataT............................................................................................... 24 B.5 OperationT ............................................................................................................ 25 B.6 TransferResultDataT ............................................................................................. 25 Bibliography .......................................................................................................................... 26

Table 1 – Capability file part ................................................................................................... 7 Table 2 – Protocol Version Information ................................................................................... 8 Table 3 – Device identification information mapping................................................................ 9 Table 4 – Device type catalog mapping ................................................................................... 9 Table 5 – Protocol type ISA100.11a ...................................................................................... 10 Table 6 – Inherited DeviceType property mapping ................................................................ 10 Table 7 – ISA100.11a wireless device types identification attributes ..................................... 10 Table 8 – Inherited BlockType property mapping .................................................................. 11 Table 10 – Method Connect arguments ................................................................................. 15 Table 11 – Method Disconnect arguments ............................................................................ 16 Table 12 – Method Transfer arguments ................................................................................. 18 Table 13 – Method GetPublishedData arguments ................................................................. 19 Table A.1 – Elements of ISA100_WirelessNetworkT ............................................................. 21 Table A.2 – Elements of ISA100_WirelessConnectionPointT ................................................. 22 Table A.3 – Attributes of ISA100_WirelessIdentificationT ...................................................... 22 Table A.4 – Attributes of ISA100_WirelessObjIdentificationT ................................................ 23 Table B.1 – Attributes of TransferSendDataT ........................................................................ 24 Table B.2 – Enumerations of OperationT .............................................................................. 25 Table B.3 – Attributes of TransferResultDataT ...................................................................... 25

2007 FOREWORD 2008 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising 2009 all national electrotechnical committees (IEC National Committees). The object of IEC is to promote 2010 international co-operation on all questions concerning standardization in the electrical and electronic fields. To 2011 this end and in addition to other activities, IEC publishes International Standards, Technical Specifications, 2012 Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC 2013 Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested 2014 in the subject dealt with may participate in this preparatory work. International, governmental and non-2015 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely 2016 with the International Organization for Standardization (ISO) in accordance with conditions determined by 2017 agreement between the two organizations. 2018 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international 2019 consensus of opinion on the relevant subjects since each technical committee has representation from all 2020 interested IEC National Committees.

2021 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National 2022 Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC 2023 Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any 2024 misinterpretation by any end user. 2025 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications 2026 transparently to the maximum extent possible in their national and regional publications. Any divergence 2027 between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in 2028 the latter. 2029 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity 2030 assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any 2031 services carried out by independent certification bodies. 2032 6) All users should ensure that they have the latest edition of this publication. 2033 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and 2034 members of its technical committees and IEC National Committees for any personal injury, property damage or 2035 other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and 2036 expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC 2037 Publications.

2038 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is 2039 indispensable for the correct application of this publication. 2040 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of 2041 patent rights. IEC shall not be held responsible for identifying any or all such patent rights. 2042 International Standard IEC 62769-100 has been prepared by subcommittee 65E: Devices and 2043 integration in enterprise systems, of IEC technical committee 65: Industrial-process 2044 measurement, control and automation. 2045 This document is based on FCG_TS62769-150-1_Profiles - ISA100_1.1.0.3, a specification of the 2046 FieldComm Group, PROFIBUS Nutzerorganisation e. V., OPC Foundation and FDT Group. 2047 The text of this International Standard is based on the following documents: 2048 FDIS Report on voting 65E/XX/FDIS 65E/XX/RVD

2049 Full information on the voting for the approval of this International Standard can be found in 2050 the report on voting indicated in the above table. 2051 oSIST prEN 62769-150-1:2018

This document has been drafted in accordance with the ISO/IEC Directives, Part 2. 2052 A list of all parts in the IEC 62769 series, published under the general title Field Device 2053 Integration (FDI), can be found on the IEC website. 2054 The committee has decided that the contents of this document will remain unchanged until the 2055 stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to 2056 the specific document. At this date, the document will be

2057 • reconfirmed, 2058 • withdrawn, 2059 • replaced by a revised edition, or 2060 • amended. 2061

2062 The National Committees are requested to note that for this document the stability date 2063 is 2023. 2064 THIS TEXT IS INCLUDED FOR THE INFORMATION OF THE NATIONAL COMMITTEES AND WILL BE 2065 DELETED AT THE PUBLICATION STAGE. 2066

2071 1 Scope 2072 This International Standard IEC 62769-150-1 specifies an FDI profile for IEC 62734.

2073 2 Normative References 2074 The following documents are referred to in the text in such a way that some or all of their 2075 content constitutes requirements of this document. For dated references, only the edition 2076 cited applies. For undated references, the latest edition of the referenced document (including 2077 any amendments) applies. 2078 IEC 62734:2014, Industrial networks - Wireless communication network and 2079 communication profiles - ISA 100.11a 2080 IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device 2081 Description Language (EDDL) 2082 IEC 62541-100:–, OPC Unified Architecture – Part 100: OPC UA for Devices 2083 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client 2084 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages 2085 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model 2086 IEC 62769-6, Field Device Integration (FDI) – Part 6: FDI Technology Mapping 2087 IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices 2088 3 Terms, definitions, abbreviated terms and acronyms 2089 3.1 Terms and definitions 2090 For the purposes of this document, the terms and definitions given in IEC 62734, IEC 61804 2091 series, IEC 62541-100, IEC 62769-4, IEC 62769-5, and IEC 62769-7 and the following apply. 2092 ISO and IEC maintain terminological databases for use in standardization at the following 2093 addresses:

2094 • IEC Electropedia: available at http://www.electropedia.org/ 2095 • ISO Online browsing platform: available at http://www.iso.org/obp 2096 3.1.1

2097 object 2098 basic entity which defines standardized behavior and features in a ISA100.11a wireless 2099 device 2100 3.2 Abbreviated terms and acronyms 2101 For the purposes of this document, the following abbreviated terms and acronyms apply. 2102 EDD

User Application Process 2109 UAPMO User Application Process Management Object 2110 DMO

Wireless Compliance Institute 2114 4 Conventions 2115 4.1 EDDL syntax 2116 This document specifies content for the EDD component that is part of FDI Communication 2117 Packages. The content using EDDL syntax uses the font Courier New. The EDDL syntax is 2118 used for method signature, variable, data structure and component declarations. 2119 4.2 Capitalizations 2120 The IEC 62769 series use capitalized terms to emphasize that these terms have a FDI 2121 specific meaning.

2122 Some of these terms using an acronym as a prefix for example 2123 • FDI Client, or 2124 • FDI Server. 2125 Some of these terms are compound terms such as: 2126 • Communication Servers, or 2127 • Profile Package. 2128 Parameter names or attributes are concatenated to a single term, where the original terms 2129 start in this term with a capital letter such as: 2130 • ProtocolSupportFile or 2131 • ProtocolType. 2132 Parameter names or attributes can also be constructed by using an underscore character to 2133 concatenate two or more terms such as: 2134 • DEVICE_REV or 2135 • DEVICE_MODEL 2136 5 Profile for ISA100.11a 2137 5.1 General 2138 This profile specifies the protocol specifics needed for FDI Packages describing 2139 communication servers, gateways and devices. 2140 5.2 Catalog profile 2141 5.2.1 Protocol support file 2142 5.2.1.1 Capability file 2143 Each ISA100.11a FDI Device Package shall contain a capability file.

The capability file part is 2144 described in Table 1. 2145 Table 1 – Capability file part 2146 Parameter Description Content Type: txt/plain Root Namespace: Not applicable Source Relationship: http://fdi-cooperation.com/2010/relationships/attachment-protocol Filename: Use file extension .CFF

5.2.1.2 FDI Communication Packages 2148 The same rules as for FDI Device Packages applies. 2149 5.2.2 CommunicationProfile definition 2150 IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. The 2151 ISA100.11a specific value shall be “ISA100_Wireless”.

2153 Not supported in this standard. 2154 5.2.4 Protocol version information 2155 IEC 62769-4 defines an element type named InterfaceT for the Catalog XML schema. The 2156 element type InterfaceT contains an element named Version which is supposed to provide 2157 version information about the applied communication protocol profile. The value has to follow 2158 the IEC 62769-4 defined version information schema defined in the element type VersionT. 2159 ISA100.11a defines the version of the protocol as a value of the parameter 2160 DMO.Comm_SW_Minor_Version. A value of 0 indicates protocol version 2009 and a value of 2161 1 indicates protocol version 2011. The general rule is to use the value of 2162 DMO.Comm_SW_Minor_Version parameter as the major version part of VersionT and the 2163 value “0” for the minor version and build parts Table 2 shows the protocol version information: 2164 Table 2 – Protocol Version Information 2165 Protocol Version InterfaceT Version value ISA100.11a 2009 1.0.0 ISA100.11a 2011 2.0.0 The Protocol Version defined in a package is provided for informational purposes only, and shall not be used to determine the compatibility or applicability of a package to a device.

2166 5.3 Associating a Package with a device 2167 5.3.1 Device type identification mapping 2168 The purpose of device type identification mapping is to enable FDI host systems to compare 2169 the scan result against the topology representation in the Information Model. FDI host 2170 systems shall also be enabled to determine the FDI Device Package that fits for a device 2171 entry contained in the scan result. This will enable the user of an FDI host system to 2172 synchronize the Information Model with the actual installation.

2173 The Communication Server implemented scan service (defined in 5.6.1.7 provides the scan 2174 result through an XML document (the schema is defined in Clause A.5). 2175 The scan result contains device type identification and device instance identification. 2176 FDI host systems comparing the actual network topology configuration against the topology 2177 representation in the Information Model shall be enabled to handle the following situations: 2178 a) The physical Device instance identified at a specific device address is not logically present 2179 in the Information Model (as Instance): Enable the FDI Host system to find the appropriate 2180 FDI Device Package according to the device catalog information. 2181 b) The physical Device instance identified by the device address is logically present in the 2182 Information Model (as Instance): Enable the FDI Host system to compare device type 2183 information presented in scan result (see the identification in Clause A.5) and the device 2184 type specific information of the Instance present in the Information Model. 2185 The FDI Device Package contains device type identification information that can be compared 2186 to scan result based on the Catalog Schema in IEC 62769-4 defining the XML (simple) 2187 element types “DeviceModel” and “Manufacturer”.

As a result of the FDI Package deployment the FDI Package information is then present in the 2189 Information Model as the specified FunctionalGroup Identification containing SerialNumber 2190 and Tag (see 5.4.3). 2191 The mapping between different device identification data sources is described in Table 3. 2192 Since scan results provided by the Communication Server can convey data that is produced 2193 by the device (firmware) the device type identification mapping shall be supported by 2194 providing corresponding data in the FDI Device Package contained Catalog and Information 2195 Model.

2196 Table 3 – Device identification information mapping 2197 FDI Device Package Information Model Communication Server provided scan result Catalog specified type Manufacturer FunctionalGroup: Identification Browse Name: Manufacturer Element (path): ConnectionPoint/Identification Attribute: Manufacturer Catalog specified type DeviceModel FunctionalGroup: Identification Browse Name: DeviceModel Element (path): ConnectionPoint/Identification Attribute: DeviceModel

2198 ISA100.11a device types are uniquely identified by the parameters UAPMO.IDENT_NUMBER 2199 found in the UAPMO. The IDENT_NUMBER parameter contains the Vendor ID, Model ID and 2200 Device Revision. These parameters are used to associate a given device instance to an FDI 2201 Device Package.

These parameters are mapped to the FDI Device Package Catalogue 2202 according to Table 4 . 2203 Table 4 – Device type catalog mapping 2204 Catalog Element ISA 100.11a Mapping Manufacturer element of InterfaceT (see IEC 62769-4) UAPMO.IDENT_NUMBER 0xFFFFFFFF00000000 String format “0xdddddddd” where dddddddd is theVendor ID number in hexadecimal format. DeviceModel element of InterfaceT (see IEC 62769-4) UAPMO.IDENT_NUMBER 0x00000000FFFF0000String format “0xdddd” where dddd is the Model ID number in hexadecimal format. DeviceRevision element ListOfSupportedDeviceRevisionsT (see IEC 62769-4) UAPMO.IDENT_NUMBER 0x000000000000FFFF String format “x.0.0” where x is the Device Revision in decimal format (no leading zeros).

2205 5.3.2 Device type revision mapping 2206 IEC 62769-4 envisions a concept that allows to determine the compatibility between an FDI 2207 Device Package and a Device. IEC 62769-4 specifies a life cycle management process 2208 bearing on a single version information provided for the entire device. Mapping of version 2209 information is defined in Table 4.

2211 5.4 Information Model mapping 2212 5.4.1 ProtocolType definition 2213 In Table 5 a subtype of ProtocolType is defined to identify network communication using this 2214 profile.

Table 5 – Protocol type ISA100.11a 2216 Attribute Value BrowseName ISA100_Wireless IsAbstract False References NodeClass BrowseName

DataType TypeDefinition ModellingRule Subtype of the ProtocolType defined in IEC 62541-100.

2217 5.4.2 DeviceType mapping 2218 Each device type inherits the properties of DeviceType. The mapping of the inherited 2219 properties from DeviceType is defined in Table 6. 2220 Table 6 – Inherited DeviceType property mapping 2221 Property ISA100.11a Mapping SerialNumber DMO.EUI_64 – 8 byte Extended Unique Identifier defined in DMO RevisionCounter UAPMO.Static_Revision_Level

- 2 byte revision counter defined in UAPMO Manufacturer String taken from FDI package catalog (ManufacturerName from PackageT) Model String taken from FDI package catalog (Name of DeviceTypeT, which is a localized name) DeviceManual empty text string (not supported) a DeviceRevision DEV_REV (UAPMO) SoftwareRevision empty string (not defined) HardwareRevision empty string (not defined) a Device manuals are exposed as attachments of the FDI Device Package.

2222 5.4.3 FunctionalGroup identification definition 2223 As defined in IEC 62541-100:–, 5.3, each device representation in the FDI Server hosted 2224 Information Model shall contain a protocol specific FunctionalGroup named Identification. This 2225 FunctionalGroup organizes variables found in the UAPMO of the device type instance.

2227 Table 7 – ISA100.11a wireless device types identification attributes 2228 BrowseName

DataType Mandatory/Optional MANUFAC_ID UInt32 Mandatory DEV_TYPE UInt16 Mandatory DEV_REV UInt16 Mandatory HARDWARE_REV String Optional SOFTWARE_REV String Optional ITS_VER UInt16 Mandatory 5.4.4 BlockType property mapping 2229 ISA100.11a device types are object oriented referred as block-oriented according to 2230 IEC 62541-100. IEC 62769-5 specifies the mapping of EDDL BLOCK_A elements to block 2231 types and instances. 2232 The BLOCK_A maps as a subtype of the topology element BlockType and inherits the 2233 properties per IEC 62541-100. The mapping of the inherited properties of the BlockType is 2234 specified in Table 8 . 2235 oSIST prEN 62769-150-1:2018

Table 8 – Inherited BlockType property mapping 2236 Property ISA100 Wireless Mapping (Object ParameterSet) RevisionCounter ST_REV

ActualMode MODE_BLK.ACTUAL PermittedMode MODE_BLK.PERMITTED NormalMode MODE_BLK.NORMAL TargetMode MODE_BLK.TARGET

2237 5.4.5 Mapping to Object ParameterSet 2238 The ParameterSet is relative to each Object.

The ParameterSet includes all the parameters 2239 found in the PARAMETERS, LOCAL_PARAMETERS and LIST_ITEMS.

2240 The browse name of the parameters found in the PARAMETERS and LOCAL_PARAMETERS 2241 is the member name in the respective lists.

LIST_ITEMS do not have member names; therefore the browse 2243 name of each LIST in the LIST_ITEMS is the item name of the list. 2244 5.5 Topology elements 2245 5.5.1 ConnectionPoint definition 2246 The ConnectionPoint type ConnectionPoint_ISA100_Wireless shall be used to identify 2247 ISA100.11a network communication and is defined in Table 9.

The ConnectionPoint type 2248 ConnectionPoint_ISA100_Wireless is a sub type of the abstract type ConnectionPointType 2249 defined in IEC 62541-100.

2250 The DevAddr property shall be the IPV6 (16 bytes) address of the device. 2251 The DevMfg property shall be the 4-byte UAPMO.Manuf_ID, and can be used to help 2252 automate the process of assigning live devices in the scan list to offline placeholders. 2253 The DevType property shall be the 2-byte UAPMO.Dev_Type, and can be used to help 2254 automate the process of assigning live devices in the scan list to offline placeholders. 2255 The DevRev property shall be the UAPMO.Dev_Rev, and can be used to help automate the 2256 process of assigning live devices in the scan list to offline placeholders. 2257 The DevTag property shall be the DMO.Tag_Name (16 characters). 2258 The DevPollAddr property shall be the DMO.Short_Address (2 bytes). 2259 Table 9 – ConnectionPointType ConnnectionPoint_ISA100_Wireless definition 2260 Attribute Value BrowseName ConnectionPoint_ISA100_Wireless IsAbstract False References NodeClass BrowseName