How to create and configure preventive maintenance?

When you select a workshop, a responsible person is automatically suggested.

• Only the assets to which the user has access are available;
• 
If a route is selected, the user must have access to all its components;
• Only routes that contain at least one asset are available;
• If the asset has a supplier and/or customer assigned to it, those values are automatically inherited (and can be changed).

On the Work Orders tab, you can combine multiple maintenance plans into a single work order when their respective events occur on the same date.

When the Join Plans option is enabled, work orders are created according to the following rules:

• The work order created includes all maintenance plans with scheduled events for the same day;
• The creation of the work order follows the order of events, and it is only possible if there are no previous events to be processed;
• This validation applies:
  • To events in the same plan, when there are no substitutions;
  • To any previous event in the main plan or in the substitute plans, when there are substitutions;
• The same work order is associated with all preventive maintenance events scheduled for that day
• If, for the same day, there are events where only some meet the creation criteria, the work order is created only for those events.

Preventive maintenance has two plans:

• Daily plan;
• Weekly plan;

The following are scheduled for October 2:

• Event 3 of the daily plan;
• Event 4 of the weekly plan;

Scenario:

• Event 1 in the daily plan already has an associated work order;
• Event 2 in the weekly plan does not yet have an associated work order (it is behind schedule).

In this case, when creating the work order for October 2:

• Only the daily plan (event 3) is included in the work order;
• The weekly plan is not included because there is a previous event (Event 2) that has not yet been processed.

On the Scheduling tab, you can set the scheduling criteria that determine the date of the next event. There are three selection criteria:

• Fixed Date: this criterion is not affected by the dates of previous work orders; in other words, events always occur on the same date;
• Opening Date: this criterion is based on the creation date of the previous work order. This criterion must consider the first transition to a status that allows for work or cost recording. If the initial status allows for such entries, the work order date must be considered;
• Closing Date: this criterion is based on the closing date of the previous work order; in other words, the closing date is determined by the status of the work order that is configured as the end of the SLA.

It is also possible to:

• Set the time zone in which preventive maintenance events should occur;
  • In the event preview, dates and times are displayed according to the time zone;
  • After approval, events are recalculated based on the defined time zone;
• Associate a Reference Calendar, from the following options:
  • None;
  • Company Default;
  • Other: when you select this option, the Calendar field becomes available, allowing you to choose a specific calendar to associate with preventive maintenance;
• Set a Reference Time from the following options:
  • None;
  • Company Default;
  • Other: when you select this option, the Time Schedule field becomes available, allowing you to choose a specific time to associate with the preventive maintenance task;

On the Planned Work tab, you can define the maintenance plans associated with preventive maintenance that will generate events and work orders, as well as their respective execution rules.

This tab allows you to configure how preventive maintenance is planned, including the recurrence, replacement criteria, and parameters associated with event generation.

1. Recurrence

Each maintenance plan can be configured based on the following planning types:

• Recurrence: recurring scheduling supports three types of settings: daily, weekly, and monthly.
  • Daily frequency: sets the time at which preventive maintenance should take place;
  • Frequency: allows you to specify how often (every few days, weeks, or months) preventive maintenance takes place;
  • Weekly: allows you to specify one or more days of the week on which maintenance should take place;
  • Monthly: allows you to specify a day of the month or a day rule for performing preventive maintenance. During recalculation, 30 days are always included;
  • Recurrence interval: defines the start and end dates of the recurrence.
• Meter:
  • Meter-based planning allows you to schedule preventive maintenance based on the readings of meters associated with equipment, tools, or locations.
  • The meter may be directly linked to the preventive maintenance item or indirectly through the family, brand, model, or function of the location.
  • To define the plan, you must specify:
    • The meter to be used;
    • The meter value range at the end of which maintenance must take place.
  • Events can be generated based on:
    • The average and the scheduled date;
    • The counter value alone;
  • When maintenance is scheduled based solely on the counter value, the Use Average parameter must be disabled. If it is enabled, the average is used to calculate the maintenance events;
  • If the average is not used in the recalculation, events are not scheduled based on a specific date and are not displayed in the Planner; only the date of the next event is indicated;
  • Counter-based scheduling cannot be used in conjunction with time-based recurrence. Note: When preventive maintenance is created based on a counter and the associated counter already has readings, upon approving the preventive maintenance and generating the events, the cumulative reading for the first event is set to the value that is greater than the counter’s current reading. This means that events that would fall between the initial value defined in the plan and the counter’s current value are excluded.
• When events are generated based on the counter, a rule applies whereby no more than one event is generated per day, even if the defined interval is shorter than the current average of the counter.

On this tab, when you associate a maintenance plan, you can also define tolerances related to the execution of events.

• Advance Tolerance: If the difference between the event date and the scheduled date exceeds the defined tolerance, the event is rescheduled to the new date;
• Delay Tolerance: If the difference between the scheduled date and the event date exceeds the defined tolerance, the event is rescheduled for the new date.

3. Replacement Criteria

In preventive maintenance plans, you can also select the replacement criteria, defining the rules that determine when a new event replaces or updates previous events. The replacement criteria can be as follows:

• None;
• Main (Multiplier)
• Replacement.

The replacement criteria must comply with the following rules:

• All plans with a main replacement criterion must have at least one associated replacement plan;
• A main plan cannot be linked to another main plan;
• Each maintenance plan must be associated with a main plan;
• Replacement plans cannot have a defined recurrence;
• Replacement plans for the same main plan must have a different number of events;
• The number of events in a replacement plan must be greater than 0.

Plan replacement allows certain plans to be executed at specific times during events, replacing the main plan based on the defined number of occurrences.

For example, on a monthly plan:

• A main plan can be executed for most events;
• And, for specific events (e.g., every 3 or 12 occurrences), a replacement plan can be executed.

Note: The settings defined on this tab directly influence how events are generated and how maintenance plans are applied over time.