Company1 min read
Where we’re taking Incanta next
Aerlattice is a starting point for developing Canadian expertise and choosing useful problems in defence technology.
Read articleJournal
Perspectives on defence and technology, and updates from Incanta.
Product1 min read
What comes after a working demonstrator?
Aerlattice shows how the planning workflow can work. Establishing whether it is ready for operational use takes a different kind of evidence.
Read article
Operations1 min read
Working through a flight request in Aerlattice
An introduction to the demonstrator’s workflow, from setting up a request to checking alternatives and recording a decision.
Read article
Operations1 min read
Making flight-planning software easier to use
How the map, route alternatives and request workflow help people follow a plan from an edit to a decision.
Read article
Aerlattice1 min read
Where planning ends and aircraft control begins
How Aerlattice distinguishes a proposed plan, an observation and a reviewed change within its planning workflow.
Read article
Operations1 min read
Keeping a useful record of a planning decision
A reviewer returning to a plan needs to understand what was checked, what changed and why an option was accepted. The record should make that possible.
Read article
Airspace1 min read
What we can learn from a flight-planning exercise
An exercise lets someone follow a plan through time, introduce a change and revisit the decision afterwards. Its value depends on understanding what it represents.
Read article
Aerlattice1 min read
A closer look at Aerlattice
A working desktop demonstrator connecting flight requests, conflict checks, route choices, reserved corridors and exercise monitoring.
Read article
Airspace1 min read
Planning when the picture is incomplete
Why plans, observations and the time information becomes available need distinct roles in a planning workspace.
Read article
Aerlattice1 min read
Comparing ways to change a flight plan
How bounded route search compares changes in path, timing and radio use while preserving the request’s constraints.
Read article
Company1 min read
How we’re building Aerlattice
The architecture behind Aerlattice: an interface for exploration, a planning engine for checks and a local repository for the working record.
Read article
Product1 min read
What working offline means in Aerlattice
Why local calculations, a shared planning engine and persistent project records belong together in the desktop architecture.
Read article
Airspace1 min read
Understanding an airspace conflict
How timed route segments, active airspace restrictions and radio windows shape an airspace conflict check.
Read article
Operations1 min read
Keeping people involved in automated planning
Why route generation, constraint checking and acceptance should have distinct roles in automated planning.
Read article
Aerlattice1 min read
Giving a reviewer enough context
The design behind a reviewable flight request: a clear route version, an understandable assessment and an explicit decision.
Read article
Canada1 min read
What control over defence software looks like
How local records, portability and maintainable software inform our approach to Canadian control.
Read article
Airspace1 min read
Why we started with airspace
Why we chose a focused airspace problem before expanding the scope of the product.
Read article
Canada1 min read
Why build airspace software in Canada?
Why uncrewed flight planning is a focused starting point for contributing to Canadian defence software.
Read article
Canada1 min read
Building Incanta in Canada
Building in Canada means keeping the expertise to understand, maintain and improve the software over time.
Read article
Company1 min read
Building defence software in Ottawa
Introducing Incanta and the problem behind Aerlattice: helping people understand and review uncrewed flight plans.
Read article