Troubleshooting or dÃÆ' Â © panneuring is a form of problem resolution, often applied to repair a product or process that fails on a machine or system. This is a systematic and logical search for the source of the problem to solve it, and make the product or process operational again. Troubleshooting is necessary to identify symptoms. Determining the most likely cause is the elimination process - eliminating possible causes of the problem. Finally, troubleshooting requires confirmation that the solution returns the product or process to its working status.
In general, problem solving is the identification or diagnosis of "problems" in the flow of company or system management caused by such failure. The problem is initially described as a symptom of damage, and problem solving is the process of determining and addressing the causes of these symptoms.
A system can be explained in terms of expected, desired or intended behavior (usually, for an artificial system, its purpose). Events or inputs to the system are expected to produce certain results or outputs. (For example, selecting the "print" option from various computer applications is meant to generate copies that appear from certain devices). Unwanted or unwanted behavior is a symptom. Problem solving is the process of isolating the specific cause or cause of symptoms. Often a symptom is a product or process failure to produce any results. (Nothing is printed, for example). Corrective action can then be taken to prevent further failures of a similar type.
Forensic engineering methods are useful in tracking problems in products or processes, and various analytical techniques are available to determine the cause or cause of certain failures. Corrective action can then be taken to prevent further failures of a similar type. Precautions are possible using failure and effects mode (FMEA) and fault tree analysis (FTA) before full-scale production, and this method can also be used for failure analysis.
Video Troubleshooting
Aspect
Usually troubleshooting is applied to something that suddenly stops functioning, because previous working conditions form expectations about the continuation of behavior. So the initial focus is often on the latest changes to the system or environment in which it exists. (For example, a printer "is working when plugged in there"). However, there is a well known principle that correlation does not imply causality. (For example, a device failure shortly after plugging into a different outlet does not necessarily mean that the event is related.Failure can be a coincidence problem.) Therefore, problem solving requires critical thinking rather than magical thinking.
It's useful to consider the general experience we have with light bulbs. Light bulbs "burn" more or less randomly; finally recurrent heating and cooling of the filament, and the power fluctuations supplied to it cause the filament to crack or evaporate. The same principle applies to most other electronic devices and similar principles apply to mechanical devices. Some failures are part of the normal wear and tear components in a system.
The basic principle in problem solving is from the simplest and most probable problems that may be first. This is illustrated by the old saying "When you see the horse's tracks, look for a horse, not a zebra," or use another proverb, use the KISS principle. This principle produces a general complaint about the help desk or manual, which they sometimes question: "Is it plugged in and does the outlet have power?" But this should not be regarded as an insult, but should serve as a reminder or conditioning to always check things simple things before asking for help.
The troubleshooter can check each component in the system one at a time, replacing the components that are known to be good for each potentially suspicious. However, this "serial substitution" process can be considered degenerate when components are replaced without regard to hypotheses about how their failure can lead to symptoms being diagnosed.
Simple and intermediate systems are characterized by lists or dependency trees among their components or subsystems. More complex systems contain cyclical dependencies or interactions (feedback loops). Such a system is less able to accept the "splitting" splitting technique.
It also helps start from a known good state, the best example is a computer reboot. Cognitive journey is also a good thing to try. Comprehensive documentation generated by proficient technical writers is helpful, especially if it provides operating theories for the subject's device or system.
Common causes of problems are poor design, eg poor human factor design, where devices can be inserted backwards or upwards due to lack of appropriate coercion functions (behavior-forming constraints), or lack of fault-tolerant design. This is particularly bad if it is accompanied by habituation, where the user simply does not pay attention to the wrong use, for example if two parts have different functions but share common cases so it is unclear on which ordinary checks the parts are used.
Troubleshooting can also be a systematic checklist, troubleshooting procedures, flowchart or table created before a problem occurs. Developing an earlier troubleshooting procedure allows for ample thought about the steps to resolve the problem and organize problem solving into the most efficient troubleshooting process. The troubleshooting table can be computerized to make it more efficient for users.
Some computerized troubleshooting services (such as Primefax, later renamed Maxserve), immediately point out the top 10 solutions with the highest probability of fixing the underlying problem. The technician can answer additional questions to progress through the troubleshooting procedure, each step narrowing down the list of solutions, or immediately implementing a solution that he/she feels will fix the problem. This service provides a rebate if the technician takes additional steps after the issue is resolved: report a solution that actually fixes the problem. The computer uses this report to update its estimates of which solution has the highest probability of fixing a particular set of symptoms.
Maps Troubleshooting
Half separation
Efficient methodical problem solving begins with a clear understanding of the expected behavior of the observed system and symptoms. From there, the troubleshooter establishes a hypothesis about potential causes, and designs (or may refer to the standard checklist) to eliminate these prospective causes. This approach is often called "divide and conquer".
Two common strategies used by troubleshooters are to check for the conditions that are often encountered or easily tested first (for example, checking to make sure that the printer's light is on and that the cord is firmly attached at both ends). This is often referred to as "flushed front panel."
Then, "halve" the system (eg in the network printing system, check to see if the work reaches the server to determine if there is a problem in the end-user "to" end subsystem or "to" device).
This latter technique can be very efficient in systems with long chains of serial dependencies or interactions between their components. This is just a binary search app in various dependencies and is often referred to as "half-split".
Reproducing symptoms
One of the main principles of problem solving is that reproducible problems can be isolated and resolved reliably. Often the great effort and emphasis in problem solving is placed on the reproductive ability... to find procedures to induce symptoms reliably to occur.
Intermittent Symptoms
Some of the most difficult problem-solving problems relate to symptoms that occur intermittently. In electronics this is often the result of a thermally sensitive component (since the resistance of the circuit varies with the temperature of the conductor inside). Compressed air can be used to cool certain points on a circuit board and a heat gun can be used to raise the temperature; so troubleshooting electronic systems often requires the application of these tools to reproduce the problem.
In the computer programming race conditions often cause intermittent symptoms that are very difficult to reproduce; various techniques can be used to force certain functions or modules to be called faster than those that will operate normally (analogous to "heating up" components in hardware circuits) while other techniques can be used to introduce greater delays in, or force synchronization in between, other modules or interaction processes.
Intermittent problems can be defined thus:
Intermittent is a problem with no known procedure to consistently reproduce the symptoms.
In particular he insists that there is a difference between the frequency of occurrence and the "known procedure for consistently reproducing" a problem. For example, knowing that intermittent problems occur "in" an hour of a particular stimulus or event... but that sometimes happens in five minutes and the other time it takes almost an hour... is not not a " known procedure "even if the stimulus does not increase the frequency of symptoms that can be observed from the symptoms.
Nevertheless, sometimes the problem solver has to use statistical methods... and can only find procedures to increase the incidence of symptoms to the point where serial substitution or some other technique is feasible. In such cases, even when the symptoms seem to disappear for a significantly longer period, there is a low confidence that the root cause has been found and that the problem is completely solved.
Also, tests can be run to emphasize certain components to determine whether the components have failed.
Many problems
Isolating a single component failure that causes symptoms that can be reproduced is relatively easy.
However, many problems only occur as a result of some failure or error. This is especially true for fault tolerant systems, or those that have built-in redundancy. Features that add redundancy, error detection and failover to the system can also be interrupted, and failure of a fairly different component in any system will "lower it."
Even in a simple system, the problem solver must always consider the possibility that there is more than one error. (Replacing each component, using serial substitution, and then replacing each new component back for the old one when symptoms are found to persist, may fail to resolve such cases.More importantly the replacement of any component with a damaged component can actually increase the number problem rather than eliminating it).
Note that, while we are talking about "replacing components", the resolution of many problems involves adjustment or adjustment rather than "replacement." For example, a break in the conductor --- or "dirty or loose contact" may only need to be cleaned and/or tightened. All discussions about "replacement" should be interpreted as "replacement or other adjustments or maintenance."
See also
- 5 Why
- Tub curve
- Causes and effects
- Debugging
- Forensic engineering
- No Problems Found
- Troubleshooting
- Analysis of root causes
- Diagnosis of RPR Problems
References
Source of the article : Wikipedia
0 Comments