FDI Host Integration of OPC UA Devices for Online and Offline Support

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Field Device Integration (FDI) systems face challenges in efficiently supporting advanced field devices that use OPC UA and OPC UAFX communication protocols, requiring significant effort for device model development and configuration, especially in both online and offline environments.

Innovation Solution

The proposed FDI system leverages OPC UA and OPC UAFX device and user interface models to reduce the complexity of FDI package configuration, allowing for consistent online and offline support by minimizing the need for separate device models and utilizing the field device's own communication structure, enabling scalable device simulation and reduced programming efforts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional FDI systems support advanced field devices using OPC UA and OPC UAFX protocols, then device integration capability is improved, but device complexity and configuration effort increase significantly

Engineering Contradiction:
Improvedevice integration capabilityVSAvoidconfiguration effort
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The FDI host is designed to universally support multiple communication protocols (HART, Fieldbus, OPC UA, OPC UAFX) through a single integrated platform. The system uses a common device model structure that can adapt to different protocols, eliminating the need for separate configuration systems for each protocol type and reducing overall configuration complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system dynamically changes communication parameters based on the detected protocol type. When an OPC UA or OPC UAFX device is detected, the FDI host automatically adjusts its communication interface and data model interpretation accordingly, allowing the same hardware platform to handle diverse protocols without manual reconfiguration.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If separate device models are created for online and offline environments, then environment-specific functionality is improved, but development time and programming effort increase

Engineering Contradiction:
Improveenvironment-specific functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges online and offline device models into a single unified device model structure. The FDI host can dynamically switch between online and offline modes using the same underlying device model, eliminating the need to maintain separate model versions and reducing development time while preserving environment-specific functionality through mode switching.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The device model is designed to be dynamic rather than static, allowing it to adapt its behavior based on the operational context (online or offline). The same device model can represent a field device in both online operation and offline simulation, with the system dynamically adjusting its interaction mode based on current operational requirements.

Inventive Principle:
Principle #15Dynamics

3Manufacturing precision

If comprehensive device models are developed for all field devices, then integration accuracy is improved, but programming effort and development activities increase

Engineering Contradiction:
Improveintegration accuracyVSAvoidprogramming effort
Core Design Contradiction:
Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The system uses standardized device model templates that can be copied and instantiated for different field devices. Rather than creating unique comprehensive models for each device, the FDI host uses protocol-specific templates (including OPC UA and OPC UAFX templates) that capture essential device characteristics, reducing programming effort while maintaining sufficient integration accuracy.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The device models implement only the essential parameters and functions needed for typical FDI operations rather than comprehensive coverage of all possible device features. This partial modeling approach achieves sufficient integration accuracy for most applications while significantly reducing development effort, allowing the system to handle advanced protocols without requiring exhaustive device documentation.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240411297A1Enhanced on-line field device integration system
Publication Date: 2024.12.12 FIELDCOMM GROUP INC
  • US20240411297A1 patent drawing
  • US20240411297A1 patent drawing
  • US20240411297A1 patent drawing

AI summary

A field device integration (FDI) system is configured to support the use of OPC UA, OPC UA FX and other flexible (or open) information model based communication protocols in an FDI environment or with an FDI host in a manner that enables the FDI host to fully integrate the support of OPC UA devices with other devices, including other devices that do and that do not support the OPC UA communication protocol. The FDI system design reduces FDI package configuration activities for the OPC UA devices and optimizes the use of the OPC UA data models developed for the OPC UA device within the FDI environment. Still further, the FDI system enables an FDI host to support device communications in both an on-line environment, in which the devices are communicatively connected to the FDI host while operating on-line in a process or factory environment, and in an off-line environment, in which the FDI system simulates or models the operation of a device that is not currently communicatively connected to the FDI host.