Overview

iOS 6.1.3 introduces MDT UI v1 — the new V5 map-first iPad experience for bidirectional unit users. It brings Incident and Unit lists onto the map, statusing from a persistent map status bar, a redesigned Incident Details view with Locations, Units, Building Story, Route, Closest Hydrants, Preplan, Notes, and Take Command, and quick actions for Edit Preplan, Street View, and Quick Route. The new experience is rolled out by client through Remote Config, starting with the Verdugo CAD agencies.

New Features

V5 iPad MDT Experience

• What - Added a new map-first MDT experience for eligible iPad unit users using supported bidirectional CAD workflows. The redesigned interface makes the map the primary workspace and introduces updated navigation, incident and unit panels, status controls, and incident details while maintaining access to existing responder functionality.
• Why - A map-first interface gives responders operating from an iPad a more operationally focused workspace where incident information, unit locations, status controls, and response tools can be accessed without repeatedly moving between separate screens.
• How
  • The new MDT experience is available to eligible iPad unit users using supported bidirectional workflows.
  • Access is controlled at the organization level and can be enabled without requiring an application update.
  • Eligible users are automatically directed to the new interface when it is enabled for their organization.
  • Users who are not eligible or whose organization has not enabled the new experience continue using the existing interface.
• Use Case - A unit operating from an iPad can use the map as its primary response workspace, review active incidents and units, update its response status, and access incident information without leaving the map-based interface.

Map-First MDT Interface

• What - Added the new V5 map shell with a persistent map surface, left-side navigation, pan and zoom functionality, and animated information panels designed specifically for the new iPad MDT experience.
• Why - Keeping the map at the center of the interface allows responders to maintain geographic and operational awareness while accessing other response information.
• How
  • Open the application on an eligible iPad with the new MDT experience enabled.
  • The Map opens as the primary workspace.
  • Pan or zoom the map using the existing map controls and gestures.
  • Use the left-side navigation and available panels to access additional responder functionality.
• Use Case - While responding to an incident, personnel can maintain a continuous view of the response area while opening incident, unit, and other operational information as panels over the map.

MDT Map Toolbar and Address Search

• What - Added map toolbar actions and address search directly to the new MDT map interface, providing access to common map tools without leaving the primary map workspace.
• Why - Providing map tools and address search directly from the MDT home screen reduces navigation and allows responders to quickly locate addresses and interact with the map during response operations.
• How
  • Open the Map in the new MDT interface.
  • Use the available Map Toolbar controls for supported map actions.
  • Select Address Search to locate an address.
  • Search results are displayed within the map workflow.
• Use Case - A responder can search for a nearby address while maintaining the current incident map and operational context rather than navigating to another screen.

MDT Menu and Options Panel

• What - Added a Menu entry to the new left-side navigation along with an Options panel. Available menu items continue to respect the user's existing permissions.
• Why - The updated navigation provides access to additional First Due functionality while preserving the map as the primary MDT workspace and maintaining existing permission controls.
• How
  • Select Menu from the left-side navigation.
  • Review the available menu options.
  • Open Options for additional supported functionality.
  • Menu availability automatically follows the user's assigned permissions.
• Use Case - A responder can access another authorized First Due module from the MDT interface without losing the map-centered navigation experience.

Active Incidents Panel

• What - Added an Active Incidents panel to the new MDT interface with incident loading, refresh, selection, and appropriate empty and error states.
• Why - Providing active incidents directly alongside the map allows responders to quickly review current calls and select an incident without leaving their primary operational workspace.
• How
  • Open the Active Incidents panel from the new MDT interface.
  • Review the available active incidents.
  • Refresh the list when needed.
  • Select an incident to access its information.
• Use Case - A unit monitoring multiple active calls can review the incident list from the map and select the appropriate incident without navigating to a separate incident screen.

Units Panel

• What - Added a Units panel to the new MDT interface, including unit information and corresponding map pins consistent with the existing Units functionality.
• Why - Displaying units and their mapped positions from the primary MDT workspace improves resource visibility and helps responders maintain situational awareness during multi-unit incidents.
• How
  • Open the Units panel from the MDT interface.
  • Review available unit information.
  • Use the corresponding map information to view unit locations when available.
  • Continue interacting with the map while using the panel.
• Use Case - During a multi-unit response, personnel can open the Units panel and quickly identify other responding resources and their locations on the map.

Map-Based Unit Statusing

• What - Added a persistent status bar to the MDT map that allows units to update operational statuses such as Enroute, On Scene, and Transport without leaving the map. The status controls remain available even while Incident Details is open and include support for the Transport destination workflow.
• Why - Keeping status controls readily accessible reduces navigation during active response and allows unit personnel to update their operational state while continuing to view incident information and the map.
• How
  • Use the Status Bar at the bottom of the MDT map.
  • Select the appropriate unit status.
  • When selecting Transport, complete the applicable destination workflow.
  • Status controls remain available while Incident Details is open.
• Use Case - A unit arriving at an incident can select On Scene directly from the map and continue reviewing Incident Details without navigating back to another status screen.

Fullscreen Incident Details

• What - Added a redesigned fullscreen Incident Details experience to the new MDT interface, providing access to core incident information within the map-based workflow.
• Why - Bringing detailed incident information into the MDT workspace gives responders access to critical dispatch information while maintaining a consistent response-focused interface.
• How
  • Select an incident from the map or Active Incidents panel.
  • Open Incident Details.
  • Review the available incident information.
  • Return to the map or use the associated Details Bar to access additional incident tools.
• Use Case - While responding to a call, personnel can open the incident and review detailed dispatch information directly from the MDT interface.

Incident Details Bar

• What - Added an Incident Details Bar that provides incident, unit, radio, and destination information through compact chips and serves as the container for additional incident information and actions.
• Why - Presenting important response information in a compact persistent area allows responders to reference key details without unnecessarily covering the map.
• How
  • Open an incident within the new MDT interface.
  • Use the Details Bar to review available incident, unit, radio, and destination information.
  • Select available options to open additional incident panels and actions.
  • The map and unit status controls remain accessible as supported.
• Use Case - A responder can reference radio and destination information while continuing to monitor the incident map and unit status controls.

Incident Locations

• What - Added a Locations section to the new Incident Details experience that displays available address, location, and caller information associated with the incident.
• Why - Consolidating location and caller information within Incident Details gives responders quick access to important dispatch information from the primary MDT workflow.
• How
  • Open Incident Details.
  • Select Locations.
  • Review the available address, location, and caller information.
• Use Case - A responder can quickly verify the dispatched address and available caller information before arriving on scene.

Incident Units and Unit Positions

• What - Added a Units section to Incident Details with Unit Positions, search and filtering capabilities, and Assign/Unassign functionality.
• Why - Providing unit assignments and positions within the incident workspace helps users understand resource deployment and manage applicable unit assignments without leaving Incident Details.
• How
  • Open Incident Details.
  • Select Units.
  • Search or filter the displayed units as needed.
  • Review available Unit Positions.
  • Use Assign or Unassign when permitted and operationally appropriate.
• Use Case - During an expanding incident, an authorized user can review unit positions and manage assignments directly from the incident's Units section.

Building Story in Incident Details

• What - Added a Building Story section to the new Incident Details experience. The section is automatically hidden when no Building Story information is available for the incident location.
• Why - Providing Building Story information within the MDT incident workflow gives responders additional property context while avoiding unnecessary interface elements when no information exists.
• How
  • Open Incident Details.
  • Select Building Story when the option is available.
  • Review the available property information.
  • If no Building Story exists, the option is automatically hidden.
• Use Case - Responders approaching a preplanned occupancy can review available Building Story information from Incident Details before arrival.

Incident Notes

• What - Added a Notes section to the new Incident Details experience for reviewing available incident call notes.
• Why - Call notes can contain important supplemental information that may affect response operations. Making them directly available from Incident Details reduces the need to navigate away from the active incident.
• How
  • Open Incident Details.
  • Select Notes.
  • Review the available incident call notes.
• Use Case - A responder can review additional information supplied with the call while remaining within the active incident workflow.

Incident Routing

• What - Added Route / Calculate Directions to the Incident Details Bar, allowing responders to start the existing map-routing workflow directly from the selected incident.
• Why - Direct access to routing reduces the number of steps required to begin navigation and keeps routing integrated with the map-first MDT experience.
• How
  • Open the applicable incident.
  • Access the Details Bar.
  • Select Route or Calculate Directions.
  • Follow the existing routing workflow to the incident destination.
• Use Case - A unit receiving an unfamiliar response address can begin calculating directions directly from Incident Details without leaving the incident workflow.

Closest Hydrants

• What - Added Closest Hydrants to Incident Details, providing nearby hydrants with distance information and options to view the selected hydrant.
• Why - Quick access to nearby water supply information supports apparatus positioning and response planning during incidents where hydrant access may be required.
• How
  • Open Incident Details.
  • Select Closest Hydrants.
  • Review the available hydrants and their distances.
  • Select View for the desired hydrant.
• Use Case - An engine company responding to a structure fire can quickly review nearby hydrants and identify an appropriate water supply before arriving on scene.

Preplan Access from Incident Details

• What - Added direct Preplan access from Incident Details when preplan information is available for the occupancy associated with the incident.
• Why - Direct access to preplans allows responders to review important property and operational information without navigating away from the active incident.
• How
  • Open Incident Details.
  • Select Preplan.
  • Review the available preplan information for the incident occupancy.
• Use Case - While responding to a commercial occupancy, personnel can open its preplan directly from the active incident to review relevant building and response information.

Take Command from Incident Details

• What - Added Take Command to the new MDT Incident Details workflow, connecting eligible users to the existing Incident Command process while respecting established permissions.
• Why - Providing Take Command directly from the active incident reduces navigation and gives authorized command personnel faster access to Incident Command workflows.
• How
  • Open Incident Details.
  • Select Take Command.
  • Continue through the existing Incident Command workflow.
  • Availability is controlled by the user's existing permissions.
• Use Case - An authorized officer arriving at an incident can initiate the command workflow directly from Incident Details without navigating through a separate module.

Incident Quick Actions

• What - Added Edit Preplan, Street View, and Quick Route actions to the Incident Details Bar and associated More actions, providing faster access to frequently used incident tools.
• Why - Placing common operational actions within the active incident reduces navigation and allows responders to access location, routing, and preplan tools more efficiently.
• How
  • Open the applicable incident.
  • Access the Details Bar or More actions.
  • Select Edit Preplan, Street View, or Quick Route as needed.
  • Complete the selected workflow using the existing functionality and applicable permissions.
• Use Case - While approaching an incident, a responder can quickly open Street View to review the property, start a Quick Route, or access the preplan without leaving the active incident workspace.

Feature Enhancements

Configurable MDT Rollout

• What - Added organization-level rollout controls for the new V5 MDT interface. The experience can be enabled for selected organizations without requiring a new application version, while users outside the enabled group continue using the existing interface.
• Why - A controlled rollout allows the new MDT experience to be introduced progressively while maintaining the established interface for organizations that have not yet transitioned.
• How
  • The V5 MDT interface is enabled at the organization level for supported deployments.
  • Eligible iPad unit users automatically receive the new interface when their organization is enabled.
  • Organizations not enabled for the new experience continue using the legacy interface.
  • No end-user configuration is required.
• Use Case - An organization can transition eligible MDT users to the new map-first experience while other organizations continue operating with the established interface until they are ready to transition.

Fixes

Dispatch Data Synchronization and Account Switching

• What - Improved dispatch synchronization throughout the new MDT experience so the top bar, status controls, and Incident Details remain aligned with the current dispatch. This update also corrected system bar contrast, ensures Acknowledge opens the correct incident, and prevents unit, status, message, and dispatch information from a previous account from carrying over after account switching.
• Why - Responders need the MDT interface to consistently represent the currently active dispatch and account. Stale information from another incident or account can create confusion during active response operations.
• How
  • Continue receiving and acknowledging dispatches normally.
  • The Top Bar, status controls, and Incident Details automatically stay synchronized with the current dispatch.
  • Selecting Acknowledge opens the applicable incident.
  • When switching accounts, account-specific unit, status, message, and dispatch information is refreshed for the newly selected account.
  • No additional configuration is required.
• Use Case - A responder acknowledges a new dispatch and is taken to the correct incident with matching status and dispatch information. If the user later switches accounts, information associated with the previous account is no longer displayed in the new session.