Dependency Graph Asset Status Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current asset management systems are inefficient in tracking and troubleshooting complex assets, as they require manual expertise and focus on physical file-level structures, failing to provide comprehensive status reporting for conceptual assets like characters or shots, and miss changes in unmanaged files.
Innovation Solution
The solution involves creating a dependency graph to derive asset status, allowing for the reporting of individual file and aggregate asset statuses, with features like relevance-weighted result filtering and collection of multiply-rooted assets into an asset tree, enabling querying of related assets and aggregating status data for root assets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual tracking and troubleshooting methods are used for complex assets, then users can identify asset issues, but the process requires significant time and expert knowledge
Solution Approach 1:
The patent replaces manual mechanical tracking methods with an automated computer-based system that uses dependency graphs and status data aggregation to automatically determine asset status, eliminating the need for manual expertise and significantly reducing time requirements
Solution Approach 2:
The patent introduces a dependency graph as an intermediary structure that automatically tracks relationships between assets and files, serving as a mediator that computes and propagates status information without requiring direct manual intervention
2Loss of information
If file-level asset management is focused on, then physical file status can be tracked, but conceptual aggregate assets like characters or shots cannot be comprehensively reported
Solution Approach 1:
The patent implements a nested structure where dependency graphs contain multiple levels of aggregation - individual files are nested within asset nodes, which are nested within aggregate asset nodes, allowing comprehensive tracking from file-level to conceptual asset-level in a hierarchical manner
Solution Approach 2:
The patent creates a universal asset management system that handles both individual files and aggregate assets through the same dependency graph infrastructure, enabling the system to report on any level of abstraction without requiring separate management mechanisms
3Reliability
If changes in managed files are tracked, then file-level modifications are detected, but changes in unmanaged files are missed
Solution Approach 1:
The patent implements feedback mechanisms where the system continuously monitors both managed and unmanaged files associated with assets, automatically detecting changes and updating dependency graphs to reflect current asset status regardless of whether files are formally managed
4Loss of information
If comprehensive asset status reporting is implemented, then complete asset information is provided, but the system complexity increases
Solution Approach 1:
The patent segments the asset management system into distinct functional components - dependency graph construction, status data collection, aggregation logic, and reporting modules - allowing comprehensive functionality to be achieved through modular, manageable segments rather than a monolithic complex system
Data Source
AI summary
A method for a computer system includes determining a dependency graph for a user-selected aggregate asset comprising a plurality of nodes, determining node types for the plurality of nodes, when a first node of the plurality of nodes comprises a file-level asset node, the method includes determining first status data associated with the first node, when a second node of the plurality of nodes comprises an aggregate asset node, the method includes determining a plurality of file-level asset nodes that are children nodes of the aggregate asset node, and determining status data associated with each of the plurality of file-level asset nodes, aggregating the first status data and the status data associated with the plurality of file-level asset nodes to form status data for the aggregate asset for the user.


