Vehicle capability profile
Record which fuel, diagnostic, odometer, engine-hour, EV and sensor measures are available.
Use compatible vehicle signals for fuel, diagnostics, odometer, engine hours, EV energy and performance across Fleetly.
Vehicles and connected devices expose different data. Fleetly can map available CAN, OBD and OEM signals by vehicle so the platform understands which measures are supported and how confidently they can be used.
The same connected signal can support several outcomes: odometer for maintenance, fuel totals for efficiency, fault codes for vehicle health and battery information for EV management.
Each capability works with the wider Fleetly platform, keeping vehicles, drivers, events, evidence and outcomes connected.
Record which fuel, diagnostic, odometer, engine-hour, EV and sensor measures are available.
Use compatible vehicle-interface and telematics sources.
Connect supported manufacturer data services where rights and interfaces permit.
Use available totals, level, rate, hours and related signals.
Bring supported warning and fault information into vehicle health workflows.
Use available state-of-charge, range, energy and powertrain data.
This capability works inside Fleetly One Platform, sharing the same vehicles, drivers, events, workflows and reporting as the wider fleet operation.
Fleetly makes sophisticated fleet technology usable by connecting each signal to a decision, an owner and an outcome.
Confirm the vehicle, interface, device and available data.
Check signal meaning, units, quality and operational use.
Connect the measures to Fleetly’s shared vehicle model.
Activate relevant maintenance, intelligence and alert workflows.
A field name does not guarantee a reliable operational measure. Fleetly records source and capability so dashboards can distinguish directly measured, estimated and unavailable information.
Access to manufacturer or vehicle data depends on vehicle specification, device support, contractual rights and technical integration.
Explore the open Fleetly ecosystemTalk to Fleetly for a solution assessment based on your vehicles, devices, operating model and required outcomes.
CAN bus data are signals exchanged between electronic systems within a vehicle. Available access can include engine, fuel, odometer, diagnostic or powertrain information.
No. Availability depends on the vehicle, interface, device, permissions and integration.
OEM data are vehicle signals made available by the manufacturer through an approved interface or connected service.
Yes. A validated vehicle signal can support Tracking, Maintenance and Intelligence.
Fleetly can preserve source and capability context so measures are used according to their confidence and availability.
We will focus the demonstration on your vehicles, risks, workflows and existing technology.