Of all the numbers that feed OEE, one does more damage when it is wrong than any other, and it is the one most people guess: ideal cycle time. It is the benchmark your machine's real speed is measured against, so a sloppy value silently inflates or deflates your whole OEE score. If your OEE looks suspiciously good, or makes no sense, the ideal cycle time is the first place to look.
Performance is real speed versus ideal cycle time — so the benchmark has to be right.
Ideal cycle time is the fastest time in which a machine can produce one good unit under optimal conditions, the theoretical best, not the average you happen to achieve. It is the speed benchmark at the heart of OEE's performance factor. Some teams use the closely related "ideal run rate" (units per hour), which is simply its inverse.
Within OEE, the performance factor is calculated as: Performance = (Ideal Cycle Time × Total Count) ÷ Run Time. In plain terms, it compares how fast you actually ran to how fast you ideally could have. That makes ideal cycle time the yardstick for the entire performance dimension, and any error in it flows straight into your reported OEE.
Manufacturer's nameplate rate. A reasonable starting point, but it reflects lab conditions and may not match your product, tooling or materials.
Demonstrated best. Often more honest: the fastest sustained rate you have actually achieved producing good units. It proves the speed is attainable on your floor.
Per product, not per machine. Different products usually have different ideal cycle times on the same machine; one blanket value distorts everything.
The classic error is using the average achieved cycle time as the "ideal." If your benchmark is just your typical speed, your performance factor will always look close to 100%, and all your speed losses, minor stops and slow running, vanish from the data. Your OEE looks great and improves nothing. The ideal must represent the best possible, so the gap to it stays visible and actionable.
Manually timing cycles and maintaining ideal-rate values per product across many machines is tedious and quickly goes stale, exactly the kind of effort that gets abandoned and turns into dark data. Capturing actual cycle times automatically lets you set realistic ideals from demonstrated best performance and keep them current, which is also why a sound move beyond the OEE spreadsheet matters. For the related lean timing concepts, see takt time vs cycle time.
Fabrico captures real cycle times directly from the machines, so you can base ideal cycle time on demonstrated best performance per product rather than a guess, and keep it accurate over time. That makes the performance factor, and therefore your whole OEE, trustworthy, and keeps speed losses visible so they can actually be improved.
The fastest time a machine can produce one good unit under optimal conditions, the theoretical best speed used as the benchmark in OEE's performance factor.
Performance = (Ideal Cycle Time × Total Count) / Run Time. It is the benchmark your actual speed is compared against.
Using your average achieved speed as the "ideal." That hides all speed losses and makes OEE look better than it is.
Make your OEE trustworthy from the inputs up. See how Fabrico captures real cycle times so your performance factor reflects reality. Book a demo today.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
