Transcribed from the video “RCPE What vs Who”
So, the root cost problem elimination. It’s really just a structured approach to eliminate problems…that’s all it is. It’s what usually happens when people say they do root cause, in my experience, this is the morning meeting and someone says motor tripped-out costing production loss. So, what happens in the morning meeting, now I haven’t been to yours, but somewhere, the first thing people say is this a maintenance problem or is this an operations problem. Oh, it’s a motor that tripped out so this is obviously a maintenance problem. So operations guys they say oh they just lean back and they stop thinking now. So great, we don’t have to worry about this is not our problem. So you lose 75 percent of your thinking power. So the Maintenance Department continues to say “Okay, is this a maintenance problem?” Is it a mechanical problem or is it an E/I problem. And they’re going to say no it’s not mechanical is a motor that trip. Of course that very homogeneous group of E/I we need to figure out is an electrical or instrumentation problem…
Maintenance personnel go to work and do their jobs taking measurements and writing reports, often with great care and skill. Their reports and recommendations then travel into a deep abyss from which they never return. Sound familiar? This situation is all too common in the condition monitoring (CM) world.
If you are currently running a vibration monitoring program in-house or outsourcing it to a consultant, before you potentially throw any more money in the toilet, you really need to audit your vibration monitoring program and ask yourself if you are getting any value out of it.
If you do not know what benefits you are getting from a program, you are probably not getting any benefits at all! On the other hand, if you are getting benefits but not documenting them, then your program is at risk for being cut. Either way, you need to know what is going on with your program and document it if it is good or fix it if it is not.
by Ned Callahan
Apollo RCA Facilitator and Trainer, ARMS Reliability
“How long should an RCA take?”
This question is similar to how long is a piece of string?
I have heard one manager in a plant that has stipulated a maximum of two hours for an Root Cause Analysis to be conducted in his organisation. Another expects at least “brainstormed” solutions before the conclusion of day one – within 6 or 7 hours. It is not uncommon for a draft report to be required within 48 hours of the RCA. Continue reading →
Semiconductor devices are almost always part of a larger, more complex piece of electronic equipment. These devices operate in concert with other circuit elements and are subject to system, subsystem and environmental influences. When equipment fails in the field or on the shop floor, technicians usually begin their evaluations with the unit’s smallest, most easily replaceable module or subsystem. The subsystem is then sent to a lab, where technicians troubleshoot the problem to an individual component, which is then removed–often with less-than-controlled thermal, mechanical and electrical stresses–and submitted to a laboratory for analysis. Although this isn’t the optimal failure analysis path, it is generally what actually happens.
What follows is a brief description of how to properly perform semiconductor failure analysis without introducing unwanted artifacts into the analysis. Continue reading →