Author Archive

Implementing Reliability Off Shore Half-Way Around the World

Tuesday, March 23rd, 2010

Having a great time working with an R&D drilling ship in Asia.  They have been an Ivara customer for several years using Ivara’s EAM software, now they are embarking on a project to implement on-shore our procurement and inventory modules and on-ship EXP Enterprise to improve asset performance and reliability.  This is a challenging implementation as we are dealing with language, distance and time zones, however the project is making excellent progress.  Go-live Phase One is scheduled for April and a pilot Work ID  (RCM / FMEA) project will start in that same time frame.  We love a challenge!

Value of having your CBM and shop floor integrated

Friday, March 12th, 2010

The value of a conditioned based maintenance system, fully integrated to your other CBM tools/equipment? I couldn’t state its value better than one of our customers did recently… 

“Using the Ivara EXP software Asset Health Monitoring Panel, I noticed a trend. The equipment was showing an increase in vibration that would not have been detected until much too late.  We caught the signature change and determined it was a greasing issue. We corrected the automatic grease system, saving substantial repair time.  A very impressive demonstration to our maintenance and operations team of the value of EXP.  Everyone is for CBM and I am impressed with Ivara.”

Analyzing troublesome asset during training session nets immediate value

Friday, February 19th, 2010

I conducted an MTA introduction for major worldwide food processing company this week.  Instead of sitting though a bunch of presentations on the values of FMEA and our tools, we had them select an asset to perform an analysis.  They selected a proprietary asset that was causing more than normal downtime for their plant and processes.  This session was designed to be a combination of an introductory/education session, actual MTA (FMEA) and software training session.  We had 2 representatives from the plant (operations and maintenance) with 10 more observers sitting in from around the world.   We  started by facilitating the session and made such quick progress were able to hand the process over and let one of their observers facilitate and offer some coaching.  Results were recorded in our application as we conducted the analysis, real time.  We were then able to spend time discussing different options for implementing the routes quickly to the floor especially using some of the new slick functions in EXP Release 5.14 to speed implementation.  

Result from week;  great to see a customer get real value and quick results using our tools; we have generated lots of interest from the locations outside North America;  now working to put a plan together to engage the rest of North America and other locations around the world. 

Sometimes a one week analysis is worth a thousand words.

Key Performance Indicators – Count something, Count anything

Friday, April 10th, 2009

There is a lot of talk at management meetings about measuring and Key Performance Indicators (KPIs), but some of these KPIs are really of little to know value at all. Here are some useful guidelines to tell if a KPI is worth creating, if you cant answer yes to all four questions then you should question the value of tracking the data.

  1. Can an acceptable target be defined for the KPI?
  2. Can an action plan be defined to improve or correct an unacceptable KPI result?
  3. Can you define who is responsible for the KPI?
  4. Can the responsible person take action to effect the KPI results?

Counting the number of work orders in your back log and watching it increase or decrease does not mean a whole lot. Monitoring the ratio of hours executed on Planned versus Unplanned work and also measuring percent accuracy of planned hours versus actual hours are two valuable measures of how much (quantity) you are planning and how well (Quality).

Start with your business processes. For each significant process or set in the process define a measure that fits the 4 guidelines above.

If you need assistance with this in a Reliability context refer to Ivara’s APM (Asset Performance Management) process and its defined KPIs or have Ivara conduct a Reliability Assessment.

Prepackaged Reliability Programs

Monday, March 9th, 2009

One of the tricks of the trade that seems to be going around these days are reliability programs that require little to none of your resources and come mostly prepackaged.  The pitch will be something like, “we have seen many plants like yours before and we can take the maintenance plan from the last plant and with little or no input from your resources implement into your plant”.

Sounds to good to be true, and it is.

These programs are fraught with problems, mostly around acceptance by your organization and the appropriateness of the action plans based on your operating environment.  A good example of this is the application of EPRI content.  Any qualified reliability professional will tell you this content can be of great value however it needs to be reviewed for each operating environment and often for specific type of equipment.  When Failure Modes are developed out of context of your plant and operating environment and without the input of your experts, you will get too many, you will miss some and you may get incorrect frequencies based on consequences.  Reliability programs can be implemented cost effectively and efficiently with the appropriate use of content and processes (RCM/MTA/CPR).  But beware if it all sounds too easy, Reliability Program box can be checked, but benefit will not be achieved.

The two most common reasons a reliability program can fail and how you can avoid them.

Tuesday, March 3rd, 2009

Project created, project team focuses on one area in the plant, conditioned based maintenance increased, time based reduced, failures avoided.   Success?  Ah, but then, project team moves on to second area of plant, in the first area compliance goes down, reliability goes down.  KPI’s are in place, the new maintenance program is not being followed, but nothing is done…

There can be several reasons for the above failure.

Maintenance and operations personnel report equipment between PF interval, equipment does not get repaired, i.e. report gets “backlogged”, result, over time personnel stop reporting condition.

Project team moved on, supervision and management after years of being rewarded for firefighting go back to what they know.  A quick overview of a reliability program to these individuals is often taken as the flavor of the month and heads node while in meetings but attitudes do not change.

How to avoid these problems?

When a reliability program is implemented the organization should understand that quite often work load increases until equipment condition is brought back to a maintainable state.  That is, there is often a significant amount of failure modes found as soon as new inspections are instigated.  If these reported issues are not tracked and a plan formulated to address them, confidence will be lost.  What is the point of reporting this stuff if nothing gets done!

  1. Back fill reliability team members.
  2. Have team members who can augment area maintenance during and shortly after implementation of program.
  3. Monitor KPI’s and react quickly if proactive work load grows.  Execute PM first, Proactive work second.
  4. Make sure maintenance program is periodically reviewed for appropriateness and operating context.

Everyone, and that means everyone, (Management, Operations, Maintenance, Engineering, QA, Etc.) must understand the importance of why the company started down the program path.  In addition, there must be clearly identified measures in place and everyone, top down and bottom up must treat those KPI’s as critical.  If routes are not performed or found issues are not corrected, failures will not be avoided.

  1. Focus maintenance meetings on not just project status but sustaining progress.
  2. Reward success, track avoided failures.  (Often reduced/avoided failures are quite difficult to quantify, another blog!)
  3. If possible adjust compensation plans to match project objectives.If obstacles persist to the program, take action to correct.
  4. Overall communicate, communicate, communicate.