Unit 5 Flashcards
One of the easiest ways of troubleshooting or performing maintenance on equipment is by conducting a ___ ___.
visual inspection
A visual inspection can, and should be conducted ____, ____ and ____ equipment operations.
before, during and following
Before beginning an internal analysis, perform a visual inspection on the _____ of the equipment.
exterior
When inspecting equipment (like test equipment) that
requires periodic calibration, always check the ____ ____.
calibration sticker
Ensure it is within its due calibration date and that the piece of equipment is rated for the test to be performed. If the item is near or past the required calibration date, take the equipment item to the ___ ___ ___ ___ for recalibration because the equipment is considered to be non-operational.
Precision Measurement Equipment Laboratory (PMEL)
Any maintenance activity, such as an inspection, servicing, or
replacement that’s performed as part of a scheduled plan, rather than as a response to a breakdown.
Preventative Maintenance
What does PMI stand for?
periodic maintenance inspections
______ are often referred to as periodic, scheduled, or routine maintenance because the T.O. or commercial manual states how often the ____ must be conducted (e.g., monthly, quarterly, annually, etc….). This practice is a proactive approach to ensuring equipment is kept in peak operating condition.
PMIs
What does LWC stand for?
Local Work Cards
Because these inspections are performed on a routine basis, ___ ___ ___ are often created.
LWC
_____ is a form of problem solving. It is a logical, systematic approach to solving a problem, and making the equipment or system operational again.
Troubleshooting
What are the seven steps to the trouble shooting process?
- Identify the problem
- Establish a theory
- Test the theory
- Establish a plan
- Implement the solution
- Verify functionality
- Document the process
The following describes which step in the seven step troubleshooting process?
The first thing that you need to be aware of when troubleshooting
a problem is that the symptoms are not the problem. When troubleshooting, it is critical that you identify the underlying problem. What is causing the symptoms to manifest? Is there really a problem or is it just operator error? To do that, you should question the user. Ask detailed questions about when the symptoms occurred and why they may have occurred. If possible, try to re-create the issue. This can be extremely helpful when determining if anything has changed, because sometimes the symptoms will change over
time. It can also lead to figuring out what may have caused the initial problem.
Step 1: Identify the problem
The following describes which step in the seven step troubleshooting process?
After you have identified the base problem that is causing the symptoms, you will establish a list of probable causes. Try to create a
comprehensive list by brainstorming, asking other technicians, and/or researching the equipment history. Once you have a list of all the possible probable causes, use your technical knowledge to prioritize that list from most likely to least likely. Incidentally, be
sure to question the obvious. For instance, can you receive a signal but not transmit? You should probably look at the transmit circuit.
Establish a theory
The following describes which step in the seven step troubleshooting process?
Once you have established your theory of probable cause, you will need to test your theory to determine if it is, indeed, the actual cause. Your theory was created from the most likely probable cause, so you need to determine how best to test it. Using the system’s circuits & diagrams (Cs & Ds) to aid in testing your theory at the component level will greatly improve your ability to determine
the source of the issue.
Step 3: Test the Theory
There are two methods for “Testing the Theory” in the steven step troubleshooting process which are:
Serial or half-split methods
The following describes which “Test the Theory” method?
When utilizing the ___ ___, start at the beginning of the circuit or assembly, and systematically work your way through the circuit. Serial troubleshooting can be tedious and time consuming since you are working through every step, in order, to test the system. There may be some situations where this will be the best troubleshooting method for finding the problem.
Serial method
The following describes which “Test the Theory” method?
This technique allows you to locate defects within a few
measurements. Essentially the technique involves splitting the circuit path into halves and troubleshooting from the middle of the first half, then the second half, and so on. Once you determine which half the problem exists in, split the faulty section in half again and conduct the rest of the test. The half-split method is the most efficient means of troubleshooting an issue and can save time and your patience.
Half-split method
The following describes which step in the seven step troubleshooting process?
Once you have tested your theory and determined the actual cause of the problem, you will need to establish an action plan. Simple problems will probably only need simple plans. Some repairs are as simple as replacing a component, circuit card or module, resetting circuit connection, or replacing connectors, terminals, or ground points. Additionally, some problems will require you to order parts before repairs can begin, and any parts research should be included in the repair plan. If the plan involves multiple steps or a lot of time, you may need to write it down before implementation.
Step 4: Establish a plan
The following describes which step in the seven step troubleshooting process?
Now that the plan is ready, it’s time to implement the solution.
If any parts need to be ordered, that should be the first thing done. When all the parts and/or tools have been gathered, repair can begin. However, if it is a complex problem, or an issue above your expertise, you may need to escalate the ticket to a higher tier or a
different work center for maintenance.
Implement the solution
The following describes which step in the seven step troubleshooting process?
After making a repair, you must perform an operational check to verify that the system is fully functional. You should verify all the functions and settings are working on the equipment before returning it to service. If everything works, you may find that you can implement preventative measures so that the problem does not
occur again. Conversely, if full system functionality has not occurred, you will need to go back to step one and work through the troubleshooting process again to find the new or recurring problem.
Verify functionality
The following describes which step in the seven step troubleshooting process?
Once everything is fully functional, documenting the process
becomes important. This is where you document findings, actions, and outcomes. If the problem occurs again, there will be information available to walk someone through the means of troubleshooting and resolving the issue. This documentation also captures a
history of equipment and users so that perpetual issues (trends) become known and recorded. An important aspect of this is that both positive and negative outcomes should be documented. This can save time during future troubleshooting and prevent others from taking the same missteps you may have taken.
Step 7: Document the process
Overdue equipment is considered…?
Non-operational
Identifying, repairing and/or replacing worn components before failure
Preventative Failure
- Provide convenient reference to routine tasks in a consolidated format
- Setup, Operations, PMIs
- Derived from TO/manual
- Validated by QA
Local Work Cards
The following describes which step in the seven step troubleshooting process?
What is causing the symptoms to manifest?
Is there really a problem or is it just operator error?
Question the user
Try to re-create the issue
Determine if anything has changed
Identify the Problem
The following describes which step in the seven step troubleshooting process?
Establish a list of probable causes
Prioritize the list
From most likely to least likely
Establish a Theory of Probable Cause
The following describes which step in the seven step troubleshooting process?
Two useful methods to troubleshoot a fault:
Serial
Half-Split
Step 3: Test probable cause theory to determine actual cause
The following describes which step in the seven step troubleshooting process?
Start at the beginning of the circuit or assembly
Systematically working through the circuit
Can be tedious & time consuming
Ideal for some situations
Serial Method
The following describes which step in the seven step troubleshooting process?
Allows for fault detection within a few measurements
Involves splitting the circuit path into halves
Troubleshooting from the middle of the first half
Then the second half
Etc.…
After determining which half the problem exists in, split the faulty section in half again & conduct the rest of the test
Most efficient means of troubleshooting an issue
Half Split Method
The following describes which step in the seven step troubleshooting process?
Simple problems will probably only need simple plans.
Replacing a component, resetting a circuit, or replacing connectors
Step 4: Establish an action plan
The following describes which step in the seven step troubleshooting process?
Order parts if necessary
Begin repairs
If it is a complex problem, may need to escalate the ticket
Step 5: Implement the solution
The following describes which step in the seven step troubleshooting process?
Verify all functions & settings are working before returning it to service
Implement preventative measures to mitigate future issues
If system doesn’t function as it should repeat the troubleshooting process
Step 6: Verify full system functionality
The following describes which step in the seven step troubleshooting process?
Findings, actions, and outcomes
Both positive & negative
Information available for reoccurring problems
Saving time
Captures a history of the equipment
Step 7: Document the Process
The following describes which step in the seven step troubleshooting process?
