The product
Representative interface — sample data, not a client system.
Interface summary
What the pre-flight workspace puts on one screen
- Live weather read against the operator's own limits
- A 17-step release checklist run in sequence
- Authorisation, crew, aircraft and site status
- Operational alerts and pilot-in-command notes
- A release gate that a person has to action
Client project
Built for an external client.
Who uses it
The pilot in command, and the crew around them who have to agree a flight is ready.
- Before
- Weather, authorisation, crew, aircraft and site checks sit in separate documents and apps, and the pilot in command reconciles them from memory under time pressure.
- After
- The same checks are reconciled on one screen, and releasing a flight is a deliberate action with the pilot's notes attached to it.
The problem
The workspace runs in Singapore unmanned-aircraft operations, in the minutes before a flight is released.
Pre-flight readiness is not one check, it is several that have to agree: the weather at the site, the authorisation covering the flight, the crew on duty, the aircraft's condition and the site itself. Held across separate documents and apps, the pilot in command has to reconcile them from memory under time pressure, and the decision to release leaves no durable record.
What PSOI Tech delivered
- Live weather envelope with editable operating limits
- 17-step controlled pre-flight release checklist
- PIC notes, operational alerts and release-gate workflow
Decisions that shaped it
- 01
Operating limits are editable, not hard-coded
Wind, visibility and other limits differ by airframe and by an operator's own procedures, so the weather envelope reads live conditions against limits the operator sets rather than against a fixed threshold baked into the software. The workspace shows the comparison; the operator keeps ownership of the numbers.
- 02
The checklist is a release gate, not a form
The 17 steps run in a controlled sequence and feed a single release decision, so a flight is not released while a step is outstanding. That makes the checklist part of the decision rather than paperwork completed alongside it.
- 03
The pilot in command stays the decision maker
The workspace reconciles inputs and raises operational alerts, but the release gate is a human action with PIC notes attached to it. Nothing in the build clears a flight automatically — the software supports the judgement, it does not replace it.
- 04
One screen, ordered by what blocks a launch
Weather, authorisation, crew, aircraft and site checks are laid out in the order they can stop an operation, so the thing most likely to ground a flight is visible first rather than buried several taps into a menu.
Where it stands
One decision-support workspace for Singapore unmanned-aircraft operations, live and in use.
No performance figures are published for this build. PSOI Tech publishes outcome numbers only where the client has measured and approved them, so this entry describes the work rather than claiming a result.