Before You Order AMRs — Define Your Zones First (VDA 5050 v3)

Before you sign an order for a fleet of mobile robots, it is worth answering a question that is rarely asked at the purchasing stage: where is this robot allowed to drive, where must it slow down, and where may it not enter at all without permission? This is not an implementation detail but a facility design matter. The new version of the VDA 5050 v3 communication standard moves AMR zones from the level of the individual vehicle to the level of the entire fleet, and this changes the order of work: first you map out the zones, and only then do you order the robots.

What VDA 5050 v3 really changes

VDA 5050 is an open standard for communication between mobile robots and the master fleet control system. Its purpose is simple: it lets you run a fleet made up of vehicles from different manufacturers from a single system, instead of locking the plant into one supplier. Version 3.0 is not a cosmetic update. As The Robot Report describes, the update adds three things that matter to anyone planning a heterogeneous fleet: the zone concept, path sharing and a standardised power-saving mode. At the same time, the standard remains backward compatible with the earlier approach based on defined trajectories and corridors.

The first change is the most important. Previously, a robot was mainly given points and routes to travel. Now the software starts to “think in zones” — it operates with areas of the facility to which traffic rules have been assigned. An autonomous robot can plan its own path between designated points, while the master system takes care of traffic management by exchanging route information between vehicles. For your facility, this means one thing: for the fleet to work, someone has to design these zones and rules first.

Three types of AMR zone to map out before you order

The zone concept in VDA 5050 v3 consists of areas with defined rules governing robot traffic. The standard explicitly lists several types, and each of them corresponds to a real decision you would have to make on the shop floor anyway.

• Restricted-access zones — areas that the robot must not enter, or may enter only under certain conditions. These are places where people work, quality control stations and zones with heavy manual transport.
• One-way routes — areas where traffic runs in one direction only. They separate flows that would otherwise block each other on narrow routes.
• Zones requiring authorisation — areas that the robot may enter only after explicit permission from the control system. Typically doors, airlocks, passages between halls and places where heavy traffic intersects.

Note that these are not robot parameters — they are decisions about how the space is organised. Even the best vehicle will not guess that the zone by the loading dock is one-way or that entry into the assembly buffer requires permission. Someone has to tell it in the configuration, and before that, establish it in the facility design. That is why mapping out the zones is work done before selecting AGV and AMR robots, not after delivery.

Path sharing needs boundaries, including physical ones

Path sharing is a powerful feature: the robot plans its own route between points instead of rigidly following a single line. Flow improves, but so does the number of possible travel paths. If a robot can choose one of several routes, it will appear in several places in the facility in a way that is less predictable for a person standing nearby.

This is where a limitation arises that is easy to forget when buying software: the zone exists in the control system, but people cannot see it. An operator, a warehouse operative or a forklift driver has no access to the fleet interface — they have only what they can see on the floor. If path sharing allows a robot to appear on several routes, each of those routes must also be physically legible. Otherwise you have a situation where the vehicle “knows” where it is going and the people around it are guessing.

That is why the zone in the software and the zone on the shop floor must match to the centimetre. The boundaries of one-way zones and restricted-access areas are marked with floor markings — tapes and markers that turn an abstract rule into a visible line. Where a route crosses pedestrian traffic, or where a zone changes character, markings alone are sometimes too weak, and flexible fencing is used, for example ZonePro mobile barriers, which physically fence off an area and allow the boundary to be moved quickly when the layout changes.

A heterogeneous fleet raises the stakes

The main reason VDA 5050 v3 was created is to scale heterogeneous fleets — running vehicles from different manufacturers from a single system, without dependence on one supplier. This is good news for a plant that wants to expand its fleet in stages and add robots of different types: small transport units, tow tractors, lifting platforms.

There is, however, a consequence. The more vehicle types move around a single facility, the more important it is for the zones to be defined once and respected by all of them. If each supplier had its own, incompatible understanding of routes, you would be back to square one — chaos and lock-in. A common language of zones only works if there is a single, coherent map of traffic rules to which further robots are connected. That map is your facility design, not a feature you buy along with the first vehicle.

Before you send a request for quotation — an AMR zone checklist

The list below helps you set the right order: zones first, robots second. It is worth going through it before talking to a supplier, because these are questions that will be asked at the fleet configuration stage anyway.

• Have you drawn up a map of restricted-access areas — places the robot does not enter, or enters only conditionally?
• Have you designated one-way routes where aisles are too narrow for two-way traffic?
• Have you defined zones requiring authorisation — doors, airlocks, passages between halls?
• With path sharing enabled, are all alternative routes physically legible, not just in the system?
• Do the zone boundaries on the floor match the boundaries in the fleet configuration?
• Is the zone plan independent of the supplier, so that adding a robot from another manufacturer does not require redesigning the whole thing?
• Can the markings and fencing be moved when the layout changes, without breaking up the floor?

If your answer to most of these questions is “not yet”, that is a sign you are starting at the right end. A software-based zone concept works best when it has physical support on the shop floor: the robot must “see” the zone in the system, but people must understand it at first glance. These two layers are designed together, before the order is placed, not after the first incident.

Does VDA 5050 v3 force you to replace your existing fleet?

No. The standard remains backward compatible with the earlier approach based on defined trajectories and corridors, so new features such as the zone concept can be introduced gradually. The key is for the zone map of the facility to be ready and coherent — then further vehicles are connected to the existing rules.

Who should define the zones — the robot supplier or the plant?

The decision on which areas are closed, one-way or require authorisation is made by the plant, because it follows from the organisation of work and flows, not from the vehicle’s parameters. The integrator translates these decisions into the fleet configuration. Ideally, the zone plan is created together with the design of the markings and fencing, so that the version in the software and the version on the floor form a single, coherent solution.

Sources

• The Robot Report, “VDMA version 3.0 of VDA 5050 will help mobile robot fleets scale” — a discussion of the changes in VDA 5050 v3 (zone concept, path sharing, power-saving mode, heterogeneous fleets): therobotreport.com