AUBO
Pick/place, machine tending and work cells
View integration profileTRUSTED FACTORYFLOW
Different equipment. A connected operating flow.
Explore robot ecosystems and how FactoryFlow connects business work to Fleet/RCS, robot cells and controllers.
A coordination layer above equipment systems.
Respect interface differences, connect the workflow.
Robot arms, cobots and AMRs have their own controllers, modes and management systems. FactoryFlow links tasks/executions to jobs or missions through deployment-specific adapters/profiles. Work is connected without assuming universal protocols or competing traffic authorities.
The catalogue describes connections confirmed by Mobile-ID. Applicability is assessed by model, firmware, options and profile; a vendor name does not establish acceptance of every product.
The connected equipment ecosystem.
One profile format for 12 vendors. Groups support equipment discovery, not ranking.
Universal Robots
Tending, assembly and collaborative packaging
View integration profileTechman Robot
Vision-assisted cells and programmed operations
View integration profileDOBOT
Compact pick/place, tending and sorting
View integration profileDoosan Robotics
Assembly, tending and collaborative work
View integration profileABB Robotics
Industrial cells, palletizing and PLC handshakes
View integration profileFANUC
Industrial cells and controller-executed work
View integration profileAutoXing
Internal transport, replenishment and delivery points
View integration profileMiR
AMR transport fleets and replenishment
View integration profileOMRON
AMR logistics and fleet management
View integration profileSEER Robotics
Logistics fleets based on SRC controllers
View integration profileHIKROBOT
Robotic warehouses, transport and replenishment
View integration profileTransport and robot cells meet at handover.
Reference coordination scenario, not an accepted multi-vendor deployment claim.
-
01
WMS/MES requests material to the cell with item, lot and source-work identity.
-
02
WCS coordinates transport through the selected fleet/RCS, retaining mission ID and handover gates.
-
03
Confirm material handover and cell readiness; the controller runs the selected program under profile.
-
04
Job/QC results return to source work; transport and production have distinct completion milestones.
Cross-vendor coordination requires designed traffic domains, station handshakes and integration responsibility. Two FactoryFlow profiles do not imply vendor A-to-B compatibility.
Assess the configuration before the integration path.
Identify the vendor system
Record model/controller, firmware, SDK/API and options. Choose fleet or robot-side interfaces and check authentication and operating mode.
Validate meaningful mappings
Bind execution to vendorJobId/missionId and compare native state, timestamps and errors. Assign ownership of ACK-without-completion cases.
Accept through scenarios
Test connection loss, duplicate commands, occupied stations and recovery. Field owners verify interlocks, modes and return-to-service conditions.
Already have equipment on site?
Bring models, firmware, fleet/controller systems and the workflow you need to connect.
Fleets, cells and PLCs coordinate through handovers.
Reference responsibility map separating work orchestration, traffic and field control.