Once you've set up your preventive maintenance planning and the plan is up and running for your assets, the Railfleet system will start to compute the due dates for your preventive maintenance operations based on the telematics data or the manual counters available on Railfleet, and the dates you entered when closing the initialisation events.

The scheduler always starts planning based on the execution date and the counter value of the last operation of the same type or a parent operation.

Here is a visual representation of how due dates for preventive events are computed:

Based on the available data Railfleet calculates the most precise average usage of an asset and adjusts the due date estimations accordingly.

The data we use can be

• Recent telematic data: in this case the average usage is calculated based on the measured usage of the previous 30 days.
• Manual counter readings: in this case the average usage is calculated based on the difference between the last 2 counter readings.

The average usage is capped by the minimum daily average value that you were able to enter when setting up the counter type

This prevents the average from dropping too low, or even to “0”, which would result in preventive maintenance operations being planned in an infinite future.

## Average usage calculations: an example

Here are a few possible scenario’s for a GPS km counter based preventive operation, due at 10 000 km:

### 1. Recent GPS data is available and the asset runs.

• We calculate the average usage based on the measured GPS kms of the last 30 days. Let’s suppose the average value is 250 km per day.
• The last known counter value is taken as a starting point. For example: 5000 km, 1 minute ago.
• The next preventive operation will be due in (10 000 km - 5000 km) / 250 = 20 days.

### 2. GPS data is available, but the asset does NOT run.

• We calculate the average usage based on the measured GPS kms of the last 30 days. In this scenario the average usage can be quite low, because the asset is not running: for example 2 km per day.
• The average is capped by the minimum daily average value of the counter type, for example 100 km per day.
• The last known counter value is taken as a starting point. For example: 5000 km, 1 minute ago.
• The next preventive operation will be due in (10 000 km - 5000 km) / 100 = 50 days.

### 3. No telematics GPS data is available (e.g. if the asset is not equipped with a telematic device or the telematic device is not working properly):

• We calculate the average usage based on the manual counter values of the last 30 days, for example 75 km per day.
• The average is capped by the minimum daily average value of the counter type, for example 100 km per day.
• The last known counter value is taken as a starting point. For example 5000 km, 5 days ago.
• The next preventive operation will be due in ((10 000 km - 5000 km) / 100) - 5 days = 50 - 5 days = 45 days.
Did this answer your question?