Professional Documents
Culture Documents
Jim McCaherty
Mining Forum - Peoria
September 23 - 28, 2007
Why do we measure?
Management without metrics is “management” by intuition.
2
Why do we measure?
ANSWER: Metrics help us make sense of our
situation; we become smarter and gain
some degree of control over the outcome.
OBSERVATION
Mining equipment management
spends more time reporting
performance than improving
performance.
3
*
* Only the latter two provide information that directly helps to improve the operation.
4
Objective
Define a process using data that is commonly
available at most sites to develop quantifiable
measures to assess site performance and
identify weak areas, poor practices and other
opportunities for improvement. Use the
process as a “Management Tool” to prioritize
and attack the key issues affecting
performance.
5
Why use Performance Metrics?
• ____________
To assign and fix blame.
• etc.
6
PHILOSOPHY
Apply what you know to what you would like
to know!
7
What would you like to know?
… from a Maintenance perspective
Application
% A/F Design
Repairs Quality Pit Depth
Haul Distance
Grades
…
Parts Application
Reuse
Maintenance Operation
Parts
Op Skill
Price Repair Quality P’Load
Mgmt.
Bunching
others Delays
Blasting
…
8
*
Availability:
Used to measure performance and contributions of
Equipment Management team in support of the
mine’s production goals.
If my performance is substandard,
• Why?
• What can I do to improve it?
9
Availability:
Variations (general forms):
Total Calendar Hours – all Downtime Hours
Physical Availability =
Total Calendar Hours
10
Availability:
Variations (general forms):
Scheduled Hours – all Downtime Hours
Physical Availability =
Scheduled Hours
12
Identify Key Performance Indicators &
Establish Benchmarks:
Repair Frequency .… MTBS (Mean Time Between Shutdowns)
machine reliability
repair quality / maintenance effectiveness
Benchmark = 60 to 80 hours
13
MTBS (Mean Time Between Shutdowns)
Operating Hours
MTBS (hours) =
number of shutdowns in the period
14
Identify Key Performance Indicators &
Establish Benchmarks:
Repair Frequency .… MTBS (Mean Time Between Shutdowns)
machine reliability
repair quality / maintenance effectiveness
Benchmark = 60 to 80 hours
Repair Duration .….. MTTR (Mean Time To Repair)
machine serviceability
repair timeliness / maintenance efficiency
Benchmark = 3 to 6 hours
15
MTTR (Mean Time To Repair)
16
Identify Key Performance Indicators &
Establish Benchmarks:
Repair Frequency .… MTBS (Mean Time Between Shutdowns)
machine reliability
repair quality / maintenance effectiveness
Benchmark = 60 to 80 hours
Repair Duration .….. MTTR (Mean Time To Repair)
machine serviceability
repair timeliness / maintenance efficiency
Benchmark = 3 to 6 hours
Utilization ………… Operated Hours / Available Hours
Results are determined by Operations
NOT Maintenance
17
Availability:
Operating Hours + Stand-By Hours
Availability general form =
Operating Hours + Stand-By Hours + Downtime Hours
Operating Hours
Availability Index =
Operating Hours + Downtime Hours
18
Identify Key Performance Indicators &
Establish Benchmarks:
Reliability &
Repair Effectiveness
MTBS
Availability Index =
MTBS + MTTR
Serviceability &
Repair Efficiency
90%
80%
Availability Index - (%)
70%
Why MTBS?
60%
50%
40%
30%
20%
10%
0%
0 25 50 75 100 125 150 175 200
MTBS - (hours)
MTTR = 3 hrs MTTR = 4.5 hrs MTTR = 6 hrs MTTR = 7.5 hrs MTTR = 9 hrs MTTR = 12 hrs
20
Maintenance & Repair Management Scenario
First PCR Equipment
cycle Disposal
PCR * X
• Vital to minimize / • Who’s in Control? • Fixed frequency • A planning window to • Frequency determined
Downtime Major prevent unscheduled keep condition of the by component life targets
Characteristics stops • Must be minimized • Well known routine machine at defined level & health
• Frequency; a function • Negative influence on • The foundation of • Frequency determined • Window used for
of MTBS MTBS, MTTR & efficient / effective by Planning restoring machine to
Availability maintenance mgmt. standard
21
Maintenance & Repair Management Scenario
PCR * X
…
Downtime Reasons Unscheduled PCR
Detection Routines Periodic Services Scheduled Repairs Planned Component
Repairs
(Major & Minor) Replacement
Performance Evaluation
Evaluation
Continuous Improvement
Correct / Improve
22
Why MTBS? First PCR
cycle
Equipment
Disposal
PCR * X
…
PCR
Downtime Reasons Detection Unscheduled Periodic Scheduled Repairs (Planned
Routines Repairs Services (Major & Minor) Component
Replacement)
MTBF:
Considers only Failures … Unscheduled Repairs (reliability element).
MTBnF:
Considers non-Failures … quantifies our efforts in Failure avoidance
(influence reliability).
24
What do we know ?
Start Complete
CompleteRepair
Repair Repair
Labor Stop
Stop Scheduled
Equipment ID
Start Number
Repair
Equipment ID Number Labor Man-
Stop Man-
Code Service Meter Scheduled
StopHoursCode Reason Service
Comments Meter
(Date & (Date
Time)
(Date&&Time)
Time)
DurationHours Reason Comments Reading
(Date & Time) Duration Field
ReadingField/ /Shop
Shop
Yes
F
F
S
S
No
No
No
No
HT001 4/14/03 10:54 PM 4/14/03 11:01 PM 0.12 0.00 162 Delays Waiting for Mechanic 16436.4 S No
HT001 4/14/03 11:01 PM 4/15/03 2:22 AM 3.34 3.34 100 Engine Low engine power 16436.4 Yes S No
HT001
HT001
HT001
HT001
4/15/03 2:55 AM
4/15/03 3:23 AM
4/15/03 4:48 AM
4/15/03 4:57 AM
Availability Target = 88%
4/15/03 3:23 AM
4/15/03 4:11 AM
4/15/03 4:57 AM
4/15/03 5:57 AM
0.48
0.79
0.16
0.99
0.00
0.79
0.00
0.99
162
100
162
100
Delays
Engine
Delays
Air Intake & Exhaust System
Waiting for Mechanic
Engine derate 30
Waiting for Mechanic
Air cleaner plugged
16437.0
16437.0
16437.6
16437.6
Yes
Yes
F
F
F
F
No
No
No
No
HT001 4/15/03 7:35 AM 4/15/03 8:05 AM 0.51 0.51 120 Tires & Rims Tire Check - Pos. #3 16439.1 Yes F No
HT001 4/16/03 12:51 PM 4/16/03 12:56 PM 0.08 0.00 162 Delays Waiting for Mechanic 16467.2 F No
HT001 4/16/03 12:56 PM 4/16/03 1:25 PM 0.48 0.48 100 Engine Low engine oil level 16467.2 Yes F No
HT001 4/17/03 2:13 AM 4/17/03 2:22 AM 0.14 0.00 162 Delays Waiting for Mechanic 16479.7 S No
HT001 4/17/03 2:22 AM 4/17/03 9:29 AM 7.12 7.12 100 Engine Engine derate 31 16479.7 Yes S No
HT001 4/17/03 9:43 AM 4/17/03 9:58 AM 0.25 0.00 162 Delays Waiting for Mechanic 16479.9 S No
HT001 4/17/03 9:58 AM 4/17/03 1:09 PM 3.19 3.19 100 Engine Engine derate 31 16479.9 Yes S No
25
The process - STEP 1:
Evaluate Overall Fleet Performance
Equip. Start Repair Complete Repair Stop Labor Shop /
Code Reason Comments SMR Stop Scheduled
ID (Date / Time) (Date / Time) Duration Manhours Field?
HT001 4/1/03 12:00 AM 4/1/03 12:00 AM 0.00 0.00 1 comment Document SMR 16214.4 N/A N/A
HT001 4/3/03 7:06 PM 4/3/03 7:33 PM 0.44 0.00 162 Delays Waiting for Mechanic 16279.8 S No
HT001 4/3/03 7:33 PM 4/5/03 7:21 AM 35.80 35.80 100 Engine Low engine power 16279.8 S No
HT001 4/5/03 7:21 AM 4/6/03 9:25 PM 38.07 76.14 111 Cooling System Replace aftercooler gasket 16279.8 Yes S No
HT001 4/7/03 9:29 AM 4/7/03 11:10 PM 13.67 41.00 202 PM 2000 Hr PM 16291.6 Yes S Yes
HT001 4/8/03 4:42 PM 4/8/03 6:02 PM 1.35 4.00 120 Tires & Rims Replace tire - position #3 16308.7 Yes S No
HT001 4/9/03 1:41 AM 4/9/03 1:52 AM 0.18 0.00 162 Delays Waiting for Mechanic 16316.2 S No
HT001 4/9/03 1:52 AM 4/9/03 2:17 AM 0.41 0.41 118 Suspension System L/F Suspension Noise 16316.2 S No
HT001 4/9/03 2:17 AM 4/9/03 6:24 AM 4.11 12.33 120 Tires & Rims Replace tire - positions #1 & 2 16316.2 Yes S No
HT001 4/9/03 8:48 PM 4/9/03 9:00 PM 0.20 0.00 162 Delays Waiting for Mechanic 16330.2 S No
HT001 4/9/03 9:00 PM 4/10/03 3:16 AM 6.27 6.27 100 Engine Low boost pressure 16330.2 Yes S No
HT001 4/10/03 5:02 AM 4/10/03 5:07 AM 0.08 0.00 162 Delays Waiting for Mechanic 16331.9 F No
HT001 4/10/03 5:07 AM 4/10/03 5:31 AM 0.40 0.40 128 Cab / Operator Station Repair L/H Door Lock 16331.9 Yes F No
HT001 4/10/03 6:21 AM 4/10/03 6:26 AM 0.08 0.00 162 Delays Waiting for Mechanic 16332.8 F No
HT001 4/10/03 6:26 AM 4/10/03 6:42 AM 0.27 0.27 128 Cab / Operator Station Repair L/H Door Lock 16332.8 Yes F No
HT001 4/14/03 3:28 PM 4/14/03 3:39 PM 0.19 0.00 162 Delays Waiting for Mechanic 16434.8 S No
HT001 4/14/03 3:39 PM 4/14/03 9:21 PM 5.69 5.69 100 Engine Engine oil leaks / Low boost pressure 16434.8 Yes S No
HT001 4/14/03 10:54 PM 4/14/03 11:01 PM 0.12 0.00 162 Delays Waiting for Mechanic 16436.4 S No
HT001 4/14/03 11:01 PM 4/15/03 2:22 AM 3.34 3.34 100 Engine Low engine power 16436.4 Yes S No
HT001 4/15/03 2:55 AM 4/15/03 3:23 AM 0.48 0.00 162 Delays Waiting for Mechanic 16437.0 F No
HT001 4/15/03 3:23 AM 4/15/03 4:11 AM 0.79 0.79 100 Engine Engine derate 30 16437.0 Yes F No
HT001 4/15/03 4:48 AM 4/15/03 4:57 AM 0.16 0.00 162 Delays Waiting for Mechanic 16437.6 F No
HT001 4/15/03 4:57 AM 4/15/03 5:57 AM 0.99 0.99 100 Air Intake & Exhaust System Air cleaner plugged 16437.6 Yes F No
HT001 4/15/03 7:35 AM 4/15/03 8:05 AM 0.51 0.51 120 Tires & Rims Tire Check - Pos. #3 16439.1 Yes F No
HT001 4/16/03 12:51 PM 4/16/03 12:56 PM 0.08 0.00 162 Delays Waiting for Mechanic 16467.2 F No
HT001 4/16/03 12:56 PM 4/16/03 1:25 PM 0.48 0.48 100 Engine Low engine oil level 16467.2 Yes F No
HT001 4/17/03 2:13 AM 4/17/03 2:22 AM 0.14 0.00 162 Delays Waiting for Mechanic 16479.7 S No
HT001 4/17/03 2:22 AM 4/17/03 9:29 AM 7.12 7.12 100 Engine Engine derate 31 16479.7 Yes S No
HT001 4/17/03 9:43 AM 4/17/03 9:58 AM 0.25 0.00 162 Delays Waiting for Mechanic 16479.9 S No
HT001 4/17/03 9:58 AM 4/17/03 1:09 PM 3.19 3.19 100 Engine Engine derate 31 16479.9 Yes S No
26
MTBS What do we need?
27
MTBS
Operating Hours
MTBS (hours) =
number of shutdowns in the period
3415.77
MTBS (hours) = = 20.70 hours
165
28
MTTR What do we need?
29
MTTR
Downtime Hours
MTTR (hours) =
number of shutdowns in the period
838.60
MTTR (hours) = = 5.08 hours
165
30
Availability Index
MTBS
Availability Index =
MTBS + MTTR
20.70
Availability Index = = 80.29%
20.70 + 5.08
31
*
Analysis:
STEP 2:
Analyze Overall Fleet Performance
32
*
Interpretation:
33
Identify Key Performance Indicators &
Establish Benchmarks:
% Scheduled Downtime .…
Defines the extent that Equipment
Management is in control of
the situation vs. reacting to it.
Effectiveness of the Equipment
Management system.
Benchmark = 80% of all DT is
planned & scheduled.
34
% Scheduled What do we need?
35
% Scheduled
168.10
% Scheduled Downtime = = 20.05%
838.60
STEP 3:
Develop an Action Plan
36
Recommendations / Action Plan:
37
STEP 4:
Evaluate Individual Machine
Performance
38
*
Analysis / Interpretation:
39
Recommendations / Action Plan:
40
Pareto Analysis – HT002
41
Pareto Analysis – HT002
42
43
44
STEP 5:
Analyze Truck HT002 Performance
45
Analysis / Interpretation:
Chronic (repetitive) repairs performed on truck
HT002 due to engine and electrical system.
Incorrect problem diagnosis and/or poor repair
execution (“redo”) are leading to excessive
number of repetitive problems.
NOTE: 85.5% of downtime & 77.8% of shutdowns
on truck HT002 are due to engine and electrical
system.
Eliminating “redo” on HT002 will increase fleet MTBS
by 41% and reduce fleet downtime (increase
STEP 6:
availability) by 31%.
STEP 7:
Evaluate Component / System
Performance
47
Identify Key Performance Indicators &
Establish Benchmarks:
Top Problem Summary .…
Enables Equipment Management
to identify the most significant issues
and focus its resources on their
containment & resolution.
“Rule of Thumb”: Apply Pareto
analysis; information must be
quantified and compared against
historical performance and / or
established references.
Target: All downtime is documented by
cause and in terms of frequency,
duration and cost of each repair.
48
Top Problem Summary
49
Top Problem Summary
50
Top Problem Summary
To Calculate Impact on Availability:
Total Downtime
= Total Downtime
(system / component)
X (1 - Availability Index)
(all causes)
EXAMPLE:
Total Downtime
= Total Downtime
(Engine)
X (1 - Availability Index)
(all causes)
268.97 hours
= 838.60 hours
X (1 -.8029)
51
Top Problem Summary
STEP 8:
Analyze Component / System
Performance
52
Top Problem Summary
53
Top Problem Summary
Opportunity to Improve:
EXAMPLE:
54
Analysis / Interpretation:
• Pareto applies … Top four issues (20%) account for 73.5% of all
downtime (14.5% lost availability).
• Opportunity to improve > 12%.
55
Analysis / Interpretation:
56
Analysis / Interpretation:
58
Observations / Recommendations (general):
• Highly utilized fleet performing poorly.
• Maintenance organization is extremely reactive; operation is out of
control.
• Percentage of scheduled downtime is very low (20% by hours /
4.2% by event.
• PM and Condition Monitoring functions are substandard.
• Information management is ineffective … not learning from failures.
• Invest in efforts to put management in control of the operation.
• Reinforce / emphasize PM & Condition Monitoring practices.
• Learn from failures … “Past performance is frequently a valid
predictor of future behavior” !
59
Which method is your organization using?
60
Using Data to Drive Decisions
Questions? /
Comments?
Key Points / “Take-Aways”
• Understand the “big picture” & what is driving the end results …
“Drill Down” into issues by fleet / individual machine /
systems,
62
Using Data to Drive Decisions
END