Back to all posts
Projects & Retrofits7 min read·October 25, 2026

Which Obsolete Control Equipment Should You Replace First?

TB
ThynkBlox Automation Team
Automation Engineering

To prioritise obsolete PLC replacement, rank equipment by failure consequence, replacement availability and recovery difficulty. Put equipment with serious consequences and an unproven recovery route ahead of equipment that is simply older. Check support status, spare condition, source code and connected systems before deciding what to replace first.

What should determine the replacement order?

Start with what happens to the plant if the equipment becomes unavailable. Then establish whether you can restore its required function with the parts, files, tools and people you actually have. For equipment you keep running, see which control system spares a plant should keep.

Use these three questions for each controller, operator panel, drive or control-system component:

Decision factorQuestions to answerEvidence to record
Failure consequenceWhat stops? What happens to the process, product and connected equipment? Is there an assessed safe fallback?Agreed failure scenario, affected operations and fallback limits
Replacement availabilityIs an appropriate replacement available? Is the spare suitable and its condition verified?Exact part details, supplier confirmation and spare test record
Recovery difficultyCan the team restore the program, configuration and interfaces, then prove correct operation?Backups, required tools, access, recovery procedure and validation plan

Do not let a convenient spare cancel out a serious consequence. Safety-related concerns need separate assessment with a qualified assessor; a maintenance ranking is not a safety assessment.

Within comparable consequence groups, bring forward equipment with the weakest replacement and recovery arrangements.

How do you assess failure consequence?

Write a specific failure scenario rather than assigning a vague label such as “critical”.

For example, ask what would happen if a controller failed during production. Would one machine stop, would a shared utility become unavailable, or would several lines lose a required function? What would happen to material already in the process?

Ask operations and maintenance to agree:

  • Which equipment and production activities depend on it.
  • What happens to product already being processed.
  • How the process reaches and remains in its assessed safe condition.
  • Whether an alternative operating route exists and has been approved.
  • What must be checked before production resumes.

Separate business consequences from safety-related concerns. Record both, but do not turn them into one average score.

A device serving several machines deserves attention even if it looks minor in the control cabinet. Include shared communications equipment and supporting systems in the assessment where the plant depends on them.

What does support status actually tell you?

Treat “obsolete” as a prompt to gather evidence, not as a complete replacement decision.

For the exact equipment version, request written confirmation of:

  • Whether technical support remains available and what it covers.
  • Whether repair or replacement is offered.
  • Which replacement parts are suitable.
  • What software and access arrangements are required.
  • Any stated limits on continued support.

Keep the confirmation with the equipment record. Do not treat a reseller listing as proof of manufacturer support, or a previous purchase as confirmation of current availability.

Distinguish between support for the physical equipment and your ability to maintain its application. Even where repair is available, ask who can restore the configuration and validate the machine afterwards.

If support information is missing, record it as unknown. Give that uncertainty an owner and a next action rather than silently treating it as low risk.

When does a spare count as a recovery option?

Count a spare as ready only after its suitability and condition have been checked.

The assessment should identify the exact hardware variant, required firmware, accessories and configuration. Include power supplies, racks, communications modules and other parts needed for the proposed recovery.

Record where the spare is stored, who owns it and whether another machine relies on the same item. A shared spare should not appear as a dedicated recovery provision for every asset.

Have competent personnel define appropriate inspection and testing under controlled conditions. Keep the result and acceptance criteria with the spare.

Distinguish clearly between these states:

  • Ready: suitability verified, condition checked and restoration requirements available.
  • Unverified: an item exists, but suitability or condition remains uncertain.
  • Unavailable: no acceptable replacement has been confirmed.

A purchase order is a procurement action. Keep it separate from evidence that a usable spare is on site.

Why do source code and dependencies change the priority?

Assess recovery as a complete sequence: obtain suitable equipment, restore the application, reconnect its dependencies and validate operation.

For each asset, check whether you hold the editable project, the required software version, authorised access and relevant configuration files. Establish whether the saved project corresponds to the application currently running.

Do not assume that a file labelled “backup” provides everything needed for restoration or future changes. Record what it contains and what has actually been verified.

Map dependencies such as:

  • Operator screens, recipes and alarm settings.
  • Drives, remote input/output and communications interfaces.
  • Engineering computers, software licences and required access.
  • Connections to supervisory systems and other machines.
  • Drawings, instrument settings and machine-specific parameters.

Where source code is missing, assign an assessment before scheduling replacement. Establish what can be recovered through authorised means, what behaviour must be documented and what requires redesign.

For an agreed description of sequences, interfaces and failure behaviour, use the checklist in what a functional design specification should contain.

Where drawings are missing too, see how to assess a plant with missing control drawings.

How can you turn the assessment into a practical ranking?

Use a short priority list supported by evidence. Avoid a formula that hides a serious consequence behind several favourable scores.

The following example is illustrative. It describes a decision method, not measured plant results.

Illustrative assetConsequence and recovery evidenceProposed action
Shared process controllerSeveral operations depend on it; no verified spare; current editable project missingResolve safety-related questions with a qualified assessor, assess recoverability and develop replacement scope first
Packaging controllerOne machine affected; suitable spare tested; current project and restoration procedure verifiedRetain with documented checks and plan replacement around an agreed opportunity
Local displayApproved alternative operating route exists; replacement configuration unverifiedVerify the alternative and configuration before deciding whether replacement is urgent

The first asset leads because its consequence and recovery gap combine. The example does not justify ignoring the others.

For each priority, state the next action. That might be replacement, spare verification, backup recovery or dependency mapping. Where evidence is incomplete, an assessment may be the first urgent job.

What should the replacement plan contain?

For each asset selected for replacement, define the required outcome before choosing hardware.

Record the functions to preserve, interfaces to change, acceptance tests, responsibilities and handover requirements. Identify what must be prepared before the shutdown, including drawings, application files and test arrangements.

Define rollback conditions and the latest point at which rollback remains practical. If rollback is not feasible, state that explicitly and agree the contingency.

Our guide to planning a PLC retrofit around a shutdown window covers preparation and commissioning decisions.

Keep two actions visible for each priority asset: how to reduce the current recovery gap, and how to complete the replacement. Agree who owns each action and what evidence will close it.

What common mistakes should you avoid?

Replacing by age alone. Use age as background information. Base the decision on consequence, availability and demonstrated recovery arrangements.

Counting untested stock as protection. Verify suitability and condition before relying on a spare.

Treating a backup folder as a recovery plan. Identify the required files, tools, access and validation steps.

Assessing only the PLC. Include the connected equipment and software needed to restore the function.

Leaving unknowns unassigned. Record missing evidence, name an owner and decide how it will be resolved.

Using a ranking to approve continued operation. Where safety-related concerns arise, involve a qualified assessor and address them separately.

Revisit the ranking when support, spare condition, plant dependencies or operating requirements change.

What questions come up most often?

Should every unsupported PLC be replaced immediately?

Use unsupported status as a reason to assess priority. Examine the failure consequence, available recovery arrangements and unresolved concerns before setting the replacement programme.

What if we have a spare but no source code?

Verify exactly what files are available and whether the required restoration is possible. Keep spare availability and application recoverability as separate findings until both are demonstrated.

Can we keep older equipment after the assessment?

Retention can be a proposed outcome. Document the evidence, unresolved limits, required checks and conditions that would trigger another review. Resolve safety-related questions with a qualified assessor.

What should we do first with a long equipment list?

Identify shared dependencies and high-consequence failures, then check their replacement and recovery evidence. Turn the largest gaps into named actions before expanding the replacement scope.


Need help setting the replacement order? Contact us to discuss an assessment of your control equipment, recovery arrangements and retrofit priorities.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.