Preparing the published article.
Project Governance for Multi-Site Robot Rollouts
One cell is a project; ten cells is a programme.
What changes at scale
| Area | Single cell | Multi-site programme |
|---|---|---|
| Standard | Whatever works here | One frozen design with parameters |
| Spares | Local decisions | Shared pool with agreed stock levels |
| Training | On-the-job | Standard curriculum and assessment |
| Data | Local logs | Common counters and dashboards |
| Support | Call the integrator | Internal first line, then escalation |
Governance that actually helps
- A single design authority who can approve or reject deviations.
- A stage gate after each site: what was learned, what is frozen, what changes.
- A published deviation process — otherwise every site quietly redesigns.
- A named owner per site, not per department.