Controller Data Update Mediator for Facility Monitoring Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The facility monitoring system disclosed in Patent Literature 1 fails to collect and modify separately managed data effectively, as it only redirects requests and lacks simultaneous data update capabilities, leading to potential data inconsistencies and unreflected modifications.
Innovation Solution
A facility device system with a first and second controller connected via a network, where the first controller acquires and sends post-modification data to the second controller, and the second controller determines if modifications have been made within a set time period, sending permission or rejection notifications to allow or deny data updates, ensuring data consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the monitoring server device merely redirects requests from the monitoring information display device to the monitoring device, then the system structure is simple, but the contents of the file cannot be modified
Solution Approach 1:
The monitoring server device acts as an intermediary between the monitoring information display device and the monitoring device. It not only redirects requests but also processes and modifies file contents before returning them. This mediator role enables both simple system structure and data modification capability to coexist.
2Loss of information
If the monitoring server device collects data from multiple monitoring devices, then data consolidation is achieved, but simultaneous updates from multiple devices cause data inconsistency
Solution Approach 1:
The monitoring server device performs preliminary actions by setting a waiting-time period before processing data updates. When a monitoring device sends updated data, the server waits for a predetermined time to check if other devices also send updates. This preliminary waiting action prevents data inconsistency by ensuring all simultaneous updates are captured before processing.
3Reliability
If the waiting-time period is set long, then data consistency is improved, but the response time increases
Solution Approach 1:
The system dynamically adjusts the waiting-time period parameter based on the specific update scenario. By changing this time parameter, the system balances between ensuring data consistency (longer time) and maintaining responsive performance (shorter time), optimizing both reliability and response time.
Data Source
AI summary
A schedule data acquisition requestor requests and acquires schedule data from a sub controller. When a modification to the acquired schedule data is made, a schedule data update requestor sends the modified schedule data to the sub controller and requests an update. A schedule data update processor sends a permission notification to a main controller in response to the update request and writes the modified schedule data onto its own flash memory. Conversely, when a rejection notification is sent from the sub controller, the schedule data update requestor displays a warning message and new schedule data on a screen.