Recurring movement schedule
Manage repeat arrivals, departures, route days, passenger windows, and service dependencies.
Operations can be generated by pattern, vessel, route, or seasonal program.
scheduled operations
A MERIDIAN site version for commercial operators managing scheduled departures, passenger and crew needs, fuel, waste, maintenance windows, notices, incident follow-up, and port-service coordination for multiple active vessels.
Tailored service story
This version keeps the navigation functional and service-led, while adapting language, metrics, tasks, and operating examples to fleet operators.
Manage repeat arrivals, departures, route days, passenger windows, and service dependencies.
Operations can be generated by pattern, vessel, route, or seasonal program.
Group fuel, water, waste, cleaning, stocking, inspections, and minor maintenance across multiple vessels.
Batch work by dock, vendor, route, or departure priority to reduce wasted movements.
Coordinate boarding notes, accessibility needs, announcements, local notices, transport, and guest-service exceptions.
Designed for commercial and charter operators where timing and public-facing service matter.
Track operational holds, repairs, defect notes, parts runs, return-to-service status, and supervisor sign-off.
The view emphasizes what blocks operation and what must happen next.
Common pain points
Schedules and services repeat, but the coordination starts from scratch.
A hold or a delay ripples through the day without a clear owner.
End-of-week numbers are pulled together by hand.
Your command deck
MERIDIAN is permissioned by role. You see your operation, and only your operation.
Working together
Work the schedule from one shared plan.
Batch service jobs with scope and evidence.
See exceptions and reporting without a manual pull.
Example workflow
Recurring movements in one place.
Fuel, waste, and maintenance batched.
A clear owner for every hold.
Supervisor-ready from the live file.
Each vessel and job is scoped; partners see only what they are invited to.
Guest and invited access is approval-gated and scoped — never open public signup.
Discretion
Everyone invited into your operation sees only what their role needs. The operating file stays yours.
Questions
Yes — recurring schedules and repeatable service are the core.
A hold or delay gets an owner and a status, and its impact is visible.
Yes — passenger and guest support is part of the workflow.
Yes — from the live operating file, not a manual pull.
Get started
See how MERIDIAN adapts to your workflows, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.