Deploying a robot is a workflow project, not a plug-and-play purchase. Start by mapping routes, doors, connectivity, traffic patterns, access rules and the tasks that staff will keep owning.
Any building or third-party system interface should be treated as a separate, site-specific workstream. Technical access, responsibilities and acceptance tests need to be confirmed before it is included in scope.
A useful pilot has agreed routes, supervision, exception handling and measurable success criteria. Its duration and expansion decision should follow the evidence from that site rather than a fixed public promise.