Condition-Based Maintenance 

Purpose

In the case of condition-based maintenance, maintenance activities are always performed when the measuring point of a technical object has reached a particular state, for example, every time a brake pad has been worn away to the minimum thickness permitted.

Prerequisites

In the following example process, you use the PM-PCS Interface and the customer exit IMRC0001. The PM-PCS Interface is an interface between the R/3 System and external systems such as a Process Control System (PCS).

Process Flow

The following example describes a process scenario.

You use a building control system to monitor a building’s air conditioning system. You use a SCADA system (Supervisory Control And Data Acquisition system) that recognizes events that you have predefined. You define one of the events so that the drop in pressure at an air filter may not be greater than 50 mbar. The air filters are changed once a year, but when there is such a great loss in pressure, a note can be used to indicate that the air filter is dirty and must be exchanged earlier.

  1. Each time 50 mbar is exceeded, the SCADA system transfers this in the form of a measurement reading (for example, 52 mbar) via the PM-PCS interface to the R/3 System.
  2. The R/3 System generates a measurement document and a malfunction report for the measurement reading of 52 mbar.
  3. The R/3 System recognizes 53 mbar as a measurement that exceeds the threshold value of 50 mbar, or as the valuation code "Measurement reading not OK".
  4. In addition to the malfunction report, the R/3 System can trigger other events, for example, a customer-specific workflow, using customer exit IMRC0001.

For more information on the maintenance planning functions in the R/3 System (for example, creating a maintenance plan, performing scheduling) see Maintenance Planning.