Skip to content
In active development
Motrix Emergency

Offline fleet operations for hurricane response, storm preparation, and disaster recovery.

Motrix Emergency is the incident-operations edition of Motrix: a local-first desktop app built to keep command staff and field teams operating when internet and cellular service are unreliable.

Built for agencies preparing for severe weather and emergency response operations. Motrix Emergency brings offline fleet coordination, road status visibility, statewide map operations, and pre/post-event data handoff into one operational workspace.

Offline First Design
Incident Based Operations
Florida Statewide Basemap
Current Core Features

Built for command desks, staging operations, and field coordination during outages.

The Emergency edition is structured around operational continuity when cloud-only dispatch and browser workflows are not enough.

Incident Command Desk

Create incidents, set the active operational period, and separate vehicles, drivers, check-ins, assignments, work orders, and road reports by incident.

Fleet Operations

Track vehicle rosters, driver rosters, assignments, emergency work orders, and deployment status for staging, field response, and out-of-service conditions.

Vehicle Check-Ins

Capture manual check-ins with driver status, fuel level, last-known location, and optional map coordinates for live operational visibility.

Road Passability Reporting

Log blocked, limited, or open routes with severity, timestamps, reporter information, location notes, and optional coordinates for post-event review and sync-back.

Offline Statewide Mapping

Use a working Florida PMTiles basemap with local asset handling, active basemap switching, and no live web-map dependency during operations.

Emergency Bundle Import / Export

Prepare before the storm by importing operational data, then export structured bundles after field operations for Motrix Cloud handoff and sync-back workflows.

Operational Model

Designed around the incident, not the normal workday.

Pre-storm readiness Import fleet data, basemap packs, and overlay datasets before connectivity becomes uncertain.
Landfall and response Keep road status, vehicle deployments, and field check-ins moving from a local-first desktop command station.
Recovery and sync-back Preserve road reports, attachments, work orders, and operational notes so the event history can be exported back into the broader Motrix workflow.
Feature Direction

What the Emergency edition covers now

These are the product pillars reflected in the current build and near-term direction.

Incident and fleet coordination

  • Vehicle and driver roster management
  • Vehicle-to-driver assignments for operational periods
  • Emergency and recovery work order tracking
  • Vehicle status visibility for staging, deployment, and out-of-service conditions

Map-driven field reporting

  • Create road reports directly from the map by dropping a pin and completing the sidebar workflow
  • Capture closures, debris, flooding, and restricted routes with structured severity tracking
  • Store location descriptions with optional coordinates for later review and export

Local evidence and documentation

  • Attach photos and documents to road reports and work orders
  • Keep files stored locally for offline access during the operational period
  • Support future FEMA, audit, and after-action documentation workflows

Desktop foundation

  • Electron desktop application with separated main process, preload bridge, and renderer
  • SQLite-backed local data for incidents, fleet records, check-ins, work orders, and attachments
  • Basemap pack handling for future larger state and regional offline map packs
Cloud + Emergency

How Motrix Emergency fits with Motrix Cloud

This is meant to complement the core Motrix product, not replace it.

Before the event

Prepare and export

Motrix Cloud becomes the system of preparation, while Motrix Emergency becomes the field-ready operational package.

During the event

Keep operating offline

The emergency desktop app is designed to continue working through internet and cellular outages while command staff coordinate incidents locally.

After the event

Sync back and document

Operational history, road reports, check-ins, and attachments can be exported back out to support recovery, reporting, and future sync-back workflows.

What comes next

The current build is functional, but still evolving.

Near-term product direction includes direct Motrix Cloud export/import workflows, expanded inspection and DVIR support, stronger reporting/export options, real operational datasets, and Windows-first field validation.

  • Motrix Cloud export/import workflow for emergency operations
  • Sync-back from Motrix Emergency to Motrix Cloud after operations
  • Additional inspections and offline reporting workflows
  • Expanded field validation with real emergency operations use cases