What is AIS-140?
Automotive Industry Standard 140
Definition
AIS-140 full form is Automotive Industry Standard 140. It mandates Vehicle Location Tracking Devices (VLTD) and emergency panic buttons in public and commercial transport vehicles. Certified devices transmit real-time location to state backend control centres and must meet defined hardware, connectivity, and emergency-response requirements.
Why it matters for Indian fleets
Commercial vehicles in India need AIS-140 certified trackers to pass RTO fitness and permit checks. Non-compliant or generic imported trackers risk failing inspection and detention.
What the standard actually requires
AIS-140 is an Automotive Industry Standard issued under the Central Motor Vehicles Rules framework, drafted by ARAI and notified by the Ministry of Road Transport and Highways. It specifies what a tracking installation on a public service or commercial transport vehicle must consist of, and the requirements go well beyond "fit a GPS device".
- A certified Vehicle Location Tracking Device, tested and approved by an authorised agency rather than self-declared as compliant.
- Emergency buttons accessible to passengers or the driver, which raise an alert to the backend rather than merely sounding locally.
- Continuous transmission of location to a state backend control centre, not only to the vendor’s own platform.
- Internal backup battery, so the device keeps reporting if main power is disconnected, which is what stops the obvious method of defeating it.
- Tamper detection and alerts.
- Defined reporting intervals, more frequent when an emergency has been raised than during normal running.
Which vehicles it applies to
The standard targets public service and commercial transport rather than private cars. In practice the vehicles most consistently covered are those carrying passengers or operating under a permit.
- Passenger transport: buses, school buses, taxis and other public service vehicles.
- Goods vehicles under state notifications, particularly those carrying hazardous goods.
- National permit vehicles, where the permit itself is conditioned on compliance.
Because transport is state-administered, the exact scope, the timelines and the enforcement intensity differ between states. The device standard is national; the obligation to fit it, the backend it reports to and the certificate procedure are state matters. A fleet operating across states should expect to deal with more than one process, which is the single most common surprise in AIS-140 projects.
Why an ordinary GPS tracker will not do
This is the most expensive misunderstanding in the category. A cheap imported tracker can report position accurately and still fail an inspection outright, because accuracy was never the requirement.
It has no certification against the standard, no panic button wired to a backend, no backup battery, no tamper alerting, and critically no connection to the state backend control centre. A device reporting only to a private vendor dashboard does not satisfy a rule whose purpose is that the state can see the vehicle in an emergency.
The failure usually surfaces at the worst moment: at fitness renewal or permit issue, when the vehicle is already earning and taking it off the road costs real money. Buying on device price alone reliably produces this outcome.
Getting compliant without paying twice
- Confirm the state requirement first, since scope and procedure vary and the backend is state-specific. Guides for Bihar, Odisha, Uttar Pradesh, Rajasthan, Maharashtra, West Bengal and Tamil Nadu cover the procedure state by state.
- Verify the certificate, not the claim. Ask for the test certificate and check the model against the state’s approved vendor list, because "AIS-140 compliant" on a product page is a marketing statement.
- Check backend integration is live for the specific state you operate in, not merely supported in principle.
- Get the compliance certificate the RTO will actually ask for at fitness or permit time, and keep it with the vehicle documents.
- Plan for the fleet, not the vehicle, so devices, SIM connectivity and certificates renew on a schedule you control instead of one discovered at a check post.
Frequently asked questions
Is AIS-140 mandatory for all vehicles in India?
No. It targets public service and commercial transport vehicles, principally passenger vehicles such as buses, school buses and taxis, national permit vehicles, and goods vehicles covered by state notifications. Private cars are not covered. Exact scope and timelines are set by each state.
Can I use a normal GPS tracker for AIS-140 compliance?
No. A certified device is required, with an emergency panic button, internal backup battery, tamper detection and live transmission to the state backend control centre. An uncertified tracker can report location perfectly and still fail inspection, because location accuracy was never the requirement.
What happens if a vehicle is not AIS-140 compliant?
The practical consequence is failure at RTO fitness or permit renewal, which takes the vehicle off the road until it is resolved. Non-compliant vehicles are also exposed to challans and detention at check posts, and the lost operating days usually cost more than the device.
Why do AIS-140 requirements differ between states?
The device standard is national, but transport is administered by states. Each state notifies which vehicle categories are covered, runs its own backend control centre, maintains its own approved vendor list and sets its own certificate procedure, so a fleet operating across states deals with several processes.
How do I verify a device is genuinely AIS-140 certified?
Ask the vendor for the test certificate from an authorised testing agency and check the specific model against the approved vendor list published by the state you operate in. Confirm separately that live integration with that state’s backend control centre is operational, not merely supported.
Related MoboSafe workflows
Review the documented product scope and setup requirements for these related operational tasks.
Fleet Asset Management
Manage fleet vehicles, trailers, equipment, ownership, insurance documents, device assignments, and utilisation in MoboSafe.
Vehicle Inspections
Digital pre-trip, post-trip, and periodic vehicle inspections with configurable checklists, defect photos, and inspection history.
Fleet Insurance Claims
Organise fleet insurance claims with incident records, supporting documents, survey status, settlement details, and claims reports.
Begin
Ready to connect your whole operation?
Explore tracking, trips, assets, fuel, inventory, accounting, and payroll with the MoboSafe team. Build a rollout around the workflows your fleet needs.