Station and Apparatus Deployment

53 Pages·2006·3.41 MB·English

Portland Fire and Rescue
Service Delivery System Study
V. STATION AND APPARATUS DEPLOYMENT
This chapter discusses the deployment of fire stations and emergency response apparatus
in Portland. As discussed in the previous chapters, there are many factors that should be taken
into account when determining the appropriate number of stations, including demand for
services, population, density of demand and population, size of the jurisdiction, and desired
response times. This chapter applies these factors to the current and future situation of the
Portland Fire and Rescue (PF&R).
METHODOLOGY
Before any analysis took place, project team members gathered and reviewed information
related to properly locating fire stations, including but not limited to:
• Current station locations and building ages
• Current apparatus deployment
• Current zoning and land use and related policies
• National response time standards (see Chapter IV)
• Current PF&R response time standards (see Chapter IV)
• Current and projected population (see Chapter III)
• Current and projected demand and workload (see Chapter III)
Actual incident data for FY00 and FY05 was gathered from the computer aided dispatch
system (CAD). Data included addresses for geocoding, type of incident, units responding (FY05
only), and overall response times (FY05 only).38 Geographic information system (GIS) files used
for the analysis were provided by the city.
Due to the size of the city and differences in the areas covered, it would be difficult to
complete a thorough analysis while looking at the city as a whole. Therefore, the city was
analyzed by the PF&R response districts which are shown in Map 8. Since District 1 contains
only Station 1, Districts 1 and 2 were combined for the analysis.

38 Geocoding is a process by which the street address of an emergency incident is translated into latitude and longitude so that it can be placed onto a map.
TriData, a Division of 84 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Map 8: PF&R Districts

Travel speed was based on U.S. Census Tiger files contained in the road files provided by
the city. Tiger files contain census feature class codes (CFCC codes) that define road types and
can be used to assign estimated speed limits. Speed limits were then set at 10 miles per hour
below the typical speed limit based on road type to account for obstacles that a unit may
encounter while responding to an incident such as traffic congestion, stops, and turns. No speed
limits were set below 25 mph.
Estimated travel time for each road segment was based on the speed limits and length of
the segment. Road segments containing a traffic calming device had 4.7 seconds per device
added to the estimated travel time. The additional time was based on the average delay caused by
speed humps as recorded by PF&R in previous studies.
TriData, a Division of 85 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Station and apparatus deployment analysis was based on the goals outlined in Chapter IV,
Determining Resource Needs.
CURRENT RESPONSE TIMES
The first step in the deployment analysis is a review of department-wide response times.
As discussed in Chapter IV, response time is the total amount of time elapsing between an
individual calling 911 and emergency service personnel arriving at the scene. Response time can
be broken down into multiple segments for analysis.
Methodology – The analysis of response times included emergency incidents only. Call
processing included the first-dispatched unit from each incident. Turnout, travel, vertical, and
total response times included only engines, trucks, rescues, and the squad. These criteria were
applied to keep the analysis in line with the standards against which times are being compared.
For all time segments, the CAD data from FY05 was used. In some cases there were invalid
entries (did not have a time recorded) or obvious errors (unit arrived before the call came in) that
were excluded from the dataset. All response times are for Code 3 calls only, which are high
priority calls. Code 1 calls are lower priority calls where apparatus does not go to the incident
with lights and sirens; therefore, response times are much higher due to the apparatus traveling
with the flow of traffic. Finally, to eliminate outliers, times that were more than three standard
deviations from the median were also excluded. Three times the standard deviation was used
because assuming that the travel times had a normal distribution 99.7 percent of incidents are
expected to fall within three standard deviations.
Call Processing – Call processing time includes both call processing (taking down
necessary information) and dispatch (notifying the appropriate units). Some CAD systems track
each time segment separately; most do not. Throughout this section call processing time includes
dispatch time.
In Portland, when an individual calls 911, the call is answered and dispatched at the
Bureau of Emergency Communications (BOEC). BOEC call takes gather the necessary
information, code the call, and transfer it to the appropriate BOEC fire/EMS or police dispatcher,
who dispatches the appropriate units. All of this time is included in the call processing times
discussed below.
In FY05, call processing times for PF&R averaged 1:13 with a 90th percentile time of
1:53. Table 20 shows the 90th percentile call processing time for FY05 by type of call. EMS calls
are processed slightly slower than fire calls, but the difference is not statistically significant.
EMS call processing times are almost 30 seconds higher than PF&R’s current goal for high
priority EMS calls, while fire times are nearly one minute higher than the current goal for urgent
priority fire calls. It should be noted that the BOEC User Board sets the call processing goals;
TriData, a Division of 86 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
however, PF&R should work with the BOEC in determining how to reduce the overall call
processing times.
Table 20: PF&R Call Processing Time by Call Type
Type 80th Percentile 90th Percentile Portland Goal
EMS 01:29 01:52 01:30
Fire 01:22 01:48 01:00

Some variation can be expected by time of day to correspond with heavier or lighter call
volumes. Figure 20 depicts the variation in 90th percentile call processing time by time of day.
Despite the variation in call levels, call processing time is relatively steady throughout the day
ranging from 1:50 between 8 A.M. and 10 A.M. to 2:00 between midnight and 2 A.M.
Figure 20: 90th Percentile Call Processing Time by Time of Day, FY05
0:03:00 20.00
9TA0ivmteher aPgeer cCeanltlisle P Cear lDl Paryocessing 6.89 17.78 18.04 18.18 17.44 18.00
1
6
0:02:30 5
15. 16.00
2
1
4.
1
14.00
0:02:00
70 12.00
2.
1
5
5 8
0:01:30 9. 9.2 10.00
7
6
7. 8.00
2
3
0:01:00 6.
6.00
4.00
0:00:30
2.00
8 0 0 4 0 3 1 6 2 4 5 1
5 0 5 5 5 5 5 5 5 5 5 5
1: 2: 1: 1: 1: 1: 1: 1: 1: 1: 1: 1:
0 0 0 0 0 0 0 0 0 0 0 0
0:00:00 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0.00
Midnight- 2:00- 4:00- 6:00- 8:00- 10:00- Noon- 2:00- 4:00- 6:00- 8:00- 10:00-
1:59am 3:59am 5:59am 7:59am 9:59am 11:59am 1:59pm 3:59pm 5:59pm 7:59pm 9:59pm 11:59pm

Figure 21 depicts the variation in 90th percentile call processing time by time of day and
call type. EMS call processing times remain reasonably steady throughout the day ranging
between 1:48 and 1:57. Fire call processing times fluctuate quite a bit over the course of the day
with a nearly 30 second spike from 8 A.M. to 10 A.M. Call processing times for other calls appear
to be high, but this is likely because most of these types of calls are low priority or non-
emergency incidents; therefore, more time can be spent gathering relevant information.
TriData, a Division of 87 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Figure 21: 90th Percentile Call Processing Time by Time of Day and Call Type, FY05
0:03:00
EMS Fire Other
0:02:30
0:02:00
0:01:30
0:01:00
0:00:30
0:00:00
Midnight- 2:00- 4:00- 6:00- 8:00- 10:00- Noon- 2:00- 4:00- 6:00- 8:00- 10:00-
1:59am 3:59am 5:59am 7:59am 9:59am 11:59am 1:59pm 3:59pm 5:59pm 7:59pm 9:59pm 11:59pm

Although call processing times in Portland are higher than current and recommended
goals, they are not much out of line with those in other communities, some of examples of which
are shown in Table 21.
Table 21: Comparison of 90th Percentile Call Processing Times39
City 90th Percentile
Cincinnati, Ohio 01:03
Corpus Christi, Texas 01:39
Irving, Texas 01:44
Long Beach, California 02:39
Portland, Oregon 01:53

Recommendation 16: Review the call processing and dispatch process to determine
whether any changes can be made to improve call processing and dispatch times. Areas to
consider include staffing levels in the dispatch center, the amount of information gathered before
dispatching the first unit, and turnover rates in dispatch staff and resulting lack of experience. A
full review of the dispatch center in Portland was beyond the scope of this study; therefore,
information on staffing and turnover was not reviewed. These are common issues within dispatch

39 We had relatively recent data from other TriData studies for these communities
TriData, a Division of 88 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
centers. PF&R should work closely with the BOEC to lower the current call processing times, as
they are a critical component in overall response time.
Turnout – Turnout time is measured from when the alarm is received by personnel to
when the apparatus begins driving to the incident scene. The average turnout time in Portland in
FY05 was 1:09 with a 90th percentile time of 1:51, nearly 60 seconds higher than the
recommended time of 1:00 as discussed in Chapter IV.
When examining the turnout times by call type, the times remain similar to the overall
results. EMS, fire, and other incident turnout times are 1:48, 1:42, and 1:56 respectively, again
nearly 60 seconds over our recommended goal. Turnout times for fire and EMS are very similar
despite fires requiring the donning of protective equipment. There is also no significant
difference in 90th percentile turnout times by unit type with the times ranging from 1:50 to 2:02.
Turnout time vary considerably by time of day. Station design and personnel duties (e.g.
inspections) also play a role. Figure 22 shows turnout times by time of day during FY05. There
is significant (nearly one-minute) variation in turnout time by time of day, which can be expected
since personnel are generally asleep between midnight and 6 A.M. (when turnout times are
highest). Turnout times during the rest of the day exceed the recommended one-minute time for
turnout by around 30 seconds.
Figure 22: Turnout Times by Time of Day, FY05
0:03:00 20.00
9A0vtehr aPgeer cCeanltlisle p Teur rDnaoyut Time 6.89 17.78 18.04 18.18 17.44 18.00
1
6
0:02:30 5
15. 16.00
2
1
4.
1
14.00
0:02:00
70 12.00
2.
1
5
5 8
0:01:30 9. 9.2 10.00
7
6
7. 8.00
2
3
0:01:00 6.
6.00
4.00
0:00:30
2.00
3 9 0 1 1 9 5 8 9 5 8 1
1 1 2 1 3 2 2 2 2 2 2 5
2: 2: 2: 2: 1: 1: 1: 1: 1: 1: 1: 1:
0 0 0 0 0 0 0 0 0 0 0 0
0:00:00 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0.00
Midnight- 2:00- 4:00- 6:00- 8:00- 10:00- Noon- 2:00- 4:00- 6:00- 8:00- 10:00-
1:59am 3:59am 5:59am 7:59am 9:59am 11:59am 1:59pm 3:59pm 5:59pm 7:59pm 9:59pm 11:59pm

TriData, a Division of 89 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Finally, some units turnout faster than others. Engine 20, for example, had a 90th
percentile turnout time of 1:37 in FY05, the lowest of all engines. Engine 16, on the other hand,
had a 90th percentile turnout time of 2:07, 30 seconds longer. The reason for this is unclear;
however, a possible reason for the higher turnout times is that units in Portland are not always in
the station. Crews perform inspections and public education throughout their first-due areas. It
takes longer to turnout for a call when personnel are away from the station rather than in
quarters. The extra time to turnout may be worth the benefits and cost-savings of using crew
personnel “downtime” for prevention activities such as inspections and public education.
Of the different segments of response time (call processing, turnout, and travel) it is
easier and less costly to improve call processing and turnout times. Travel time is typically much
more difficult and the most expensive to improve (e.g., new/more stations, new roads, or traffic
signal pre-emption devices). Reducing the first two times will reduce total response times.
Reduction in call processing and turnout time also permits longer travel times without increasing
total response times; thus, stations can typically serve larger areas and still meet response time
goals. The critical time is to dispatch the first unit; further call processing can occur
simultaneously (i.e., talking more to the caller to obtain details).
Travel – Travel (drive) time is the time it takes to travel from the station, or wherever the
unit is, to the emergency incident. Station and apparatus placement has the biggest impact on
travel time. (Apparatus are not always in the station when dispatched to an incident.) Additional
factors influencing travel time include traffic, weather, traffic limiting devices (stop lights, speed
bumps, etc.), and driver familiarity with the area. It should be noted that fire apparatus stop at all
signal controlled intersections before proceeding through – a safe practice. While this will
slightly increase travel times, the tradeoff for safety may be worth the extra time. (Studies have
documented a significant number of injuries and fatalities caused by vehicular crashes involving
emergency response vehicles driving through intersections and responding en-route to an
incident). Traffic congestion and weather are beyond the department and city’s control; however,
traffic limiting devices and driver knowledge are not.
Travel times in Portland are higher than the TriData recommended 90th percentile travel
times of four minutes. In FY05, PF&R experienced an average travel time of 3:56 and a 90th
percentile time of 5:58 overall. However, the four-minute travel time is recommended for the
first arriving unit only. (The idea is that a four-minute travel time coupled with the recommended
call processing and turnout times will result in an overall six-minute total response time for the
first unit to each call.)
The 90th percentile travel time for the first arriving unit on all call types was 5:41, better
but still nearly two minutes higher than the recommend goal. When broken down by call type,
the 90th percentile travel time for first arriving unit to EMS calls was 5:39. For fire calls, the 90th
percentile travel time was 5:41. Both of these are more than two minutes higher than the
TriData, a Division of 90 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
recommended four-minute travel time. Table 22 shows the 90th percentile travel times by call
type for FY05.
Table 22: 90th Percentile Travel Time by Call Type, FY05
Response 90th Percentile 90th Percentile 80th Percentile 70th Percentile
Level (All Units) (First Arriving Unit) (First Arriving Unit) (First Arriving Unit)
EMS 05:43 05:39 04:47 04:13
Fire 08:05 05:41 04:36 03:59
Other 06:11 05:53 04:48 04:12
Overall 05:58 05:41 04:46 04:12

It is not until the 70th percentile range that the travel times fall below the four-minute
goal for travel.
In addition to varying by response level and call type, travel times vary by time of day
due to traffic and visibility. Relatively steady travel times throughout the day in Portland, as
shown in Figure 23, indicate that congestion due to rush-hour traffic is not a major problem for
PF&R.
Figure 23: 90th Percentile Travel Time by Time of Day, FY05
0:07:00 20.00
9A0vtehr aPgeer cCeanltlisle p Terra Dvaeyl Time 6.89 17.78 18.04 18.18 17.44 18.00
1
0:06:30 56
15. 16.00
2
1
4.
1
14.00
0:06:00
70 12.00
2.
1
5
5 8
0:05:30 9. 9.2 10.00
7
6
7. 8.00
2
3
0:05:00 6.
6.00
4.00
0:04:30
2.00
8 1 2 9 7 4 7 4 7 6 0 4
5 1 0 4 3 4 2 4 3 2 3 4
5: 6: 6: 5: 5: 5: 5: 5: 5: 5: 5: 5:
0 0 0 0 0 0 0 0 0 0 0 0
0:04:00 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0.00
Midnight- 2:00- 4:00- 6:00- 8:00- 10:00- Noon- 2:00- 4:00- 6:00- 8:00- 10:00-
1:59am 3:59am 5:59am 7:59am 9:59am 11:59am 1:59pm 3:59pm 5:59pm 7:59pm 9:59pm 11:59pm

TriData, a Division of 91 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Vertical – Vertical response time is the time to get from the street to the patient’s side or
fire location and includes time to dismount from vehicle, assemble equipment, and locate the
patient or fire floor. The time can be significant in areas with high-rise buildings or large
properties (e.g., malls or golf courses). Vertical response time often is not tracked by first
responders; however, PF&R does track vertical response times on many EMS calls.
On EMS calls, services cannot be provided until personnel arrive at the side of the
patient. In FY05, PF&R’s vertical response time averaged 1:44 with a 90th percentile time of
3:07. Since so few departments record vertical response times, it is not possible to compare this
to other communities.
While it is possible to reduce the other components of response time through technology
and fire station location, it is difficult to substantially and safely reduce vertical response times.
As a result, the importance of built-in fire suppression systems cannot be overstated. These
systems buy time for the firefighters to get to where they have to be within the structure to
completely extinguish fire or provide emergency care.
Total Response Time – It is important to note that, for mathematical reasons, one
cannot simply add the average or 90th percentile time components of response time to reach the
total response time. In FY05, total response times for PF&R averaged 6:12 for the first arriving
unit to all calls with a 90th percentile total response time of 8:31. When factoring in vertical
response times PF&R averaged 7:32 with a 90th percentile time of 10:15. All of these times are
well above current and recommended goals.
Table 23 shows the 90th, 80th, and 60th percentile total response times for first arriving
unit in FY05 incidents by call type. There is a nearly one minute difference in total response time
between EMS calls and fire calls at the 90th percentile level; however, that decreases at the 80th
percentile level. The total response times are over the recommended goal of six minutes at the
90th percentile level, and do not fall below six minutes until the 60th to 50th percentile level.
Table 23: FY05 60th, 80th and 90th Percentile Total Response Time by Call Type
Call Type EMS Fire
60th Percentile 06:12 06:01
80th Percentile 7:18 7:27
90th Percentile 8:16 9:00
80th Percentile with Vertical 9:03 –
90th Percentile with Vertical 10:12 –

Generally, the variation in total response time by time of day follows the same pattern as
the travel time since that is the largest component. Total response time by time of day is shown
in Figure 24.
TriData, a Division of 92 March 2006
System Planning Corporation
Portland Fire and Rescue Chapter V. Station and Apparatus Deployment
Service Delivery System Study
Actual response times in Portland are compared to NFPA standards and the study team’s
recommended goals in Table 24.
Figure 24: 90th Percentile Total Response Time by Time of Day, FY05
0:12:00 20.00
0:11:00 9A0vtehr aPgeer cCeanltlisle p Teor tDaal Ryesponse Time 6.89 17.78 18.04 18.18 17.44 18.00
1
0:10:00 56
15. 16.00
2
0:09:00 4.1
1
14.00
0:08:00
70 12.00
0:07:00 2.
1
5
5 8
0:06:00 9. 9.2 10.00
7
0:05:00 7.6 8.00
2
3
0:04:00 6.
6.00
0:03:00
4.00
0:02:00
2.00
0:01:00 3 8 2 5 4 4 1 0 1 7 9 6
1 3 1 3 0 0 4 0 0 5 5 1
9: 9: 9: 8: 8: 8: 7: 8: 8: 7: 7: 8:
0 0 0 0 0 0 0 0 0 0 0 0
0:00:00 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0.00
Midnight- 2:00- 4:00- 6:00- 8:00- 10:00- Noon- 2:00- 4:00- 6:00- 8:00- 10:00-
1:59am 3:59am 5:59am 7:59am 9:59am 11:59am 1:59pm 3:59pm 5:59pm 7:59pm 9:59pm 11:59pm

Table 24: Portland 90th Percentile Response Times, FY05 vs. Standards and Goals
Current PF&R Recommended
Current 90th Reduction Reduction
Call Type Time Segment Percentile Goal Needed Goal Needed
Call Processing: Urgent 0:01:00 0:00:48
Fire Call Processing: High 0:01:48* 0:01:30 0:00:18 0:01:00 0:00:48
Call Processing: Low 0:02:00 N/A
Call Processing: High 0:01:30 0:00:22
EMS 0:01:52* 0:01:00 0:00:52
Call Processing: Low 0:03:00 N/A
ALL Turnout 0:01:51 0:01:00 0:00:51
Travel 0:05:41 0:04:00 0:01:41
Fire
Total 0:09:00 0:05:20 0:06:00 0:03:00
Travel 0:05:39 0:04:00 0:01:39
EMS
Total 0:08:16 0:06:00 0:02:12
* The analysis did not break the call processing times into priority levels, but rather as an overall time for both EMS and Fire
calls.

TriData, a Division of 93 March 2006
System Planning Corporation