Laserfiche WebLink
Station Location, Apparatus, and Staffing Analysis <br />Roseville, MN <br />Typically, incident densities (i.e., the number of incidents that occur within various parts <br />of the city) are generated by geocoding their addresses/locations. However, information <br />regarding incident locations was not available in CAD data provided by the city of Roseville, <br />which precluded the examination of incident densities for this analysis. <br />Response Time Analysis <br />The first step in the deployment analysis was a review of department-wide response <br />times. Response time is the total elapsed time between an individual dialing 911 and emergency <br />service personnel arriving at the scene. Response times can be broken down into multiple <br />segments for analysis: call processing, dispatch, turnout, travel, and the overall (total) time taken <br />to arrive at the incident. <br />As noted, RFD provided twelve months of CAD data for the 2007 calendar year. In some <br />cases, there were obvious errors (e.g. the unit arrived before the call was made). They were <br />excluded from the dataset used in the analysis. In addition, outliers that were more than three <br />standard deviations from the mean were eliminated. If response times have a normal distribution, <br />99.7 percent of incidents are expected to fall within three standard deviations, and the 0.3 percent <br />of incidents that was excluded from the response time analysis likely contains errors. <br />Call Processing and Dispatch Time -Call processing time includes the time to get <br />information from the caller (i.e., call initiation) and enter it into the dispatch system record. This <br />is measured from the time the call is received to the time the call is transferred to a dispatcher. <br />Dispatch time begins when the 911 call is transferred from the call taker to a dispatcher and <br />continues until units are alerted to respond. Many jurisdictions consider call processing and <br />dispatch together as a single time segment. Data for call initiation times was not easily procured <br />by RFD, making it difficult to calculate the call processing time interval. To address this <br />challenge call processing times are extrapolated from St. Paul Minnesota Fire Department's call <br />processing times that were calculated in a previous TriData study conducted in 2005 as they <br />belong to the same dispatch center as RFD. RFD and St. Paul Minnesota Fire Department call <br />processing times are largely similar. The overall call processing times at the 90~' percentile for <br />all responding units and call types was 1 minute, 1 second and an average of 32 seconds. When <br />broken down by call type, EMS calls were processed and dispatched more quickly than fire calls, <br />meeting the recommended goal of 1 minute 90 percent of the time. Fire call processing and <br />dispatch times were slightly higher than the 1 minute goal, with 1 minute 9 seconds at the 90a' <br />percentile. Nevertheless, overall call processing and dispatch times for both types of calls are <br />extremely good. <br />System Planning Corporation 9 May 2008 <br />TriData Division <br />