AGV and AMR technology explained through process, safety and ROI

In practice this means several layers work together at the same time: the vehicle, localization, traffic control and task logic. The trip itself is only the final result of earlier decisions about orchestration, route planning and reaction to events in the environment.

A good rollout is not about launching a single robot. It is about building a stable operating model. That is why we analyse not only the route, but also pick-up and drop-off points, priority rules, human interaction and the conditions under which the system must stay predictable when the load grows.

Automating internal transport with AGV trucks and autonomous mobile robots AMR is a major step towards higher logistics and manufacturing efficiency. For people and machines to work together safely, however, the whole system has to be built on rigorous and modern standards. The most important one is ISO 3691-4, which replaced the older EN 1525 approach and defines safety requirements for driverless industrial trucks and their systems in a much more precise way.

The standard is built around several core pillars. The first is a comprehensive risk assessment aligned with ISO 12100 and carried out for the specific plant and the specific process. This includes collision points, floor conditions, visibility, personnel presence and realistic traffic scenarios. The outcome of that analysis determines which preventive measures must be designed into the project before the system is allowed to operate.

The second pillar is work-zone management. ISO 3691-4 distinguishes the operating zone, operating hazard zone, restricted zone, confined zone and load transfer area. In practice this means different requirements for clearances, speed limits, signalling and the way each area is protected. Defining those zones correctly allows the rollout team to protect people without sacrificing throughput across the facility.

The third pillar is the reliability of the safety functions themselves. In line with ISO 13849-1, critical functions such as braking, personnel detection and speed monitoring usually need to achieve Performance Level d. In practice this requires redundant safety architectures in which a single component failure does not result in the loss of the protective function or a sudden increase in risk for operators and nearby staff.

ISO 3691-4 also makes it clear that safety is a shared responsibility. The OEM is responsible for delivering a safe machine in its factory state. The system integrator is responsible for implementing that machine safely in the real customer environment, including maps, scanner fields, speed reductions and interaction logic. The end user is responsible for safe day-to-day operation, keeping transport paths clear, training employees and carrying out regular audits and inspections.

In practical terms, investing in a system that complies with ISO 3691-4 means greater reliability, better protection of employee health and a more stable logistics operation around the clock. It is a standard that structures the project from the technical, legal and operational side at the same time, and it shortens the path to a safe rollout in a real industrial environment.

In warehouses and plants, the vehicle should react to upstream data: task status, station readiness, carrier ID, pick confirmation or process block. That is why we treat integrations as part of the rollout logic rather than a technical add-on after the fleet goes live.

We work with both lighter event exchange scenarios and deeper WMS, MES, ERP or SCADA connections. The goal is data consistency and clear responsibility: the upstream system knows when to trigger transport, and the AGV layer knows how to execute it safely and efficiently.

The more vehicles and process points you have, the more important central orchestration becomes. It decides which robot should execute which task, how to avoid congestion, when to pause traffic and how to keep throughput stable with changing production or warehouse priorities.

A good fleet management system also creates transparency. The team sees task queues, vehicle statuses, fleet utilization and the process points where losses appear. That means it can support both live control and continuous optimization.

In many plants the first business effect does not come from automating the whole site. It comes from taking over one critical repetitive process. That is where it is easiest to calculate labour savings, supply reliability and the reduction of transport chaos.

That is why we build ROI models on operating data: number of trips, shift rhythm, cycle time, labour cost, buffer logic and throughput impact. This gives a decision model based on the process, not just on a technology promise.