There are many directions a defence software company could take. We chose to start with a concrete task: helping someone plan an uncrewed flight in airspace that other flights also need to use.
That gives Aerlattice a clear focus. The application holds requests, checks how they fit together, offers alternatives and keeps a record of the review.
A shared area creates a shared problem
In an exercise, two requests may each be workable on their own and still compete for the same area during the same period. One team’s change can affect another request’s timing or available route.
Putting those requests in the same workspace makes the relationship easier to examine. The discussion can address a particular overlap and the options for resolving it.
Airspace gives us a way to explore that coordination in detail. Routes have heights and times; restrictions have boundaries and active periods. A useful review needs to consider them together.
Give the first task enough attention
Even this focused workflow raises plenty of questions. How should a finding be explained? How does a reviewer compare a detour with a later departure? What happens to an accepted plan while someone examines a replacement?
We can work through those questions in the demonstrator and show the results in an application. Whether the workflow helps representative users is something we still need to evaluate.
Broader context can come with clear boundaries
A flight may serve a task on land or at sea, but that does not make a flight-planning application a complete picture of those activities. Additional context would need a defined purpose and a clear account of its source and limits.
For now, Aerlattice’s role is planning, simulation and review. Starting there gives us a specific piece of work to improve and an honest way to explain what the current product does.
