Cycle Time & Capacity Calculator: From Seconds per Unit to Annual Output
This free cycle time and capacity calculator converts a demonstrated cycle time into realistic hourly, daily, and annual capacity for production planners, manufacturing engineers, and operations managers. It accounts for parallel stations, shift patterns, working days, and - critically - a utilization factor that separates theoretical from achievable output. At the defaults (45-second cycle, 3 stations, two 8-hour shifts, 85% utilization), the system produces about 204 units per hour, 3,264 per day, and 816,000 per year. Use it to sanity-check quotes, size new lines, and test whether promised delivery dates are physically possible.
Your numbers
Actual demonstrated cycle time at the constraint operation, not the design ideal.
Identical machines or cells running this operation in parallel.
Scheduled hours per shift before applying the utilization factor.
Production shifts per working day.
Share of scheduled time actually producing, after downtime, changeovers, and minor stops. 80-85% is a solid discrete plant; use your OEE availability x performance if known.
Typical 5-day operations run 240-250 days after holidays and shutdowns.
Your results
Estimates only. Real capacity depends on product mix, sequence-dependent setups, and constraint interactions that a single-operation model cannot capture.
Get your full capacity analysis report
We will email you a personalized capacity model with utilization benchmarks and constraint analysis for your operation, and a Netray specialist will follow up to pressure-test the numbers with you.
No spam. Your results stay private. Unsubscribe anytime.
The capacity math, step by step
Gross hourly capacity per station is 3600 divided by cycle time in seconds - an 45-second cycle yields 80 units per hour. Multiplying by parallel stations gives gross system rate, and applying the utilization factor converts it to a realistic rate: 80 x 3 x 85% is 204 units per hour. Daily capacity multiplies by productive hours and shifts; annual capacity multiplies by working days. The effective system cycle time output inverts the hourly rate so you can compare directly against takt time. The single most common capacity planning error is skipping the utilization factor - quoting 100% of theoretical rate guarantees late orders because no plant runs without changeovers, breakdowns, and minor stops.
Choosing a defensible utilization factor
Utilization here means the share of scheduled time your stations actually spend producing at rate. If you track OEE, multiply availability by performance and use that. If you do not, these reference points keep you honest:
- 90%+ is achievable only on dedicated, low-changeover lines with mature TPM - be skeptical of plans that assume it.
- 80-85% is a realistic target for well-run discrete operations with moderate mix.
- 65-75% is typical for high-mix job shops with frequent setups and shared equipment.
- Below 60% usually signals chronic downtime or scheduling problems worth fixing before buying capacity.
From single-operation capacity to real plant capacity
This model describes one operation, but plant output is set by the constraint - the single operation with the least capacity relative to demand. Run this calculator for each major work center on a routing and the smallest annual figure is your realistic ceiling; adding capacity anywhere else buys nothing. Watch for mix effects too: if changeover-heavy products grow as a share of demand, effective utilization at the constraint drops even though nothing on the floor changed. That is why serious capacity planning lives in finite-capacity scheduling tools fed by accurate routings and demonstrated (not standard) cycle times, rather than in one-off spreadsheets that go stale the week after they are built.
How Netray helps you plan capacity for real
Netray builds capacity planning on top of Infor SyteLine and LN using data you already own: routings, demonstrated run rates from shop floor transactions, and live order load. We implement finite-capacity scheduling so promise dates reflect the constraint's actual availability, and deploy on-prem AI that continuously reconciles standard cycle times against demonstrated performance - flagging routings whose standards have drifted more than 10% from reality. For aerospace, defense, and electronics clients, all of this runs inside your firewall. A focused engagement typically corrects the top 50 routings and stands up constraint-level scheduling in one quarter.
Frequently Asked Questions
Should I use standard cycle times or demonstrated cycle times?
Use demonstrated cycle times for capacity planning and promising, and keep standards for costing until they are corrected. In most shops, standards were set at implementation and have drifted - sometimes 15-30% - as products, tooling, and methods changed. Planning against optimistic standards systematically overloads the schedule. Pull actual run rates from shop floor transactions over the last 90 days and use the median, not the best run.
How do I handle multiple products with different cycle times?
For a quick answer, compute a demand-weighted average cycle time: multiply each product's cycle time by its share of unit volume and sum. For anything more serious, express capacity in hours rather than units - each product consumes hours at the constraint according to its routing - and compare total demanded hours against available hours. That is exactly what finite-capacity scheduling automates, including sequence-dependent setup effects.
What is the difference between capacity and OEE?
They answer different questions with the same underlying data. OEE looks backward: how much of planned time did we convert into good product at rate? Capacity looks forward: how many units can we commit to? The utilization factor in this calculator is effectively your OEE availability times performance, applied prospectively. A plant improving OEE at its constraint is literally creating sellable capacity without capital spending.
Ask Netray to benchmark your quoted capacity against demonstrated shop floor data and find the routings that are lying to your scheduler.
Related Tools
Takt Time Calculator
Compute the takt time your line must hit to meet customer demand, plus the required hourly rate for supervisors and schedulers.
Discrete ManufacturingOEE Calculator (Overall Equipment Effectiveness)
Break your Overall Equipment Effectiveness into availability, performance, and quality, and see how far you sit from the 85% world-class benchmark.
Discrete ManufacturingProduction Scheduling Maturity Assessment
Score your scheduling practice across method, capacity logic, adherence, and shop floor feedback - and see the staged path to finite-capacity scheduling.
Go Deeper
Finite Capacity Scheduling: A Practical Guide
Finite capacity scheduling explained: how it differs from infinite MRP loading, APS options for SyteLine and LN, data prerequisites, and AI-assisted scheduling.
Shop Floor Data Collection: Connecting Machines to ERP
Shop floor data collection guide: connect CNC machines, barcode scanning, and IIoT sensors to ERP. Covers OPC UA, MTConnect, Factory Track, costs, and AI agents.