Indiana Department of Homeland Security
HB1427 Semi-Annual Fire Run Reporting — Interactive Appendix
Reporting Period: 2025-07-01 to 2025-12-31
Generated: February 27, 2026
Data Source: ImageTrend

Key Reporting Logic

Purpose of this appendix

This appendix provides interactive tables that show HB1427 reporting totals and how those totals change under a small set of quality control scenarios. These scenarios help separate true incident activity from reporting artifacts that can appear in raw extracts. The two key reporting scenarios are multiple rows representing the same incident and extremely high and implausible apparatus reporting.

How to read the tables

Each reporting table shows the selected scenario value, the HB1427 Reported baseline value, and a Delta vs HB1427 Reported.

  • HB1427 Reported corresponds to Deduplicated w/ Apparatus Truncation.
  • Delta vs HB1427 Reported is HB1427 Reported − Scenario Value.
  1. What counts as a “run”

For HB1427 reporting, a run is counted once per unique combination of: Agency FDID + NFIRS Number + Incident Date.

This approach avoids cross‑agency collisions when NFIRS numbers repeat across different agencies in the source extracts.

  1. Duplicate-record review (what we tested, what we found, and what we did)

The source extracts can contain multiple rows that refer to the same incident. This review summarizes the tests performed to understand why duplicates occur and the decision logic used for HB1427 reporting.

What we tested

  • Duplicate run identifiers (run_key = Agency FDID + NFIRS Number + Incident Date).
  • Whether duplicates are driven by multiple dispatch timestamps (dispatch_dt).
  • Whether duplicates include different addresses.
  • Whether incident type changed with apparatus/personnel patterns.
  • Whether duplicates look like true incident updates over time (i.e., additional apparatus and personnel dispatch).

Key results

  • Duplicate run_key groups found: 54,695.
  • Duplicate anatomy (top patterns):
    • Dispatch time varies but apparatus and personnel are stable: 93.03%.
    • Exact duplicates (repeated rows with no variation): 3.72%.
    • Mixed / needs review: 3.2%.
    • Those requiring manual review were explainable artifacts. The City of Gary Fire Department (99% of cases), Marion Fire Dept., and. Crown Point Fire Rescue Dept were missing incident type codes among duplicates and the remaining three agencies have multiple incident codes for the same NFIRS number (n=3 runs total).

Decision logic for deduplication

  1. For HB1427 reporting, one run is counted once per (Agency FDID + NFIRS Number + Incident Date).
  2. QC indicates most duplicate rows are reporting artifacts rather than distinct runs or deployments.
  3. Therefore duplicates are collapsed using MAX across apparatus/personnel fields (not SUM) to avoid double-counting.
  1. Vehicle totals used for reporting

HB1427 requires reporting the number of vehicles participating in each run. Vehicle totals are derived from three apparatus fields: Suppression, EMS, and Other apparatus.

Step 1 — Deduplicate to one run record

When multiple raw rows exist for the same run, they are consolidated so each incident is counted once.

Step 2 — Compute total vehicles

  • Total vehicles = Suppression apparatus + EMS apparatus + Other apparatus (missing treated as 0)

Step 3 — Apparatus truncation (conditional)

In several cases, the number of apparatuses reported were not plausible. Because the number of dispatched apparatuses cannot exceed the number of like personnel, we deployed additional logic to control data reporting artifacts. When an apparatus count exceeds the corresponding personnel count and personnel is present, the apparatus count is capped (or truncated) at the personnel value for that category. This addresses structural inconsistencies that can occur when personnel is reported as 0 or otherwise lower than the number of vehicles. This also controls data artifacts (e.g., 750,000 vehicles dispatched on a single run) so this report better reflects actual conditions.

4. Quality control scenarios included in this appendix

This appendix includes three scenarios to show how totals change under different treatments of duplicates and apparatus/personnel inconsistencies.

Scenario label Deduplication Apparatus truncation Primary purpose
Deduplicated w/ Apparatus Truncation (HB1427 Reported baseline) Yes Yes (conditional) Official HB1427 reporting totals
Deduplicated w/out Apparatus Truncation Yes No Isolate the impact of truncation on vehicle totals
Raw ImageTrend No (raw rows) No Reference point for totals as extracted (no deduplication, no truncation)

Note: The “no truncation” scenario primarily affects vehicle-based metrics. Raw totals are provided as context only.

1) Statewide

The table below provides statewide HB1427 metrics. Use the dropdown to view the baseline totals and the two quality control scenarios.

2) Agency drill-down

The table below provides HB1427 metrics by agency. Use the search box to find an agency, then select a scenario.

3) QC & Audit Appendix

This section provides limited audit-oriented context used to interpret statewide and agency totals.

3.1 Active Agencies Without Fire Run Data in the Current Reporting Period

3.2 Apparatus Reporting Inconsistencies

The table below shows agencies with the largest differences (top 50) in vehicle totals between the baseline (with truncation) and the 'no truncation' scenario.