Humanoids & Robotics · Source published 27 June 2024
Research signal
The June 2024 GXO–Agility announcement used a Robots-as-a-Service arrangement. A service model changes the commercial relationship, but workplace responsibilities still need explicit allocation.
Source: GXO and Agility Robotics — deployment agreement · 27 June 2024.
Event Systematic perspective
Our editorial recommendation is to start with an operational responsibility map before negotiating a headline price. Who starts a shift, responds to a stopped task, approves a software change and restores ordinary operations? A recurring fee is difficult to assess without understanding the labour and support it requires from the customer.
For HR and procurement, the useful comparison is cost per accepted unit of work at an agreed service level. Include supervision, training, integration, downtime and the consequences of missed output. Avoid equating a quoted robot rate with a complete employee cost: the resources and responsibilities being purchased are different.
Put it into practice
- Document the boundary between vendor support and on-site operational supervision.
- Agree how incidents, service interruptions and software changes will be communicated to affected workers.
- Retain a workable fallback process so a trial does not leave the team unable to complete essential work.
Explore employer services, career development and the AI Academy. Discuss your workforce priorities with Event Systematic →
