Skip to main content
AER-02 · Aerospace & Defense

Mission Planning Knowledge Assistant

Outcome​

Support the mission planner in building a course of action that is grounded only in approved intelligence products, current doctrine and verified resource availability, with classification handling and human authority enforced at every step of the planning cycle.

Portfolio attributeValue
Primary personaMission planner
Primary aggregateMissionPlanningFolder
Cosmos DB containers3
Grounding dataapproved intelligence, doctrine, maps, resources
Development estimateUSD 60-220 monthly dev estimate
Runtime optionsPython FastAPI and C# ASP.NET Core

Productivity hypothesis​

These measures reflect the workflow, evidence, decision boundary, and industry risk for this use case.

Impact typeMeasureConservative internal assumptionCustomer measurement
ProductivityTask cycle time8-15% reduction(baseline median task minutes - assisted median task minutes) / baseline median task minutes * 100
Quality or riskEvidence discovery time10-20% reduction(baseline median evidence-search minutes - assisted median evidence-search minutes) / baseline median evidence-search minutes * 100

Important: Conservative internal pilot assumptions only; not public benchmarks, commitments, or expected customer results. Validate against a comparable baseline or matched control cohort with mandatory human review.

Rationale: Mission planners can assemble approved evidence faster, but mission sensitivity supports only a narrow decision-support productivity assumption.

Pilot guardrail: Use only approved intelligence, doctrine, maps, and resource information; keep operational planning human-controlled.

Customer validation plan​

  1. Baseline the current workflow with representative users and tasks.
  2. Run the accelerator on the same task mix with human review retained.
  3. Measure task cycle time and evidence discovery time with the documented formulas.
  4. Replace internal assumptions with customer-observed results before a business case.

Why Azure Cosmos DB​

This AI solution needs an operational data plane, not only a vector index:

  • Hybrid vector and full-text retrieval combines semantic recall with exact identifiers, codes, names, and domain language.
  • Hierarchical partition keys and metadata predicates keep tenant and domain boundaries in the normal query path.
  • Operational JSON, source chunks, workflow and agent state, feedback, and audit records remain together for low-latency reads and governed writes.
  • Change feed reacts to source and operational updates without polling.
  • Autoscale throughput, configurable consistency, and multi-region distribution support variable demand and enterprise availability.

Domain workflow​

Domain workflow

StageActorInput → outputApproval
1. Mission analysis and constraint framingMission plannerMission → constraintAndAssumptionSetPolicy controlled
2. Approved intelligence retrievalMission planning knowledge assistantconstraintAndAssumptionSet → IntelligenceProductChunkPolicy controlled
3. Doctrine-bounded COA developmentMission planning knowledge assistant with plannerDoctrineChunk → CourseOfActionPolicy controlled
4. Wargaming and comparisonPlanning staffCourseOfAction → coaComparisonMatrixHuman required
5. Commander approval of selected COAApproving authoritycoaComparisonMatrix → approvedCourseOfActionHuman required

Technical architecture​

Technical architecture

Cosmos DB data model​

ContainerHierarchical partition keyDocumentsSearch paths
missionPlanningFolders/tenantId, /missionIdMission, ResourceAvailability, CourseOfAction, PlanningDecisionRecord/coaVectorEmbedding, /coaVector
intelligenceProductArchive/tenantId, /productIdIntelligenceProductChunk/chunkVectorEmbedding, /chunkVector
doctrineLibrary/tenantId, /echelonApplicabilityDoctrineChunk/chunkVectorEmbedding, /chunkVector

Query contract​

QueryContainerScopePurpose
ClearanceScopedIntelRetrievalintelligenceProductArchivecross-partition-boundedRetrieve only intelligence the requesting planner is cleared and authorized to see, still inside its validity window. Intentional cross-partition fan-out across the intelligenceProductArchive reference container, bounded by the tenant prefix, the caller clearance rank, the caller releasability tokens and the product validity window, returning only the top-ranked product chunks.
ApplicableDoctrineConstraintsdoctrineLibrarysingle-partitionRetrieve doctrine and rules-of-engagement constraints applicable to the echelon and mission type.
ResourcesAvailableInWindowmissionPlanningFolderssingle-partitionFind platforms and crews actually available and ready across the execution window.
PlanningDecisionAuditmissionPlanningFolderssingle-partitionReconstruct the ordered decision trail for after-action review and authority audit.

Python and C# services route each document type to its declared container and hierarchical partition key. ETag-based writes protect mutable aggregates, while append-only records and bounded cross-partition queries preserve scale.

Azure deployment​

Azure deployment

Clone the source repository, authenticate with Azure, and run:

Set-Location accelerators/aerospace-defense/mission-planning-knowledge-assistant
az login
./Deploy.ps1 -Runtime python -Location eastus2

Change python to csharp to deploy the .NET implementation.

Explore the implementation​

Return to all accelerators