Use Catalog Profiles, Failure Codes to Analyze Assets
EP Editorial Staff | January 13, 2017
By Kristina Gordon, DuPont
Determining why an asset failed during production is a critical function, not only for general reporting, but to measure asset costs and make informed decisions about future use. The SAP system provides an effective means of documenting the key aspects of damages, causes, tasks, and activities. Catalog profiles are used to group attributes together and allow maintenance personnel to document asset failure in the maintenance notification.
Q: What defect codes exist in the SAP catalog profile and how do you turn them on?
A : Catalog profiles are created based on a company’s general business practices. Each company will have its own standards and naming convention and they should be followed in this setup to maintain consistency and avoid confusion.
The SAP catalog structure goes from catalog to code group to code. Each of these must be set up in the IMG (implementation guide), which is a SAP configuration. A catalog profile should be created such that it describes the equipment at a level that helps identify the possible failures associated with its particular equipment group.
Once the catalog and failure codes are configured, they are assigned to equipment masters. This will connect a catalog profile and corresponding damage or failure code to a specific equipment type, and then allow the proper failure code to be selected and added to the notification for that asset, as seen in the example below.
As shown in the equipment-master screen (next column), the equipment description is R/V, with some identifying characteristics (identification number 531503, in this case). The catalog profile (bottom of the screen) states the profile number with the description “Valve, Safety Relief.”
In the work-order notification generated for the equipment above, the object part goes into a more granular description of the catalog profile, “Disk”.
Finally, the failure code for the damage can be selected. In this example, the inspection produced a “Worn” result.
SAP includes the following key transactions for viewing failure-analysis results:
• MCI5: Damages, based on damage, cause, and activity
• IW67: List of tasks completed for the damages
• IW69: List of items with damage, cause, and other catalog details
• IW65: List of activities with damage, cause, and other catalog details.
Knowing the failure rate can optimize PM intervals and improve failure response and work practices. MT
Kristina Gordon is SAP Program Consultant at the DuPont, Sabine River Works plant in West Orange, TX. If you have SAP questions, send them to email@example.com and we’ll forward them to Kristina.