Task Dependency Sequencing Compliance (TDSC)

GMI-RE-040Renewable EnergyInfrastructure-Dependent

Definition

Proportion of multi-site routes where information-dependent tasks were sequenced correctly, with diagnostic tasks preceding the decisions they inform, rather than in travel-time-optimized order. Route optimizers that minimize distance break diagnostic chains the maintenance process assumes are intact.

The Measurement Gap

The Measurement Gap

Route optimization algorithms in renewable energy maintenance sequence site visits by travel time, equipment availability, and weather windows. They do not consider information dependencies between tasks at different sites. When a technician performs an oil sample collection at Site A and a gearbox repair decision at Site B, the optimizer may schedule Site B first because it is closer to the starting depot, even though the oil analysis result from Site A should inform whether the gearbox at Site B needs a full rebuild or a minor adjustment. The technician arrives at Site B, makes the repair decision without the diagnostic information, and either makes a suboptimal decision or delays the repair until the sample result arrives, defeating the route efficiency that justified the sequencing in the first place.

This information dependency problem is invisible in standard route optimization metrics. Travel time is minimized, sites per route is maximized, and the schedule adherence looks excellent. But the quality of decisions made at information-consuming tasks is degraded because the information-producing tasks were not completed first. The resulting unnecessary return visits, suboptimal repair decisions, and deferred actions are attributed to individual judgment calls rather than to a systematic sequencing failure in the routing algorithm.

The Decision It Enables

TDSC identifies which task-dependency patterns are being broken by travel-optimized sequencing and quantifies the compliance rate for each dependency type. When TDSC for hard dependencies (where the decision genuinely cannot be made without the diagnostic result) drops below acceptable levels, the organization adds sequencing constraints to the routing optimizer for those specific dependency patterns. This accepts a travel time penalty in exchange for decision quality improvement. For soft dependencies (where the information is helpful but not essential), the organization can tolerate lower compliance and let the optimizer prioritize travel efficiency. TDSC provides the evidence to distinguish between dependencies that must be respected and those where the travel efficiency tradeoff is acceptable.

Formula

Primary Formula:

TDSC = Correctly_Sequenced_Pairs / Total_Dependent_Pairs_in_Routes x 100

Variable Definitions:

Variable Definition
Correctly_Sequenced_Pairs the number of dependent task pairs where the information-producing task was scheduled before the information-consuming task within the same route or within a timeframe that allows the information t...
Total_Dependent_Pairs_in_Routes all identified dependent task pairs included in multi-site routes during the measurement period

Calculation Example:

Over a month of multi-site routes, the task dependency map identifies 45 dependent task pairs across all routes. Of these, 32 are hard dependencies and 13 are soft dependencies. Review of actual route sequences shows 24 of 32 hard dependency pairs were correctly sequenced and 8 of 13 soft dependency pairs were correctly sequenced. TDSC(hard) = 24/32 x 100 = 75%. TDSC(soft) = 8/13 x 100 = 62%.

Edge Cases and Measurement Boundaries:

Dependencies must be identified and cataloged before TDSC can be measured. This requires creating a task dependency map that most organizations do not currently maintain, which is the infrastructure investment that makes this metric Infrastructure-Dependent. Some same-day dependencies may be moot if the diagnostic result cannot be obtained same-day regardless of sequencing (for example, if oil sample lab turnaround is 48 hours, sequencing the sample first on the same-day route provides no benefit). Actual task execution order may differ from planned route sequence if technicians resequence based on field conditions; capture actual execution order from mobile workforce application timestamps where available.

Proposed formula, pending validation pilots.

At a Glance

Unit
Percentage
Trend Direction
Higher; more compliant sequencing
Reporting Frequency
Monthly
Category
Field Execution Efficiency vs. Quality
← Route Compression Quality Score (RCQS)Defect Portfolio Demand Clustering Index (DPDCI) →

Assess Your Organization

The AI-GPS Assessment evaluates your AI governance maturity and recommends KPIs like this one for your implementation roadmap.

Take the Free AI-GPS Assessment