Loading / Chargement
Ferries · Product direction
PaxRelay’s orchestration model is being designed to extend to ferry operations where schedule, port and weather changes need a coordinated passenger response.
Sailing 218
Terminal A → Terminal B
Where the model can apply
Terminal teams, vehicle passengers, foot passengers and onward connections may need different actions from the same operational event. Normalization and workflow rules can keep those paths connected.
Reusable orchestration
The source fields, passenger groupings and operational thresholds would be configured for ferry operations rather than copied from aviation.
Receive a sailing or terminal change
Normalize the route and departure context
Identify affected booking groups
Apply ferry-specific conditions and approvals
Prepare the applicable passenger update
Record the decision and delivery state
The underlying event, workflow and communication model is intended to support ferry use cases. Operator-specific discovery and validation are required before representing a ferry deployment as production-ready.
Ferry capabilities are on the product roadmap and are not presented as an established customer offering.
If your team handles recurring sailing or terminal disruptions, we can compare the workflow with the platform architecture.