The Maintenance module allows you to automate preventive maintenance for your assets by generating tasks when a meter reaches predefined milestones instead of using fixed calendar dates.

For example, you can schedule maintenance every 250 operating hours, every 10,000 km (or miles), or based on any other meter associated with an asset.

A maintenance planning uses an asset's meter readings to estimate when predefined milestones will be reached and automatically generates the corresponding maintenance tasks.

The process consists of six steps:

Go to Planning Templates, then create a new template or edit an existing one.

Under Cycle Configuration, select Meter (Asset Required) instead of Time-Based.

With this type of template, selecting an asset is always required when creating a planning.

Choose the meter that will be used by the planning, for example:

The maintenance strategy defines the milestones at which tasks will be generated.

For example:

The preview lets you visualize the order and frequency of each maintenance milestone.

The execution window determines when a task will be created and how long it will remain available to be completed.

Configure:

Planning start, which can be:

Task availability duration.

If you configure:

The task will remain available for a total of 6 days:

This buffer is recommended because maintenance dates are projections and may change based on the asset's actual usage.

Each maintenance level can include one or more forms.

For example:

You can enable Carry Tasks Across Levels.

When enabled, the forms configured for one maintenance level are automatically inherited by higher levels.

For example:

If both milestones occur at the same time, PM2 can also include the PM1 inspection.

This ensures that maintenance activities from lower levels are not skipped when a higher-level maintenance takes priority.

Inherited forms can always be removed manually if needed.

Once the template has been created, create a new maintenance planning.

Select:

Only assets with a configured meter will be available.

The Location field is automatically populated using the selected asset.

The prediction engine estimates when the asset will reach each maintenance milestone.

There are two available methods.

Uses the asset's historical meter readings to calculate an average usage rate.

For example:

Based on this information, DataScope projects when the asset will reach 250 hours, 500 hours, and the remaining milestones.

You can also define how many months of historical data should be used for the calculation (Calculation Range). For example, if you choose the last six months, DataScope calculates the average usage rate using only the readings recorded during that period. If the asset doesn't have that much historical data, all available readings are used.

If there isn't enough historical data yet, you can manually enter an estimated daily usage.

For example:

Projected dates will automatically adjust as new meter readings are recorded.

Before activating the planning, you must create the task associated with each maintenance level.

Each task can be assigned to:

Once every maintenance level has an assigned task, the Create and Activate Planning button becomes available.

After activation, the planning displays information such as:

You'll also find a timeline showing all projected maintenance milestones and a table summarizing:

The maintenance milestones shown in the projection are not actual tasks. They are estimates based on the predicted usage of the asset.

This information is updated every time someone opens the Maintenance module. At that moment, DataScope recalculates the projections using the most recent meter readings. For example, if the equipment was used earlier that day, that reading will already be reflected the next time the module is opened.

Even if nobody opens the module, DataScope performs an automatic update once a day to keep the projections up to date.

When that update determines that a maintenance milestone has entered its execution window, the corresponding task is automatically created and behaves like any other task in the system:

A company manages a fleet of trucks and performs preventive maintenance every 10,000 km, with a major service every 50,000 km.

To automate this process, they create a maintenance template using the Mileage meter and define milestones at:

As each truck approaches one of these milestones, DataScope estimates when it will be reached. Once the milestone enters the configured execution window, the corresponding maintenance task is automatically created and assigned to the designated mechanic or responsible user.

The same workflow can be used for equipment with hour meters, industrial machinery with cycle counters, or any other asset that uses meters.