Industrial augmented reality can put visual instructions and other information into a worker’s field of view, while virtual reality can create immersive environments for training, design, and collaboration. For industrial automation teams, the potential is practical: support people working on production floors or in the field without separating them from the physical task. Realizing that potential, however, depends on more than selecting a headset. Device usability, application content, processing location, and network performance all shape the experience.
How AR and VR differ in industrial settings
Virtual reality (VR) places the user inside a computer-generated three-dimensional environment, typically viewed through a head-mounted display (HMD). The system tracks head movement and updates the displayed view; some experiences also use haptic feedback to simulate touch. This makes VR suited to experiences where the user can work in a virtual setting, such as training or examining a design.
Augmented reality (AR), by contrast, overlays visual or audio information on the user’s view of the physical world. A worker wearing AR glasses might see task instructions while remaining oriented to the equipment in front of them. The distinction is useful when assessing an application: VR replaces the surrounding view with a virtual environment, while AR adds digital information to the real one. Mixed reality generally describes experiences that combine elements of immersive and interactive systems.
Industrial augmented reality use cases
On a production floor, AR can present step-by-step instructions alongside the product or equipment being worked on. The source paper describes an example in which factory workers used AR glasses to follow assembly instructions. It also identifies troubleshooting in the field as a potential application: a technician could share video or images of a problem and communicate with more experienced support staff. These uses aim to make relevant guidance available in context, rather than requiring a worker to rely only on separate documentation or an on-site specialist.
VR has a different role. It can provide a virtual space for training, collaboration, or design review. In settings where people need to interact with a digital environment rather than inspect the physical work in front of them, immersion and tracked movement can be useful. Both approaches can also support customer service processes: the paper notes that VR-based tools could help representatives debug problems remotely and serve as training aids.
These are possible applications, not automatic outcomes. A deployment needs a clear task to support, suitable content, and a device that workers can use effectively. The paper identifies device complexity, cost, content availability, and user experience as adoption challenges. In an industrial environment, the application also needs to fit the work process and the capabilities of its intended users.
Why latency and bandwidth matter
Network performance becomes especially important when an experience depends on interaction or when processing is shared between a headset, an edge system, and the cloud. If a user moves their head or manipulates a virtual object, the system needs to respond quickly enough for the environment to feel coherent. The paper identifies latency above 20 milliseconds as a potential source of noticeable delay and discomfort in VR. It also describes motion-to-photon latency: the interval between a head movement and the corresponding update on the display.
Not every application places the same demands on a network. Pre-recorded 360-degree video can use buffering and content caching, reducing the impact of variable network latency. Interactive tasks are less forgiving. Examples in the paper include controlling remote machinery, multiplayer gaming, and collaborating on a design. When interaction data must travel across a network before the scene can be updated, delay can undermine responsiveness.
Bandwidth is another consideration. The paper describes 10–50 Mbps as a typical range for current interactive AR/VR experiences and notes that next-generation systems may require more than 200 Mbps. Higher throughput can support more demanding media and interaction, but available bandwidth varies across networks and locations. Engineers planning a deployment should therefore assess the complete path between the application, processing resources, and user device—not just the connection at one point in the system.
Edge computing and network planning
One way to address latency is to place processing closer to the user. Multi-access edge computing (MEC) brings cloud-computing capabilities and services to the network edge. Rather than sending every processing task to a distant data center, an application can use nearby resources where the architecture allows. This may reduce the distance data travels and help manage network congestion, although the appropriate design depends on the application and endpoint locations.
5G and network slicing are also identified as parts of the developing infrastructure toolkit. Network slicing allows logical networks for different services to share physical infrastructure. For a latency-sensitive application, it may provide a way to manage service requirements across that infrastructure. These technologies should be viewed as options to evaluate, not as substitutes for understanding the application’s actual performance needs.
Processing can also be divided among the headset, edge, and cloud. The paper anticipates that AR/VR systems will combine local processing with cloud capabilities, with some workloads moving closer to the edge. For system integrators and operations teams, that makes end-to-end design important: the device, application, network, and compute platform need to work together.
Practical considerations for automation teams
- Start with the work task. Define whether the need is in-context guidance, remote troubleshooting, immersive training, or another use case before choosing AR or VR.
- Test interaction and response. Determine which actions must feel immediate and how network delay affects the task.
- Plan for device and content fit. A capable headset is only useful if its form factor and the application suit the users and environment.
- Review the full delivery path. Consider where rendering and other processing occur, and whether edge resources could help meet latency needs.
- Build organizational expertise. The paper recommends developing immersive-media knowledge and improving workflows through iterative experience.
Conclusion
Industrial augmented reality and VR offer different ways to connect digital information with work: AR overlays guidance on the physical environment, while VR immerses users in a virtual one. Their value depends on matching the technology to a real task and delivering a usable experience. For automation teams, that means evaluating devices, content, bandwidth, latency, and processing location together. Edge computing, 5G, and network slicing may contribute to future deployments, but careful end-to-end planning remains essential.