See Exactly Which Components Are Being Lost — Not Just That Scrap Happened
Go beyond total scrap counts and reason codes by tracking the specific components being scrapped within an assembly, sub-assembly, or routing step.
10in6 Scrap by Component gives manufacturers a more detailed view of scrap by linking component loss to the operation, product, assembly, and scrap reason behind it.
New to scrap tracking? Start with Scrap Tracking first.
Standard scrap tracking tells you that loss occurred.
Sometimes that is enough. But in more complex assembly environments, it is not enough to know that a part or assembly was scrapped. The real question is which components inside that assembly were lost, at which operation, and for which reason.
Without that level of detail, the plant may know scrap is high without knowing whether the loss is concentrated in a specific component, a specific operation, a specific assembly step, a specific scrap reason, or a specific product routing.
That makes follow-up slower and ERP entry more manual than it needs to be.
10in6 Scrap by Component changes that by tracking component-level loss directly inside the scrap workflow.
How Scrap by Component fits with Scrap Tracking
Scrap Tracking
- What was scrapped
- Where it happened (line, shift, product)
- Why it happened (reason code)
- Which production period was affected
Scrap by Component
- Which specific components inside the assembly were lost
- How many of each component were scrapped
- Which operation those components were associated with
- Which scrap reason ties to which component
For most operations, Scrap Tracking is the right starting point. For operations that need deeper root-cause visibility, more detailed reporting, or easier ERP entry, Scrap by Component adds that additional precision.
See Scrap Tracking →How 10in6 Scrap by Component works
10in6 provides a configuration layer that allows the plant to define which components can be scrapped from a given part, sub-assembly, or routing step. Once configured, the operator is shown only the relevant choices for the situation.
In one configuration, components are associated with specific operations in a product routing map, and default scrap quantities can be set by operation to reduce operator effort. In another, components are associated with specific scrap reasons for each product. Both approaches are designed to show the operator only the relevant choices for their situation — reducing confusion and entry errors.
What you can capture
Component-level scrap quantities
Record how many of one or more components were scrapped as part of a scrap event, instead of only recording the assembly-level loss.
Component-to-operation relationships
Associate components with specific operations or routing steps so the entry process reflects how the product is actually built.
Component-to-reason relationships
Where needed, associate components with specific scrap reasons so the system can narrow the valid choices based on the failure mode being recorded.
Product and assembly context
Tie component scrap back to the product, assembly, or sub-assembly so the loss is not viewed in isolation.
Shift-level entry history
Give users visibility into all entries made during the selected shift so the team can review what has already been recorded.
Operator-friendly entry workflow
Use a dedicated component scrap editor that minimizes confusion by showing only the components valid for the selected operation, product, or scrap reason.
With 10in6 Scrap by Component, your team can:
- Move from assembly-level scrap to component-level visibility
- See which specific components are being lost most often
- Understand whether the same operation or reason is driving repeated loss
- Summarize component-level scrap for cleaner ERP handoff
- Support more precise root-cause conversations across teams
- Build a component-level history that grows more useful over time
- Scrapped components can be automatically backflushed to ERP
In many operations, scrap analysis stops too early
The plant knows the assembly was lost, but not which component inside it is driving the repeated cost. That makes it harder to answer which components are being lost most often, whether a specific routing step is driving the loss, and whether the same issue is affecting multiple products or assemblies.
Scrap by Component gives the team a more precise view of where the loss is concentrated. That leads to better follow-up, better reporting, and better root-cause conversations.
Connected to the rest of your platform
Scrap by Component questions
- How is Scrap by Component different from Scrap Tracking?
- Scrap Tracking gives the broader view of scrap by reason, product, line, and shift. Scrap by Component adds a deeper layer by showing which specific components inside the assembly were scrapped, at which operation, and for which reason.
- Do we have to configure components ahead of time?
- Yes. The system is configured so valid components are associated with operations, routing steps, products, or scrap reasons depending on the workflow design. This is what allows the operator to see only the relevant choices during entry.
- Can the system limit what operators see during entry?
- Yes. Users are shown only the components relevant to the selected operation or scrap reason in order to reduce confusion and entry errors.
- Can operators enter more than one scrapped component in a single event?
- Yes. The component scrap editor allows users to enter quantities for one or more components that are to be scrapped as part of a single entry.
- What reports are available?
- Scrap by Component supports a Scrap Component Summary Report and a Scrap Detail Report, covering component type, scrap reason, assembly, date and time, and entry-level detail.
- Is Scrap by Component necessary for every plant?
- No. Most plants can start with Scrap Tracking. Scrap by Component is most valuable when assemblies are more complex and the team needs more precise component-level loss analysis or cleaner ERP entry for component-level scrap.
Need this configured around your actual equipment and workflows?
Every 10in6 deployment includes our team — connecting your equipment, configuring your workflows, and supporting your operation long after go-live.
Go beyond scrap totals and see exactly what is being lost.
See how 10in6 Scrap by Component adds the next level of scrap detail for operations that need deeper visibility into recurring loss.