Entity

Bill of Materials (BOM)

The hierarchical definition of every component, sub-assembly, raw material, and quantity required to produce one unit of a finished product — including revision history, effectivity dates, and alternate/substitute material rules.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI cannot plan material requirements, simulate product cost scenarios, or validate that the right inputs are staged for production without a machine-readable BOM; implicit tribal knowledge about 'what actually goes into this product' blocks every downstream optimization.

Production Operations Capacity Profile

Typical CMC levels for production operations in Manufacturing organizations.

Formality
L2
Capture
L2
Structure
L2
Accessibility
L1
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Bill of Materials (BOM). Baseline level is highlighted.

L0

The BOM lives in the heads of senior manufacturing engineers. When someone asks 'what goes into Part 7842?', the answer is 'ask Tom, he's been building those for 15 years.' Tom retires next month and with him goes the knowledge of which alternate components actually work.

AI cannot perform material planning, cost analysis, or production validation because no machine-readable BOM exists.

Create any written record of product composition — even a spreadsheet listing components and quantities for each finished good.

L1

BOMs exist as Excel spreadsheets or paper parts lists stored in engineering folders. Each product has a list of components and quantities, but formats vary by engineer. Finding the BOM for Part 7842 Rev C means asking 'which folder is it in?' and hoping the filename makes sense.

AI could potentially read exported BOM files, but cannot reliably traverse parent-child relationships or determine which revision is current because structure varies per file.

Standardize BOM format with consistent fields — parent item, component, quantity per, unit of measure, reference designator — and establish revision control.

L2Current Baseline

BOMs are maintained in a standard template with consistent structure: parent-child relationships, quantities, units, and revision tracking. Engineers update BOMs using the template in SharePoint or a basic database. BOMs are findable and consistent, but they're documents — not linked to inventory, costs, or production.

AI can retrieve and parse BOM structures by part number, but cannot calculate actual material costs, check component availability, or validate that the BOM matches what's actually built.

Move BOMs into ERP or PLM with structured fields, effectivity dates, and links to item master records for cost, lead time, and inventory data.

L3

BOMs are structured records in ERP or PLM with discrete fields: component ID, quantity, unit, effectivity dates, reference designators, and find numbers. Each BOM links to item master records for cost and lead time. The system can answer 'what's the total material cost for Assembly X at current prices?' programmatically.

AI can perform material requirements planning, cost roll-ups, and component availability analysis. Production validation against BOM structure is possible for current-state analysis.

Add formal entity relationships linking BOMs to engineering changes, approved suppliers, alternate components, and manufacturing routings.

L4

BOMs are schema-driven entities with explicit relationships to approved suppliers, alternate components, engineering changes, routings, and where-used cross-references. Each component links to its supply chain. An AI agent can ask 'if Supplier X has a disruption, which end products are affected and what alternates are approved?' and get a complete answer.

AI can perform complex supply chain impact analysis, cost optimization across substitutes, and end-to-end material planning. Autonomous procurement decisions for routine components are possible.

Implement real-time BOM generation — BOMs that auto-update from CAD models when designs change.

L5

BOMs generate automatically from CAD models and update in real-time. When an engineer adds a component in the design, the BOM updates. When purchasing approves a new alternate, it's immediately available. The BOM is a live reflection of design intent, supply chain capabilities, and manufacturing reality — not a document someone maintains separately.

Fully autonomous BOM management. AI can validate designs against manufacturability, optimize component selection, and maintain BOM accuracy without human intervention.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Bill of Materials (BOM)

Other Objects in Production Operations

Related business objects in the same function area.

Production Order

Entity

The transactional record that authorizes and tracks the manufacture of a specific quantity of a specific product — containing the item to build, quantity ordered, due date, BOM revision, routing, priority, and real-time status (released, in-progress, complete, closed).

Routing and Process Plan

Process

The ordered sequence of manufacturing operations required to transform raw materials into a finished product — specifying each operation's work center, setup time, cycle time, tooling requirements, and labor skill requirements.

Equipment Asset Record

Entity

The master record for each piece of production equipment — identity, location, rated capacity, operating specifications, maintenance history, current condition, calibration status, and OEE (Overall Equipment Effectiveness) metrics.

Production Schedule

Entity

The time-phased plan that assigns production orders to specific resources (machines, lines, cells) across specific time slots — incorporating changeover sequences, priority rules, constraint windows, and frozen/slushy/liquid planning horizons.

Sensor Network Configuration

Entity

The managed infrastructure of sensors, data collection points, and signal routing that instruments production equipment — defining which sensors monitor which assets, sampling rates, alarm thresholds, signal conditioning rules, and the mapping between physical measurement points and logical asset identifiers.

Downtime Event Record

Entity

The structured log of every production stoppage — start time, end time, affected equipment, reason code (planned maintenance, breakdown, changeover, material shortage, quality hold), operator notes, and impact in lost units or lost minutes.

Shift and Labor Assignment

Relationship

The record of workforce deployment to production — shift patterns, crew compositions, individual operator assignments to work centers, skill certifications held, training completion status, and attendance/availability data.

Energy Consumption Record

Entity

The metered utility usage data broken down by equipment, production line, or facility zone — electricity, gas, water, compressed air, and steam consumption linked to time periods, production volumes, and operating conditions.

Digital Twin Model Configuration

Entity

The virtual replica definition that maps physical production assets, process flows, and constraints into a simulation-ready model — including asset topology, process logic, throughput parameters, failure distributions, and calibration state against actual production data.

Scheduling Priority Rule

Rule

The codified logic that determines how production orders are sequenced on constrained resources — including priority classes (customer commitment, margin, shelf life), tie-breaking rules, expedite override policies, and the weighting formulas that schedulers apply (often implicitly) when competing orders contend for the same time slot.

Lot Release Decision

Decision

The recurring pass/fail judgment point where a completed production lot is evaluated against acceptance criteria before advancing to the next process stage, packaging, or shipment — encompassing the decision criteria, authority levels, hold/release/disposition outcomes, and the evidence package required to support each decision.

Changeover Sequence Rule

Rule

The defined logic governing product-to-product transition sequences on production lines — including sequence-dependent setup times, cleaning requirements, tooling swap matrices, product family groupings, and the optimization constraints that determine which changeover paths minimize total lost time.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.