When the Machine PC Dies, Does the Line Stop?

The computer at the head of a production line is nothing like an office PC. It carries the machine builder's software, recipes accumulated over years, parameter files, often a USB licence dongle, and usually a version of Windows that stopped being supported some time ago. It may not even appear in the IT inventory, because nobody treats it as a computer — it is seen as part of the machine.

Then one morning it will not boot. The fault is usually an ordinary disk failure. What was on that disk is anything but ordinary to rebuild.

What actually holds you up

Finding replacement hardware is the easy part. The waiting starts afterwards:

• Which Windows version did the machine software run on, and will the new hardware even take it?
• Where is the installation media, and does the vendor still supply that version — or charge for it?
• How is the licence reactivated? Some vendors do it themselves, which means an exchange of e-mails across time zones.
• Where were the recipes, mould parameters and user settings stored?
• Serial port cards, a specific driver, a date format or a language setting can all break communication with the machine.

Each item takes hours on its own and some take days. Stacked up, a single shift of downtime turns into most of a week.

Price the downtime with your own numbers

The clearest way to see the value of this preparation is to cost one stoppage. The formula is simple: hourly output multiplied by contribution per part. Multiply that by the hours you would realistically be down, then add late orders, overtime and the delivery date you promised a customer.

Run it twice — once with the preparation in place, once without. The gap is what half a day of imaging work buys you.

A disk image, not a file backup

What matters on this machine is not the documents. It is the installation itself. Copying files will not reproduce the environment after a rebuild.

The right method is a full disk image: operating system, machine software, drivers, settings and data in one copy. Write that image to an SSD and keep it on the shelf, and the response to a failure becomes a disk swap — minutes of work instead of hours of reinstallation.

Record the licences and dongles

An image does not solve everything. Some industrial software ties its licence to hardware and loses it when the disk changes. Alongside the image you need a written record:

• Which software, which version, which licence number
• Whether there is a USB dongle, where it is kept, and whether a spare exists
• Who performs activation, and through which e-mail address or phone number
• Where the installation media that shipped with the machine is stored

The record fits on one page, and on the day of a failure it is the most useful document you own.

Taking the image safely

• Work during planned downtime, never while the line is producing.
• Nothing is done to the machine's own program, that is, the PLC side. What is copied is the computer's disk.
• Restores happen with the plant supervisor's approval and in their presence. The decision to return to production belongs to the plant.
• Bring the restored machine up carefully: an operator panel can write values to the machine as it starts, so make sure the line is clear and safe first.
• Test the image once after taking it. An untested image is not a backup, and the worst moment to discover that a copy will not open is during a breakdown.

Refresh it once a year

Every software update, new recipe and changed setting ages the image. Refreshing it once a year, ideally during the annual maintenance stop, is enough. Do not delete the previous image immediately; keep two versions side by side.

How Yamanlar Bilişim helps

Our part is this: inventory the machine PCs, take a full disk image during planned downtime, prepare the spare disk, and put the licence record in writing. We do not touch the machine's program. The equivalent discipline on the server and office side sits in our backup and disaster recovery work, and the rest of what we do for production sites is on the manufacturing and workshops page.

Frequently asked questions