OMEN
DIU OMEN Solicitation License

OMEN — Open Mission Engine

A government-owned, modular mission software platform that enables contested-environment aircrew operations through integrated situational awareness, tactical mapping, standards-based data fusion, and deterministic evaluation.

DIU License ARES-E Energy
Explore Architecture View on GitHub
OMEN is not a single application. It is a mission software ecosystem — engine, map, data layer, evaluation, and operational infrastructure working together to deliver trusted, resilient mission capabilities.

Core Capabilities

🗺️

Integrated Situational Awareness

Blue-force, threat, airspace, and mission data fused into a single common operating picture for aircrew decision-making.

📡

Tactical Moving Map

Aviation-optimized display built with MapLibre GL JS and React, featuring offline resilience and DDIL-ready rendering.

🔗

Critical Abstraction Layer (CAL)

Standards-based data normalization across CoT, KML, GeoJSON, NOTAM, and UDL operational data sources via typed adapters.

🧪

Deterministic Evaluation

ARES-E–inspired test harnesses, DDIL simulation profiles, red-team fault injection, and human-in-the-loop review gates.

🤖

Bounded AI / Agentic Support

Route risk scoring, anomaly detection, and mission summarization under strict human-on-the-loop governance with HITL gates.

🔋

Energy-Aware Operation

Compute budgeting, thermal management, mode-based throttling, and edge-device endurance via DaScient Energy integration.

Lines of Effort

LOE 1

Open Mission Engine & SDK

Plugin runtime kernel with event bus, policy engine, telemetry pipeline, and typed SDK for adapter and plugin development.

engine/ · sdk/
LOE 2

Tactical Moving Map Application

React + MapLibre GL JS tactical display with mission overlays, offline mission packages, and cockpit-optimized UX design.

map-app/
LOE 3

Data Integration & Interoperability

Critical Abstraction Layer with protocol adapters (CoT, KML, GeoJSON, NOTAM, UDL), normalization pipelines, and delta sync.

cal/ · adapters/

Five-Layer Architecture

┌──────────────────────────────────────────────────────────────────┐ │ Layer A — Presentation │ │ Tactical Map · Mission Overlays · Threat / BFT · Alerts │ └───────────────────────────┬──────────────────────────────────────┘ │ Plugin APIs / Event Bus ┌───────────────────────────▼──────────────────────────────────────┐ │ Layer B — Mission Engine │ │ Plugin Runtime · Service Orchestration · Policy · Telemetry │ └──────────┬───────────────────────────────────┬───────────────────┘ │ Canonical Entities │ Config / Secrets ┌──────────▼──────────────────┐ ┌────────────▼───────────────────┐ │ Layer C — CAL │ │ Layer D — Evaluation │ │ Adapters · Normalization │ │ Harnesses · DDIL Sim │ │ Validation · Sync/Cache │ │ Red-Team · HITL Review │ └──────────────────────────────┘ └────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────┐ │ Layer E — Infrastructure │ │ Edge Runtime · Containers · Signed Artifacts · Fleet Mgmt │ └──────────────────────────────────────────────────────────────────┘

See the Architecture page for a detailed breakdown of each layer and its components.

Design Principles

  1. Mission Effectiveness First — every component improves decision quality, survivability, or mission continuity
  2. Open Architecture — open interfaces, open standards, government ownership
  3. DDIL Resilience — useful at low bandwidth, high latency, or fully disconnected
  4. Modular Replaceability — any component replaceable without full system rewrites
  5. Deterministic Core, Adaptive Edge — safety-critical behavior is auditable; AI is optional and bounded
  6. Least-Privilege Trust — narrow, continuously enforced auth and data access
  7. Human-on-the-Loop — aircrew and operators retain final authority over mission-critical decisions
  8. Energy-Aware Operation — compute efficiency, thermal management, bandwidth optimization
  9. Observability by Default — telemetry, logs, traces, and health as first-class features
  10. Community-Enabled Improvement — open feedback loops where policy permits

Repository Structure

OMEN/ ├── spec.md # Full Solutions Package Specification ├── docs/ # Architecture, LOE guides, security, evaluation, deployment ├── examples/ # Plug-and-play sample adapter, plugin, and mission package ├── sdk/ # Typed interfaces, data contracts, UI components, guides ├── engine/ # Mission engine core, policy, telemetry, ARES-E & Energy hooks ├── map-app/ # Tactical moving map application (React + MapLibre) ├── cal/ # Canonical data models, normalization pipelines, sync ├── adapters/ # CoT, KML, GeoJSON, NOTAM, UDL adapters ├── evaluation/ # Test harnesses, DDIL simulation, red-team scenarios ├── notebooks/ # Jupyter training manuals and field guides └── ops/ # Docker, Kubernetes, CI/CD, IaC, SBOM tooling

Quick Start

1

Clone the repository

git clone https://github.com/DaScient/OMEN.git
cd OMEN
2

Run the sample adapter

cd examples/sample-adapter
pip install -r requirements.txt
python run_adapter.py
3

Run the sample plugin

cd examples/sample-plugin
pip install -r requirements.txt
python run_plugin.py
4

Launch the evaluation harness

cd evaluation
pip install -r requirements.txt
pytest harnesses/ -v

Integration Ecosystem

Ecosystem Role in OMEN Key Directories
DaScient ARES-E Deterministic evaluation, red-teaming, HITL assurance, typed schemas engine/ares_e/ · evaluation/
DaScient Energy Resource-constrained intelligence, energy-aware scheduling, world-sensing engine/energy/ · ops/energy/

Training & Notebooks

Notebook Audience Description
01_omen_overview.ipynb All staff OMEN architecture orientation
02_sdk_quickstart.ipynb Developers SDK and plugin authoring quickstart
03_cal_adapters.ipynb Developers CAL adapter development guide
04_evaluation_harness.ipynb Test engineers Evaluation harness walkthrough
fg_01_aircrew_map.ipynb Aircrew / operators Tactical map field guide
fg_02_ddil_ops.ipynb Operators DDIL operations field guide
ares_e_integration.ipynb Engineers ARES-E integration walkthrough
energy_integration.ipynb Engineers DaScient Energy integration walkthrough

Technology Stack

Category Technologies
Backend Python 3.11+, Pydantic v2, FastAPI
Frontend React, TypeScript, MapLibre GL JS, CesiumJS (optional)
Build Vite, pytest, Playwright, Vitest
Infrastructure Docker, Kubernetes/K3s, GitHub Actions
Observability OpenTelemetry, Prometheus, Grafana
Security Cosign/Sigstore, OPA, OAuth2/OIDC, SPIFFE/SPIRE