Reference
"Air-Gapped" Mission Planning Suite glossary
Terms used in "Air-Gapped" Mission Planning Suite and its documentation.
Applies to "Air-Gapped" Mission Planning Suite as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
Terms used in "Air-Gapped" Mission Planning Suite and its documentation.
| Term | Meaning |
|---|---|
| Plan version | One saved state of a plan; an approved version is locked and later changes start a new version. |
| Course of action | One alternative way of carrying out the mission, built as a version and compared with others. |
| Data package | A set of map, imagery, elevation or unit data prepared for loading onto devices, with a data date. |
| Readiness check | A check on the device that the data packages a mission depends on are present and dated. |
| Sync point | The sync service your organization runs at unit or home station that devices exchange changes with. |
| Sync conflict | Edits to the same part of a plan made on separate devices, held for a person to resolve. |
| Planning factors | Rates and assumptions your unit sets that drive movement and sustainment calculations. |
| Control measure | A boundary, phase line, checkpoint or similar graphic used to coordinate units on the map. |
| Local sharing | Passing plans and products between devices in the same unit without a sync point. |
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.