12
1 Failsafe Failsafe Start/Finish Start/Finish Paul Hopkins Paul Hopkins

Failsafe and systems start and finish

Embed Size (px)

Citation preview

11

FailsafeFailsafeStart/FinishStart/Finish

Paul HopkinsPaul Hopkins

22

Future

Assurance (against)

Incidents (of)

Liability

Systems

Accountability

Foundation

Evolution

Forward thinking and learning from the past

Providing protection for all involved

Avoiding another negative occurrence

Consequences of occurrence

Policies, audits and dissemination

Everyone has a responsibility

Underpinning systems to prevent and protect

Always developing

33

The role Overall Failsafe (via all), throughout multi-disciplinary teams

and other connected parties

Lead person to identify possible risk

Lead person to implement and communicate changes to avoid future negative reoccurrence

Audit analysis to identify trends and improve

Cascade trends to service users

44

Diagnosis of. Diagnosis of. Who is? Who is?

This still constitutes a significant part of Failsafe.This still constitutes a significant part of Failsafe.

Held in the system for a prolonged period?Held in the system for a prolonged period?

Where does this fall within Failsafe? Should this form an Where does this fall within Failsafe? Should this form an sprcific group?sprcific group?

QualificationQualification

55

Making the Start LineMaking the Start Line

Set the guidelinesSet the guidelines

Criteria (Benchmark – KPI’s)Criteria (Benchmark – KPI’s)

Regularly checked against the unit?Regularly checked against the unit?

Is this the start of Failsafe?Is this the start of Failsafe?

Do the KPI’s reflect good Failsafe (timelines, benchmarks % Do the KPI’s reflect good Failsafe (timelines, benchmarks % etc)?etc)?

66

RunningRunning

Clearly defined and well marshalled by quality standardsClearly defined and well marshalled by quality standards

1.1. Short distance = ??Short distance = ??

2.2. Long distance = ??Long distance = ??

3.3. Relay = Excellent communication between all partiesRelay = Excellent communication between all parties

Good relay practice between parties promotes safety for all, Good relay practice between parties promotes safety for all, also: cost, time and overall efficiency)also: cost, time and overall efficiency)

77

InjuryInjury

Fracture in practiceFracture in practice

Injury = Referred to another race (Fracture in practice)Injury = Referred to another race (Fracture in practice)

Who should communicate during Injury?Who should communicate during Injury?

Systems need to remain linkedSystems need to remain linked

88

The future

Reduced finances - Costs spiral

Budget cuts: services need to cost improve

Additional demand within services

Need thorough efficiency in all aspects of Failsafe

To protect future services and service users

99

Future

Assurance against

Incidents (of)

Liability

Systems

Accountability

Foundation

Evolution

Forward thinking, together

Providing protection for all involved, together

Avoiding any negative occurrences, together

Monitor Consequences of occurrence and minimise, together

Policies, audits and disseminate, together

We are all responsible, together

Underpin systems to prevent and protect, together

Continually develope, together

Due to the future demands, Failsafe within services needs to consolidate……

1010

FinishFinish

The big questionThe big question

Is there actually a finish point to Is there actually a finish point to Failsafe???????Failsafe???????

1111

Answer, No….Answer, No….

Processes are perpetualProcesses are perpetual

GoldGold = All win within the systems = All win within the systems

No silver or bronze.No silver or bronze.

1212

Thank youThank you

"Talent wins games, but teamwork and "Talent wins games, but teamwork and intelligence wins championships." intelligence wins championships."

(Michael Jordan)(Michael Jordan)