Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62390: Industrial Automation Device Profile Guideline
Interoperability is the holy grail of industrial automation. With dozens of fieldbus protocols, hundreds of device types, and thousands of manufacturers worldwide, ensuring that devices from different vendors can seamlessly exchange data and work together is a monumental engineering challenge. IEC 62390:2005 — “Industrial automation systems and integration — Device profile guideline” — was developed to address this challenge by providing a common framework and methodology for creating consistent, interoperable device profiles across diverse industrial communication protocols. Although officially withdrawn in recent years, its principles have been absorbed into and continue to influence contemporary device integration standards such as FDI (Field Device Integration), FDT/DTM, and OPC UA Companion Specifications.
Tip While IEC 62390 is no longer an active standard, understanding its profile structure methodology is essential for engineers working with legacy PROFIBUS and PROFINET installations, and the functional block concepts it established remain relevant in modern OPC UA information modeling.
Device Profile Structure and Methodology
IEC 62390 defines a device profile as a standardized description of a device’s capabilities, parameters, communication features, and behavioral characteristics. The standard establishes a three-layer profile architecture: the Device Type layer identifies the category of the device (e.g., variable frequency drive, pressure transmitter, valve actuator); the Functional Block layer defines the logical functions the device performs (e.g., analog input, PID control, diagnostic monitoring); and the Parameter layer specifies the individual data items, their data types, ranges, and access rights.
The profile methodology follows a systematic decomposition approach. Starting from the device’s intended application function, the profile writer identifies the required functional blocks, then maps each block to specific parameters and communication objects. IEC 62390 mandates that each parameter be fully described with its identifier, name, data type (per IEC 61131-3 or ISO/IEC 11404), unit of measurement (per ISO 80000), value range, default value, and access rights (read-only, write-only, read-write). Communication-specific mapping — how the parameter appears on a particular fieldbus protocol — is defined in separate communication profile annexes, maintaining a clean separation between device functionality and network transport.
| Profile Layer | Description | Example (Pressure Transmitter) | Standardization Level |
|---|---|---|---|
| Device Type | High-level device classification | Pressure Transmitter (24P) | IEC 62390 |
| Functional Block | Logical function grouping | Analog Input FB, Diagnostic FB | Protocol-specific |
| Parameter | Individual data item definition | PV (Process Value), Scaled range 0–100 bar | Manufacturer-extensible |
| Communication Mapping | Protocol-specific data packaging | PROFIBUS PA profile 3.0 mapping | Protocol-specific |
Functional Block Concepts and Parameter Modeling
The functional block concept in IEC 62390 draws heavily from IEC 61131-3 (Programmable Logic Controllers) and IEC 61804 (Function Blocks for Process Control). Each functional block encapsulates a specific capability of the device, complete with its input parameters, output parameters, and internal configuration data. The standard defines several standard block types: Analog Input (AI), Analog Output (AO), Digital Input (DI), Digital Output (DO), Controller (CTL), and Diagnostic (DIAG). Each block type has a predefined set of mandatory and optional parameters, ensuring that a pressure transmitter’s Analog Input block presents the same basic parameter structure regardless of the manufacturer.
Parameter modeling in IEC 62390 is particularly notable for its attention to semantic richness. Beyond simple data type definitions, each parameter carries a classification attribute indicating its operational significance: Configuration parameters (C) are set during commissioning and rarely changed, while Dynamic parameters (D) change during normal operation. The standard also defines a hierarchical parameter numbering scheme — the “slot/subslot/index” model — which later became a foundational concept in PROFINET IO device modeling. This hierarchical approach enables efficient data access over fieldbus networks with limited bandwidth, as the master can request entire parameter groups in a single transaction rather than polling individual items.
Warning One common pitfall in device profile implementation is inconsistent parameter classification. IEC 62390 clearly distinguishes between configuration parameters (set once during commissioning) and observable parameters (read during operation). Misclassifying a configuration parameter as observable can lead to unnecessary bus traffic, while the reverse can prevent critical runtime adjustments.
Legacy Relevance and Migration Pathways
Although IEC 62390 has been withdrawn, its influence on modern industrial automation standards is substantial. The device profile methodology it established directly informed the development of PROFIBUS PA profile 3.0 and 4.0, PROFINET IO device modeling, and the HART Field Device Specification (FDS). Engineers maintaining installations based on these protocols will inevitably encounter profile structures rooted in IEC 62390 principles. More importantly, the conceptual framework — particularly the functional block decomposition and parameter hierarchy — has been carried forward into the FDI (IEC 62769) and OPC UA (IEC 62541) companion specification development processes.
For organizations planning migration from legacy fieldbus systems to Ethernet-based industrial communication (PROFINET, EtherNet/IP, OPC UA), understanding IEC 62390’s profile model provides a clear roadmap for translating existing device descriptions into modern information models. The parameter hierarchy maps naturally to OPC UA’s node-based address space, and the functional block concept aligns with OPC UA’s object-oriented type system. Tools exist that can automatically transform IEC 62390-style electronic device descriptions (EDD) into OPC UA information models, preserving the engineering investment in existing device profile definitions.
Good Practice When migrating legacy device profiles to OPC UA, maintain the same slot/subslot/index hierarchical parameter numbering from IEC 62390 as a namespace in the OPC UA address space. This practice preserves backward compatibility with existing engineering tools and operator training documentation.
| Modern Standard | IEC Number | Relationship to IEC 62390 |
|---|---|---|
| FDI (Field Device Integration) | IEC 62769 | Replaced profile methodology with package-based integration |
| FDT/DTM | IEC 62453 | Adopted profile parameter hierarchy |
| OPC UA Companion Specs | IEC 62541 | Functional block concept mapped to object types |
| PROFINET IO Device Model | IEC 61784 | Extended slot/subslot/index model from IEC 62390 |
Frequently Asked Questions
Q1: Why was IEC 62390 withdrawn, and what replaced it?
IEC 62390 was withdrawn because the device profile landscape evolved toward more comprehensive integration frameworks. FDI (IEC 62769) and FDT/DTM (IEC 62453) offer richer capabilities including graphical user interfaces, advanced diagnostics, and web services. However, the core profile structuring concepts from IEC 62390 live on within these newer standards rather than being replaced entirely.
Q2: Does IEC 62390 apply to wireless industrial automation devices?
The original standard was developed primarily for wired fieldbus protocols. However, its profile methodology is protocol-agnostic and has been successfully applied to WirelessHART and ISA100.11a device descriptions. The functional block and parameter hierarchy concepts translate naturally to wireless profiles, though communication-specific mapping annexes need to be developed separately.
Q3: How does IEC 62390 relate to electronic device descriptions (EDD)?
IEC 62390 provides the conceptual framework for device profiles, while EDD (IEC 61804-3) is a specific implementation language for encoding those profiles. Think of IEC 62390 as the schema or template specification, and EDD as the machine-readable file format that instantiates the schema for a specific device. EDD files for PROFIBUS and HART devices are direct implementations of IEC 62390-style profiles.
Q4: Can new device development still reference IEC 62390?
While the standard is withdrawn, its methodology can still serve as an internal reference for profile structure design. However, for new development, it is recommended to directly adopt FDI packages (IEC 62769) or OPC UA information models, which represent the modern evolution of the concepts IEC 62390 originally formalized.
