Industrial PCs routinely last 10 to 15 years or more. The people who commission them typically don’t! Engineers move on, system integrators change, facility managers rotate through roles. The institutional knowledge of how a system was built, configured and connected leaves with them. This makes it essential for system integrators to create a handover package for every industrial PC, one that survives the inevitable changes in staff, contractors and organisational knowledge over the years between commissioning and failure.
It’s a situation we see a lot. A beverage manufacturer contacted us to build a replacement for a failed rackmount industrial PC that had been controlling their bottling line. The original system was old, running a legacy operating system with proprietary add-on I/O cards and specialist software. No documentation existed. No disk image. No record of the hardware specification, the I/O card models or the software configuration.
To specify a replacement, we needed detailed photos of the original system, access to analyse the system drive, and significant research time to identify components and find a compatible hardware platform that could accept the original I/O cards and run the legacy software. What should have been a straightforward hardware replacement became a forensic investigation that added weeks to the lead time and substantially increased the cost.
In another example, we were called to several Coles supermarkets where Ethernet-to-serial converters connecting PCs to commercial refrigeration controllers had failed. There was no documentation for the serial port configuration, and the existing converters were password protected. We spent several days on site using trial and error to determine the correct serial settings before we could configure replacement units. The information needed to do that job in 20 minutes simply didn’t exist in any accessible form.
The pattern is consistent. Even where documentation and disk images were created at commissioning, the people who knew where they were stored have often left the organisation before the equipment fails. New staff are not told about the backups. When a failure occurs, nobody knows anything about the system configuration or where any records might be.
The organisations that handle this well are typically those where a contractor or integrator maintains a long-term relationship with the end customer and stores all site equipment configuration details and OS images on their behalf. When hardware eventually fails, they can procure a replacement and configure it without starting from scratch. That relationship and that documentation are worth far more than the cost of creating them.
What should be in the handover package
The following is a practical checklist for any industrial PC handover. None of these items are difficult to produce at commissioning time. All of them become difficult or impossible to reconstruct years later!
System overview and block diagram. A person tasked to replace a failed PC 10 years in the future will likely not have any background knowledge about how the overall system works and fits together, unless that has been documented. Document how the whole site plant works, with block diagrams and descriptions that include why certain design decisions were made. Then the details of the industrial PCs and other equipment can be understood in the overall site context, which makes it much easier to specify a replacement with confidence.
Hardware specification. The full model number, motherboard, processor, RAM and SSD types and capacities including industrial grade and wide temperature ratings, and any expansion cards installed. It’s important to note the environmental ratings that the PC was specified with. This allows a supplier to quote a compatible replacement without needing to inspect the original unit. The difference between having this information and not having it can be the difference between a same-day quote and a multi-week investigation.
Operating system and licence keys. The OS version, edition and licence key. For Windows IoT or embedded licenses, the licence type and any activation details. If the licence is tied to hardware, note that. A replacement PC without the correct licence information may require purchasing a new licence, if one is even available for a legacy OS.
BIOS and firmware settings. Any BIOS settings changed from factory defaults, and the reason for the change. This includes boot order, serial port configuration, power-on behaviour and any settings related to specific I/O cards or peripherals. A replacement PC configured with default BIOS settings may not work correctly, and without documentation, nobody will know what needs to change.
Application software and configuration. The application name, version, installer media or source, licence keys, and any configuration files or settings specific to the site. If the software vendor requires a support contract for access to installers or updates, note the contract details.
Full disk image. A complete image of the system drive, stored in a known location with clear labelling. This is the single most valuable item in the handover package. A current disk image can reduce recovery time from weeks to hours. It captures everything: the OS, drivers, application software, configuration and licence activation state. The image should be updated periodically and verified to confirm it can be restored successfully.
Network configuration. IP address, subnet mask, gateway, DNS settings and any VPN or remote access configuration. For systems on industrial networks, document the network segment and any firewall rules or access controls that apply.
Serial, USB, and other interface connections. For every connected device, document the port used, the protocol, the baud rate and serial settings, and any driver requirements. This is the information that turns a multi-day trial-and-error exercise into a five-minute configuration task.
Power supply details. The input voltage, connector type and power supply model. This is simple to document and prevents a common and expensive mistake. We have seen industrial PCs ordered with 12V DC inputs connected to 24V industrial supplies, resulting in instant damage. We have also seen PCs connected to under-rated power supplies causing erratic behaviour. Recording what the system actually needs avoids these problems on replacement.
Spare parts recommendations. A recommendation for which components should be held as spares, including whether an identical configured spare PC should be purchased.
Handover location and access. Where the documentation package is stored, who has access and how it will be maintained over time. Ideally a placard should be displayed at the PC location showing where the documentation and backups are stored. This is the detail that determines whether the documentation actually gets used when it is needed, or whether it disappears into a filing cabinet and is forgotten.
The spare PC conversation
Recommending a configured spare PC as part of the handover is the item on this list that integrators most commonly leave out. The concern is understandable: it increases the project cost, and integrators worry that the customer might see it as a lack of confidence in the system being delivered.
The framing matters. A spare is not recommended because you expect an imminent failure. It’s recommended because nothing lasts forever, and the real problems occur 10 to 15 years down the track. When the then-obsolete PC finally fails, nobody remembers anything about the system, and a compatible replacement is difficult or impossible to source.
A spare purchased and configured at commissioning time, stored with the handover documentation and a current disk image, transforms the eventual failure from a crisis into a planned swap. The cost of the spare is a fraction of the cost of emergency recovery, expedited sourcing and production downtime that results from not having one.
Integrators who include this recommendation, and explain the reasoning clearly, are providing genuine long-term value to their customers. It also reinforces the integrator’s role as a trusted advisor with a long term focus, rather than simply a system installer.
Who is responsible?
The handover package should be created by the integrator who commissions the system, but the end customer needs to take ownership of maintaining and storing it. Both parties should know where it is and how to access it.
For organisations with IT staff involved in plant equipment, disk images and system documentation tend to be better maintained. Where plant equipment is managed by facility managers or operations staff without an IT background, these items are more likely to be overlooked. This isn’t a criticism of those staff. It simply reflects that disk imaging and system documentation are not part of their normal responsibilities. The integrator is in the best position to create these records and explain their importance during handover.
The best practice we see is where the integrator retains a copy of the full handover package and the end customer holds another. If either party loses their copy, the other can provide it. If the integrator relationship changes, the customer still has everything they need.
The cost of getting it right – or wrong
Creating a complete handover package at commissioning adds a modest amount of time to the project. A few hours of documentation, a disk image and a clear handover conversation with the customer.
Skipping it saves that time in the short term. But when the PC fails years later and nobody knows the specification, the configuration, the licence keys or the serial port settings, the recovery cost is measured in weeks of lead time, thousands of dollars in investigation and reverse-engineering, and the production downtime that accumulates while it all happens.
The organisations that recover quickly from hardware failures aren’t the ones with the newest equipment. They are the ones with the best documentation.
How ESIS can help
We keep records of every system we build, so when a customer needs a replacement or a spare, we can replicate the original specification without starting from scratch. But we can only do this for systems we supplied originally. For systems we didn’t build, we depend on whatever documentation exists, and in many cases, that’s very little.
If you are an integrator delivering industrial PC systems, we are happy to work with you on documentation templates, disk imaging advice and spare hardware planning. If you are an end customer who has inherited a system with no documentation, we can help assess what you have and develop a plan to reduce your exposure.
Contact us to discuss your current and future industrial PC requirements.
