Automatic duty status changes (ADSC) overview

Overview

Automatic duty status change (ADSC) uses the Maven adapter (VDA) and vehicle movement to update duty status without manual changes.

When the adapter and app function correctly, ADSC:

• Switches to Driving when the vehicle moves faster than 5 mph.

• Switches to On Duty, Not Driving when the vehicle remains stopped for more than 5 minutes.

Exceptions

ADSC follows special rules when these special statuses are active:

• On Duty – Yard Move

  • Status remains On Duty – Yard Move until the vehicle reaches 25 mph.

  • At 25 mph or above, ADSC switches to Driving.

• Off Duty – Personal Conveyance

  • Status remains Off Duty – Personal Conveyance, no matter the speed or duration of movement.

  • ADSC does not switch to Driving while personal conveyance is active, because this time is treated as personal use and is not regulated driving time.

This overall behavior is called Automatic Duty Status Change (ADSC).

Identify possible ADSC issues

Drivers often describe ADSC issues in ways like:

• “Truck is not switching to drive when moving.”

• “Shift time is going down, but drive and break clocks are stuck.”

• “Drive time is not recording.”

To verify ADSC behavior:

1. Open the driver’s HOS logs in the Maven Fleet Portal.

2. Review the daily log:

   • ADSC working correctly:

     • Log contains events labeled “Automatic Duty Status Change” for transitions into Driving and back to On Duty.

   • ADSC not working:

     • Log does not contain any “Automatic Duty Status Change” events.

     • Duty statuses change only through manual entries.

If ADSC entries are missing for periods when the vehicle moved, treat the case as an ADSC issue and continue to technical troubleshooting.

When reviewing issues, also check:

• If mileage is missing but the driver is connected and receiving ADSC events, follow the Mileage missing guide.

• If the driver is receiving ADSC and mileage, but HOS timers are incorrect, follow the HOS timers troubleshooting guide.