Archive for the ‘Implementation Success’ Category

Maintenance in a mobile world –and still get reliability

Tuesday, May 25th, 2010

One of our customers, PG&E, had challenges using a paper-based inspection system covering a 70,000-square-mile service area. They found it very labor intensive, there were lots of duplicate entries, inconsistent inspection criteria, difficult to see trends or identify systemic problems, and there was a general lack of data validation. Many details typically get lost in transcribing from paper to system. It’s hard to see the big picture and takes too long to act on recommendations.

What they did in just 3 months was translate all their paper definitions into Ivara EXP’s mobile application on Panasonic Toughbooks. They have condition indicators, states, task templates, standard tasks plus the definition of the corrective tasks to trigger in SAP. All the corrective work parameters are defined in SAP. They use bar coding to identify equipment being inspected which allows for flexible routing of activity. They insert work instructions for collecting a reading directly on each indicator and use feedback from the field to tune the program.

Reliability has definitely gone mobile at PG&E –they now have visibility to asset data, their SAP work orders, current and historical condition information in a disconnected mode. They are empowered to make fast and accurate maintenance decisions based on accepted best practices and real-time asset health. Here’s a link to their story: http://www.ivara.com/content/PDFs/ivara_expremote_casestudy.pdf .

Jerry Olsen and John Wysocki of PG&E recorded a webinar with all the details of their success… if you want the details on their mobile solution, request it here:

CBM at Pacific Gas & Electric- Ivara EXP & SAP PM enables Mobile Workforce to Achieve Cost-Efficient Reliability & Compliance

Online training session helps customers to continuously improve

Tuesday, May 11th, 2010

Last week, we held a 3-hour on-line web training session in which customers learned the fundamentals of KPI development for Maintenance and Reliability using Ivara EXP. RCM Practitioner and KPI expert Carlo Odoardi led the session. The Online KPI training session covered everything from the theory of Leading vs. Lagging Indicators to developing KPI dashboards and comparative analyses.  The juiciest part was understanding the Ivara object model structure and finding the right data for specific KPI calculations. Ivara’s new KPI template library was also reviewed.  There was lots of time for Q&A in this interactive session and participants even got a break at about half time, just as if they were in a real classroom. Surveys were sent out after the session to get feedback? Let us know what you think… We are always looking for ways to improve the customer experience…

Customer success stories prove the value of the Ivara solution

Friday, April 23rd, 2010

Newly published case studies and success stories are available and we want to share them with you first!

Explore how Exelon uses Ivara Asset Health Indices to drive capital planning and maintenance prioritization, fixing a problem that was once prevalent in one of America’s largest electric companies. 

Read the Exelon Case Study

See how Ivara EXP Remote became a solution that drives maintenance excellence at transmission substations for one of the largest electric utilities in the United States.

Read the Ivara EXP Remote Case Study

Finally, read this white paper to discover how Ivara EXP is one of the key tools in helping companies move toward a smarter electrical grid that supports low carbon and renewable resources.

Read the Smart Electrical Grid White Paper

More Ivara Reliability Practitioners Receive their CMRP Designation

Thursday, March 25th, 2010

Congratulations to Joseph Marin and Eugene Gavrikov on achieving their CMRP designation!

The Certified Maintenance and Reliability Professional designation is the #1 credentialing program for certifying the knowledge, skills and experience of M&R professionals. The program is run through the Society of Maintenance and Reliability Professionals (SMRP). Passing the exam is about more than just committing textbooks to memory; it’s a thorough examination of individual expertise measured against a universal standard.  Every facility needs at least one CMRP on its team- and most should have more. Ivara has many. They have the knowledge and skills to ensure efficiency and productivity on site- from technical skills and streamlined processes to performance management and managerial confidence.

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!

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.

Maintenance and Operations Partnership: The Secret to Success in Reliability Improvement

Tuesday, February 2nd, 2010

While talking with a wide variety of companies, I believe that many still think that the whole reliability improvement effort belongs to the maintenance organization and it alone. In reality, that has been tried for many, many years with very limited success. It’s all about operations and maintenance working together to understand what has to be done and then working jointly to make it happen.

It’s no different than our automobiles. The mechanics can work their hearts out to have our cars in peak condition but then we have to do our part and work with them in learning how to care for our auto if we want that condition to sustain itself. This includes tasks we can help with such as checking the fluid levels, tire air pressure how we drive it,  etc. 

It’s all about us working together. We collectively need to have all our personnel understand how the equipment is supposed to function, all the many ways that it can fail, and their respective roles to keep the failures from occurring. There are incredibly straight forward processes that can be used to help this happen. Maintenance Task Analysis (MTA) and Reliability Centered Maintenance (RCM) are two that come to mind. They are designed to help bring together all those that we want to care for and operate our assets and get at the root of how to optimize equipment performance. By now most folks have heard of these approaches to improving performance but how many have really gotten into ‘making it happen’. The value to both the shop floor and the company itself are unbelievable.

If you happen to be one of those that hasn’t taken this type opportunity to the next level, please give it some serious consideration. The success that you’ll enjoy just might be your own.

 Enjoy the journey and good luck.

Maintenance Tips: Inspection & Inspectors

Friday, January 15th, 2010

by Brian Flett, Director Project Management, Ivara

How you Define your Inspection Program can mean the Difference Between Success and Failure

Poor performing assets result in lost production, poor product quality, late deliveries, accidents, incidents, and even major catastrophes. We need to balance risk and cost. On average, a capital-intensive manufacturing facility will identify 200 or more modes per one million dollars in assets. If we don’t know what those failure modes are, or the likelihood of them occurring, then we are turning a blind eye on the risk they pose to your organization.

To start, we need to regularly inspect and monitor trends in the condition of our assets. But how we record inspections and respond to failure modes can have a huge impact on financial results.

Make it Easier for your Inspectors and Reap the Benefits in Asset Performance

Inspection results are often vague and subjective because they tend not to accurately specify the severity of equipment condition. When results are open to interpretation like OK/Normal or Not OK/Abnormal, maintenance plans cannot be optimized. This may lead to maintenance being performed too early or too late, causing more costly maintenance than necessary. We need to be more specific in how we define inspections to ensure accurate and consistent recording of equipment condition.

Make it easy for any inspector by predefining condition severities that can be selected when doing the inspection. This leaves the guesswork out of it. Ivara EXP Enterprise is a tool that allows us to set predefined severity states for each piece of equipment. By using these predefined states during an inspection, we can identify the equipment’s actual state and compare its performance against its normal condition. Once we have enough data about equipment that we have inspected using these severity states, we can track and trend equipment performance. This will provide the information we need to perform the right corrective work at the right time.

To find out more about how Ivara EXP can help you make condition inspections easy, come back to our blog next month to read the next Ivara tip!

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.

Cultivating Asset Reliability Programs

Tuesday, August 25th, 2009

You can’t grow Asset Reliability Programs (ARP) like mushrooms! We have all seen or heard the old saying “I am like a mushroom… people keep me in the dark and feed me crap”. ARP’s are more of a cash crop, the ARP is the seed and your workforce is the soil in which it will be planted and from which it will grow.

Before you begin you must cultivate the soil. Prepare your workforce for the upcoming change, the more information the better.

Cultivating the workforce will allow you to start with a more prepared field. Don’t just tell them what is coming; take the time to solicit feedback. You have at your disposal a wealth of legacy knowledge that may help you shape your ARP or provide you insight into what they have seen go wrong with similar programs in the past.

Just like certain crops thrive in certain environments, ARP’s should be developed in the same manner. Your ARP should be developed with your working environment or operating context in mind. Specific machinery, how it is being used, in what environment, and the workforce operating and maintaining it should all be evaluated and used to develop a sound ARP.

You can’t force a plant to grow. If you plant it at the wrong time, don’t properly prepare the soil, over water, over fertilize, or don’t have the proper environmental conditions it just simply will not grow. You also will likely fail if you just plant it and leave it without support. The same goes for your ARP.

Once you have prepared and planted your ARP in the workforce, watch and listen to both. The answers are there and willing it to grow and thrive is just not going to work. Why is it not growing? What does it need? What adjustments need to be made in order to make it grow? If you are not progressing properly solicit feedback from the workforce and change conditions as necessary to get back on track. They will appreciate being a part of the solution and not being treated like mushrooms. It will also help show your ARP sponsors that even if there are problems, you are intelligently cultivating solutions to ensure success.

Keys for success:

  • Cultivate your workforce. Make them a part of your ARP’s success from concept to completion.
  • Make sure your ARP is being developed with your working environment, operating context, and workforce in mind.
  • Provide the right environment for your ARP to grow.
  • Measure growth and change the conditions as necessary to provide the environment your ARP needs to continue to grow.