How to Estimate Line Speed Capacity (Nameplate vs. Real)

Ask a plant manager how fast a line runs and you'll often get the number off the equipment spec sheet: the extruder's nameplate rating, the motor's top speed, the number that was true in a lab or a demo, under ideal conditions, with no changeover, no material variation, and nothing downstream slowing it down. That number is real. It's just usually not the number you should be scheduling against.

Why nameplate speed and real speed diverge

Nameplate or rated speed describes what a piece of equipment is capable of in isolation. What actually limits throughput on the floor is often somewhere else entirely:

• Downstream equipment. On an extrusion line, the extruder itself is frequently not the bottleneck. Cooling capacity, calibration, sizing, and haul-off equipment often cap the achievable rate well below what the extruder could theoretically push, especially on larger diameters or thicker walls where cooling time dominates.
• Material behavior. Some resins, colors, or compounds run stably at a certain speed and start producing out-of-spec output above it. The nameplate rating doesn't know or care what material is loaded.
• Tooling and setup specifics. The same nominal product can run at a different real speed depending on which die, calibrator, or downstream configuration a specific line happens to have installed, even across lines with identical nameplate ratings.
• Operator and process variation. Real runs include startup, ramp-up to stable speed, minor adjustments, and the small stops that don't show up in a spec sheet but do show up in a shift log.

None of this means nameplate speed is useless. It's a ceiling, not an estimate. Planning against it produces a schedule that looks achievable on paper and doesn't survive contact with the floor.

What to use instead

The number that actually belongs in a schedule is a demonstrated rate: what a specific line has actually produced on a specific SKU (or a close family member, if this exact one hasn't run yet), measured from a real run, net of startup and ramp time. If you have production history, that's the best source. If you don't, start with a conservative estimate, well under nameplate, and correct it with real numbers as soon as you have a few actual runs to measure against.

A few practical notes on doing this well:

• Track rate by line and by product, not once for the whole plant. The same SKU can run at meaningfully different real speeds on two lines with the same nameplate rating, because tooling, calibration, and wear differ line to line. A single plant-wide "units per hour" number erases that difference and produces a schedule that's wrong for whichever line it doesn't match.
• Update the number when you get better data. A rate estimated before a line ever ran a product is a guess. A rate measured over several real runs is data. Treat the second one as the one that should win, and revisit it periodically, since tooling wear and process changes can shift real throughput over time.
• Separate rate from availability. A line's achievable speed while running and how much of the scheduled time it's actually running (after downtime and changeovers) are two different numbers. Conflating them into one "effective rate" hides which one you actually need to fix if output falls short.

Why this matters for the schedule, not just the estimate

A schedule built on an optimistic rate doesn't just risk one late order. It compounds: every order on that line inherits the same overstated throughput, so a week that looks fully booked on paper is actually oversold, and the gap doesn't show up until orders start missing due dates in sequence. Getting the rate right is one of the few inputs where being conservative and correct beats being optimistic and wrong, because the cost of the second one shows up on every order behind the first late one.

Where the capacity calculator and RunMark fit

RunMark's free extrusion production capacity calculator deliberately doesn't guess a rate for you. You enter a rated throughput as an input, and it calculates net available hours, scrap-adjusted good output, and completion timing from whatever number you provide. That's intentional: the calculator is a fast way to test a demand against a rate you actually trust, not a substitute for knowing that rate in the first place.

Inside RunMark itself, throughput is stored per line and per SKU rather than as one plant-wide figure, the same principle the calculator encourages: the number that drives the schedule should reflect what a specific line actually does with a specific product, not a single average that happens to be right for none of them.