Skip to main content
All CollectionsRelease notesRailnova platform release notes
Simplified preventive scheduling configuration - September 2024
Simplified preventive scheduling configuration - September 2024
Updated over a week ago

In June 2022, we introduced the new component management module on the Railnova platform. While this enhanced functionality, it also added complexity to the configuration of maintenance plans for customers using our preventive maintenance scheduler.

Today, we are pleased to announce that we have simplified the process for all customers who do not use the component management module.

Our platform supports two types of preventive maintenance scheduling:

  1. Component-level preventive maintenance scheduling: Each component tracks its preventive operations, maintenance counters, and maintenance history independently. This information remains linked to the component, even if it is removed from one asset or installed on another. This approach offers a more advanced and accurate method for managing preventive maintenance.

  2. Asset-level preventive maintenance scheduling: In this model, preventive operations, maintenance counters, and history are linked directly to an asset.

Customers using component-level preventive maintenance scheduling will not see any changes. However, we have simplified the configuration and management of maintenance plans for those who don't.

Key changes

  • Maintenance counters can now be defined at the asset level (not just at the component level).

  • There is no longer a need to create "dummy" asset components. We have reintroduced the option to attach maintenance plans directly to an asset.

All configurations not using our component module have been automatically migrated to this new method.

For more details on configuring asset-level maintenance plans, please refer to the following help article.

We believe these changes will restore simplicity for many of our customers using preventive maintenance scheduling. We also expect these improvements to reduce errors previously caused by manual processes.

Did this answer your question?