Operations
AxleGuard records duty events, remaining clocks, carrier-proposed corrections, driver decisions, certifications, diagnostics and transfer evidence. The workflow is implemented, but the product is not yet an FMCSA-registered ELD and does not present itself as one.
In the product
What changes
Each outcome connects what the software does to the decision a planner, loader or driver can actually make.
The same workspace shows drive available, the duty window, break timing and the eight-day cycle for the selected driver and home-terminal date.
A trip plan can fit the miles and still fail the clock. Putting the record beside the work makes that conflict visible before it becomes a roadside conversation.
Carrier staff submit a change request. The affected driver accepts or rejects it, and both the request and decision remain in the record.
Editing the original event hides who changed it. A proposal-and-decision workflow preserves the driver’s control and the sequence of evidence.
Registration, self-test, diagnostics, malfunctions, output-file evidence and physical testing are tracked as separate readiness records.
A polished duty graph is not an ELD registration. The current API keeps telematic and local roadside transfer locked until registration evidence is recorded; the other readiness checks remain visible but are not yet enforcement gates.
How it works
The logic is visible. There is no “AI decided” step between the load and the verdict.
Important boundary
This is a development HOS and ELD record workflow, not an FMCSA-registered ELD. The current API gates telematic/local transfer on recorded registration status. Self-test, output-file validation and physical vehicle testing are tracked, but the code does not yet enforce all three as transfer prerequisites.
The record is tied to the driver’s home-terminal day and profile.
Events feed the clocks, graph, break calculation and cycle total.
Original events, proposed changes and driver decisions remain distinguishable.
Registration controls telematic/local transfer today. Self-test, file validation and physical testing remain separate evidence that must be reviewed before production use.
Where to test it
Related capabilities
