AIS-140 is a government-mandated technical standard for vehicle tracking devices fitted to public and commercial vehicles in India. It sets out what a device has to do, how it communicates with government servers, and how it gets tested before anyone can sell it as compliant. This guide covers the standard itself: what it requires, how certification works, and what to check before you buy a device. If you’re past that stage and want the current 2026 enforcement deadline and a software feature checklist for what to run on top of a compliant device, see the Related blog link further down.
KEY TAKEAWAYS
- AIS-140 is a technical standard, not a brand or a type of GPS tracker. A device has to be tested and certified against it before it can be sold as compliant.
- Certification comes from agencies authorised under India’s Central Motor Vehicle Rules, mainly ARAI and ICAT, not from a manufacturer’s own claim.
- A compliant device has to use GNSS positioning, carry a panic button, transmit to a government backend, and keep running on battery backup if main power is cut.
- Fitness certificate renewal in most states is checked against live device status in the Vahan database, so an offline or uncertified device can hold up renewal.
- States are enforcing this differently. Some check at fitness renewal, some run roadside challans, some fix an installation deadline and price.
- The same data a certified device sends to the government can also feed a fleet management platform for route visibility, geofencing, and reporting.
India’s telematics and fleet safety systems market is projected to grow at a CAGR of 25.41% between 2026 and 2030, reaching an estimated $4.35 billion by 2030, a rise driven in large part by AIS-140 compliance mandates. That growth is the market’s response to a rule that has quietly become a daily operational reality for fleet operators across the country.
In this guide, we cover what AIS-140 actually requires, how a device gets certified, how enforcement differs across states, what to check before buying a device, and how fleets can turn the same compliance data into daily operational visibility.
AIS-140 at a glance
| Element | Requirement |
| Governing body | Ministry of Road Transport and Highways |
| Certifying agencies | ARAI, ICAT |
| Positioning | GNSS (GPS combined with NavIC) |
| Mandatory hardware | Panic button, tamper alert, battery backup |
| Data destination | State ITS server, linked to Vahan |
| Checked at | Fitness certificate renewal, and roadside in several states |
Why AIS-140 matters right now
A vehicle’s fitness certificate renewal in most states runs through the Vahan database, and Vahan checks the device status before it clears the renewal. A device that’s gone offline, or one that was never certified in the first place, can stall that renewal even if the vehicle itself is in good mechanical shape.
Vehicles in the mandated categories, buses, taxis, school vans, and a growing list of goods carriers, can’t legally run without a working, certified device once a state has notified the requirement for that category. And the reason the rule exists at all has nothing to do with paperwork. AIS-140 came out of passenger safety incidents on public transport, and the panic button and live location feed are the direct answer to that. The scale of that safety push shows in the funding behind it: MoRTH approved a scheme to set up state-wise vehicle tracking and monitoring centres under the Nirbhaya Framework at a total estimated cost of ₹463.90 crore, shared between the central and state governments, built to track exactly the kind of incidents that pushed the standard into existence. The compliance side of it is a byproduct, not the point.
What is AIS-140?
AIS-140 stands for Automotive Industry Standard 140, published under India’s Central Motor Vehicle Rules and administered by the Ministry of Road Transport and Highways. It rolled out from April 2019, starting with buses, taxis, school vans, and other public service vehicles, and has since extended to goods carriers and other commercial categories in most states.
Fleet owners often treat AIS-140 as a product. It isn’t. It’s a specification a device has to pass, similar to a BIS mark on an appliance. No manufacturer gets to call a device AIS-140 compliant just because the box says so.
What does AIS-140 actually require?
The standard sets requirements across three parts of a compliant system.
- Hardware
The device has to use GNSS positioning (GPS combined with India’s own NavIC system), send data over a cellular network, include a panic button, and keep running on battery backup for a minimum period if main power is cut. It also has to flag an alert if someone tries to remove or tamper with it.
- Communication
The device sends location and status data at set intervals to a government backend, usually the state’s ITS server linked to Vahan, and fires a separate emergency packet the moment the panic button is pressed.
- Backend and storage
Whoever receives the data, whether a state system or a private fleet software vendor, has to store it for a minimum period and produce it on request during an audit or an incident review.
Skip any one of these three parts, and the device isn’t AIS-140 compliant, no matter how well it tracks location.
How does AIS-140 certification actually work?
This is the step most fleet buyers skip, and it’s usually where problems show up later.
A device can’t declare itself compliant. It has to pass testing at an agency authorised under the Central Motor Vehicle Rules, most commonly the Automotive Research Association of India (ARAI) or the International Centre for Automotive Technology (ICAT). Both issue a Type Approval Certificate once a device clears testing.
| Step | What happens |
| Application | The manufacturer submits the device with technical drawings and specifications |
| Testing | Agency tests actual samples for positioning accuracy, transmission timing, panic button response, and backup power life |
| Review | Engineers check results against the published AIS-140 protocol before sign-off |
| Certificate issued | The device receives a Type Approval Certificate number, checkable independently of the vendor’s claims |
| Ongoing checks | Manufacturer re-tests periodically to confirm that production units still match the certified design |
A certificate covers the tested model, not every unit that ships afterward, which is why the re-testing step matters.
Enforcement looks different in every state
AIS-140 is a national standard, but the rollout is state by state, and no two states are running it the same way.
Karnataka picked a hard deadline over open-ended enforcement: every public service and national permit goods vehicle had one year, December 2023 through November 2024, to fit a device from the state’s approved list, at a fixed price of ₹7,599 excluding GST. Publishing the price meant operators weren’t negotiating blind. More than 6.5 lakh public service vehicles fall under the mandate, feeding into a centralised command centre that routes panic alerts straight to police, ambulance, and fire response.
Odisha took the portal route instead of a fixed deadline. Its dedicated compliance system checks device status directly against Vahan transactions, and the mandate spans public service vehicles, national permit vehicles, and vehicles carrying hazardous goods, so a single missed category doesn’t slip through.
Chandigarh ties enforcement to the fitness inspection itself: maxi cabs, motor cabs, and buses get checked for a working device at that stage, and vehicles caught without one are challaned on the spot rather than only flagged at renewal.
What holds across all three approaches: once MoRTH notifies a vehicle category in a state, non-compliance eventually stops the fitness certificate, the route permit, or both. States differ on when and how they catch it. None of them let it go uncaught for long.
What non-compliance actually costs
An offline or uncertified device doesn’t sit quietly in the background. Fitness certificate renewal gets denied when the device status in Vahan doesn’t match. A denied renewal means the vehicle can’t legally operate, whatever shape the engine is in.
Roadside checks in several states now issue on-the-spot fines for vehicles running without a working device. Route permits can be revoked for repeated non-compliance. Government tenders, school transport contracts, and an increasing number of private logistics contracts already ask for AIS-140 compliance proof before they sign a vehicle on contract. None of that shows up in the certification paperwork itself. It shows up the first time a renewal gets rejected or a load gets turned away over a missing certificate, the same way a mechanical fault that goes unflagged by predictive health monitoring turns into a breakdown instead of a scheduled repair.
What should you check before buying a device?
- Ask for the ARAI or ICAT certificate number and verify it yourself instead of taking the vendor’s word for it.
- Confirm the device is on your state’s approved or whitelisted vendor list. Central type approval and state whitelisting are two separate things, and a device can have one without the other.
- Check that the panic button routes to both the government server and your own dashboard, not just one of them.
- Ask how battery backup is actually tested, not just what’s printed on the spec sheet.
- Find out who handles Vahan linkage and backend registration. This often gets left to the fleet to sort out after installation, and it’s the step that most often causes renewal delays.
How Intangles helps fleets get more from AIS-140 data
A certified device is already sending a steady stream of location, status, and event data to government servers. Most fleets stop there, even as enforcement has shifted from a one-time installation check to an ongoing operational baseline that fleets are now expected to maintain year-round. The data sits inside a compliance dashboard that only gets opened during an audit, while dispatchers keep running routes off phone calls and drivers’ own updates, and managers piece together vehicle history from whatever the state portal happens to show. That works until a vehicle goes missing from its route, a panic alert needs a fast response, or someone needs three months of location history for an incident review and has to request it from the state system.
Intangles is a digital twin company serving the transportation and logistics industry across 18 countries, with more than 500,000 vehicles on its platform. When AIS-140 grade telemetry connects to a fleet management layer like operations automation, the same data that satisfies the regulator becomes route history, geofencing alerts, idle time reports, and driver behaviour signals, instead of sitting untouched until the next audit.
| Capability | What it does |
| Location Tracking | Turns certified GPS/NavIC data into live route visibility and geofencing alerts |
| Fleet Reporting | Converts raw location and status pings into idle time, route deviation, and utilisation reports |
| Alerting | Flags device downtime, signal gaps, or panic events directly to fleet managers, not just to the state server |
For fleets running mixed operations, a few buses alongside a goods segment, this matters more than it looks. One certified device can satisfy the regulator and give operations teams a live view of the fleet, as long as the software on top of it is built to do both jobs.
Explore the platform or get in touch with our team to learn how Intangles’ location tracking turns certified AIS-140 telemetry into day-to-day fleet visibility.
KNOW MORE
Frequently Asked Questions
Is AIS-140 a type of GPS tracker?
No. It’s a technical standard that a device has to be tested and certified against. Different manufacturers build the actual devices, but each one has to clear ARAI or ICAT testing to carry AIS-140 certification.
Who certifies AIS-140 devices?
Agencies authorised under India’s Central Motor Vehicle Rules, mainly ARAI and ICAT, test devices and issue the Type Approval Certificate.
Does every commercial vehicle in India need an AIS-140 device?
The mandate covers public service and commercial categories notified by each state, including buses, taxis, school transport, and goods carriers. Coverage, deadlines, and enforcement methods all vary by state, so check with your State Transport Authority for your specific vehicle category.
What happens if a device stops transmitting data?
Since fitness certificate renewal is checked against live device status in Vahan in most states, an offline device can delay or block renewal. Several states also issue roadside fines for vehicles running with a non-functioning device.
Can AIS-140 data be used for more than compliance?
Yes. The same location and event data a certified device sends to government servers can feed a fleet management platform for route visibility, geofencing, and reporting.
How is AIS-140 different from a standard GPS tracker?
A standard GPS tracker just logs location for internal use. An AIS-140 certified device has to meet tested requirements for positioning accuracy, government data transmission, panic button response, and battery backup, and it has to prove all of that through independent certification, not marketing claims.
We’re looking forward to meeting you