For fifty years, NFIRS was the answer to a simple question: what happened on that run? Every fire dept in the country typed the same codes into the same boxes and the data went to the same place, and the modeling on top of it shaped everything from staffing formulas to NFPA standards to how your city budgets its next apparatus buy.
NFIRS 5.0 is going away. NERIS V1 — the Fire Safety Research Institute's National Emergency Response Information System — is what replaces it. This is not a formatting change. It's a data-model change, an authentication change, a submission-flow change, and a schema-of-schemas change. If your records vendor tells you "we'll handle it, don't worry about it," ask them what environment they're submitting to today. If they can't answer sandbox, test, or prod, they haven't started.
We built the full NERIS integration into Piran Command months ago. This post is what we wish someone had written for us when we started.
What actually changed
NFIRS was a flat report. One incident, one form, a hundred-something fields, a batch upload once a month. NERIS is a live API. Every incident is a structured payload — Core, Fire module, Medical module, Tier 2 for the deep stuff — authenticated via OAuth 2.0 client credentials, submitted per-department, per-environment, with validation on the way in.
That means:
- Every dept needs credentials. Not a login. A client ID and secret, scoped per environment (sandbox for developing against, test for staging, prod for the real thing).
- Every station needs to be registered. NERIS knows about your physical stations. You register them once, get back a NERIS ID, and every incident references it.
- Every apparatus needs to be registered. Same deal. Engine 1 isn't just "Engine 1" — it's a NERIS resource with an ID that travels with it on every dispatch.
- Every run submits live. No more end-of-month batches. When you terminate an incident, the payload goes up. Errors come back synchronously. You fix them synchronously.
None of that is bad. In fact, it's the most meaningful upgrade to fire data infrastructure in a generation. But it means your records vendor either did the work or they didn't, and there is no middle ground.
The three environments (and why they matter)
NERIS exposes three environments:
| Environment | What it's for |
|---|---|
| Sandbox | Developer playground. Nothing sticks. Break stuff freely. |
| Test | Staging. Real credentials, real submissions, real errors — nothing counted in national statistics. |
| Prod | The real thing. Every submission is on the record. |
If your vendor is telling you they're "ready for NERIS" but they only have sandbox creds, they are not ready. If they have test creds but have never submitted a real incident, they are not ready. Ask them directly, in writing: "Have you submitted a real incident to NERIS prod on behalf of a real fire department?" Then ask which department, and confirm with that department's chief.
We're building this transparently on purpose. Our NERIS module ships with per-environment credential storage on the department record and a switch in the admin UI to move between them. Chiefs pilot in test. When they're comfortable, they flip to prod. That's how software this important should feel.
The vendor landscape (and why most aren't ready)
Records-management systems in the fire service are old software. Some of them predate the smartphone. NFIRS 5.0 was itself layered on top of NFIRS 4, which was layered on top of paper. The migration to NERIS is a from-scratch integration for most vendors — new auth model, new data model, new submission cadence — and most of them have not done the work yet.
We don't name competitors on this blog. But you can benchmark any vendor yourself with three questions:
- "What NERIS environment are you submitting to today?" If the answer isn't "prod," they're not ready.
- "How do stations and apparatus get registered?" If the answer involves a spreadsheet you email in, they're not ready.
- "Can I preview the NERIS payload before it submits?" If the answer is no, they're black-box submitting on your behalf. Not ready.
We built preview-before-submit into Piran Command because chiefs told us they didn't trust invisible pipelines. They wanted to see the JSON. So we show them the JSON.
What NERIS-ready actually looks like
We ship it live. Here's the checklist we hold ourselves to and every department using Piran Command gets:
- Per-environment OAuth client with automatic token refresh and backoff on 429/5xx
- Sandbox / test / prod switch, per-department, in the admin UI
- Station registration flow, one-click, stores the NERIS station ID back on your record
- Apparatus registration flow, one-click per unit, stores the NERIS resource ID back on your apparatus record
- Automatic serialization from your Piran Command incident to a validated NERIS payload (Core, Fire, Medical, Tier 2)
- Hard-error / warning split on the validation pass — you see what will block a submission before you try
- Preview endpoint to inspect the exact JSON that would submit
- Submit endpoint with per-incident status tracking
- Daily / date-range export endpoint for auditing
That's what "NERIS-ready" means. Anything less is a marketing claim.
What to do this week
If you're a chief reading this and you're not sure where your department stands:
- Ask your records vendor which NERIS environment they're submitting to today. Get it in writing.
- Check your run cards. Which stations and apparatus are you going to need to register? Make a list now.
- Look at your last thirty incidents. How many would fail validation today for missing fields (times, dispositions, personnel, disposition codes)? The gap between what you're collecting today and what NERIS demands is your migration debt.
- Talk to another chief who's already piloting. If you don't know one, we'll introduce you.
We built this the way we wish it existed when we were on the line
We're firefighters. Piran Command started because the tools we were using to run our own department were built by people who had never worn the gear. NERIS is important because the data shapes every NFPA standard we work under, every ISO rating, every budget cycle. It should not be a black box, and it should not be a checkbox on a vendor sales sheet.
If your department is looking at the NERIS transition and wondering what "ready" actually looks like, we're happy to walk you through what we built. Fifteen minutes, no sales script, just the payload and the flow.