Control System Engineering Data Caching for Large-Scale UI Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interfaces for managing control system engineering data are inefficient, particularly when dealing with large datasets, as they require multiple filters and scrolling, leading to laborious data retrieval and potential errors, and do not effectively manage memory resources or track data modifications.
Innovation Solution
Implementing a processor-based interface control server that uses a temporary database to store and manage engineering data, allowing for on-demand retrieval and caching of data subsets, enabling efficient data navigation and modification tracking without overwhelming system memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If all engineering data is loaded into internal memory for viewing and modification, then data access speed is improved, but system memory consumption increases significantly
Solution Approach 1:
The patent segments the engineering data into multiple pages, where each page contains a subset of data records (e.g., 50,000 records per page). Only the currently viewed page is loaded into internal memory, while other pages remain in the temporary database. This segmentation allows fast access to the active page while keeping overall memory consumption manageable.
Solution Approach 2:
The patent pre-loads the currently viewed page of engineering data into internal memory before the user requests it. When a user navigates to a specific page, that page's data is retrieved from the temporary database and loaded into memory in advance, ensuring fast access when the user views or modifies the data.
2Reliability
If a maximum limit is imposed on the number of data records that can be viewed simultaneously, then system stability is improved, but data completeness deteriorates
Solution Approach 1:
The patent adds a temporal dimension to data access by implementing pagination with navigation controls. Instead of limiting users to viewing only a small subset of data at once, the system allows users to navigate through multiple pages of data sequentially. This transforms the problem from a spatial limitation (memory capacity) to a temporal solution (sequential access across time), maintaining system stability while providing access to complete data sets.
3Measurement precision
If multiple filters are applied to retrieve specific engineering data, then data retrieval precision is improved, but operation complexity increases
Solution Approach 1:
The patent introduces a temporary database as an intermediary layer between the engineering data repository and the user interface. This temporary database pre-stores engineering data in a structured format with embedded navigation capabilities. Instead of requiring users to apply multiple filters to the source repository, the system provides direct navigation to specific pages and subsets of data through the intermediary, simplifying the retrieval process while maintaining precision.
4Quantity of substance
If the maximum number of data records is increased to handle larger datasets, then data capacity is improved, but memory handling performance deteriorates
Solution Approach 1:
The patent segments the large engineering data set into multiple manageable pages, each containing a controlled number of records (e.g., 50,000 records per page). The temporary database stores these segmented pages, and the system loads only the required page into internal memory at any given time. This segmentation enables the system to handle large data capacities while maintaining efficient memory handling performance by avoiding the need to load entire large datasets into memory simultaneously.
Data Source
AI summary
The invention enables managing of control system engineering data for the purposes of implementing a control system user interface. In an embodiment, implementing the invention comprises (i) receiving data retrieval parameters, (ii) instantiating a temporary database, comprising an original data table and a modified data table, (iii) retrieving, based on the data retrieval parameters, a set of engineering data from one or more engineering data repositories, (iv) storing the retrieved set of engineering data within the original data table, and (v) responsive to an instruction to display a first sub-set of engineering data, (a) retrieving the first sub-set of engineering data from the original data table, (b) storing the first sub-set of engineering data within an internal cache memory, and (c) retrieving the first sub-set of engineering data from the internal cache memory and displaying the data.


