Fleet Management for Taxi Fleets

AIS-140 was introduced after a series of passenger safety incidents, and the emergency button requirement follows directly from that.

For a taxi fleet the practical consequence is that the device is tied to the permit. A vehicle whose device has stopped transmitting is not merely untracked, it is at risk at the next permit or fitness renewal.

The failure is usually silent: a lapsed data plan or a device never registered on the state backend. Both keep the unit powering on while the state record goes quiet. See the VLTD backend.

In goods transport, harsh driving is a cost. With a passenger aboard it is a complaint, and complaints reach the aggregator or the transport authority.

What is worth monitoring is the pattern rather than the incident: the driver consistently braking hard or cornering fast, rather than the one who did it once in traffic.

Where a camera is fitted, it also protects the driver. Passenger disputes are otherwise one word against another, and the driver usually loses that. See AI dashcams.

A taxi fleet earns on time occupied and pays on time owned, and the gap between the two is where the margin is.

Measuring idle time per vehicle rather than across the fleet exposes the variation, which is usually driver and location rather than vehicle.

The same data answers where to position vehicles, because demand concentrates in patterns that are visible once trips are recorded.

Driver turnover in taxi fleets is high, which means hiring happens continuously and often under time pressure with a vehicle standing idle.

That pressure is exactly where verification discipline slips, and an unverified licence on a passenger vehicle is the worst place for it to slip.

Verification against Sarathi takes seconds and checks the thing that matters, which is whether the licence exists and covers the class. See driver verification.