Best Practices: Practical Uses of FireRMS Data to Improve Your Agency's Performance Lisa M. Blouin Fire Rescue Business and Compliance Manager
Optimize your FireRMS data to perform staffing and response studies, monitor ISO (Insurance Service Organization) compliance, review fire assessment data and develop successful grant applications.
FireRMS Reporting FireRMS already contains hundreds of Reports in the Report Menus. Whereas, my previous presentation showed you how to Create and Run Ad-hoc Queries and Reports and Customize an existing FireRMS report, This presentation will provide specific examples of how FireRMS data can be used to Improve Organizational Performance.
FireRMS Data is used in many Critical Departmental Activities including: ISO Compliance - Training, Premise, Inspections, Hydrants Fire Assessment Fee/Fire Inspection Fees NFIRS Compliance Staffing Studies Grant Requests - ALS Rescue, Lifepaks, Hazmat Monitors, Engine Refurb, Hydraulic Stretchers, PPE, Extrication Equipment, etc. Mutual Aid/Automatic Aid Reporting Unit Response/Deployment Analysis Incident Analysis Medicaid Reimbursement Programs Impact Studies (Developments, Traffic Cones, etc.)
Monitor ISO (Insurance Service Organization) compliance
Example 1: Finding training record discrepancies that need to be corrected in your FireRMS database
Example 2: ISO Training Report Detail
Example 3: ISO Training Summary Report {ISOTrainingExtract.sesstart} in DateTime (2014, 01, 31, 00, 00, 00) to DateTime (2015, 01, 31, 00, 00, 00) and not ({ISOTrainingExtract.lastname} in ["", "", " 2/2/2015
Example 4: Premise Reports and Annual Inspections
Example 5: Hydrant Maintenance Reports
Using custom tables in Access to further analyze your FireRMS data for your Fire Assessment Studies
Example 6: Table of custom groups based on incident type to identify Non-EMS Incidents.
Example 7:Table of Initial Dispatch Codes to identify origination of Cancelled en-route or false calls
Example 8:Table of Fixed Property Use Codes to identify Property Classifications
Using FireRMS data to develop successful grant applications and perform response studies.
Screenshot of Assistance to Firefighter grant (AFG) grouping.
Example 9: Table of custom groups based on grant group type.
Example 10: Using FireRMS Unit Response data identified additional units were needed based on scientific workload studies.
Example 11: Using FireRMS Unit Response data to show Increases (1997 thru 2014) Station & unit 1997 2014 % change Total Unit Responses by Assigned Station 32395 47676 47.17% Does not include Captains & Battalions Station 5 5796 9971 72.03% Engine 5 1547 4185 170.52% Rescue 5 4246 5369 26.45% Rescue 205 3 417 13800.00% Platform 5 680 1255 84.56% *Partial increase due to removal of L40 from service in 2010 Station 105 5540 7580 36.82% Engine 105 1360 2809 106.54% Rescue 105 4180 4771 14.14% Station 5 and 105 11336 17551 54.83% Station 31 8028 12364 54.01% Engine 31 1467 3155 115.06% Rescue 31 3136 4899 56.22% Rescue 231 3187 4077 27.93% Hama 31 238 233-2.10% Station 40 2860 3588 25.45% Engine 40 697 1248 79.05% Rescue 40 1932 2340 21.12% Ladder 40 231 Taken out of Service Station 45 5638 7435 31.87% Engine 45 1710 2535 48.25% Rescue 45 3313 3916 18.20% Ladder 45 615 984 60.00% *Partial increase due to removal of L40 from service in 2010 Station 74 4533 6738 48.64% Engine 74 1501 2884 92.14% Rescue 74 3032 3854 27.11%
Example 12: Using FireRMS Unit Response data to show unit responses by district Date Range: From 1/1/2014 To 12/31/2014 S tation(s) used "All" Total CP105 E105 E40 E45 E5 E74 EH31 HM31 L40 L45 Total 50,586 1650 2809 1248 2535 4185 2884 3155 233 2 984 1255 4771 417 4077 3 1 2 2339 3915 5369 3854 4898 105 6,687 344 1489 90 17 352 115 387 30 55 204 2112 33 323 169 16 479 90 382 7 1 1 1 1 1 2 01 525 28 4 74 29 1 1 2 13 19 14 2 2 81 6 172 76 1 05 13,501 489 764 138 9 2896 82 295 47 92 340 2131 315 520 342 34 4169 262 576 06 1 1 07 2 2 102 3 1 1 1 17 1,013 1 1 6 11 9 495 4 1 11 8 3 5 19 2 434 3 27 1 1 31 10,292 212 226 41 420 323 357 1638 46 1 330 203 203 27 2391 1 74 437 210 257 2895 40 3,937 96 242 920 6 230 22 68 21 1 39 230 187 11 35 2 1612 8 132 21 54 45 8,454 278 36 6 1893 93 370 425 55 307 82 57 6 441 1 32 3198 89 536 549 70 5 1 1 1 1 1 74 6,158 229 50 19 174 208 1414 334 29 148 183 54 10 360 21 196 114 2178 436 P5 R105 R205 R231 R240 R245 R31 R40 R45 R5 R74 RH31
Example 13: 2014 Engine Responses to EMS calls to help justify need for additional ALS Unit. Engine Responses to EMS E5 EH31 E40 E45 E74 E105 District 5 2,365 65 34 4 17 418 District 31 59 986 8 88 61 32 District 40 18 7 508 1 3 24 District 45 17 150 4 1,331 88 4 District 74 42 123 6 37 972 24 District 105 147 207 14 8 64 1,110 Totals 2,648 1,538 574 1,469 1,205 1,612
Finding Automatic Aid Incidents that need to be pulled into your FireRMS database (Connected CAD and FireRMS Data, linked via alarm date
Example 14: Finding Automatic Aid Incidents that need to be pulled into your FireRMS database
Example 15: Finding Data entry errors in your FireRMS Incident Reports
This Conclude my presentation of Best Practices: Practical Uses of FireRMS Data to Improve Your Agency's Performance Any Questions or Discussion? Lisa M. Blouin Fire Rescue Business and Compliance Manager