Cruise Voyage Operations Management
Operation of cruise voyages — itinerary planning, port and shore excursion operations, onboard cabin and guest programmes, marine and bridge operations, embarkation, and shipboard health and sanitation — delivered against international maritime safety regulation.
Cruise Voyage Operations Management (BC-4090) is a level-1 business capability in the Travel & Hospitality model. The catalog holds 0 API surface(s) from 0 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Authorities this capability cites
Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.
Sub-capabilities
Voyage Itinerary Planning BC-4090.10
Planning of voyage itineraries, deployment, repositioning, and itinerary substitution decisions.
Port & Shore Excursion Operations BC-4090.20
Operations at port calls including turnaround, tendering, and shore excursion catalogue, sales, and delivery.
Onboard Cabin & Stateroom Operations BC-4090.30
Onboard cabin and stateroom operations including turnover, assignment, mid-cruise upsell, and specialty-suite service.
Onboard Guest Programme Operations BC-4090.40
Onboard entertainment, activities, kids' clubs, and specialty venue operations across the voyage.
Marine & Bridge Operations BC-4090.50
Marine and bridge operations covering navigation, propulsion, port documentation, and provisioning coordination.
Onboard Embarkation & Disembarkation BC-4090.60
Embarkation and disembarkation operations including pre-boarding verification, customs clearance, and onboard baggage flow.
Cruise Health & Sanitation Operations BC-4090.70
Onboard health and sanitation operations including inspection readiness, outbreak detection and response, and water and pool sanitation.
Providers that reach this capability
No provider in the catalog currently publishes an API surface that reaches this capability. That is a real answer, not a gap in the page: much of what an enterprise does runs on internal systems that publish no API at all.