A short fleet snapshot

• Tell me briefly which parts of your fleet operations this project should touch Options: Voyage planning, Crew scheduling, Passenger manifest and immigration, Port logistics, Onboard revenue and POS, Regulatory documentation, IT/infrastructure, Other
• How many vessels do you expect to be in scope for the next 12 months Options: 1 (pilot only), 2-3, 4-7, 8-15, More than 15
• Walk me through a typical itinerary complexity for vessels in scope, including number of ports and jurisdiction changes per cruise Options: Mostly regional with few jurisdictions, Multiple countries per itinerary, Global itineraries across many jurisdictions, Mixed profile across fleet
• Which teams will be primary users of the platform on shore and on board Options: Shoreside voyage planning, Shipboard operations/bridge, Crew management, Port logistics team, Revenue management/retail ops, Compliance and safety, IT/Integrations
• If you had to pause adding new vessels today, what single operational bottleneck would force that decision

Where the pressure builds: recent operational shocks

• Which recurring operational failure costs you the most in fines, delays, or guest impact Options: Port documentation/compliance, Crew scheduling conflicts, Manifest inaccuracies, Onboard revenue reconciliation, Integration outages with reservation systems, Other
• Describe a recent incident where compliance or port requirements created an unexpected delay or fine, and who managed the response
• How often do crew scheduling errors lead to labor disputes, unmet minimum complements, or regulatory risk Options: Weekly, Monthly, Quarterly, Rarely, Never
• How do limited connectivity windows affect mission-critical shipboard workflows like manifest submission or POS reconciliation Options: Major impact daily, Occasional operational delays, Minor inconvenience, No meaningful impact
• Which single failure in these operational areas would make you halt a pilot or require immediate remediation before proceeding

Hidden costs and knock-on effects

• Which downstream cost or reputational impact tends to be overlooked until it becomes urgent Options: Port detention risk, Passenger compensation and rebooking, Crew overtime and penalties, Revenue leakage from POS discrepancies, Regulatory fines, Other
• On average how many disruptive operational events require escalation to senior leadership per year Options: 0-2, 3-6, 7-12, More than 12
• Who currently pays the cost when an operational integration fails between ship and shore Options: Shoreside operations budget, IT/engineering, Vessel operations, Shared/unclear
• When these disruptions occur, which metrics do you track to measure impact Options: Minutes of delay, Fine amount, Guest complaints, Revenue adjustment, Crew overtime hours, Other
• Which operational assumption do you most worry might be wrong as we scope a pilot

Who's in the room and who gets called at 2 AM

• Who gets notified first when a system error threatens a sailing Options: Shipboard master/operations, Shoreside operations lead, IT/Network team, Commercial/revenue ops, Other
• Which shipboard and shoreside roles must be involved for a pilot to be considered valid Options: Master/Bridge officer, Shipboard IT admin, Shoreside voyage planner, Crew scheduling owner, Compliance officer, Revenue manager, Integration owner
• Who must sign off on data sharing, API access, and port manifest changes Options: Shoreside operations, Legal/compliance, IT/security, Vessel captain, Other
• Walk me through your typical 2 AM escalation for voyage disruptions, including who makes the call to change course or call ports
• Is there anyone who can veto a pilot, and if so who and on what grounds

The alternatives you're weighing

• Which solution types are you actively evaluating alongside an external platform Options: Staying with incumbent vendor, Building internal solution, Point solutions for crew or manifests, Integration middleware only, Do nothing, Other
• Has anyone proposed solving this entirely with internal resources, and if yes did they outline timeline and headcount Options: Yes with timeline and headcount, Yes without details, No, Undecided
• What would have to be demonstrably true about your current approach for you to keep it rather than move to an external platform
• Which incumbent capability, if present today, would remove the need for change Options: Complete manifest automation, Crew scheduling rule engine, End-to-end integration with reservations, Connectivity-resilient sync, None of the above
• If the pilot delivers the expected operational gains, what would stop you from converting to a fleet rollout within your target window

The hard constraints that will make or break this project

• Which integration or regulatory dependency could derail your timeline if it takes longer than planned Options: Reservation system API access, Port authority approvals, Crew union consultation, Flag-state compliance review, Network/VPN provisioning, Other
• Which onshore systems must we integrate with and are APIs available for those systems Options: Reservation/booking system API available, Crew management system API available, Shoreside POS/revenue system API available, No APIs available, Partial APIs
• Who owns those APIs and who will be our day-to-day technical contact
• Is your historical guest, booking, and crew data centralized and accessible for migration Options: Centralized and accessible, Partially centralized, Fragmented across systems, Not available
• Which single missing prerequisite would force us to delay the pilot

Testing the solution in real conditions: pilot success criteria

• Which measurable acceptance metric would make you sign off on a single-vessel pilot the same week the tests succeed Options: On-time manifest submissions X% improvement, Crew schedule accuracy X% improvement, POS revenue reconciliation within X hours, No critical outages during connectivity blackouts, Other
• Which workflows must be demonstrably resilient under limited connectivity during the pilot Options: Manifest submission, Crew schedule updates, POS offline reconciliation, Safety-critical messaging, Passenger manifest amendments
• How will you quantify passenger and revenue impact during the pilot Options: Guest complaint counts, Onboard spend variance, Reconciliation errors, Net promoter score change, Other
• Who will provide shipboard test resources and approve the test windows for cutover drills Options: Shipboard operations, Master/bridge, Shipboard IT, Shoreside operations, Other
• If the pilot fails to meet the connectivity resilience acceptance, do you have contingency funds or schedule flexibility to re-run testing Options: Yes, No, Maybe/depends

Operational handoffs and scale: configuration, training, and rollout boundaries

• Which pilot configuration choices would be hardest to change once we start fleet rollout Options: Data retention/migration approach, Crew scheduling rule sets, Integration endpoints and field mappings, Authentication and access models, Sync frequency and failover rules
• Which integrations require one-time migration versus continuous sync for ongoing operations Options: Reservation system - continuous, Crew HR system - migration then sync, POS - continuous, Port authority filings - periodic
• Who will own training and change management for vessel crews and shoreside teams during rollout Options: Shoreside training team, Shipboard training officers, Third-party training partner, Combined responsibility
• What are the typical port or operational windows you require for a cutover, and how often do those windows appear per quarter Options: Weekly, Biweekly, Monthly, Quarterly, Irregular/depends on itinerary
• If training uptake on the first two vessels is below your threshold, what would you do Options: Pause rollout and retrain, Proceed with extra shoreside support, Re-evaluate timeline, Escalate to leadership

Commercial gates and decision timing

• Which internal deadline would force you to make a vendor decision regardless of pilot timing Options: End of this fiscal quarter, End of this fiscal year, Before next vessel delivery, No hard deadline
• What budget range is provisioned for the pilot and initial rollout phase Options: Pilot only - under $50k, $50k-$150k, $150k-$500k, Over $500k, Not yet budgeted
• Who in procurement or legal must sign commercial and data processing terms Options: Procurement lead, Legal counsel, Compliance officer, IT/security
• If the pilot proves value, how quickly can your organization convert to a commercial commitment and begin fleet rollout Options: Immediately within 2 weeks, Within 1 month, 1-3 months, Longer than 3 months
• If the key approval or budget item is not delivered by the end of this fiscal quarter, will that stop the deal Options: Yes, No, It depends

Final practicalities before we schedule a pilot

• Which practical item missing from this list would prevent a pilot from starting in your next available port window Options: API credentials, Shoreside VPN access, Shipboard admin user, Port window approval, Crew training slot, Data extract for migration, Other
• Who on your side is authorized to sign the pilot statement of work Options: Operations director/VP, Procurement lead, IT/security lead, Legal signatory, Other
• Which shipboard connectivity profile best matches the vessel we would pilot Options: High bandwidth, few blackouts, Variable bandwidth with planned blackouts, Low bandwidth with frequent blackouts, Unknown
• When is the next realistic port window you could make available for a cutover test Options: Within 2 weeks, 2-6 weeks, 6-12 weeks, More than 12 weeks, Unsure
• If we present a joint plan that addresses the items above, can you commit to scheduling the pilot within your next available window Options: Yes, Maybe, No

• Solution Walkthrough: Validated Operational Workflows

• Confirm the current state and its cost to your team
• You confirm the demonstrated voyage and crew workflows eliminate the manual reconciliation you described.
• Provide one representative itinerary with recent change events and one recent crew roster including union constraints for use in the end-to-end scenario runs.
• You confirm the demonstrated connectivity resilience behavior meets your operational risk threshold for the pilot vessel.
• Walk a voyage-planning scenario end-to-end
• Provide the list of ports of call that historically cause the most compliance or documentation failures and any recent examples of port-state findings.
• Seller to deliver a tailored workflow diagram mapping your provided scenarios to the proposed shipboard and shoreside steps within three business days of this session.
• You agree on the measurable acceptance criteria and the remaining evidence required before pilot authorization.
• Validate a crew-scheduling scenario with union and flag rules
• Seller to run a connectivity resilience simulation using the provided itinerary and deliver the test log and reconciliation behavior report before the pilot kickoff decision.
• You identify the pilot vessel and confirm the initial scope of scenarios to run during the single-vessel pilot.
• Show compliance document flow and a limited-connectivity resilience test
• Confirm acceptance criteria and remaining evidence
• Confirm the single-vessel pilot candidate and a two-week pilot window for integration and acceptance testing.
• Forced validation, confirm this matches what you meant

• Solution Walkthrough: Validated Operational Workflows
• Solution Experience Deck
• Solution Brief - Solution Walkthrough

• meeting
• slides
• document

• Migrate Guest and Booking Records
• Data Cleansing and Deduplication for Legacy Records
• Deploy Shipboard Offline Sync and Local Cache
• Integrate Reservation and Revenue-Management Systems
• Build API Integrations and Endpoint Mapping
• Configure Voyage Planning and Routing Engine
• Implement Crew Scheduling with Labor Rule Enforcement
• Deploy Passenger Manifest and Immigration Exports
• Install Port Call Logistics and Terminal Messaging
• Deploy Onboard POS, Inventory, and Revenue Reconciliation
• Configure Regulatory Compliance Documentation and Filing
• Run Single-Vessel Pilot Deployment and Go-Live
• Fleet-wide Rollout and Systems Cutover Support
• Train Shoreside and Onboard Users

Migrate Guest and Booking Records

• How many years of guest history and booking records must be migrated for initial cutover? Options: Less than 1 year, 1-3 years, 4-10 years, More than 10 years
• List the source systems that contain reservations and guest profiles (legacy reservation DB, loyalty CRM export, onboard PMS, spreadsheets). Options: Legacy reservation database, Loyalty CRM export, Onboard PMS, Spreadsheet exports, Other
• Identify the unique identifiers that must be preserved to reconcile bookings with onboard records (reservation ID, booking reference, loyalty ID, passport number).
• Provide the migration completeness percentage and maximum allowable duplicate or unmatched record rate you will accept as evidence of a successful guest and booking migration. Options: 95% complete / <=1% duplicates, 98% complete / <=0.5% duplicates, 99% complete / <=0.1% duplicates, Custom
• In what export formats can your reservation system produce booking and guest payloads for mapping (CSV, XML, JSON, EDI)? Options: CSV, XML, JSON, EDIFACT/EDI, Other

Data Cleansing and Deduplication for Legacy Records

• Do you have a canonical source of truth for guest contact details (shore CRM, onboard PMS) that should be used during deduplication? Options: Shore CRM, Onboard PMS, No single source, Other
• Describe the legacy identifier combinations used to detect duplicate guests (for example name+date of birth+passport, email, loyalty ID).
• Specify the data quality thresholds to apply during cleansing (percent complete for contact fields, valid passport rate). Options: 70% complete, 85% complete, 95% complete, Custom
• Will duplicates be auto-merged at a confidence threshold or routed to a manual review queue for ambiguous matches? Options: Auto-merge with confidence threshold, Manual review for ambiguous matches, Hybrid approach
• Are there regulatory or privacy constraints that prevent migrating certain PII or free-text legacy notes for passengers? Options: Yes, No

Deploy Shipboard Offline Sync and Local Cache

• Name the shipboard systems that must continue to operate during full offline periods (voyage plan, crew roster, passenger manifest, POS). Options: Voyage planning, Crew roster, Passenger manifest, Onboard POS, Other
• Estimate the maximum offline period the shipboard cache must support between shore synchronizations. Options: Up to 6 hours, 6-24 hours, 24-72 hours, 72+ hours
• At what cadence should the ship publish sync heartbeats or status to shoreside when connectivity is available? Options: On every change, Hourly, 4x per day, Custom
• Using what shipboard hosts will the local cache reside (ship server, POS terminals, crew tablets)? Options: Ship server, POS terminals, Crew tablets, Hybrid
• Within what recovery window must offline sync conflicts be resolved once connectivity is restored? Options: <15 minutes, <1 hour, <4 hours, Custom

Integrate Reservation and Revenue-Management Systems

• Select the reservation and revenue systems that must be integrated at go-live (booking engine API, CRS exports, RMS feeds, payment gateway). Options: Booking engine API, Central reservation system (CRS), Revenue management system (RMS), Payment gateway, Other
• How many key business events require near-real-time synchronization to the platform (booking created, booking modified, cancellation, payment captured)? Options: 1-2 events, 3-4 events, 5+ events
• Does your reservation system publish webhooks or only batch exports that will affect integration latency? Options: Webhooks / real-time API, Batch exports (SFTP/API polling), Both
• Who on your team will own day-to-day reconciliation between the reservation system and onboard POS revenue?
• By what method are historical bookings exported for initial reconciliation and baseline (full CSV export, incremental API feed, SFTP batches)? Options: Full CSV export, Incremental API feed, SFTP batches, Other

Build API Integrations and Endpoint Mapping

• Provide the authentication mechanisms your endpoints support for integrations (OAuth2, API key, Basic Auth, mutual TLS). Options: OAuth2, API key, Basic Auth, mTLS (mutual TLS), SFTP
• In what payload formats must we deliver and consume data for integration mapping (JSON, XML, CSV, EDIFACT)? Options: JSON, XML, CSV, EDIFACT/EDI, Other
• Do you have OpenAPI/Swagger or formal API documentation available for endpoint mapping and test harness development? Options: Full OpenAPI/Swagger, Partial docs, No formal docs
• Who is the technical owner for each endpoint to approve mappings and provide test credentials?
• Identify any middleware, ESB, or message queue components that must be registered with for production integration (e.g., MQ, Kafka, ETL server). Options: Message queue / ESB, ETL jobs, Integration platform as a service, None

Configure Voyage Planning and Routing Engine

• List the voyage planning artifacts you need imported or produced (route polylines, port call ETAs/ETDs, berth constraints). Options: Route polylines, Port call ETAs/ETDs, Berth constraints, Fuel consumption profile, Other
• Are there regulatory overlays to enforce in routing such as Emissions Control Areas, mandatory pilotage zones, or traffic separation schemes? Options: Yes, No
• Will automatic fuel-optimized routing be enabled or will voyage adjustments require manual shoreside approval? Options: Automatic with approval workflow, Manual only, Hybrid
• Within what ETA variance should guest and crew notifications be triggered (minutes/hours)? Options: <15 minutes, 15-60 minutes, 1-3 hours, Custom
• Should berth and terminal time-window constraints block automated scheduling when violated? Options: Yes, No

Implement Crew Scheduling with Labor Rule Enforcement

• State the number of crew roles and contract types the scheduler must support (officers, ratings, hotel staff, contracted vendors). Options: Fewer than 10, 10-30, 30+
• Indicate the specific labor rules that must be encoded (maximum hours, rest periods under STCW, union shift rules). Options: STCW rest hour rules, Union shift rules, Maximum hours per day/week, Other
• Name any shore-leave or visa constraints per nationality that must be enforced when building rosters for port calls.
• Specify the roster change SLA required when a substitution or emergency change is needed prior to sailing. Options: <2 hours, 2-24 hours, 24+ hours
• By whom will certificates, medicals, and passport expiries be validated and synchronized to shipboard devices?

Deploy Passenger Manifest and Immigration Exports

• Indicate the export formats required by each port authority you call (API, CSV, local XML schema, eManifest). Options: API (REST), CSV export, Local XML schema, eManifest portal, Other
• State the mandatory fields that must appear on manifests for your busiest ports (passport number, nationality, place of birth, cabin number).
• When are typical manifest cut-off windows for your busiest ports (hours before arrival)? Options: >24 hours, 12-24 hours, 6-12 hours, <6 hours
• Choose whether automated visa and shore-entry checks should be executed against manifest data prior to submission. Options: Yes, run automated checks, No, manual checks only, Hybrid
• In what transmission methods do port authorities require manifests (SFTP, HTTPS with mTLS, email with PGP)? Options: SFTP, HTTPS with mTLS, Email with PGP, Portal upload

Install Port Call Logistics and Terminal Messaging

• Select the terminal messaging formats your port and terminal partners use (custom XML, SFTP batch, REST callbacks). Options: Custom XML, SFTP batch, REST callbacks, EDI
• Does your port call stakeholder list include terminal ops, ground handlers, provisioning vendors, or customs teams that must receive automated notifications? Options: Terminal ops, Ground handlers, Provisioning vendors, Customs, Other
• At what frequency should ETA/ETD be published to external partners during approach and turnaround? Options: On every change, Hourly, 4x per day, Custom
• Should customs, bonded stores, or provisioning declarations be transmitted automatically at specific milestones during the port call? Options: Yes, No
• Which team will own integration to terminal messaging endpoints and certificate provisioning for secure transmissions?

Deploy Onboard POS, Inventory, and Revenue Reconciliation

• Which onboard POS systems and terminal types must be integrated at cutover (bar POS, retail, specialty restaurants)? Options: Bar POS, Retail POS, Specialty restaurant POS, Spa/F&B kiosks, Other
• Describe the inventory SKU mapping and costing artifacts that must be preserved to enable accurate revenue reconciliation.
• Confirm the reconciliation accuracy threshold and time-to-close discrepancy you require to accept revenue reporting at go-live. Options: 99.5% accuracy / 24 hours, 99% / 48 hours, 95% / 72 hours, Custom
• Confirm whether onboard POS terminals must store offline transactions locally and auto-replay to shore when connectivity is restored. Options: Yes, local store and auto-replay, No, do not store locally, Store locally but manual replay
• Which fiscal or tax reporting artifacts must be produced per port call for onboard revenue (local tax summary, duty reports, VAT filings)? Options: Local tax summary, Duty reports, VAT filings, Other

Configure Regulatory Compliance Documentation and Filing

• Describe the regulatory regimes and conventions your filings must comply with (IMO conventions, SOLAS manifests, ISPS, flag-state reporting). Options: IMO conventions, SOLAS, ISPS, Flag-state reporting, Other
• Provide the list of document types that must be auto-generated (cargo declarations, garbage record book entries, fuel consumption logs, alcohol service logs). Options: Cargo declarations, Garbage record book, Fuel consumption logs, Alcohol service logs, Other
• Confirm whether time-stamped, tamper-evident records are required to meet auditability for your auditors or flag administration. Options: Yes, No
• Indicate which parties require copies of compliance filings (port authority, flag administration, shoreside compliance team). Options: Port authority, Flag administration, Shoreside compliance, Other
• Specify the statutory retention period for compliance records per jurisdiction you operate in. Options: 1 year, 3 years, 5 years, Custom

Run Single-Vessel Pilot Deployment and Go-Live

• Which single vessel will be used for the pilot and characterize its itinerary complexity (number of ports, international crossings).
• When do you plan to initiate the pilot and how many voyages should the pilot cover to validate operational workflows? Options: 1 voyage, 1-3 voyages, 3-6 voyages, Custom
• What pilot acceptance criteria will confirm go-live for the vessel (for example: manifest exports accepted >98%, offline sync recovery <1 hour, booking reconciliation >99%)? Options: Use example criteria, Provide custom criteria
• Detail the shipboard and shoreside roles that must participate in pilot user acceptance testing and sign-off. Options: Bridge officers, Hotel operations, IT/Connectivity, Shoreside ops, Other
• Outline rollback triggers that would authorize reverting the vessel to legacy systems during the pilot (for example: manifest rejection by port, critical revenue mismatch, system outage >4 hours). Options: Manifest rejection by port, Critical revenue mismatch, System outage >4 hours, Other

• decision_readiness
• desired_state
• current_state
• success_criteria
• gaps
• stakeholders
• decision_readiness
• success_criteria
• current_state
• desired_state
• gaps
• stakeholders
• stakeholders
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Receive buyer pilot acceptance sign-off document
• Deliver consolidated pilot exceptions log with mitigation plans and owners
• Complete integration acceptance test report for each integration endpoint
• Provide data migration validation report and documented rollback checkpoint
• Submit shipboard limited-connectivity resilience test results
• Receive training completion records for shipboard and shoreside owners
• Obtain regulatory/compliance acceptance for pilot artifacts
• Agree and sign operational support and incident SLA for pilot-to-fleet conversion
• Receive written authorization to progress to commercial commitment

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form / Subscription Agreement
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• Pilot Acceptance & Handover Agreement
• Pilot-to-Fleet Conversion Milestone Schedule
• Governance & Escalation Plan
• Change Order Agreement
• Termination & Data Return Addendum

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Fleet Acceptance Gate (around day 90)
• Quarterly Operational Review
• Annual Realization Review

• Publish the quarterly KPI dashboard with annotated trend explanations and data sources.
• Confirm the incumbent system's decommission or retention state and the data archival/migration status.
• Publish the signed acceptance record or conditional acceptance document to the shared workspace within 24 hours.
• Create remediation tickets for any failed criteria with owners, milestones, and verification steps.
• Deliver formal confirmation of incumbent system archival or read-only retention and evidence of migration completion.
• KPI trend review
• Verify KPI stability against Solution Scope targets and identify any metrics at risk of regression.
• Ensure the number of unresolved operational issues older than 30 days decreases and owners are accountable.
• Agree prioritization for enhancement requests that materially affect operational KPIs and document next steps.
• Reconfirm success criteria and owners
• Owners to update their remediation tickets with progress notes and new target dates where required.
• Deliver a prioritized enhancement list with acceptance criteria for implementation consideration in the next quarter.
• Year-to-date KPI summary
• Confirm whether annual targets for manual reporting hours and integrated-vessel coverage were met and document any gaps.
• Agree three concrete process improvements to institutionalize and owners to implement them in the coming year.
• Lock the recurring governance cadence and incident escalation process for the next 12 months.
• Publish the annual realization report with raw metric exports and a red/amber/green assessment per Solution Scope target.
• Document and circulate the top three process changes with implementation checklists and owner assignments.
• Confirm the quarterly review schedule and the shared channel escalation rules for the coming year.
• Confirm the deployment completed and integrations are reachable with no critical blockers unresolved.
• Identify the top 5 open issues, assign owners, and confirm target resolution dates.
• Establish a shared channel for ongoing issues and enhancement requests and confirm its usage rules.
• Publish the deployment validation report and list of open issues to the shared channel within 48 hours.
• Shipboard operations to provide sample workflow logs for two voyages to validate sync behavior.
• Create the shared issues/enhancements channel and confirm access for named owners.
• Schedule the Fleet Acceptance Gate meeting and circulate required evidence checklist drawn from Solution Scope.
• Present outcome data for named metrics
• Determine whether port ETA variance and crew schedule compliance rate are moving toward Solution Scope targets and document root causes for any gaps.
• Agree a remediation plan with owners and dates that closes identified gaps before the acceptance gate.
• Confirm the data sources and validation steps that will be used for the acceptance decision.
• Owner to publish the metric extraction queries and raw data snapshots used for the review for auditability.
• Create a remediation ticket list with priority, owner, and target completion dates.
• Restate acceptance criteria and numeric targets
• Produce a documented acceptance decision with a named buyer signatory for fleet acceptance or a conditional acceptance with explicit remediation timelines.
• List remediation items for any failed criteria with owners and absolute completion dates.
• Deployment and migration validation
• Backlog and blocker burn-down
• Diagnose gaps and root causes
• Recurring operational risks and mitigation effectiveness
• Present outcome data versus each criterion
• Document pass/fail decision and capture signatory
• Lessons learned and process improvements
• Open issues and remediation plan
• Enhancement request queue review
• Early adoption signals and usage patterns
• Remediation plan for failed criteria
• Open issues triage
• Confirm ongoing governance and review cadence
• Confirm readiness timeline to Fleet Acceptance Gate
• Compliance incidents and audit readiness
• Immediate remediation actions and next steps
• Incumbent system decommission status
• Quarterly action plan