05.03.2014 Views

Development and Implementation of a Fatigue Management ... - ICMM

Development and Implementation of a Fatigue Management ... - ICMM

Development and Implementation of a Fatigue Management ... - ICMM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

<strong>Development</strong> <strong>and</strong><br />

implementation <strong>of</strong> a<br />

<strong>Fatigue</strong> Risk <strong>Management</strong><br />

System (FRMS)<br />

Dr Alex<strong>and</strong>ra Holmes


Overview<br />

What is an FRMS?<br />

Why do I need an FRMS?<br />

How do I get started?


Terminology<br />

•<strong>Fatigue</strong> <strong>Management</strong> Programme (FMP)<br />

•Alertness <strong>Management</strong> Programme (AMP)<br />

•<strong>Fatigue</strong> Risk <strong>Management</strong> Programme (FRMP)<br />

•<strong>Fatigue</strong> <strong>Management</strong> System (FMS)<br />

•Others....


What is an FRMS?<br />

“A data‐driven means <strong>of</strong> continuously monitoring <strong>and</strong><br />

managing fatigue‐related safety risks, based upon<br />

scientific principles <strong>and</strong> knowledge as well as operational<br />

experience that aims to ensure relevant personnel are<br />

performing at adequate levels <strong>of</strong> alertness.”<br />

ICAO SARP Annex 6, Part 1 (2011)


Components <strong>of</strong> an FRMS<br />

FRMS Policy<br />

Effective Reporting System<br />

<strong>Fatigue</strong> Risk <strong>Management</strong> (FRM) Processes<br />

FRMS Safety Assurance Processes<br />

Data Collection & Hazard<br />

Identification<br />

Performance Monitoring &<br />

Continuous Improvement<br />

Risk Assessment<br />

Safety<br />

Performance<br />

Indicators<br />

(SPI)<br />

Managing changes that may<br />

impact on the FRMS<br />

Risk Mitigation<br />

Annual FRMS<br />

Audit <strong>and</strong> Review<br />

Communication: Safety Promotion & Feedback<br />

<strong>Fatigue</strong> <strong>Management</strong> Training Program (FMTP)


An FRMS is not...<br />

• work <strong>and</strong> rest time limitations e.g. national drivers hours<br />

rules, organisational limits<br />

• a scientific study e.g. <strong>of</strong> a fatigue monitoring device<br />

• isolated fatigue management initiatives e.g. the provision<br />

<strong>of</strong> a napping facility, schedule change<br />

• a fatigue management plan e.g. sleep contract, individual<br />

return to work plan<br />

• fatigue management training<br />

• fatigue modelling s<strong>of</strong>tware


Why do I need an FRMS?<br />

1. Requirement or recommendation<br />

• Regulatory, organisational or contractual<br />

requirement or recommendation<br />

2. <strong>Fatigue</strong> is a recognised safety risk<br />

• We are having fatigue-related safety events<br />

• Our existing efforts to mange fatigue are not<br />

effective<br />

• Employees undertaking safety critical tasks <strong>and</strong><br />

working shift work <strong>and</strong>/or extended hours


3. Other benefits<br />

Why do I need an FRMS?<br />

• Reduced absenteeism, improved health, retention,<br />

morale, efficiency <strong>and</strong> reputation<br />

• Operational advantage


How do I get started? <strong>Implementation</strong> plan<br />

1. Review existing materials on FRMS<br />

• API, <strong>ICMM</strong> Australia, ICAO, UK DfT, Transport Canada etc<br />

2. Gain top-level endorsement<br />

• management need to want to know what is really going on<br />

• recognise that it will be uncomfortable


<strong>Implementation</strong> Plan<br />

3. Appoint a fatigue champion<br />

• with operational knowledge<br />

• who reports directly to senior management<br />

4. Gap analysis<br />

• undertake a gap analysis against the relevant<br />

requirements or recommendations


5. Assess the current situation<br />

• fatigue model analysis <strong>of</strong> schedules<br />

• actigraphy <strong>and</strong> sleep diary studies<br />

• hazard identification <strong>and</strong> risk<br />

assessment workshops<br />

• analysis <strong>of</strong> incident <strong>and</strong> accident<br />

databases<br />

• employee fatigue surveys


Actigraphy


Sleep/activity diary


<strong>Implementation</strong> Plan<br />

4. Strategic Planning<br />

• State your case <strong>and</strong> goal<br />

• Determine how much will be spent <strong>and</strong> what the<br />

indicators <strong>of</strong> success will be<br />

• Develop a timeline<br />

5. Communicate the plan <strong>and</strong> create ownership


Conclusion<br />

• What is an FRMS?<br />

• Why do I need an FRMS?<br />

•How do I get started?


Advice for those implementing FRMS<br />

For regulators<br />

“Do it with industry not to them”<br />

For operators<br />

FRMS is a change management issue:<br />

there will be resistance like any other<br />

change<br />

Need to win over hearts <strong>and</strong> minds Important that it becomes a living<br />

document; not simply policy on paper<br />

FRMS is complex but you need to<br />

keep it as simple as possible<br />

Important to raise awareness for<br />

all relevant parties<br />

Shouldn’t be rushed<br />

Requires a mature safety culture<br />

Requires management commitment<br />

Important to have a fatigue champion<br />

FRMS manager needs operational<br />

knowledge


What are the objectives <strong>of</strong> my FRMS?<br />

• Compliance<br />

• Enhanced safety – reduced accidents<br />

• Systematic risk management processes<br />

• Improved health, retention morale etc


<strong>Fatigue</strong> Causes & Consequences<br />

Job Factors<br />

Individual<br />

Factors<br />

<strong>Fatigue</strong><br />

Human<br />

Performance<br />

Health<br />

Operational<br />

Performance<br />

Roster<br />

Timing<br />

Individual<br />

Factors<br />

Operational<br />

Performance<br />

Duration<br />

Rotation<br />

Predictability<br />

Time zones<br />

Work<br />

Factors<br />

Traits<br />

· e.g. health<br />

· medications<br />

· chronotype<br />

Lifestyle<br />

· e.g. sleep<br />

environment<br />

· recreation<br />

· second job<br />

· domestic<br />

situation<br />

FATIGUE<br />

Human<br />

Performance<br />

Mood<br />

Communication<br />

Memory<br />

Health<br />

Cardiovascular<br />

Gastrointestinal<br />

Well-being<br />

Incidents<br />

Insurance<br />

Absenteeism<br />

Productivity<br />

Costs<br />

Morale<br />

Workload<br />

Vigilance<br />

Retention<br />

Job design<br />

Opportunity<br />

for naps<br />

Problem solving<br />

Risk taking<br />

Reputation<br />

Environment<br />

Reaction time


Objective data on fatigue?<br />

Despite many recognising fatigue as an issue, there is<br />

currently limited objective data on:<br />

- Scale <strong>of</strong> the problem;<br />

- Contributors;<br />

- At-risk groups;<br />

- Consequences for safety <strong>and</strong> productivity.


Clockwork Research<br />

Specialists in effective fatigue risk management<br />

Independent – impartial, credible advice<br />

Experienced team providing ground level support<br />

Develop <strong>and</strong> deliver strategies for managing fatigue risk<br />

Translate academic research into operational solutions<br />

Experienced trainers<br />

© Clockwork Research Ltd, 2011


<strong>Fatigue</strong> models<br />

• There are many available e.g. FAID, FAST, HSE Index,<br />

CAS<br />

• Carefully identify which model is most appropriate for<br />

your organisation (science, usability, cost, ongoing<br />

development)<br />

• Independent reviews e.g. CASA, Rio Tinto, Rail Safety<br />

Alert<br />

• A fatigue model can lead to poor fatigue management<br />

<strong>and</strong> bad decision making – ensure you underst<strong>and</strong><br />

what the model predicts badly <strong>and</strong> it’s limitations<br />

• Different models will output different results

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

Saved successfully!

Ooh no, something went wrong!