PMSModule 01 · Onboard operations
Planned maintenance that keeps working when the satellite link doesn't.
A complete ship planned maintenance system built around a vessel → system → equipment → component hierarchy. Calendar and running-hour schedules generate work orders on board; crews execute them with job instructions, questionnaires, readings, materials and completion photos — fully offline — while every change queues for synchronisation with shore.
The maintenance backbone of the fleet
- 01Higher PMS compliance with fewer overdue jobs
- 02One maintenance truth shared by vessel and shore
- 03Audit-ready history for class, flag and vetting inspections
Capabilities
What PMS does
Four-level asset hierarchy
Model every vessel as systems, equipment and maintainable components — propulsion, electrical, utilities — with maker, model, serial number, ERP codes, bearing, coupling and certificate details on each item.
Calendar & running-hour schedules
Standard jobs carry their own schedules. Due work orders are generated automatically, and running-hour readings keep counter-based jobs honest.
Rich job library
Reusable standard jobs with job instructions, internal and external resources, materials required and used, questionnaires, file attachments and certificates — authored once on shore, delivered to every vessel.
Work orders built for the engine room
Clear due-date indicators, schedule progress, readings, instructions and notes in one view. Completion captures photos straight from the camera plus supporting files — and keeps entries safe if a submission needs to be retried.
Controlled postponements
Crews raise postponement requests offline without touching the work order. Shore reviews, adjusts date and reason, then approves or rejects — and the decision returns through sync.
Critical spares & inventory context
Track critical spares per equipment item on both sides of the sync, alongside the item master, so the parts picture is never a separate spreadsheet.
Notes that don't get lost
Work-order notes and floating notes keep shift-to-shift and vessel-to-shore context readable and dated, with change logs and notifications on every record.
Data quality guardrails
Shore-side flagging spots duplicate standard jobs, multiple open work orders, missing equipment or schedule links and cross-vessel mistakes before they become audit findings.
How it flows
A closed, auditable loop.
- 1
Plan
Calendar and running-hour maintenance generated from the standard-job library.
- 2
Execute
Job cards, work orders, instructions, readings and photos captured on board.
- 3
Control
Approvals, due / overdue alerts, postponement decisions and a full audit trail.
- 4
Learn
History, defects, spares, manuals and lifecycle records feed fleet knowledge.
Outcomes
What changes for your fleet
- Higher PMS compliance with fewer overdue jobs
- One maintenance truth shared by vessel and shore
- Audit-ready history for class, flag and vetting inspections
- Less double entry between paper, spreadsheets and email
Frequently asked
Does the PMS work without an internet connection?
Yes. The vessel application runs on a local database on board. Crews create, update and complete work orders offline; changes are marked pending and synchronised automatically once connectivity returns.
Can we import our existing equipment and job lists?
Yes. Equipment libraries and standard jobs can be imported from structured spreadsheet templates, then refined and bulk-edited on shore before being pushed to vessels.
How are running hours handled?
Engine and equipment running hours are recorded as readings and reviewed on shore. Running-hour based schedules use those counters to drive due dates, and the data is visible in fleet dashboards.
See PMS on your own fleet data.
Book a 30-minute walkthrough with our team. We'll map your workflows, connectivity and data sources — and show you the platform live, including what happens when the link drops.