15.07.2013 Views

Download - Royal Australian Navy

Download - Royal Australian Navy

Download - Royal Australian Navy

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Applying Reliability-<br />

Centred Maintenance to<br />

Mechanical, Electrical,<br />

Electronic and Structural<br />

Systems<br />

Introduction<br />

In the March edition of <strong>Navy</strong> Engineering Bulletin, the benefits of<br />

applying Reliability-centred Maintenance to Naval assets were explored.<br />

It was shown that there is now a large body of experience in Defence to<br />

demonstrate that SAE JA 1011 compliant RCM (such as RCM2 and Def<br />

Stan 02 45) produces a maintenance programme which reduces the<br />

high cost of traditional naval maintenance without sacrificing system<br />

availability or reliability. Ongoing benefits in the <strong>Royal</strong> <strong>Navy</strong> for applying<br />

RCM to the majority of platforms and systems are expected to be in<br />

excess of £50M per annum.<br />

The article explained that true<br />

RCM involves answering seven<br />

structured questions about the<br />

asset or system under review:<br />

• What are the functions of the<br />

asset in its present operating<br />

context?<br />

• How can the asset fail to fulfil<br />

each function?<br />

• What would cause each<br />

functional failure?<br />

• What happens when each failure<br />

occurs?<br />

• In what way does each failure<br />

matter?<br />

• What can be done to predict or<br />

prevent each failure?<br />

• What should be done if no<br />

suitable proactive task can be<br />

found?<br />

Through the first four questions,<br />

RCM defines functional<br />

requirements, including<br />

performance standards, defines<br />

what we mean by ‘failure’ and<br />

completes a Failure Modes and<br />

Effects Analysis (FMEA) for the<br />

asset in question. The fifth<br />

question determines failure<br />

consequence and determines<br />

how each failure matters. The four<br />

RCM consequence types are<br />

‘Hidden, Safety, Environmental,<br />

Operational (loss of mission in<br />

the naval sense) and Non-<br />

Operational. The last two<br />

questions enable the appropriate<br />

failure management policy to be<br />

developed.<br />

These seven questions can only<br />

be answered by people who know<br />

the asset best – the maintainers<br />

and operators supplemented by<br />

specialist input where<br />

appropriate.<br />

Readers of <strong>Navy</strong> Engineering<br />

Bulletin have requested more<br />

information about the<br />

applicability of this process to the<br />

complete range of systems and<br />

subsystems which make up<br />

modern platforms and weapon<br />

systems. This article shows that<br />

NAVY ENGINEERING BULLETIN SEPTEMBER 2003<br />

the RCM process applies equally<br />

well to mechanical, electrical,<br />

electronic systems and naval<br />

structures and reviews the value<br />

of a comprehensive RCM<br />

database.<br />

RCM and Failure Management<br />

Before we can understand how<br />

RCM can be applied ‘across the<br />

board’, we must try to understand<br />

both the nature of failure and the<br />

decision-making logic involved in<br />

undertaking SAE compliant RCM.<br />

The six failure patterns<br />

The starting point is the six failure<br />

patterns described in the March<br />

issue, reproduced in Figure 1.<br />

These patterns, which are<br />

fundamental to understanding<br />

maintenance programme<br />

development, show the possible<br />

ranges of failure mode behaviour<br />

and are plots of conditional<br />

probability of failure (vertical axis)<br />

against time in service (horizontal<br />

axis). They arise from a large body<br />

of failure analysis conducted in<br />

BY DR ALUN ROBERTS, THE<br />

ASSET PARTNERSHIP<br />

37

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!