Maritime AI Digest · 30 August 2026
Anschütz Wires Vision Into the Bridge — Then Hands the Manoeuvre to the Autopilot
Anschütz did two things in four days, and read together they describe the whole arc of bridge automation: on 24 August it announced the integration of SEA.AI's machine vision into its AUTONOMICS navigation suite, and on 27 August it unveiled AUTONOMICS CGA, a collision and grounding avoidance system that can transfer selected manoeuvres directly to the autopilot. First, the eyes. SEA.AI's technology identifies and classifies objects picked up by optical and thermal sensors — vessels, buoys, floating debris and people in the water — adding a fourth sensor track alongside radar, ENC and AIS. The gap it fills is specific and well known to anyone who has kept a watch: small targets, close-range objects, unlit craft, and vessels with no AIS transponder. SEA.AI CEO Marcus Warrelmann described the work as turning pixels into a classified object the system can act on. Anschütz's Hans-Christoph Burmeister called reliable detection of small objects "the missing link in existing commercial maritime sensor systems." Second, the hands. AUTONOMICS CGA fuses radar, AIS, charts and AI-enabled electro-optical and infrared sensors, continuously assesses encounters against COLREG requirements, calculates a safe manoeuvring area from vessel characteristics, chart data, traffic and navigational constraints, and generates collision-avoidance trajectories. It then does the thing that separates decision support from automation: selected heading-only actions transfer directly to Anschütz autopilots for execution. The stated benefit is reducing the manual analysis a navigator must perform by prioritising relevant targets. Development is aligned to the MASS Code, and CGA is entering a validation phase with selected customers as a standalone system compatible with various bridge configurations. Why the heading-only limit is the most interesting sentence in the announcement. Heading changes are recoverable, visible, and conventional under COLREGs; speed changes are the ones that surprise other vessels and unwind less gracefully. Restricting automatic execution to heading is a designer drawing a deliberate line — the same move we identified in BetterSea's compliance agent, which prices everything and executes nothing. The guardrail is again the product feature. Why this matters for ship managers: this is your bridge in three or four years. The commercial questions arrive before the regulatory ones: what happens to your bridge procedures when the system proposes a trajectory the officer disagrees with, who is accountable for an accepted proposal, and what your OOW does during a four-hour watch of supervising rather than deciding. What to do now: ask your bridge equipment supplier, at your next newbuild or retrofit specification, which actions their system can execute without confirmation, and how that boundary is configured. Get the answer in the specification, not the brochure. Then ask your DPA how an accepted automated manoeuvre would be recorded, because your incident investigation depends on being able to reconstruct who chose what. The honest caveat: no vessel deployments, customer names, validation timeline, detection accuracy figures, false-positive rates or commercial availability date have been published for either announcement. Validation with selected customers is a stage, not a result. SEA.AI's detection performance in the conditions that matter — heavy weather, glare, sea clutter — is asserted rather than published, and machine vision degrades precisely where you most want it. The MASS Code alignment is a design intention, not an approval. [SEA.AI integration · AUTONOMICS CGA]
This story is part of the Maritime AI Digest of 30 August 2026.
More on: Autonomous ships