Dependency Structure Visualization for Digital Ecosystems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Consumer-facing organizations face challenges in managing their digital ecosystems due to the lack of a clear dependency structure between front-end applications and back-end technologies and services, which hinders issue resolution and user experience improvement.

Innovation Solution

A system and method for aggregating and visualizing a dependency structure within a digital ecosystem using application logging data, metadata, customer intent, organizational structure, and operational support information, determining latency and success/error rates, and generating visualization data for display.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software-based tools are used to manage computing infrastructure, then basic management functions are provided, but clear dependency structure between consumer, front-end applications, and back-end technologies is lost

Engineering Contradiction:

Improvemanagement functionVSAvoiddependency structure

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The patent introduces a dependency structure visualization system that acts as an intermediary between management tools and the digital ecosystem. This system aggregates log data from multiple sources and presents it in a visual format that reveals dependency relationships, allowing managers to see the full picture without changing existing management workflows.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical log analysis methods with automated data aggregation and visualization systems. Instead of manually tracking dependencies through logs and metadata, the system automatically collects, processes, and displays dependency structures, reducing manual effort while preserving critical information.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Loss of information

If comprehensive log data is collected from multiple sources, then complete ecosystem information is obtained, but data aggregation and visualization complexity increases

Engineering Contradiction:

Improveecosystem informationVSAvoiddata aggregation system

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent creates a universal data aggregation platform that handles multiple types of log data (application logs, access logs, error logs) and metadata through a single system. This multi-functional approach consolidates what would otherwise require separate processing systems, reducing overall complexity while maintaining comprehensive information capture.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements self-service capabilities where the visualization automatically generates dependency structures from raw log data without requiring manual configuration. The system autonomously aggregates data, identifies relationships, and presents visualizations, reducing the operational complexity of managing comprehensive log collection.

Inventive Principle:

Principle #25Self-service

3Ease of repair

If dependency structure visualization is implemented, then troubleshooting and user experience improvement are enhanced, but system implementation complexity increases

Engineering Contradiction:

Improvetroubleshooting capabilityVSAvoidvisualization system

Core Design Contradiction:

Ease of repairVSDevice complexity

Solution Approach 1:

The patent replaces complex manual troubleshooting processes with automated dependency visualization. Instead of manually analyzing log data to identify issues, the system automatically generates visual representations of dependency structures, making troubleshooting straightforward while the underlying complexity is handled by the automated system.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The visualization system serves as an intermediary that translates complex dependency relationships into intuitive visual formats. This mediator layer handles the complexity of data processing and relationship mapping, presenting simplified views to users while maintaining comprehensive analysis capabilities behind the scenes.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11327731B2Systems and methods for a digital ecosystem

Publication Date: 2022.05.10 FMR CORP

AI summary

Systems and methods for aggregating a dependency structure based on application logging data, application metadata, customer intent and journey, organizational structure, and operational support information. The method includes receiving data using an application programming interface. The method further includes, for each user, determining a start point and an end point corresponding to user activity on a networked system. The method also includes, for each user, determining a task based on the start point and end point corresponding to the user activity. The method further includes, for each user, determining operations data corresponding to the user activity. The method also includes, for each user, determining a dependency structure based on the task and the operations data. The method also includes aggregating the dependency structure, the task, and the operations data into a visualization. The method further includes generating for display the visualization on a user device.