AIS-140 is two obligations, and most tenders only price one of them.
There is the device on the vehicle, which is certified. And there is the platform behind it, which has to keep pushing a correct record to the state backend for as long as the fleet runs. The first is bought once. The second is operated, and it is where deployments quietly fail their compliance.
The statutory record, produced and pushed.
Formatted push
The record is assembled in the format the state's VLTD backend expects and pushed on the schedule it expects, from the platform rather than from each device.
Panic to 112 / ERSS
A panic press is routed to the emergency response system as well as to your own control room, so the statutory path and the operational path are not one point of failure.
Per-state onboarding
Each state backend is onboarded separately with its own certification testing. We treat that as defined work per state rather than a switch that is on or off.
Any device, any vendor
The obligation follows the fleet, not the hardware. Units from different suppliers are normalised into one record before the statutory push is built.
Evidence when asked
What was pushed, when, and whether it was acknowledged — retained so a compliance question has an answer that is not a recollection.
Silence is a finding
A device that stops reporting stops being compliant. Device health and last-contact are monitored and alerted on rather than discovered at an audit.
Where the boundary is.
Bring the clause, not the summary.
AIS-140 wording differs by state and by package. Send the tender text and we will mark it clause by clause.