NAUTILUS CONN · OPERATOR APPLICATION
See the vessel’s state before you take control
NAUTILUS CONN is the Windows operator application in development for vessel observation, mission review and supervised control. It brings the vessel state, connection quality and current control owner together, with the age of the information visible before the operator acts.
IN DEVELOPMENT · PILOT CONVERSATIONS OPEN
NAUTILUS / FILM
Watch NAUTILUS CONN.
ON THIS PAGE→
Page sections appear in preview
01 / NAUTILUS CONN
A clear control point for a complex system
The operator needs to know which vessel is selected, who currently controls it and whether the information on screen is fresh enough to support the intended action.
CONN’s design brings vessel identity, active mode, authority lease, bearer health, navigation integrity, camera capture age, alerts and command outcomes into one view. Admitted demand, equipment acknowledgement and observed response receive distinct labels.
The operator can judge whether the available view and feedback support the next action.
02 / NAUTILUS CONN
Keep operator input subject to onboard checks
The initial prototype target is a Windows handheld with gamepad and touch input. Controller mappings, axis calibration, enabling action and input limits are versioned for the exact unit and commissioned vessel.
Continuous manual input has a short expiry and requires valid authority and feedback. Lost focus, device lock, controller disconnect, stale feedback, suspended application or a failed link withdraws that input according to the vessel profile. A recovered connection requires a fresh deliberate handover.
Every input enters the same typed command and WATCH admission path. The onboard boundary remains responsible for deciding which operation may proceed.
03 / NAUTILUS CONN
Review a destination before it becomes a mission action
A touch or click on a chart creates a destination proposal with the relevant coordinates, chart context and vessel state. The operator reviews it before separate explicit confirmation.
COURSE assesses the proposal using mission, operating-area and traffic constraints. WATCH checks authority, navigation integrity and interlocks before any resulting control intent reaches BRIDGE.
If the chart context, position or collision evidence is insufficient, the interface must explain why execution is unavailable.
04 / NAUTILUS CONN
Useful visibility under bandwidth pressure
Video and navigation state retain their capture or source times. Stale media becomes conspicuous, and a control mode that relies on it must be withdrawn when its limits are exceeded.
The design prioritises control, authority and health traffic ahead of video. A stream may degrade or stop when resources are constrained, with that change visible to the operator.
05 / NAUTILUS CONN
A trusted operator endpoint
CONN requires an enrolled device, authenticated operator session and commissioned Windows image. Application signatures, protected credentials and approved peripheral and driver inventories form part of the proposed field configuration.
External radios and cellular equipment require separate selection and testing. Supported route topology, SHACE integration and mode-specific timing must be demonstrated for the actual deployment.
The on-screen safe-state control is a remote request whose outcome must be shown. Physical emergency stop and local takeover remain independent vessel provisions.
06 / NAUTILUS CONN
Validate the experience against a real operating mode
An initial CONN discussion can define the observe-only workflow, simulator controls, destination review and authority display. Physical remote control requires the security, bearer, feedback and vessel gates to pass separately.
CONN is a working product name. The application, exact handheld configuration and operational SHACE connection need separate validation before field control. The current lab path does not establish a native Windows SHACE client.