No CAD Specification - NERIS
NERIS Incident Specification
NERIS FAQ | NERIS Specification | NERIS Fire Department Specification | NERIS Incident Specification
Reporting by Responserack Fire Department RMS.
NERIS Draft Specification
Note: NERIS is currently a draft specification (where this is based upon version: V0.1 - December 2023) and is subject to change.
NERIS - is a DRAFT SPECIFICATION, presented here to aid in review
WORK IN PROGRESS: This information is draft and subject to change. We have presented this information in order to promote review and feedback on the specification. Please provide your feedback to the NERIS team.No CAD Specification
The NERIS incident core specification details the main aspects of the incident when a CAD system is not available.
- Data Framework Overview - the data values, and their definitions.
- Data Framework Details - further details on the data.
- Data Framework Examples - examples of the data.
Data Framework
The data framework provides fields and definitions for the data.
General
- fd_neris_id - This 10 digit integer is a unique identifer for each fire department. Entity type plus state and county FIPS plus with random trailing characters.
- incident_number - Unique numeric identifier for the event that requires dispatch of department resources.
- incident_address_1 - House number and street name of incident; can also be cross streets
- incident_address_2 - Additional address information
- incident_city - City in which incident occurs
- incident_state - State in which incident occurs
- incident_zip - Zip Code in which incident occurs
- incident_latitude - WGS84 latitude of incident
- incident_longitude - WGS84 longitude of incident
- time_incident_created - The time at which the call was received
- time_first_arrival - The time at which the first unit arrived on scene
- time_incident_closed - The time at which the dispatch center closes the call or the last unit leaves the scene
- dispatch_incident_category - The general incident category that informs the corresponding response type
- dispatch_incident_type - The initial incident type as dispatched
- mutual_aid - Identifies whether or not mutual aid was provided on the incident and whether this record is associated with it being provided to another agency or received
- mutual_aid_name - The name(s) of the Fire Department(s) where aid was received/given
- mutual_aid_neris_id - The unique NERIS ID(s) for the fire department(s) where aid was received/given
- station_id - Name of the station responding to the incident
- unit_id - Name of the unit responding to the incident
- unit_capability - The type of unit dispatched on the call
Data Framework Details
General
| Attribute | Definition | Comment | Mandatory |
|---|---|---|---|
| fd_neris_id | This 10 digit integer is a unique identifer for each fire department. Entity type plus state and county FIPS plus with random trailing characters. | Yes | |
| incident_number | Unique numeric identifier for the event that requires dispatch of department resources. | Yes | |
| incident_address_1 | House number and street name of incident; can also be cross streets | Yes | |
| incident_address_2 | Additional address information | No | |
| incident_city | City in which incident occurs | Yes | |
| incident_state | State in which incident occurs | Yes | |
| incident_zip | Zip Code in which incident occurs | Yes | |
| incident_latitude | WGS84 latitude of incident | Computed | |
| incident_longitude | WGS84 longitude of incident | Computed | |
| time_incident_created | The time at which the call was received | Will accept best approximate time, since exact time may not be known. | Yes |
| time_first_arrival | The time at which the first unit arrived on scene | No | |
| time_incident_closed | The time at which the dispatch center closes the call or the last unit leaves the scene | Will accept best approximate time, since exact time may not be known. | Yes |
| dispatch_incident_category | The general incident category that informs the corresponding response type | See incident_type sheet | Yes |
| dispatch_incident_type | The initial incident type as dispatched | See incident_type sheet | Yes |
| mutual_aid | Identifies whether or not mutual aid was provided on the incident and whether this record is associated with it being provided to another agency or received | Yes | |
| mutual_aid_name | The name(s) of the Fire Department(s) where aid was received/given | Comes from FD Specifications - Mutual Aid Agencies (for Selection Purposes) | No |
| mutual_aid_neris_id | The unique NERIS ID(s) for the fire department(s) where aid was received/given | Comes from FD Specifications - Mutual Aid Agencies | No |
| station_id | Name of the station responding to the incident | Station maps to Core Department Spec | Yes |
| unit_id | Name of the unit responding to the incident | Unit maps to Core Department Spec | Yes |
| unit_capability | The type of unit dispatched on the call | Unit type maps to Core Department Spec, See Unit Types Sheet | Yes |
Data Framework Examples
General
| Attribute | Example |
|---|---|
| fd_neris_id | FD06067001 |
| incident_number | FDID_20230814000001, FDID_20230814000002 |
| incident_address_1 | 1234 Market St |
| incident_address_2 | Apt. Number |
| incident_city | Baltimore |
| incident_state | Maryland |
| incident_zip | 21230 |
| incident_latitude | 39.299236 |
| incident_longitude | -76.609383 |
| time_incident_created | MM/DD/YYYY HH:MM:SS |
| time_first_arrival | MM/DD/YYYY HH:MM:SS |
| time_incident_closed | MM/DD/YYYY HH:MM:SS |
| dispatch_incident_category | FIRE, EMS, RESCUE, POLICE, HAZMAT, ADMIN, WEATHER |
| dispatch_incident_type | Structure Fire, Overdose, etc. |
| mutual_aid | Received, Given, None |
| mutual_aid_name | DCFD, PGFD, etc. |
| mutual_aid_neris_id | 2343201 |
| station_id | 703 |
| unit_id | A702, PA711, E731 |
| unit_capability | Ambulance, Paramedic Engine, etc. |
Need more NFIRS help?
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.