Runtime Blocking Path Detection for Changing Task Dependencies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex processes involving multiple tasks with changing dependencies are difficult to model accurately, leading to challenges in identifying blocking paths that impede job progress, which can cause capacity shortages and impact long-range planning.
Innovation Solution
A system and method for blocking path detection that scans task states and identifies ownership teams with tasks that are either in progress or blocked, designating them as on a blocking path when all tasks assigned to that team are finished or waiting, and provides notifications or actions when the team exceeds a threshold time on the blocking path.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If complex processes with changing dependencies are modeled a priori, then planning can be performed, but the model becomes inaccurate due to frequent changes in task processing and dependencies
Solution Approach 1:
The system dynamically determines blocking paths during job execution rather than using static a priori models. The blocking path identification is performed at runtime based on current task states and dependencies, allowing the system to adapt to changing conditions without requiring complex dynamic modeling beforehand.
Solution Approach 2:
The system self-monitors task states and automatically identifies blocking paths without external intervention. The job execution system itself tracks task progress and determines which teams are blocking progress, eliminating the need for separate complex modeling systems.
2Measurement precision
If blocking paths are identified by monitoring all task states, then accurate blocking path detection is achieved, but computing resource consumption increases
Solution Approach 1:
The system extracts only the critical information needed for blocking path identification - specifically, which tasks are in progress or blocked and which team owns them. Rather than monitoring all task attributes, it focuses only on state and ownership information relevant to determining blocking paths, reducing computational overhead while maintaining detection accuracy.
3Reliability
If continuous monitoring of task states is performed, then blocking paths are detected accurately, but time is lost due to frequent scanning
Solution Approach 1:
The system performs periodic blocking path determination during job execution rather than continuous monitoring. Blocking paths are identified at specific checkpoints in the job workflow, providing reliable detection without the overhead of constant scanning.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system and method for blocking path detection is provided. A job comprises tasks with at least some of the tasks dependent on other task(s). Each task is assigned to an ownership team. At a particular point in execution of the job, states of tasks of the job are identified. The states include one of three mutually exclusive states: waiting for another task/finished, in progress, and, blocked. When all the tasks with identified states of in progress or blocked are assigned to a particular ownership team, the particular ownership team is identified as on a blocking path. An action can be performed regarding the blocking path, for example, selected in accordance with policy-defined response actions such as generating an incident, escalating an existing incident, and/or sending a notification (e.g., an accumulated time on the blocking path can be calculated for each team with team(s) notified when certain threshold(s) are exceeded).