As you review Fuel Analytics dashboards and reporting, you may notice “lagging” dates. This resource provides a non-technical explanation of how the data is gathered and displayed. 

Last ATG Reading vs. Fuel Analytics Results

The Last ATG Reading result shows the timestamp of the most recent inventory data received from the site. This is updated close to real time as ATG data arrives and is displayed in the site/facility local time zone.

The Fuel Analytics results, including Inventory Variance, Trends, flow-related outputs, and other calculated analytics, are produced by the scheduled daily processing task. These outputs are not updated every time a new ATG reading is received. They are calculated after the system has received enough data to process a complete operating day.
 

Because of this, there can be a visible gap between:

• the latest ATG data received, and
• the latest date shown in processed Fuel Analytics results.

For example, the system may already be receiving ATG data for 22 April, while the analytics results currently show processed trends up to the end of 20 April. This usually means the system has received newer raw data, but the daily processing task has not yet completed the next processing cycle for that data.

Widget Refresh Schedules

It is also worth noting that some information displayed in the dashboard widgets may follow a different refresh schedule from the main daily trend and variance results.

These widgets may not always align exactly with the dates shown in the daily analytics results. Some widget information is refreshed through hourly scheduled outputs, while the trend and variance results depend on the full daily analytics processing cycle. As a result, a widget may appear more current than the daily trend or variance results.

Summary

In practical terms: 

• Last ATG Received = latest raw site data received from the client.
• Fuel Analytics/trend date = latest completed daily analytics processing output.
• The analytics outputs are expected to lag the live ATG receipt timestamp by at least one full processing day.
• Depending on processing timing, time zones, backlog, or when the source files arrive, this can sometimes appear as a lag of up to a few days.
• Date and time displays should also be interpreted carefully because timestamps may be received, converted, processed, and displayed across different time zones.