Fault logs

The role of fault logs.
Fault logs can be recorded systematically and this therefore helps with diagnosing and preventing
problems. Fault logs can be good at identifying reoccuring faults, which could highlight
problems with the computer system itself.

Example of a fault log:
Staff Name and Date - Ian / 31/7/03
Problem and description (including any error messages) - Mouse stopped working.
Time taken to fix problem - 30 mins
 Attempted solution and suggestions for next step -  Checked mouse device settings in control
panel / system. No properties found. Turned off PC and Swapped over mouse. Mouse started
working again.

Person who fixed it  - Jo
Contact information - Central Services IT co-ordinator


 An Example of fault logs within a company:
The fault logs need to gather certain information and this information can be judged on:
Within the company EGS, an example of their fault log:
They have to discover the:

The name and the role of the organization
Company
Equipment make, model and the serial number
Description of the fault
To tackle the fault, the EGS engineer takes the information listed in the fault and
will then talk directly to the customer about the fault and enlist them with a reference
number. The reference number is used throughout the process and the customer can refer to this
at any time.
Further support is offered if the fault cannot be determined and this support comes in the form of emailing through
further information about the fault, or if the fault is hardware, then possibly
sending back the damaged hardware. Once the fault is all sorted out, then the case is closed.