Acceptance as maintenance archiving: how to use the data left from commissioning

Typical acceptance deliverables are not enough to support later maintenance: without no-load and full-load baseline current, vibration and temperature data, later degradation has nothing to be compared against; without a wear parts list, spare preparation is guesswork.

This data is cheapest to capture during installation and commissioning; miss it and it is gone for good.

We added three mandatory items to the acceptance list: a baseline data sheet for every station (current, vibration, temperature, cycle time), a wear parts and recommended spares list, and a controller fault code and action table.

The data goes straight into the equipment file and the inspection standard: inspection thresholds are derived from the baseline data and spare stock is initialised from the list. The day acceptance is completed is the day the maintenance system starts.

Acceptance is in essence about establishing the first trustworthy data set for the equipment's whole life. An acceptance that collects only a certificate gives that data up.

The value of baseline data shows up six months later: every question of whether something has degraded has an anchor to compare against.

In most plants acceptance and maintenance are two disconnected skins: once acceptance is signed, the data is locked in a drawer, and equipment may enter service with hidden problems while nobody knows where the starting point is. This case welded the two together - the acceptance checklist mandatorily includes three items, a baseline-data sheet, a wear-parts list and a fault-code reference table - so that the day acceptance is completed is the day the maintenance system starts. Inspection thresholds are derived from the baseline data and spare-part inventory is initialised from the list, with not a single day's gap.