Critical Event Object Dependency Structuring for Project Risk Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex projects often fail due to difficulties in understanding and evaluating priorities, risks, and dependencies, leading to insufficient resource allocation and poor communication between stakeholders, resulting in high failure probabilities that can have detrimental economic impacts.

Innovation Solution

A system and method for reducing project failure probability through the generation, evaluation, and dependency structuring of critical event objects, utilizing an orchestration server that initiates sessions, generates failure event objects, assesses risks, and assigns responsibilities, while also employing machine learning for predictive modeling and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional project management tools are used to track and evaluate project aspects, then basic project monitoring is achieved, but the system cannot effectively reduce project failure probability due to insufficient insight into critical events and their dependencies

Engineering Contradiction:
Improveproject success probabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments project risks into discrete critical event objects, each representing a specific failure criterion. These objects are independently evaluated and structured in dependency hierarchies, allowing the system to manage complexity by breaking down overall project risk into manageable, analyzable units rather than treating project monitoring as a monolithic process

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces critical event objects as intermediary entities between project activities and failure outcomes. These objects serve as mediators that capture, structure, and evaluate risk information, enabling the system to bridge the gap between raw project data and actionable risk insights without requiring direct complex analysis of all project elements

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive risk evaluation is performed on all project components, then project failure probability can be reduced, but resource allocation becomes inefficient as less important components receive excessive resources

Engineering Contradiction:
Improveproject success probabilityVSAvoidresource allocation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by evaluating and structuring critical event objects with different priority levels and dependency relationships. Resources are allocated based on the specific characteristics, risk levels, and dependency positions of individual critical events rather than uniformly across all project components, ensuring that high-risk areas receive appropriate attention while lower-risk areas consume fewer resources

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the parameter of risk evaluation from a uniform approach to a differentiated approach based on critical event properties. By assigning different weights, priorities, and dependency levels to various critical event objects, the system dynamically adjusts resource allocation parameters to match actual risk distribution, improving both reliability and resource efficiency

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If critical risks are identified through post-mortem analysis, then understanding of failure causes is improved, but the ability to prevent failure upfront is lost as risks are only identified after failure occurs

Engineering Contradiction:
Improvefailure insightVSAvoidtime to prevent failure
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent implements preliminary action by structuring critical event objects and their dependencies before project execution. The system evaluates risk criteria and establishes dependency hierarchies in advance, enabling proactive identification and mitigation of potential failures before they occur, rather than relying on reactive post-mortem analysis

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent establishes feedback mechanisms where critical event objects continuously monitor and evaluate project risk status. The system provides ongoing feedback about potential failures and their dependencies, allowing stakeholders to adjust project course and allocate resources dynamically based on real-time risk assessment rather than waiting for failure to occur

Inventive Principle:
Principle #23Feedback

4Measurement precision

If detailed tracking of project priorities and dependencies is implemented, then project evaluation accuracy is improved, but communication and coordination between stakeholders become more difficult due to system complexity

Engineering Contradiction:
Improveproject evaluation accuracyVSAvoidstakeholder communication ease
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent creates simplified representations (copies) of complex project dependencies through critical event objects and their hierarchical structures. These objects serve as manageable models that capture essential risk relationships without requiring stakeholders to navigate the full complexity of underlying project details, making communication and coordination more accessible while maintaining evaluation accuracy

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11729202B2Reducing project failure probability through generation, evaluation, and/or dependency structuring of a critical event object
Publication Date: 2023.08.15 PRIIO INC
  • US11729202B2 patent drawing
  • US11729202B2 patent drawing
  • US11729202B2 patent drawing

AI summary

Disclosed is a method, a device, a system and/or a manufacture of reducing project failure probability through generation, evaluation, and/or dependency structuring of a critical event object. In one embodiment, a system for building a failure dependency hierarchy includes an orchestration server and a network. The orchestration server initiates a session and provisions computing resources. An object generation routine receives a failure event criterion. An object initiation routine then generates a failure event object associated with the failure event criterion. A risk assessment routine generates a risk value by inputting a probability data and an impact data into a risk assessment function. A dependency routine stores in a referential attribute a unique identifier of a second failure event object to define a failure dependency. A user assignment routine associates the unique identifier of a user profile with the failure event object to assign responsibility for preventing the failure event.