Scrap, rework, and downtime reasons: turning production losses into useful evidence

Production does not always proceed exactly as planned. Some output is scrapped, some requires rework, and some time is lost through downtime. These are different types of loss and need different explanations.

A reason code provides a consistent classification. It helps the business see patterns across orders and periods rather than rely only on unrelated free-text descriptions.

Three different conditions

Scrap describes output or material that cannot be accepted for its intended use under the relevant decision. Rework describes additional work intended to make output acceptable. Downtime describes time during which the resource is not performing the planned operation.

One event can involve more than one consequence, but the recorded quantities and times should not be combined indiscriminately. Ten minutes of downtime is not ten units of scrap, and a reworked piece is not automatically an additional finished unit.

DNA's reason structure

DNA manufacturing reason codes distinguish Scrap, Rework, and Downtime. The documented setup can also carry cost or GL implications. This makes the classification relevant to both operational improvement and financial interpretation.

The reason should describe the known cause as accurately as the evidence allows. A generic code such as Other may be necessary occasionally, but repeated use weakens analysis. Equally, assigning a precise cause without evidence can create a misleading pattern.

A practical comparison

Two orders each lose one hour. The first stops because material did not arrive at the station. The second stops because the machine failed. Treating both as low operator productivity points management toward the wrong remedy.

The first may require better supply coordination; the second may require maintenance. The quantity of lost time is similar, but the responsible process and corrective action differ.

Connecting loss with the order

Operation confirmations and quality records place the reason in context: product, order, operation, work centre, shift, and quantity or time. That context helps identify whether the issue is isolated or concentrated in a particular process.

A high scrap percentage should also have a clear denominator. Five scrapped pieces out of 20 differs from five out of 2,000. The measure needs to retain the production basis used for comparison.

Improvement rather than blame

Useful loss data supports investigation of causes. It should not encourage staff to hide problems by classifying all output as good or all time as productive. Honest recording makes the actual cost and capacity constraints visible.

DNA's classifications provide a shared vocabulary. The business uses the resulting evidence to improve supply, setup, maintenance, training, and product quality.