SERTICA Alternatives for Fleet Maintenance, Spares and Marine Procurement

The two invoices that start a SERTICA review

The first is the software invoice, and it is the less important one. Marine technical systems are priced per vessel with modules on top, so every ship you add reprices you, and the modules you enabled during implementation keep billing whether the fleet uses them or not. That produces an annual conversation but rarely a real problem.

The second invoice is the one that matters: what you actually spend on spares and services. Somebody in the office notices that three vessels bought the same pump seal from three suppliers at three prices in one quarter, or that stock on board has drifted so far from the record that superintendents order duplicates because they do not trust the system, or that a dry dock came in over budget because purchasing decisions were made vessel by vessel without any fleet level view. That is when a technical director starts asking what the system is actually giving him. The software has done what it was configured to do. It recorded transactions. It did not tell anyone what those transactions meant, and no packaged product will do that for your specific trade without work.

What SERTICA is genuinely good at

Planned maintenance is a deceptively deep problem, and any product that has survived in this market has absorbed a great deal of it. Component hierarchies down to the equipment level, running hour and calendar triggered jobs, critical equipment flagging, class and survey linkage, deferred job handling with justification, and a job history that stands up when an inspector asks for evidence. Reproducing that from a blank page is a serious undertaking and teams routinely underestimate it by a factor of three.

The Danish maritime software scene it comes from has also been pragmatic about the ship to shore problem: vessels need to work when the link is down, and records have to reconcile without a human arbitrating every conflict. Replication that behaves predictably across a fleet is unglamorous engineering that nobody thanks you for until it fails. The procurement side deserves credit too, because requisition to order to receipt with budget checking is genuinely useful once configured, and most fleets never configure it fully. Before you shop for an alternative, find out how much of what you already own is switched off.

Where maintenance and procurement systems get tight

Analysis is the first ceiling, and it is nearly universal. Transactional systems record events well and answer analytical questions poorly. Cost per running hour by equipment class across a fleet, supplier performance measured by delivery reliability rather than quoted price, maintenance backlog trend by vessel and by superintendent, budget variance with the reason attached: these are the questions that change decisions, and they usually require exporting data and rebuilding it elsewhere.

The second is the catalogue and identity problem. Spare parts have manufacturer codes, maker part numbers, internal codes, impa or issa references and free text descriptions, and across a mixed fleet the same physical item appears under several identities. Products give you catalogue structures, and keeping them clean is a data governance job that no software performs for you. Until that is solved, fleet level buying power stays theoretical. The third is workflow rigidity in approvals. Approval thresholds that differ by owner, by vessel type, by port and by urgency, with a technical sign off separate from a commercial one, do not always fit a standard model. When they do not fit, people approve by email and enter records later, which is exactly the audit trail failure the system was bought to prevent.

What you can actually choose between

Remain and configure. Before any project, audit how much of the existing licence is dormant, whether budget control is actually switched on, and whether the catalogue has ever been cleaned. Many fleets are running a fraction of what they pay for, and a focused configuration and data cleanup engagement is cheap compared with everything else on this page. Replace with another platform. SpecTec AMOS, BASSnet, ABS Nautical Systems, Danaos, Hanseaticsoft Cloud Fleet Manager and ShipNet all compete in this space with different weightings between technical management, procurement and financials. Replacement is justified by a structural gap or a broken relationship, and it costs you a year.

Add rather than replace. Marine e-procurement networks such as ShipServ exist specifically to connect fleets to supplier catalogues and quotations, and they sit alongside a maintenance system rather than displacing it. Or build the analytical and procurement layer yourself: pull maintenance, stock and purchase data out of the existing platform into your own store, clean the item identity problem once, and run fleet level sourcing, budget control and supplier performance on top. That option leaves the certified maintenance and class core untouched, which is exactly where you do not want surprises.

The build case, stated honestly

Building pays back when purchasing volume is large enough for a small percentage to matter, and when the fleet is diverse enough that no packaged catalogue fits. A twenty vessel fleet spending seriously on spares and services can justify a bespoke sourcing and analysis layer on the procurement saving alone, before counting the superintendent hours currently spent in spreadsheets. It also pays back for specialised tonnage, offshore support vessels, dredgers, research ships and similar assets whose maintenance regimes and equipment structures do not resemble the merchant fleet models most products were built around.

The argument against is equally clear. Never rebuild the planned maintenance and class survey core casually. That is where regulatory nuance accumulates, where an error becomes a detention, and where the accumulated history has legal weight. Never build if you have no shore side technical owner, because a maritime system without an owner degrades into an expensive data entry exercise within eighteen months. And be honest about the real problem: if the underlying issue is that jobs are closed in bulk at the end of a rotation without genuine work being recorded, a new system will produce the same fiction faster.

Migrating maintenance history without losing compliance

Treat history as the primary asset. Before anything else, secure a complete export: equipment hierarchies with maker and model detail, job definitions with intervals and triggers, executed job history with dates and running hours, deferrals with their justifications, class and survey linkage, stock and location records, purchase and supplier history, and attached documents including certificates and drawings. Then confirm the new environment can hold all of it in queryable form, not as a pile of files.

Migrate one vessel at a time and choose a sister ship first if you have one, because the second vessel of a class costs a fraction of the first. Run parallel through at least one full crew rotation and one port call with a real requisition, so both the maintenance and purchasing paths are proven end to end. Freeze catalogue cleaning as a separate workstream that starts before migration, because migrating a dirty catalogue simply relocates the problem. Keep the outgoing system readable for several years, since class, flag, insurance and warranty questions look backwards, and schedule cutover well clear of dry dock, special survey and any vetting inspection.

What it costs either way

Commercial platforms in this space quote per vessel with modules, plus implementation, plus data migration priced separately, and migration is the line most often underestimated. Model your three year fleet size, and ask specifically what happens to pricing when vessels leave the fleet. On the custom side, based on Digital Heroes delivery experience: a procurement, spares and analysis layer that reads from your existing maintenance system, cleans item identity and drives fleet level sourcing runs roughly $55k to $130k over 10 to 16 weeks. Add supplier portals, quotation comparison and budget workflow and you are in the $120k to $250k range. A full maintenance and procurement platform including planned maintenance, class linkage and vessel side offline operation runs $170k to $420k, and should be phased across at least a year. Hosting is a modest monthly cost independent of fleet size, and budget an ongoing retainer for regulatory and catalogue maintenance.

My recommendation

For most owners and managers: remain on the maintenance core, spend on catalogue cleanup and configuration first, then build the procurement and analysis layer where the return is measurable in spend rather than in convenience. For fleets above roughly twenty five vessels with serious purchasing volume, the analysis layer usually pays for itself inside two years. For operators of specialised tonnage, look harder at owning more of the stack, because the standard merchant vessel model is what is failing you. Replace the whole platform only when there is a structural gap you can name in one sentence, and when you have a technical owner ashore who will still be there in three years.