Assignment 8.1 Itc System and Principals
- Submitted by: darthmalik
- Views: 227
- Category: Other
- Date Submitted: 05/13/2014 01:55 AM
- Pages: 4
- Report this Essay
Task 1
Diagnostic repair procedure.
Fault validation
Firstly, we need to confirm if the problem is actually there and is repeatable and if it is affecting an individual or is it a common fault. The user will need to be questioned to confirm this and if possible / required you should physically investigate.
Information gathering
Once a fault has been confirmed the next stage is to gather more information to assist in the resolution of the issue. There are many places that information can be gained from and more information will make any fault resolution easier. Some places include:
Information analysis
Once you’ve gathered the needed data you can begin to analyse it and select the best cource of action to take to get the issue resolved.
Solution Identification
This is the stage where a solution is gained. This maybe a software issue, a hardware issue and may need replacement parts. Whatever the solution is a problem log should be filled in to record all the actions taken.
Diagnostic process
Information sources
Information sources can include:
* Automatic error messages
* A knowledge base
* More experienced colleagues
* Previous repair records
* Technical manuals
* Machine specifications
* The internet (which can include fault code databases, manufacturers websites, online manuals and forums)
* Previous problem logs
* Your own knowledge, which will keep increasing!
Specific fault identification
Flowcharts are a great way to resolve specific commonly occurring problems and a solution can usually be quickly found.
A good resource for flowcharts to commonly occurring faults can be found here: Diagnostic flowcharts
To minimise disruption you need to ensure a reasonable and realistic timeframe is given to the user. A spare computer should be assigned if available and you must ensure that if it is possible all data is backed up before starting any work on a machine.
If you get to a stage...
Diagnostic repair procedure.
Fault validation
Firstly, we need to confirm if the problem is actually there and is repeatable and if it is affecting an individual or is it a common fault. The user will need to be questioned to confirm this and if possible / required you should physically investigate.
Information gathering
Once a fault has been confirmed the next stage is to gather more information to assist in the resolution of the issue. There are many places that information can be gained from and more information will make any fault resolution easier. Some places include:
Information analysis
Once you’ve gathered the needed data you can begin to analyse it and select the best cource of action to take to get the issue resolved.
Solution Identification
This is the stage where a solution is gained. This maybe a software issue, a hardware issue and may need replacement parts. Whatever the solution is a problem log should be filled in to record all the actions taken.
Diagnostic process
Information sources
Information sources can include:
* Automatic error messages
* A knowledge base
* More experienced colleagues
* Previous repair records
* Technical manuals
* Machine specifications
* The internet (which can include fault code databases, manufacturers websites, online manuals and forums)
* Previous problem logs
* Your own knowledge, which will keep increasing!
Specific fault identification
Flowcharts are a great way to resolve specific commonly occurring problems and a solution can usually be quickly found.
A good resource for flowcharts to commonly occurring faults can be found here: Diagnostic flowcharts
To minimise disruption you need to ensure a reasonable and realistic timeframe is given to the user. A spare computer should be assigned if available and you must ensure that if it is possible all data is backed up before starting any work on a machine.
If you get to a stage...