Skip to content

Boat maintenance software

Know what is due, what is broken and what can leave.

A routine service approaching its interval is a different job from a boat waiting on a repair. PATHR Fleet brings the schedule, reported issues, completed work and vessel availability into the same maintenance workspace.

Explore fleet maintenance

Explore the actual dashboard with a simulated fleet. No account needed.

Actual PATHR Fleet Maintenance screen showing Pelican’s simulated raw-water impeller issue, in-progress work and out-of-service status.
Actual dashboard · Simulated fleet · Pelican’s unresolved repair and current availability are shown together.
1

Plan the next service

Review tasks due by engine hours, calendar time or both. Use the relevant vessel and manufacturer schedule rather than a generic interval.

2

Give each defect a record

Keep the reported observation, assessment, work status and supporting notes distinct from a completed repair.

3

Make availability deliberate

Use an explicit staff hold when required. Review outstanding work and release conditions before returning a vessel to service.

Put the service interval beside the actual engine hours.

Halcyon’s afternoon demo shows roughly seven engine hours remaining before its configured service is due. That is a planning allowance, not a declaration that the boat has failed. The task can also have a calendar limit, with the earlier due condition needing attention.

When compatible instruments provide engine hours, HelmLink can bring that reading into the workflow. Where hours are unavailable, an hour-based countdown cannot be evaluated; a calendar schedule and documented readings need their own process. A connected network alone does not guarantee that every engine reports hours.

  • Tasks due by hours, days or both
  • Due-soon and overdue states stay distinct
  • Completed work updates the service record
Inspect the sample engine readings
Actual PATHR Fleet dashboard with simulated Halcyon engine telemetry, about 1,493 meter hours and roughly seven hours remaining before its configured 1,500-hour service point.
Actual dashboard · Simulated fleet and readings

Keep the next booking separate from permission to sail.

A booked boat still needs a readiness decision. The fleet view puts vessel status, its current or next booking, available readings and service allowance together, so staff can investigate before check-out.

An unresolved issue, planned downtime and a manual hold are separate controls. Not every open issue automatically grounds a vessel. Staff decides when a hold is required, records the work actually performed and reviews the release conditions before changing availability. An inspection-generated maintenance issue retains its source evidence without assigning that release decision to AI.

  • Vessel availability visible with bookings
  • Repair records distinct from service plans
  • Staff-controlled holds and release decisions
Check fleet availability in the demo
Actual PATHR Fleet Vessels table with simulated vessel status, current or next booking, available HelmLink readings, engine hours and next maintenance due.
Actual dashboard · Simulated fleet and readings

From the screen to your operation

Try the workflow.
Then plan it around your boats.

  1. 01

    Review what is coming due

    Check each task’s interval, last completed service and available meter reading. Confirm the schedule against the requirements for that boat and engine.

  2. 02

    Record the actual concern

    Create an issue with the observation, severity and follow-up. Keep a diagnosis, parts estimate and completed work distinguishable.

  3. 03

    Set the operational response

    Choose any required hold or planned downtime and communicate the owner and release conditions before the next departure.

  4. 04

    Log work after completion

    Retain the date, meter reading and technician’s record. Review remaining issues before an authorized person returns the boat to service.

Before you decide

The practical questions.

What you can explore now, where the limits are, and what to discuss with the PATHR team.

Can we use this with our live fleet today?

The public maintenance workspace is an interactive simulated demo. Live Fleet access is planned, and a pilot must agree the supported workflows, connectivity and any development needed. The demonstration is not evidence of a deployed customer maintenance system.

Are engine hours collected automatically?

HelmLink currently reads available data from NMEA 2000 equipment. Automatic hours depend on the engine, gateway and network actually publishing them. Field units upload over Wi-Fi today; cellular-equipped pilot units are planned. A missing reading remains unavailable rather than being estimated as a measured value.

Can maintenance be scheduled by date and engine hours?

Yes in the working demo. Tasks can use calendar intervals, engine-hour intervals or both, as well as a specific due point. A task becomes due when an applicable limit is reached. Without a reported engine-hours value, the hour-based limit cannot be evaluated.

Does every open defect take a vessel out of service?

No. An issue can carry an explicit out-of-service decision, and staff can apply a manual hold or planned downtime. Inspection-generated maintenance does not automatically ground a boat. The responsible team must decide the appropriate operational restriction and release requirements.

Does PATHR predict failures or guarantee fewer breakdowns?

No such outcome is established. The demonstrated workflow organizes readings, service plans, issues and work records. It supports staff decisions but does not prove that a boat is fit to depart, replace required inspections or establish predictive-maintenance accuracy.

A closer look at your operation

See how PATHR fits your fleet.

Bring the situations your team handles every day. We’ll walk through the dashboard around those workflows and map the equipment, connectivity and setup for your fleet.

We confirm scope, availability and pricing with you.

Book a call

How it starts

  1. We reply by email to arrange your fleet walkthrough.
  2. We review the workflows, onboard equipment and connectivity your operation needs.
  3. We agree the setup, timing and pricing for bringing PATHR to your fleet.

Bring PATHR to your fleet with a setup planned around your boats, equipment and team.

What we review together

  • Your operating day

    Focus the walkthrough on your boats, handovers and the work that slows your team down.

  • Equipment compatibility

    NMEA 2000 is supported today. Bring your equipment list so we can confirm the connections and readings available for each boat. Additional systems are reviewed individually.

  • Connectivity review

    Field units upload over Wi-Fi today. Cellular-equipped units are planned; we agree coverage and reporting expectations for your operation.

  • Dashboard workflows

    Explore the chart, alerts, manually entered bookings, maintenance and dispatch. The public dashboard uses simulated data; we confirm the workflows available for your deployment.

  • A practical rollout plan

    Agree the boats, supported workflows, equipment and onboarding for your rollout. We plan timing and pricing with you so your team knows how to get started.