A planning exercise gives us a manageable way to explore a change. A departure moves, a route deviates or a feed stops, and we can examine what the application shows the person reviewing it.
Aerlattice includes eight exercises covering traffic, weather, route detours, timing, radio contention and monitoring incidents. They provide a starting point for exploring the application’s workflow.
Follow the sequence over time
The shared exercise clock makes timing visible. Users can follow recorded or simulated positions and review alerts for deviations, feed loss and projected collisions.
This allows a discussion to move beyond a single screenshot. When did the situation change? What information was available then? Did the proposed replacement address the finding, and what needed review before it could replace the accepted plan?
Replacement routes remain drafts for a person to consider. The exercise therefore includes the decision process as well as the movement of aircraft.
Keep a record you can revisit
Plans, assessments, decisions and recordings stay together in the local workspace. Replaying an exercise can help someone look more closely at a moment they missed or explain a decision to another reviewer.
The core workflow runs offline. An optional receive-only connection can bring in simulator telemetry, while the external ADS-B aircraft layer requires internet access. It’s useful to be clear about which source of positions an exercise is using.
Know what an exercise demonstrates
A supplied scenario shows behaviour under a particular set of conditions. It doesn’t establish how the application will perform in every setting, or how a team would use it during an actual operation.
That distinction helps us learn from the demonstrator without asking it to prove more than it can. Representative studies and operational validation remain separate work ahead.
