NADIR / Platform / 01 of 04
Connect what you already export. See drift before anyone reports it.
Monitor is the read-only half of the platform. It takes the telematics feed and the repair orders your fleet already produces, scores every vehicle against its own history, and surfaces the ones that have moved since the wrench was last on them.
Inputs
Two feeds and no new hardware.
There is nothing to install in the vehicle. Monitor reads the telematics stream you already pay for, joined to repair-order close timestamps by VIN, and optionally a CAN feed through the Pulse edge pack when the data is not allowed to leave your network. Everything downstream of that is derived.
The arrows only run one way. There is no return path from the scoring service to the vehicle, no diagnostic session, no ECU write, and no configuration that could add one. That constraint is what lets a fleet turn this on alongside whatever it already operates without opening a functional-safety case.
Honesty about inputs
Scored on what actually arrives.
Fleets are heterogeneous and the signals are not uniform. Radar status reaches 72 percent of tractor units and 18 percent of the legacy ones; IMU raw is patchier still. Monitor reports coverage per signal per group rather than averaging it into a single reassuring number, because the weakest cell is what bounds what the product can claim for that group.
The other thing that happens on connect is backfill. Thirty days of history are pulled and scored before the first new event arrives, which means week one is not an empty dashboard — it opens with the repair events that already happened and the handful that were already past tolerance when we found them.
Output
What changed since last week.
A tier on its own is a snapshot. The useful artefact is movement: which vehicles escalated, which recovered, and whether the ones that recovered are the ones you actually dispatched. Roughly four fifths of the fleet stays where it was in any given week, and that mass is deliberately drawn as almost nothing so the movement is what the eye lands on.
Escalations are the work. Recoveries are the evidence that last week's work landed. A vehicle that dropped from CRITICAL to NOMINAL without a bay visit is not good news — it is a question about your threshold, and Monitor puts both numbers in front of you rather than one.
Monitor never books anything, never writes anything, and never contacts the vehicle.
It produces a scored, attributable timeline. Everything that follows is a person acting on it.
Want this pointed at your fleet?
We are onboarding fleets and repair networks a few at a time. Tell us what you run and we will reach out.