M08 Maintenance Procedure
M08 Maintenance Procedure
Level-II
Based on March 2022, Curriculum Version 1
This unit defines the competence required to set up maintenance procedures to keep equipment
and software operating effectively and efficiently.
This module is designed to meet the industry requirement under the irrigation and drainage
occupational standard, particularly for the unit of competency: Implementing Maintenance
Procedure
This module covers the units:
Equipment and software maintenance
Revision of appropriate practices
Identification of maintainable IT components
Maintenance procedures
Learning Objective of the Module
Determine best practices for equipment and software maintenance
Revise practices, where appropriate
Identify and analyze IT system components to be maintained
Apply maintenance procedures
Module Instruction
For effective use this modules trainees are expected to follow the following module instruction:
1. Read the information written in each unit
2. Accomplish the Self-checks at the end of each unit
3. Perform Operation Sheets which were provided at the end of units
4. Do the LAP test giver at the end of each unit and
5. Read the identified reference book for Examples and exercise
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 behavior of a PC.
System unit Floppy disk drive activity Floppy disk drive mechanisms
indicator (light) Speaker (beep) Fan
Front panel indicators such as: Hard disk drive
Power on LED (light emitting
diode)
Hard disk drive activity
LED
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.
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. Dont turn a computer on and off several times every
day.
- 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.
Consult your index of symptoms:
- Using your logbook, help desk database, or any relevant flow charts in reference books
and manuals.
Localize to a stage.
Isolate to the failed part.
Test and verify proper operation.
After diagnosing and rectifying the fault, you need to document it in the log book or help desk
database for future reference.
Hardware toolkit
What equipment are you likely to need when carrying out the fault-finding? The most useful
tool, which 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
POST cards
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. Typically, a normal BIOS chip stops when theres a severe
error condition. POST cards can actually continue and go through a full testing cycle. 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.
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
Proprietary
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
The User Requirement document is a specification of requirements from the user point of view,
and its contents are thus essentially non-technical.
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.
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.
Such confusion can be avoided by recognizing that business requirements are not objectives, but
rather meet objectives (i.e., provide value) when satisfied. Business requirements whats do not
decompose into product/system/software requirement hows. Rather, products and their
requirements represent a response to business requirements presumably, how to satisfy what.
Business requirements exist within the business environment and must be discovered, whereas
product requirements are human-defined (specified).
Business requirements are not limited to high-level existence, but need to be driven down to
detail. Regardless of their level of detail, however, business requirements are always business
deliverable whats that provide value when satisfied; driving them down to detail never turns
business requirements into product requirements.
Business requirements are often listed in a Business Requirements Document or BRD. The
emphasis in a BRD is on process or activity of accurately accessing planning and development of
the requirements, rather than on how to achieve it; this is usually delegated to a Systems
Requirements Specification or Document (SRS or SRD), or other variation such as a Functional
Specification Document. Confusion can arise between a BRD and a SRD when the distinction
between business requirements and system requirements is disregarded. Consequently, many
BRDs actually describe requirements of a product, system, or software.
Description
Connect Broader business goal Well-defined business requirements help lay out a project
charter, a critical to step in executing business strategy or
business goals, and to take it to the next logical step of
developing it into an IT system. This helps monitoring overall
project health and provides for positive traction with key
project stakeholders including sponsors.
Consensus creation and collaboration The benefit of a structured format typical of business
requirements documentation helps create positive consensus
and better collaboration where the business stakeholder group
might be a large cross-functional team, distributed
geographically.
Name: Date:
Instruction: Answer all the questions listed below, if you have some clarifications- feel
free to ask your teacher.
A. Choose the correct answer from the given alternatives
1. Reasons why a computer might hang each time a specific software application is run
A. corrupted file C. hard disk failure
B. an incorrect installation D. All
2. During Power supply checking which question is correct?
A. Is the plug inserted snugly into the computer?
B. Is the power cord plugged into an appropriate wall power outlet?
C. Is the wall power outlet working?
D. All
3. Among the following which one is diagnostic tool?
A. Scandisk for Microsoft
B. fsck (file system check) for Unix clones like Linux
C. Disk First Aid for Apple MacIntosh systems
D. All
4. Which one is not hard ware toolkit?
A. Screwdrivers C. Anti-static strap
B. Anti-virus D. All
B. Write True if the statement is Correct and False if the statement is Incorrect
1. The Eco-Management and Audit Scheme (EMAS) is the EU voluntary instrument which
acknowledges organizations that improve their environmental performance on a continuous
basis.
2. Liquid crystal displays (LCDs) consume about half the power of an equivalent-sized cathode
ray tube (CRT) screen.
A service-level agreement (SLA) is a contract between a service provider and its internal or
external customers that documents what services the provider will furnish and defines the
service standards the provider is obligated to meet
Why are SLAs important?
Service providers need SLAs to help them manage customer expectations and define the
circumstances under which they are not liable for outages or performance issues. Customers
can also benefit from SLAs in that they describe the performance characteristics of the service,
which can be compared with other vendors' SLAs, and also set forth the means for redressing
service issues -- via service credits, for example. For a service provider, the SLA is typically
one of two foundational agreements it has with customers. Many service providers establish a
master services agreement to establish the general terms and conditions in which they will
work with customers. The SLA is often incorporated by reference into the service provider's
master services agreement. Between the two service contracts, the SLA adds greater specificity
regarding the services provided and the metrics that will be used to measure their performance.
What goes into an SLA?
In addition to establishing performance metrics, an SLA may include a plan for addressing
downtime and documentation for how the service provider will compensate customers in the
event of a contract breach. Service credits are a typical remedy. Here, the service provider
issues credits to the customer based on an SLA-specified calculation. Service providers, for
example, might provide credits commensurate with the amount of time it exceeded the SLA's
performance guarantee.
A service provider may cap performance penalties at a maximum dollar amount to limit
exposure.
The SLA will also include a section detailing exclusions, that is, situations in which an SLA's
guarantees -- and penalties for failing to meet them -- don't apply. The list might include events
such as natural disasters or terrorist acts. This section is sometimes referred to as a force
majeure clause, which aims to excuse the service provider from events beyond its control.
Who needs a service-level agreement?
SLAs are thought to have originated with network service providers, but are now widely used
in a range of IT-related fields. Companies that establish SLAs include IT service providers,
managed service providers and cloud computing service providers. Corporate IT
organizations, particularly those that have embraced IT service management (ITSM), enter
SLAs with their in-house customers -- users in other departments within the enterprise. An IT
department creates an SLA so that its services can be measured, justified and perhaps
compared with those of outsourcing vendors.
Automobile manufacturers recommend having an engine tuned and oil changed regularly to keep
a car running as efficiently as possible. Similar maintenance is required of a computer system. It
is best not to wait until problems arise-avoid problems in the first place! An organization can
carry out much of its own routine, preventive maintenance (e.g., checking database size, purging
outdated records, and deleting idle user accounts), but in spite of efforts to deliver a high-quality
preventive maintenance program, problems will still occur. To deal with them, many
organizations have maintenance agreements with outside contractors for fix-it-when-it-breaks
service, particularly for hardware. The key factors in these agreements are response time to a
trouble call and the availability and proximity of spare parts. In other words, planners need to
know how long it will take to get the problems fixed when (not if) they arise.
When a maintenance program is successful, every area of the company is positively affected.
Today, top organizations are reaping the benefits from implementing well- designed and
Create a lean and effective oil analysis program. Oil analysis is a powerful tool in a
maintenance program. This case study presents alternatives to expensive in-house test
equipment, good utilization of outside labs, oil storage solutions, methods of reporting findings
to further the program, and selling the program to upper management as well as to operations
and maintenance.
Put maintenance checklists to use. While most groups will say they have checklists, requiring
their use and the accountability are often major factors for success. In your organization, what
processes do you have in place to ensure that people use maintenance procedures and checklists?
Avoid the 5 biggest risks. Asset management is an integrated approach to optimizing the life
cycle of your assets, beginning at conceptual design, through to usage, decommissioning and
disposal. By acknowledging and paying attention to these five primary risks to effective asset
management, you can put in place plans to mitigate the effects these might have on their
program.
Give maintenance technicians equipment ownership. How do you strike a balance between
equipment ownership and building the skills through cross training, and having the ability to get
the work done all the time? Is it based on the culture of the organization?
Instruction: Answer all the questions listed below, if you have some clarifications- feel free to
ask your teacher.
I. Write True if the statement is Correct and False if the statement is Incorrect
1. The Monitoring Maintenance Lifecycle is a monitoring development process to reduce
maintenance costs.
2. Monitoring Maintenance Lifecycle are methods and standards for improving and
mastering maintenance processes.
3. Optimize PM tasks
• General: Legally binding assurance (which may or may not be in writing) that a good or
service is, among other things, fit for use as represented, free from defective material and
workmanship, meets statutory and/or other specifications. A warranty describes the
conditions under, and period during, which the producer or vendor will repair, replace, or
other compensate for, the defective item without cost to the buyer or user. Often it also
delineates the rights and obligations of both parties in case of a claim or dispute.
Contracting: Expressed or implied undertaking that a certain fact regarding the subject
matter of a contract is, or will be, true.
Unlike conditions (the central points), warranties are deemed incidental points, and a breach
of warranty is usually not a valid reason for voiding a contract but it entitles the aggrieved
party to damages. See also in nominate term and intermediate term.
Insurance: Written pledge by the insured party that a specified condition exists or does
not exist. Breach of warranty entitles the insurer to treat the insurance contract as void even if
the actual loss is unaffected by the breach. See also representation.
ICT equipment companies guarantees that all the products undergo backbreaking quality
control testing before delivery and installation. In the event that any product of these
manufacturers is found to be defective, the company will provide service for product repair
and/or component replacement as may be necessary within the warranty period as per the
terms mentioned here under.
Give general description of the system, from the point of the user:
In what environment it works (home, near patient bed, operating rooms .)
• Who the users are
What it is for
The main functions
The main interfaces, input and outputs
If your software is integrated in a large system, you may reference a document that
describes this system.
Physical architecture overview
Describe the hardware components on which software runs and their
interactions/relationships
Use components diagrams, deployment diagrams, network diagrams,
interface diagrams…
Hardware Component description
Describe the content of each hardware component in the architecture
- Its identification
- The purpose of the component
- The software component it receives
- Its technical characteristics: type of machine, CPU, RAM, disk and so on.
- Its network hardware interfaces
Logical architecture overview
- Describe the top level software components and their interactions/relationships.
- Use UML package diagrams and/or layer diagrams and/or interface diagrams.
- Describe also the operating systems on which the software runs.
Software Component description
Describe the content of each top-level software component in the architecture the
description should contain:
- Its identification
- The purpose of the component,
- Its interfaces with other components,
Workflow / Sequence 1
Describe here the workflow / sequence of a main function
For example, the user queries data, what happens, from his terminal to the database?
Workflow / Sequence 2
Repeat the pattern for each main function of the system
3.1.2. System architecture capabilities
Describe here the rationale of the hardware / software architecture in terms of
capabilities:
- Performances (for example response time, user mobility, data storage, or any
functional performance which has an impact on architecture)
- User / patient safety
- Protection against misuse
- Maintenance (cold maintenance or hot maintenance),
- Adaptability, flexibility
- Scalability, availability
- Backup and restore
- Hardware and Software security: fault tolerance, redundancy, emergency stop,
recovery after crash
- Administration,
- Monitoring, audit
If the results of human factors analysis have an impact on the architecture, describe here
for each risk human factors output what has been done to mitigate the risk in the
architecture.
Computer hardware
This is the physical technology that works with information 66. Hardware can be as small as a
smart phone that fits in a pocket or as large as a supercomputer that fills a building. Hardware
also includes the peripheral devices that work with computers, such as keyboards, external disk
drives, and routers. With the rise of the Internet of things, in which anything from home
appliances to cars to clothes will be able to receive and transmit data, sensors that interact with
computers are permeating the human environment.
Computer software
Telecommunications
This component connects the hardware together to form a network. Connections can be through
wires, such as Ethernet cables or fibber optics, or wireless, such as through Wi- Fi. A network
can be designed to tie together computers in a specific area, such as an office or a school,
through a local area network (LAN). If computers are more dispersed, the network is called a
wide area network (WAN). The Internet itself can be considered a network of network.
Instruction: Answer all the questions listed below, if you have some clarifications- feel free to
ask your teacher.
I. Write True if the statement is Correct and False if the statement is Incorrect
1. A warranty describes the conditions under, and period during, which the producer or
vendor will repair or replace defective item without cost to the buyer or user.
2. ICT equipment companies guarantees that all the products undergo backbreaking quality
control testing before delivery and installation.
3. Pledge by the insured party that a specified condition exists or does not exist
A. Bandwidth
B. Inconsistent Data
C. Cyber security
D. All
- Not all troubleshooting processes are the same, and technicians tend to refine their
own troubleshooting skills based on knowledge and personal experience.
Hardware Maintenance
Software Maintenance
Review updates
Create a schedule
The first and last steps involve effectively communicating with the customer.
Data Protection
“What types of problems are you having with your computer or network?”
then, ask closed-ended (yes/no) questions “Have you changed your password recently?”
If this step turns up nothing, continue to the next step of the troubleshooting process.
Document it and proceed to the end of the troubleshooting process. Fig 1.6. Solution
When system, user, or software errors occur on a computer, the Event Viewer is updated with
information about the errors:
- Event ID number
Although this utility lists details about the error, you may still need to research the solution.
when troubleshooting, power on the computer and listen to the beep code sequence. Document
the beep code sequence and research the code to determine the specific hardware failure.
If the computer boots and stops after the POST, investigate the BIOS settings to determine
where to find the problem. Refer to the motherboard manual to make sure that the BIOS settings
are accurate.
Have the customer confirm that the problem has been solved
Document everything that you try, even if it fails. The documentation that you create will
become a useful resource for you and other technicians.
While it requires minimal planning, the drawbacks of reactive maintenance can be substantial if
its not carried out correctly. If the approach is used for all equipment, there can be huge delays
in production when a critical piece of equipment fails. Further, if you don’t have the right parts
and supplies on hand, the costs for rushed shipping can become significant. In short, reactive
maintenance often means more downtime and higher maintenance costs when its not used
strategically.
Also known as proactive maintenance, this method involves periodically taking assets offline
and inspecting or repairing them at predetermined intervals (usually time or event-based
triggers). The goal of this approach is to extend the useful life of an asset and prevent
breakdowns from occurring.
Many organizations employing preventive maintenance use CMMS software to trigger work
orders when a PM is due. This allows a facility to automate much of its scheduling efforts, which
is a key ingredient of this preventive approach. Because planning is done in advance, its much
easier to have the right parts and resources on hand to complete each task.
With all maintenance types, there are potential drawbacks to relying solely on preventive
maintenance. If the PM schedule isnt regularly monitored, audited, and improved, PM
creep can occur. This is when technicians get bogged down by unnecessary tasks and cost the
organization time and money.
Similarly, performing too many PMs can open the door for post-PM breakdowns. There are a
number of ways to prevent this, but the risk gets higher as PMs Get more frequent. The bottom
line is, if a preventive maintenance program is used, it should go hand in hand with PM
optimization.
Predictive maintenance (PdM) aims to predict failures before they happen so maintenance can
occur at just the right time. PdM uses data from machine sensors and smart technology to alert
the maintenance team when a piece of equipment is at risk of failing. For example, a sensor may
use vibration analysis to alert the maintenance team that a piece of equipment is at risk of failing,
at which point it will be taken offline, inspected, and repaired accordingly.
It is possible to carry out PdM via visual inspections of equipment, but the easiest way to
establish a predictive maintenance strategy is by using a CMMS to track meter readings. The
advantage of PdM (over PM) is the potential for cost savings from reduced man-hours spent on
maintenance, and more insight as to the performance and potential issues arising with the
machine. Additionally, a reliance on data and sensor information means maintenance is
determined by the actual condition of equipment, rather than a best-guess schedule or gut feel.
Of course, relying so heavily on data means that there is a higher up-front cost to ensuring this
maintenance approach can thrive. Another thing to keep in mind with predictive maintenance is
that you have to walk before you can run. For an organization coming from a pen-and-paper or
Excel- based maintenance program, you have to first build on the processes and insights that
preventive maintenance provides in order to build an effective predictive maintenance plan.
RCM is considered complex because each individual asset must be analysed and prioritized
based on criticality. The most critical assets are those that are likely to fail often or will result in
large consequences in the event of failure. Because each piece of equipment is analysed on its
own, its possible that the end result of embarking on an RCM effort is having as many different
maintenance plans as you do pieces of equipment.
RCM is very sophisticated, to the extent where it is not a realistic or necessary technique for
every organization. Its requires a very mature maintenance team that has mastered prevention,
basic inspections, predictive maintenance, and has access to lots of existing data on their assets.
Document approvals are formalized processes that you use to track the development of a
whole document. Using document approvals, you can route documents for approval, monitor the
approval process from person to person, log who approved or denied the document, and review
suggestions that they made about the document. The process facilitates a more detailed control of
a document and helps ensure that the contract is within standards of individuals and groups in an
organization.
Document approvals use approval framework. For document approvals, the approval process ID
that you use must be named Document. The approval framework supports multiple approvers
who can be notified at the same time, creating parallel approval paths. Approvers can approve or
deny transactions and assign ad hoc reviewers or approvers for the transaction. When the
approval process is complete, the system updates the document as approved or rejected. Supplier
Contract Management also incorporates an optional clause-level approval stage so that the
system can automatically include appropriate individuals in an approval process based on the
presence or modification of specific contract clauses.
During the approval process, approvers can add other approvers or reviewers to the current or a
later stage of the approval process. For example, if an author wants input from an inventory
analyst, she can add the analyst as an approver. This is called ad hoc approval. It applies only to
the approval instance in which the addition occurs and does not affect the overall approval flow.
Only the approver who adds an ad hoc approval can delete it.
An author can also be a document approver. Document writers approving their own documents
are called self-approval. A check box setting on the Approval Process Definition page enables
An administrator can manage approvals by reassigning those that do not have alternates defined
for their approval. You can enter criteria to limit the number of approvals that the system
displays.
The approval processing of documents can also include enabling internal users to digitally sign
documents at the same time they approve the document if the installation and document type
settings dictates signatures are to be captured for this document during approvals. You can
configure the system to capture internal signatures before, during, or after approvals.
Preview Approval
Select to view a list of approvers based on the approval process definition.
Make comments about the document before continuing the approval process.
Orientation is important because it lays a foundation for the users in the department. First
impressions are important since they establish the basis for everything that follows. Without
orientation, users sometimes feel uncomfortable in his/her activities and take longer to reach
his/her full potential.
Encourages users confidence and helps the new user adapt faster to the job;
For smooth, safe and successful maintenance work a prior risk assessment has to be carried out.
A risk assessment is a careful examination of what could cause harm to people, allowing one to
judge whether there are enough precautions in place or more if more are needed to prevent harm.
It involves identifying the hazards present in any undertaking (whether arising from work
activities or from other factors, e.g. the layout of the premises) and then evaluating the extent of
the risks involved, taking into account existing precautions Potential hazards could be: dangerous
substances, confined spaces, working at height, awkward positions, plant under pressure, moving
parts of machinery, unexpected start-ups, chemical substances or dust in the air, stress,
communication problems, etc. Outsourcing and subcontracting should be afforded special
consideration and the risk assessment should include both perspectives as well as any problems
with work arrangements and communication.
The results of a suitable and sufficient risk assessment should enable to choose which good
practice measures are most appropriate in preventing risks in general and also in preventing
risks to any individuals identified as being particularly at risk. The implementation may mean
making changes to the organization and working procedures, working environment, equipment
and products used. Changes could also be necessary in training management and staff as well as
improving communications.
Employees and their representatives should be involved in the carefully planned adoption
of any policies and measures, as a key component of success. This should include coordination
and communication between the contractor and service company personnel. The general
principle, also laid down by the respective EU directives, is that risks should be prevented at
source and that work organization, tasks, equipment and tools should be adapted to workers in
order to eliminate and reduce risks. Measures should follow the prevention hierarchy:
Elimination of risks
This means for example that personal protective equipment has only to be seen as last resort.
There have to be periodic reviews to check that measures, policies and procedures remain
appropriate and are working and revised if necessary.
Based on the conducted risk assessment the following issues need special attention:
A qualification level has to be determined for the specific repair and maintenance tasks. It
may be necessary to put a permission system in place, only giving specifically trained
people access to sensitive and dangerous areas. The issuing of permits for work and lock-
off systems has also to be considered. A permit to work should detail the work to be done
and the precautions to be taken.
Enough time and appropriate resources have to be allocated. Stress and unsuitable tools
may lead to errors, unsafe situations and prolonged down times.
Coordinating panels involving the service company have to be set up while the means
and paths of communication between all stakeholders need to be established carefully.
Comprehensive instructions should be provided. For complicated tasks written work
orders should be issued and discussed with the workers.
Ensuring instructions, qualification and further education of the workers performing maintenance
tasks is another important planning issue. With buildings and machines becoming more and more
sophisticated, and maintenance also being seen as a means to improve technology, maintenance
staffs need to keep up with this development. Employees should be given the opportunity to not
only develop their knowledge but to also bring in their experience. This is all the more important
as maintenance tasks can always bring about situations of unplanned and unforeseeable danger
and workers need to make use of all their knowledge and skills to manage these situations safely.
It also plays an important role in changing risky behaviour on behalf of the workers. However, in
this aspect it is also of utmost importance that all superiors set a good example and always
follow the determined rules themselves.
It might also be necessary to seek advice from outside experts, if the company does not have
sufficiently qualified personnel.
Maintenance workers and their representatives should already in the planning stage look to it,
that the outsourcing issue is considered sufficiently:
Outside workers are usually less familiar with the company-specific layout and
construction of machinery and plants; special instructions are needed.
Communication between own and outside workers may be problematic with regards to
time, language and organisation; special monitoring as to understanding of measures is
necessary.
Only authorized personnel should be allowed to do repair or maintenance work. This becomes all
the more important when the machines and structures are more sophisticated. Only then can it be
guaranteed that the right steps are followed and the correct equipment is used.
The work area needs to be secured by preventing unauthorized access, for example, by using
barriers and signs and safe routes, which have to be established for workers to enter and exit the
work area.
Structures and machines have to be cut off from any energy sources, such as power supplies and
pressure hoses using special locks, whereby only the maintenance workers and their supervisors
have the keys necessary for doing this. Warning signs should be attached to machinery, with the
date and time of lock-off, as well as the name of the person authorized to remove the lock. In this
way, the safety of the worker performing the maintenance on the machine will not be jeopardized
by another worker inadvertently starting it up.
Any residual energy should be safely discharged (e.g. an exhaust system for decompression of
gases and liquids may be necessary) and it should be considered that some machine parts may
need additional time to move into their home position. This has to be indicated in the machines
manual. The essential health and safety requirements of machines and plants have to be met with
regards to maintenance. They have been established by the Council Directive 2006/42/EC on
machinery.
Sometimes, it can be necessary to conduct the repair or maintenance work at running machines.
In this case special measures have to be taken:
If that is not possible, special protection devices have to be used (special tools, mobile
switches), the speed of the machine has to be reduced, and special covers for dangerous
areas have to be provided.
If this should, in some very special cases, not be possible, special measures have to be
taken based on a detailed risk assessment. Supervision must be provided throughout the
process.
According to statistical data, the next largest cause of accidents during maintenance – after
„getting injured at running machines‟ – is, „falling from heights‟. This clearly shows that in
addition to improving the design of structures, machines and plants in order to provide easier
access for maintenance and repair, it is very important that maintenance workers have safe
Stationary steps (fitted with slip resistant material) and work platforms with guards
(secured against unauthorized access)
Maintenance work often requires contact with a variety of substances, many of them hazardous:
Cleaning and lubricating agents should be selected carefully e.g. using selection tools
such as GISBAU CatSub or Clean tool, in order to use substances with the least impact
on human health.
During the work time, gases, smokes and vapors may occur, e.g. by releasing pressure,
cleaning surfaces or welding and soldering. When appropriate, quantitative
measurements should be taken. Workers or supervisors can also be equipped with test
tubes. Appropriate exhaust systems have to be put in place and comfortable personal
protection equipment has to be provided.
If liquids flowing from machines or plants cannot be avoided during maintenance work,
workers have to have proper instructions and equipment to handle these (exhaust, skin
protection, etc.).
Work often produces or raises dust. The risk assessment will indicate as to whether there
is any asbestos risk present (brake linings, sealing, insulations). In this case, very special
measures have to take.
Flammable substances as well as welding and soldering will also involve the danger of
fires and explosions. (Dust too, when getting airborne, can lead to explosions). This
requires special equipment (e.g. non-sparking tools) and related instructions.
Instruction: Answer all the questions listed below, if you have some clarifications- feel free to
ask your teacher.
D. All
D. All
A. Working Correctly
C. Acting incorrectly
D. All
II. Write True if the statement is True and Write False if the statement is incorrect
2. RCM is very sophisticated, to the extent where it is not a realistic or necessary technique
for every organization
4. Reactive maintenance often means more downtime and higher maintenance costs when
its not used strategically.