BILL OF MATERIALS INTELLIGENCE

Four views.
One truth.
Zero drift.

Engineering's BOM differs from manufacturing's. Manufacturing's differs from procurement's. Procurement's differs from service's. And the actual as-built configuration? That lives in Excel. Lattice ends this permanently.

LIVE MULTI-VIEW BOM — PRODUCT AX-7200 REV D
eBOM · AS-DESIGNED
Engineering BOM
Functional structure from CAD
342 components
mBOM · AS-PLANNED
Manufacturing BOM
Assembly sequence optimized
389 line items
sBOM · AS-SERVICED
Service BOM
Field-replaceable units + kits
127 service items
aBOM · AS-BUILT
Serialized BOM
Unit SN-48720 actual config
100% traced
Cross-view reconciliation: 3 discrepancies detected, 2 auto-resolved
eBOM Rev D added PN-4420-B titanium bracket · mBOM routing updated · sBOM kit K-220 regenerated · 1 pending: supplier AVL mismatch on PN-6180
RECONCILING
THE COST OF BOM INACCURACY

The BOM is the single most critical data structure in manufacturing — and the one PLM systems manage worst.

Every BOM error propagates downstream: wrong parts ordered, wrong assemblies built, wrong kits shipped to the field.

91%
Average BOM accuracy sounds acceptable — until you realize 9% error translates to $1.8M annually in scrap, rework, and wrong-parts-ordered
FORGE AXIOM DEPLOYMENT DATA
Drift
Engineering BOM, manufacturing BOM, service BOM, and as-built records inevitably diverge when managed in separate systems
OPENBOM / INDUSTRY ANALYSIS
Excel
The as-maintained BOM for field assets is still managed in spreadsheets at most manufacturers — disconnected from engineering and ERP
BEYOND PLM 2025
150%
Configurable products require 150% BOMs containing all possible variants — resolved to buildable 100% configurations per order in milliseconds
INDUSTRY STANDARD

Ask 10 engineers what a BOM is, and you will get 15 answers. That is because BOMs are shaped by purpose: a design BOM is not the same as a manufacturing BOM, which is different from a service BOM, which is different from a serialized as-built record. In most organizations, each of these views lives in a different system — PLM, ERP, field service CRM, Excel — and they drift apart the moment they are created. Lattice manages all four views in a single reconciled data model.

Lattice is not a BOM editor grafted onto a PLM system. It is a graph-native, multi-view BOM architecture built into the Axiom product knowledge graph. The engineering BOM reflects how the product is designed. The manufacturing BOM reflects how it is built. The service BOM reflects how it is maintained. The as-built BOM records exactly what was installed in each serialized unit. Changes in any view propagate to affected views with configurable reconciliation rules. Variant and options configuration supports product families with millions of valid combinations — resolved in milliseconds. Because the BOM is not a spreadsheet. It is the skeleton of your product.

WHY LATTICE

Five capabilities that transform the BOM from a fragmented artifact into a unified product definition.

Four Views, One Data Model
eBOM, mBOM, sBOM, aBOM — all managed in a single reconciled graph. Changes in the engineering BOM automatically propagate to manufacturing, service, and as-built views with configurable reconciliation rules. No middleware. No manual sync.
Four BOM views reconciled in real time within a single data model
150% Variant Configuration
Master BOMs containing all possible options across all product variants, with rule-based configuration that resolves to a buildable 100% BOM for each customer order. Millions of valid combinations resolved in milliseconds.
Millions of variant combinations resolved to buildable BOMs in <1 second
Sub-Second BOM Explosion
Where-used queries, multi-level BOM explosions, and cross-reference lookups across 50,000+ components complete in sub-second response time. Because Rust compiles to native code with zero runtime overhead.
BOM explosion across 50,000+ components in <1 second
Native ERP Synchronization
Axiom's BOM is the ERP's BOM. No middleware translation layer. No "certified connector." Engineering changes propagate to manufacturing planning in real time. The as-designed and the as-built are one data model.
Zero integration middleware between PLM BOM and ERP BOM
Serialized As-Built Traceability
Every unit that ships has a serialized as-built record — capturing the exact configuration installed, including any deviations, substitutions, or rework performed during manufacturing. Full traceability from as-designed intent to as-built reality.
100% as-built traceability for every serialized unit shipped
BOM INTELLIGENCE ENGINES

Eight engines. Every component traced.

From CAD extraction through variant configuration to serialized as-built records — Lattice governs every BOM view, every reconciliation, and every cost roll-up.

01
Multi-View BOM Architecture
eBOM · mBOM · sBOM · aBOM · Unified graph model · Cross-view reconciliation · Drift prevention
▼
The fundamental problem with BOM management is structural: each department needs a different view of the same product, and each view lives in a different system. Engineering's eBOM reflects functional decomposition from CAD. Manufacturing's mBOM reflects assembly sequences and workstation assignments. Service's sBOM reflects field-replaceable units and repair kits. The as-built aBOM records what was actually installed in each serialized unit. In traditional PLM, these are separate data structures maintained by separate teams — and they drift apart immediately. Lattice manages all four views as interconnected perspectives on a single product graph. When a component changes in the eBOM, the system identifies every affected mBOM routing, every impacted sBOM kit, and every as-built record that may require field retrofit assessment. Cross-view reconciliation runs continuously, detecting discrepancies the moment they appear.
Graph-native multi-view architecture — all four BOM views exist as interconnected perspectives on the same product data graph. A component is one node with four view-specific contexts, not four copies in four systems
Continuous reconciliation engine — monitors all four views for discrepancies in real time. When engineering adds a component to the eBOM, manufacturing is notified to update routings. When manufacturing substitutes a process material, engineering is notified for approval
View-specific structure transformation — the same product can have completely different hierarchies in each view: eBOM organized by functional system, mBOM by assembly station, sBOM by service module, aBOM by serial number. All linked, all reconciled
Drift prevention with audit trail — every cross-view discrepancy is logged with timestamp, source, and resolution. Audit-ready evidence that all BOM views are consistent with the master product definition at any point in time
4
BOM views reconciled in single data model
Real-time
Cross-view discrepancy detection
Zero
BOM drift between engineering and manufacturing
Graph
Native architecture (not file-folder hierarchy)
02
Variant & Options Configuration
150% super-BOM · Rule-based resolution · Product family management · Order-specific configuration
▼
Configurable products present a combinatorial explosion that spreadsheet BOMs cannot handle. A product family with 8 option categories and 5 choices per category produces 390,625 valid configurations. A 150% BOM contains every possible component across every variant. Configuration rules define which components are included, excluded, or substituted for each order. Lattice manages 150% super-BOMs with constraint-based rules that resolve to buildable 100% configurations in milliseconds. Rules enforce technical compatibility (this motor requires this controller), regulatory compliance (this market requires this certification), and commercial logic (this option package includes these features). Invalid configurations are blocked before they reach manufacturing.
150% super-BOM management — master BOM containing all possible components across all variants. Each component tagged with effectivity conditions: option codes, market codes, regulatory codes, and customer-specific configurations
Constraint-based configuration rules — technical (this pump requires this seal material), regulatory (EU market requires CE marking components), commercial (option package A includes features X, Y, Z). Rules enforced at configuration time, not discovered at assembly time
Order-specific BOM generation — from a validated configuration, Lattice generates a 100% buildable BOM with exact quantities, routings, and work instructions for that specific order. No manual BOM editing for configured products
Configuration impact analysis — when an engineering change affects a component in the 150% BOM, Lattice identifies every product configuration that includes that component and every open order that would be affected
Millions
Valid configurations supported per product family
<1s
Configuration resolution time
Zero
Invalid configurations reaching manufacturing
Auto
Order-specific BOM + routing generation
03
CAD-to-BOM Synchronization
Multi-CAD extraction · Assembly relationship mapping · Metadata harvesting · Revision linkage
▼
The engineering BOM should be extracted from CAD, not typed into a spreadsheet. But multi-CAD environments make this extraction unreliable — each CAD system represents assemblies, parts, and metadata differently. Lattice provides deep integration with every major CAD platform (NX, CATIA, Creo, SolidWorks, Inventor, Onshape, Fusion), extracting BOM structures, assembly relationships, material assignments, and custom properties directly from the native data model. When a designer saves a new revision, the eBOM updates automatically. When an assembly relationship changes, the BOM hierarchy reflects it immediately. No manual BOM re-entry. No CAD-to-PLM mismatch.
Native CAD extraction — BOM structure, component quantities, material assignments, and custom metadata extracted directly from each CAD system's native data model. Not a generic STEP/JT import — deep integration with each platform's assembly API
Multi-CAD reconciliation — when a product uses NX for structures, CATIA for surfaces, and SolidWorks for fixtures, Lattice reconciles all three into a unified eBOM with cross-CAD assembly relationships preserved
Automatic revision linkage — every eBOM revision is linked to the exact CAD revision that generated it. When CAD changes, the BOM updates. When the BOM is queried, the system knows which CAD revision it represents
Metadata harvesting — material grade, surface finish, weight, tolerance class, and custom properties extracted from CAD and populated into the BOM automatically. Eliminates the manual data entry that causes 60% of BOM errors
7+
Major CAD platforms with native extraction
Auto
BOM update on CAD save (no manual re-entry)
100%
CAD revision to BOM revision linkage
60%
BOM errors eliminated via automated extraction
04
eBOM↔mBOM Transformation
Structure restructuring · Phantom assemblies · Process materials · Routing integration · Workstation assignment
▼
The engineering BOM reflects how the product is designed. The manufacturing BOM reflects how it is built. These are fundamentally different structures — and the transformation between them is where most BOM drift originates. An eBOM organized by functional system (powertrain, chassis, body) must be restructured into an mBOM organized by assembly station (station 1 installs frame, station 2 mounts powertrain, station 3 adds body panels). Manufacturing adds process materials (adhesives, lubricants, consumables), phantom assemblies for kitting, and packaging components that do not exist in engineering's view. Lattice manages this transformation with full traceability — every mBOM line item traces back to its eBOM origin, and every eBOM change automatically flags affected mBOM routings for review.
Guided structure restructuring — manufacturing engineers restructure the eBOM into mBOM organization (by station, by cell, by line) while maintaining traceable links to engineering items. Every mBOM component traces to its eBOM origin
Process material management — adhesives, sealants, lubricants, consumables, and packaging materials added to the mBOM with consumption quantities per unit. Tracked for procurement but invisible to engineering's functional view
Phantom assembly management — kitting phantoms, pre-assembly groups, and manufacturing convenience assemblies exist in the mBOM for production efficiency but do not appear in the eBOM's functional structure
Bidirectional change propagation — when engineering changes a component, the affected mBOM routings are flagged. When manufacturing needs to substitute a process material, the request flows back to engineering for approval through Cascade
100%
mBOM-to-eBOM traceability maintained
Bi-dir
Change propagation (eng ↔ mfg)
Auto
Routing flag on eBOM change
Zero
Untracked mBOM deviations from eBOM
05
Service BOM & Aftermarket Intelligence
Field-replaceable units · Repair kits · Supersession chains · Spare parts forecasting
▼
The service BOM is the orphan of product data management. In most organizations, the sBOM is maintained in a separate system — or worse, in spreadsheets — by field service teams who have no connection to engineering or manufacturing. When engineering changes a component, the service team does not know. When a part is superseded, the sBOM is not updated. When a customer calls for a replacement part, the service team checks a catalog that may be three revisions behind. Lattice manages the sBOM as an integral view of the same product data model. When engineering changes a component, the sBOM automatically reflects the change — updating service kits, spare parts catalogs, and field-replaceable unit definitions. Supersession chains track part evolution, ensuring that field service always knows the current-production equivalent of any legacy part number.
Automatic sBOM generation — service-relevant items automatically identified from the eBOM based on serviceability rules: field-replaceable, repairable, consumable, or wear-item classifications. The sBOM is derived, not manually created
Kit and assembly management — service kits group related replacement components (gasket sets, bearing kits, seal kits) with installation instructions and required tools. Kit contents auto-update when constituent parts change
Supersession chain tracking — when a part is replaced by a newer version, the supersession chain maintains full history: PN-4420 → PN-4420-A → PN-4420-B. Field service can identify the current-production equivalent of any legacy part in one query
Spare parts demand forecasting — based on installed fleet size, operating hours, historical failure rates (from Echo), and supersession status, Lattice predicts spare parts demand for each component — feeding procurement with data-driven stocking levels
Auto
sBOM derivation from engineering data
Chain
Full supersession history per component
Real-time
Kit content updates on engineering changes
Forecast
Demand prediction from fleet + failure data
06
As-Built Serialized Traceability
Unit-level configuration · Deviation capture · Rework recording · Lifetime traceability
▼
The as-built BOM answers the question that no other BOM view can answer: "What exactly was installed in this specific unit?" Not what was designed. Not what was planned. What was actually assembled, including any substitutions, deviations, or rework performed during manufacturing. For regulated industries — aerospace, medical devices, defense — this is not optional; it is a legal requirement. For all manufacturers, it is the foundation of warranty analysis, field service, and recall management. Lattice captures the as-built configuration automatically from manufacturing execution: barcode-scanned components at point-of-use, serialized subassembly records, and deviation/rework documentation — creating a lifetime digital record for every unit that ships.
Automated as-built capture — barcode and RFID scanning at assembly stations automatically records the exact component revision, lot number, and serial number installed in each unit. No manual data entry; no after-the-fact reconstruction
Deviation and rework documentation — when an assembler substitutes a component, performs rework, or deviates from the BOM, the deviation is captured in the as-built record with authorization reference, reason code, and quality disposition
Lifetime configuration tracking — the as-built record evolves throughout the product's operational life: field service replacements, retrofits, and upgrades are all captured, maintaining a complete configuration history from manufacturing through end-of-life
Fleet configuration queries — "show me every unit that contains lot 2024-0891 of material XY" returns results in seconds, enabling targeted recalls, service bulletins, and warranty analysis based on actual installed configurations
100%
Unit-level as-built configuration capture
Scan
Barcode/RFID automated capture at assembly
Life
Lifetime configuration evolution tracking
Seconds
Fleet-wide "where-installed" query response
07
Cost Roll-Up & Should-Cost Intelligence
Multi-level cost aggregation · Supplier price comparison · Should-cost modeling · What-if analysis
▼
The BOM is the most accurate basis for product cost estimation — but only if all four views contribute their cost data. Engineering knows material specifications. Procurement knows supplier pricing. Manufacturing knows labor and overhead. Service knows warranty and lifecycle cost. Lattice aggregates cost data from all views into multi-level cost roll-ups that reflect the true cost of the product at every level of the BOM hierarchy. Should-cost models compare actual supplier pricing against parametric estimates based on material weight, complexity, and manufacturing process — identifying components where suppliers may be overcharging. What-if analysis enables engineering to see the cost impact of design alternatives before committing to a revision.
Multi-level cost roll-up — aggregates material cost, purchased component cost, manufacturing labor, overhead, and supplier markup at every level of the BOM hierarchy. Costs roll up automatically as the BOM changes — no manual recalculation
Should-cost modeling — parametric models estimate what a component should cost based on material weight, complexity factor, manufacturing process, and regional labor rates. Highlights components where actual pricing significantly exceeds should-cost — flagging negotiation opportunities
Design alternative cost comparison — when engineering considers multiple design approaches (casting vs. machining, aluminum vs. steel, single-source vs. multi-source), Lattice shows the full BOM cost impact of each alternative before the decision is made
Lifecycle cost integration — incorporates warranty cost data (from Echo), spare parts consumption rates, and field service labor to calculate total lifecycle cost — not just manufacturing cost. Reveals designs that are cheap to build but expensive to support
Auto
Multi-level cost roll-up on BOM change
Should
Cost modeling with supplier price comparison
What-if
Design alternative cost analysis
Total
Lifecycle cost (MFG + warranty + service)
08
BOM Comparison & Reconciliation
Cross-revision diff · Cross-view diff · Cross-order diff · Compliance gap detection
▼
The ability to compare BOMs — across revisions, across views, across orders, and across products — is the most requested and least available capability in PLM. "What changed between Rev C and Rev D?" should be a one-click answer, not a manual line-by-line comparison in Excel. Lattice provides instant BOM comparison across every dimension: revision-to-revision (what changed in this ECO?), view-to-view (where does the mBOM diverge from the eBOM?), order-to-order (how does this customer's configuration differ from the standard?), and product-to-product (what parts are shared across the product family?). Every difference is categorized, quantified, and linked to its root cause — whether an engineering change, a manufacturing substitution, or a configuration rule.
Cross-revision comparison — instant diff between any two BOM revisions: added components, removed components, quantity changes, material substitutions, and supplier changes. Each difference linked to the ECO that caused it
Cross-view reconciliation — compares eBOM against mBOM to identify discrepancies: components in engineering's view that are missing from manufacturing's, process materials in manufacturing's view that engineering has not approved, and quantity mismatches between views
Cross-order comparison — compares configured BOMs across customer orders to identify commonality and variation. Enables make-to-stock/make-to-order optimization by revealing which configurations share the most common subassemblies
Compliance gap detection — compares the BOM against regulatory material restrictions (RoHS, REACH, TSCA, Proposition 65) and flags non-compliant components before they enter the supply chain. Material declarations flow from supplier data through the BOM to compliance reports
1-click
Cross-revision BOM diff with root cause
4-way
Comparison (revision, view, order, product)
Auto
RoHS/REACH/TSCA compliance gap detection
Zero
Manual line-by-line BOM comparison in Excel
DEPLOYMENT EVIDENCE

Three manufacturers. BOM accuracy transformed.

ENGINEER-TO-ORDER · MULTI-SITE MANUFACTURING
Industrial equipment manufacturer unifies three CAD systems and eliminates $1.8M in BOM-driven quality costs
3 manufacturing plants · 5 CAD environments · 28,000 active part numbers
An engineer-to-order industrial equipment manufacturer was running NX at one plant, SolidWorks at another, and Inventor at a third — with Excel BOMs as the actual source of truth for manufacturing. BOM accuracy was 91%. The 9% error rate translated to $1.8M annually in wrong-parts-ordered, assembly rework, and production delays. After deploying Lattice, CAD-to-BOM synchronization eliminated manual BOM entry across all three CAD platforms. Multi-view reconciliation caught discrepancies between engineering and manufacturing views within minutes instead of weeks. BOM accuracy reached 99.7% within 90 days. The $1.8M quality cost essentially disappeared.
99.7%
BOM accuracy (up from 91%)
$1.8M
Annual quality costs eliminated
3→1
CAD systems unified into single BOM
CONFIGURE-TO-ORDER · HIGH-VARIANT MANUFACTURING
HVAC manufacturer resolves 2.8 million product configurations in milliseconds
12 product families · 340+ option codes · 150% super-BOM with 8,400 components
A commercial HVAC manufacturer with 12 product families and 340+ option codes was managing variant configuration in a custom-built rules engine that took 45 seconds to resolve a single configuration — and frequently produced invalid BOMs that were caught during assembly. Field service had no visibility into which components were installed in specific customer units, making warranty claims a guessing game. Lattice's 150% super-BOM with constraint-based configuration replaced the legacy rules engine. Configuration resolution dropped from 45 seconds to under 800 milliseconds. Invalid configurations were blocked at order entry. The serialized as-built BOM gave field service exact configuration visibility for every installed unit.
800ms
Configuration time (down from 45s)
2.8M
Valid configurations managed
Zero
Invalid configs reaching assembly
AEROSPACE · SERIALIZED TRACEABILITY
Defense contractor achieves 100% as-built traceability — DCMA audit completed in 4 hours
240,000 product records · ITAR controlled · AS9100D certified
A Tier-1 aerospace structures manufacturer was maintaining as-built records in a combination of Teamcenter, shop floor paper travelers, and Excel reconciliation sheets. DCMA auditors spent three days tracing component serialization through this fragmented system during the annual audit. After deploying Lattice with barcode-scanned as-built capture at every assembly station, the as-built record became automatic and immediate. Every component's serial number, lot number, material certification, and supplier traceability code was captured at point-of-use. The following year's DCMA audit — covering the same scope — completed in four hours. The auditor called it the most complete serialized traceability system he had reviewed.
4 hrs
DCMA audit time (down from 3 days)
100%
As-built serialized traceability
Zero
Paper travelers remaining in process

"Our BOM accuracy was 91%. That sounds acceptable until you realize that 9% of incorrect BOMs translates to $1.8 million annually in scrap, rework, wrong-parts-ordered, and production delays. We had three CAD systems, a legacy Windchill install, and Excel BOMs that were the actual source of truth for manufacturing. Lattice unified everything. The BOM is now extracted automatically from CAD, reconciled across engineering and manufacturing views, and shared with the ERP in real time. Accuracy went to 99.7%. The $1.8 million in quality costs essentially disappeared."

VP of Manufacturing Engineering
ENGINEER-TO-ORDER INDUSTRIAL EQUIPMENT · 3 PLANTS · 28,000 PART NUMBERS

"The DCMA auditor spent three days last year tracing serial numbers through our paper travelers and Excel sheets. This year, he sat at a terminal, queried the as-built record for any assembly, and saw every component — serial number, lot number, material cert, supplier traceability — in one screen. He finished in four hours and told us it was the most complete traceability system he had ever audited. Four hours instead of three days."

Director of Quality & Configuration Management
TIER-1 AEROSPACE STRUCTURES · ITAR · AS9100D · 240K RECORDS

Stop managing four BOMs.
Start managing one truth.

Upload a sample BOM. Watch Lattice transform it into four reconciled views with variant configuration, cost roll-up, and compliance checking — in minutes.

Or contact the Lattice BOM team at lattice@brindwell.com