See Which Components Inside an Assembly Are Being Scrapped
Record the specific components scrapped at each assembly, sub-assembly or routing step, alongside the usual reason code.
10in6 Scrap by Component ties each component loss to the operation, product, assembly and scrap reason behind it.
New to scrap tracking? Start with Scrap Tracking first.
One scrapped assembly, one line on the scrap report
When an assembly is scrapped partway down the line, the scrap entry usually records one assembly and one reason. For a simple product that is enough. For an assembly built from components of very different value, it leaves out which components went in the bin, at which operation, and why.
Scrap can then look high without anyone being able to say whether the loss sits in one component, one assembly step or one product routing. Follow-up takes longer, and someone has to work out the component scrap for the ERP by hand.
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
Scrap by Component adds to Scrap Tracking rather than replacing it. Scrap reporting by reason, line, shift and product carries on as before, with the components behind each loss added on top. It is worth adding on lines where root-cause work, detailed reporting or ERP scrap entries need component-level figures.
See Scrap Tracking →How 10in6 Scrap by Component works
During setup, the plant defines which components can be scrapped from each part, sub-assembly or routing step.
There are two common setups. In one, components are mapped to operations in the product's routing, and a default scrap quantity can be set for each operation so the operator has less to type. In the other, components are mapped to scrap reasons for each product. Both keep the operator's list short, which cuts entry errors.
What you can capture
Component-level scrap quantities
Record how many of each component were scrapped in a single scrap event, alongside the assembly.
Component-to-operation relationships
Link components to specific operations or routing steps, so entry follows how the product is built.
Component-to-reason relationships
Where needed, link components to scrap reasons, so picking a failure mode narrows the component list.
Product and assembly context
Each component entry carries the product, assembly or sub-assembly it came from.
Shift-level entry history
Review every entry made during the selected shift before adding more.
Operator-friendly entry workflow
A dedicated component scrap editor lists only the components valid for the selected operation, product or scrap reason.
Where component scrap data goes
Scrap by Component questions
- Why track scrap at the component level?
- Because an assembly-level scrap count hides where the money went. Component-level records show which parts are lost most often and at which operation, make scrap cost accurate when components differ in value, and keep component inventory and ERP scrap entries correct without manual adjustment.
- How is Scrap by Component different from Scrap Tracking?
- Scrap Tracking records scrap by reason, product, line and shift. Scrap by Component adds the component detail underneath: which parts of the assembly were lost, the operation where it happened, and the reason.
- Do we have to configure components ahead of time?
- Yes. Valid components are associated with operations, routing steps, products or scrap reasons, depending on how the workflow is designed. That setup is what lets the operator 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. Scrap Tracking is the usual starting point. 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.
Set up around how your plant runs
Standardized platforms expect the plant to change to fit the software. Do-it-yourself platforms leave your team to build and maintain everything. With 10in6, we configure the system around your equipment, codes and reports, and your team runs it day to day.
Your equipment, codes and reports
Your checks, intervals and forms set up per line and product, and traceability built around your part numbers and your customers’ requirements.
Your team runs it day to day
Operators, downtime and scrap codes, products and targets, shift schedules, checks, alerts, emailed reports and real-time boards are managed by your own people. Everyday changes need no support ticket and no invoice.
A project manager for the bigger things
New machines, new modules and custom reports go through a 10in6 project manager who already knows your deployment, so nothing starts from scratch. If you would rather we made everyday changes too, we can.
Still here years later
The system keeps being refined after go-live, and new capabilities are added without rebuilding it. Some of our customer relationships have run for 12 years, and 97% of customers say they would never go back.
“Our 10in6 Project Manager has been very responsive and the software is flexible enough to be configured to our specific needs.”
How the 10in6 delivery model works →
Find out which components your scrap is made of.
See how component scrap is entered at the station and reported by component, operation and reason.