Theory off troubleshooting method for techniciansppt

Teoria de Resolucion de Problemas Técnicos

1. General troubleshooting
RMB 73RH C & 73RH C HT

2. Troubleshooting
Expectations
Fixes problems quickly, efficiently and
economically satisfying
Corrects the cause of the problem, not only
the effect
Solves the problem so that it doesn’t appear
again
Does not create any new problems, when
solving the current problem
Stops similar problems arising in the future

3. Troubleshooting
8 steps in the troubleshooting system
1.Learn the SHOULD-value for the product
2.Collect and separate information
3.Specify the problems
4.Changes
5.Test for the cause
6.Make prioritizations
7.Actions
8.Think beyond the repair

4. What, where, when, how?
What
–What is your problem about?
–What is wrong with it?
Where
–Where is your problem ?
When
–When was your problem discovered?
–When and in what situation was your problem discovered?
–When, how many times, has the problem since then?
How
–How many things have this problem?
–How serious is the problem?
4
The clearer you can describe the
problem, the clearer you can see
what caused it!

5. 8 steps
1. SHOULD-value
Trouble-shooting starts by having a clear
understanding of what should happen.
Find out how it should look, how it should feel,
how it should sound and how it should
perform.
That is the way to trace the problem quickly!

6. “The rig is broken down.”
You are called in to fix the problem. Nobody
knows exactly what is happening.
–Try to get more information.
–Ask for more facts.
8 steps
2. Collect and separate all information
Remember:
You can not repair anything
if you do not know why it
went wrong.

7. 1
2
34
5
What? Where? When?
Analyze facts
Find inadequacies in your information
Find the changes which can have caused
what you are trying to explain
Check all possible causes to see if they
explain all possible facts on the problem
Check out everything about the problems by asking:
8 steps
3. Specify the problems

8. 8 steps
4. Changes
Adjustments
Repairs
Modifications
New personnel
A new area of application
New place
Look for the unusual and for things that
have changed

9. 8 steps
5. Test for the causes
Can this cause give that result?
Does this explain what happened, where it
happened and the degree to which it happened?
Make a list of possible causes
Verify a cause against the specification of the
problems:
Think a minute and
gain an hour
A B C D E
X
X
X
X
X
X

10. 8 steps
6. Make prioritizations
On site:
Check out the possible causes from
your list
Make prioritizations
Concentrate on things that need your
attention the most

11. 8 steps
7. Actions
A permanent, fully-corrective measure is a
smart conclusion to a problem:
It is a rational product of systematic
troubleshooting

12. 8 steps
8. Think beyond the repair
Consequences
Other places
What is the cause
Information
All these attempts to get ahead of
the problem are connected with
preventive maintenance
Thinking beyond the repair means trying to see
what could happen after the repair, so that you
can do something before it happens
For maintenance instructions
-check the manual!

13. Committed to
sustainable productivity.