ARIA is the software platform by IOMA, an IT/OT industrial integrator based in Turin

ARIA/AMR
ARIA AMR · Use cases

A day with ARIA AMR.

Concrete scenarios with real personas. No generic storytelling — these are the steps you see on the line when ARIA AMR is in production.

Scenarios2 scenarios
Persona

Giulia

Shift lead · assembly department

The department runs four AMRs and no other ARIA module. Giulia uses ARIA AMR to keep the stations supplied and clear the end of line without sending a forklift driver back and forth.

Declared typical scenario: it describes how the module is used, not a project already delivered.

  • 06:00

    Opens the operational map

    → She sees where the robots are, how much battery they have, and whether the fleet manager responds, before the first request comes in.

  • 07:30

    Launches line feeding with a routine transport

    → The route from the supermarket to the station is already configured: one click, and the fleet manager assigns the free robot.

  • 10:10

    A robot has stopped in front of a station

    → The diagnosis says why — battery below threshold, load not verified, or blocked area — and suggests the recovery, instead of a phone call to the vendor.

  • 13:50

    Closes the shift with the summary

    → Missions completed, cancelled, and rejected, median time, and per-robot utilization: she exports it to Excel for the production meeting.

Persona

Paolo

Logistics manager · warehouse and lines

ARIA Warehouse runs the warehouse and ARIA MES/SCADA runs the lines. The robots are the bridge: material reaches where production asks for it, and the end of line clears without anyone having to notice.

Declared typical scenario: it describes how the module is used, not a project already delivered.

  • 06:15

    Opens the queued missions

    → Warehouse moves and line requests arrive as fleet missions: nobody retypes them by hand in the fleet manager.

  • 09:00

    The line asks for end-of-line unloading

    → When the container is full, the line event read by ARIA MES/SCADA creates the mission to the warehouse.

  • 11:30

    Changes a mission's destination

    → A bay is taken by an unplanned load: he redirects the robot from the mission table, without cancelling and starting over.

  • 15:45

    Checks stock at the end of the shift

    → With ARIA Warehouse the completed transfer is written to the warehouse: stock follows the load instead of chasing it.

Questions · scope · cost

Let's talk about your scenario.

Bring us your case: who uses it, which stations it touches, which KPIs count. We discuss it with the team that commissions the plants.