Entering content frameObject documentation Maintenance Strategy Locate the document in its SAP Library structure

Definition

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:

Use

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

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:

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

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:

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

Strategy Header

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:

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

You can create a maintenance strategy with three packages for maintaining a pressurized tank.

This graphic is explained in the accompanying text

You can assign several packages with different cycle durations to a strategy. All packages must have the same dimensions, for example, 'time', 'weight', or 'length'. The packages or maintenance cycles within a strategy have a common basic unit of conversion. This unit corresponds to a particular dimension, for example, 'time', ‘weight’, or ‘length’.

Packages within one strategy may have different cycle units, but they all have the same dimension.

Example

A strategy contains three packages:

Here, the dimension 'time' has the cycle units 'week', 'month', 'year'.

If you work with hierarchies for packages and several packages are due on the same date, note that one year and twelve months are considered to be of different length in the SAP System.

1 year = 365 days; 12 months = 360 days (12 x 30)

Integration

For strategy plans, you can assign a maintenance task list if necessary to a maintenance item in the strategy plan which describes the maintenance tasks to be performed in its operations. The same strategy must be specified in the maintenance task list as in the strategy plan. This means that you can assign the maintenance packages of the assigned maintenance strategy to individual operations in the maintenance task list. For example, you assign the maintenance package "every 6,213.71 miles" to the operation "oil change".

Through the assignment of maintenance packages to operations, you define the frequency (in this case, every 6,213.71 miles) in which the operations should be performed. For more information, see Assignment of Task Lists to the Maintenance Item.

See also

Changing a Maintenance Strategy.

 

Leaving content frame