After creating your counter types, counters and operation groups, you can start setting up your maintenance plan. Go to the “Preventive maintenance settings” section on the admin home page and click on “Maintenance plans”.

On the next page, you will find a complete overview of all of the maintenance plans that have been created by your company.

If the desired maintenance plan doesn't exist yet, you can create a new one by clicking on the green “add maintenance plan” button at the top of the page.

Give your new maintenance plan a name, and add the relevant operation groups by selecting them in the left column and moving them to the right with the right-pointing arrow.

You can select several operation groups at once by holding "Control" (or "Command" on a Mac).

Click on the "Save" button once you are done.

It is now time to assign the maintenance plan to your assets.

To assign the maintenance plan individually for each asset, simply go to the assets menu, look for the asset you'd like to update and click on its ID to open the asset page.

If you have it, add your asset's built date. The built date is used as the initialisation date for preventive maintenance events.

Select your maintenance plan from the dropdown menu, then save.

Note: If your asset already has a maintenance plan and you're assigning a new one, this can impact preventive maintenance scheduling.

You can also assign the same maintenance plan to several assets at once directly on the maintenance plan page.

Go to "Preventive maintenance settings", click on "Maintenance plans", and then on the plan you'd like to assign to several assets.

Below the operation groups, you'll find a list of assets without a maintenance plan assigned.

Choose the relevant assets by selecting them in the left column and moving them to the right with the right-pointing arrow.

You can select several assets at once by holding "Control" (or "Command" on a Mac).

Click on the "Save" button once you are done.

Note: If an asset already has a maintenance plan, you won't be able to assign a new one from this page. This can only be done on the asset page itself.

Once it's done, you're almost set. You will have to wait until the next morning to allow the scheduler to run the update on all events automatically.

When you first assign a maintenance plan to an asset, the scheduler creates an initial event for each maintenance operation. This event appears on the Operational dashboard and the Maintenance planning page.

To get started with your preventive maintenance plan for a specific asset, you’ll need to close each initial event either on the Operational dashboard or on the Maintenance planning page and enter the date (and counter if applicable) of the last time this type of operation has been performed on the asset in question. The initial event is based on the build date of the asset, and this date is used as the initialisation date for all preventive maintenance.

You can add the build date on the asset page:

Once an operation group's latest and biggest init event has been closed, please click on each init event for child operations of that same operation group, and select "Discard" to remove them completely. Please wait for the automatic scheduler to run overnight and update your maintenance plan.

Remember that every time you add a new operation group to your maintenance plan, you'll need to initialise this operation group so that the system can start calculating the next due maintenance correctly.

Based on that information and the available (manual or telematics) asset data, the system will calculate your maintenance planning more accurately.

Once you've set up your preventive maintenance planning and the plan is up and running for your assets, the Railnova system will automatically start to compute the due dates for your preventive maintenance operations based on the telematics data or the manual counters available on the Railnova platform, 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.

Please note that the system automatically recalculates the due date and due usage of the next preventive event once the previous event is closed. However, if that next event is already planned in an intervention, its due date and due usage are not recalculated.

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

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

The data we use can be

The minimum daily average value caps the average usage that you were able to enter when setting up the counter type.

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

Please note that if two operations from the same group are planned to take place within 10 days of each other, the system will automatically combine them and move the biggest operation to the nearest date.

For instance, if an IS4 should take place on 10 January and an IS1 should take place on 2 January, the IS4 date will be moved to 2 January and the IS1 will disappear from the schedule.

Here are a few possible scenarios for a GPS km counter-based preventive operation, due at 10 000 km:

A. Recent GPS data is available, and the asset runs.

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

C. 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):

Do you still have questions? Go to the Railnova platform and click "Contact us" for help!