1 / 34

Public Consultation Service Redesign Proposal 2014

Public Consultation Service Redesign Proposal 2014. Introduction:.

Download Presentation

Public Consultation Service Redesign Proposal 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Public Consultation Service Redesign Proposal 2014

  2. Introduction: Warwickshire Fire and Rescue Service is required to save around £2.4 million pounds over a four year period, that equates to 12% of its overall funding. As part of these savings we have had to look at how we can deliver frontline services differently. The response model improves our current emergency response standard. If implemented we will respond to serious incidents in rural areas within 10 minutes on 80% of occasions. That has reduced our current response time by half and means that if you live in a small town or village anywhere in the county you will receive the same level of response as our large urban centres. Change is always difficult, however we would reassure the public in Warwickshire that this would not impact on our priorities: • Protect the public • Protect our firefighters • Do our very best Rob Moyney Area Commander Operational Response

  3. Background & Context: Key Aims • The key aims of the proposed delivery model are to: • Improve outcomes to the community • Redesign the Service • Save money

  4. Background & Context: Savings Implementation • The Service Redesign proposal is based on a plan to achieve a target saving of £2.4m over a four year period • This consultation focusses on the implementation required within years 1 & 2 • Further implementation detail of years 3 & 4 is dependant on review and validation at the end of years 1 & 2

  5. Background & Context: WFRS contribution target of £2.4m over four years towards the WCC overall savings target means a reduction in staff numbers … which requires a new Delivery Model That incorporates an amended wholetime duty system and is supported by appropriate vehicles, equipment and managerial structures

  6. Background & Context: Current Fire Engines • Wholetime (WT) fire stations maintain fire engine availability by operating either shift crewed or day crewed systems • Retained Duty System (RDS) fire stations facilitate fire engine availability using ‘on call’ firefighters

  7. Background & Context: Current Fire Stations

  8. Background & Context: Operational Staff The 2 year savings target will require the removal of: • 30 Wholetime (WT) posts • 5 Fire Control Room Officer posts

  9. Activity Levels: Life Risk Incidents Incidents in Warwickshire 2011 - 2012 Life Risk P1 & P2 Incidents Non Life Risk P3 & P4 Incidents

  10. Activity Levels: Life Risk Incidents Location of P1 & P2 Incidents Location of P1 & P2 Incidents Heat Map Incidents in Warwickshire 2011 - 2012

  11. Activity Levels: Engine Availability Average RDS Engine Availability compared to Incident Demand … by hour of day Average RDS appliance availability Number of incidents Time of Day Appliances with full crew available to respond to life risk incidents Incident hourly profile

  12. Activity Levels: Conclusion • By analysing activity levels and incident demand we have found that: • Retained (RDS) appliance availability is reduced during the day • Maximum number of appliances are available when incident activity is at its lowest • Operational staff capacity needs to be aligned with incident demand • Single appliance locations are required to achieve better response times across the whole County • Both Wholetime (WT) and Retained (RDS) duty systems are required to achieve a flexible response

  13. Proposed Response Model • The overall aim of the proposed Response Model is to: • Provide a quicker response to life risk incidents such as building fires and road traffic collisions (RTCs) across the whole of the County • Maintain the current response of 10 minutes to urban areas • Significantly improve the response times within rural areas (currently 20 minutes) • Enable the Fire and Rescue Service to achieve a target saving of £1.3m over a two year period

  14. Proposed Response Model: Duty Systems

  15. Proposed Response Model • The proposed response model will be phased in over the next four years • Fire engines in the model are distributed across single vehicle locations to achieve geographic coverage • Following implementation of the response model, the effectiveness of response locations will be continually evaluated

  16. Proposed Response Model: Response Locations

  17. Proposed Response Model : Year 1, 2015, Available Pumps

  18. Proposed Response Model : Year 1, 2015, Dynamic Dispersal

  19. Proposed Response Model: 2015 Year 1, Day

  20. Proposed Response Model: 2015 Year 1, Night

  21. Proposed Response Model : Year 2, 2016, Overview • Because of changes in the numbers of wholetime firefighters, to achieve the required savings, year 2 sees the introduction of: • An additional RDS fire engine at Rugby • A change at the Leamington hub from 4 to 3 wholetime fire engines

  22. Proposed Response Model : Year 2, 2016, Available Pumps

  23. Proposed Response Model : Year 2, 2016, Dynamic Dispersal

  24. Proposed Response Model: 2016 Year 2, Day

  25. Proposed Response Model: 2016 Year 2, Night

  26. Response Model: Resilience Arrangements • Availability of 20 fire engines at all times will be achieved by maintaining a strategic reserve, crewed by firefighters that are recalled to duty • Mobilising of resilience appliances will be achieved within a 30 to 90 minute time period depending on the location of responding firefighters within the County.

  27. Proposed Response Model : Performance • The proposed model will: • Get a fire engine to life risk emergencies across the County within 10 minutes on 80% of occasions (which is an increase of 6% on current performance across the County) • Get a second fire engine to life risk emergencies across the County within 15 minutes on 80% of occasions

  28. Response Model: Performance The proposed Response Model is designed to achieve a quicker response to life risk incidents such as building fires and road traffic collisions (RTCs) across the whole of the County and is benchmarked against 10 minute and 15 minute performance.

  29. Wholetime Duty System: Demand… by hour of day P1 & P2 Incidents, Building Fires & RTCs, by hour of day Number of Incidents 64.5% of P1&P2s occur between 1000hrs and 2200hrs Time of Day

  30. WT Duty System: Demand… by hour of day Property Fires (P1&P2) 1000 hrs to 2200 hrs (Day) Property Fires (P1&P2) 2200 hrs to 1000 hrs (Night) More RED persons reported 10:00 – 22:00

  31. WT Duty System: Demand… by hour of day RTCs (P1) 1000 hrs to 2200 hrs (Day) RTCs (P1) 2200 hrs to 1000 hrs (Night) More P1 RTC’s 10:00 – 22:00

  32. WT Duty System: Conclusion • By analysing activity levels and incident demand • by hour of day we have found that we can: • Improve our initial response standards and fire engine availability by deploying whole-time firefighters at more response locations. • Have more fire engines and firefighters available between the peak hours of 10am and 10pm. • Match peaks in demand by changing firefighters’ shifts

  33. New Delivery Model: Support & Capacity Building Delivery Model Management Structure Introduce a management structure to support and enhance the proposed response model Vehicles and Equipment Provide replacement fire appliances and equipment as required to support the model Operational Training Deliver training systems to ensure well trained operational crews

  34. New Delivery Model: Implementation Timeline 2015 - 2016

More Related