CPQ Guide

Tag: MBOM

  • Assemblies and Subassemblies in Product Configuration

    Assemblies and subassemblies are the structural building blocks of a configurable product model. In manufacturing CPQ, an assembly is a functional or physical grouping of components, while a subassembly is a lower-level grouping that is installed, tested, purchased or manufactured as part of a larger assembly. Modeling these relationships correctly allows a CPQ configurator to validate customer selections, calculate prices, generate a configurable bill of material (BOM), support engineering automation and pass reliable product data to enterprise systems.

    This is more than a matter of arranging parts in a product tree. A configurable pump skid, industrial conveyor, HVAC unit or specialty vehicle may contain optional assemblies, mutually exclusive subassemblies, quantity-dependent components, variant-specific hardware and engineering calculations. The product model must represent those relationships and apply rules consistently from the initial configuration through quoting, design release and production.

    In manufacturing CPQ, assemblies and subassemblies usually sit between the commercial product definition and the detailed engineering and manufacturing structures. They can influence configuration, costing, pricing, lead time, CAD outputs, engineering review and the final production BOM. The exact capabilities depend on the CPQ platform and its integrations; not every CPQ system creates BOMs, automates CAD or supports deep engineering structures.

    What are assemblies and subassemblies?

    An assembly is a product or functional unit made from multiple components or lower-level assemblies. A subassembly is an assembly used inside a larger assembly. The distinction is relative to the product level being examined: a motor-and-coupling module may be a subassembly of a pump package but a complete assembly for a motor supplier.

    Examples include:

    • A conveyor system containing a drive assembly, frame assembly, guarding assembly and controls assembly.
    • A centrifugal pump package containing a pump assembly, motor assembly, baseplate assembly, coupling guard and instrumentation panel.
    • An air-handling unit containing a fan section, filter section, coil section, damper assembly and control panel.
    • A specialty vehicle containing a chassis assembly, powertrain assembly, hydraulic system, cab assembly and body equipment.

    Assemblies can be defined by physical structure, manufacturing responsibility, serviceability, purchasing strategy or functional behavior. A CPQ model therefore should not assume that every visible product grouping is automatically a manufacturing subassembly. The product structure must reflect how the manufacturer designs, prices, sources, builds and services the product.

    Why assemblies matter in manufacturing CPQ

    A generic sales quoting tool may treat a product as a list of selectable options. A manufacturing CPQ system often needs to understand which components belong together, where they are installed, which options are compatible and what downstream data must be produced.

    Assembly-level modeling helps a manufacturer:

    • organize a large product model into maintainable modules;
    • reuse a common subassembly across multiple finished products;
    • apply rules at the appropriate level of the product structure;
    • calculate quantities, costs, prices, dimensions and capacities;
    • generate configurable engineering or manufacturing BOMs;
    • identify which changes require engineering review;
    • control optional, mandatory, purchased and manufactured content;
    • create product-specific CAD models, drawings or installation documents when supported;
    • send structured data to enterprise resource planning (ERP), product lifecycle management (PLM), product data management (PDM) or manufacturing execution systems (MES).

    Without this structure, configuration rules become a flat collection of exceptions. That makes them difficult to test and increases the risk that a valid-looking quote produces an incomplete BOM or an unbuildable design.

    How assemblies are represented in a product model

    A product model is the structured definition of a configurable product, including features, options, components, rules, calculations and relationships. Assemblies normally appear as nodes in a hierarchical product tree.

    Industrial pump package
  Pump assembly
    Casing
    Impeller
    Mechanical seal
    Bearing housing
  Drive assembly
    Motor
    Coupling
    Coupling guard
  Baseplate assembly
    Baseplate
    Anchor hardware
  Instrumentation assembly
    Pressure transmitter
    Temperature sensor
    Junction box

    Each node may have attributes such as part number, revision, description, quantity, unit of measure, sourcing type, effective dates, plant, operation, lead time, cost and sales price. A configurable node may also have conditions that determine whether it is included, which variant is selected and how its quantity or parameters are calculated.

    Common assembly attributes

    Attribute Purpose in configuration Manufacturing example
    Assembly type Identifies a standard, configurable, purchased or engineered structure. Standard motor module versus engineered skid assembly.
    Parent relationship Shows where the assembly is installed or used. Control panel installed on the main frame.
    Option condition Controls when the assembly is included. Washdown enclosure required for a food-processing application.
    Quantity rule Calculates the number of instances. One support bracket for every defined length of conveyor.
    Variant or revision Controls the applicable design or part revision. High-temperature seal kit for a specified temperature range.
    Manufacturing status Indicates whether content is released, obsolete or under review. Prevent a superseded drive assembly from being quoted.
    Downstream mapping Connects the model to ERP, PLM, CAD or other records. Map a CPQ assembly to an ERP phantom assembly or material.

    Assembly rules and configuration constraints

    Assembly logic determines how a selected product configuration changes the product structure. Rules may add, remove, replace or modify assemblies and components. They may also block combinations that would create an unsafe, incompatible or unmanufacturable result.

    Typical rules

    • Inclusion rules: selecting a 400-volt motor adds the corresponding motor assembly and electrical protection components.
    • Exclusion rules: a compact enclosure excludes a large variable-frequency drive because there is insufficient space.
    • Dependency rules: selecting a stainless-steel wetted path requires compatible seals, fasteners and instrumentation.
    • Substitution rules: a selected performance range chooses one of several impeller or gearbox variants.
    • Quantity rules: the number of rollers, supports, brackets or cable sections is calculated from product dimensions.
    • Compatibility rules: a high-pressure valve assembly can only be selected with a body material and actuator rated for that pressure.
    • Completeness rules: an electrical control assembly cannot be released until the required disconnect, enclosure and control voltage are defined.

    Rules can be implemented as simple rules-based logic, constraint-based logic or guided selling. Rules-based logic explicitly states conditions such as if option A is selected, include assembly B. Constraint-based configuration evaluates permitted combinations across many variables, such as pressure, flow, temperature, material, dimensions and regulatory requirements. Guided selling helps a user reach a valid configuration through questions, but it does not replace the underlying product rules.

    These approaches can be combined. A guided selling interface may ask about fluid type and operating temperature; a constraint engine may then determine compatible materials and seals; and a rules engine may add the appropriate subassemblies to the BOM.

    Assemblies, subassemblies and BOM structures

    A bill of material (BOM) lists the components and quantities needed to define or build a product. Assembly modeling is closely related to BOM generation, but the two concepts are not identical. A product model describes configurable behavior, while a BOM is a resulting or released structure for a particular product, variant or manufacturing process.

    Configurable BOM

    A configurable BOM contains alternatives, optional components, rules or placeholders that can resolve into a specific structure after configuration. It may represent the range of possible products before a customer makes selections.

    Engineering BOM

    An engineering BOM (EBOM) represents the product as designed, often emphasizing functional and design relationships. It may contain CAD parts, design assemblies, technical documents and engineering revisions.

    Manufacturing BOM

    A manufacturing BOM (MBOM) represents how the product is built. It may reorganize components by production operation, work center, plant, kit or assembly sequence. A single engineering subassembly can be split, combined or restructured for manufacturing.

    Structure Main purpose Relationship to CPQ
    Configurable BOM Represent possible product variants and option logic. Resolved from customer selections and configuration rules.
    EBOM Represent the designed product and engineering relationships. May receive selected components, parameters or revisions.
    MBOM Represent the buildable production structure. May be generated or completed downstream in ERP or manufacturing systems.

    A CPQ application may generate one or more of these structures, or it may pass configuration results to PLM, PDM or ERP for authoritative BOM creation. The implementation should define which system owns each structure rather than assuming that CPQ is the system of record.

    Example: configuring a pump skid

    Consider a pump skid configured for a chemical-processing customer. The user selects flow rate, discharge pressure, fluid temperature, wetted material, motor voltage, control method and installation environment.

    The CPQ product model may apply the following logic:

    1. The required duty point selects a pump family and calculates a suitable impeller diameter.
    2. The fluid and temperature select a compatible casing material, seal arrangement and gasket material.
    3. The motor power calculation selects a motor size and starter or variable-frequency drive.
    4. An outdoor installation adds a weather-resistant enclosure and modifies the baseplate coating.
    5. A hazardous-area classification restricts the motor, instruments, enclosure and cable entries.
    6. The selected control method adds a control panel subassembly with the required components.
    7. The final configuration creates a quote, a price calculation, a lead-time estimate and, where supported, an engineering BOM or CAD package.

    Some outcomes are commercial and some are engineering outcomes. The price may use assembly-level costs, purchased component prices, labor, engineering effort, margin and freight rules. The BOM may include the selected motor, seal, valves, instruments and hardware. A CAD integration may use calculated dimensions and selected variants to produce a skid layout. These capabilities may be distributed across CPQ, CAD, PLM and ERP rather than delivered by one application.

    Assemblies in CTO, ETO, MTO and ATO workflows

    Assembly modeling supports several manufacturing approaches, but the required depth differs.

    • Configure-to-order (CTO): the manufacturer builds a product from predefined options and approved subassemblies. The model should resolve to known components and routings with limited engineering intervention.
    • Engineer-to-order (ETO): the configuration defines requirements, but engineers create or adapt designs for the order. Assembly structures may include engineered placeholders, calculated dimensions or review gates.
    • Make-to-order (MTO): production begins after the order, often using a configured product definition and order-specific planning.
    • Assemble-to-order (ATO): standard subassemblies are stocked or prepared in advance and combined after the customer order.

    For example, a standard conveyor drive module may support CTO, while a conveyor frame with unusual length, loading and environmental constraints may move into ETO. The CPQ system should make that transition explicit, such as by assigning an engineering review status or creating a structured handoff to engineering.

    Relationship to CAD and engineering automation

    Assemblies are often the bridge between commercial configuration and design automation. A CAD system may use the selected assembly variant, dimensions, mounting points, material, hole patterns and component positions to create a product-specific model or drawing.

    Possible outputs include:

    • an assembly-level 3D model;
    • configured component models;
    • 2D manufacturing or installation drawings;
    • dimension and clearance checks;
    • customer layout drawings;
    • assembly instructions or service documentation.

    CAD automation is not automatic merely because a CPQ platform contains an assembly tree. The CAD models, parameters, templates, mappings, revision controls and error handling must be implemented. Read more about CAD and engineering automation in manufacturing CPQ.

    Assembly-level pricing, costing and quoting

    Assembly structure can support more accurate costing and pricing. A configurable pump package may calculate material cost from the pump, motor, baseplate, instruments and controls, then add labor, testing, engineering, overhead and margin. An assembly may also have its own price, cost, lead time or approval threshold.

    However, price structure should not be confused with product structure. A commercial package may be sold as one line item even when it contains many manufacturing assemblies. Conversely, one physical assembly may contain components that need separate commercial treatment because of options, service contracts or compliance requirements.

    Pricing and BOM logic should be tested independently. A component can be included in the BOM without having a separate visible price, or a commercial option can change price without changing the physical BOM. Guidance on this relationship is covered in BOM generation, pricing and quote automation.

    Maintainability and governance

    Large assembly models become difficult to maintain when structure, rules and ownership are unclear. A practical governance model should define:

    • which team owns each assembly and its rules;
    • which system is authoritative for item numbers, revisions and released BOMs;
    • how common subassemblies are reused across product families;
    • how obsolete parts and superseded revisions are blocked;
    • how effective dates, plants and regional variants are handled;
    • how rules are named, documented and tested;
    • which changes require engineering, manufacturing or commercial approval;
    • how configuration results are traced back to the options and rules that created them.

    Modular product models are generally easier to maintain than one large flat model, but excessive modularization also creates problems. A subassembly should represent a meaningful reusable or governed unit. Creating a separate node for every minor component can make navigation, testing and integration unnecessarily complex.

    Testing assembly logic

    Testing should cover both valid and invalid configurations. A useful test set includes normal products, boundary values, incompatible options, missing selections, revision changes and downstream output checks.

    Test area Example
    Selection validity Confirm that a high-pressure pump cannot use an unrated seal assembly.
    Quantity calculation Verify that conveyor support quantities change correctly with length.
    Variant selection Confirm that the correct motor and coupling are selected for each power range.
    BOM completeness Check that required fasteners, brackets and control components are included.
    Revision control Ensure an obsolete subassembly cannot be selected after its effective end date.
    Integration output Verify that item numbers, quantities and revisions are accepted by ERP or PLM.
    Engineering escalation Confirm that an out-of-range dimension creates an ETO review rather than an invalid release.

    Automated test cases are particularly useful when a common subassembly is reused across many product families. A change to a motor, valve, enclosure or mounting pattern can have consequences in every parent assembly that uses it.

    Common limitations and implementation risks

    • Confusing sales options with physical structure: not every selectable option is a component, and not every component should be exposed to sales users.
    • Duplicated assembly definitions: copies of the same subassembly can diverge and produce inconsistent pricing or BOM results.
    • Unclear system ownership: CPQ, ERP, PLM and CAD may each hold part of the product definition. Without clear ownership, revisions become difficult to control.
    • Hidden engineering assumptions: rules based on undocumented calculations are difficult for sales, engineering and IT to maintain.
    • Overly flat models: a large list of individual components makes dependencies and reuse difficult to understand.
    • Overly deep models: excessive hierarchy can slow configuration and complicate integrations, reporting and user interfaces.
    • Incomplete downstream mapping: an assembly may configure correctly but fail when ERP requires a specific item, unit, plant or routing.
    • Unsupported automation claims: a CPQ product may support configurable options but not native EBOM, MBOM, CAD or engineering calculations.

    These risks should be addressed during requirements analysis and implementation planning. See the guide to manufacturing CPQ implementation, testing and governance and the overview of CPQ integrations with ERP, PLM, PDM, CAD and MES.

    Recommended implementation approach

    1. Map the current product structure: document finished products, assemblies, subassemblies, options, common parts and engineered variants.
    2. Separate structure from rules: identify what the product contains and what conditions determine inclusion, substitution or quantity.
    3. Classify each assembly: mark it as standard, configurable, purchased, manufactured, phantom, engineered or service-related according to the manufacturer’s processes.
    4. Define ownership: decide whether CPQ, ERP, PLM, PDM or CAD owns each item, revision, BOM and design record.
    5. Model a representative product family: choose a product with meaningful configuration complexity rather than a simple demonstration product.
    6. Connect downstream outputs: test quote lines, prices, BOMs, CAD parameters, engineering tasks and ERP transactions.
    7. Test reuse and change impact: modify a shared subassembly and evaluate every affected parent product.
    8. Establish release governance: document approvals, effective dates, revision rules, ownership and regression testing.

    The goal is not to reproduce every legacy engineering record inside CPQ. The goal is to hold enough product and rule information to guide valid configuration and create reliable downstream outputs, while preserving the appropriate system of record for detailed engineering and production data.

    Related manufacturing CPQ concepts

    Assemblies and subassemblies are closely connected to product configuration, product models and configuration rules, as well as configure-to-order and engineer-to-order workflows. They also relate to configurable BOMs, engineering automation, costing, quote generation and enterprise integration. For a broader introduction, see the guide to manufacturing CPQ.

    Frequently asked questions

    1. What is an assembly in product configuration?

    An assembly is a product structure made from multiple components or lower-level assemblies. In manufacturing CPQ, it may represent a functional module, manufacturing unit, purchased package or configurable section of a finished product.

    2. What is a subassembly?

    A subassembly is an assembly used inside a larger assembly. Examples include a motor-and-coupling module in a pump package or a drive module in a conveyor.

    3. Are assemblies the same as BOMs?

    No. An assembly is a structural product concept, while a BOM is a formal list of components and quantities for a product, variant or manufacturing process. A CPQ product model may resolve into one or more BOM structures.

    4. Can a CPQ configurator generate subassemblies automatically?

    Some manufacturing CPQ systems can generate or resolve configurable subassemblies. Others only pass selections and parameters to ERP, PLM, PDM or another engineering system. This capability must be verified for the specific platform.

    5. How do assembly rules prevent configuration errors?

    Rules can include required assemblies, exclude incompatible variants, select approved substitutions and calculate quantities. They can prevent combinations such as an undersized motor, incompatible seal or incorrectly rated enclosure.

    6. Should every component be modeled as a separate subassembly?

    No. Separate subassemblies should represent meaningful reusable, functional, manufacturing or governed units. Modeling every small component as a separate module can make the product model harder to maintain.

    7. How do assemblies affect pricing?

    Assembly contents can contribute material, labor, purchased-component, testing and engineering costs. An assembly may also carry a price or surcharge, although commercial pricing does not always mirror the physical BOM exactly.

    8. How do assemblies affect CAD automation?

    Selected assemblies can provide CAD variants, dimensions, mounting locations, materials and parameters. When the necessary CAD integration and templates exist, these inputs can produce product-specific models or drawings.

    9. What is the difference between an EBOM and an MBOM for assemblies?

    An engineering BOM represents the designed product, while a manufacturing BOM represents how the product is built. Manufacturing may reorganize or combine engineering assemblies for production operations.

    10. How are assemblies used in configure-to-order manufacturing?

    In configure-to-order manufacturing, approved assemblies and subassemblies are selected from a defined product model. The resolved structure should normally map to known parts, routings and production data.

    11. How are assemblies used in engineer-to-order manufacturing?

    In engineer-to-order manufacturing, assemblies may include calculated dimensions, engineered placeholders or review conditions. CPQ can define requirements and initiate engineering work rather than fully determining every component.

    12. Can one subassembly be reused in several products?

    Yes. Reuse is a major reason to model subassemblies explicitly. The shared module must have controlled revisions, compatible interfaces and rules that work in each parent product.

    13. Which system should own assembly data?

    There is no universal answer. CPQ may own commercial configuration logic, PLM or PDM may own design structures, and ERP may own released manufacturing items and plant-specific data. Ownership and synchronization must be defined during implementation.

    14. What happens when a selected assembly is not buildable?

    A well-designed model should block the configuration, request a missing selection, calculate a valid alternative or route the order to engineering review. It should not silently create an incomplete production structure.

    15. How should assembly changes be tested?

    Test valid and invalid combinations, quantity calculations, BOM completeness, revisions, pricing, CAD outputs and integrations. Also test every major parent product that reuses the changed subassembly.

    16. Are assemblies visible to sales users?

    They can be, but they do not have to be. Sales users may select business-level options such as capacity or environment, while the CPQ model resolves the underlying assemblies and components automatically.

    17. How do assemblies support dealer or distributor configuration?

    They allow dealers to work with understandable product choices while the system applies technical rules and resolves the required modules. Permissions may limit access to engineering-level details or sensitive costs.

    18. What is a phantom assembly?

    A phantom assembly is a logical grouping used for planning or structuring a BOM that may not be built or stocked as a separate physical unit. Whether and how it is supported depends on the manufacturing system and integration design.

    19. What is the main implementation mistake with assembly modeling?

    A common mistake is copying an existing BOM into CPQ without defining configuration behavior, ownership, revisions and downstream mappings. A usable product model must explain how customer choices produce a valid product structure.

    Semantic map

    • CPQ connects customer requirements to configurable product structures.
    • Assemblies organize components into functional or manufacturing units.
    • Subassemblies provide reusable modules within larger product structures.
    • Configuration rules control assembly inclusion, exclusion, substitution and quantity.
    • Constraints prevent incompatible or unbuildable combinations.
    • Configured products can generate resolved BOMs when the CPQ platform supports that capability.
    • EBOMs represent designed products and MBOMs represent manufacturing structures.
    • CAD automation can use configured assembly parameters to create product-specific design outputs.
    • Assembly content contributes to costing, pricing, lead-time estimation and quote generation.
    • CPQ exchanges configuration and order data with ERP, PLM, PDM, CAD and MES through integrations or APIs.
    • CTO uses approved assemblies, while ETO may use engineered assembly requirements and review gates.
    • Assembly governance controls ownership, revisions, reuse, testing and release status.