Step-by-step methods for the questions that come up when production numbers do not add up. Every example uses the synthetic data behind the ProdCrest demo; none is a customer result.
The master data, definitions and history to check before production records move into a new ERP or MES: product identity, part weights, cavities, reason codes, units, dates and a parallel run, with a synthetic worked example.
Why a scrap Pareto can change its top bar when you switch from kilograms to pieces, how to convert with dated part weights, and when two bars should be read as a tie, with a synthetic worked example.
How to tell a shot count from a piece count, record active cavities and test every shift's output against machine capacity, with a synthetic example where one machine's week was entered in shots.
Seven checks that find wrong dates, product names, duplicates, missing shifts, unit mix-ups, shot counts and mismatched totals in shift logs and ERP exports, with a worked synthetic example.
How to map free-text downtime reasons to a short class list, keep “other” visible and move to fixed codes, with a synthetic example where one changeover was written seven ways.
A step-by-step method for reconciling spreadsheet production totals with ERP-confirmed output per work order: join key, tolerance, period close, reason labels and which number to report.
Missing a question?
Common questions about scope and data handling are on the questions page. If your question is not covered, write to info@prodcrest.com.