KEY TAKEAWAYS
- A VLTD keeps a vehicle legal: it sends location and emergency alerts to state systems and is checked on VAHAN at fitness and permit time. Fleet telematics keeps a vehicle productive: it tracks engine health, fuel and driving for the operator.
- Fleets can run the two on separate devices, or on one AIS-140 certified device that also reads vehicle data and feeds the fleet’s own platform.
- One device means one installation, one SIM and one data stream to manage. Two devices can make sense where an existing telematics system is deeply embedded and working well.
- Whatever the setup, only an AIS-140 type-approved device, registered on VAHAN with working emergency buttons, counts for VLTD compliance.
- Since the Supreme Court’s May 2026 order tied fitness certificates and permits to a verified VLTD, fleets that already run telematics are deciding how to add compliance, and fleets buying VLTDs are deciding whether to get more from them.
Since May 2026, a missing VLTD can cost an Indian fleet its fitness certificate and permit. The Supreme Court directed that no public service vehicle be granted either until a VLTD and emergency buttons are verified and reflected on VAHAN.
Many of the fleets now buying VLTDs already run some form of fleet telematics. Many others are buying a VLTD for the first time and wondering whether the same device can do more.
Both groups face the same question: should VLTD compliance and fleet telematics run on one device or two?
In this blog, you will learn what each system is for, the three common setups, how data flows when one device does both jobs, which setup fits which kind of fleet, what to check before you buy, and how to roll it out across a mixed fleet.
What is each system for?
A VLTD answers to the regulator. Fleet telematics answers to the operator.
| VLTD | Fleet telematics | |
| Main job | Compliance and passenger safety | Operations, cost and vehicle health |
| Who receives the data | The state’s vehicle tracking platform and monitoring center | The fleet operator’s own platform |
| What it reports | Location, speed, emergency button and tamper alerts | Location plus engine data, fuel, driving behavior and maintenance alerts |
| Checked by | RTOs, through VAHAN | Nobody; it’s the operator’s choice |
For how a VLTD works and where it stops short, see what is a VLTD. For whether your fleet should go beyond basic AIS-140 tracking at all, see AIS-140 vs advanced telematics. This blog picks up from there: how to run both.
What are the three common setups?
| Setup | How it works | Strength | Trade-offs |
| 1. VLTD only | A certified VLTD for compliance; no fleet telematics | Lowest upfront cost; meets the rule | Location and alerts only; no engine, fuel or maintenance data |
| 2. VLTD plus a separate telematics device | A certified VLTD for compliance, and a second device (often existing) for fleet telematics | Keeps an existing telematics system untouched | Two installations, two SIMs, two devices to keep powered and maintained; data in two places |
| 3. One AIS-140 certified device that also does telematics | A single type-approved device sends compliance data to the state platform and vehicle data to the fleet’s platform | One installation and one device to maintain; compliance and operations data in one view | Depends on the device reading vehicle data on your makes and models; needs a vendor that supports both jobs |
How does data flow when one device does both jobs
- The device is fitted and registered
An AIS-140 type-approved device is installed with its emergency buttons and linked to the vehicle on VAHAN. For new vehicles, the vehicle manufacturer or its authorized agency does this; for retrofits, the VLTD dealer or fitment center links the device and an inspector checks the fitment (Meghalaya Transport Department SOP, October 2025). - Compliance data goes to the state
Location and status reach the state’s vehicle tracking platform. Emergency button presses raise an alert at the state monitoring center, which coordinates with the State Emergency Response Support System (SERSS) (PIB, MoRTH Year End Review 2025). - Operational data goes to the fleet platform
The same device reads vehicle data, for example through the OBD port, and sends it to the operator’s telematics platform. - Alerts reach the right people
Emergency and tamper alerts go to the authorities. Maintenance, fuel and driving alerts go to the fleet team. - Compliance is checked as usual
RTOs check the VAHAN registration at fitness and permit renewal, whatever else the device does.
The compliance side is fixed by the rules. The operational side is what the fleet chooses to add.
Which setup fits which fleet?
| Fleet | Usual best fit | Why |
| Bus or cab operator (public service vehicles) | Setup 3 | Every vehicle needs a VLTD; one device gives compliance plus fleet visibility without doubling hardware |
| National permit truck fleet | Setup 3 | Permit authorization needs the VLTD; engine and fuel data drive most of the savings on long hauls |
| Hazardous goods carrier | Setup 3 | Compliance and live location are non-negotiable, and vehicle health matters for safety |
| Fleet with a well-embedded telematics system it’s happy with | Setup 2, reviewed at renewal | Avoids disrupting a working system; consider moving to one device when contracts or hardware come up for renewal |
| Small fleet focused only on passing fitness | Setup 1, with a path to Setup 3 | Lowest cost now; choose a VLTD vendor that can add telematics later |
| Mixed BS-IV and BS-VI fleet | Setup 3 with a device that supports both | One device type across vehicle generations simplifies installs and spares |
What should you check before you choose?
| Question | Why it matters |
| Is the device AIS-140 type-approved, and is the vendor empaneled in your states? | Only certified devices count for VLTD compliance; see AIS-140 certified GPS vendors in India |
| Does it register on VAHAN, and who does the registration? | An unregistered device fails at fitness and permit checks |
| Does it read vehicle data on your makes and BS generations? | Without engine data, there’s no maintenance or fuel insight |
| Does it send data to both the state platform and your platform? | That’s what lets one device do both jobs |
| Does it alert when unplugged or powered off? | An offline device is a compliance gap and a data gap |
| What’s the full cost per vehicle in rupees over the contract, for one device vs two? | Hardware, installation, SIMs, subscriptions and maintenance all add up; see AIS-140 device cost in India |
| Who owns the data, and can you export it? | You’ll want your operating history if you change vendors |
Related Article: Best OBD Fleet Devices in India Compared
How do you roll it out across a mixed fleet?
- Sort vehicles by compliance status: VLTD fitted and registered, fitted but not registered, or none.A VLTD already reports location, speed and alert events. With the right platform behind it, the same data supports trip replay for disputes, geofences for route adherence and early warning when a unit goes offline.
- Fix the urgent ones first: vehicles due for fitness or permit renewal without a registered VLTD.
- Pilot the combined setup on 10 to 20% of the fleet, covering each make and BS generation.
- Check both data paths during the pilot: VAHAN shows the device, the state platform receives data, and your platform receives vehicle data and alerts.
- Roll out by depot or route, retiring duplicate devices as vehicles move to one device.
For the compliance steps on their own, see VLTD rules for Indian commercial fleets.
How Intangles run VLTD compliance and fleet telematics on one device
Intangles’ InGenious device is AIS-140 certified and supports both BS-IV and BS-VI vehicles, so a mixed-generation fleet can standardize on one device for compliance and operations. It connects through the vehicle’s OBD port with no modifications and raises an alert if it’s unplugged or powered off, catching gaps before they surface at an inspection.
| What the fleet gets | From the same device |
| VLTD compliance | AIS-140 certified tracking with emergency buttons |
| Location tracking | Live position, trip history and geofences |
| Predictive health monitoring | Developing engine faults flagged early |
| Fuel monitoring | Fuel use and sudden drops |
| Driver behavior monitoring | DriveIQ flags 20+ behavioral exceptions, such as speeding and harsh braking |
Everything is managed in InRoute, Intangles’ fleet intelligence platform. Intangles works with Indian fleets in trucking and transit.
Discover how Intangles’ predictive analytics platform turns one AIS-140 certified device into compliance, vehicle health and fuel insights for your fleet.
Frequently Asked Questions
Can one device be both a VLTD and a fleet telematics device?
Yes, if it’s AIS-140 type-approved, registered on VAHAN with working emergency buttons, and also reads vehicle data and sends it to the fleet’s platform. The compliance data goes to the state platform; the operational data goes to the operator.
Does factory-fitted OEM telematics count as a VLTD?
Only if the unit itself is AIS-140 type-approved, has emergency buttons and is registered against the vehicle on VAHAN. Many factory systems are built for fleet management, not compliance, so check the certificate for your specific model rather than assuming.
If I already have GPS tracking, do I still need a VLTD?
Yes, for vehicles that fall under the rule. An ordinary GPS tracker doesn’t count, however much it reports. You can keep it alongside a VLTD, or replace both with one certified device that does both jobs.
Does VLTD data go to my fleet management software?
Not automatically. A VLTD’s compliance data goes to the state’s platform. Whether you also see it, and whether you get engine and fuel data, depends on the device and the platform behind it. Ask the vendor whether the device sends data to both.
Is one device cheaper than two?
Often, because you pay for one installation, one SIM and one device to maintain. But compare the full cost per vehicle in rupees over the contract, including subscriptions, and factor in what an existing telematics system would cost to replace.
Which setup is best for a mixed BS-IV and BS-VI fleet?
Usually one AIS-140 certified device that supports both generations, so every vehicle uses the same hardware for compliance and operations. Pilot it across each make and generation before rolling out.
We’re looking forward to meeting you