GB/T 45283.3-2025 Configuration file exchange for industrial control system HMI―Part 3: Extended exchange description English, Anglais, Englisch, Inglés, えいご
This is a draft translation for reference among interesting stakeholders. The finalized translation (passing through draft translation, self-check, revision and verification) will be delivered upon being ordered.
ICS 25.040.40
CCS N 18
National Standard of the People's Republic of China
GB/T 45823.3-2025
Configuration file exchange for industrial control system HMI – Part 3: Extended exchange description
工业控制系统人机接口组态文件交互 第3部分：扩展交互描述
(English Translation)
Issue date: 2025⁃02⁃28 Implementation date: 2025⁃09⁃01
Issued by the State Administration for Market Regulation
the Standardization Administration of the People's Republic of China
Contents
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Extended interactive file description
6 IO devices scalable configuration
7 Variable IO link extensible configuration
8 Function
9 Primitive template
Annex A (Normative) Extended interactive configuration XML file schema
Annex B (Informative) Extended configuration of commonly used IO devices
Annex C (Informative) Common variable IO link extension configuration
Annex D (Informative) Commonly used function declarations
Bibliography
Configuration file exchange for industrial control system HMI – Part 3: Extended exchange description
1 Scope
This document specifies the file structure of extended interactive file of general human-machine interface (HMI) software configuration of industrial control system, and standardizes the XML description format of elements such as extensible configuration of IO equipment, extensible configuration of variable IO link, function, primitive template, etc.
This document is suitable for the interactive engineering of controller man-machine interface extension configuration file in process industry, discrete industry and other industries. The design, development and software function verification of human-machine interface software extension interactive file export/import tool are used for reference.
2 Normative references
The following documents contain requirements which, through reference in this text, constitute provisions 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.
GB/T 45283.2-2025 Configuration file exchange for industrial control system HMI - Part 2: Basic exchange description
3 Terms and definitions
There are no terms and definitions to be defined in this document.
4 Abbreviations
For the purposes of this document, the following abbreviations apply.
IO: Input/Output
OPC: OLE for Process Control
UA: Unified Architecture
XML: Extensible Markup Language
5 Extended interactive file description
5.1 Extended configuration information
The extended interactive information of man-machine interface of industrial control system consists of four parts: extensible configuration of IO equipment, extensible configuration of IO link, function and primitive template. The extended interactive configuration XML file schema shall be as specified in Annex A.
5.2 Extended interaction description file description
The extended interaction description file is used to describe the extended configuration information of the human-machine interface of the industrial control system. On the basis of the basic interaction file, the extended definition and function definition of variable links related to IO device configuration and device drivers are expanded. The file structure is consistent with the basic interaction nodes. Consistent, see Clause 6 of GB/T 45283.2-2025 for details.
6 IO devices scalable configuration
6.1 Configuration IODeviceExtension
The element "IODeviceExtension", as an extended sub-element of the IO device driver configuration "IODevice", is an element specific to the communication protocol "protocol" or the vendor "device, or an element whose attributes are specific to the protocol or the vendor. Refer to Appendix B for the definition of IO device extension configuration.
6.2 Extensible general description method of IO device configuration
The element "IODeviceExtension" description should comply with the following rules.
a) The extended information consists of one or more sets of key-value pairs (attribute names and attribute values).
b) The attribute name shall be subject to the English name given by the manufacturer. If there is no English name, the Chinese name Pinyin given by the manufacturer shall be used. The naming rules for attribute names shall be based on 5.2 of GB/T 45283.2-2025.
c) The attribute value can be an integer or an enumerated quantity. If the integer value represents the sequence number, the integer quantity starts from 0. The enumerator is the exact enumerated value name expressed as a string.
d) If there is a hierarchical division. The principles of classification are: Major category first, subcategory later. Each classification corresponds to a node of XML, and the subordinate classification node is the child node of its superior classification node. The XML file structure of device extensible configuration information is shown in Appendix B.
7 variable IO link extensible configuration
7.1 Variable IO link extension configuration "IOLinkExtension"
The element "IOLinkExtension", as the extension node name of the IO device driver configuration "IOLink" element, is a child element of the element "IOLink" element and is used to describe the extension configuration information of the IO link. Its attributes are specific to the protocol or vendor. The IO link configuration definition is provided in Annex C.
7.2 Variable IO Link Configuration Extensible General Description Method
The "IOLinkExtension" description shall comply with the following rules.
a) The extended information consists of one or more sets of key-value pairs (attribute names and attribute values).
b) The attribute name shall be subject to the English name given by the manufacturer. If there is no name, the Chinese character name given by the manufacturer shall be used. The naming rules for attribute names shall be based on 5.2 of GB/T 45283.2-2025.
c) The attribute value can be an integer or an enumerated quantity. If the integer value represents the sequence number, the integer quantity starts from 0. The enumerator is the exact enumerated value name expressed as a string.
d) If there is a hierarchical division. The principle of classification is: major categories first, subcategories later. Each classification corresponds to a node of XML, and the subordinate classification node is the child node of its superior classification node. The class name shall be based on the English name given by the English manufacturer. If there is no English name, the Chinese character name given by the manufacturer shall be used.
8 Function
8.1 Function set "Functions ''
The element "Functions" describes a collection of user-defined Functions in the configuration project, including one or more custom Function "Function" elements. Users can encapsulate some public and general operations or operations as Functions, which are called and executed by scripts. Its content is shown in Figure 1.
