ForgeShiftCompass
Visibility and DataPractice D1

Throughput Monitoring

Throughput Monitoring tracks parts produced against target on an hour-by-hour cadence, with reasons captured for every miss — so deviations are caught and acted on the same shift.

  • Assessment3 questions
  • Templates1
  • Root causeISHIKAWA-6M

What world-class looks like

Every shift tracks parts produced vs target, good vs scrap, and target vs actual cycle time on an hour-by-hour cadence; deviations trigger investigation and action the same day.

How mature is your operation?

These are the questions Compass asks for this practice, and the levels it scores you against.

Production targets and reason codes

Per-shift production targets, with documented reason codes for any miss.

Do you set production targets per shift and document the reason when you miss them?

Level 1 → 5World class at level 4

  1. No formal targets — we run what we run
  2. Daily target only; misses are noted informally
  3. Per-shift target with an end-of-shift reason if missed
  4. Hour-by-hour target with a documented reason code per missWorld class
  5. Real-time target tracking with reason codes captured on every deviation event

Hourly production tracking

How parts produced (target, actual, good, scrap) and cycle time are captured during the shift.

How do you capture parts produced and cycle time during the shift?

Level 1 → 5World class at level 4

  1. We don't track parts produced or cycle time during the shift
  2. Operator estimates total parts at end of shift
  3. Paper or spreadsheet tally — actual vs target, good vs scrap
  4. Tablet-based hour-by-hour tracking with target, actual, good, scrap, and cycle timeWorld class
  5. Automatic part counters feed a live production board against target

Throughput review and action

Cadence of throughput review and action ownership.

How often is throughput vs target reviewed and what happens as a result?

Level 1 → 5World class at level 4

  1. Not reviewed
  2. Occasionally, when an obvious miss happens
  3. Monthly review; limited action taken
  4. Daily shift huddle — top miss reason gets an owner and dateWorld class
  5. Real-time board on the floor; top miss reason addressed each shift with documented action

Where to start

  • Operator-entered hour-by-hour tracking

    Visibility · L1→L2 · Low complexityCloses · Hourly production tracking
  • Automated part counting via GLYPH passive capture

    Visibility · L2→L3 · Medium complexityCloses · Hourly production tracking
Root-cause methodISHIKAWA-6M

Next steps

Scoring your operation against Throughput Monitoring takes a few minutes and needs no account.