Field Device Function Block Security and Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Field devices in energy systems face challenges in configuring specific functions for customers while avoiding oversizing and ensuring cost-effectiveness, as they need to provide all desired functions without exceeding the customer's willingness to pay.
Innovation Solution
A field device with a security mechanism that checks and blocks device functions based on an identification block, allowing only enabled functions to be executed, and uses XML format for function description blocks, enabling easy enabling or disabling of functions through software configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the field device provides all possible functions to meet every customer request, then the device functionality and versatility are improved, but the device complexity and cost increase
Solution Approach 1:
The patent segments the device functions into individual function blocks that can be independently selected and configured. Each function is modular and can be enabled or disabled separately, allowing the device to provide only the specific functions needed by each customer rather than all possible functions, thus reducing complexity while maintaining versatility.
Solution Approach 2:
The patent implements dynamic configuration of device functions through software-based enabling and disabling of function blocks. The device can adapt its functionality dynamically based on customer requirements without hardware changes, allowing the same physical device to serve multiple application scenarios with different function sets.
2Adaptability or versatility
If the field device provides all possible functions to meet every customer request, then the device versatility is improved, but the manufacturing and pricing complexity increase
Solution Approach 1:
The patent creates a universal device platform that can perform multiple functions through software configuration rather than hardware variants. A single device type with all possible function blocks integrated can be manufactured once, then customized for different customers by enabling/disabling specific functions via software, eliminating the need to manufacture multiple device variants.
Solution Approach 2:
The patent uses parameter-based configuration where device functionality is controlled by enabling/disabling parameters (function blocks) rather than physical hardware changes. This allows the same manufactured device to be adapted to different customer needs by changing software parameters, simplifying manufacturing while maintaining versatility.
3Reliability
If a security device blocks execution of non-enabled functions, then device security and proper licensing are improved, but the device operation complexity increases
Solution Approach 1:
The security device automatically checks and controls execution of function blocks without requiring manual intervention. The system self-manages the enabling/disabling of functions based on configuration, and the security mechanism operates autonomously to block non-enabled functions, reducing the operational burden on users while maintaining security.
Solution Approach 2:
The security device provides feedback by checking whether each function block is enabled before execution and blocking it if not enabled. This automatic feedback mechanism ensures security requirements are met without requiring users to manually verify function availability, simplifying operation while maintaining reliability.
Data Source
Figure 1~2
Figure 3~4
AI summary
The invention relates to a field device (10), in particular a protective device, having a microprocessor arrangement (20) which executes a program module (PM), which defines the device function, during operation of the field device. The invention provides for the field device to have a protection device (40) which is configured in such a manner that it checks whether a function description block (FB), which has been input and describes a desired device function, describes an enabled device function and, in the case of a device function which has not been enabled, blocks execution of said function and, in the case of a device function which has been enabled, enables execution of said function.