Dispatch Priority Alignment Score (DPAS)

GMI-TEL-018TelecommunicationsPilot-ReadyPattern O-5: Override Value / Trust

Definition

Percentage of dispatch sequences where the workforce optimizer's routing order matches business priority order, measuring how often travel efficiency silently outranks urgency.

The Measurement Gap

Measurement Gap and Decision

What DPAS Measures: DPAS calculates the percentage of dispatch sequences where the workforce optimizer's routing order matches business-value priority order. A "priority inversion" occurs when the optimizer schedules a lower-priority job before a higher-priority job because the lower-priority job is geographically closer.

Decision Supported:

Is the route optimizer protecting high-value customer commitments, or is it sacrificing SLA compliance for geographic efficiency? Without DPAS, dispatch efficiency is measured by total drive time, jobs completed per shift, and overall SLA compliance: none of which reveal whether the optimizer is systematically causing SLA misses on high-value jobs by routing technicians to low-value nearby jobs first.

Why This Is Unmeasured:

Workforce optimizers minimize total drive time or maximize jobs per shift. SLA priority is typically a secondary constraint, not the primary objective. This means the optimizer will route a technician to a residential installation 5 minutes away before an enterprise SLA-critical repair 20 minutes away: even though the enterprise job has a 4-hour SLA window that is about to expire. The SLA miss is attributed to "insufficient staffing" rather than to a routing decision that prioritized geographic efficiency over business value. DPAS makes these priority inversions visible and countable (Gartner, "Workforce Optimization: The SLA Priority Blind Spot," 2024; Field Service News, "Route Optimization vs. Business Priority: Resolving the Conflict," 2023).

Formula

Plain Language: For each dispatch sequence (a technician's ordered job list for a shift), check whether any lower-business-priority job was scheduled before a higher-business-priority job. Count the sequences without any such inversions. Divide by total sequences.

Notation:

DPAS = Dispatch_sequences_without_priority_inversion / Total_dispatch_sequences × 100

Variable Definitions:

  • Dispatch_sequences_without_priority_inversion = shift-level job sequences where no lower-business-priority job precedes a higher-business-priority job in the execution order (count, dimensionless)
  • Total_dispatch_sequences = all technician shift-level job sequences generated by the optimizer in the measurement period (count, dimensionless)
  • Business priority defined by: SLA tier × time-to-SLA-breach × revenue impact. A job with a tighter SLA window AND higher revenue impact outranks a job with a looser SLA AND lower revenue.

Units:

Percentage. 100% = perfect alignment between routing order and business priority. Lower values indicate more frequent priority inversions.

Sign Convention:

Higher is better. 100% means no priority inversions occurred.

Edge Cases:

  • A lower-priority job directly on the route to the higher-priority job may be worth completing en route. Allow a "de minimis" exception: if the lower-priority job adds less than 15 minutes to the arrival time at the higher-priority job, it is not counted as an inversion.
  • Jobs added mid-shift (emergency dispatches): re-evaluate the remaining sequence from the insertion point forward.
  • Minimum sample: 100 dispatch sequences per market per measurement period.

Proposed formula, pending validation pilots.

At a Glance

Unit
Percentage
Trend Direction
Higher
Reporting Frequency
Monthly
Category
Fraud, Workforce, and Regulatory Calibration
← Compliance Work Segregation Index (CWSI)Fraud Detection Coverage Drift (FDCD) →

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