Commands and state
Verify controller and RMI option before selecting the interface; RMI is not universal.
TRUSTED FACTORYFLOW
Industrial cells and controller-executed work. Remote Motion Interface (RMI), theo option.
RMI is a published vendor interface, not assumed on every controller. No raw motion authority from the browser.
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 | Remote Motion Interface (RMI), theo option |
| Related modules | Robot Cell / Program Repository / Adapter |
| Work mapping | job intent → selected interface; controller status → reconciliation |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Verify controller and RMI option before selecting the interface; RMI is not universal.
Keep FactoryFlow job intent separate from controller program/mode; no raw browser motion.
Accept mode changes, connection loss and recovery against the actual option, not another vendor template.
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.