What is configuration &
variant management in PLM?
Configuration and variant management helps engineering teams define the options, features and parts that make up a family of related products. Instead of maintaining an unrelated BOM for each model, teams work with shared components, controlled product choices and rules that determine which combinations are valid.
Within product lifecycle management (PLM), those choices can be connected to engineering revisions, approvals and downstream product structures. This makes it easier to distinguish the complete product family from the exact configuration selected for one order, market or use case.
Choose a valid product definition.
Product configuration is the process of selecting compatible features, assemblies and options for a particular product. Dependencies, exclusions and effectivity rules establish what can be selected together and what belongs in its configured BOM.
Control differences across the family.
Variant management organizes the models and versions that result from those choices. It keeps shared parts reusable while maintaining visibility into the differences between regional products, customer-specific configurations and released revisions.
In practice, the two disciplines work together: BOM management provides the product structure, configuration rules define valid selections, and engineering change management helps control updates to shared parts and released variants.
One product family.
Every variant connected.
Compare the models. Check the options. Apply the rules. Keep every configuration connected to the shared product definition.
More choices.
One clear view.
Bring models and variants into one controlled product family. Compare configurations side by side and see which choices make each product different.

Every option.
Its place in the family.
Review models, options, and features in one matrix. Reuse shared parts and modules while keeping the differences between variants visible.

Valid choices.
Repeatable logic.
Control which parts and options belong together. Apply dependencies, exclusions, and effectivity rules before generating the configured BOM.

The selected variant.
The exact parts.
Filter the shared 150% BOM into the 100% BOM for a product, order, market, or customer. Give manufacturing and procurement the structure they need.

Reuse the foundation.
Shared parts and modules across the product family.
Make the choices clear.
Options and rules connected to the configuration.
Build the right variant.
A precise BOM for manufacturing and procurement.
Grow the product range.
Keep one source of truth.
A new variant shouldn’t mean another BOM to maintain. Keep the shared structure, selected options, and product history together.
One definition.
Room for every variant.
Bring models, options, and features into one controlled product family. Keep engineering and manufacturing working from the same definition.

Reuse the engineering work.
Build on shared parts and modules. Add product choices without rebuilding the structure for every model.
Shared structures and options
A 150% BOM, or Super BOM, holds the possible parts and options for a product family. Reuse the common structure when defining individual variants.
Catch invalid combinations.
Make dependencies, exclusions, and effectivity part of the configuration logic. Validate selections before they reach production.
Configuration rules
Manage regional models, optional assemblies, and customer-specific requirements through repeatable rules rather than rebuilding the product structure each time.
Keep the history in reach.
Follow a configured BOM back to its options, source structure, rules, and revisions. Keep the product context attached.
Revisions and engineering changes
Connect configurations with documents, CAD data, approvals, and engineering changes. When a shared part changes, teams can review its impact on related configurations.
Give each team the right view.
Engineering reuses the product definition. Manufacturing and procurement work from the selected configuration. Product and quality keep its context.
A connected product definition
Manage option availability and trace each variant through revisions and released structures. Keep the selected product, market, or customer configuration connected to its source.
Every option in.
The exact BOM out.
Start with the product family’s 150% BOM. Apply the selected options and rules to generate the 100% BOM for the variant you need.
Define once.
Reuse across the range.
Build a Super BOM for the product family, with reusable modules and options. Keep every possible part in the shared structure before selecting the configuration.

Choose the options.
Check the combinations.
Select the model, market, or customer options. Validate dependencies and effectivity so the selected combination follows the product family’s rules.

The right product.
The right BOM.
Generate the 100% BOM for the selected configuration. Give manufacturing and procurement the exact parts, with the source structure and selected options still traceable.

See the choices.
Follow the result.
Watch how a reusable product structure becomes the configured BOM for a selected variant.
Product variant example.
One family. One valid build.
Consider an industrial pump manufacturer offering multiple motor voltages and seal materials. The product family uses many common components, but each order must contain a compatible combination. A shared product structure and configuration rules help teams define that build without manually recreating the entire BOM.
Industrial pump range
The common platform includes the pump housing, impeller and mounting hardware. A customer selects the requirements that change the motor and seal assemblies.
- SharedHousing, impeller and mounting components
- Motor230 V or 400 V option
- SealStandard or chemical-resistant option
- ControlMotor controller matched to the chosen voltage
A precise BOM for the selected pump.
- 1Choose requirements
The selected build uses a 400 V motor and a chemical-resistant seal.
- 2Check compatibility rules
The motor choice requires a matching controller; the alternative 230 V controller is excluded from this build.
- 3Derive the configured 100% BOM
The output contains the shared pump components plus the selected motor, controller and seal. Unselected alternatives stay in the wider product family, not this build.
- 4Maintain revision context
When a shared component changes, engineering can review which released configurations are affected before updating the appropriate structures.
This is a conceptual manufacturing example, not a customer case study or a claim about a preconfigured Nora IPLM pump template. Explore MBOM management for downstream manufacturing structures, or review the dedicated configuration management software guide for detailed capabilities.
Your product family.
Its wider context.
Explore the
configuration software.
See how options, rules, and configured BOMs work together in Nora IPLM.
Make room for
customer requirements.
Explore variant management for automotive suppliers and their product families.
Manage the range.
Keep the shared foundation.
Explore product configuration for equipment manufacturers.
Get to know
configuration management.
What to know before you define your next product family.
What is configuration and variant management?
Configuration defines valid combinations of options, features, and parts. Variant management controls the product versions created from those choices. Nora IPLM connects both to BOMs, revisions, and engineering changes.
What is a 150% BOM?
A 150% BOM, or Super BOM, contains all possible parts and options for a product family. Rules filter this shared structure into the exact 100% BOM for a selected variant.
What does a 100% configured BOM include?
Only the parts and options required for a specific product, order, market, or customer configuration. It gives manufacturing and procurement a precise product structure to work from.
How do rules prevent invalid combinations?
Dependencies, exclusions, and effectivity conditions determine which options and parts apply to each variant. Teams validate selections before generating the configured BOM.
Can we manage customer-specific variants?
Yes. Use customer, order, market, or model requirements to select a configuration from shared product options and rules.
How are configurations connected to changes?
Selected options and configured BOMs stay linked to source structures, rules, revisions, and engineering changes. Teams can trace how a variant was defined and which product data was released.
What is the difference between product configuration and variant management?
Product configuration selects the valid options and parts for one product build. Variant management organizes and controls the different models and versions across the product family, including shared components, revisions and market-specific differences.
How does configuration effectivity work?
Effectivity determines when or where an option, part or rule is applicable. Depending on the configuration model, conditions may relate to a product version, market, date or other approved criteria, so the resulting BOM contains only applicable items.
When should engineering teams move beyond spreadsheets for product variants?
Spreadsheets become harder to maintain when multiple teams reuse parts, introduce options, change revisions or approve customer-specific builds. Connected configuration management helps organize rules and trace each selected BOM back to its source product structure.
More variants.
Less repeated work.
Bring your options, rules, and product structures together. See how Nora IPLM turns product choices into a controlled, configured BOM.
