ECO Cycle Time and Backlog Calculator
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.
Your numbers
Count every ECO that is not yet released or closed, including those waiting on approvers.
Average over the last 8 to 12 weeks.
Average ECOs released or closed per week over the same period.
Hands-on hours across author, checker and approvers, not elapsed time.
Hours each engineer can realistically give to change work after design projects.
Your results
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.
Average ECO cycle time vs closure rate
Sweeps ECOs closed per week from 4 to 30, holding your other inputs fixed.
Automate the ECO flow report
Optional: we can set up a read-only weekly report of open ECOs, aging and closure rate from your ERP or PLM data.
Optional. The tool and every export work without this. No spam.
How to use the calculator
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.
- 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
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
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
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.
Frequently Asked Questions
What is a good ECO cycle time?
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?
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?
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?
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.
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.
Related Tools
Engineering Change Cutover Cost Calculator
Decide whether to cut an engineering change in immediately or let old stock run out, based on scrap, rework and the weekly benefit of the new design.
Engineering & PLMDesign Change Cost Escalation Calculator
Model the cost of the same design change at different lifecycle phases, with tooling and affected-unit rework, to justify earlier design reviews.
Engineering & PLMECO Backlog Aging Worksheet
List open ECOs with stage, owner, age and target days, and see overdue days and engineering hours at a glance for the weekly change board.
Engineering & PLMECO Implementation and Closure Checklist
Verify that BOMs, drawings, stock, suppliers, work instructions and quality records are all updated before you close an engineering change.
More Engineering & PLM tools
See all- SAP Super BOM Design Worksheet
- SAP Engineering Change Number Checklist
- SAP Document Info Record Template
- SAP Change Master and Revision Level Log
- SAP Engineering Change Request (ECR) Template
- SAP BOM Usage and Item Category Reference
- SAP Engineering Change Obsolescence Exposure Calculator
- SAP Engineering Change Affected Materials Impact Worksheet
- Cloud MRP BOM Data Cleanup Worksheet