Date post: | 27-Dec-2015 |
Category: |
Documents |
Upload: | miranda-whitehead |
View: | 217 times |
Download: | 0 times |
Utah Fire Incident Reporting System
NFIRS 5.0 Required Modules
Module Use Primarily Driven By Incident Type….Module 1 All Incidents
Module 2 Fire
Module 3 Structure Fire
Module 4 Civilian Casualty
Module 5 Fire Service Casualty
Req
uir
ed
in
U
tah
Utah Fire Incident Reporting System
NFIRS 1 - Basic Module
is completed for every incident
Utah Fire Incident Reporting System
NFIRS 1 - Basic Module
Used for all incidents to collect common informationState legislation determines which optional modules must be submitted to the stateEntries on Basic Module may require that other modules be completed
Utah Fire Incident Reporting System
A - Header Information
Contains the information that uniquely identifies the incident ( FDID, state, incident date, number, and exposure)
Incidents may have several exposure fires requires a separate report uses the same incident number and
consecutive exposure numbers Identifies if reporting a change, deletion,
or no activity
Delete AChange
NFIRS - 1 Basic
No Activity Incident Number Stat ion FDID Exposure Inc ident Date
MM DD YYYY
State
Utah Fire Incident Reporting System
B - Location
Identifies specific location of the incident
Indicates whether Wildland Module is used and “Alternate Location Specification” is provided
Accepts GIS Compatible Format
Intersection Block address In front of Rear of Adjacent to Directions
B Location Check this box to indicate that the address for this incident is provided on the Wildland Fire Module in Section B “Alternative Location Specification.”
Census Tract (Local option)
Suffix Number/Milepost Prefix Street or Highway Street Type
City Zip Code State Apt./Suite/Room
Cross street or directions, as applicable
-
Utah Fire Incident Reporting System
C - Incident Type
Identifies the single most significant situation found Includes codes for all types of
incidents handled by fire service agencies
Fire takes precedence over all other incident types (if multiple situations exist at the same incident)
C Incident Type
Incident Type
1 15
Utah Fire Incident Reporting System
D - Aid Given or Received
Options include:Mutual aid given
or receivedAutomatic aid
given or receivedOther aid givenNone
Their FDID
Their Incident Number
Their State
Mutual aid received Automatic aid recv. Mutual aid given Automatic aid given Other aid given None
12345N
D Aid Given or Received
Their FDID
Their Incident Number
Their State
Mutual aid received Automatic aid recv. Mutual aid given Automatic aid given Other aid given None
12345N
D Aid Given or Received
Collects receiving department’s FDID and incident #
Utah Fire Incident Reporting System
E1 - Dates & Times
Collects date and time of alarm , arrival time, controlled time, and last unit cleared Automated systems capture time in
seconds 0000 hours=midnight
E1 Dates & Times Midnight is 0000
Year Hour Min Check boxes ifdates are thesame as Alarm Date.
Month Day
Alarm
Arrival
Controlled
ALARM always required
ARRIVAL required, unless cancelled or did not arrive
CONTROLLED optional, except for wildland fires
LAST UNIT CLEARED, required except for wildland fires Last Unit Cleared
Utah Fire Incident Reporting System
E2 - Shift and Alarms
Identifies the on-duty shift or platoon; the number of alarms transmitted for the incident; and the district number
E2 Shifts & Alarms
Shift orplatoon
Alarms District
Local Option
Utah Fire Incident Reporting System
F - Actions Taken
Records the three most significant actions performed on the incident scene by responding personnel
Codes include entire spectrum of fire service activities, including EMS & Hazardous Materials
Actions TakenF
Primary Action Taken (1)
Additional Action Taken (2)
Additional Action Taken (3)
Utah Fire Incident Reporting System
G1 - Resources
Collects the total number of personnel and apparatus, by type, that responded to the incident
This information will be automatically calculated if using the apparatus or personnel module in an automated system
Check this box and skip this section ifan Apparatus or Personnel form is used.
PersonnelApparatus
Check box if resource counts includeaid given resources.
EMS
Other
Suppression
ResourcesG1
Utah Fire Incident Reporting System
G2 - Dollar Losses & Values
Provides an estimate of the total dollar loss and the pre-incident value of the property and contents
PRE-INCIDENT VALUE: Optional
Estimated Dollar Losses & Values G2
LOSSES: Required for all fires. Otherwise optional. None
Property $ , ,Contents , ,
Property $ , ,Contents $ , ,
Complete for all firesUsing replacement value is recommended
Utah Fire Incident Reporting System
H1 - Casualties
Identifies the number of deaths or injuries as a result of the incident (or during mitigation of the incident)
None
Injuries Deaths
H1 Casualties
Fire Service
Civilian
Utah Fire Incident Reporting System
H2 - Detector
Identifies the presence of detectors at the time of the incident and whether they alerted the occupants.
X
DetectorH2Required for confined fires
Detector alerted occupants
Complete for confined fires when
occupants were alerted
Utah Fire Incident Reporting System
H3 - Hazardous Materials Release
Documents the occurrence of a hazardous materials release at the incident
The Hazmat Module (NFIRS-7) should be completed if “other” is checked
H3 Hazardous Materials Release
None Natural gas: slow leak, no evacuation or hazmat actions
Propane gas: <21 lb. tank (as in home BBQ grill)
Gasoline: vehicle fuel tank or portable container
Kerosene: fuel burning equipment or portable storage
Diesel fuel/fuel oil: vehicle fuel tank or portable storage
Household solvents: home/office spill, cleanup only
Motor oil: from engine or portable container
Paint: from paint cans totaling <55 gallons
Other: Special Hazmat actions required or spill > 55 gal., Please complete the Hazmat form
N123456780
Utah Fire Incident Reporting System
I - Mixed Use Property
Captures data on the overall use of the structures on a property If a structure has two or more property uses, or
If a property has two or more structures with different uses
Mixed Use Property INN102033405153585960636500
Not mixed Assembly Use Education use Medical use Residential use Row of stores Enclosed mall Business & residential Office use Industrial use Military use Farm use Other mixed use
Utah Fire Incident Reporting System
J - Property Use
The specific use of the property where the incident occurred
J Property Use
131161162213215241311331
Structures
Church, place of worship Restaurant or cafeteria Bar/tavern or nightclub Elementary school or kindergart. High school or junior high College, adult ed. Care facility for the aged Hospital
341342361419429439449459464519
Clinic, clinic type infirmary Doctor/dentist office Prison or jail, not juvenile 1- or 2- family dwelling Multi-family dwelling Rooming/boarding house Commercial hotel or motel Residential, board and care Dormitory/barracks Food and beverage sales
539579571599615629700819882891
Household goods, sales, repairs Motor vehicle/boat sales/repairs Gas or service station Business office Electric generating plant Laboratory/science lab Manufacturing plant Livestock/poultry storage (barn) Non-residential parking garage Warehouse
Outside
Property Use
124655669807919931
Playground or parkCrops or orchardForest (timberland)Outdoor storage areaDump or sanitary landfillOpen land or field
936938946951960961962
Vacant lot Graded/cared for plot of land Lake, river, stream Railroad right of way Other street Highway/divided highway Residential street/driveway
981984
Construction site Industrial plant yard
Look up and enter a Property Use code only if you have NOT checked a Property Use box:
Utah Fire Incident Reporting System
K1 - Person/Entity Involved
Collects the name and contact information for persons or entities (businesses, companies) involved in the incident or related to the property
More people involved? Check this box and attach Supplimental Forms (NFIRS-1S) as necessary.
Business name (if applicable)
Check this box if same address as incident locat ion. Then skip t he t hree duplicat e address lines.
Person/Entity InvolvedK1Local Opt ion Area Code Phone Number
Mr., Ms., Mrs. SuffixLast NameMIFirst Name
Zip CodeStat e
CityApt ./Suit e/RoomPost Office Box
SuffixSt reet TypeSt reet or Highw ayPrefixNumber
Utah Fire Incident Reporting System
K2 - Owner
Collects the name and contact information for the person or entity that owns the property where the incident occurred
More people involved? Check this box and attach Supplimental Forms (NFIRS-1S) as necessary.
Business name (if applicable)
Check this box if same address as incident locat ion. Then skip t he t hree duplicat e address lines.
Person/Entity InvolvedK1Local Opt ion Area Code Phone Number
Mr., Ms., Mrs. SuffixLast NameMIFirst Name
Zip CodeStat e
CityApt ./Suit e/RoomPost Office Box
SuffixSt reet TypeSt reet or Highw ayPrefixNumber
Utah Fire Incident Reporting System
L - RemarksProvides for a
narrative description of the incident
Includes an instructional box intended to provide guidance for completing the report
Check the box that applies and then complete the additional Fire mod. based on Incident Type as follows:
Fire Module Required?
Buildings 111 Special structure 112
Confined 113-118 Mobile Property 120-123 Vehicle 130-138 Vegetation 140-143 Special outside fire 161-164
Complete Fire & Structure Complete Fire Mod. & the I block on Structure Module Complete Fire Module Complete Fire Module Complete Fire Module Complete Fire or Wildland Complete Fire Module
Utah Fire Incident Reporting System
M - Authorization
Collects the name and identifying information for the Officer in Charge of the incident and the member completing the incident report
M Authorization
Officer in charge ID Signature Position or rank Assignment Month Day Year
Member making report ID
Signature Position or rank Assignment Month Day Year
Check box if same as Officer in charge.
1
Utah Fire Incident Reporting System
Summary
The Basic Module (NFIRS 1) is used for every incidentState legislation determines which optional modules must be submitted to the stateThe Basic Module is the only report which must be completed for many incident types