AIS 140 For EV Fleets
💡 AIS 140: Key Highlights
- A permit condition, not a purchase decision — Rule 125H binds vehicle categories, not powertrains. Two- and three-wheelers, e-rickshaws and permit-free vehicles are exempt.
- Three parts: a type-approved VLT device, prescribed panic buttons, and a backend registered with your state.
- The feed carries position and emergencies only — no state of charge, temperature or charging session.
- On an EV the wiring decides everything: no alternator, no ignition circuit, a depot charge that reads as sleep.
If your vehicles run on a national or state permit — staff and school buses, permit taxis, contract coaches, national-permit goods vehicles — AIS 140 is a condition on your permit and fitness certificate, not a product you evaluate. Electrifying does not remove it; it changes where the device draws power, and how badly it performs when mistaken for an operations feed.
It is also newly enforced: in May 2026 the Supreme Court recorded that fewer than 1% of public service vehicles carry a working tracker and emergency button, and gave states liberty to withhold fitness certificates.
Which Vehicles AIS 140 Binds — And Which Are Exempt
The obligation is Rule 125H of the Central Motor Vehicles Rules, 1989, inserted by G.S.R. 1095(E) of 28 November 2016. It binds public service vehicles under section 2(35) of the Motor Vehicles Act, requiring a vehicle location tracking device and one or more emergency buttons conforming to AIS-140:2016.
Four categories sit outside it: two-wheelers, three-wheelers, e-rickshaws, and — the exemption most operators miss — any transport vehicle needing no permit. That clause is why the mandate follows your permit, not your purchase. Vehicles registered from 1 January 2019 left the dealership fitted; older ones came in through state retrofit windows. The enforcement point never moved: registration, permit issue, fitness renewal.
| Vehicle in scope | Where the mandate bites |
|---|---|
| Electric staff, school or contract bus | Permit issue and every fitness renewal |
| Electric permit taxi or cab | Registration and permit renewal |
| National-permit electric goods vehicle | National permit issue and renewal |
Two identical electric vans can therefore sit in one depot with different obligations. Scope by permit register, not vehicle list.
What A Compliant AIS 140 Setup Actually Includes
1. A type-approved VLT device
The model must hold a Type Approval Certificate from a testing agency named in Rule 126 of the CMVR — in practice ARAI or ICAT — uploaded to VAHAN before tagging, and re-tested annually. AIS-140 stays operative until BIS specifications are notified. Its M2M SIM carries a mandated validity: two years under eight years of vehicle age, one year over.
2. Panic buttons, in prescribed positions
The button count is not the installer’s choice. A passenger car needs one per passenger row plus a driver button; a bus needs them at roughly two-metre intervals down both sides, with a dedicated button for each reserved ladies’ row; a national-permit truck needs one in the driver’s reach. All are hard-wired, and a cut wire raises a tamper alert.
3. A backend registered with your state
This is the part operators discover late. Tagging the device on VAHAN is not compliance. The manufacturer or dealer must also register it against your vehicle and your permit-holder details on the State Monitoring Centre — the state’s command-and-control centre. That centre establishes connectivity, verifies SIM validity and tests the panic button remotely; only when it pushes activation back to VAHAN is the fitment certificate issued. Registration is per state, so a certified vendor can still leave you a transmitting device with no activation record.
The obligation is continuing: the owner, not the vendor, must keep the device transmitting. Our EV fleet compliance checklist covers the wider record set this sits under.
AIS 140 Is A Compliance Feed, Not A Fleet Operations Feed
The published packet formats settle this faster than any vendor conversation, because the list is fixed: position, speed, heading, satellite and network data, ignition state, main power status, two voltage readings, emergency and tamper status, plus harsh-braking, over-speed and geofence alerts.
Nowhere in it is a state of charge, a pack temperature, an energy figure or a charging session — the two voltage fields describe the device itself. Our EV fleet telematics guide covers where battery data comes from. The question here is architectural.
The standard already assumes you have somewhere else to send data
A compliant device must support at least two backend IP addresses — one for the regulatory position stream, one for the emergency response system — beyond any used operationally. The standard never pretends the regulatory feed is your fleet system: it leaves room for a third destination without defining it. Nor is that stream readable back. It ends in a state system you cannot query.
An electric fleet therefore runs two streams. The procurement question is how many boxes produce them.
| Approach | What you get | What it costs |
|---|---|---|
| Two devices — certified VLT plus a separate operational source | Clean separation; swap the compliance box without touching operational history | Two SIMs per vehicle, two failure modes, duplicated data |
| One device — certified VLT whose vendor also streams a copy to you | One box, one SIM, one install; events reach your own platform via an API | Lock-in across both jobs; the API is a negotiated term, not part of certification |
One detail decides whether that copy is worth anything: reporting frequency is set by the backend, not the box. State protocols require a packet at least every ten minutes with the ignition off — a trail that satisfies a regulator and is useless for dispatch. Specify the operational rate separately.
What Changes When The Vehicle Is Electric
AIS 140 was written for vehicles with an engine, an alternator and an ignition key. An electric bus or van has none of them.
Where the device draws power
The device expects a conventional 12 V or 24 V supply — the specification’s own samples are 12.5 V and 24.6 V. On an EV no alternator holds that rail up; a DC-DC converter does, and often runs only while the vehicle is awake. Tap a live rail and a parked EV discharges its auxiliary battery; tap a switched one and the device falls back to an internal cell rated for about four hours. Neither survives a weekend.
It becomes a compliance problem because the device reports it: main-power disconnect and low internal battery are named alerts, so a badly powered VLT leaves a health record reading as a dead device at renewal. Ask which rail the installer taps, and route those alerts into the same fleet alert management queue as your battery alerts.
Why ignition-off behaviour differs
Ignition on and off are hard-coded states driving the reporting rate, and an EV has no ignition circuit — so the sense line must map to a ready signal or accessory rail. Map it wrong and the failure is quiet: on a live feed every vehicle reports as running around the clock; on the wrong switched output, real trips log at sleep frequency.
The same gap makes charging invisible: a vehicle plugged in at the depot is ignition-off, so eight hours of charging produce a few sleep packets from a stationary point. Charging data alongside your EV vehicle tracking comes from the charger and the vehicle bus, as our EV fleet system integration guide covers.
An AIS 140 Procurement Checklist
Five questions separate a quote that clears a fitness test from one that does not. Ask them in writing.
- Certification at model level. The Type Approval Certificate for the exact make and model, plus current Conformity of Production status.
- Backend registration, per state. Written confirmation the vendor is registered with the State Monitoring Centre wherever you register vehicles.
- SIM term and renewal. The validity in the contract, and who pays when it expires. A dead SIM is a non-compliant vehicle.
- Data retention and read-back. How long the vendor holds your position history, in what format, and whether you can export it — the regulatory copy is unreadable to you.
- Ownership on exit. Switching vendors in year three: who owns the history, what does re-tagging cost, how long is each vehicle off the road?
Handled properly, AIS 140 is a bounded obligation: certified box, buttons in the right places, backend registered, renewals diarised. The mistake is letting it stand in for visibility it was never designed to give — which is why the operational copy belongs in a fleet operating system like YoMobility, beside your charging and battery data.
Frequently Asked Questions
Sources: MoRTH — Central Motor Vehicles Rules, 1989 | ARAI — Standardisation | ICAT — Services | BIS — Transport Engineering
Run Compliance And Operations Off One Fleet Record
Tell us your permit mix and states of registration, and we will map which vehicles are in scope and where the operational feed should land.