PM Estimated Hours

Comments

10 comments

  • Nadarajan, Ananthan

    This PM estimated hours is important to track real PM hours vs hours taken to complete. 

    0
    Comment actions Permalink
  • Kevin Bryan

    I believe this would be a great feature for those wanting to truly manage PM time (true time) and resources. As time constraints for machine access increases this info would be extremely valuable for maintenance to coordinated with their customers accurate PM requirements. This running average could be dynamically adjusted over time to determine true PM man hours based on time (man hours) logged into a PM dispatch.

    0
    Comment actions Permalink
  • CJohnson

    Where do the "real PM hours" originate from?  It is easy to say this job should take 4 hours and if these machines are all the same, then all of them will take 4 hours.  But after performing the job, you realize one machine could take 6 hours because there may be extra guarding to take off, or the location is difficult to get in to.  These are things I hope to find, whether something can be done to make the PM more efficient and reduce the needed time, or just realize that this machine will indeed take 2 hours longer. 

    Once enough data is collected and an average is calculated, then we would have a "true" "real PM hours".

    0
    Comment actions Permalink
  • Holman, Nathaniel J

    Agreed you would almost want a report for PM's estimated vs actual side by side. Even better a report that would allow you to click a box or something that says show me PM's that went over their estimated time. A report that goes out a business year with PM estimated hours to help budget manpower and justify additions or subtractions from that. Personally I think the scheduling and scheduled event reporting could use a fresh coat of paint all around for usability and usefulness.

    0
    Comment actions Permalink
  • Chad Williams

    I requested creation of this type of report with L2L about 18 months ago and I know that it is in the works to be completed.  In the meantime I have figured out a way to achieve this with L2L's existing reports.  If anyone would like to know how to do this please feel free to reach out to me.  It does take some work but the results you see are a very good tool to evaluate your existing PM program.

     

    0
    Comment actions Permalink
  • Devin Baldwin

    Which would be more valuable: A report that compares planned vs actual, or a setting to automatically adjust PM estimates based off of previous completion times?

    0
    Comment actions Permalink
  • Holman, Nathaniel J

    I don't know if you want to go down the automatically adjust road. You could run into people intentionally dragging their feet to get more time to do them.

    0
    Comment actions Permalink
  • Chad Williams

    Planned vs. Actual report would be ideal.

    0
    Comment actions Permalink
  • CJohnson

    I can understand the concern Nathaniel has about people taking advantage of this.  I could also see this happening but I think if you're average is eventually taken over a very long period of time, then you would be able to see the discrepancy. 

    After considering the planned vs actual suggestion, I think this would also be a valuable source of information.  If I must choose between the 2, I would say the report would be better.

    0
    Comment actions Permalink
  • Kevin Bryan

    I would think the planned vs. actual would be the most valuable assuming the actual time is dynamic and is adjusted over time according to average man hours per PM.  It would also be nice to show a trend on hours/time both planned and actual with the ability to display a desired goal for actual time? If you can challenge the team to a goal it will hopefully eliminate the concern of people intentionally dragging their feet:)

    0
    Comment actions Permalink

Please sign in to leave a comment.