0

Condition-based Maintenance
Business Process Processing

SAP AG

(C) SAP AG

LO810

6-1

0.2

Business Process
e Cod

Wo rks ho p

R/3

Generates PM notifications

When a motor breaks down, a defect code is automatically transmitted. This triggers a notification.
SAP AG

If the lift at your company breaks down, the repair is automatically triggered by the transmission of the current condition data. If, for example, a motor in the lift breaks down, a specific malfunction code is transmitted which triggers a corresponding notification in the PM component of the R/3 System.

(C) SAP AG

LO810

6-2

0.3

Unit Objectives:
At the conclusion of this unit, you will be able to:
Describe the concept of condition-based

maintenance
Describe the functions of the SCADA

interface

SAP AG

(C) SAP AG

LO810

6-3

0.4

Functions
Pressure drop
de Co de Co
ter Fil

Notification
Measurement document

Process data

Event

SCADA

R/3

Confirmation Distributed control system Interface R/3 - PM

R

SAP AG

The objective of condition-based maintenance is an online transmission of condition data (measurement documents), which, under certain conditions, automatically results in work (notification) being arranged by the R/3 System. The advantages of online transmission (in contrast to the batch input procedure) are: Synchronous transmission and updating of condition data Generation of a measurement document Confirmation of the transaction to the notifying system Transmission of customer-specific data is possible Automatic generation of notifications

(C) SAP AG

LO810

6-4

0.5

Communication Profile

R/3
Partner system (PCS, SCADA) R/3 PM Business application

OCX or C library (generated by R/3)

R/3 RFC function module

R

SAP AG

Communication between R/3 and the partner system is made on the basis of RFC modules (RFC = Remote Function Call). The R/3 System provides a series of RFC modules which form a defined interface for the transmission and editing of process data. Within the R/3 System, a client RFC module (C library) is generated. This module can then be implemented in the partner system and forms the interface to the R/3 System. The modules can be configured in such a way that when a tolerance value is exceeded, an event is triggered which generates a notification in the PM component of the R/3 System. At a later date, after the notification has been created, the current system condition can be displayed by the person responsible (customer exit). All the necessary modules are contained in the standard R/3 System. The documentation for this interface is part of the R/3 online documentation (from 4.0 - under PMTechnical Objects-PM-PCS-Interface).

(C) SAP AG

LO810

6-5

0.6

Notification with Code

Example:
Damage catalog

Notification 10 000 579

Mechanical damage Code 010 020 030 Corrosion Broken glass Motor defect

SAP AG

With the appropriate configuration, the process data can be transmitted together with condition codes. If the condition codes of the external system have been matched with the codes in the PM component of the R/3 System, the transmitted condition code can be copied directly into the notification and record the appropriate damage.

(C) SAP AG

LO810

6-6

0.7

Summary (1)
Condition-based maintenance comprises the

online coupling of distributed control systems with R/3 PM using the SCADA interface.
When tolerance values are exceeded, process

condition data for processes triggers an event which can trigger a notification in R/3 PM.
Damage codes can be copied directly into the

notification.

SAP AG

(C) SAP AG

LO810

6-7