BOM revisions

A product name alone cannot explain which assembly structure the team reviewed. A BOM revision gives Production Planner a product reference, a revision label and an effective window. Status distinguishes Draft, Review, Released and Obsolete. Use these records to establish the intended structure before the shop receives instructions, with the earlier revision still available for comparison when an assembly changes.

The revision workflow checks an identified product and revision, a valid interval and an unreleased structure before moving Draft to Review. That result means the draft passed its submission checks. Manager decides whether the reviewed structure may be released. An operator should be able to distinguish a submitted revision from the structure the manager has authorized for use.

• Product identity. Link the product to the intended item record. Item code and name help the planner distinguish similar assemblies; a new text label should not become another product merely because an import uses different spelling.
• Effective window. Enter effective start and effective end deliberately. Agree how the team interprets the dates and checks competing windows. Manager reviews the dates with Production Planner before authorizing the structure for use.
• Release decision. Keep Draft preparation, Review submission and Released use separate. A later component substitution needs an editable revision and a reviewed change rather than an overwrite of the structure people have already used.

Agree revision naming with the people who maintain assembly instructions. Configure the revision release action for the Manager who will decide it. Assign draft preparation and change requests to Production Planner. Rehearse those permissions with the actual planner and approver accounts before relying on the review queue.

Also agree the production handoff. Production Planner checks the intended revision alongside the work order and communicates it through the team’s assembly instructions. Decide where the operator finds those instructions and who replaces an earlier copy after release. Rehearse this handoff with the people who prepare and run the work.

Use a demonstration assembly whose current structure is revision A. Prepare revision B with a changed effective interval and a replacement component, retaining A as the released structure while B is reviewed. Submit B with the revision workflow, keep A intact and ask the reviewer to explain what still needs a decision before B is used.

Ask Manager to review the structure and decide whether B may become Released through the release action. Then ask Production Planner to identify which revision the next work order should use. Include an order whose required date falls near the change. The planner should explain the chosen structure and show the operator the instructions for that run.

• BOM revision drafts — Product, revision and dates together before submission.
• Revision review — Structures waiting for the release decision.
• Released revisions — Released structures with effective dates for the planner to check before the handoff.

Revision preparation and release covers the submission and decision. Use engineering change review when replacing an existing structure, then review implementation.