
A vehicle does not always announce a developing fault with a dashboard warning light. Battery voltage can deteriorate, engine temperatures can drift and diagnostic systems can register potential faults before a warning becomes visible. Real-time vehicle monitoring helps identify these changes early enough for an owner or fleet manager to investigate and arrange maintenance before a minor issue becomes an unexpected breakdown.
For a business operating five to seventy vehicles, the practical benefit is not constant observation of drivers. It is better information about vehicle condition, more predictable maintenance and fewer avoidable interruptions. Connected monitoring can bring diagnostic information into one place, helping managers decide which vehicle needs attention and when.
The two-week idea in this article is a useful planning perspective, not a guaranteed countdown. Some developing faults may provide warning signs over several weeks; others can escalate much faster. The value of monitoring depends on the vehicle, the component, the available sensors and the quality of the diagnostic system. Combining those signals with scheduled maintenance creates a more reliable approach than waiting for a warning light or relying on memory.
Real-Time Vehicle Monitoring: Key Points
- Monitoring can identify developing diagnostic faults and abnormal sensor trends before a dashboard warning appears, but no system guarantees a two-week prediction window.
- Three alert levels, sensible thresholds and regular reviews help distinguish actionable problems from notification noise.
- OEM systems and aftermarket telematics serve different fleet requirements; vehicle compatibility, data access, privacy and total ownership costs should guide the choice.
- Why Can Real-Time Monitoring Detect a Failure Before Any Warning Light Appears?
- How to Set Monitoring Alerts So You Don’t Get Spammed While Still Catching Real Problems?
- OEM Monitoring or Aftermarket Telematics: Which Works Better for 5 Vehicles?
- The Monitoring Mistake That Gives You Data but Still Leaves You With Breakdowns
- When Should You Review Monitoring Reports to Prevent Issues Without Extra Admin?
- How to Set Up Maintenance Tracking in 20 Minutes Without Buying Any Software?
- OEM Monitoring or Aftermarket Telematics: Which Works Better for 5 Vehicles? (Fleet-Wide Cost and Rollout Perspective)
- How Maintenance Tracking Prevents the “I Forgot” Repair That Costs £900
Why Can Real-Time Monitoring Detect a Failure Before Any Warning Light Appears?
Real-time vehicle monitoring can sometimes detect a developing fault before a dashboard warning appears because it examines diagnostic information and changes in vehicle operating data, rather than waiting for a warning threshold to be reached. Some onboard diagnostic systems also store a pending fault code before activating the malfunction indicator light. However, early detection depends on the fault, the vehicle’s diagnostic logic and the monitoring equipment.
A dashboard warning light is not a continuous assessment of every component’s remaining lifespan. It is an indicator activated according to diagnostic rules established for particular vehicle systems. Depending on the fault and diagnostic strategy, a warning may appear after a threshold is exceeded or after a fault has been detected across multiple driving cycles.
Monitoring adds value by examining three different signal families:
- Pending diagnostic trouble codes: An onboard diagnostic system can record a potential fault before confirming it and illuminating the malfunction indicator light. The code indicates something worth investigating, not necessarily a failed component.
- Sensor trend deviations: Repeated readings can reveal changes in battery voltage, coolant temperature or other available operating parameters. A persistent deviation from a vehicle’s normal behaviour may justify an inspection.
- Usage-pattern anomalies: Repeated cold starts, unusual operating conditions or changes in vehicle usage can provide additional context when interpreting diagnostic information.
The distinction between a pending and confirmed diagnostic trouble code is particularly important. The EPA technical report on on-board diagnostic systems explains that some diagnostic algorithms initially store a pending code and activate the malfunction indicator light only if the fault is detected again during a subsequent trip. Other diagnostic strategies may activate the light after a single detection.
This does not mean that every pending code becomes a serious mechanical failure. Some codes may disappear if the fault does not recur, while others require further diagnosis. The correct response is to interpret the code in the context of the affected system and the vehicle manufacturer’s diagnostic information.
Predictive diagnostics can also use more advanced methods. Research published by SAE International describes a machine-learning approach using vehicle Controller Area Network (CAN) data to identify impending faults. Its research application involved an air-conditioning compressor system. This demonstrates a technical approach to predictive fault diagnosis, not a universal commercial capability or a validated two-week warning period for every vehicle.
The prediction window depends on the component. A battery may show a gradual deterioration that becomes visible through repeated measurements. A cooling-system problem, by contrast, can develop into an overheating event much more quickly. A monitoring platform cannot reliably turn every abnormal reading into an exact date of failure.
For small fleets, this distinction changes how monitoring should be used. The objective is to identify abnormal vehicle behaviour, confirm whether it matters and arrange an appropriate inspection. It is not to build a detailed picture of where every driver goes or how they behave.
Early detection creates an opportunity to intervene, but only when the information is interpreted correctly. The next step is ensuring that useful signals generate proportionate alerts rather than a constant stream of notifications.
How to Set Monitoring Alerts So You Don’t Get Spammed While Still Catching Real Problems?
The most effective monitoring alerts separate minor changes from problems requiring action. A three-tier structure works well for small fleets: informational alerts for trends worth reviewing, warnings for persistent deviations requiring attention within days, and critical alerts for immediate safety-related action. This approach prevents every diagnostic event from being treated as an emergency.
Alert fatigue usually starts when a monitoring platform sends notifications without distinguishing their practical importance. A single unusual reading should not automatically trigger the same response as a persistent fault affecting a safety-related system.
A useful configuration separates alerts into three levels:
| Alert level | Typical purpose | Recommended response |
|---|---|---|
| Informational | A trend or minor deviation worth recording | Review during the next scheduled fleet check |
| Warning | A persistent abnormal reading or recurring diagnostic issue | Investigate and arrange appropriate action within days |
| Critical | A potentially serious fault or safety-related condition | Follow the vehicle’s safety instructions and arrange immediate assessment |
For example, a gradual change in a non-critical operating parameter may be suitable for a scheduled review. A persistent battery-voltage issue may justify a warning and a battery test. An overheating warning requires a much more urgent response, including stopping safely when the vehicle manufacturer’s instructions indicate that continued driving is unsafe.
Pending diagnostic codes deserve particular attention. An alerting system that sends a notification for every pending code can create unnecessary interruptions. The EPA report discussed earlier explains that some pending codes are not confirmed and may be erased when a fault does not recur, subject to exceptions for certain diagnostic monitors. Therefore, a pending code should trigger interpretation rather than an automatic repair decision.
Where the platform supports it, configure notifications around persistence, affected systems and diagnostic severity. Do not automatically downgrade an emissions-related code: emissions faults can still require investigation, and classification alone does not establish that a problem is harmless.
A practical calibration method is to begin with the platform’s default settings and evaluate the results over the first month. Record the alerts received, the vehicle involved, whether the issue was confirmed and whether any action was necessary. Then review recurring notifications and adjust those that consistently produce no useful outcome, without weakening safety-critical warnings.
For each alert, ask three questions: Is the signal persistent? Does it concern a system that can affect vehicle safety or reliability? Is there a clear next action? This makes the alert history a practical tool for improving the configuration rather than an ever-growing notification archive.
The objective is not to receive fewer notifications at any cost. It is to make sure that important information remains visible and that drivers and fleet managers understand what each notification actually requires.
OEM Monitoring or Aftermarket Telematics: Which Works Better for 5 Vehicles?
For a five-vehicle fleet, OEM monitoring is often attractive when vehicles come from the same manufacturer and the owner wants integrated vehicle information. Aftermarket telematics is generally worth considering when vehicles come from different brands and a single fleet dashboard is a priority. Neither solution is automatically better: diagnostic coverage, compatibility, data access and subscription terms determine the practical choice.
OEM monitoring is built into the vehicle or provided through the manufacturer’s connected services. Because it is integrated with the vehicle’s systems, it may expose manufacturer-specific diagnostic information and provide access to features that a generic diagnostic device cannot read.
However, information may be distributed across separate manufacturer applications or portals. A fleet with vehicles from several manufacturers may therefore need to consult multiple systems unless an integration is available.
Aftermarket telematics commonly uses an OBD-II device or a hardwired installation. A compatible platform can bring information from different vehicles into a common dashboard. The trade-off is that the information available depends on vehicle compatibility, diagnostic access and the capabilities of the provider’s hardware and software.
The U.S. Department of Energy‘s guidance on fleet telematics distinguishes OEM-installed, aftermarket and temporary telematics systems. It also discusses diagnostic information, reporting, data access and security considerations.
| Decision criterion | OEM monitoring | Aftermarket telematics |
|---|---|---|
| Installation | Integrated into the vehicle or factory-connected system | May use an OBD-II dongle or hardwired installation |
| Diagnostic access | May provide manufacturer-specific information | Depends on device, vehicle and provider compatibility |
| Mixed-brand fleet | May require multiple manufacturer portals | Can offer a common dashboard across supported vehicles |
| Maintenance information | Depends on manufacturer services and vehicle capabilities | Depends on supported diagnostic parameters and integrations |
| Data management | Subject to manufacturer access and export policies | Subject to telematics provider access and export policies |
| Physical equipment | Usually factory integrated | May require an externally installed or plug-in device |
There are three practical issues to check before choosing either option.
- Vehicle age and compatibility: Older vehicles may not support the same diagnostic features as newer models. Vehicles registered before 2010 should be checked individually rather than assumed to provide complete standard OBD-II data.
- Diagnostic port availability: An aftermarket dongle occupies the diagnostic connection. Check whether it interferes with routine garage diagnostics, whether it can become dislodged and whether the installation is suitable for the vehicle.
- Data portability: Ask whether the owner can download historical records, share diagnostic information with an independent mechanic and retain usable records after cancelling the subscription.
Data portability is particularly important for a small business. A low monthly subscription is less attractive if historical information becomes inaccessible when the contract ends. Before purchasing, request written clarification on raw data exports, retention periods, account closure and the ability to share information outside the provider’s platform.
Warranty questions also deserve care. Factory integration does not automatically make every OEM service suitable for every vehicle, and an aftermarket installation does not automatically invalidate a manufacturer’s warranty. Check the actual warranty terms and installation requirements rather than relying on general claims.
Privacy should be part of the purchasing decision. Vehicle diagnostic data and driver-related information are not necessarily the same thing. A fleet owner should understand whether a platform collects GPS location, journey history, driver identifiers or only technical vehicle information, and configure access according to the business purpose.
For five vehicles, a common dashboard can save administrative effort, but it should not come at the expense of missing diagnostic information or unclear data ownership. A short pilot is more reliable than committing the entire fleet to a system based on a demonstration alone.
The Monitoring Mistake That Gives You Data but Still Leaves You With Breakdowns
The biggest monitoring mistake is collecting vehicle data without defining what happens when an abnormal reading appears. A dashboard cannot prevent a breakdown by itself. If nobody reviews the alert, confirms the problem or arranges the appropriate maintenance, the information remains unused and the underlying fault can continue developing.
This problem is particularly common when a small business introduces telematics without assigning operational responsibility. The owner may assume that the system will automatically organise maintenance, while the driver assumes someone else is checking the notifications.
The solution is to create a response rule for each alert category. Every important notification should have three elements:
- An owner: The person responsible for reviewing and responding to the alert.
- A defined action: For example, arrange a diagnostic inspection, book a service or take the vehicle out of use when safety instructions require it.
- A response timeframe: The period within which the issue must be investigated, based on its severity.
For example, a recurring battery-voltage warning could be assigned to the fleet manager, who arranges a battery and charging-system test. A critical temperature alert may require the driver to stop safely and follow the manufacturer’s instructions rather than continue the journey while waiting for an office review.
There is also an opposite mistake: acting too quickly on a single weak signal. A temporary change in a sensor reading does not necessarily prove that a component needs replacing. Replacing parts without confirming the fault increases maintenance expenditure and can undermine confidence in the monitoring system.
A better approach is to cross-check a non-critical abnormal trend over two or three trips, where appropriate, and compare it with other available information. A mechanic can then use diagnostic equipment and physical inspection to confirm whether intervention is needed. This confirmation process must never delay action when a critical safety warning requires an immediate response.
For a five-vehicle fleet, even a small number of unresolved notifications can accumulate. Without assigned responsibilities, the fleet manager may discover the same issue repeatedly without knowing whether anyone has acted on it.
Monitoring becomes operationally useful when each meaningful alert creates a documented decision. That decision may be to inspect, repair, monitor or close the alert after investigation. The important point is that the decision is recorded and has an accountable owner.
Once responsibilities are clear, the remaining challenge is making sure the information is reviewed often enough to catch developing problems without creating another administrative burden.
When Should You Review Monitoring Reports to Prevent Issues Without Extra Admin?
A small fleet does not need constant manual dashboard checks to benefit from connected monitoring. A practical routine combines a short weekly review, a more detailed monthly assessment and immediate attention to critical alerts. The right frequency depends on vehicle usage, operational risk and how quickly the monitoring platform reports important changes.
Different review sessions should answer different questions. A weekly glance is designed to identify unresolved warnings and obvious red flags. A monthly review looks for patterns that may not trigger individual alerts but could indicate changing vehicle condition or operating costs.
Weekly review: approximately 5–10 minutes. Review the fleet overview and check for critical notifications, persistent warnings and unresolved maintenance actions. Identify which vehicles require follow-up and confirm that previous alerts have an owner.
Monthly review: a deeper maintenance assessment. Compare monitoring information with the maintenance schedule. Depending on the platform, useful indicators may include changes in fuel consumption, battery voltage, engine operating temperatures and idle time. These are indicators for investigation, not proof of a specific mechanical failure.
Event-driven review: when something important happens. A critical alert, an unusual operating condition or a long journey planned for a vehicle may justify checking the relevant information outside the normal schedule. Safety-related notifications should not wait until the next weekly review.
The Department of Energy’s fleet telematics guidance discusses automated reporting on weekly, monthly and quarterly schedules. These are available reporting approaches, not mandatory review intervals for every small business.
The simplest way to make this routine sustainable is to attach it to something that already happens. A Monday fleet check, monthly fuel-card reconciliation or invoicing day can provide a natural reminder. This avoids creating another independent task that relies on someone remembering to open the monitoring application.
There should also be a limit to the amount of information collected for manual review. If the process regularly takes more than ten minutes or expands into several pages of metrics, reconsider which indicators genuinely influence maintenance decisions. A smaller set of useful measures is easier to maintain than a comprehensive report nobody reads.
Monitoring reports work best alongside a basic maintenance calendar. The calendar handles predictable servicing, while connected diagnostics help identify issues that do not follow a fixed schedule.
How to Set Up Maintenance Tracking in 20 Minutes Without Buying Any Software?
A basic vehicle maintenance tracker can be created in around 20 minutes using a spreadsheet or phone calendar. Record each vehicle, its current mileage, the manufacturer’s service requirements and the next maintenance date or mileage. Then create reminders early enough to arrange the work before the relevant service interval is reached.
This approach is suitable for owners who need a simple way to remember routine servicing without purchasing a fleet management subscription. It is not a predictive diagnostic system, but it can prevent avoidable maintenance delays caused by missing information or forgotten appointments.
The setup can be completed in five steps:
- List the vehicles. Create one entry for each vehicle, including its registration reference, make, model and year. The deliverable is a complete fleet list.
- Find the correct maintenance schedule. Consult each vehicle’s handbook or the manufacturer’s official maintenance information. Record the relevant service intervals. The deliverable is a vehicle-specific schedule.
- Record current mileage. Note the current odometer reading and the date it was checked. The deliverable is a dated mileage baseline for every vehicle.
- Calculate the next service reminder. Identify the next applicable time- or mileage-based maintenance requirement and set an earlier reminder. The deliverable is a calendar entry for each upcoming service.
- Assign responsibility. Decide who checks mileage, books appointments and confirms completed work. The deliverable is a named owner and a maintenance status for every vehicle.
The reminder buffer should reflect the time needed to arrange and complete maintenance. A business that uses a garage with long booking lead times needs to schedule reminders earlier than one that can obtain an appointment quickly. After the first service cycle, adjust the reminder based on the actual time required to book and complete the work.
Manufacturer schedules matter. Generic online advice cannot replace the maintenance requirements for the specific vehicle, model year and operating conditions. Some vehicles also have more demanding maintenance schedules when used for intensive commercial work, frequent short journeys or other severe operating conditions.
The UK Health and Safety Executive‘s guidance on vehicle inspection and planned maintenance recommends scheduling preventive inspections according to time or mileage and following manufacturer guidance. It also highlights the importance of checking safety-related components and reporting faults.
A spreadsheet can include the following columns:
| Field | Information to record |
|---|---|
| Vehicle reference | Registration or internal fleet identifier |
| Current mileage | Latest odometer reading and check date |
| Maintenance requirement | Service item specified by the manufacturer |
| Next due point | Applicable mileage or date |
| Reminder | Date or mileage at which booking should begin |
| Responsible person | Person arranging or confirming the work |
| Status | Planned, booked, completed or requiring follow-up |
The limitation is important: a maintenance calendar tracks what should happen according to a schedule. It cannot independently identify a battery that is deteriorating unexpectedly, an abnormal temperature trend or a developing diagnostic fault between services.
That is why calendar-based maintenance and real-time vehicle monitoring should be treated as complementary systems. One prevents predictable servicing omissions; the other adds information about developing conditions that may not appear on a calendar.
Once the routine schedule is documented, connected monitoring can fill the remaining information gap without requiring the business to replace a simple, functioning maintenance process.
Key Decisions Before Standardising Fleet Monitoring
- Choose technology based on the actual diagnostic information available across the fleet, not simply the number of features shown in a demonstration.
- Calculate the complete ownership cost, including subscriptions, hardware, administration and data access after cancellation.
- Test the solution on a limited number of vehicles and confirm that drivers, managers and mechanics can use the resulting information effectively.
OEM Monitoring or Aftermarket Telematics: Which Works Better for 5 Vehicles? (Fleet-Wide Cost and Rollout Perspective)
For a five-vehicle fleet, the best monitoring investment is the solution that delivers useful information at an acceptable total cost over the period the vehicles will remain in service. Comparing the purchase price of an OBD dongle with an OEM subscription is not enough. Hardware, recurring charges, installation, administration, data portability and driver acceptance all affect the real cost.
A practical comparison starts with the expected ownership period. Rather than selecting the cheapest device, calculate the total expenditure across the period during which the business expects to use it.
For each option, include:
- Initial hardware and installation expenditure.
- Recurring subscription fees for every connected vehicle.
- Any additional charges for diagnostic features, data storage or integrations.
- Potential replacement equipment and maintenance costs.
- Time spent switching between manufacturer applications or managing separate accounts.
- Administrative time required to review reports and coordinate maintenance.
- Costs or restrictions associated with exporting historical data or ending the contract.
The comparison should also account for services already included with some vehicles. If certain vehicles have factory-connected services still covered by an introductory or trial period, immediately purchasing another system may create unnecessary overlapping expenditure. Check what those existing services actually provide, when the included period ends and whether the information can be accessed in a useful fleet-wide format.
A mixed fleet requires particular care. A common aftermarket dashboard may simplify administration, but some vehicles may provide more useful diagnostic information through their original manufacturer systems. A business should compare the actual data available for each vehicle rather than assume every device delivers identical coverage.
Driver acceptance also influences whether monitoring delivers reliable information. An aftermarket plug-in device is visible and may be unplugged or dislodged. If the business does not explain why it is installed, drivers may regard it as a means of monitoring their movements rather than maintaining vehicle condition.
Introduce the system around practical outcomes: identifying maintenance problems earlier, reducing roadside interruptions and improving vehicle reliability. Explain exactly what information is collected, who can access it and whether location tracking is enabled. Avoid collecting driver-related information that is unnecessary for the stated operational purpose.
Before rolling out equipment across all five vehicles, run a pilot on one or two representative vehicles for a month. The pilot should establish whether:
- The system provides the expected diagnostic information for those vehicle models.
- Alerts are relevant and can be interpreted without specialist knowledge.
- The application is straightforward for the person responsible for maintenance.
- An independent mechanic can access and use the necessary diagnostic information.
- Historical records can be exported and retained under acceptable terms.
Document the results rather than relying on a general impression. A pilot that reveals limited compatibility or excessive notification noise can prevent a larger investment in unsuitable equipment.
Once the pilot confirms diagnostic usefulness, acceptable costs and workable data arrangements, standardising the fleet becomes a more informed decision. The objective is a manageable maintenance system, not the largest possible collection of vehicle data.
How Maintenance Tracking Prevents the “I Forgot” Repair That Costs £900
A maintenance reminder can prevent an expensive repair when the underlying problem is a missed service rather than an unpredictable mechanical failure. The £900 figure is best treated as an illustrative scenario, not a verified average repair cost. The actual financial impact depends on the vehicle, the component, the damage and the cost of the resulting repair.
Forgetting maintenance rarely means that someone deliberately ignores a vehicle. More often, there is no reliable external system recording when a service is due, who should book it or whether the work was completed. The vehicle continues operating until the missed maintenance becomes visible through a warning, a garage inspection or a roadside incident.
Consider a hypothetical example involving a vehicle with a manufacturer-specified timing-belt replacement requirement. The owner records the interval incorrectly or fails to schedule the replacement. If the belt subsequently fails, the resulting engine damage may be substantially more expensive than the planned maintenance. The precise outcome depends on the engine design and the circumstances of the failure.
Illustrative maintenance scenario: The cost of forgetting a scheduled repair
Imagine a small business operating a van that requires a scheduled component replacement. The maintenance date is not recorded, and nobody receives a reminder. The van continues working until the component fails and the vehicle requires an unexpected repair.
For planning purposes, £900 can be used as a hypothetical repair scenario. It is not an independently verified estimate, an average cost or a claim about a specific vehicle. The owner should replace this example with an actual garage quotation and include any additional costs associated with downtime and recovery.
The financial consequences extend beyond the repair invoice. An unavailable vehicle can disrupt deliveries, require another vehicle to be substituted or force changes to customer appointments. Depending on the circumstances, recovery and towing may also increase the total expenditure.
For a business whose vehicles carry goods or passengers, reliability can affect customer confidence as well. A missed maintenance appointment may therefore create operational consequences that are not immediately visible on the garage invoice.
There are two distinct prevention layers:
- Calendar-based maintenance tracking: Prevents predictable omissions by recording manufacturer service intervals, current mileage, upcoming maintenance and booking responsibilities.
- Real-time vehicle monitoring: Helps identify developing diagnostic problems or abnormal operating trends that may appear between scheduled maintenance appointments.
Neither system replaces physical inspection or professional diagnosis. A monitoring platform cannot guarantee that a component will not fail, and a maintenance calendar cannot identify every unexpected fault. Their value comes from covering different sources of risk.
For each vehicle, the business can estimate its own potential exposure by comparing the cost of scheduled maintenance with the plausible cost of a missed service, the resulting repair and any additional downtime or recovery expenses. Actual quotations and vehicle-specific maintenance requirements should be used rather than assuming that £900 applies universally.
For owners and small fleet managers, the next step is straightforward: document the maintenance schedule, decide who responds to alerts and introduce connected monitoring only where it provides useful additional information. A system that helps the business act at the right time is more valuable than one that simply produces more data.
Can real-time vehicle monitoring really predict a breakdown two weeks in advance?
Sometimes monitoring can identify developing faults days or weeks before a failure becomes apparent, but two weeks is not a guaranteed prediction window. The available warning period depends on the component, fault progression, diagnostic coverage and monitoring technology. A gradual battery deterioration may offer more opportunity for investigation than a rapidly escalating overheating problem. Monitoring should be treated as an early-warning tool rather than a guaranteed breakdown countdown.
Does vehicle monitoring require GPS tracking?
No. Vehicle diagnostic monitoring can focus on technical information such as fault codes, battery voltage and available engine parameters. GPS location tracking is a separate capability that some telematics systems also offer. Fleet owners should check the provider’s data collection settings, disable unnecessary location features where possible and explain what information is collected and why.
Can an OBD-II dongle detect every mechanical problem?
No. An OBD-II device can retrieve supported diagnostic information, but its coverage varies by vehicle, manufacturer and device. Some manufacturer-specific diagnostic information may require compatible equipment. Mechanical wear, physical damage and faults that do not generate accessible diagnostic signals may not be detected. OBD monitoring therefore complements, rather than replaces, inspections and professional diagnostics.
How much time does a small fleet need to manage vehicle monitoring?
The time required depends on fleet size, alert volume and platform design. A practical starting point is a short weekly review of unresolved alerts and a more detailed monthly assessment of maintenance trends. Critical alerts need immediate attention rather than waiting for these scheduled checks. Automating reports and assigning clear responsibilities helps keep the process manageable.
Should a small business choose OEM monitoring or aftermarket telematics?
OEM monitoring is worth evaluating when a fleet mainly uses one manufacturer and needs integrated diagnostic information. Aftermarket telematics may be more convenient for mixed-brand fleets that need a common dashboard. Before choosing, compare vehicle compatibility, diagnostic coverage, total subscription costs, data exports, retention policies and the ability to share information with an independent mechanic. A pilot involving one or two vehicles can help establish whether the system meets the business’s actual requirements.