48
Ryan Kay

Reporting Case Studies

  • Upload
    emaint

  • View
    288

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Reporting Case Studies

Ryan Kay

Page 2: Reporting Case Studies

Gathering the criteria for your Output requirements will always drive better input

Page 3: Reporting Case Studies

Most are accomplishable by the user

Some require partnership with Support

Page 4: Reporting Case Studies

Facility Management

Joined us in 2006 with 10 locations worldwide

Previously used home-grown program

Page 5: Reporting Case Studies

“Metrics Report” – Gives the ability to track time spent on Facility requests in the following ways:

Time it took to complete the work assigned

Time it took to respond to the requests

Time it took from the point of entry to the last minute someone worked on the issue

Total hours spent on the job

Page 6: Reporting Case Studies

Addition of fields to Work Order

◦ Response Time

◦ Job Time

◦ Job Duration

◦ Time to Complete

Page 7: Reporting Case Studies

Addition of fields to Work Order

◦ Response Time

◦ Job Time

◦ Job Duration

◦ Time to Complete

Page 8: Reporting Case Studies

◦ Response Time: First Labor Charge Start Date/Time – Work Order

Date/Time

◦ Job Time: Total of the Work Order Labor Charges

◦ Job Duration: Last Labor Charge Stop Date/Time – Work Order Date/Time

◦ Time to Complete: Last Labor Charge Stop Date/Time – Work Order Date/Time

Page 9: Reporting Case Studies
Page 10: Reporting Case Studies
Page 11: Reporting Case Studies

The FoxPro Report Builder

◦ Helps us develop complex report forms to compliment the Query Builder

Page 12: Reporting Case Studies

A data input process that supports the desired & required output

An easy to use report that displays up-to-the-minute Metrics on their work orders

Page 13: Reporting Case Studies

Manufacturing Facility

Joined us with one location in 2006 as an Enterprise client

Previously used home-grown system designed in 1975

Page 14: Reporting Case Studies

Downtime by Division ◦ Downtime categorized by division, or area

Mean Time Between Failures◦ Mean Time between each failure work order

Time to Complete◦ Total and average times to complete work orders

Page 15: Reporting Case Studies
Page 16: Reporting Case Studies

Addition of Fields to the Work Order

◦ Machine Status

◦ Unscheduled Downtime

◦ Scheduled Downtime

◦ Machine Back Up

Page 17: Reporting Case Studies

Addition of Fields to the Work Order

◦ Unscheduled Downtime

◦ Scheduled Downtime

◦ Machine Back Up

Page 18: Reporting Case Studies

Addition of Fields to the Work Order

◦ Unscheduled Downtime Populates only if the Machine Status is “Down”

◦ Scheduled Downtime Entered by hand on work orders where the status was

“Running” or “Not Applicable”

◦ Machine Back Up The date/time the machine returned to service, entered by

hand on closeout. Used only when the machine status is “Down”

Page 19: Reporting Case Studies
Page 20: Reporting Case Studies
Page 21: Reporting Case Studies
Page 22: Reporting Case Studies

No additional account or form configuration required◦ Uses fields already established in X3 for collecting

data on:

Work Order Date and Time Machine Status

Page 23: Reporting Case Studies
Page 24: Reporting Case Studies
Page 25: Reporting Case Studies
Page 26: Reporting Case Studies

Addition of Fields to the Work Order

◦ Job Time

◦ Time to Complete

Page 27: Reporting Case Studies
Page 28: Reporting Case Studies

Addition of Fields to the Work Order

◦ Job Time Calculates the total time between the first charge

start time and the last labor charge stop time

◦ Time to Complete Calculates the time between the last labor charge

stop time and the work order date/time

Page 29: Reporting Case Studies
Page 30: Reporting Case Studies
Page 31: Reporting Case Studies

On-demand statistics of machine performance

On-demand statistics of staff hours perfomance

Page 32: Reporting Case Studies

Chevron and eMaint partnered to deliver “Computex MMS,” a branded and configured version of X3 specific to lubrication management for Chevron’s industrial clients

Page 33: Reporting Case Studies

Route Schedule report◦ Ability to print the scheduled work route (PM’s) for a

technician during the specified timeframe based on Route Route Sequence

◦ Schedule must show details about the lubrications needed for the job Lube Points Lube Method Product Needed

◦ Must use existing schedule report from old system

Page 34: Reporting Case Studies

Addition of fields to Work Order

◦ Route Number

◦ Route Sequence

◦ Lube Points

Page 35: Reporting Case Studies
Page 36: Reporting Case Studies
Page 37: Reporting Case Studies
Page 38: Reporting Case Studies

An easy to read schedule sheet for technicians to use with no need to re-learn a new form

A great compliment to the PM process

Page 39: Reporting Case Studies

Facility Management, outdoor performing arts center

Joined us in 2007

No previous maintenance program

Page 40: Reporting Case Studies

Preventive Work Orders performance

◦ Needed to see the open PM work orders that are late based on allowed completion time

Page 41: Reporting Case Studies

Addition of fields to PM Schedule

◦ Number of Days to Complete

Addition of fields to the Work Order

◦ Number of Days to Complete

Page 42: Reporting Case Studies
Page 43: Reporting Case Studies

Addition of fields to PM Schedule & Work Order

◦ Values from the PM populate the work order automatically

Page 44: Reporting Case Studies
Page 45: Reporting Case Studies
Page 46: Reporting Case Studies
Page 47: Reporting Case Studies

A performance report that allows Bethel Woods to monitor outstanding PMs

A report that is now publishable to the Dashboard

Page 48: Reporting Case Studies