Every vessel under the Workboat Code needs a Safety Management System — remotely-operated and uncrewed included — and has since the Code came into force on 13 December 2023. No grace period.
SMS Uncrewed builds that system, turns the telemetry already flowing through your ROC into surveyor-ready evidence, and is built by people who speak both autonomy and surveyor.
An SMS for a remotely-operated vessel isn't coming — it's been mandatory since the day the Code came into force. What a surveyor actually wants is a system that's started, honest and evidenced — not a flawless binder. We make that evidence the byproduct of your telemetry, not a paperwork project.
▸ Workboat Code Edition 3 — in force 13 December 2023, no grace period · MGN 710 §1.2 (systems proportionate to size, complexity & risk).
Two sites, one system. The Code treats your vessel and your Remote Operations Centre as a single SMS — and the evidence has to join them up.
No purpose-built tool. So the compliance record lives in spreadsheets, shared drives, and someone's memory — improvised, and fragile at survey.
Telemetry ≠ evidence. Battery health, sensor status, watch logs already stream through your ROC. Nothing is turning that stream into a cited, dated record.
We don't touch your perception or control stack. That's your turf. We're the compliance, evidence and intelligence layer around the vessel.
The full SMS: certificates, risk assessments, the append-only working log, drills, personnel & competency, ROC procedures — audit-grade and cited, one canonical record spanning vessel + ROC. This is the engine we've already shipped to crewed workboats, tuned to Annex 2.
Battery thermal-runaway early-warning signatures, sensor cross-checks, watch-manning gates — deterministic rules first, lead-times expressed as ranges conditional on your sensors. No "predictive," no remaining-useful-life hand-waving. We build this with your telemetry, not against a datasheet.
Retrieves and cites the Code, drafts the evidence pack, surfaces what's due — and declines the verdict. Compliant-or-not stays with your surveyor. It is fenced to never invent a requirement or a safety-critical number.
Every vessel sharpens the next one's evidence and early-warning — fault patterns, calibration drift, survey-day questions. The moat a spreadsheet can't grow. Built once the design partners are live.
An "ask about the Code" assistant sits on the site and in the product — sealed: no tenant data, PII-scrubbed, cheapest-model, rate-limited, and cite-or-decline. It quotes the Code and refuses the ruling. That's the whole product's AI posture, on display.
To crewed commercial workboats, in production, built by marine engineers — not guessed at from an office.
Perception and control are yours. We're the layer around the boat — no competitive overlap, no IP risk to your core.
Fenced, cited, no overclaim. A skeptical engineer can read exactly where the AI acts and where it stops.
The output is what an inspector actually asks for — dated, cited, evidenced. NVIDIA Inception · Plymouth cluster.
Reveal only once the inspector endorsement is real.
Reveal only with cited LR/ABS/DNV specifics.
Not a sign-up. A conversation. Tell us where the compliance grind actually hurts and we'll show you what we'd build with you. Five questions to start:
Honest AI · cite-or-decline
Built on a shipped, audit-grade SMS
Marine engineers who speak surveyor
Plymouth autonomy cluster
