Mobile robots in logistics: starting from flows and integrations
How to study internal transport, missions, exceptions and connections with management systems before evaluating a fleet of mobile robots.
An autonomous mobile robot, often referred to as AMR, can be used to transport materials within a factory. To understand whether it makes sense in a certain context, however, it is necessary to observe the complete logistical flow. Travelling along an aisle is only part of the job: someone requests transportation, the cargo must be ready, and the destination must be able to receive it.
Mobile robotics is among the themes that EL-AI intends to explore. This article offers an analysis guide for warehouse, production and information systems managers. It does not describe an existing EL-AI fleet and does not promise cost reductions: it illustrates how to build a project question that can be tested.
Drawing the journey of the material
Start from a pair of points: origin and destination. Describe what material moves, how it is contained, who authorizes the departure, and what event confirms delivery. Add possible waits: material not ready, workstation busy, request cancelled, container not suitable.
Let's consider a hypothetical example: replenishing an assembly bench with small containers from the warehouse. If the container arrives when the counter is still full, transportation alone does not solve the problem. It is necessary to define a waiting point or a different call logic, together with whoever manages the activity.
Collect real route data
A floor plan is useful, but it must be compared with what happens during the work. Noting intersections, doors, surfaces, space variations and loading areas helps the comparison with the supplier. The distribution of requests over time also matters: a daily average can hide peaks concentrated in a few minutes.
Observe the process at different times without turning the data collection into an ideal demonstration. Record requests, departures, arrivals and reasons for waiting. The objective is to distinguish travel time from other causes of delay, so as not to attribute an improvement to the vehicle which instead depends on the organisation.
Distinguish robots and fleet management
As the number of vehicles increases, the importance of coordination grows. As an example of functionality available on the market, MiR Fleet documents mission assignment, monitoring and traffic management, with interfaces for integration with enterprise systems. These are features of the product of the manufacturer mentioned, not of an EL-AI solution.
When defining the requirements, separate the transport request from its assignment to a vehicle. Clarify what happens when a robot is unavailable and who can reschedule a mission. Charging and maintenance must be included in the operational plan: continuous theoretical availability does not represent a measure of the service actually provided.
Planning information exchange
A useful integration allows you to recognize the same mission in different systems. Identifier, origin, destination, priority and status are a starting point for discussion. You should also agree on how to handle repeated messages, invalid requests and communication breakdowns.
For example, if a management system sends the same request twice after a network problem, the desired behavior cannot remain implicit. The team must decide how to recognize it and verify the response in the test environment. This is an integration question, separate from the robot's navigation functions.
Evaluate the service, not just the speed
- Time between request accepted and delivery completed.
- Missions completed without intervention and reasons for exceptions.
- Waiting time at loading and unloading stations.
- Availability during the agreed operational windows.
- Traceability of deliveries and comprehensibility of statuses for operators.
The criteria and thresholds must be defined on the real case, together with the supplier and site managers. Integration and risk assessment require appropriate skills: this list serves to prepare the comparison, not to configure the safety of a fleet.
An initial test should close with a flowchart, an exception log, and an extension decision. The possible value for EL-AI also lies in the connection between physical movement and digital processes: a direction to be studied with evidence, without confusing strategic interest and commercial availability.
Content prepared with AI assistance; source consulted on 19 September 2026. The examples are hypothetical. Illustrative cover generated with AI.
Illustrative AI-generated cover; it does not depict actual EL-AI people, premises or installations.