A foundational statement of principles for Asset Management practice
PREFACE — Purpose of the Doctrine
This doctrine defines the essential principles that underpin effective Asset Management, particularly in a cruise ship environment. It is intended as a point of reference for discussions, decisions, and evaluations of maintenance strategy, reliability, and organisational integrity. It outlines what Asset Management is at its core, independent of software, trends, or corporate fashion.
It also serves as a bridge for those outside the engineering discipline. Drawing on experience from information technology, this doctrine helps lay people understand not only what Asset Management is, but how information systems support the function. IT provides the structure, accessibility, and analytical capability that allow engineering knowledge to be captured, organised, and applied consistently. In this way, technology does not replace engineering judgement — it amplifies it, ensuring that insight, data, and operational reality are aligned.
Narrative
INTRODUCTION — The Functional Purpose of Asset Management
An asset’s value is defined by the function it provides. Asset Management is the discipline of ensuring that function is delivered safely, reliably, and cost‑effectively throughout the asset’s lifecycle.
Asset Management is often described in terms of systems, processes, and compliance, but its true purpose is far more practical and operational. In a complex environment such as a cruise vessel, Asset Management exists to ensure that the ship delivers its intended service with minimal disruption, predictable performance, and sustained value across its lifecycle. This purpose can be understood through three functional pillars.
The first pillar is operational continuity. Assets must perform their intended function reliably so that the guest experience remains uninterrupted. Every system — from propulsion to HVAC to galley equipment — contributes to the overall service promise. When assets operate as designed, the ship functions as a coherent whole.
The second pillar is controlled intervention. When an issue arises, or when predictive indicators suggest a potential failure, Asset Management provides the specifications, inventory, instructions, and timing required to perform maintenance with minimal disruption. This ensures that interventions are safe, efficient, and unlikely to introduce secondary failures. Maintenance becomes a managed activity rather than an improvised response.
The third pillar is lifecycle value preservation. A well‑maintained and well‑documented asset retains its value. For high‑value assets such as cruise ships, the maintenance record becomes part of the vessel’s financial integrity. Accurate documentation demonstrates care, compliance, and predictable lifecycle cost, all of which contribute to the ship’s resale value and long‑term viability.
Together, these three pillars define the practical purpose of Asset Management: to ensure reliable service, enable controlled maintenance, and preserve asset value. They form the operational backbone of the discipline and provide the context for all subsequent principles within this doctrine.
The Role of the Asset Management System in Professional Judgement
An Asset Management system does not replace the knowledge, experience, or professional judgement of Marine Engineers. It enhances these capabilities by providing analytical metrics, historical data, and performance indicators that reveal the service quality of each asset. The system informs decision‑making, but it does not dictate it. Engineers remain responsible for interpreting the data, applying their technical understanding, and determining when modifications to maintenance strategies are appropriate. Such adjustments, grounded in experience, operational context, and risk awareness, are essential for sustaining ship operations while reducing cost, time, and material consumption. Asset Management therefore acts as an enabler: a structured framework that supports, rather than supplants, the expertise of those who maintain the vessel.
Maintenance Strategies Define the Method of Control
Maintenance activities fall into distinct strategic categories. Each represents a different philosophy of how an organisation manages risk, cost, and reliability. Effective Asset Management requires understanding these strategies, selecting them intentionally, and applying them consistently.
Reactive Maintenance
Maintenance performed after a failure has occurred. It restores function but carries high operational, financial, and reputational risk. Reactive work is sometimes unavoidable but should never be the dominant strategy.
That said, reactive maintenance has a legitimate place on a cruise ship, typically in the hotel environment. Low‑criticality “hotel defects” such as light bulbs, switches, minor plumbing issues, and cosmetic wear fail often, pose no operational threat, and can be fixed quickly by onboard tradesmen with the right tools and spares. This is routine work, expected and planned for. It is not a weakness in the Asset Management system; it is simply the nature of running a floating hotel.
Preventive Maintenance (PM)
Scheduled interventions designed to prevent failure. These tasks are time‑based or usage‑based and rely on historical patterns of degradation. Preventive maintenance reduces the likelihood of failure but may introduce unnecessary work if intervals are poorly defined.
Preventive maintenance is typically based on manufacturer recommendations, which directly influence compliance and warranty obligations. Product descriptions, maintenance instructions, and required parts are clearly identified, ensuring that work is carried out to the standard expected by the equipment designer. Many of these details are replicated directly into the Asset Management System, providing engineers with immediate access to specifications and ensuring that work order documentation is accurate, consistent, and complete. For many systems, especially those with operational or safety significance, critical spare parts must be held onboard to support timely intervention. In this context, preventive maintenance is not optional — it is a structured, documented commitment to preserving reliability, compliance, and asset integrity.
Predictive Maintenance (PdM)
Condition‑based interventions triggered by evidence of degradation. This strategy uses inspections, sensors, vibration analysis, thermography, oil sampling, and other diagnostic tools to detect early signs of failure. Predictive maintenance enables timely intervention with minimal disruption and is a key component of modern reliability practice.
PdM is a highly specialised discipline, typically enabled through integration with one or more third‑party monitoring systems. Maintenance decisions are deferred or advanced based on the actual condition of the asset rather than fixed intervals. Sensors and routine inspection records feed into trend‑monitoring platforms, and when defined thresholds are breached, the system automatically triggers a corrective — or in some cases reactive — work order.
Thresholds for heat, vibration, noise, pressure, and other indicators are set by the manufacturer but can be refined through operational experience and local insight into how the asset behaves in its specific environment. When applied correctly, predictive maintenance can save significant cost by avoiding unnecessary interventions, reducing labour and material consumption, and preventing secondary failures caused by intrusive or premature maintenance.
Used properly, PdM is not just a maintenance strategy — it is a risk‑reduction and cost‑avoidance tool that materially improves reliability and operational continuity.
Proactive Maintenance
Proactive Maintenance is driven by the operational insight engineers gain from working directly with the assets, this is the “Brand X knowledge” that comes only from experience. This insight is used to refine preventive schedules, adjust predictive thresholds, improve inspection routines, and eliminate the underlying causes of repeat failures. In this way, Proactive Maintenance converts lived engineering experience into structured improvements that enhance reliability, reduce intrusive maintenance, and strengthen the overall Asset Management system.
Run‑to‑Failure (RTF)
A deliberate strategy applied to low‑criticality assets where failure has minimal operational or safety impact. Run‑to‑failure is not neglect; it is an intentional decision supported by risk assessment and cost justification. It is appropriate only when the consequences of failure are acceptable and the asset can be restored quickly.
In practice, experienced engineers often apply this strategy through what can be described as “Brand X knowledge”, the operational insight gained from years of working directly with the asset. Early in many careers, this approach is sometimes misinterpreted as non‑compliance with manufacturer rules, yet it is frequently a mature, experience‑based optimisation. Engineers understand which components fail harmlessly, which failures can be corrected in minutes, and which manufacturer recommendations are unnecessarily conservative for real‑world conditions. When applied with this depth of insight, run‑to‑failure becomes a controlled, intelligent strategy that preserves resources, avoids intrusive maintenance, and maintains operational continuity without compromising safety or reliability.
In this Doctrine
1. Assets Exist to Deliver Service – An asset’s value is defined by the function it provides.
2. Maintenance Is a Preventive Discipline – Repair is a consequence of failure. Maintenance is the prevention of failure. The maturity of an organisation is reflected in the balance between these two.
3. Predictive Maintenance Is Pattern Recognition – Predictive methods do not replace engineering judgement; they enhance it.
4. Failure Modes Must Be Understood, Not Assumed – Every failure has a cause, a mechanism, and an effect.
5. Culture Determines Reliability – Reliability is a behavioural outcome as much as a technical one.
6. Asset Registers Are Structural Maps – Accuracy in the asset hierarchy is essential for planning, analysis, and decision‑making.
7. Backlog Is a Risk Indicator – Backlog reflects organisational risk, resource pressure, and future reliability exposure.
8. Run‑to‑Failure Is a Valid Strategy When Intentional – Acceptable failure must be explicitly justified and documented.
9. Data Requires Interpretation – Insight arises from context, engineering understanding, and disciplined decision‑making.
10. Leadership Owns Consequence – Asset performance reflects leadership choices. Accountability cannot be delegated.
Postscript
This doctrine is intended as a stable reference for future discussions on Asset Management, Predictive Maintenance, and organisational reliability. It provides a shared vocabulary and a clear framework for evaluating decisions, strategies, and cultural behaviours. It is not tied to any specific organisation or system; it represents the underlying truths of the discipline itself.
Asset Management is also a philosophy — one that is frequently misunderstood by senior leaders who do not work directly with the risks. Decisions made in pursuit of short‑term savings in manpower, spare‑part retention, or extended maintenance cycles may deliver immediate financial benefit, but they also increase the probability of failure. On a cruise ship, such failures carry consequences that reach far beyond cost: they affect the safety of the vessel, its crew, and its passengers.
For this reason, the Asset Management system is not simply another IT platform. It is the strategic backbone of the ship’s operational integrity. Without it, there is no reliable vessel to operate, no predictable maintenance environment, and no assurance of safety. Among all onboard information systems, Asset Management stands apart as the most critical, because it protects the ship itself.
This doctrine therefore serves not only as guidance for engineers, but as a safeguard against organisational drift — a reminder that reliability is a leadership choice, and that the discipline of Asset Management must be protected, understood, and upheld at every level.
About the Author
As the author, I am Niel Hillawi. I began my journey in Asset Management in 1983 as an AMOS technician at SpecTec in Manchester, UK. The principles and philosophy has stayed with me ever since. Over the decades, I have taught and implemented the AMOS system across more than 50 cruise ships within P&O Cruises, Princess, and Cunard Line, and served as the principal product owner within Carnival UK. I helped steer the system’s evolution, onboarded successive generations of users, and witnessed firsthand how a modest investment yielded millions in operational savings.
My understanding has been shaped not only by experience, but by the generosity of Marine Engineers — Murdo McCloud, David Strawford, Paul Clasby, Charlie Hill, Jim Craig, Christopher Wright, and many others in this world — who welcomed me, not a Marine Engineer, into their exclusive world. Their insight, patience, and trust remain the foundation of everything I know. This doctrine is, in part, a tribute to them.