A Run at Rate is a structured production trial used to verify whether a process can sustain the required output under defined operating conditions.

The exact requirements vary by organization, customer, and industry.

The general idea is to test the production system at or near the intended demand rate rather than assuming that equipment nameplate speed proves real capacity.

Define the required rate

The required output should come from actual demand assumptions.

Takt Time provides a useful demand-based reference.

The team should define:

  • required quantity;
  • test duration;
  • product mix;
  • planned staffing;
  • shift conditions;
  • expected quality;
  • planned downtime assumptions.

A short burst at maximum speed is not the same as sustained production capability.

Use normal production conditions

The trial should resemble the intended operating system as closely as practical.

That includes:

  • actual operators;
  • normal material supply;
  • normal tooling;
  • standard work;
  • approved inspection;
  • expected changeovers;
  • normal maintenance support.

If special engineering support is required throughout the trial, record that fact.

Measure more than output

A process can hit the required quantity while hiding serious weaknesses.

Review:

  • first-pass yield;
  • scrap;
  • downtime;
  • cycle time;
  • staffing;
  • bottleneck utilization;
  • material shortages;
  • rework;
  • changeover loss.

First Pass Yield helps show whether production achieved output without excessive rework.

Identify the true constraint

If the rate is not achieved, determine where the system lost capacity.

Bottleneck Analysis can help identify the process step limiting throughput.

Do not automatically blame the slowest-looking machine.

The constraint may come from:

  • material handling;
  • quality checks;
  • staffing;
  • software;
  • changeover;
  • starvation;
  • blocking.

Compare with planned capacity

Capacity Planning estimates whether the process should have enough capacity.

Run at Rate tests that assumption under real conditions.

A mismatch between planned and demonstrated capacity is valuable learning.

Define acceptance criteria before the test

Do not decide after the run what counts as success.

Criteria may include:

  • required units;
  • quality level;
  • maximum downtime;
  • staffing limit;
  • process capability;
  • sustained duration.

The criteria should reflect customer and business requirements.

Treat failures as launch learning

A failed Run at Rate is useful when it reveals problems before full production.

The team should record:

  • what limited output;
  • whether the issue was temporary or structural;
  • required countermeasures;
  • retest conditions.

Countermeasure Management can help ensure significant gaps have owners and effectiveness checks.

Common mistakes

Testing only equipment speed, using extra people not planned for production, excluding quality losses, using a test duration too short to expose problems, changing acceptance criteria after the result, and treating a failed test as a paperwork problem instead of process learning are common mistakes.

Practical sequence

  1. define required demand and rate.
  2. define test duration and product mix.
  3. establish acceptance criteria.
  4. prepare normal production resources.
  5. run the process under representative conditions.
  6. measure output and losses.
  7. identify the constraint.
  8. compare actual with planned capacity.
  9. correct significant gaps.
  10. repeat the test when required.

The practical lesson

Run at Rate converts theoretical capacity into demonstrated capability.

It tests whether the whole production system can deliver the required result, not whether one machine can run fast for a few minutes.

This topic also connects with Production Readiness Review. Use that method when the improvement requires the related operating or management discipline.