What does AIS 140 compliance require?
AIS 140 compliance means a public service vehicle carries a certified Vehicle Location Tracking Device (VLTD) and an emergency button, and that the device reports to a government-designated backend. It is a legal requirement under Rule 125H of the Central Motor Vehicles Rules, 1989, and states check it when the vehicle comes up for its fitness certificate.
That is the short version. Most of what is written about AIS 140 is device marketing, so this guide separates what the rules require from what a vendor would like you to buy. If you are budgeting, our fleet management software cost guide covers prices.
- *Key takeaways**
- Rule 125H of the CMVR was inserted by notification GSR 1095(E) dated 28 November 2016 and made the tracking device and emergency button mandatory for public service vehicles from 1 April 2018 (West Bengal transport notice).
- New public service vehicles registered after 1 January 2019 had to comply; the 2018 Order sets the standard (Motor Vehicles (VLTD and Emergency Button) Order, 2018).
- States must check fitment and working status when a vehicle is presented for fitness certification (same Order).
- The Supreme Court has said no public service vehicle should get a fitness certificate or permit without a VLTD and panic button (Moneylife).
- A plain GPS tracker is not AIS 140 compliant unless it is certified to the standard and reports to the designated backend.
What is AIS 140?
AIS 140 is the Automotive Industry Standard, published by ARAI under the Ministry of Road Transport and Highways, that sets minimum technical and functional requirements for a vehicle location tracking device and emergency button in public transport vehicles.
The standard is the technical half. The legal half is Rule 125H, which says which vehicles must carry the device. The 2018 Order ties the two together by naming the standard and the vehicles it applies to. Vendor guides add that the device must support GPS and India’s NavIC, though we have not confirmed that from the standard’s text (FleetX).
Which vehicles need AIS 140?
AIS 140 applies to the public service vehicles named in Rule 125H(1) of the CMVR. In practice that means vehicles carrying passengers for hire, such as buses, taxis, maxicabs and school buses, rather than private cars.
Two cautions. First, the exact list and the dates differ by state, and some older taxis, maxicabs and city buses have been given exemptions in certain circulars, such as a Mizoram one (TeamLease RegTech). Second, vendor blogs also list goods vehicles and give conflicting deadlines, from 2018 to March 2026. We have not found a source we trust for a nationwide truck deadline, so check your state transport department or VAHAN before you act on one.
| Question | What the sources support |
|—|—|
| Public service vehicles (passenger, for hire) | Covered under Rule 125H(1) |
| New vehicles registered after 1 January 2019 | Must comply at registration |
| Older registered vehicles | Retrofit directed; check your state’s date |
| Private cars | Not covered by Rule 125H |
| Goods vehicles | Vendor claims vary; confirm with your state |
What must the device do?
A compliant device must give the vehicle’s location, carry a physical emergency button, report to the designated backend, and keep working when the network drops. Here is the list we use when scoping a project:
1. Location. Position from GPS, with NavIC support reported by vendors.
2. Emergency button. A passenger or crew member can press it, and the alert goes to the backend. The device should store an alert if there is no signal and send it with priority once the network returns (FleetX).
3. Backend reporting. Data goes over mobile data, with SMS as a fallback, to a backend control centre (Indrastra summary of the 2018 draft).
4. Configurable reporting rates. Specifications describe separate rates for normal running, ignition on, ignition off and emergency, set over the air (ICG document). Be wary of a vendor quoting one fixed interval as “the rule”.
5. Certification. The device must be tested by an agency named in the rules. ARAI and ICAT are the names you will see.
Is a normal GPS tracker enough?
No. A normal GPS tracker shows you where a vehicle is, but it is not tested to the standard, usually has no emergency button, and does not report to the government backend. It is fine for your own tracking and not acceptable at a fitness inspection.
The reverse is also true. An AIS 140 device on its own gives the regulator a dot on a map. It does not tell you which routes lose money, which driver idles most or when a service is due. That is software, and it is separate from compliance.
How is compliance checked?
Compliance is checked at fitness certification. The Order requires states and Union Territories to check fitment and functional status of the device when the vehicle is presented (2018 Order). Karnataka, for instance, made fitment compulsory for the fitness certificate and has inspectors verify the device and panic button with a mobile app (Tribune).
Before an inspection, check that:
- the device model is on the certified list;
- it is activated and registered on the state’s backend;
- the emergency button actually triggers an alert;
- the SIM has data and is not expired.
An expired SIM is the cheapest way to fail. The device is fine and the vehicle still does not report.
What does AIS 140 not require?
AIS 140 does not require you to buy a particular brand, a particular software package or a particular subscription. The rules name a standard and a certification route, not a vendor. It also does not tell you how to use the location data inside your own business.
That matters when a salesperson says compliance requires their full platform. It requires a certified device that reports to the designated backend and works at inspection. Everything beyond that, such as trip reports, fuel analysis, driver scoring and maintenance alerts, is a business decision you can make separately.
Ask three questions of any quote: is the device certified, is it registered on the backend your state uses, and what do I pay each year for the SIM and platform? If the answers are vague, keep looking.
The angle most guides miss: device versus software
The legal requirement is about the device and the backend. What you do with the data is up to you, and most operators who buy only for compliance pay twice. They fit a certified device for the regulator, then buy tracking software for themselves, often from a different vendor, with a second SIM.
If the same device feeds both, compliance reporting becomes a by-product of the data you already collect. Check this with your vendor before you buy: can the certified device also send to your own platform, and who owns that data?
What we’ve seen at DECK IT
We are DECK IT, a software company in Ahmedabad building since 2017, and we build smart mobility platforms including QwikFleet, our fleet management software for cab, truck and public transport fleets. Many fleet owners who ask us about AIS 140 are really asking for two things at once: a device the inspector accepts, and a dashboard they can use. The compliance part is a one-time exercise per vehicle; the dashboard is where the daily value is.
Our advice is to settle the compliance device first, then check that your software can read from it. Details are on our fleet management solution page.
Frequently asked questions
What is AIS 140 in simple terms?
AIS 140 is the Indian standard for a certified GPS tracking device with an emergency button in public service vehicles. It sets how the device must locate the vehicle, raise alerts and report to a government backend.
Is AIS 140 mandatory?
Yes, for public service vehicles covered by Rule 125H of the Central Motor Vehicles Rules. The mandate began on 1 April 2018, with new vehicles registered after 1 January 2019 required to comply. Exact dates for older vehicles vary by state.
Which vehicles need an AIS 140 device?
Public service vehicles named in Rule 125H(1), such as buses, taxis and school buses. Private cars are not covered. Whether goods vehicles are covered depends on your state, so confirm with your transport department.
Does AIS 140 require a panic button?
Yes. The standard requires an emergency button, and the alert must reach the backend. If there is no network, the device stores the alert and sends it with priority when signal returns.
Can I use a normal GPS tracker for AIS 140?
No. Only a device certified to the standard and registered with the designated backend counts. A normal tracker can still be used for your own fleet monitoring.
Who certifies AIS 140 devices?
Devices are tested by agencies named in the rules; ARAI publishes the standard and ICAT is among the testing bodies. Always check the certificate before buying.
Conclusion
AIS 140 compliance is a device, an emergency button and a backend link, checked when your vehicle comes up for its fitness certificate. Confirm which of your vehicles are covered in your state, buy a certified device, and make sure the SIM and registration are live before the inspection.
Then decide what you want from the data. If you would like help scoping a compliant device together with fleet software, tell us about your fleet and we will come back within a working day.
Last updated: