KEY TAKEAWAYS
- Most new Indian commercial vehicles now generate diagnostic data: BS VI brought OBD to heavy-duty vehicles in April 2020, and the stricter BS VI-2 OBD stage applied to all heavy-duty sales and registrations from April 2023.
- OBD shows that something has failed. It doesn’t show what is about to fail or why the same failure keeps repeating.
- Indian operating conditions (heat, dust, variable fuel quality, overloading and mixed BS-III to BS-VI fleets) make fault codes harder to interpret.
- Layering AI on OBD and CAN data turns isolated alerts into component-level health scores and predictions.
- Intangles’ digital twin combines OBD, CAN, GPS and sensor data into one view of each vehicle’s health, with 96% predictive AI accuracy.
Where is fleet health actually being managed today, and more importantly, why do breakdowns still happen despite having vehicle data?
Across India, lakhs of commercial vehicles operate under high-pressure conditions, with road transport carrying about 70% of domestic freight, according to Indian Infrastructure. Most fleets already use on-board diagnostics and telematics to monitor vehicle performance. Access to data isn’t the problem.
The challenge is using that data to prevent breakdowns before they happen. A truck that fails on a highway costs a tow, an emergency repair, idle crew time and a missed delivery, and those costs add up across a fleet. India’s logistics cost was 7.97% of GDP, or ₹24.01 lakh crore, in 2023–24, according to the DPIIT–NCAER Assessment of Logistics Cost in India, so every avoided breakdown matters.
This is where vehicle diagnostics is evolving. What started as basic fault detection through OBD is now shifting toward AI-driven vehicle health monitoring that can predict failures, not just report them.
In this blog, you will learn how OBD works in Indian commercial vehicles, where it falls short in Indian conditions, and how combining it with AI moves fleets from reactive repairs to predictive control in 2027.
Understanding OBD-II in Indian commercial vehicles
OBD-II is a standardized diagnostic interface that gives direct access to a vehicle’s internal systems. It captures critical parameters such as engine performance, fault codes, emissions data and real-time operating conditions through the OBD port on Indian trucks.
In practical terms, it marked the first structured step toward on-board diagnostics in India, as vehicles moved from purely mechanical systems to data-enabled machines.
In India, OBD reached heavy commercial vehicles with the BS VI emission norms in April 2020. For heavy-duty vehicles, OBD was introduced in two stages: BS VI-1 for type approvals from April 2020, and the stricter BS VI-2 stage for all sales and registrations from April 2023, according to Transport Policy. Earlier OBD requirements applied only to light-duty vehicles. For OBD-II basics, see what is OBD-II.
This created a foundational layer of visibility into engine health, fuel efficiency and compliance. But visibility alone did not solve operational inefficiencies.
What OBD-II provides and where it falls short
OBD-II provides a starting point for fleet visibility, not a complete view of vehicle health.
It gives access to:
- Engine fault codes and diagnostic trouble alerts
- Core engine parameters such as RPM, coolant temperature and throttle position
- Emission-related data required under regulatory standards
For fleets, this was a significant shift from reactive maintenance to basic real-time monitoring. However, the limitations are structural.
OBD-II does not explain why a failure is occurring. It does not indicate whether a component is likely to fail in the near future. It does not connect vehicle performance with driver behavior, load conditions or route stress. Most importantly, it does not correlate multiple signals to build a unified view of vehicle health.
In simple terms, OBD-II identifies that something has failed. It does not identify what is about to fail or what caused the failure pattern in the first place.
This gap is where traditional diagnostics end, and where fleet telematics and deeper analytics begin to matter, turning raw fault codes into actionable operational insight.
For why fleets with OBD still face breakdowns, and how to close each gap, see why OBD alerts miss fleet breakdown risks in India.
How OBD evolved in Indian commercial vehicles
The evolution of OBD in India has been closely tied to emission norms and regulatory upgrades.
- BS-IV (nationwide from April 2017): stricter emission limits, but no OBD requirement for heavy-duty vehicles.
- BS VI (April 2020): India skipped BS-V. Heavy-duty vehicles gained OBD (BS VI-1) along with after-treatment systems such as DPF and SCR.
- BS VI Phase 2 (April 2023): the stricter BS VI-2 OBD stage for all heavy-duty sales and registrations, plus real-driving-emissions conformity testing.
Each phase increased the data vehicles produce. None of them, on its own, improved how fleets use it.
Fleets gained access to more signals, alerts and parameters, but breakdowns, unplanned downtime and reactive maintenance cycles persist. More data does not automatically translate into better decisions.
For BS VI vehicles, after-treatment health matters too. DEF monitoring flags DEF level and quality problems before they cause engine derates.
How AIS-140 compliance shaped telematics in Indian transport
The AIS-140 regulation marked a major shift in how commercial vehicles are monitored in India. Under it, an AIS-140 certified vehicle location tracking device with an emergency (panic) button is mandatory for new public service vehicles registered from January 1, 2019, with auto-rickshaws and e-rickshaws exempt. Several states have also applied it to national permit vehicles.
Some fleets use AIS-140 trackers with OBD integration, combining location tracking with limited vehicle-level diagnostics. Together, these rollouts brought telematics to Indian transport at scale and gave fleets basic operational visibility.
At a functional level, these systems provide:
- Real-time vehicle location tracking
- Basic operational alerts
- Limited diagnostic and status signals
This was a significant step forward in fleet digitization. However, AIS-140 is fundamentally a compliance-driven framework, not an intelligence system.
While it improved visibility, it did not improve decision-making. Fleets gained data streams, but not the analytical capability to interpret them in operational context. As a result, large volumes of fleet data are generated every day, but only a fraction is used to improve uptime, maintenance planning or cost control.
This creates a clear gap between tracking vehicles and understanding vehicle health, and that gap widens as fleets grow.
Why India’s fleet challenges demand more than basic OBD
Fleet challenges in India are shaped by highly variable, high-stress operating environments. Instead of the controlled conditions that traditional diagnostic systems assume, Indian fleets face extreme weather, uneven terrain, congestion and inconsistent loads.
In this environment, OBD systems can detect faults, but they cannot explain why those failures keep repeating. This creates a gap between diagnostics and real operational understanding.
Extreme operating conditions in Indian fleets
Vehicles in India operate under continuous environmental and mechanical stress.
High temperatures, dust, traffic congestion and long operating hours accelerate wear on critical components such as brakes, engines and cooling systems. Over time, this leads to faster degradation than standard service intervals expect.
While OBD systems can detect failures or threshold breaches, they cannot interpret the operating context behind them. As a result, alerts remain reactive, not preventive, which limits their impact on maintenance.
Fuel quality and engine degradation risks
Fuel variability remains a persistent problem for commercial vehicles in India.
Inconsistent fuel quality and occasional adulteration directly affect combustion efficiency, leading to injector clogging, irregular mileage and increased engine stress. These issues often develop gradually and are difficult to isolate using standard diagnostic signals alone.
As a result, fleets often respond to symptoms instead of addressing the underlying cause of performance decline.
Overloading and long-term vehicle damage
Overloading continues to be a common practice in Indian freight movement because of short-term economic incentives.
However, the long-term impact on vehicle systems is significant. Suspension systems fatigue faster, braking efficiency drops under sustained load, and engine components operate under continuous strain.
Over time, these stresses accumulate, resulting in unexpected breakdowns and higher lifecycle maintenance costs, turning short-term gains into long-term losses.
Mixed fleet complexity in India
Most fleets in India are mixed, running a combination of BS-III, BS-IV and BS-VI vehicles.
Each category differs in sensor depth, diagnostic capability and data availability. This fragments visibility and makes it difficult to make consistent decisions across the fleet.
As a result, Indian fleets now need more than tracking or basic diagnostics. They need systems that can unify data across vehicle types and give a consistent view of fleet health.
The core challenge in Indian fleet operations is not data collection. It is interpreting that data in real-world operating environments.
This gap between visibility and understanding is what stops traditional diagnostics from improving uptime, cost efficiency and long-term fleet performance.
Why OBD and AI together matter for fleets in India
Vehicle behavior in India is not uniform. It changes with route conditions, driver behavior, load variations and operating environments. This variability is one of the key reasons why OBD alone is not enough for long-term fleet control.
OBD systems are effective at identifying faults, but they operate in isolation. They do not interpret patterns or explain why failures repeat. When AI is layered over OBD data, fleets move beyond fault detection into continuous vehicle understanding. This is where vehicle health monitoring in India shifts from reactive tracking to predictive intelligence.
Vehicle health monitoring at component level
With AI applied on top of OBD and sensor data, vehicle health can be understood at a much more granular level. Instead of viewing the vehicle as a single unit, each component builds its own performance profile over time
This changes how fleets interpret degradation. A component does not simply fail suddenly. It shows patterns of stress that build up gradually, often influenced by usage and operating conditions. AI helps surface these patterns early, before they turn into breakdowns.
What changes is not just visibility, but timing. Issues are identified earlier in their lifecycle, which lets fleets intervene before failures affect operations. This improves reliability and reduces unexpected downtime.
Predictive maintenance based on real vehicle usage
Traditional maintenance planning assumes that vehicles degrade uniformly over time. In real fleet operations, usage is highly uneven. Some vehicles run heavy loads every day, while others follow shorter or less demanding routes.
When OBD data is combined with AI models, maintenance shifts from time-based to usage-based.
Instead of servicing vehicles at fixed intervals, fleets can align maintenance with actual wear. This reduces unnecessary servicing and ensures maintenance happens when it is truly needed. Over time, this lowers operating costs and makes better use of workshop capacity.
Connected intelligence across vehicle, driver and route
Most fleet issues are not caused by a single factor. They emerge from the interaction between driver behavio
Most fleet issues are not caused by a single factor. They emerge from the interaction between driver behavior, route conditions and vehicle health. Without connecting these data points, fleets only see fragments of the problem.
AI brings these signals together into a unified view. Fleets can see how driving patterns affect vehicle performance and how specific routes contribute to faster wear.
This connected view makes recurring operational risks visible. For example, certain routes may consistently lead to higher engine stress, or specific driving behaviors may correlate with faster component wear.
Once these relationships are visible, fleets can move from reacting to breakdowns to preventing them through informed operational changes.
r, route conditions, and vehicle health. Without connecting these data points, fleets only see fragments of the problem.
AI helps bring these signals together into a unified view. With AI vehicle tracking India, fleets can understand how driving patterns impact vehicle performance and how specific routes contribute to faster wear.
This connected intelligence makes it possible to identify recurring operational risks. For example, certain routes may consistently lead to higher engine stress, or specific driving behaviors may correlate with faster component degradation.
Once these relationships are visible, fleets can move from reacting to breakdowns to preventing them through informed operational changes.
From reactive repairs to predictive fleet control
When OBD and AI work together, fleet operations change fundamentally. Instead of responding after a failure, fleets can anticipate issues before they occur. Maintenance becomes planned rather than urgent. Downtime becomes scheduled rather than unexpected. Decisions are based on condition rather than assumption.
This is the core value of combining diagnostics with intelligence. It is not about collecting more data. It is about using existing data to understand vehicle behavior and improve operational control.
Use cases: how fleets are using OBD data today
In India, fleet operators increasingly use on-board diagnostics for real-world operational decisions. While OBD data is still limited in scope, it already improves visibility across vehicle performance, maintenance needs and operational efficiency.
However, its value is mainly in detection and reporting. The interpretation layer is still limited, which is why most fleets use OBD data as a supporting input rather than a decision system.
Reducing breakdowns and roadside failures
One of the most common uses of OBD data is early fault detection. Alerts for overheating, battery issues or engine misfires help fleets catch potential failures before they escalate.
This lets maintenance teams act while the vehicle is still in operation or at a scheduled stop, instead of reacting to breakdowns on highways or long-haul routes. In practice, this reduces unplanned downtime and improves vehicle availability.
However, these alerts are event-based, not predictive. They show failure conditions but do not always explain recurrence patterns.
Improving fuel and emissions performance
OBD data also helps monitor fuel consumption and emission-related performance across vehicles, routes and drivers.
Fleet operators use it to spot inefficiencies such as excessive fuel use or mileage below expected levels. This matters for BS-VI compliance and for cost control in operations where fuel is a large share of spend.
While this improves visibility, it still works at a reporting level rather than a corrective or predictive level.
Detecting abuse and misuse
Driver behavior directly affects vehicle health and operating costs. OBD data helps identify harsh acceleration, sudden braking, excessive idling and unauthorized route use.
These insights help fleets reduce misuse and improve driving discipline over time. In many cases, this also means fewer mechanical failures caused by poor vehicle handling.
Driver behavior monitoring builds on this foundation by adding structured behavior scoring and risk interpretation.
Supporting warranty, insurance and resale
Historical OBD data creates a digital record of how each vehicle has been used. This improves transparency in warranty claims and supports insurance processes with usage-backed evidence.
In resale, vehicles with consistent performance records and well-documented maintenance histories tend to hold their value better than vehicles with limited or unclear data.
This makes OBD data not just an operational tool, but also a financial and asset-value tool for fleet owners. Although it delivers clear operational benefits, it is still largely analyzed in isolation.
It provides signals, but not system-level intelligence. This is where its limits show in complex fleet environments, and where more integrated, AI-driven approaches to vehicle health come in.
How Intangles turns OBD and CAN data into a vehicle health “brain”
Most fleets already generate large volumes of data. The challenge is not availability, but fragmentation. OBD systems capture faults, GPS tracks location, and sensors record operational signals, but these data streams often sit in silos.
On their own, they provide partial visibility. They do not explain how vehicle behavior, operating conditions and component health are connected. This is where Intangles takes a fundamentally different approach to predictive health monitoring. Instead of treating data as isolated inputs, it builds a unified intelligence layer where every signal contributes to a continuous understanding of vehicle health.
The system combines OBD data, CAN bus data, GPS movement patterns and sensor streams such as fuel level and temperature into a single operational view of the vehicle. Intangles’ device connects through the OBD port with no vehicle modifications.
Data fusion across OBD, GPS, CAN and sensors
The key shift is not in data collection, but in data interpretation. Instead of switching between multiple dashboards, all signals are integrated into one telematics analytics platform that consolidates vehicle behavior into a single view. This removes noise and surface patterns that are otherwise invisible.
A fuel drop is no longer treated as an isolated event. It can be linked to route conditions, driving behavior or load variation. Similarly, a fault code is not just a warning signal. It is interpreted in the context of usage history and operating stress.
This connected layer is what moves AI-based vehicle health monitoring from reactive alerts to structured decision support.
Digital twin for real-time vehicle health monitoring
At the core of this system is a digital twin model, where each vehicle is represented as a continuously evolving digital counterpart.
Instead of static records, the vehicle becomes a live model that updates with every trip, capturing how components behave under real operating conditions.
Through this model, fleets get:
- A real-time health score for each vehicle
- Component-level risk indicators that evolve over time
- Predictive alerts that identify likely failure points before breakdowns occur
Intangles’ predictive AI runs at 96% accuracy, so issues are no longer detected after failure. They are anticipated based on degradation patterns and usage context.
For fleets using Intangles’ digital twin, this enables a shift from fixed maintenance schedules to condition-based intervention.
From data visibility to operational intelligence
The real shift is subtle but significant. Fleets move from reacting to breakdowns to anticipating them. Maintenance decisions become targeted, downtime becomes predictable, and operational planning becomes data-driven rather than assumption-based.
Instead of managing vehicles as individual assets, fleets begin managing them as a connected system of behaviors, components and conditions.
This is where fragmented telematics ends, and unified vehicle intelligence begins.
How to implement a vehicle health monitoring system in fleet operations
Moving from basic diagnostics to AI-driven monitoring does not require a complete infrastructure overhaul. Most fleets already have the building blocks in place, including AIS-140 devices, OEM connectivity and OBD-based systems.
The shift is less about adding more tools and more about using existing data better through a structured rollout.
Step 1: Audit existing fleet data systems
The first step is to identify what is already available in the fleet.
In many cases, fleets already run a mix of AIS-140 trackers, OEM telematics connections and aftermarket OBD devices. However, this data often remains underused or disconnected across systems.
A clear audit maps existing data sources, avoids duplication and lays the foundation for a structured vehicle health monitoring system.
Step 2: Run a predictive maintenance pilot
Scaling across the entire fleet at once often creates noise rather than clarity.
A better approach is to start with a defined pilot group. This could include vehicles on high-risk routes, older vehicles with more frequent breakdowns, or specific OEM categories.
A focused pilot shows whether early alerts improve uptime, reduce breakdowns and improve maintenance planning before a wider rollout.
Step 3: Define fleet performance KPIs
Without defined metrics, fleet visibility does not translate into operational value.
Key KPIs typically include breakdown frequency, maintenance cost per kilometer, fuel consumption trends and overall vehicle uptime. These indicators show whether the system is delivering real operational improvements.
Tracking these KPIs keeps decisions based on measurable outcomes rather than assumptions, especially in the early stages of AI-based monitoring.
Step 4: Integrate insights into fleet workflows
Data alone does not improve fleet performance. The real impact comes when insights are built into operational workflows.
This means connecting alerts and diagnostics with existing telematics platforms, maintenance systems and workshop processes. Equally important is defining clear response workflows: who acts on an alert, how quickly, and what resolution steps follow. Alerts are only useful when someone owns them, and operations automation turns them into scheduled workshop jobs.
Without this integration, even advanced monitoring systems remain underused.
The shift from reactive maintenance to predictive control is not held back by a lack of data, but by how effectively that data is used.
The impact builds over time. Breakdowns fall not just because faults are detected earlier, but because patterns across the fleet become visible. Maintenance becomes more targeted, and operational planning becomes more predictable.
In most fleets, the data needed for this already exists. AIS-140 systems, OBD inputs and OEM telemetry already generate continuous signals. The gap is not in availability, but in how effectively that data is turned into action.
When fleet decisions shift from reacting to failures to preventing them, reliability becomes more stable and easier to manage at scale. This is where AI-enabled vehicle health monitoring moves from being a visibility layer to an operational advantage.
For fleet managers, the next step is not collecting more data, but structuring how existing data is used to improve uptime, reduce breakdowns and control maintenance costs. Intangles helps fleets connect vehicle data, failure patterns and maintenance workflows into one system that supports real-time decisions across operations.
For how AI is changing fleet management across India more broadly, see how AI is revolutionizing fleet management systems in India. Intangles works with fleets in trucking, construction and mining across India.
Discover how Intangles’ predictive analytics platform can turn the OBD data your fleet already generates into early warnings that prevent breakdowns in 2027.
KNOW MORE
Frequently Asked Questions
Is AI-based vehicle health monitoring only for large fleets?
No. Smaller fleets often see results faster, because avoiding even a few breakdowns makes a visible difference to a small operation. Most platforms can start with a handful of vehicles and scale up, and the key is reviewing the data consistently.
How much does AI-powered vehicle health monitoring cost for an Indian fleet?
The cost depends on hardware, data capture and analytics. OBD-based telematics is relatively affordable, and the return comes from fewer breakdowns, better fuel efficiency and lower maintenance spend. Compare vendors on full cost per vehicle in rupees over the contract, including installation and support.
What if my fleet has many older vehicles without OBD-II?
This is common in India. Older vehicles can still be monitored with retrofit kits, CAN bus readers where available, or external sensors that capture fuel consumption, temperature and other key usage parameters. A mixed fleet strategy works, with newer vehicles providing richer data than older ones.
How much data does OBD telematics generate, and is it expensive to store?
OBD telematics generates a continuous stream of engine performance and vehicle health data. Storage is not a real constraint today, because cloud storage handles these volumes efficiently and at low cost. The real challenge is using the data effectively.
Why does vehicle health monitoring need to be different for Indian conditions?
Indian fleets operate in highly stressful conditions, with extreme temperatures, dust, heavy traffic, overloading and variable fuel quality. Conventional diagnostic models assume stable environments and may miss these variables, so vehicle health monitoring in India needs to account for real operating context.
When did OBD become mandatory for commercial vehicles in India?
For heavy-duty commercial vehicles, OBD requirements came with the BS VI emission norms in April 2020, in two stages: BS VI-1 OBD for type approvals from April 2020, and the stricter BS VI-2 OBD stage for all sales and registrations from April 2023, alongside real-driving-emissions conformity testing. Earlier OBD I and OBD II requirements applied to light-duty vehicles only.
We’re looking forward to meeting you