Our reason for building airspace software in Canada is straightforward: we want to contribute the ability to develop it here, understand it and keep improving it.
That doesn’t require dismissing software built elsewhere. A useful product still has to earn its place through what it does and how well it fits the work. For Incanta, the contribution begins with Aerlattice.
Build around a task we can examine
Aerlattice focuses on preparing and reviewing uncrewed flight requests. It brings routes, timing, checks and alternatives into one desktop workspace.
This is a specific enough task to inspect closely. A reviewer can follow a request, examine where it conflicts with the rest of an exercise and consider a change. The application records the decision and keeps it with the plan.
Building that workflow gives us something concrete to evaluate. It also lets us describe the product without implying that we’ve built a national traffic-management service.
Make room for different working conditions
One choice we made early was to keep core planning available offline. A user can work with the local workspace without needing a public internet connection. Plans, checks and recordings remain together, with backups and exports available.
That is a useful capability to examine when connectivity is limited or the work needs to remain on a particular machine. Whether the application is suitable for a specific environment still needs to be established through evaluation.
Develop the capability over time
Being based in Ottawa gives Incanta a home in Canada. The longer-term contribution depends on continuing to improve the application and learning how well it supports the people using it.
Aerlattice is currently a demonstrator. Representative user studies and operational validation remain work ahead. We want that work to give us a sound basis for the next decisions about the product.
