Emulated DTMs for Distributed Field Device Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional process control systems face limitations in distributed control due to the requirement that device and communication DTMs must be instantiated on the same physical device, making it difficult to manage and configure field devices across diverse geographical areas and networks.
Innovation Solution
The system employs emulated device and communication DTMs to enable distributed control, allowing device DTMs and communication DTMs to interact and communicate remotely, using a client and a communication interface component with emulated DTMs to abstract communication mechanisms and protocols from the host application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device DTMs and communication DTMs are instantiated on the same physical device, then communication reliability is improved, but system flexibility and distributed control capability deteriorate
Solution Approach 1:
The system segments the DTM functionality by introducing emulator components that separate the device DTM instantiation from the communication DTM instantiation. The first emulator emulates the communication DTM at the first location, while the second emulator emulates the device DTM at the second location, allowing spatial distribution while maintaining functional integrity
Solution Approach 2:
Emulator components act as intermediaries between the physically separated device DTM and communication DTM. The first emulator receives requests from the device manager and forwards them to the second emulator, which then communicates with the field device, bridging the spatial gap while maintaining protocol compliance
2Adaptability or versatility
If device DTMs and communication DTMs are distributed across different physical locations, then system flexibility and remote management are improved, but communication complexity and protocol compatibility deteriorate
Solution Approach 1:
The emulator components create virtual copies of the DTM functionality at remote locations. The first emulator copies the communication DTM interface at the first location, and the second emulator copies the device DTM interface at the second location, allowing remote access without requiring physical co-location
Solution Approach 2:
The emulator components provide universal interface functionality that works across different physical locations and communication protocols. The emulators handle protocol translation and adaptation, allowing the device manager to interact with field devices through a standardized interface regardless of the underlying communication protocol
Data Source
AI summary
A system includes a client and an interface component. The client includes (i) a device manager associated with a field device in a process control system and (ii) a first emulator configured to emulate a communication manager. The device manager defines a user interface associated with the field device. The interface component includes (i) a second emulator configured to emulate the device manager and (ii) the communication manager. The communication manager is configured to communicate with the field device over a communication link using a specified protocol. The client is physically separated from the interface component. The communication manager could represent a communication Device Type Manager (DTM), and the device manager could represent a device DTM. Also, the first emulator could emulate at least some functions of the communication DTM, and the second emulator could emulate at least some functions of the device DTM.


