Fleet Standardisation Doesn't Fail in Your CMMS. It Fails Before It.
There's a version of fleet standardisation that exists in project plans, and a version that actually works. The gap between them is almost always data, specifically what happens to data before it goes into your asset management platform.
This is worth dwelling on, because the instinct in most standardisation programmes is to focus on the platform. Get everyone on the same system. Align the asset hierarchies. Standardise the workflows. That work is real and necessary. But the platform is only as good as the data inside it, and for most fleets that data has never been properly built. It's been accumulated.
Go and look at two vessels in your fleet in the same class, with the same main engines. Compare their maintenance task libraries in the CMMS. In most fleets they won't match. Intervals differ. Task descriptions are worded differently. One vessel has inspection steps the other doesn't. Equipment hierarchies built at commissioning by different contractors using different conventions. Parts records linked inconsistently, or not at all. Both vessels supposedly standardised on the same platform, but operating off data that was never standardised in the first place.
That's not a CMMS problem. It's a data problem, and it lives upstream of the CMMS.
The reason it's so common is that asset data in the maritime world gets built in fragments. Data packages come in from shipyards. OEM manuals arrive at delivery. Commissioning teams populate the CMMS under time pressure, making judgment calls that get baked in. Vessels change hands and documentation doesn't always follow. Engineers compensate for gaps using local knowledge, which works fine until they rotate off. Every modification, every equipment swap, every software update to the PMS adds another layer to a data structure that was inconsistent to begin with.
The challenge is compounded for groups that have grown through acquisition or that operate multiple brands. Cruise operators are a good example. Companies like Carnival Corporation and Royal Caribbean Group manage fleets where individual brands, think Holland America, Princess, Celebrity, Silversea, historically ran their own technical operations with a high degree of autonomy. Each brand made its own choices about CMMS configuration, asset naming, task libraries, and spare parts catalogues. That made sense when brands were managed independently. It becomes a significant problem when the group wants to move to a single fleet-wide standard, benchmark performance across brands, or rationalise procurement at scale.
The platform conversation is well advanced in that world. Both groups have made substantial investments in consolidating onto common asset management environments, and the intent to standardise is genuine and well-funded. But consolidating onto a single platform doesn't automatically reconcile the underlying data. A Celebrity Cruises vessel and a Silversea vessel running on the same AMOS instance are still operating off data that was built by different teams to different conventions, and until that's resolved the standardisation is nominal rather than real.
By the time a fleet operator launches a standardisation programme, they're rarely working with a clean slate. They're working with years of accumulated, inconsistent, partially-correct data spread across a fleet, and sometimes across brands. The platform work proceeds on top of it, which is why standardisation programmes so often deliver less than they promised. The architecture improves. The underlying data doesn't, or not enough.
The fix isn't more platform work. It's treating asset data as something that needs to be built and maintained with the same rigour you'd apply to any other engineering discipline, which means having a proper staging layer between raw data and your live CMMS environment.
A staging layer sounds more technical than it is. In practice it's the step that most organisations either skip or do badly: before data goes into production, it gets validated, cleaned, structured, and reviewed. Equipment hierarchies are checked against what's actually on the vessel. Naming conventions are normalised across the fleet. Maintenance task libraries are built from primary sources, OEM documentation, rather than copied between vessels and edited ad hoc. Parts records are reconciled. Duplicate assets are resolved. The data that enters the CMMS is data you can actually rely on.
For a single vessel this is manageable, if tedious. For a fleet it's a different problem in scale, and the approach that works for one ship, engineers working through data manually, spreadsheets, email trails, doesn't scale to fifty or a hundred. The economics don't work, and the consistency doesn't hold.
What changes the picture is being able to run that staging process systematically at fleet scale, ingesting data from multiple sources and formats, applying consistent validation and structure rules across the fleet, and extracting maintenance-relevant content from OEM documentation at volume rather than vessel by vessel. The output is structured, CMMS-ready data with consistent hierarchies, standardised task libraries, and equipment-to-document traceability that holds across the fleet regardless of build era or brand.
We worked with a major international passenger fleet on a programme of exactly this kind, a fleet-wide data build spanning multiple vessel classes, drawing on accumulated OEM documentation and existing CMMS records as source material, and producing a standardised data set that fed directly into their asset management programme in a way that the platform work alone hadn't been able to achieve. The specifics stay confidential, but the shape of the problem and what it actually takes to resolve it is consistent across any fleet operating at that scale.
Three questions that cut through quickly:
For two vessels in the same class, how different are their maintenance task libraries in the CMMS? If the answer is significantly, the data layer hasn't been standardised regardless of what the platform looks like.
When a new vessel is delivered, how long until its data is properly loaded and validated in the fleet system? If the answer is months, the bottleneck is the staging process, or the absence of one.
What percentage of your maintenance tasks can be traced directly to a primary source, an OEM document, a class requirement, an RCM output? If that traceability is thin, your reliability programmes are built on foundations that can't be audited.
These aren't questions about which system you're running. They're questions about what's inside it.
AssetStage is a CMMS data staging platform for maritime, energy, and industrial operations, built to close the gap between raw asset data and a functioning, trustworthy CMMS. Get in touch if you're working through a fleet-scale data problem.