Semantic Field Device Access Through Ruleset-Based Parameter Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for accessing field device parameters in industrial plants face challenges when there is no one-to-one mapping between semantic identifiers and field device parameters, limiting the ability to retrieve or write values efficiently.
Innovation Solution
A computer-implemented method that uses a ruleset to translate semantic identifiers into parameter values, allowing for the retrieval and writing of values by generating computer-executable code that computes the sought values from dependent parameter values, even in cases where there is no one-to-one mapping, utilizing a broker entity or engineering tool to manage access and conversion between different engineering units.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If semantic identifiers are used to access field device parameters, then unified access to parameters across different devices is improved, but the system cannot handle cases where one semantic identifier maps to multiple parameters or requires computation
Solution Approach 1:
The patent introduces a broker entity as an intermediary between the DCS and field devices. This broker maintains a ruleset that defines mappings between semantic identifiers and field device parameters, including complex mappings requiring multiple parameters or computations. The broker translates semantic identifier requests into appropriate field device parameter accesses, handling complexity internally while presenting a unified interface to the DCS.
Solution Approach 2:
The system enables self-service by allowing the broker to automatically resolve semantic identifier to parameter mappings using the ruleset. The broker autonomously determines which field device parameters correspond to a given semantic identifier and performs necessary computations, eliminating the need for manual configuration or intervention when parameter mappings change or require complex resolution.
2Loss of information
If multiple field device parameters are mapped to a single semantic identifier, then comprehensive data access is improved, but the retrieval process becomes more complex
Solution Approach 1:
The broker entity serves as an intermediary that manages the mapping between semantic identifiers and multiple field device parameters. When a semantic identifier is requested, the broker consults the ruleset to determine all associated parameters, retrieves them, and performs any necessary computations to provide the complete information set to the DCS, thereby maintaining comprehensive data access while managing retrieval complexity centrally.
Solution Approach 2:
The system segments the complex retrieval process into distinct components: the ruleset storing mapping relationships, the broker entity handling translation and coordination, and the field devices providing raw parameter data. This segmentation allows each component to specialize in its function, making the overall system more manageable despite handling complex many-to-one mappings.
3Ease of operation
If semantic identifiers are used for field device access, then ease of operation is improved, but handling diverse measurement units and terminology across devices becomes challenging
Solution Approach 1:
The broker entity provides a universal interface that handles diverse field devices through a common mechanism. The ruleset stores device-specific mapping information, allowing the same semantic identifier to map to different parameters on different device types. This universal approach maintains ease of operation while accommodating device diversity, as the broker automatically adapts the translation process based on the specific device and parameter being accessed.
Solution Approach 2:
The system applies local quality by allowing different mapping rules to be defined for different field devices and parameters within the same ruleset. Each semantic identifier can have device-specific or parameter-specific mappings that tailor the translation process to local requirements, such as different measurement units or terminology conventions, while maintaining a unified access interface.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A computer-implemented method (100) to assist retrieving one or more parameter values (4) from a field device (1), comprising the steps of: • receiving (110) a command to read a value (2) of a variable from the field device (1), wherein the field device (1) is designated by a field device identifier (1a) and the variable is designated by a semantic identifier (2a); • retrieving (120), based on the field device identifier (1a) and the semantic identifier (2a), from a ruleset (3), at least one rule (3a) indicating a dependency of the sought value (2) of the variable on one or more parameter values (4) of the field device (1); and • proceeding to (130a), and/or generating (130b) computer-executable code (9a) configured to: ∘ obtain (140) the parameter values (4) of the field device (1) on which the sought value (2) of the variable depends according to the at least one rule (3a); and ∘ compute (150) the sought value (2) of the variable from these parameter values (4) according to the at least one rule (3a).