A planning session shouldn’t depend on an internet connection when the information needed for the exercise is already on the machine. That’s the starting point for offline work in Aerlattice.
The current Windows desktop demonstrator performs its core planning, checking, project storage and local rendering offline. The user can work with the contents of the local workspace without a public-cloud connection.
Keep the plan and its context together
A workspace holds more than routes. It includes assessments, review decisions and recordings, so someone can return to the reasoning behind a plan.
Complete workspace backups keep that record portable. Exports provide another way to retain project records, plans and reservation volumes. These capabilities matter when work needs to be moved or revisited later.
Keeping the work local also makes the available information easier to describe: a check uses what is represented in the workspace. The result needs to be understood in that context.
Know which features are connected
The optional ADS-B layer displays external aircraft and requires an internet connection. The optional MAVLink input receives simulator telemetry; it needs a connection to that simulator and does not send aircraft commands.
Those features have different purposes from core planning. Their availability should be understood separately from whether a local request can be prepared, checked and reviewed.
Offline does not mean complete
A local workspace can contain old or incomplete information just as any other workspace can. Working without internet access does not establish that the data is current, that every aircraft is represented or that the application is approved for a particular environment.
What it provides is continuity for the core planning task. The user can keep working with the information they have, preserve the decisions made around it and understand which additional features depend on a connection.
