An automated cell URS is fundamentally a line-by-line list of testable requirements that links each business driver to a measurable acceptance criterion, with a controlled revision history [S2][S3].
Cell scope typically covers the robot or motion platform, end-of-arm tooling, fixtures, conveyors or AGV handoff, the PLC or robot controller, safety I/O, and the supervisory SCADA or MES interface, and each block needs its own requirement lines [S3].
Start with the business case before any number
The URS exists for two reasons: investment protection and compliance, and the business rationale must lead the document before any regulatory wrapper is added [S4]. Investment protection means specifying the right tool for the right job so the cell does not become a multi-year liability; compliance then becomes a natural by-product of having a controlled, approved document. The recommendation in the chromatography URS literature is to write the financial and throughput justification first, then layer the quality controls on top, because a URS written only for auditors tends to be ignored by operations and never updated in the field [S4].
For an automated cell, the business case normally fixes three numbers up front: target parts per shift, target first-pass yield, and target payback in months, and every requirement below them must trace back to one of these three drivers [S2].
The single-thought, verifiable rule
Each URS line should express one clear thought and be checkable as pass or fail, which is the rule that separates a real specification from a brochure pasted into a Word file [S2]. A line such as "the cell shall achieve 120 assemblies per 480-minute shift at 99.5 percent first-pass yield" is testable; "the cell shall be high-speed and reliable" is not, and the second form is what suppliers ignore when disputes arise. Line numbering such as URS-0142, plus a unique title, owner, and verification method, is the minimum metadata that makes the line auditable [S3].
A practical verification column typically uses four methods: I = inspection, T = test, A = analysis, D = demonstration, and the same cell can carry different methods on different lines, for example "T" on cycle time, "D" on changeover under 10 minutes, "A" on MTBF [S3].
Required section structure for a cell URS
A working cell URS organises the requirements into eight sections, and skipping any of them creates the failure modes that suppliers exploit during disputes [S2][S3].
1. Scope, exclusions, and cell boundaries, with a one-line definition of what is inside the cell envelope and what stays on the upstream or downstream line.
2. Product and process data, including the part family, mass range, tolerance stack, and the variants that must run without retooling.
3. Throughput and cycle time, with the takt, the slowest station time, and the recovery time after a fault.
4. Equipment and component requirements, naming the robot reach and payload, controller family, force gauge range for any press-fit or torque verification, and IP rating for the cabinet.
5. Interfaces and controls, covering fieldbus, safety bus, and the MES or SCADA hand-off protocol.
6. Quality and inspection, listing the sensors used for in-process checks and their accuracy class.
7. Safety and ergonomics, referencing ISO 12100 risk assessment and ISO 10218 for robot cells.
8. Lifecycle, including mean time between failures target, spare-parts commitment, and documentation deliverables.
Throughput, changeover, and OEE in numeric terms
Throughput belongs as a numeric line, not a paragraph: parts per minute, station takt in seconds, and the acceptable recovery time after a stop, all with tolerances [S2]. Changeover time for a mixed-model cell is normally called out as a separate line, because the cell that runs one SKU fast but takes 90 minutes to switch is rarely the cell that was bought. Overall equipment effectiveness is typically split into availability, performance, and quality, with each axis given its own number, and URS language that only says "high OEE" is a known red flag during supplier negotiation [S3][S4].
Common cycle-time windows for discrete-assembly cells in 2026 quoting rounds run 4–12 seconds per station, with full changeover on a five-variant family targeted at 10–20 minutes and an availability floor of 90 percent, but these numbers must come from your own line balance rather than industry folklore.
Comparison: URS by writing style
The way each requirement is phrased changes the legal and operational weight of the document, and the four styles below cover most of what reviewers will see in 2026 cell procurements.
Directive ("shall") versus descriptive ("should"): the supplier is bound only by "shall", and 100 percent of functional requirements should use it, while "should" is reserved for nice-to-haves and future options [S2].
Closed metric ("cycle time less than or equal to 6.0 s at 95 percent confidence") versus open adjective ("fast cycle time"): the closed form survives a Factory Acceptance Test dispute, the open form does not [S3].
Traceable ("per ISO 9283 positioning repeatability of ±0.05 mm") versus branded ("ABB-grade accuracy"): the standard reference is the only one an auditor will accept.
Lifecycle-anchored ("MTBF 8 000 h, MTTR 30 min") versus generic ("high reliability"): the first form drives spare-parts and service contract terms, the second form does not [S4].
Common failure modes the URS must close
The same URS gaps show up on almost every failed automated-cell project, and each is cheap to close in the writing stage and expensive to close after delivery [S2][S4].
No URS at all, with the supplier quoting from a standard datasheet, is the leading root cause of post-installation disappointment, and the URS is also the document that protects the buyer's negotiation leverage if delivery slips [S4].
Copy-paste from a prior project leaves the old cycle time, the old part number, and the old controller family in place, so version control with a revision table and a change log is mandatory [S3].
Conflating instrument and software requirements creates audit findings when the cell uses a load cell for press-fit monitoring, because the metrology accuracy, calibration interval, and the data-handling software each need their own URS lines, and they cannot be merged into one [S4].
Skipping the URS-to-design traceability matrix lets "shall" statements disappear between procurement and detailed engineering, which is why each URS line should map to at least one design-output document and one verification record [S3].
Sign-off, traceability, and the role of the cell URS in risk assessment
The URS is closed when operations, quality, safety, and finance have all signed against a controlled revision, and a controlled URS is the prerequisite input to the ISO 12100 risk-assessment step that any new cell has to clear before the safety circuit is wired [S3]. A practical tool for cell scope design and reach studies is a digital twin built directly from the URS, because the URS carries the cycle-time, payload, and reach numbers that the simulation must hit to be valid.
Once the URS is signed, every change request after that point should run through a formal change-control gate with cost and schedule impact, because uncontrolled URS edits during build are the single most common reason a cell ships late and over budget [S2].
Track two signals on the next review: the ratio of "shall" lines to "should" lines, which should sit above 4:1 for a production cell, and the percentage of URS lines with a defined verification method, which should be 100 percent before the document goes to bidders.