"Air-Gapped" Mission Planning Suite

The Air-Gapped Mission Planning Suite is a map-based planning application that runs entirely on a laptop with no network connection. Staff build plans for movement, sustainment and coordination on locally stored maps, the commander reviews and approves them, and every change is recorded on the device. When an approved secure connection is available, plans and changes sync with other devices and the home station, and any conflicting edits are put in front of a person to resolve.

The problem it solves

Planning tools that depend on a cloud service or a constant network connection stop working where units most need them: in austere, contested or disconnected locations. Staff fall back on paper maps, acetate overlays, slide decks and spreadsheets, each holding a different version of the plan. When connectivity returns, reconciling those versions is manual, changes made in the field are lost or duplicated, and there is no reliable record of who changed the plan and when.

Who it’s for

• Unit and staff planners at battalion, brigade and equivalent echelons
• Commanders who review and approve plans
• Logistics and sustainment planners supporting deployed units
• Expeditionary, special operations and disaster-response teams working in disconnected locations
• Training and exercise staff who plan and review exercises

1. PrepareBefore departure, devices are loaded with the maps, imagery, unit and equipment data and plan templates the mission needs. The device checks that the data it will depend on is present before it leaves a connected network.
2. PlanPlanners build the plan on the map with standard symbology: routes, phase lines, assembly areas, checkpoints, supply points and coordination measures, with tasks and timings attached to units. Everything runs on the device with no network.
3. Approve and issueThe commander reviews the plan, comments on it and approves a version. The approved version is locked, and products such as overlays and movement tables are produced for issue.
4. SyncWhen an approved secure connection becomes available, the device exchanges changes with the unit's sync point or home station. Changes that do not conflict are merged; conflicts are listed for a person to resolve.

Fully offline operation

Maps, plans, calculations and the audit record all live on the device; nothing needs a network to work.

Offline maps and imagery

Map and imagery packages your organization provides are stored locally in standard formats such as GeoPackage and offline tile sets.

Standard symbology

Units, control measures and tactical graphics are drawn with MIL-STD-2525 symbology.

Movement planning

Routes, march tables, checkpoints and timings calculated from distances and the planning factors your unit sets.

Sustainment planning

Supply points, consumption estimates and resupply schedules built from the unit and equipment data loaded on the device.

Coordination overlays

Boundaries, phase lines and fire support coordination measures kept as separate layers that can be shown, hidden and issued on their own.

Courses of action

Several versions of a plan built and compared side by side, with the differences in routes, timings and resources listed.

Versioned approval

The commander approves a specific version, which is then locked; any later change starts a new version.

Secure sync with conflict review

Changes sync over approved connections only, and conflicting edits are never silently overwritten.

Local sharing

Plans and products can be passed between devices in the same unit over a local network or approved removable media.

Printable products

Overlays, movement tables and plan summaries printed or exported for briefings when screens are not practical.

On-device audit record

Every change, approval, export and sync is recorded on the device with the person and time, and carried to the home station on sync.

Commander

Reviews courses of action, comments, and approves the plan version that is issued

Operations planner

Builds plans, courses of action, movement and coordination overlays

Logistics planner

Builds sustainment and resupply plans and maintains planning factors

Subordinate leader

Receives approved plans and products for their unit and records progress

Data manager

Prepares data packages, manages sync and resolves sync conflicts with planners

Reviewer (read-only)

Views plans, versions and the audit record for after-action review and inspection

Map and imagery data

Maps, elevation data and imagery your organization is authorized to use, loaded as GeoPackage files or offline tile sets.

Unit and equipment data

Unit structure, equipment and supply data imported from your organization's systems by file before departure.

Plan exchange formats

Plans and overlays exported in common formats such as KML and GeoPackage for use in other approved systems.

Sync point

A sync service run by your organization at unit or home station, reached only over connections you approve.

Identity and smart cards

Users sign in on the device with credentials issued by your organization, including smart cards where your devices support them, without needing a network.

Tactical edge infrastructure

Devices can be managed alongside Moraph's Tactical Edge Compute Node Manager where your unit uses it.

Work API

At home station, approved plans and audit records are available to your reporting and archive systems through the Moraph Work API.

Sign-in on the device

Users sign in with credentials your organization issues, and roles come from your identity provider at each sync.

Role-based access

What each person can see and do follows their role and unit; building a plan is separate from approving it.

Encryption at rest and in transit

Data on the device and during sync is encrypted, using the cryptographic modules your organization approves for the device.

Approved connections only

Sync runs only over connections and to sync points your organization has approved; the application never reaches out to the internet.

Complete audit trail

Every change, approval, export and sync is logged with the person and time, and cannot be edited on the device or at home station.

Your authority, cleared support

On classified networks and devices the Suite is operated under your authority. Support tickets for defense clients are handled only by US citizens with active clearances.

Disconnected devices

Installed on your organization's ruggedized laptops, running fully offline.

Client-hosted sync point

The sync service runs in your environment at unit or home station, including classified networks, operated under your authority.

Training environment

An unclassified training and exercise environment can be hosted in Moraph's United States region.

With edge infrastructure

Optionally deployed with Moraph's Tactical Edge Compute Node Manager to manage devices and updates in the field.

Planning requirements

We work with your planners to set up plan templates, planning factors, symbol sets and the products your unit issues.

Data packages

We agree which map, imagery and unit data is loaded, in which formats, and the process your data managers follow to prepare it.

Device setup

The Suite is installed on the ruggedized laptops your organization provides and configured to your device hardening standards.

Sync design

Sync points, approved connections and conflict-resolution responsibilities are set up within your network architecture.

Authorization support

We provide control mappings, documentation and test evidence to support your organization's authorization of the devices and sync points.

Training and exercise

Planners, commanders and data managers are trained on their own workflows, and the Suite is used in an exercise before operational use by agreement.

• The Suite is a planning tool. It does not compute firing solutions, control weapons or replace your organization's command and control or fire support systems.
• It does not track forces in real time. Positions on the map are what planners enter or import, not live feeds.
• Offline data is only as current as the last load or sync; the Suite shows the date of each data package but cannot update it without a connection.
• Conflicting edits made on separate devices are not merged automatically; a person decides which change stands.
• Maps, imagery and unit data come from sources your organization provides and is authorized to use; their accuracy is outside Moraph's control.
• Ruggedized hardware, device hardening and procedures for lost or captured devices are your organization's responsibility; the Suite supports them with encryption and audit records.
• Moraph does not claim accreditation for any classified environment. Use on classified devices and networks is under your authority and authorization.
• Plans and approvals in the Suite support the commander's decisions; they do not replace orders issued through your organization's procedures.

• Disconnect a test laptop from every network and build a plan from start to approval
• Load a map package for a training area you use and check symbology and products against your standards
• Make conflicting edits on two disconnected devices, reconnect, and review how the conflict is presented
• Check that an approved version cannot be changed and that later edits start a new version
• Review the audit record carried back to the sync point after a disconnected period
• Confirm role separation: who can build, approve, export and resolve conflicts