Closing Codes for Beginners

The Basics of Closing Codes for Work Orders in EAM

In the early days of rolling out EAM, back when it was known as 7i, I was working with Nucor Steel on their project and we would take our work to the bar after leaving the site. This bar happened to be at Earl Jackson’s house and it was named the G-Spot. The saying goes, “hard to find, but fun when you get there”. Actually, the G-Spot got its’ name from Gwen – Earl’s wife. She helped in the construction of the bar, so Earl and Chuck, their best friend named it the G-Spot. What does this have to do with closing codes? I’ll explain.

One night after a long day of work we retreated to the G-Spot and re-deployed our laptops to the bar counter. We were in deep discussions about what is called static data such as equipment classes and part classes, then I sprung the question on Earl, “what do you want to do about closing codes?”. Then suddenly out of know where Earl spouted out the genius I’m about to share with you. It was if he was possessed by some higher power who was using him to channel the information to me so I could capture it. It was truly an amazing experience to behold.

Importance of Closing Codes

Closing codes in the EAM world are four valuable pieces of information to be captured on each and every work order at the time of closing. These four pieces of information help a maintenance department determine common reoccurring problems in their areas of responsibility.

It is expected that anyone within an organization report problems with equipment or assets to the maintenance department with a Work Request. The work request screen is usually dummied down to make the process of entering a work request easy. The user describes the nature of the problem in the work request description field. He then selects the equipment from a look up. Some organizations let the user choose the type of work order, i.e. emergency or corrective, and some even let the user choose the priority.

Earl’s Profound Knowledge

Earl said, “We can’t expect our ordinary requestor to know the nature of the problem when they submit a work order, so all we want from them is to use four of their five God given senses to tell maintenance why they think there is a problem.” Those five senses are as follows:

Problem codes

  • Visual – Something doesn’t look right.
  • Smell – Something doesn’t smell right.
  • Sound – Something doesn’t sound right.
  • Temperature – Something is too hot or cold.

When maintenance arrives on scene they look for the same problem that the requestor reported before taking action. Earl said, “We expect maintenance to categorize the problem into the major food groups of maintenance. These food groups are:

Failure codes

  • Mechanical
  • Electrical
  • Hydraulic
  • Pneumatic
  • Lubrication

You can guarantee that one of these failures is the source of the problem. Then we move on to what action is required. This is simple and applies to every situation:

Action codes

  • Adjust
  • Repair
  • Replace
  • Upgrade

Then in the final analysis maintenance determines the cause however painful it is.

Cause codes

  • Negligence
  • Normal wear
  • Run to failure
  • Act of God

This pretty much sums up everything we need in closing codes. Then as Earl usually does, he finishes his speech with “so…”.

To find out more about closing codes or to get in touch with us for any questions you may have, click here.

Leave a Reply

Your email address will not be published. Required fields are marked *

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>