After Installation: The Maintenance and Spare-Parts Plan Your Automation Needs

The first difficult stop tests the handover

A newly installed cell runs its acceptance product successfully. A few weeks later, a sensor fails. Maintenance can identify it, but the part number in the manual differs from the installed revision. Purchasing has a supplier contact, but no confirmed replacement lead time. The controller backup exists on an engineer’s laptop, and nobody on the next shift knows whether it matches the current program.

This is an illustrative failure chain, not a Quindart customer story. None of its individual gaps looks large during a successful demonstration. Together they can turn an ordinary component failure into a prolonged interruption. The maintenance plan should therefore begin while the equipment is being specified, when documentation, access and support can still be made explicit deliverables.

Excellence industrielle’s 2024 report describes sensors for predictive maintenance in its technology showcase. That demonstrates an area worth exploring, not a requirement to buy predictive software. Before adding another alarm, establish who can inspect a fault, obtain the right part and restore the agreed operating state. [1]

Define who owns the complete operating chain

List the equipment, control software, interfaces, network dependencies, tooling and business records needed for the cell to work. A production stop may originate in a mechanical component, a disconnected order feed or an expired service account. Each needs a responsible owner and a clear route from the operator’s observation to qualified diagnosis.

Distinguish operator checks, planned maintenance, specialist work and supplier support. State what each role may do and what requires escalation. Do not let a troubleshooting guide imply permission to bypass guarding, defeat an interlock or restart equipment after an unresolved fault. Isolation, access and return-to-service procedures must be defined and approved by the site’s qualified people for the actual installation.

Write the support boundary in ordinary language. Who answers outside normal hours? Is remote diagnosis included, and who authorizes remote access? Does a response target mean acknowledgment, investigation or restoration? Record exclusions, contact routes and escalation alternatives. A contact name without an agreed responsibility is a fragile maintenance arrangement.

Choose spares by the consequence of not having them

Start with a parts register tied to the installed equipment revision. Include manufacturer, exact part number, firmware or configuration dependencies where relevant, approved substitutes, storage conditions and the document that confirms compatibility. A catalogue photo is insufficient when connectors, ratings or program versions differ.

For each part, assess failure consequence, detectability, replacement time, replenishment lead time and available workaround. An inexpensive part with a long lead time and no substitute can deserve more attention than an expensive item with reliable local availability. Have maintenance explain the practical replacement constraints and purchasing verify the replenishment assumption.

Decide deliberately which parts to hold on site, which can be obtained locally and which remain supplier-held. Record minimum stock, reorder trigger and ownership. A supplier-held spare is useful only if its availability, access and delivery arrangement are credible. Avoid treating an unconfirmed overseas listing as a recovery plan.

Review the register when a part is consumed or replaced by a new revision. Check shelf life, storage requirements and any need to preserve configuration. A spare that has deteriorated in storage, or cannot be configured without an unavailable specialist, may offer less protection than its presence on a shelf suggests.

A backup becomes useful when restoration is demonstrated

Inventory the programs, recipes, parameters, drawings, configuration files, licences and credentials needed to recover. Identify the owner, approved storage location, access controls and version. Keep secrets out of public manuals. Agree what the supplier will deliver and what remains proprietary before accepting a system that the site cannot independently restore or support.

Create a restoration test appropriate to the system and authorized by the site. It may use a spare controller or a non-production environment; it should not create an unsafe interruption just to prove that a file opens. Record the backup version, target hardware, prerequisites, person performing the test and outcome. A successful file copy is different from a demonstrated recovery.

Include the information connections. After a restore, how will the system distinguish work already completed from work still pending? Who checks that order status, batch records and counts remain consistent? Replaying every queued message can duplicate a production event or instruction. The handover should explain reconciliation and the point at which a responsible person permits normal operation to resume.

Set maintenance intervals from evidence, then revise them

Use the manufacturer’s instructions, the site’s qualified assessment and actual operating conditions to establish initial maintenance tasks. Do not copy an interval from another factory with different duty, contamination or product variation. Record whether a task is time-based, usage-based or condition-triggered, what evidence closes it and who may defer it.

Connect planned work to production commitments and parts availability. A scheduled inspection is difficult to execute if the line cannot be released or the required replacement part was never ordered. Give planning enough notice to reserve a suitable window and define how overdue safety-critical or production-critical tasks are escalated.

Add condition monitoring when a signal supports a useful decision. The signal needs a credible baseline, an interpretation, a responsible person and enough warning time to act. A rising vibration trend without a response plan can become another unattended chart. Review false alarms and missed events before expanding a monitoring system across the plant.

Accept the operating capability as well as the machine

Before final handover, walk through a short set of representative situations with production, maintenance, IT and the supplier: an unavailable part, a lost connection, a changed recipe, an interrupted shift and a controlled recovery. These are tabletop or authorized test scenarios, not invitations to create hazardous faults. Record unresolved items, owners and due dates.

Check that the site has current drawings, approved maintenance instructions, a critical-spares register, tested backups, training evidence and support contacts. Confirm that the people on the relevant shifts can find them. Where an acceptance item is incomplete, make the remaining responsibility and commercial treatment explicit rather than relying on a promise that someone will email it later.

After installation, review the first interruptions and the assumptions they exposed. Update the spare list, instructions and support boundary when equipment or production changes. Quindart treats continuing operation as part of scoping automation, with responsibilities agreed for the actual engagement. The accompanying plan helps the buyer make those responsibilities visible before a successful demonstration becomes an unsupported asset.