Obsolescence is usually treated as a lifecycle event that arrives years after installation, often at the worst possible moment. In practice, the decisions that determine how painful or how uneventful obsolescence will be are made much earlier, during commissioning and acceptance. This article provides a checklist-based framework for warehouse operators, maintenance engineers and controls teams to capture the evidence, spare-part strategy and failure-coding discipline needed before a system is handed over to operations.
The focus here is not on predicting which component will fail first. It is on making the current state of the installed equipment knowable and reproducible so that future maintenance decisions are based on evidence rather than on memory. A conveyor zone, a sorter, an automated storage and retrieval machine or a palletizing cell can all be treated with the same logic: what we do not record at commissioning, we cannot compare against later, and what we cannot compare against, we cannot manage proactively.
The Commissioning Window as an Obsolescence Opportunity #
Commissioning is the period when equipment is operated under controlled conditions, usually with manufacturer representation on site, with load profiles being exercised and with access to internal parameters that will later be hidden behind security settings. For maintenance teams, this is the last and best opportunity to record condition baselines, thermal signatures, vibration levels, current draws, firmware versions, setpoint values and network configurations.
Obsolescence planning is not about predicting the future. It is about making the present state reproducible. When a drive, controller or network switch fails several years after commissioning, the maintenance team must be able to answer three questions. What exact hardware and firmware version is installed? What were its normal operating parameters? And what evidence exists to prove that a replacement behaves in the same way as the original? Without a commissioning baseline, none of these questions can be answered reliably.
Functional acceptance tests typically focus on throughput, cycle time, accuracy and safety. Obsolescence planning adds a different acceptance question: can the as-built configuration be maintained for its intended life? This shifts the conversation from whether the machine works today to whether the machine can be repaired tomorrow. Warehouse operators often discover that a machine performs well in acceptance tests but has a single proprietary circuit board with no alternative supply. The commissioning record should make that reality visible before the commercial acceptance is signed.
Obsolescence evidence is time-sensitive. Software version records only remain accurate as long as nobody changes the configuration. Wiring photographs only remain useful if the physical layout is not altered. This is why the commissioning window matters: it is the point at which the as-built state matches the documented state, and the discrepancy between the two is smallest.
Scope and Authority Boundaries #
The checklist in this article is a supporting document. It does not override site procedures, lockout requirements, OEM documentation or the judgment of competent engineers. Any inspection or acceptance activity must respect energy isolation rules, safe access requirements and the equipment manufacturer’s limits. No observation or evidence-collection task should create a hazard or require the temporary disabling of a safety function.
The ownership of obsolescence evidence should be explicit from the start. The maintenance engineer owns the maintainability review and the spare-part evaluation. The controls team owns the software, firmware and network inventory. The operations team owns the functional acceptance tests. A single coordinator should consolidate the evidence and maintain the obsolescence register after handover. When responsibilities are distributed without a coordinator, evidence becomes fragmented and later interpretations become unreliable.
Pre-Commissioning Obsolescence Review #
Before equipment is energized, the maintenance and controls teams should begin a structured review of what has actually been delivered. This is not a paper exercise. The purpose is to identify components that will be difficult to source, difficult to configure or difficult to replace over the equipment’s service life.
The following items should be gathered and reviewed prior to commissioning:
- Manufacturer’s recommended spare parts list, including part numbers that appear on the actual nameplates rather than the part numbers from a general catalog.
- End-of-life notices, last-time-buy deadlines and long-term availability statements for electronics, drives, PLCs, HMIs and network infrastructure.
- Firmware and software version matrix for all programmable devices, including sensors and safety relays where applicable.
- Configuration backups and documented restore procedures for each device.
- A list of long-lead-time items that could extend downtime beyond the target the warehouse operator has in mind.
- Identification of third-party components embedded within an OEM assembly. This is particularly important in automated warehouses where a single supplier may integrate devices from several manufacturers.
The spare parts strategy must distinguish between three categories that serve different purposes. Consumable spares are wear items consumed during normal maintenance, such as belts, filters, lubricants and wear strips. Insurance spares are kept to cover failure modes that have a low probability but a high consequence if they occur, such as a sorter controller board. Obsolescence stock is purchased intentionally as the last available supply, typically for electronic components, proprietary boards and devices whose manufacturer has announced discontinuation. A common error is to treat all spares as equivalent, which leads to obsolescence stock being consumed during routine repairs without triggering a replenishment or substitution decision.
Obsolescence stock must be stored under controlled conditions. Electrostatic-sensitive components require anti-static packaging. Battery-backed devices may need periodic refreshing. Rubber and plastic parts may degrade even in storage. The commissioning plan should include a storage procedure and, where permitted by the manufacturer, a periodic functional test schedule for critical obsolescence stock.
Inspection Design for Maintainability Evidence #
Inspection design during commissioning is the act of defining which physical and logical measurements will be captured as the reference set for future condition assessment. The goal is to collect evidence that will allow future maintenance teams to evaluate equipment health without disassembling it and without running it under unsafe conditions.
Measurement points should be defined for temperature, vibration, current, torque, pressure and flow where these parameters are meaningful. Each measurement point should be marked physically, photographed and referenced with a consistent naming convention. The naming convention should include the zone, the asset, the component and the direction of measurement. A motor bearing on a transfer conveyor should have a name that tells a future engineer exactly which bearing was measured, not just which motor was involved.
Baseline values should be stored in a repository that is accessible to both the maintenance and controls teams. This repository is not a maintenance report; it is a controlled document that will be referenced for years. It should contain the date, the responsible engineer, the instrument used and the operating conditions at the time of measurement.
Visual inspection evidence is equally valuable. Cable terminations, connector seating, grounding and strain relief should be photographed before panels are fully dressed and before covers are installed. These photographs serve as a reference when later electrical faults are suspected to be caused by poor installation practice.
Evidence Collection Standards #
Evidence should be recorded by a nominated engineer and reviewed by a second person where possible. A personal log book is not a substitute for a structured record because personal logs are rarely accessible to the entire maintenance organization. Each evidence record should include the date, the equipment identifier, the measuring instrument and the calibration status of that instrument.
Photographs should include a scale reference and a location identifier. For example, a photograph of a drive panel should show the panel label, not just the interior wiring. Environmental conditions should be recorded for every baseline measurement. A motor current reading on a warm day under partial load is not comparable to a motor current reading on a cold day under full load. Without the environmental context, a future comparison may produce a false alarm or may mask a real deterioration.
Software evidence is different from physical evidence. The evidence should include the exact version number, a checksum or hash if available, the installer’s name, the date and a description of functional behavior at the time of capture. A screenshot of a setting screen is useful only if the context in which the setting appears is clear.
Common Interpretation Errors in Baseline Evidence #
The most frequent error in using baseline evidence is comparing readings that were recorded under different conditions. A vibration baseline taken at no-load is not useful for evaluating the same equipment under load. A thermal image taken during a cold warehouse environment is not useful for comparison with an image taken in summer. The commissioning record must therefore state the load profile and ambient conditions for each baseline reading.
Another common error is confusing installation vibration with operational vibration. Some vibration is present during commissioning because the equipment is being run in for the first time. This is not necessarily a defect, and it is not the same as the steady-state vibration that will appear after the equipment has settled. Baselines must be taken under representative load, after the equipment has been run long enough to stabilize, not during a cold start.
Thermal images are often treated as calibrated temperature measurements even when the camera settings have not been verified against a reference. An infrared image is a relative representation of surface temperature, and its accuracy depends on emissivity settings and distance. The commissioning record should state the emissivity setting used and the distance from the target.
Finally, teams should not assume that controller memory is persistent. Many PLCs, drives and HMIs overwrite or clear event buffers, alarm histories and diagnostic logs when power is removed or when a new program is loaded. If a fault is witnessed during commissioning, the evidence must be captured before the system is powered down, because it may not exist afterward.
Failure Coding and Repeat-Fault Reduction #
Obsolescence planning is incomplete without a failure coding scheme that will remain meaningful for the entire service life of the equipment. Failure codes are not a clerical convenience. They are the backbone of repeat-fault reduction. If a failure cannot be coded consistently, it cannot be counted, and if it cannot be counted, it cannot be identified as a repeat pattern.
During commissioning, every component should be tagged with a unique physical identifier and a logical identifier that matches the control system. A conveyor motor may be physically labeled M-12 and logically referenced in the PLC as Zone-12-Motor. The failure code system should reference both identifiers so that a maintenance person in the field and a controls engineer looking at alarms are describing the same physical object.
The failure code should describe four elements: the failed component, the failure mechanism, the likely cause and the detection method. For example, a code might identify a limit switch, an intermittent contact, a worn cam and detection by a through-beam sensor. This level of detail supports both corrective maintenance and root-cause analysis.
Building the Coding Taxonomy #
The taxonomy should be kept flat, with no more than two
Practical Review Table #
| Review area | Evidence | Interpretation caution |
|---|---|---|
| Operating state | Mode, sequence step, mission and interlock status | Expected holds can resemble equipment faults. |
| Physical condition | Alignment, wear, contamination, obstruction and load condition | One visible defect may be a consequence rather than the cause. |
| Event history | Time-aligned alarms, input changes and recent interventions | Unaligned clocks can reverse the apparent event order. |
| Validation | Controlled test result under representative conditions | A single successful cycle does not establish long-term reliability. |
Apply this table to obsolescence planning: commissioning and acceptance checklist using approved site procedures and documented evidence.
