Understanding Vehicle Replacement Forecasts

DREAM projects each vehicle's replacement date from whichever hits first — age or mileage. Here is how the math works and where to find the report.

Quick Answer

Open Reports → Vehicle Lifecycle Forecast. Vehicles are grouped by projected replacement year, with an Overdue bucket for anything already past its replacement date.

Every vehicle in DREAM has a smart projected replacement date — the earlier of two candidate dates: age-based (in-service date + lifespan) and mileage-based (projected from odometer readings).

Age basis

If a vehicle has a lifespan (e.g., 7 years) and an in-service date, DREAM calculates when the vehicle hits that age. This requires only the in-service date and lifespan — nothing else.

Mileage basis

If a vehicle has a replacement odometer (e.g., 300,000 km) and at least 2 odometer readings spanning 3 months or more, DREAM computes the average monthly usage and projects forward to when the vehicle hits the replacement odometer.

If the vehicle is already past its replacement odometer, the projection produces a date in the past — and the vehicle appears in the Overdue section of the report.

Which one wins

DREAM picks the earlier of the two candidates. The Vehicle Lifecycle Forecast report shows a Basis column indicating which one drove the date for each vehicle.

Running the report

Go to Reports → Vehicle Lifecycle Forecast, choose the number of years to project (3 / 5 / 10), and generate. The output groups vehicles by year, with an Overdue bucket at the top for vehicles already past their replacement date.

Vehicles also appear in the standard asset Lifecycle Forecast reports automatically — the smart replacement date is just the asset's `expiryDate` under the hood, so vehicles slot into the right year alongside other assets.

💡 Tip: The more odometer readings a vehicle has, the more accurate the mileage projection. Use the Odometer Entry bulk action monthly to keep readings fresh across the whole fleet.