Manufacturing Downtime: Reducing Server Interruptions in Production Operations
Updated: Nov 5

An MES outage does not always stop the machinery. Local PLCs may continue executing existing control logic while the application used to issue work orders, record production steps and track work in progress is unavailable. The result is a gap between what is happening on the production floor and what the central system can see and record.
How a Server Interruption Affects Production Operations
An MES or production-management application may support:
Work orders and production instructions
Work-in-progress status
Material and product tracking
Production records and performance information
Data exchange with ERP, warehouse or quality systems
Operator visibility and exception handling
When the server becomes unavailable, operators may be unable to retrieve the current work order, record a completed step or confirm whether connected systems received the latest production information.
Where the affected workload is a supervisory or monitoring application, operators may also lose visibility of alarms and current process status.
Local controllers can continue executing existing logic, but the production team may still need to hold the affected job while it verifies the application state, reconciles missing updates and confirms that the next operation can proceed.
Why the Recovery Window Matters
High Availability is designed to restore an affected workload, commonly by restarting or transferring it to another environment.
This reduces downtime, but users and interfaces may need to reconnect. Queued information may need to be processed, and work-in-progress records may need to be checked before normal operations resume.
Where this recovery work is acceptable, HA may be sufficient. Where restarting the production application creates an unacceptable operational interruption, Fault Tolerance should be evaluated.
Where Fault Tolerance Fits
vServerFT keeps CPU execution, memory and disk state synchronised in real time across two physical nodes.
During a covered hardware failure, it is designed to keep the protected virtual server workload running without requiring the application to restart.
For a compatible MES, supervisory or production-management workload, this can allow the infrastructure team to address the failed hardware while the protected application continues running. It can help maintain access to production information and avoid the reconnection, backlog and record checks caused specifically by an application restart.
For a broader explanation of why avoiding the restart matters, see Why Fault Tolerance Matters: Real Benefits Beyond Failover.
Define and Test the Protection Boundary
FT protects the server workload placed within the FT environment. It does not make the complete production line fault tolerant.
PLCs, robots, CNC machines, sensors, production equipment, plant networks and external systems require their own protection and recovery arrangements. FT also cannot correct inaccurate production instructions or data.
Before deployment, the manufacturer, application supplier and infrastructure team should confirm:
Which application and server components will be protected
Whether the application vendor supports the proposed virtual environment
Which databases, interfaces and network paths the application requires
Which failures remain outside the FT platform
During a controlled hardware failure test, users should still be able to access the protected application, view current production information and exchange the required data with connected systems. Equipment, controller and network failures outside the FT platform should be tested separately.




