Product variety is growing faster than static BOMs can support.
Manufacturers are under pressure to offer more choices, regional versions, customer-specific requirements, and configurable product families without slowing engineering or creating uncontrolled product data.
Configuration and variant management is the process of defining product options, rules, dependencies, and valid combinations so teams can generate accurate configured products without duplicating product structures.

Static BOMs work for simple products. They break down when products become configurable.
Separate BOMs for every model, option, market, or customer requirement create duplicate data, repeated engineering work, and higher risk of inconsistency.
Duplicate BOMs
Separate BOMs appear for similar variations, creating repeated product data.
Manual Updates
Teams repeat updates across multiple structures instead of changing shared logic once.
Invalid Combinations
There is no reliable way to validate option combinations before release.
Limited Traceability
Teams struggle to connect customer orders to the exact final BOM that was built.
Conflicting Data
Outdated or conflicting product data can move downstream unnoticed.
Slower Launches
Repeated engineering changes delay decisions, releases, and product launches.
One governed product family.
Every valid configuration, controlled.
See how teams define options once, apply configuration rules and release exact 100% BOMs without creating separate structures for every product variation.
Centralize product features and options
Manage product options, attributes, feature families, and option groups in one controlled environment.
Explore option and feature control
Apply dependencies and effectivity rules
Define compatibility, dependency, exclusion, effectivity, and availability rules to protect product accuracy.
Review rule-driven configuration
Release an accurate configured BOM
Generate the correct 100% configured BOM for manufacturing, procurement, planning, and delivery.
Explore configured BOM generation
From a 150% Super BOM to a 100% BOM.
Five connected stages.
Nora IPLM uses a 150% BOM, also known as a Super BOM, to manage all possible parts, modules, features, and options within a product family. Configuration rules then filter the complete structure to generate the exact 100% BOM required for a specific variant.
Define the product family
Create a reusable structure for models, modules, and product lines.
- Organize reusable product platforms, models and feature families.
- Link each product family to its approved modules and variants.
Build the 150% BOM
Store all possible parts, features, assemblies, and options in one Super BOM.
- Maintain every possible assembly, part, module and feature in a Super BOM.
- Keep shared components reusable instead of duplicating variant BOMs.
Apply configuration rules
Use dependencies, exclusions, and effectivity logic to control valid combinations.
- Check required options, dependencies, exclusions and compatibility.
- Apply market, customer, date and revision effectivity before release.
Select the configuration
Choose customer, order, market, model, or feature-specific parameters.
- Select the exact order, model, market and customer requirements.
- Verify that the selected features resolve to a valid product variant.
Generate the 100% BOM
Produce the exact BOM needed for manufacturing, procurement, planning, and delivery.
- Derive only the selected components and applicable revisions.
- Release the 100% BOM for manufacturing, procurement and delivery.
Variant management software features: options, rules and configured BOMs
Control product family logic, valid option combinations, configuration effectivity and downstream BOM releases in one connected lifecycle.
Centralized Option and Feature Control
Manage product options, attributes, feature families, and option groups in one controlled environment.
150% BOM / Super BOM Management
Maintain one reusable 150% BOM that contains all valid possible product components and options.
Rule-Driven Configuration
Define compatibility, dependency, exclusion, effectivity, and availability rules to protect product accuracy.
Automatic Configured BOM Generation
Generate the correct 100% configured BOM for manufacturing, procurement, planning, and delivery.
Variant Traceability
Trace selected options, rule decisions, engineering changes, and final configured outputs across the lifecycle.
Engineering Change Control
Update shared product logic once and keep related variants aligned through controlled change workflows.
Date, Market & Revision Effectivity
Control which option, component or rule applies to each date, market, customer or product revision.
Connected Manufacturing Handoff
Deliver the exact selected components and applicable product records for procurement, planning and manufacturing.
Move from duplicated structures to controlled product logic.
A reusable 150% BOM and rules avoid managing each variant as a disconnected engineering structure.
Static BOM Approach
- One BOM per variant
- Repeated parts and structures
- Manual updates across BOMs
- Hard to validate combinations
- Poor visibility across variants
- Higher risk of manufacturing confusion
Nora IPLM 150% BOM Approach
- One Super BOM for the full product family
- Reusable modules, options, and rules
- Shared product logic updated once
- Rules control valid configurations
- Traceability from option to BOM
- Accurate 100% BOM output for downstream teams
Rule-based product variant example: a configurable warehouse forklift
Variant management software should show how a family-level engineering BOM resolves into a buildable selection. The same product family can contain several battery types, charging systems, lift heights, safety options, and regional packages without requiring a separate master BOM for every combination.
Practical application
Illustrative example: a warehouse forklift family includes standard and heavy-duty lift assemblies. A customer selects a higher lift capacity and a lithium battery package. Rules check load and charger compatibility, exclude incompatible options, and select the matching components from the 150% BOM to form one 100% configured BOM.

What engineering should verify
Review the selected forklift battery, lift assembly, charger and safety package before releasing the configured BOM.

Variant control for every manufacturer and team
Connect engineering, manufacturing, product management, procurement and quality around valid configurations, releases and revisions.
Engineering Teams
Reduce duplicate structures and manage product logic from one controlled environment.
Manufacturing Teams
Receive accurate configured BOMs for each order, market, or product variant.
Product Managers
Control product families, platform strategies, option availability, and market-specific variants.
Procurement Teams
Source the exact configured parts and assemblies needed for each valid product output.
Quality and Compliance Teams
Trace configurations, changes, approvals, and released product structures across the lifecycle.
Leadership Teams
Scale product variety while reducing rework, errors, and operational complexity.
- Configurable products
- Optional assemblies
- Regional variants
- Custom engineering
- Reusable platforms
- Multi-discipline products
Configuration & Variant Management Resource Library
Explore related Nora IPLM workflows for controlled product configurations, reusable BOMs and manufacturing-ready output.
Product Configuration Management
See how product options, rules and configuration baselines work together for customer and market requirements.
Explore resourceBOM Management
Manage reusable engineering product structures that stay linked to approved parts and revisions.
Explore resourceMBOM Management
Connect variant choices with manufacturing-ready structures and downstream production requirements.
Explore resourceConfiguration and Variant Management overview
Explore the full Nora IPLM module for product variants, rules and controlled BOM generation.
Explore resourceFrequently
Asked
Questions
Answers to common questions about configurable product families, 150% and 100% BOMs, option rules and effectivity.
What is Configuration & Variant Management in PLM?
Configuration & Variant Management in PLM helps teams define product options, rules, dependencies, and valid combinations so they can manage product variety without duplicating BOMs for every variation.
What is the difference between product configuration and variant management?
Product configuration focuses on selecting valid options and rules for a specific product. Variant management focuses on organizing and controlling multiple product variations across models, markets, customers, and lifecycle stages.
What is a 150% BOM?
A 150% BOM, or Super BOM, contains all possible parts, modules, options, and features for a product family. Configuration rules filter it into the exact BOM needed for a specific product variant.
What is a 100% configured BOM?
A 100% configured BOM is the exact product structure required for a specific order, customer, market, or configuration. It includes only the valid components selected from the broader 150% BOM.
How does configuration management reduce BOM duplication?
Instead of creating separate BOMs for every product variation, teams maintain one reusable product structure with rules and options. This reduces repeated data, manual updates, and inconsistent product information.
Can Nora IPLM support customer-specific variants?
Yes. Nora IPLM helps teams manage customer-specific, market-specific, order-specific, and region-specific configurations using controlled options, rules, and effectivity conditions.
How do configuration rules work in Nora IPLM?
Rules define which options are required, optional, dependent, mutually exclusive, or valid for a given model, customer, market, revision, or date. This helps prevent invalid product combinations.
Why is variant management important for manufacturers?
Manufacturers need variant management to control product complexity, reduce engineering rework, improve manufacturing accuracy, and maintain traceability across product families, BOMs, changes, and orders.
How does rule-based configuration prevent errors?
Rule-based configuration validates choices before they move downstream. It prevents incompatible options, missing dependencies, outdated revisions, and invalid BOM structures from reaching manufacturing.
Is Nora IPLM useful for teams moving away from Excel-based option lists?
Yes. Nora IPLM replaces disconnected spreadsheets with controlled configuration data, lifecycle traceability, rule validation, and connected BOM workflows inside a PLM environment.
How is PLM variant management different from CPQ software?
PLM variant management controls the engineering product family, option rules, applicable BOMs and revisions. CPQ usually manages customer-facing configuration, prices and quotes. Organizations may connect the two processes, but they serve different purposes.
What is effectivity in variant management?
Effectivity determines when or where a component, option or rule applies, such as by date, revision, market or product variant. It helps teams resolve valid configurations and avoid mixing components from incompatible revisions.
Ready to simplify product complexity?
Manage every variant with confidence.
Explore how Nora IPLM helps manufacturers manage variants, reduce BOM duplication, and generate accurate configured BOMs from one connected PLM environment.