Using the safety cameras
How ship and shore review a camera event, analyse a still, and hand it to a work order or an incident.
AI safety cameras turn a still from the ship into an event with a sentence: bridge watch, deck and mooring, the engine room, security, or a MARPOL sign. Video is meant to stay on board. The office sees the event, the still and the score. The fleet manager and the superintendent review the queue ashore. The master and the chief engineer review the events on their ship. In the demo, Ravi Menon and Capt. Erdem Yılmaz have edit on cameras. Kaan Erdem and Maren Holt have publish.
Dashboard and pages
Camera events is http://localhost:4400/app/cameras . It shows the FleetVision score for the fleet and for each area, the change over 30 days, open and critical counts, the events that need review, and a league of vessels with the worst score first.
Events is http://localhost:4400/app/cameras/events . Filter by area, severity, status, vessel and source. One event is http://localhost:4400/app/cameras/events/ and then the event id: the still, the timeline, and the actions below.
Camera walls is http://localhost:4400/app/cameras/vessels . A vessel opens her wall, a 48-hour timeline per area, her events, and the panel that analyses a still you upload. Integrations is http://localhost:4400/app/integrations/cameras .
Workflows
Acknowledge needs edit. It records who saw the event. Close needs edit, a note, and an outcome of closed or false positive.
Raise a work order needs publish (cameras.escalate with work_order). It plans a predictive work order for the next port call, titled from the event. Open an HSEQ incident needs the same publish level (cameras.escalate with incident). It does not create the incident. It marks the event so HSEQ can open one. The link stays pending until HSEQ writes the incident id, and that write also needs edit on cameras.
Analyse a still needs edit. You pick the vessel and the camera and upload a still of at most 2 MB.
Shared records
An escalated work order is a predictive-maintenance work order. An escalated incident is an HSEQ incident. The event page points at the maintenance list until a single order is linked. The oil-mist event on MV Aldersea also names the related planned-maintenance job. The risk score itself still belongs to predictive maintenance.
What the demo simulates
Every event, still, camera and activity bucket is generated. The stills are three pictures per vessel, reused per station. With no ANTHROPIC_API_KEY, analysis is a deterministic result of the image hash and is marked simulated_vision. The Claude vision call is wired only on http://localhost:4400/app/cameras/analyze . Sending cameras.analyze any other way stays simulated. No NVR and no edge box feed events.
Integrations
The ONVIF recorder, the onboard edge AI box and Anthropic vision are mocks. See Connections and the module reference.