# Bottleneck Analysis Calculator: Find the Constraint

> Source: https://netray.co/tools/bottleneck-analysis-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Enter process time, machine count and OEE for three resources, then see weekly capacity, which one is the bottleneck, and how utilization rises with demand.

## Category

mes-shop-floor

## Industry

Discrete Manufacturing

## Audience

- Production scheduler
- Industrial engineer
- Plant manager

## Tool

**Kind:** calculator

**Inputs:**

#### Weekly demand

**Key:** demand

**Type:** number

**Default:** 380

**Min:** 0

**Step:** 10

**Unit:** units

**Help:** Units the customers require per week.

#### Scheduled hours per week

**Key:** hours

**Type:** number

**Default:** 80

**Min:** 1

**Step:** 1

**Unit:** h

**Help:** For example two 8 hour shifts for five days is 80.

#### Average OEE

**Key:** oee

**Type:** slider

**Default:** 75

**Min:** 30

**Max:** 100

**Step:** 1

**Unit:** %

**Help:** Availability times performance times quality.

#### Resource A time per unit

**Key:** t1

**Type:** number

**Default:** 12

**Min:** 0.1

**Step:** 0.5

**Unit:** min

#### Resource A machines

**Key:** n1

**Type:** number

**Default:** 2

**Min:** 1

**Step:** 1

#### Resource B time per unit

**Key:** t2

**Type:** number

**Default:** 9

**Min:** 0.1

**Step:** 0.5

**Unit:** min

#### Resource B machines

**Key:** n2

**Type:** number

**Default:** 1

**Min:** 1

**Step:** 1

#### Resource C time per unit

**Key:** t3

**Type:** number

**Default:** 5

**Min:** 0.1

**Step:** 0.5

**Unit:** min

#### Resource C machines

**Key:** n3

**Type:** number

**Default:** 1

**Min:** 1

**Step:** 1

**Outputs:**

#### Resource A capacity per week

**Key:** cap1

**Expr:** hours * 60 * oee / 100 * n1 / t1

**Format:** integer

#### Resource B capacity per week

**Key:** cap2

**Expr:** hours * 60 * oee / 100 * n2 / t2

**Format:** integer

#### Resource C capacity per week

**Key:** cap3

**Expr:** hours * 60 * oee / 100 * n3 / t3

**Format:** integer

#### Bottleneck capacity per week

**Key:** cap_b

**Expr:** min(cap1, min(cap2, cap3))

**Format:** integer

**Primary:** true

**Description:** The line can never ship more than the slowest resource can process.

#### Bottleneck resource (1 = A, 2 = B, 3 = C)

**Key:** which

**Expr:** if(lte(cap1, cap_b), 1, if(lte(cap2, cap_b), 2, 3))

**Format:** integer

#### Bottleneck utilization at current demand

**Key:** util_b

**Expr:** demand / max(cap_b, 1) * 100

**Format:** percent

**Primary:** true

**Description:** Above 100 percent means demand cannot be met without more capacity.

#### Maximum weekly throughput

**Key:** thru

**Expr:** min(demand, cap_b)

**Format:** integer

#### Capacity gap (negative means shortfall)

**Key:** gap

**Expr:** cap_b - demand

**Format:** integer

**Chart:**

#### Bottleneck utilization versus weekly demand

**Type:** line

**X:** demand

**From:** 100

**To:** 700

**Steps:** 30

**Series:**

- util_b

**Disclaimer:** Assumes a serial line, no scrap between steps and the same OEE on every resource. Adjust the time per unit upward to reflect scrap or rework loops.

## Content

**Intro:** Every production line has a bottleneck: the resource with the least capacity relative to what it must process. Improving anything else does not raise output. This calculator compares the weekly capacity of three resources against demand and shows which one is the constraint.

**Sections:**

#### How to use it

**Body:** Enter weekly demand, the scheduled hours per week and an average OEE. Then enter the process time per unit and the number of parallel machines for each of three resources, for example machining, assembly and test. The calculator converts everything to units per week for each resource and picks the lowest as the bottleneck. Try raising demand or adding a machine to see how the constraint moves. Use the chart to see where the bottleneck reaches 100 percent utilization.

**Bullets:**

- Use actual time per unit including setup spread over the lot.
- Use measured OEE per resource if you have it; this tool uses one average.
- Combine operations on the same machine into one resource.

#### The method

**Body:** Capacity per week equals scheduled minutes times OEE times machine count divided by process minutes per unit. The resource with the lowest capacity is the bottleneck, in line with the Theory of Constraints, which says that an hour lost at the constraint is an hour lost for the whole system. Utilization is demand divided by bottleneck capacity. Throughput is limited to the lower of demand and bottleneck capacity. The remaining resources have protective capacity, which is what lets the constraint stay busy despite variation.

#### Worked example

**Body:** With 80 scheduled hours and 75 percent OEE, resource A with two machines at 12 minutes per unit gives 600 units a week. Resource B with one machine at 9 minutes gives 400, and resource C with one machine at 5 minutes gives 720. Resource B is the bottleneck at 400 units. Demand of 380 means it runs at 95 percent, with almost no headroom. Adding a second machine at B raises its capacity to 800 and moves the constraint to A at 600. That is the pattern: fix the constraint and the next one appears.

#### Common mistakes

**Body:** A frequent error is to use nameplate capacity instead of demonstrated capacity, which overstates every resource. Another is to improve a non-constraint, such as speeding up resource C, and expect more output. Also watch for shifting bottlenecks caused by product mix, where different products load different machines. In that case, run the calculator for each mix scenario, or weight the process times by the expected mix.

**Cta:** If you want the bottleneck identified from live routings, work center calendars and actual reporting in your ERP, Netray can help you build that analysis over your data.

**Faq:**

#### How do I identify a bottleneck in production?

**Answer:** Compare the effective capacity of each step in units per period. The step with the lowest capacity, or the one with the highest utilization and the longest queue in front of it, is the bottleneck. Confirm on the floor: downstream stations wait on it while upstream stations pile up work.

#### Why does the bottleneck matter for scheduling?

**Answer:** The bottleneck sets the output of the whole system, so the schedule should be built around it. Keep it fed, avoid starving it, and protect its time from changeovers, breaks and quality problems. Other resources can then be scheduled to support it.

#### What utilization is safe for the bottleneck?

**Answer:** Queues grow quickly as utilization approaches 100 percent, so many planners aim for roughly 85 to 90 percent on the constraint while keeping it never idle. The right figure depends on variability, so treat the target as a starting point to adjust from experience.

#### Can the bottleneck move?

**Answer:** Yes. It can move when you improve the constraint, when product mix changes, or when a machine goes down. That is why you recheck capacity after every material change and keep protective capacity at the other resources.

## Search terms

bottleneck analysis calculator, find bottleneck in production line, constraint capacity calculation, theory of constraints calculator, process capacity vs demand, bottleneck utilization, throughput of production line, capacity by resource

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json