Reports Module Updates

Reports Module Updates

New Data Sources:


1 - Daily Log Data Source

  • What - A new Daily Log data source has been added to the Ad Hoc reporting system, providing comprehensive reporting capabilities for the Daily Log submodule within the Activities module. This data source captures day-to-day operational events including event types, apparatus involvement, timing, duration, and personnel participation, with full compatibility for filtering, grouping, and summary functionality within Ad Hoc reports.
  • Why - While users could previously view and filter Daily Logs within the Activities interface, these capabilities were limited to basic searches without advanced reporting options. The new data source enables users to create detailed summaries, interactive dashboards, and automated scheduled reports that deliver deeper insights into agency activity trends, workload distribution patterns, and apparatus utilization metrics.
  • How - The Daily Log data source is automatically available to users with existing Ad Hoc reporting permissions and requires no additional setup or role changes.
    • Navigate to Ad Hoc Reports and select Create New Report
    • Choose Daily Log from the available data sources
    • Configure your report using standard Ad Hoc functionality including filters, grouping, and summaries
    • The data source supports joins with Personnel records and includes lookup tables for Activity Type, Event Type, and Apparatus
    • Reports will automatically respect multi-tenant filtering and existing report-sharing permissions
  • Use Case - A fire department chief can now create a monthly dashboard showing apparatus utilization trends by generating a summary report that groups Daily Log entries by apparatus type and calculates total operational hours per unit. Additionally, supervisors can set up automated weekly reports to track personnel participation patterns across different event types, helping identify training needs and optimize shift scheduling based on actual operational data rather than manual tracking methods.

2 - Work Order Labor Data Source

  • What - A new Work Order Labor data source has been added to Ad Hoc reporting, providing detailed labor information for work orders including personnel assignments, completion details, and cost breakdowns. This data source supports one-to-many relationships with Work Orders and enables comprehensive tracking of labor activities across vendors and internal personnel.
  • Why - While users could previously view labor details within the Work Orders interface, there was no capability to generate aggregated financial reports or analyze trends across different vendors and personnel. This new data source enables budget analysis, cost tracking, vendor performance evaluation, and labor utilization reporting directly within the Ad Hoc system.
  • How - The Work Order Labor data source is automatically available to users with existing Ad Hoc reporting permissions.
    • Navigate to Ad Hoc Reports and select Create New Report
    • Choose Work Order Labor as your data source
    • Use standard Ad Hoc functionality for filtering, grouping, and summaries
    • The data source automatically joins with Work Orders as the parent relationship
    • Filter by vendor assignments or user assignments using the Completed By Type field
    • Access vendor names and user lists through the Completed By fields
  • Use Case - A fleet maintenance supervisor can create monthly cost analysis reports by grouping Work Order Labor records by vendor to compare external service costs against internal labor expenses. Additionally, administrators can generate quarterly reports showing labor utilization trends by filtering for internal personnel assignments and analyzing total hours worked across different types of maintenance activities to optimize staffing and budget allocation.

3 - Updated CAD Incident Number in Incident Report Data Sources

  • What - The CAD Incident Number field in Ad Hoc and ODBC reports has been updated with improved fallback logic to ensure it consistently displays the same value shown as the Dispatch Number in the Incident Report interface. The enhancement addresses cases where valid dispatch numbers appeared as NULL in reports despite being visible in the system.
  • Why - Depending on how incident records are created or imported, the Dispatch Number can be stored in different database tables, but the previous reporting logic only checked one location. This caused valid dispatch numbers to appear as NULL in Ad Hoc and ODBC reports even though users could see the correct values in the Incident Documentation screen, creating data accuracy issues for reporting teams.
  • How - This update is automatically applied to existing incident report data sources with no user action required.
    • The CAD Incident Number field will now automatically display correct values in both f_incident_report and f_incident_report_neris data sources
    • Existing Ad Hoc reports and ODBC connections will immediately benefit from improved data accuracy
    • All current filters, joins, and exports continue to function without modification
    • No changes needed to report configurations or column references
  • Use Case - Fire department analysts creating monthly incident summary reports will now see complete CAD Incident Number data instead of encountering unexpected NULL values, enabling accurate cross-referencing with dispatch system records. This ensures that incident volume reports and response time analyses include all incidents regardless of how they were originally entered or imported into the system, providing more reliable data for operational decision-making and compliance reporting.

4 - Work Order Items Data Source

  • What - A new Work Order Items data source has been added to Ad Hoc reporting, providing detailed visibility into the one-to-many relationship between Work Orders and their associated inventory items and other parts. This unified data source consolidates both inventory-based items and non-inventory "Other Parts" into a single dataset for comprehensive item-level analysis.
  • Why - Previously, Ad Hoc users could only report on Work Orders at the parent level without access to the individual parts and materials linked to each work order. This limitation prevented detailed analysis of material usage patterns, cost tracking at the item level, and operational performance metrics that require parts-level data visibility.
  • How - The Work Order Items data source appears automatically as a child data source under Work Orders for users with existing Ad Hoc permissions.
    • Navigate to Ad Hoc Reports and select Work Orders as your primary data source
    • Choose Work Order Items as a related child data source to access item-level details
    • Use the Type field to distinguish between "Inventory" items and "Other Part" entries
    • Apply standard Ad Hoc functionality including filtering, grouping, and summary calculations
    • Create aggregations using quantity and cost fields for material usage and expense analysis
  • Use Case - A fleet maintenance manager can generate monthly parts consumption reports by joining Work Orders with Work Order Items to analyze which inventory items are most frequently used across different vehicle types and identify cost trends. Additionally, procurement staff can create quarterly reports summarizing total material costs by grouping Work Order Items by type and calculating aggregate expenses to support budget planning and vendor negotiations.

5 - Work Order Comments Data Source

  • What - A new Work Order Comments data source has been added as a child table under Work Orders in Ad Hoc reporting, providing access to comment records associated with individual work orders. This data source exposes the one-to-many relationship between Work Orders and their comment history, including comment text, creation timestamps, and author information.
  • Why - Agencies needed the ability to review, audit, and analyze technician communication, operational feedback, and activity history at scale rather than viewing comments individually within the Work Orders interface. This enhancement enables systematic analysis of comment patterns, communication trends, and operational insights across multiple work orders and time periods.
  • How - The Work Order Comments data source automatically appears as a child option when selecting Work Orders as your primary data source.
    • Navigate to Ad Hoc Reports and select Work Orders as your primary data source
    • Choose Work Order Comments as a related child data source to access comment details
    • Filter and analyze using available fields: Id, Created At, Created By, and Comment text
    • Apply standard Ad Hoc functionality including criteria filtering, grouping by author or date ranges, and summary calculations
    • Create reports combining work order metadata with associated comment activity
  • Use Case - A fleet maintenance supervisor can generate monthly communication analysis reports by grouping Work Order Comments by technician to identify which staff members provide the most detailed documentation and track common issues mentioned across multiple work orders. Additionally, quality assurance teams can create audit reports filtering comments by date ranges and searching for specific keywords to ensure proper maintenance procedures are being followed and documented consistently.

6 - Data Source Join Between Inspections and Invoicing

  • What - A new join relationship has been established between the Inspections and Invoices data sources in Ad Hoc reporting, allowing users to directly connect inspection records with their corresponding billing information. This enhancement enables cross-module reporting between the Inspections and Invoicing systems within a single Ad Hoc report.
  • Why - Users previously could not correlate inspection activities with their associated invoicing data in a unified report, requiring separate analyses or manual data compilation. This join capability enables comprehensive financial and operational reporting that connects inspection work with billing outcomes for better revenue tracking and cost analysis.
  • How - The join between Inspections and Invoices is automatically available when building Ad Hoc reports.
    • Navigate to Ad Hoc Reports and select Inspections as your primary data source
    • Invoices will now appear as an available related data source for joining
    • Configure your report to include fields from both Inspections and Invoices modules
    • Apply filters, grouping, and summary calculations across both data sources as needed
  • Use Case - A fire prevention bureau can create comprehensive monthly reports showing inspection activities alongside their corresponding invoice amounts to track revenue generated from different types of inspections. Finance teams can also analyze inspection-to-billing cycles by joining these data sources to identify delays between completed inspections and invoice generation for improved cash flow management.


New Feature Enhancement:


1 - Extended Custom Columns to Criteria

  • What - Custom Columns created in Ad Hoc reports can now be used as filters within the Criteria section, allowing users to apply conditions and comparisons to computed values just like standard data source fields. This enhancement automatically makes all user-defined Custom Columns available in the Criteria dropdown with appropriate operators based on their data type.
  • Why - Previously, users could create Custom Columns using formulas and expressions but couldn't filter reports based on these calculated values, limiting the ability to refine results using computed data. This restriction prevented advanced filtering scenarios such as showing only records where a calculated date difference exceeds a specific threshold or filtering by concatenated field values.
  • How - Custom Columns automatically become available in Criteria once created, with no additional setup required.
    • Create your Custom Column using formulas or expressions in the Columns section
    • Navigate to the Criteria section where your Custom Column will now appear in the dropdown
    • Select your Custom Column and choose appropriate operators based on its data type (numeric, text, or date/time)
    • Apply multiple filters using different Custom Columns within the same report
    • The filtering evaluates on computed values after calculations are performed
  • Use Case - An EMS supervisor can create a Custom Column calculating response time differences between dispatch and arrival times, then use Criteria to filter for only incidents where response time exceeded 8 minutes for performance analysis. Similarly, a fire department analyst could create a Custom Column concatenating incident type and location data, then filter reports to focus on specific combinations like "Structure Fire - Downtown District" for targeted operational reviews.

2 - Extended Custom Columns to Filters

  • What - Custom Columns created in Ad Hoc reports are now available as interactive Filters, allowing users to dynamically refine report outputs based on computed values from their custom calculations. Custom Columns appear in the Filters transfer list with type-appropriate operators and support multi-filter combinations within the same report.
  • Why - Users could previously create Custom Columns for calculations like date differences and text concatenations but couldn't use these computed values to filter their data interactively. This limitation restricted drill-down analysis and dashboard exploration capabilities, preventing users from dynamically refining results based on their calculated logic.
  • How - Custom Columns automatically become available as Filters once created in the report.
    • Create your Custom Column in the Columns section using desired formulas or expressions
    • Navigate to the Filters section where your Custom Column will appear in the left transfer list
    • Move your Custom Column to the active filters area on the right
    • Select appropriate operators based on the column's data type (numeric, text, boolean, or date/time)
    • Combine Custom Column filters with standard field filters using AND/OR logic
    • Use these filters in both standalone reports and embedded dashboard widgets
  • Use Case - A fire department analyst can create a Custom Column calculating "Days Since Last Inspection" for apparatus maintenance, then use it as a Filter to dynamically display only vehicles requiring attention within the next 30 days. Similarly, an EMS supervisor could create a Custom Column combining incident priority and response district information, then filter dashboard views to focus on high priority calls in specific coverage areas for real-time operational decision-making.

    • Related Articles

    • Reports Updates

      Video No video this month. All new enhancements are new Data Sources or new Fields found here when creating an Ad-Hoc report: Enhancements: 1) NFIRS EMS Data Source with NERIS Fields What - The NFIRS EMS data source in Ad Hoc reporting has been ...

    • ITM Reports - Overview

      Purpose Statement This guide demonstrates the overall navigation of ITM Reports within First Due, providing fire department personnel with comprehensive instructions for managing, reviewing, and processing fire protection system inspection reports. ...

    • Reports Module Updates

      Video New Feature What: Multi-Agency Dataset Sharing Tool Why: Agencies with a Parent / Child data relationship want control of what data is being shared. How: Go to the Reports Module > Set Up > Multi-Agency Dataset Sharing Select the Parent Agency ...

    • Reports Module Updates - Sept 2025

      Video New Feature 1 - New Email Option for Timed-out Ad Hoc Downloads What - A new fallback email delivery system has been implemented for Ad Hoc report downloads that experience timeout errors during file generation. When users attempt to download ...

    • Release Notes - Reports Module

      In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. Video New Features 1. Apply multi-function delete options when deleting Reports. What: A new two-step delete process when using the ...