Specifying a Robotics Deployment
The document that decides whether a deployment succeeds is written before anyone quotes for it. Covers requirements, integrator selection, acceptance testing, and the clauses people wish they had insisted on.
Runs most often inManufacturing and industrialsLogistics and supply chain
What participants can do afterwards
- Write a specification in terms of your process rather than a product
- Evaluate integrators on the questions they ask you
- Define acceptance criteria you can actually test on the day
- Plan for the throughput you have at peak, not on average
- Sign a contract that still protects you in year two
Modules
4 modules, 8 facilitated hours.
1.Specifying the process
2.5 hrsDescribing what must happen rather than what to buy.
- Write a process-led specification
2.Choosing an integrator
2 hrsJudging a partner by the questions they ask you.
- Evaluate an integrator properly
3.Acceptance
2.5 hrsCriteria you can test on the day, at peak rather than average.
- Define testable acceptance criteria
4.The contract clauses that matter later
1 hrsSupport, spares, response times and software escrow: the clauses whose absence is only discovered in year two.
- Insist on the clauses whose absence hurts in year two
How it is delivered
A facilitator runs the course live, in person or live online. Attendance is taken per session, participants submit work against the modules above, and a facilitator grades it. Those records stay with the organisation and can be exported.
Further reading
Robotics training is an operations problem, not an engineering one is the public briefing that sits next to this course.
