VARIANT & OPTIONS CONFIGURATION

One product
definition.
Millions of valid
configurations.

A product family with 12 option categories can produce millions of valid configurations. Helix resolves the correct buildable BOM for any specific configuration in under 800 milliseconds — enforcing technical, regulatory, and commercial constraints at the point of selection, not at the point of assembly failure.

LIVE CONFIGURATION — PRODUCT FAMILY HX-9200 COMPRESSOR
DRIVE TYPE
Variable Speed Electric
SELECTED
PRESSURE RANGE
High Pressure (350 bar)
SELECTED
SEAL MATERIAL
PTFE (required by HP)
AUTO-REQUIRED
COOLING
Air Cooled (blocked)
INCOMPATIBLE
MOTOR FRAME
IEC 315 (auto-selected)
DRIVEN BY DRIVE
MARKET
EU — ATEX Zone 1
SELECTED
CERTIFICATION
ATEX + PED (auto-applied)
MARKET-DRIVEN
CONTROLLER
VSD Controller Mk4
DRIVEN BY DRIVE
Resolved: 100% buildable BOM — 847 components · 23 options selected · 4 constraints enforced · 0 conflicts
Resolution time: 340ms · 150% super-BOM filtered to 100% · Routing generated · Cost roll-up: €48,200 · Lead time: 14 weeks
CONFIGURATION VALID
THE CONFIGURATION CRISIS

Invalid configurations cost more than wrong parts. They cost lost orders, rework, and trust.

When an invalid configuration reaches manufacturing, the cost is not a single rework order — it is the systemic erosion of confidence in the entire order-to-production pipeline.

390K
Valid configurations from just 8 option categories with 5 choices each (5&sup8;)
COMBINATORIAL MATH
<800ms
Helix configuration resolution time — resolving 150% super-BOM to buildable 100% BOM
LATTICE ARCHITECTURE
Zero
Invalid configurations reaching manufacturing floor — constraints enforced at selection, not at assembly
HELIX DEPLOYMENT DATA
45s→0.8s
Configuration resolution time reduction vs. legacy rules engines for high-variant manufacturers
HVAC CASE STUDY

The 150% super-BOM contains every possible component across every variant of a product family. It is the master definition — the universe of what the product could be. Configuration rules define which components are included, excluded, or substituted for each specific order. Selecting “High Pressure” requires PTFE seals and blocks air cooling. Selecting “EU market” auto-applies ATEX certification components. Selecting “Variable Speed Drive” auto-selects the matching motor frame and controller. Helix resolves these constraints in milliseconds, producing a buildable 100% BOM with routing, cost, and lead time — before the sales rep leaves the customer’s conference room.

The architectural distinction between Helix and traditional variant configuration is constraint-based resolution versus rule-based resolution. Rule-based systems require an explicit rule for every valid and invalid combination — and with 12 option categories, the number of required rules grows exponentially. Constraint-based systems define what must be true for a configuration to be valid — and the solver finds all solutions that satisfy the constraints simultaneously. This is why Helix scales to millions of configurations without exponential rule growth: because constraints are composable, not combinatorial.

WHY HELIX

Five capabilities that transform variant management from a configuration nightmare into a competitive advantage.

Constraint-Based Resolution
Defines what must be true for a configuration to be valid — not what is invalid. The solver finds all solutions that satisfy constraints simultaneously, scaling to millions of configurations without exponential rule growth.
Constraint-based: O(n) rule growth. Rule-based: O(2&sup n;) rule growth.
Multi-Layer Rule Architecture
Technical constraints (this pump requires this seal), regulatory constraints (this market requires this certification), and commercial constraints (this package includes these features) are modeled as independent layers that compose without interference.
Three rule layers: technical, regulatory, commercial — independently maintained
Real-Time Cost & Lead Time
Every option selection instantly updates the total BOM cost (from Lattice cost roll-up), manufacturing lead time (from Forge ERP routing), and component availability (from procurement). The sales rep sees the price and delivery impact of every choice in real time.
Cost, lead time, and availability updated on every selection change
Invalid Configuration Prevention
Invalid combinations are blocked at the point of selection — not discovered at the point of assembly. When selecting “High Pressure,” the “Air Cooled” option is grayed out because the constraint solver has already determined it is incompatible. No invalid configuration can be ordered.
Zero invalid configurations reaching manufacturing — blocked at selection
Cascade Change Integration
When Cascade processes an ECO that affects a component in the 150% super-BOM, Helix identifies every product configuration that includes that component and every open order that would be affected — before the change is approved.
ECO impact analysis across all configurations in the product family
CONFIGURATION INTELLIGENCE ENGINES

Eight engines. Every variant governed.

From constraint satisfaction solving through market-specific regulatory layers to product family analytics — Helix operates eight engines that transform the combinatorial explosion of product variants into a controlled, governed, and instantly resolvable configuration space.

01
150% Super-BOM Architecture
Master component universe · Option-tagged items · Conditional inclusion/exclusion · Multi-level variant nesting
The 150% super-BOM is the master definition of everything a product family could be. It contains every component across every variant — the high-pressure seal and the low-pressure seal, the electric motor and the diesel engine, the CE-marked controller and the UL-listed controller. Each component is tagged with the option codes, market codes, and regulatory codes that determine when it is included in a resolved configuration. The super-BOM is not a flat list — it is a hierarchical structure with variant nesting at every level. A top-level assembly may have 3 variants, each containing sub-assemblies with their own variant branches, creating a tree of configurations that Helix navigates during resolution.
Option code tagging: Every component in the 150% BOM carries option codes that define its inclusion conditions. Simple codes (DRIVE=ELECTRIC) and compound codes (DRIVE=ELECTRIC AND PRESSURE=HIGH) determine which components appear in the resolved BOM. Tags are inherited through the hierarchy: a parent tagged DRIVE=ELECTRIC automatically includes all its children
DNP (Do Not Place) management: Components tagged as DNP for specific configurations remain in the super-BOM structure but are excluded from the resolved BOM, procurement, and work instructions. DNP status is managed per configuration, not per component — the same component may be DNP in one configuration and required in another
Multi-level variant nesting: Variants nest to arbitrary depth. A compressor may have 3 drive variants, each with 4 pressure variants, each with 2 seal variants, each with 3 cooling variants. Helix navigates this tree in milliseconds because the constraint solver prunes impossible branches early
150%
Complete component universe per family
N-deep
Multi-level variant nesting
Tag
Option/market/regulatory code system
DNP
Per-configuration exclusion management
02
Constraint Satisfaction Engine
CSP solver architecture · Arc consistency · Backtracking with pruning · Incremental constraint propagation
At its core, product configuration is a constraint satisfaction problem (CSP). Variables are the option categories (drive type, pressure range, seal material, cooling method). Domains are the valid choices per category. Constraints define which combinations of choices are valid. Helix solves this CSP using arc consistency propagation with backtracking — the same family of algorithms that powers industrial scheduling solvers, but optimized for the specific structure of product configuration. When a user selects an option value, the solver immediately propagates the consequences through all constraints: incompatible options are blocked, required options are auto-selected, and the remaining valid choices are narrowed — all in a single propagation pass.
Arc consistency (AC-3/AC-4): After each selection, the solver enforces arc consistency across all constraint arcs. If option A=X eliminates all valid values for option B, the solver detects the inconsistency immediately — before the user can make another selection. This prevents dead-end configurations proactively
Incremental propagation: Each new selection triggers propagation only for the constraints that involve the changed variable — not a full re-solve. This is why resolution time is measured in milliseconds, not seconds: the solver does proportional work per selection, not full-problem work
Conflict explanation: When a selection is blocked, Helix does not just say “incompatible.” It explains which constraint is violated and which prior selection caused the conflict: “Air Cooling is incompatible because High Pressure requires liquid or glycol cooling (constraint: PRESSURE_COOLING_COMPAT)”
Complete enumeration on demand: Beyond resolving a single configuration, Helix can enumerate all valid configurations for a given partial selection. “If the customer has selected High Pressure and Electric Drive, how many valid configurations remain?” The solver computes the answer exhaustively — critical for product family analytics and market coverage analysis
CSP
Constraint satisfaction architecture
AC-3
Arc consistency propagation
<800ms
Full resolution time
Why
Conflict explanation for blocked options
03
Option Code Dependency Graph
Requires/excludes/implies relationships · Transitive closure · Cycle detection · Dependency visualization
Behind the constraint solver lies a dependency graph that models the relationships between every option in the product family. Option A requires Option B. Option C excludes Option D. Option E implies Option F unless Option G is also selected. These relationships form a directed graph with typed edges (requires, excludes, implies, unless). Helix computes the transitive closure of this graph at model definition time — meaning that indirect dependencies are pre-computed and available for instant propagation during configuration.
Typed dependency edges: REQUIRES (A needs B), EXCLUDES (A blocks B), IMPLIES (A auto-selects B), UNLESS (A implies B unless C is selected). Each edge type has distinct propagation semantics in the constraint solver
Transitive closure pre-computation: If A requires B and B requires C, then selecting A will auto-select both B and C. These transitive chains are computed when the model is published, not at configuration time — enabling instant propagation during order entry
Cycle detection: Circular dependencies (A requires B, B requires C, C excludes A) create unsolvable configurations. Helix detects cycles at model validation time and reports them to the configuration engineer before the model is published
Graph
Typed dependency model
4
Edge types (requires/excludes/implies/unless)
Pre
Transitive closure at publish time
Cycle
Detection at model validation
04
Market & Regulatory Rule Layers
Geographic market rules · Certification auto-application · Export restriction enforcement · Regional pricing
The same product sold in different markets requires different configurations — and the differences are regulatory, not optional. A compressor sold in the EU requires ATEX certification for hazardous environments and PED certification for pressure equipment. The same compressor sold in North America requires UL listing and ASME certification. Helix models market-specific requirements as an independent constraint layer that activates when a market is selected — automatically adding the required certification components and blocking incompatible options without requiring the sales rep to know the regulatory details.
Market-driven auto-configuration: Selecting “EU Market” automatically activates ATEX, PED, and CE requirements. Selecting “North America” activates UL, ASME, and NEC requirements. The constraint solver applies the market rules alongside technical constraints in a single resolution pass
ITAR/EAR integration via Sentinel: For defense-related product variants, market selection triggers Sentinel’s export control evaluation. Configurations containing ITAR-controlled components are blocked for non-US-person customers and non-TAA-covered destinations
Regional pricing overlays: Different markets may have different pricing structures for the same options (tariffs, local sourcing requirements, certification costs). Helix applies regional pricing overlays during cost roll-up, ensuring the quoted price reflects the true market-specific cost
Auto
Market-driven certification application
ITAR
Export control via Sentinel integration
Multi
Regional pricing overlay support
Layer
Independent regulatory constraint layer
05
Order-Specific BOM Resolution
150% → 100% BOM · Routing generation · Work instruction assembly · Procurement trigger
The endpoint of configuration is a 100% buildable BOM with exact quantities, routings, and work instructions for one specific order. Helix resolves the 150% super-BOM by evaluating every component’s option tags against the validated configuration, removing excluded components, including required components, and producing a flat, buildable BOM with manufacturing routing and work instruction references. This resolved BOM flows directly to Forge ERP for MRP explosion and procurement — no manual BOM editing, no re-entry, no interpretation.
Routing variant selection: Different configurations may require different manufacturing routings. A high-pressure variant may require additional machining operations and hydrostatic testing. Helix selects the correct routing variant alongside the BOM resolution — ensuring that manufacturing instructions match the component selection
Work instruction assembly: Configuration-specific work instructions are assembled from modular instruction blocks. Each block is tagged with the same option codes as its BOM components — ensuring that the assembler receives instructions matching exactly the components in their kit
Procurement trigger: The resolved BOM feeds directly into Forge ERP’s MRP engine. Components with insufficient stock trigger purchase requisitions with the correct quantities, specifications, and delivery dates. No procurement delay waiting for manual BOM finalization
100%
Buildable BOM from 150% master
Route
Variant routing auto-selected
WI
Config-specific work instructions
MRP
Direct feed to Forge ERP procurement
06
Configuration Impact Analysis
ECO-to-configuration mapping · Open order impact · Active fleet exposure · Cascade integration
When Cascade processes an engineering change that affects a component in the 150% super-BOM, Helix computes the configuration impact: which product configurations include the affected component, which open orders use those configurations, and which installed units in the fleet were built with those configurations. This is the inverse of resolution — instead of resolving options to components, Helix traces a component back to the options that include it.
Configuration-aware impact analysis: A component change does not affect all 2.8 million configurations — it affects only the configurations whose constraint solver includes that component. Helix computes the exact subset, enabling targeted communication rather than blanket notifications
Open order exposure: For every affected configuration, Helix queries the open order book to identify which customer orders are impacted. The change manager sees the exact order count, customer list, and delivery timeline impact before approving the change
Exact
Subset of affected configurations
Orders
Open order impact computed
Fleet
Installed base exposure mapped
Cascade
Native ECO integration
07
Product Family Analytics
Configuration frequency analysis · Option popularity · Commonality scoring · Portfolio optimization
The configuration data is itself a strategic asset. Which configurations are ordered most frequently? Which options are never selected? Which combinations generate the highest margins? Helix’s analytics engine aggregates configuration data across all orders to reveal product family intelligence: the 80/20 pattern (80% of orders use 20% of possible configurations), the underperforming options (configured but rarely ordered), and the missing configurations (frequently requested but not available in the current model).
Configuration frequency heatmap: Visualizes which option combinations are ordered most frequently. Reveals that 80% of orders cluster around a small number of “standard” configurations — enabling make-to-stock optimization for the most common variants while maintaining configure-to-order for the long tail
Option cannibalization analysis: Identifies options that compete with each other: when Option A is selected, Option B is almost never chosen. May indicate that the product family has redundant options that increase complexity without increasing market coverage
Margin-by-configuration: Computes the profit margin for each configuration by combining the configuration-specific BOM cost (from Lattice), the configuration-specific price (from the pricing engine), and the configuration-specific warranty cost (from Echo). Reveals which configurations are most and least profitable
80/20
Configuration frequency distribution
Margin
Per-configuration profitability
MTS
Make-to-stock optimization signals
Gap
Missing configuration detection
08
Visual Configuration Interface
3D parametric visualization · Real-time rendering · AR preview · Sales enablement
Configuration is a spatial decision. Customers understand their choices better when they can see the product change as they configure it. Helix’s visual configuration engine renders a 3D parametric model that updates in real time as options are selected: choosing “High Pressure” visually swaps the housing geometry, selecting “Electric Drive” replaces the diesel engine with a motor assembly. The visualization is not a pre-rendered image library — it is a parametric model driven by the same option codes that drive the BOM, ensuring visual-to-BOM consistency. Augmented reality preview enables the customer to place the configured product in their facility using a tablet or smartphone.
Option-driven model swap: Each option code is linked to a 3D geometry variant in the CAD system (via Lattice’s CAD-to-BOM synchronization). Selecting an option triggers a geometry swap in the viewer — maintaining consistent visual representation with zero manual 3D content creation
Dimensional parametrics: For continuously variable options (pipe length, tank capacity, frame height), the 3D model scales parametrically rather than swapping discrete geometry. The visual model matches the exact dimensional configuration ordered
AR facility preview: Using ARKit/ARCore on mobile devices, the configured product can be placed at true scale in the customer’s facility. Sales engineers demonstrate fit, clearance, and service access before the order is placed
3D
Real-time parametric visualization
AR
Augmented reality facility preview
Sync
Visual-to-BOM consistency guaranteed
Zero
Manual 3D content creation needed
DEPLOYMENT EVIDENCE

Three manufacturers. Configuration mastered.

HVAC · CONFIGURE-TO-ORDER · HIGH VARIANT
Commercial HVAC manufacturer resolves 2.8 million configurations in 800ms — zero invalid orders reaching production
12 product families · 340+ option codes · 8,400 components in 150% super-BOM
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 discovered during assembly. After deploying Helix, constraint-based resolution dropped configuration time from 45 seconds to under 800 milliseconds. The constraint solver blocked invalid combinations at selection time, eliminating the 12% of orders that previously reached the shop floor with unbuildable configurations. Field service gained exact configuration visibility for every installed unit through Lattice’s as-built traceability. Order-to-ship cycle time decreased by 3 weeks as configuration-related rework was eliminated.
800ms
Resolution time (down from 45s)
Zero
Invalid configs reaching assembly
3 wk
Cycle time reduction
INDUSTRIAL PUMPS · GLOBAL MARKETS · MULTI-REGULATORY
Pump manufacturer deploys 14 market-specific regulatory layers across 6 global regions without rule duplication
6 regional markets · 14 certification standards · 4,200 configurable components
A global industrial pump manufacturer selling into 6 regional markets (EU, North America, Middle East, Asia-Pacific, India, Latin America) was maintaining separate configuration models per market — 6 copies of the same product family, each with market-specific rules manually synchronized. Rule drift between copies caused certification errors: a pump configured for the EU market was shipped without the required ATEX-rated junction box because the EU model had not been updated after a recent engineering change. After deploying Helix with independent regulatory rule layers, all 6 markets share a single 150% super-BOM with 14 certification standards modeled as composable constraint layers. Market selection activates the correct layer automatically. Engineering changes propagate to all markets simultaneously through a single super-BOM update.
1
Super-BOM for all 6 markets (was 6)
14
Certification layers, composable
Zero
Certification errors (was 8/year)
AUTOMOTIVE TIER-1 · PRODUCT FAMILY RATIONALIZATION
Configuration analytics reveal 60% of option combinations never ordered — product family rationalized from 840K to 180K configurations
4 product families · 840K theoretical configurations · 18 months of order data analyzed
An automotive Tier-1 supplier offering 4 product families with a theoretical configuration space of 840,000 variants was struggling with inventory management, tooling complexity, and procurement scale inefficiency. Helix’s Product Family Analytics engine analyzed 18 months of order data and revealed that 95% of orders used only 12% of available configurations. Additionally, 60% of theoretically valid configurations had never been ordered and were unlikely to be ordered based on market analysis. By rationalizing the option matrix — removing truly unused options, combining rarely-distinguished variants, and establishing standard configurations for the 80% case — the effective configuration space was reduced from 840K to 180K. Inventory carrying cost decreased 22% and tooling complexity dropped proportionally.
78%
Configuration space reduction
22%
Inventory cost decrease
95/12
95% orders from 12% of configs

“Our legacy configurator took forty-five seconds to resolve a single order. In that forty-five seconds, the sales rep was staring at a spinner, the customer was losing patience, and twelve percent of the time the result was an invalid BOM that would not be discovered until someone on the shop floor tried to build it. Helix resolves in eight hundred milliseconds. The customer sees the price, the lead time, and a three-dimensional model of their exact configuration before the sales rep finishes their coffee. Zero invalid configurations have reached our assembly floor since deployment.”

VP of Sales Operations & Product Management
COMMERCIAL HVAC · 12 PRODUCT FAMILIES · 2.8M CONFIGURATIONS

“We were maintaining six copies of the same configuration model — one per market. Every engineering change had to be applied six times. Every rule had to be synchronized six times. And still, a pump shipped to Rotterdam without its ATEX junction box because the EU model was two changes behind. One super-BOM. Fourteen regulatory layers. Market selection activates the correct constraints automatically. We have not shipped a single certification error since deployment.”

Director of Global Product Configuration
INDUSTRIAL PUMPS · 6 GLOBAL MARKETS · 14 CERTIFICATION STANDARDS

Stop managing
variants in
spreadsheets.
Start resolving them
in milliseconds.

Upload your product family. Watch Helix build the 150% super-BOM, model the constraints, and resolve your first configuration in under a second.

Or contact the Helix configuration team at helix@brindwell.com