Maintenance Strategy

A maintenance strategy defines the rules for the sequence of planned maintenance work. It contains general scheduling information, and can therefore be assigned to as many maintenance task lists (PM task lists) and maintenance plans as required. A maintenance strategy contains maintenance packages in which the following information is defined:

• The cycle in which the individual work should be performed (for example, every two months, every 3,106.86 miles, every 500 operating hours)
• Other data which affects scheduling

From Release 4.0A, maintenance strategies are optional. If you want to perform simple preventive maintenance in your company, for which one maintenance cycle is sufficient, then you can work with single cycle plans . In contrast, you use strategy plans to show complex maintenance cycles.

You create some maintenance plans with a maintenance strategy. The following table shows which maintenance plan types require a maintenance strategy.

Maintenance Plan Type	Maintenance Strategy
Single cycle plan, time-based	No
Single cycle plan, performance-based	No
Strategy plan, time-based	Yes
Strategy plan, performance-based	Yes
Multiple counter plan	No

If you want to use time-based or performance-based strategy plans in your company, you must first define

• Where regular maintenance is required (shown in the system as a maintenance item )
• The frequency of these maintenance tasks in terms of performance or time (shown in the system as maintenance packages )

For this, you must compare the legal requirements, manufacturer recommendations and costs of preventive maintenance with the cost of a breakdown. You should also consider how you can set up the tasks in a maintenance plan, so that scheduling and maintenance activities are combined most effectively.

Once you have determined the optimum cycles for preventive maintenance, you can define a suitable maintenance strategy. Using the PM application component, you can create strategies which represent the scheduling rules for all the preventive maintenance tasks required within your company. As these strategies contain general scheduling information, they can be assigned to as many different maintenance plans as required.

By using maintenance strategies containing general scheduling information, you can:

• Reduce maintenance plan creation time

You do not need to create the same scheduling information for each maintenance plan.

• Update scheduling information easily

Maintenance packages are referenced. In other words, when you make changes in the maintenance strategy (for example, delete packages, change the preliminary or follow-up buffer), the changes are also valid for the assigned maintenance plans. However, the scheduling parameters are copied into the respective maintenance plan. For more information about the effects of the changes, see Scheduling Parameters ).

Structure

A maintenance strategy consists of:

• Strategy header
• Scheduling parameters
• Scheduling indicators
• Maintenance packages

The individual components of a maintenance strategy are explained in detail below:

Strategy Header

• Name of the strategy
• Short text

Scheduling Parameters

The scheduling parameters (for example, call horizon, shift factor) contain the scheduling data for the respective maintenance strategy, with which you can influence the scheduling of maintenance plans. When you create a strategy plan, the system copies this data to the plan where you can change it.

Scheduling Indicators

Within a maintenance strategy, you can use different scheduling indicators to specify the type of scheduling you require or to define a cycle set:

• Time-based (for example, every 30 days)
• Time-based by key date (for example, every 30 days on the 30th day of the month)
• Time-based by factory calendar (for example, every 30 working days)
• Performance-based (for example, every 50 operating hours)

Maintenance Packages

Maintenance activities that must be performed at a particular date or point in time are combined into maintenance packages. These contain, for example, the cycle duration and unit of measurement. For more information, see Maintenance Packages . Example: