Samsara integration: hours of service and ETAs

R. Diaz's unit reports hours of service, location and engine data to Samsara every few minutes, and Roadmark reads all three. It's the same feed behind three different screens: tracking turns it into one ETA per load and explains the math in plain words, dispatch planning checks it before putting a driver on the next load, and billing measures the dock arrival and departure times it reports against the free time in a rate confirmation to bill detention.

None of that needs a new device in the truck. Samsara's own REST API is what Roadmark reads from: an admin creates a token from Samsara's dashboard, under Settings → API Tokens, and grants it the scopes for the data it should read, such as hours of service logs. Nothing about how Samsara runs in the cab changes.

Once it's connected, the ELD is one of five sources Roadmark checks for a load's status, alongside the driver app, a carrier's own app or an EDI 214, visibility networks, and a check call when nothing else is reporting. When the truck slows down or stops, that shows up in the ETA before anyone calls to ask, and it's the same dock-arrival and dock-departure data that turns into a detention line on the invoice, without someone timing it by hand.

For a fleet already running Samsara, that mostly means the load board and the invoice catch up to what the truck has been reporting all along: an ETA that reflects the truck's actual position and hours, a plan that respects the hours left on the clock, and a detention charge that matches the dock clock instead of a guess written on the back of a BOL.