Industrial modernisation has traditionally been associated with replacement cycles. Equipment reaches a certain age, newer technology becomes available and the organisation begins considering when the existing system should be replaced. That approach becomes much harder to justify when large industrial sites contain thousands of automation assets installed at different points in time, performing very different functions and carrying very different levels of operational importance.

For operators in the Middle East managing large process facilities, manufacturing plants or networks of sites, replacing everything that is approaching obsolescence is rarely realistic or necessary. The more useful question is what happens if a particular asset can no longer perform its function and how difficult it would be to restore that function. An older component with adequate support and spare coverage may present manageable exposure, while another component that appears less urgent could create a significant production interruption if there is no replacement available when it fails.

This changes modernisation from a technology-refresh exercise into a risk-management discipline. Rather than asking which equipment is oldest, organisations need enough information about their installed assets to understand where lifecycle risk intersects with operational criticality.

‘Modernisation must compete for capital and engineering resources alongside other operational priorities.’ – Sudhir Gupta

Rockwell Automation’s 2026 State of Smart Manufacturing research illustrates the wider pressure behind that shift. In the Middle East, 41 per cent of manufacturers identify increasing business resilience as an important outcome from digital transformation, while investment still must contend with practical constraints: 39 per cent cite internal budget pressures and the same proportion identify the ability to execute capital projects as an obstacle. Modernisation therefore must compete for capital and engineering resources alongside other operational priorities, making it increasingly important to direct investment toward the assets where it will remove the greatest exposure.

Age is not the same as risk

A useful assessment begins with knowing what is installed. Although most organisations have equipment records, the physical plant can evolve considerably over the life of an automation system. Components are replaced during maintenance; production equipment is modified and software changes as systems are supported over time. The information originally created when the plant was commissioned may therefore no longer provide a sufficiently accurate picture for making long-term investment decisions.

As automation products move towards the end of their commercial life, the availability of replacement parts and technical support can begin to change, adding another layer to the risk assessment. Lifecycle status alone, however, still does not establish priority because the operational consequence of losing an asset can differ enormously from one application to another.

A component supporting a duplicated or non-critical function may be able to remain in service for longer if there is an appropriate contingency. The same lifecycle position on equipment that constrains an entire production process deserves very different treatment. Criticality therefore needs to sit alongside obsolescence when decisions are made.

The operational impact of a failure depends not only on whether a replacement component exists, but on whether it can be obtained and installed within an acceptable period. Restoration time therefore needs to be part of the risk calculation, because a spare that is theoretically available but cannot reach the site quickly enough to meet production requirements offers a very different level of protection from one held locally and ready for use.

Increasing inventory indiscriminately is not the answer

Modernisation planning also needs to account for the dependencies between physical control equipment and the software environments that support it. Existing applications may rely on particular operating systems, software versions or communications architectures, while an upgrade in one part of the system can create compatibility issues elsewhere. Mapping those relationships before migration begins reduces the risk of discovering hidden dependencies during commissioning or, worse, within a tightly controlled shutdown window.

An installed-base assessment therefore becomes valuable because it brings those different forms of exposure into the same decision. The objective is not simply to produce an inventory. It is to distinguish between equipment that can continue operating with acceptable support and equipment where the combination of criticality and diminishing supportability has created an unacceptable operational risk.

Spares belong in the resilience strategy

The same reasoning changes how organisations should think about spare-parts inventories. Industrial storerooms are often viewed through the lens of inventory cost, with pressure to reduce the amount of capital tied up in components that may remain unused for years. For automation equipment approaching obsolescence, however, the absence of a relatively low-value component can potentially determine how quickly an important process returns to service.

Increasing inventory indiscriminately is not the answer. The objective should be to align spare coverage with operational exposure, identifying where a critical asset requires local protection and where existing inventory provides little meaningful resilience.

That assessment can reveal problems in both directions. Plants may be carrying excess stock for equipment that is no longer critical or may already have been replaced, while another production area has inadequate coverage whose failure would have a much consequence. Viewing the installed base and the storeroom together allows inventory decisions to reflect production requirements rather than historical purchasing patterns.

Across multi-site organisations, similar automation platforms may be operating at several locations even though spare-parts inventories are managed independently. Looking at those sites collectively can reveal where support strategies could be coordinated more effectively, while still recognising that geography, lead times and the criticality of individual operations may justify keeping certain components locally.

Phased modernisation is particularly important in operations

This enterprise perspective can also expose the cumulative scale of obsolescence. A single ageing component may represent a manageable problem at one site, but the same component deployed repeatedly across several facilities can create a larger business exposure. Conversely, identifying common equipment across the organisation may create opportunities to manage remaining spares more intelligently while migration is phased.

Installed-base information needs to remain current for that approach to work. A one-off assessment provides a valuable baseline, but plants continue to change after the exercise has been completed. Equipment is replaced during routine maintenance and modernisation projects alter the composition of the asset base. Without a process for maintaining that information, the organisation gradually returns to the same uncertainty it was trying to eliminate. The goal should therefore be a living view of lifecycle exposure rather than a report that is produced, used for one investment decision and then allowed to become outdated.

Sequence modernisation around consequence

Once risk is visible, modernisation can be planned very differently. Instead of creating a large backlog labelled simply as obsolete equipment, organisations can separate assets that require intervention from those that can remain safely in service with appropriate support.

For some equipment, the sensible response may be migration because the combination of operational importance and limited support has become too great. Elsewhere, stronger spare coverage may allow migration to wait until a planned production outage or a wider control-system upgrade. Assets presenting comparatively little operational exposure can remain further down the investment schedule.

That flexibility matters when the ability to execute capital programs is itself constrained. A risk-based roadmap provides a reason for sequencing expenditure beyond the age of the technology and makes it easier to explain why one migration should take precedence over another. Capital can be concentrated where it removes the most significant exposure while engineering teams avoid taking on unnecessary change.

It also encourages modernisation to be coordinated. An equipment replacement may create an opportunity to improve access to operational data or strengthen connectivity, but those benefits should be considered within the future architecture rather than added as an afterthought to an obsolescence project. Equally, replacing equipment without understanding its dependencies can create unnecessary integration work and increase the complexity of the migration. 

Cybersecurity also needs to be considered as part of that modernisation strategy. Many legacy automation environments were designed around relatively flat or closed networks, whereas modern industrial systems increasingly rely on more open Ethernet-based architectures and greater connectivity between operational and enterprise systems. As organisations migrate automation assets to newer technology, the opportunity should therefore be used not only to improve performance and connectivity, but also to build security into the modernised architecture from the outset.

Phased modernisation is particularly important in operations where shutting down an entire plant or production system is impractical. Once the installed base has been mapped and dependencies understood, migration can be divided into manageable stages and aligned with maintenance periods or other planned interventions. This allows organisations to reduce exposure progressively without treating modernisation as an all-or-nothing decision.

The discipline also protects against the opposite mistake: retaining legacy systems indefinitely simply because they continue to run. Reliability today does not guarantee supportability tomorrow. If an organisation waits until a critical obsolete component fails before determining its replacement strategy, the migration timetable is being dictated by the failure rather than by the operator.

A more mature approach establishes that strategy while the equipment is still functioning. Teams know which assets can be sustained, where critical spares are required and which systems need a defined migration path. Modernisation then becomes a planned response to changing risk rather than an emergency reaction to equipment failure.

For industrial operators, this is ultimately the value of understanding the installed base in detail. It creates the evidence needed to distinguish ageing from genuine exposure and allows limited investment to be directed towards the areas where it will make the greatest difference to operational continuity.

The objective is not to eliminate every legacy asset from the plant. It is to reach a position where the organisation understands the risk attached to keeping each critical system in service and has a credible response when that risk becomes unacceptable. When modernisation decisions are made on that basis, capital planning becomes more defensible and migration can take place on the operator’s timetable rather than being forced by the next failure.