HOS Margin Consumption Rate (HMCR)

GMI-TF-023Fleet & TransportationPilot-Ready

Definition

Average remaining drive-time minutes at trip completion for AI-dispatched loads, measuring how thin a margin the dispatch optimization algorithm leaves between actual drive time consumed and the 11-hour HOS limit under 49 CFR 395.3.

The Measurement Gap

Fleet compliance programs track HOS violations as a lagging indicator, but never measure how close the AI dispatcher is pushing drivers to the limit before violations occur. The blind metrics that create false confidence include:

HOS Violation Rate: The standard compliance metric, but it only counts events after the line has been crossed. A fleet can have zero violations while routinely dispatching loads that leave drivers with five minutes of remaining drive time. The violation rate looks clean until one traffic delay converts a thin margin into a violation.

Fleet Utilization Rate: Higher utilization is celebrated in operations reviews, but utilization is the inverse of margin. A fleet running at 95% HOS utilization is by definition running at 5% margin, and the dispatch optimizer is rewarded for consuming the very buffer that prevents violations.

On-Time Delivery Rate (OTD): Loads arrive on time, which looks like operational excellence, but the question OTD cannot answer is: at what regulatory margin cost? A 99% OTD achieved by consuming HOS buffers is borrowing compliance risk to fund delivery performance.

Decision Supported:

Is the AI dispatch optimizer systematically consuming the regulatory buffer between actual drive time and the HOS limit? Are drivers routinely finishing trips with dangerously thin remaining margins: where any delay (traffic, weather, detention) would push them into a violation? HMCR answers whether the dispatch algorithm needs a mandatory minimum buffer constraint added to its optimization logic.

Formula

Plain language: For each completed trip, calculate how many drive-time minutes the driver had remaining against the 11-hour (660-minute) HOS driving limit at the moment the trip ended. Average that remaining margin across all trips in the fleet. Additionally, track what percentage of trips finished with less than 30 minutes remaining and less than 15 minutes remaining: those are the trips operating in the danger zone.

Notation:

HMCR = (1/N) × Σ (HOSLimit - ActualDriveTime_i) for i = 1 to N trips

Distribution metrics:

  • % trips with margin < 30 minutes
  • % trips with margin < 15 minutes
  • % violations (margin ≤ 0 minutes)

Variables:

Variable Description Source
HOSLimit 660 minutes: the 11-hour driving limit under 49 CFR 395.3. For trips where the 14-hour duty window is the binding constraint, use 840 minutes (14 hours) minus non-driving duty time as the effective limit, whichever is tighter Regulatory constant + ELD duty status (NATIVE)
ActualDriveTime_i Total driving-status minutes recorded by the ELD for trip i, measured from duty period start to trip completion ELD (NATIVE)
N Total number of AI-dispatched trips completed in the measurement period TMS (NATIVE)
AI dispatch assignment Record linking the trip to an AI-generated dispatch decision: required to distinguish AI-dispatched loads from manually dispatched loads TMS (NATIVE)
Trip completion timestamp The moment the trip was completed, used to determine HOS clock position at trip end ELD / telematics (NATIVE)
HOS violation records Formal HOS violations recorded by the ELD: used to validate that margin ≤ 0 trips correspond to recorded violations ELD (NATIVE)

Proposed formula, pending validation pilots.

At a Glance

Unit
Time (minutes)
Trend Direction
Higher; more margin remaining
Reporting Frequency
Monthly
Category
HOS and Rest Quality Compliance
← Campaign Regulatory Completion Uniformity (CRCU)Rest Strategy Safety Differential (RSSD) →

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