Map & unit tracking

Know where the operation stands.

Field shares unit location and status. OPS combines that data with missions and configured weather, fire, outage, and aircraft layers.

Request access Get Field and OPS

Field · iOS and AndroidOPS · macOS and Windows

AIGIS OPS · Operational picture

Sanitized AIGIS OPS operational map with four fictional units, incident filters, map controls, and an object inspector

Representative data shown in the implemented AIGIS Field and AIGIS OPS interfaces. No production unit or responder records are pictured.

AIGIS Field

iOS and Android

Report from the response

Share location and unit status, see nearby operational context, and keep the active mission available on the device responders already carry.

AIGIS OPS

macOS and Windows

Coordinate the operating picture

Monitor more units at once, filter by incident and operational state, inspect map objects, and take permitted actions without leaving the map.

Unit context

Read unit position, status, and next action.

See where a unit last reported, whether it is moving, what work defines its current state, and which action an authorized operator can take next.

Callsign and configured operational status
Location age, tracking health, and telemetry confidence
Movement, heading, speed, and battery when reported
Current mission, capabilities, and PAR state
Recent trail points when location history is available
Route, ETA, and nearby-unit context

Connected-device fields vary by source. When supplied, AIGIS can also display reported fuel, battery voltage, engine RPM, VIN, GPS solution, firmware, and device configuration.

AIGIS OPS · Selected unit

Fictional unit data in the implemented OPS unit-inspection workflow. Actions remain permission- and connectivity-dependent.

AIGIS OPS · Operational data status

Sanitized AIGIS OPS source-health view identifying stale unit location data while leaving the map available

Representative degraded-source state using fictional data.

Data trust

A live map should show when it is no longer live.

AIGIS exposes location age, source timestamps, refresh state, and degraded or unavailable inputs so operators can distinguish current information from context that needs verification.

CurrentPosition and source are within configured age.

StaleThe last report remains visible with a warning.

UnavailableThe missing source is explicit instead of implied.

Operational conditions

See what can change the plan.

Place the conditions affecting the response over the same map used to understand units and missions, then return to a clear operating picture.

Weather

Radar, public alerts, storm cells, convective conditions, lightning, wind, flooding, heat, air quality, and tropical systems.

Fire

Observed fire activity, fire-weather alerts, dry-lightning risk, and outlook information beside the resources that may be affected.

Infrastructure

Power-outage conditions in the same operational frame as units, facilities, access routes, and community needs.

Aviation

Aircraft position, track, classification, altitude, groundspeed, heading, squawk, flight details, and temporary flight restrictions when available.

Areas of operation, points of interest, issues, SOS events, and imported GIS layers can remain visible beside the external conditions affecting the response. Layer availability depends on configuration, permissions, source coverage, and source health.

Operational focus

Filter the map for the current task.

Narrow the map by incident, unit freshness, PAR state, capability, mission type, issue priority, or SOS status. Saved views preserve a useful command frame for the next handoff.

Current view

Medical units · Open PAR

3 active filters

MED-2 · Available

MED-7 · Assigned

MED-9 · PAR open

Initial incident overview

Weather impact

Night-shift handoff

Search area

Evacuation operations

AIGIS Dispatch

Create and assign missions from the map.

Field responders can create and take missions when policy allows. Authorized OPS users can assign units, update status, review routes, and follow the work.

Explore AIGIS Dispatch

Need identified

A responder or coordinator identifies work from the field or map.

Mission created

When incident policy allows, Field responders can create a mission and take it with their active unit.

Unit coordinated

OPS can assign, update, route, and follow the mission and unit state.

Work retained

Mission status remains connected to the incident record through completion.

AI-assisted. Operator reviewed.

Research the point before committing resources.

When enabled, AIGIS can assemble a structured weather brief for a selected point or mission using available current conditions, official alerts, lightning, road-weather context, timing signals, and applied risk thresholds.

See the weather research workflow

Selected map point

Staging Area North

Operator review required

Structured weather brief

The result can surface identified impacts, timing windows, confidence, assumptions, warnings, and recommended precautions for an operator to evaluate.

Unsafe after

Identified from available signals

Clear by

Recommended timing target

Signals

Official alerts and risk timeline

Confidence

Reported with the research

AI assistance is advisory. Operators remain responsible for source verification, interpretation, and operational decisions. Availability depends on configuration and permissions.

Operational handoff

Save the map view for the next shift.

Saved views retain the incident scope, filters, visible counts, active layers, and source-health notes.

Active incident scope

Visible unit and operational-object counts

Current layers and weather-impact context

Source-health and degraded-mode notes

See your units and operating conditions in AIGIS.

Request access for AIGIS Field and AIGIS OPS using your unit types, mission flow, status model, and operational map requirements.

Request access Get Field and OPS