Prepyr

Analyze manufacturing defects by batch, machine, and shift

Compare defect rates using inspected or produced units as the denominator, then trace changes across material, machine, method, environment, and measurement context. Start with the what one row represents and definitions, calculate only from eligible records, and check the result against the source before using it.

Where the difficulty begins

Production, quality, maintenance, and material records use batch, work-order, or timestamp grains. Rework can be counted twice, inspection intensity varies, and defect codes change across inspectors.

From the field · Quality engineer

Compare defect rates using inspected or produced units as the denominator, then trace changes across material, machine, method, environment, and measurement context.

Production, quality, maintenance, and material records use batch, work-order, or timestamp grains. Rework can be counted twice, inspection intensity varies, and defect codes change across inspectors.

Columns used in the example

work_order · batch_id · machine_id · shift · material_lot · units_produced · units_inspected · defect_code · rework_flag · scrap_quantity

Follow it with your own file

  1. Map production and inspection records to one approved batch and work-order hierarchy.
  2. Standardize defect codes and distinguish first-pass, rework, and final outcomes.
  3. Calculate rates with visible inspected and produced denominators, then compare stable peer groups.
  4. Use time, maintenance, material, and environment evidence to test explanations for material changes.

Check: Good, reworked, and scrapped units must reconcile to the defined production population, with inspection coverage reported beside defect rates.

Check the source before you publish

  • what one row represents and eligible population documented
  • Dates, units, currencies, and identifiers validated
  • Good, reworked, and scrapped units must reconcile to the defined production population, with inspection coverage reported beside defect rates.
  • Exceptions retained for human review
  • Published result links back to its evidence

Build the result step by step

  1. Define the decision: Map production and inspection records to one approved batch and work-order hierarchy.
  2. Prepare the evidence: Standardize defect codes and distinguish first-pass, rework, and final outcomes.
  3. Calculate the result: Calculate rates with visible inspected and produced denominators, then compare stable peer groups.
  4. Review the exceptions: Use time, maintenance, material, and environment evidence to test explanations for material changes.

What may be distorting the answer

  • The source files do not share one documented what one row represents or cutoff.
  • The decision owner cannot trace the headline result to eligible source records.
  • A lower defect rate during a period of lower inspection coverage may be a measurement change, not improved process quality.

What a useful answer looks like

Compare defect rates using inspected or produced units as the denominator, then trace changes across material, machine, method, environment, and measurement context.

Where judgment still matters

A lower defect rate during a period of lower inspection coverage may be a measurement change, not improved process quality.

Decide how much review the task needs

ApproachWhat it answersWhat remains at risk
Quick spreadsheet totalA narrow descriptive questionDefinitions, duplicate rows, timing, and exceptions may be hidden
Reviewed analysisThe stated decision with reconciled evidenceHuman judgment is still required for policy and action
Ongoing monitored workflowThe same decision across new periodsunexpected column changes and changed business rules still need review

The decisions that matter

  • Compare defect rates using inspected or produced units as the denominator, then trace changes across material, machine, method, environment, and measurement context.
  • Good, reworked, and scrapped units must reconcile to the defined production population, with inspection coverage reported beside defect rates.
  • A lower defect rate during a period of lower inspection coverage may be a measurement change, not improved process quality.

Doing these steps in Prepyr

Prepyr accepts CSV files only. Export the worksheet or table you need as a UTF-8 CSV first; workbook formulas, formatting, macros, charts, and other sheets will not be included. Describe the result you need: Analyze manufacturing defects by batch machine and shift. Check the columns selected, preview any proposed changes, and compare the output with the source before applying or exporting it.

Prepyr steps used here: Statistical Profiling · ML Classification · Feature Importance · Model Comparison

A decision-ready result for “Analyze manufacturing defects by batch machine and shift,” with its assumptions, exceptions, and source totals still visible.

Questions readers usually ask next

Can this quality engineer analysis be done in Excel?

Yes for a small, stable file. Keep the source unchanged, document formulas and exclusions, and check outputs against the source.

What should not be automated?

Do not automate the final policy or business judgment. A lower defect rate during a period of lower inspection coverage may be a measurement change, not improved process quality.