Commands and state
Distinguish SRC control, RDS orchestration and RoboShop configuration.
TRUSTED FACTORYFLOW
SEER Robotics / FactoryFlow
Logistics fleets based on SRC controllers. SRC / RDS.
Applications and control boundaries
Logistics fleets based on SRC controllers
With RDS, RDS owns traffic/charging; RoboShop is a configuration tool. Never allow independent dual dispatch.
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.
Objects exchanged with FactoryFlow
| Component | Scope |
|---|---|
| Referenced interface | SRC / RDS |
| Related modules | WCS / Fleet Adapter / Traffic Governance |
| Work mapping | execution + map/point reference → RDS task; robot/task state → WCS |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Engineering distinctions that matter
Execution conditions
Map executions to RDS tasks with map/point revisions; RDS owns traffic and charging.
Recovery and reconciliation
On point/map changes hold dispatch and reconcile RDS tasks; prevent dual independent dispatch.
Accept the configuration actually installed
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. |
Vendor technical documentation
Interface documentation does not establish FactoryFlow acceptance of every model or option.
Connect SEER Robotics to existing work.
Bring equipment records and the use case to discovery to agree profiles and tests.