Robot Payload, Reach, and Cycle Time Shortlist Before RFQ
Robot Payload, Reach, and Cycle Time Shortlist Before RFQ
Section titled “Robot Payload, Reach, and Cycle Time Shortlist Before RFQ”Robot shortlists often start with catalog numbers: payload, reach, repeatability, speed, and price. That seems rational until the first quote cycle exposes the real problem. The selected arm may carry the part, but not the gripper. It may reach the pickup point, but not with a useful wrist orientation. It may meet cycle time in a simulation, but not after guarding, sensing, approach paths, settling time, and recovery behavior are included.
Before asking for quotes, the team should translate the application into a robot-class boundary. That boundary should describe payload with tooling, useful reach, motion envelope, cycle-time budget, product variation, duty expectations, and recovery behavior. Otherwise every integrator will fill in assumptions differently.
Quick answer
Section titled “Quick answer”Shortlist the robot around loaded EOAT payload, usable reach inside the cell, and cell cycle time, not around maximum catalog payload or maximum reach alone. Add margin for gripper weight, cable dress, part variation, acceleration, wrist orientation, tool offset, safety approach paths, and future SKU drift. If the shortlist cannot explain those assumptions, the RFQ is premature.
The goal is not to pick the final robot model before integrator input. The goal is to prevent proposals from solving different problems.
Payload is not just part weight
Section titled “Payload is not just part weight”Nominal payload is one of the easiest numbers to misuse.
The real payload includes:
- the part or package,
- the end-of-arm tool,
- vacuum cups, fingers, clamps, compliance devices, or magnets,
- sensors on the tool,
- brackets and adapters,
- hoses, fittings, and cable dress burden,
- retained product during acceleration,
- and any off-center moment caused by the tool geometry.
A 10 kg part does not automatically belong on a 10 kg robot. If the tool weighs 4 kg, the center of gravity is offset, and acceleration matters, the real application may need a higher payload class.
Payload margin should be explicit
Section titled “Payload margin should be explicit”Use a margin model before RFQ.
| Payload factor | Why it matters |
|---|---|
| EOAT weight | Often consumes more capacity than early estimates assume |
| Part weight variation | Wet, full, boxed, wrapped, or off-spec products may weigh more |
| Center of gravity | Offset loads reduce practical capability |
| Acceleration and deceleration | Faster motion increases mechanical demand |
| Wrist orientation | Some poses are less forgiving than nominal payload charts imply |
| Future SKU drift | The cell may inherit heavier or larger products later |
If the team does not know the EOAT weight yet, the RFQ should say so. Hiding that uncertainty produces false precision.
Reach means useful reach, not maximum radius
Section titled “Reach means useful reach, not maximum radius”Maximum reach is a brochure number. Useful reach is the robot’s ability to hit the required points with the correct tool orientation, clearance, approach path, and recovery access.
Useful reach must include:
- pickup position,
- drop position,
- approach and retract distance,
- clearance around guarding, conveyors, machines, racks, and fixtures,
- wrist orientation at the task point,
- tool length and offset,
- safe home position,
- recovery positions,
- and maintenance access.
A robot may technically reach a point but still be a poor fit if it reaches it near the edge of its envelope, with awkward posture, poor speed, limited clearance, or fragile cable routing.
Cycle time is a cell property
Section titled “Cycle time is a cell property”Robot motion time is only one part of cycle time.
Cell cycle time includes:
- product detection or ready signal,
- robot approach,
- grip or pickup confirmation,
- motion to transfer,
- placement or release,
- settling time,
- outfeed confirmation,
- return or next approach,
- tool vacuum build or clamp response,
- vision or barcode time if used,
- safety-zone interactions,
- and recovery from normal variation.
If a quote promises robot cycle time but ignores infeed, outfeed, sensing, or machine handshakes, it is not answering the production question.
The early shortlist table
Section titled “The early shortlist table”Before RFQ, build a table like this:
| Question | Needed answer before quoting |
|---|---|
| What is the heaviest real item? | Include worst normal product, not only average |
| What is estimated EOAT mass? | Include unknown range if final tool is not designed |
| What is the farthest useful reach point? | Include wrist orientation and tool offset |
| What is the required cell rate? | State parts per minute, cases per hour, or machine takt |
| What variation must the first cell handle? | Define first-phase SKU or part family boundary |
| What recovery actions must be possible? | Define operator, maintenance, and integrator recovery expectations |
| What shift pattern must it survive? | One shift pilot, two-shift production, or lights-out ambition |
This table helps integrators quote the same scope instead of guessing.
How robot class changes with the boundary
Section titled “How robot class changes with the boundary”| Boundary condition | Shortlist effect |
|---|---|
| Low payload, frequent human interaction, modest speed | Cobot may deserve first review |
| Higher payload, faster cycle, guarded cell | Traditional six-axis robot often becomes cleaner |
| Planar motion, compact footprint, high cadence | SCARA may fit if orientation and reach stay simple |
| Long reach, mixed pickup/drop geometry | Articulated robot usually has stronger flexibility |
| Heavy EOAT or offset load | Move up payload class before optimizing price |
| Future SKU growth likely | Avoid a robot that only barely fits today’s best case |
Robot class should follow the cell problem. It should not be chosen because the team likes the category label.
Common RFQ failure modes
Section titled “Common RFQ failure modes”Weak robot RFQs usually contain one of these mistakes:
- part weight but no EOAT estimate;
- max reach point but no tool orientation;
- target throughput but no upstream/downstream timing;
- product list but no first-phase SKU boundary;
- layout sketch but no recovery access;
- safety concept but no operator intervention pattern;
- brand preference but no payload and cycle-time evidence;
- or cycle-time promise without explaining what is included.
Those gaps do not just make quotes inconsistent. They create change orders later.
A stronger pre-RFQ evidence pack
Section titled “A stronger pre-RFQ evidence pack”Give integrators:
- product weights and dimensions;
- worst-normal product examples;
- target cycle rate and shift pattern;
- pickup and drop geometry;
- layout constraints and access constraints;
- current operator method and pain points;
- known variation and defect conditions;
- desired EOAT assumptions or open uncertainty;
- recovery expectations;
- acceptance-test expectations;
- and rollout ambition beyond the first cell.
This does not over-constrain the integrator. It removes ambiguity around the business problem.
Practical shortlist rule
Section titled “Practical shortlist rule”If two robot classes both appear possible, choose the class that reduces total cell risk, not the one with the most attractive catalog number.
That means:
- do not choose a smaller robot if payload margin is fragile;
- do not choose a larger robot if footprint and guarding become the real bottleneck;
- do not choose a cobot if the cell will be guarded and throughput-heavy anyway;
- do not choose SCARA if future reach and orientation flexibility are likely;
- and do not let future flexibility justify a cell that is too expensive for the first repeatable win.
Pre-RFQ checklist
Section titled “Pre-RFQ checklist”- Document true payload including part, EOAT, attachments, and uncertainty.
- Map useful reach points with wrist orientation, tool offset, and clearance.
- Break cell cycle time into robot motion, sensing, gripping, handshakes, and recovery.
- Define first-phase SKU or part family boundary.
- State shift pattern, uptime expectation, and support model.
- Identify where payload, reach, or cycle margin is still unknown.
- Ask integrators to quote around the same assumptions and name exclusions explicitly.