<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=6813716&amp;fmt=gif">
Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

NERIS Transition Guide

With the industry shift to NERIS, our team has been working hard to ensure that we can continue to ingest your RMS data and seamlessly integrate it with your existing data. Different RMS vendors have been handling the transition in different ways, and we’ve done our best to accommodate those changes.

Depending on your RMS vendor and your method of data transfer between RMS and Darkhorse, there may be action needed by your team to ensure the data flow isn’t interrupted and that new data, like NERIS incident types, is included.

Below, you’ll find instructions based on your RMS vendor and data transfer method. Please have a read through and let your Darkhorse analyst know if you have any questions.

Please review the instructions below that apply to your department:

ESO API Users

  • Because ESO has replaced their existing Fire module with a new NERIS module, the old method of importing your data will cease to work once you transition.
  • Action Required: You'll need to generate a new API key for us to import data from ESO's new system.
  • You can find detailed instructions for generating your new API key here.

First Due ODBC Users

  • No action needed. Your incident and response data will continue to import without interruption. We've already made the necessary adjustments to import the new NERIS columns from First Due's data warehouse.

Email Attachment/Emailed Reports (Any RMS Vendor)

  • ESO Clients: If existing columns remain populated, you will only need to add NERIS incident type columns to the report. If not, you may need to build a new report using fields from the NERIS module. Your new reports can be directed to the same Darkhorse data ingestion email as before.
  • Other RMS Vendors:
    • If existing columns remain populated and NERIS incident type is captured in an existing column, no action is needed.
    • If new fields have been created for NERIS incident types or other existing columns, your report will need to be updated to include these fields.
    • Action Required (if applicable): Please contact your Darkhorse analyst about any new fields and when the change will be made effective.

SFTP Upload Users (Any RMS Vendor)

  • If existing columns remain populated and NERIS incident type is captured in an existing column, no action is needed.
  • If new fields have been created for NERIS incident types or other existing columns, your report will need to be updated to include these fields.
  • Action Required (if applicable): Please contact your Darkhorse analyst about any new fields and when the change will be made effective.

API Users Not Mentioned Above

  • At this time, we have not received information from other vendors about how/if their existing APIs will be affected. If any changes occur that will require updates our end, please know that we will prioritize making any changes as soon as we possibly can.

Frequently Asked Questions

Will there be a crosswalk between NFIRS codes and NERIS codes?

We will automatically map your old NFIRS codes to the NERIS equivalent using the official NERIS crosswalk. However, this crosswalk is not very detailed; you can expect that previous NFIRS incident types will translate to NERIS incident subcategories at best. At present, there is no high-granularity crosswalk that could be considered an industry standard.

We expect that, as time progresses, an industry standard crosswalk will be developed, conventions will emerge, and agencies will establish their own internal methods. Our ability to remap these incidents is flexible and can be updated as industry practices evolve.

What if my RMS vendor isn’t mentioned above?

If you are sending us data via email attachments or SFTP uploads, then you can follow the instructions outlined above.

If your data is being sent by another API or data connection not mentioned, we have not received any information from your RMS vendor about how/if their process will change. Please know that, if any changes occur that will require updates on our end, we will prioritize making any changes as soon as we possibly can. If you have any questions or concerns, please do not hesitate to reach out to your Darkhorse analyst.

Will my data feed to Darkhorse be interrupted?

For ESO clients, the Fire Incidents module is being deprecated and replaced with the new NERIS module. Action is needed as outlined above, otherwise, you may experience an interruption in data ingestion.

For other RMS vendors, we do not anticipate interruptions. We can continue to ingest your data as we have been, though NERIS incident type fields will need to be added to your reports if they're not already captured.

Will the new NERIS incident types be available in Darkhorse as soon as they appear?

For certain data pipelines, like ESO API or First Due ODBC, we will integrate the new NERIS incident type data into our apps as soon as possible, ahead of January 1st.

For other methods of data transfer, we will be mapping the new fields as they come in. The sooner you can add them to your reports, the sooner we can add them to our applications!

What will the NERIS incident type data look like in Darkhorse?

By default, the new primary NERIS incident type will be mapped into your existing “RMS/NFIRS Incident Major Category/Minor Category/Incident Type” fields. As we receive that new data, those types will begin to appear in your existing accordions. Old NFIRS codes and categories will remain there, and we do not plan to remove them in the foreseeable future.

Using the official NERIS crosswalk, we will also be adding a new accordion that translates the old NFIRS codes into their NERIS equivalent. Although the translation is not very granular, it will provide some continuity across the transition and allow you to compare incident types using the NERIS conventions.

Because our systems currently only allow a single incident type per incident (the NFIRS convention), only the primary NERIS incident type will be available in these default accordions. We plan to expand that capability to support multiple incident types per incident in the future.

Will the switch to new NERIS codes affect our apps or create errors?

The new NERIS codes will not create any errors. However, if your agency uses RMS incident types for the purposes of reporting or performance measurement, the transition will affect the apps and you may find those metrics to stop populating once you’ve made the switch.

As you determine new metrics you’d like to track or rules around how you would like to switch from your NFIRS code-dependent metrics to new NERIS codes, please let us know and we’ll happy to update our configuration as soon as possible.

What if I have other questions?

If you have anything you'd like to discuss further, please don't hesitate to contact your Darkhorse Analyst. We're committed to supporting you through this transition.