NFIRS Codes Cheat Sheet - NFIRS Coding - NFIRS Examples - FDIDs - POCs
Definition: The effectiveness of the fire detection equipment in alerting occupants.
Need something else? Here is the complete list of all NFIRS modules and subsequent NFIRS transactions, plus a list of all NFIRS elements.
NFIRS 5.0 relational edit validation rules are provided to ensure NFIRS data is consistent and correct for the fire/reporting concepts that are being modeled. Relational edits determine relationships between multiple fields / elements. These are the rules for ‘Detector Effectiveness’.
Rule | Group | Overview |
---|---|---|
Relational Edit Rule 75 | If the detector operated, did it alert occupants?. |
Here are the NFIRS codes for the ‘Detector Effectiveness’ element, including any “other” values in case none of the preselected choices match:
Detector Effectiveness | Code |
---|---|
Detector Alerted Occupants, Occupants Responded | 1 |
Detector Alerted Occupants, Occupants Failed To Respond | 2 |
There Were No Occupants | 3 |
Detector Failed To Alert Occupants | 4 |
Undetermined | U |
A few NFIRS elements are reused accross a number of transactions, but typically the value is captured by one transaction only.
Specification | Value |
---|---|
Requirement | Optional |
Expected Length | 1 |
Element Type | Coded Field - The coded field relating to an entry in the code table. Most coded fields allow for Plus+ One codes. For these fields the expected length of the coded entry is depicted as (National length OR Plus+ One length). Only fields with this notation in the expected length column allow for Plus+ One definitions. If the user has not provided information, an empty field should be transmitted. |
Need more help with NFIRS, or not yet found what you are looking for? Please see if these help …
For more information see the NFIRS Cheat Sheet, NFIRS Coding and contact Responserack to learn about our fire department software.