Incident Location Tool Now Available for Canadian Agencies (Feature Enhancement)

What
The Incident Location Tool — which enables map-based point and polygon incident location capture — has been extended to support agencies in Canada. A new Enable Location Mapping Tool toggle allows the feature to be turned on individually per agency.

Why
Canadian agencies needed access to the same powerful location capture and validation capabilities already available to US agencies, ensuring consistent incident location data collection across all supported regions.

How
The Incident Location Tool must be enabled per agency before Canadian users can access its functionality.

• Navigate to Setup and select the Response Tab
• Locate the Location Mapping Tool subsection
• Toggle Enable Location Mapping Tool to the on position for the applicable agency
• Once enabled, the agency will have access to point and polygon selection, geometry storage, and Ignition Point marking
• The toggle defaults to off — no existing agency configurations are affected until explicitly enabled

Use Case
- A Canadian fire agency can now capture precise incident location data using map-based point and polygon tools, matching the workflow used by US agencies.
- An administrator can enable the tool for a specific Canadian agency without impacting any other agency's existing setup or behavior.
- A dispatcher can validate and record an incident's geographic location using the mapping tool, improving accuracy of response data for Canadian incidents.

For additional information and detailed instructions, please refer to the Fire Incident Report: Location Area Map Tool Knowledge Base article.

Incident Locator Tool Enhancements for Incident Type Requirements and Aid Given Boundary Override (Feature Enhancement)

What — The Incident Locator Tool configuration on the Fire Incident Setup > Response tab has been enhanced with two new settings: a dropdown/multi-select to define which primary incident types require address validation through the Locator Tool, and a new option to allow Aid Given calls to be located outside the operational boundary.

Why — These changes provide administrators with greater flexibility in how the Locator Tool is applied across different call types, reducing unnecessary steps for certain incidents while ensuring mutual aid calls can be accurately located beyond a department's configured boundary.

How
- Navigate to Fire Incident Setup and select the Response tab
- Locate the updated Locator Tool requirement setting, previously a single checkbox
- Use the dropdown/multi-select to choose the primary incident types (e.g., wildfire, outdoor fire, hazmat) that should require address validation through the Locator Tool
- Locate the new setting beneath Configure Operational Boundary
- Enable the option to allow Aid Given calls to be located outside the operational boundary
- Save your configuration changes
- Note: Incident types not selected in the dropdown will not require the additional Locator Tool validation step during incident creation

Use Case
- A dispatcher creating a medical call is no longer prompted to use the Locator Tool, reducing unnecessary clicks for call types that do not require it.
- An administrator can configure wildfire and hazmat incidents to require Locator Tool validation while leaving other call types unaffected.
- A unit responding to a mutual aid incident can accurately locate and record an Aid Given call that falls outside the agency's defined operational boundary.

Self-Service Historical NFIRS Data Import (New Feature)

What – Users can now upload historical NFIRS .TXT files directly through the Import Historical Fire Incidents screen, eliminating the need for engineering or backend involvement. Imported records are brought in with full field mapping and remain read-only after import.

Why – Previously, importing historical NFIRS data required a lengthy manual, engineer-executed process for every request. This feature empowers clients and Implementation Managers to complete imports independently, reducing delays and operational overhead during onboarding.

How
- Navigate to the Import Historical Fire Incidents screen within the application
- Select the option to upload a NFIRS .TXT file
- Upload the file and review any validation errors surfaced during processing
- Resolve flagged errors as needed and resubmit
- Monitor import status through to completion directly within the screen
- Imported historical records will be read-only and cannot be edited after import
- Imports are managed to avoid contention with other active NFIRS or ePCR jobs running on the server

Use Case
- A fire department onboarding to the platform can upload years of historical incident records without waiting on a support request or engineering intervention.
- An Implementation Manager can independently manage a client's historical data import, tracking progress and resolving validation issues in real time.
- An agency needing to preserve historical NFIRS records in the system can do so quickly and accurately, with confidence that all standard NFIRS spec fields are correctly mapped.

NERIS Incident Analysis Submission Support (New Feature)

What – Agencies can now capture and submit NERIS Incident Analysis secondary schema data — including cause/origin, contributing factors, and loss metrics — directly within the existing incident report. This enrichment data is submitted separately from the base report through a dedicated Submit Analysis action.

Why – NERIS now accepts Incident Analysis secondary schema data as optional enrichment, and agencies have compliance-driven targets to begin submitting this information. This feature ensures agencies can meet those obligations without workarounds or manual processes outside the system.

How
- This feature is available on incidents that have already been Authorized and assigned a NERIS ID
- Navigate to the Incident List and locate the applicable incident
- Open the incident report and complete the Incident Analysis fields, including cause/origin, contributing factors, and loss metrics
- Once the base report is Authorized, select the Submit Analysis action to submit the secondary schema data to NERIS
- Monitor submission progress using the new Incident Analysis Status column on the Incident List
- Note: This feature applies to the Incident Analysis secondary schema only — CRR and Health & Wellness secondary schemas are not included at this time

Use Case
- A fire investigator completes an incident report and, after authorization, submits enrichment data capturing the cause and origin of a structure fire directly to NERIS.
- A records manager uses the Incident Analysis Status column to quickly identify which incidents still have pending or incomplete secondary schema submissions.
- An agency administrator reviews loss metrics submitted through the Incident Analysis schema to ensure all enrichment data is accurately reported to NERIS.

Dedicated CAD Narrative Field for Incident Reports (New Feature)

What – A new CAD Narrative field is now available in incident reports, allowing CAD Notes to be populated into a dedicated field separate from the General Narrative. This gives agencies greater control over how CAD-sourced content is organized within their incident documentation.

Why – Agencies need the ability to keep CAD-sourced narrative content distinct from general narrative entries to maintain cleaner, more structured incident records and align with evolving data standards that treat CAD notes as a separate data point.

How
- A System Administrator can configure this behavior in the agency's settings
- Locate the existing "Populate CAD Notes into General Narrative" setting
- Below it, find the new "Populate CAD Notes into CAD Narrative" setting
- Select the desired option — note that these settings are mutually exclusive, so enabling one will automatically disable the other
- Once the CAD Narrative setting is enabled, the CAD Narrative field will appear in incident reports and will auto-populate with CAD Notes
- This feature is available to all agencies, not limited to a specific reporting standard or client type
- Both settings cannot be active at the same time, and existing General Narrative behavior remains unchanged

Use Case
- An agency wants CAD-dispatched comments to appear in their own dedicated field so reviewers can quickly distinguish between dispatcher notes and manually entered narrative content.
- A System Administrator configures the new setting so that all incoming CAD Notes automatically populate the CAD Narrative field, keeping incident reports consistently organized.
- An agency transitioning to structured incident reporting standards can route CAD Notes through the appropriate field without disrupting existing General Narrative workflows.