benchmarking in m5 - trapeze groupgo.volarisgroup.com/rs/volarisgroup/images/aw_fleetfocusm5... ·...

Proprietary and Confidential. Copyright © 2012 AssetWorks Inc. All rights reserved.

Objective

To help fleets use M5 data to measure performance against industry benchmarks.

Fleet Management Software2


Assumptions and DefinitionsBenchmarks are derived from several sources but are primarily based on a benchmarking study performed for Siskiyou County by Quality Fleet Management Company.PMM– Performance Metrics and Measures. An M5 optional module that allows for the analysis of

data trends.

Dashboard. Real-time (nearly) reporting based on triggers designed to inform an Application User when something needs their attention.– OPM

• Operational Performance Monitors. Dashboards provided by AssetWorks.

– KPI• Key Performance Indicator. Dashboard written by customers.

Standard Reports. Out-of-the-Box reports written in Crystal.Adhoc Report. An M5 optional module that allows customers to create their own reports. These reports are based on Views that present field names in a user-friendly way and where table joins have already been made.All SQL in this presentation are for Oracle.Data on the following slides comes from a “stale” demo database.



Benchmarks


Benchmark Title BenchmarkDirect vs. Indirect Labor 70%

Repeat Repairs 3%

Warranty Recovery Rate 90%

Repair Before Failure Rate 70%

PM vs. Repair Percentage 40%

Percent On-Time PMs 90%

Turnaround Time 90% in 48 hrs

Inventory Turns 4 Turns

Usage Reporting 100%

Utilization Percentage 70%


Direct vs. Indirect Labor

The percent of time a technician spends charging time to a work orders versus indirect time (Indirect labor includes tasks such as training and shop clean-up) charged to overhead tasks.

Repair facilities should strive for a direct versus indirect labor ratio of 70%.



Direct vs. Indirect Labor

OPM Dashboard– OPM LABOR

KPI Dashboard– Direct Labor

PMM– Direct Labor %

Standard Report– Location Labor Productivity

Standard Report– Labor Indirect Journal



OPM Dashboard



KPI Dashboard


select

round(sum(case when chg_type = 'D'

then duration end) /

sum(duration),2) as "Direct Hours"

from view_emp_labor_jnl

where location = ':<LOCATION>'

and duration != 0

and substr(fisc_pd, 1, 4) =

(select substr(fisc_pd, 1, 4)

from calendar_days

where cal_date = trunc(sysdate))


PMM

Direct Labor %



Standard Report



Benchmarks



Repeat Repairs 3%










Repeat Repairs

Repeat Repairs are often referred to as Comebacks or Rework. They are repairs that must be performed a second time to fix a previous problem.

Fleets should strive for fewer than 3% Repeat Repairs.

Repeat Repair parameters are setup in the Repeat Repairs screen.

Don’t forget the Repeat Work batch process.



Repeat Repairs

KPI Dashboard

– In-House Repeat Repair %

KPI Dashboard

– Repeat Jobs by Location-30 Days Back



KPI Dashboard

In-House Repeat Repair %


select (no_exceptions / repeat_jobs) * 100.00 as

Percent_Possible_Repeat_Work

from view_kpi_repeat_job_count

where location = ':<LOCATION>'

and total_jobs > 0


KPI Dashboard

Repeat Jobs by Location-30 Days Back


select u.unit_no, j.job, j.open_dt, j.wo_no,

j.repeat_fl, n.note

from o_wo o, unit_dept_comp_main u,

o_job j, notes n

where o.company = j.company

and o.company = u.company

and j.note_id = n.note_id

and o.location = ':<LOCATION>'

and j.repeat_fl = 'Y'

and o.unit_id = u.unit_id

and o.wo_no = j.wo_no

and o.open_dt between trunc(sysdate) -

30 and trunc(sysdate)

order by 1, 2, 3

Date variable can

be altered in the

SQL statement or

can be added as a

configurable

variable like

‘:<LOCATION>’


Benchmarks



Repeat Repairs 3%










Warranty Recovery Rate

Fleets perform warranty work for a myriad of reasons. It is often too expensive and too time consuming to take a vehicle to a dealer for warranty work to be performed.

Fleets should strive for a recovery rate of 90% on the warranty work that they perform.



Warranty Recovery Rate

PMM

– WARR_COST_MAINT_COST

KPI Dashboard

– Warranty Violations with or without Claims

Standard Report

– WO Warranty Job Cost

Standard Report

– Work Order Warranty Violations



PMM

WARR_COST_MAINT_COST



KPI Dashboard

Warranty Violations with or without Claims


select u.unit_no, o.wo_no, w.claim_no, j.open_dt, j.job,

coalesce(sum(j.act_comm_cost_do+j.act_labor_cost_do+j.act_part_cost_do),0), z.amount_cost_do,

v.description,

decode(j.warranty_violation_fl,

'P', 'Part',

'S', 'System',

'C', 'Component',

'W', 'Whole Unit',

'J', 'Job Reason',

'Other') as "Violation"

from o_wo o, o_job j, job_visit_reason v, unit_main u. warr_claim w, warr_claim_detail z

where o.unit_id = u.unit_id

and u.unit_id = w.unit_id

and o.wo_no = j.wo_no

and j.wo_no = w.wo_no

and j.job_reason = v.job_reason

and j.job_id = z.job_id

and o.status != 'X'

and j.warranty_violation_fl != 'N'

and j.open_dt between trunc(sysdate) - 30 and trunc(sysdate)

and o.location like ':<LOCATION>'

order by 1, 2, 3


Standard Report

WO Warranty Job Cost



Standard Report

Work Order Warranty Violations



Benchmarks



Repeat Repairs 3%










Repair Before Failure Rate

In M5, a breakdown is defined as any repair with a Work Order Reason identified as a Breakdown.

In M5, a road call is defined as any Job Reason where the Road Call checkbox is checked.

The industry Repair Before Failure Rate benchmark is 70%.



Repair Before Failure Rate

PMM– Count of Road Call Jobs for this Maintenance Location

KPI Dashboard– Breakdowns in the last 30 Days

Standard Reports– Unit Job Cost History– Unit Job Reason History– Unit Job Reason Summary– Work Order Job Cost History– Work Order Job Reason History– Work Order Repair Reason– Export Labor Charges



PMM

Count of Road Call Jobs for this Maintenance Location



KPI Dashboard

Breakdowns in the last 30 days


select u.unit_no, o.wo_no, o.open_dt,

v.description

from o_wo o, visit_reason v, unit_main u

where o.visit_reason = v.visit_reason

and o.company = v.company



and v.breakdown_fl = 'Y'

and o.open_dt between trunc(sysdate) -

30 and trunc(sysdate)

and o.location = ':<LOCATION>'

and o.status != 'X'

order by 1, 3, 2


Standard Reports

Unit Job Cost History

Unit Job Reason History

Unit Job Reason Summary

Work Order Job Cost History

Work Order Job Reason History

Work Order Repair Reason

Export Labor Charges



Benchmarks



Repeat Repairs 3%










PM vs. Repair Percentage

PM hours as a percentage of total maintenance hours.

Job Reason must be Maintenance and Preventive.

The percentage of PMs to repair orders should be more than 40%.



PM vs. Repair Percentage

OPM Dashboard

– Preventive Maintenance

KPI Dashboard

– PM Hours as a % of Total Direct Hours

Standard Report

– Labor Job Analysis



OPM Dashboard

Preventive Maintenance



KPI Dashboard

PM Hours as a % of Total Direct Hours


select round((sum(decode(v.mnt_preventive_fl, 'Y', c.duration, 0)) /

sum(c.duration)) * 100.0,2) as "Percent PM"

from o_labor_chg c, o_job j, job_visit_reason v, o_wo o, unit_dept_comp_main

u

where c.company = j.company

and j.company = v.company

and j.company = o.company



and c.job_id = j.job_id

and c.wo_no = j.wo_no

and j.wo_no = o.wo_no

and c.end_time between trunc(sysdate - 30) and trunc(sysdate)

and j.location = ':<LOCATION>'

having sum(c.duration) > 0


Standard Report

Labor Job Analysis



Benchmarks



Repeat Repairs 3%










Percent of On-Time PMs

Percent of jobs performed between M5's Earliest Date and Latest Date.

At least 90% of a fleet's PM inspections should be performed on time.



Percent of On-Time PMs

PMM

– PM Completed – Avg Days Late

– PM Completed On Time %

Standard Report

– Department PM Summary



PMM

PM Completed – Avg Days Late



PMM



Standard Report

Department PM Summary



Benchmarks



Repeat Repairs 3%










Turnaround Time

The number of clock hours between Work Order Open and Work Order Complete.

At least 90% of the equipment that enters a shop for repair should be returned within 48 hours.



Turnaround Time

Dashboard

– Turnaround Time


SELECT CASE

WHEN trunc(completed_dt) = trunc(open_dt) THEN 'A) Same Day'

WHEN trunc(completed_dt) = trunc(open_dt) + 1 THEN 'B) 1 Day Turnaround'

WHEN trunc(completed_dt) = trunc(open_dt) + 2 THEN 'C) 2 Day Turnaround'

WHEN trunc(completed_dt) = trunc(open_dt) + 3 THEN 'D) 3 Day Turnaround'

WHEN trunc(completed_dt) > trunc(open_dt) + 3 THEN 'E) 4 or More Days Turnaround'

ELSE 'Other'

END AS Turnaround,

wo_no,

JOB,

location,

due_date,

open_dt,

completed_dt,

round(completed_dt - open_dt, 1) as Days_to_complete

FROM o_job

WHERE status = 'DON' AND

completed_dt - open_dt >= 0 AND

LOCATION = ':<Location>' AND

completed_dt >= add_months(SYSDATE, - to_number(':<Enter Months Back from Today (Ex: 12 is a year ago)>'))

ORDER BY 1, 8


Turnaround Time



Benchmarks



Repeat Repairs 3%










Inventory Turns

The number of times the current on-hand quantity of stock parts gets issued every year.

Stock inventory should turn at least 4 times per year.



Inventory Turns

Adhoc Report

KPI Dashboard

– Inventory Turns



Adhoc Report



KPI Dashboard

Inventory Turns


SELECT part_no, description,

qty_on_hand, qtd_issued, to_ratio,

min_level, max_level

from view_parts_part_inv_loc

where ACTIVE_FL = 'Y'

AND NI_NS_FL IS NULL

AND LOCATION = ':<Location>'

AND TO_RATIO < 4

AND MIN_LEVEL > 0

ORDER BY 2


Benchmarks



Repeat Repairs 3%










Usage Reporting

The collection of meter readings over a span of time.

Usage should be reported for 100% of metered fleet equipment on a monthly basis.



Usage Reporting

KPI Dashboard

– No Meter Readings


select maint_loc, unit_no, meter,

ltd_usage, meter_date, round(sysdate

- meter_date,2) as days_since

from unit_dept_comp_main

where sysdate - meter_date >

:<DAYS_BACK>

and maint_loc in (select location from

loc_group_locations where loc_group

= ':<LOC_GROUP>')

AND STATUS IN ('A', ‘D')

and meter_date is not null

and meter is not null

and unit_type = 'U'

ORDER BY 1, 2


Benchmarks



Repeat Repairs 3%










Utilization Percentage

The percent utilization of equipment compared to the expected use (could be annual or monthly) of that equipment.

Measuring utilization against a standard can either be set at the Activity Code or at the Maintenance Class Code.

Fleet units should achieve at least 70% of expected utilization.



Utilization Percentage

KPI Dashboard

– Low Use Units

Standard Report

– Unit Utilization and Cost Summary



KPI Dashboard


select u.using_dept, u.unit_no, round

(u.avg_usage1, 2) as AVG_MOS_USE,

v.act_code, round (a.annual_avg_use / 12,

2) as EXP_MOS_USE

from view_meterstats u,

unit_dept_comp_main v, activity a

where u.unit_id = v.unit_id

and v.act_code = a.act_code

order by 1, 2


Standard Report




[email protected]

Questions?

benchmarking in m5 - trapeze groupgo.volarisgroup.com/rs/volarisgroup/images/aw_fleetfocusm5... ·...

Documents