Using vetting
How the shore records an inspection, answers an observation and closes it.
Vetting is the preparation for SIRE 2.0, CDI, PSC, flag, terminal and TMSA inspections, and the close-out of the observations they leave. The vetting superintendent ashore records the inspection and drafts the response. A person with publish closes the observation. In the demo Sofia Lindqvist has edit. Kaan Erdem and Maren Holt have publish. The master has view and can read the pack. He cannot close an observation.
Dashboard and pages
The overview is http://localhost:4400/app/vetting . It shows the gap score each vessel carries into the next inspection, the items behind that score, open observations, inspections that are due, and a link to each vessel’s evidence pack.
Inspections is http://localhost:4400/app/vetting/inspections . One inspection is that path plus the id: observations, responses, evidence links and close-out.
TMSA is http://localhost:4400/app/vetting/tmsa . Thirteen elements, each with a self-assessed stage from 1 to 4 and the evidence for that stage. The evidence pack is http://localhost:4400/app/vetting/evidence/ and then the vessel id. Integrations is http://localhost:4400/app/integrations/vetting .
Workflows
Record an inspection needs edit (vetting.inspection.record). The button is Record inspection. A planned inspection has no result. A date in the past needs one. There is no action to mark a planned inspection done later. Record the done inspection as a new one.
Respond needs edit (vetting.observation.respond). You write the response and you may attach evidence links. Close needs publish (vetting.observation.close). The button is Close.
Update a TMSA stage needs edit (vetting.tmsa.update). The stage is 1 to 4 and the evidence text is required. view is enough to read scores, inspections and the pack. An agent cannot close an observation.
Shared records
PSC readiness stays in certificates. The evidence pack shows that score and links to http://localhost:4400/app/documents/psc . It does not keep a second number. Gap-score weights are illustrative. A term from a module the viewer cannot see counts as zero, and the page says which module.
What the demo simulates
Inspections, observations, inspector companies, SIRE and PSC references and the TMSA stages are generated. No SIRE report is imported. The OCIMF and Q88 connectors are mocks.
Integrations
OCIMF SIRE 2.0 and Q88 are mocks. See Connections and the module reference.