Defense & Intelligence · Moraph software

"Air-Gapped" Mission Planning Suite

Plan on the map without a network, and sync when a secure connection returns

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

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.

  • Cloud-dependent tools stop working when the connection drops
  • Plans are split across paper, slides and spreadsheets in different versions
  • Reconciling field changes with the home station is done by hand
  • There is no reliable record of who changed the plan, or when

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

Requirements it supports

Joint Publication 5-0, Joint PlanningMIL-STD-2525, Joint Military SymbologyDoD Instruction 8510.01, Risk Management Framework for DoD SystemsCNSSI 1253, Security Categorization and Control Selection for National Security SystemsNIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and OrganizationsFIPS 140-3, Security Requirements for Cryptographic Modules

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    Plans on the device

    Planners start from the list of plans on the device, with each plan's version, status and last sync.

    PlanVersionOwnerStatusLast sync
    Exercise Example North: movementv4Operations plannerApprovedBefore departure
    Exercise Example North: resupplyv3Logistics plannerChanges since approvalBefore departure
    Exercise Example North: COA 2v2Operations plannerIn reviewNot synced
    Example route reconnaissancev1Operations plannerDraftNot synced
    Planners start from the list of plans on the device, with each plan's version, status and last sync.

  2. Step 2

    The plan record

    Each plan shows its approved version, the layers it contains and the data it depends on.

    Exercise Example North (fictional) · Movement plan v4

    Approved by
    Commander
    Units
    4 fictional sample units
    Routes
    Route Example Blue, Route Example Gold
    Map package
    Example training area, loaded before departure
    Unit data
    Older than map package

    Layers

    • Boundaries and phase lines
    • Routes and checkpoints
    • Assembly areas
    • Coordination measures
    Each plan shows its approved version, the layers it contains and the data it depends on.

  3. Step 3

    The movement table

    Movement timings are calculated from the routes on the map and the planning factors your unit sets.

    SerialUnitRouteStart pointRelease pointDistance
    1Example Unit ARoute Example BlueCheckpoint 1Checkpoint 642 km
    2Example Unit BRoute Example BlueCheckpoint 1Checkpoint 642 km
    3Example Unit CRoute Example GoldCheckpoint 2Checkpoint 957 km
    4Example Support UnitRoute Example GoldCheckpoint 2Release point not setTo be confirmed
    Movement timings are calculated from the routes on the map and the planning factors your unit sets.

  4. Step 4

    Sustainment

    Resupply needs are estimated from the unit and equipment data on the device and the factors the logistics planner sets.

    Example Unit C · Resupply plan v3

    Supply point
    Example Supply Point 2
    Planning period
    3 days (sample)
    Fuel estimate
    Based on 18 sample vehicles
    Water estimate
    Based on sample unit strength
    Status
    Changed since approval

    Changes since approval

    • Supply point moved from Example Supply Point 1
    • Resupply timing moved later by one serial
    • Comment added for commander's review
    Resupply needs are estimated from the unit and equipment data on the device and the factors the logistics planner sets.

  5. Step 5

    Syncing after reconnecting

    When an approved connection returns, the device exchanges changes and records exactly what moved.

    Device EX-07 · Sync with unit sync point

    1. Approved connection detected and device authenticatedSync service
    2. 12 changes sent, 9 changes receivedSync service
    3. Movement plan v4 confirmed as approved at home stationSync service
    4. !2 conflicting edits held for reviewSync service
    5. Conflicts assigned to the logistics plannerData manager
    When an approved connection returns, the device exchanges changes and records exactly what moved.

  6. Step 6

    Resolving conflicts

    Edits made on two devices to the same item are shown side by side, and a person decides which stands.

    ItemThis deviceOther deviceAssigned toDecision
    Example Supply Point 2 locationMoved north of Checkpoint 4Original locationLogistics plannerPending
    Serial 4 release pointCheckpoint 9Checkpoint 8Operations plannerPending
    Phase Line Example Red labelRenamedUnchangedOperations plannerKept this device
    Edits made on two devices to the same item are shown side by side, and a person decides which stands.

Workflows

The principal workflows

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

    • Area of operations selected and map and imagery packages loaded
    • Unit, equipment and supply data imported from your systems
    • Plan templates and symbol sets loaded
    • Readiness check confirms data is complete and records its date
    • Device signed out to the user and unit

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

    • Planner creates the plan from a template or a previous plan
    • Units, routes, control measures and timings drawn on the map
    • Movement and sustainment tables calculated from distances and planning factors
    • Courses of action compared side by side
    • Plan sent to the commander for review on the same or a nearby device

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

    • Commander reviews the plan and its courses of action
    • Comments returned to planners, or a version approved
    • Approved version locked; further changes create a new version
    • Overlays, tables and printable products generated
    • Products shared by local transfer to other devices in the unit

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

    • Device detects an approved connection and authenticates
    • Changes since the last sync sent and received
    • Non-conflicting changes merged with their history kept
    • Conflicting edits shown side by side for a planner to resolve
    • Sync recorded with what moved, when and between which devices

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Commander

Commander, deputy commander, officer authorized to approve plans

Reviews plans and courses of action and approves the version that is issued.

Sees

  • All plans and courses of action for their unit
  • Differences between versions and courses of action
  • Comments from planners and subordinate leaders
  • Data readiness, including the age of maps and unit data

Does

  • Reviews plans and compares courses of action
  • Returns plans with comments
  • Approves a specific version for issue
  • Delegates approval authority to a named deputy where your procedures allow

Cannot

  • Edit an approved version; changes start a new version
  • Delete plans or audit records
Approvals
Their approval locks a plan version for issue; delegations they make are recorded.
Notified about
Plans sent for review and approved plans changed after approval.

Operations planner

Operations officer, plans officer, staff planner

Builds the plan on the map, including movement, control measures and courses of action.

Sees

  • Plans for their unit and the data loaded on the device
  • Comments from the commander
  • Sync conflicts assigned to them

Does

  • Creates plans from templates or earlier plans
  • Draws routes, control measures and coordination overlays
  • Builds and compares courses of action
  • Sends plans for review and generates products
  • Resolves sync conflicts assigned to them

Cannot

  • Approve a plan
  • Change an approved version
  • Change planning factors or templates without the data manager
Approvals
Plans they build are approved by the commander before issue.
Notified about
Comments and approvals on their plans and conflicts assigned to them.

Logistics planner

Logistics officer, sustainment planner, supply officer

Builds the sustainment and resupply parts of the plan.

Sees

  • Plans for their unit and the unit, equipment and supply data on the device
  • Planning factors for consumption
  • Sync conflicts assigned to them

Does

  • Places supply points and plans resupply
  • Maintains consumption planning factors for the unit
  • Generates sustainment tables
  • Sends sustainment plans for review
  • Resolves sync conflicts assigned to them

Cannot

  • Approve a plan
  • Change an approved version
Approvals
Sustainment plans are approved by the commander with the rest of the plan.
Notified about
Comments and approvals on their plans and conflicts assigned to them.

Subordinate leader

Subordinate unit leader, team leader, element leader

Receives the approved plan and products for their unit and reports progress against it.

Sees

  • Approved plans and products issued to their unit
  • Tasks and timings for their unit
  • Comments addressed to them

Does

  • Views and prints approved products
  • Records progress and checkpoints reached
  • Adds comments for the planners and commander

Cannot

  • Edit plans
  • See plans not issued to their unit
  • Export data beyond the products issued to them
Approvals
Nothing they do needs approval; their comments go to the planners.
Notified about
New or changed plans issued to their unit.

Data manager

Knowledge manager, geospatial or data specialist, communications staff

Makes sure devices carry the right data and that sync works and is reconciled.

Sees

  • Data packages on each device and their dates
  • Sync history and conflicts for the unit
  • Device sign-out records

Does

  • Prepares and loads map, imagery and unit data packages
  • Maintains templates, symbol sets and planning factor libraries
  • Runs sync and assigns conflicts to planners
  • Signs devices out and back in

Cannot

  • Approve plans
  • Change plan content beyond resolving a conflict assigned to them
  • Delete audit records
Approvals
Template and planning factor changes are confirmed by the operations or logistics lead your unit names.
Notified about
Sync failures, unresolved conflicts and devices with outdated data.

Reviewer (read-only)

After-action review staff, exercise controller, inspector

Reviews how a plan developed and was approved, without changing anything.

Sees

  • Plans, versions and approvals within the scope granted
  • Sync history and conflict decisions
  • The audit record

Does

  • Reads and compares plan versions
  • Exports records for after-action review, with each export logged

Cannot

  • Change, approve or delete anything
  • Keep access after it expires
Approvals
Their access is approved by the commander or a delegate, with a scope and an end date.
Notified about
Nothing by default.

Administrator

System administrator, device administrator

Manages users, devices and the sync service without working on plan content.

Sees

  • Users, roles and units
  • Devices, software versions and sync service health
  • The record of permission changes

Does

  • Adds and removes users or maps them from your identity provider
  • Installs and updates the Suite on devices
  • Maintains the sync service and approved connections
  • Runs access review reports

Cannot

  • Open plan content
  • Approve plans
  • Grant themselves a planning or command role
Approvals
Role changes that grant approval authority are confirmed by the commander or a delegate.
Notified about
Devices that have not synced for a period your unit sets, update failures and access reviews coming due.

Permissions at a glance

ActionCommanderOps plannerLog plannerSub. leaderData managerReviewerAdmin
Create and edit plansView onlyFullFullNo accessNo accessNo accessNo access
Build courses of actionView onlyFullFullNo accessNo accessNo accessNo access
Approve a plan versionApprovesNo accessNo accessNo accessNo accessNo accessNo access
View issued plans and productsFullFullFullOwn work onlyView onlyView onlyNo access
Record progress and commentsFullFullFullOwn work onlyNo accessNo accessNo access
Export and print productsFullFullFullOwn work onlyNo accessView onlyNo access
Load data packagesNo accessNo accessNo accessNo accessFullNo accessNo access
Change templates and planning factorsNo accessApprovesApprovesNo accessFullNo accessNo access
Run sync and assign conflictsNo accessNo accessNo accessNo accessFullNo accessNo access
Resolve sync conflictsNo accessOwn work onlyOwn work onlyNo accessOwn work onlyNo accessNo access
View audit recordView onlyNo accessNo accessNo accessView onlyView onlyView only
Manage users and devicesApprovesNo accessNo accessNo accessNo accessNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Building a plan and approving it are separate: planners cannot approve, and an approved version is locked so changes always start a new version that goes back for approval.
  • Roles are configured with you during implementation and limited by unit, so a subordinate leader sees only the plans issued to their unit.
  • Roles are held on the device so they work offline, and are refreshed from your identity provider at each sync; permission changes are recorded in the audit record.
  • Reviewers for after-action reviews and inspections get temporary read-only access with a defined scope and an end date, rather than shared accounts.

Features

What it does

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

How it connects to your systems

Connects toHowWhat flows
Map and imagery dataMaps, elevation data and imagery your organization is authorized to use, loaded as GeoPackage files or offline tile sets.In: map, elevation and imagery packages for the area of operations.
Unit and equipment dataUnit structure, equipment and supply data imported from your organization's systems by file before departure.In: unit, equipment and supply records.
Plan exchange formatsPlans and overlays exported in common formats such as KML and GeoPackage for use in other approved systems.Out: overlays, routes and control measures. In: overlays from other approved systems.
Sync pointA sync service run by your organization at unit or home station, reached only over connections you approve.In and out: plan changes, approvals and audit records.
Identity and smart cardsUsers sign in on the device with credentials issued by your organization, including smart cards where your devices support them, without needing a network.In: user identity and roles, refreshed at each sync.
Tactical edge infrastructureDevices can be managed alongside Moraph's Tactical Edge Compute Node Manager where your unit uses it.Out: device and software status. In: approved software and data updates.
Work APIAt home station, approved plans and audit records are available to your reporting and archive systems through the Moraph Work API.Out: plan versions, approvals and audit records.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

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.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Plan status

For commander and planners

Every plan on the device or sync point with its version, status, owner and approval.

Break down by
Plan, Status, Owner, Unit
Delivered as
On the device; printable
Used for
Knowing which version is approved and what is still in work.

Changes since approval

For commander and planners

Every change made to a plan since its last approved version, with who made it and when.

Break down by
Plan, Layer, User
Delivered as
On the device; printable
Used for
Deciding whether changes need the commander's approval before issue.

Movement and sustainment tables

For planners and subordinate leaders

Movement serials, routes, timings and resupply schedules from the approved plan.

Break down by
Unit, Route, Serial, Supply point
Delivered as
On the device; printable; export
Used for
Issuing the plan in a form units can carry and brief.

Data and sync

Device data readiness

For data managers

For each device, the map, imagery and unit data loaded and the date of each package.

Break down by
Device, Data package, Package date
Delivered as
At the sync point; printable
Used for
Making sure devices leave with complete, current data.

Sync history

For data managers and administrators

Each sync with the devices involved, changes sent and received, and conflicts raised.

Break down by
Device, Sync point, Date, Result
Delivered as
At the sync point; CSV export
Used for
Finding devices that have not synced and diagnosing sync problems.

Conflict decisions

For data managers and planners

Every sync conflict, the two versions, who resolved it and which version stood.

Break down by
Plan, Resolver, Decision
Delivered as
At the sync point; CSV export
Used for
Checking that conflicts were resolved by the right people.

Review and audit

Plan history

For commanders, after-action review staff and inspectors

How a plan developed, from first draft through each version, comment and approval.

Break down by
Plan, Version, User, Date range
Delivered as
At the sync point; PDF export
Used for
After-action review and lessons learned.

Exports and products

For security staff and administrators

Every export and printed product, by user, plan and device.

Break down by
User, Plan, Device, Format
Delivered as
At the sync point; CSV export
Used for
Accounting for plan information that left the application.

Audit record extract

For inspectors and security staff

Who did what, when and on which device, for a selected plan, device or period.

Break down by
Plan, Device, User, Date range
Delivered as
At the sync point; CSV and PDF export
Used for
Answering inspection and investigation requests.

Access review

For commanders and administrators

Every user with their roles, unit and devices, and when they last signed in or synced.

Break down by
Role, Unit, Last activity
Delivered as
At the sync point; CSV export
Used for
Periodic certification of who can plan, approve and administer.

Exports, access and evidence

  • Operational reports work on the device without a network and can be printed for briefings.
  • Data, sync and audit reports are run at the sync point, where records from every device are brought together after each sync.
  • Reports can be exported to CSV, and history and audit reports to PDF; approved plans and records are available to your archive through the Moraph Work API at home station.
  • Reports respect each viewer's role and unit; reviewers can be given read-only access to plan history and the audit record.
  • Every export and printed report is itself recorded in the audit record.

Deployment

Where and how it runs

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 controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

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.

Limitations

What it does not do

Worth knowing before you evaluate it.

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

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

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

Questions

Frequently asked questions

Does anything need a network to work?

No. Planning, approval, products and the audit record all work on the device. A connection is only needed to sync with other devices or the home station.

What happens when two people change the same thing while disconnected?

Both changes are kept and shown side by side at sync, and a planner or data manager decides which one stands. Nothing is overwritten silently.

Which hardware does it run on?

The ruggedized laptops your organization provides and approves. We confirm the supported operating systems and specifications during scoping.

Is the Suite accredited for classified use?

Moraph does not claim accreditation. Where you use it on classified devices or networks, it is authorized and operated under your authority, and we provide documentation to support your process.

How is it priced?

As a subscription, usually measured by the number of devices and sync points, with implementation charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate "Air-Gapped" Mission Planning Suite

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: "Air-Gapped" Mission Planning Suite guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: "Air-Gapped" Mission Planning Suite support guide.

Related products