Unit of Competence:

Implement
Maintenance Procedure
 LO 1:
Determine best practices for
equipment and software maintenance
Identifying computer hard ware to be maintained
• There are several ways to identify the normal operation of a personal
computer.
• Most people use diagnostic software packages like PC Tools, Norton
Utilities and/or Check It to test a computer.
• Those diagnostic packages provide user-friendly operations to perform
testing of a computer.
• However, you can initially make measurable observations using your
senses, that is, the sights and sounds to identify the normal operation
of the computer.
• The table below suggests where to look and what you might hear to
get an indication of normal behaviour of a PC.
Cont.…
Device Sights Sounds

System unit • Floppy disk drive activity indicator Floppy disk drive mechanisms
(light) Speaker (beep)
• Front panel indicators such as: Fan
 Power on LED (light emitting diode) Hard disk drive

 Hard disk drive activity LED

Display unit (monitor) Power on indicator

Text displayed on screen

Keyboard Num lock indicator

Caps lock indicator

Scroll lock indicator

Cont.…

Table 1.1: Reference points for indications of normal behaviour of a PC

Potential sources of damage to computer hardware
and software
There are a number of common causes of damage to a computer or its
components. These are:
• Temperature variations
• Power cycling
• Static electricity
• Power line noise
• Radio frequency interference
• Phosphor burn on a monitor
• Dust and pollutants
• Water
Temperature variations
Cause
• Temperature variations (expansion and contraction of components from temperature
change) can lead to serious problems.

Damages
• Chip creep : where the heating and cooling of components can cause movement, usually
out of the socket that holds the component.
• Signal traces on circuit boards can be cracked and separated.
• Solder joints can be broken.
• Contacts undergo accelerated corrosion.
• Solid-state components can be damaged.
• Read and write problems on hard disk drive (due to expansion and contraction of the
platter of hard disk the data may be written at a different location relative to the track
centre).
Cont.…
Advice
• Ensure a computer operates in correct ambient temperature. Refer to
the computer User’s Manual for this information.
• Ensure the ambient temperature when the:
­system is on it is in the range of 15-32 °C
system is off it is in the range of 10-40 °C.
Power cycling
Cause
• Turning on a cold computer subjects it to the greatest possible internal
temperature variation.
Damages
• Same as for temperature variation
Advice
• Power on a computer only once daily. Don’t turn a computer on and
off several times every day.
Static electricity
Cause
• This problem usually appears during winter months when humidity is low, or in
extremely dry climates where the humidity is low year-round.
• Some static-sensitivity problems are caused by improper grounding of computer
power.
Damages
• Electronic components
Advice
• Always use a grounded power cord plugged into a properly grounded outlet. You could
use an outlet tester to check that it is properly grounded, but today, OH&S requires
that all power equipment be properly tested and certified. This includes the outlets,
cables and connectors.
• Use a grounded static mat underneath a computer, or an antistatic wrist-strap, before
touching internal components of the computer.
Cont.…

Fig.1. Grounded static mat Fig.2. Antistatic wrist-strap

Power line noise
Cause
• This problem is caused by poor quality power being supplied
to a computer system.
• It can also be caused by sharing a power source with other
higher power consuming equipment, such as coffee makers,
copy machines or a laser printer.
• The wire size and length will affect the resistance of a power
circuit.
Damages
• All system components
Cont.…
Advice
• A computer system should be on its own circuit with its own circuit
breaker.
• A three-wire circuit is a necessity.
• To decrease resistance, avoid extension cords unless absolutely
necessary and then use only heavy-duty extension cords.
• Avoid using too many items on a single outlet.
• Add an Uninterruptible Power Supply (UPS) as a power conditioner.
Radio frequency interference
Cause
• Mobile phones, cordless phones, fax machines and any radio
transmission equipment
Effects
• Sporadic random keystrokes will appear, as though an invisible entity
were typing on the keyboard
• White spots and lines appear on the screen
Advice
• Install specially shielded cables (built-in toroid core cables) outside a
system unit.
Phosphor burn on a monitor
Cause
• The phosphor on a cathode ray tube can be burned.
Damages
• Reduces the life of monitor (cathode ray tube)
Advice
• Turn both brightness and contrast levels to the minimum.
• Use a screensaver that displays different patterns on a screen.

NB: CRT phosphors are specific chemical compounds, which are arranged
on the inside of the screen tube in a certain order and are available in
various colors, starting with basic red, green and blue.
Cont.…

Fig.3. A monitor with phosphor burn

Dust and pollutants
Cause
• A power supply fan carries airborne particles through a computer.
• Food crumbs are attracted by magnetic media, while cigarette ash and smoke are drawn
toward disk drives.
Damages
• Floppy disk heads and media
• Electronic components (dust on the surface of components prevents necessary heat loss)
Advice
• Use power supply unit with air filter (the filter must be cleaned and changed
periodically).
• Don’t operate an unprotected computer in a dusty environment, e.g an industrial
workshop.
Water
Cause
• On a desktop, coffee or tea spills over a keyboard or into a monitor.
Damages
• Keyboard malfunction
• Monitor explosion (if a monitor is on)
Advice
• Never eat, drink or smoke inside a computer room.
The first steps towards troubleshooting
Reflect
Here is a typical scenario reported to the help desk.
• A client phones the help desk and reports that the computer hangs each
time they try to run a particular application.
What might be the source of the problem?
What steps will you take to find out?
This is the trouble shooter’s challenge!
Cont.…
Feedback
• In all cases where you are trying to troubleshoot a problem, you need
to use a logical step-by-step approach. For example, two questions
that you would always ask in this situation are:
When did the problem begin?
Has any new hardware or software been added between the time that
the problem appeared and when the system was last working
correctly?
Cont.…
Here is a list of reasons why a computer might hang each time a specific
software application is run. It could indicate:
• a corrupted file
• an incorrect installation
• hard disk failure
• a virus
• a new application causing conflict
• new hardware causing conflict
• new device drivers causing a conflict with older software.
General troubleshooting guide
Here’s a general troubleshooting guide that you can use when a
computer develops a fault.
1. Don’t panic.
2. Observe:
• What are the symptoms?
• What conditions existed at the time of failure?
• What actions were in progress?
• What program was running?
• What was displayed on the screen?
• Was there an error message?
• What functions are still working?
Cont.…
3. Use your senses (sight, hearing, smell and touch).
• Is there any odour present?
• Does any part of the system feel hot?
4. Check power supply:
• Is the plug inserted snugly /closely/ into the computer?
• Is the power cord plugged into an appropriate wall power outlet?
• Is the wall power outlet working?
Cont.…
5. Documentation (fill in a pre-designed check list):
• What is the computer doing?
• What is the computer not doing?
• What is being displayed on the screen?
• Is there any error message?
• What is still operating with everything connected?
• Is power still operating on each part of a computer?
6. Assume one problem:
• Use correct data and resources
• Use relevant technical manuals and information
7. Use proper test equipment.
Cont.…
8. Isolate units one-by-one:
• If a system worked when all peripherals were disconnected, turn power off and
reconnect one of the peripherals. Power on and test. If that unit works, turn the power
off and reconnect another peripheral. Again, power up and test. Follow this procedure
until a unit fails.
9. Consult your index of symptoms:
• Using your logbook, help desk database, or any relevant flow charts in reference
books and manuals.
10. Localise to a stage.
11. Isolate to the failed part.
12. Test and verify proper operation.

Remember that: After diagnosing and rectifying the fault, you need to document it in
the log book or help desk database for future reference.
A hardware fault-finding checklist
Here’s a useful checklist that you can use to help you diagnose faults in
hardware.
• First, consult any service level agreements (SLA) to ascertain if or
clarify response time obligations and internal/external responsibilities.
Determine also if there are there any other organisational guidelines
you need to follow.
• Consult documentation logged from previous related or similar
situations. Determine a set of questions can you ask the user, your
colleagues and your supervisor that might assist you in finding a
solution.
Cont.…
• Remember to keep safety as your highest priority by observing OH&S
precautions, that is, ensure your own safety first, and then consider other
precautions such as static discharge, etc.
• Check the power supply. Ensure it is working and that it is powering the
motherboard.
• If no video is displayed try swapping the monitor with a known good
one.
• If the video controller is built in, disable it and try another known
working video card. To disable the built in video controller you will
need to access the system CMOS or BIOS setup. On some systems,
simply inserting a new video card will automatically disable the built in
video.
Cont.…

Fig.4. video card

Cont.…
• Remove all expansion cards. If the machine boots, replace the cards
one by one until the problem reappears.
• Check the CPU fan is operating.
• Check the RAM chips by swapping them with known good ones.
• Check the motherboard for signs of blown components.
• If still no success, you might swap the entire motherboard and CPU.

Remember to document everything you do according to organisational

guidelines.
Is the problem with the hardware or the software?
• A computer system consists of a hardware sub-system and a software
sub-system.
• However, when looking for the cause of the fault, sometimes it can be
difficult to determine if the fault is hardware or software.
• Once you have determined that the fault is confined to one of these
two sub-systems, you can then isolate it, focus on the fault-finding
process, and rectify the fault.
Cont.…
• The easiest way to determine whether a problem is hardware or
software is to test the hardware with software packages that are
known to be good and that have successfully run on the system before.
• If the system boots and operates correctly, then the fault can be put
down to software.
• If the system does not boot or operate correctly then the fault can be
put down to hardware.
Configuration problems

• Configuration problems are problems that arise when a computer

system is set up for the first time or when new peripherals/components
are added to the system.
• When the component is first added, the system is not ready to receive
the hardware, until the system is prepared to support the device.
• This mismatch can be rectified by:
installing the appropriate software device drivers
configuring CMOS/BIOS
configuring the operating system.
The POST
• The Power On Self Test (POST) operates whenever a computer is
switched on.
• Whenever you start up the computer system, the computer
automatically runs a series of tests.
• At this time the computer tests the basic functionality of vital
components such as the CPU, RAM, video card, motherboard, and
input and output devices.
• POST tests are not particularly thorough, but they represent the first
line of defence, especially in handling severe motherboard problems.
Cont.…
• If the POST test finds a problem which is severe enough to keep the
system from operating properly, it halts boot up of the system and
produces audio beeps and/or error messages.
• You can find the meanings of these error signs in documentation from
the system manufacturer — this is often required for an accurate
understanding of audio beeps and messages.
• But if the POST fails, then at least you know the problem is hardware-
related.
The boot up process
• Carefully watching the steps in the boot process can reveal a lot about
the nature of problems in a system.
• By doing this you can include or exclude various possible causes of
faults.
• The absence of one or more of the following during booting can
indicate a fault:
When power is applied, the power supply fan should work.
The keyboard lights should flash as the rest of the system components are
reset.
A POST memory count and test should be seen.
A BIOS message should be visible on the monitor.
Cont.…
The floppy drive access light should come on briefly.
The hard disk access light should come on briefly.
An audible short beep should be heard.
The floppy disk access light should come briefly before a check of the hard
drive starts.
An operating system prompt, message, or logo should be visible.
• By observing the above sequence you should be able to work out
where the problem might be, that is, isolate the fault.
• For instance, if any of the above steps (except the last one) fails in
some regard, then you know the problem is hardware-related.
Hardware toolkit
• What equipment are you likely to need when carrying out the fault-finding? The most
useful tool, that you should never leave home without, is a good quality Philips-head
screwdriver. However, other tools in your hardware toolkit may include:
screwdrivers — a full set and range of sizes
anti-static strap
pointy-nose pliers
multimeter
known good components such as video card, cables, mouse, hard-disk drive, network
interface card (NIC), CD-ROM drive
serial and parallel loop-back connectors
boot disks
a range of testing software for the loop-back plugs and NIC
a POST card.
Cont.…
• A POST card is a device that plugs into an empty slot in the
motherboard.
• When the system boots up, the card runs a series of diagnostics.
• In some cases these cards replace the normal functions of the BIOS.
The great advantage of using these cards is that you do not have to
resort to software running off the hard drive or a floppy disk.
• POST cards are normally used when systems are ‘dead’, or when the
system cannot read from the hard drive or the floppy drive.
• Some POST cards also come with a series of light emitting diodes
(LEDs) that produce coded error signals that you could interpret
together with a manual. Other cards produce audio beep signals.
Cont.…

Fig.5. A POST card

Diagnostic software
• There is a wide range of diagnostic tools available that can help you
identify all sorts of computer problems.
• Generally, the diagnostic software used for testing system components
and/or performance falls into two categories:
 Generic
 Pproprietary.
Generic diagnostic software
• The generic tools available are usually sold as software packages and
are very limited.
• To evaluate the usefulness of generic software you have to assume that
the software supplier has tested their software with all original
equipment manufacturer (OEM) hardware and software you may want
to test.
• This is not to say the providers of these packages are supplying a
defective product — just that they can really only test the
functionality of devices and systems functions known to the
program writers and this will exclude many proprietary devices. A
good example of this would be network interface cards (NICs).
Cont.…
• Most of the generic diagnostic packages will probably be able to
determine that the NIC is installed in the system, however, if the exact
functionality instructions of the NIC are not built into the diagnostic
software, an accurate result will probably not be achieved.
• This is better understood when considering that the same NIC OEM
may provide a different diagnostics utility with each of many similar
NICs.
• If the wrong version of the diagnostics utility is tried with the wrong
NIC, even the most basic loop-back test will often fail. This highlights
the need to pay close attention to the software provided by OEMs.
Cont.…
• Another factor to consider is that general diagnostic software uses
information gained from the underlying operating system, which gains
its information from the BIOS.
• This means that the operating system (using its device driver) may not
be able to accurately provide information on the device. If the
information provided to the diagnostic software is not extremely
accurate, then valid test results are not a reasonable expectation.
• For truly accurate testing of a device you should use the software
provided by the manufacturer or use specialised diagnostic software
that can bypass the operating system all together.
Propriety diagnostic software
• If diagnostic software is operated on its own specially designed operating
system, then direct access (via the BIOS) to the hardware will likely yield
accurate and thorough details.
• Having unimpeded access to the low-level functions of the hardware
means the diagnostic software is able to run rigorous testing and reporting.
• After all, it’s unlikely that rigorous memory testing could be performed
while there are several other programs currently running in memory.
• Two examples of good diagnostic software are:
Micro-Scope Diagnostic Suite from Micro2000 (
http://www.micro2000.com/)
PC Certify Lite from Pro Tech Diagnostics (
http://www.protechdiagnostics.com/)
Common diagnostic tools
• All operating systems come with utilities that are used for general
checking, repair and reporting of faults.
• Each operating system is different but they do have some tools in
common such as hard disk scanning tools, e.g.
• Scandisk for Microsoft
• fsck (file system check) for Unix clones like Linux
• Disk First Aid for Apple MacIntosh systems.
Leave a trail to follow
• Apart from the use of diagnostic software (and a little trial and error) examining
documentation on past faults and their solutions can reveal a lot.
To give two examples:
The introduction of a new device (say a different brand of NIC) may bring with it
some configuration problems. If there is documented evidence of previous
problems, together with information on how the problem was solved, you can more
efficiently remedy similar problems. The remedy may come in the form of an
automated configuration file (script), or a decision to purchase less trouble-prone
devices.
The reports generated by some help desk software may indicate that a particular user
consistently experiences problems with certain devices, or software applications.
This information could then be used to reduce future incidents of support calls by
providing or recommending targeted training for that user. The term currently in use
for this is ‘just in time training’ (JIT).
Finding more information
• Experience, a logical approach and reviewing previously documented problems
and solutions, can form the backbone of being able to analyse and determine the
cause of system faults.
• However, there is always something new and no single person or group can form
the only valid source of good information. There will always be a need to
perform some research as a result of some fault or problem caused by hardware
or software. The Internet provides other sources of information that can be relied
upon.
• When you do research on the Internet, you should check the source of the
information, and bookmark (add to favourites) those that you consider valid and
useful.
• In the Research section of this Learning Pack you’ll find many websites to carry
out further research of the topics discussed here, including hardware-related and
software-related websites.
Summary
To be able to analyse and determine system faults you need to:
• have a general knowledge of how computers and individual
components should work
• use your senses to take in all the factors involved, eg sights, smell and
sounds
• take a logical approach using questioning, flow charts, checklists and
general guidelines
• have a good toolkit of both hardware and software tools
• use documentation on previous problems or faults generated by help
desk software.
Cont.…
You should also:
• know the factors that can adversely affect computers and components,
in order to prevent further problems occurring
• know where to find troubleshooting information at short notice
• document the fault and the resolution before the job can be considered
as finished
• keep calm while everything fails around you!
Identifying Vendor documentation, peer
organizations or research information
Assessing Vendor documentation Regarding to ISO
Standards
• Manufacturers should be able to demonstrate that they have a
commitment to environmental good practice, and that their equipment
has been designed with environmental impacts in mind.
• Most ICT equipment available in the world is manufactured overseas,
so there is limited opportunity to influence the design of the equipment.
• However, maintaining ICT equipment should require suppliers to
provide information on the steps being taken by the manufacturer to
reduce the environmental impact of their products.
• In some regions of the world, such as Europe and North America,
governments are increasingly regulating the manufacturing process to
reduce waste.
Cont.…
• Manufacturers are also starting to adopt Corporate Social Responsibility
(CSR), which recognizes an obligation to consider the interests of customers,
employees, shareholders, communities, and ecological considerations in all
aspects of their operations. This obligation is seen to extend beyond their
statutory obligation to comply with legislation.
• The Eco-Management and Audit Scheme (EMAS) is the EU voluntary
instrument which acknowledges organizations that improve their
environmental performance on a continuous basis.
• EMAS registered organizations are legally compliant, run an environment
management system and report on their environmental performance through
the publication of an independently verified environmental statement. They
are recognized by the EMAS logo, which guarantees the reliability of the
information provided.
Cont.…
• Fewer toxic components In January 2003 the European Parliament and
the Council of the European Union issued an RoHS (Restriction of
Hazardous Substances) Directive 2002/95/EC on the restriction of the
use of certain hazardous substances in electrical and electronic
equipment, and Directive 2002/96/EC on waste electrical and
electronic equipment.
• The two directives were designed to tackle the fast-increasing waste
stream of electrical and electronic equipment. Directive 2002/96/EC
requires increased recycling of electrical and electronic equipment to
limit the total quantity of waste going to final disposal.
Cont.…
• It also requires producers to take responsibility for taking back and
recycling electrical and electronic equipment. This is intended to
provide incentives for manufacturers to design electrical and
electronic equipment in an environmentally more efficient way, which
takes waste management aspects fully into account. Consumers should
be able to return their equipment free of charge.
• In order to prevent the generation of hazardous waste, Directive
2002/95/EC requires the substitution of various heavy metals such as
lead, mercury, cadmium and hexavalent chromium in new electrical
and electronic equipment put on the market from 1 July 2006.
Using recycled content

• In 1999 a computer supplier announced the world’s first desktop PC

using 100 per cent recycled plastic in all the plastic parts.
• However, it appears this was not commercially sustainable, and the
company’s 2006 Corporate Responsibility Report states that 28 per
cent (by weight) of all plastic resins contain recycled plastic content,
with a net recycled plastic content weight representing 8.1 percent of
total purchases (against a corporate goal of 5 per cent).
• The EU RoHS Directive precludes the use of some recycled materials
because of the use of substances such as flame-retardant bromides.
Some Examples of hard wares include:
LCD display screens
• Liquid crystal displays (LCDs) consume about half the power of an
equivalent-sized cathode ray tube (CRT) screen. LCDs also have direct
user benefits in terms of saving desk space, and they are better for your
health.
• CRT monitors radiate three electron beams that are continually refreshing
the entire screen 60 to 85 times each second. Although your brain doesn’t
register the constant refreshing, your eyes do, and they have to work harder
to absorb the information. LCD monitors don’t refresh in this way: pixels
are constantly on or off, which greatly reduces eye fatigue and strain.
• An LCD monitor also generates less heat than a CRT, lessening the air
conditioning loads in an office.
Desktop printers
• Desktop printers, while convenient for users, can be costly to maintain and
operate. On the other hand, when printers are networked and shared among
groups of users (the most common scenario), no one is responsible for
turning them off at night. Current good practice is to consolidate printing
functions into networked MFDs that are deployed on the basis of one per
floor.
• As noted above, MFDs have good power management tools and duplex
printing (both sides) can be set as a default.
• Desktop printers typically have less functionality than MFDs and only more
recent models have started to provide duplex printing as a default option.
• The Ministry for the Environment provides sustainability guidelines for
office consumables such as paper and ink cartridges.
Impact of ISO on ICT
• In the 1980s ISO began the work of devising “process” standards, specifically the
ISO 9000 Quality Management System standards.
• Firms in the ICT industry want to become ISO certified in order to improve their
business practices and retain business with certain customers.
• More than 90% of ICT companies worldwide work within the needs of
standardization. The term standardization is used in ICT companies to measure the
quality of their services.
• Applying ISO in ICT companies is considered to be significant in that it allows these
companies to implement the total quality management (TQM) strategy to improve
their organizational performance (Magd, 2006).
• ICT practices have used many ISO standards such as ISO 9001 QMS, ISO 20000
ITSM, ISO 27001 ISMS and other standards. For example, ISO 9001 QMS helps
bring out the best in organizations by enabling people to understand the processes of
delivering products/services to customers.
ISO’s Quality Management System
• It is a model for continual improvement and customer satisfaction, and
any organization looking to improve how it functions or does business
can use it, regardless of size or sector.
• ISO 20000 ITSM promotes the adoption of an integrated process
approach for effectively delivered managed services to meet business
and customer requirements.
• To take another example, ISO 27001 ISMS provides information to
responsible parties for establishing, implementing, operating,
monitoring, reviewing, maintaining and improving a documented
Information Security Management Systems (ISMS). It also designed to
ensure adequate security controls that protect information assets,
document ISMS and give confidence to customers and interested parties.
Obtaining User Requirements
• The User Requirement document is a specification of requirements
from the user point of view, and its contents are thus essentially
non‑technical.
• It is not mandatory for the specification to include any technical
elements. However, the users often do have technical requirements,
and when they do such requirements have to be included in the User
Requirement document. But even then they must be presented so as to
be capable of being understood by the non-technical reader.
• The users will usually rely upon the services of appropriate technical
advisors to help in the specification of such requirements.
Hardware requirements
• If hardware is to be supplied, it warrants its own detailed requirements
section. This should specify requirements in a little or as much detail
as the users care about the matter.
• A minimal specification might be concerned just with the general
nature, capacity and performance of the equipment to be provided.
• But the defined requirements might even, for reasons of compatibility
or standardization, go so far as to specify particular makes and models
of equipment, if that is what the user community wants.
Business requirements
• Business requirements, also known as stakeholder requirements
specifications (StRS), describe the characteristics of a proposed system from
the viewpoint of the system's end user. Products, systems, software, and
processes are ways of how to deliver, satisfy, or meet business requirements
Confusion arises for three main reasons.
• A common practice is to refer to objectives, or expected benefits, as 'business
requirements.'
• People commonly use the term 'requirements' to describe the features of the
product, system, software expected to be created.
• A widely held model claims that these two types of requirements differ only in
their level of detail or abstraction — wherein 'business requirements' are high-
level, frequently vague, and decompose into the detailed product, system, or
software requirements.
 Benefits of Business Requirements
Structured explanation of a business process or method defined early in the life cycle helps reduce
Reduce Project failure project failures that occur due to misaligned or misrepresented requirements leading to failure of
user expectations.
Well-defined business requirements help lay out a project charter, a critical step in executing
Connects to broader business business strategy or business goals, and to take it to the next logical step of developing it into an IT
goals system. This helps monitoring overall project health and provides for positive traction with key
project stakeholders including sponsors.

The benefit of a structured format typical of business requirements documentation helps create
Consensus creation and
positive consensus and better collaboration where the business stakeholder group might be a large
collaboration
cross-functional team, distributed geographically.

Good quality of business requirements when captured early on not only improves success of a
Saves costs project but also save overall costs associated with change requests, and related investments in
training, infrastructure, etc.
Difficulties of Business requirement
• Business requirements are often prematurely hardened due to the large
stakeholder base involved in defining the requirements, where there is
a potential for conflict in interests.
• The process of managing and building consensus can be delicate and
even political by nature.
• A lesser challenge, though common, is that of distributed teams with
stakeholders in multiple geographical locations. It is natural that sales
staff is closer to their customers, while production staff is closer to
manufacturing units; finance and HR, including senior management
are closer to the registered headquarters.
Identifying business needs

Includes the following steps:

• Business definition
• Understand business domain(s)
• Organization goals
• Core competence
Documenting Maintenance Procedures
• A maintenance procedure is only as good as its measurement data.
Poor data may be worse than no data at all because poor data may lead
to the wrong analysis, resulting in working on the wrong thing.
• One of the best ways to help ensure good data collection is to have
well-written procedures.
Why are Standard Maintenance Procedures
Necessary?
• To protect the health and safety • To increase equipment reliability
of employees. .
• To help ensure that everyone • To serve as a training document.
performs a task to the same • To help document the equipment
degree of precision. management procedure.
• To save time when performing a • To help protect the environment.
task.
• To provide a basis for accident
• To help ensure that standards and investigation
regulations are met.
• To minimize the effects of
personnel turnover.
What Information Should be Contained in a Standard
Maintenance Procedure?
• Formal title and document number.
• A statement reading: "Read all of the steps in this standard
maintenance procedure before beginning work."
• Personal protective equipment (PPE) required to do the job.
• All safety and environmental hazards to be aware of while doing the
job.
• A detailed list of steps for performing the job or task.
• A complete list of tools and materials for doing the job.
• References to other documents needed to perform the job.
Cont.…
• Photos and diagrams where needed to explain job steps.
• Measurements, standards and tolerances in the standard maintenance procedure steps.
• Any other important information that may help the worker complete the task in a
satisfactory manner.
• A definition of skills required for performing the job.
• Hours required to perform the job.
• Number of people required to perform the job.
• Required frequency of performing the job.
• Preparation and revision dates.
• Approval and review signatures.
• Space to provide feedback as to the accuracy and effectiveness of the standard
maintenance procedure.
THANK YOU!