Detailed instructions for use are in the User's Guide.
[. . . ] SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2, version for SAP solutions - Business Guide
Version 12. 2. 0. 0
October 2009
Copyright
© Copyright 2009 SAP AG. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Trademarks
All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. [. . . ] The Rapid Mart includes all notification types for category "01". You can use the IMG (SAP solutions Implementation Guide) to configure notification types. Each notification can also have several line items that describe in greater detail the specifics of the notification. SAP solutions maintains notification catalogs that store information about damage, cause, and location (see "Malfunction Catalogs" on page 28). If data entry for these is timely and correct in SAP solutions, this information can be useful for failure analysis. However, missing information in these source tables can cause discrepancies in your analyses and reports. The notification section extracts data from the SAP solutions header and line item levels for each notification. The corresponding SAP solutions tables are:
· · ·
QMIH - Quality Notification - maintenance header QMEL - Quality Notification - general header QMFE - Quality Notification - items
The target table in the Rapid Mart schema is NOTIFICATION_FACT.
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
31
3
Subject Areas Service Notification Section
The section also extracts data from SAP solutions to indicate status, such as in-progress, postponed, completed, or deleted. The notification section does not store the history of changes to the data and it does not extract information about activities and tasks. To support plant maintenance analysis, the section allows you to classify equipment and functional locations, and their hierarchies. Though notification items can be part of the classification system, the section does not extract class allocation data for notification items. Therefore, this version of the Rapid Mart does not allow you to classify notification items. However, the NOTIFICATION_FACT table does contain a field, OBJ_ID_CLASS, that captures the assignment of a notification item to classes and characteristics. You can use this as a link to classifications at the line item level when customizing the Rapid Mart. The section also contains a second fact table MTBR_MTTR_FACT that calculates:
· ·
MTBR = Mean (or Average) Time Between Repairs (also called up time) MTTR = Mean (or Average) Time To Repair (also called down time)
The NOTIFICATION_FACT table is extracted and populated from SAP solutions first. The SAP solutions Plant Maintenance Information System (PMIS) only calculates MTBR and MTTR on a monthly basis. However, you can use data from the notification section to analyze MTBR and MTTR for any duration.
Rapid Mart processing
The section captures the following dimensional attributes and their associated dimension tables: Attribute Name Business Area Classification Hierarchy Dimension Tables BUSINESS_AREA CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA
Company Code Controlling Area
32
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
Subject Areas Service Notification Section
3
Attribute Name Cost Center & Hierarchy
Dimension Tables COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR INTERNAL_ORDER, INTERNAL_ORDER_HIER, INTERNAL_ORDER_HIER_HZ, INTERNAL_ORDER_HIER_VR, INTERNAL_ORDER_HIER_BAD MAINTENANCE_PRIORITY MALFUNCTION_CAUSE, MALFUNCTION_DAMAGE, MALFUNCTION_OBJ_PART MALFUNCTION_EFFECT MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT NOTIFICATION DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY PLANNING_GROUP PLANT PLANT_LOCATION SERVICE_PERSON TIME_DIM
Equipment & Hierarchy
Functional Location & Hierarchy
Internal Order & Hierarchy
Maintenance Priority Malfunction Catalogs
Malfunction Effect Material & Product Hierarchy Material By Plant Notification Notification Category Notification Type Planning Group Plant Plant Location Service Person Time Dimension
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
33
3
Subject Areas Service Notification Section
Attribute Name Unit Of Measure Work Center & Hierarchy
Dimension Tables UNIT_OF_MEASURE WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact Table Fields
The section contains the following measures. Note: The focus is on reporting durations, therefore most measures are in time units rather than monetary currency or quantities:
Fact Table Name MTBR_MTTR_FACT Column Name DAYS_DOWNTIME DAYS_UPTIME HOURS_DOWNTIME HOURS_UPTIME MINS_DOWNTIME MINS_UPTIME NOTIFICATION_FACT DAYS_COMPLT DAYS_DOWNTIME DAYS_REQ HOURS_COMPLT HOURS_DOWNTIME HOURS_REQ MINS_COMPLT MINS_DOWNTIME MINS_REQ QTY_DOWNTIME Description Calculated Days of downtime (as Malfunction end Malfunction start) Calculated Days of uptime: Prev Malfunction end date Malfunction start date Calculated hours of downtime (as Malfunction end Malfunction start) Calculated hours of uptime: Prev Malfunction end date Malfunction start date Calculated minutes of downtime (as Malfunction end Malfunction start) Calculated minutes of uptime: Prev Malfunction end date - Malfunction start date Number of Days to eliminate malfunction (calculated) Number of malfunction days (calculated) Number of Required days to fix malfunction (calculated) Number of Hours to eliminate malfunction (calculated) Number of malfunction Hours (calculated) Number of Required Hours to fix malfunction (calculated) Number of Hours to eliminate malfunction (calculated) Number of malfunction Minutes (calculated) Number of Required Minutes to fix malfunction (calculated) QMIH-AUSZT - Downtime
34
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
Subject Areas Service Notification Section
3
Additionally, several "flags" are employed to capture notification status on the NOTIFICATION_FACT table: Column Name BREAKDOWN_FLAG COMPLT_FLAG Description EQIH-MSAUS - Breakdown indicator. Set to 1 if there is a breakdown JEST-STAT (lookup) - NOCO notification completed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - NOPR notification is progress status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - OSNO outstanding notification status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - NOPO notification postponed status is active (1 is active, 0 is inactive) QMFE-KZLOESCH - Indicator: delete data record. Set to 1 if an item is deleted JEST-STAT (lookup) - DLFL notification completed status is active (1 is active, 0 is inactive)
IN_PROGRESS_FLAG
OUTSTANDNG_FLAG
POSTPONE_FLAG
ITEM_DELETE_FLAG NOTIFICTN_DELETE_FLAG
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
35
3
Subject Areas Service Notification Section
Rapid Mart data
The following diagrams shows the tables in the notification section organized as a Star Schema: Notification Fact (1 of 2):
36
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
Subject Areas Service Notification Section
3
MTTR / MTBR Fact (2 of 2):
With the tables in this section, you can analyze maintenance notifications along several dimensions:
· · · · · · · ·
Business Area Classification Hierarchy Company Code Controlling Area Cost Center & Hierarchy Document Category (Notification Category) Document Type (Notification Type) Equipment & Hierarchy
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
37
3
Subject Areas Service Notification Section
· · · · · · · · · · · · · · · · · · · · · · · · ·
Functional Location & Hierarchy Internal Order & Hierarchy (Service Order & Hierarchy) Maintenance Priority Malfunction Catalogs (Cause, Damage, and Object Part) Malfunction Effect Material & Product Hierarchy Material By Plant Notification Planning Group Plant Plant Location Service Person Time Dim Unit Of Measure Work Center & Hierarchy What is the maintenance history of this piece of equipment?What is the mean time to repair (MTTR) and the mean time between repairs (MTBR) for this functional location for the last 5 years by quarter?Are there any trends in malfunctions across a particular functional location and associated hierarchy? [. . . ] Each maintenance Service Order can include actual cost and an estimate of the cost to complete the Service Order. SAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. Actual costs are posted at confirmation time, and can be analyzed after work is completed.
Reports
Sample Reports for this section include:
·
Service Cost Balance Trend Comparison
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide 123
4
Reports Service Order Cost
· ·
Service Cost Balance Variance Trend Service Cost YTD Trend Analysis
Service Cost Balance Trend Comparison
Displays the service cost balance trend data for the selected Company Code, Fiscal Years, and Equipment hierarchy.
Actual Balance Trend
View actual service cost balance trend by equipment hierarchy.
124 SAP BusinessObjects Plant Maintenance Rapid Mart XI 3. 2 for SAP solutions Business Guide
Reports Service Order Cost
4
Variance Previous Period
View actual service cost variance vs. previous period trend by equipment hierarchy.
Calculations
· ·
Section Hierarchy Lvl 1 = [Equipment Level 1 Full Name] Balance Variance vs. [. . . ]