There is a particular feeling of satisfaction when you open the Planned Maintenance System and everything is green with no overdue jobs and no critical alarms in the maintenance dashboard. The PMS says the maintenance is up to date, reports are submitted, running hours are recorded, inspections are signed off and all certificates are valid.
On paper, the ship looks healthy, but then you walk into the engine room you can see another reality. A pump is leaking from the mechanical seal, a bilge well has oil traces that should not be there, one auxiliary engine sounds different from the others, the air compressor takes longer than usual to build pressure and a purifier needs more frequent sludge discharge than before.
The crew knows about these things, but nobody has written them properly. The PMS is green, but the ship is not well.
This is one of the most dangerous illusions in modern ship management: believing that compliance is the same as reliability. It is not.
Compliance means that the system says the required tasks were completed. Reliability means that the machinery can perform safely, consistently, and predictably under real operating conditions. Those two things are connected, but they are not the same.
A ship can be compliant and still be fragile. A PMS can be updated and still fail to reflect reality. A maintenance record can look perfect while the engine room is slowly developing problems that will appear later as breakdowns, off-hire, safety incidents, or expensive repairs.
This article is not against PMS. A good Planned Maintenance System is essential, because it creates structure, accountability, traceability, and discipline. Without it, engine room maintenance can quickly become chaotic.
But the PMS is not the ship.
The ship is steel, heat, pressure, vibration, contamination, wear, corrosion, fatigue, human judgment, and operational history, while the PMS is only a tool and and like every tool, it is only as good as the people using it.
What a Green PMS Really Means
A green PMS normally means that scheduled maintenance tasks have been closed within the required time window. That is all.
It does not automatically mean that the job was done properly, that the equipment condition was good, that the crew understood what they inspected, that hidden defects were found or that the machinery is reliable.
It simply means that someone closed the job.
In a well-managed engine room, that closure represents real work: inspection, measurement, cleaning, testing, adjustment, verification, and proper reporting. In a poorly managed engine room, it may represent only administration and this is where the problem begins.
The PMS is designed to support maintenance, but sometimes the maintenance culture becomes designed to satisfy the PMS. The crew starts working for the software instead of working for the machinery.
The objective becomes: “Close the job” and not: “Understand the condition”. This small shift is extremely dangerous. Because once people start treating PMS completion as the final objective, the system becomes green while the machinery continues to deteriorate.
The Chief Engineer must never confuse a completed task with a healthy machine.
A maintenance job is not finished because it has been clicked closed. It is finished when the equipment is inspected, tested, understood, and left in a reliable condition — or when a defect has been properly raised, tracked, and escalated.
That difference separates paper compliance from real engineering.
The Ship Does Not Read the PMS
Machinery does not care about checklists and it only responds to physics. If lubrication is poor, wear will increase. If cooling is restricted, temperature will rise. If filters are bypassing, contamination will circulate. If vibration is ignored, cracks and looseness will develop. If corrosion starts, it will continue unless stopped and so on.
The PMS can document maintenance, but it cannot cancel reality.
This is why experienced engineers often detect problems long before the system does. They hear a change in sound, feel abnormal vibration, notice a small pressure fluctuation, smell overheated insulation and they recognize that something has changed.
This is not superstition, but operational awareness.
A good engineer does not only look at the PMS. A good engineer looks at the ship, because the PMS tells you what was planned, while the engine room tells you what is happening.
Both matter, but when they disagree, the engine room is usually telling the truth.
How Ships Become “Compliant but Sick”
A ship rarely becomes unreliable overnight. Most serious failures begin as small weak signals that were visible to someone before the breakdown happened and the ship becomes sick when these signals are normalized.
The PMS may remain green because the scheduled jobs continue to be closed, but the real condition continues to deteriorate in the background and there are several common reasons for this.
1. PMS Jobs Are Too Generic
Many PMS jobs are written in broad language: “Inspect pump condition”, “Check for leaks”, “Overhaul as required”, “Clean filter”, “Test operation”, “Inspect safety devices” and so on.
These instructions may be acceptable for experienced engineers, but they are often too vague for junior crew members. What exactly must be inspected? Which clearances must be measured? What condition is acceptable? What trend should be compared? What readings must be recorded? What is the rejection criterion? When should a defect be raised?
If the PMS job does not guide the engineer toward meaningful inspection, the task can become superficial. The job is closed, but the machine is not truly assessed and that is why a Chief Engineer must periodically review critical PMS tasks and ask a simple question:
“Does this job actually help us understand the condition of the equipment?”
If the answer is no, the task needs improvement. Good PMS instructions should not only tell the crew to inspect, but should tell them what matters.
For example, a better pump inspection task should include seal condition, bearing temperature, coupling condition, abnormal noise, vibration, foundation bolts, suction and discharge pressure, motor current, and comparison with previous readings.
The difference between a generic checklist and a meaningful inspection is the difference between administration and reliability.
2. Jobs Are Closed Without Evidence
In many engine rooms, PMS tasks are closed with short comments such as: “Done”, “Checked”, “Found OK”, “Completed”, “Tested satisfactory”. These comments may be acceptable for simple routine tasks, but they are dangerous when used everywhere.
What was checked? What was measured? What was found? What was cleaned? What was replaced? What was the condition before and after? Were any abnormalities observed?
A maintenance history full of “done” and “OK” is almost useless when a failure occurs.
Imagine investigating a generator turbocharger failure and finding that every previous inspection says “checked OK.” That does not help the Chief Engineer, it does not help the superintendent, it does not help the next crew and surely it does not help the company understand whether the failure was sudden, developing, or missed.
Good PMS records should create technical memory.
The ship changes crews, engineers sign off, superintendents rotate, spare parts are consumed, problems come and go, but the maintenance history should remain as the vessel’s engineering memory. If that memory is empty, the ship becomes dependent on verbal handovers and personal recollection and that is not reliable management.
For critical equipment, PMS comments should include useful evidence: running hours, measured values, clearances, temperatures, pressures, parts replaced, abnormal findings, photos where useful, recommendations and next action required.
A green PMS with poor comments is not a maintenance record. It is a digital illusion.
3. Defects Are Not Connected to PMS Reality
One of the biggest weaknesses in shipboard maintenance is the gap between PMS tasks and defect management. A crew may complete a maintenance job and find something wrong, but the defect is not always properly raised. Sometimes it is mentioned verbally, sometimes it is written in the engine logbook, sometimes it is kept in someone’s notebook, sometimes it is postponed until “later” and sometimes it disappears during crew change.
The PMS job is closed, but the defect remains alive and this is how ships become sick.
A proper maintenance culture must make one thing very clear: if a PMS job reveals an abnormal condition, the job should not simply be closed as satisfactory. A defect, follow-up job, or technical note must be created.
For example: If a pump seal is leaking, do not just write “pump inspected”. If a cooler is cleaned and pressure drop remains high, do not write “cooler cleaned”. If an air compressor valve plate is damaged, do not close the job without recording the finding. If a purifier bowl needs abnormal cleaning, do not simply reset the interval and move on. The PMS should not hide defects, but should expose them.
A green PMS is only meaningful if known defects are visible, tracked, prioritized, and managed.
4. The Crew Works to Avoid Overdue Jobs, Not to Improve Reliability
There is pressure on ships. Pressure from inspections, vetting, audits, management or charterers. Pressure from limited manpower, short port stays, dry dock preparation or from continuous reporting.
Under this pressure, the PMS can become a scoreboard. Green is good – Red is bad.
Nobody wants overdue jobs, nobody wants explanations and nobody wants office emails asking why the maintenance percentage is low. So the crew focuses on keeping the system green and this is understandable, but it can become unhealthy.
When the main goal is avoiding overdue jobs, the crew may rush inspections, postpone deeper investigation, or close tasks based on minimum effort. Reliability requires a different mentality.
The question should not be only: “Are the PMS jobs completed?”
The better question is: “Which equipment can still fail despite completed PMS jobs?”
That question changes the discussion completely and it forces the Chief Engineer and the team to think beyond the software. This is where real reliability thinking begins.
5. PMS Intervals Do Not Always Match Actual Operating Conditions
A PMS interval is often based on calendar time, running hours, maker recommendations, company standards, or class requirements. That is necessary, but it is not always enough as ships do not operate in identical conditions. One vessel may run long ocean passages with stable load, another may maneuver frequently. One may operate in cold seawater, another may operate in tropical conditions. One may burn cleaner fuel, another may experience fuel instability. One may have experienced years of good maintenance, another may have hidden historical damage.
The same PMS interval can be suitable for one ship and insufficient for another.
For example, a seawater cooler may need more frequent cleaning depending on sea temperature, biological fouling, and operating area. A purifier may need attention more often depending on fuel quality and sludge formation. Air filters may clog faster in dusty cargo environments. Auxiliary engines operating at low load may develop different problems from engines running at healthy load.
The PMS gives a baseline, but the ship gives the correction.
A strong Chief Engineer does not blindly obey intervals when the machinery is showing different needs. He adjusts attention based on evidence. This does not mean ignoring the PMS, but it means using professional judgment to supplement it.
The PMS should never become an excuse to delay necessary maintenance. If a machine is telling you it needs attention now, do not wait for the next scheduled job only because the PMS is still green.
6. Compliance Can Reward Appearance More Than Understanding
One uncomfortable truth is that many inspection systems reward visible order more than deep technical understanding.
A ship with neat records, updated PMS, clean folders, and good dashboard indicators may look better than a ship where the Chief Engineer is openly tracking difficult defects and technical weaknesses. But from a reliability perspective, the second ship may actually be healthier. Why? Because visible defects are manageable, while hidden defects are dangerous.
A ship that admits its weaknesses can plan spares, request support, adjust operation, and prevent failure, while a ship that hides weaknesses behind green indicators becomes a risk.
The purpose of maintenance management is not to look perfect, but to know the truth early enough to act and this is where leadership matters.
The Chief Engineer must create a culture where reporting problems is not treated as failure. If junior engineers are afraid to report defects because it may create more paperwork or criticism, they will learn to keep quiet and silence makes the ship sick. A healthy engine room culture encourages engineers to say:
- “Chief, this pump does not sound right”
- “Chief, this temperature trend is slowly increasing”
- “Chief, we cleaned the filter but the pressure drop returned quickly”
- “Chief, this valve is passing”
- “Chief, this job is closed, but I am not happy with the condition”
That is not negativity, but engineering maturity.
7. The Real Condition Is Often Found Between the PMS Jobs
Many important discoveries happen outside scheduled maintenance.
A good engineer builds a mental map of the engine room. He knows how the machinery sounds when healthy, which pump vibrates slightly more than the others, which generator responds better to load, which cooler has less margin, which valves are rarely touched but critical or which equipment has history. The PMS may not capture all this unless the crew actively records it. This is why engine room rounds remain extremely important, even in an age of digital systems, sensors, and automated reports, because human senses are still powerful diagnostic tools.
The Chief Engineer who relies only on the PMS becomes blind to the ship’s real condition, but the one who combines PMS discipline with physical inspection builds reliability.
The Difference Between PMS Maintenance and Reliability Management
PMS maintenance asks: “Was the job completed?”
Reliability management asks: “Can the equipment continue to perform its function without failure?”
These are very different questions.
PMS maintenance is task-based, while reliability management is condition-based, risk-based, and consequence-based.
A task-based system says: “The pump was inspected this month.”
A reliability-based mindset asks: “Is this pump likely to fail? What would happen if it fails? Do we have standby capacity? Do we have spares? Are there early warning signs? Has the condition changed since last month?”
This is the mindset that separates a ship that merely passes inspections from a ship that operates safely and predictably. The best engine rooms do both.
- They respect PMS discipline, but they do not worship it.
- They close jobs properly, but they also challenge what the jobs are telling them.
- They maintain records, but they also inspect reality.
- They comply with requirements, but they also think about failure modes.
- They use the system, but they do not let the system replace engineering judgment.
How a Chief Engineer Should Read a Green PMS
When the PMS is green, the Chief Engineer should not simply relax. A green PMS should trigger a second question:
“Good. Now what is not shown here?”
This is a powerful question because every ship has hidden risk areas. The Chief Engineer should regularly compare the PMS with the physical condition of the engine room. Walk the engine room with the PMS in mind.
- If the PMS says a pump was recently inspected, go and look at it.
- If a cooler was cleaned, check whether the temperatures improved.
- If a compressor was overhauled, check charging time and oil carryover.
- If a generator maintenance was completed, check load response and exhaust temperature balance.
- If a safety device was tested, check whether the crew understands its function.
- If a valve was operated, check whether it was returned to the correct position and marked properly.
This is not micromanagement, but verification. A Chief Engineer must trust the team, but trust does not remove responsibility and verification protects everyone. It protects the ship, crew, the company and Chief Engineer himself. Because when something fails, nobody will ask only whether the PMS was green. They will ask why the failure was not anticipated.
The Warning Signs of a Sick Ship with a Green PMS
There are many warning signs that a vessel may be compliant but unreliable.
One warning sign is repeated small breakdowns. If many minor failures happen across different systems, the issue may not be isolated, but may indicate poor maintenance quality, weak troubleshooting, or a culture of temporary fixes.
Another warning sign is a clean PMS but a growing defect list. This means scheduled maintenance is being completed, but actual machinery condition is not improving.
Another warning sign is frequent emergency repairs. A ship that is always reacting is not truly maintained, even if the PMS looks good.
Another warning sign is poor technical comments. If the PMS history contains mostly generic remarks, the vessel has weak maintenance memory.
Another warning sign is crew dependency on one person. If only one engineer knows the real condition of important systems, the ship is vulnerable during crew change.
Another warning sign is repeated “monitoring.” Monitoring is useful only when it has limits, frequency, and action criteria. “Keep under observation” can easily become a polite way of doing nothing.
Another warning sign is abnormal housekeeping. Oil traces, salt deposits, temporary wires, unsecured items, missing labels, dirty filters, and neglected bilges often reveal more about reliability than the PMS dashboard.
The engine room always speaks and the question is whether the leadership is listening.
What Good Looks Like
A reliable ship does not necessarily have zero defects. That is unrealistic.
A reliable ship has visible defects, understood risks, proper follow-up, competent people, accurate records, and disciplined execution. In a good engine room, the PMS is green because the work is genuinely done, not because the system has been fed with empty confirmations.
In a good engine room, maintenance comments contain useful information, defects are raised early, repeated failures are investigated, spare parts are planned according to risk, critical equipment receives more attention than cosmetic tasks and temporary repairs are controlled and recorded.
The Chief Engineer walks the engine room and compares records with reality, but most importantly, the crew understands that the PMS is not there to impress auditors. It is there to protect the ship.
That is the correct mentality.
Compliance Is the Minimum. Reliability Is the Standard.
Compliance is necessary because a ship must comply with regulations, class requirements, company procedures, maker recommendations, and safety management systems. But compliance is only the minimum acceptable framework. Reliability requires more. It requires curiosity, discipline, technical memory, honest reporting, leadership, accountability and it requires Chief Engineers who do not hide behind dashboards.
The PMS can tell you that maintenance was planned and recorded, but only engineering judgment can tell you whether the ship is truly healthy.
This is why the best Chief Engineers do not ask only: “Is the PMS green?”,
They ask: “What is the ship trying to tell us?”
That question can prevent breakdowns, save money, avoid off-hire, protect crew and can turn a maintenance department into a reliability culture.
Final Thoughts: Do Not Let the Green Screen Fool You
A green PMS is good, but it is not enough. It should give confidence only when it is supported by real inspections, meaningful records, accurate defect reporting, machinery trends, and honest engineering judgment.
The danger begins when people stop looking beyond the screen, because the ship may already be warning you. Through a leak, smell, vibration, a rising temeperature, a repeated alarm and a machine that sounds different from yesterday.
The PMS may still be green, but the ship may be sick. And the Chief Engineer’s job is not to protect the color of the dashboard, but to protect the reliability of the vessel.
That is the difference between compliance and true engineering.
If you want more practical, real-world marine engineering articles written from the engine room perspective — not from an office chair — visit chiefengineerlog.com and subscribe.
At chiefengineerlog.com, we discuss the things that really matter onboard: leadership, machinery reliability, troubleshooting, maintenance culture, and the lessons that only the engine room can teach.
