Understanding AIS-140: What Vehicle Operators Actually Need to Know

What Is AIS-140 and Why Should You Care?

If you run public transport vehicles in India, AIS-140 is not optional. It has been mandatory since April 2018 for all new registrations of public service vehicles. The Automotive Industry Standard 140, issued by the Automotive Research Association of India (ARAI), lays down the exact specifications for vehicle tracking systems that must be fitted in all public transport vehicles.

But here is the part most vendors skip when they are trying to sell you a tracker: AIS-140 is not just about installing a GPS device. The standard covers hardware specs, server connectivity, emergency buttons, and data transmission protocols. Getting it wrong means failed inspections, fines, and wasted money.

The Actual Hardware Requirements

An AIS-140 compliant Vehicle Location Tracking (VLT) device must meet specific criteria. The device needs GPS and GLONASS capability for positioning. It must have internal and external antennas. There are two emergency buttons required: one near the driver and one accessible to passengers. The device needs a built-in battery backup of at least four hours, so tracking continues even if someone disconnects the main power.

The hardware must be ARAI-certified. This is where many vehicle operators get caught. They buy a cheap tracker from an online marketplace, install it, and then discover during RTO inspection that it does not carry the ARAI certification number. That means reinstallation with a certified device, double the cost, and sometimes a penalty.

Server and Backend Requirements

The tracking data from your vehicles must reach two destinations. First, your own vehicle management server or your vendor's server. Second, the government's VAHAN portal run by the Ministry of Road Transport and Highways. The data format follows IRNSS (Indian Regional Navigation Satellite System) standards.

Your VLT device must transmit location data at least once every 60 seconds when the vehicle is moving and once every five minutes when stationary. That is roughly 1,440 data packets per vehicle per day at minimum. The server needs to store this data for at least 365 days.

This backend cost is what many operators forget to budget for. The device itself might cost ten to fifteen thousand rupees, but the annual server and SIM charges add another three to five thousand per year per vehicle.

State-by-State Implementation

Here is something that frustrates vehicle operators across India. While AIS-140 is a central standard, each state transport department has its own timeline and enforcement intensity. Karnataka and Uttar Pradesh were early adopters and strictly enforce compliance during fitness certificate renewal. Rajasthan and Maharashtra have been progressively tightening enforcement since 2022.

Some states also have additional requirements layered on top of AIS-140. For instance, certain states mandate that the VLT vendor be empanelled with the state transport authority. If your vendor is not on that list, your certified device might still fail inspection.

What Compliance Actually Costs

Let us break down the real numbers for 20 public transport vehicles:

Hardware cost: A certified AIS-140 device runs between eight thousand to fifteen thousand rupees per unit. For 20 vehicles, that is 1.6 to 3 lakh rupees.

Installation: Professional installation costs around 500 to 1,500 rupees per vehicle. For 20 vehicles, that is 10,000 to 30,000 rupees.

Annual server and SIM: Server connectivity plus SIM data charges run 2,500 to 5,000 rupees per vehicle per year. For 20 vehicles, that is 50,000 to 1 lakh per year.

First-year total: Roughly 2.2 to 4.3 lakh rupees for 20 vehicles. After year one, the recurring cost drops to the server and SIM charges.

How to Choose the Right AIS-140 Vendor

Three things matter more than price. First, check that the device has a valid ARAI test report number. Ask to see the certificate, not a photocopy. Second, confirm that the vendor is empanelled with your state transport authority. Third, ask about the data retention policy. If the vendor's server loses data, you lose compliance.

At MobiSafe, we handle all three. Our GT-300 AIS device carries full ARAI certification, we are empanelled across 14 states, and our servers maintain 24 months of data retention, double the mandatory requirement.

Common Mistakes to Avoid

We have seen hundreds of vehicle operators go through the AIS-140 compliance process. The most common mistakes are buying non-certified devices to save money, not budgeting for annual recurring costs, ignoring the emergency button installation, and not testing the data feed to VAHAN before the inspection date.

The last one is particularly painful. The VAHAN integration sometimes takes 7 to 15 working days to activate. If you wait until a week before your fitness certificate renewal, you will likely miss the deadline.

Start the process at least 45 days before you need to be compliant. That gives you time for hardware delivery, installation, VAHAN integration testing, and a buffer for any issues.