Quick Reference

Menu map, the demo data set and what its codes mean, the status vocabularies, and rules of thumb.

Menu map (10 groups, 54 models)

The demo data set

One coherent narrative — a single operator, a single vessel, one operating cycle, 139 rows across all 54 models. Start at Vessels → Southern Trader and follow the drill-downs.

The players

The headline scenario (pre-departure fire-pump defect)

Status vocabularies (the enums you will see)

• Vessel — ACTIVE, LAID_UP, SUSPENDED, SOLD, DECOMMISSIONED
• VesselCertificate.verification_status — UNVERIFIED, VERIFIED, EXPIRED, SUSPENDED, REVOKED
• SafetyManagementSystem — DRAFT, UNDER_REVIEW, APPROVED, CURRENT, SUPERSEDED, WITHDRAWN
• PersonQualification.verification_status — PENDING, VERIFIED, EXPIRED, SUSPENDED, REJECTED
• FitnessForDutyDeclaration.fatigue_status — FIT, FIT_WITH_CONTROLS, UNFIT
• RiskControl.effectiveness_status — PROPOSED, IMPLEMENTED, EFFECTIVE, DEGRADED, INEFFECTIVE
• Defect.severity — OBSERVATION, MINOR, MAJOR, CRITICAL
• Defect.operational_effect — NONE, DEGRADED, RESTRICTED, UNAVAILABLE, UNSAFE
• Defect.defect_status — REPORTED, ASSESSED, CONTROLLED, REPAIR_PLANNED, UNDER_REPAIR, MONITORING, CLOSED, DEFERRED
• MaintenanceWork.work_status — REQUESTED, PLANNED, IN_PROGRESS, AWAITING_PARTS, COMPLETED, VERIFIED, CLOSED, CANCELLED
• VesselInspection.overall_result — PASS, PASS_WITH_OBSERVATIONS, FAIL, INCOMPLETE
• Voyage.voyage_status — PLANNED, READY, DEPARTED, UNDERWAY, DELAYED, ARRIVED, COMPLETED, CANCELLED
• VoyageReadiness.overall_result — READY, READY_WITH_CONDITIONS, NOT_READY
• Incident.severity — NEAR_MISS, MINOR, SERIOUS, VERY_SERIOUS
• Incident.incident_status — REPORTED, TRIAGED, INVESTIGATING, ACTIONS_OPEN, READY_TO_CLOSE, CLOSED
• CorrectiveAction.action_status — OPEN, ASSIGNED, IN_PROGRESS, AWAITING_VERIFICATION, CLOSED, OVERDUE, CANCELLED
• AuditFinding.finding_type — CONFORMITY, OBSERVATION, IMPROVEMENT, MINOR_NONCONFORMITY, MAJOR_NONCONFORMITY

Rules of thumb

• Follow the vessel. Almost every record hangs off Vessel; open Southern Trader and use the drill-down tabs to reach its certificates, SMS, crew, maintenance, voyages, incidents and audits.
• A certificate that exists is not a certificate that is current. Check verification_status and expiry_date, not just the presence of a row.
• A voyage is only as good as its readiness assessment. A Voyage with an open critical Defect should carry a NOT_READY VoyageReadiness — the demo shows both the block and the release.
• Reporting ≠ investigation ≠ action. An Incident links to a separate IncidentInvestigation and one or more CorrectiveActions; a finding or a defect can each spawn their own action, tracked independently to verification.
• Roles are distinguished on purpose. Where a table references Person through more than one column (assessed-by vs approved-by, reported-by vs verified-by), each is its own drill-down tab — that separation is the whole assurance argument.
• The workflow rules are documented, not enforced. Numbering masks, the readiness gate, the three-way separation and closeout are all held by the demo data rather than validated by the app (Phase 2).