Archive for the ‘Process & Practices’ Category

Domtar Espanola wins Uptime Award for Best Asset Health Management Program

Wednesday, December 14th, 2011
Domtar Expanola wins Uptime award for Best Asset Health Management Program

Leaders in the maintenance reliability community met to honor fellow maintenance reliability professionals for their outstanding achievements and to celebrate individual excellence at the Uptime® Magazine Best Maintenance Reliability Program Awards at the International Maintenance Conference held Dec. 5 – 8, 2011.

Ivara customer, Domtar Espanola won Best Asset Health Management Program.

I wanted to highlight one of their leaders, Kim Hunt. Kim spoke in several sessions at the IMC conference and I was so impressed with her passion for establishing a reliability culture. Kim is the Reliability Manager at Domtar’s Pulp and Paper Mill in Espanola, Ontario. She specializes in lubrication, planning, predictive tools, CMMS implementation and the development and implementation of the Ivara EXP condition based asset management program (referred at Domtar as “RDM” – Reliability Driven Maintenance). Kim believes that leadership, commitment, teamwork and persistence are key to Domtar successfully weathering the challenging market conditions.

Congratulations to the team at Domtar.

Link to Uptime Magazine Q&A with the winners… http://www.nxtbook.com/nxtbooks/reliabilityweb/uptime_20121201/#/62

Planning in a Proactive Maintenance World

Wednesday, August 31st, 2011

Quick, how many tasks are in your work backlog?
How many have been done before?
How many standard tasks exist in your system?
How many of those tasks have been formally identified and formally reviewed?
What are the risks and consequences of the asset failing?

…That bad?

Planning has been around as a practice since work was invented. However, most of the effort has been in ‘work avoidance’ (not functional failure avoidance).  There has always been a wishful thinking and crossed fingers approach to Maintenance Management.

Proactive culture indicates that all work/tasks are formally planned. A proactive culture provides early warning or prediction of preventable failures through formal Work Identification methods, ie. RCM, MTA (FMEA), RCA, & PDM. These methodologies can be utilized to ensure your planning efforts correlate to getting to the right work on the right equipment at the right time.

If work is formally identified, prior to the need for a response, then the preventative work/task and/or the proactive corrective work/task are both known and can be planned in advance.  The specific roles and responsibilities of the Planner in a proactive, reliability focused environment are different than in a reactionary breakdown maintenance environment. Planners need to understand the practice of Reliability Centered Maintenance to get to the proactive elements of planning.

Take an RCM course in your area… http://www.thealadonnetwork.com/products-services/public-courses-training/

 

Need to fix Planning and Scheduling before looking at Reliability? Think again…

Tuesday, August 31st, 2010

As I visit with many sites across all industries around the country, I continue to hear folks say that they have to fix their planning, scheduling and work order data collection systems before they can go after driving improved reliability. In my opinion, nothing could be further from the truth.

Most organizations today do a poor job of writing out work orders for tasks being done and then providing the needed data after job completion to build a healthy history base. If you think about how long it would take to build a meaningful database, it would take forever to get a solid initiative in place. This is time that most organizations simply do not have.

I believe the key to getting a reliability program underway is to first determine baseline performance data for your most critical equipment that will be key to determining when an asset is starting to function outside of its acceptable boundaries. There are different processes such as Maintenance Task Analysis (MTA)  that allow you to determine this in a very credible way. Once you know what data needs to be looked at, you can then decide how you want this information collected and processed. It can run from simple check sheets done manually or automated using handheld devices all the way up to online data collection and automated condition based monitoring to capture the necessary readings. The trick then becomes how to best analyze, correlate and act on all of this data, often being summarized from of thousands of data points.  If  you are able to look only at the data that falls out of acceptable limits, then it is a lot easier to manage. This is where technology like Ivara EXP comes into the picture.

EXP filters the data and calls your attention to the readings only when necessary and only to those readings that require attention. This in itself is an amazing aid and can save tons of time and resources. With this kind of information being conveyed close to real time to whomever needs to see it, will allow for proactive steps to be taken prior to failure taking place. Hence you have just caught a potential failure prior to it occurring and causing all the time and heartache  that goes along with unplanned downtime. The key to remember is that all of this can be done on your most critical assets in fairly short order. The recorded information that helps you spot and resolve the potential failure also is applied to that historical database (that we started out talking about wanting at the beginning of this posting).

You can and, in fact, should give serious consideration to this approach if you’re looking for timely improvement without taking forever to get started. Improved RELIABILITY can be yours and the gains it brings shared with everyone in the organization in weeks and months, NOT years.

Good luck and enjoy the journey.

Want to get promoted in Maintenance and Reliability?

Wednesday, April 28th, 2010

What you should be doing in Maintenance and Reliability if you want to get promoted… first off and most importantly, you need to help your company meet these goals:

  1. Improving asset availability and capability
  2. Maximizing asset life
  3. Reducing asset maintenance costs

Once you realize that there is no “Silver Bullet” approach, start building upon a plan that supports a phased maturity model. Develop solid processes with linked tasks supported by clearly defined roles and responsibilities. Develop skilled and motivated people to implement-Involve everyone in your reliability efforts. By championing the cause, and documenting results, by association you will look good and likely will be in the running for a promotion.

Use technology appropriately to enable good processes and practices. Long term sustainable results can only be achieved by implementing all aspects of the solution. If you implement a new practice, but forget about process, it likely will not be sustainable in the long term.

Your personal 10 steps to success are:

  1. Acquire asset management knowledge and skills
  2. Develop mentoring relationships
  3. Volunteer for more responsibilities
  4. Quantify your success
  5. Practice self promotion – but don’t brag
  6. Be a team player
  7. Listen to other’s point of view – don’t close your mind
  8. Always be professional
  9. Always look for improvement opportunities
  10. Create your own opportunities-take chances

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.

Defining Failures and Being Consistent

Wednesday, February 17th, 2010

To identify when maintenance is required, we need to define failure. The traditional view was that as equipment gets older, it is more likely to fail. The old definition of failure is when the equipment breaks down and is no longer operational.

However, studies have shown that the majority of failures are not age related.
In the new definition of failure, all equipment entering service immediately starts to wear, whether installed as new or brought back to new through repair. Equipment will eventually reach a point where it fails to meet the operating requirement. This failure point is not necessarily predictable – it could happen early on or after years of use.

If the equipment has no capability at all, it is in a totally failed state or breakdown state. If there is some capability, but the equipment is not meeting the desired level of performance, it is said to be in a functionally failed or partially failed state.
By conducting inspections of equipment condition on a regular basis, you can track early signs or indicators of a partial or functional failure long before it breaks down. By finding indicators of failure, maintenance can be targeted more accurately. When you look for indicators of failure, this is called conducting a condition inspection.

Let’s use an example. We have a pump that is required to supply between 130 and 100 gallons of water to the process. If it supplies any less than 100 gallons, the process will not operate properly. In the past, we defined failure as the point when the pump broke and does not pump any water at all. But most failures do not occur instantly. To track potential failures, we use indicators (such as tolerances, or gauge readings or other visual physical signs that indicate equipment condition is deteriorating). Since the failure point is not necessarily related to age, indicators must be monitored on a regular basis. Let’s use a gauge reading as our indicator. The indicator reads that the pump is only pumping 105 gallons. Since this is the low end of what it is required to do, it is considered a potential failure or point P on the curve. If the deterioration is not corrected, it will continue until it is pumping less than 100 gallons of water. The pump is still working, but not at the desired performance level – it has a functional failure. This is today’s definition of failure, the point where the asset fails to perform its intended function.

The amount of time that elapses between the detection of a potential failure and its deterioration to functional failure is known as the PF interval. If you properly define inspection tasks, you are able to detect failure long before it occurs and perform the corrective maintenance work when it will least impact operations.

Remember that if the potential failure (P) is not detected, the equipment will continue to deteriorate until the point where it reaches functional failure (F). Once enough condition inspection data has been defined, you can calculate the PF Interval and plan maintenance activities.

Is your PM program good enough?

Monday, January 11th, 2010

Upon visiting a very successful company a couple of weeks ago, I got engaged in a serious conversation with their management on why their PM program wasn’t enough to allow them to reach optimum performance. I believe the following findings can be repeated in many plants across all industries so wanted to share it with you.

It seems that the plants leadership has worked over the past 2 years to put in place a complete PM program for all of its process control equipment. To their credit, they did a good job of identifying key assets and drafting an outline of what needed to be done and how frequently they should do it but that’s where the effort came to a stop.

Though they took a good first pass at the mentioned program, they failed to involve shop floor personnel in defining key equipment and leveraging their experience and knowledge to define what needed to be done and how often the PM should be scheduled. As you might guess, this caused a credibility gap when the program was rolled out, one which they never really recovered from.

The next shortcoming was the lack of using a formal process to get at the root of what needed to be looked at based on cost to do and consequences of failure. This allowed a number of PM’s to be put in place that really were a waste of time and dollars due to the very limited payback that could be expected vs the outlay of resources to accomplish the work. This is where a structured approach such as Maintenance Task Analysis (MTA), or for key critical assets, the use of Reliability Centered Maintenance (RCM) would be a tremendous help in insuring the right work would be done at the right time.

Another shortfall to the approach that was taken was the lack of understanding for what Predictive Maintenance (PdM) concepts could do for them relative to seeing problems starting to develop prior to their becoming an issue. Time based maintenance is just to hit and miss for the majority of failures we try to catch when attempting to improve equipment reliability and performance. This is backed by documented findings that over 80% of all failure is random in nature.

Another shortfall that I would like to touch on is the importance of documenting the findings while performing a PM. Actually this needs to be done for all work, including the Reactive Maintenance carried out each day. This documented data allows you to understand exactly what and where your failures are occurring. This information really becomes the key to improving future performance. The data needs to be captured, documented and trended so as to be of the most value in sorting out what you want to focus on to drive improvement.

The company I’m relating to didn’t understand how critical these steps were and thus really evolved to what I call the ‘Poke and Hope’ approach to driving improvement.

As you think about the short comings listed here, I would encourage you to consider how your respective programs were developed and how well they are serving your needs. Does any of this sound like what might be taking place within your organization? I believe you’ll agree that this true story could be happening to you. Good Luck!

Implementing Operator Inspection Routes

Monday, October 19th, 2009

The Challenge –As many of you challenged with Implementing the results of FMEA’s or RCM analysis results have probably already experienced the question always arises “Will the Operator Routes on the PDA replace the traditional Operator Route Sheets?”

 This is just one of many “Culture Change” issues that arises on the path from a “Reactive” culture to a “Proactive” one. One school of thought is that by making many of the Condition Based Maintenance(CBM) checks items on the Operators Daily Route, organizations can avoid the challenge of how to manage routes with frequencies that vary from 3 day to 7 day and options in between. However, this results in what is perceived as incomplete operator routes.

 The source of the problem

 The reason many organizations struggle with this aspect of implementing a CBM system is that many of the checks that appear on Operator Route Sheets are looking for components that have already failed (the solenoid valve that no longer opens or closes or the control panel bulb that has burned out).

During an MTA or RCM the reliability fundamentals that are followed direct the group to follow a CBM approach if the failure mode:

  1.  Has a P-F interval that is long enough to allow the resolution of the failure without suffering the consequences of the failure.
  2. The P-F interval is consistent.
  3. The effort to apply the CBM approach is worth doing.

In addition to these considerations, the Organization is instructed that it is OK to check components more frequently that ½ the P-F interval especially if there is no additional cost i.e. “Operators are already there and therefore there is no extra cost”. This point is debatable. As a result, during the analysis a number of identified failures result in a decision of “No Scheduled Maintenance”.

 However, on today’s Operator Route Sheets, these “No Scheduled Maintenance” failures show up as daily checks since these Route Sheets are comprised of checks of components that “Have Already Failed” along with components that are “In the Process or Failing”

Some solutions

The best solution to this issue is dependent on the culture of the organization and their tolerance to change.

  1.  If the culture of the organization is very resistive to change, a possible solution would be routes that include checks that would be considered as “No Scheduled Maintenance” in an MTA or RCM analysis. This solution will produce routes that are similar to existing Operator Routes but run the risk of becoming extremely large since Operator Routes cover a significant number of failures although they are not always explicitly identified as points on a route. This approach will allow the organization to overcome some of the cultural change impact but may introduce some other challenges.

    It should also be noted that most of the CBM checks that appear on these Daily operator routes, in fact have a P-F interval that is often much longer than 2 days. This obviously makes sense since a P-F interval of only 2 days leaves very little time to prevent the consequences of the failure and would probably end up as a No Scheduled Maintenance or a Redesign in the analysis. Remember that a correctly Facilitated and Implemented Work Identification Analysis should have P-F intervals that are as accurate as possible. This always allows the option of putting the inspection on a route that is more frequent but still ensures that the P-F on the Failure Mode is retained in the event of future changes to any route frequencies.

  2. If the culture of the organization is more receptive to change, an alternate option is to create Operator Inspection Routes that are more closely tied to the actual P-F intervals. This will result in Operator routes that must be performed at frequencies of 5, 7 days or more. The issue with this approach is that you are now asking the Operators to manage inspections that do not fall into their regular routine and must also be managed. This approach also provides a clear distinction between the normal Operator Routes and the CBM Checks that the Operators are being asked to perform.
  3. The issue that often drives the Operators desire that the Routes contain all the checks they are presently performing is the feature of Integration to their CMMS. This integration now offers the added advantage of automating the process of generating a Corrective Action in the CMMS without having to go through the often annoying job of finding the asset in the CMMS and creating the necessary Work Request.

Another solution to this challenge is to create 2 separate routes for a system (one containing the CBM checks and another containing the No Scheduled Maintenance checks). Although this option may appear to address the desires of the Operators to make their life easy, it also adds a great deal of additional administration.

Other suggestions to improve the ease of use of pda’s

The expectation of an Operator as they walk their route is that all things should be running as expected. They are therefore looking for exceptions. This approach is facilitated in the Ivara PDA’s through the “Default to Normal” function that allows the Operator to record that all things were operating as expected except for any noticed “Non Normal’s”. This approach works well except for the cases where the Operators are expected to enter a Numeric Value for an Indicator. Implementations should always take the approach that unless a Numeric Entry is required for Trending or as an input to a Calculation there is no need to require a numeric entry. As all Operators will tell you, they often check that their equipment is operating within accepted norms by checking that a gauge needle is within the “Normal” range. Therefore, if the Implementer uses the approach of defining ranges for Normal and Alarm in a Visual Indicator, the Operator can take advantage of the “Default to Normal” approach and therefore avoid having to enter Numerical Readings where they provide no benefit.

It’s not magic…

There is no magic answer to the question of how to address the Change Management introduced to an organization as part of an Asset Reliability Initiative. Perhaps the most important points are:

  1. Have Senior Management clearly communicate thegoals and objectives of the initiative.
  2. Ensure that the Senior Management Team follows up regularly with the Program to ensure that all employees understand the importance of the initiative and that the changes that are introduced, although they may be uncomfortable, are worthwhile.

Your Asset Maintenance Program-Fact or Fiction?

Thursday, July 30th, 2009

Many of us have created maintenance programs for our assets over many years and with the help of many different people. Often the adjustments made to these are driven by a reaction to a given problem that “bit us” without fully understanding:

  1.  what created the problem in the first place
  2. the bottom line true financial impact of the failure and
  3. if  it’s worth doing something different, what is the best method to monitor that aspect of the assets health.

Too many times these changes/additions are driven by what “someone thinks” and not by truely looking at the facts. Over time these behaviors lead to an asset maintenance program that has reduced benefits and can create questionable feelings about the kind of job  maintenance is really doing.

What I would suggest you consider (if the above sounds all too familiar in your organization) is to step back and take a fresh look at what you feel really should be the appropriate program. I also believe it’s critical for both operations and maintenance to work on this together with the added assistance of engineering as appropriate.

There are several processes that take you through an excellent review of how an asset can fail and what can, and in fact should, be done to seeing the problem evolving to a point of concern. Maintenance Task Anaylsis and RCM are two that you should at least take a look at as they might relate to your environment. Using MTA for all but the most critical assets can promote a very effective and resource smart approach as you get started. The use of RCM can then be considered for the most critical balance of the assets that you are concerned about.

Taking advantage of your personnel’s experience coupled with these processes WILL result in a very credible and effective program created by the shop floor and driven by facts, not speculation. What a great way to both clean up a program and get your folks on board. You really can’t lose! Good luck.

Change is required to improve in Maintenance, RCM is a positive change…

Thursday, July 23rd, 2009

The reason to change any process including manufacturing or maintenance is desire for improvement; to be better than your competition.

 

In today’s world, the main driving force for change is quality (of product, service, and work) and cost reduction. To improve quality or save money you need to introduce some sort of change; you need to modify, transform or completely move away from your current practices. We all know that in order to succeed in any change, the entire organization (from top to bottom) needs to understand the necessity for change and be dedicated and supportive in adopting it. The same applies within the Maintenance organization.

 

RCM is a positive change for the maintenance process –and inspection routes are one of the most important aspects to implement from RCM. Why?

 

If you are not observing equipment condition continuously –either with some sort of continuous monitoring system (Condition Based Maintenance) or with inspection routes,  then your maintenance department will never move away from being reactive. It is virtually impossible to continuously monitor an entire system, or where possible, it can be very expensive. Many companies are now using a combination of both or using only inspection routes with Maintenance Management responsible for Inspector training and motivation, as well as route optimization. The reason for this is that the majority of RCM action plans call for human sense inspections that can only be achieved by inspections and routes.

 

Recording data during an inspection can be a painful process especially if you’re printing out routes and entering data manually into CMMS. But with use of handheld computers (which Ivara offers), the entire process is automated. An Inspector enters his inspection data into the handheld. He/she is immediately warned of any out of normal readings based on pre-set thresholds. When the route is done, all data is transferred wirelessly into Ivara EXP, providing Maintenance with a centralized view of all condition data from all sources. With this centralized view of essentially real-time data, Maintenance is empowered to make informed decisions, ensuring the right work send to the CMMS for completion.

 

With diligence to this proactive process, inspection routes catch equipment failures in early stages which results in saving money, time and effort. The whole game is about equipment uptime; elimination of unwanted long downtimes and costly repairs.