What we’ve built and where we’re headed
The NERIS-compatible Fire Incidents application was released to all ESO agencies — giving every customer access to the new standard well ahead of the January 2026 compliance deadline.
CAD data flows seamlessly into both NFIRS and NERIS simultaneously.
- Agencies gained self-service tools to manage record status in bulk
Scheduling integration completed and deployed.
- EHR integration began bringing patient data directly into incident records
ESO Fire Incidents customers went live on the national NERIS standard. ESO moved to a weekly release cadence to rapidly address customer feedback and stabilize the experience post-launch.
The first full-featured NERIS incident print page launched.
- Agency logo & header on every page
- Standardized footer with incident # and page count
- Permission-controlled print access
- Logical page breaks for readability
- Print cached for fast repeat requests
- Cross street data in Location column
Print capabilities expanded with privacy controls and file packaging.
- Configurable field redaction
- Attachments downloadable as .zip with PDF
- Attachment count column added to incidents grid
- Resources date/times respect agency time zone
Updated analytics dashboards gave agencies powerful tools to understand their NERIS data.
- Incomplete Locked Incidents
- AFG Grant – Fire Incidents
- 214 Data
- Fire Incident Report Performance
- Personnel & Units (call volume)
Significant improvements to how addresses are captured and displayed.
- Cross street search with auto-populate
- Cross street modifier field (NERIS schema compliant)
- Exposures header shows Apt/Unit/Suite
- 10+ validation and permission bug fixes
The Resources workflow received its biggest overhaul yet — a fully rebuilt multi-page experience with real-time save conflict detection.
- Address parser live — replaces manual ESRI lookup as first step in import workflow
The ability for each agency to configure which fields are required, optional, or hidden in their incident workflow.
- Set fields as required, optional, or hidden per your agency’s workflow
- Reduce clutter for incident types that don’t need every field
- Enforce completeness for fields your department prioritizes
