Project Database Key Field Change Control System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing changes to key data fields in project management applications is inefficient, as administrators must track numerous changes across various teams, leading to challenges in ensuring project progress without impacting timely completion.

Innovation Solution

A method and system that define activities, key data fields, and actions within a project management application, where changes to key data fields trigger specific actions based on pre-specified conditions related to project progression metrics, with control levels escalating as the project advances, allowing for actions such as logging, restricting access, requiring approval, and canceling activities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If administrators manually track all changes to data fields, then change management reliability is improved, but time consumption and operational complexity increase

Engineering Contradiction:
Improvechange management reliabilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically performs change tracking and impact analysis without requiring administrator intervention. The project management application self-monitors data field changes, calculates impact on project metrics, and notifies relevant users automatically, eliminating the need for manual tracking while maintaining reliable change management

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements automatic feedback mechanisms where changes to key data fields trigger immediate impact analysis and notifications. The system continuously monitors project metrics and provides real-time feedback to stakeholders about how changes affect project timeline, budget, and milestones, ensuring reliable change management through automated information flow

Inventive Principle:
Principle #23Feedback

2Reliability

If administrators manually track all changes to data fields, then change management reliability is improved, but device complexity increases

Engineering Contradiction:
Improvechange management reliabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system autonomously performs change monitoring, impact analysis, and user notification functions. The project management application automatically detects changes to key data fields, calculates their impact on project metrics, and notifies relevant users without requiring administrator setup or intervention, thereby maintaining reliability while minimizing operational complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system introduces an automated intermediary layer between data field changes and project stakeholders. This intermediary automatically analyzes the impact of changes on project metrics and mediates the information flow to relevant users, simplifying the operational process while ensuring reliable change management through systematic automated handling

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If strict control is applied to all data field changes, then project progress control is improved, but productivity decreases

Engineering Contradiction:
Improveproject progress controlVSAvoidproject completion speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies differentiated control measures based on the specific impact of each change. High-impact changes that affect critical project metrics trigger strict control procedures including manager approval and team notification, while low-impact changes are processed automatically with minimal intervention, thereby maintaining project control while preserving productivity

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adjusts the level of control applied to data field changes based on their calculated impact on project metrics. The control mechanism transitions from strict manual approval for high-impact changes to automated processing for low-impact changes, optimizing the balance between project progress control and team productivity throughout the project lifecycle

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9805318B2Method, system and program product for conditionally controlling changes to key data fields in a project database
Publication Date: 2017.10.31 KYNDRYL INC
  • US9805318B2 patent drawing
  • US9805318B2 patent drawing
  • US9805318B2 patent drawing

AI summary

A method, system and program product for performing one or more actions in response to a change made to a key data field in a project management application for managing a project. The method includes establishing one or more metrics to be monitored for a project, defining one or more actions for at least one key data field of a plurality of key data fields in the project management application, the one or more actions being defined in accordance with a level of control to be exercised and being triggered by one or more pre-specified conditions associated with the one or more metrics monitored for the project. The method further includes automatically performing at least one action of the one or more actions in response to a relative impact to the project caused by a change made to the at least one key data field.