These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- BOM Management
- Features
- Component structure
Component structure
Review each component quantity, stated unit and scrap allowance against its editable parent revision.
OverviewDraft component structure×
BOM Management · Component structure
New
Draft component structure
Approval waits for the manager
| Id | Revision | Component | Quantity per | Unit | Scrap percent | |
|---|---|---|---|---|---|---|
| IDD-321 | BMR-7974 | ITM-4100 | 490 | UNT-297 | 10 | |
| IDD-418 | BMR-5115 | ITM-8211 | 800 | UNT-166 | 16 | |
| IDD-844 | BMR-2882 | ITM-5525 | 50 | UNT-525 | 18 | |
| IDD-954 | BMR-8728 | ITM-2480 | 850 | UNT-545 | 4 | |
| IDD-955 | BMR-1430 | ITM-1527 | 490 | UNT-749 | 17 |
6 of 6 records
IDD-321BOM components · BMC-81528
RevisionBMR-7974
ComponentITM-4100
Quantity per490
UnitUNT-297
Scrap percent10
What you can do
Make the assembly requirement explicit
The planner needs to know what goes into an assembly before deciding whether its structure is ready for review. A component line holds the revision and component references with quantity per assembly, unit and scrap percentage. Each line belongs to a specific BOM revision. The component reference resolves to an item record, so similar component names can be checked against the actual item identity used in purchasing and stock records.
The component workflow requires a positive quantity, a stated unit and a scrap percentage within the permitted range. Its parent revision must not be Released. Validation confirms an eligible structure once and keeps the review focused on the parent revision. Describe a component as validated only after the guard accepts it, and inspect revision status when deciding whether the parent remains editable.
How the work is organized
- Quantity per assembly. Record quantity per assembly with its intended unit. The field describes the assembly requirement; it does not create a material issue or prove that stock has been reserved for a production run.
- Component reference. Select an existing item for the component and link the line to the correct parent revision. The parent product and revision status provide context when the planner is checking lines outside the revision header.
- Scrap allowance. State scrap percentage deliberately and review its meaning with the operator. The validation range is zero through one hundred. Discuss the allowance with Production Planner when agreeing the material quantities for the run.
What to agree during setup
Agree the relationship between the unit on a component line and the unit on its item record before importing quantities. Where a supplier source uses packs and production uses individual pieces, settle the quantity and unit in the source data. Ask the planner and operator to explain the same requirement using the assembly instructions. Record the agreed unit consistently before loading component quantities.
Choose who may edit component lines during Draft and Review and how the Manager receives a complete structure for release. Configure access to prevent an operator from changing a released requirement. Test the actual workflow guard as well as the screen: a hidden edit button is insufficient evidence that a direct write is rejected.
Check the handoff on an actual case
Prepare an example assembly with a fastening component whose quantity per assembly is four and whose unit is each. Add the line to an editable revision and validate it. In the rehearsal, try a zero quantity and an omitted unit; both should be rejected by the component workflow rather than becoming an apparently usable structure.
Then set scrap percentage outside the permitted range and verify rejection. Release the parent through the engineering decision and attempt to validate a changed component against it. That action must fail because the parent is Released. Prepare the replacement line on a new editable revision instead. Finally, compare the reviewed line with the operator’s instruction source so the same unit and quantity survive the manual production handoff.
What your team sees
- Draft component structure — Components, quantities, units and allowances on Draft revisions.
- Revision board — Revisions grouped by their review and release status.
- Revision review — The header whose complete structure is being considered.
Follow the work through
Use revision preparation and release to validate the structure. Follow engineering change review for substitutions, and settle source references in the data model.
What it keeps track of
Data model- BOM components
- Component lines within a BOM revision.
- BOM revisions
- Bill-of-materials revisions for a product.
- Items
- Materials, components and finished goods.
Who uses it
Permissions- Production Planner
- , Manager, Production Operator, Admin.
- Production Planner
- Prepares lines, and Production Operator checks operating meaning during rehearsal.
- Manager
- Decides the structure release, and Admin maintains the agreed master-data access.
Set up BOM Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.