Ask five vessels in a mixed fleet what their main sea water pump is called and you may get five answers. That is harmless on one ship and fatal for fleet reporting. The aim of PMS standardisation is simple: the same machine, the same code and the same job rules on every vessel, with differences that are deliberate and visible. This guide shows a Fleet Manager how to design that standard for tankers, bulkers, ferries and small vessels together, and how to migrate into it without losing history the class society cares about. For the system-switch side of the project, see our guide to migrating from AMOS to a cloud planned maintenance system.

One Standard for Every Vessel: PMS Data Migration for a Mixed Fleet
Equipment hierarchies, job libraries, coding rules and a phased migration that makes fleet-wide maintenance reporting possible.
Free trial available. Or book a walkthrough built around your own mixed fleet.
1 standard
Before the first import
Decide the hierarchy, job codes and naming rules first. Migrating mess just moves the mess.
9 levels
ISO 14224 taxonomy
A parent-child hierarchy written for petroleum, petrochemical and gas, borrowed by other industries.
6 phases
One vendor's migration model
From planning workshop to production go-live (BASS, a vendor page).
8 steps
Our AMOS migration sequence
From auditing the source to archiving it, per vessel.

Why a Mixed Fleet Needs One PMS Standard Before It Needs a New System

What breaks in fleet reporting when every vessel names and codes things differently

Fleet reports add up numbers from many vessels. If one ship calls a job lubrication and another calls it servicing, or one lists a pump as equipment while another lists it as a component, any KPI built on them compares labels instead of machinery. A vendor guide to PMS data migration from BASS lists the same pitfalls: inconsistent equipment naming across fleets, outdated or duplicate records, missing job histories and incomplete maintenance hierarchies. It is a vendor page, so treat its claims about its own service as marketing. The pitfalls themselves match what we see.

One pump, four names: the kind of naming drift a standard removes (invented example)
VesselName in the old PMSName in the standardWhat the mapping rule says
Vessel A (tanker)No.1 SW COOL PUMPSea water cooling pump 1Standard name from the common core, number as a suffix
Vessel B (bulker)S/W cooling pp STBDSea water cooling pump 1Side words mapped to a number only where the standard allows
Vessel C (ferry)SWCP-1Sea water cooling pump 1Abbreviation expanded and checked on board
Vessel D (small vessel)Cooling pump (sea)Sea water cooling pump 1Generic name matched using maker and model
Invented example to show the pattern. Real names will differ, and the mapping rule must be checked against the machinery on board.

How a common core plus vessel-type modules handles tankers, bulkers, ferries and small craft

A mixed fleet does not need identical hierarchies. It needs identical rules. The design below puts everything common, such as propulsion, electrical, safety and navigation, in one core with shared codes and names. Ship types then add modules for their own systems. The module names are examples, and the small vessel module shows that a reduced set can still follow the same coding rules.

One Standard for a Mixed Fleet: A Common Core Plus Vessel-Type Modules (Our Design Concept)
COMMON CORE: SAME CODES, NAMES AND JOB RULES ON EVERY VESSELPropulsion and auxiliary machineryElectricalSafety and lifesavingNavigation and communicationHull and deck
Tanker moduleCargo systems, inert gas, pumps
Bulk moduleHatch covers, cargo gear
Passenger or ferry moduleRamps, stabilisers, passenger safety
Small vessel moduleReduced set, same coding rules
Our concept for handling mixed tonnage: keep one code and naming rule for everything common, and let ship types add their own branches without breaking the rules. The module names are examples.
Give Every Vessel the Same Equipment Structure and Job Rules
Set up one hierarchy, one job library and one naming rule for the fleet, then move each vessel in with its history and evidence intact.
Free trial available. Or book a walkthrough built around your own mixed fleet.

Equipment Hierarchies and Coding Standards: SFI, ISO 14224 or Your Own

What a coding standard does and which options the sources describe

SFI is described in a paper by T. Urke, of the Ship Research Institute of Norway, as a multi-purpose decimal coding system in which equipment, systems and machinery are given group numbers according to their purpose or function. It was intended for use within and between companies, including for maintenance. We could not see its group structure in the sources we read, so confirm the current version before adopting it. Our own AMOS migration article advises adopting an industry classification such as SFI for the equipment hierarchy. ISO 14224 is another model, covered next.

How ISO 14224's nine levels can inform a ship hierarchy

A CPCON summary lists the ISO 14224 taxonomy as nine levels, from industry and business category through installation, plant or unit, system, equipment unit, subunit and maintainable item down to part. It adds that the standard was developed for the petroleum, petrochemical and natural gas industries and is used as a model elsewhere. The table below is our mapping of those levels to a ship. It is a pattern to borrow, and you should check the standard before making any conformity claim.

The ISO 14224 Levels and How They Might Map to a Ship (Standard From CPCON Summary, Ship Mapping Is Ours)
Levels 1 to 3Business, category, installationCompany, fleet, vessel
Levels 4 and 5Plant or unit, section or systemMachinery space, system (cooling water)
Level 6Equipment unitPump, generator, boiler
Level 7SubunitLubrication or cooling subunit
Levels 8 and 9Maintainable item, partBearing, seal, filter element
Levels as listed on a CPCON summary of ISO 14224. The standard was written for the petroleum, petrochemical and natural gas industries, so it is a model to borrow, not a ship rule. The ship examples in the right column are ours. Check the standard itself before claiming conformity.

Building a Job Library That Works Across Different Ship Types

Why a fleet master job with type templates and visible overrides keeps differences deliberate

Standardising jobs does not mean forcing the same interval on every vessel. Maker manuals, class and the company's safety management system decide intervals. What a standard gives you is one master job per task and equipment class, adjusted by ship type where the trade demands it, with any vessel-specific override recorded and approved. The diagram shows our design concept.

A Job Library With Inheritance: Fleet Master, Type Template, Vessel Override (Our Design Concept)
FLEET MASTER JOB
One job per task and equipment class
Code, title, default interval, acceptance criteria, evidence required.
▼
VESSEL-TYPE TEMPLATE
Adjusted for tanker, bulker or ferry
Intervals or steps that differ by trade, with the reason recorded.
▼
VESSEL OVERRIDE
Maker, model and class specifics
Allowed, but visible and approved, so the fleet can see where ships differ.
Our concept. Intervals must still follow maker manuals, class and the company's safety management system. The point is that every difference is deliberate and visible.

Which fields to map for each object before any data moves

Before extracting anything, write a mapping sheet that says what each source field becomes. The sheet below lists the objects our migration article treats as in scope, plus the rules to write down. Agree it with the superintendents and the class society before the pilot.

A field mapping sheet to agree before any data moves (our suggested template)
ObjectFields to mapRule to write downSource status
Equipment registerCode, name, parent, type, maker, model, serialOne coding system and one naming rule for all vesselsOur suggestion
Job templatesJob code, title, interval, counter, acceptance criteriaFleet master job code, with type and vessel overridesOur suggestion
Maintenance historyCompletion date, person, notes, attachmentsHow much history to bring and what counts as class-relevantMI migration article
Running hoursCounter value and dateReconcile to the machine on board at cutoverMI migration article
SparesPart, quantity, link to equipmentDuplicates merged, links checkedMI migration article
Open defects and deferralsStatus, reason, approverAll carried over with the reason intactMI migration article
The first column is a suggested layout. Rows marked MI draw on our own AMOS migration article.

Migrating Without Losing Class-Relevant History or the Open Position

What to bring, what to archive and why the pilot should be a hard vessel

Our migration article recommends bringing the full equipment register, current job definitions, history covering at least the current class survey cycle, current counters, live spares positions, open defects and deferrals, and certificates in force. It suggests leaving very old or dormant records in a read-only archive with a named person able to query it. For the pilot, it recommends a difficult vessel with crews briefly using both systems, so mapping problems surface early.

What to Bring and What to Leave Behind in the Move (Marine Inspection AMOS Migration Article, Summarised)
BRING
  • Full equipment register
  • Current job definitions
  • History for the current class survey cycle, ideally the previous one too
  • Current counters and running hours
  • Live spares positions
  • Open defects and deferrals
  • Certificates in force
LEAVE BEHIND (ARCHIVE, DON'T DELETE)
  • Very old completions with no detail
  • Equipment from past conversions
  • Dormant job templates
  • Duplicate parts
  • Superseded attachments
  • Old users and workflows, which get rebuilt
From our own migration article. It also says not to economise on class-relevant history and that retention depends on your obligations and survey cycle. Check with your class society.

A phased sequence that cuts over vessel by vessel

The sequence below follows our migration article with the standard-design step made explicit. Cutover is per vessel, timed to docking, crew change or a quiet period, with the outstanding position documented and checked at each switch. Neither the vendor page nor our article gives fixed timelines, and we do not invent any.

A Phased Migration Sequence for a Mixed Fleet (Based on Our AMOS Migration Article, Adapted)
1
Audit the source
Count records, naming consistency, useful history and attachments.
2
Design the standard
Hierarchy, codes, job rules, naming. Agree before mapping.
3
Map the objects
Field by field, with written rules.
4
Pilot a hard vessel
Not the best-kept ship. Expose the problems early.
5
Fix and re-run
Correct the mapping from what the pilot showed.
6
Roll out by vessel
Timed to dockings or quiet periods, not one fleet-wide switch.
7
Reconcile per vessel
Document the outstanding position at cutover and check it.
8
Archive the source
Read-only, with a named person who can query it.
Sequence follows our own migration article, with the standard-design step made explicit. A vendor model (BASS) has six phases: planning workshop, extraction and mapping, cleaning, conversion and delivery, user acceptance testing and go-live. Neither source gives fixed durations, and neither do we.

The PMS Standardisation and Migration Readiness Checklist

A checklist with a checkpoint type on each item for the Fleet Manager and the superintendents

Use the table to confirm the standard exists on paper before the first record moves, that the source data has been audited and that cutover can be reconciled. Adapt it to your fleet and class requirements.

PMS standardisation and migration readiness checklist, with a checkpoint type on every item (our suggested template)
ItemWhat to checkCheckpoint type
Coding standardOne coding system chosen and documented, such as SFI or your ownRecord
Equipment hierarchyCore structure plus type modules agreed and approvedRecord
Naming rulesWritten rules, with examples, applied the same way on every vesselRecord
Job libraryFleet master jobs with intervals traced to makers, class and SMSRecord
Source data auditDuplicates, gaps and obsolete records counted before mappingTest
Class society informedClass told of the change and the approach agreedRecord
Pilot vessel resultPilot data checked against the machinery on boardVisual
Cutover reconciliationOutstanding position matched before and after the switchTest
Our suggested template. Checkpoint types: Visual, Test and Record.

Mistakes That Turn a Standardisation Project Into a Second Mess

Six habits that leave the new system as inconsistent as the old one

1
Migrating before standardising
Moving inconsistent data into a new system gives you inconsistent data in a new system. Agree the standard first.
2
Piloting on the easiest ship
The well-kept vessel hides the problems. Pilot on a difficult one, as our migration article advises.
3
One fleet-wide switch date
Vessels are rarely in one place. Cut over per vessel, timed to docking or quiet periods.
4
Copying every vessel's quirks
If every override is accepted, there is no standard. Make differences deliberate and visible.
5
Deleting the old history
Archive it, read-only, with a named person who can query it. Do not economise on class-relevant history.
6
Forgetting class and flag
Tell the class society about the change and keep survey-relevant records intact.

Systems That Keep a Standardised Fleet Standard After Go-Live

How a dated photo repository, task ownership and deadlines support the migration and what follows

Standardisation is not finished at go-live. Marine Inspection supports a dated photo repository, observations turned into tasks with owners, deadlines and evidence, and certificate and equipment tracking. During migration, dated photos of nameplates and machinery can confirm the register against what is on board, and tasks with owners can chase mapping gaps vessel by vessel. After go-live, the same structure keeps new equipment coded the same way. For the wider design of the system itself, see our {L2}.

Frequently Asked Questions About PMS Data Migration and Fleet Standardisation

Why standardise PMS data across a mixed fleet?

Fleet reporting only works when the same thing has the same name and code on every vessel. Without that, comparisons between ships mean comparing labels, not machinery.

Which coding standard should we use?

SFI is a multi-purpose decimal coding system that groups equipment by function, according to a description by T. Urke of the Ship Research Institute of Norway. We could not see its group structure in the sources we read, so check the current publication. You can also design your own, as long as it is documented and applied consistently.

Can we use ISO 14224 for ships?

It was written for the petroleum, petrochemical and natural gas industries and is adopted elsewhere as a model. Its nine-level taxonomy is a useful pattern, but it is not a ship requirement, and we do not claim conformity.

Should every vessel have identical jobs?

No. Intervals must follow maker manuals, class and your safety management system. Use a fleet master job, type templates and visible vessel overrides, so differences are deliberate.

Which vessel should we pilot first?

Our migration article says to pilot a difficult vessel, not the best-maintained one, so the problems show early.

How much history should we migrate?

Our migration article suggests at least the current class survey cycle and ideally the previous one, plus open defects and deferrals. Your retention obligations and survey cycle decide, so check with your class society.

How long does migration take?

The sources we read give no fixed durations. It depends on the fleet's calendar, the state of each vessel's data and how far vessels differ in configuration.
Make Fleet Reporting Possible by Making Every Vessel Speak the Same Language
One hierarchy, one job library and a vessel-by-vessel migration that keeps class-relevant history and open defects intact.
Free trial available. Or book a walkthrough built around your own mixed fleet.