Robot cycle time is not machine-tending output

What decision should cycle evidence support?

A robot motion time can help compare one programmed movement. It does not establish the net output of a machine-tending cell. Production depends on the complete operating loop: part presentation, robot handling, machine availability, door and chuck or fixture actions, processing, inspection, rejection, replenishment, interruptions and recovery.

The buyer decision is therefore not whether the robot is fast. It is whether the configured cell can produce accepted parts at the required demand rate under the agreed part mix and operating conditions, while preserving safe access and a workable recovery path.

Why does the complete state history matter?

The OPC Foundation's current Machine Tools information model separates production states such as initializing, running, interrupted, ended and aborted. Its runtime model records starts, ends, interruptions and abortions, and its time-based KPI guidance explains that useful time measures can require the duration of multiple states rather than one headline value.

That distinction is practical for tending. A short robot move does not recover time lost while the machine is unavailable, a part is mispresented, quality approval is pending, a program is being changed or an operator is restoring the cell. Record those states separately so the proposed solution is not credited for time it cannot control.

What should the baseline contain?

Use the baseline to identify the actual constraint. If machine processing dominates and the operator already tends several machines, faster handling may not materially change output. If handling blocks the machine or creates variable idle time, a tending solution may have a clearer production hypothesis.

• Required good parts by product or part family during the real demand window.
• Observed machine processing time and its distribution, not only a nominal recipe value.
• Manual load, unload, cleaning, gauging, deburring and quality-disposition time.
• Setup, program, gripper, fixture and verification time for each representative changeover.
• Waiting caused by upstream presentation, downstream capacity, quality release or missing material.
• Fault, interruption and recovery categories, including who responds and how production restarts.
• Rejected or damaged parts and the point at which their disposition becomes known.

How should a provider's cycle claim be assessed?

Ask the provider to state the exact configuration and scope behind the claim: robot and software version, tool, part, presentation method, path, speeds, machine interface, inspection steps, safeguards and exclusions. Separate simulated time, dry-cycle time, a demonstrated best case and an observed production distribution.

NIST's manufacturing-robot agility work is useful here because it treats efficiency and effectiveness under changing conditions as measurable system properties. That research does not certify a tending application, but it supports testing the system against the variation and anomalies that matter to the buyer rather than relying on one ideal cycle.

What should a representative pilot measure?

The pilot should preserve raw state and event evidence where the interfaces allow it. OPC UA production and interruption states can provide a common structure, but the responsible machine builder, integrator, safety duty holders and operator still need to agree which signals are authoritative and how they may be used.

• Good parts completed during a named operating window and demand condition.
• Complete loop time from ready-for-load through accepted output, reported as a distribution.
• Machine waiting, robot waiting, blocked, interrupted and aborted time by reason.
• Interventions, recovery time, restart authority and any manual work retained.
• Changeover time across the agreed part family, including verification before release.
• Quality escapes, rejected parts, damage and the evidence used for disposition.
• The tested configuration, conditions, exclusions and a pre-agreed proceed, revise or stop rule.

The practical next step

Bring RobotAtom one machine-tending problem with the machine, part family, demand window and current operating loop. We can structure the requirements, expose the likely constraint, compare suitable solution approaches and providers, and define a bounded pilot with measurable acceptance conditions.

RobotAtom leads the solution process but does not certify machine safety, production capability or compliance. Manufacturers, integrators and accountable site specialists remain responsible for their claims, designs and approved scope.