PROJECT NAUTILUS · FREQUENTLY ASKED QUESTIONS
Your questions about NAUTILUS
Find out what NAUTILUS covers, how the licensing model works and what needs to be established for your vessel.
IN DEVELOPMENT · PILOT CONVERSATIONS OPEN
What is PROJECT NAUTILUS?
NAUTILUS is an AIC development programme for a proprietary, licensable maritime integration and autonomy platform. It brings secure communications, onboard camera intelligence, qualified navigation state, planning, software authority and vessel adapters into one architecture for crewed and uncrewed vessels.
Is NAUTILUS available as a production product?
NAUTILUS’s working engineering specification defines a development and migration target. Production configurations, supported adapters, operational security profiles, pricing and physical-control evidence remain to be established. Talk to AIC about a technical discussion or pilot that fits your vessel.
What are the six modules?
WAVE handles application communications and delivery evidence. HORIZON provides onboard camera observations. RECKON supplies navigation state and integrity. COURSE proposes mission actions. WATCH governs authority and software interlocks. BRIDGE translates authorised intent into the commissioned equipment interface and returns measured feedback.
Where does SHACE fit?
SHACE is the external secure packet-tunnel dependency used for permitted WAVE routes. It is separate from the six NAUTILUS modules. WAVE still authenticates its application peer, while WATCH assesses command authority aboard the vessel.
Does NAUTILUS use post-quantum cryptography?
Operational remote command requires a reviewed post-quantum SHACE profile. The documented SHACE lab profile uses ML-KEM-1024, ML-DSA-87 and an AES-GCM packet path. Its operational profile, supported topology and assurance remain release gates; lab evidence does not establish production certification.
What does edge protection include?
The design covers device identity, minimum service permissions, protected credentials, signed updates, controlled model and adapter activation, bounded resources and auditable command admission. Secure or measured boot, encrypted storage and hardware-backed key protection are evaluated on the actual selected host.
Is the platform open source?
The NAUTILUS core is intended to remain proprietary and licensed by AIC. Open integration refers to documented, versioned contracts that authorised customers and builders can implement under agreed SDK and licence terms.
Who owns the hardware, data and adapters?
The proposed model gives customers ownership of their selected hardware, commissioned installation, operational data and adapters they author, subject to agreed terms. AIC retains the core platform IP. The final contract defines rights, support, portability and third-party obligations.
Can customers integrate their own ECU and sensors?
That is the purpose of the adapter model. Each device needs a supported physical connection, documented protocol, signed capability declaration and conformance evidence. A generic connector alone does not establish compatibility. Control requires WATCH authority and a commissioned BRIDGE adapter.
Can a mission continue without communications?
A signed mission staged aboard may continue while its authority, required data, navigation, feedback and reserves meet the approved limits. A failed prerequisite causes the defined contingency. This capability must be proved for the named mission and vessel.
Can NAUTILUS operate without GNSS?
Permitted behaviour depends on the remaining validated sensors and the function being exercised. RECKON reports degraded or denied navigation and preserves uncertainty. A heading-based function may remain possible while position-dependent waypoint following is unavailable. Universal GNSS-denied navigation is not an established capability.
Can HORIZON identify military ships?
The initial model baseline is vessel detection. Military or naval-subtype outputs require a suitable signed model and separate validation evidence for the supported classes and conditions. Visual appearance remains an observation rather than verified identity or intent.
Does camera detection provide target range?
The initial design provides an approximate bearing, with an absolute bearing only when valid heading and calibration support it. Baseline range is unavailable. Target localisation and approach workflows require additional validated evidence.
What is NAUTILUS CONN?
CONN is the working name for the Windows operator application in development. Its functions cover vessel state, control ownership, link quality, video age and command outcomes, with supervised controls subject to vessel approval. Its prototype and supported device configuration require separate validation.
Can the platform use radio, cellular and cloud relay?
Those are bearer options to evaluate with the selected equipment, topology and network limits for each mode. Azure Relay is a candidate whose composition with the required end-to-end SHACE route remains an integration decision. Available bandwidth alone does not establish suitability for remote control.
How are commands and outcomes recorded?
The design separates application delivery, WATCH admission, equipment acknowledgement and measured vessel response. Correlated audit evidence links the principal, policy, identifiers, decisions and outcomes. An uncertain post-dispatch result remains outcome unknown until reconciled.
Is the software a vessel safety approval?
WATCH provides a defined software authority and interlock boundary. Whole-vessel safety, physical emergency arrangements and operating approval require the builder, operator and relevant approval parties to establish the case for the installed vessel and intended use.
How is pricing structured?
Pricing is to be agreed. The intended model makes the core licence, integration, hardware, commissioning, support and optional managed services visible. A commercial discussion should cover vessel count, required functions, offline use and ongoing maintenance.
What should we bring to a first discussion?
A non-sensitive outline of the vessel type, mission, equipment interfaces, operating area, security requirements and project stage is enough to start. We can use those inputs to identify the relevant modules and a realistic evaluation scope.