# ECO Cycle Time and Backlog Calculator

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

## Short answer

Use Little's law to turn open ECO count and closure rate into average cycle time, backlog clearing time and the engineering headcount your change flow needs.

## Category

engineering-plm

## Audience

- Engineering manager
- Configuration manager
- PLM administrator

## Tool

**Kind:** calculator

**Inputs:**

#### Open ECOs in flight

**Key:** open_ecos

**Type:** number

**Default:** 64

**Min:** 0

**Step:** 1

**Unit:** ECOs

**Help:** Count every ECO that is not yet released or closed, including those waiting on approvers.

#### New ECOs per week

**Key:** arrivals

**Type:** number

**Default:** 9

**Min:** 0

**Step:** 0.5

**Unit:** per week

**Help:** Average over the last 8 to 12 weeks.

#### ECOs closed per week

**Key:** closures

**Type:** number

**Default:** 8

**Min:** 0

**Step:** 0.5

**Unit:** per week

**Help:** Average ECOs released or closed per week over the same period.

#### Engineering touch time per ECO

**Key:** touch_hours

**Type:** number

**Default:** 11

**Min:** 0

**Step:** 0.5

**Unit:** hours

**Help:** Hands-on hours across author, checker and approvers, not elapsed time.

#### Productive change hours per engineer per week

**Key:** fte_hours

**Type:** number

**Default:** 12

**Min:** 1

**Step:** 1

**Unit:** hours

**Help:** Hours each engineer can realistically give to change work after design projects.

**Outputs:**

#### Net backlog growth per week

**Key:** net_growth

**Expr:** arrivals - closures

**Format:** decimal

**Description:** Positive means the backlog is growing every week.

#### Change flow load (arrivals vs closures)

**Key:** load

**Expr:** arrivals / closures * 100

**Format:** percent

**Description:** Above 100 percent the queue cannot stabilise.

#### Average ECO cycle time

**Key:** cycle_weeks

**Expr:** open_ecos / closures

**Format:** weeks

**Primary:** true

**Description:** Little's law: work in process divided by throughput.

#### Weeks to clear backlog

**Key:** clear_weeks

**Expr:** if(gt(closures, arrivals), open_ecos / (closures - arrivals), 0)

**Format:** weeks

**Description:** Shows 0 when arrivals meet or exceed closures, meaning the backlog never clears at the current rates.

#### Engineering hours demanded per week

**Key:** eng_hours

**Expr:** arrivals * touch_hours

**Format:** hours

#### Engineers needed on change work

**Key:** fte_needed

**Expr:** eng_hours / fte_hours

**Format:** decimal

**Primary:** true

**Chart:**

#### Average ECO cycle time vs closure rate

**Type:** line

**X:** closures

**From:** 4

**To:** 30

**Steps:** 27

**Series:**

- cycle_weeks

**Disclaimer:** Little's law assumes a stable flow. If the backlog is growing quickly, treat cycle time as an indicator and measure real elapsed days from ECO creation to release as well.

## Content

**Intro:** An engineering manager is often asked why changes take so long and how many people are needed. This calculator applies Little's law to your open ECO count and closure rate to give an average cycle time, and shows whether your flow can ever clear the backlog.

**Sections:**

#### How to use the calculator

**Body:** Pull the open ECO count and the weekly arrival and closure counts from your PLM or ERP change module for the last two to three months. Enter touch hours as the actual hands-on effort per change, not the calendar duration. The result shows the average cycle time, the weeks to clear the queue and the number of engineers the change flow consumes. Move the closure rate to see what a faster board or an extra checker would do.

**Bullets:**

- Use averages over at least 8 weeks to smooth out release spikes.
- Count emergency and standard ECOs together unless you track them separately.
- Exclude cancelled ECOs from closures.

#### The method behind the numbers

**Body:** Little's law states that average work in process equals throughput multiplied by average time in the system. Rearranged, cycle time is open ECOs divided by closures per week. When arrivals exceed closures the net growth is positive and the clearing time cannot be computed, because the queue grows without bound. When closures exceed arrivals the backlog clears in open ECOs divided by the difference.

#### Reading the chart and a worked example

**Body:** With 64 open ECOs, 9 arrivals and 8 closures a week, cycle time is 8 weeks and the backlog grows by one ECO a week. Raising closures to 12 a week cuts the cycle time to about 5.3 weeks and clears the backlog in roughly 21 weeks. The chart shows the steep gain from small throughput improvements when you start near saturation.

#### Common mistakes

**Body:** Counting only ECOs that are actively being worked hides the approval queue, which is usually where most elapsed time sits. Mixing minor documentation changes with full form-fit-function changes also distorts touch time. Finally, remember Little's law gives an average, so a few long-running ECOs can sit far above it.

**Cta:** If your open ECO list and approval status live in an ERP or PLM, Netray can wire up a read-only report that refreshes these figures weekly without manual exports.

**Faq:**

#### What is a good ECO cycle time?

**Answer:** It depends on change class and industry. Simple documentation changes may close in days, while form-fit-function changes with supplier and customer approval often take weeks. Compare your own trend by change class rather than chasing a universal number.

#### Why is my backlog never clearing?

**Answer:** If new ECOs arrive as fast as or faster than you close them, the queue cannot shrink. You need higher closure capacity, fewer unnecessary changes, or a triage rule that stops low-value requests from becoming full ECOs.

#### Should I include waiting time at approvers?

**Answer:** Yes. Open ECOs include those waiting for approval, so the cycle time reflects elapsed time. Touch hours should only include real effort, which is why the two inputs are separate.

#### Can I use this for ECRs as well as ECOs?

**Answer:** Yes, if you apply it to one stage at a time. Use ECR counts for the review stage and ECO counts for the implementation stage, then add the cycle times to estimate the total request-to-release duration.

## Search terms

eco cycle time calculator, engineering change backlog, engineering change order lead time, ecn throughput, littles law engineering changes, how long does an eco take, engineering change workload, change board backlog

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