Frequently asked questions about ARIA Warehouse.

Yes. ARIA Warehouse shares its master data with SCADA but is standalone: it can be deployed as a WMS alone, integrated with an existing MES via real-time or REST APIs.

Yes, multi-warehouse is native. Every user has an active context and can switch from the topbar. Tables and forms refocus on the current warehouse's data. Per-warehouse permissions.

Integration happens on the vendor fleet manager's standard interface, through a dedicated service: the reference adapter is validated against KUKA.AMR Fleet. Factory logic is kept separate from each vendor's dialect, so adding a vendor means writing a new adapter, not redoing the integration. The AMR path never touches the PLCs: it's a channel of its own.

The vendor's fleet manager stays in charge of the robots — navigation, traffic control, and picking the idle unit are its job. ARIA Warehouse is the layer above: it decides what moves and to which location based on orders, quality, and stock, and follows the mission through to its outcome.

Yes, and it's optional. On mission completion the transfer can be written into the warehouse automatically, so stock follows the physical move instead of chasing it. It's enabled in stages: you start in observation only — the system logs what it would have written — and switch it on once the logs convince you.

Yes, through automations. A production or quality event — a lot rejected by inspection, for instance — can start the transfer mission with no human in the loop. Every automation starts disarmed and in observation only; a real dispatch requires arming it explicitly plus a dedicated fleet-command permission.

Yes. Every movement is logged: batch, quantity, source and target location, operator, timestamp. Integrated with SCADA's genealogy: from raw material to finished part, one single timeline.

CSV, JSON, and PDF (standardized printouts). For continuous integration with audit tools, a dedicated real-time channel is available.