Requirements, Architecture Options & Concept Review

Turn the brief into a verification cross-reference matrix:

Include mechanical, electrical, control, data, safety, human, operational, maintenance, cybersecurity, environmental, and decommissioning requirements.

Generate architectures

Develop at least three: simple fixture/assist, dedicated mechanism, and flexible mechatronic or robotic system. Sketch functional blocks, material flow, information flow, energy, people, service, safety boundary, and responsibility.

Use calculations only precise enough for the decision: payload/reach, torque, cycle budget, sensor feasibility, footprint, throughput, energy, safety concept, and cost range. The goal is to retire fatal flaws before detailed CAD.

Review with evidence

Present requirement coverage, decision matrix, sensitivity, top risks, unknowns, experiments, lifecycle cost range, worker feedback, and reasons alternatives were rejected. Invite challenge at interfaces: part-to-fixture, sensor-to-controller, controller-to-drive, robot-to-PLC, cell-to-operator, maintenance-to-energy control.

Gate 2

Pass only if the selected architecture covers critical requirements, no unresolved hazard makes the concept untenable, economics remains plausible under downside assumptions, and a feasible experiment exists for every high-risk unknown. NIST’s focus on performance requirements and test methods is the model: capability must be stated so another person can verify it ¹.