Using the Phase Model

Describing Benefits

Objective

After completing this lesson, you will be able to describe the benefits of the phase model

Benefits of the Phase-Based Process

The comprehensive phase-based process supports you in the maintenance of technical objects. Maintenance requests and orders are processed according to nine phases.

The phase-based maintenance process has been designed to be used within the functional scope of the Reactive Maintenance (4HH) and Proactive Maintenance (4HI) scope items that differs from how the maintenance process had been run before (based on the scope items BH1, BH2 and BJ2). This means that you can only process your maintenance orders according to phases if the scope items Reactive Maintenance and Proactive Maintenance are active or if you have configured the phase model in Customizing the same way as it is delivered for these scope items.

According to this model, all maintenance orders of the Reactive Maintenance and Proactive Maintenance order types are processed with additional planning, approval, preparation, scheduling, and execution steps that are also reflected in additional system statuses.

Processes using the Phase Model

The following processes support the phase model:

  • Reactive Maintenance: The process that involves this order type allows you to perform maintenance of technical objects whenever a breakdown or a failure occurs. This process helps you reduce an asset’s downtime and increase productivity.

  • Proactive Maintenance: The process that involves this order type allows you to prevent the failure or breakdown of an asset by implementing preventive maintenance and using proactive measures. This ensures that the assets are well utilized and are available. It encourages optimal performance of assets and reduces cost by minimizing breakdowns.

  • Improvement Maintenance (4VT): Perform and track work that leads to improvement of assets such as redesign, upgrades etc. - integrated with Project Management (Supports the phase model).

  • Operational and Overhead Maintenance (4WM‏): Record activities such as training, development, documentation, routine work, and so on (Supports the phase model).

Note

Scope Items 4VT and 4WM are only available in SAP S/4HANA Cloud, Public Edition.

Phases and Subphases

Diagram depicting phases and subphases. They are described in the following text.

Within the phase-based processes maintenance requests and maintenance orders are processed following a business logic with a clearly defined sequence of steps which includes mandatory steps.

Example:

  • Maintenance orders must always be based on an accepted maintenance request. The maintenance request must have the system status APOK (Approval: OK) - which transfers it to the Accepted (Request) subphase.

  • Maintenance orders must always be approved - either manually or automatically - using a workflow process based on teams and responsibilities.

There are different methods to adapt this business logic (see also lesson Customizing the Phase-based Process).

Learning

SAP FacebookSAP YoutubeSAP LinkedIn