External System Integration
This page covers connecting the J1600 to systems outside the robot: warehouse management systems (WMS), fleet layers, site software, and other equipment. It is for teams deciding whether, when, and how to integrate.
Integration is a choice, not a requirement
The J1600's basic workflow — map by driving, save locations, launch tasks from the touchscreen — requires no WMS, no fleet manager, no Wi-Fi, and no IT project. Optional rather than mandatory systems integration is a core design principle: a deployment can stay standalone for its entire life, or scale into a connected system when the application grows.
This matters for cost. Full automation of a pallet flow typically requires WMS-to-fleet-manager integration, precise load data, and tightly controlled processes. Keeping the operator in the loop lets the J1600 skip that layer for most deployments. See human-in-the-loop automation.
Available integration routes
| Route | Use it for | Requires |
|---|---|---|
| VDA 5050 | Fleet coordination, including multi-vendor fleets under one compatible fleet layer | Advanced software |
| REST API | Direct integration with other software and equipment | Advanced software |
| Fleet Manager | Orchestrated multi-J1600 deployments and advanced mission planning | Per-robot license |
The Advanced software upgrade (€14,500 end-user list) covers VDA 5050, the REST API, advanced mission planning, and advanced system integration with other software and equipment. It is easiest to install at the factory with the robot order; a partner can retrofit it, and customers cannot install it themselves.
Who performs the integration
Integration with other software and equipment is offered as an add-on to the five-day installation and commissioning package (€10,000 end-user list), which also handles feasibility, drop points, task and safety validation, training, and acceptance testing. On-site engineering support lists at €2,400 per day plus travel. Partners and The Mobile Robot Company deliver this work; contact your partner or hello@mobilerobot.com to scope a project.
Typical scaling sequence
- Standalone start. One robot, Standard software, teach-and-repeat tasks. Value from day one, no integration.
- Connected functions. Add Wi-Fi to use come-to-me (calling the robot from a mobile app or web interface) and automatic charging.
- Fleet and systems. Upgrade to Advanced software for VDA 5050, the REST API, and Fleet Manager when several robots or external systems enter the picture.
For concrete task patterns at each stage, see example workflows.