How to Preserve Your BOM at Key Product Development Milestones

Arena BOM Snapshot provides teams with a permanent, trustworthy record of the product configuration at the milestones that matter, from a pilot build or supplier commitment to a quality investigation or compliance event. The effective bill of materials (BOM) can continue to evolve through routine change processes, while the preserved snapshot remains a stable reference point. With this capability, teams can intentionally preserve that record and refer to it later with confidence.

Product development doesn’t stand still. While teams coordinate sourcing, prepare for quality inspections, evaluate costs, ramp up production, and work toward delivery targets, bills of materials (BOMs) continue to evolve.

Sooner or later, these activities raise a critical question:

“What exact product configuration did we build, ship, certify, or commit to at that particular milestone?”

To answer it confidently, product teams need a point-in-time view of a BOM, including subassembly and component revisions, without disrupting ongoing development. Arena’s BOM Snapshot capability provides that historical reference point by preserving a complete, trusted record of a product configuration at a specific moment in time.

We sat down with Arena Senior Product Manager Pär Svensson to discuss how it works and where it delivers the greatest value.

Pär, how would you describe Arena BOM Snapshot?

Pär: Arena BOM Snapshot preserves the full BOM structure and associated data as a fixed, read-only point-in-time record. Users can create a snapshot from an effective or superseded revision at a meaningful product development milestone, establishing a permanent record that remains unchanged as subsequent revisions and engineering change orders (ECOs) move forward.

Think of it as freezing the BOM at a significant moment in its history. Teams can go back to that snapshot to see the BOM data as it existed then, while development continues.

What information does a BOM snapshot preserve?

Pär: BOM snapshot preserves much more than a list of components. It captures a comprehensive view of the product configuration, including:

• Item number, name, category, and phase
• Quantities
• Costs
• File associations
• Component substitutes
• Reference designators
• Notes
• Sourcing relationships
• Custom attributes

This information gives teams a complete historical record that they can reference long after the product has evolved.

What are some common use cases for Arena BOM Snapshot?

Pär: Teams create snapshots whenever they need to preserve a trusted BOM record at key events such as:

• Releasing a product to manufacturing
• Establishing a configuration baseline
• Preparing evidence for a regulatory audit or internal review
• Providing suppliers and manufacturing partners with a stable product reference
• Retaining product records for quality investigations, costing, or sourcing activities

Consider a quality investigation:

A team discovers a compliance issue in an effective product assembly and captures a snapshot before making the corrective change. After the corrected revision takes effect, the live BOM moves forward with the compliant configuration. The snapshot, however, preserves the earlier configuration and affected parts for future reference.

How does Arena BOM Snapshot differ from BOM History?

Pär: That’s probably the question I receive most often. The two capabilities are complementary but serve different purposes.

Arena BOM History provides an on-demand, read-only view of a BOM at a prior release or selected past date based on revision, effective date, and phase information. It helps teams investigate what was effective at a particular time, compare past states, and understand how the BOM evolved without requiring a snapshot to have been created in advance. A BOM history view captures less data than a BOM snapshot

By contrast, Arena BOM Snapshot captures and preserves the full BOM structure as a fixed, read-only record at a defined point in time. It provides a permanent baseline that remains unchanged as subsequent revisions move forward.

A simple way to distinguish the two is:

• BOM history answers: “What BOM structure and effective revisions were in place at this release or on this past date?”
• BOM snapshot answers: “What complete BOM configuration and associated data did we deliberately preserve at this milestone?”

How does a user create a BOM snapshot in Arena PLM and QMS?

Pär: Users with the required Arena access can create a snapshot from an effective or superseded revision through the Snapshot menu. They simply select “Create Snapshot,” enter or accept a name, add a description if needed, and save. Arena preserves the supported item and BOM views as they appear at capture, without requiring an ECO or changing the effective BOM.

When a user creates a snapshot of an assembly, Arena also captures the subassemblies and components within its BOM. The top-level assembly is captured as a direct snapshot, while its subassemblies and components are captured as an indirect snapshot. Users can navigate between the direct and indirect snapshots while remaining in the preserved product context.

Which teams benefit most from Arena BOM Snapshot?

Pär: BOM snapshot provides value across the entire product organization. Quality and compliance teams gain a lasting record to support audits and reviews. Supply chain and sourcing teams can reference accurate product information when collaborating with suppliers. Manufacturing teams have a trusted record of the BOM at key milestones, while engineering teams can establish reliable configuration baselines.

Ultimately, everyone has a shared point-in-time reference they can rely on as the product continues to evolve.

What business impact do you expect customers to see with Arena BOM Snapshot?

Pär: It really comes down to confidence.

When organizations can easily preserve and reference complete product configurations, they spend less time reconstructing the past and more time making informed decisions. They improve traceability, simplify supplier collaboration, and strengthen configuration control.

As products become more complex and compliance requirements increase, having a trusted record of what the product looked like at a specific milestone becomes increasingly valuable.

Learn more about Arena’s BOM management capabilities. Request a demo.