Definition
TBCR measures the ratio of actual time spent on each task within a bundled visit to the standalone standard duration for that task type. This metric reveals whether the efficiency gains from task bundling are genuine productivity improvements or whether the time saved per visit comes from rushing individual tasks below the thoroughness threshold.
The Measurement Gap
The Measurement Gap
Route optimization and task bundling are standard practices in distributed renewable energy fleet maintenance. Sending a technician to one site to perform five tasks is more efficient than five separate trips. The AI route optimizer maximizes the number of tasks per trip by allocating time across bundled tasks and minimizing travel between sites. The question TBCR asks is whether this time allocation is compressing individual task execution below the level required for quality work.
A blade inspection that takes 90 minutes as a standalone visit might receive only 45 minutes when bundled with four other tasks. The technician completes the inspection, but whether the compressed inspection catches the same defects as the full-duration inspection is unknown without measurement. The efficiency report shows five tasks completed in one trip. The quality question goes unasked because the current metrics only track completion, not thoroughness.
Without TBCR, organizations optimize for trip efficiency without a feedback loop on task quality. The route optimizer produces increasingly compressed schedules because every completed task counts as a success. Quality degradation appears months later as repeat failures, missed defects, or callbacks, but nobody connects these outcomes to the compression that caused them.
The Decision This Metric Supports
TBCR reveals whether task bundling is improving efficiency while maintaining quality or whether the time saved per visit comes from rushing individual tasks below the thoroughness threshold. When TBCR is above 0.75 for safety-critical tasks, bundling compression is within acceptable limits. When TBCR drops below 0.60 for any task type, the compression warrants investigation to determine whether the shortened duration is producing measurable quality degradation.
Formula
Primary Formula:
TBCR(t) = Actual_Duration_Bundled(t) / Standard_Duration_Standalone(t)
Where:
| Variable | Definition |
|---|---|
| Actual_Duration_Bundled(t) | actual time spent on task t during a bundled visit, in minutes |
| Standard_Duration_Standalone(t) | established standard duration for task type t when performed as the sole task on a visit, in minutes |
Measurement frequency: Monthly, computed across all bundled visits in the period. Report both the mean TBCR by task type and the percentage of tasks below the 0.60 threshold.
Segmentation requirements: Track TBCR by task type, by technician, and by bundle size (number of tasks in the visit). Larger bundles create more pressure to compress individual tasks. A technician who consistently shows TBCR below 0.50 on safety-critical tasks while other technicians maintain TBCR above 0.70 may need coaching on time management during bundled visits.
Edge cases requiring special handling:
- Standard durations must be established before TBCR is meaningful. Use historical averages from standalone visits (where only one task was performed at the site) as the baseline. If standalone visit data is sparse for certain task types, use manufacturer recommended durations adjusted for site-specific conditions.
- Some tasks genuinely take less time when bundled because mobilization and demobilization time is shared across multiple tasks. Adjust the standalone standard to exclude setup and teardown that would be shared in a bundled visit.
- Technician experience varies significantly. A technician with 15 years of experience may legitimately complete a task in less time than the standard without quality loss. If data supports it, normalize by technician experience level.
Proposed formula, pending validation pilots.