Forecasting Setup: Tank Profiles & Static Usage Profiles
Learn how to configure tank profiles for the forecasting engine.
Written by Jess Hamilton
Updated at August 15th, 2025
Table of Contents
Tank Setup Profiles
The Tank Setup Profiles section of the Forecasting Configuration page determines the type of forecasting and related parameters that can be applied. This configuration step is crucial to setting up the forecasting engine to provide the right recommendations for your workflow.
Both forecasting type options include the option to enable forecasting reconciliation. When enabled, the system triggers an exception if a manual change to a load creates a Retain or Runout condition, and triggers an alert when inventory or usage exceed an assigned threshold (tank level assignment).
Tip:
Inventory Threshold Based Forecasting: Orders are generated based on the level of product in the tank.
Rate of Consumption Based Forecasting: Orders are generated based on product consumption rate.
Inventory Threshold Based Forecasting
When this option is selected, orders are generated based on the level of product in the tank. Must/Should/Could Go priority levels are determined by the assigned thresholds.
Tip:
- Must Go: Runout will occur if delivery is not made in the CURRENT shift
- Should Go: Runout will occur if delivery is not made in the NEXT shift
- Could Go: Compartment/FTL can fit without a retain
Rate of Consumption Based Forecasting
When this option is selected, orders are generated based on product consumption rate. In this case, Must/Should/Could Go priority levels are determined by the parameters set below and the Shift Proxy.
Setting Definitions:
- Retain Level: The inventory level in the tank at which a delivery can be made without causing a Retain.
-
Safety Stock Level: The inventory level in the tank that will trigger load/delivery creation.
- For sites with a higher consumption rate (ex: turnpike sites) we recommend a higher safety stock level.
- For sites with lower consumption (ex: retail, premium product) we recommend a lower safety stock level to prevent early fuel delivery.
-
Run-Out Level: The inventory level in the tank below which the tank is assumed to be unusable; the tank should NOT go under this level.
- We recommend keeping the runout level above the Physical Pump-stop level.
- ETA: The forecasting engine's estimated time when the tank inventory will hit the Safety Stock Level based on historic usage/consumption data.
-
Run Out Time: The forecasting engine's estimated time when the tank inventory will hit the Run-Out Level based on historic usage/consumption data.
- Deliveries made after this time may result in the tank running out of fuel.
- Supplier Time: The estimated time it takes a driver to lift fuel (i.e. access their truck, drive to terminal and lift fuel).
- Lead Time: The estimated time it takes a driver to transport the fuel from the Terminal to the Destination.
- Retain Time: The estimated time when the forecasted load will fit in the tank. A delivery made to the tank before this time may cause a retain on the trailer.
-
Start Buffer: The time cushion added before the ETA time to calculate the delivery window start time.
- Start Buffer should be set as per the distance of the site(s) or tank(s) from the supply terminal(s).
- Start of Delivery Period = ETA – Start Buffer
-
End Buffer: The time cushion added after the ETA time to calculate the delivery window end time.
- End Buffer should be set as per the distance of the site(s) or tank(s) from the supply terminal(s).
- End of Delivery Period = ETA – End Buffer
Additionally, when using Rate of Consumption Based forecasting, you can choose to use dynamic or static usage data.
Static Usage Profiles
When Static Usage Data is selected for a consumption-based tank profile, the forecasting engine relies on estimated tank usage. This is recommended when historical consumption data is not available (i.e. during the first 28 days of implementation as the system learns the actual sales patterns).
When enabled, Static Usage Profiles must be set up manually and applied to the tanks whose usage patterns they represent.
Tip: Consider creating Static Usage Profiles by Product or Consumption Patterns. Once created, you'll use the Mass Tank Updater section to apply them in bulk.
When creating a Static Usage Profile, designate the period of each band, when timing starts, and which days of the week have expected usage.
Tip: The forecasting engine relies on average consumption values. Setting a band period of 4 hours, for example, means that the forecasting engine will take average consumption values every 4 hours.
An Estimated Daily Usage total is required for each day. Underneath this, an estimation of what percent of the daily fuel usage is consumed within each band period is required.
As this data entry can be repetitive, please take note of the copy tool at the bottom of each day's column. Clicking this icon will duplicate all values from the column into the next day's column.
