Activity Templates for Centralized ERP Project Deliverables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current project management systems fail to efficiently centralize and reuse knowledge and execution data across large, geographically dispersed teams, leading to duplication of efforts and inefficiencies in project execution.

Innovation Solution

A computing system that generates enterprise project deliverables using activity templates stored in a data repository, allowing for the identification and selection of relevant templates based on project requirements, with a feedback loop to enhance template usability and configuration for future projects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual project management methods are used with individual team members documenting artifacts in productivity software, then team members can maintain flexibility and autonomy in their work, but knowledge and execution data become functionally and geographically dispersed, leading to duplication of efforts and inefficiencies

Engineering Contradiction:
ImproveTeam member autonomy and flexibilityVSAvoidKnowledge dispersion
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent merges previously dispersed project artifacts and execution data into a unified data model that centralizes knowledge storage while maintaining team member autonomy. The unified data model consolidates functional and geographic knowledge into a single accessible repository, eliminating information silos without restricting individual team members' operational flexibility.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified data model serves multiple functions simultaneously: it stores project artifacts, tracks execution data, enables template generation, and supports collaboration across geographically dispersed teams. This multi-functional system replaces multiple separate documentation tools while maintaining ease of access for all team members.

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

2Productivity

If project artifacts are documented in productivity software with manual coordination, then team members can work independently with their own documentation, but this leads to duplication of efforts and inefficiencies in project execution

Engineering Contradiction:
ImproveIndividual team member efficiencyVSAvoidTime for duplicative work
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining activity templates based on historical project data and industry standards. These templates contain pre-structured deliverables, tasks, and milestones that can be automatically instantiated for new projects, eliminating the need for team members to manually create documentation from scratch and reducing duplicative work.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements copying by allowing activity templates to be reused across multiple projects. Once a template is created and validated in one project, it can be copied and adapted for future projects, eliminating the need to recreate similar project structures and reducing time spent on duplicative documentation efforts.

Inventive Principle:
Principle #26Copying

3Reliability

If knowledge specific to project execution stays with individual team members, then each member maintains expertise and autonomy, but this prevents central sharing of knowledge and details for reference by other team members

Engineering Contradiction:
ImproveIndividual expertiseVSAvoidKnowledge sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The unified data model implements a nested structure where individual team member expertise and contributions are nested within the broader organizational knowledge base. Personal knowledge artifacts are stored and linked within the unified data model, allowing individual expertise to be preserved while simultaneously making it accessible to the entire organization through the centralized system.

Inventive Principle:
Principle #7Nested doll (Nesting)

4Productivity

If activity templates are used to generate project deliverables automatically, then project execution efficiency is improved and data access is centralized, but the system complexity increases due to template management and configuration requirements

Engineering Contradiction:
ImproveProject execution speedVSAvoidTemplate management system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements feedback loops where execution data from completed projects is automatically captured and used to refine and improve activity templates. This feedback mechanism allows the system to learn from actual project outcomes, automatically updating templates to reflect best practices and reducing the need for manual template management and configuration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11449813B2Generating project deliverables using objects of a data model
Publication Date: 2022.09.20 ACCENTURE GLOBAL SOLUTIONS LTD
  • US11449813B2 patent drawing
  • US11449813B2 patent drawing
  • US11449813B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for receiving requirements data for a first enterprise resource planning (ERP) project and accessing a data repository that includes multiple templates. A subset of the templates include activity templates and each template is associated with at least one other ERP project. A system identifies activity templates based on the requirements data. Each identified activity template defines deliverables for performing the first ERP project. The system receives user input for validating an identified activity template by referencing the requirements data. The system selects an activity template in response to receiving the user input that validates the activity template. The system uses the selected activity template to generate a first deliverable for executing the first ERP project. The first deliverable is represented by a data object in the activity template that receives workflow data for execution of the first deliverable.