I did talk with our ACE team and they explained why we are seeing this.
To answer your question: both the Fuel and EV Energy Usage report and ACE draw from the same underlying fuel data source, so your methodology is sound. The discrepancy you are seeing is due to a timing difference in how the data is aggregated, not an error in either tool.
Here is how the data flows:
- Fuel and EV Energy Usage report — reflects near real-time data directly from the source. When you run this report, you are seeing the most current fuel readings available.
- ACE (using the VehicleKPI aggregation) — the fuel data in ACE goes through a daily aggregation pipeline before it is available. This means ACE can lag behind the Fuel and EV Energy Usage report by up to one day. The two numbers should converge once the aggregation catches up.
What this means for your zone-based fuel analysis:
- If you are comparing figures between the two tools on the same day or shortly after the period ends, you may see a temporary difference — this is expected.
- For historical periods (e.g. last week or last month), the numbers from both tools should align once aggregation has completed.
- For the most up-to-date fuel totals, the Fuel and EV Energy Usage report is the more real-time source.
Your approach of validating methodology before adding zone parameters is exactly the right thing to do. Once you confirm the figures align for a settled period, you can be confident in your zone-level analysis.
Please let us know if you have any other questions. We are here to help.
Have a great day!
Eishi FUN