Skip to main content

Can We Add Capabilities or Expand After Deployment?

How deployments can grow and adapt after go-live

Yes — operations can evolve after deployment

Your facility isn't static. Shelf layouts change. Patrol routes get adjusted. Volume grows. We account for this in how we build and maintain deployments.

Expanding the robot's operating zone

If you expand your warehouse or add a new section to the patrol area, we update the facility simulation to include the new space and retrain the robot for the expanded environment. The original facility model is preserved as the baseline — we extend it rather than start from scratch.

Adding new tasks or workflows

If you want the robot to take on additional tasks it wasn't originally deployed for — for example, a warehouse robot that starts doing shelf scanning in addition to transport — that requires a training update. The feasibility and scope of the update depends on the hardware's physical capabilities and the complexity of the new task. We'll assess it and scope it as a change request.

Additional units

If you want to scale up the number of robots at a facility, adding units is faster than the initial deployment because the facility simulation already exists. New units are trained in the existing simulation environment and deployed.

What requires a formal change request vs. what's routine

Minor patrol route adjustments and configuration changes are routine and handled as part of post-deployment support. Significant capability additions, facility expansions, or additional hardware are scoped and quoted as change requests.

Did this answer your question?