The failure of orphaned systems is one of most common scenarios we encounter. Industrial systems are built to last for up to 20 years, but the integrators and engineers who build them rarely stay that long in the same role, let alone at the same company. When the system eventually fails, it causes a cascade of challenges that can’t be easily overcome.
Picture this. A maintenance manager at a water treatment plant calls ESIS with a problem that has nothing to do with hardware failure. The industrial PC running their filtration control system is working fine. The problem is that nobody knows just how it works. This is what we call an orphaned system.
The systems integrator who designed and commissioned the system eight years earlier has closed their business. The original project engineer has retired. There’s no documentation beyond a single-page network diagram pinned to the inside of the cabinet door. The PC is running a custom SCADA application on Windows 7, communicating with PLCs over serial, with a configuration that has clearly been tweaked and tuned over the years by someone who understood it deeply.
That someone has gone. And the maintenance manager knows that when the PC eventually fails, they will be in serious trouble.
A common situation that nobody plans for
People move on. Businesses close. Engineers retire. Contractors finish their engagement and move to the next project. The knowledge of how a system was built, why certain decisions were made, and what quirks exist in the configuration walks out the door with them.
What remains is an industrial PC sitting in a cabinet, doing its job quietly, with no one on site who fully understands what is running on it or how it was set up.
These orphaned systems work until they don’t. And when they stop working, the recovery process isn’t a simple hardware swap. It’s a forensic exercise.
What makes the failure of these systems difficult
When a well-documented system fails, replacing the PC is relatively straightforward. You know the operating system, the application software, the communication protocols, the I/O requirements and the configuration details. You can rebuild it.
When an orphaned system fails, you are starting from almost nothing.
Here is what typically needs to be figured out, often under significant time pressure:
- What operating system is installed, and is it a standard build or a customised embedded image?
- What application software is running, and where are the installation files or licence keys?
- What communication protocols are in use, and how are they configured?
- Are there custom scripts, scheduled tasks or startup routines that are not obvious?
- What expansion cards or serial adapters are installed, and what drivers do they need?
- Are there dependencies on specific hardware, such as legacy ISA slots, parallel ports or particular chipsets?
- Has the configuration been modified since commissioning, and if so, by whom and how?
Answering these questions with a dead PC and no documentation can take days or weeks. In a production environment, that translates directly to downtime, cost and stress.
The hardware isn’t the real cost
The industrial PC itself might be worth a few thousand dollars. The cost of the work to understand, replicate and restore the system can be many times that. And the cost of extended downtime while that work happens can dwarf everything else.
We have seen situations where a failed orphaned PC led to weeks of reduced plant capacity because the replacement process required reverse-engineering the entire software environment. In one case, the original application software was no longer available from the vendor, and the licence was tied to hardware that no longer existed. The eventual solution required significant engineering effort to recreate the operating environment on modern hardware while preserving compatibility with the existing PLC infrastructure.
These are not unusual situations. They are predictable consequences of systems that outlive the people who built them.
How to avoid a crisis
There are some practical steps maintenance managers can take before an orphaned system fails.
- Document what’s running. Open the cabinet. Record the PC model, serial number, operating system version, installed software, network configuration and any expansion cards. Take photos of the wiring, the BIOS settings, and the Windows device manager. This basic information can save days during a recovery.
- Create a disk image. A full disk image of the running system is the single most valuable thing you can have when a PC fails. It captures everything: the operating system, application software, drivers, configuration and any customisations that were made over the years. Store it securely and verify it periodically.
- Identify critical dependencies. Does the system rely on a specific operating system version? Are there legacy communication protocols like serial Modbus or proprietary interfaces? Are there expansion cards that are no longer manufactured? Understanding these dependencies tells you how difficult a future replacement will be.
- Assess hardware availability. If the PC is an older model, find out whether compatible replacement hardware is still available. If it’s not, start planning now. Waiting until the PC fails and then discovering that the hardware is obsolete turns a manageable problem into an emergency.
- Talk to your equipment suppliers. A good industrial hardware supplier can help you assess the current state of your installed base and identify systems that are at risk. They can also advise on replacement hardware that maintains compatibility with legacy software and interfaces, which is often the most critical requirement.
The best time to replace an orphaned industrial PC is while it’s still running. You have access to the live system, you can test the replacement alongside the original, and you can manage the transition on your own schedule rather than in the middle of a production crisis.
This doesn’t mean every old PC needs to be replaced immediately. It means you should know which systems are most at risk, and have a realistic plan for what happens when they fail. For some systems, that plan might be a spare PC with a cloned disk image sitting on a shelf. For others, it might be a planned migration to current hardware and software during the next scheduled shutdown.
The key is making these decisions deliberately, with good information, rather than reactively under pressure.
How ESIS approaches these situations
We deal with orphaned industrial systems regularly. In many cases, the customer comes to us after a failure has already occurred, and the work becomes a recovery exercise. But increasingly, we work with maintenance teams and project engineers who are proactively reviewing their installed base, and planning ahead.
Our approach typically involves assessing the existing hardware and software environment, identifying compatibility requirements and constraints, and recommending replacement hardware that preserves the customer’s investment in their existing software and infrastructure. For legacy systems running older operating systems or relying on obsolete interfaces, this often means selecting industrial PCs that support the specific I/O, chipsets, or operating system versions that the application requires.
We have built replacement PCs for systems running everything from DOS to Windows XP Embedded to early Linux distributions. The hardware is rarely the hard part. Understanding the full picture of what needs to be replicated is where the real work lies, and that work is dramatically easier when it starts before the original system fails.
Don’t wait for the emergency
If you have industrial PCs on your site that were commissioned by people who are no longer available, those systems deserve attention now. Not panic, not an immediate replacement program, but a deliberate assessment of what’s running, what the risks are and what your options look like.
The engineers who built these systems usually did good work. The systems have lasted for years, often well beyond their expected life. But longevity without documentation creates a specific kind of risk that only becomes visible when something breaks.
If you are managing systems like these and want to understand your options, get in touch with us. We can help you assess what you have, identify the highest-risk systems and plan a practical path forward.
ESIS Industrial Electronics offers a range of industrial computing solutions, including rugged tablets, data loggers, industrial displays, integrated computing platforms and programmable interfaces for direct PLC integration. Talk to us about your project requirements, and solutions to keep business operations running efficiently.
