Synthesizing Aerial Telemetry into Mission-Critical Dispatch Operations
A unified command interface integrating real-time drone intelligence with ground operations to enhance situational awareness for emergency responders.
RoleLead Researcher & Designer
TimelineMay 2025 - May 2026
MethodsContextual Inquiry, Semi-Structured Interviews, Ride-Alongs, Affinity Mapping, Journey Mapping, Persona Development, Task Analysis, Competitive Analysis, Literature Review, Information Architecture, Storyboarding, Low-Fi Prototyping, High-Fi Prototyping, Usability Testing, Iterative Design
Tech StackLeaflet.js, D3, HTML/CSS
Overview
What should a drone-integrated dispatch system look like?
Police departments are increasingly deploying drones for situational awareness during active incidents. But the aerial intelligence these drones capture often fails to reach dispatchers in real-time because it exists in separate systems operated by specialized drone pilots.
My thesis explores how to synthesize multiple telemetry streams, including live drone feeds, officer positions, and incident data, into a unified interface that enhances rather than overwhelms dispatcher decision-making.
"How do I consolidate fragmented information streams into a single pane of glass that enhances situational awareness without increasing cognitive load?"
Problem
Managing Information Overload in High-Stakes Response
Police dispatchers coordinate officer response while managing overwhelming streams of incoming information: 911 calls, CAD system updates, radio communications, and incident notes. When drones capture aerial footage during active incidents, that critical intelligence often remains siloed.
30+
Officer interviews conducted
17
Officer ride-alongs
6
Critical workflow themes
4
Primary personas
Research
Understanding Dispatch Operations Through Contextual Inquiry
I conducted semi-structured interviews with 30+ personnel across seven agencies, including Atlanta PD, Georgia Tech PD, and Georgia State Patrol, and completed 17 officer ride-along observations to understand current workflows, pain points, and information needs during active incidents.
Research Methods
Semi-structured Interviews: 30+ officers across patrol, dispatch, and drone operations
Contextual Inquiry: 17 ride-alongs observing officer operations in real-time
Affinity Mapping: Synthesized 120+ data points into 6 critical themes
Journey Mapping: Documented information flow during multi-unit responses
Key Insights
Insight 01
Fragmentation Over Volume
Dispatchers experienced cognitive overload not from the volume of information, but from its fragmentation across multiple systems. Consolidation was the design opportunity.
Insight 02
Trust in Aerial Perspective
Officers expressed high trust in drone footage for situational awareness but frustration that it rarely reached dispatchers who could coordinate response.
Insight 03
Priority Triage is Mental
Dispatchers maintain priority rankings mentally rather than in any system. Visual priority indicators could reduce cognitive burden.
Research
How I Got There: Research Artifacts
Affinity map: 120+ data points synthesized into 6 themes
Dispatcher journey map: information flow during incident response
Officer journey map: field response and communication touchpoints
Solution
OVERWATCH: A Unified Interface for Situational Awareness
OVERWATCH creates a single pane of glass where dispatchers see live drone feeds, interactive mapping with officer positions, and AI-assisted query capabilities. The system automatically prioritizes incidents by severity.
Information Hierarchy: Single Pane of Glass
Three-column interface: Calls for Service and Incident Summary (left) | Suspect Details and Activity (center) | Map and Drone feed (right).
Live Drone Feed Integration
Real-time aerial footage with officer position overlay and automated suspect tracking.
Interactive Mapping
Leaflet.js-powered map showing real-time officer positions and incident locations.
AI Query Interface
Natural language queries to surface incident history and officer availability.
Priority Escalation
Color-coded alerts with automated severity assessment and escalation workflows.
Interface Architecture
OVERWATCH is a three-column dashboard built for officers operating in high-stress, time-critical scenarios. Each panel serves a distinct operational purpose, and their placement reflects how officers naturally scan for information during active incidents. Use the arrows below to explore each component.
Login Screen
The session begins with operator identification. This screen gates access and ties all subsequent actions to a named officer for audit trails and research logging.
Operator identification screen with session start button
Operational Workflow
Officer enters their name before the session starts
All interactions are logged and associated with this identifier
Session data can be exported for after-action review
Design Decisions
Single required field reduces friction at shift start
Blue accent border signals system readiness
Research disclosure is upfront and transparent
Example: Officer Martinez begins her shift by entering her name. The system logs her session start time (08:00) and will attribute all notes, queries, and status changes to her badge for the supervisor's shift report.
Calls for Service (Left Column)
The CAD queue displays all active incidents, sorted by priority. Officers can scan pending calls and select which to focus on. This panel is marked as a "stationary card," meaning it remains visible even when the interface shifts to driving mode.
CAD queue showing active 10-71 Armed Person call (red stripe) with pending incidents below
Operational Workflow
Scan queue to identify highest-priority incidents
Click a call to load its details into the center column
View call ID, time received, 10-code, location, and assigned units at a glance
Access "Today's Calls" for historical context on repeat locations
Monitor pending vs. active status for resource allocation
Design Decisions
Priority color stripe (red, amber, green) provides instant severity assessment
Monospace font for IDs ensures character alignment and reduces misreads
Active call is highlighted with a distinct border state
Compact mode collapses to headline summary for driving scenarios
Fixed position prevents accidental scroll during vehicle motion
Example: A 10-71 (Armed Person) appears at the top of the queue with a red stripe. The officer clicks it, and the Incident Summary panel populates with suspect description, location, and weapon status. The drone feed automatically switches to the associated aerial view.
Incident Summary (Left Column)
The primary incident card displays location, suspect description, weapon status, and caller information. This is the first place officers look when assigned to a call.
Primary incident card displaying location, suspect description, weapon status, and caller information
Operational Workflow
Confirm location before responding
Note suspect description for identification on arrival
Check weapon field to determine tactical approach
Review caller name and phone for callback if needed
Verify current disposition (IN SERVICE, CLEAR, etc.)
Design Decisions
Three-row grid (Location, Suspect, Weapon) matches radio briefing order
Call details strip expands to show caller info and signal code
CFS ID displayed in header for cross-reference with dispatch
Fixed card height prevents layout shift when switching calls
Weapon field uses warning color when firearm is logged
Example: Officer receives assignment to CFS 2401-001234. The incident summary shows: Location: Student Center lobby. Suspect: Black male, red hoodie, blue jeans. Weapon: FIREARM LOGGED, handgun drawn. Caller: DOMINIC at 404-555-0142. The officer now has everything needed to approach safely.
Suspect Details (Center Column)
A dedicated panel for suspect identification, including physical attributes, and database query results. Supports NCIC/GCIC lookups for warrant status and prior contacts.
Suspect details panel with NCIC query results showing name, warrant status, and prior contacts
Operational Workflow
Run NCIC/GCIC query when suspect name is obtained
Check warrant status before contact
Review prior contacts and flags for officer safety
Update physical description as new intel arrives
Upload suspect photo from body camera or witness
Design Decisions
Two-column layout: photo and name on left, attributes on right
Warrant status uses color-coded badges (unknown, clear, active)
"Awaiting query" state makes clear when data is pending vs. unavailable
Photo placeholder shows silhouette until image is uploaded
Priors/flags field highlights repeat offenders
Example: Dispatch provides a partial name from a witness. The officer types "run DL GA-1234567" into the activity input. NCIC returns: James Wilson, DOB 04/15/1989, active warrant for aggravated assault. The suspect details panel updates with this information and flags the active warrant in red.
Activity (Center Column)
A unified stream combining dispatch updates and officer notes. Supports tag-based filtering, voice dictation, and natural language commands for plate runs and license queries.
Unified activity stream with color-coded tags (LOCATION, SUSPECT, WEAPON, ACTION) and timestamp entries
Operational Workflow
Monitor incoming dispatch updates in real-time
Add officer notes via keyboard or voice dictation
Run plate queries with "run plate ABC1234" syntax
Filter by tag (LOCATION, SUSPECT, WEAPON, OFFICER, NCIC, ACTION)
Search activity history for specific keywords
Design Decisions
Color-coded badges for each note type enable rapid scanning
Timestamp on every entry creates audit trail
Voice dictation button allows hands-free input while driving
Tag filter strip uses toggle pattern for multi-select
Enter key submits note without requiring mouse click
Expandable text area for longer narratives
Example: The officer arrives on scene and taps the microphone button. She dictates: "Suspect fled on foot eastbound toward parking deck." The note is auto-tagged as LOCATION and appears in the activity stream with timestamp 10:28 AM. Other units see this update immediately.
Map (Right Column)
A Leaflet.js-powered interactive map showing incident location, officer positions, and patrol zones. Supports zoom controls and flag markers for key locations.
Leaflet.js interactive map showing incident location and nearby unit positions
Operational Workflow
Identify incident location relative to patrol position
View nearby unit locations for backup coordination
Zoom to street level for approach planning
Track suspect movement when correlated with drone feed
Review patrol zone boundaries
Design Decisions
Dark map tiles reduce glare during night shifts
Floating zoom buttons avoid obscuring map center
Right column placement keeps map adjacent to drone for spatial correlation
Collapsible sidebar allows map to expand when detail is needed
Compact mode shows unit count and flag summary
Example: The map shows a red marker at the Student Center with 8 nearby units. The officer zooms in and sees Unit 12 is 200 meters east, Unit 14 is approaching from the north. She coordinates on radio: "Unit 12, hold at the east exit. I'll approach from south."
Drone (Right Column)
Live aerial video feed with HUD overlay showing battery, altitude, and distance. Supports thermal imaging palettes for low-light and concealment scenarios.
Live drone feed panel with battery, altitude, distance metrics and thermal palette selector
Operational Workflow
Monitor suspect position from aerial perspective
Switch thermal palettes for night or concealment scenarios
Check drone battery and signal status before relying on feed
Request drone deployment if not already on scene
Correlate aerial view with ground position via map
Design Decisions
HUD overlay shows critical metrics without obscuring video
Video controls are minimal since feed is typically passive monitoring
Example: The drone feed shows a parking garage at 260 ft altitude. The officer switches to white-hot thermal and spots a heat signature behind a vehicle on level 3. She radios: "Suspect is on parking level 3, northwest corner, behind the silver sedan." Ground units adjust approach accordingly.
Threat Indicator (Subheader)
A real-time threat assessment display in the subheader that shows threat level (1-10 scale), priority code, and incident status. This component provides immediate situational awareness without requiring officers to scan multiple panels.
Threat assessment showing CRITICAL level (10) with priority pill displaying 10-code and status
Operational Workflow
Check threat score (1-10) before approaching scene
Monitor priority pill for current 10-code and severity level
Use threat level to determine tactical approach
Brief backup units on threat status en route
Design Decisions
Threat bar uses color gradient (green to red) for peripheral vision scanning
Priority pill shows 10-code with color-coded severity (red for high, amber for medium, green for low)
Persistent subheader placement ensures visibility across all interface states
Example: The threat score shows 10 (CRITICAL) in red with a full progress bar. The priority pill displays "10-71 – HIGH PRIORITY" indicating an armed person call. The officer immediately recognizes this as a maximum-threat scenario requiring tactical approach.
Header Bar and Status Controls
The header provides system-wide controls and status indicators. Includes call duration timer, unit status dropdown, mode toggles, and quick-action buttons.
Header bar with call duration timer, time display, and mode togglesSubheader action buttons: Play Summary, Generate Handoff, Compare Incidents, Request Backup, En Route, New CFSSuggested next steps recommendation strip for tactical guidance
Key Components
Call Duration: Timer tracking time since call assignment
Status Dropdown: IN SERVICE, CLEAR, REPORT, TRAFFIC options
Mode Toggle: Switches between STATIONARY and DRIVING layouts
Voice Button: Activates voice command recognition
Action Buttons: Play Summary, Generate Handoff, Compare Incidents, Request Backup, En Route, New CFS
Design Decisions
Driving mode collapses non-essential panels for reduced distraction
Green accent for New CFS button signals constructive action
Amber accent for En Route signals transitional status
Export button allows session data download for after-action review
Modal Dialogs
OVERWATCH uses modal dialogs for complex workflows that require focused attention. Each modal dims the background and prevents interaction with the main dashboard until dismissed.
New CFS Modal: Officer-initiated call creation with location fields, call type, priority, and optional suspect photo upload
Officer-initiated call creation modal with incident information, flags, and narrative fields
Today's Calls Modal: Historical view of all calls handled during the current shift
Handoff Report Modal: Generates a formatted report for shift change or backup briefing, supports copy-to-clipboard and email
Generated handoff report showing incident details, location history, and actions taken
Incident Comparison Modal: Side-by-side comparison of multiple incidents for pattern recognition
Side-by-side incident comparison matrix showing pattern recognition across similar cases
Keyboard Shortcuts Modal: Reference guide for power users navigating via keyboard
Example: At shift change, the outgoing officer clicks "Generate Handoff." The modal produces a report summarizing current call status, suspect description, weapon intel, and unit positions. She copies this to clipboard and sends it to the incoming officer via MDT.
Design System
A dark, utilitarian interface system built for high-stakes dispatch environments. Every decision optimizes for rapid threat scanning, night-shift legibility, and zero ambiguity under stress. No decorative elements, no sci-fi chrome.
Color System
Dark backgrounds reduce eye strain during 12-hour shifts. Priority colors are WCAG AA compliant and distinguishable for colorblind operators.
Background Surfaces
--bg-input
--bg-primary
--bg-panel
Priority Colors
Critical
Warning
Action
Resolved
Typography
Helvetica Neue throughout the interface. Clean, legible, and optimized for rapid scanning under stress.
Display / Helvetica Neue Bold
OVERWATCH
Body / Helvetica Neue Regular
Unit 42 responding to 10-50 at North Ave. ETA 3 min.
Data / Helvetica Neue Medium
CFS-2024-0847 | 14:32:07 | 10-50PI
Design Decisions
Critical Choices and Trade-offs
The design process involved several key decisions that balanced dispatcher needs with technical constraints and organizational realities.
Information Hierarchy
The primary challenge was determining what information deserves screen real estate. Through iterative testing with dispatch staff, I established a hierarchy: active incident list (left), map with positions (center), drone feed (right when active).
Alert Escalation Logic
I designed a three-tier alert system: Priority 1 (red) for immediate threats, Priority 2 (yellow) for developing situations, and Priority 3 (blue) for routine calls. The system automatically suggests drone deployment for Priority 1 incidents.
Priority States: Color-Coded Response System
Priority 1
Immediate Threat (Red)
Auto-triggers drone deployment, escalates to supervisor
Priority 2
Developing Situation (Yellow)
Monitored status, drone available on request
Priority 3
Routine Call (Blue)
Standard dispatch, no aerial support needed
Resolved
Closed Incident (Gray)
Archived for reporting and analysis
Outcomes
Research Impact and Next Steps
This thesis work informs future police-drone integration research and contributes to HCI best practices for emergency response systems.
6
Design recommendations produced
17
Officer ride-alongs conducted
30+
Officer interviews completed
2026
Defense/public safety impact planned
Reflection
What I Learned
Domain Expertise Takes Time
Understanding dispatch operations required significant immersion. The ride-alongs were invaluable for understanding the rhythm and pressure of the work in ways interviews couldn't capture.
Consolidation Over Addition
The instinct is to add features. The insight from research was that dispatchers needed fewer systems with better integration, not new capabilities.
High-Stakes Design is Different
Designing for emergency response has no room for error or confusion. Every interaction must be immediately clear under stress. This discipline improved my work across all domains.