Recurring movement schedule
Manage repeat arrivals, departures, route days, passenger windows, and service dependencies.
Schedule model
Operations can be generated by pattern, vessel, route, or seasonal program.
Services for Fleet Operators
Actual service delivery, written for the way this audience works.
Each service card includes rollover or tap details for deeper explanation without interrupting the page flow.
Fleet service coordination
Group fuel, water, waste, cleaning, stocking, inspections, and minor maintenance across multiple vessels.
Batching services
Batch work by dock, vendor, route, or departure priority to reduce wasted movements.
Passenger and guest support
Coordinate boarding notes, accessibility needs, announcements, local notices, transport, and guest-service exceptions.
Passenger context
Designed for commercial and charter operators where timing and public-facing service matter.
Maintenance holds
Track operational holds, repairs, defect notes, parts runs, return-to-service status, and supervisor sign-off.
Return-to-service
The view emphasizes what blocks operation and what must happen next.
Fuel and waste cycles
Plan recurring fuel, water, pump-out, trash, recycling, and special handling with completion records.
Utility cadence
Useful for high-frequency fleets where services are routine but timing-sensitive.
Port and local notices
Attach local restrictions, closures, safety notices, weather impacts, and traffic changes to affected vessels.
Notice propagation
One notice can be routed to the vessels, staff, or service plans it affects.
Incident and exception log
Record operational incidents, guest-impacting exceptions, service delays, and corrective actions.
Exception record
Designed for supervisors who need a clean end-of-day view.
Daily operations report
Summarize movements, service completion, open exceptions, vendor performance, and tomorrow’s watch items.
Supervisor output
A practical report for shift handover and management review.
Service matrix
From intake to operational output.
Every service is structured as an intake, routing rule, operating workflow, and completion output.
Service layerIntakeRoutingStatusOutputPortal
Recurring movement scheduleProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Fleet service coordinationProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Passenger and guest supportProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Maintenance holdsProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Fuel and waste cyclesProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Port and local noticesProfile + request dataRole / vessel / location● Live queueReport / completion noteFleet Operators
Day-to-day reality
Built for weeks that repeat — and days that don't.
For a working fleet, most service demand is predictable: fuel before the weekend departure block, pump-out after the last run, provisioning ahead of a charter series, a wash-down between turnarounds. What breaks the week is never the routine — it is the fuel truck that arrives during a boarding window, the pump-out missed because a vessel swapped berths, the defect note that quietly becomes a canceled departure.
Services on the schedule, not beside it
MERIDIAN treats each service in this catalog as part of the operating schedule, not a separate to-do list. Routine work is planned into the gaps between movements, and anything that threatens a departure surfaces as an exception while there is still time to re-plan.
Every request carries the departure block it must not touch.
Example lifecycle
One service request, raised to closed.
A grouped fuel run, followed through every state a fleet service request passes on this version.
Raise
After the morning runs, crew flag low fuel on two tour vessels. The operator opens a fuel request and groups in a third vessel that is due for its recurring top-up anyway.
Route
The request routes by vessel, dock, and time window. The fuel vendor sees scope, quantities, and dock access notes — plus the departure block the job must not touch.
Schedule
The vendor proposes a window between the midday and evening departures. A conflict with a planned berth move is flagged, and the window shifts once — visibly, with an owner.
Execute
Each vessel's fill is confirmed on completion, with quantities and evidence attached to the job instead of texted to whoever happened to ask.
Close
The job closes into the daily operations report, and the recurring fuel cycle updates so next week's grouping starts from what actually happened.
Questions
Frequently asked about services.
Can services recur automatically?
Yes — fuel, waste, cleaning, and inspection cycles can be generated by pattern, vessel, route, or seasonal program, then adjusted week by week.
How are vendors brought into a request?
Vendors are invited into the specific job with its scope, window, and dock notes. They see the work they are assigned, not your wider operation.
What happens when a service conflicts with a departure?
The conflict surfaces as an exception with an owner. The service window moves, or the movement does — either way the change is recorded, not improvised on the dock.
Is completion evidence captured?
Yes — completion notes, quantities, and attachments live on the job and roll into the daily operations report.
Can we shape the catalog to our fleet?
Service categories, cycles, and routing rules are configured per operation, so the catalog reflects the services your fleet actually runs.
Next page
Translate these services into workflow states.
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for fleet operators.
Get started
Put your service catalog on the operating schedule.
Request access to see these services configured around your fleet's real cycles, or ask for a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.