VESSEL, SENSOR AND EDGE INTEGRATION
Connect your vessel to NAUTILUS
Bring the equipment that suits your vessel. NAUTILUS uses documented, versioned interfaces to connect its licensed core with selected sensors, machinery and communications hardware. The platform is in development, with each supported configuration established through integration and testing.
IN DEVELOPMENT · PILOT CONVERSATIONS OPEN
NAUTILUS / FILM
See the integration boundary.
ON THIS PAGE→
Page sections appear in preview
01 / NAUTILUS
Start with the vessel and the intended effect
Start with the task and the equipment available to deliver it. Identify the hull, propulsion and steering arrangement, ECU, physical overrides, sensors, power and operating limits.
NAUTILUS’s intended partner ports cover sensing, vessel state, machinery health, control intent and feedback, mission-device status or actions, media and communications. Each capability needs a named source, declared semantics and acceptance evidence.
02 / NAUTILUS
Connect through a versioned adapter contract
The BRIDGE integration contract records capabilities, units, time basis, supported commands, ranges, timing, cancellation and failure behaviour. Signed adapter packages bind that contract to the named device, firmware and vessel scope.
Documented vendor APIs and candidate Ethernet, isolated CAN, serial, USB or approved I/O interfaces can provide the physical route. Marine protocol use remains subject to the applicable licensing, device support and conformance requirements.
Each adapter is tested against the connected equipment. Its supported functions are declared, so the operator knows what is available and the planner can account for missing capability.
03 / NAUTILUS
Choose an edge host for the whole installation
The specification considers industrial mini PCs and Jetson-based systems, with exact support to follow commissioning. Selection must cover inference capability, native dependencies, operating system, drivers, secure storage, network separation, power and thermal behaviour.
The assembled enclosure, cables, connectors and interface modules need their own environmental evidence. IP65/IP66-class construction is a target for a selected assembly, subject to its actual test record. Component specifications alone cannot establish the ingress rating of the installed system.
04 / NAUTILUS
Harden the image and the peripheral boundary
The proposed host acceptance records software and firmware versions, enabled services, process permissions and the peripheral inventory. Secure or measured boot, encrypted storage, protected device credentials and signed update paths are evaluated on the selected configuration.
Approved external radios, cellular equipment and associated drivers become part of that configuration. A communications path must demonstrate peer identity, SHACE topology and the timing envelope required by its operating mode.
05 / NAUTILUS
Build evidence in stages
1. Define the integration. Agree the mission, equipment, ownership matrix, threat model and acceptance boundaries.
2. Establish read-only evidence. Connect sensing and machinery health, preserving source, units, timestamps and quality.
3. Exercise the adapter in simulation. Prove supported intent, range limits, watchdogs, disconnects and feedback semantics.
4. Evaluate the assembled system. Run hardware-in-loop, power, resource, security and fault tests on the named configuration.
5. Commission the vessel mode. Progress to bounded physical trials with the appropriate safety case, supervision and operating approval.
06 / NAUTILUS
An integration kit with a clear commercial boundary
The planned licensed kit includes a capability manifest schema, simulator support, a read-only adapter example, control conformance checks and fault fixtures. Supported contracts, access, maintenance rights and migration arrangements will be defined in the agreed licence.
AIC retains the core platform IP. Customer equipment, data, self-authored adapters and partner component IP are addressed explicitly in the commercial agreement.
Talk to AIC about the equipment aboard, the software interface it provides and the work needed to connect it.