Commands and state
Choose Cloud API or robot-side SDK and identify WAN-dependent paths.
TRUSTED FACTORYFLOW
Internal transport, replenishment and delivery points. Cloud API / robot-side SDK.
Select Cloud API or robot-side SDK; do not assume open ROS. WAN loss requires offline policy and task reconciliation before resend.
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 | Cloud API / robot-side SDK |
| Related modules | WCS / Fleet Adapter / Edge |
| Work mapping | pickup/drop-off + execution → task/mission; status/alarm → WCS |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Choose Cloud API or robot-side SDK and identify WAN-dependent paths.
Map execution pickup/drop-off to vendor tasks and retain task IDs for late callbacks.
On WAN loss check local policy and query existing tasks before recreation; do not assume open ROS.
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.