CPQ Guide

Tag: 3D CPQ

  • 3D CPQ Software: Complete Guide for Manufacturers

    3D CPQ software combines Configure, Price, Quote (CPQ) capabilities with three-dimensional product visualization and, in some implementations, CAD and engineering automation. For manufacturers, it can show customers and sales teams what a configured machine, vehicle, enclosure or assembly will look like while validating configuration rules, calculating price and producing downstream engineering data.

    The most important distinction is that 3D visualization and manufacturing CPQ are not the same thing. A 3D viewer may display selectable options without understanding engineering constraints or producing manufacturing data. A manufacturing-oriented 3D CPQ system connects the visual model to a product model, configuration rules, calculations, pricing, bills of material (BOMs), computer-aided design (CAD) outputs and enterprise systems where those capabilities are implemented.

    This guide explains how 3D CPQ works, what data it requires, how it supports the sales-to-engineering handoff, where it fits in the technology stack, and what manufacturers should verify before selecting a platform. For the broader subject, see the guide to manufacturing CPQ software.

    What is 3D CPQ software?

    3D CPQ software is a product configuration and quoting system that represents configurable products in three dimensions while applying product rules, engineering logic, pricing and quoting workflows. Depending on the architecture, the 3D model may be a visual representation only, a parametric model driven by configuration values, or a connected CAD output used to generate drawings and manufacturing data.

    A typical 3D CPQ interaction might allow a user to select a pump type, alter connection orientation, choose a motor, set dimensions and add accessories. The system can update the three-dimensional view, reject incompatible combinations, calculate price and produce a quote. More advanced implementations can also create a configurable BOM, an engineering BOM (EBOM), a manufacturing BOM (MBOM), product-specific drawings or a CAD file.

    These capabilities are not automatically included in every CPQ product. Buyers should evaluate visualization, configuration, CAD automation, BOM generation, engineering calculations and integrations as separate capabilities.

    How 3D CPQ differs from generic sales CPQ

    Generic sales CPQ usually focuses on selecting commercial products, applying discounts and producing a proposal. Manufacturing CPQ must often model the physical product and its engineering consequences. A configuration can affect dimensions, materials, structural loads, motor sizing, electrical requirements, production operations and compliance documentation.

    Capability Generic sales CPQ Manufacturing-oriented 3D CPQ
    Product selection Options and packages Options, dimensions, components, materials and engineering parameters
    Validation Commercial dependencies Commercial, geometric, mechanical, electrical and manufacturing constraints
    Visualization Optional product images Interactive 3D representation of the configured product or assembly
    Outputs Quote and proposal Quote plus BOM, configuration record, CAD outputs or engineering handoff where supported
    Downstream systems Customer relationship management (CRM) and enterprise resource planning (ERP) CRM, ERP, product lifecycle management (PLM), product data management (PDM), CAD and manufacturing systems

    The distinction matters because a visually attractive configurator can still leave engineering teams with incomplete or untrusted data. The objective is not simply to rotate a model on a web page. The objective is to connect customer intent with a valid product definition and repeatable operational outputs.

    How a 3D CPQ architecture works

    A 3D CPQ solution normally contains several related layers. They may be delivered by one platform or connected through application programming interfaces (APIs) and integration services.

    1. Product model

    The product model defines the configurable structure. It may contain product families, modules, features, options, dimensions, materials, components, accessories and dependencies. For example, an industrial air-handling unit model could include fan type, casing width, filter section, heating coil, control panel, access doors and insulation.

    The model should identify which values are customer-selectable, which are calculated, which are inherited from a product family and which are controlled by engineering. It should also distinguish commercial options from physical components. Selecting a premium warranty is not the same kind of event as selecting a larger motor.

    2. Rules and constraints

    Rules determine which combinations are valid and what the system should do when a selection changes. Rules-based configuration uses explicit conditions such as “if option A is selected, option B is required.” Constraint-based configuration represents permitted or prohibited relationships across values, ranges and dependencies. Guided selling helps a user reach a suitable product by asking questions, but it may not provide the full engineering validation required for production.

    Typical rules include:

    • Preventing a pump motor from exceeding the available electrical supply.
    • Requiring a reinforced frame when a machine exceeds a specified load.
    • Limiting enclosure dimensions based on transport or manufacturing constraints.
    • Adding a mounting kit when a selected valve requires a particular connection standard.
    • Preventing two accessories from occupying the same physical position.
    • Changing available materials based on temperature, pressure or chemical exposure.

    Good rule design is central to product configuration and configuration validation. Rules should be testable, traceable to a business or engineering requirement and assigned to an owner.

    3. 3D representation and visualization

    The visualization layer maps configuration values to geometry, colors, materials, labels and assembly states. It may hide or display components, change dimensions, substitute models, update camera views or show connection points.

    There are several common approaches:

    • Configured image or scene: pre-rendered images or simple scene changes provide visual guidance but have limited geometric intelligence.
    • Component-based 3D viewer: the system assembles reusable component models and applies visibility or placement rules.
    • Parametric 3D model: dimensions and geometry respond to configuration parameters.
    • CAD-connected configuration: the CPQ process sends validated parameters to a CAD or design automation service that generates product-specific geometry, drawings or files.

    The correct approach depends on the product and required output. A distributor may need a clear visual explanation of a standard conveyor configuration. An engineer-to-order machine builder may need validated dimensions and CAD data rather than only a visual model.

    4. Engineering calculations

    Some products require calculations before they can be quoted. Examples include pump duty and motor selection, pressure drop, structural capacity, thermal performance, cable sizing, airflow, lifting capacity and vehicle payload.

    Calculations can be embedded in the CPQ model, called from an external engineering service or performed in a connected design application. The implementation should record inputs, formulas, assumptions, units and results. A 3D view should not be treated as proof that the selected product is technically suitable.

    5. Pricing, costing and quoting

    The CPQ system can use configuration results to determine component prices, labor, services, freight assumptions, margins, discounts and approval requirements. Pricing remains a separate concern from geometric visualization. A model can look correct while a price is wrong, and a correct price does not prove that the configuration is manufacturable.

    For a deeper treatment of this data flow, see BOM generation, costing, pricing and quote automation.

    6. Downstream outputs

    A completed configuration may produce a quote, proposal, configuration summary, BOM, CAD file, drawing request, engineering task or order payload. The exact output depends on the product and the systems connected to CPQ.

    An EBOM is an engineering bill of material that describes the product from a design perspective. An MBOM is a manufacturing bill of material organized for production, including manufacturing structure, operations or assembly requirements. A configurable BOM may contain rules or placeholders that resolve into a specific product BOM after configuration. These structures should not be assumed to be interchangeable.

    Typical data flow from configuration to production

    1. Start with requirements: a customer, dealer or sales engineer enters application requirements such as capacity, dimensions, environment, voltage or material.
    2. Apply product logic: the system proposes valid options and prevents incompatible combinations.
    3. Update the 3D model: the visual representation changes to reflect selected modules, dimensions and accessories.
    4. Run calculations: sizing, performance or compliance calculations determine whether the configuration satisfies technical requirements.
    5. Calculate cost and price: component costs, labor, margins, discounts and commercial rules are applied.
    6. Generate outputs: the system creates the quote and, where supported, configuration data, BOMs, CAD outputs or engineering documents.
    7. Transfer information: approved data moves to CRM, ERP, PLM, PDM, manufacturing execution system (MES) or another production process.
    8. Release and maintain: engineering and product teams manage revisions, effective dates and rule changes.

    This process supports a controlled sales-to-engineering and order-to-production workflow. It does not eliminate the need for engineering review in every situation. Instead, it helps distinguish standard or configure-to-order work from exceptions that require engineer-to-order handling.

    Manufacturing examples of 3D CPQ

    Industrial machinery

    A machinery builder may configure frame length, guarding, conveyor width, drive package, sensors and control architecture. The 3D model can show the machine footprint and selected modules. Rules can prevent a motor or guard from conflicting with the chosen frame, while CAD automation may generate a layout drawing for customer approval.

    Pumps and valves

    A pump configuration may depend on flow, head, fluid, temperature, materials, seal type, motor, connection standard and mounting arrangement. The system may use engineering calculations to narrow compatible models, display the selected assembly and generate a component list. The visualization is useful, but hydraulic and mechanical validation remain essential.

    Electrical equipment and enclosures

    An enclosure configurator may manage width, height, depth, doors, gland plates, cooling, disconnects and internal components. Three-dimensional placement can reveal clashes and improve communication with the customer. The system may also need to calculate heat dissipation, verify space requirements and generate a panel layout or manufacturing request.

    Specialty vehicles

    A vehicle builder may configure chassis, body modules, seating, storage, lifting equipment, electrical packages and safety options. A 3D view helps stakeholders understand the final vehicle, while rules protect payload, clearance, mounting and electrical constraints. The downstream result may be a vehicle-specific BOM and engineering task rather than a fully automated production package.

    Benefits of 3D CPQ for manufacturers

    • Clearer customer communication: customers can see the effect of dimensions, modules and accessories before order approval.
    • Earlier detection of configuration issues: visual and rule-based validation can expose missing, overlapping or incompatible selections.
    • Less repetitive engineering work: standard calculations, model assembly and document generation can be automated where the product model is mature.
    • More accurate sales-to-engineering handoff: engineering receives structured configuration data instead of relying only on free-text notes or marked-up proposals.
    • Faster quoting for repeatable products: valid configurations can be priced and documented without restarting the design process for every inquiry.
    • Better dealer and distributor support: channel users can configure products consistently without needing to know every internal engineering rule.
    • Improved change control: product teams can update rules, components, geometry and pricing through governed releases.

    Limitations and risks

    3D CPQ is not a substitute for a product strategy, clean engineering data or a controlled product lifecycle. Common limitations include:

    • High modeling effort: configurable geometry, dependencies and calculations require detailed analysis and maintenance.
    • Incomplete product data: inconsistent part numbers, outdated CAD files, missing dimensions or unreliable costs undermine the result.
    • Rule complexity: unmanaged exceptions can create contradictory rules, slow performance and difficult testing.
    • Visualization gaps: a model may be visually persuasive without representing every internal component, tolerance or manufacturing process.
    • Integration boundaries: data may not transfer cleanly between CPQ, CAD, PLM, ERP or MES if identifiers, revisions and ownership are not defined.
    • Performance and usability: large assemblies and detailed models can create browser, mobile or network performance problems.
    • Over-automation: forcing unusual engineer-to-order products through a standard configurator can create risk instead of removing it.

    Manufacturers should define when a configuration is automatically released, when it requires engineering approval and when it must enter a separate design process.

    3D CPQ and CTO, ETO, MTO and ATO

    Production strategy affects the right level of automation. Configure-to-order (CTO) uses predefined modules and rules to produce a valid product after customer selection. 3D CPQ is often a strong fit when the product architecture is modular and repeatable.

    Engineer-to-order (ETO) creates or significantly changes the design for a specific order. A 3D CPQ system may capture requirements, create a preliminary model and initiate engineering work, but it may not fully automate the final design.

    Make-to-order (MTO) means production starts in response to an order, while assemble-to-order (ATO) combines stocked or predefined modules after ordering. These terms describe production and fulfillment approaches; they do not by themselves prove that a product can be configured automatically.

    Integration with enterprise systems

    3D CPQ usually sits between customer-facing processes and engineering or operational systems. The integration design should identify the system of record for each data type.

    System Typical relationship with 3D CPQ
    CRM Opportunity, account, contact, sales process and quote context
    ERP Item masters, inventory, costs, prices, orders, customers and financial processing
    PLM Product structures, revisions, lifecycle states, engineering changes and released definitions
    PDM CAD files, document metadata, versions and controlled design data
    CAD Parametric models, assemblies, drawings and design automation
    Product information management (PIM) Commercial product descriptions, attributes, media and channel content
    MES Production execution, work instructions, status and manufacturing data

    For integration patterns and ownership questions, see the guide to CPQ integration with ERP, CRM, PLM, PDM, CAD and MES. A practical design should define part-number ownership, revision behavior, configuration identifiers, error handling, security and whether data moves synchronously or through approved release events.

    How to evaluate 3D CPQ software

    Manufacturers should evaluate the complete workflow rather than judging a platform by the presence of a 3D viewer. Important questions include:

    • Can the product model represent modules, variants, dimensions, materials and optional components?
    • Can rules express cross-component, geometric, electrical and engineering constraints?
    • Is the 3D model visual-only, component-based, parametric or connected to CAD?
    • Can the system expose configuration values to CAD automation or engineering calculations?
    • What outputs are supported: quote, configuration record, configurable BOM, EBOM, MBOM, drawing or CAD file?
    • How are part numbers, revisions, units and engineering attributes managed?
    • Can users distinguish standard CTO configurations from ETO exceptions?
    • How are rule changes tested, approved, versioned and rolled back?
    • What happens when an ERP, PLM or CAD service is unavailable?
    • Can the system support sales engineers, dealers, distributors and customer self-service without exposing uncontrolled data?
    • How are large assemblies, mobile devices and high-resolution models handled?
    • Which capabilities are native, which require customization and which depend on third-party applications?

    Vendor claims should be validated with a representative product model and real outputs. A useful proof of concept should include incompatible selections, dimensional changes, a pricing change, a BOM comparison, a CAD or drawing requirement and an exception that requires engineering review. The manufacturing CPQ comparison and selection guidance can help structure this evaluation.

    Implementation approach

    Define the first product scope

    Start with a product family that has meaningful configuration volume and reasonably stable rules. Avoid beginning with the most customized product if its design logic is not yet documented.

    Establish data ownership

    Document who owns item numbers, CAD models, prices, costs, technical attributes, product rules, revisions and released BOMs. A CPQ system should not become an uncontrolled duplicate of ERP or PLM.

    Separate visual logic from engineering logic

    Some rules control what appears in the viewer; others determine whether the product is technically valid. Keep these concerns identifiable even when they are evaluated in one transaction.

    Build and test representative configurations

    Test normal, boundary, invalid, discontinued and exception scenarios. Include unit conversions, missing data, revision changes, integration failures and products with large assemblies. A visual inspection alone is not sufficient; compare expected BOMs, prices, calculations and CAD outputs.

    Define release and exception workflows

    Decide when a quote is valid, when an engineering approval is required and how a changed configuration affects an existing quote. This is especially important when a 3D CPQ system supports both CTO and ETO workflows.

    Plan ongoing governance

    Product models require maintenance as components, suppliers, prices, regulations, CAD models and manufacturing processes change. Establish release management, regression testing, rule ownership, usage monitoring and a process for retiring obsolete options. The CPQ implementation guide covers requirements, migration, testing, governance and maintenance in more detail.

    Semantic map

    The following relationships summarize the main entities discussed in this guide:

    • 3D CPQ software connects product configuration, visualization, engineering and quoting.
    • Product models define configurable products, modules, options, dimensions and components.
    • Configuration rules prevent invalid combinations and trigger dependent selections.
    • 3D visualization represents the selected product configuration.
    • Engineering calculations evaluate technical requirements such as capacity, load, flow or heat.
    • CAD automation generates product-specific geometry, drawings or design files when supported.
    • A configured product can generate a BOM, configuration record or engineering request.
    • An EBOM represents an engineering product structure.
    • An MBOM represents a manufacturing-oriented product structure.
    • CPQ exchanges customer and commercial data with CRM.
    • CPQ exchanges item, price, cost and order data with ERP.
    • CPQ exchanges released product and revision data with PLM or PDM.
    • CTO uses predefined modules and rules for repeatable products.
    • ETO requires engineering work for product-specific designs or exceptions.
    • Sales-to-engineering handoff transfers validated configuration data to downstream teams.

    Frequently asked questions

    1. What is 3D CPQ?

    3D CPQ is CPQ software that combines product configuration and quoting with three-dimensional visualization. In manufacturing, it may also connect configuration values to engineering calculations, BOMs, CAD automation and production systems.

    2. Is a 3D product configurator the same as 3D CPQ?

    No. A 3D configurator may only display product variants. 3D CPQ adds commercial and operational processes such as validation, pricing, quoting and potentially BOM or engineering outputs.

    3. Does every 3D CPQ system generate CAD files?

    No. Some systems provide visualization only, while others connect to CAD or design automation tools. CAD generation must be verified for the specific CAD system, product model and output format required.

    4. Can 3D CPQ generate a manufacturing BOM?

    Some platforms can generate or export BOM data, but not every CPQ system creates an MBOM. The buyer should verify whether the output is an EBOM, MBOM, configurable BOM or simple component list.

    5. Can a 3D model validate engineering requirements?

    Not by itself. Geometry can help identify visual or spatial issues, but technical validation usually requires configuration rules, engineering calculations, simulation or engineering review.

    6. What products benefit most from 3D CPQ?

    It is often useful for configurable machinery, equipment, vehicles, enclosures, HVAC systems, material handling products, electrical assemblies and other products where options affect geometry or customer understanding.

    7. How does 3D CPQ support sales engineers?

    It gives sales engineers a structured way to collect requirements, select valid options, explain the resulting product and produce a quote with clearer engineering information.

    8. Can dealers use 3D CPQ?

    Yes, if the platform supports dealer or distributor workflows and provides appropriate access controls. The manufacturer must decide which options, prices, technical data and outputs each channel user can access.

    9. Does 3D CPQ replace engineering?

    No. It can automate repeatable configuration and documentation, but engineering remains necessary for new products, unusual requirements, exceptions and changes outside the validated product model.

    10. How is 3D CPQ related to PLM?

    Product lifecycle management (PLM) manages product definitions, revisions and lifecycle processes. 3D CPQ uses selected product and engineering data to configure and quote products, with integration required to keep definitions aligned.

    11. How is 3D CPQ related to PDM?

    Product data management (PDM) commonly manages CAD files, documents, metadata and revisions. A 3D CPQ system may retrieve controlled models or send parameters to design automation through a PDM or CAD environment.

    12. Can 3D CPQ support engineer-to-order products?

    It can support ETO by capturing requirements, creating preliminary configurations and initiating engineering tasks. Full automated design generation is not appropriate for every ETO product.

    13. What is the difference between a 3D viewer and a parametric model?

    A viewer displays geometry, while a parametric model changes geometry according to defined parameters. A viewer may show options without being able to calculate or generate the corresponding engineering design.

    14. What data is needed to implement 3D CPQ?

    Typical inputs include product structures, options, rules, dimensions, component identifiers, CAD models, technical attributes, costs, prices, calculations, BOM logic and integration mappings.

    15. How should 3D CPQ configurations be tested?

    Test valid and invalid combinations, boundary values, dimensional changes, pricing, BOM results, CAD outputs, revision changes, integration errors and cases that should be routed to engineering.

    16. Can 3D CPQ work with ERP?

    Many manufacturing CPQ implementations integrate with ERP, but the depth varies. The integration may exchange items, prices, costs, customers, orders, inventory or configuration identifiers. These capabilities must be verified for the chosen platform.

    17. Is 3D CPQ suitable for customer self-service?

    It can be suitable for self-service when the product is sufficiently standardized and the user interface hides unnecessary engineering complexity. Products with frequent exceptions may need sales or engineering involvement.

    18. What is the biggest implementation risk?

    A major risk is attempting to automate an undocumented or unstable product model. Rule ownership, clean data, controlled CAD assets and a clear exception process are prerequisites for reliable results.

    19. How does 3D CPQ affect quote accuracy?

    It can improve accuracy by linking valid configuration selections to prices, components and calculations. It does not guarantee accuracy if source costs, rules, CAD data or integration mappings are incomplete.

    20. What should a 3D CPQ proof of concept include?

    Use a real product family with option dependencies, dimensional changes, an invalid combination, a price change, a BOM requirement, a representative 3D output and at least one engineering exception.