Keep the original request.
Review proposals against the requirements that prompted them.
NORM / Mission workspace
One workspace.
A clearer mission plan.
Bring the requirements, AI-assisted planning, waypoint edits,
and operator review into the same workflow.
Windows previewFixed-wing waypointsOperator approval
The current preview.
Designed for review. Still undergoing hardware validation.
▣
Windows
Packaged preview
↗
Fixed-wing
Waypoint mission focus
◇
AI assistance
Interpretation and proposals
+
Human approval
Device actions need a decision
Work on a draft.
Edit the plan before deciding whether it is ready to proceed.
Check what happened.
A proposal, approval, and device result are separate records.
Waypoints & storage
Make the route reviewable.
Work with mission drafts and waypoint edits before any device action.
Task context
Keep the requirements close to the proposed plan.
Waypoint review
Examine the route and make edits before approval.
Separate approval
Saving a draft does not start a device.
The mission workflow
From a brief
to a reviewed plan.
One thing matters to us: the original requirements must not get lost along the way. AI helps organize, interpret, and suggest. People still check conditions on the ground and approve actions involving a device.
Illustrated workflow · 01
Start with the task.
Bring the mission requirements into the workspace so the proposed plan can be reviewed against the original request.
Illustrated workflow · 02
Turn the brief into a proposal.
AI helps interpret the request and propose a mission plan. The proposal remains a draft for the operator to examine.
Illustrated workflow · 03
Review the route in detail.
Review and edit the proposed waypoints before deciding whether the plan is ready for approval.
Illustrated workflow · 04
Keep the decision with the operator.
Actions involving a vehicle require human approval. Approval is separate from the AI’s suggestion and from verification of the device result.
Illustrated workflow · 05
Keep the task and its records together.
Keep device mission records alongside the planning workflow. Full real-device transfer, verification, and limited control are still undergoing acceptance testing.
The mission workflow
From a brief to a reviewed plan.
One thing matters to us: the original requirements must not get lost along the way. AI helps organize, interpret, and suggest. People still check conditions on the ground and approve actions involving a device.
01 / Mission brief
Start with the task.
Bring the mission requirements into the workspace so the proposed plan can be reviewed against the original request.
02 / AI-assisted planning
Turn the brief into a proposal.
AI helps interpret the request and propose a mission plan. The proposal remains a draft for the operator to examine.
03 / Waypoint editing
Review the route in detail.
Review and edit the proposed waypoints before deciding whether the plan is ready for approval.
04 / Operator approval
Keep the decision with the operator.
Actions involving a vehicle require human approval. Approval is separate from the AI’s suggestion and from verification of the device result.
05 / Mission records
Keep the task and its records together.
Keep device mission records alongside the planning workflow. Full real-device transfer, verification, and limited control are still undergoing acceptance testing.
Observations
Put the device context
alongside the plan.
Use the workspace to review observation views and mission records.
Map context
The application capture shows the observation interface and its map.
Clear connection state
The visible status distinguishes the local service from a connected vehicle.
Evidence has a scope
A map view does not prove mission transfer or a completed flight.
Engineering evaluation
Know what
has been checked.
Available as a Windows technical preview for product discussions and engineering evaluation.
Try organizing requirements, drafting waypoints, working with maps, and reviewing plans. Uploads to real flight controllers and the control loop are still being validated. The preview is not intended for real flights, unattended operation, or production use.
Current development statusMore application views
A closer look.
Open a screenshot to inspect the original capture and its visible state.
NORM for Windows
Your next mission
starts with a plan.
Available as a Windows technical preview for product discussions and engineering evaluation.
Try organizing requirements, drafting waypoints, working with maps, and reviewing plans. Uploads to real flight controllers and the control loop are still being validated. The preview is not intended for real flights, unattended operation, or production use.
Talk to NORM
Let’s talk about your next mission.
Bring a mission, and see if the next round of preparation can be a little clearer.
hello@normautonomy.com