Shopfloor

Manufacturing performance: pace, losses and quality

Work from demand and the line constraint to OEE, downtime, changeovers, capability and a realistic improvement case.

This sequence connects production metrics to decisions. The outcome is a one-page improvement hypothesis with a consistent time boundary, loss mechanism, owner and verification measure. Use illustrative inputs first, then adapt the definitions to your operation.

FIG. 03At the inspection gate
Flow. Inspect. Improve. Work moves through an inspection station. Cycle time, stops and accepted output describe different parts of this flow; measure each separately.

1. Separate the clocks

Read takt, cycle and lead time. Reproduce the 45-second takt example in the takt calculator. Write the shift, excluded breaks and demand period beside the result.

2. Find the constraint

Read line balancing and capacity. Use the capacity calculator to compare ideal output with availability and yield losses. Explain why serial stations cannot be counted as independent parallel lanes.

3. Reconcile losses

Read the OEE loss tree and downtime reason-code design. Use the OEE calculator and downtime log to preserve planned time, run time and causes without overlapping line-stop intervals.

4. Choose a targeted intervention

For setup losses, use the SMED guide and observation sheet. For repeated failures, use MTBF and MTTR. Name the mechanism you expect to change, not merely the dashboard percentage.

5. Keep quality visible

Read first pass and rolled throughput yield and capability indices. Try the sample statistics and capability tools. Preserve subgroup and time information rather than accepting a high index as proof of stability.

6. Verify the benefit

Read the automation business-case guide. Test a conservative scenario in the ROI calculator. State how recovered time becomes shipped good units, avoided cost or useful flexibility.

Deliverable

Write the current boundary, leading loss, proposed change, expected mechanism and before/after observation window. Include a condition that would disprove your hypothesis. This keeps the improvement review grounded in operational evidence.