Discrete ManufacturingFree calculatorPDF, Excel, Word exportDiscrete Manufacturing

Process Cycle Efficiency Calculator

Process cycle efficiency compares the time your product is being worked on with the time it spends in the system. In most factories it comes out in single digits, which shows where improvement effort belongs: waiting.

Your numbers

min

Time the product is actually transformed in a way the customer pays for.

min

Inspection, setup share, handling that cannot yet be removed.

min
960 min

Time the work sits between steps.

%

Your results

Process cycle efficiency
1.2%
Lead time needed to hit target PCE
60 min
Total lead time
1,035 min
Total lead time in hours
17 hrs
Share of lead time spent waiting
92.8%
Lead time to remove
975 min
Save results:

PCE (%) as waiting time changes

Sweeps Waiting and queue time from 0 to 2000, holding your other inputs fixed.

Measure lead time from ERP timestamps

An optional walkthrough of extracting order lead time and queue time from ERP data.

Optional. The tool and every export work without this. No spam.

How to use it

Take the numbers from a value stream map or a product traced through the floor. Enter value-added time, required non-value-added time, move time and waiting time for one unit or one order. The total is the lead time. PCE is value-added time divided by that total. Set a target PCE to see how short the total lead time would need to be with the value-added content unchanged.

The formula and its benchmarks

PCE equals value-added time divided by total lead time, expressed as a percentage. It is the same ratio as the value-added ratio on a value stream map timeline. A typical discrete job shop sits below 5 percent, many assembly lines at 5 to 15 percent, and well-run flow lines at 25 percent or more. Treat these as rough guides, since they depend on how strictly you define value-added.

  • PCE = value-added / total lead time
  • World-class flow is often quoted above 25 percent
  • Job shops are commonly below 5 percent
  • Define value-added from the customer's view

Reading the result

Notice how the chart falls steeply as waiting grows. Because value-added time is usually small, cutting waiting by half often does more than any speed-up of the machine itself. Look at the wait share: if it is above 80 percent, work on batch size, scheduling and WIP limits before touching cycle times. Pair this with Little's Law to link the waiting to the WIP you hold.

Common mistakes

Counting all machine time as value-added overstates PCE, since setup and rework are not paid for by the customer. Using standard routing times while measuring lead time from actual dates mixes bases. Measure both from the same sample. Also keep the unit consistent: one piece, one batch or one order, not a mixture. ERP order timestamps can supply the lead time, but touch time usually comes from the floor.

  • Counting setup as value-added
  • Mixing routing and actual data
  • Inconsistent unit of measure
  • Using the average of orders with different routes

Frequently Asked Questions

What counts as value-added?

Work that changes the product's form, fit or function, which the customer is willing to pay for and which is done right the first time. Inspection, moves and setups are generally not value-added.

Is a low PCE bad?

It is normal and it shows opportunity. A job shop with low PCE may be appropriate for its mix. The point is to measure it, set a target and track progress by product family.

How is PCE different from OEE?

OEE measures machine effectiveness over planned time. PCE measures the proportion of a product's total time in the process that adds value. They answer different questions.

How do I measure waiting time?

Subtract touch and move time from total lead time, or track queue times between steps using order timestamps, a data collection system or a simple tag on the first order of the day.

Netray can help calculate lead time from ERP order dates and compare it with routed touch time, to give a PCE per product family.