Identify the slowest station, estimate weekly throughput, apply OEE losses, and see whether your line can realistically meet demand.
Introduction
Capacity problems in manufacturing are rarely caused by one simple number. A production line may appear to have enough staffed hours and enough machines to satisfy demand, yet finished output still falls short because the work does not flow evenly. One station runs slower than the rest. Changeovers quietly consume part of the shift. Breakdowns and minor stops cut into available time. Speed losses reduce actual rate below the ideal standard. Scrap and rework erase part of the volume that looked good while it was still in process. By the time the week ends, the plan that seemed realistic in a meeting no longer matches what can actually ship.
This calculator is built to make that gap visible in a fast, practical way. You enter the number of stations, the cycle time at each station, the schedule, daily downtime, batch setup time, operator count, and the familiar OEE inputs of availability, performance, and quality. The tool then identifies the slowest adjusted station, treats that station as the line constraint, and estimates two useful outputs: theoretical capacity if losses did not matter, and realistic capacity after common production losses are applied. It also compares that realistic figure with your weekly target so you can see whether the plan is achievable under current conditions.
The result is especially useful when a team is deciding where to focus. If realistic output is low because the bottleneck cycle time is too long, the best answer may be faster tooling, method redesign, or parallel capacity at that station. If theoretical capacity looks healthy but realistic capacity is weak, then the bigger opportunity may be uptime, speed stability, quality, or schedule discipline rather than more labor or more hours. That distinction matters because improvement projects are expensive, and the wrong project can consume time without increasing throughput.
What the inputs mean and how the math works
Start with the line configuration. The product or process name is simply a label, but the workstation count matters because it controls how many station-time fields appear. Those station times should represent normal run conditions in seconds per unit. It is better to use a stable average from direct observation or standard work than a best-ever number. A line is only as accurate as the times you feed into it, and exaggerated speed assumptions are one of the main reasons capacity plans become unreliable.
The schedule fields define the gross production window for the week. Hours per shift, shifts per day, and operating days per week create the planned time base. Daily downtime is then subtracted from each shift before weekly minutes are calculated. This is important because lines do not get to use every nominal minute on the calendar. Even a healthy plant loses time to maintenance, micro-stops, adjustments, cleaning, staging delays, and changeovers. Setup time is entered separately and spread across the batch size so each unit carries a fair share of that burden. A line with short batches and frequent product changes will usually lose more effective capacity than a line with long runs.
The operational metrics capture why theoretical capacity almost always overstates reality. Availability asks how much of planned runtime the equipment is actually available. Performance asks how close the line operates to its ideal pace while it is running. Quality asks what share of units are good without rework or scrap. Their product is OEE. Schedule adherence is applied after OEE because even a capable line cannot make units during time that was never truly executed according to plan. Together, those values turn a clean engineering estimate into a more honest planning estimate.
The formulas below describe the model used on the page. The first expression defines OEE. The second states the core bottleneck rule that the station with the longest cycle time limits total system throughput. The third applies both OEE and schedule adherence to move from theoretical to realistic capacity. Those relationships are simple, but they capture a large share of the reason manufacturing plans succeed or fail.
Inside the script, station times are converted from seconds per unit into minutes per unit, setup time per unit is added, and the longest adjusted station time becomes the pace setter for the whole line. Weekly available minutes are divided by that bottleneck time and then multiplied by operator count to estimate theoretical weekly capacity under the current script logic. Realistic capacity is then found by multiplying theoretical capacity by OEE and schedule adherence. In plain language, the line can only move as fast as its slowest step, and every loss factor pushes real output farther below the ideal number.
Worked example
Suppose an assembly line has five stations with average times of 40, 35, 60, 25, and 20 seconds per unit. The plant runs 8-hour shifts, 2 shifts per day, and 5 days per week with 10 operators. Setup time is 15 minutes per batch and the typical batch size is 50 units, so each unit carries 0.3 minutes of setup burden. After that adjustment, the testing station is still the slowest point in the route. That station becomes the bottleneck because every other step must ultimately wait for it.
Now add operating losses. If daily downtime averages 30 minutes, available time per shift falls before any capacity math starts. If availability is 85 percent, performance is 90 percent, and quality is 95 percent, OEE becomes 72.7 percent. If schedule adherence is 92 percent, realistic capacity is pushed lower still. This is the moment where the calculator becomes more useful than a rough line-rate estimate, because it shows the difference between what the line could produce in an ideal world and what it is likely to deliver in a real week.
If the weekly target is 2,000 units, the comparison tells you whether the target is supported by the current process. When realistic capacity exceeds the target, the line has some room for demand swings, rush orders, and ordinary disruption. When realistic capacity falls below the target, the gap gives the team a concrete improvement challenge. Instead of saying that the line feels tight, the team can say exactly how many additional units per week must be recovered and then decide whether the most credible lever is bottleneck improvement, better uptime, better quality, longer operating hours, or a different batch strategy.
Assumptions, interpretation, and better decisions
This analyzer is meant to be practical, not perfect. It assumes that the line can be represented by a station sequence with reasonably stable cycle times and that the slowest adjusted station is an acceptable proxy for the system constraint. In a mixed-model environment, a high-variability process, or a plant with frequent rework loops, the true bottleneck may shift over the course of the day. Material shortages, operator skill variation, and sequence-dependent changeovers can also change the picture. That does not make the calculator wrong; it simply means the result should be read as a structured estimate rather than a promise.
Interpret the outputs in order. The bottleneck station tells you where to look first. Theoretical capacity tells you the upper bound under the model. Realistic capacity tells you what the current operation is more likely to achieve after normal losses are applied. The target comparison tells you whether the plan is supported. If the gap between theoretical and realistic capacity is wide, then line reliability, speed consistency, and quality may deserve more attention than raw labor hours. If the bottleneck is dramatically slower than every other station, then attacking that station often creates the largest throughput gain.
It is also worth noting what happens when improvement work is aimed at the wrong place. Speeding up a non-bottleneck station can feel productive because local metrics improve, but total output may stay flat if the slowest station remains unchanged. That is why bottleneck logic is so powerful. It helps protect a team from scattered effort. A small cycle-time reduction at the true constraint can matter more than a dramatic improvement at a station that already had spare capacity.
Use the tool as a first-pass planning and teaching aid. It is strong for weekly scheduling, staffing discussions, rough scenario testing, and prioritizing kaizen work. If the numbers will be used to justify a major capital purchase or a contractual delivery commitment, follow this result with direct observation, time studies, and more detailed analysis. In other words, let the calculator narrow the conversation quickly, then use deeper study where the business risk is highest.
Planning with bottlenecks instead of guesswork
Capacity planning is not the same as counting machine hours. In many plants, the real planning mistake happens before the first unit is built. Teams take nominal schedule hours, multiply by a rate they hope to achieve, and assume the result is a valid output commitment. That shortcut ignores how production systems actually behave. Throughput is shaped by the slowest step, by changeover frequency, by uptime, by speed stability, by first-pass quality, and by whether the schedule is executed as planned. A line can look busy every minute of the day and still underperform because the work is accumulating in front of a weak point that has not been treated as the governing constraint.
Hidden constraints are expensive because they drive the wrong response. When shipments slip, the first instinct is often overtime, expediting, or pressure on every department at once. Those actions may raise cost without raising output. If testing is the bottleneck, adding effort to packaging or to an already fast assembly step will not create more shipments. The queue simply grows in front of the constraint. The calculator helps keep improvement grounded by showing which station is likely pacing the line and by estimating how far losses have pushed real output below the ideal headline number.
The comparison between theoretical and realistic capacity is one of the most useful conversations on the page. Theoretical capacity is not meaningless; it shows what the line could do if the modeled constraint set the pace without loss. But realistic capacity is the better operating number because it reflects the quality of execution. A large gap between the two usually means the biggest win is not another machine or another shift. It may mean unstable uptime, chronic small stops, weak standard work, quality drift, or poor adherence to the published schedule. That insight prevents teams from solving the wrong problem with an expensive answer.
The target comparison adds discipline to decision-making. If realistic capacity is above target, the line may have enough margin to absorb ordinary variation and some rush work. If it is below target, the weekly shortfall becomes concrete. A precise weekly gap is useful because it allows trade-offs to be evaluated rationally. Could a setup reduction program recover that many units? Would an operator reallocation at the bottleneck matter? Is the business better served by more uptime, by a batch-size change, or by adding hours? Once the shortfall is visible, improvement options can be judged against the same requirement instead of being debated in the abstract.
The calculator is also valuable for scenario testing. A team can keep the line structure fixed and try one change at a time: lower setup minutes, better availability, higher quality, a shorter bottleneck cycle, or a different staffing level. Even though the model is intentionally simple, this kind of controlled comparison is often enough to reveal which lever has the strongest effect. That makes meetings more productive. Instead of jumping from opinion to opinion, the team can ask which assumption changed the result and whether that change is actually realistic on the floor.
Use the output as a structured estimate, then deepen the analysis when the stakes rise. For weekly planning, prioritization, and teaching, the model is fast and transparent. For a large equipment purchase, contract commitment, or major layout redesign, the result should be followed by direct observation, updated standards, queue analysis, and perhaps a more detailed simulation. In practice, that is a strength rather than a weakness. A calculator like this helps teams reach the right question quickly, and asking the right question is often the first real improvement step in manufacturing.
