This guide explains how revision control works in multi-level Bills of Materials (BOMs): what it is, why it’s complex, and which strategies manufacturers use to manage it effectively. It’s written for engineers, product managers, and operations teams transitioning from spreadsheet-based revision tracking to a structured PLM approach. By the end, you’ll understand the two primary revision control methods, their tradeoffs, and how to choose the right strategy for your organization.
Making modifications can be challenging, which is why the subject of revision management often prompts a great deal of inquiry. This is particularly difficult and crucial for firms transitioning from a revision management system primarily based on “Excel ware.” In the context where your only tool is a hammer, all issues, including those related to revision control, are treated as nails.
What Is a Multi-Level BOM?
A Bill of Materials (BOM) is a comprehensive list of raw materials, parts, assemblies, and sub-assemblies required to manufacture a product.
A multi-level BOM, in particular, represents the hierarchy of components and sub-components in complex assemblies, extending from the finished product to its simplest parts. However, as with any complex system, a multi-level BOM’s maintenance can pose significant challenges. The complexity increases manifold as each level has its own revisions, leading to a critical need for an effective revision control system.
This is where structured change control becomes essential. In multi-level BOMs, a single component change can cascade through multiple assembly levels, affecting costs, lead times, and inventory. Change Control prevents errors by making these cascading effects visible before implementation – and that is what separates a robust revision control system from a reactive one.
Revision control is the process of tracking, managing, and approving changes to product data over time, ensuring that all teams are always working from the correct, authorized BOM version.
Why Multi-Level BOM Revision Control Is Complex
A multi-level BOM is not just a single list but a set of BOMs for each level, each associated with its unique assemblies or sub-assemblies. Every assembly, sub-assembly, or part within this structure might have numerous revisions due to various factors like design changes, quality improvements, vendor changes, etc.
This multilayered structure demands a meticulous, robust, and scalable revision control system. This system would need to consider each level’s unique revisions, ensuring that the changes reflect accurately across all dependent and associated elements.
To address this complexity, manufacturers typically adopt one of two core revision control strategies – or a hybrid of both. Here’s how each works.
Naming Conventions and Hierarchy Standards
One of the most overlooked foundations of effective revision control is consistent naming conventions and clear hierarchy standards across all BOM levels. Without them, collaboration across engineering, procurement, and manufacturing breaks down quickly.
A common and costly example: an organization where the assembly level uses an alphabetic revision scheme (Rev A, Rev B) while the component level uses a numeric scheme (Rev 1, Rev 2). When a sub-assembly is revised and the component revision reference is updated, there is no shared language to confirm whether the component revision being referenced is the same one procurement ordered last quarter. This inconsistency creates downstream traceability failures – the kind that only surface during an audit or a field quality event.
Establishing hierarchy standards means defining, before any revision work begins, what constitutes a level, how each level is named, and what revision scheme applies uniformly across the structure. This is not a PLM configuration detail – it is a prerequisite for any revision control strategy to function reliably.
The Data Silo Problem
Naming convention gaps are compounded when different departments operate from disconnected systems. Engineering may revise a sub-assembly in the PDM system, update the revision record, and close the ECO – while procurement is still working from an Excel snapshot exported two weeks prior that doesn’t reflect the change. The result is that the correct revision exists in one system and the wrong revision drives purchasing decisions in another.
This is not an edge case. Data silos are one of the most common structural failures in multi-level BOM management, and they make revision control a local discipline rather than an organizational one. Effective revision control requires that all stakeholders – engineering, manufacturing, procurement, quality – are accessing the same live BOM data, not copies of it.
From Change Management to Revision Control: The ECO/ECN Bridge
Revision control does not begin with a version number – it begins with a change. Before any revision is created in a multi-level BOM, an Engineering Change Order (ECO) or Engineering Change Notice (ECN) should initiate and authorize that change. This is the bridge between change management and revision control that many organizations skip, and its absence is one of the primary reasons revision histories become unreliable.
An ECO defines the scope of the change, identifies all affected BOM levels, documents the rationale, and obtains the necessary approvals. Only once the ECO is approved should a new revision be created and released.
Without this upstream gate, revisions accumulate without context. Engineers update components reactively, revision numbers increment without traceability, and the BOM becomes a log of what changed rather than a record of why – and whether it was authorized. The ECO/ECN process is what gives revision control its integrity, and it is the foundation both strategies described below depend on.
Top-Down Revision Control: How It Works and When to Use It
The Top-Down approach is an overarching revision control system. It is simple but brutal. In this method, if a revision occurs at any level of the BOM, the change triggers an automatic downward revision for all associated sub-levels. This strategy ensures consistency and unity across all levels of the BOM data. But the cost of this method is high. You will be creating many-many revisions.
For example, if a component within a sub-assembly is revised, all the associated BOM levels – right up to the top – are automatically updated with this revision. This mechanism is good when you need to create a first revision baseline. It can work in some scenarios, especially with contract manufacturers.
Regardless of which revision control method you use, every revision record should include supporting details – the rationale for the change, a list of impacted parts, and updated CAD files. This ensures that the revision history is not just a version log but a complete, auditable record of product evolution.
However, while the top-down method maintains comprehensive synchronization, it may also lead to unnecessary revisions where they are not directly relevant.
Bottom-Up Mixed Revision Control: A More Flexible Approach
Unlike the top-down method, the bottom-up mixed revision control approach offers greater flexibility. Here, each item or BOM is edited independently, and the upper-level BOM only captures the latest saved revision.
This approach allows for specific, granular changes without disturbing the entire BOM data structure. For instance, a minor change in a component does not necessarily trigger a revision in the entire product line, preventing unnecessary paperwork or system updates.
In the picture above you can see 6 changes that were done to the same structure of the multi-level BOMs as before, but it didn’t cause the creation of extra revisions to all levels.
Yet, this method’s flexibility can also lead to challenges in maintaining comprehensive control and visibility across all BOM levels.
Impact analysis is a key practice for mitigating this risk – by evaluating the full scope of a change before it is implemented, teams can identify which assemblies, components, and processes will be affected across all BOM levels. This allows for informed decision-making and prevents incomplete or conflicting updates from entering the product structure.
Bottom-Up Revision is the most common approach for ongoing production, starting changes at the component or sub-assembly level.
Without diligent management, it could result in inconsistencies, especially in large and complex BOM structures. One of them is to apply FFF (Form, Fit, and Function criteria). FFF criteria are a standard engineering framework used to determine whether a component change is significant enough to require a new revision – if the changed part looks the same, connects the same way, and performs the same function, a new revision may not be necessary. We will talk about it later in future articles.
Top-Down vs Bottom-Up Mixed Revision Control: Comparison
Understanding the tradeoffs between these approaches makes it easier to define a revision management strategy that fits your organization’s specific needs.
| Top-Down | Bottom-Up Mixed | |
|---|---|---|
| Mechanism | Automatic downward | Independent editing |
| Consistency | High | Requires active management |
| Revision volume | High | Low to moderate |
| Flexibility | Low | High |
| Best for | Baselines / Contract manufacturing | Ongoing Production |
| Main risk | Unnecessary revisions | Inconsistencies if poorly managed |
Why You Need a Formal BOM Revision Management Strategy
Given the complexities of multi-level BOMs, it becomes evident that an ad-hoc approach to revision control, such as simple mechanisms applied in Excel, would fall short of the robustness required in managing changes.
In the absence of a well-planned revision management strategy, organizations risk inconsistencies, delays, and errors that could negatively impact product quality, production timelines, and overall business performance.
Engineering Change Orders (ECOs) are a core component of this strategy – they formally document why a change was made, who approved it, and what downstream impacts it carries on cost, inventory, and dependent components. Without ECOs, revision history is incomplete and difficult to audit.
A proper granular-level revision control strategy can thus be a cornerstone of a robust change management system.
There isn’t a ‘one-size-fits-all’ approach to managing revisions in multi-level BOMs. Depending on the specific requirements, an organization might find the top-down, bottom-up, or a hybrid approach most effective. Regardless of the strategy chosen, it is essential that the solution provides real-time visibility, consistency, and traceability across all levels of the BOM.
With a clear strategy in place, the final step is ensuring your tooling supports it – particularly when moving away from Excel-based tracking.
FAQ
What are the key benefits of implementing a structured BOM revision control system?
The key benefits of structured BOM revision control include:
- Full traceability: every change is logged, attributed, and recoverable
- Reduced production errors: manufacturing always works from approved, current data
- Cross-team consistency: engineering, procurement, and production share a single source of truth
- Faster change management: structured workflows replace ad-hoc, email-based approvals
- Regulatory compliance: documented revision history supports audits and quality certifications
What is the difference between top-down and bottom-up BOM revision control?
Top-down revision control automatically updates all BOM levels when a change occurs anywhere in the structure, ensuring full synchronization but generating a high volume of revisions. Bottom-up mixed revision control allows each level to be updated independently, giving teams more flexibility while keeping revision volume low. The right choice depends on your product complexity, team size, and how frequently changes occur.
How does BOM revision control support product management across the full lifecycle?
In product management, BOM revision control ensures that the product structure remains accurate and traceable from initial design through manufacturing and into maintenance. As a product evolves – through design changes, supplier updates, or quality improvements – revision control gives product managers visibility into what changed, when, and why. This supports better decision-making, reduces cross-functional miscommunication, and keeps the entire product lifecycle aligned around a single, authoritative data source.
How does revision control apply to manufacturing BOM?
Revision control applies to the manufacturing BOM by ensuring that only approved, validated versions of the product structure reach the production floor. Any uncontrolled change to a manufacturing BOM can result in production errors, non-conforming parts, or costly rework.
Why does BOM hierarchy matter for revision control?
In revision control, BOM hierarchy determines how changes propagate – a revision at one level may or may not affect levels above or below it, depending on the strategy used. Understanding your BOM hierarchy is the foundation of any effective revision control system.
How does OpenBOM handle revision control in complex product structures?
OpenBOM supports revision control across multi-level BOM data by managing each item and BOM level as an independent, revisable data object with its own revision history. Teams can apply either top-down or bottom-up revision strategies, with change requests and approval workflows controlling when and how revisions are created. This keeps complex product structures traceable and consistent without generating unnecessary revisions across unaffected levels.
Choosing the Right Revision Control Strategy for Your Multi-Level BOM Management
When a company is coming from “simple” but messy Excel revision control, we recommend making some analysis in the strategy of revision control. Your BOM is not an Excel file with all lines, but a robust product structure. It is granular and each level is defined as a separate BOM with its own revisions. A successful revision control in multi-level BOMs is a balance between flexibility and control.
Modern PLM systems achieve this by using multi-level revisioning to maintain a single source of truth across both engineering and manufacturing stages – ensuring that every team, from design through production, is always working from the same validated product structure.
It requires criteria definition when a component (or BOM) needs to be changed and up-rev to the next level. Remember, a carefully designed and executed revision control strategy is not just about managing changes – it’s about ensuring the integrity of your product and the sustainability of your business.
At OpenBOM we help you to develop a strategy to build a robust revision control system in complex multi-level structures, but still keep it simple and manageable.
REGISTER FOR FREE to check how OpenBOM can help you today.
Best, Oleg
Join our newsletter to receive a weekly portion of news, articles, and tips about OpenBOM and our community.
