Fuel measurement provenance
Record whether a value comes from CAN, a tank sensor, an estimate or a transaction feed. Avoid presenting calculated values as direct measurements.
Connected technology / Fuel & Energy Data
Make fuel and energy comparisons you can explain.
Connect supported vehicle readings, fuel transactions and energy data around a clear measurement model for mixed fleets.
Plan your integrationMAKE THE CONNECTION USEFULStart with the decision.
Start with the decision.
Design the data around it.
Tank level, fuel consumed, fuel purchased and battery energy describe different things. Combining them without a shared definition creates misleading results. Fleetly integration planning identifies each source and its measurement boundaries so operational teams can investigate cost and efficiency with appropriate confidence.
PRACTICAL USE CASES
Where this integration can add value.
Transaction reconciliation
Map permitted fuel-card or purchase records to the correct vehicle and period. Investigate unmatched transactions before treating them as vehicle consumption.
EV energy context
Keep vehicle energy use, charger-delivered energy and billed energy distinct. Compare equivalent work and include source coverage.
Efficiency investigations
Analyse fuel or energy use alongside distance, vehicle class and duty cycle. Review gaps, calibration and operational changes before attributing a trend.
Every connection has a working path.
Select a stage to see what needs to happen and why it matters.
Fuel & Energy Data / Identify
Separate the measurement sources
List vehicle, sensor, transaction and charging data with units and ownership.
Read the complete workflow
- Separate the measurement sources
List vehicle, sensor, transaction and charging data with units and ownership.
- Match the asset and period
Resolve vehicle references and timing before combining records.
- Validate quality and coverage
Flag implausible readings, missing distance and unmatched transactions for review.
- Use equivalent operating work
Calculate agreed measures within comparable vehicle and duty-cycle groups.
- Turn the finding into an action
Review context with fleet and finance teams and measure the effect of the agreed change.
DATA WITH CONTEXT
Agree the meaning before moving the data.
These are scoping considerations, not field names or a published API schema. Confirm the exact contract for your implementation.
| Data area | Why it matters | What to validate |
|---|---|---|
| Fuel level | Describes the amount or proportion in the tank. | Check sensor calibration and units. |
| Fuel used | Represents consumed fuel over a period or cumulative reading. | Validate source, resets and distance coverage. |
| Purchase record | Records a commercial fuel or energy transaction. | Match vehicle, time, quantity and cost. |
| Energy reading | Represents energy at a defined measurement boundary. | Distinguish charger delivery from vehicle consumption. |
PREPARE YOUR INTEGRATION
A useful first conversation starts here.
Mark what you have prepared and use the remaining items to shape your discussion. This checklist stays in this page session.
0 / 5Preparation items checked
Preparation only; this is not a compatibility assessment or production approval.
Opens your email app with an editable summary. Nothing is sent automatically.
COMMON QUESTIONSUnderstand the scope.
Understand the scope.
Plan with confidence.
Can a fuel-level drop prove theft?
No. Investigate measurement quality, vehicle movement, refuelling and other context before reaching a conclusion.
Can fuel purchases be reported as consumption?
Not without a justified method. Purchase timing and consumption timing differ, especially across short reporting periods.
How should diesel and EV efficiency be compared?
Use a common operational output and a transparent cost basis. Keep litres and energy units distinct rather than blending them into one raw measure.
Are all fuel-card and charging systems connected?
No universal compatibility is implied. Provide the source and interface details so the required integration can be assessed.
SUPPORTING RESOURCES
Take the next step with a clear plan.
Confirm your production scope.
Features and integration methods depend on the agreed devices, interfaces, permissions and enabled modules. Request the current technical documentation before implementation; never include passwords or access tokens in an initial enquiry.