Plant Floor Remote Operations in Manufacturing
Production and office networks are deliberately separate. OT/IT segmentation is the first question this scenario has to answer.
Updated
Settle one thing first, or you may be on the wrong page:
- You are a manufacturer managing equipment in your own plant → this page
- You build machines and support the ones you sold → remote diagnostics for equipment you ship
The constraints are entirely different. What follows is the former.
First question: OT and IT are two networks
In most plants the production network (OT) and the office network (IT) are separate, and that separation is usually a deliberate security design rather than an accident of history.
So office-network practice cannot simply be carried across. Three shapes work in practice:
- Controlled egress from the production network — IT allows specific hosts and ports; one conversation, valid long-term
- Through a jump host — connect to the jump host, reach the production network from there. One more hop, but a clear boundary
- Fully isolated — remote access does not apply. Here it is worth considering on-premises deployment, with the server inside your own network
Establish which one early. It decides not a configuration detail but whether this approach works for you at all.
Second question: line equipment cannot just be restarted
Restarting an office PC costs nothing. Restarting an industrial PC mid-run can scrap a batch of work in progress.
Remote work on the plant floor therefore demands more visibility before acting — see the state clearly first, rather than “try a restart”. Connection logs and automatic session recording are not only a compliance item here; they are the only way to reconstruct who changed what before that line stopped. Both start at the Team edition; see security and audit.
Third question: industrial PCs are not all standard Windows
Embedded systems, cut-down Windows, and Linux-based HMIs are all common on a plant floor.
The packaged WorksLink client ships for Windows and macOS only. Linux devices cannot use it. Where they genuinely need to be reachable, the client SDK is cross-platform and can be embedded into the device’s own software — see embedding remote control in your own product.
Walk the device inventory during evaluation rather than halfway through rollout.