Client Server Configuration Tool for Field Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In automation systems, the existing client/server architecture for configuring field devices leads to bottlenecks in communication, resulting in delayed user interface responses due to the need for intensive interaction between the client and server for every parameter change during configuration.
Innovation Solution
A configuration tool is implemented in a client/server architecture that uses a field-device-type-specific information package to validate and process configuration data locally on the client, reducing the need for repeated client/server communication by validating data directly on the client and only transmitting validated changes to the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If intensive interaction between client and server is performed for every parameter change during configuration, then configuration data can be validated and processed centrally, but communication bottlenecks occur and user interface response time increases
Solution Approach 1:
The client performs preliminary validation of configuration data locally before transmitting to the server. The client validates parameter changes against the EDD and business logic rules in advance, so that only validated data needs server processing, reducing communication rounds and improving response time while maintaining validation reliability
Solution Approach 2:
The validation and processing functions are segmented between client and server. The client handles local validation of configuration parameters against EDD and business logic, while the server handles final integration and storage. This segmentation allows parallel processing and reduces the need for intensive back-and-forth communication
2Stability of the object's composition
If configuration data is transmitted repeatedly between client and server during editing, then data consistency can be maintained, but communication overhead increases and bottlenecks occur
Solution Approach 1:
The client performs preliminary validation and prepares configuration data locally before transmission. By validating data in advance and only transmitting necessary changes, the system maintains data consistency while reducing communication frequency and overhead, thereby improving configuration speed
Solution Approach 2:
The system implements feedback mechanisms where the server confirms receipt and acceptance of configuration data. The client receives feedback from the server about the status of transmitted data, allowing it to maintain local copies and reduce repeated transmissions while ensuring consistency
Data Source
AI summary
A method/device for managing/configuring field devices in an automation installation with a configuration tool designed to physically identify a field device therein, to logically incorporate it into, and configure it in, the automation installation, wherein the configuration tool to uses a prescribed field-device-type-specific information package describing functions and data of the field device at least partially and wherein the configuration tool has a server and a client, the server being designed to integrate received configuration data with the field-device-type-specific information package into an information package and to validate and process the information package with a piece of validation logic, and the client having a user interface for taking the configuration data. To avoid bottlenecks in the client/server communication, the client is equipped with an information package instance, and is designed to integrate taken configuration data into a package and validate the package. The server is designed to take validated packages.