Commands and state
Select iWMS or FactoryFlow WMS as stock master before robot mapping.
TRUSTED FACTORYFLOW
Robotic warehouses, transport and replenishment. RCS / iWMS.
Choose FactoryFlow WMS or iWMS as stock master per project. RCS owns robots/traffic; robot callbacks cannot directly update stock.
FactoryFlow links business work to the vendor system through a selected adapter/profile. Vendor interfaces below are technical references; deployment scope is configuration-specific, not implied by the brand name.
| Component | Scope |
|---|---|
| Referenced interface | RCS / iWMS |
| Related modules | WMS Integration / WCS / Fleet Adapter |
| Work mapping | warehouse demand → RCS mission; mission/container state → reconciliation |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Select iWMS or FactoryFlow WMS as stock master before robot mapping.
Map containers, stations and RCS missions to executions; RCS owns robot traffic.
Robot callbacks cannot post stock: validate handover then report to the selected WMS; test duplicates.
The configuration record identifies model/controller, firmware, options, authentication, adapter build and state mapping. Test the target equipment, including disconnects and unresolved outcomes.
| Test | Evidence to reconcile |
|---|---|
| Command acceptance | Task/execution links to a vendor ID; ACK and completion remain distinct. |
| Redelivery and reconnect | Query existing work before recreation; retain identities and exception decisions. |
| Handover / completion | Verify scans/handshakes and outcomes at the owning system, not robot state alone. |
Interface documentation does not establish FactoryFlow acceptance of every model or option.
Bring equipment records and the use case to discovery to agree profiles and tests.