"Air-Gapped" Mission Planning Suite

Principal workflows

• Prepare: Before 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.
• Plan: Planners 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.
• Approve and issue: The 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.
• Sync: When 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.

Who uses it

• 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

Reporting

• Plans by status, version and approving commander
• Changes made since the last approved version
• Sync history by device, with conflicts and how they were resolved
• Device data readiness, including the date of maps and unit data on each device
• Exports and printed products, by user and plan
• Plan history for after-action review

Features

• 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.

Integrations

• 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.

Deployment

• 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.

Security and privacy

• 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.

Limitations

• 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.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/air-gapped-mission-planning-suite. Purchasing routes and company information: www.moraph.com/how-to-buy.