Using predictive maintenance
How an alert becomes a work order at the next port, and who may notify the crew.
Predictive maintenance is the queue of components that are drifting away from the model. Each alert carries a failure probability and the days left, so the superintendent can put the work on the next port call instead of waiting for a breakdown. The chief engineer reads the alerts for the ship and can acknowledge them. The underwriter does not have this module. Tom Achebe’s access is insurance and cameras only, so this queue is hidden from him.
Dashboard and pages
Alerts is http://localhost:4400/app/alerts . Open alerts sit on a matrix of failure probability against days left, with the components that are alerting. Each row has the vessel, the component, the symptom, the probability, the days left and the status. One alert opens http://localhost:4400/app/alerts/ and then the id.
Risk insights is http://localhost:4400/app/risk . It shows the risk score per vessel and its top driver, the 90-day fleet trend, alerts per week by severity, the false-positive rate and the time to resolve.
Work orders is http://localhost:4400/app/maintenance . Orders raised from alerts are grouped by port call, with overdue and completed work beside them. Integrations is http://localhost:4400/app/integrations/predict .
Workflows
Acknowledge an alert and resolve it need edit (alert.acknowledge, alert.resolve). Create a work order and change its status need edit (workorder.create, workorder.status).
Notify crew needs publish (alert.notify). The button sends the alert to the ship by email or satcom. In the demo it shows a notice and sends nothing. Dismiss a critical alert needs publish (alert.dismiss). Lower severities can be closed with edit. Agents never hold publish, so Watchkeeper can edit alerts and cannot notify or dismiss a critical one.
Shared records
The risk score on the fleet map, on the insurer’s screen and on the camera league is this module’s score. The work order is the same record the port-call page lists for that vessel and port. A camera event can raise one of these work orders. The planned-maintenance job card is a different record. It is the class and hours job, not this alert.
What the demo simulates
MV Aldersea’s main-engine bearing temperature sits above the predicted band: critical, 72 % within 9 days, with Rotterdam in 4 days. MV Northwind’s auxiliary engine lube-oil pressure is low. MV Pacifica shows a sensor gap. The history includes a dismissed false positive. Machinery values are generated. No historian is polled.
Integrations
The MQTT gateway, the Siemens historian, ABB, Rolls-Royce MTU, Iridium and WhatsApp are mocks. Notify crew does not call them. See Connections and the module reference.