Cloud Project Management Platform Modular Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional project management platforms are difficult to scale and deploy on-demand, requiring time-consuming and resource-intensive installation and configuration on-premise, and customizations can burden the upgrade process, leading to increased downtime and resource usage.

Innovation Solution

A computer-implemented project management platform deployed on a cloud-computing platform, utilizing a content management platform as a container to access and customize applications, with server systems hosting customizations and data, allowing for rapid deployment and management of project management tools as a service, including authentication and data storage in a multi-tier architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional on-premise project management platforms are installed and configured for each entity, then the platform can be customized for specific entities, but the deployment becomes time-consuming and resource-intensive

Engineering Contradiction:
Improveentity-specific customizationVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments the project management platform into independent, modular applications that can be selectively deployed. Each application is a self-contained unit that can be installed and configured independently, enabling rapid deployment while maintaining entity-specific customization capabilities through the modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses template-based application definitions that can be copied and deployed across multiple entities. These templates contain pre-configured settings and structures that can be rapidly replicated, significantly reducing deployment time while still allowing entity-specific customizations through parameter configuration.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If traditional on-premise project management platforms are installed for each entity, then the platform can be customized for specific entities, but the deployment becomes resource-intensive

Engineering Contradiction:
Improveentity-specific customizationVSAvoidtechnical resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system implements a universal platform architecture where core infrastructure, security protocols, and base application logic are shared across all entities. This multi-functional foundation reduces the technical resources required for each individual deployment while maintaining the ability to customize applications for specific entity needs.

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

Solution Approach 2:

By segmenting the platform into modular applications with shared dependencies, the system avoids redundant resource consumption. Common libraries, frameworks, and configuration management systems are shared across applications and entities, reducing the overall technical resources required while preserving customization capabilities.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If customizations are applied to applications in traditional project management systems, then the platform adapts to entity needs, but the upgrade process becomes burdened with increased downtime and resource usage

Engineering Contradiction:
Improveapplication customizationVSAvoidupgrade downtime
Core Design Contradiction:
Adaptability or versatilityVSDuration of action of moving object

Solution Approach 1:

The system segments customizations into application-specific modules that are independent of the core platform infrastructure. This allows upgrades to be applied at the application level without requiring system-wide reconfiguration, significantly reducing upgrade downtime while preserving entity-specific customizations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary configuration of application templates with standardized customization options before deployment. This pre-configured framework allows for rapid application of entity-specific customizations without requiring extensive post-deployment modification, and enables faster upgrades since the base structure is already optimized.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If customizations are applied to applications in traditional project management systems, then the platform adapts to entity needs, but the upgrade process becomes burdened with increased resource usage

Engineering Contradiction:
Improveapplication customizationVSAvoidtechnical resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system implements universal configuration management and upgrade mechanisms that handle customizations across multiple applications and entities simultaneously. This approach consolidates resource requirements for processing and managing customizations, reducing the technical resources needed compared to handling each customization independently in traditional systems.

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

Data Source

PatentUS10482426B2Project management platform
Publication Date: 2019.11.19 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10482426B2 patent drawing
  • US10482426B2 patent drawing
  • US10482426B2 patent drawing

AI summary

Implementations are directed to providing a project management (PM) platform as a cloud-based service by providing a content management (CM) platform, and applications on a cloud-based server system, transmitting instructions to display an electronic document on a display of a computing device, and receiving a user selection of an application through the electronic document, and in response: transmitting a first request to the CM platform, receiving a page frame associated with the application from the CM platform, transmitting a second request to server systems, the server systems hosting customizations and data, receiving at least one response from the one or more server systems, the at least one response comprising at least one customization and data, and displaying, on the computing device, an application page within the page frame, the application page including the at least one customization, and at least a portion of the data.