04.05.2014 Views

Fire Station Location Study - City of Oklahoma City

Fire Station Location Study - City of Oklahoma City

Fire Station Location Study - City of Oklahoma City

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

OKLAHOMA CITY FIRE DEPARTMENT<br />

FIRE STATION LOCATION STUDY<br />

Submitted to:<br />

<strong>Fire</strong> Chief G. Keith Bryant<br />

<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

820 N.W. 5th<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 73106<br />

(405) 297–3314<br />

Submitted by:<br />

TriData, a Division <strong>of</strong> System Planning Corporation<br />

1000 Wilson Blvd., 30th Floor<br />

Arlington, VA 22209<br />

(703) 351–8300<br />

SEPTEMBER 2006


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Table <strong>of</strong> Contents<br />

ACKNOWLEDGMENTS ................................................................................................. 1<br />

EXECUTIVE SUMMARY ................................................................................................ 3<br />

I. INTRODUCTION.......................................................................................................... 6<br />

Organization <strong>of</strong> the Report ......................................................................................................... 6<br />

Scope <strong>of</strong> Work and Overall Methodology.................................................................................. 7<br />

Overview <strong>of</strong> <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department ........................................................................... 9<br />

Background <strong>of</strong> <strong>City</strong>................................................................................................................... 10<br />

II. RISK AND DEMAND ................................................................................................ 15<br />

What are the major risks? ......................................................................................................... 15<br />

Population ................................................................................................................................. 19<br />

Aging Demographics ................................................................................................................ 21<br />

The Future: Demand and Workload Forecasts ......................................................................... 21<br />

Workload Forecast by Unit....................................................................................................... 25<br />

III. DETERMINING RESOURCE NEEDS...................................................................... 31<br />

Sources to Aid in Developing Criteria...................................................................................... 32<br />

Response Times ........................................................................................................................ 35<br />

Number <strong>of</strong> <strong>Station</strong>s ................................................................................................................... 44<br />

Number <strong>of</strong> Apparatus................................................................................................................ 51<br />

Inter-jurisdictional Comparisons .............................................................................................. 61<br />

IV. STATION AND APPARATUS DEPLOYMENT ....................................................... 67<br />

Current Response Times........................................................................................................... 67<br />

Analysis <strong>of</strong> <strong>Station</strong> and Apparatus <strong>Location</strong>s........................................................................... 76<br />

Recommended Moves and Additional <strong>Station</strong>s and Apparatus................................................ 80<br />

Summary................................................................................................................................... 95<br />

<strong>Fire</strong> Prevention.......................................................................................................................... 98<br />

Opportunities for Regional Cooperation................................................................................... 99<br />

V. EMERGENCY MEDICAL SERVICES .................................................................... 102<br />

Overview................................................................................................................................. 102<br />

Ability to House EMS Units and Personnel ........................................................................... 107<br />

TriData, a Division <strong>of</strong> September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

APPENDIX A: SUMMARY OF RECOMMENDATIONS ............................................. 113<br />

APPENDIX B: CAPITAL RECOMMENDATIONS BY BUDGET YEAR ..................... 115<br />

APPENDIX C: REPORT MAPS.................................................................................. 116<br />

TriData, a Division <strong>of</strong> September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

ACKNOWLEDGMENTS<br />

We wish to thank the leaders and staff members <strong>of</strong> the many <strong>Oklahoma</strong> <strong>City</strong> agencies<br />

that provided valuable insight for this study. They not only provided information and welcomed<br />

our visits to their areas, but also interacted helpfully with us throughout the study.<br />

<strong>Fire</strong> Chief G. Keith Bryant, and many other chiefs, <strong>of</strong>ficers, firefighters and managers <strong>of</strong><br />

the <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department were extremely cooperative, gracious, and forthcoming in<br />

relation to providing data, facilitating tours <strong>of</strong> the city, arranging station and facility visits and<br />

providing insight into the department.<br />

We would particularly like to thank Captain James Kruta who was the Project Manager<br />

for the department. He efficiently and effectively facilitated all <strong>of</strong> our data requests, arrangement<br />

<strong>of</strong> meetings, and visits, while keeping a strict, succinct schedule during our triage and follow-up<br />

visits.<br />

The men and women <strong>of</strong> the <strong>Oklahoma</strong> <strong>City</strong> government were instrumental in making this<br />

study a success. Without their cooperation, our ability to produce a quality product would have<br />

been compromised. Some <strong>of</strong> these pr<strong>of</strong>essional included:<br />

<strong>City</strong> Councilman Gary Mars (retired fire chief)<br />

<strong>City</strong> Manager James Couch<br />

Assistant <strong>City</strong> Manager M.T. Berry<br />

<strong>Fire</strong> Chief G. Keith Bryant<br />

Deputy Chief David Landsbeger, <strong>Fire</strong> Operations<br />

Deputy Chief Pete Hurston, <strong>Fire</strong> Prevention<br />

Deputy Chief Tony Young, Support Services<br />

Battalion Chief Donald Fonzie, Communications<br />

Major James Blocker, Emergency Medical Services<br />

Major Michael Burner, Health and Safety Officer<br />

Major Shawn Bray, Building Service<br />

Lieutenant Betty Lamb, Communications<br />

While we received excellent input and cooperation from the city, the evaluation and<br />

recommendations reflected in the report are those <strong>of</strong> the TriData project team. The principal<br />

members <strong>of</strong> the team and their areas <strong>of</strong> responsibility are shown below, but this was a team effort<br />

and views were sought from multiple team members on virtually every aspect <strong>of</strong> the <strong>Oklahoma</strong><br />

<strong>City</strong> <strong>Fire</strong> Department.<br />

TriData, a Division <strong>of</strong> 1 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Acknowledgements<br />

TRIDATA STAFF<br />

Philip Schaenman<br />

Stephen Brezler<br />

Harold Cohen<br />

Daryl Sensenig<br />

Steven Lee<br />

Robin Davis<br />

Maria Argabright<br />

Teresa Copping<br />

Corporate Oversight<br />

Project Manager<br />

Deputy Project Manager<br />

Senior Research Analyst<br />

<strong>Station</strong> <strong>Location</strong>, Response Time, and GIS Analysis<br />

Inter-jurisdictional Comparisons, <strong>Station</strong> <strong>Location</strong>, GIS Analysis<br />

Production Coordination and Support<br />

Production Coordination and Support<br />

TriData, a Division <strong>of</strong> 2<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

EXECUTIVE SUMMARY<br />

This report presents the results <strong>of</strong> a detailed analysis <strong>of</strong> fire station locations, response<br />

times, demand forecasts, and resource deployment for <strong>Oklahoma</strong> <strong>City</strong>, <strong>Oklahoma</strong>. The TriData<br />

Division <strong>of</strong> the System Corporation <strong>of</strong> Arlington, Virginia conducted this analysis.<br />

In late 2005 <strong>Oklahoma</strong> <strong>City</strong> sought proposals from outside firms to conduct a <strong>Fire</strong> <strong>Station</strong><br />

<strong>Location</strong> <strong>Study</strong>. The <strong>City</strong> believed that housing, demographic and growth patterns had changed<br />

in the <strong>City</strong> in recent years. The scope <strong>of</strong> the study considered the satisfactoriness <strong>of</strong> the current<br />

station locations and deployment to meet existing demand and changes needed to meet growth.<br />

Our study makes 25 recommendations in four major chapters.<br />

• Risk and Demand<br />

• Determining Resource Needs<br />

• <strong>Station</strong> and Apparatus Deployment<br />

• Emergency Medical Services<br />

A table <strong>of</strong> the recommendations with a page reference for each is included as an<br />

appendix.<br />

CHAPTER II: RISK AND DEMAND ANALYSIS<br />

This Chapter describes the risk to <strong>Oklahoma</strong> <strong>City</strong> and the influences <strong>of</strong> population on<br />

demand for services <strong>of</strong> the fire department.<br />

The majority <strong>of</strong> emergency dispatches are for requests for emergency medical services.<br />

<strong>Fire</strong> calls make up 14 percent <strong>of</strong> the requests while requests for EMS service make up 78 percent<br />

and other incidents are 8 percent <strong>of</strong> the total requests for service.<br />

There are several areas <strong>of</strong> the city where response times exceed the nationally recognized<br />

standards for the time it takes for fire department resources to arrive on the scene <strong>of</strong> an<br />

emergency. We made several recommendations regarding the relocation <strong>of</strong> existing fire<br />

department resources and the locations <strong>of</strong> future stations to meet the anticipated needs <strong>of</strong> future<br />

service demands in Chapter IV, <strong>Station</strong> <strong>Location</strong> and Apparatus Deployment.<br />

CHAPTER III: DETERMINING RESOURCE NEEDS<br />

Making a determination <strong>of</strong> the proper levels <strong>of</strong> resources for a fire department to deploy<br />

requires balancing the safety concerns <strong>of</strong> citizens, risk factors and the financial situation <strong>of</strong> the<br />

local government.<br />

In making recommendations the project team considered standards <strong>of</strong> the Insurance<br />

Service Office (ISO), National <strong>Fire</strong> Prevention Association (NFPA), Center for Public Safety<br />

Excellence/Commission on <strong>Fire</strong> Accreditation International (CFAI) and The United States<br />

TriData, a Division <strong>of</strong> 3 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Executive Summary<br />

Occupational Safety and Heath Administration (OSHA). Standards <strong>of</strong> each organization are<br />

discussed in detail in this chapter.<br />

The NFPA’s <strong>Fire</strong> Protection Handbook makes staffing recommendations based on the<br />

number fire fighters needed for three types <strong>of</strong> building occupancies and hazards. These<br />

occupancies and hazards area classified as High, Medium and Low. We found the OKCFD meets<br />

or exceeds the NFPA guidance in all three categories. We recommend reducing the numbers and<br />

types <strong>of</strong> equipment dispatched for Medium and Low hazard occupancies as a means to manage<br />

work loads and improve response times by increasing availability <strong>of</strong> resources.<br />

There were 13 other cities used to make comparisons <strong>of</strong> the OKCFD. We compared<br />

populations, staffing, apparatus, call volume and per capita costs. <strong>Oklahoma</strong> <strong>City</strong> fares well in<br />

our comparisons. With the exception <strong>of</strong> cost per capita, the <strong>City</strong> falls near the average value <strong>of</strong><br />

the categories listed.<br />

CHAPTER IV: STATION LOCATION AND APPARATUS DEPLOYMENT<br />

This chapter discusses the deployment <strong>of</strong> fire stations and emergency response apparatus.<br />

Many factors should be taken into account when determining the appropriate number <strong>of</strong> stations,<br />

including demand for services, population, density <strong>of</strong> demand and population, size <strong>of</strong> the<br />

jurisdiction, and desired response times. This chapter applies these factors to the current and<br />

future situation <strong>of</strong> the department.<br />

Actual incident data for CY04 through the first quarter <strong>of</strong> CY06 was gathered from the<br />

computer aided dispatch system (CAD). Data included addresses for geocoding, type <strong>of</strong> incident,<br />

units responding, and overall response times. 1 Geographic information system (GIS) files used<br />

for the analysis were provided by the city.<br />

Analysis <strong>of</strong> the four and eight minute response time routes from each station found there<br />

are several regions <strong>of</strong> the city where response times exceed those times. As the city continues to<br />

grow into these regions, expansion <strong>of</strong> coverage will be necessary. The chapter includes maps that<br />

show the current response patterns and the improvements in coverage and fractile response<br />

values if recommended redeployments and additional resources are made.<br />

Research validated a recommendation made by <strong>Oklahoma</strong> <strong>City</strong> Planning Department in a<br />

study <strong>of</strong> the Southwest Sector Plan. Page 35 <strong>of</strong> that report identifies a location at Council and<br />

SW 104 th Street that was recommended for a new fire station. 2 That region <strong>of</strong> the city is<br />

experiencing growth and has the potential for continued expansion. This will be the case if the<br />

planned extension <strong>of</strong> the Interstate Highway network occurs.<br />

1 Geocoding is a process by which the street address <strong>of</strong> an emergency incident is translated into latitude and<br />

longitude so that it can be placed onto a map.<br />

2 Southwest Sector Plan, <strong>Oklahoma</strong> <strong>City</strong> Planning Department, page 35<br />

TriData, a Division <strong>of</strong> 4<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Executive Summary<br />

We recommend the redeployment <strong>of</strong> existing resources such as rescue ladder companies;<br />

district chiefs and tankers (water tenders). We visited each fire station to determine its ability to<br />

house additional personnel and equipment. Mapping also identifies improved response patterns.<br />

Our study identified the stations where capital improvements would have to me made prior to the<br />

addition <strong>of</strong> additional equipment. This was not a detailed structural study <strong>of</strong> the buildings rather,<br />

it was a feasibility review to see which buildings could accommodate more equipment and<br />

personnel.<br />

This report can be used as a multi-year planning document for the future needs <strong>of</strong> the<br />

city. The fire station location recommendations are presented with priorities attached to show the<br />

needs as they exist today and with the expected growth <strong>of</strong> the city.<br />

CHAPTER V: EMERGENCY MEDICAL SERVICES<br />

The Emergency Medical Services system was reviewed with respect to; the fire<br />

department’s role in EMS, suggested station locations for EMS transport units, and ability to<br />

house EMS units and personnel. We examined both quantitative and qualitative issues and<br />

involved stakeholders throughout the department. The complete detailed study <strong>of</strong> Emergency<br />

Medical Service was beyond the scope <strong>of</strong> this project, the study does make seven<br />

recommendations for improvement <strong>of</strong> the EMS delivery system. The core recommendations are,<br />

the all engine companies are upgraded to paramedic engine status, i.e. adding an Advanced Life<br />

Support (ALS) provider to each company. The program to complete this concept was started<br />

several years ago but has not been completed due to budget constraints. Another important<br />

recommendation was to add a contingency plan to the city’s emergency plan in the event <strong>of</strong> the<br />

contractual EMS provider defaulting by means <strong>of</strong> a work stoppage or other failure to deliver<br />

services.<br />

TriData, a Division <strong>of</strong> 5<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. INTRODUCTION<br />

<strong>Oklahoma</strong> <strong>City</strong> and the <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department (OCFD) requested the<br />

assistance <strong>of</strong> a pr<strong>of</strong>essional consulting firm to provide a fire station location and apparatus<br />

deployment analysis. The focus <strong>of</strong> this study was to evaluate current station and apparatus<br />

locations and make recommendations to improve coverage and services. To perform the<br />

evaluation, the city selected TriData, a division <strong>of</strong> System Planning Corporation.<br />

TriData is an internationally recognized consulting firm that has undertaken over 130<br />

studies <strong>of</strong> this type, including studies for Fort Worth, Houston, Louisville, and many other metro<br />

cities. In addition, TriData works closely with the United States <strong>Fire</strong> Administration to compile<br />

annual fire loss statistical data and undertake topical studies on current issues affecting fire and<br />

emergency medical response in the United States.<br />

ORGANIZATION OF THE REPORT<br />

This report is organized into an introduction containing the methodology and general<br />

information about the project scope, then four main chapters, and finally a chapter listing a<br />

summary <strong>of</strong> all recommendations. While each chapter is largely a self-contained analysis reading<br />

the entire report aids in better understanding the whole study. The major chapters include:<br />

Chapter II, Risk and Demand discusses pressures that exist on the fire department to<br />

meet their requests for service, including an analysis <strong>of</strong> future population changes and a<br />

projection <strong>of</strong> demand which is important in predicting future viability <strong>of</strong> the system as well as<br />

the need for more or fewer resources to meet these demands.<br />

Chapter III, Determining Resources Needs discusses performance goals and standards<br />

typically used in the fire and EMS industry. The project team compares the city to these<br />

standards and makes recommendations on goals to be met.<br />

Chapter IV, <strong>Station</strong> and Apparatus Deployment presents a geographic information<br />

system (GIS) analysis <strong>of</strong> station locations and resource deployment. The analysis presents<br />

population and demand projections through 2020. Models are used to propose a new station<br />

configuration to meet the demand for emergency service while reducing redundancy <strong>of</strong> stations<br />

and apparatus coverage.<br />

Chapter V, Emergency Medical Services TriData was asked to evaluate several<br />

components <strong>of</strong> the Emergency Medical Services system including: (a) the fire department’s role<br />

in EMS, (b) suggested station locations for EMS transport units, (c) ability to house EMS units<br />

and personnel. We examined both quantitative and qualitative issues by involving stakeholders<br />

throughout the department and the OKC/EMSA Medical Director, Dr. John Sacra.<br />

TriData, a Division <strong>of</strong> 6 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

SCOPE OF WORK AND OVERALL METHODOLOGY<br />

The review <strong>of</strong> station locations included a review <strong>of</strong> the current allocation and location <strong>of</strong><br />

resources (Task I), forecast <strong>of</strong> future demands for service and population trends (Task II), and<br />

recommended changes to the current system (Task III).<br />

Needs Assessment – Demand for service is the product <strong>of</strong> demand per capita and<br />

population served. One needs to consider both elements in projecting demand.<br />

We assessed needs for fire, EMS (including ALS and BLS), and other emergency<br />

services using several approaches including: an analysis <strong>of</strong> trends in demand by type <strong>of</strong> call;<br />

projections <strong>of</strong> demand in terms <strong>of</strong> call per capita and per business (as available) and projection<br />

<strong>of</strong> overall demand in light <strong>of</strong> expected growth in total population and businesses; evaluation <strong>of</strong><br />

the current quality <strong>of</strong> services (and hence the need to improve); discussions with local <strong>of</strong>ficials;<br />

and evaluation <strong>of</strong> the risks. We also considered the degree to which demand for service needs<br />

vary throughout the region and environs.<br />

Methodology – The methodology used for this study is based on TriData’s 24 years in<br />

undertaking similar projects. The study used a mixture <strong>of</strong> data analysis and personal interviews.<br />

This allowed the project team to develop a thorough picture <strong>of</strong> the Department.<br />

The study began with a kick-<strong>of</strong>f conference call on March 6, 2006 between TriData staff<br />

and representatives from the OKC FD to discuss the study and discuss a tentative schedule for<br />

the first on site meeting. The kick-<strong>of</strong>f conference ensured that the study plan was appropriate and<br />

that staff assignments are in line with the goals <strong>of</strong> the project.<br />

From March 14 to 17, 2006, members <strong>of</strong> the TriData team visited the city to perform a<br />

“triage” <strong>of</strong> goals, priorities and issues. The TriData team met with the OKC FD senior staff,<br />

project managers, representatives from the International Association <strong>of</strong> <strong>Fire</strong> Fighters Local #157<br />

and city <strong>of</strong>ficials from the Planning and Zoning Office and <strong>City</strong> Manager’s Office. <strong>City</strong><br />

Councilman Gary Marrs; a retired <strong>Fire</strong> Chief <strong>of</strong> the <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department and<br />

commander <strong>of</strong> the response to the Murrah Building bombing in 1995 was also interviewed. The<br />

visit also included ride-alongs with district chiefs to examine the conditions <strong>of</strong> the fire stations as<br />

per the scope <strong>of</strong> work. At the conclusion <strong>of</strong> the visit, a wrap-up meeting was conducted with key<br />

members <strong>of</strong> the OKCFD project team to discuss any issues that were identified during the visit.<br />

During the phase <strong>of</strong> the project, specialists from the study team undertook a series in<br />

depth reviews <strong>of</strong> the various functions, concentrating on the station location, station conditions<br />

and staffing issues. A series <strong>of</strong> data analyses were undertaken to project demand and consider<br />

various station location configurations, using GIS s<strong>of</strong>tware.<br />

Risk Assessment (Task I and Task II) – In undertaking a risk assessment we consider<br />

actual past experience and potential risk for fire and EMS and other calls. We considered major<br />

TriData, a Division <strong>of</strong> 7<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

fire risks (e.g., unsprinklered high-rises) hazardous materials risks, aging <strong>of</strong> the population, and<br />

concentration <strong>of</strong> people with high EMS demand. We determined whether risks are more or less<br />

uniformly distributed, or concentrated in particular areas. We identified (current and future)<br />

trends affecting fire and emergency protection—population growth, demographics, risks,<br />

incidents over the past decade, and crew workload.<br />

As part <strong>of</strong> this analysis, we used a methodology in which we project demand and<br />

population trends. We broke out call demand by call type, including fire, EMS, hazmat, etc. For<br />

this task, we have collected historical data (preferably from the CAD) for at least the past 3–5<br />

years.<br />

RESPONSE TIME ANALYSIS: We looked at response times, call volume, and types <strong>of</strong><br />

incidents to determine the distribution and deployment <strong>of</strong> fire protection personnel and the<br />

proper types <strong>of</strong> equipment or apparatus to be used. GIS s<strong>of</strong>tware was used to assist in making<br />

these decisions.<br />

We considered not only <strong>of</strong> the average response times <strong>of</strong> the areas served, but the<br />

cumulative frequency distribution <strong>of</strong> response times or fractile response times (i.e., the percent <strong>of</strong><br />

calls responded to in 3 minutes, 4 minutes, 5 minutes, etc.), and the response times by area <strong>of</strong> the<br />

region and by type <strong>of</strong> call. Based on the demand projections and where growth is anticipated,<br />

TriData made recommendations on response time goals, determinations <strong>of</strong> the need for coverage<br />

in particular areas, the best locations for apparatus based on demand and response time goals,<br />

and <strong>of</strong>fered specific recommendations on future delivery patterns.<br />

APPARATUS DEPLOYMENT: The station location analysis was tied into the apparatus<br />

deployment analysis and included an analysis <strong>of</strong> the number and types <strong>of</strong> units, the types <strong>of</strong><br />

apparatus used, and the recommended staffing levels. Consideration was given to the level <strong>of</strong><br />

service that can be provided once a unit arrives, to the safety <strong>of</strong> firefighters, EMS providers, and<br />

the public, and to compliance with national standards and guidelines.<br />

Based on the quantitative and qualitative considerations, we developed approaches for<br />

<strong>Oklahoma</strong> <strong>City</strong> to use in making decisions about the future. Without an unlimited budget, it was<br />

not possible to make decisions strictly on response time standards regardless <strong>of</strong> the cost <strong>of</strong><br />

reaching those objectives.<br />

Prevention – Prevention programs influence demand by how <strong>of</strong>ten by giving them<br />

information on how to keep safe and when to make emergency calls. Prevention was not within<br />

the scope <strong>of</strong> this study; however, we needed to understand the role <strong>of</strong> the staffed units in fire and<br />

injury prevention as part <strong>of</strong> understanding their “busyness” and capacity to handle growth. The<br />

strength <strong>of</strong> the prevention program affects demand in the future, which in turn determines<br />

whether units get over taxed, and influences the need for relief units. So we had to consider at<br />

least that aspect <strong>of</strong> prevention.<br />

TriData, a Division <strong>of</strong> 8<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

Apparatus and Equipment – Most <strong>of</strong> the analyses <strong>of</strong> the adequacy <strong>of</strong> apparatus and<br />

equipment were considered as part <strong>of</strong> the station location study. We addressed the types <strong>of</strong><br />

apparatus needed for recommended new stations and shifting <strong>of</strong> equipment to different locations.<br />

OVERVIEW OF OKLAHOMA CITY FIRE DEPARTMENT<br />

The OKCFD is a municipal fire department that serves a city with over 530,000 residents<br />

and covers 621 square miles. This is one <strong>of</strong> the largest land areas in the nation, which affects<br />

deployment strategies. OCFD provides the city with fire suppression, wildland firefighting,<br />

hazardous materials mitigation, emergency medical service, technical rescue, fire prevention, fire<br />

investigation and public education. There are 948 employees <strong>of</strong> which 825 are uniformed. 3<br />

The fire chief has a safety <strong>of</strong>ficer, a liaison to emergency management, a civilian business<br />

manager and three deputy chiefs reporting directly to him. The deputy chiefs manage the<br />

activities <strong>of</strong> the three major bureaus: Prevention Services, Support Services, and Operational<br />

Services.<br />

The Prevention Services Bureau has three battalion chiefs supervising the <strong>Fire</strong><br />

Investigation, Code Enforcement, and Public Education sections. The city makes a substantial<br />

commitment to public education. This is commendable given budget limitations <strong>of</strong> the past few<br />

years that saw reductions in staffing elsewhere in the department.<br />

Logistical and administrative services are provided by the Support Services Bureau,<br />

which includes maintenance, dispatch, human resources, a graphics <strong>of</strong>fice, FMIS, and facilities<br />

management.<br />

The bulk <strong>of</strong> the employees in the department are assigned to the Operations Services<br />

Bureau, headed by a deputy chief. The city is divided into 6 districts. A district/battalion chief<br />

supervises each district. Each district chief has an aide (district administrative assistant) who<br />

drives the battalion vehicle and act as adjunct for the chief.<br />

The city operates 36 engine companies out <strong>of</strong> 35 stations. Twenty <strong>of</strong> these engines are<br />

staffed with four personnel, one <strong>of</strong> whom is an Advanced Life Support (ALS) provider. These 20<br />

engines are designated as paramedic engines. The remaining 16 engine companies are staffed<br />

with three personnel. The department plans to upgrade these 16 engines to paramedic engines.<br />

Details <strong>of</strong> this program are included in Chapter V. There are 13 rescue ladders that have<br />

conventional aerial apparatus augmented with extrication and other rescue tools, thus the<br />

description “rescue ladder”. These companies are staffed with three personnel.<br />

Due to the hazards <strong>of</strong> ground cover or brush fires, the department also has 15 smaller<br />

“brush trucks” that have small (


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

As there are areas <strong>of</strong> the city that lack hydrant systems, the Department also operates 6<br />

water tenders (tankers). The tankers are independently staffed with a driver/operator.<br />

<strong>Station</strong> 5 is the hazardous materials response station and <strong>Station</strong> 8 houses the technical<br />

rescue team. Minimum staffing for each shift 213 personnel.<br />

BACKGROUND OF CITY<br />

<strong>Oklahoma</strong> <strong>City</strong> was founded when the west was still young. In 1889, President Benjamin<br />

Harrison authorized the opening <strong>of</strong> the Unassigned Lands, present day <strong>Oklahoma</strong> <strong>City</strong>. Settlers<br />

lined up at the borders, some slipping across the borders early, gaining the nickname “Sooners”.<br />

Over 10,000 people staked a claim in the area and by 1910, <strong>Oklahoma</strong> <strong>City</strong> was the largest city<br />

in the state and became its capital. Today, the city is a diverse, thriving metropolis and the 29 th<br />

largest city in population the United States It is home to Tinker Air Force Base and several<br />

Fortune 1000 and 500 companies. The city was the site <strong>of</strong> the 1995 bombing <strong>of</strong> the Alfred P.<br />

Murrah Federal Building, the largest act <strong>of</strong> terrorism on American soil until the 9/11 attacks. 168<br />

people were killed and over 12,300 rescue workers and volunteers responded in the recovery<br />

effort.<br />

Size – <strong>Oklahoma</strong> <strong>City</strong> is the third largest city in the United States in terms <strong>of</strong> geographic<br />

area. It encompasses 621 square miles, with an urban core <strong>of</strong> over 240 square miles. It has grown<br />

through several annexations. The city is largely suburban and rural. The city’s urban area, like<br />

many other large cities, is currently experiencing a redevelopment and re-growth.<br />

Demographics – The city is home to a very diverse population. African-Americans and<br />

Hispanics account for over 25 percent <strong>of</strong> the 506,132 residents listed in the 2000 census.<br />

National studies have shown that African Americans, Hispanic and Native Americans tend to be<br />

at higher risks for fire injury and death than other groups, while Asians tend to experience lower<br />

risk. Figure 1 depicts the percent <strong>of</strong> the population by ethnic group from the 2000 Census.<br />

TriData, a Division <strong>of</strong> 10<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

Figure 1: <strong>Oklahoma</strong> <strong>City</strong> Demographics<br />

Asian American,<br />

3.5%<br />

Other, 7.1%<br />

American Indian,<br />

3.5%<br />

Hispanic, 10.1%<br />

African American,<br />

15.4%<br />

White, 60.4%<br />

White African American Hispanic American Indian Asian American Other<br />

Source: United States Bureau <strong>of</strong> the Census, 2000 Population<br />

Note: Total is greater than 100 because it is possible for respondents to report Hispanic and a race.<br />

National studies have shown an inverse correlation between income and fire risk.<br />

Residents with lower income are <strong>of</strong>ten at higher risk for becoming victims <strong>of</strong> fire than persons<br />

with higher incomes. Sixteen percent <strong>of</strong> the population and 12.4 percent <strong>of</strong> families live below<br />

the poverty level. This is higher than the national averages <strong>of</strong> 12.4 percent and 9.2 percent, Out<br />

<strong>of</strong> the total population, 9.2 percent <strong>of</strong> residents 65 and older live below the poverty level.<br />

Age – The median age for residents is 34.0. This is slightly lower than the national<br />

median age <strong>of</strong> 36.2. <strong>City</strong> residents 65 years and older make up 11.5 percent <strong>of</strong> the population,<br />

and 14.3 percent <strong>of</strong> residents are under the age <strong>of</strong> 10. Based on national statistics, these two age<br />

groups are more at risk during fires than the population at large. The elderly (individuals over the<br />

age <strong>of</strong> 65) also tend to use the EMS system at a higher rate than the general population.<br />

Education 4 – <strong>Oklahoma</strong> <strong>City</strong> public schools are one <strong>of</strong> the few urban school systems in<br />

the county seeing a rise in enrollment. There are also many private and parochial schools in the<br />

4 Table DP-2. Pr<strong>of</strong>ile <strong>of</strong> Selected Social Characteristics, 2000 Census.<br />

TriData, a Division <strong>of</strong> 11<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

area. According to the 2000 Census, over 133,101 residents over the age <strong>of</strong> 3 were enrolled in an<br />

<strong>Oklahoma</strong> <strong>City</strong> school. The city also boasts many colleges and universities including <strong>Oklahoma</strong><br />

<strong>City</strong> University, <strong>Oklahoma</strong> State University-<strong>Oklahoma</strong> <strong>City</strong>, and the University <strong>of</strong> Central<br />

<strong>Oklahoma</strong>. The University <strong>of</strong> <strong>Oklahoma</strong> is located just south <strong>of</strong> the city in the suburb <strong>of</strong> Norman.<br />

The area also has many community colleges and vocational schools.<br />

Over 80 percent <strong>of</strong> the population 26 years and older have obtained a high school<br />

diploma or higher. Nearly a quarter (24 percent) <strong>of</strong> the residents hold a bachelor’s degree or<br />

higher. Education has been related to fire risk; people with lower levels <strong>of</strong> education tend to be at<br />

a higher risk for fire injury or death. Those with lower education also tend to have lower income,<br />

another risk factor.<br />

Economy – The city has a varied and diverse economy. Oil and gas still play a major<br />

role as well as the service industry. The stockyards are the largest in the world and many <strong>of</strong><br />

Fortune 500 and 1000 companies call the city home. Tinker AFB and its associated contractors,<br />

such as Boeing and Northrop Grumman, employ many <strong>of</strong> the cities residents.<br />

The city’s unemployment rate stays rather steady at around 3.3 percent though this might<br />

change due to a recent closing <strong>of</strong> a General Motors plant. This is lower than the national rate <strong>of</strong><br />

5.4 percent. According to the 2000 Census, the median household income was $34,947.<br />

Although this is less the than the national median <strong>of</strong> $41,994, city residents enjoy the second<br />

lowest cost <strong>of</strong> living<br />

Transportation – <strong>Oklahoma</strong> <strong>City</strong> is a major regional hub in the Great Plains. It is<br />

bisected by Interstate 35, Interstate 40, and Interstate 44. Like other large cities, the city is served<br />

by an extensive network <strong>of</strong> major highways and freeways, however, due to a smaller population<br />

that is spread out most roads are less congested than most comparably sized cities.<br />

The city is home to several airports, including Wiley Post airport and the Will Rogers<br />

World Airport that processes almost 9,000 planes and 300,000 passengers a month. 5 Tinker Air<br />

Force Base, located in eastern <strong>Oklahoma</strong> <strong>City</strong>, is the largest air depot in the nation and the<br />

second largest military installation in the state. Base closures in other areas have solidified<br />

Tinker’s future as a major USAF installation.<br />

The city is also a major passenger and freight rail stop. Amtrak’s Heartland Flyer runs a<br />

daily service to and from Fort Worth, TX. Several freight lines, such as the Burlington Northern-<br />

Santa Fe and the Union Pacific, run trains in the area. Each day several thousand tons <strong>of</strong> cargos,<br />

including hazardous materials, run through the city’s suburbs.<br />

Due to the rejuvenation <strong>of</strong> the downtown area, the city is making a push towards mass<br />

transit. It currently runs a large bus and trolley system and the city government is reviewing a<br />

5 www.flyokc.com/releases Aviation Activity Report, January 2006<br />

TriData, a Division <strong>of</strong> 12<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

study to implement light-rail in the region. <strong>City</strong> planners are also adding many pedestrian and<br />

bicycle paths that will make the city accessible no matter what transportation you take.<br />

Tax Base 6 – The majority (54 percent) <strong>of</strong> the city’s fiscal year 2004-2005 General Fund<br />

Revenue <strong>of</strong> $267,485,261 was from the city sales tax. This is broken down into a two percent<br />

general sales tax, a one percent public schools tax, a 0.75 percent public safety tax, and a .125<br />

percent zoo sales tax. Other revenue is raised through fines, franchise fees, licenses and permits,<br />

and service charges. The General Fund Revenue is expected to grow 3.3 percent over the next<br />

five years, which might not be enough to keep up with the growth in city expenditures, public<br />

safety consumes 55 percent <strong>of</strong> this budget each year.<br />

Housing 7 – Home ownership, type <strong>of</strong> residence, and structure age are all factors that<br />

contribute to fire risk and the need for emergency services. Older homes tend to be at higher risk<br />

for fire, particularly if they are not properly maintained. Some newer homes, mainly multi-unit<br />

structures are constructed with built-in fire protection, such as sprinklers.<br />

Of the city’s 228,188 housing units, 65 percent are single-family, detached homes,<br />

followed by multi-family dwellings with 20 or more units (8.1 percent). Over 30 percent <strong>of</strong><br />

<strong>Oklahoma</strong> <strong>City</strong>’s homes were built before 1959. These homes are at a higher risk for fire if not<br />

properly maintained. Since 1990, about 15 percent <strong>of</strong> the areas houses were constructed and each<br />

year an average <strong>of</strong> 2,000 to 3,000 homes are built.<br />

The majority <strong>of</strong> the homes (67 percent) are valued below $99,999 and 26 percent valued<br />

between $100,000 and $150,000. Less than 0.1 percent <strong>of</strong> homes are valued over $1,000,000.<br />

Climate – Summers can be extremely hot with an average temperature <strong>of</strong> 82°F and daily<br />

highs above 90°F. The Great Plains can suffer from massive droughts and heat waves that place<br />

a strain on water and energy consumption. Average lows in the winter are below freezing and the<br />

city receives around nine inches <strong>of</strong> snow annually.<br />

<strong>Oklahoma</strong> <strong>City</strong>’s biggest threat comes from its location in Tornado Alley. Each year<br />

when warm air from the Gulf <strong>of</strong> Mexico meets cold air from the north violent thunderstorms are<br />

spawned which produce torrential, flooding rains, hail, and tornadoes. Figure 2 shows the area<br />

known as “tornado alley”, where tornadoes have a relatively high occurrence.<br />

6 Five Year Forecast 2006-2010, <strong>City</strong> <strong>of</strong> <strong>Oklahoma</strong> <strong>City</strong><br />

7 Table DP-4. Pr<strong>of</strong>ile <strong>of</strong> Selected Housing Characteristics. 2000 Census<br />

TriData, a Division <strong>of</strong> 13<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

I. Introduction<br />

Figure 2: Climate Map <strong>of</strong> Tornado Activity 8<br />

Geography – The city is located in central <strong>Oklahoma</strong> in the Great Plain region <strong>of</strong> the<br />

United States. The area is relatively flat to gently rolling hills with rich, fertile soil for agriculture<br />

and ranching. <strong>Oklahoma</strong> <strong>City</strong> is home to several large natural lakes and man-made reservoirs.<br />

The North Canadian River runs through the middle <strong>of</strong> town, seven miles <strong>of</strong> which have been<br />

dammed up to create the <strong>Oklahoma</strong> <strong>City</strong> River, and the Canadian River runs to the south <strong>of</strong> the<br />

city.<br />

8 NOAA Storm Prediction Center, http://www.spc.noaa.gov/faq/tornado<br />

TriData, a Division <strong>of</strong> 14<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. RISK AND DEMAND<br />

A city’s risk <strong>of</strong> fire and other emergencies is affected by a variety <strong>of</strong> factors, including<br />

the built environment, climate, geography, and population. This chapter discusses some <strong>of</strong> the<br />

major risks, and then discusses the trends in demand and future demand projections.<br />

WHAT ARE THE MAJOR RISKS?<br />

All large cities have a variety <strong>of</strong> risks for fire and major emergencies and <strong>Oklahoma</strong> <strong>City</strong><br />

has its share and more.<br />

Airport – There are two commercial airports within city limits. Will Rodgers World<br />

Airport is a large modern air passenger and airfreight center. As <strong>of</strong> February 2006 more than<br />

500,000 passengers and 10.8 million pounds <strong>of</strong> freight passed through the airport. 9 At this rate,<br />

an annual projection <strong>of</strong> 3 million passengers and almost 130 million pounds <strong>of</strong> freight can be<br />

expected. A smaller facility, Wiley Post Airport serves general aviation and air taxi services.<br />

Wiley Post does not have scheduled commercial flights. The Will Rodgers World Airport<br />

operates its own separate fire station. <strong>Fire</strong> and Rescue services were previously provided by the<br />

city although these services have been privatized. While the airport operates the primary ARFF<br />

units, the OKCFD is responsible for all calls in the terminal and any other structure fire at the<br />

airport. The department is also responsible for all medical calls at the airport.<br />

Tinker Air Force Base is also within the city limits and has ARFF and structural fire<br />

fighting resources <strong>of</strong> its own and has a mutual aid agreement with <strong>Oklahoma</strong> <strong>City</strong>. At 5,000<br />

acres it is a major USAF facility and employs more than 20,000 military and civilians personnel.<br />

Tinker AFB is the largest single-site employer in the state <strong>of</strong> <strong>Oklahoma</strong> and is a significant<br />

contributor to the local and regional economies. 10 As other bases nation-wide are closed, the<br />

activities at those base are being moved to other facilities. Tinker is one <strong>of</strong> the bases that are<br />

growing as witnessed by the addition <strong>of</strong> a US Navy air unit to tenant list. The additional air<br />

traffic represents a third airport within the city limits.<br />

High-Rises – High-rise firefighting is labor intensive even if a fire is contained by a<br />

sprinkler system. Even when there is minimal fire, high-rise fires <strong>of</strong>ten require at least a second<br />

alarm assignment. The logistics <strong>of</strong> high-rise firefighting include the need for personnel to use<br />

stairways to transport equipment, handle logistics, and provide relief for other firefighters.<br />

<strong>Oklahoma</strong> <strong>City</strong> also demonstrated to the nation that high-rises housing government<br />

<strong>of</strong>fices can be terrorist targets in the center <strong>of</strong> the heartland. The Murrah Building explosion<br />

9 www.flyokc.com/ releases February 2006.<br />

10 Global Secuirty.org<br />

TriData, a Division <strong>of</strong> 15 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

demonstrated the nature <strong>of</strong> this threat and put the city in the forefront <strong>of</strong> terrorist concerns until<br />

9/11.<br />

Road Network – The city is a major regional hub in the Great Plains. Interstate 35,<br />

Interstate 40, Interstate 44, Interstate 235, and Interstate 240 bisect it. Like other large cities, the<br />

city is served by an extensive network <strong>of</strong> major highways and freeways, however due to a<br />

smaller population that is spread out most roads are less congested than most comparably sized<br />

cities. The road network is expected to expand with proposals for a “West Outer Loop Extension<br />

<strong>of</strong> Interstate 35 that would connect Interstates 44 and 240 in the Southwest portion <strong>of</strong> the city.<br />

The expansion <strong>of</strong> the road network will cause more development in the area <strong>of</strong> the city that is<br />

zoned for the Urban Growth Area.<br />

Railway – The city is also a major passenger and freight rail stop. Amtrak’s Heartland<br />

Flyer runs a daily service to and from Fort Worth, TX. Several freight lines, such as the<br />

Burlington Northern-Santa Fe and the Union Pacific, run trains in the area. Each day several<br />

thousand tons <strong>of</strong> cargos, including hazardous materials, run through the city and the suburbs.<br />

Brush <strong>Fire</strong>s – The city has a large amount <strong>of</strong> undeveloped areas that are susceptible to<br />

ground cover (brush fires) during periods <strong>of</strong> dry weather. The spring <strong>of</strong> this year was particularly<br />

dry and caused a surge in the number <strong>of</strong> and severity <strong>of</strong> these fires. These fires <strong>of</strong>ten are laborintensive<br />

and time consuming but generally do not cause significant dollar losses in property. As<br />

the population expands in the rural service area, the potential for property damage increases as<br />

more and larger homes are constructed in areas are otherwise not developed and <strong>of</strong>ten without<br />

water mains. This phenomenon known as Urban-Wildland Interface will challenge the<br />

department to adopt new strategies to limit life and property loss.<br />

The department to its credit has equipped several stations with specialized brush<br />

firefighting equipment and water tenders (tanker). As drought conditions are cyclic there will be<br />

some years that are more active and some that are less. As the Northeast region <strong>of</strong> city continues<br />

to grow with residential development, the risk <strong>of</strong> a brush fire that does significant structural<br />

damage will increase.<br />

Hazardous Materials (Hazmat) – As a transportation hub, <strong>Oklahoma</strong> <strong>City</strong> has risks<br />

for a hazardous materials release resulting from product transportation accidents. Rail yards and<br />

interstate highways that intersect increase the possibility <strong>of</strong> truck accidents or railroad events.<br />

The petrochemical industry contributes to the amounts <strong>of</strong> hazardous materials being processed,<br />

refined, and shipped through and about the city on trucks, rail cars and pipelines. There are<br />

several target hazards including;<br />

• Magellan Oil<br />

• Cato Oil<br />

• B & M Oil<br />

TriData, a Division <strong>of</strong> 16<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

• Harcross Chemicals<br />

• Estes Chemicals<br />

• Trigen<br />

• Xerox<br />

There are four water treatment facilities that store and use hazardous materials such as<br />

Chlorine as well as other industrial applications.<br />

Age Demographics – The median age for residents is 35 years old, just below the<br />

national median <strong>of</strong> 36. <strong>City</strong> residents that are 65 years old and older make up almost 11 percent<br />

<strong>of</strong> the population. Based on national statistics, these two age groups are more at risk during fires<br />

than the population at large. The elderly (individuals over the age <strong>of</strong> 65) also tend to use the<br />

EMS system more than the general population.<br />

Planning and Zoning – The area <strong>of</strong> the city east <strong>of</strong> the Interstate 35-44 corridor is<br />

expected to see an increase in residential and commercial construction. Currently listed as part <strong>of</strong><br />

the rural area, development is anticipated in this northeast portion <strong>of</strong> the city. Much <strong>of</strong> this region<br />

is outside the four-minute response pattern. There is also part <strong>of</strong> the southwest area <strong>of</strong> the city, in<br />

the vicinity <strong>of</strong> the proposed Outer Loop Interstate that is zoned for urban growth in the<br />

development plan. This area is likewise beyond the four-minute response pr<strong>of</strong>ile.<br />

The <strong>Oklahoma</strong> <strong>City</strong> Planning Department has identified those areas <strong>of</strong> the city where<br />

development is likely to occur. This is due to existing trends and zoning patterns. This data will<br />

assist in determining those areas <strong>of</strong> the city where response times are not adequate for the<br />

demand for services.<br />

Figure 3 shows the land use patterns in effect at this time. While subject to future<br />

revision, this information is useful to assist in the projection <strong>of</strong> development.<br />

The Northeast area <strong>of</strong> the city is part <strong>of</strong> the Rural Growth Area and has seen an increase<br />

in residential building permits. Also, the average value <strong>of</strong> the residential units is increasing. The<br />

median housing value for this area is $93,215. 11 This amount is about 16 percent higher than the<br />

average for the reset <strong>of</strong> the city. With more development and the increased value <strong>of</strong> the property<br />

the potential for increases in fire loss is evident.<br />

11 Population and Land Use Projections for the Fiscal Analysis Zones report for the <strong>City</strong> Of <strong>Oklahoma</strong> <strong>City</strong>, Tischler<br />

Bise, Inc. page 17<br />

TriData, a Division <strong>of</strong> 17<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department II. Risk and Demand<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 3: <strong>Oklahoma</strong> <strong>City</strong> Land Use Plan<br />

TriData, a Division <strong>of</strong> 18<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

The Southwest Urban Zone is another area <strong>of</strong> projected growth based on building permit<br />

data. By the year 2015, a projection <strong>of</strong> an additional 8,400 more residential units and about<br />

20,000 more people will live in the area. 12 If the proposed Outer Loop Road to connect I-40 and<br />

I-44 is built, commercial development can be expected along that corridor.<br />

The current response times exceed the national standards in these areas <strong>of</strong> the city. If<br />

growth continues in areas that are underserved now, the potential for losses, both civilian and<br />

property, will increase.<br />

EMS Risks – EMS risks are <strong>of</strong>ten dependant on socio-economic status and age. The<br />

demand for service among the poor and elderly is higher than the demands from other segments<br />

<strong>of</strong> the population. As the population ages the demands for EMS services will increase. This<br />

impacts OCFD operation as first responder EMS is part <strong>of</strong> the operational pr<strong>of</strong>ile <strong>of</strong> the<br />

department.<br />

POPULATION<br />

<strong>Oklahoma</strong> <strong>City</strong> is the largest city in <strong>Oklahoma</strong>. On July 1, 2005 its population was<br />

estimated at 531,600. The greater metropolitan area surrounding and including the city comprises<br />

32 percent <strong>of</strong> the state’s population. The city accounts for 15 percent <strong>of</strong> the statewide population.<br />

Population estimates for 2001–2020 are shown in Table 1. From 2001–2005 the city<br />

averaged a yearly net increase <strong>of</strong> 4869 persons. The observed growth rate was slightly less than<br />

one-percent annually. This can be described as low to moderate growth. Projections for the years<br />

2006, 2010, 2015, and 2020 were supplied by the city. 13 The annual rate <strong>of</strong> growth is predicted to<br />

remain very near to one-percent through 2020. Under these assumptions, the city should number<br />

approximately 620,500 persons in 2020. Unlike many other cities, <strong>Oklahoma</strong> <strong>City</strong> has enormous<br />

room for growth within the city boundaries.<br />

12 IBID page 20<br />

13 Projections created by the Planning department were chosen. The firm <strong>of</strong> Bucher, Willis, and Ratliff developed<br />

projections using a similar methodology. These projections were based on 2005 estimates that differed greatly from<br />

2005 Census Bureau estimates. For this reason, the projection series created by the Planning department was<br />

selected.<br />

TriData, a Division <strong>of</strong> 19<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Table 1: <strong>City</strong> Population, 2001–2020 14<br />

* = Forecast<br />

Year Population (July 1)<br />

2001 512,126<br />

2002 518,156<br />

2003 524,858<br />

2004 528,042<br />

2005 531,600<br />

2006 541,500<br />

2010 561,300*<br />

2015 591,000*<br />

2020 620,500*<br />

These totals, as well as those from the years between projections are shown in Figure 4. 15<br />

The population is expected to exceed 600,000 by 2017. This is a net increase <strong>of</strong> 6473 persons per<br />

year over the 11-year period. These population increases will undoubtedly increase the<br />

department’s workload in the future.<br />

Figure 4: Projected <strong>City</strong> Population, 2001–2020<br />

650,000<br />

600,000<br />

550,000<br />

500,000<br />

450,000<br />

400,000<br />

350,000<br />

300,000<br />

Year<br />

14 <strong>City</strong> Planning<br />

15 Linear interpolation was used to project population for years not supplied by the Planning department.<br />

TriData, a Division <strong>of</strong> 20<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

AGING DEMOGRAPHICS<br />

Studies have shown that services to the elderly increase the workload for fire<br />

departments. A high percentage <strong>of</strong> most departments’ medical workload comes from the<br />

population aged 65 and over. Data from the 1990 and 2000 censuses and the net change in<br />

percent <strong>of</strong> the population by age range are shown in Table 2.<br />

Table 2: Population Age Demographics, 1990 and 2000 16<br />

Age 1990 2000<br />

Change<br />

1990-2000<br />

under 18 115,473 129,274 +0.4%<br />

18-45 194,948 210,157 +2.3%<br />

45-64 81,519 108,603 +3.1%<br />

65 & over 52,779 58,098 +0.4%<br />

Total 444,719 506,132 + 5.84%<br />

Note the observed change between 1990 and 2000 for the city closely followed statewide<br />

changes for the same time period. During this time period, the 45 to 64 year old age group grew<br />

by 3.1 percent. This trend is expected to continue statewide through 2010. This age group is not<br />

expected to produce a disproportionately higher amount <strong>of</strong> incidents. As this population segment<br />

ages, by the year 2020, the state is expected to have a considerably higher proportion <strong>of</strong> persons<br />

at least 65 years old. If this trend also occurs in the city, the department’s medical workload is<br />

likely to increase. 17 Increased demand for services <strong>of</strong> this type will be hypothesized and<br />

considered in incident projections in the following section.<br />

Recommendation 1: The city should continue to monitor age demographic and use this<br />

data to project demand.<br />

A population’s demographics can change over time. Anticipating these changes allows a<br />

provider to address the need for changes in protocol, station location, and deployment.<br />

THE FUTURE: DEMAND AND WORKLOAD FORECASTS<br />

The project team used two models to forecast future demand. This projection procedure<br />

was developed over the past 24 years <strong>of</strong> conducting fire department studies. The number <strong>of</strong><br />

incidents in a given year can be predicted to fall between the two projections with a fairly high<br />

degree <strong>of</strong> likelihood. The first model assumes that per capita demand will remain constant. As a<br />

16 Source: 1990 and 2000 Census 100 Percent Data and U.S. Census Bureau, Population Division, Interim State<br />

Population Projections, 2005.<br />

17 Demographic projections for the city were unavailable. However, state population trends play a prominent role in<br />

the Planning department’s population projections cited earlier. For this reason, state demographic trends are seen as<br />

a good indicator for age demographics in the city.<br />

TriData, a Division <strong>of</strong> 21<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

result, demand will grow or decline at the same rate as the population. Since population growth<br />

is predicted, this method produces increasing call totals for <strong>Oklahoma</strong> <strong>City</strong>.<br />

Per capita demand has <strong>of</strong>ten been shown to increase over time, leveling out at some<br />

point. This increase in demand is <strong>of</strong>ten termed increased utilization <strong>of</strong> services. The growth is<br />

<strong>of</strong>ten attributed to aging <strong>of</strong> the population or an increase in the community’s confidence in (or<br />

awareness <strong>of</strong>) fire/EMS services<br />

The estimated demand produced by holding per capita demand constant is <strong>of</strong>ten lower<br />

than actual demand turns out to be. The second method assumes that per capita demand will<br />

continue to grow as it has in recent years for the foreseeable future. Although growth can be<br />

negative, this method is called the increased utilization or increased per capita demand model.<br />

This method tends to overestimate the number <strong>of</strong> future incidents, because demand per capita is<br />

likely to level out at some point if not decrease.<br />

These models represent best and worst case scenarios (extremes are accelerating per<br />

capita demand, or flattening <strong>of</strong> demand). They are referred to throughout this report as low and<br />

high demand projections.<br />

Current Demand –As noted before, the Department’s long-term resource needs depend<br />

partially on the expected future demand for services and workloads <strong>of</strong> individual units. Demand<br />

is the number (and types) <strong>of</strong> calls for service—services provided by the entire fire department.<br />

Analysis <strong>of</strong> demand also indicates which times <strong>of</strong> day certain services are used the most, and<br />

allows decision-makers to consider alternative deployment and staffing methodologies.<br />

Demand for service varies greatly between communities for a number <strong>of</strong> reasons. For<br />

example, the degree <strong>of</strong> urbanization, community income level, and overall age and health <strong>of</strong> the<br />

population impact demand. Demand is also affected by the degree that fire and EMS services are<br />

publicized and to which the public is encouraged to call for service. Citizens will typically call<br />

for 911 services disproportionately more in a city than in rural areas with suburban communities<br />

somewhere in between.<br />

On average, the department responds to over 53,000 incidents a year, <strong>of</strong> which roughly<br />

78 percent are EMS incidents. 18 <strong>Fire</strong>s comprise approximately 14 percent and other incidents<br />

make up the remaining 8 percent. Demand on individual units is sometimes affected by response<br />

protocols. The number <strong>of</strong> incidents is not to be confused with the number <strong>of</strong> unit responses,<br />

which will be discussed shortly. An emergency call may require the response <strong>of</strong> more than one<br />

unit, but only one incident number is generated. For example, if a fire department dispatches two<br />

engines and a truck to a garage fire; this is one incident with three unit responses.<br />

18 Incidents were broken into incident type based on CAD data supplied by the Department. Two years were<br />

available, 2004 and 2005, and their combined totals in each category divided by their sum for both years are defined<br />

as the proportion <strong>of</strong> incidents.<br />

TriData, a Division <strong>of</strong> 22<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Past Demand – Table 3 shows demand for services from 2001 through 2005. The final<br />

two years <strong>of</strong> the period show incident totals divided into three categories: fires, EMS incidents,<br />

and other incidents. 19 Earlier data is not available by type <strong>of</strong> call.<br />

Table 3: <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Incidents, 2001–2005<br />

Year Total <strong>Fire</strong> EMS Other<br />

2001 50,544 * * *<br />

2002 50,483 * * *<br />

2003 51,330 * * *<br />

2004 55,022 7,730 42,501 4,791<br />

2005 59,765 8,273 46,635 4,857<br />

Average 53,429 8,002 44,568 4,824<br />

* Data not available<br />

Total incidents displayed a clear upward trend overall. Incident totals tell half the story <strong>of</strong><br />

a department’s contribution. They are an intermediate measure <strong>of</strong> workload, less detailed than<br />

responses or hours in service.<br />

Per Capita Demand – The size and relative age <strong>of</strong> the population along with past<br />

demand are elements required to project a department’s demand for services. Demand per capita<br />

- the number <strong>of</strong> incidents requiring response divided by the size <strong>of</strong> the population - was analyzed<br />

in order to predict future demand. The trend in per capita demand is shown in Table 4. Note that<br />

demand is shown in terms <strong>of</strong> calls per thousand population to keep the data in integers and more<br />

understandable.<br />

Table 4: <strong>Fire</strong> Department per capita demand, 2001–2005<br />

Year<br />

Incidents per 1000<br />

persons<br />

2001 98.7<br />

2002 97.4<br />

2003 97.8<br />

2004 104.2<br />

2005 112.4<br />

The apparent trend is toward moderate growth in calls per capita. This trend will be used<br />

to determine future demand. The trend in per capita is growing faster than the total population<br />

and has a large impact on demand.<br />

After calculating past incident demand, the trend was analyzed to determine the expected<br />

future trends. Several mathematical measures were considered for each incident category. These<br />

19 Incident totals by type were calculated from CAD data that was only available for 2004 and 2005.<br />

TriData, a Division <strong>of</strong> 23<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

measures include the mean <strong>of</strong> yearly per capita increases, the geometric mean <strong>of</strong> yearly per<br />

capita increases, and a least squares fit linear regression model applied to per capita demand.<br />

Yearly per capita increase in incidents was chosen to represent growth in demand quantified.<br />

This value, 3.4 percent, will be called the observed growth rate.<br />

Recommendation 2: Monitor yearly per capita demand by category and re-analyze data<br />

every five years. This is an important step in targeting prevention efforts. A baseline trend with<br />

incidents proportioned by major type should be established. 20 Sustained movement against<br />

expectations should be identified and analyzed for cause and potential effect on workload.<br />

Demand Projections – The demand model considers demand increases due to both<br />

population increase and changes in per capita demand. The two methods discussed below<br />

produce high and low boundaries into which a future year’s incident totals can be expected to<br />

fall. The first method for estimating the number <strong>of</strong> incidents in a future year is to assume the<br />

current per capita demand for service will remain constant. In this case, demand grows in<br />

proportion to population growth. In most cases, per capita demand has been shown to increase<br />

over time, thus the demand predicted with this method will <strong>of</strong>ten fall short <strong>of</strong> the true value.<br />

The second projection method assumes that per capita demand can be described by the<br />

historic trend. The number <strong>of</strong> incidents projected in this fashion tends to be above the true value<br />

since demand fluctuates and per capita demand levels <strong>of</strong>f eventually. The growth rate was<br />

slowed by a factor <strong>of</strong> one-half after seven years, because demand per capital is unlikely to<br />

continue to grow at the observed rate for the entire fifteen-year period. Using these two models,<br />

upper and lower boundaries are produced. The number <strong>of</strong> incidents in a given year is likely to<br />

fall between the two projections.<br />

Using population projections supplied by the city and the observed per capita demand<br />

growth rates discussed above, high and low projections through the year 2020 were created, as<br />

shown in Table 5. The low demand projection grows only as a result <strong>of</strong> projected population<br />

increases but has been supplemented by a one-time increase, which reflects the unlikelihood <strong>of</strong><br />

zero growth in per capita demand. The best-case scenario projects the department’s call totals to<br />

remain below 75,000 through 2020. On the other hand, high demand could produce incident<br />

totals above 75,000 as soon as 2011. Figure 5 (on the following page) illustrates the upper and<br />

lower boundaries for total incidents. 21<br />

20 Projecting incident totals by type leads to a more detailed projection; however, incident totals split by type were<br />

only available for <strong>Oklahoma</strong> <strong>City</strong> for 2004 and 2005. A longer data history is necessary to predict incidents using<br />

this method.<br />

21 As a consequence <strong>of</strong> the projection method, high and low boundaries converge shortly after the initial year. To<br />

prevent this occurrence, totals from 2007 were replaced with the average <strong>of</strong> 2006 and 2008 to produce a smooth<br />

boundary.<br />

TriData, a Division <strong>of</strong> 24<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Table 5: Upper and Lower Projected Incident Levels, 2006–2020<br />

Year<br />

High<br />

Boundary<br />

Low<br />

Boundary<br />

2006 65,068 62,938<br />

2007 66,784 64,598<br />

2008 68,500 66,258<br />

2009 71,453 66,852<br />

2010 74,529 67,447<br />

2011 77,866 68,161<br />

2012 81,344 68,875<br />

2013 83,578 69,588<br />

2014 85,864 70,302<br />

2015 88,203 71,016<br />

2016 90,591 71,725<br />

2017 93,034 72,434<br />

2018 95,534 73,143<br />

2019 98,092 73,852<br />

2020 100,710 74,561<br />

Figure 5: Upper and Lower Incident Levels, 2001–2020<br />

120,000<br />

100,000<br />

80,000<br />

60,000<br />

40,000<br />

High Boundary<br />

Low Boundary<br />

Incident s<br />

20,000<br />

-<br />

Year<br />

WORKLOAD FORECAST BY UNIT<br />

In order to assess the likely impact <strong>of</strong> increased population and demand for service on the<br />

workload <strong>of</strong> stations and units, we start with the forecast <strong>of</strong> incidents discussed in Chapter III.<br />

TriData, a Division <strong>of</strong> 25<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Relying on the historic ratio <strong>of</strong> responses to incidents to estimate total unit responses, and<br />

allocating unit responses based on their historic proportion by station and unit we developed two<br />

forecasts <strong>of</strong> unit activity.<br />

Low Growth Scenario – The first forecast <strong>of</strong> unit workload, shown in Table 6, is based<br />

on the low growth projection <strong>of</strong> incidents. This projection assumes no changes in response<br />

protocol or incident proportions. In other words, the department’s workload will grow, but the<br />

proportion <strong>of</strong> structure fires, vehicle accidents, hazardous materials incidents, etc., will remain at<br />

2005 levels. This is probably the best-case scenario for total unit responses. Unit responses in<br />

2005 are shown as a baseline. The forecast begins in 2006 and presents five-year increments<br />

through 2020.<br />

Two response thresholds were considered significant for the purposes <strong>of</strong> this study. We<br />

used a threshold <strong>of</strong> 3,000 responses per year as an indication that a unit’s activity level is high<br />

enough to be unavailable for a significant share <strong>of</strong> the responses in its first-due district. It is not a<br />

firm rule, just a flag <strong>of</strong> the level where reduced availability <strong>of</strong>ten becomes a major factor in<br />

degradation <strong>of</strong> response times. In the year 2005, a single unit was over the 3,000 call threshold.<br />

By 2020 the best-case scenario projects the number <strong>of</strong> units expected to have workload above<br />

that threshold to be at 6. Each <strong>of</strong> these units is an engine, and all except one is already above<br />

2,500 responses. Depending on the average amount <strong>of</strong> time in service, units at this level may be<br />

unavailable about a quarter <strong>of</strong> the time. 22 The second threshold, 4,000 incidents will be discussed<br />

under the high growth scenario.<br />

Although several units are likely to be above the 3,000 call threshold by 2020 and two are<br />

now, the system as a whole can absorb many more calls than at present without overloading most<br />

units in the near future. The busiest units in the system are E17, E24, E25, and E9. It may be<br />

necessary to place additional units in these response areas to prevent degradation in the quality <strong>of</strong><br />

service that may result from the forecasted high response totals that these units are likely to<br />

encounter at the end <strong>of</strong> the projection period (Table 6).<br />

Table 6: Low Growth Impact on Engine Company Responses, 2005–2020<br />

Unit 2005 2006 2010 2015 2020 Unit 2005 2006 2010 2015 2020<br />

E1 2,160 2,275 2,438 2,567 2,695 E27 573 603 647 681 715<br />

E10 2,044 2,153 2,307 2,429 2,550 E28 625 658 705 743 780<br />

E11 1,531 1,612 1,728 1,819 1,910 E3 1,581 1,665 1,784 1,879 1,972<br />

E12 2,199 2,316 2,482 2,613 2,743 E30 1,992 2,098 2,248 2,367 2,485<br />

E13 1,083 1,140 1,222 1,287 1,351 E31 1,924 2,026 2,171 2,286 2,400<br />

E14 1,932 2,035 2,180 2,296 2,410 E32 249 262 281 296 311<br />

E15 2,415 2,543 2,725 2,870 3,013 E33 1,265 1,332 1,428 1,503 1,578<br />

22 Using the time in-service in conjunction with responses produces another measure <strong>of</strong> workload called unit hour<br />

utilization, the result <strong>of</strong> the time out on a call.<br />

TriData, a Division <strong>of</strong> 26<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Unit 2005 2006 2010 2015 2020 Unit 2005 2006 2010 2015 2020<br />

E16 1,962 2,066 2,214 2,331 2,448 E34 2,188 2,304 2,469 2,600 2,730<br />

E17 2,745 2,891 3,098 3,262 3,425 E35 1,086 1,144 1,226 1,290 1,355<br />

E18 1,530 1,611 1,727 1,818 1,909 E36 469 494 529 557 585<br />

E19 2,656 2,797 2,997 3,156 3,314 E37 1,241 1,307 1,401 1,475 1,548<br />

E2 849 894 958 1,009 1,059 E4 1,506 1,586 1,700 1,790 1,879<br />

E20 807 850 911 959 1,007 E5 1,583 1,667 1,786 1,881 1,975<br />

E21 2,232 2,351 2,519 2,652 2,785 E51 554 583 625 658 691<br />

E22 1,888 1,988 2,131 2,243 2,355 E6 1,379 1,452 1,556 1,639 1,720<br />

E23 1,913 2,015 2,159 2,273 2,387 E7 2,113 2,225 2,385 2,511 2,636<br />

E24 2,950 3,107 3,329 3,505 3,680 E8 1,678 1,767 1,894 1,994 2,093<br />

E25 3,192 3,361 3,602 3,793 3,982 E9 2,862 3,014 3,230 3,401 3,571<br />

Table 7 shows the low growth forecasts for companies other than engines in the same 15-<br />

year time span. In 2005, there were only six units, BP-23, BP-33, BP-4, RL-14, RL-16, and RL-<br />

25 that exceed 1,000 calls per year. Only one <strong>of</strong> these units, BP-23 is projected to surpass 1500<br />

calls per year under the low growth impact projections.<br />

Table 7: Low Growth Impact, Non-Engine Companies, 2005–2020<br />

Unit 2005 2006 2010 2015 2020 Unit 2005 2006 2010 2015 2020<br />

206 6 6 7 7 7 C3 403 424 455 479 503<br />

212 3 3 3 4 4 C4 308 324 348 366 384<br />

301 1 1 1 1 1 C5 351 370 396 417 438<br />

317 3 3 3 4 4 C6 357 376 403 424 445<br />

401 1 1 1 1 1 DEPCH 22 23 25 26 27<br />

402 1 1 1 1 1 F125 2 2 2 2 2<br />

406 1 1 1 1 1 F531 1 1 1 1 1<br />

600 1 1 1 1 1 F533 273 287 308 324 341<br />

607 3 3 3 4 4 F721 390 411 440 463 487<br />

609 3 3 3 4 4 F722 397 418 448 472 495<br />

611 1 1 1 1 1 HM5 300 316 339 356 374<br />

614 5 5 6 6 6 HM55 32 34 36 38 40<br />

623 1 1 1 1 1 HT24 1 1 1 1 1<br />

329D 33 35 37 39 41 R8 806 849 910 958 1,006<br />

AIR1 465 490 525 553 580 RL1 692 729 781 822 863<br />

AR401 199 210 225 236 248 RL14 1,079 1,136 1,218 1,282 1,346<br />

AR402 172 181 194 204 215 RL15 923 972 1,042 1,097 1,152<br />

AR403 196 206 221 233 245 RL16 1,009 1,063 1,139 1,199 1,259<br />

AR404 6 6 7 7 7 RL18 727 766 820 864 907<br />

AR405 27 28 30 32 34 RL22 734 773 828 872 916<br />

AR406 23 24 26 27 29 RL25 1,078 1,135 1,217 1,281 1,345<br />

BP13 861 907 972 1,023 1,074 RL30 812 855 916 965 1,013<br />

TriData, a Division <strong>of</strong> 27<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Unit 2005 2006 2010 2015 2020 Unit 2005 2006 2010 2015 2020<br />

BP15 452 476 510 537 564 RL31 866 912 977 1,029 1,080<br />

BP2 810 853 914 962 1,011 RL34 668 703 754 794 833<br />

BP20 609 641 687 724 760 RL6 589 620 665 700 735<br />

BP23 1,234 1,300 1,393 1,466 1,539 RL7 829 873 936 985 1,034<br />

BP25 404 425 456 480 504 RL9 910 958 1,027 1,081 1,135<br />

BP27 564 594 636 670 704 TK27 133 140 150 158 166<br />

BP28 644 678 727 765 803 TK33 76 80 86 90 95<br />

BP3 853 898 963 1,014 1,064 TK34 52 55 59 62 65<br />

BP32 219 231 247 260 273 TK35 64 67 72 76 80<br />

BP33 1,065 1,122 1,202 1,265 1,329 TK36 96 101 108 114 120<br />

BP35 688 725 776 818 858 TK37 54 57 61 64 67<br />

BP36 462 487 521 549 576 TP27 1 1 1 1 1<br />

BP37 568 598 641 675 709 TP28 1 1 1 1 1<br />

BP4 1,009 1,063 1,139 1,199 1,259 TP33 1 1 1 1 1<br />

C1 567 597 640 674 707 TP34 22 23 25 26 27<br />

C2 437 460 493 519 545 TPR22 29 31 33 34 36<br />

High Growth Scenario – The complement to the best case scenario, the upper boundary<br />

forecast for unit workload, is shown in Table 8. This projection series again assumes response<br />

protocols and incident type proportions will remain at 2005 levels. A better projection, used in<br />

other cities, projects demand by type <strong>of</strong> call and then studies the results. We had to modify this<br />

study approach because data by type <strong>of</strong> call was not available. The present method still gives an<br />

idea <strong>of</strong> what can be expected if a lid is put on demand via prevention or other methods. The<br />

increased utilization <strong>of</strong> services model discussed in the Demand Analysis section is applied to<br />

this fixed ratio <strong>of</strong> incidents to responses. These unit response totals are therefore a good deal<br />

higher. They represent the worst-case scenario for department workload. Note that six units are<br />

projected to surpass 3,000 calls by 2010 vs. four in the low growth scenario, and four units<br />

would surpass the extremely high use threshold at 4,000 incidents by 2015 and six by 2020.<br />

Table 8: High Growth Impact on Engine Company Responses, 2005–2020<br />

Year 2005 2006 2010 2015 2020 Year 2005 2006 2010 2015 2020<br />

E1 2,160 2,352 2,694 3,188 3,640 E27 573 624 715 846 966<br />

E10 2,044 2,225 2,549 3,017 3,444 E28 625 680 779 922 1,053<br />

E11 1,531 1,667 1,909 2,259 2,580 E3 1,581 1,721 1,972 2,333 2,664<br />

E12 2,199 2,394 2,742 3,245 3,706 E30 1,992 2,169 2,484 2,940 3,357<br />

E13 1,083 1,179 1,351 1,598 1,825 E31 1,924 2,095 2,399 2,839 3,242<br />

E14 1,932 2,103 2,409 2,851 3,256 E32 249 271 311 367 420<br />

E15 2,415 2,629 3,012 3,564 4,069 E33 1,265 1,377 1,577 1,867 2,132<br />

E16 1,962 2,136 2,447 2,896 3,306 E34 2,188 2,382 2,728 3,229 3,687<br />

E17 2,745 2,989 3,423 4,051 4,626 E35 1,086 1,182 1,354 1,603 1,830<br />

TriData, a Division <strong>of</strong> 28<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Year 2005 2006 2010 2015 2020 Year 2005 2006 2010 2015 2020<br />

E18 1,530 1,666 1,908 2,258 2,578 E36 469 511 585 692 790<br />

E19 2,656 2,892 3,312 3,920 4,476 E37 1,241 1,351 1,548 1,832 2,091<br />

E2 849 924 1,059 1,253 1,431 E4 1,506 1,640 1,878 2,223 2,538<br />

E20 807 879 1,006 1,191 1,360 E5 1,583 1,723 1,974 2,336 2,668<br />

E21 2,232 2,430 2,783 3,294 3,761 E51 554 603 691 818 934<br />

E22 1,888 2,056 2,354 2,786 3,181 E6 1,379 1,501 1,720 2,035 2,324<br />

E23 1,913 2,083 2,386 2,823 3,224 E7 2,113 2,300 2,635 3,118 3,561<br />

E24 2,950 3,212 3,679 4,354 4,971 E8 1,678 1,827 2,093 2,476 2,828<br />

E25 3,192 3,475 3,981 4,711 5,379 E9 2,862 3,116 3,569 4,224 4,823<br />

As with the low growth projections we also looked at non-engine company responses<br />

using this higher growth pr<strong>of</strong>ile. Table 9 shows the results. Using this projection, there will be<br />

eight units that surpass 1,500 calls per year and three that exceed 1,400 calls per year by 2020.<br />

Table 9: High Growth Impact, Non-Engine Companies, 2005–2020<br />

Year 2005 2006 2010 2015 2020 Year 2005 2006 2010 2015 2020<br />

206 6 7 7 9 10 C3 403 439 503 595 679<br />

212 3 3 4 4 5 C4 308 335 384 455 519<br />

301 1 1 1 1 2 C5 351 382 438 518 591<br />

317 3 3 4 4 5 C6 357 389 445 527 602<br />

401 1 1 1 1 2 DEPCH 22 24 27 32 37<br />

402 1 1 1 1 2 F125 2 2 2 3 3<br />

406 1 1 1 1 2 F531 1 1 1 1 2<br />

600 1 1 1 1 2 F533 273 297 340 403 460<br />

607 3 3 4 4 5 F721 390 425 486 576 657<br />

609 3 3 4 4 5 F722 397 432 495 586 669<br />

611 1 1 1 1 2 HM5 300 327 374 443 506<br />

614 5 5 6 7 8 HM55 32 35 40 47 54<br />

623 1 1 1 1 2 HT24 1 1 1 1 2<br />

329D 33 36 41 49 56 R8 806 878 1,005 1,190 1,358<br />

AIR1 465 506 580 686 784 RL1 692 753 863 1,021 1,166<br />

AR401 199 217 248 294 335 RL14 1,079 1,175 1,346 1,592 1,818<br />

AR402 172 187 214 254 290 RL15 923 1,005 1,151 1,362 1,555<br />

AR403 196 213 244 289 330 RL16 1,009 1,099 1,258 1,489 1,700<br />

AR404 6 7 7 9 10 RL18 727 792 907 1,073 1,225<br />

AR405 27 29 34 40 45 RL22 734 799 915 1,083 1,237<br />

AR406 23 25 29 34 39 RL25 1,078 1,174 1,344 1,591 1,817<br />

BP13 861 937 1,074 1,271 1,451 RL30 812 884 1,013 1,198 1,368<br />

BP15 452 492 564 667 762 RL31 866 943 1,080 1,278 1,459<br />

BP2 810 882 1,010 1,195 1,365 RL34 668 727 833 986 1,126<br />

TriData, a Division <strong>of</strong> 29<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

II. Risk and Demand<br />

Year 2005 2006 2010 2015 2020 Year 2005 2006 2010 2015 2020<br />

BP20 609 663 759 899 1,026 RL6 589 641 734 869 993<br />

BP23 1,234 1,343 1,539 1,821 2,079 RL7 829 903 1,034 1,223 1,397<br />

BP25 404 440 504 596 681 RL9 910 991 1,135 1,343 1,533<br />

BP27 564 614 703 832 950 TK27 133 145 166 196 224<br />

BP28 644 701 803 950 1,085 TK33 76 83 95 112 128<br />

BP3 853 929 1,064 1,259 1,437 TK34 52 57 65 77 88<br />

BP32 219 238 273 323 369 TK35 64 70 80 94 108<br />

BP33 1,065 1,159 1,328 1,572 1,795 TK36 96 105 120 142 162<br />

BP35 688 749 858 1,015 1,159 TK37 54 59 67 80 91<br />

BP36 462 503 576 682 779 TP27 1 1 1 1 2<br />

BP37 568 618 708 838 957 TP28 1 1 1 1 2<br />

BP4 1,009 1,099 1,258 1,489 1,700 TP33 1 1 1 1 2<br />

C1 567 617 707 837 955 TP34 22 24 27 32 37<br />

C2 437 476 545 645 736 TPR22 29 32 36 43 49<br />

The high growth scenario, not surprisingly, shows a department that will be much busier<br />

than it is today. 18 engine companies are projected to be above the 3,000 response threshold by<br />

2020, with several above the 4,000 response threshold. At this level units are frequently<br />

unavailable to meet calls for service and neighboring units must be deployed to neighboring<br />

territories, sharply increasing response time. Often the neighboring unit will be very busy, too.<br />

Response times degrade even farther as more distant units are called to respond, or gaps in<br />

coverage occur. This cascading effect can drastically slow response times to much <strong>of</strong> the city.<br />

E15, E19, E24, E25, and E9 are projected to be above the extremely high threshold under the<br />

high growth scenario. The city will likely have to consider staffing an additional unit in each <strong>of</strong><br />

these engines’ first run areas if the scenarios materialize.<br />

TriData, a Division <strong>of</strong> 30<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. DETERMINING RESOURCE NEEDS<br />

When, where, and how much are the common questions asked by administrators, city or<br />

county council, and citizens when it comes to determining the resources government should<br />

provide. Determining the proper level <strong>of</strong> fire department resources involves asking the same<br />

questions while balancing the safety concerns <strong>of</strong> citizens and the financial situation <strong>of</strong> the local<br />

government.<br />

Of the ‘when, where, and how’ questions “where” the number and location <strong>of</strong> fire<br />

stations is the biggest question and has the most impact on other decisions. Some <strong>of</strong> the areas it<br />

can impact include: how many units are needed, how big should they be, and when should the<br />

units be deployed. All <strong>of</strong> these impact overall cost. Poorly placed fire stations, apparatus, and<br />

personnel <strong>of</strong>ten results in more resources than are needed to provide the desired level <strong>of</strong> service.<br />

The availability <strong>of</strong> land to build on impacts the cost and the size <strong>of</strong> a new station, which can also<br />

impact the types <strong>of</strong> apparatus that can be located at that station.<br />

Deciding how many emergency response resources to deploy, and where, is not an exact<br />

science. There are no perfect deployment models. The ultimate decision is based on a<br />

combination <strong>of</strong> risk analysis, pr<strong>of</strong>essional judgment, and the city’s willingness to accept more or<br />

less risk. Accepting more risk generally means that fewer resources are deployed, though<br />

deploying more resources is no guarantee that loss will be less, especially in the short term.<br />

Obviously, there are many pieces to consider, but there are some good sources to draw on<br />

to help make the decisions. In this chapter we review some <strong>of</strong> the available sources, including the<br />

Insurance Services Office (ISO), the National <strong>Fire</strong> Protection Agency (NFPA), the Center For<br />

Public Safety Excellence/Commission on <strong>Fire</strong> Accreditation International (CFAI), the<br />

Occupational Safety and Health Administration (OSHA), and comparable departments across the<br />

nation. The purpose <strong>of</strong> this review is to outline standards to be used later in the report for<br />

answering the following questions:<br />

• What should the department’s minimum crew size and overall staffing level be?<br />

• Are there opportunities for more effective and/or more efficient use <strong>of</strong> department<br />

resources?<br />

• Are department stations located optimally throughout the city considering the various<br />

services <strong>of</strong>fered by the department?<br />

• How does the level <strong>of</strong> risk in <strong>Oklahoma</strong> <strong>City</strong> compare to other jurisdictions<br />

nationwide?<br />

• How do the services provided by the department correspond to those provided by<br />

similar jurisdictions?<br />

TriData, a Division <strong>of</strong> 31 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

SOURCES TO AID IN DEVELOPING CRITERIA<br />

A number <strong>of</strong> sources have developed criteria that are widely used in decision-making or<br />

deployment <strong>of</strong> resources. Ultimately is it judgment, not following any other source to determine<br />

what is best for <strong>Oklahoma</strong> <strong>City</strong>. Most <strong>of</strong> the so-called standards are not based on extensive<br />

research but are written by committees with limited data available. .<br />

Insurance Services Office (ISO) – The ISO is a national insurance engineering service<br />

organization that assigns a public protection classification (PPC) to jurisdictions based on fire<br />

department services. Insurance companies typically establish insurance rates for individual<br />

occupancies or groups <strong>of</strong> occupancies based on the PPC. PPCs are established using the ISO’s<br />

<strong>Fire</strong> Suppression Rating Schedule (FSRS). Once widely used by fire departments to evaluate<br />

system performance, the FSRS’s use is somewhat limited in that it only evaluates fire protection<br />

(not EMS, which most fire departments now provide to some degree). Also, the FSRS does not<br />

consider efficiency (e.g., how many resources are deployed in comparison to the number <strong>of</strong><br />

actual calls). Though not as widely used now, ISO ratings are still appropriate to consider as part<br />

<strong>of</strong> a more comprehensive system performance review. Combined with other assessments, ISO<br />

standards are useful, but not by themselves.<br />

ISO RATING: To analyze a community’s fire protection, the ISO uses a grading system<br />

<strong>of</strong> 1 to 10. A community protection factor <strong>of</strong> one is the highest possible grade with insurance<br />

rates likely to be lowest for the community (ratings increase by 1 for every 10 credits, e.g., Class<br />

1 = 90.00+ credits, Class 2 = 80.00-89.99, Class 3 = 70.00-79.99, etc.). A community with a<br />

Class 10 rating means that there essentially is no recognized fire protection system or availability<br />

<strong>of</strong> water for fire suppression. Only a very small number <strong>of</strong> communities with very effective<br />

water distribution systems and mostly career fire departments are able to achieve a rating <strong>of</strong> one.<br />

<strong>Oklahoma</strong> <strong>City</strong> was last evaluated by the ISO in 1994 and currently holds a #3 rating.<br />

In 2000, the nation’s largest home insurance carrier, State Farm, announced it would<br />

cease to use the ISO PPC as the basis for its home insurance rates, and would use its own internal<br />

data to determine rates. While the exact effects <strong>of</strong> this are yet to be seen, for economic reasons it<br />

is unlikely that State Farm’s rates will be much different than those determined by the ISO<br />

method. In addition, most insurance carriers band groups <strong>of</strong> ratings together for efficiency; thus,<br />

there may be no difference in treatment <strong>of</strong> a Class 1 versus a Class 4. Therefore, depending on<br />

the rating system used by individual insurance carriers in <strong>Oklahoma</strong> <strong>City</strong>, there may be little or<br />

no fiscal advantage to property owners by being in a certain PPC.<br />

TriData, a Division <strong>of</strong> 32<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

According to a report issued by the ICMA in 2002:<br />

In its practical application, the rating schedule is a tool used for assessing<br />

the insurance rate charged in a specific community on a specific property.<br />

Generally, the better the rating schedule classification, the lower the<br />

insurance premium charged. Although one cannot say with certainty what<br />

the effect <strong>of</strong> an improved rating schedule classification might be in a<br />

specific community, improvements in the classification in communities<br />

with between 10 and 5 tend to result in lower insurance premiums for<br />

residential properties. Improvements when the community has ratings<br />

better than five can result in lower premiums on commercial and industrial<br />

properties but will usually have a negligible effect on premiums for<br />

residential properties. 23<br />

ISO ratings are somewhat limited in their application because they are related mostly to<br />

the performance <strong>of</strong> the water system and water pressure to deal with a large-scale fire, rather<br />

than the every day house fire (40 percent <strong>of</strong> the rating is based on water availability for fire<br />

suppression). As noted in the ISO’s <strong>Fire</strong> Suppression Rating Schedule, “The Schedule is a fire<br />

insurance rating tool, and is not intended to analyze all aspects <strong>of</strong> a comprehensive public fire<br />

protection program. It should not be used for purposes other than insurance rating”. 24 A<br />

community may have an excellent fire department and communications system, but it may have<br />

a higher numerical rating if the water distribution system is not constructed to ISO standards.<br />

The three components evaluated by ISO in making a final determination <strong>of</strong> rates are:<br />

• <strong>Fire</strong> department: number <strong>of</strong> engines, training, personnel, procedures, etc. (50 percent).<br />

Equipment accounts for 26 percent, personnel for 15 percent, and training for the<br />

remaining 9 percent.<br />

• Water supply (40 percent).<br />

• Emergency dispatching and communications (10 percent).<br />

A review <strong>of</strong> the <strong>Fire</strong> Suppression Rating Schedule can be useful to city decision-makers<br />

when trying to develop an understanding <strong>of</strong> the components evaluated by ISO engineers as part<br />

<strong>of</strong> their community survey process and as a tool in developing a comprehensive analysis <strong>of</strong> their<br />

fire department. A brief overview <strong>of</strong> the rating system is given below.<br />

<strong>Fire</strong> Department – Fifty percent <strong>of</strong> the overall grading is based on the number <strong>of</strong> engine<br />

companies and the amount <strong>of</strong> water a community needs to fight a fire. ISO reviews the<br />

distribution <strong>of</strong> fire companies throughout the area and checks that the fire department tests its<br />

23 International <strong>City</strong>/County Management Association, Managing <strong>Fire</strong> and Rescue Services, 777 N. Capitol Street,<br />

N.E., Washington, DC, 2002, p. 293.<br />

24 <strong>Fire</strong> Suppression Rating Schedule, Edition 02-03, ISO Properties, Inc., 2003<br />

TriData, a Division <strong>of</strong> 33<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

pumps regularly and inventories each engine company's nozzles, hoses, breathing apparatus, and<br />

other equipment. ISO also reviews the fire company records to determine:<br />

• The types and extent <strong>of</strong> training provided to fire company personnel,<br />

• The number <strong>of</strong> people who participate in training,<br />

• The number <strong>of</strong> firefighters responding to emergencies, and<br />

• The maintenance and testing <strong>of</strong> the fire department's equipment.<br />

Water Supply – Forty percent <strong>of</strong> the grading is based on the community's water supply.<br />

This part <strong>of</strong> the survey focuses on whether the community has sufficient water for fire<br />

suppression beyond daily maximum consumption. ISO surveys all components <strong>of</strong> the water<br />

supply system, including pumps, storage, and filtration. Observations <strong>of</strong> the tests at<br />

representative locations in the community are used to determine the rate <strong>of</strong> flow the water mains<br />

provide. Finally, the distribution <strong>of</strong> fire hydrants is examined to ensure that no location is more<br />

than 1,000 feet from the closest hydrant.<br />

Under the guidelines established by ISO, a community is eligible for Class 8 or better<br />

rating if the municipal water supply is capable <strong>of</strong> delivering at least 250-gallons per minute<br />

(gpm) for a period <strong>of</strong> at least two hours. The 250-gallon per minute flow is in addition to the<br />

daily maximum rate <strong>of</strong> consumption.<br />

Dispatch and Communications – Ten percent <strong>of</strong> the overall grading is based on how<br />

well the fire department receives and dispatches fire alarms. Field representatives evaluate the<br />

communications center looking at the number <strong>of</strong> operators at the center, telephone service<br />

(includes the number <strong>of</strong> telephone lines coming into the center), and the listing <strong>of</strong> emergency<br />

numbers in the telephone book. Field representatives also look at the dispatch circuits and how<br />

the center notifies firefighters about the location <strong>of</strong> the emergency.<br />

National <strong>Fire</strong> Protection Association (NFPA) – The NFPA is an international,<br />

nonpr<strong>of</strong>it organization dedicated to reducing the worldwide burden <strong>of</strong> fire and other hazards on<br />

the quality <strong>of</strong> life by developing and advocating scientifically based consensus codes and<br />

standards, research, training, and education. The NFPA recommendations are standards and<br />

guidelines developed by committees <strong>of</strong> chief <strong>of</strong>ficers, volunteer representatives, union <strong>of</strong>ficials,<br />

and industry representatives. Although the NFPA’s standards are not legally binding, they are<br />

<strong>of</strong>ten codified into local ordinances, and it is important to consider NFPA standards whether or<br />

not they are adopted locally since NFPA standards sometimes become the de facto standard for<br />

evaluating different levels <strong>of</strong> fire and emergency service protection.<br />

Center for Public Safety Excellence/Commission on <strong>Fire</strong> Accreditation<br />

International (CFAI) – Another highly influential group, the CFAI consists <strong>of</strong> representatives<br />

from the International Association <strong>of</strong> <strong>Fire</strong> Chiefs (IAFC) and the International <strong>City</strong>/County<br />

Management Association (ICMA). The CFAI and the accreditation process were designed to<br />

TriData, a Division <strong>of</strong> 34<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

establish industry-wide performance measures for overall organizational performance and the<br />

establishment <strong>of</strong> the standard for a jurisdiction is purely voluntary. While a small fraction <strong>of</strong> fire<br />

departments across the nation (about 100) have gone through the accreditation process and others<br />

are working toward that goal, most departments are focusing on the creation <strong>of</strong> a “Standards <strong>of</strong><br />

Response Coverage” document (one <strong>of</strong> four items required for accreditation). The standard <strong>of</strong><br />

coverage concept has become proven so useful that the CFAI expanded the original 44-page<br />

chapter into a 190+ page “how-to” manual.<br />

The CFAI does not make many explicit recommendations on standards for fire/EMS<br />

departments to adopt. Rather, it encourages a thorough assessment <strong>of</strong> risks in the community,<br />

public expectations and the resources needed to meet expectations given the risks. The creation<br />

<strong>of</strong> written standards should then be based on that assessment. Part <strong>of</strong> the methodology for setting<br />

standards includes looking at what other, similar communities are doing.<br />

Occupational Safety and Health Administration (OSHA) – OSHA develops<br />

regulations to protect workers from occupational injuries and illnesses. While there are many<br />

regulations that apply to firefighting operations, one <strong>of</strong> the most critical is 29 CFR 1910.134,<br />

which addresses requirements for respiratory protection in IDLH (immediately dangerous to life<br />

and health) atmospheres, including structural firefighting. In such cases, personnel are required<br />

to work in teams <strong>of</strong> two, with two personnel operating inside the IDLH and two personnel<br />

standing by outside the IDLH in the event the entry team becomes incapacitated. This regulation<br />

is most commonly referred to as the “Two-in/Two-out” rule.<br />

RESPONSE TIMES<br />

Response time is one <strong>of</strong> the most common performance measures used by the fire service<br />

because it is understood by citizens, easy to compute, and useful in the evaluation <strong>of</strong> end results.<br />

It is the way most citizens evaluate the level <strong>of</strong> service provided; though, response time itself<br />

really is not a measure <strong>of</strong> the quality <strong>of</strong> service, though it does reflect the timeliness <strong>of</strong> service,<br />

an attribute desired by citizens.<br />

While demand for services and individual unit workloads dictate how many stations and<br />

apparatus are needed in a community (discussed later in this chapter), response times dictate<br />

where specific resources should be placed. There is, however, no single set <strong>of</strong> nationally<br />

accepted response time standards.<br />

Measurement Methodology – To determine overall response time, the clock starts<br />

when an individual calls 911 (or alternate emergency number) and stops when the first<br />

emergency provider arrives at patient’s side or the scene <strong>of</strong> the incident.<br />

Several caveats should be kept in mind. First, response times are subject to a variety <strong>of</strong><br />

measurement errors and only measure one aspect <strong>of</strong> overall system performance. For example,<br />

response times are distorted when units report their arrival on scene either early or late. Second,<br />

TriData, a Division <strong>of</strong> 35<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

response times are frequently not comparable across fire-rescue systems because <strong>of</strong> the differing<br />

manners in which they are calculated. Not all departments track vertical response times (that is,<br />

the time from arrival on scene to patient contact), so their total response times likely would be<br />

lower than the total response times <strong>of</strong> a department that does track them.<br />

Many fire/EMS departments report average response times while others report fractile<br />

response times. 25 Average response times have been increasingly less used by the emergency<br />

service industry because small numbers <strong>of</strong> very short or long responses—<strong>of</strong>ten recorded in<br />

error—can distort the results. Also, the public is interested in how fast a system responds in most<br />

cases (fractile) rather than usually (average). More and more departments are adopting the 90 th<br />

percentile for reporting response times (mostly due to NFPA 1710’s use <strong>of</strong> this measure).<br />

A fractile response time <strong>of</strong> x at the 90 th percentile means that units respond in x minutes,<br />

or less, 90 percent <strong>of</strong> the time. The remainder beyond the compliance fractile (90 th percentile in<br />

this case) is the operational tolerance for the system, meaning the system is designed with the<br />

understanding that 10 percent <strong>of</strong> the calls will have response times that exceed the target.<br />

Although it is possible to design a system that may ensure rapid response close to 100 percent <strong>of</strong><br />

the time, it is generally not cost-effective.<br />

Response times here are defined to include four components, that are further illustrated in<br />

Figure 6.<br />

Call Processing and Dispatch – This time begins when the call taker/dispatcher answers<br />

the 911 call and ends when the first unit is dispatched.<br />

Turnout – This is the time elapsed from dispatch to departure from the station (or other<br />

location); it comprises activities such as donning protective gear and boarding the apparatus.<br />

Travel – This period begins with departure from the station and ends when the unit<br />

advises that they are on the scene. It does not include the time to actually reach the fire or patient<br />

after arrival at the street location <strong>of</strong> the incident.<br />

Vertical – This is the amount <strong>of</strong> time from arrival at the scene to arrival at the side <strong>of</strong> the<br />

patient or the site <strong>of</strong> the fire. It may include going up a high-rise (and hence the term vertical<br />

response) or traveling within a hospital, golf course, factory, or other expansive site to get to the<br />

site <strong>of</strong> a fire or the side <strong>of</strong> a patient.<br />

Figure 6 illustrates the public conception <strong>of</strong> response times. The illustration shows the<br />

progression from the receipt <strong>of</strong> the emergency call and includes turnout and travel times, both on<br />

the streets and then vertical if necessary.<br />

25 Fractile measurement reports the percentage <strong>of</strong> calls responded to in x minutes.<br />

TriData, a Division <strong>of</strong> 36<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Figure 6: Components <strong>of</strong> Total Response Time<br />

Response Time<br />

(lay public conception)<br />

911 call Units Apparatus First unit Arrival at<br />

received dispatched en route on scene patient/fire<br />

Call Processing – Begins when<br />

the emergency call is answered<br />

and ends when emergency<br />

responders are dispatched to the<br />

identified address <strong>of</strong> the call.<br />

Additional activities and<br />

information gathering may take<br />

place after notification <strong>of</strong><br />

responders, but this is not included<br />

in call processing time.<br />

Turnout – Begins when<br />

emergency responders are<br />

notified and ends when<br />

appropriate emergency<br />

apparatus actually leaves the<br />

station en route to the location<br />

<strong>of</strong> the emergency.<br />

Travel (Drive) – Begins<br />

when the first appropriate<br />

emergency apparatus<br />

actually leaves the station<br />

and ends when the first<br />

appropriate apparatus<br />

arrives at the scene <strong>of</strong> the<br />

emergency.<br />

Vertical – Begins when<br />

the first appropriate<br />

apparatus arrives at the<br />

scene <strong>of</strong> the emergency<br />

and ends when personnel<br />

arrive at the patient’s side<br />

or the fire location.<br />

Most departments do not record the vertical response time component. OCFD currently<br />

records a “with patient” time for EMS calls. During FY 2005 42 percent (24,919) <strong>of</strong> all incidents<br />

with a OCFD unit arriving on-scene had a “with patient” time recorded. While this is better data<br />

than is available in most departments, there is room for improvement. Given the number <strong>of</strong> highrises,<br />

large facilities (i.e. malls, hospitals, schools), and large open areas (parks) in <strong>Oklahoma</strong><br />

<strong>City</strong>, this component has the potential to be significant. In FY 2005, vertical response time<br />

averaged 1:44 in <strong>Oklahoma</strong> <strong>City</strong>. (Response times are discussed in more detail in Chapter IV.)<br />

Recommendation 3: Continue tracking vertical response times and expand the<br />

program to include all call types. While this time is nearly impossible to reduce, it is important<br />

to assess its impact on total response time and determine whether other components should be<br />

reduced to compensate for the vertical response component to maintain total response time goals.<br />

For example, buildings with average vertical response times over two minutes and over x calls<br />

per year may be classified as higher priority locations and resources placed closer in order to<br />

reduce total response times.<br />

Importance <strong>of</strong> Response Times – While the speed <strong>of</strong> response is not directly indicative<br />

<strong>of</strong> outcome or quality, response times do affect the number <strong>of</strong> lives saved and the extent <strong>of</strong><br />

property losses averted when an emergency occurs. This means that while arriving in<br />

3 or 4 minutes every time does not guarantee everyone will live and there will be less damage,<br />

more people can be helped or the fire can be put out before the entire building is consumed when<br />

emergency personnel arrive in 5 minutes rather than 10 or 20.<br />

<strong>Fire</strong> spreads quickly after ignition and the faster it is found and extinguished, the better<br />

the results; similar to someone suffering from life threatening symptoms, the probability <strong>of</strong><br />

survival increases the quicker the patient is treated.<br />

Despite these general observations, current statistical models cannot realistically assess<br />

nor predict the quality <strong>of</strong> fire services in terms <strong>of</strong> lives saved and property losses averted. In<br />

place <strong>of</strong> true measures <strong>of</strong> fire rescue service outcome, response time is <strong>of</strong>ten used as a proxy<br />

measure.<br />

TriData, a Division <strong>of</strong> 37<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Figure 7 depicts the fire propagation curve, which shows the effect <strong>of</strong> time and<br />

temperature rise <strong>of</strong> a free-burning fire on the destruction <strong>of</strong> property. According to multiple<br />

studies, extension <strong>of</strong> the fire beyond the room <strong>of</strong> origin begins approximately 6 to 8 minutes after<br />

ignition, and flashover <strong>of</strong> the room <strong>of</strong> origin occurs within 10 minutes <strong>of</strong> ignition. (Flashover is<br />

the simultaneous ignition <strong>of</strong> all flammable material in an enclosed area. 26 ) In some modern<br />

rooms with low ceiling and plastics, flashover can occur in two to four minutes, according to<br />

studies by the National Institute <strong>of</strong> Standards and Technology.<br />

Figure 7: <strong>Fire</strong> Propagation Curve<br />

Source: <strong>Fire</strong> Protection Handbook, 18th Ed., National <strong>Fire</strong> Protection Association<br />

Response Time Standards: <strong>Fire</strong>/Rescue Service – The most widely recognized<br />

standard used in response time analysis is outlined in NFPA 1710, Organization and Deployment<br />

<strong>of</strong> <strong>Fire</strong> Suppression Operations, Emergency Medical Operations and Special Operations to the<br />

Public by Career <strong>Fire</strong> Departments.<br />

NFPA 1710 was established in 2001 and contains two recommendations that caught the<br />

attention <strong>of</strong> fire service managers and city administrators across the nation. The standard<br />

recommends 4-person staffing for all engine and truck companies (discussed later), and a<br />

5-minute dispatch-to-arrival time to be met on 90 percent <strong>of</strong> calls. The time increases to<br />

6-minutes when one minute is added for call processing/dispatch time, as recommended in<br />

NFPA 1221, Standard for the Installation, Maintenance, and Use <strong>of</strong> Emergency Services<br />

Communications Systems. The 5-minute period includes 1 minute for turnout time and 4 minutes<br />

for travel. The travel time translates to a driving distance <strong>of</strong> 2 miles from the first-due fire station<br />

26 http://en.wikipedia.org/wiki/Flashover<br />

TriData, a Division <strong>of</strong> 38<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

to the incident (driving at an average speed <strong>of</strong> 30 mph). Detailed data regarding response times<br />

for <strong>Oklahoma</strong> <strong>City</strong> are discussed in later chapters.<br />

Again, like all NFPA standards, NFPA 1710 may be adopted by a local jurisdiction, but<br />

is not mandatory. Unlike many NFPA standards, NFPA 1710 is not based on much <strong>of</strong> a research<br />

foundation, but rather is the majority vote reflecting experience and opinion <strong>of</strong> a committee,<br />

within which there was much disagreement. There is no published information on the expected<br />

reductions in losses or injuries as a function <strong>of</strong> increased staffing and only a little on the effect <strong>of</strong><br />

increased response times. Nevertheless, despite having been formulated largely on the basis <strong>of</strong><br />

expert opinions and task sequencing (what must be done and how many it takes to do it) rather<br />

than research, NFPA 1710 has become the de facto benchmark for the emergency response<br />

community. Of note, all groups have not embraced NFPA 1710, including the ICMA.<br />

In addition to the NFPA, the CFAI found that departments average 50 seconds for call<br />

processing/dispatch time. This is actually a far less stringent goal than 60 seconds 90 percent <strong>of</strong><br />

the time since an average is closer to the 50 th percentile. The CFAI also found a 60-second<br />

average for turnout time. The CFAI baselines were developed by analyzing response records<br />

from multiple departments over a decade ago. The new CFAI document, Creating and<br />

Evaluating Standards <strong>of</strong> Response Coverage for <strong>Fire</strong> Departments, now recommends using<br />

fractile measurements rather than averages but does not <strong>of</strong>fer recommendations on response time<br />

goals.<br />

Response Time Standards: Emergency Medical Services – One method <strong>of</strong> measuring<br />

and evaluating response times is to count the number <strong>of</strong> patients who survive to the point <strong>of</strong><br />

being released from a hospital. Although survival is not solely a function <strong>of</strong> the timeliness <strong>of</strong><br />

care, time is crucial to a critically injured or seriously ill patient. Guidelines published by Basic<br />

Trauma Life Support International (a widely known training institute) suggest that a trauma<br />

patient’s odds <strong>of</strong> survival are directly linked to the amount <strong>of</strong> time that elapses between the<br />

injury and definitive surgical treatment. 27<br />

Prevention <strong>of</strong> death and disability secondary to acute coronary syndromes is also an issue<br />

<strong>of</strong> time. The American Heart Association 2005 guidelines for CPR and Emergency Cardiac Care<br />

emphasize the importance <strong>of</strong> shortening response time to suspected cardiac arrest patients. 28<br />

If brain tissues are deprived <strong>of</strong> oxygen, they will begin to die within four to six minutes.<br />

For that reason it is imperative to begin resuscitation measures as soon as possible. A recent<br />

27 Campell JE. (Ed.). 2000. Basic Trauma Life Support for Paramedics and Other Advanced Providers (4 th ed).<br />

Englewood Cliffs, NJ: Prentice-Hall. pp. 24-26.<br />

28 AHA. 2005. Highlights <strong>of</strong> the 2005 American Heart Association Guidelines for Cardiopulmonary Resuscitation<br />

and Emergency Cardiovascular Care. Currents in Emergency Cardiovascular Care, 16(4), 1-25.<br />

TriData, a Division <strong>of</strong> 39<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

study in Ottawa, Ontario, found that defibrillation was most effective if it was provided within<br />

six minutes <strong>of</strong> the patient’s initial collapse. 29 , 30<br />

The study also found the following:<br />

Effectiveness decreased significantly as the interval between cardiac arrest and<br />

defibrillation increased between six and 11 minutes.<br />

After 11 minutes, the odds <strong>of</strong> patient survival were extremely poor.<br />

The odds <strong>of</strong> patient survival were doubled if ALS (paramedic) care was provided<br />

alongside BLS (layperson/police <strong>of</strong>ficer/EMT) defibrillation at all points prior to 11 minutes. 31<br />

The American College <strong>of</strong> Emergency Physicians noted that for every minute <strong>of</strong> cardiac<br />

arrest the chance <strong>of</strong> survival decreases up to 10 percent. EMS systems should attempt to achieve<br />

travel times <strong>of</strong> 3–4 minutes for medical first response and 6–8 minutes for advanced life support<br />

ambulance transport. 32<br />

Nationally, the closest thing to a response time standard for paramedic (ALS) transport<br />

units in an urban/suburban EMS system with automatic defibrillation-capable first responders is<br />

8 minutes in 90 percent <strong>of</strong> the critical (i.e., life-threatening) calls. This de facto standard is an<br />

amalgamation <strong>of</strong> generally accepted criteria or rules-<strong>of</strong>-thumb. No standards-making consensus<br />

group has ever formally defined a standard for ambulance response times. Generally, various<br />

EMS systems interpret the idea <strong>of</strong> a standard in two ways. Some jurisdictions view the 8-minute<br />

standard to mean 8 minutes and all <strong>of</strong> the 59 seconds that follow; other jurisdictions view it as 8<br />

minutes exactly. The latter, more stringent definition is suggested and is more consistent with the<br />

medical principles on which it is based. In <strong>Oklahoma</strong> <strong>City</strong>, ALS first responder services are<br />

provided by the engine companies and not by transport-capable medic units; therefore, the<br />

response time for the first arriving unit is the same as the NFPA 1710 6-minute response time.<br />

This form <strong>of</strong> response time measurement is called a fractile response time because it is<br />

stated in terms <strong>of</strong> the fraction <strong>of</strong> calls responded to within a specified time. A fractile response<br />

time standard specifically acknowledges that there will be some response time outliers in even<br />

the best-performing EMS systems. In this case, 10 percent <strong>of</strong> calls can have response times<br />

29 Defibrillation is a critical intervention that can be provided by paramedics using manual defibrillators, or by<br />

laypersons, police <strong>of</strong>ficers, or EMTs using automatic external defibrillators.<br />

30 USA Today ran a series <strong>of</strong> investigative reporting articles on EMS services across the country (July 28-30, 2003).<br />

The title <strong>of</strong> one article was “Six Minutes To Live or Die.” In this article, new research was cited from the Mayo<br />

Clinic that suggested the six-minute mark is when lives are saved or lost.<br />

31 Nichol G, Stiell IG, Laupacis A, Pham B, De Maio VJ, and Wells GA. 1999. “A Cumulative Meta-Analysis <strong>of</strong> the<br />

Effectiveness <strong>of</strong> Defibrillator-Capable Emergency Medical Services for Victims <strong>of</strong> Out-<strong>of</strong>-Hospital Cardiac Arrest.”<br />

Annals <strong>of</strong> Emergency Medicine, 34 (4 pt. 1): 517-25.<br />

32 Pratt, F. D. & Overton, J. (2005). Ground Transport Ambulances. In Brennan, J.A. & Krohmer, J.R. [Eds.].<br />

American College <strong>of</strong> Emergency Physicians Principles <strong>of</strong> Emergency Medical Services Systems, [3 rd Ed.]. Boston:<br />

Jones and Bartlett Publishers.<br />

TriData, a Division <strong>of</strong> 40<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

greater than 8 minutes and the system can still meet the standard. The standard specifically does<br />

not use average response time as its measurement because arithmetic averages can be distorted<br />

by a small number <strong>of</strong> outliers.<br />

Factors Impacting Response Time Goals – Decisions about response time goals are<br />

not easy to make. Although the standards discussed above provide a framework for setting goals,<br />

it is ultimately up to the municipal government policymakers and the fire department to<br />

determine appropriate response times and service levels based on the needs <strong>of</strong> the community<br />

they serve. Common factors that should be taken into account include population density, call<br />

volume and distribution by type <strong>of</strong> call, land use, and available resources. Whether or not to<br />

apply new technology, such as automatic vehicle locators and traffic preemption devices, is also<br />

important as these can improve response times, even without building new stations.<br />

POPULATION DENSITY: Population density is the most basic and common measure used<br />

to define whether an area is urban, suburban, or rural. In many ways it determines the other<br />

factors listed above. That is, the more people you have in an area, the higher and more<br />

concentrated your call volume will be.<br />

The U.S. Census defines urban and rural areas on multiple levels. On a county or city<br />

scale, the simplified Census definition <strong>of</strong> an urban area is an area with at least 1,000 people per<br />

square mile. All other areas are rural. However, this definition does not have a middle ground—<br />

suburban.<br />

Suburban is a vague and somewhat subjective idea, which makes it the most difficult type<br />

<strong>of</strong> area to define. Suburban areas tend to be mostly residential and are generally on the edges <strong>of</strong><br />

urban areas. We divide areas into urban, suburban, and rural by population as follows:<br />

• Urban – 2,000+ people/sq. mile or incorporated<br />

• Suburban – 1,000–1,999 people /sq. mile or within one mile <strong>of</strong> a city’s limits<br />

• Rural – under 1,000 people /sq. mile<br />

<strong>Oklahoma</strong> <strong>City</strong> has areas in each <strong>of</strong> the categories above.<br />

SUPPLEMENTAL PROTECTION SYSTEMS: A fire that smolders or burns undetected or is<br />

unreported for a long time may make such sufficient headway as to negate even the fastest<br />

response by a fire department. For example, if the fire burns 20 minutes before it is detected,<br />

even with a five-minute fire department response time, the damage will have been done. These<br />

built-in detection systems and use <strong>of</strong> simple smoke alarms can reduce time to detect, and make a<br />

larger difference than the drive time <strong>of</strong> emergency vehicles. Even better is built-in suppression<br />

systems which not only detect but extinguish or at least old fires in check.<br />

In <strong>Oklahoma</strong> <strong>City</strong> all new high-rise buildings (5 or more stories or 75 or more feet above<br />

the lowest level accessible by fire department) are required to be fit with sprinkler systems. Some<br />

communities have even begun requiring sprinkler systems to be installed in single-family homes.<br />

TriData, a Division <strong>of</strong> 41<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

In 1978 San Clemente, CA, implemented the nation’s first comprehensive and mandatory<br />

residential sprinkler program. Only a few other communities that we are aware <strong>of</strong> have such a<br />

comprehensive program. They include Prince Georges County, MD; Scottsdale, AZ;<br />

Montgomery County, MD; and in August 2006, Frederick County, MD. With residential<br />

sprinklers in place, response times to fire calls in suburban and rural areas (where most new<br />

housing development is taking place throughout the country) can be longer than for urban areas<br />

where the housing stock is older and more likely to be unsprinklered.<br />

TRAFFIC CALMING: Many communities across the nation are installing traffic-calming<br />

devices (speed bumps and speed humps) to reduce vehicle speeds, mostly in residential<br />

neighborhoods. These devices are popular with neighborhood residents, who <strong>of</strong>ten demand them.<br />

However, each speed bump adds an estimated 10 to 12 seconds to emergency apparatus response<br />

times. The installation <strong>of</strong> these devices is a value judgment on the part <strong>of</strong> elected <strong>of</strong>ficials, who<br />

must weigh the satisfaction and possibly improved traffic safety to neighborhoods with the<br />

potential for longer emergency response times and the possible need for additional fire and EMS<br />

resources to compensate for the slower travel times. A study on this trade<strong>of</strong>f undertaken for the<br />

Boulder, CO, <strong>City</strong> Council in 1997 showed that the likely reduction <strong>of</strong> traffic fatalities from the<br />

slowing <strong>of</strong> traffic was far less than the likely increase in deaths from slowing the response to<br />

delayed response for cardiac arrests and other emergencies. 33<br />

TRAFFIC SIGNAL PREEMPTION: On the positive side, traffic light preemption systems<br />

change the traffic lights as emergency vehicles approach, stopping civilian vehicles, and<br />

allowing emergency vehicles to enter intersections on a green light, thereby reducing the<br />

likelihood <strong>of</strong> a side-impact or head-on collision with another vehicle when having to go through<br />

red lights. These systems can be activated by siren or by infrared technology. When activated,<br />

the traffic light changes to a temporary green signal for the approaching emergency vehicle.<br />

Such a system is an excellent way to improve the safety <strong>of</strong> citizens and firefighters during<br />

emergency responses. In establishing operating procedures for such traffic devices, the<br />

department should restrict emergency vehicle operators from entering intersections on red lights<br />

because a delayed green light at an intersection with a preemption device can mean that another<br />

emergency vehicle is entering the intersection from the cross-road.<br />

AUTOMATIC VEHICLE LOCATION (AVL) AND MOBILE DATA COMPUTERS (MDCS):<br />

Implementation <strong>of</strong> an AVL system is beneficial because it allows dispatchers to see the actual<br />

location <strong>of</strong> any unit on a computer-generated map <strong>of</strong> the city. The AVL data could also be<br />

integrated into the CAD system to calculate the truly closest unit to any given emergency and<br />

make a dispatch recommendation accordingly, rather than making dispatches on the basis <strong>of</strong> the<br />

33 Deaths Expected From Delayed Emergency Response Due to Neighborhood Traffic Mitigation, 3 April 1997;<br />

submitted by Ronald Bowman to Boulder, CO <strong>City</strong> Council.<br />

TriData, a Division <strong>of</strong> 42<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

fixed station locations. In addition to improving dispatching, AVL improves personnel safety<br />

because a unit that is in trouble can be quickly located.<br />

Additionally, an AVL system can be integrated with MDCs installed in each emergency<br />

response unit. With the appropriate integration <strong>of</strong> AVL, navigational, and MDC technologies, the<br />

AVL can provide the MDC with a visual map showing the current unit location <strong>of</strong> the unit and<br />

the incident location along with the most efficient route <strong>of</strong> travel.<br />

MDCs can be used to provide CAD data, city maps, building plans, fire-rescue pre-plans,<br />

hospital status, patient information, navigational directions to responding units, etc. to units<br />

directly in the field. MDCs can also be used to log status and file incident reports. MDCs can be<br />

supported by 800 MHz radio system channels, code-division multiple access (CDMA) cellular<br />

technology (the same technology used to access the Internet on cell phones), and other wireless<br />

communications technologies.<br />

OCFD units are currently equipped with MDCs that are used to record the en route and<br />

on scene times. Units are not equipped with AVL. OCFD evaluated AVL in the past and<br />

determined it was not cost effective.<br />

Recommendation 4: Consider the use <strong>of</strong> AVL in front-line units. As units spend more<br />

time on EMS and other types <strong>of</strong> calls, they are more likely to be in the field when a second call<br />

comes in, which increases the utility <strong>of</strong> AVL. An analysis <strong>of</strong> overlap <strong>of</strong> calls would be useful.<br />

AVL can help reduce response times, and are a lot lower cost than adding a station. Automatic<br />

vehicle location should be evaluated to determine its impact on response times.<br />

Response Time Goals – Often the best place to start when defining response time goals<br />

is actual response times in the areas protected, un<strong>of</strong>ficial de facto goals already used by the<br />

department, and goals used by neighboring or comparable communities. Citizen satisfaction with<br />

the current level <strong>of</strong> service also can be factored in, though most citizens are not likely to know<br />

the quantitative results.<br />

Actual response times are discussed in the next chapter. The city has identified goals for<br />

call handling and dispatch in its Standard <strong>of</strong> Emergency Response Coverage, July 2004. Table 10<br />

summarizes the goals. Call processing and dispatch for OCFD is handled by the Bureau <strong>of</strong><br />

Emergency Communications (BOEC). PR&F and BOEC jointly agreed to these goals and<br />

incorporated them into an intergovernmental agreement.<br />

TriData, a Division <strong>of</strong> 43<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Table 10: OCFD Call Processing and Dispatch Time Goals<br />

Type <strong>of</strong> Call Goal Compliance<br />

Urgent <strong>Fire</strong> Calls 1:00 90%<br />

Priority 2 <strong>Fire</strong> Calls 1:30 90%<br />

Non-priority <strong>Fire</strong> Calls 2:00 90%<br />

High priority EMS Calls 1:30 90%<br />

Low priority EMS Calls 2:00 90%<br />

As the above discussion shows, setting overall response time goals is a complex and<br />

difficult task. Nevertheless, without these goals making decisions on how many resources are<br />

needed, where to put them, and when they are needed would be left up to individual whim and<br />

could easily lead to exorbitant, unnecessary expenses. It is therefore critically important to<br />

clarify the terminology and the trade<strong>of</strong>fs to be made.<br />

Based on the above and, in comparison to other like cities, we recommend the department<br />

adopt the response time goals shown in Table 11. These are close to best feasible practice in high<br />

performing departments.<br />

Call Type<br />

<strong>Fire</strong> (first due unit)<br />

EMS<br />

Call<br />

Priority<br />

Table 11: Recommended Response Time Goals<br />

Call<br />

Processing* Turnout Travel Total Compliance<br />

Urgent 1:00 6:00<br />

High 1:30 4:00 6:30<br />

Non-priority 2:00<br />

7:00<br />

1:00<br />

High 1:00 6:00<br />

4:00<br />

Low 1:30<br />

7:00<br />

<strong>Fire</strong> (Ladder) All 1:00<br />

* Under authority <strong>of</strong> the Bureau <strong>of</strong> Emergency Communications.<br />

6:00 8:00<br />

90%<br />

Recommendation 5: Adopt the response time goals listed above in Table 11. These are<br />

response time goals that would comply with NFPA standards, and put OCFD in the leading edge<br />

<strong>of</strong> practice.<br />

NUMBER OF STATIONS<br />

Once response time and other goals have been set, the process <strong>of</strong> determining how many<br />

stations are needed and where to place them can begin. The setting <strong>of</strong> realistic goals requires an<br />

iterative process. One considers what is being achieved (actual response times today) and what it<br />

would take to improve them. The goals might be loosened if the cost to achieve them is too high.<br />

Unfortunately, a major hole in the state <strong>of</strong> the art is the lack <strong>of</strong> knowledge <strong>of</strong> how much loss<br />

would be reduced if response times were improved by 30 seconds or a minute. We know faster is<br />

better to reduce losses, but not how much money or injury reduction is to be gained. So the<br />

TriData, a Division <strong>of</strong> 44<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

whole process depends on judgment in light to alternatives and their cost. This section looks at<br />

criteria for determining the number and location, size, and timing for stations.<br />

Number and <strong>Location</strong> <strong>of</strong> <strong>Station</strong>s – How many stations a department needs to protect<br />

an area depends in large part on the size <strong>of</strong> the built-up area to be protected. The degree <strong>of</strong><br />

sprinklerization (automatic sprinklers), automatic or mutual aid agreements, risks present, and<br />

type <strong>of</strong> developments to be protected all impact the placing <strong>of</strong> stations, but the sheer size <strong>of</strong> the<br />

area and speed limits on the street network are the prime factors, along with the desired response<br />

time goals. The latter are more a factor <strong>of</strong> standards and past experience than <strong>of</strong> risk, but risks to<br />

be protected influences placement <strong>of</strong> some stations.<br />

Response time goals will have the largest impact on the number <strong>of</strong> stations needed. To<br />

illustrate the point, if apparatus from a given station currently can get anywhere in an area within<br />

six minutes at 30 mph, and there were a perfect east-west, north-south street network, the area<br />

served by one station would be an 18-square-mile diamond-shaped area three miles in diameter<br />

from the center (station location) to any corner. If one wished to serve that same 18-square-mile<br />

area with a two-minute response, one would need nine stations instead <strong>of</strong> one because each<br />

station would be able to serve only two square miles.<br />

In addition to goals, the road network plays a sizeable role in the number <strong>of</strong> stations<br />

required. A perfect grid-patterned road network allows for the largest area to be reached in a<br />

given time, assuming uniform travel speeds on all road segments. Access to high-speed<br />

roadways (interstates, limited-access highways, etc.) increases the reachable area; winding,<br />

narrow, steep roads and traffic calming devices decrease the area reachable in a given time.<br />

ISO Compliance – ISO awards points for distribution <strong>of</strong> apparatus (and by proxy for<br />

distribution <strong>of</strong> stations). ISO reviews the distribution <strong>of</strong> engine and ladder companies and awards<br />

points based partially on the percent <strong>of</strong> developed area within 1.5 miles <strong>of</strong> an engine company<br />

and 2.5 miles <strong>of</strong> a ladder. Quints can be used to obtain points toward number <strong>of</strong> engines or<br />

rescue ladders needed. A quint can be counted as an engine and one-half <strong>of</strong> a ladder company, or<br />

as a full ladder company.<br />

Response Time Analysis – The analysis <strong>of</strong> actual response times compared to response<br />

time goals and geographic information system (GIS) modeling <strong>of</strong> response coverage provides the<br />

most dynamic and accurate assessment <strong>of</strong> the need for additional or fewer stations.<br />

To conduct a response time and GIS analysis, some basic information is needed,<br />

including:<br />

• <strong>Station</strong> locations and building ages<br />

• Apparatus deployment<br />

• Zoning and land use and related policies<br />

• National response time standards<br />

TriData, a Division <strong>of</strong> 45<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

• Current and projected population<br />

Actual incident data for the most recent year (and additional years if possible), including<br />

address, type <strong>of</strong> incident, units responding, and overall response time for each incident.<br />

GIS layers for the area, included road network, water, station locations, risks, etc.<br />

A response time analysis can help determine areas where an additional station may be<br />

needed. The GIS analysis confirms or refutes the need and allows decision-makers to see the<br />

impact <strong>of</strong> alternatives.<br />

While this type <strong>of</strong> analysis is more location specific than a standard formula such as ISO,<br />

it is only as accurate as the data available. That is, if the incident data is incomplete or<br />

inaccurate, it is difficult to assess how the department is doing compared to the adopted goals.<br />

This type <strong>of</strong> analysis is also less prescriptive than the ISO standard, and more subjective;<br />

however, it can be tailored to a specific department or even specific area served by a department.<br />

Therefore, even with the possible data issues, a response time and GIS analysis provides a more<br />

realistic assessment <strong>of</strong> the number and placement <strong>of</strong> fire stations.<br />

A response time and GIS analysis was completed for <strong>Oklahoma</strong> <strong>City</strong> and is discussed in<br />

Chapter V, <strong>Station</strong> and Apparatus Deployment.<br />

Determining <strong>Station</strong> Size – Once the decision to add, consolidate, or rebuild a station<br />

has been made and the site(s) selected, the process moves on to determining the size <strong>of</strong> each<br />

station—how many units and people should it be designed to house?<br />

While an architect will work with the department to determine the exact size and layout<br />

<strong>of</strong> a new station, there are some basic factors a department should consider from the beginning:<br />

• How many units will need to be housed at the station during its lifetime? (Apparatus<br />

bays typically make up the largest portion <strong>of</strong> a fire station.)<br />

• How many personnel will staff the units?<br />

• What facilities will they need (sleeping quarters, parking, fitness facilities, etc.)?<br />

• Will additional units and personnel need to be housed at the station in the foreseeable<br />

future?<br />

• How many <strong>of</strong>fices do we need?<br />

• Do we want a community space for the public?<br />

• How big are the available lots in the area the station will go?<br />

Although not done as part <strong>of</strong> this study, comparisons can be made with other departments<br />

and the size <strong>of</strong> their stations to get an idea <strong>of</strong> how much space will be needed.<br />

TriData, a Division <strong>of</strong> 46<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Determining Timing and a Capital Improvement Plan – This section describes<br />

methodology for creating a timeline for the relocation, closure, and construction <strong>of</strong> fire stations.<br />

It also presents criteria and models for making decisions about the timing <strong>of</strong> capital<br />

improvements.<br />

METHODOLOGY FOR PRIORITIZING FIRE STATION CAPITAL IMPROVEMENTS: There<br />

are several questions that need to be answered before deciding on the priority <strong>of</strong> a new station, or<br />

one which is considered for upgrade.<br />

Current Service Levels – How large is the current service deficiency? How fast are calls<br />

being handled in that area? How many calls would a new station in that area handle? To what<br />

extent would the addition <strong>of</strong> a station in that area correct the deficiency?<br />

Future Service Levels – If there is no current deficiency, when will there be a service<br />

deficiency in the area in the future? Is the deficiency a function <strong>of</strong> response times, workload, or<br />

both?<br />

Cost <strong>of</strong> Alternative Solutions – What alternatives to building a station exist in the<br />

area, e.g., expanding/renovating the current station, redeployment <strong>of</strong> current resources,<br />

contracting out, or co-location <strong>of</strong> a fire/EMS resource with the other service or adding a new unit<br />

to an existing station (which is recommended, as will be seen)? What are the costs and benefits<br />

<strong>of</strong> each option?<br />

The flowchart in Figure 8 details the methodology described above.<br />

When prioritizing repairs or renovations, an initial screening should be done to determine<br />

the long-term viability <strong>of</strong> the facility. It is important to know whether the facility will be useful<br />

from a system-wide operational standpoint beyond its expected useful lifecycle. If a facility will<br />

be unnecessary from a service delivery viewpoint before it would need replacement or major<br />

renovation, then it is not worth doing much repair work to it. That is, if the station will need only<br />

minor repairs for the next 5 years but major renovation in 6 years but the station will not be<br />

needed after 3 years because a new one will be opening up down the road, then it does not make<br />

sense to make major repairs or renovations to the building.<br />

TriData, a Division <strong>of</strong> 47<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Figure 8: Capital Improvements Prioritization Methodology<br />

No Priority<br />

START<br />

None foreseeable<br />

When will<br />

there be a service<br />

deficiency?<br />

None now<br />

How large is<br />

the current service<br />

deficiency?<br />

Small<br />

Low Priority<br />

Within<br />

7 years<br />

Medium Priority<br />

Medium/Large<br />

Within 15 years<br />

Low Priority<br />

How fast are<br />

calls being handled<br />

in that area?<br />

With service<br />

target levels<br />

Below service level targets<br />

Not much<br />

Yes<br />

To what<br />

extent would a new<br />

station correct the<br />

problem?<br />

A Lot/Some<br />

Are there<br />

alternatives<br />

to building a<br />

station?<br />

1000+<br />

per year<br />

How many calls<br />

would a new<br />

station handle?<br />

Below 500<br />

per year<br />

Medium Priority<br />

No<br />

500-1000 per year<br />

High Priority<br />

No<br />

Are there<br />

alternatives to<br />

building a<br />

station?<br />

Yes<br />

The next consideration is how long it will take to provide a suitable replacement if one is<br />

needed. If a station needs to be relocated, how long will it be before the replacement station is<br />

ready for occupancy? It may be appropriate to only make temporary or relatively minor repairs<br />

until the move to the new station is completed. If the delay in opening a new station is going to<br />

be lengthy, more <strong>of</strong> the necessary repairs should be made in the interim.<br />

TriData, a Division <strong>of</strong> 48<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Feasibility <strong>of</strong> Consolidating/Closing <strong>Station</strong>s – A methodology similar to<br />

prioritizing the need for a new station can be applied to determining the feasibility <strong>of</strong><br />

consolidating or closing existing stations (Figure 9).<br />

A few notes on terminology in this methodology: to close a station is to discontinue using<br />

the station as a base for operations <strong>of</strong> fire or EMS apparatus and take the units at that station out<br />

<strong>of</strong> service. Closed stations result in empty buildings that can be converted to other uses, if<br />

desired, rather than destroyed. Units taken out <strong>of</strong> service can be used as reserve apparatus, or to<br />

replace older apparatus elsewhere in the area.<br />

To consolidate a station is to discontinue using one or more buildings but to continue<br />

operating all units from the stations being consolidated. A consolidation may result in a new<br />

building if both stations being consolidated are in need <strong>of</strong> major repairs, if neither building is<br />

large enough to hold the necessary apparatus, or if a new single location would provide better<br />

response coverage than either existing location.<br />

TriData, a Division <strong>of</strong> 49<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Figure 9: Consolidation/Closure Feasibility Methodology<br />

START<br />

How much<br />

overlap exists in<br />

current<br />

station/unit<br />

coverage<br />

(based on<br />

response time<br />

goals)?<br />


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

NUMBER OF APPARATUS<br />

Number and <strong>Location</strong> <strong>of</strong> Apparatus – Unless a department considers alternative<br />

deployment methods such as system status management—used primarily in EMS—apparatus<br />

locations will be determined in conjunction with stations. The number and type <strong>of</strong> units, on the<br />

other hand, is determined by demand and response goals.<br />

BASED ON RISKS: The deployment <strong>of</strong> apparatus is related to the locations <strong>of</strong> fire stations<br />

in the community. The number <strong>of</strong> and types <strong>of</strong> apparatus that are required is based on that risk is<br />

tied to the staffing <strong>of</strong> those units. Apparatus and personnel response complements based on risk<br />

level are discussed below in the section on staffing.<br />

NATIONAL STANDARDS: Aside from the response complement based on risk levels, the<br />

NFPA does not make recommendations on the number <strong>of</strong> front-line apparatus a department<br />

should have. The NFPA does, however, make recommendations on the number <strong>of</strong> reserve<br />

apparatus.<br />

The NFPA also <strong>of</strong>fers a suggested ratio <strong>of</strong> eight to one in terms <strong>of</strong> front-line to reserve<br />

engine and ladder apparatus. ISO recommends a ratio <strong>of</strong> reserve to front-line apparatus <strong>of</strong> either<br />

1:4 or 1:3, depending on the type <strong>of</strong> apparatus and the frequency with which it is used.<br />

WORKLOADS: Determining how busy units are is important for establishing their<br />

availability for the next call and because it provides insight on how much capacity various units<br />

have to handle more work, or whether additional units are needed. One needs to consider both<br />

the number <strong>of</strong> calls (demand) and the time spent on calls (workload) (number <strong>of</strong> calls x average<br />

time per call)—the unit’s workload. (Workload here is emergency workload only, not all the<br />

training and other tasks undertaken at the station, nor the documentation for emergency<br />

responses.)<br />

Through CAD systems, fire departments are able to keep detailed records about service<br />

times; these data are useful in determining the availability <strong>of</strong> a specific unit or station. Again, the<br />

concept <strong>of</strong> workload is not merely a count <strong>of</strong> how many calls to which a unit was dispatched.<br />

One unit can have fewer responses than another but remains on the scene longer on average (e.g.<br />

more working incidents), and so has a greater workload. Evaluating workload is important when<br />

looking at the overlaps in coverage to an area that may be required to achieve the response time<br />

goals adopted by the city/department and is part <strong>of</strong> the CFAI self-assessment process. An<br />

analysis <strong>of</strong> workload also can indicate whether a new station should be built or new apparatus<br />

purchased—or if current stations should be closed or units moved.<br />

A fire/EMS system must incorporate the necessary redundancies based on whether<br />

adjacent stations or units are likely to be available for emergency response. Below are guidelines<br />

developed by TriData that outline the redundancy levels needed to meet response time goals<br />

TriData, a Division <strong>of</strong> 51<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

according to response levels and are based on our experience with workloads and how they<br />

affect availability.<br />

1. Very Low (4,000 responses/yr) – Overlapping calls may occur hourly,<br />

regardless <strong>of</strong> the time <strong>of</strong> day. The closest station/unit is likely to be unavailable thus<br />

requiring the response <strong>of</strong> adjacent stations/units. Frequent transfers or move-ups are<br />

required for the delivery system to meet demand. <strong>Station</strong>s/units must be located with<br />

redundancy (back-up units) to achieve stated travel time objectives established by the<br />

community. This footprint is usually found in very densely populated urban areas and<br />

is especially evident in EMS services located in urban areas with very high demand<br />

for service. (Overlap can be achieved with additional stations or additional units in<br />

existing stations.)<br />

The 3,000–3,200 response level (very high category above) is the point at which units are<br />

<strong>of</strong>ten considered “busy” and their availability needs to be evaluated. This is a rough rule <strong>of</strong><br />

thumb, not a fixed standard. At this point, response times <strong>of</strong>ten will begin getting longer from<br />

TriData, a Division <strong>of</strong> 52<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

frequent call overlap (calls to the same first-due area arriving back-to-back). 34 As units become<br />

busier, the chances for overlap or simultaneous alarms increase, and second-due units begin to<br />

answer more calls. This causes a domino effect where unit B is dispatched to a call in unit A’s<br />

area because unit A is already engaged, causing unit B to be unavailable for the next call in its<br />

own area. Unit C must then respond to unit B or unit A’s area, and so forth.<br />

Again, the 3,000-response threshold is just a rule <strong>of</strong> thumb. How much time a unit is<br />

unavailable due to being involved with another incident is better assessment <strong>of</strong> the impact <strong>of</strong><br />

workloads on availability and response times. This is the second factor in workload, known as<br />

unit hour utilization (UHU).<br />

UNIT HOUR UTILIZATION: UHU is a calculation that estimates the amount <strong>of</strong> time a unit<br />

is occupied on emergency calls as a percentage <strong>of</strong> the total amount <strong>of</strong> hours a unit is staffed and<br />

available for response (a unit staffed full-time is available 8,760 hours per year). In other words,<br />

UHU measures the percentage <strong>of</strong> on-duty time consumed by emergency service field activities.<br />

A high UHU means lower availability for calls. Poor availability negatively impacts response<br />

times.<br />

The specific formula used to calculate the UHU for each unit is:<br />

UHU=<br />

(number <strong>of</strong> calls) x (average call duration in hours)<br />

8,760 hours per year<br />

UHU measures the percent <strong>of</strong> a unit’s time in service that is spent running calls. There is<br />

other time that is not accounted for, however, which includes time for training, maintenance, and<br />

other preparedness-related functions. Public education efforts also are not included in the UHU<br />

calculation. In other words, when units are not engaged in emergency response, it does not mean<br />

they are not working.<br />

UHU is used more in relation to EMS units than fire suppression units; although,<br />

evaluation <strong>of</strong> UHUs is useful to different extents in both cases.<br />

While there is consensus within the industry on the importance <strong>of</strong> utilization rates and<br />

how to measure them, the interpretation <strong>of</strong> how indicative utilization rates are <strong>of</strong> overall system<br />

efficiency is debatable. Most believe that a UHU between 35 and 45 percent for EMS is good for<br />

economic efficiency. (This is more common with private ambulance providers.) If a UHU is<br />

greater than 45 percent, units <strong>of</strong>ten are not available and response times suffer. If a UHU is<br />

below 35 percent, units may not be well utilized, but response times may be high too <strong>of</strong>ten.<br />

34 A “first-due” ‘area is a certain geographic area <strong>of</strong> the overall fire department response jurisdiction that is assigned<br />

to a particular fire station and the units that are assigned to them. Generally, it is best to dispatch the closest unit or<br />

company to any particular type <strong>of</strong> incident. Companies may be assigned to incidents outside <strong>of</strong> their first-due area,<br />

such as a second-due area, as the need arises because <strong>of</strong> the normal first-due unit being out-<strong>of</strong>-service or other<br />

circumstances.<br />

TriData, a Division <strong>of</strong> 53<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Many communities choose to aim for a UHU in the 15–25 percent range to improve or maintain<br />

good response times. If a unit has a UHU <strong>of</strong> 40 percent, it will not be available for the next call<br />

40 percent <strong>of</strong> the time. This is, <strong>of</strong> course, an average over the course <strong>of</strong> the day.<br />

There are no guidelines on UHU levels for fire units; however, many larger departments<br />

recently evaluated by TriData experience engine and truck UHUs between 5 and 15 percent. If a<br />

unit is out <strong>of</strong> its station on a call more than 10 percent <strong>of</strong> the time, then it is unlikely to meet<br />

response time goals <strong>of</strong> 90 percent <strong>of</strong> calls in 4-minute travel times, since a second further away<br />

station will have to respond. Thus UHU <strong>of</strong> 5.15 percent is consistent with a goal <strong>of</strong> being there<br />

about 90 percent <strong>of</strong> the time.<br />

In order to develop an effective resource deployment plan, units must be available to<br />

respond to incidents most <strong>of</strong> the time. No amount <strong>of</strong> resource placement planning will improve<br />

system wide response times if the responding units are not available.<br />

REPLACEMENT SCORING SYSTEM: Some fire departments (primarily on the East Coast)<br />

use a scoring system developed by the American Public Works Association Fleet Service<br />

Committee for assessing fire apparatus for replacement, or a scoring system similar to it. 35<br />

Examples <strong>of</strong> its use may be found in many Virginia jurisdictions e.g. (Chesapeake, Hampton,<br />

Newport News, Virginia Beach, and York County). The scoring system considers the variables<br />

<strong>of</strong> age, mileage, maintenance costs, and operating conditions. A replacement score is calculated<br />

for each vehicle based on the sum <strong>of</strong> its scores for age, usage, and condition. Data for the<br />

calculations usually are obtained from computerized vehicle maintenance records and work<br />

orders.<br />

Assigning one point for each month beyond the date on which it was purchased scores<br />

the age <strong>of</strong> the vehicle. The usage score assigns one point for each 1,000 miles traveled or 3.5<br />

points for each 100 hours <strong>of</strong> use, whichever is higher. The condition <strong>of</strong> the vehicle is scored on a<br />

scale <strong>of</strong> zero, two, or four for each aspect, in accordance with criteria for each <strong>of</strong> the categories,<br />

including the body, interior, installed functional apparatus, maintenance/repair cost, and mission.<br />

The sum <strong>of</strong> the scores for each category is then multiplied by a factor <strong>of</strong> 12 to obtain the overall<br />

vehicle score. If the overall score exceeds the point limit established for the respective vehicle<br />

category, the vehicle is recommended for replacement or disposal. The categories and associated<br />

maximum scores are listed in Table 12. Other factors such as vehicle downtime can be included<br />

in such a system.<br />

The critical component in any service-life-assessment system is the absolute requirement<br />

that a vehicle must be able to safely and reliably perform in a manner consistent with the<br />

vehicle’s designated purpose, regardless <strong>of</strong> mileage or hours <strong>of</strong> use.<br />

35 American Public Works Association (2003). Fleet Service Committee. http://www.apwa.net<br />

TriData, a Division <strong>of</strong> 54<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Table 12: Maximum Vehicle Points Before<br />

Disposal/Replacement is Recommended (APWA System)<br />

Vehicle Category<br />

Maximum Vehicle<br />

Points<br />

Sedans, station wagons, and jeeps 162<br />

Heavy duty trucks and towed equipment 192<br />

Special purpose equipment such as boats and trailers 192<br />

Light-duty trucks 196<br />

Medium- to heavy-duty trucks (including ambulances) 220<br />

<strong>Fire</strong> apparatus 225<br />

Specifications – Finally, once the number and type <strong>of</strong> apparatus and replacement<br />

programs are determined, the department must develop specifications for each piece <strong>of</strong><br />

apparatus.<br />

APPLICABLE STANDARDS FOR FIRE APPARATUS: There are several federal regulations,<br />

fire service consensus standards, and fire insurance standards that have influenced the design <strong>of</strong><br />

modern fire apparatus. The federal standards include requirements mandated by the National<br />

Traffic and Motor Vehicle Safety Act and the Clean Air Act. The fire service consensus<br />

standards consist <strong>of</strong> NFPA Standards 1201, 1500, and 1901. The fire insurance standard is that<br />

developed by the ISO, while the CFAI also has references to fire apparatus design and<br />

procurement in their assessment manual.<br />

NATIONAL TRAFFIC AND MOTOR VEHICLE SAFETY ACT OF 1966: This Act mandated<br />

that all manufacturers adhere to specific safety standards when designing and constructing motor<br />

vehicles. The Clean Air Act has emission control standards that affect engine performance,<br />

which led to incorporation <strong>of</strong> electronic controls on diesel engines.<br />

NATIONAL FIRE PROTECTION ASSOCIATION STANDARD 1201, DEVELOPING FIRE<br />

PROTECTION SERVICES FOR THE PUBLIC (1994): This standard includes sections on<br />

procurement and maintenance <strong>of</strong> fire apparatus. They require (a) inventory control <strong>of</strong> all fire<br />

apparatus and equipment owned and operated by a fire department; (b) implementation <strong>of</strong><br />

forecasting methods to project apparatus service-life expectancies and replacement needs; (c)<br />

development <strong>of</strong> written fire apparatus bid specifications in accordance with NFPA standards; (d)<br />

implementation <strong>of</strong> routine inspection and preventive maintenance programs; and (e)<br />

implementation <strong>of</strong> service testing for fire pumpers and aerial devices.<br />

NATIONAL FIRE PROTECTION ASSOCIATION STANDARD 1500, FIRE DEPARTMENT<br />

OCCUPATIONAL SAFETY AND HEALTH PROGRAM (1992): Chapter 4, Vehicles and Equipment,<br />

addresses (a) fire apparatus design requirements; (b) training and certification <strong>of</strong> fire apparatus<br />

operators: (c) safe driving and operating practices for fire apparatus; (d) safety practices for<br />

TriData, a Division <strong>of</strong> 55<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

firefighters riding fire apparatus; and (e) regular inspection and preventive maintenance and<br />

repair <strong>of</strong> fire apparatus.<br />

NATIONAL FIRE PROTECTION ASSOCIATION STANDARD 1901, AUTOMOTIVE FIRE<br />

APPARATUS (1996): This standard outlines design requirements for (a) pumper fire apparatus;<br />

(b) initial attack fire apparatus; (c) mobile water supply fire apparatus; (d) aerial fire apparatus;<br />

(e) special service fire apparatus; (f) chassis and vehicle components; (g) low voltage electrical<br />

systems and warning devices; (h) driving and crew areas; (i) body, compartments, and equipment<br />

mounting; (j) fire pump and associated equipment; (k) water transfer pump and associated<br />

equipment; (l) water tanks; (m) aerial devices; (n) foam proportioning systems; (o) compressed<br />

air foam systems; (p) line voltage electrical system; (q) command and communications; (r) air<br />

systems; and (s) winches.<br />

INSURANCE SERVICES OFFICE: Requirements for fire apparatus are addressed in the ISO<br />

fire department resources criterion. Based on the results <strong>of</strong> Basic <strong>Fire</strong> Flow calculations, one<br />

computes the minimum number <strong>of</strong> engine companies and pump capacities needed to meet<br />

estimated fire suppression requirements. Depending on the total number <strong>of</strong> buildings that are at<br />

least 3 stories or 35 feet in height, the need for ladder or service companies is also determined.<br />

CENTER FOR PUBLIC SAFETY EXCELLENCE/COMMISSION ON FIRE ACCREDITATION<br />

INTERNATIONAL (CFAI): Assessment Manual, Chapter VI, Physical Resources, Criterion 6B,<br />

apparatus and resources says that “Rating for this criterion is based on the performance<br />

indicators <strong>of</strong> (a) apparatus location in accordance with established standards <strong>of</strong> coverage for the<br />

community; (b) appropriateness <strong>of</strong> apparatus types for services provided; (c) existence <strong>of</strong> an<br />

apparatus replacement schedule; and (d) existence <strong>of</strong> a program for writing apparatus<br />

replacement specifications so that fire apparatus are designed and purchased to be adequate to<br />

meet the agency’s goal and objectives.”<br />

PERFORMANCE SPECIFICATIONS: Performance specification is the process <strong>of</strong> stating the<br />

requirements for apparatus procurement in terms <strong>of</strong> what the vehicles do rather than the way to<br />

get there. Most, if not all, apparatus manufacturers today indicate that if the purchaser specifies<br />

performance requirements rather than requirements for specific components, the manufacturer<br />

can engineer the apparatus to conform. For example, if the department were to specify a 1,250<br />

gpm. pumper and its road performance requirements, the manufacturer would figure out the<br />

appropriate engine, transmission, and the driveline combination to accomplish the goal. The<br />

manufacturer would ensure that the horsepower and torque provided would be sufficient to meet<br />

the needs <strong>of</strong> the apparatus. This in turn would save the department money and time by<br />

eliminating unnecessary over-sizing <strong>of</strong> the engine and related equipment for the apparatus.<br />

In using performance-based specifications, consideration must be given to how the<br />

configuration will perform as it ages, after routine wear <strong>of</strong> the apparatus. In other words, one<br />

needs to state how long the vehicle is expected to last and still provide the desired performance.<br />

TriData, a Division <strong>of</strong> 56<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Perhaps the most desirable specification combines a performance specifications format<br />

with a general design format (e.g., four doors, bench seat). Including minimum performance<br />

standards in the specification for various components and systems is a good way to ensure proper<br />

36 37 38<br />

performance.<br />

Complement Based on Risk – The number <strong>of</strong> firefighters needed per engine or truck<br />

(ladder) company is a subject <strong>of</strong> hot debate in the fire world. The NFPA has much influence in<br />

this area as well. The fundamental issues in determining unit staffing include:<br />

• The ability to start operations with the first arriving unit;<br />

• The ability to rapidly amass critical staffing for incidents <strong>of</strong> various sizes and types <strong>of</strong><br />

hazards;<br />

• <strong>Fire</strong>fighter safety, and;<br />

• Productivity <strong>of</strong> a unit and the system <strong>of</strong> units.<br />

<strong>Oklahoma</strong> <strong>City</strong> considers minimum staffing for its fire apparatus to be three personnel,<br />

except for paramedic engines that have four personnel. This minimum staffing level is below the<br />

level specified in NFPA standards (except <strong>of</strong> paramedic engines.) NFPA Standard 1500, <strong>Fire</strong><br />

Department Occupational Safety and Health Program says that “…a minimum acceptable fire<br />

company staffing level should be four members responding or arriving with each engine and<br />

each ladder company responding to any type <strong>of</strong> fire.” NFPA 1710 also suggests that fire<br />

suppression units be staffed with a minimum <strong>of</strong> four personnel. Many cities still operate<br />

successfully with 3 person staffing, (e.g. Arlington, Texas) provided that enough personnel<br />

quickly arrive on scene.<br />

While the staffing <strong>of</strong> the unit affects its efficiency, a more important criterion is how fast<br />

the total team can be assembled for a given incident regardless <strong>of</strong> the number <strong>of</strong> vehicles on<br />

which they ride. The National <strong>Fire</strong> Protection Handbook, 18 th Edition, Typical Initial Attack<br />

Response Capability Assuming Interior Attack and Operations Response Capability (Table 10-<br />

2A), makes staffing recommendations based on the number <strong>of</strong> firefighters arriving on the scene<br />

<strong>of</strong> a fire depending upon the type <strong>of</strong> occupancy (low-, medium-, and high-hazard occupancy).<br />

The NFPA staffing recommendations by the type <strong>of</strong> hazard areas follows:<br />

• HIGH-HAZARD OCCUPANCIES (schools, hospitals, nursing homes, explosive plants,<br />

refineries, high-rise buildings, and other high-risk or large fire potential occupancies):<br />

At least four pumpers, two ladder trucks (or combination apparatus with equivalent<br />

36 Senter, Edward L. (1998, July). Evaluating <strong>Fire</strong> Apparatus Design Changes in the Norfolk Department <strong>of</strong> <strong>Fire</strong><br />

and Paramedical Services. Emmitsburg, MD: National <strong>Fire</strong> Academy, Executive <strong>Fire</strong> Officer Program.<br />

37 Norfolk <strong>Fire</strong> and Paramedical Services. (1993). Vehicle study. Norfolk, VA.<br />

38 Capital Safety Systems. (1991). Calvert County, Maryland Emergency Apparatus Assessment & Analysis, Calvert<br />

County, MD<br />

TriData, a Division <strong>of</strong> 57<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

capabilities), two chief <strong>of</strong>ficers, and other specialized apparatus as may be needed to<br />

cope with the combustible involved; not fewer than 24 firefighters and two chief<br />

<strong>of</strong>ficers.<br />

• MEDIUM-HAZARD OCCUPANCIES (apartments, <strong>of</strong>fices, mercantile and industrial<br />

occupancies not normally requiring extensive rescue or firefighting forces): At least<br />

three pumpers, one ladder truck (or combination apparatus with equivalent<br />

capabilities), one chief <strong>of</strong>ficer, and other specialized apparatus as may be needed or<br />

available; not fewer than 16 firefighters and one chief <strong>of</strong>ficer.<br />

• LOW-HAZARD OCCUPANCIES (one-, two-, or three-family dwellings and scattered<br />

small businesses and industrial occupancies): At least two pumpers, one ladder truck<br />

(or combination apparatus with equivalent capabilities), one chief <strong>of</strong>ficer, and other<br />

specialized apparatus as may be needed or available; not fewer than 12 firefighters<br />

and one chief <strong>of</strong>ficer.<br />

The recommendations and guidelines outlined in the NFPA Handbook should be<br />

considered, but are not necessarily the final word as the NFPA guidelines do not address how<br />

fire departments will also be able to comply with the OSHA mandated “Two-in/Two-out” rule<br />

(discussed below). Also, the NFPA guidelines do not address OSHA’s requirement that a rapid<br />

intervention team/crew (RIT/RIC) be on-scene at a working fire.<br />

Table 13 shows the OCFD’s response complement to a structure fire based on risk versus<br />

the NFPA guidelines outlined above.<br />

Table 13: Current <strong>Oklahoma</strong> <strong>City</strong> Structure <strong>Fire</strong> Response Complement vs. NFPA Guidelines<br />

Type <strong>of</strong> Occupancy OCFD Response Complement NFPA Guidelines<br />

High-Hazard<br />

(High-rises in <strong>Oklahoma</strong><br />

<strong>City</strong>)<br />

Total<br />

Medium-Hazard<br />

Total<br />

4 Engines<br />

2 Ladder Trucks (Rescue<br />

Ladder)<br />

2 District chiefs + Support Units<br />

24 <strong>Fire</strong>fighters<br />

2 Chief Officers<br />

4 Engines<br />

2 Ladder Trucks<br />

24 <strong>Fire</strong>fighters<br />

2 Chief Officers<br />

2625 26<br />

4 Engines<br />

2 Ladder Trucks (Rescue<br />

Ladder)<br />

2 District chiefs + Support Units<br />

24 <strong>Fire</strong>fighters<br />

2 Chief Officers<br />

3 Engines<br />

1 Ladder Truck<br />

16 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

26 17<br />

TriData, a Division <strong>of</strong> 58<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Type <strong>of</strong> Occupancy OCFD Response Complement NFPA Guidelines<br />

Low-Hazard<br />

Total<br />

3 Engines<br />

1 Ladder Truck (Rescue ladder)<br />

2 Chiefs<br />

18 <strong>Fire</strong>fighters<br />

2 District chiefs+ Support Units<br />

2 Engines<br />

1 Ladder Truck<br />

12 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

20 13<br />

Due to variables in engine company staffing i.e., the OCFD paramedic engine companies<br />

are staffed with four personnel instead <strong>of</strong> three, the staffing figures for OCFD may differ slightly<br />

for a given response. These figures represent an average if half <strong>of</strong> the engines are staffed with<br />

three and the other half with four fire fighters. As <strong>Oklahoma</strong> <strong>City</strong> has a sizeable rural (nonhydrant)<br />

area, these responses are supplemented with tanker and brush trucks as needed.<br />

CONCLUSION: <strong>Oklahoma</strong> <strong>City</strong> meets or exceeds NFPA guidelines for all three types <strong>of</strong><br />

occupancy listings. In the Medium and Low Hazard Occupancy, OCFD sends almost 50% more<br />

equipment and personnel than the NFPA recommends.<br />

Recommendation 6: Consider reducing the weight <strong>of</strong> response (number <strong>of</strong> and types <strong>of</strong><br />

units) that respond to medium and low hazard alarms.<br />

Table 14 illustrates the proposed weight <strong>of</strong> response for the department. The response<br />

complement for high-hazards is appropriate and would not change. The addition <strong>of</strong> tankers or<br />

brush vehicles would likewise not change.<br />

Table 14: Proposed <strong>Oklahoma</strong> <strong>City</strong> Structure <strong>Fire</strong> Response Complement vs. NFPA Guidelines<br />

Type <strong>of</strong> Occupancy OCFD Response Complement NFPA Guidelines<br />

High-Hazard<br />

(High-rises in <strong>Oklahoma</strong><br />

<strong>City</strong>)<br />

Total<br />

Medium-Hazard<br />

Total<br />

4 Engines<br />

2 Ladder Trucks (Rescue<br />

Ladder)<br />

2 District chiefs + Support units<br />

24 <strong>Fire</strong>fighters<br />

2 Chief Officers<br />

4 Engines<br />

2 Ladder Trucks<br />

24 <strong>Fire</strong>fighters<br />

2 Chief Officers<br />

2625 26<br />

3 Engines<br />

1 Ladder Truck (Rescue ladder)<br />

1 Chief Officer +Support units<br />

16 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

3 Engines<br />

1 Ladder Truck<br />

16 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

17 17<br />

TriData, a Division <strong>of</strong> 59<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Type <strong>of</strong> Occupancy OCFD Response Complement NFPA Guidelines<br />

Low-Hazard<br />

Total<br />

3 Engines<br />

1 Ladder Truck (Rescue ladder)<br />

1 Chief Officer + Support Units<br />

16 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

2 Engines<br />

1 Ladder Truck<br />

12 <strong>Fire</strong>fighters<br />

1 Chief Officer<br />

17 13<br />

There are several advantages to reducing the weight <strong>of</strong> responses.<br />

• Reduced workloads for busy units.<br />

• Reduced fuel costs and vehicle maintenance costs.<br />

• Reduced response times in high activity periods. By reducing the numbers <strong>of</strong><br />

apparatus on certain types <strong>of</strong> calls, more companies will remain available for service.<br />

This will reduce response times.<br />

• Improved safety. By reducing the weight <strong>of</strong> response the potential for motor vehicle<br />

accidents involving fire apparatus will be reduced.<br />

• Increased time for non-emergency activities such as <strong>Fire</strong> Prevention and Public<br />

Education.<br />

These reductions in the weight <strong>of</strong> response would still keep <strong>Oklahoma</strong> <strong>City</strong> at or above<br />

the NFPA recommendations.<br />

Standards and Laws – Additional standards for staffing are related to OSHA’s<br />

regulations for firefighter safety.<br />

OSHA: <strong>Fire</strong>fighting is a dangerous and physical labor-intensive occupation. Although<br />

technologically the tools and equipment used by firefighters have changed dramatically over the<br />

years, the basic goals have remained almost unchanged: to preserve life and protect property by<br />

successfully extinguishing fires—and not get hurt in the process. To accomplish this, firefighters<br />

must be able to quickly and efficiently gain access to a fire and apply an extinguishing agent<br />

(typically water, but increasingly foam and other agents are gaining popularity). This requires<br />

emergency responders to operate in dangerous environments where they are at high risk for<br />

serious injury or death.<br />

To protect the heath, safety, and welfare <strong>of</strong> firefighters, the federal government enacted<br />

regulations to ensure that firefighters operate in and around structure fires safely. Enacted by the<br />

Department <strong>of</strong> Labor and the Occupational Safety and Health Administration (OSHA), 29 CFR<br />

1910.134, also known as “Two-in/Two-out,” mandates that there must be a minimum <strong>of</strong> four<br />

personnel on the scene <strong>of</strong> a structural fire before personnel can initiate interior operations. Two<br />

firefighters must remain on the exterior <strong>of</strong> the structure, properly equipped with full turnout gear<br />

and self-contained breathing apparatus (SCBA) to act as a RIC in the event the firefighters<br />

TriData, a Division <strong>of</strong> 60<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

operating inside the structure become incapacitated or trapped. Although OSHA allows one RIC<br />

member to have an additional role such as incident commander or safety <strong>of</strong>ficer, as long as<br />

rescue activities can be performed without jeopardizing the safety <strong>of</strong> other firefighters, a pump<br />

operator cannot make up part <strong>of</strong> the RIC unless the apparatus is in a positive water source, which<br />

allows the pump to be unstaffed for a period.<br />

INTER-JURISDICTIONAL COMPARISONS<br />

In order to put a department’s performance in perspective, it is helpful to compare the<br />

department with other departments that share similar characteristics. In so doing, a department<br />

can find benchmarks by which to measure its own performance. When these comparisons differ<br />

drastically, further evaluation is required.<br />

Jurisdictional comparisons are not easy to interpret as there are many variables. No two<br />

jurisdictions are exactly the same size, with the exact same population, and with identical<br />

governmental organization or services. However, many jurisdictions do share similar qualities.<br />

While these comparisons cannot be as considered directly indicative <strong>of</strong> the department’s<br />

performance, they are <strong>of</strong> value. They allow helpful in assessing a department in relation to the<br />

performance <strong>of</strong> its peers, identifying departmental strengths, and suggesting areas for<br />

improvement.<br />

<strong>Oklahoma</strong> <strong>City</strong> is a difficult city to make comparisons with because <strong>of</strong> its size; the city<br />

has the third largest land area <strong>of</strong> any city. There are many cities with similar populations, but<br />

few that share comparable land areas and populations. Fourteen cities have been identified for<br />

comparison, including Jacksonville, FL. Jacksonville is the city whose land area is most<br />

comparable to <strong>Oklahoma</strong> <strong>City</strong>. A variety <strong>of</strong> cities <strong>of</strong>fer a basis for comparison by population. In<br />

the comparison below, averages exclude <strong>Oklahoma</strong> <strong>City</strong>.<br />

Community Comparison – Table 15 shows the population and land areas <strong>of</strong> each city<br />

used in this comparison. The populations do not take into account visitors or day-time working<br />

populations, but instead cover only in-city residents. <strong>Oklahoma</strong> <strong>City</strong>, as well as many <strong>of</strong> the<br />

other cities in the comparison, has a large metropolitan area. Jacksonville, Indianapolis and<br />

<strong>Oklahoma</strong> <strong>City</strong> are the three largest cities by land area used in this comparison. <strong>Oklahoma</strong> <strong>City</strong><br />

has the lowest population density and the largest first-due station area <strong>of</strong> the comparison group.<br />

The city maintains a population-protected per station that is below average when compared with<br />

similar cities, because <strong>of</strong> the large area.<br />

TriData, a Division <strong>of</strong> 61<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

<strong>City</strong><br />

Table 15: Comparison <strong>of</strong> Populations Served per <strong>Station</strong><br />

Population<br />

(2003 Census<br />

Estimate)<br />

Land Area<br />

(Square Miles<br />

Protected)<br />

Square Miles/<br />

<strong>Station</strong><br />

Population<br />

Served/<br />

<strong>Station</strong><br />

Population/<br />

Square Mile<br />

Indianapolis, IN 783,438 361.0 13.9 30,132 2,170<br />

Tucson, AZ 507,658 195.0 9.8 25,383 2,603<br />

Albuquerque, NM 471,586 181.0 8.2 21,436 2,605<br />

El Paso, TX 584,113 250.5 8.1 18,842 2,332<br />

Denver, CO 557,478 153.0 4.9 17,983 3,644<br />

Omaha, NE 404,267 116.0 5.0 17,577 3,485<br />

Milwaukee, WI 586,941 96.0 2.7 16,304 6,114<br />

Austin, TX 672,011 252.0 5.9 15,628 2,667<br />

Fort Worth, TX 585,122 293.0 7.5 15,003 1,997<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 523,303 607.0 17.3 14,952 862<br />

Jacksonville, FL 773,781 758.0 13.5 13,818 1,021<br />

Tulsa, OK 387,807 183.0 6.3 13,373 2,119<br />

Kansas <strong>City</strong>, MO 442,768 314.0 9.2 13,023 1,410<br />

Memphis, TN 645,978 279.0 5.1 11,745 2,315<br />

Average 569,458 264.0 7.7 17,711 2,652<br />

Apparatus Comparison – In terms <strong>of</strong> type and distribution <strong>of</strong> apparatus, the department<br />

compares well. The city was an engine to truck ratio <strong>of</strong> 2.8, which is significantly lower than the<br />

average. The city also has a higher engine to 10,000 citizen ratio, at 0.69, the fourth highest ratio<br />

<strong>of</strong> cities included in this comparison. This ratio is slightly above the 0.62 average as shown in .<br />

Table 1.<br />

TriData, a Division <strong>of</strong> 62<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Table 16: Comparison <strong>of</strong> Engine Companies per 10,000 Population<br />

<strong>City</strong> Engines Trucks Quints<br />

Engines/<br />

10,000 pop E: T Ratio<br />

Memphis, TN 55 31 0 0.85 1.8<br />

Kansas <strong>City</strong>, MO 33 12 0 0.75 2.8<br />

Tulsa, OK 28 4 10 0.72 7.0<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 36 13 0 0.69 2.8<br />

Jacksonville, FL 50 12 0 0.65 4.2<br />

Milwaukee, WI 37 16 0 0.63 2.3<br />

Fort Worth, TX 35 4 10 0.60 8.8<br />

Austin, TX 40 9 4 0.60 4.4<br />

Omaha, NE 23 9 0 0.57 2.6<br />

El Paso, TX 31 7 6 0.53 4.4<br />

Denver, CO 28 15 0 0.50 1.9<br />

Albuquerque, NM 22 5 0 0.47 4.4<br />

Tucson, AZ 21 13 3 0.41 1.6<br />

Indianapolis, IN 25 14 0 0.32 1.8<br />

Average 33 12 3 0.58 3.7<br />

Staffing – While the department ranks fifth in total staffing and sixth in the number <strong>of</strong><br />

uniformed firefighters per capita, the percentage <strong>of</strong> uniform firefighters in relation to total<br />

department personnel is significantly lower. Uniformed staffing ratios averaged 95%, while<br />

OKCFD’s staffing ratio was 87%.<br />

In this comparison, six departments have a higher level <strong>of</strong> minimum duty staffing per<br />

10,000 citizens. The number <strong>of</strong> uniformed personnel per 10,000 citizens (15.3) is slightly higher<br />

than the average (15.27) Further, there is no significant difference between the number <strong>of</strong><br />

personnel on-duty between the sample cities (Table 17).<br />

<strong>City</strong><br />

Total Staffing<br />

Table 17: Staffing Comparison<br />

Uniformed FF<br />

(career)<br />

Uniformed<br />

Personnel/<br />

10,000 pop.<br />

Min On-Duty<br />

Staffing<br />

Min On- Duty<br />

Staff/<br />

10,000 pop.<br />

Kansas <strong>City</strong>, MO 950 900 20.3 300 6.8<br />

Tulsa, OK 724 694 17.9 209 5.4<br />

Milwaukee, WI 1090 1013 17.3 260 4.4<br />

Omaha, NE 671 658 16.3 173 4.3<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 948 825 15.5 213 4.0<br />

Jacksonville, FL 1217 1129 14.6 300 3.9<br />

Fort Worth, TX 859 817 14.0 216 3.7<br />

Tucson, AZ 646 590 11.6 184 3.6<br />

Denver, CO 958 914 16.4 186 3.3<br />

Austin, TX 1110 1053 15.7 222 3.3<br />

TriData, a Division <strong>of</strong> 63<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

<strong>City</strong><br />

Total Staffing<br />

Uniformed FF<br />

(career)<br />

Uniformed<br />

Personnel/<br />

10,000 pop.<br />

Min On-Duty<br />

Staffing<br />

Min On- Duty<br />

Staff/<br />

10,000 pop.<br />

Indianapolis, IN 751 751 9.6 250 3.2<br />

Albuquerque, NM 681 660 14.0 143 3.0<br />

Average 878 834 15.2 222 4.1<br />

Table 18 describes the minimum on duty staffing in several other cities. The ratio <strong>of</strong> 4:1<br />

is the average <strong>of</strong> all <strong>of</strong> the cities and for <strong>Oklahoma</strong> <strong>City</strong>. With the 213 uniformed staff members<br />

that the <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department requires as minimum staffing, the department staffs<br />

most <strong>of</strong> its apparatus with three firefighters. Twenty <strong>of</strong> the 36 engine companies in <strong>Oklahoma</strong><br />

<strong>City</strong> are Paramedic Engine Companies that have a four-person crew at all times. The remaining<br />

engines have three-person crews. Two-thirds <strong>of</strong> the cities in the comparison staff all engine<br />

companies with four.<br />

NFPA 1710 recommends staffing levels <strong>of</strong> at least four firefighters on every engine<br />

company and four firefighters on every company performing truck operations. The <strong>Oklahoma</strong><br />

<strong>City</strong> <strong>Fire</strong> Department’s staffing level are below this NFPA staffing recommendation on nonparamedic<br />

engine companies. Proponents <strong>of</strong> NFPA 1710 believe that this potentially limits the<br />

effectiveness <strong>of</strong> first-arriving companies on the fire ground. It may also create an unsafe work<br />

environment, requiring demanding tasks to be shared by fewer individuals, limiting the ability <strong>of</strong><br />

first-responding crews to simultaneously perform all necessary life-saving and fire suppression<br />

tasks on the fire ground, and reducing the amount <strong>of</strong> time and/or frequency that fire crews may<br />

spend in rehab or recuperation areas during extended incidents.<br />

<strong>City</strong><br />

Table 18: Unit Staffing Comparison<br />

Min On-Duty<br />

staffing<br />

Minimum<br />

Engine<br />

Staffing<br />

Minimum<br />

Truck Staffing<br />

Kansas <strong>City</strong>, MO 300 4 4<br />

Milwaukee, WI 260 4 5<br />

Omaha, NE 173 4 4<br />

Fort Worth, TX 216 4 4<br />

Tucson, AZ 184 4 4<br />

Denver, CO 186 4 4<br />

Austin, TX 222 4 3<br />

Albuquerque, NM 143 4 3<br />

Tulsa, OK 209 3 3<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 213 3 3<br />

Jacksonville, FL 300 3 4<br />

Indianapolis, IN 250 3 3<br />

Average 222 4 4<br />

TriData, a Division <strong>of</strong> 64<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

Call Statistics – In 2005, the OKCFD ran 61,484 calls, with more than 80 percent,<br />

being EMS related. Compared with the size <strong>of</strong> <strong>Oklahoma</strong> <strong>City</strong>’s population, this call volume is<br />

slightly lower than average. The department runs 1,174.9 calls per 10,000 citizens, while the<br />

group average is 1,333 calls per 10,000 citizens. The city is slightly lower than average in fire<br />

calls per 10,000 citizens and the same in EMS calls per 10,000 citizens.<br />

The city’s percentages by call type are very comparable to most other cities. Over the<br />

past decade, stronger building and fire codes, safer materials, smoke detectors led to a decrease<br />

in the number <strong>of</strong> fire suppression calls. Residential and industrial sprinkler systems, and<br />

enhanced 911 systems also enable fire departments to respond and mitigate fire suppression<br />

incidents in a faster and more efficient manner, but that nothing to do with the number <strong>of</strong> calls.<br />

During this same period, an aging population and other factors have led to an upsurge <strong>of</strong> EMS<br />

related calls. These calls are expected to continue to increase in the coming decades, requiring<br />

departments to continually evaluate their service levels (Table 19).<br />

<strong>City</strong><br />

Table 19: Call Volumes per 10,000 Citizens<br />

Total Incidents<br />

<strong>Fire</strong> Calls/<br />

10,000 pop.<br />

EMS Calls/<br />

10,000 pop.<br />

All Calls/<br />

10,000 pop.<br />

Memphis, TN 118,565 418.4 1417.0 1835.4<br />

Milwaukee, WI 93,755 269.4 1328.0 1597.3<br />

Jacksonville, FL 121,604 424.6 1147.0 1571.6<br />

Albuquerque, NM 72,628 261.8 1278.3 1540.1<br />

Denver, CO 78,340 482.5 922.7 1405.3<br />

Tucson, AZ 68,543 202.5 1147.7 1350.2<br />

Tulsa, OK 50,902 67.3 1039.0 1312.6<br />

Fort Worth, TX 73,542 535.6 721.2 1256.9<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 61,484 230.4 944.5 1174.9<br />

Indianapolis, IN 81,893 636.5 408.9 1045.3<br />

Austin, TX 64,771 271.1 692.7 963.8<br />

Omaha, NE 31,972 198.9 591.9 790.9<br />

Average 77,865 342.6 972.2 1,333.6<br />

Operating Costs – At $88.6 million, <strong>Oklahoma</strong> <strong>City</strong> has the fourth largest operating<br />

budget and the second highest cost per capita in the comparison group (Table 20). The average<br />

cost per capita is $26.58 per capita above the mean.<br />

Some variables to consider include whether fire code enforcement, vehicle maintenance,<br />

building maintenance, information systems, and other ancillary services are included in the cities<br />

fire departments budget. In OKC, costs for all <strong>of</strong> these services are charged to the fire department<br />

budget.<br />

TriData, a Division <strong>of</strong> 65<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

III. Determining Resource Needs<br />

<strong>City</strong><br />

Population<br />

(2003 Census<br />

Estimate)<br />

Table 20: Cost per Capita Comparison<br />

Total Staffing<br />

Uniformed<br />

Personnel<br />

/10,000 pop<br />

All Calls<br />

/10,000 pop<br />

Operating<br />

Budget<br />

FY 2006<br />

Cost per<br />

Capita<br />

<strong>Oklahoma</strong> <strong>City</strong>, OK 523,303 948 15.5 1174.9 $88,526,524 $169.28<br />

Memphis, TN 645,978 1823 24.3 1835.4 $116,400,000 $180.19<br />

Tulsa, OK 387,807 724 17.9 1312.6 $61,489,000 $158.56<br />

Denver, CO 557,478 958 16.4 1405.3 $88,300,000 $158.39<br />

Omaha, NE 404,267 671 16.3 790.9 $63,000,000 $155.84<br />

Milwaukee, WI 586,941 1090 17.3 1597.3 $88,404,023 $150.62<br />

Fort Worth, TX 585,122 859 14.0 1256.9 $84,143,287 $143.80<br />

Austin, TX 672,011 1110 15.7 963.8 $95,800,000 $142.56<br />

Jacksonville, FL 773,781 1217 14.6 1571.6 $109,000,000 $140.87<br />

Tucson, AZ 507,658 646 11.6 1350.2 $68,594,850 $135.12<br />

Albuquerque, NM 471,586 681 14.0 1540.1 $61,000,000 $129.35<br />

Indianapolis, IN 783,438 751 9.6 1045.3 $58,258,171 $74.36<br />

Average 579,642 957 15.6 1,333.6 $81,308,121 $142.70<br />

Overall, the department receives good marks in comparability. Given the size <strong>of</strong> the land<br />

area covered, the number <strong>of</strong> fire apparatus serving the community seems appropriate and is very<br />

similar to other departments in the comparison. Though this comparison does not include the<br />

specific service areas <strong>of</strong> each station, it is important to be mindful <strong>of</strong> station placement in<br />

relation to the more densely populated areas <strong>of</strong> the city. Since the population density overall is<br />

low, it is important to consider factors related to increased response time because <strong>of</strong> distance<br />

traveled from a station for a particular call.<br />

The department’s call volume, overall operating budget and cost per capita is comparable<br />

to cities <strong>of</strong> similar size for fire department services is comparable to similar departments. This<br />

includes Jacksonville, FL, a jurisdiction <strong>of</strong> similar size.<br />

TriData, a Division <strong>of</strong> 66<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. STATION AND APPARATUS DEPLOYMENT<br />

This chapter discusses the deployment <strong>of</strong> fire stations and emergency response apparatus<br />

at present and going into the future. As discussed in the previous chapters, many factors should<br />

be considered when determining the appropriate number <strong>of</strong> stations, including demand for<br />

services, population, density <strong>of</strong> demand and population, size <strong>of</strong> the jurisdiction, and desired<br />

response times.<br />

For the analysis, project team members gathered information related to station station<br />

locations, including:<br />

• Current station locations and ages<br />

• Current apparatus deployment<br />

• Current zoning, land use and related policies<br />

• National response time standards (see Chapter IV)<br />

• Current OCFD response time standards (see Chapter IV)<br />

• Current and projected population (see Chapter III)<br />

• Current and projected demand and workload (see Chapter III)<br />

Incident data for CY04 and CY06 was gathered from the computer aided dispatch system<br />

(CAD). The data included addresses for geocoding, type <strong>of</strong> incident, units responding, and<br />

overall response times. 39 Geographic information system (GIS) files used for the analysis were<br />

provided by the city.<br />

CURRENT RESPONSE TIMES<br />

The first step in the deployment analysis is a review <strong>of</strong> department-wide response times.<br />

As discussed in Chapter IV, response time is the total amount <strong>of</strong> time elapsing between an<br />

individual calling 911 and emergency service personnel arriving at the scene. Response time can<br />

be broken down into multiple segments for analysis.<br />

The CAD data from CY05 was used to evaluate each segment <strong>of</strong> response times. Invalid<br />

entries (e.g. did not have a time recorded) or obvious errors (e.g. unit arrived before the call<br />

came in) were excluded from the dataset. To eliminate outliers, response times that were more<br />

than three standard deviations from the mean were excluded (Assuming that the travel times<br />

have an approximately normal distribution, three standard deviations equates to 99.7 percent <strong>of</strong><br />

incidents.)<br />

39 Geocoding is a process by which the street address <strong>of</strong> an emergency incident is translated into latitude and<br />

longitude so that it can be placed onto a map.<br />

TriData, a Division <strong>of</strong> 67 September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Call Processing & Dispatch – Call processing time normally includes both call<br />

processing (taking down necessary information) and dispatch (notifying the appropriate units).<br />

Some CAD systems track each time segment separately; most do not. Both are tracked separately<br />

in <strong>Oklahoma</strong> <strong>City</strong>.<br />

In <strong>Oklahoma</strong> <strong>City</strong>, when an individual calls 911, the call is initially answered at the<br />

Bureau <strong>of</strong> Emergency Communications (BOEC). Once the call taker determines that the<br />

emergency is fire or medical related the call is transferred to a fire/EMS dispatcher. <strong>Fire</strong> dispatch<br />

personnel then gather necessary information from the caller and dispatch units. All <strong>of</strong> this time is<br />

included in the call processing times discussed below.<br />

In CY05, call processing times for OCFD averaged 0:34 with a 90 th percentile time <strong>of</strong><br />

1:16 for all call types and priorities. Table 21 shows the 90 th percentile call processing time for<br />

CY05 by type <strong>of</strong> call. The 90 th percentile time for EMS calls are slightly higher than those for<br />

fire calls. The 90 th percentile for EMS call processing times is almost 1 minute higher than<br />

NFPA’s recommended goal, while the 90 th percentile for fire is nearly 30 seconds higher than the<br />

recommended goal. How EMS calls are dispatched are discussed in Chapter V.<br />

Table 21: OCFD Call Processing Time by Call Type<br />

Type<br />

90 th Percentile<br />

<strong>Oklahoma</strong> <strong>City</strong><br />

Goal<br />

EMS 01:20 00:30<br />

<strong>Fire</strong> 00:59 00:30<br />

Some variation can be expected by time <strong>of</strong> day to correspond with heavier or lighter call<br />

volumes. Figure 10 depicts the variation in 90 th percentile call processing time by time <strong>of</strong> day.<br />

Despite the variation in call levels, call processing time is relatively steady throughout the day<br />

ranging from 1:20 between 12 A.M. and 2 A.M. to 1:11 between 6 P.M. and 8 P.M.; a variance <strong>of</strong><br />

nine seconds. This indicates that call-processing performance is very good.<br />

TriData, a Division <strong>of</strong> 68<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Figure 10: 90 th Percentile Call Processing Time by Time <strong>of</strong> Day, CY05<br />

0:01:30<br />

90th Percentile Call Processing<br />

0:01:20<br />

0:01:10<br />

0:01:00<br />

0:00:50<br />

0:00:40<br />

0:00:30<br />

0:01:20<br />

Midnight-<br />

1:59am<br />

0:01:19<br />

2:00-<br />

3:59am<br />

0:01:12<br />

4:00-<br />

5:59am<br />

0:01:17<br />

6:00-<br />

7:59am<br />

0:01:18<br />

8:00-<br />

9:59am<br />

0:01:17<br />

10:00-<br />

11:59am<br />

0:01:16<br />

Noon-<br />

1:59pm<br />

0:01:18<br />

2:00-<br />

3:59pm<br />

0:01:15<br />

4:00-<br />

5:59pm<br />

0:01:11<br />

6:00-<br />

7:59pm<br />

0:01:14<br />

8:00-<br />

9:59pm<br />

0:01:16<br />

10:00-<br />

11:59pm<br />

Dispatch time in <strong>Oklahoma</strong> <strong>City</strong> averages 0:34 and has a 90 th percentile time <strong>of</strong> 1:07.<br />

Table 22 shows the 90 th percentile dispatch time by type <strong>of</strong> call for CY05. The 90 th percentile for<br />

EMS calls is almost 30 seconds faster than the 90 th percentile time for fire calls; however, both<br />

are higher than the recommended goal <strong>of</strong> 30 seconds. They are inline with the current goal for<br />

the dispatch center, with fire being higher than the goal by 34 seconds, and EMS calls exceeding<br />

the goal by only 6 seconds.<br />

Table 22: OCFD Dispatch Time by Call Type<br />

Type<br />

90 th Percentile<br />

<strong>Oklahoma</strong> <strong>City</strong><br />

Goal<br />

EMS 01:06 01:00<br />

<strong>Fire</strong> 01:34 01:00<br />

As with call processing, dispatch times can be expected to vary depending on the time <strong>of</strong><br />

day. Figure 11 shows the 90 th percentile dispatch times based on time <strong>of</strong> day. Again, despite the<br />

variation in call volume, dispatch time is steady throughout the day ranging from 1:14 between 2<br />

P.M. and 4 P.M. to 1:04 between 4 A.M. and 6 A.M.; a variance <strong>of</strong> 10 seconds.<br />

TriData, a Division <strong>of</strong> 69<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Figure 11: 90 th Percentile Dispatch Time by Time <strong>of</strong> Day, CY05<br />

0:01:30<br />

90th Percentile Dispatch<br />

0:01:20<br />

0:01:10<br />

0:01:00<br />

0:00:50<br />

0:00:40<br />

0:00:30<br />

0:01:11<br />

Midnight-<br />

1:59am<br />

0:01:08<br />

2:00-<br />

3:59am<br />

0:01:04<br />

4:00-<br />

5:59am<br />

0:01:05<br />

6:00-<br />

7:59am<br />

0:01:13<br />

8:00-<br />

9:59am<br />

0:01:13<br />

10:00-<br />

11:59am<br />

0:01:12<br />

Noon-<br />

1:59pm<br />

0:01:14<br />

2:00-<br />

3:59pm<br />

0:01:11<br />

4:00-<br />

5:59pm<br />

0:01:08<br />

6:00-<br />

7:59pm<br />

0:01:08<br />

8:00-<br />

9:59pm<br />

0:01:08<br />

10:00-<br />

11:59pm<br />

The overall call processing and dispatch time averages 1:10 with a 90 th percentile time <strong>of</strong><br />

2:06. This is over a minute higher than the recommended 90 th percentile time <strong>of</strong> one minute. It is<br />

not until dropping to the 50 th percentile levels that call processing and dispatch times fall under<br />

one minute. Table 23 shows the overall times at various percentile levels.<br />

Percentile<br />

Table 23: Overall Call Processing & Dispatch Times<br />

Call Processing<br />

Time Dispatch Time Overall Time<br />

90 th Percentile 0:01:16 0:01:10 0:02:08<br />

80 th Percentile 0:00:55 0:00:52 0:01:39<br />

70 th Percentile 0:00:41 0:00:41 0:01:22<br />

60 th Percentile 0:00:30 0:00:34 0:01:10<br />

50 th Percentile 0:00:22 0:00:27 0:00:59<br />

Recommendation 7: Review the call processing and dispatch process to determine<br />

whether any changes can be made to improve call processing and dispatch times. Areas to<br />

consider include staffing levels in the dispatch center, the amount <strong>of</strong> information gathered before<br />

dispatching the first unit, and turnover rates in dispatch staff and resulting lack <strong>of</strong> experience. A<br />

full review <strong>of</strong> the dispatch center was beyond the scope <strong>of</strong> this study; therefore, staffing and<br />

turnover was not reviewed. These are common issues within dispatch centers.<br />

TriData, a Division <strong>of</strong> 70<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Turnout & Travel – Turnout time is measured from when the alarm is received by<br />

personnel to when the apparatus begins driving to the incident scene. Travel (drive) time is the<br />

time it takes to travel from the station, or wherever the unit is, to the emergency incident. <strong>Station</strong><br />

and apparatus placement has the biggest impact on travel time. (Apparatus are not always in the<br />

station when dispatched to an incident.) Additional factors influencing travel time include traffic,<br />

weather, traffic limiting devices (stop lights, speed bumps, etc.), and driver familiarity with the<br />

area. Traffic congestion and weather are beyond the department and city’s control; however,<br />

traffic limiting devices and driver knowledge are not. Turnout time is not recorded separately<br />

from travel time in <strong>Oklahoma</strong> <strong>City</strong>. The times discussed below are for both turnout and travel<br />

(from the time the unit is dispatched until it arrives at the incident). The average turnout and<br />

travel time in <strong>Oklahoma</strong> <strong>City</strong> in CY05 was 4:34 with a 90 th percentile time <strong>of</strong> 7:03, slightly over<br />

two minutes higher than the recommended time <strong>of</strong> five minutes as discussed in Chapter IV (one<br />

minute for turnout, and four minutes for travel).<br />

When examining the turnout and travel times by call type, the times remain similar to the<br />

overall results. The 90 th percentile EMS, fire, and other incident turnout times are 6:43, 8:10, and<br />

8:11 respectively, nearly 2 minutes over the recommended time for EMS calls, and over three<br />

minutes higher for fire calls. The variance in time between EMS and fire calls could be due to<br />

fire calls requiring the donning <strong>of</strong> protective equipment, therefore taking more time to turnout.<br />

When looking at only priority 1 and priority 2 calls, the times are only slightly affected (EMS<br />

time 6:45, fire time 7:56). In other words, the more urgent calls do not change response behavior.<br />

Turnout and travel times vary considerably by time <strong>of</strong> day. <strong>Station</strong> design and personnel<br />

duties (e.g. inspections) also play a role. Figure 12 shows turnout times by time <strong>of</strong> day during<br />

CY05. There is significant (1:19) variation from the peak to the low. This can be expected since<br />

personnel are generally asleep between midnight and 6 A.M., and travel is more difficult due to<br />

reduced visibility, though traffic may be less. Turnout and travel times during the rest <strong>of</strong> the day<br />

exceed the recommended five-minutes for turnout and travel by almost two minutes.<br />

The city’s land mass must always be considered. Travel times in several areas may be<br />

consistently longer due to response district size. These variables were considered when making<br />

our recommendations.<br />

TriData, a Division <strong>of</strong> 71<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Figure 12: Turnout & Travel Times by Time <strong>of</strong> Day, CY05<br />

0:10:00<br />

90th Percentile Turnout & Travel Time<br />

0:09:00<br />

0:08:00<br />

0:07:00<br />

0:06:00<br />

0:05:00<br />

0:04:00<br />

0:07:32<br />

Midnight-<br />

1:59am<br />

0:08:05<br />

2:00-<br />

3:59am<br />

0:07:45<br />

4:00-<br />

5:59am<br />

0:07:03<br />

6:00-<br />

7:59am<br />

0:06:57<br />

8:00-<br />

9:59am<br />

0:06:47<br />

10:00-<br />

11:59am<br />

0:06:50<br />

Noon-<br />

1:59pm<br />

0:06:55<br />

2:00-<br />

3:59pm<br />

0:06:59<br />

4:00-<br />

5:59pm<br />

0:06:46<br />

6:00-<br />

7:59pm<br />

0:06:49<br />

8:00-<br />

9:59pm<br />

0:07:03<br />

10:00-<br />

11:59pm<br />

Figure 13 shows the variation in turnout and travel times by call type for 2005. EMS<br />

times generally reflect those showed in Figure 12 peaking between 2 A.M. and 4 A.M. and having<br />

the fastest time between 6 P.M. and 8 P.M. <strong>Fire</strong> calls have consistently higher response times than<br />

EMS calls. There are two major peaks in fire turnout and travel times; between 2 A.M. and 4<br />

A.M., and 2 P.M. and 4 P.M. The lowest times for fire calls are between 8 P.M. and 10 P.M. (7:36).<br />

The difference in times between EMS and fire calls could be caused by first due units not being<br />

available because <strong>of</strong> high EMS call volumes. The result would be that the second or third due<br />

units are responding.<br />

TriData, a Division <strong>of</strong> 72<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Figure 13: Turnout & Travel Times by Time <strong>of</strong> Day and Call Type, CY05<br />

0:10:00<br />

OCFD EMS <strong>Fire</strong> Other<br />

0:09:00<br />

0:08:00<br />

0:07:00<br />

0:06:00<br />

0:05:00<br />

0:04:00<br />

0:07:16<br />

0:08:35<br />

0:08:39<br />

Midnight-<br />

1:59am<br />

0:07:51<br />

0:09:02<br />

0:08:57<br />

2:00-<br />

3:59am<br />

0:07:35<br />

0:08:29<br />

0:08:10<br />

4:00-<br />

5:59am<br />

0:06:52<br />

0:07:39<br />

0:07:50<br />

6:00-<br />

7:59am<br />

0:06:43<br />

0:07:54<br />

0:08:16<br />

8:00-<br />

9:59am<br />

0:06:26<br />

0:07:44<br />

0:07:48<br />

10:00-<br />

11:59am<br />

0:06:24<br />

0:08:19<br />

0:08:29<br />

Noon-<br />

1:59pm<br />

0:06:25<br />

0:08:39<br />

0:07:38<br />

2:00-<br />

3:59pm<br />

0:06:26<br />

0:08:11<br />

0:09:20<br />

4:00-<br />

5:59pm<br />

0:06:20<br />

0:07:59<br />

0:07:57<br />

6:00-<br />

7:59pm<br />

0:06:31<br />

0:07:36<br />

0:07:48<br />

8:00-<br />

9:59pm<br />

0:06:44<br />

0:07:38<br />

0:07:42<br />

10:00-<br />

11:59pm<br />

When looking at only priority 1 and 2 calls by time <strong>of</strong> day, EMS times remain largely the<br />

same; however, fire response times drop a good deal at certain points <strong>of</strong> the day. Figure 14<br />

shows the changes in fire times by time <strong>of</strong> day for all priorities and for only priority 1 and 2<br />

calls. There is an average decrease in turnout and travel time <strong>of</strong> 19 seconds over the course <strong>of</strong> the<br />

day, quite small. The largest decrease occurs between 2 A.M. and 4 A.M. (1:03), and the response<br />

time actually increases slightly between 10 P.M. and Midnight (0:13). While considering only<br />

priority 1 and 2 calls does improve fire turnout and travel times, they still remain two to three<br />

minutes higher than the recommended five minutes.<br />

TriData, a Division <strong>of</strong> 73<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Figure 14: Priority 1&2 vs. Overall <strong>Fire</strong> Turnout & Travel Times by Time <strong>of</strong> Day, CY05<br />

0:10:00<br />

<strong>Fire</strong><br />

P1&2 <strong>Fire</strong><br />

0:09:00<br />

0:08:00<br />

0:07:00<br />

0:08:12<br />

0:07:59<br />

0:07:58<br />

0:07:19<br />

0:07:37<br />

0:07:03<br />

0:08:08<br />

0:08:30<br />

0:08:11<br />

0:07:33<br />

0:07:35<br />

0:07:51<br />

0:06:00<br />

0:05:00<br />

0:04:00<br />

0:08:35<br />

Midnight-<br />

1:59am<br />

0:09:02<br />

2:00-<br />

3:59am<br />

0:08:29<br />

4:00-<br />

5:59am<br />

0:07:39<br />

6:00-<br />

7:59am<br />

0:07:54<br />

8:00-<br />

9:59am<br />

0:07:44<br />

10:00-<br />

11:59am<br />

0:08:19<br />

Noon-<br />

1:59pm<br />

0:08:39<br />

2:00-<br />

3:59pm<br />

0:08:11<br />

4:00-<br />

5:59pm<br />

0:07:59<br />

6:00-<br />

7:59pm<br />

0:07:36<br />

8:00-<br />

9:59pm<br />

0:07:38<br />

10:00-<br />

11:59pm<br />

Table 24 shows the 90 th percentile turnout and travel times for EMS, fire, and other calls<br />

by all priority levels as well as only priority 1 and 2 calls. EMS calls remain about the same<br />

regardless <strong>of</strong> priority. <strong>Fire</strong> times, however, improve by 14 seconds when only looking at priority<br />

1 and 2 calls. Other call times increase for priority 1 and 2, this is largely due to only a few other<br />

type incidents being such a high priority.<br />

Table 24: 90 th Percentile Turnout & Travel Time by Call Type and Priority<br />

Call Type All Priorities Priority 1 & 2 Difference<br />

EMS 0:06:43 0:06:45 + 0:00:02<br />

<strong>Fire</strong> 0:08:10 0:07:56 - 0:00:14<br />

Other 0:07:41 0:08:22 + 0:00:41<br />

It is easier and less costly to improve call processing and turnout times than travel<br />

response time. Travel time is typically much more difficult and the most expensive to improve,<br />

(requiring new stations, new roads, traffic signal interruption devices, etc. Reduction in call<br />

processing, dispatch, and turnout time also permits longer travel times without increasing total<br />

response times. The critical time is to dispatch the first unit; further call processing can occur<br />

simultaneously (i.e., talking more to the caller to obtain details).<br />

TriData, a Division <strong>of</strong> 74<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Total Response Time – For mathematical reasons, one cannot simply add the 90 th<br />

percentile time components <strong>of</strong> response time to reach the total 90 th percentile response time, one<br />

needs to compute the total directly. In CY05, total response times for OCFD averaged 05:47 for<br />

the first arriving unit to all calls with a 90 th percentile total response time <strong>of</strong> 08:35. Total<br />

response times are above current and recommended goals by 02:35.<br />

Table 25 shows the 90 th , 80 th , 70 th , and 60 th percentile total response times in CY05<br />

incidents by call type. There is a nearly two minute difference in total response time between<br />

EMS calls and fire calls at the 90 th percentile level; however, that decreases at the 80 th percentile<br />

level, which is still quite a good level to achieve. The total response times are over the<br />

recommended goal <strong>of</strong> 6 minutes at the 90 th percentile level, and do not fall below 6 minutes until<br />

the 60 th percentile level. The difference between fire and EMS response times could be attributed<br />

to fire apparatus having extended travel times or, there being more apparatus available for EMS<br />

calls.<br />

Table 25: CY05 60 th , 80 th, and 90 th Percentile Total Response Time by Call Type<br />

Call Type EMS <strong>Fire</strong><br />

60th Percentile 0:05:36 0:06:08<br />

70th Percentile 0:06:08 0:06:53<br />

80th Percentile 0:06:52 0:07:57<br />

90th Percentile 0:08:12 0:09:58<br />

Actual response times in <strong>Oklahoma</strong> <strong>City</strong> are compared to NFPA standards and the study<br />

team’s recommended goals in Table 26.<br />

Table 26: <strong>Oklahoma</strong> <strong>City</strong> Response Times, CY05 vs. Standards and Goals<br />

Time Segment<br />

Current 90 th<br />

Percentile<br />

Current OCFD<br />

Goal<br />

Reduction<br />

Needed<br />

Recommended<br />

Goal<br />

Reduction<br />

Needed<br />

Call Processing 0:01:16 n/a n/a 0:00:30 0:00:46<br />

Dispatch 0:01:10 0:01:00 0:00:10 0:00:30 0:00:40<br />

Call Processing + Dispatch 0:02:08 n/a n/a 0:01:00 0:01:08<br />

Turnout + Travel 0:07:03 0:05:00 X 0:00:44 0:05:00 0:02:03<br />

Total 0:08:35 0:06:00 Y 0:01:05 0:06:00 0:02:35<br />

X<br />

The 5 minute goal for OCFD is at the 80 th percentile level (current 80 th percentile response time – 5:44)<br />

Y<br />

The 6 minute total response time goal is at the 80 th percentile level (current 80 th percentile response time – 7:05)<br />

TriData, a Division <strong>of</strong> 75<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Total response times are over two minutes (2:35) higher than the recommended time <strong>of</strong><br />

six minutes all calls. These total response times are high and the department should take steps to<br />

reduce the times and improve 90 th percentile compliance. That being said, the department is<br />

doing a very good job providing service, meeting the six-minute response time goal at the 60 th<br />

percentile level. Focus should be placed on reducing call processing and dispatch times to get the<br />

overall total response time closer to the 90 th percentile compliance level, unless the city is willing<br />

to accept the current level <strong>of</strong> performance as a norm.<br />

ANALYSIS OF STATION AND APPARATUS LOCATIONS<br />

This section provides an in-depth look at station and apparatus placement. The goal is to<br />

determine what areas, if any, are in need <strong>of</strong> additional or fewer resources. Engine coverage is<br />

discussed by region while rescue ladder, hazmat, and battalion chief coverage is discussed<br />

citywide.<br />

This study focused on the following points for each station:<br />

• <strong>Station</strong> <strong>Location</strong><br />

• Date <strong>of</strong> construction<br />

• Number <strong>of</strong> personnel assigned<br />

• Availability <strong>of</strong> additional space for more personnel<br />

• Availability <strong>of</strong> additional space for more apparatus<br />

• Special issues that impact response times<br />

Excluded was an engineering structural analysis <strong>of</strong> each station.<br />

Figure 15 on the next page, shows the fire districts and current fire station locations. Note<br />

that there is no <strong>Station</strong> 26. Tables 27–32 are descriptions <strong>of</strong> the stations organized by fire district.<br />

TriData, a Division <strong>of</strong> 76<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 15: <strong>Fire</strong> Districts and <strong>Fire</strong> <strong>Station</strong> <strong>Location</strong>s 2006<br />

TriData, a Division <strong>of</strong> 77<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Station</strong><br />

Number<br />

Table 27: Characteristics <strong>of</strong> <strong>Station</strong>s in District 601<br />

Constructed<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

1 1977 53 Yes No None<br />

4 1981 15 Yes No None<br />

5 1994 30 Yes No None<br />

6 1997 24 Yes Yes None<br />

8 1986 27 Yes Yes None<br />

10 1973 15 No No None<br />

<strong>Station</strong><br />

Number<br />

Constructed<br />

Table 28: Characteristics <strong>of</strong> <strong>Station</strong>s District 602<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

2 1978 16 Yes Yes None<br />

11 1976 15 Yes Yes None<br />

12 1974 15 Yes Yes None<br />

18 1990 31 Yes Yes None<br />

22 1990 26 Yes Yes None<br />

27 1987 23 No No None<br />

<strong>Station</strong><br />

Number<br />

Constructed<br />

Table 29: Characteristics <strong>of</strong> <strong>Station</strong>s District 603<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

7 1982 11 No No None<br />

13 1977 17 Yes Yes None<br />

16 1970 26 Yes Yes None<br />

23 1974 21 No Yes None<br />

28 1983 21 No Yes None<br />

36 1994 21 Yes Yes None<br />

TriData, a Division <strong>of</strong> 78<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Station</strong><br />

Number<br />

Constructed<br />

Table 30: Characteristics <strong>of</strong> <strong>Station</strong>s District 604<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

3 1978 17 Yes Yes Radio<br />

Coverage<br />

15 1970 30 Yes No None<br />

30 1968 36 No No None<br />

32 1978 17 No Yes None<br />

34 1993 30 Yes Yes None<br />

37 1996 21 Yes Yes None<br />

<strong>Station</strong><br />

Number<br />

Constructed<br />

Table 31: Characteristics <strong>of</strong> <strong>Station</strong>s District 605<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

9 1968 27 No No None<br />

19 1951 15 Yes Yes None<br />

21 1960? 15 No Yes Poor Physical<br />

Condition<br />

25 1991 39 No Yes None<br />

35 1993 21 Yes Yes None<br />

<strong>Station</strong><br />

Number<br />

Constructed<br />

Table 32: Characteristics <strong>of</strong> <strong>Station</strong>s District 606<br />

Current<br />

Personnel<br />

Room for<br />

Additional<br />

Personnel?<br />

Room for<br />

Additional<br />

Apparatus?<br />

Special Issues<br />

14 1993 27 Yes Yes None<br />

17 1986 15 Yes Yes None<br />

20 1978 18 Yes Yes None<br />

24 1978 15 Yes Yes None<br />

31 1973 36 Yes Yes Limited parking<br />

33 1991 18 Yes Yes None<br />

In the course <strong>of</strong> evaluating station relocations, consideration must given to the finding<br />

that nine <strong>of</strong> the buildings will not accommodate more apparatus and that eight <strong>of</strong> buildings are at<br />

their practical limits for personnel.<br />

TriData, a Division <strong>of</strong> 79<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

RECOMMENDED MOVES AND ADDITIONAL STATIONS AND APPARATUS<br />

We conducted a GIS analysis <strong>of</strong> response time reach <strong>of</strong> each station for the four and eight<br />

minute response times. As the city continues to grow it will become necessary to expand the<br />

number <strong>of</strong> fire stations to maintain desired coverage. . The current coverage for four minute<br />

response times is illustrated in Figure 16. There are large portions <strong>of</strong> the city especially the<br />

Northeast and Southwest quadrants, where response times far exceed the four-minute goal.<br />

In addition to the need for construction <strong>of</strong> some new stations and the associated increases<br />

in staffing, we found opportunities to move existing companies for greater coverage, especially<br />

from the downtown area to locations where current response times surpass the four minute level.<br />

In the downtown area there are overlaps in coverage that are sufficient and allow these resources<br />

to be redeployed. The coverage still will be adequate for most calls in the areas from which they<br />

are moved. The recommendations are listed in priorities based on current and projected<br />

development and the projections for demand. Capital funding will have to be planned in advance<br />

and these recommendations should be incorporated into any master planning process.<br />

Overall, we recommend five new stations, closing two existing stations and movement <strong>of</strong><br />

several pieces <strong>of</strong> apparatus.<br />

Bricktown - <strong>Station</strong> 6 is in poor condition and resides on land that is to be sold to the<br />

University <strong>of</strong> <strong>Oklahoma</strong>. The engine and rescue ladder will provide better service from other<br />

locations. Engine 6 would be moved to a location in the Northeast portion <strong>of</strong> the <strong>City</strong> and the<br />

Rescue Ladder would be moved to the new station for Engine 51.<br />

<strong>Station</strong> 1 houses two engine companies, Engine 1 and Engine 51. Engine 51 is the third<br />

slowest company in the <strong>City</strong>. Only Engines 36 and 32 have fewer annual responses. If the growth<br />

projections shown in Table 6 are used as a baseline, and if Engine 1 absorbed all <strong>of</strong> Engine 51’s<br />

responses (which is unlikely), Engine 1 would still not exceed the 3000 response per threshold<br />

for several years. If the dispatch recommendations regarding the weight <strong>of</strong> response<br />

(Recommendation #6) are adopted, Engine 1 may not exceed the 3000 call level until after 2010.<br />

Current legislation calls for a new station to be built in Bricktown. Funding for the station<br />

is tied to the legislation. The proposed building should be a minimum <strong>of</strong> a three-bay structure<br />

with drive through bays and have accommodations for 10-14 personnel per shift. A building <strong>of</strong><br />

this size will provide flexibility for any future redeployments or additions <strong>of</strong> apparatus. This<br />

includes the ability to house an ambulance.<br />

Figure 18 shows a 4-minute response map showing the projected coverage areas after<br />

Engine 51 is moved. <strong>Station</strong>s 5, 7, 8, 10 and 51 (Bricktown) will provide the redundancy needed<br />

to assure back-up response into <strong>Station</strong> 1’s area.<br />

Recommendation 8: Priority #1 –Construct a new fire station at the intersection <strong>of</strong><br />

Reno Avenue and Lincoln Avenue in the “Bricktown” district. Move Engine 51 from <strong>Station</strong> 1<br />

TriData, a Division <strong>of</strong> 80<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

and upgrade this company to paramedic engine status. Move the rescue ladder from <strong>Station</strong> 6 to<br />

this new station.<br />

Northeast – The northeast area <strong>of</strong> the city is expanding with newer, larger homes being<br />

built at a fast pace. This area relies on <strong>Station</strong>s 2 and 27 for fire and EMS first response. Jones,<br />

<strong>Oklahoma</strong> also borders this area, but its fire department a volunteer department and the <strong>City</strong><br />

should not depend heavily on mutual aid. The addition <strong>of</strong> a northeast company will help alleviate<br />

the response time challenge.<br />

The tanker from <strong>Station</strong> 21 should also be moved to the new <strong>Station</strong> 6. Engine 6 should<br />

be upgraded to paramedic engine status. With the number <strong>of</strong> engine companies now located<br />

downtown the response times or workloads will not be compromised in the downtown area.<br />

Given the existing growth and development patterns compared to the response time deficiencies;<br />

this move is the second priority.<br />

Recommendation 9: Priority #2 - Relocate Engine 6 from North 10th Street to a new<br />

station at the Northwest corner <strong>of</strong> Henney and Memorial Roads. The tanker from <strong>Station</strong> 21<br />

should also be moved to this station. Funding for this project should be included in Fiscal Year<br />

2008 and construction to begin as soon as possible.<br />

<strong>Location</strong> “B” in Figure 17 shows the location <strong>of</strong> the new <strong>Station</strong> 6.<br />

TriData, a Division <strong>of</strong> 81<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 16: Current 4-Minute Travel Time<br />

TriData, a Division <strong>of</strong> 82<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 17: Proposed <strong>Location</strong> <strong>of</strong> the New Northeast <strong>Station</strong><br />

TriData, a Division <strong>of</strong> 83<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Current access to the Kilpatrick Turnpike in the northeast portion <strong>of</strong> the city is limited.<br />

As part <strong>of</strong> the capital project to construct a new fire station, highway access to the Turnpike<br />

should be included because the closest access to the turnpike is now in <strong>Station</strong> 2’s area. This will<br />

provide access from both directions and reduce response times to incidents on the turnpike.<br />

Response times on the turnpike to the city boundary will not improve if this step is not<br />

taken. There are no obvious obstacles to placing a station near this location. <strong>Station</strong> design, and<br />

the amount <strong>of</strong> property needed to accommodate the new station is beyond the scope <strong>of</strong> this study.<br />

Recommendation 10: When the new Northeast station is built, provide emergency<br />

vehicle access to the Turnpike. This will allow access from two directions and improve<br />

response times.<br />

Southwest – Consider adding a new station at the Northwest corner <strong>of</strong> Council and SW<br />

104 th Street and close Engine 4 and move Engine 4 to this location. This area is an Urban Growth<br />

Area defined by the <strong>City</strong>. If the planned outer loop highway is constructed, linking the Kilpatrick<br />

Turnpike with Interstates 44 and 240, growth and development will surely follow. The <strong>City</strong><br />

should consider acquiring land now for use as a fire station, rather than waiting for the growth to<br />

occur and drive property costs up.<br />

The <strong>Oklahoma</strong> <strong>City</strong> Planning Department conducted a study <strong>of</strong> growth for the Southwest<br />

portion <strong>of</strong> the <strong>City</strong>. The “Southwest Sector Plan” prepared in March <strong>of</strong> 2006 examined 3.5 and 5<br />

minute response patterns in this portion <strong>of</strong> the <strong>City</strong>. 40 The funds for land acquisition, design and<br />

construction should be included in the FY 2009 Budget. The suggested location is indicated as<br />

“C” in Figure 18.<br />

Recommendation 11: Priority #3 – Relocate <strong>Station</strong> 4 from Reno and Santa Fe to a<br />

location on the Northwest corner <strong>of</strong> Council and SW 104th Street. This Engine Company<br />

should be upgraded to Paramedic Engine status.<br />

By closing <strong>Station</strong> 4 and moving Engine 4 to the new location, no gaps in the 4 or 8<br />

minute response times appear. If the current number <strong>of</strong> annual responses are divided among the<br />

surrounding companies, (Engines, 8, 7, 1, 51 [Bricktown] and 23) none <strong>of</strong> these companies<br />

should exceed the 3000 annual response levels for many years. The recommended changes to the<br />

weight <strong>of</strong> responses will also help slow the rate <strong>of</strong> growth in responses.<br />

STRATEGIC CONSIDERATIONS: Given the growth in population and housing trends and,<br />

the demand research discussed earlier, there are other areas <strong>of</strong> the city where the response time<br />

will exceed the four and eight minutes. Current and anticipated growth will require new<br />

companies to be added to keep response times within accepted limits. The new stations address<br />

near future as opposed to immediate needs than the moves <strong>of</strong> the existing companies. Creating<br />

40 Southwest Sector Plan, <strong>Oklahoma</strong> <strong>City</strong> Planning Department, page 35.<br />

TriData, a Division <strong>of</strong> 84<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

new companies also has a higher cost due to the increases in personnel costs. Land acquisition at<br />

this time is advisable as a means to reduce future capital costs.<br />

Southwest – The extreme southwest sections <strong>of</strong> <strong>Oklahoma</strong> <strong>City</strong> lie between the smaller<br />

cities <strong>of</strong> Mustang, Yukon and Tuttle. Between 2000-2005, Mustang and Tuttle experienced a 20<br />

percent increase and Yukon a 5 percent increase in population. This projected population growth<br />

will likely lead to a population increase in the adjoining areas <strong>of</strong> the city. 41<br />

With growth projections in mind another Engine Company will be need in the far<br />

Southwest part <strong>of</strong> town.<br />

Recommendation 12: Priority #4 – Construct and staff a new station with a Paramedic<br />

Engine Company in the area <strong>of</strong> Richland and 59th Street.<br />

This location is indicated as “D” on Figure 18. While demand for service does not make<br />

this project as high a priority as the first three stations nonetheless, the <strong>City</strong> should acquire<br />

property for a station in this area. Funding for construction, apparatus and new personnel to staff<br />

the equipment should be included in the FY 2011 Budget.<br />

Alternatively, protection could be enhanced by consolidating the Mustang <strong>Fire</strong><br />

Department into the OKCFD. A full discussion <strong>of</strong> this is beyond the scope <strong>of</strong> this report.<br />

Southeast – The federal military Base Alignment, Relocation and Closure (BRAC) has<br />

designated Tinker Air Force Base and Will Rogers Field Air National Guard <strong>Station</strong> as areas for<br />

realignment and growth. 42 As such, activities will be brought to these bases. As more military<br />

and civilian employees will work in this area, housing and development needs may increase.<br />

Further, these locations may be terminal career points for retiring military and civilian personnel.<br />

In the same area <strong>of</strong> the <strong>City</strong> an issue is the Urban-Wildland interface. Brush fire<br />

challenges are already experienced in this area. The city should consider adding a new station<br />

near Douglas and 149 th Street.<br />

Recommendation 13: Priority #5 – Add a new station with a paramedic engine and<br />

tanker at Douglas and 149 th Street.<br />

This location is indicated as “E” in Figure 18. As with the new station location in<br />

Recommendation #12, the current demand makes this location a lower priority than<br />

Recommendations #8, #9 and #11. Funding for this project be in the FY 2013 Budget, but<br />

possibility earlier if growth and demand are accurate.<br />

With the implementation <strong>of</strong> recommendations 8 through 13 above, the four minute<br />

response time coverage would be as shown in Figure 18.<br />

41 http://www.city-data.com/city/Mustang-<strong>Oklahoma</strong>.html<br />

42 http://www.globalsecurity.org/military/facility/tinker.htm<br />

TriData, a Division <strong>of</strong> 85<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 18: Proposed 4 Minute Travel with new <strong>Station</strong> locations<br />

TriData, a Division <strong>of</strong> 86<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Relocations and Unit Additions – The analysis <strong>of</strong> current resource deployment also<br />

found that there is overlap with rescue ladder coverage and district chief coverage. We make<br />

several recommendations to more efficiently deploy these resources. .<br />

RESCUE LADDERS: The current rescue ladder coverage pattern shows that the rescue<br />

ladders are concentrated in the central part <strong>of</strong> the city. As the city expands outward there is a<br />

need to have the rescue ladder coverage expand as well. The need is illustrated in Figure 19.<br />

There are large areas <strong>of</strong> the city where the response time for the rescue ladders exceeds 8<br />

minutes.<br />

There is a need to achieve eight-minute response time coverage for the eastern side <strong>of</strong><br />

the city. Figure 19 shows that the closest rescue ladder (Ladder 16) has an extended response<br />

time east <strong>of</strong> <strong>Station</strong> 13. Figure 20 shows how an additional rescue ladder will help bridge this<br />

gap. This move also enhances additional heavy rescue coverage along the current and future<br />

planned I-240.<br />

The review <strong>of</strong> the <strong>Station</strong> 28 indicates that there is not enough room to add another<br />

company to the existing building so, this move will require a capital improvement project to add<br />

space for apparatus and personnel. Given the gaps in coverage as illustrated in Figure 19 above,<br />

this move is necessary. Funding for this project should be included in the FY 2010 Budget.<br />

Recommendation 14: Add a rescue ladder to <strong>Station</strong> 28 and make necessary additions<br />

to the building to accommodate additional apparatus and personnel<br />

In the far Southwest area <strong>of</strong> the <strong>City</strong> another gap in Rescue Ladder coverage exists. By<br />

relocating an existing rescue ladder company, more effective response coverage would occur.<br />

Moving the rescue ladder from <strong>Station</strong> 31 to <strong>Station</strong> 20 can do this. By doing so, this company<br />

would provide coverage for both areas .The eight-minute response pattern depicted in 19<br />

supports this point.<br />

Based on the review <strong>of</strong> the building at <strong>Station</strong> 20, this will require a capital improvement<br />

project to add space for equipment and personnel. As part <strong>of</strong> other deployments, this move is<br />

reduce response times for ladder companies. This project should be funded in the 2010 budget<br />

Recommendation 15: Move the rescue ladder from <strong>Station</strong> 31 to <strong>Station</strong> 20 and make<br />

necessary additions to the building to accommodate additional apparatus and personnel.<br />

.<br />

TriData, a Division <strong>of</strong> 87<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 19: Current Rescue Ladder <strong>Location</strong>s and Eight Minute Travel times<br />

TriData, a Division <strong>of</strong> 88<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 20: Proposed Rescue Ladder <strong>Location</strong> and Eight-Minute Travel<br />

TriData, a Division <strong>of</strong> 89<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

DISTRICT CHIEFS: A similar pattern <strong>of</strong> overlap in the District chief coverage exists with<br />

several District chiefs too close together and in some areas too far apart. Figure 21 illustrates the<br />

current locations <strong>of</strong> District chief in Blue. Presently, all six district chiefs are concentrated in the<br />

central city area. This provides much over lap downtown at the cost <strong>of</strong> increasing response times<br />

to the outlying areas <strong>of</strong> the city. Response times to the outlying areas <strong>of</strong> the <strong>City</strong> could be<br />

improved by relocating some <strong>of</strong> the chiefs. These moves would improve operations by providing<br />

the Command function on scene earlier in the incident in the outlying areas.<br />

Changes in district chief boundaries will require capital improvement projects to add<br />

space for <strong>of</strong>fices, vehicles and quarters. Figure 22 illustrates the new locations for the District<br />

chiefs.<br />

Recommendation 16: Move District Chief 602 from <strong>Station</strong> 18 to <strong>Station</strong> 2 and Move<br />

District Chief 603 from <strong>Station</strong> 7 to <strong>Station</strong> 23.<br />

By realigning the stations for the District chiefs, their response times will improve. These<br />

recommendations would not change the boundaries <strong>of</strong> the existing districts.<br />

TriData, a Division <strong>of</strong> 90<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 21: Current <strong>Location</strong> <strong>of</strong> District Chiefs<br />

TriData, a Division <strong>of</strong> 91<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 22: Proposed <strong>Location</strong> <strong>of</strong> District Chiefs<br />

TriData, a Division <strong>of</strong> 92<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

TANKERS: Wildland/Urban interface and the risk <strong>of</strong> brushfires require the city to pay<br />

special attention to the availability <strong>of</strong> water supplies. Many areas outside the central city lack<br />

access to water for fire suppression. The department must strategically place equipment to shuttle<br />

water and deliver water to remote sites.<br />

The above recommendations include the addition and movement <strong>of</strong> tankers in specific<br />

areas <strong>of</strong> the city. Figure 23 shows the proposed locations <strong>of</strong> Tankers.<br />

TriData, a Division <strong>of</strong> 93<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 23: Proposed <strong>Location</strong> <strong>of</strong> Tankers<br />

TriData, a Division <strong>of</strong> 94<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

SUMMARY<br />

The analysis <strong>of</strong> response times and demands for service coupled with expected<br />

development <strong>of</strong> the <strong>City</strong> led us to several conclusions:<br />

• Large portions <strong>of</strong> the city exceed the areas <strong>of</strong> four and eight minute response time<br />

reach for fire and ALS units. At this time, much <strong>of</strong> this area is undeveloped.<br />

Residential and commercial growth is predicted to occur in these areas.<br />

• There are overlaps in coverage in the downtown area. Response times are within four<br />

and eight minute pr<strong>of</strong>iles and workloads are not excessive (see Figure 24).<br />

• The Northeast and Southwest quadrants <strong>of</strong> the city continue to grow and current<br />

zoning will not slow this growth. Planned expansion <strong>of</strong> the Interstate Highway<br />

network will only add to this growth.<br />

• Opportunities exist to move some existing companies from downtown to outlying<br />

growth areas. The costs would be for capital outlays to construct new buildings,<br />

which is vastly less than adding new stations, personnel and equipment.<br />

• <strong>Location</strong>s have been identified for future companies to be established. These<br />

locations can be incorporated into a 5 year or 10 year planning process to include<br />

some land acquisition now and plans for capital funding.<br />

TriData, a Division <strong>of</strong> 95<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 24: Proposed Four and Eight-Minute Travel Times for current and proposed <strong>Station</strong>s<br />

TriData, a Division <strong>of</strong> 96<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Summary <strong>of</strong> Deployment Changes – Table 33 summarizes the deployment changes by<br />

station. Personnel are listed by shift and reflect authorized staffing, not actual. Paramedic engines<br />

companies are shown staffed with 5 personnel assigned to them and operate with 4 personnel,<br />

while rescue ladders and non-paramedic engines are staffed with 4 to assure operating with 3<br />

personnel. There are several recommendations for upgrades <strong>of</strong> existing engine companies to<br />

become paramedic engine companies in the next chapter. Those upgrades are listed in this table.<br />

This table represents the effect <strong>of</strong> all <strong>of</strong> the recommendations TriData has <strong>of</strong>fered in this study.<br />

The location and storage <strong>of</strong> reserve equipment was not listed in this table.<br />

<strong>Station</strong><br />

Table 33: Summary <strong>of</strong> Proposed Deployment Plan<br />

Equipment<br />

1 Engine, Rescue Ladder, Air Unit,<br />

EMS Supervisor. District chief<br />

2 Engine, District Chief and Brush<br />

Truck<br />

Minimum<br />

Personnel<br />

Per Shift<br />

Changes<br />

14 Move Engine 51 to new station in<br />

Bricktown<br />

6 District chief moved here from <strong>Station</strong><br />

18<br />

3 Engine and Brush Truck 5 Upgrade to paramedic engine<br />

4 Engine and Brush Truck 5 Moved to new station at Council and<br />

104 th Street<br />

5 Engine and Haz-Mat 10 None<br />

6 Engine and Tanker 6 Moved to Henny and Memorial Street<br />

Tanker added from <strong>Station</strong> 21 added.<br />

Upgrade engine to paramedic engine<br />

Rescue ladder moved to new station<br />

in Bricktown<br />

7 Engine and Rescue Ladder 5 Rescue ladder and District chief<br />

Moved to <strong>Station</strong> 23<br />

8 Engine, Rescue Ladder, Dive Units 9 None<br />

9 Engine and Rescue Ladder 9 None<br />

10 Engine 5 None<br />

11 Engine and Command Post Vehicle 4 None<br />

12 Engine and Light Unit 5 None<br />

13 Engine and Brush Truck 5 Upgrade to paramedic engine<br />

14 Engine and Rescue ladder 9 None<br />

15 Engine, Rescue Ladder and Brush<br />

10 None<br />

Truck<br />

16 Engine and Rescue Ladder 9 None<br />

17 Engine 5 None<br />

18 Engine, Rescue Ladder and Foam<br />

Trailer<br />

10 District Chief Moved to <strong>Station</strong> 2<br />

20 Engine Rescue Ladder and Brush<br />

Truck<br />

8 Rescue Ladder moved from <strong>Station</strong><br />

31<br />

21 Engine 5 Tanker moved to <strong>Station</strong> 6<br />

TriData, a Division <strong>of</strong> 97<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

<strong>Station</strong><br />

Equipment<br />

22 Engine, Rescue Ladder and Turnpike<br />

Rescue<br />

23 Engine, District Chief and Brush<br />

Truck<br />

Minimum<br />

Personnel<br />

Per Shift<br />

9 None<br />

24 Engine, and Light Tower 5 None<br />

25 Engine, Rescue Ladder District chief<br />

and Brush Truck<br />

Changes<br />

7 District chief moved here from<br />

<strong>Station</strong> 7<br />

11 None<br />

27 Engine, Brush Truck and Tanker 6 None<br />

28 Engine, Rescue Ladder and Brush<br />

Truck<br />

29 Engine, Brush and Tanker 5 None<br />

30 Engine, Rescue and District chief 11 None<br />

9 Add a new Rescue ladder Company<br />

31 Engine, District Chief 6 Rescue ladder moved to <strong>Station</strong> 20<br />

32 Engine and Brush Truck 5 None<br />

33 Engine Brush Truck and Tanker 6 Upgrade to paramedic engine<br />

34 Engine, Rescue Ladder and Tanker 10 None<br />

35 Engine, Brush Truck and Tanker 5 None<br />

36 Engine, Brush Truck and Tanker 5 None<br />

37 Engine, Brush Truck and Tanker 6 Upgrade to paramedic engine<br />

51-“A”<br />

New<br />

6-“B”<br />

New<br />

4-“C”<br />

New<br />

“D”<br />

New<br />

“E”<br />

New<br />

Engine and Rescue Ladder 8 New <strong>Station</strong> (projected) Engine 51<br />

from <strong>Station</strong> 1 and Rescue ladder<br />

from <strong>Station</strong> 6<br />

Engine and Tanker 5 New <strong>Station</strong> (projected) Engine from<br />

<strong>Station</strong> 6 and Tanker from <strong>Station</strong> 21<br />

Engine and Brush Truck 4 New <strong>Station</strong> (projected) Engine from<br />

<strong>Station</strong> 4<br />

Engine 4 New <strong>Station</strong> (proposed)<br />

Engine 4 New <strong>Station</strong> (proposed)<br />

FIRE PREVENTION<br />

The Prevention Services Bureau is led by a deputy chief and is subdivided into <strong>Fire</strong><br />

Investigation, Code Enforcement and Public Education sections. A Battalion Chief leads each<br />

section <strong>of</strong> the Bureau. There are a total <strong>of</strong> 37 people assigned to the Prevention Services Bureau<br />

all <strong>of</strong> them are captains, majors or chief <strong>of</strong>ficers. Thirteen positions are assigned to Public<br />

Education, a significant number and this commitment public fire safety is one <strong>of</strong> the strengths <strong>of</strong><br />

the department.<br />

TriData, a Division <strong>of</strong> 98<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

The <strong>Fire</strong> Prevention Services have an extensive emergency-planning program for<br />

business. A comprehensive smoke alarm program is another major program <strong>of</strong> this <strong>of</strong>fice. A fire<br />

safety trailer is another form <strong>of</strong> outreach from <strong>Fire</strong> Prevention.<br />

One <strong>of</strong> the goals <strong>of</strong> department is to reduce the fire fatality rate in to below the national<br />

average. The current rate is four deaths per 100,000 population. In the Fiscal Year 04-05, there<br />

were 24 fire fatalities in the city. 43[1]<br />

The Operations Division performs limited building inspections on existing commercial,<br />

public assembly and other target hazards. These inspections are recorded on a single page form.<br />

These inspections are conducted on an in-service basis, i.e. the company remains available for<br />

dispatch to emergency responses. These inspections are for routine fire code compliance. Items<br />

such as exit signage, exit access, and fire extinguisher maintenance are evaluated. More technical<br />

aspects such as the adequacy <strong>of</strong> sprinkler coverage or effectiveness <strong>of</strong> separations are referred to<br />

the <strong>Fire</strong> Prevention Office. The intent <strong>of</strong> this plan is for each business to be inspected by<br />

suppression companies once in a three year time span. Other high-risk occupancies such as<br />

hospitals and nursing homes are inspected once a year.<br />

OPPORTUNITIES FOR REGIONAL COOPERATION<br />

There are at least 18 small municipalities or unincorporated areas that operate within or<br />

near the city borders. Their characteristics are summarized in Table 34 and Table 35. The<br />

histories <strong>of</strong> these cities vary but many incorporated as a way to separate from the “big city.”<br />

These communities serve populations between 2,400 and 54,000 and provide a variety <strong>of</strong><br />

services. Thirteen communities provide fire protection and EMS first response, two do not<br />

operate fire departments and three unincorporated areas receive fire and EMS services from the<br />

<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department.<br />

Regionalization <strong>of</strong> fire and EMS service was discussed by as recently as September <strong>of</strong><br />

2005. An overview revealed that regionalization would yield savings to taxpayers. Increased<br />

efficiency was not directly studied but based on an economy <strong>of</strong> scale, an increase is likely. The<br />

mayor and some council members strongly support efforts at regionalization.<br />

Several small communities have realized the advantages <strong>of</strong> consolidating fire and EMS<br />

services with larger departments. They realized that these smaller departments were costly,<br />

provided service duplication and served as starting points for employees to gain experience until<br />

they could achieve employment with a larger, better paying department. Other areas realized that<br />

their volunteer fire and EMS service could not keep up with response and training demands.<br />

43[1] <strong>Oklahoma</strong> <strong>City</strong> Budget for FY 2005-2006 page 253<br />

TriData, a Division <strong>of</strong> 99<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Recently, the city discussed the consolidation <strong>of</strong> the Bethany <strong>Fire</strong> Department (also<br />

serving Woodlawn Park) with the OKCFD. This consideration was short-lived as Bethany FD<br />

employees led a successful grassroots effort to derail the merger. A different approach may yield<br />

better outcomes. This approach includes a joint management/labor work group involving both<br />

cities followed by a joint effort at citizen mobilization. Internal efforts should focus on Bethany<br />

personnel being absorbed into the department without the loss <strong>of</strong> pay, rank or seniority.<br />

Community outreach should stress the advantages <strong>of</strong> being served by a larger municipal fire<br />

department.<br />

Currently, the city provides services to the city <strong>of</strong> Valleybrook and the unincorporated<br />

areas <strong>of</strong> Lake Aluma, Sportsman’s Club and Stockyards, all <strong>of</strong> which are within city limits.<br />

Bethany (and Woodlawn Park), Warr Acres, The Village, Nichols Hills, Forrest Park and<br />

Mustang are contained within the OKC city limits and provide their own fire and EMS<br />

protection (Table 34).<br />

Table 34: <strong>Fire</strong> Departments with OKC <strong>City</strong> Limits<br />

Department Population <strong>Fire</strong> Personnel<br />

Annual Personnel<br />

Costs<br />

Bethany 20,300 25 $1,296,000<br />

Warr Acres 9551 17 $828,000<br />

The Village 10,000 17 $840,000<br />

Nichols Hills 4,020 14 $1,009,092<br />

Forrest Park 1,100 Volunteer ?<br />

Mustang 10,500 11 Career/<br />

25 Volunteer<br />

$963,611<br />

Dell <strong>City</strong>, Midwest <strong>City</strong>, Spencer, Moore, Jones, and Yukon border OKC and provide<br />

their own fire and EMS services (Table 35).<br />

Table 35: <strong>Fire</strong> Departments Bordering OKC<br />

Department Population <strong>Fire</strong> Personnel<br />

Annual Personnel<br />

Costs<br />

Dell <strong>City</strong> 22,000 26 $1,128,000<br />

Midwest <strong>City</strong> 54,000 89 $4,908,000<br />

Spencer 4,000 7 $180,000<br />

Moore 41,000 54 $3,144,000<br />

Jones 2,611 Part-Time/Volunteer $6,108<br />

Yukon 21,000 12 $470,000<br />

The current eight-minute response maps shown in Figure 24 indicate that OCFD could<br />

cover all or some <strong>of</strong> these cities with the response pr<strong>of</strong>ile.<br />

Total Coverage – Bethany, Warr Acres, The Village, Nichols Hill, Forrest Park<br />

TriData, a Division <strong>of</strong> 100<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

IV. <strong>Station</strong> and Apparatus Deployment<br />

Partial Coverage – Dell <strong>City</strong> (70 percent), Midwest <strong>City</strong> (15 percent), Jones (30<br />

percent), and Mustang (20 percent)<br />

Planned additional <strong>Oklahoma</strong> <strong>City</strong> stations will further increase this coverage. This data<br />

does not include coverage if OCFD would incorporate the city’s stations and personnel.<br />

There are many variables including social, technological, economic, environmental and<br />

political that affect the decision to pursue full or partial merger. Any attempts to accomplish this<br />

should be based on a plan involving the cities, the departments, the communities, fire department<br />

leadership and labor organizations. A full discussion <strong>of</strong> these opportunities is beyond the scope<br />

<strong>of</strong> this report.<br />

Recommendation 17: Formally consider the strengths and weaknesses <strong>of</strong> incorporating<br />

smaller departments, in and near the city limits, into the department. This should include<br />

personnel, stations, apparatus, communications centers and other assets. Our study suggests that<br />

there are duplications <strong>of</strong> coverage and there is potential for economy <strong>of</strong> scale if OKCFD<br />

provides service to several <strong>of</strong> theses communities.<br />

TriData, a Division <strong>of</strong> 101<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. EMERGENCY MEDICAL SERVICES<br />

TriData was asked to evaluate several components <strong>of</strong> the Emergency Medical Services<br />

system including: (a) the fire department’s role in EMS, (b) suggested station locations for EMS<br />

transport units, (c) ability to house EMS units and personnel. We examined both quantitative and<br />

qualitative issues by involving stakeholders throughout the department.<br />

OVERVIEW<br />

Emergency Medical Services (EMS) is provided by two agencies, the <strong>Oklahoma</strong> <strong>City</strong><br />

<strong>Fire</strong> Department (OCFD) and EMSA, a “public trust” agency that oversees the provision <strong>of</strong> EMS<br />

care and transportation to the city.<br />

<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department – The OCFD provides first responder EMS from 36<br />

fire stations, with 20 engine companies able to provide advanced life support care with the rest<br />

providing basic life support. Each ALS engine responds with at least one paramedic and three<br />

EMT-Bs, while BLS suppression units respond with at least three EMT-Bs. The 20 paramedic<br />

engines are assigned to the higher call volume areas.<br />

OCFD first response units are dispatched from a newly opened city public safety<br />

communications center. Calls are received by a 911 police communications operator who<br />

transmits requests for EMS to an EMSA operator. Using the Clawson Medical Priority Dispatch<br />

(MPD) program, certain emergencies are forwarded to fire dispatch for assignment <strong>of</strong> a first<br />

responder unit. There is a mechanism for immediate, simultaneous routing <strong>of</strong> emergencies to<br />

EMSA and fire dispatch but it is not always used.<br />

The fire department and EMSA have acknowledged that there are instances where the<br />

first responder requests from EMSA to the fire department were delayed. This could create a lifethreatening<br />

situation. A change in dispatching methods could alleviate the situation. Switching<br />

MPD to the PSAP 911 operator will result in rapid, simultaneous forwarding <strong>of</strong> emergencies to<br />

the appropriate agency. Recent research supports this to decrease dispatch times. 44<br />

Recommendation 18: Move the MPD function to the PSAP 911 operators. This will<br />

result in quicker relaying <strong>of</strong> calls to all appropriate dispatch functions.<br />

Emergency Medical Services Authority (EMSA) – The Emergency Medical Services<br />

Authority (EMSA) was established in Tulsa in 1977 to provide high quality ambulance service,<br />

to acquire and maintain physical properties, to charge and collect user fees, to oversee operations<br />

and to fulfill administrative duties on behalf <strong>of</strong> the communities it represents.<br />

44 Jameson, A. (2006). Differences in EMS Response Time Based Upon Dispatch Procedure. Presented at the 2006<br />

Society <strong>of</strong> Academic Emergency Medicine Annual Meeting (May 18-21, 2006). San Francisco, CA.<br />

TriData, a Division <strong>of</strong> 102<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department V. Emergency Medical Services<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 25: Paramedic Engine <strong>Station</strong> <strong>Location</strong>s (and their four to six minute coverage areas)<br />

TriData, a Division <strong>of</strong> 103<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

EMSA was invited to extend its role into <strong>Oklahoma</strong> <strong>City</strong> in 1990. The EMSA service<br />

area is currently divided into the Western and Eastern Divisions. The Western Division includes<br />

<strong>Oklahoma</strong> <strong>City</strong>, Edmond, Valley Brook, and Lake Aluma. The Eastern Division comprises<br />

Tulsa, Bixby, Sand Springs, and Jenks.<br />

The Authority administers the system, manages contractual agreements, maintains patient<br />

records, handles billing and collections, purchases goods and services, markets the ambulance<br />

service, deals with financial matters and makes policy recommendations to the Board <strong>of</strong><br />

Trustees. A competitive process is utilized every five years to select a private contractor to staff<br />

the ambulances. Paramedics Plus is the current holder <strong>of</strong> the contract to provide emergency<br />

medical services and dispatch personnel, and to oversee operations. This arrangement provides<br />

the communities control <strong>of</strong> the system and equipment while receiving the benefits <strong>of</strong> competitive<br />

bidding. 45<br />

EMSA is required to respond to 90 percent <strong>of</strong> emergency calls within 8:59 in the city’s<br />

core and 12:59 in the rural zones. A minimum <strong>of</strong> seven advanced life support units must be inservice.<br />

To meet peak demand, up to 12 units are placed in service. Each ALS unit is staffed by<br />

at least one EMT-P and one EMT-B.<br />

EMSA is managed by a staff hired by the authority to oversee operations and<br />

administration. Medical direction is provided by Dr. John Sacra, an emergency physician who<br />

oversees EMSA’s OKC and Tulsa operations and serves as medical director <strong>of</strong> OCFD.<br />

Paramedics Plus – Paramedics Plus is a private entity owned by the East Texas Medical<br />

Center in Tyler, TX. Paramedics Plus provides emergency services, personnel and equipment<br />

based on a community’s specific needs. Currently Paramedics Plus serves Tulsa and <strong>Oklahoma</strong><br />

<strong>City</strong> through Emergency Medical Services Authority (EMSA), the exclusive emergency medical<br />

services provider for more than 1.1 million people in Central and Northeast <strong>Oklahoma</strong>. They<br />

have 62 ambulances, and handle 72,580 transports annually in <strong>Oklahoma</strong>.<br />

Paramedics Plus provides qualified personnel to EMSA and is responsible for salary,<br />

benefits and all other remuneration to employees. Personnel working in Tulsa or OKC are hired<br />

using a cooperative process between Paramedics Plus and EMSA.<br />

Challenges – Several EMS challenges were identified by the fire chief and other<br />

members. These items appeared consistent throughout the department.<br />

The initial ALS plan included upgrading all engine companies to advanced life support<br />

level. Starting in 1997, 20 companies have been upgraded, but staffing challenges have<br />

prohibited expansion. There are 21 members who have expressed a desire to attend paramedic<br />

training but staffing to backfill positions is unavailable.<br />

45 <strong>City</strong> Manager. (2001). <strong>City</strong> Manager’s Report (August 28, 2001). <strong>Oklahoma</strong> <strong>City</strong>, OK, 2.<br />

TriData, a Division <strong>of</strong> 104<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

In October, 2006, the city will determine if the contract with EMSA and Paramedics Plus<br />

will be renewed. There is a window <strong>of</strong> opportunity for the fire department to take a greater EMS<br />

role. The continuing question is “what role should the OCFD have in EMS delivery?”<br />

EMSA receives a $4.0 million annual subsidy from the city. They also collect fees on a<br />

per call basis and have a subscription option for citizens to avoid co-payments. The fire<br />

department provides first responders that are not reimbursed by either cash or credit for in-kind<br />

services.<br />

It is difficult for the fire department to recruit trained paramedics. Attempts at nationwide<br />

recruiting yielded disappointing results.<br />

Medical Direction – TriData conducted an extensive interview with EMSA’s medical<br />

director, Dr. John Sacra. Dr. Sacra is the full-time medical director for both EMSA locations, but<br />

is independent from the EMSA authority. He is appointed by a joint medical control board<br />

comprised <strong>of</strong> representatives from all stakeholder organizations. Although his paycheck is from<br />

EMSA, the funding is from all sources.<br />

Dr. Sacra believes that the current EMS system is excellent, citing that OKC has the third<br />

highest cardiac arrest save rate in the country. He believes that OCFD and EMSA’s use <strong>of</strong><br />

identical protocols, common equipment and joint medical direction has led to this success.<br />

Another basis for success is the integrated continuous quality improvement (CQI)<br />

program. All transport units collect electronic patient care data that allows for 100 percent<br />

review <strong>of</strong> EMS reports to assure protocol compliance. EMSA uses Physio-Control’s<br />

Medusa/Lifenet EMS s<strong>of</strong>tware for electronic data collection. He is concerned that the fire<br />

department will choose a different s<strong>of</strong>tware program, thereby compromising data sharing and<br />

data integration. We noted that the fire department has other data needs as well, especially<br />

fulfillment <strong>of</strong> the NFIRS reporting requirements.<br />

Recommendation 19: The OCFD should choose a reporting s<strong>of</strong>tware package that is<br />

able to manipulate data in a manner that makes it compatible with EMSA’s s<strong>of</strong>tware.<br />

Dr. Sacra mentioned that the medical director was not included on the OCFD command<br />

chart. The medical director is part <strong>of</strong> the EMS leadership team in all provider organizations. To<br />

recognize this distinction, the medical director should be acknowledged as a key staff member.<br />

Recommendation 20: The OCFD should consider formally recognizing the medical<br />

director as a member <strong>of</strong> the FD command staff. This could be done without any change in<br />

duties or compensation.<br />

Dr. Sacra also remarked on the role <strong>of</strong> the fire department in EMS. He fully supports the<br />

first responder role and further recommends that the outlying engine companies become ALS<br />

engines.<br />

TriData, a Division <strong>of</strong> 105<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

Placing ALS capabilities in outlying areas is not an immediate priority. At this time, so<br />

few calls are generated in these outlying areas, placing units there that they may serve little<br />

purpose. The outlying stations should be upgraded as demand levels increase. At this point,<br />

EMSA stands to gain most from this upgrade as they are under less pressure to respond quickly<br />

to outlying areas. Our interview with Councilman (and former OKC fire chief) Gary Marr<br />

revealed that for every minute increase in EMSA’s mean response time, they save on average<br />

$1M in costs.<br />

Dr. Sacra is concerned with skill pr<strong>of</strong>iciency levels <strong>of</strong> ALS providers. Training too many<br />

paramedics will lead to skill decay based on numbers <strong>of</strong> emergency responses. This is <strong>of</strong> concern<br />

to many medical directors and warrants consideration. TriData examined OCFD skill pr<strong>of</strong>iciency<br />

by examining three variables: endotracheal intubation success rates, IV success rates and IO<br />

success rates. These rates were compared to other EMS jurisdictions throughout the country.<br />

Table 36 shows the results.<br />

Procedure<br />

Table 36: EMS Skill Pr<strong>of</strong>iciency for OCFD<br />

Attempts<br />

Attempts<br />

Successful<br />

Attempts<br />

Unsuccessful<br />

Percent<br />

Attempts<br />

Successful<br />

IV 4045 3259 776 81%<br />

Endotracheal Intubation (ET) 281 231 50 82%<br />

IO 3 2 1 67%<br />

OCFD’s ET success rate is slightly lower than other EMS systems. One reason may be<br />

that OCFD paramedics <strong>of</strong>ten can only make one intubation attempt before arrival <strong>of</strong> EMSA.<br />

EMSA’s pr<strong>of</strong>iciency data was not accessible.<br />

rates are another skill that can be evaluated. OCFD’s IV Therapy success rate is 81<br />

percent which is comparable to other EMS agencies. For example, our recent study <strong>of</strong> Portland,<br />

OR FD revealed a success rate <strong>of</strong> 75 percent. Comparing success rates revealed that OCFD’s had<br />

a higher success rate.<br />

A comparison <strong>of</strong> pr<strong>of</strong>iciency between OCFD and other jurisdictions in ET Intubation is<br />

shown in Table 37.<br />

TriData, a Division <strong>of</strong> 106<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

Table 37: ET Intubation Comparisons<br />

Source Attempts Success % Success<br />

Nova Scotia 46 112 103 94.3%<br />

Cady, C & Pirrallo, R. 47 2144 1969 91.6%<br />

Colwell, C.B., Et.al. 48 124 120 96.7%<br />

Garza, Et. al. 49 1066 909 85.3%<br />

Wang, Et al. 50 783 680 86.8%<br />

Deakin, Et. al. 51 52 35 71.2%<br />

Gerich, Et. al. 52 383 373 97.4%<br />

McGuire, Et. al. 53 263 223 84.8%<br />

El Dorado County EMS 54 63 57 90.0%<br />

Overall 4990 4469 88.68%<br />

<strong>Oklahoma</strong> <strong>City</strong> FD 281 251 82.0%<br />

(p


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

<strong>Station</strong><br />

Table 38: <strong>Station</strong> and Personnel Facilities<br />

Room For<br />

Medic Unit<br />

Personnel<br />

Facilities<br />

General Condition<br />

30-E, RL, DC No No Good No<br />

34-PE, RL, T Yes Yes Good Yes<br />

32-E,B Yes No Good No<br />

3-E, B Yes Yes OK-Back-in only, standing<br />

water<br />

15-PE,RL, B No Yes OK-Drainage Issues No<br />

37-E, B, T Yes Yes Good Yes<br />

21-PE, B (unstaffed) Yes No Poor-Many issues, beyond<br />

renovation<br />

19-PE, AU Yes Yes Fair-Water issues, copper<br />

piping, others<br />

25-PE, T, B, BC Yes No Fair No<br />

9-PE, LR No No Good No<br />

35-E, B, LR Yes Yes Good Yes<br />

2- E , B Yes Yes Good Yes<br />

11-E & Command Unit Yes Yes Good needs cosmetic<br />

repairs<br />

12-E. Reserve B, light<br />

Tower<br />

18-E, RL, DC, Reserve B,<br />

foam trailer<br />

22-E, RL, Turnpike Rescue<br />

Vehicle<br />

Fully Medic<br />

Ready<br />

Yes<br />

No<br />

Yes<br />

Yes<br />

Yes Yes Good Yes<br />

Yes Yes Shared complex with the Yes<br />

Police Dept.<br />

Yes Yes Good Yes<br />

27-E, T, B No No Good No<br />

20-E, B Yes Yes Good Yes<br />

31-PE,RL, DC Yes Yes Good but limited parking Yes<br />

33-E, T, B Yes Yes Good Yes<br />

14-E, RL Yes Yes Good Yes<br />

17-PE Yes Yes Original construction date Yes<br />

not reported<br />

24-PE,light tower Yes Yes Good Yes<br />

2-E, RL, R Rescue, Air unit, Yes Yes Good Yes<br />

EMS Supervisor DC<br />

1- 2 E, RL, AU, EMS No Yes No<br />

Supervisor, DC Reserve<br />

Apparatus<br />

4-E, B No Yes Size is very restrictive No<br />

5-E, Haz-Mat & reserve No Yes Good No<br />

hazmat<br />

6-E, RL No Yes No drive through bays, No<br />

building condition poor<br />

8-E, Rescue Dive Rescue<br />

Boat<br />

Yes Yes Good Yes<br />

TriData, a Division <strong>of</strong> 108<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

<strong>Station</strong><br />

Room For<br />

Medic Unit<br />

Personnel<br />

Facilities<br />

General Condition<br />

10-E No No Fair No<br />

7-E, RL, DC No No No drive through bays No<br />

13-E, B Yes Yes Small bunkroom Yes<br />

16-E, RL, Yes Yes Good Yes<br />

23-E, B Yes No Good No<br />

28-E, B Yes No Company must use bottled<br />

water<br />

36-E,B , T Yes Yes Good Yes<br />

Fully Medic<br />

Ready<br />

No<br />

OCFD and EMS Transportation – Without an intense evaluation process, (which was<br />

beyond the scope <strong>of</strong> this study) it is impossible to determine whether it would be beneficial for<br />

the fire department to take over all aspects <strong>of</strong> EMS. It is readily apparent that OCFD’s first<br />

responder ALS program is a major contributor to excellent EMS care. Recent studies have<br />

determined that <strong>Oklahoma</strong> <strong>City</strong> has one <strong>of</strong> the highest rates <strong>of</strong> successful resuscitation from out<strong>of</strong>-hospital<br />

cardiac arrest. 55<br />

If necessary, the OCFD could house an EMS transport unit and board crews at 24<br />

stations. Figure 26 shows the suggested locations <strong>of</strong> EMS transport units and shows the sixminute<br />

and eight-minute projected response times from these stations. This map excludes<br />

<strong>Station</strong>s 4 and 6 and adds the proposed northeast (A) and southwest (B) stations (as<br />

recommended in an earlier chapter.<br />

During our meeting with IAFF Local 157 President Mike Anderson, we discussed the<br />

cultural change that would occur if the fire department started providing EMS transportation. All<br />

personnel would be part <strong>of</strong> the system. It appeared that labor <strong>of</strong>ficials were ready to accept this<br />

responsibility. Responses from field personnel were mixed. Most understood the need to be<br />

involved with EMS, but providing full service needed more consideration.<br />

Contingency Plan – Whenever a municipal agency depends on private contractors to<br />

provide public safety, it is reasonable and prudent to have a contingency plan to cover<br />

unexpected lapses or termination <strong>of</strong> services. This is equally important to CBRNE types <strong>of</strong> plans<br />

since a sudden loss <strong>of</strong> EMS transport services are equivalent to industrial sabotage. The chances<br />

<strong>of</strong> this scenario are as likely as the chances <strong>of</strong> a terrorist incident.<br />

55 Sayre, M.R., Hallstrom, A., R. Rea, T. D., et al. (2006). Cardiac arrest survival rates depend on paramedic<br />

experience [ABS]. Academic Emergency Medicine, 13(5), supplement 1, 55-56.<br />

TriData, a Division <strong>of</strong> 109<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department V. Emergency Medical Services<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 26: <strong>Location</strong>s for EMS Transport Units<br />

TriData, a Division <strong>of</strong> 110<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

V. Emergency Medical Services<br />

We were unable to find evidence <strong>of</strong> a formal contingency or fail-safe plan for EMS<br />

service should the above occur. <strong>Oklahoma</strong> <strong>City</strong> went through a recent scare, when Paramedics<br />

Plus was threatened with an employee job action. The matter was resolved without service<br />

interruption, but this scare should emphasize the need for a contingency plan.<br />

Recommendation 21: The OCFD, EMSA, and <strong>Oklahoma</strong> <strong>City</strong> Emergency<br />

Management should create or update EMS contingency plans for disruption <strong>of</strong> service<br />

secondary to contractor default. Consider making this plan an annex to the OKC Emergency<br />

Plan.<br />

Observations – The OCFD has 21 <strong>Fire</strong>fighter EMT-Bs interested in obtaining<br />

paramedic certification. The department has the finances and education resources but lack the<br />

staffing to backfill for these positions. There are currently 18 persons assigned as drivers fro the<br />

district/battalion chiefs. By assigning these personnel back to engine or truck companies, backfill<br />

would be available. Eighteen new paramedics would allow 3 or 4 engine companies to upgrade<br />

to paramedic engine level.<br />

Recommendation 22: Consider temporarily reassigning the district/battalion chief<br />

administrative assistants (DAA’s) to engine or truck companies and detail as many as possible<br />

to paramedic training. This reassignment could be temporary until all engine companies are<br />

upgraded to paramedic engine.<br />

When determining which Engine companies to first upgrade, we used the number <strong>of</strong> total<br />

calls, the number <strong>of</strong> medical responses and the number <strong>of</strong> medical responses where patient<br />

contact occurred.<br />

Based on these variables, we recommend that Engines 3, 33, 35, 13 and 37 be upgraded<br />

respectively.<br />

Recommendation 23: After training additional paramedics, upgrade Engines 3, 33, 35,<br />

13 and 37 respectively. As additional paramedics are available the remaining stations can be<br />

upgraded. An alternative is to equip the remaining companies with ALS equipment and upgrade<br />

them as personnel are available.<br />

Recommendation 24: Continue the goal <strong>of</strong> upgrading all engine companies to<br />

paramedic engines. All new engine companies should be staffed as Paramedic Engines.<br />

Figure 27 is an illustration <strong>of</strong> the proposed Paramedic Engine Company locations.<br />

TriData, a Division <strong>of</strong> 111<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department V. Emergency Medical Services<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 27: Paramedic Engine Company <strong>Location</strong>s<br />

TriData, a Division <strong>of</strong> 112<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

APPENDIX A: SUMMARY OF RECOMMENDATIONS<br />

Number Recommendation Page<br />

1 The city should continue to monitor age demographics. 21<br />

2 Monitor yearly per capita demand by category and analyze data every five 24<br />

years.<br />

3 Continue tracking vertical response times and expand the program to<br />

include all call types.<br />

37<br />

4 Reconsider the use <strong>of</strong> AVL in front-line units. As units spend more time on<br />

EMS and other types <strong>of</strong> calls, they are more likely to be in the field when a<br />

second call comes in, which increases the utility <strong>of</strong> AVL.<br />

5 Adopt the response time goals listed above in Table 11. These are response<br />

time goals and would comply with NFPA standards.<br />

6 <strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department should consider reducing the weight <strong>of</strong><br />

response (number <strong>of</strong> and types <strong>of</strong> units) that respond to medium and low<br />

hazard alarms.<br />

7 Review the call processing and dispatch process to determine whether any<br />

changes can be made to improve call processing and dispatch times.<br />

8 Priority #1 –Construct a new fire station at the intersection <strong>of</strong> Reno Avenue<br />

and Lincoln Avenue in the “Bricktown” district.<br />

9 Priority #2 – Relocate <strong>Station</strong> 6 from is current location to a location on the<br />

Northwest corner <strong>of</strong> Henney and Memorial Streets. Redeploy the Tanker<br />

from <strong>Station</strong> 21 to the new <strong>Station</strong> 6<br />

10 When funding the construction <strong>of</strong> the new <strong>Station</strong> 6 provide emergency<br />

vehicle access to the Turnpike for units from the new station.<br />

11 Priority #3 – Relocate <strong>Station</strong> 4 from its current location to a location on the 84<br />

Northwest corner <strong>of</strong> Council and 104 th Street.<br />

12 Priority #4 – Construct and deploy a new Paramedic Engine Company in 85<br />

the area <strong>of</strong> Richland and 59 th Street.<br />

13 Priority #5 – Construct and deploy a new Paramedic Engine Company and 85<br />

Tanker at Douglas and 149 th Street.<br />

14 Place a new rescue ladder company at <strong>Station</strong> 28. 87<br />

15 Move the rescue ladder from <strong>Station</strong> 31 to <strong>Station</strong> 20. 87<br />

16 Move District Chief 602 from <strong>Station</strong> 18 to <strong>Station</strong> 2.and Move District 90<br />

Chief 603 from <strong>Station</strong> 7 to <strong>Station</strong> 23<br />

17 The OCFD should formally consider the strengths and weaknesses <strong>of</strong><br />

incorporating smaller departments, in and near the city limits, into the<br />

department.<br />

101<br />

18 Move the MPD function to the PSAP 911 operators. 102<br />

19 The OCFD should choose a reporting s<strong>of</strong>tware package that is able to 105<br />

manipulate data in a manner that makes it compatible with EMSA’s<br />

43<br />

44<br />

59<br />

70<br />

82<br />

803<br />

84<br />

TriData, a Division <strong>of</strong> 113<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Appendix A<br />

Number Recommendation Page<br />

s<strong>of</strong>tware.<br />

20 The OCFD should consider formally recognizing Dr. Sacra as a member <strong>of</strong><br />

the OCFD Command staff.<br />

105<br />

21 The OCFD, EMSA and <strong>Oklahoma</strong> <strong>City</strong> Emergency Management should 111<br />

create or update EMS contingency plans for disruption <strong>of</strong> service secondary<br />

to contractor default. Consider making this plan an annex to the OKC<br />

Emergency Plan.<br />

22 Consider reassigning the district/battalion chief drivers to engine or truck 111<br />

companies and detail as many as possible to paramedic training.<br />

23 After training additional paramedics, upgrade Engines 3, 33, 35, 13 and 37 111<br />

respectively.<br />

24 Continue the goal <strong>of</strong> upgrading all engine companies to paramedic engines. 113<br />

TriData, a Division <strong>of</strong> 114<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

APPENDIX B: CAPITAL RECOMMENDATIONS BY BUDGET YEAR<br />

Budget<br />

Year Number Recommendation Page<br />

FY 2008 8 Priority #1 –Construct a new fire station at the intersection <strong>of</strong> Reno Avenue<br />

and Lincoln Avenue in the “Bricktown” district.<br />

80<br />

FY 2008 9 Priority #2 – Relocate <strong>Station</strong> 6 from is current location to a location on the<br />

Northwest corner <strong>of</strong> Henney and Memorial Streets. Redeploy the Tanker<br />

from <strong>Station</strong> 21 to the new <strong>Station</strong> 6<br />

FY 2009 11 Priority #3 – Relocate <strong>Station</strong> 4 from its current location to a location on<br />

the Northwest corner <strong>of</strong> Council and 104 th Street.<br />

81<br />

85<br />

FY 2010 14 Deploy a new Rescue ladder Company at <strong>Station</strong> 28. 87<br />

FY 2011 12 Priority #4 – Construct and deploy a new Paramedic Engine Company in<br />

the area <strong>of</strong> Richland and 59 th Street<br />

FY 2013 13 Priority #5 – Construct and deploy a new Paramedic Engine Company and<br />

Tanker at Douglas and 149 th Street.<br />

85<br />

85<br />

TriData, a Division <strong>of</strong> 115<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

APPENDIX C: REPORT MAPS<br />

Figure 1: Current <strong>Fire</strong> <strong>Station</strong>s ................................................................................................... 117<br />

Figure 2: <strong>Fire</strong> Districts................................................................................................................ 118<br />

Figure 3: Current 4 Minute Travel.............................................................................................. 119<br />

Figure 4: District 601 4 Minute Travel....................................................................................... 120<br />

Figure 5: District 602 4 Minute Travel....................................................................................... 121<br />

Figure 6: District 603 4 Minute Travel....................................................................................... 122<br />

Figure 7: District 604 4 Minute Travel....................................................................................... 123<br />

Figure 8: District 605 4 Minute Travel....................................................................................... 124<br />

Figure 9: District 606 4 Minute Travel....................................................................................... 125<br />

Figure 10: Current Rescue Ladder <strong>Location</strong> And 8 Minute Travel............................................ 126<br />

Figure 11: District 601 8 Minute Travel..................................................................................... 127<br />

Figure 12: District 602 8 Minute Travel..................................................................................... 128<br />

Figure 13: District 603 8 Minute Travel..................................................................................... 129<br />

Figure 14: District 604 8 Minute Travel..................................................................................... 130<br />

Figure 15: District 605 8 Minute Travel..................................................................................... 131<br />

Figure 16: District 606 8 Minute Travel..................................................................................... 132<br />

Figure 17: Proposed 4 Minute Travel ......................................................................................... 133<br />

Figure 18: Proposed District 601 4 Minute Travel ..................................................................... 134<br />

Figure 19: Proposed District 602 4 Minute Travel ..................................................................... 135<br />

Figure 20: Proposed District 603 4 Minute Travel ..................................................................... 136<br />

Figure 21: Proposed District 604 4 Minute Travel ..................................................................... 137<br />

Figure 22: Proposed District 605 4 Minute Travel ..................................................................... 138<br />

Figure 23: Proposed District 606 4 Minute Travel ..................................................................... 139<br />

Figure 24: Proposed Ladder Rescue <strong>Location</strong> And 8 Minute Travel ......................................... 140<br />

Figure 25: Proposed District 601 8 Minute Travel ..................................................................... 141<br />

Figure 26: Proposed District 602 8 Minute Travel ..................................................................... 142<br />

Figure 27: Proposed District 603 8 Minute Travel ..................................................................... 143<br />

Figure 28: Proposed District 604 8 Minute Travel ..................................................................... 144<br />

Figure 29: Proposed District 605 8 Minute Travel ..................................................................... 145<br />

Figure 30: Proposed District 606 8 Minute Travel ..................................................................... 146<br />

Figure 31: Proposed 4 And 8 Minute Travel .............................................................................. 147<br />

Figure 32: Current <strong>Location</strong> Of District Chiefs.......................................................................... 148<br />

Figure 33: Proposed <strong>Location</strong> Of District Chiefs ....................................................................... 149<br />

Figure 34: Current Tanker <strong>Location</strong>s.......................................................................................... 150<br />

Figure 35: Proposed Tanker <strong>Location</strong>s....................................................................................... 151<br />

Figure 36: Current <strong>Location</strong> Of Paramedic Engines................................................................... 152<br />

Figure 37: Proposed Paramedic Engine Upgrades...................................................................... 153<br />

Figure 38: <strong>Location</strong>s for EMS Transport Units .......................................................................... 154<br />

Figure 39: <strong>Location</strong> Of The New Northeast <strong>Station</strong>................................................................... 155<br />

Figure 40: Total Call Density 2005 ............................................................................................ 156<br />

Figure 41: <strong>Fire</strong> Call Density 2005 .............................................................................................. 157<br />

Figure 42: EMS Call Density 2005............................................................................................. 158<br />

Figure 43: Summary Of Changes ............................................................................................... 159<br />

TriData, a Division <strong>of</strong> 116<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 1: Current <strong>Fire</strong> <strong>Station</strong>s<br />

TriData, a Division <strong>of</strong> 117<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 2: <strong>Fire</strong> Districts<br />

TriData, a Division <strong>of</strong> 118<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 3: Current 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 119<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 4: District 601 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 120<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 5: District 602 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 121<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 6: District 603 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 122<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 7: District 604 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 123<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 8: District 605 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 124<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 9: District 606 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 125<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 10: Current Rescue Ladder <strong>Location</strong> And 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 126<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 11: District 601 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 127<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 12: District 602 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 128<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 13: District 603 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 129<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 14: District 604 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 130<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 15: District 605 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 131<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 16: District 606 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 132<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 17: Proposed 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 133<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 18: Proposed District 601 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 134<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 19: Proposed District 602 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 135<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 20: Proposed District 603 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 136<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 21: Proposed District 604 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 137<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 22: Proposed District 605 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 138<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 23: Proposed District 606 4 Minute Travel<br />

TriData, a Division <strong>of</strong> 139<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 24: Proposed Ladder Rescue <strong>Location</strong> And 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 140<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 25: Proposed District 601 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 141<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 26: Proposed District 602 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 142<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 27: Proposed District 603 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 143<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 28: Proposed District 604 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 144<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 29: Proposed District 605 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 145<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 30: Proposed District 606 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 146<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 31: Proposed 4 And 8 Minute Travel<br />

TriData, a Division <strong>of</strong> 147<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 32: Current <strong>Location</strong> Of District Chiefs<br />

TriData, a Division <strong>of</strong> 148<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 33: Proposed <strong>Location</strong> Of District Chiefs<br />

TriData, a Division <strong>of</strong> 149<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 34: Current Tanker <strong>Location</strong>s<br />

TriData, a Division <strong>of</strong> 150<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 35: Proposed Tanker <strong>Location</strong>s<br />

TriData, a Division <strong>of</strong> 151<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 36: Current <strong>Location</strong> Of Paramedic Engines<br />

TriData, a Division <strong>of</strong> 152<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 37: Proposed Paramedic Engine Upgrades<br />

TriData, a Division <strong>of</strong> 153<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 38: <strong>Location</strong>s for EMS Transport Units<br />

TriData, a Division <strong>of</strong> 154<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 39: <strong>Location</strong> Of The New Northeast <strong>Station</strong><br />

TriData, a Division <strong>of</strong> 155<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 40: Total Call Density 2005<br />

TriData, a Division <strong>of</strong> 156<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 41: <strong>Fire</strong> Call Density 2005<br />

TriData, a Division <strong>of</strong> 157<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 42: EMS Call Density 2005<br />

TriData, a Division <strong>of</strong> 158<br />

September 2006<br />

System Planning Corporation


<strong>Oklahoma</strong> <strong>City</strong> <strong>Fire</strong> Department Appendix C<br />

<strong>Fire</strong> <strong>Station</strong> <strong>Location</strong> <strong>Study</strong><br />

Figure 43: Summary Of Changes<br />

TriData, a Division <strong>of</strong> 159<br />

September 2006<br />

System Planning Corporation

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

Saved successfully!

Ooh no, something went wrong!