Project Visualization System for Complex Dependencies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing project management visualization tools are limited in their ability to handle complex multi-level dependencies, are often specific to particular delivery types, lack support for hybrid methodologies, and fail to clearly visualize dependencies and their impacts across project phases.

Innovation Solution

A project visualization system that uses a data fabric to store and synchronize project data, generating graphical views to depict complex dependencies and associations, and employs an artificial intelligence model to recommend suitable views based on natural language problem statements, enabling real-time data-driven decision-making.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing project management visualization tools are used, then basic project data can be displayed, but they cannot effectively handle complex multi-level dependencies

Engineering Contradiction:
Improveability to handle complex multi-level dependenciesVSAvoidvisualization accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments complex project dependencies into hierarchical levels, displaying them in a structured format that can handle multi-level relationships. The system breaks down complex dependency networks into manageable segments that can be visualized and analyzed effectively, resolving the contradiction between handling complexity and maintaining visualization reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces additional visual dimensions to represent dependency levels and relationships. By adding dimensional depth to the visualization (showing not just connections but also hierarchical levels and dependency types), the system can effectively display complex multi-level dependencies without sacrificing accuracy.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If project management tools are designed for specific delivery types, then they can provide specialized functionality, but they lack support for hybrid methodologies

Engineering Contradiction:
Improvesupport for hybrid methodologiesVSAvoidsystem flexibility
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal project management visualization system that can handle multiple delivery types (waterfall, agile, hybrid) within a single platform. The system is designed to be multi-functional, adapting to different methodologies without requiring separate specialized tools, thus resolving the contradiction between versatility and complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements a dynamic system that can adapt its visualization and management approach based on the specific delivery type or hybrid combination being used. The system flexibly adjusts its behavior and display to match the project methodology, providing specialized functionality when needed while maintaining overall simplicity.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If traditional project management tools are used, then basic tracking is possible, but they fail to clearly visualize dependencies and their impacts across project phases

Engineering Contradiction:
Improvedependency impact visibilityVSAvoidvisualization capability
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent uses color-coded visual indicators to represent different dependency types, impact levels, and project phases. This visual encoding allows users to quickly grasp dependency impacts across phases without complex analysis, resolving the contradiction between information visibility and visualization complexity.

Inventive Principle:
Principle #32Color changes

Solution Approach 2:

The patent introduces an intermediary visualization layer that translates complex dependency data into intuitive visual representations. This intermediary layer processes and presents dependency information in a comprehensible format, making impacts visible without requiring the user to understand the underlying complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If manual project data analysis is performed, then detailed examination is possible, but it consumes significant time and reduces productivity

Engineering Contradiction:
Improvedecision-making efficiencyVSAvoiddata analysis time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical analysis with automated computational systems that quickly process project data and generate visualizations. This substitution eliminates time-consuming manual work while maintaining or improving analysis depth, resolving the contradiction between productivity and time consumption.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent implements self-service automation where the system automatically analyzes project data, identifies dependencies, and generates visualizations without requiring manual intervention. The system serves itself by performing data processing and analysis tasks that would otherwise consume significant human time, thereby improving productivity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12020352B2Project visualization system
Publication Date: 2024.06.25 ACCENTURE GLOBAL SOLUTIONS LTD
  • US12020352B2 patent drawing
  • US12020352B2 patent drawing
  • US12020352B2 patent drawing

AI summary

In some implementations, a device may receive project management data including information related to project elements associated with one or more projects and associations among the project elements associated with the one or more projects. The device may generate one or more data structures representing the project elements associated with the one or more projects and the associations among the project elements associated with the one or more projects. The device may receive a request to visualize project data, wherein the request may indicate a view to use in order to visualize the project data and/or specify criteria related to the project data to be visualized in the view. The device may search the one or more data structures to obtain the project data to be visualized based on the criteria specified in the request. The device may render the project data using the view indicated in the request.