Transcript Slide 1

Questions on failure codes
1. Why do we collect information,
generally?
2. Why do we collect failure codes,
specifically?
3. What is a failure code?
4. How will failure codes support our
reliability and supportability goals?
1. Why do we collect information,
generally?
1. Adjust PM task
intervals & PM tasks
2. Assess desirability of
additional PM tasks
by assessing:
In order to 3. Eliminate unnecessary
1. Failure Data
(over intensive) PM
2. Inspection findings
tasks
4. Improve failure
This is a continuous process!
response
5. Redesign and Design
6. Verify contractual KPIs
(ISSC)
to improve (measurably)
readiness, survivability, and
performance safely, at lowest cost
2. Why do we collect failure
codes?
• We collect failure codes:
– When we know precisely how the compilation
and analysis of their instances, will enable us
– to perform one or more of the six activities in
the blue box.
3. What is a failure code?
• It is the answer to the question:
– “What event caused the loss (or potential
loss) of capability?”
• Usually contains a noun, a verb, and a
“due to” clause. (Bolt disintegrates due to corrosion.)
Failure Mode
= Failure Mechanism
= Failure Cause
= Failure Reason
= the event that caused the failure.
4. How will failure codes attain required
reliability and supportability goals?
• When selecting a failure cause we encounter a
recurring non-trivial, two-dimensional problem:
1) To what depth?, and,
2) To what degree of detail?
shall we consider / record the failure cause (code)?
• Unless resolved, compiled failure code
instances will:
– scatter in both dimensions.
• It is the well known “failure code
problem”.
• RCM offers a solution to the failure
code problem
Reliability analysis requires that we
record:
•
not only the instance (the fact) of the
failure mode,
• but also the nature of its occurrence.
How did the life cycle of (this instance of) the
failure mode end?
1. By functional failure?,
The Event type
2. By potential failure?, or
3. By suspension?
The combination of the Failure mode (i.e code) plus the Event type unleashes the
power of Reliability Analysis, e.g. …
Perform.
Loss
Process
Incident 1
Function,
Failure,
Cause,
Effects,
Consequences
BI-Cycle
LRCM
SpotLight
CBR
Incident 2
Function,
Failure,
Cause,
Effects,
Consequences
Conditional probabilty of failure for 200
hour intervals
KPI
ABB
Real-TPI
OSISoft
PI
0.4
0.3
0.2
Etc…
Total removals
0.1
Potential failures
Functional failures
0
2000
3000
4000
1000
Operating age since last shop visit (flight hours)
EXAKT
…
Incident “n”
DLI
ExpertAlert
Improved
maintenance
policies