+971 55 954 5801

The decision

Working is not the same as supported

A control system that has run without incident for twelve years is evidence that it was built well. It is not evidence that it is safe to keep. The risk on an obsolete system is not that it degrades gradually, it is that it runs perfectly until one component fails and there is no replacement, no patch and nobody left who knows the configuration.

That is why obsolescence decisions get postponed. Nothing is visibly wrong, the budget is large, and the change carries risk while doing nothing appears not to. The cost of doing nothing simply arrives later and all at once.

The honest framing is a question about spares and people rather than about version numbers. Can you buy a replacement for the part most likely to fail? Is there anyone who can reconfigure it? If both answers are no, the system is already a single point of failure whatever its uptime record says.

Triggers

Four signals that it is time

Any one of these on its own is worth a plan. Two together usually means the decision has already been made for you.

Spares have gone

The controller, the workstation or a specific card is no longer manufactured and the grey market is your supply chain. Check what a failure of the single most critical part would actually cost in downtime, then compare that with the upgrade.

The operating system is out of support

SCADA nodes running an unsupported Windows version cannot be patched. On a system with any network exposure that is a security exposure, and on utility assets it increasingly fails audit.

Nobody understands the configuration

The engineer who built it has gone, the source is undocumented or missing, and every change starts with reverse engineering. This is the most common trigger and the least often written down.

The plant has outgrown it

Point count near a licence limit, no capacity for the new bay or the new station, or reporting that has to be rebuilt by hand every month. Upgrading for capability is a better position to buy from than upgrading after a failure.

Options

What an upgrade can actually mean

  • Version migration on the same platform, keeping the configuration and the operator's habits, which is the least disruptive route
  • Platform change, where the existing product line has ended or no longer fits
  • Head end only, retaining field controllers where they are still supported
  • Controller and RTU replacement below an existing SCADA that is still fit for purpose
  • Staged replacement, station by station across a network, spreading both cost and risk
  • Full replacement where the architecture itself is the limitation
  • Taking over and documenting a system before deciding anything, when nobody knows what is actually installed

Track record

Systems we have replaced in service

Every one of these was a replacement of somebody else's installed system, on plant that stayed operational.

See all 19 delivered projects →

Method

How a migration is done without stopping the plant

  1. Document what is really there

    A survey of installed hardware, firmware versions, configuration and every undocumented change made since commissioning. On systems of this age this is a deliverable in its own right and often the most valuable one.

  2. Rebuild the point schedule

    Every signal with its source, address, scaling and alarm limit, reconciled against the plant rather than against the original documentation. This becomes the acceptance criteria for the new system.

  3. Build the new system alongside

    Configured and tested in parallel, driven from simulated inputs, so it is proved before it is ever asked to control anything.

  4. Cut over in stages

    Bay by bay, feeder by feeder or station by station, with the old system available until each stage is proved. Nothing is decommissioned on the strength of a drawing.

  5. Keep the fallback until acceptance

    The route back stays open until the new system has been through site acceptance and a period of normal operation, including a fault it had to handle.

Common questions

Questions we are asked about this

Our SCADA still works. Why upgrade it?

Because working and supported are different things. The question worth answering is what happens when the least replaceable component fails: whether a spare exists, whether anyone can reconfigure it, and how long the plant is down while you find out. If those answers are uncomfortable, the system is a single point of failure regardless of its uptime record.

Can you upgrade a SCADA system without taking the plant offline?

Yes, and it is how we do most of this work. The new system is built and proved in parallel, then cut over in stages with the old one available until each stage is accepted. It takes longer than a full shutdown and it is usually the only option on utility and water assets.

Do we have to change platform?

Often not. A version migration on the same platform keeps the configuration, the graphics conventions and the operators' habits, and is considerably less disruptive. Platform change is warranted when the product line has ended or the architecture is the limitation, not simply because a newer product exists.

What if we do not have the original documentation?

That is the normal condition rather than the exception. We start with a survey and rebuild the point schedule from the plant itself. It adds time at the front, and we price it separately rather than burying it, because pretending the documentation exists is how upgrade projects overrun.

Can you work on a system another company installed?

Yes. We have upgraded and replaced GE based substation control systems for TAQA Transmission and delivered a new SCMS at Khalifa Port on Hitachi Energy hardware, in both cases replacing what was already installed.

We're here to help!

We want to hear from you. Let us know how we can help.

Send a message

Address
Office 4, Mezzanine 2, Dongfeng car showroom building, Khalifa Bin Zayed The First St
Abu Dhabi, United Arab Emirates

We want to hear from you

Tell us about the system you need built, upgraded or kept running.

Contact us