Buyer's guide · onboarding
Buying the system is the easy half. This is an illustrative 30-day planning sequence, not a promised rollout duration or evidence of completed customer deployments. Adapt each phase to data preparation, configuration and operator review.
Days 1–2
Create the workspace, invite the technical office, set roles (admin, superintendent, crew). An illustrative reference vessel can be loaded so superintendents can learn the flow before a single real record is touched.
Where it goes wrong: Decide the role model now: crew update job status only, superintendents own job details. Retro-fitting permissions after the crew are trained causes confusion.
Days 3–7
Add each vessel with its particulars; its statutory template register of certificates and drills is generated straight away. Then enter the equipment register with maker, model, location, criticality and current running hours — the pilot ship first, in full, before the rest of the fleet.
Where it goes wrong: Do not bring across a decade of noise. Enter the equipment and its current hours; bring history for critical equipment only. A clean register beats a complete one.
Days 8–12
Enter planned jobs against each item with their calendar and running-hour intervals and the next due date, so the system shows what is genuinely due. Enter issuer, number, issue and expiry dates for each ISM, ISPS, SOLAS, MARPOL and class certificate.
Where it goes wrong: The first overdue list will be uncomfortable and it should be. Do not adjust due dates to make it green — deferrals with a reason and an approver are the audit-safe route.
Days 13–18
Keep the existing system as the operational record during the pilot. Close jobs, post stock movements and raise requisitions on board with the link down, then see them reach the office record when the connection returns.
Where it goes wrong: Review a queued maintenance completion during the pilot.
Days 19–24
Add the remaining vessels the same way; each one gets its statutory template register generated on arrival. Connect running hours and any sensor feed so the adaptive engine can begin re-timing jobs against real condition rather than the calendar.
Where it goes wrong: Assign one named owner per vessel for the first month. Shared responsibility for data quality means none.
Days 25–30
Run an internal audit against the new system: ask for evidence of a critical job, a drill record and a certificate, and require the crew to produce them unaided. Export the audit pack. Only then retire the old system.
Where it goes wrong: Keep a read-only export of the legacy system's history in the evidence library. You will be asked for pre-migration records at the next external audit.
No servers, no per-ship installation and no IT project: the app installs from the browser and supports offline maintenance job completion on the hardware already on board. See how the offline SaaS model works.
Create a parallel-review workspace, then review roles, vessel configuration and records before treating setup as complete.
Completion time depends on data preparation, configuration and operator review. The 30-day sequence below is an illustrative plan, not a delivery commitment. Traditional enterprise implementations run three to nine months, most of it spent on infrastructure and equipment coding.
Four lists get you most of the way: the equipment register with running hours, the job list with intervals and last-done dates, the certificate register with expiry dates, and the crew list with roles. Your team enters them in the app, and everything else is added as the crew works.
No, and you should not. Run both in parallel for one full maintenance cycle — typically one month — with the old system as the record of truth until the first audit dry run passes on the new one.
The crew were trained on a system that assumes bandwidth. If a chief engineer tries twice in a rolling engine room and the screen spins, they go back to the spreadsheet and the data dies quietly. Offline-capable is not a feature here, it is the adoption strategy.
Tell us the ship count, trades and current system — you get a dated plan back.
Talk to us
Ask about migrating an existing PMS, offline operation at sea, class and flag audits, or what your fleet would actually cost. No sales sequence, no discovery call gate.
