Ideal cycle time is the fastest sustainable time a machine takes to make one good unit under ideal conditions. You determine it from the machine's best demonstrated repeatable rate or its validated nameplate spec, never the budgeted or historical-average rate, and you set it once per product, then defend it. It is the single OEE input that decides whether the whole number is honest.
Every other OEE input is a count or a clock reading. Ideal cycle time is a judgment, and because it sits in the Performance factor as the benchmark all speed is measured against, a soft value quietly inflates OEE while nothing on the floor improves. Set it too slow and Performance can sail past 100%, which is physically impossible and a tell that the baseline is wrong. This guide is about getting that one number right: what it is, where it comes from, how to choose among nameplate, demonstrated best, and engineering standard, and how to keep it from being negotiated soft over time.
What is ideal cycle time?
Ideal cycle time is the theoretical minimum time to produce one unit when the machine runs at its full, sustainable speed with no stops and no slow-downs. It is a per-product figure, the same machine has a different ideal cycle time for a different SKU, expressed as time per unit (say 1.2 seconds per bottle) or its inverse, the ideal rate (50 units per minute). "Ideal" means best sustainable, not a one-off record set with a tailwind.
It differs from the related times people confuse it with. It is not actual cycle time which is what you really observe including slow-downs. It is not takt time which is set by customer demand, not the machine. And it is not the "standard" rate from a costing sheet, which is often a padded or averaged figure. Ideal cycle time is a property of the equipment and the product together, at their best, and in the OEE Performance formula it is the yardstick every actual cycle is measured against.
Why does ideal cycle time decide whether OEE is honest?
Because it is the reference speed, and a wrong reference biases the whole Performance factor, which then biases OEE. If the true best rate is 60 units a minute but you enter 50 as "ideal," a line genuinely running at 55 will report Performance above 100%, the machine looks like it beat a speed you understated. Flip it: enter an aspirational 70 the line has never hit, and Performance is permanently depressed, so real speed losses are buried under a baseline that was never achievable.
This is why ideal cycle time is where OEE credibility is won or lost. Availability and Quality are anchored to countable events, a stop happened or it didn't, a unit passed or it didn't. Performance floats on whatever reference you chose, and that reference is the easiest thing on the floor to negotiate: every request to "adjust the standard" so the numbers look better is really a request to move this one input. Hold it firm and Performance measures real speed loss, the slow cycles and the minor stops that live in the six big losses. Let it drift and Performance measures nothing. For how it flows into the full calculation, keep the OEE walkthrough alongside.
How do you determine ideal cycle time?
Work from real evidence toward a defensible single value per product. The method has five steps, and the discipline is refusing to soften the answer along the way:
- Gather the candidate rates. Pull three things: the equipment nameplate or datasheet rate, the fastest sustained rate the line has actually demonstrated on this product, and any engineering time standard from process design.
- Pull demonstrated best from real run data. Look at short windows of clean running, a few minutes with no stops, and find the fastest rate the line held steadily. Ignore single-cycle flukes; you want a rate it sustained, not a spike.
- Reconcile against nameplate. Demonstrated best should sit at or below nameplate. If it exceeds nameplate, either the nameplate is conservative or your count or clock is off, investigate before trusting it.
- Choose the value and write it down. Take the best sustainable rate you can defend with evidence, per product, and record it with the date and the basis ("demonstrated best, week of X" or "nameplate, validated Y").
- Validate with a controlled run. Run the line clean for a set period, count good units, and confirm the chosen ideal cycle time produces a Performance at or just under 100% during that window. If Performance exceeds 100%, the ideal is too soft; tighten it.
- Lock it and set a review trigger. Fix the value and only revisit it on a real change, new tooling, a product-spec change, a rebuild, not because a monthly number looked low.
Nameplate, demonstrated best, or engineering standard?
Default to demonstrated best, fall back to nameplate, and use the engineering standard only to sanity-check. Each source has a job, and the trouble starts when a costing or budget rate sneaks in wearing the "ideal" label.
| Source | What it is | Best used for | Watch out for |
|---|---|---|---|
| Nameplate / datasheet | Manufacturer's rated speed for the equipment | Upper bound and a reality check on demonstrated best | Rated under ideal lab conditions; may not hold with your product |
| Demonstrated best | Fastest rate your line actually sustained on this product | The working ideal cycle time in most cases | Use a sustained window, not a one-cycle fluke |
| Engineering standard | Calculated rate from process/time study | Cross-check and a starting point for new products | Often padded or averaged; not a true "ideal" |
| Budget / costing rate | Rate used for financial planning | Nothing in OEE | The most common source of soft ideal cycle times |
For an established product, demonstrated best is usually the right ideal cycle time: it reflects your equipment, your material, and your conditions, and the line has proven it can reach it. Nameplate is the ceiling and the cross-check, demonstrated best above nameplate is a red flag on your data. The engineering standard shines for a brand-new product with no run history, where you have nothing demonstrated yet. The budget rate belongs nowhere near the calculation; whenever Performance looks suspiciously flattering, a costing rate masquerading as ideal cycle time is the first thing to check.
How do you defend ideal cycle time over time?
Freeze it, document the basis, and require evidence to change it. Ideal cycle time decays the way a diet does: through small, reasonable-sounding concessions. A shift comes in low, someone suggests the "standard is too aggressive," and the ideal creeps slower, and every notch slower makes Performance and OEE look better while the line runs exactly as it did. Left alone, the number becomes whatever makes the report comfortable.
Three guards hold the line. Document the basis with each value, source, date, the run that demonstrated it, so any change starts from evidence, not opinion. Set a change trigger tied to physical reality: revisit ideal cycle time on new tooling, a spec change, or a rebuild, never because a monthly OEE dipped. And treat Performance persistently over 100% as a defect in the input, not a triumph on the floor, it is the clearest signal the ideal is soft, and it should trigger a re-validation, not a celebration. Because ideal cycle time is a judgment, wiring the count and clock to the machine removes two of the three ways Performance can be wrong and isolates the one that requires discipline; measuring at the source, the way Harmony computes true OEE from machine signals, means the only remaining variable is the reference you chose and can defend (see the platform).
What does a good ideal cycle time deliver?
A defensible ideal cycle time is what lets the Performance factor mean something, and it is the reason the 95% "world-class" Performance target is a real bar rather than an accounting artifact.
| Reference | What it says | Provenance |
|---|---|---|
| Performance factor | Uses ideal cycle time as the benchmark: (count × ideal cycle time) ÷ run time | OEE definition; Seiichi Nakajima, Introduction to TPM (Productivity Press, 1988) |
| World-class Performance | 95%, only meaningful if the ideal cycle time is a true best rate | Nakajima TPM benchmark; a reference, not an audited standard |
The Performance factor and its 95% "world-class" reference come from Seiichi Nakajima's Total Productive Maintenance work, popularized in Introduction to TPM (Productivity Press, 1988); the figure is a widely cited orientation point, not an audited industry statistic. Its meaning depends entirely on ideal cycle time being a true best rate, a 95% Performance built on a soft ideal is worth nothing. For macro context on real-world equipment use, the Federal Reserve's G.17 capacity-utilization release is a reminder that plants run well below theoretical maximums by any honest measure, ideal cycle time included.
Ideal cycle time is one number and the whole game. Determine it from demonstrated best, cross-check against nameplate, validate on a clean run, and then defend it against the slow drift toward comfortable. Use it to set honest OEE targets track its effect in your manufacturing KPIs against a clean downtime picture put a defensible value into the OEE calculator and see how honest inputs changed the picture at one plant in the CLS case study.