Project Trend Analysis via On-Demand Snapshot Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional project portfolio management systems rely on storing snapshots of project data, which consume large amounts of memory and limit analysis granularity, as they often update existing snapshots instead of creating new ones, resulting in the loss of original data and reduced tracking capabilities.
Innovation Solution
The system maintains project tracking tables and generates snapshots on demand by accessing a history table for version history, a transaction table for transaction records, and a base table for current records, allowing for trend analysis at any granularity without storing copies of project data, thereby reducing memory requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If snapshots of project data are stored to enable trend analysis, then analysis capability is improved, but memory consumption increases
Solution Approach 1:
The patent extracts only the necessary historical data elements (transaction records, version histories, base records) from complete project snapshots. Instead of storing entire project snapshots, the system extracts and stores only the minimal required data in specialized tables (transaction table, history table, base table), significantly reducing memory consumption while maintaining trend analysis capability.
Solution Approach 2:
The patent segments project data storage into multiple specialized tables rather than storing monolithic snapshots. The data is divided into: (1) transaction table for recording changes, (2) history table for version tracking, and (3) base table for current state. This segmentation allows efficient storage and retrieval of historical data without duplicating entire project states.
2Quantity of substance
If existing snapshots are updated to manage memory, then memory usage is reduced, but original data is lost and tracking capability is reduced
Solution Approach 1:
The patent implements preliminary action by creating immutable records of project data changes before any updates occur. Transaction records are created to capture the state of data before modifications, and history tables store version information in advance. This preliminary recording ensures that original data is preserved and can be retrieved later, preventing data loss while managing memory usage.
Solution Approach 2:
The patent creates selective copies of project data in specialized storage structures rather than updating existing snapshots. Transaction tables copy change information, history tables copy version data, and base tables copy current state. These copies are maintained separately and immutably, allowing memory management without loss of original information.
3Measurement precision
If snapshots are stored at high granularity, then analysis precision is improved, but memory consumption increases
Solution Approach 1:
The patent applies local quality by storing different types of data with different levels of detail in appropriate tables. Transaction tables store detailed change information at high granularity, history tables store version information, and base tables store current state data. This allows the system to provide high-granularity analysis where needed while optimizing overall storage efficiency through specialized data organization.
Data Source
AI summary
Systems, methods, and other embodiments associated with history and scenario data tracking are described. In one embodiment, a method includes receiving a request for trending analysis on project data. The request includes a trend range and a time basis. The method also includes selecting a set of records that fall within the trend range from an item table associated with the time basis, and generating a snapshot of the project data for each effective time in each selected record in the item table. The generating includes executing a trend view on (i) a history table storing a version history for every record modified, (ii) a transaction table storing a transaction history for every record modified, and (iii) a base table storing base records corresponding to a current version of the records to create the snapshot. The snapshots of project data are returned in response to the request for trending analysis.