R3 DD-PRO-090 WMT-M-59569 Work Management Metrics v5 0

DD-PRO-090 WRICEFAMPS
Functional Specifications
WMT-M-59569 Work Management Metrics
Release 3
Sirirat Sethapokin
02 June 2011
1SAP Release 3
DD-PRO-090 WRICEFAMPS Functional Specifications
WMT-M- Work Management Metrics
1SAP Release 3
Document Information
Document Title: WMT-M–59569 Work Management Metrics
Document Purpose: This document depicts the requirements pertaining to the Work Management
Metrics. It provides the development team with a basis to develop the required
Metrics.
File Name: R3 DD-PRO-090 WMT-M 59569 Work Management Metrics v5.0
File Location: https://eroom3.bhpbilliton.com/eRoom/Facility54/1SAPProject6/0_155b1
<Process Team>: WMT Work Management <Dev Type>: R Report
Document Owner
Author Position / Responsibility
Sirirat Sethapokin Process Analyst
Vaishali Pethad R&A Consultant
Change History – Current Release

Version No. Date Changed Modified By Change Nature of Amendment
Request
Mercury #
0.1 May 2011 Sirirat Sethapokin Include R3 requirements
1.0 October 2011 Tugrul Baysal Signed-off
1.1 January 2012 Sirirat Sethapokin CR76191 1. Correct definitions of Metrics to align
with Detail Report
2. Change Technical Name of Metrics
3. Add MDQ Metrics
4. Correct Test Conditions
1.2 January 2012 Sirirat Sethapokin CR77188 Change Metric Type 1 Water Input
2.0 March 2012 Tugrul Baysal Signed-off
2.1 April 2012 Sirirat CR81083 1. Change filter date of ‘Cancelled
Sethapokin System Generated Work Orders’
metric from ‘Completion Date
(TECO)’ to be ‘Completion Date’
2. Correct description of
numerator and denominator for
Finished WO not Completed
3. Add filter Event Notification on

Immediate/Urgent WO with
Impact Data
3.0 April 2012 Tugrul Baysal Signed-off
3.1 May 2012 Sirirat CR83230 1. Add User Status ‘NEW’ for
Sethapokin ‘Cancelled Notification Indicator’.
CR83236 2. Add new Main Work Centre to

capture first 4 digits from
Resource Work Centre for
Operation
Date of Issue: 27/07/2012

 2009 BHP Billiton Commercial in Confidence Page 2 of 56
1SAP Release 3
4.0 May 2012 Tugrul Baysal Signed-off

4.1 July 2012 Sirirat CR85793 Remove redundant detail on
Sethapokin characteristic filters
5.0 July 2012 Tugrul Baysal Signed-off
Change History – Previous Release

Version No. Date Changed Modified By Change Nature of Amendment
Request
Mercury #
0.1 August 2008 Goh Kai Hock Initial document
0.2 October 2008 Syed Faisal Updated with details from Shane
0.4 April 2009 Syed Faisal First Review (CR)
0.5 April 2009 David Alonso Additional Review (CR)
1.0 November 2009 Syed Faisal Final Update
1.1 April 2010 Shane Visser Update to new Template and Release 2
design
2.0 June 2010 Mark Salamone Final version sign off
1.0 7th of July 2010 PMO Signed final version
1.1 August 2010 Shane Visser CR‟s 59612 & Change Workload Control Filter
59614 Add Capacity Loading PI
Updated HR KPI spec.
FS number changed from 56087 to
59569 as per R&A
2.0 September 2010 Mark Salamone Final version sign off
3.0 December 2010 Joo Keng Teo CR: 61439 Correct word for Planned Work
Approvals Record
Approver Title / Role Signature
Tugrul Baysal Work management Process Engineer 2012.07.27
16:27:19
+08'00'
Document Distribution
Recipient Position / Responsibility
Charles Fazackerley Work Management Process Lead
Greg Owens Integration Engineer – Applications and Integration
Christian Schelling Integration Engineer – BPM, Methodology and Training
Christian Hobelsberger Integration Engineer – Development and Netweaver
Miguel Barbosa Integration Engineer – Security & Compliance

1SAP Release 3
Table of Contents
1 WRICEFAMP Information .................................................................................... 7

1.1 Document References .................................................................................. 7
2 Introduction ..................................................................................................... 8
2.1 Functional Description .................................................................................. 8
2.2 Assumptions.............................................................................................. 9
3 Metrics ......................................................................................................... 10
3.1 Metric: Compliance to Work Plan ....................................................................10
3.1.1 Information.....................................................................................10
3.1.2 Calculation Details............................................................................10
3.1.3 Data Source ...................................................................................10
3.1.4 Metric specific Notes / constraints / assumptions .......................................10
3.1.5 Metric Technical Details .....................................................................10
3.2 Metric: Adherence to Schedule Done on the Day .................................................12
3.2.1 Information.....................................................................................12
3.2.3 Data Source ...................................................................................12
3.3 Metric: Planned & Scheduled Work .................................................................14
3.3.1 Information.....................................................................................14
3.3.3 Data Source ...................................................................................14
3.4 Metric : Adherence to Schedule Finished within the Week ......................................16
3.4.1 Information.....................................................................................16
3.4.3 Data Source ...................................................................................16
3.4.5 Illustrative Example ..........................................................................16
3.5 Metric : Outstanding Work Orders and Notifications ..............................................18
3.5.1 Information.....................................................................................18
3.5.3 Data Source ...................................................................................18
3.6 Metric : Work Orders with Task List .................................................................24
3.6.1 Information.....................................................................................24
3.6.3 Data Source ...................................................................................24
1SAP Release 3
3.7 Metric : Finished Work Orders not Completed .....................................................25

3.7.1 Information.....................................................................................25
3.7.3 Data Source ...................................................................................26
3.8 Metric : Immediate/Urgent Work Orders with Impact Data Entered ............................28
3.8.1 Information.....................................................................................28
3.8.3 Data Source ...................................................................................28
3.9 Metric: Overdue System Generated Work Orders ................................................30
3.9.1 Information.....................................................................................30
3.9.3 Data Source ...................................................................................30
3.10 Metric: Schedule Loading .............................................................................32
3.10.1 Information.....................................................................................33
3.10.3 Data Source ...................................................................................33
3.11 Metric: Cancelled System Generated Work Orders ...............................................35
3.11.1 Information.....................................................................................35
3.11.3 Data Source ...................................................................................35
3.12 Metric: Fatalities ........................................................................................36
3.12.1 Information.....................................................................................36
3.12.3 Data Source ...................................................................................37
3.13 Metric: Total Recordable Injury Frequency .........................................................38
3.13.1 Information.....................................................................................38
3.13.3 Data Source ...................................................................................38
3.14 Metric: Occupational Illnesses ........................................................................41
3.14.1 Information.....................................................................................41
3.14.3 Data Source ...................................................................................42
1SAP Release 3
3.15 Metric: HSEC Significant Events .....................................................................43

3.15.1 Information.....................................................................................43
3.15.3 Data Source ...................................................................................43
3.16 Metric: Type 1 Water Input ............................................................................44
3.16.1 Information.....................................................................................45
3.16.3 Data Source ...................................................................................45
3.17 Metric: Greenhouse Gas Emissions .................................................................46
3.17.1 Information.....................................................................................46
3.17.3 Data Source ...................................................................................46
3.18 Metric: Additional Metrics..............................................................................47
4 Business Test Conditions................................................................................... 48
5 Appendices ................................................................................................... 52
5.1 Glossary of Terms ......................................................................................52
5.2 Glossary of Notification System Status .............................................................54
5.3 Glossary of Notification User Status .................................................................54
5.4 Glossary of Work Order Header System Status ...................................................55
5.5 Glossary of Work Order User System Status ......................................................55
5.6 Glossary of Work Order Operation User System Status .........................................55
5.7 Typographic Conventions .............................................................................55

1SAP Release 3
1 WRICEFAMP Information
WRICEF ID: WMT-M-59569–Work Management Metrics
Description: As part of the 1SAP project, metrics have been identified to enable BHP Billiton to
better analyse performance and to identify potential areas of improvement.
Team: Work Management
Area (SAP Components): PM
Priority:
High/mandatory Med/recommend Low/optional
Complexity:
Very Complex Complex Medium Simple
Property Level Description

Priority Mandatory Item is required to run business on 'day one' and directly support the business
case of the project
Recommended Item is not required to run the business on 'day one' and indirectly supports the
business case and quality of the project
Optional Item has little or no impact on running the business and does not support the
business case or quality of the project
Complexity Very Complex Applies for technically very challenging areas using „new technologies‟.
Complex Use of advanced „technologies‟. Complex algorithm. Complex / Sensitive

enhancements.
Medium Standard developments which we have been done in a similar manner before.
Simple Simple Enhancements.
1.1 Document References
Reference Description Link / Location

Main Process: 402.01 Performance Management
Table 1.1-1: Document references.

1SAP Release 3
2 Introduction
2.1 Functional Description
Work Management Metrics have been identified to enable Work Management GJG to analyse performance and to
identify potential areas of improvement. In the Asset Report, Work Management Metrics are grouped into two groups
with the details below:
List of Non HSEC Specific Metrics
- Compliance to Work Plan

- Planned & Scheduled Work
- Work Orders with Task List
- Finished Work Orders not Completed
- Overdue System Generated Work Orders
- Cancelled System Generated Work Orders
- Outstanding Work Orders and Notification
- Immediate/Urgent Work Orders with Impact Data Entered
- Adherence to Schedule Done on the Day
- Adherence to Schedule Finished within the Week
- Schedule Loading
List of HSEC Specific Metrics

- Fatalities
- Total Recordable Injury Frequency
- Occupational Illnesses
- Type 1 Water Input
- Greenhouse Gas Emissions
- HSEC Significant Events
All metrics will be presented monthly. In most of the metrics, information for the monthly figures originate from the date
of transaction, with the exception of the metrics listed below which are derived from weekly snapped data. Historical
Data cannot be reloaded to the Snapshot due to changes of the Statuses.
Work Order and Operation scheduling, which reflects the following mechanism:
 Snap data includes Work Orders with header user status = SCH (Scheduled) or Work Order Operations with user
status = DSP (Dispatched) as at the date of snapshot.
 Scheduling has to be completed by Thursday night by 23:59:59, as the Snap for the following Scheduling Week
occurs at 23:59:59 every Thursday night local time for individual Planning Plants based on the user time zones.
The Scheduling Week is expected to have a list of Work Orders and operations along with other related data,
such as dates, status etc. The Work Orders and operations contained in this list is not to change for any reason
as it is the baseline for the metrics.
 Scheduling Week = Monday to Sunday always.
 The metric results for‟ „Adherence to Schedule Finished within the Week‟ will fall into the month in which the last
day of the Scheduling Week (Sunday), lies.
For example:
 If the Sunday is on the 1st of September, the results of the entire scheduling week results will be
reflected in the reporting month of September even though most of the week was in August
 The metrics results for „Adherence to Schedule Done on the Day‟ will fall into the months as per operation early
start Date.
1SAP Release 3
Interval and Shift Capacity, which reflects the following mechanism:

 Interval and shift data should be maintained for the resource work centre before Thursday 24:00:00 hrs. (If
interval/shift data is not maintained before the last snap job, header capacity will be taken into account (as per the
standard extractor functionality).
 Scheduling Week = Monday to Sunday always.
 The metric results for ‟Schedule Loading‟ will fall into the month in which the last day of the Scheduling week
(Sunday), lies.
Outstanding Work Orders and Notification, which reflects the following mechanism:
 Data is derived from transaction data.
HSEC Reporting
Where Measurement Documents are used, the Measurement Reading Date is used to determine the reporting period.
For example:
If the Measurement Reading Date is the 30th of September, the data will be included into the September period.
2.2 Assumptions
 All data will be sourced from ECC.

 All metrics are based on process design.
 The Reporting Units are complex and will require updating when new Planner Groups or Plants are created.
 All New and changed R3 Metrics will exhibit refresh of Data.
 All the existing unchanged R3 Metrics (listed below) will retain historical Data in Snapshot metric version:
1. Adherence to Schedule Done on the Day
2. Planned and Scheduled work
3. Finished Work Orders not completed
4. Compliance to Work Plan
 For Non HSEC Specific metrics all data will be updated in the 2nd calendar day of each month.
 For HSEC Specific metrics all data will be updated in the 8th calendar day of each month.

1SAP Release 3
3 Metrics
3.1 Metric: Compliance to Work Plan
3.1.1 Information
Short name
Long name Compliance to Work Plan
Description Compares the number of finished system generated Work Orders in
period within tolerance, to the number of finished system generated Work
Orders in period.
Technical Name WKM009
3.1.2 Calculation Details
Formula (Number of finished system generated Work Orders in period within

tolerance / Number of finished system generated Work Orders in period)
*100
Unit of measure %
3.1.3 Data Source

Source data BW
Source data details Work Orders Report
3.1.4 Metric specific Notes / constraints / assumptions

nd
Data to be loaded on 2 Calendar day of every month.
3.1.5 Metric Technical Details
Report Field Name SAP Table-Field Name SAP BI Info Object Comments / Filters / Calculation /
<Process Specialist> <Process Specialist> <R&A Consultant> Formula / Descriptions
<Process Specialist>
Hierarchies
List fields that are needed to derive Reporting Unit
Plant AFIH- GEWRK => RPLANT To derive for Reporting Unit
CRHD -WERKS
Planner Group AFIH-INGRP RPMPLNGRP To derive for Reporting Unit
Characteristics
List fields that are needed to select and filter relevant data from source
Order Actual End date AFKO-GETRI 0CALMONTH Is equal to Metric period
Work Order Type AUFK-AUART RCORD_TYP
Work Order Header User AUFK- OBJNR -> RPM_ORDER__R
Status JEST- OBJNR -> STATUSR1
JEST - STAT

1SAP Release 3
Work Order Header System AUFK - OBJNR -> RPM_ORDER__R

Status JEST- OBJNR -> STATSYS0
JEST - STAT
Work Order Category AFIH -AKKNZ ROCATIND
Called Planned Date MHIS-NPLDA
Planner Group AFIH-INGRP RPMPLNGRP
Main Work Centre AUFK-VAPLZ RWORKCNTR
Plant AFIH- GEWRK => RPLANT
CRHD -WERKS
Planning Plant AFIH-IWERK RPLNPLANT
Key Figures
List fields that are needed to the calculations
Tolerance for Compliance Derived 10% of the Work Plan frequency
(Days) (min 1 day)
Include:
 Work order type = PM02
 Work Order Header System
Status = CNF or TECO or CLSD
 Work Order Header User Status
= SCH
 Work Order Category = 4
Order Actual End Date = Not Null
Execution Interval (Days) Count of days Order Actual Start Date - Called
Planned Date
Include:
 Work Order Type = PM02
= SCH
 Order Actual End Date = Not
Null
Finished PM02 Work Orders Count of Work Count of Work Orders
within tolerance Orders
Include:
Status = CNF, TECO, CLSD
= SCH
Null
 Execution Interval (Days) is
within ( ≤ ) Tolerance for
Compliance (Days)

1SAP Release 3
Finished PM02 Work Orders Count of Work Count of Work Orders

Orders
Include:
= SCH
Null
Calculations
Details on calculations
Numerator N/A RNOM_U Sum of Finished PM02 Work
Orders within tolerance
Denominator N/A RDEM_U Sum of Finished PM02 Work Orders
Metric - Result N/A N/A (Sum of Finished PM02 Work

Orders within tolerance/ Sum of
Finished PM02 Work Orders) * 100
3.2 Metric: Adherence to Schedule Done on the Day
3.2.1 Information
Short name
Long name Adherence to Schedule Done on the Day
Description Compares the number of Scheduled Work Order Operations in period
that was started inside a 24 hour window of the scheduled start time, to
the number of Scheduled Work Order Operations in the period.
Formula (Number of Scheduled Work Order Operations in period that were started
inside a 24 hour window / Number of Scheduled Work Order Operations
in period) *100
Unit of measure %
3.2.3 Data Source

Source data BW
Source data details Work Order Scheduling Report

 The Operation Early Start Date is the date captured in the snapshot of Thursday 23:59:59 (local time).
 The report is based on Weekly Snap data from Work Order scheduling.
 Data to be loaded on 2nd Calendar Day of every month.

1SAP Release 3
Hierarchies
CRHD -WERKS
Characteristics
Operation Early Start Date AFVV-FSAVD 0CALMONTH Is equal to Metric period
Operation Early Start Time AFVV-FSAVZ RSTARTTIM
Work Order Types AUFK-AUART RCORD_TYP
Work Order Priority AFIH-PRIOK RPRIORITY
Revision Type T352R_D-REVTY RICHREVNO_
RREV_TYP
Operation Actual Start Date AFVV-ISDD RACTSTART
Operation Actual Start Time AFVV-ISDZ ROPR_AST
CRHD -WERKS
Key Figures
Compliant Operations Count of Count of Operations
Operations
Include:
 All Snapped Operations
 Work Order Type = PM01 or
PM02 or PM04 or PM06
 Operation Actual Start Date and
Time is within the scheduled 24
hour window
 Scheduled Window = Early Start
Date and Time minus 6 hours
and plus 18 hours.
Exclude:
 Revision Type = 2
 Priority = Immediate or
Urgent (1 or 2)
Scheduled operations Count of Count of Operations
Operations
Include:
Exclude:
 Priority = Immediate or
Urgent (1 or 2)

1SAP Release 3
Calculations
Numerator N/A RNOM_U Sum of Compliant Operations
Denominator N/A RDEM_U Sum of Scheduled Operations
Metric - Result N/A N/A (Sum of Compliant Operations /
Sum of Scheduled operations) *100
3.3 Metric: Planned & Scheduled Work
3.3.1 Information
Short name
Long name Planned & Scheduled Work
Description Compares the sum of actual hours Time Confirmed on Planned and
Scheduled Work Orders in period, to the sum of actual hours Time
Confirmed Work Orders in the period.
Formula (Sum of actual hours Time Confirmed on Planned and Scheduled Work
Orders in period / Sum of actual hours Time Confirmed on Work Orders
in period)*100
Unit of measure %
3.3.3 Data Source

Source data BW
Source data details Work Order Report


nd
Data to be loaded on 2 Calendar of every month
Hierarchies
CRHD -WERKS
Characteristics
Work Order Actual End Date AFKO-GETRI 0CALMONTH Is equal to Metric period
1SAP Release 3

JEST - STAT
Work Order Header User AUFK- OBJNR ->
Status JEST- OBJNR -> RPM_ORDER__R
JEST - STAT STATUSR1
Work Order Creation Date AUFK-ERDAT RDOCCRTDT
Order Actual Start Date AFKO-GSTRI
Plant AFIH- GEWRK =>
CRHD -WERKS RPLANT
Key Figures
Actual Work (hours) AFVV-ISMNW RWOPRWORK
Days Variance from Work AFKO-GSTRI minus Count of Days Order Actual Start date – Work
Order Creation Date to AUFK-ERDAT Order Creation Date
Actual Start
Include:
 Order Types = PM01 or
 Header System Status = CNF or
TECO or CLSD
= SCH
Exclude:
 Order Actual End Date = Null
 Priority = Immediate or Urgent
(1 or 2)
N/A Count of Actual Count of Actual Work (hours)
Work (hours)
Include:
 Order Types = PM01 or
TECO or CLSD
Confirmed Work Hours for
= SCH
Planned & Scheduled Work
 Days Variance from Work Order
Creation Date to Actual Start is
greater than 7 days
Exclude:
(1 or 2)

1SAP Release 3
Work Order Hours N/A Count of Actual Count of Actual Work (hours)
Work (hours)
Include:
 Work order type = PM01 or
PM02 or PM03 or PM04 or
PM06
TECO or CLSD
Exclude:
Calculations
Numerator N/A Sum of Confirmed Work Hours for
RNOM_U Planned & Scheduled Work
Denominator N/A RDEM_U Sum of Work Order Hours

Metric - Result N/A N/A (Sum of Confirmed Work Hours for
Planned & Scheduled Work / Sum
of Work Order Hours)*100
3.4 Metric : Adherence to Schedule Finished within the Week
3.4.1 Information
Short name
Long name Adherence to Schedule Finished within the Week
Description Compares the number of finished Scheduled Work Orders in period, to
the number of Scheduled Work Orders for execution in period.
Formula (Number of finished Scheduled Work Orders in period / Number of

Scheduled Work Orders for execution in period) *100
Unit of measure %
3.4.3 Data Source

Source data BW

 The Basic Finish Date is the date captured in the snapshot of Thursday 23:59:59 (local time).
 Data to be loaded on 2nd Calendar of every month.
3.4.5 Illustrative Example

1SAP Release 3
 None
Hierarchies
CRHD -WERKS
Characteristics
Last Date of Scheduling 0CALMONTH Is equal to Metric period
Week Derived
Basic Finish Date AFKO-GLTRP RFINISHDT
Work Order Priority AFIH- PRIOK RPRIORITY
Revision Type T352R_D-REVTY RICHREVNO__
RREV_TYP
Work Order Actual End Date AFKO-GETRI RORD_ENDT Exclude: Null
CRHD -WERKS
JEST - STAT
Key Figures
Number of Finished Count of Work Count of Work Orders

Scheduled Work Orders Orders
Include:
 All Snapped Work Orders
 Order Actual End Date within
Basic Finish Date range
Exclude:
(1 or 2)

1SAP Release 3
Number of Scheduled Work N/A Count of Work Count of Work Orders

Orders Orders
Include:
 All Snapped Work Orders
Status = REL or PCNF or CNF
or TECO or CLSD
Exclude:
(1 or 2)
Calculations
Numerator N/A RNOM_U Number of Finished Scheduled
Work Orders
Denominator N/A RDEM_U Number of Scheduled Work Orders
Metric - Result N/A N/A (Number of finished Scheduled
Work Orders / Number of
Scheduled Work Orders) *100
3.5 Metric : Outstanding Work Orders and Notifications
3.5.1 Information
Short name
Long name Outstanding Work Orders and Notifications
Description Compares the number of outstanding Notifications and outstanding Work
Orders to the number of open Notifications and open Work Orders.
Formula (Number of outstanding Notifications + Number of outstanding Work

Orders) / (Number of open Notifications + Number of open Work Orders)
*100
Unit of measure %
3.5.3 Data Source

Source data BW
Source data details Work Order Report and Notification Report

 The report is based on transaction data from both Work Orders and Notification.
 Outstanding Work Orders:
 The Variance from Basic Start Date will be calculated considering the Last Date of the Metric month –
Order Basic Start date
1SAP Release 3
 Outstanding Notification:
 Notification Age in Days will be calculated considering the Last date of the metric month – Notification
Created date
 Data to be loaded on 2nd Calendar Day of every month
Hierarchies
Plant For Work Order: RPLANT To derive for Reporting Unit
AFIH- GEWRK =>
CRHD -WERKS
For Notification:
QMEL- ARBPLWERK
Planner Group For Work Order: RPMPLNGRP To derive for Reporting Unit
AFIH-INGRP
For Notification:
QMIH-INGRP
Characteristics
Metric month Load Date‟s previous 0CALMONTH Is equal to Metric period
month
Work Order Type For Work Order: RCORD_TYP
AUFK-AUART
For Work Order: RPM_ORDER__R
Work Order Header System AUFK - OBJNR -> STATSYS0
Status JEST- OBJNR ->
JEST - STAT
Order Basic Start Date For Notification: RBASSTART
AFKO-GSTRP
Order Actual End Date For Work Order:
AFKO-GETRI
Notification Type For Notification: RNOT_TYPE
QMEL-QMART
TQ80_T-QMARTX
Notification System Status For Notification: RNOTIFNUM__RS
JEST – STAT TATSYS0
Notification‟s Cancelled For Notification: RNOTIFNUM_RNO
Indicator Derived TIFCIND
Notification Created Date For Notification:

QMEL-ERDAT
BW Status: NTF2 For Notification:
JEST – STAT
Planner Group For Work Order: RPMPLNGRP
AUFK-WERKS
For Notification:
QMIH-INGRP

1SAP Release 3
Main Work Centre For Work Order: RWORKCNTR

AFIH-INGRP
For Notification:
QMEL- ARBPL ->
CRHD-ARBPL
Plant For Work Order: RPLANT
AFIH- GEWRK =>
CRHD -WERKS
For Notification:
QMEL- ARBPLWERK
Planning Plant For Work Order: RPLNPLANT
AFIH-IWERK
For Notification:
QMEL- QMNUM ->
QMIH- IWERK
Notification System Status For Notification: RCREATEON
Date (NOCO/ORAS) JCDS-UDATE
Key Figures
Days Variance from Last Count of Days Last date of the metric month –
date of the metric month to Basic Start date
Basic Start Date(Orders)
Include:
 Work order type = PM01 or PM02
or PM03 or PM04 or PM06
Outstanding WO > Count of Work Count of Work Orders

Threshold (metric month) Orders
Include:
 Days Variance from Last date of
metric month to Basic Start Date
(Orders)> 7 days
 Work Order Creation Date≤ last
date of metric month
Exclude:

1SAP Release 3
Outstanding WO > Count of Work Count of Work Orders

Threshold (snapshot month) Orders
Include:
 Days Variance from Last date of
the metric month to Basic Start
Date (Orders)> 7 days
TECO or CLSD
 Work Order Actual End Date >
last date of metric month
* e.g. metric load for June 2011
on 2nd July 2011 includes Work
Orders with Actual End Date =
01.07.2011 – 02.07.2011
Outstanding Work Orders CKF:
older than Threshold
Outstanding WO >
Threshold (metric
month)
+
Outstanding WO >
Threshold
(snapshot month)
Outstanding Work Orders Count of Work Count of Work Orders
(metric month) Orders
Include:
Exclude:
 Header System Status = CNF
orTECO or CLSD
Outstanding Work Orders Count of Work Count of Work Orders
(snapshot month) Orders
Include:
TECO or CLSD
* e.g. metric loading for June

2011 on 2nd July 2011: includes
Work Orders with Actual End
Date = 01.07.2011 – 02.07.2011

1SAP Release 3
Outstanding Work Orders CKF:
Outstanding Work
Orders (metric
month)
+
Outstanding Work
Orders (snapshot
month)
Notification Age in Days Count of Days Last date of the metric month –
Notification Created Date
Outstanding M1 Notif > 7 Count of Count of Notifications
days (metric month) Notifications
Include:
 Notification type = M1
 System status = OSNO or NOPR
 Notification Age in Days > 7 days
 Notification Created Date ≤ last
Exclude:
 BW Status: NTF2 = ORAS
 Notification‟s Cancelled Indicator
=X
Outstanding M1 Notif > 7 Count of Count of Notifications
days (snapshot month) Notifications
Include:
 Notification type – M1
 System status = ORAS or NOCO
 Notification Age in Days > 7 days
 Notification system status Date
(ORAS/NOCO)> last date of
metric month

*e.g. metric loading for June 2011
on 2nd July 2011: includes
Notification with Notification
System Status Date
(ORAS/NOCO) Date =
01.07.2011 – 02.07.2011
Exclude:
=X
Outstanding M1 Notifications CKF:
> 7 days
Outstanding M1
Notif > 7 days
(metric month)
+
Outstanding M1
Notif > 7 days
(snapshot month)

1SAP Release 3
Outstanding M1 (metric Count of Count of Notification

month) Notifications
Include:
 System status = OSNO or NOPR
Exclude:
 BW Status: NTF2 = ORAS
=X
Outstanding M1 (snapshot Count of Count of Notification
month) Notifications
Include:
 System status = ORAS or NOCO
 Notification system status Date
ORAS/NOCO> last date of metric
month

Notification with Notification
System Status Date
(ORAS/NOCO) Date =
01.07.2011 – 02.07.2011
Exclude:
=X
Outstanding M1 Notifications CKF:
Outstanding M1
(metric month)
+
Outstanding M1
(snapshot month)
Calculations
Numerator N/A RNOM_U Sum of Outstanding Work Orders
older than Threshold +
Sum of M1 Notifications older than
7 days
Denominator N/A RDEM_U Sum of Outstanding Work Orders +

Sum of Outstanding M1
Notifications
Metric - Result N/A N/A [(Sum of Outstanding Work Orders
older than Threshold) + (Sum of M1
Notifications older than 7 days)] /
[(Sum of Outstanding Work Orders)
+ (Sum of Outstanding M1
Notifications)] * 100

1SAP Release 3
3.6 Metric : Work Orders with Task List
3.6.1 Information
Short name
Long name Work Orders with Task List
Description Compares the number of completed Work Orders in period which have a
Task List, to the number of completed Work Orders in period.
Formula (Number of completed Work Orders in period which have a Task List /
Number of completed Work Orders in period) * 100
Unit of measure %
3.6.3 Data Source

Source data BW

Hierarchies
CRHD -WERKS
Characteristics
Work Order Actual End Date AFKO-GETRI 0CALMONTH Is equal to Metric period
JEST - STAT
Status1 JEST- OBJNR -> STATSYS1
JEST - STAT
CRHD -WERKS
1SAP Release 3
Task list Group QMIH-PLNNR RNOTIFNUM__RP

LNNR
Key Figures
No. Completed Work Orders Count of Work Count of Work Orders
with a Task List Orders Includes:
Status = TECO or CLSD;
 Task List Group = Not Null
Exclude:
Status1 = NCMP
No. Completed Work Orders N/A Count of Work Count of Work Orders
Orders Includes:
Status = TECO or CLSD;
Exclude:
Status1 = NCMP
Calculations
Numerator N/A RNOM_U Sum of Completed Work Orders
with a Task List
Denominator N/A RDEM_U Sum of Completed Work Orders

Metric - Result N/A N/A (Sum of Completed Work Orders
with a Task List / Sum of
Completed Work Orders) x 100
3.7 Metric : Finished Work Orders not Completed
3.7.1 Information
Short name
Long name Finished Work Orders not Completed
Description Compares the number of finished but not completed Work Orders older
than threshold, to the number of Finished but not completed Work
Orders.
Formula (Number of finished but not completed Work Orders older than threshold /
Number of finished but not completed Work Orders) *100
Unit of measure %

1SAP Release 3
3.7.3 Data Source

Source data BW

 The report is based on transaction data from outstanding Work Orders.
 Confirmed Work Orders not Completed:
 Include all work order with Order Actual end Date equals not Null

nd
Data to be loaded on 2 Calendar Day of every month
Hierarchies
CRHD -WERKS
Characteristics
month
Order Actual End Date AFKO-GETRI RORD_ENDT
Work Order Completion RWOCOMPDT
AUFK-IDAT2
Date (TECO)
CRHD -WERKS
Key Figures
Days Variance from Last Last date of metric Count of Days Last Date of metric month - Order
Date of the metric month to month minus AFKO- Actual End Date
Order Actual End Date GETRI
Finished but not completed Count of Work Count of Work Orders.
Work Orders older than Orders Include:
threshold (metric month)  Work order type = PM01 or
PM06
 Work Orders with „Days
Variance from Last date of
metric month to Order Actual
End Date „> 7 days
 Work Order Completion Date
(TECO) = Null
 Order Actual End Date ≤ last
Exclude:
 Order Actual End Date ≠ Null

1SAP Release 3

Work Orders older than Orders Include:
threshold (Snapshot month)  Work order type = PM01 or
PM06
 Work Orders with „Days
Variance from Last date of
metric month to Order Actual
End Date > 7 days
(TECO) > last date of metric
month or null
Finished but not completed CKF:
Work Orders older than
threshold Work Orders
Finished > 7 days
not TECOd (metric
month)
+
Work Orders
Finished > 7 days
not TECOd
(snapshot month)
Work Orders (metric month) Orders Include:
 Work order type = PM01 or
PM06
(TECO) = Null
Exclude:
 Order Actual End Date ≠ Null
Work Orders (snapshot Orders Include:
month)  Work order type = PM01 or
PM06
(TECO) > last date of metric
month or null
Finished but not completed CKF:
Work Orders
Finished Work
Orders (metric
month)
+
Finished Work
Orders (snapshot
month)
Calculations
1SAP Release 3
Numerator RNOM_U Sum of Work Orders Finished for

more than 7 days not TECOd
Denominator RDEM_U Sum of Finished Work Orders

Metric - Result N/A N/A (Sum of Finished but not completed
Work Orders older than threshold /
(Sum of Finished but not completed
Work Orders)*100
3.8 Metric : Immediate/Urgent Work Orders with Impact Data Entered
3.8.1 Information
Short name
Long name Immediate/Urgent Work Orders with Impact Data Entered
Description Compares the number of Notifications for Immediate/Urgent Work Orders
completed in period with all three Impact Data Codes entered, to the
number of Notifications for Immediate/Urgent Work Orders completed
within period.
Formula (Number of Notifications for Immediate/Urgent Work Orders completed in

period with all three Impact Data Codes entered / Number of Notifications
for Immediate/Urgent Work Orders completed in period) * 100
Unit of measure %
3.8.3 Data Source

Source data BW
Source data details Notification Report

 Data to be loaded on 2nd Calendar Day of every month.
Hierarchies
Plant QMEL- ARBPLWERK RPLANT To derive for Reporting Unit
Planner Group QMIH-INGRP RPMPLNGRP To derive for Reporting Unit
Characteristics
Notification Completed Date QMEL - QMDAB 0CALMONTH Is equal to Metric period
Notification Type QMEL-QMART RNOT_TYPE
Notification Priority QMEL-PRIOK RPRIORITY

1SAP Release 3
Notification System Status JEST - STAT RNOTIFNUM__RS

TATSYS0
BW Status: NTF2 JEST – STAT Include: ORAS
Work Order Number QMEL-AUFNR RPM_ORDER
Work Order Type CAUFV-AUART RPM_ORDER__R
CORD_TYP
Impact Type QMFE-OTEIL RCATCODOT
Damage Code QMFE-FECOD RCATCODFE
Cause Code QMUR-URCOD RNOTCCODE
Notification‟s Cancelled Derived RNOTIFNUM_RNO Exclude: X
Indicator TIFCIND
Planner Group QMIH-INGRP RPMPLNGRP
Main Work Centre QMEL- ARBPL -> RWORKCNTR
CRHD-ARBPL
Plant QMEL- ARBPLWERK RPLANT
Key Figures
Notification for Count of Count of Notifications
Immediate/Urgent WO with Notifications Include:
Impact codes  Notification type = M1
 Notification System status =
NOCO
 Notification Priority = 1 or 2
 Notification system status ≠
DLFL
 Coding Catalogue = D
 Coding Group = PM00022
 Coding = S001
Exclude:
 Object Code = Null
 Damage Code = Null
 Cause Code = Null
 Work Order = Null
Notifications for Count of Count of Notifications
Immediate/Urgent WO Notifications Include:
 Notification System status =
NOCO
 Notification Priority = 1 or 2
 Notification system status ≠
DLFL
 Coding = S001
Exclude:
 Work Order = Null
Calculations

1SAP Release 3
Numerator RNOM_U Notification for Immediate/Urgent

WO with Impact codes
Denominator RDEM_U Notifications for Immediate/Urgent

WO
Metric - Result N/A N/A (Notification for Immediate/Urgent

WO with Impact codes/
Notifications for Immediate/Urgent
WO) * 100
3.9 Metric: Overdue System Generated Work Orders
3.9.1 Information
Short name
Long name Overdue System Generated Work Orders
Description Compares the number of unfinished system generated Work Orders that
are overdue, to the number of unfinished system generated Work Orders.
Formula (Number of unfinished system generated Work Orders that are overdue /
Number of unfinished system generated Work Orders) *100
Unit of measure %
3.9.3 Data Source

Source data BW

 The report is based on transaction data from Work Orders.
 Data to be loaded on 2nd Calendar day of every month.
Hierarchies
CRHD -WERKS
Planner Group AFIH-INGRP To derive for Reporting Unit
Characteristics

1SAP Release 3

month
Order Actual End Date AFKO-GETRI RORD_ENDT
JEST - STAT
Called Planned Date MHIS-NPLDA RNPLDA
Basic Start Date AFKO-GSTRP RBASSTART
Work Order Category AFIH -AKKNZ ROCATIND
CRHD -WERKS
Key Figures
Overdue Interval (Day) AUFK- GSTRP minus Count of days Basic Start Date - Called Planned
MHIS-NPLDA Date
Include:
Exclude:
Number of unfinished PM02 Count of Work Count of Work Orders
Work Orders overdue Orders Include:
(metric month)  Work Order Type = PM02
 Tolerance for Compliance
(Days) is within ( ≤ ) Overdue
Interval (Days)
 Work Order Creation Date ≤ last
Exclude:

1SAP Release 3
Number of unfinished PM02 Count of Work Count of Work Orders

Work Orders overdue Orders Include:
(snapshot month)  Work Order Type = PM02
 Tolerance for Compliance
(Days) is within ( ≤ ) Overdue
Interval (Days)
* e.g. metric load for June 2011

nd
on 2 July 2011 includes Work
Orders with Actual End Date =
01.07.2011 – 02.07.2011
Number of unfinished PM02 Count of Work Include:
Work Orders (metric month) Orders  Work Order Type = PM02

Exclude:
Number of unfinished PM02 Count of Work Include:
Work Orders (snapshot Orders  Work Order Type = PM02
month)  Work Order Category = 4

Work Orders with Actual End
Date = 01.07.2011 – 02.07.2011
Calculations
Numerator N/A RNOM_U Number of unfinished PM02 Work
Orders overdue
Denominator N/A RDEM_U Number of unfinished PM02 Work

Orders
Metric - Result N/A N/A (Number of unfinished PM02 Work
Orders overdue / Number of
finished PM02 Work Orders) *100
3.10 Metric: Schedule Loading

1SAP Release 3
3.10.1 Information
Short name
Long name Schedule Loading
Description Compares the sum of hours Scheduled on Work Order Operations for
execution by Capacity Managed Resource Work Centres in period, to
Capacity Available on Capacity Managed Resource Work Centres in
period.
Formula (Sum of hours Scheduled on Work Order Operations against Capacity

Managed Work Centres in period / Sum of Capacity Available on
Capacity Managed Work Centres in period) * 100
Unit of measure %
3.10.3 Data Source

Source data BW

 The Operation Early Start Date is the date captured in the snapshot of Thursday 23:59:59 (local time).
 The Interval and shift Capacity date is the date capture in the snapshot of Friday 12:00:00 UTC.
 The Resource Work Centre capacity derived from the Shifts and Intervals is aligned with the same Scheduling
Week used for the Adherence to Schedule Done on the Day.
 This metric can only be drilled down by CSG, Asset, Operation, Plant and Main Work Centre
Hierarchies
Plant Work Order: RPLANT To derive for Reporting Unit
AFIH- GEWRK =>
CRHD -WERKS
Work Centre Capacity:

CRHD- WERKS
Characteristics
Last Date of Scheduling
Week Derived 0CALMONTH Is equal to Metric period
Operation Early Start Date AFVV-FSAVD RSTARTDT
Capacity Validity End date KAPA-DATUB
1SAP Release 3
Work Centre Responsible

Person CRHD-VERAN RWRKCTRES
Control Key AFVC-STEUS
Work Order Operation AFVC- OBJNR -> RPM_ORDER__R
System Status JEST- OBJNR -> STATSYS0
JEST - STAT
Main Work Centre Derived: RWORKCNTR
First four digits of
the resource Work
Centre (if exist in table
CRHD and where
WERKS is equal to
Plant of Resource Work
Centre)
Plant Work Order: RPLANT

AUFK-WERKS
Work Centre Capacity:

CRHD- WERKS
Key Figures
Available capacity (Hours) PPWCCP_BW -ANGEB Interval and Shift Capacity
Planned Work on Scheduled N/A Planned Work (Hours)
Operations
AFVV-ARBEI Include:
 Work Centre Responsible
Person = PM4
Exclude:
(1 or 2)
 Control Key = PMSV
Operation Work Centre N/A Available capacity (Hours)
Capacity Hours
Include:
 All Capacity Snap
 Work Centre Responsible
Person = PM4
Exclude:
 Control Key = PMSV
Calculations
Numerator N/A Sum of Planned Work on
Scheduled Operations
Denominator N/A Sum of Operation Work Centre
Capacity Hours
Metric - Result N/A (Sum of Planned Work on
Scheduled Operations / Sum of
Operation Work Centre (Capacity
Hours)

1SAP Release 3
3.11 Metric: Cancelled System Generated Work Orders
3.11.1 Information
Short name
Long name Cancelled System Generated Work Orders
Description Compares the number of system generated Work Orders cancelled in
period, to the number of system generated Work Orders completed in
period
Formula (Number of system generated Work Orders cancelled in period / Number

of system generated Work Orders completed in period) *100
Unit of measure %
3.11.3 Data Source

Source data BW


nd
Data to be loaded on 2 Calendar Day of every month.
 Data set considers only Work Orders with completed status.
Hierarchies
CRHD -WERKS
Characteristics
Work Order Completion AUFK-IDAT2 <> blank; 0CALMONTH Is equal to Metric period
Date Result = AUFK-IDAT2;
Elseif AUFK-IDAT3 <>
blank;
Result = AUFK-IDAT3;
Else blank.
JEST - STAT
Work Order Header User AUFK- OBJNR -> RPM_ORDER__R
Status JEST- OBJNR -> STATUSR1
JEST - STAT
1SAP Release 3

CRHD -WERKS
Key Figures
Number of system Count of Work Count of Work Orders
generated Work Orders Orders Include:
cancelled  Work Order Header System
Status = TECO or CLSD
Exclude:
= SCH
Number of system Count of Work Count of Work Orders
generated Work Orders Orders Include:
completed  Work Order Header System
Status = TECO or CLSD
Calculations
Numerator N/A Number of system generated Work
Orders cancelled
Denominator N/A Number of system generated Work

Orders completed
Metric - Result N/A (Number of system generated Work
Orders cancelled in period /
Number of system generated Work
Orders completed in period) *100
3.12 Metric: Fatalities
3.12.1 Information
Short name
Long name Fatalities
Description Defines the number of fatalities that have occurred within the period.
The measure is for 'controlled activities', which are activities where BHP
Billiton sets workplace HSEC standards and enforces their application.
Formula Total count of Notification Items with an Actual Severity Level = 4 against
the Impact Type of 'Safety' within Event Notifications.
Unit of measure ST

1SAP Release 3
3.12.3 Data Source

Source data BW

 The historical data of this metric is subject to change at any point of time; in order to stay in sync with ECC
data, this metric requires to be re-calculated for two fiscal years rolling back for every monthly cycle (as for
maximum number of periods in Asset report).

th
Hierarchies
Plant QMEL- ARBPLWERKS RPLANT To derive for Reporting Unit
Characteristics
Notification Date QMEL-QMDAT 0CALMONTH Is equal to Metric period
Notification Type QMEL-QMART
Notification‟s Cancelled Derived RNOTIFNUM_RNO
Indicator TIFCIND
BW Status: NTF1 JEST – STAT RNOTIFNUM_RST

ATUS1
Coding Catalogue QMEL- QMKAT RCAT_TYPE

Coding Group QMEL- QMGRP RCATGROUP
Coding QMEL- QMCOD RCAT_CODE
Impact Catalogue QMFE-OTKAT RCATTYPOT
Impact Group QMFE-OTGRP RCATGRPOT
Severity Level Actual Classification RSEV_ACT
Control Level Classification RCNTRLVL
CRHD-ARBPL
Planning Plant QMEL- QMNUM -> RPLNPLANT
QMIH- IWERK
Key Figures

1SAP Release 3
Count of Item Count of Items Count of Items

Include:
 Notification Type = M1
 Coding = S001
 Impact Catalogue = B
 Impact Group = Impact Type
 Impact Type = Safety
 Severity Level Actual = Level 4
 Control Level = Controlled
Exclude:
 Notification‟s Cancelled
Indicator = X
 BW Status: NTF1 = DLFL
Calculations
Metric - Result Sum of Count of Item
3.13 Metric: Total Recordable Injury Frequency
3.13.1 Information
Short name
Long name Total Recordable Injury Frequency (/ million manhour)
Description Defines the number of Recordable Injuries (Fatality, Lost Time Injury,
Restricted Work Injury, Medical Treatment Injury) per million hours
worked (exposure hours) within the period. The frequency, normalised by
exposure hours, enables direct comparison between businesses and
within businesses over time.
Formula [(Medical Treatment Injury + (Restricted Work Injury & Lost Time Injury) +
Fatality) / Exposure Hours]*1,000,000
Unit of measure ST/H
3.13.3 Data Source

Source data BW
Source data details Notification Report and Measurement Reading Report

data, this metric requires to be re-calculated for two fiscal years rolling back for every monthly cycle (as for
1SAP Release 3
 Data to be loaded on 8th Calendar of every month
Hierarchies
Plant Notification : RPLANT To derive for Reporting Unit
QMEL- ARBPLWERK
Measuring Document
IFLO -SWERK
EQUZ-SWERK
Planner Group Notification: RPMPLNGRP To derive for Reporting Unit
QMIH-INGRP
Measurement
Document:
IFLO-INGRP
EQUZ-INGRP
Characteristics
Notification: 0CALMONTH Is equal to Metric period
Notification Date QMEL-QMDAT
Measurement Date IMRG_IDATE 0CALMONTH Is equal to Metric period

Planner Group Notification :
QMIH-INGRP
Measurement
Document:
IFLO-INGRP
EQUZ-INGRP
Main Work Centre CRHD-ARBPL RWORKCNTR
Plant Notification : RPLANT

QMEL- ARBPLWERK
Measuring Document
IFLO-SWERK
Planning Plant For Notification: RPLNPLANT
QMEL- QMNUM ->
QMIH- IWERK
Measuring Document:
IFLO-IWERK
EQUZ-IWERK
Measuring Position IMPTT-PSORT RPSORT
Measurement Document‟s RREVERSAL
IMRG_CANCL
Reversal Indicator

1SAP Release 3
RNOTIFNUM_RNO
Notification‟s Cancelled
Derived TIFCIND
Indicator

ATUS1

Severity Level Actual Classification RSEV_ACT
Control Level Classification RCNTRLVL
Key Figures
Count of Item Count of Item
FtC (Fatality) Count of Item Includes:
 Coding = S001
 Impact Catalogue Type = B
 Impact group = Impact Type
 Impact Code = Safety
Excludes:
Indicator = X
MTC (Medical Treatment Count of Item Includes:
Injury)  Notification Type = M1
 Coding = S001
Excludes:
Indicator = X

1SAP Release 3
RWC & LTC (Restricted Count of Item Includes:

Work Injury and Lost Time  Notification Type = M1
Injury)  Coding Catalogue = D
 Coding = S001
Excludes:
Indicator = X
Exposure Hours - IMRG-READG Measurement Includes:
Reading  Measuring Position = “HSEC
C2001” and “HSEC E2001”
 Measurement Document‟s
Reversal Indicator = Null
Contractor/Employee N/A Notification:
If Vendor ≠ blank, „C‟.
If Vendor = blank, „E‟.
Measurement Document:
IMPTT-POINT > IMPTT-PSORT >
check first 6 characters
if „HSEC C‟, „C‟.
if „HSEC E‟, „E‟.
C = Contractor
E = Employee
Calculations
Numerator N/A MTC + RWC & LTC + FtC
Denominator N/A Exposure Hours
Metric - Result N/A CKF:
(MTC + RWC & LTC +
FtC)/(Exposure Hours)*1,000,000
3.14 Metric: Occupational Illnesses
3.14.1 Information
Short name
Long name Occupational Illnesses
Description Defines the number of Occupational Illnesses that have occurred within
the period.

1SAP Release 3
Formula Total Measurement Readings from Measuring Documents raised for

Occupational Illnesses.
Unit of measure ST
3.14.3 Data Source

Source data BW
Source data details Measurement Reading Report

data, this metric require to be re-calculated for two fiscal years rolling back for every monthly cycle (as for
Hierarchies
Plant IFLO-SWERK RPLANT To derive for Reporting Unit
EQUZ-SWERK
Planner Group IFLOT-INGRP RPMPLNGRP To derive for Reporting Unit
EQUZ-INGRP
Characteristics
Planner Group IFLOT-INGRP RPMPLNGRP
EQUZ-INGRP
Plant IFLO-SWERK RPLANT
EQUZ-SWERK
Planning Plant IFLO-IWERK RPLNPLANT
EQUZ-IWERK
Measuring Position IMPTT-PSORT
Measuring Point IMRG-POINT RMPOINT
IMRG_CANCL
Reversal Indicator
Unit IMRG_RECDU RRECDU
Key Figures
Measurement Reading IMRG-READG Include:
 From “HSEC C1001”
to “HSEC C1011”
 From “HSEC E1001”
to “HSEC E1011”
Reversal Indicator - Null
Calculations

1SAP Release 3
Metric - Result N/A N/A Sum of Measurement Reading
Convert to Unit
3.15 Metric: HSEC Significant Events
3.15.1 Information
Short name
Long name HSEC Significant Events
Description Defines the number of Events, within the period, with an potential level 4
or higher impact in one or more of the following Impact Types from the
BHP Billiton Severity Table:
- Health
- Safety
- Environment
- Social / Cultural
- Reputation
Formula Total count of Notification Items with a Potential Severity Level =/> 4
against a HSEC related Impact Type within Event Notifications.
Unit of measure ST
3.15.3 Data Source

Source data BW


th
Hierarchies
Plant QMEL- ARBPLWERK RPLANT To derive for Reporting Unit

1SAP Release 3
Characteristics
Notification Date QMEL-QMDAT 0CALMONTH Is equal to Metric period
Notification Number QMEL-QMNUM RNOTIFNUM
Notification‟s Cancelled Derived RNOTIFNUM_RNO
Indicator TIFCIND

CRHD-ARBPL
Planning Plant QMEL- QMNUM -> RPLNPLANT
QMIH- IWERK
ATUS1
Coding Catalogue QMEL- QMKAT RCAT_TYPE

Coding Group QMEL- QMGRP RCATGROUP
Coding QMEL- QMCOD RCAT_CODE
Severity Level Potential RSEV_ACT
Control Level Classification RCNTRLVL Include: Controlled
Key Figures
Count of Notifications Count of Count of all Notifications
Notifications Includes:
 Coding Catalogue Type = D
 Coding = S001
 Impact Catalogue = B
 Impact Group = Impact Type
 Impact Type = Safety, Health,
Environment, Social / Cultural,
Reputation
 Severity Level Potential ≥
Level 4
Excludes:
Indicator = X
Calculations
Metric - Result Sum of Count of Notifications
3.16 Metric: Type 1 Water Input

1SAP Release 3
3.16.1 Information
Short name
Long name Type 1 Water Input
Description The total volume of Type 1 water which is received by the operational
facility, or which has become available from within the operational facility,
from surface water, groundwater and third party water sources within the
period. Type 1 water is close to drinking water standards.
Formula The metric is the sum of the following Measuring Positions:

 HSEC 00032 [Water Input (Type 1): Surface water]
 HSEC 00033 [Water Input (Type 1): Groundwater]
 HSEC 00034 [Water Input (Type 1): Third party water]
Unit of measure Ml
3.16.3 Data Source

Source data BW

Hierarchies
EQUZ-SWERK
Planner Group IFLO-INGRP RPMPLNGRP To derive for Reporting Unit
EQUZ-INGRP
Characteristics
IMRG_CANCL
Reversal Indicator

1SAP Release 3

EQUZ-INGRP
EQUZ-IWERK
Unit IMRG_RECDU RRECDU
Key Figures
 From “HSEC 00032”
to “HSEC 00034”
Calculations
3.17 Metric: Greenhouse Gas Emissions
3.17.1 Information
Short name
Long name Greenhouse Gas Emissions
Description Defines the total amount of Greenhouse Gas Emissions produced within
the period.
Formula Total Measurement Readings from Measuring Documents raised for

Green House Gas Emissions.
Unit of measure KT
3.17.3 Data Source

Source data BW


th

1SAP Release 3
Hierarchies
EQUZ-SWERK
Planner Group IFLO-INGRP RPMPLNGRP To derive for Reporting Unit
EQUZ-INGRP
Characteristics
EQUZ-INGRP
EQUZ-IWERK
IMRG_CANCL
Reversal Indicator
Key Figures
 Measuring Position –
from “HSEC 00006”
to “HSEC 00012”
Calculations
3.18 Metric: Additional Metrics

Please refer to the Marketing Performance Report functional specification and/ or the corresponding ARIS metrics
catalogue for the detailed definition of the additional Work Management metrics listed below.
# Metrics Statistical Comments

Account
1 % Uniqueness Equipment WKM037
2 % Uniqueness Functional Location WKM038
3 % Uniqueness Maintenance Assembly WKM039
4 % Uniqueness Measuring Point WKM040
5 % Completeness Equipment WKM029
6 % Completeness Functional Location WKM030
7 % Completeness Maintenance Assembly WKM031
8 % Completeness Maintenance Item WKM032
9 % Completeness Measuring Point WKM033
10 % Completeness Task Lists WKM034
11 % Completeness Work Center WKM035

1SAP Release 3
12 % Completeness Work Plan WKM036
4 Business Test Conditions
No Test Condition Expected Result Verification Data Required

(Ref.:
TEST)
1 Validate Metrics Report – Numerator and Verify the All Metrics data
Metric Compliance to Work Denominator value in Numerator, required from the
Plan reconcile with Work the Metrics Report Denominator and Work Orders report BI
Orders BI Report. reconcile with the data Result values in the Report.
in the underlying BI Metrics Report
Report, and the Result against the Key
calculation/ aggregation Figures or Records
is correct. in the underlying BI
Report using
Selections and
Filters identified in
the Metrics F/Spec
Data Mapping
section.
Metric Adherence to Schedule Denominator value in Numerator, required from the
Done on the Day reconcile the Metrics Report Denominator and Work Order
with Work Order Scheduling reconcile with the data Result values in the Scheduling BI Report.
BI Report. in the underlying BI Metrics Report
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Planned & Scheduled Denominator value in Numerator, required from the
Work reconcile with Work the Metrics Report Denominator and Work Orders k BI
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Outstanding Work Denominator value in Numerator, required from the
Orders and Notification the Metrics Report Denominator and Work Orders report BI
reconcile with Work Orders reconcile with the data Result values in the Report.
and Notification BI Report. in the underlying BI Metrics Report
1SAP Release 3

Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Work Orders with Task Denominator value in Numerator, required from the
List reconcile with Work the Metrics Report Denominator and Notifications BI
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Adherence to Schedule Denominator value in Numerator, required from the
Finished within the Week the Metrics Report Denominator and Work Order
reconcile with Work Order reconcile with the data Result values in the Scheduling BI Report.
Scheduling BI Report. in the underlying BI Metrics Report
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Finished Work Orders Denominator value in Numerator, required from the
not Completed reconcile with the Metrics Report Denominator and Work Orders BI
Work Orders BI Report. reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Immediate/Urgent Denominator value in Numerator, required from the
Work Orders with Impact Data the Metrics Report Denominator and Work Orders BI
Entered reconcile with reconcile with the data Result values in the Report.
Notifications BI Report. in the underlying BI Metrics Report

1SAP Release 3

Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Overdue System Denominator value in Numerator, required from the
Generated Work Orders the Metrics Report Denominator and Work Orders BI
reconcile with Work Order BI reconcile with the data Result values in the Report.
Report. in the underlying BI Metrics Report
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Schedule Loading Denominator value in Numerator, required from the
reconcile with Work Order the Metrics Report Denominator and Work Orders BI
Scheduling BI Report. reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Cancelled System Denominator value in Numerator, required from the
Generated Work Orders the Metrics Report Denominator and Work Orders BI
reconcile with Work Order BI reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Fatalities reconcile with Denominator value in Numerator, required from the
Measurement Reading BI the Metrics Report Denominator and Work Orders BI
Report. reconcile with the data Result values in the Report.

1SAP Release 3

Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Total Recordable Injury Denominator value in Numerator, required from the
Frequency reconcile with the Metrics Report Denominator and Work Orders BI
Measurement Reading and reconcile with the data Result values in the Report.
Notification BI Report. in the underlying BI Metrics Report
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Occupational Illnesses Denominator value in Numerator, required from the
reconcile with Measurement the Metrics Report Denominator and Work Orders BI
Reading BI Report. reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric HSEC Significant Denominator value in Numerator, required from the
Events reconcile with the Metrics Report Denominator and Work Orders BI
Notification BI Report. reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Type 1 Water Input Denominator value in Numerator, required from the
Details reconcile with the Metrics Report Denominator and Work Orders BI
Measurement Reading BI reconcile with the data Result values in the Report.

1SAP Release 3
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
Metric Greenhouse Gas Denominator value in Numerator, required from the
Emissions reconcile with the Metrics Report Denominator and Work Orders BI
Measurement Reading BI reconcile with the data Result values in the Report.
Report using
Selections and
the Metrics F/Spec
Data Mapping
section.
5 Appendices
5.1 Glossary of Terms
Glossary of Terms
Terms Description
Work Management Metrics Report of Work Management Metrics, listing defined metrics for Work
Management and results.
HSEC Metrics Report of HSEC Metrics, listing defined metrics for HSEC and results.
Dimension Aggregation How data is calculated to the top level; for example, for a metric the value for
the entire organization is the sum of the values of the TMUs.
Time Aggregation Specify how e.g. monthly values are aggregated to quarterly values and
quarterly values are aggregated to yearly values for both actual and target
values.
Planning Plant A plant in which tasks are planned and prepared
Maintenance Plant A plant in which the technical objects of a company are installed.
Functional Location A Functional Location is a multi-level hierarchical structure organised
according to Functional, Process Related or Spatial criteria and are used to
capture Work Management History, Cost History and to facilitate Work
Management.
Planner Group Employee responsible for planning and processing Work Management tasks
in a plant.
Main Work Centre A Main Work Centre is assigned to a Supervisor who is responsible for
Resource Work Centres and responsible to maintain Technical Objects.
Resource / Operation Work Resource Work Centres are used for labour and machine resources.
Centre Resource Work Centres can be utilised for Planning and Scheduling or for
Time Confirmations only.
Capacity Managed Resource Capacity Managed Resource Work Centres are used for labour and machine
Work Centre resources. These Work Centres are used in Planning and Scheduling.
Task list An organisational unit that defines where a Work Order Operation must be
1SAP Release 3
performed.
Task list group Unique identifier for a task list.
Task list group counter A sub set of a task list Group. Is used to make a distinction between similar
task lists.
Revision A Revision is used for identifying work which has requirements to be
planned, scheduled and/or costed together.
Notification A Notification is used to convey work requirements, document technical
findings, and record activities performed.
Notification Types Notifications can be differentiated and grouped according to Notification
category, Notification origin and other criteria.
M1 Notification Notification for work identified
Notification Priority Notification Priority is used to convey the urgency requirements of the Work
activities. There are four Notification Priorities:
 Immediate - Commences within 24 hours from Notification creation.
 Urgent - Commences within 1-7 days from Notification creation.
 Planned - Commences more than 7 days from Notification creation.
Notification System Status SAP System sets internally as a part of general status management.
Notification User Status SAP System sets externally by a user as a part of general status
management.
Code Groups A group of Codes that are similar in content or related in some way are
combined into code groups for evaluation
Impact Type Predefined items on a maintainable item that has failed
Damage Predefined symptoms of the failure
Cause Predefined causes of the failure
Work Order A Work Order is the mechanism in the Work Management System to record
information, plan, schedule, and communicate the work requirements as well
as collect job costs. A work order is identified by a unique reference number.
Work Order Priority Planned Work Order Priorities are used to convey the scheduling
requirements of the work.
 Immediate - Work commences within 24 hours from Notification creation.

 Urgent - Work commences within 1-7 days from Notification creation.
Provides an opportunity to undertake some preparation for the Work
activity.
 Sched Day Defined - work must be scheduled on the day as defined
during planning
 Sched in Period - work must be scheduled within the scheduling period
 Sched Any Rem Cap - work may be scheduled at anytime during the
scheduling period where available capacity exists.
Basic Start Date Date when the work is planned to begin
Basic Finish Date Date when the work is planned to end
Work Order Creation Date Date that the CRTD (Created) System status was set on creating the Work
Order
Work Order Completion Date Date that the TECO status is set
(TECO)
Order Actual Start Date This is the date the job actually started on the Header. Set after the first
Confirmation on an operation.
Order Actual End Date Date that final confirmation is set.
Work Order Type Defines work purpose and allocation of security roles, number ranges and
specified routing etc.
1SAP Release 3
PM01 Work Order Standard SAP PM01 Work Order with planned planning indicator and
settlement only to cost centres.
PM02 Work Order Standard SAP PM02 System Generated Work Order with planned planning
indicator and settlement only to cost centres.
PM03 Work Order Standard SAP PM03 Work Order without the combination of Notification and
order on the header screen. Unplanned planning indicator and settlement
only to cost centres.
PM04 Work Order Standard SAP PM04 Refurbishment Order with settlement only to a material.
PM06 Work Order Standard SAP PM06 Capital Investment order with settlement only to a Work
breakdown structure (WBS) element.
Revision Type Identifying the revision type. E.g. Shutdown, Weekly Schedule etc.
Work Order Header System A processing status that is set by SAP as certain steps are done on the
Status Header level.
Work Order Header User Status A processing status that is set manually by the authorised user
Work Order Operation User A processing status that is set manually by the authorised user
Status
Control Key Determines which business transactions should be executed for the Work
Order (for example scheduling or costing).
Work Duration The total planned time for all individuals on an operation.
Schedule Freeze A specified day and time in every week where a list of work becomes the
base against which completed work is measured for Adherence to Schedule.
Time Confirmation Documents the processing status of Work Order Operations. A Time
Confirmation is used to determine at which work centre the Operation was
carried out, who performed the Operation and time taken.
Work Order Operation A detailed description of the various tasks to be carried out such as,
Operation work centre, job duration, Scope of work, responsible person etc.
Work Order Header The Work Order carries the common information relating to the operations
such as, Technical Object, settlement rules, Priority, Planner group, Main
Work Centre etc.
Safety Critical Element A Safety Critical Element is identified when a Critical Control or a specified
Local Regulation (including legal, regulatory, statutory or classified), that is
consistent with the Work Management GLD, is managed by an equipment
Performance Standard linked.
Notification‟s Cancelled Indicator Cancelled Notification of Notification Type M1 contains BW System Status as
NOCO (but not ORAS) and User Status as NEW. This notification should be
excluded from reports.
5.2 Glossary of Notification System Status
Terms Description
OSNO Notification System status indicating that the Notification has not been
processed
NOCO Notification System status indicating that the Notification has been completed
NOPR Notification System status indicating Notification in process.
ORAS Notification System status indicating that a Work Order has been assigned to
the Notification
5.3 Glossary of Notification User Status

1SAP Release 3
Terms Description
NEW Notification User Status on creation.
INF Notification User Status indicating an more information required (Scope) on
the Notification
MPT Notification User Status indicating that the Notification is generated from
Measuring Point
TLA Notification User Status indicating a Task List Attached to a Notification
APR Notification User Status indicating an Approved Notification
5.4 Glossary of Work Order Header System Status
Terms Description
CRTD Work Order Header System status indicating that the Work Order is created.
This is the default when created.
TECO Work Order Header System status indicating that the Work Order Technically
Completed. No further planned costs can be accrued.
CNF Work Order Header System status indicating that all of the Work Order
operations have been finally confirmed.
PCNF Work Order Header System status indicating that not all of the Work Order
operations have been finally confirmed.
CLSD Work Order Header System status indicating that the Work Order has been
completed and no further Actual costs can accrue.
REL Work Order Header System status indicating that the Work Order is
Released.
5.5 Glossary of Work Order User System Status
Terms Description
SCH Work Order Header User status indicating that the Work Order has
completed the Scheduling Phase of the process.
5.6 Glossary of Work Order Operation User System Status
Terms Description
SFC User Status SFC is set on all Work Order Operations for work on SCEs
which contribute to the achievement of the Performance Standard.
BSC User Status BSC is set on all Work Order Operations for work which reduces
the likelihood or consequence of Business Critical events and the work is not
Safety Critical.
5.7 Typographic Conventions
Type Style Description

[Example Text] Reference. (Use Hyperlink)
<Example Text> Placeholder.
<TODO> Not completed yet. To Do.
Example Text Important (mandatory) information.
1SAP Release 3
Example Text „How to Use‟ section. Remove before completing the document.
Table Error! No text of specified style in document.: Typographic Conventions.


R3 DD-PRO-090 WMT-M-59569 Work Management Metrics v5 0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R3 DD-PRO-090 WMT-M-59569 Work Management Metrics v5 0

Uploaded by

Copyright:

Available Formats

DD-PRO-090 WRICEFAMPS

<Process Team>: WMT Work Management <Dev Type>: R Report

Change History – Current Release

3. Add filter Event Notification on

CR83236 2. Add new Main Work Centre to

Date of Issue: 27/07/2012

4.0 May 2012 Tugrul Baysal Signed-off

Change History – Previous Release

Date of Issue: 27/07/2012

1 WRICEFAMP Information .................................................................................... 7

3.7 Metric : Finished Work Orders not Completed .....................................................25

3.15 Metric: HSEC Significant Events .....................................................................43

Date of Issue: 27/07/2012

Property Level Description

Complex Use of advanced „technologies‟. Complex algorithm. Complex / Sensitive

Simple Simple Enhancements.

1.1 Document References

Reference Description Link / Location

Table 1.1-1: Document references.

Date of Issue: 27/07/2012

List of Non HSEC Specific Metrics

- Compliance to Work Plan

List of HSEC Specific Metrics

Interval and Shift Capacity, which reflects the following mechanism:

 All data will be sourced from ECC.

Date of Issue: 27/07/2012

3.1 Metric: Compliance to Work Plan

Technical Name WKM009

3.1.2 Calculation Details

Formula (Number of finished system generated Work Orders in period within

3.1.3 Data Source

3.1.4 Metric specific Notes / constraints / assumptions

3.1.5 Metric Technical Details

Date of Issue: 27/07/2012

Work Order Header System AUFK - OBJNR -> RPM_ORDER__R

Date of Issue: 27/07/2012

Finished PM02 Work Orders Count of Work Count of Work Orders

Denominator N/A RDEM_U Sum of Finished PM02 Work Orders

Metric - Result N/A N/A (Sum of Finished PM02 Work

3.2 Metric: Adherence to Schedule Done on the Day

Technical Name WKM003

3.2.2 Calculation Details

3.2.3 Data Source

3.2.4 Metric specific Notes / constraints / assumptions

Date of Issue: 27/07/2012

3.2.5 Metric Technical Details

Date of Issue: 27/07/2012

3.3 Metric: Planned & Scheduled Work

Technical Name WKM021

3.3.2 Calculation Details

3.3.3 Data Source

3.3.4 Metric specific Notes / constraints / assumptions

3.3.5 Metric Technical Details

Work Order Header System AUFK - OBJNR -> RPM_ORDER__R

Date of Issue: 27/07/2012

Denominator N/A RDEM_U Sum of Work Order Hours

3.4 Metric : Adherence to Schedule Finished within the Week

Technical Name WKM005

3.4.2 Calculation Details

Formula (Number of finished Scheduled Work Orders in period / Number of

3.4.3 Data Source

3.4.4 Metric specific Notes / constraints / assumptions

3.4.5 Illustrative Example

Date of Issue: 27/07/2012