Getting to a common ground

It’s lunch time on a Friday and my mind is going 100 mph after a great discussion with some members of the Maximo Manufacturing Users Group.[1] Today’s topic was an open discussion on Metrics and KPI’s. While the overall discussion was good as always, a small part of the talk has stuck with me. A discussion on a key metric a participant is using is the percent of planned jobs completed against all jobs completed.

While I agree this is a great metric, it was the follow up question that was the real home run.

What is considered a planned work order?

The call went quiet for a good 15 seconds while everyone pondered that one. The discussion picked up on ideas and thoughts on what a planned work order should be, but I spoke to one of the participants after the meeting and we both commented that we had the same initial reaction - a planned work order is just is planned. Hmm… I don’t know about your setup, but I haven’t been offered the Read My Mind Analytics module for Maximo yet.

So what does a planned work order look like so analytics can be applied? Some of the criteria on what a ‘planned work order’ that was discussed included:

  • The work order is assigned to a mechanic on Labor Plans tab
  • The work order is assigned to a craft for scheduling on Labor Plans tab
  • The work order utilizes a Job Plan for work to be completed, in lieu of ad hoc job steps.
  • The work order includes all parts required for task completion
  • The work order has a Scheduled Start date

Eventually this leads back to thinking about what fields should be required information to enter and process a work order. Things like:

  • GL account
  • Work order type
  • Schedule and/or Target dates
  • Supervisor
  • Lead

What has got my mind going is if two reliability professionals’ initial reaction to this question is that ‘a planned work order is just planned’, imagine how someone removed from maintenance operations is going to think about this?[2] As I got off the phone, I started to think about other aspects of our maintenance operations that could still ambiguous to others in our company.

Here’s a short list I have so far:

  • What is an overdue PM?
  • How should we measure your backlog?
  • What is considered ‘on time completion’ of a job?
  • What is considered equipment downtime?
  • When is a work order considered to properly scheduled?

So what terms does your maintenance group need to define to get to a common ground with yourselves and other departments? I look forward to working with members of the Manufacturer’s User Group to lay some ground work on creating base definitions.

Want to talk about this more? Drop a comment or hit me up on Twitter at @MyGeekDaddy.

  1. I highly recommend joining this Maximo user group. They are some of the brightest minds on Maximo and asset reliability I get to speak with on a regular basis.  ↩
  2. That’s assuming a topic like this is even on their radar, which it probably isn’t.  ↩