Reporting of Maintenance Data 

Use

You can use this function to report measurement and counter readings taken in feeder systems (such as process control systems) to the Plant Maintenance (PM) application component using the PI-PCS Interface. If unexpected events such as malfunctions occur, you can also send a malfunction report to plant maintenance. This enables you to quickly respond to exceptional situations. You do so by creating a process message.

This function enables you to perform planned and condition-based maintenance of technical objects during production.

You can use planned monitoring and maintenance of objects to react to legal or environmental requirements, or manufacturer recommendations by documenting measurement data in measurement documents.

For more information, see Measurement Document.

Condition-based maintenance enables you to use malfunction reports to identify and rectify unplanned conditions such as malfunctions or damages in time.

You want to report the operating hours of your production line to plant maintenance. In plant maintenance, maintenance plan scheduling was used to specify the time interval at which the production line must be maintained (for example, every 2000 operating hours). You can use a message of category PI_PMMD to report the operating hours to plant maintenance.

If the line does not function properly, you can send a malfunction report in addition to the measurement data. The malfunction report requires the maintenance department to solve the problem.

For more information, see Malfunction Report.

Generally, the PM-PCS interface must be used to transfer this maintenance data to plant maintenance. This function enables companies that use PP-PI and a process control system that has been certified for the PI-PCS interface to use only one interface to transfer both their production data and maintenance data to the R/3 System.

Integration

You can transfer measurement and counter readings to the R/3 System as follows:

Customizing of the SAP reference client contains several sample process instruction categories for the confirmation of maintenance data. For general information on process instructions, see Process Instructions.

Prerequisites

To perform the planned and condition-based maintenance of technical objects, you must have defined a maintenance plan in plant maintenance. The maintenance plan defines the dates and the scope of the maintenance tasks.

See also:

PM - Maintenance Planning

Features

You use message category PI_PMMD and message destination PI16 to confirm maintenance data. Process instruction category PM_MDOC is available in the standard system.

The following sections describe what you must bear in mind when you create the process messages.

Required Message Data

For the R/3 System to be able to process the message, you must include the following data in the message:

For the system to be able to create a measurement document, you must either specify the measuring point / counter at which the measurement reading is taken or a secondary index for the measuring point. The secondary index is the measurement position maintained for the measuring point. The measurement position is used to identify the measuring point. Measurement positions are descriptive names that describe the position of a measuring point at an object or in the production line.

For measuring points that are defined as counters, you must specify the counter reading.

For measuring points that are not defined as counters, you must either enter the measurement reading to be reported or the valuation code. In Customizing, you can determine whether the measurement document must include either a measurement reading or a valuation code or both.

The system only accepts the following values:

Additional Message Data

You can include the following additional data in the message:

The system either calculates the counter reading difference or the current counter reading. By setting the X indicator, you specify that the counter reading reported is to be interpreted as the difference between the present and the last counter reading. If you do not set the indicator, the system interprets the value entered as the absolute counter reading.

Process control systems usually represent counters that take counter readings (for example, machine hours). If the last counter reading was 1000 hours and 200 hours were now reported in the process message with the Counter difference indicator being set, the total counter reading is now 1200 hours.

If you want to report the current counter reading, report 1200 hours in the process message and do not set the Counter difference indicator.

In both cases, the system automatically calculates the difference of 200 hours and shows it in the measuring point.

If you want to send a malfunction report in addition to the measurement or counter reading, you must enter the corresponding notification type. The system does not create a malfunction report unless you explicitly specify a notification type. If you do not specify a notification type, the system only creates a measurement document in plant maintenance. Apart from the malfunction report, you can also use several other notification types.

For more information, see PM - Maintenance Notifications.

In Customizing, you define the time in which the problem must be solved after notification recording for each priority. The system then calculates the start and end dates for the maintenance task. You can define further priorities in Customizing in addition to the priority values contained in the standard system.

Here, you enter the unit of the recorded value or counter reading. If you do not specify a unit, the system uses the unit stored for the measuring point or counter in the R/3 System.

If you use a different unit, the system automatically converts it. The system can only do this if:

Here, you enter the source where the measurement reading comes from.

You can enter any short text for the message. If you have not defined valuation codes in Customizing, you can also use the short text to enter a description of the malfunction.

Here, you can enter further customer-specific data.

Consistency Checks

When processing the messages, the system checks whether the values they contain are valid and consistent with one another. If an inconsistency (for example, an invalid measuring point) is discovered:

Measurement Document Number

The system assigns a unique measurement document number to each notification as well as a malfunction report number if required. These numbers are written to the message log.