Every fleet operator running commercial vehicles in India has seen the term AIS-140 — on an RTO notice, a hardware vendor's spec sheet, or a state transport department circular. Fewer can explain, without checking, exactly what it requires, which vehicles it covers, and what happens when a device that's technically “AIS-140 hardware” still fails an audit. That gap is where most compliance trouble actually starts.
What AIS-140 is
AIS-140 is a standard published by the Automotive Research Association of India (ARAI), mandating GPS-based vehicle tracking and emergency panic button systems for public service vehicles. It was framed as a direct response to safety failures in public transport — most visibly after the Nirbhaya case pushed the Ministry of Road Transport and Highways (MoRTH) to require live tracking and a way for passengers to raise an alarm from inside a moving vehicle.
The standard is not a suggestion. It's enforced through the VAHAN registration system — vehicles in mandated categories cannot be registered, or in many states cannot renew fitness certificates, without AIS-140 certified hardware fitted and reporting correctly.
Which vehicles it applies to
AIS-140 applies to vehicles used for public transport and passenger service — not private cars. In practice, that means:
- State and city public transport buses
- School buses and vans transporting children
- App-based taxis and cab aggregator vehicles (Ola, Uber, and similar)
- Contract carriages and stage carriages under state permits
- Ambulances operated as part of public emergency services in several states
Private commercial fleets — logistics trucks, FMCG distribution vans, cement mixers, construction equipment carriers — are not covered by AIS-140 itself. But the distinction matters less than it sounds: many state RTOs have started extending equivalent tracking and panic-button expectations to broader commercial categories, and several large enterprise customers now write AIS-140-equivalent tracking into vendor contracts regardless of the legal category, because it's become the de facto standard for “is this fleet properly instrumented.”
What the hardware actually has to do
“AIS-140 certified device” gets used as a catch-all, but the certification covers a specific set of functional requirements:
Live location reporting
The device must transmit GPS location at a minimum frequency — typically every 10 seconds while the vehicle is moving — to a central command centre operated by the state or city transport authority, not just to the fleet operator's own dashboard. This dual-reporting requirement is where a lot of otherwise-good GPS hardware falls short: a device built for fleet visibility alone doesn't necessarily speak the protocol the government command centre expects.
A physical panic button
A hardware button, reachable by a passenger without needing a phone or an app, that triggers an immediate distress signal — GPS coordinates plus a panic flag — to both the transport authority and, depending on the state implementation, local police control rooms. This has to work without depending on the driver, since in the scenarios the standard was written for, the driver may be the threat.
VAHAN and SATHI integration
Device data has to be reportable through India's VAHAN vehicle registration database and, in an increasing number of states, the SATHI (Smart and Trusted Agencies for Transport Hub Interchange) platform. This is the piece that turns AIS-140 from “install a tracker” into “install a tracker whose output format a government system can ingest and validate” — and it's the requirement most likely to change certification status if the vendor's backend integration isn't actively maintained.
Tamper resistance
The device has to detect and report tampering — power disconnection, GPS antenna removal, enclosure opening — rather than silently going dark. A device that just stops reporting when unplugged fails this requirement even if its normal operation is otherwise compliant.
The compliance gap that catches the most fleets: having AIS-140 certified hardware installed is not the same as being AIS-140 compliant. Certification is a hardware property. Compliance is an operating state — the device has to be correctly configured, actively reporting to the right endpoints, and passing tamper checks, continuously. Fleets get flagged at RTO audits with certified hardware that stopped reporting to VAHAN months earlier and nobody noticed.
Where fleets actually get caught out
Talking to fleet managers who've been through an RTO or state transport audit, the failures cluster around a handful of patterns — and none of them are “we didn't buy the hardware.”
Hardware installed, integration never completed
A device gets fitted during vehicle purchase or a fleet-wide rollout, but the backend integration connecting it to VAHAN or the state command centre is left as a “phase two” that never happens. The device works fine for the fleet's own dashboard. It reports nothing to the authority that actually checks compliance.
SIM or connectivity lapses
AIS-140 devices report over cellular. A fleet that doesn't actively monitor SIM balance, network fallback, or device health can have vehicles that are non-compliant for weeks without anyone noticing — the device is physically present, the vehicle looks fine on a visual inspection, but the reporting has silently stopped.
Panic button wiring degrades over time
Physical buttons in vehicles that see rough daily use — school buses, city buses — fail mechanically more often than the GPS module does. Because the panic button is only tested in an emergency or an audit, a failed button can go unnoticed for a long time.
Fleet growth outpaces the compliance process
A fleet that added 40 vehicles this year and treated AIS-140 installation as a one-time project for the original fleet often finds the newer vehicles were never brought into the same compliance pipeline — different vendor, different configuration, sometimes no integration at all.
What good AIS-140 compliance looks like operationally
The fleets that pass audits without drama treat AIS-140 as an ongoing operating requirement, not a one-time installation:
- Device health monitoring — knowing immediately when a vehicle stops reporting, rather than discovering it during an inspection
- Centralised configuration — every vehicle added to the fleet goes through the same AIS-140 setup and verification step, not an ad hoc process that depends on who's handling procurement that quarter
- Exportable, tamper-proof trip logs — when an RTO audit or an incident investigation asks for records, the fleet can produce signed logs rather than reconstructing a timeline from memory
- A single source of truth — one dashboard that shows compliance status across every vehicle, rather than checking hardware certification, connectivity, and VAHAN reporting as three separate systems
ViaLoop Fleet ingests AIS-140 protocol data natively and supports AIS-140 certified hardware without requiring a hardware swap — the platform sits on top of what's already installed. Every trip is stored with a full GPS breadcrumb trail at ten-second resolution, cryptographically signed and retained for 12 months, ready to export for an RTO audit or a VAHAN submission without reconstruction. Fleet managers get one dashboard showing device health and reporting status across every vehicle, so a compliance gap shows up as an alert — not as a finding during an inspection.