AMR & intralogistics

An AMR fleet isn't there to move crates. It's there to keep the line running.

Many plants already have the mobile robots. What's missing is the system that decides what moves, when, and to which station — and that updates stock once the move is done. That's the part we build.

The real problem

Missions launched by hand

An operator opens the fleet manager console and calls a robot. That works until three urgent jobs collide: then priority is set by whoever shouts loudest, not by the production plan.

Stock that lies

Material has physically moved, the system doesn't know. What follows is the drift between what the software says and what's actually on the rack — and the time lost hunting for it.

Two worlds that don't talk

AMR fleet on one side, WMS and MES on the other, with a spreadsheet or a person in between. Every missing integration becomes a line stop when material shows up late.

How we connect the fleet

Mission dispatch

The mission starts from the system that knows the production order, not from the console. With priority, cancellation, and resuming of paused flows.

Lift · roller · CTU · forklift · priority

Continuous telemetry

One view to tell whether the fleet is keeping up with the line or has become the bottleneck.

Robot status · battery · node and position · alarms

Location ↔ node mapping

Warehouse locations get bound to the fleet manager's map nodes. It's the tedious, indispensable work: without that binding no automation is trustworthy.

Locations ↔ nodes · areas · workstations

Stock updated by the move

On mission completion the transfer is written into the warehouse: stock follows the physical move instead of chasing it. You start in observation and switch it on once you trust it.

Transfers · observation only · staged rollout

Topology and forbidden areas

Forbidden areas can be read and toggled from the system, to handle site works or zones under maintenance without touching the console.

Areas · workstations · charging · queues · rollers · elevators

Vendor independence

Factory logic sits on top, each fleet manager's dialect sits in an adapter underneath: changing or adding a vendor is a new adapter, not a new project.

Per-vendor adapter · factory logic kept separate

Missions that start themselves

Quality reject → quarantine

Quality control rejects a lot: the mission to the quarantine area starts without anyone asking for it, and stock is updated accordingly.

Line feeding on order

The order enters execution and material moves toward the station that will consume it, with the lead time the plan decides — not the one the operator remembers.

Safety first

A mission moves real mass among people. Automations run only when explicitly armed, with dedicated permissions for fleet command and every dispatch traced.

How it's commanded today

The fleet is commanded from the warehouse; the automations are written from the line.

AMR mission dispatch — lift, roller, CTU, forklift — lives in ARIA Warehouse, the platform's WMS. AMR automations triggered by a line event are authored from ARIA MES/SCADA.

Direct station-to-station movement from the supervision dashboard is still in development: if your project needs it, let's talk.

What we bring on site

On-site analysis

We walk the material flow before writing a line of code: where the stop originates, how many trips are genuinely needed, which locations matter. Most AMR projects fail here, not in software.

Flow map · trips needed · critical locations

Fleets and automated warehouses

Experience across AMR fleets from several vendors and with vertical automated warehouses: the fleet joins the same supervision as the line.

KUKA.AMR Fleet (validated) · vertical warehouses · multi-vendor

Integration with your systems

The systems you already run connect through secure APIs and webhooks. We don't replace what works: we connect what doesn't talk.

WMS · MES · ERP · secure APIs · webhooks

Commissioning and support

From fleet-manager connection to acceptance testing with real missions, with operator training and continuous support after go-live.

Fleet connection · mapping · acceptance · training

AutomotiveE-MobilityPackagingManufacturingFood & Beverage

Want to see how it fits the rest of the factory? See the portfolio — every case starts at the field and reaches the decision, warehouse included.

Frequently asked questions

Do we really need AMRs, or is a cart and an operator enough?

It depends on how repetitive the route is and how much the time a person spends on it is worth. A fixed, frequent route with no decisions to make is the natural candidate; a route that changes every time and needs judgement often isn't. The useful question isn't «how many AMRs» but which movements today take hours from someone without adding anything to the product.

Do AMRs integrate with the WMS and MES we already run?

That is precisely the point of the integration: the fleet has to know what the line needs and when, and the warehouse system has to know what was actually moved. The link runs from the vendor's fleet manager to the management layer, with shared master data. If they stay two separate systems, you go back to reconciling by hand what the AMRs did.

Can we start with a few missions and expand later?

Yes, and it's usually the right route: start with the most repetitive journeys, measure the real result, then extend. What is worth getting right immediately is the level of integration: how missions are generated and how movements return into the management system. That's the part that costs to redo, not the number of vehicles.

Who decides priority when two lines request replenishment at once?

Mission dispatch. It's what separates an integrated fleet from a set of vehicles: priority should come from real production demand — what is about to stop — not from the order requests arrived in. Worth defining during analysis, because it becomes the rule that governs the plant's daily behaviour.

What happens if an AMR fails or the fleet stops?

The flow has to be able to continue manually: missions stay visible and assignable to an operator, and stock keeps updating from physical movement. A plant where a fleet outage also blocks material traceability is badly designed, regardless of how reliable the vehicles are.

Do you also handle safety and coexistence with people?

Yes, and it's part of the project rather than a later formality: routes, shared work areas, handover points with operators, and risk assessment. An AMR is a machine moving among people: that coexistence is designed with the same rules used for cell safety.
Let's talk

Got a project in mind?

Describe the line and the problem on a 30-minute technical call: we tell you straight away whether it's in our wheelhouse. We typically reply within 24 hours. From the first call to commissioning, you speak to the same person.

Let's talk about your project

Or:explore the ARIA platformhey@ioma.ai