Laserfiche WebLink
<br /> <br /> <br /> <br />u <br /> <br /> <br /> <br />1 <br /> <br /> <br />1 <br /> <br />t <br />r~ <br /> <br /> <br /> <br />Station Location, Apparatus, and Staffing Analysis <br />Roseville, MN <br />Data Limitations and Assumptions <br />The RFD was only able to provide CAD data for one year due to CAD system <br />limitations. This made it difficult to analyze response time trends. In addition, RFD does not <br />keep track of call initiation (i.e. call received) time, which precluded an accurate analysis of call <br />processing times. To overcome this barrier, the average call processing times were extrapolated <br />from a previous study conducted for the St. Paul Minnesota Fire Department in 2005 as they <br />belong to the same dispatch center as RFD. The time segments provided in the CAD data only <br />took into account the hours and minutes and excluded seconds. Thus, the response times for each <br />interval could only be provided in hours and minutes in this analysis. In several instances, <br />dispatchers may have manually entered in times after responding to a call if they did not have <br />enough time to enter this data into the system initially. <br />Another challenge presented in this analysis was the lack of differentiation between non- <br />emergency and emergency calls. The RFD lacks the mechanism to parcel out which calls are <br />emergency versus non-emergency. <br />Recommendation 1: %ep track emergency versus non-emergency calls. <br />The nature of each incident was classified by RFD and broken down into three <br />categories-fire, medical or DND (did not dispatch). For DND an alarm company was used <br />when a call is generated by the communications center, but not toned out for the fire department. <br />However, RFD was unable to provide a description for the incidents listed in the CAD data. For <br />example, calls were either listed as medical, fire, or DND and no other information were <br />provided about the call (i.e., "auto alarm," "chest pain," or another type of call). <br />Recommendation 2: Provide proper call information in the CAD data. RFD has <br />acknowledged that their current records management system is inadequate and are unable to <br />provide proper call information. This issue can be appropriately addressed by the use of current <br />records management software. <br />An accurate representation of the travel time reach is generally calculated based on the <br />length of GIS road centerline segments and the posted speed limits. However, speed limits were <br />unavailable for a majority of the road centerline segments and an average speed of 41 miles per <br />hour was calculated based on 518 speed limit records available out of 1700 calls for service. <br />Traffic limiting factors such as topography, narrow roads, and congestion are typically taken into <br />consideration when calculating speed limits. However, these factors were not taken into <br />consideration as main roads and highways in Roseville constitute much of the city's roadway <br />system. <br />System Planning Corporation 8 May 2008 <br />TriData Division <br /> <br />