Solutions

How Yipii Mobility is used in practice — servicing triggered by distance or by fault code, workshop operations, and keeping compliance provable.

Yipii Mobility is the maintenance side of the platform: what the vehicle needs, who does it, what it cost, and the record that it happened.

These pages describe how it is actually used, and are honest about which parts are automated and which still need a person. If you are looking for live tracking, geofences and driver behaviour, that is Yipii IoT.

By how servicing is triggered

Servicing by distance

Oil changes, filters, tyres — anything that wears by kilometres. Yipii counts down against the vehicle's own odometer and raises the job on its own. This is the most automated path in the product.

Fault-code-driven servicing

The vehicle reports an engine fault over OBD. It appears in Diagnostics and a work order is raised from it. Useful, but a person still decides — there is no rule engine on fault codes today, and this page says so plainly.

By what you run

Workshop operations

Running the bays: work orders, parts off the shelf, labour hours, and what a job actually cost against what you quoted.

Where this fits

Most customers run both products against the same vehicles — the tracker that reports position is also the thing that reports distance and fault codes into maintenance.