I'll format these as copyable bullet points for each section:
What: This feature introduces an email-based one-time password (OTP) option for multi-factor authentication (MFA), providing a secure alternative to authenticator apps for users without access to smartphones or tablets, while maintaining compliance with FedRAMP security standards and requiring users to provide both their password and an email-delivered one-time passcode for each login.
Why: This enhancement was implemented due to customer request to address critical accessibility needs for agencies where personnel may not have smart devices available, ensuring all users can maintain secure access to the system regardless of their device availability.
How:
Use Case: A fire department with field personnel who don't carry personal smartphones can now enable secure MFA access, allowing crew members to log in from station computers using their email-delivered codes while maintaining the required security compliance for their agency.
What: This feature introduces centralized role and permission management capabilities that allow parent agencies to efficiently manage and propagate role updates across all child and sub-agencies from a single administrative interface, eliminating the need for individual agency-level role management in complex organizational structures.
Why: This feature was developed due to customer request to address the significant administrative burden of manually updating roles across large-scale deployments, particularly beneficial for configurations with hundreds of participating agencies.
How
Use Case: A state-level fire coordinator managing 280 municipal fire departments can create and deploy updated incident commander roles across all participating agencies in a single operation, ensuring consistent permissions and capabilities statewide without requiring individual agency administrators to manually update their systems.
What: This feature enhancement provides client administrators with comprehensive management capabilities for saved views created by any user within their organization, including the ability to view, modify, and delete saved views regardless of the original creator, eliminating previous restrictions that required users to manage their own saved views exclusively.
Why: This enhancement was implemented due to customer request to streamline administrative oversight and improve saved view governance, particularly when addressing situations where view creators are unavailable or no longer with the organization.
How
Use Case: When a longtime shift supervisor leaves the department, the fire chief can immediately access and reassign that supervisor's critical operational saved views to current personnel, ensuring continuity of important dashboard configurations and preventing loss of customized operational interfaces.
What: This release introduces enhanced role management capabilities for administrators including the ability to filter roles by active and inactive status, view real-time user assignment counts for each role, and reactivate previously inactive roles, providing comprehensive role lifecycle management and improved visibility into role utilization patterns.
Why: This enhancement was implemented due to customer request to improve role administration workflows and provide better visibility into role usage across the system, enabling more informed decisions about role maintenance and optimization.
How
Use Case: A department administrator preparing for annual role review can filter to view all inactive roles, identify which ones have zero user assignments for potential deletion, and reactivate seasonal roles like "Training Officer" that were temporarily disabled during low-activity periods, optimizing the role structure based on actual usage data.
What: This feature enhances the import wizard by adding the ability to import personnel and user information simultaneously through a single streamlined import process, significantly reducing the manual effort required during system implementation and eliminating the need for multiple separate import operations.
Why: This enhancement was implemented due to customer request to reduce the administrative burden during system setup, as the previous process required performing three separate imports for ranks, users, and personnel information.
How
Use Case: During a new agency implementation, administrators can now import their entire roster of 200+ personnel with corresponding user accounts in a single operation, reducing setup time from hours to minutes while ensuring data consistency across both personnel records and user profiles.
What: The Import Wizard has been enhanced to support hydrant data imports directly from Emergency Reporting, a widely used fire department management system, allowing departments to seamlessly transfer their existing hydrant information into the platform while maintaining data accuracy and eliminating manual entry requirements.
Why: This feature was developed due to customer request to enable direct data migration from Emergency Reporting systems, ensuring fire departments can preserve their existing hydrant data investments when transitioning to our platform.
How:
Use Case: A fire department transitioning from Emergency Reporting can import their database of 500+ hydrant locations with complete flow rates, pressure data, and maintenance history, ensuring continuity of critical water supply information without requiring manual re-entry of years of collected data.
What: This enhancement transforms the existing ER Occupancy Import Wizard into a flexible, universal occupancy data import tool that accepts CSV files from any source while preserving legacy information, and includes a new value mapping interface that allows direct mapping of legacy RMS occupancy data to Enhanced Preplan fields during import.
Why: This enhancement was implemented due to customer request to improve data migration capabilities for clients transitioning from various record management systems, eliminating the need for technical services intervention in data mapping processes.
How:
Use Case: An agency migrating from a legacy RMS can import 1,000+ occupancy records with custom field mappings, automatically transforming their historical data structure to match Enhanced Preplan requirements without requiring technical services support or manual spreadsheet manipulation.
What: This feature enhances the ER Equipment import functionality by introducing an intelligent mapping interface that enables users to associate imported equipment data with existing system entities such as users, apparatus, and stations, streamlining the data import process through automated association capabilities.
Why: This enhancement was implemented due to customer request to improve the equipment import workflow by enabling proper data relationships during import, building upon successful mapping implementations from the occupancy import wizard.
How
Use Case: A fire department can import their complete equipment inventory from Emergency Reporting and automatically associate each piece of equipment with the correct apparatus and assigned personnel, ensuring accurate equipment tracking and accountability from day one of system deployment.