Unified Dispatcher Interface for Incident Information Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Emergency call handlers are overwhelmed by excessive and irrelevant information from disparate systems, requiring them to navigate multiple vendor-specific user interfaces and input/output devices, which complicates incident response.

Innovation Solution

A system that uses historical user interface interactions to generate a unified, card-based interface aggregating relevant UI objects from different systems, allowing dispatchers to interact with them through a single interface while learning from user preferences and behaviors using online machine learning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If dispatchers access multiple vendor-specific systems (call taking, CAD, radio console, situation awareness, R&E), then comprehensive incident information is available, but information overload and interface complexity increase

Engineering Contradiction:
Improvecomprehensive incident informationVSAvoidinterface complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges multiple vendor-specific systems (call taking, CAD, radio console, situation awareness, R&E) into a single unified user interface. This consolidation presents comprehensive incident information from all systems while eliminating the need for dispatchers to navigate multiple separate interfaces, directly resolving the contradiction between information completeness and interface complexity

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified interface serves as a universal access point that performs multiple functions simultaneously - displaying incident details, managing responder assignments, monitoring radio communications, accessing situation awareness data, and retrieving records and evidence. This single interface replaces multiple vendor-specific interfaces, maintaining comprehensive functionality while reducing overall system complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If all systems and interfaces are made available to dispatchers, then complete incident data is accessible, but navigation time and operational efficiency decrease

Engineering Contradiction:
Improveincident data accessibilityVSAvoidnavigation time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-organizing and pre-positioning all incident-related information and controls within a single unified interface. Dispatchers do not need to navigate through multiple systems or perform search operations - all necessary data and functions are immediately available in one location, eliminating navigation time while maintaining complete data accessibility

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The unified interface segments and organizes information from multiple systems into logical, easily accessible categories. Incident details, responder information, communication tools, and evidence records are presented in structured sections within the single interface, allowing dispatchers to quickly locate specific information without sifting through unrelated data or switching between systems

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11720375B2System and method for intelligently identifying and dynamically presenting incident and unit information to a public safety user based on historical user interface interactions
Publication Date: 2023.08.08 MOTOROLA SOLUTIONS INC
  • US11720375B2 patent drawing
  • US11720375B2 patent drawing
  • US11720375B2 patent drawing

AI summary

Techniques for generating a user interface (UI) for a public safety user are provided. An event trigger may be received at a computing device associated with a public safety user. The event trigger may be associated with a public safety event. Historical interaction with at least one UI object by the public safety user when handling previous event triggers of the same type as the received event trigger may be determined. The historical interaction may be retrieved from a historical UI interaction data store. UI objects that the public safety user may interact with to handle the received event trigger may be identified based on the determined historical interaction. A UI may be generated to handle the received event trigger, the UI to handle the received event trigger including the identified UI objects.