Servicing every asset every quarter looks fair on paper.
It spends the same hours on a toilet extract fan as on the AHU holding a Grade B suite.
Calendar maintenance is easy to schedule and easy to audit. Its weakness is that it has no view of consequence. When the team is short of hours, which it usually is, the cut falls evenly, and the assets that matter get the same thin slice as the ones that don't.
Criticality-based maintenance starts from a different question: what happens to product or to the validated state if this asset fails? An AHU whose failure takes a Grade B room out of its 10 to 15 Pa cascade is critical. So is its pressure control damper, and the differential pressure sensor the BMS alarms on. A comfort-cooling split unit in an office is not.
Scoring each asset that way moves effort. Critical assets get shorter intervals, condition monitoring, and spares held on site. Low-criticality assets can move to longer intervals or run-to-failure where the risk is accepted in writing. The total hours may not change much. Where they go does.
The work is in the scoring, and it is best done once from the project's own asset register rather than reinvented by the maintenance team after handover. That is how we build maintenance plans at the end of a project.
To talk it through: contact@humiley.com or +84 28 7777 6668 (Viet Nam office).
Industries




