core analysis module

Planned vs Actual Route Analysis

Compare intended mission routes against executed movement to expose where execution diverges from plan. This module surfaces deviation early, with timing and context, so teams can intervene before small misalignments compound into mission failure.

KEY SIGNALS SURFACED
  • Loss of planned route alignment
  • Waypoint omission or bypass
  • Duration of deviation and recovery
  • Early deviation onset timing
  • Intent-execution divergence zones
readiness intelligence

Why This Signal Matters

Most route failures are not abrupt. They begin as small, explainable deviations that go unnoticed until after the mission or exercise concludes. Without a clear comparison between intent and execution, teams are forced to reconstruct events after the fact instead of correcting behavior while outcomes are still recoverable.

What Becomes Visible

This module turns route comparison into actionable evidence by isolating when, where, and why execution diverged from intent.
Execution Signals Exposed
  • Where deviation began, not just where it ended
  • Whether divergence was intentional or emergent behavior
  • How long deviation persisted before correction
  • Where recovery occurred or failed
Decisions This Enables
  • Earlier instruction intervention
  • Objective after-action review
  • Reduced narrative reconstruction
  • Defensible performance assessment

How Teams Use This Signal

During operations or training
  • Identify deviation onset while activity is still in progress
  • Flag execution drift without halting the exercise
  • Preserve contextual evidence for review
During review and evaluation
  • Compare intent versus execution using shared reference points
  • Reduce subjective interpretation during debrief
  • Anchor feedback in observable movement behavior
Integration snapshot

Integration & Deployment

Designed for direct adoption inside existing mission systems.

Data Interface
Inputs
  • Planned route definitions (KML, KMZ, GeoJSON)
  • Executed movement telemetry (CSV, JSON, Parquet)
  • Mission metadata and timestamps
Outputs
  • Structured deviation events
  • Intent-versus-execution comparison objects
  • Readiness-aligned signal flags
  • JSON outputs for downstream systems, with optional PDF mini-after-action extract
Execution & Control
Deployment Models
  • Standalone Python module
  • Containerized microservice
  • API-ready integration
  • Air-gapped compatible
Configuration
  • Doctrine thresholds defined in configuration files
  • Operator-adjustable parameters
  • Core algorithms remain fixed and deterministic across deployments.
Security
Deployment models and licensing are tailored by environment and mission constraints.
View Integration OptionsStart a Pilot Discussion