AIS-140 Compliance in 2025: A Field Guide for Fleet Owners
AIS-140 requires certified Vehicle Location Tracking (VLT) units with GNSS (GPS/IRNSS support), a physical one-time panic button, secure data push to government back-ends (Vahan/state emergency systems), health checks and type approval under CMVR rules — plus backend registration/activation and yearly conformity testing. (Ministry of Road Transport & Highways)
Why this matters
- Legal: AIS-140 / Motor Vehicles Order mandates VLT + panic button for many public-service vehicles; non-compliance can trigger fines, impoundment, or permit issues.(Press Information Bureau)
- Safety: Panic alerts + precise PVT (position/velocity/time) greatly speed emergency response when correctly routed to State emergency systems.(Ministry of Road Transport & Highways)
- Operational upside: AIS-140 telemetry, once ingested into your platform, becomes fuel for analytics (route adherence, overspeed alerts, device health), reducing claims and downtime.(transight.com)
What AIS-140 actually requires
Core device / VLT features
- GNSS location (GPS; support for IRNSS/NAVIC and hybrid constellations where applicable).
- Embedded SIM / UICC and multi-network capability for resilient cellular connectivity.
- Panic/Emergency button(s) (one-time press, "normally closed" wiring, server-acknowledged reset).
- Ability to send PVT and a defined set of diagnostic fields to the Backend Control Centre (packet formats and fields are defined in the protocol).
- Device identifier (IMEI), non-volatile logs, backup SMS fallback, and minimum storage for offline logging.
- Operable on vehicle power ranges (12V/24V) and tested for automotive environmental conditions.(Ministry of Road Transport & Highways)
Backend & integration
Devices must push activation & periodic health checks to an authorised backend, which integrates with Vahan (registration), state emergency response systems and permit-holder interfaces. States may operate their own backend or allow authorized VAS providers/telecoms.(Ministry of Road Transport & Highways)
Testing & certification
Type approval & device testing is via agencies referenced under CMVR Rule 126 (e.g., ARAI/ICAT/testing bodies). Manufacturers must perform conformity of production (CoP) testing annually from initial certification. Backend systems also require certification.
Sampling / transmission specifics
Configurable highest transmit rate during operation (e.g., up to 5 sec) and a lower sleep/IGN-OFF rate (not less than 10 minutes) per protocol. Devices must also support health check message formats and activation message flows. (Ministry of Road Transport & Highways)
Who needs it & timeline
The Motor Vehicles Order and subsequent MoRTH guidance mandated VLT + emergency buttons for new public service vehicles registered on/after 1 Jan 2019; states may set enforcement timelines for older fleets and retrofits. Always verify your vehicle category with local RTO rules.(Press Information Bureau, Ministry of Road Transport & Highways)
Step-by-step: How to make a vehicle AIS-140 compliant
- Procurement: pick an ARAI/ICAT-tested VLT (type-approved) model. Ask for certificate number, CoP schedule and test reports.
- Confirm device features: panic button wiring (NC), embedded SIM (UICC), OTA firmware, backup SMS capability, required I/Os (digital/analog/CAN) and storage (≥40,000 position logs as per spec).(Ministry of Road Transport & Highways)
- Install professionally (manufacturer/authorized dealer). Ensure mounting location is secure/not accessible to passengers (unless HMI is required) and emergency buttons are reachable per seating arrangement guidance.
- Configure connectivity — set the device to send to the State backend/common layer IPs, configure SMS gateways and activation reply numbers (as required).
- Activate & register — Manufacturer/dealer must register the device IMEI/ICCID and vehicle mapping in Vahan (or the State backend) in real time during installation. Permit-holder can verify in Vahan.
- Run health checks & validation — execute the activation message/health check SMS flow and confirm the backend receives packets and shows device status. (States may require activation printouts.)
- Train operations — SOP for panic button events (acknowledge, dispatch, escalation), periodic in-field tamper checks, and a quarterly drill for response teams.
- Maintain CoP & firmware — manufacturer must conduct annual CoP tests; ensure firmware is up to date and device OEM tracks SIM validity.
Backend, alerts & incident flow
Device → primary IP (Operational Backend) + secondary IP (Regulatory/Emergency endpoint) → State Emergency Response System / Vahan update → Permit holder / Control Room notifications. Emergency alerts must be delivered to the state emergency backend and the permit-holder (as the State decides). Devices should support at least two IP addresses for alert routing and fall back to SMS if cellular is unavailable.(Ministry of Road Transport & Highways)
Practical KPIs & recommended thresholds
| KPI | Recommended target (practical) |
|---|---|
| Device activation time | < 24 hours from installation |
| Device online rate | ≥ 99% (daily availability) |
| Health-check response success | 100% for scheduled checks; alerts generated within 1 minute for missing checks |
| Panic alert delivery latency (to state backend) | ≤ 30 seconds (network permitting) |
| Packet GPS accuracy (DRMS) | ≤ 6 m (65% DRMS target in AIS-140 tests) |
These targets are operational best practices based on AIS-140 test/field requirements and state SOPs — tune to your connectivity environment. (Ministry of Road Transport & Highways)
Quick printable checklist
- Ask vendor for Type Approval Certificate no. (ARAI/ICAT) and CoP schedule.
- Verify IMEI is unalterable and logged in the device. (Ministry of Road Transport & Highways)
- Confirm embedded SIM with multi-operator OTA switching support. (hmr.araiindia.com)
- Panic button: one-time press, NC wiring, accessible per seating plan.
- Device power test: 12/24V tolerance; sleep current ≤ required spec. (hmr.araiindia.com)
- Configure two IP addresses and SMS gateway in device.
- Complete Vahan activation + print activation report.
- Setup health check frequency & alerting in backend.
- Document SOP for panic handling & quarterly drills.
- Plan annual CoP tests and firmware update cycles.
Short, anonymised case outline
Problem: City bus operator had 12% of vehicles offline >24 hr, slow panic acknowledgement, and inconsistent activation records.
Action: Replaced uncertified devices with ARAI-tested VLTs, enforced dealer-led installs with Vahan activation, configured two IPs + SMS fallback and dashboard health alerts.
Result (simulated template to adapt to your telemetry): Device online increased to 99.3%; median panic-to-ack decreased from 7 min → 45 sec; RTO audit compliance time reduced to minutes (activation report ready).
Note: Use your anonymized telemetry to populate the actual before/after numbers for a publishable case study.(Ministry of Road Transport & Highways)
FAQ
Key citations
- MoRTH — Finalized Draft AIS-140 (technical protocol, packet formats and functional requirements). (Ministry of Road Transport & Highways)
- ARAI — Amendment No.2 / Code of Practice (device testing, backend certification, CoP, Vahan integration). (ARAI)
- MoRTH / PIB and official notices — Motor Vehicles Order and mandate timing (Jan 1, 2019 guidance). (Press Information Bureau)
- Transight — vendor overview & practitioner language (your provided source). (transight.com)
- State SOPs (example West Bengal / Punjab) — practical steps for activation & device enlistment. (Transport WB)
Need Help with AIS-140 Compliance?
Get expert guidance on implementing AIS-140 compliant solutions for your fleet. Our team can help you choose the right devices, ensure proper installation, and navigate the certification process.