Start with what stays common
Identify the parts, interfaces and engineering knowledge that should be reused. For example, two offerings might share a housing while using different covers or connection modules.
Product Variant ManagementOne platform.
One platform.
Purposeful variations.
Keep what is shared connected to what can change. Organize options, choices and product definitions so teams can develop a family with a clear configuration context.
Explore the variant exampleDefine the family before multiplying the recordsOne product family.
One product family.
Many purposeful variations.
Variant management organizes the deliberate differences within a product family across its lifecycle. A family brings together a reusable foundation and the features that distinguish its offerings, such as materials, connections or performance levels. Managing those relationships helps the team explain what stays common, what varies and which offering a particular set of choices describes.
Make the difference explicit
Describe which capabilities vary and who owns the allowed choices. A new offering should have a reason to differ, a definition to review and a clear relationship to its family.
Follow the choice beyond engineeringCarry each choice.
Carry each choice.
Connect the product lifecycle.
A product choice continues to matter after design. Planning, engineering, manufacturing and service need different information about the same offering. Follow one representative variant through these disciplines to identify what each team receives, what it contributes and what must be confirmed before the next handoff.
Product planning
Describe the customer need and the offering it justifies. Separate an intended market choice from a design decision still awaiting review. The output is a recognizable offering brief: who it serves, which capabilities distinguish it and what remains to be resolved.
Engineering
Keep physical modules and relevant software requirements in context. Agree which system owns each definition and how the teams refer to the same offering. A connection change, for example, may need both a mechanical interface description and a corresponding software requirement.
Manufacturing
Identify the selected product that informs build preparation. Confirm what the receiving structure, process plan and instructions must describe. The build team needs to recognize the applicable materials and operations for this offering, including any plant-specific preparation.
Service
Make the applicable configuration recognizable when selecting supporting information. A technician needs the product in front of them, not the entire family of possibilities. Establish how the installed arrangement will be identified when locating instructions or considering a replacement component.
Choose a measurable improvement areaReuse engineering knowledge.
Reuse engineering knowledge.
Respond to new needs.
Evaluate variant management through the work it changes: serving a customer segment, reusing engineering knowledge or preparing an offering for release. The five areas below help frame an improvement objective for a real product family. Compare the current effort with the proposed way of working; results depend on the platform, information quality and process.
Greater market share
Serve meaningful customer segments through planned offerings. Assess whether a proposed variation addresses a distinct use case rather than simply increasing the catalogue.
Which unmet need deserves a distinct offering?
Reduced engineering costs
Reuse an understood engineering foundation. Look for duplicated drawings, specifications or reviews that could instead refer to a maintained common module.
Where is the team repeating work that should remain common?
Strategic flexibility
Plan how the family can respond to changing needs. Identify which adaptations fit its existing interfaces and which would require a deliberate platform revision.
Which change can the platform accommodate, and which needs new engineering?
Improved product quality
Concentrate review around shared parts and platforms. Separate evidence that applies across the family from checks triggered by a changed material, interface or operating condition.
What evidence can be reused, and what must be checked for this variation?
Faster time to market
Start from maintained knowledge rather than disconnected copies. Examine how quickly the team can assemble the information needed to review a proposed offering, without assuming a fixed schedule reduction.
Where does a new offering wait for information or reconciliation?
Make customer variety practical to deliverMeet the customer need.
Meet the customer need.
Make the variation practical.
Before adding another offering, translate the customer request into a clear delivery question. A requested capability may fit a planned choice, require a new module or expose a limit in the current platform. The questions below help make that decision before the team commits to a product it must manufacture and support.
Name the need
What will the customer use differently, and which existing offering falls short?
Test the platform fit
Can the need be addressed through a planned choice, or does it require a new module and review?
Prepare the handoff
Which manufacturing and service information must distinguish this offering from the rest of the family?
Groupe Beneteau: product diversity in practice
PTC’s customer story describes the coordination of customized boats, engineering changes and production information using Windchill and connected enterprise systems. Watch for how a customer choice travels into the work of another team.
Watch the Groupe Beneteau film
See how a platform becomes a specific offeringKeep the core.
Keep the core.
Configure the difference.
Compare the common housing with the cover and connection modules that change between these two drive-unit configurations. The shared-core strip identifies what stays fixed; each reading then connects selected choices with the definition to review. A dependency between cover and connection makes the role of family logic concrete.
Shared across both configurations
- Common base housing
- Shared mounting reference
Keep the standard arrangement clear.
The standard arrangement pairs the common drive housing with a mechanical cover and a terminal connection. Its selected choices identify the product definition the team intends to review.
- Cover choice
- Standard mechanical cover
- Connection choice
- Terminal connection
- Definition to review
- Review the parts, drawing and product context that describe this arrangement.
Describe the variation and its dependency.
The instrumented arrangement keeps the same housing while selecting an instrumentation cover and a plug connection. The relationship between those choices belongs in the family’s defined logic.
- Cover choice
- Instrumentation cover
- Connection choice
- Plug connection
- Definition to review
- Review the changed modules and the product information needed for this arrangement.
Example choice rule: an instrumentation cover requires a plug connection. The team previews, tests and releases the logic for the intended product family.
A planned combination and a released engineering definition serve different purposes. Review the selected configuration, applicable revisions and required deliverables before using it downstream.
Connect each capability to a working questionDefine the choices.
Define the choices.
Put variant features to work.
Move from the product-family idea to the information the software must maintain: reusable choices, selection logic, planned offerings and resulting structures. Open a capability for its specific role and evaluation context. Test the relevant functions against a familiar family, with the proposed applications and entitlements established first.
Option pools and option sets
Maintain reusable choices and define their scope.
Read capability details+
An option pool holds options, choices and rules; an option set references the definitions needed for a particular product context. A shared connection option may be useful across several families while each family exposes only its relevant choices. Agree who can maintain those definitions before reusing them.
Advanced selection logic
Describe parameter-based configuration needs.
Read capability details+
Parameters and constraints support configurable modules. They are distinct from choice-based assigned expressions; identify the kind of input and relationship the family actually needs. A dimensional input and a named equipment choice may require different modeling approaches.
Product family matrix
Review planned family configurations together.
Read capability details+
Ask how planners will compare offerings, recognize gaps and maintain the family over time. Reviewing configurations together can make it easier to discuss an unplanned combination or an offering that needs revision. Product Family capabilities have a separate application and entitlement scope.
Independent assigned expressions
Maintain selection logic independently of the item.
Read capability details+
Where supported and entitled, expressions can be revised without iterating the part or usage to which they are assigned. Agree the review responsibility for a logic-only change.
Rules logic
Describe the relationships among choices.
Read capability details+
Include, exclude and conditional rules serve different selection needs. Define meaningful test cases; accepting a configured combination does not replace engineering verification.
Multiple development streams
Plan parallel development and reconciliation.
Read capability details+
Identify which team owns each branch and how changes will be reviewed when work converges. Confirm the selected product and supported release rather than assuming one universal branching workflow.
Change management
Review rule and product changes in their lifecycle context.
Explore engineering change managementRead capability details+
Local and global rule effectivity and connected downstream changes need deliberate scope. Agree the applicable dates, receiving records and interface ownership.
Configure variant BOMs
Keep selection inputs separate from the resulting structure.
Explore BOM managementRead capability details+
A variant specification retains configuration inputs. Generation depends on its type and the selected process; review the resulting parts, revisions and applicability before downstream use.
Applications, supported releases, permissions and licenses determine available behavior. Advanced expressions, independent expressions, dynamic positioning and Product Family functions have distinct scope.
Choose the system for the information it ownsConnect PLM and ALM.
Connect PLM and ALM.
Give every record a home.
Choose tools around the records that need to vary. Windchill addresses the physical product definition and its configuration context; Codebeamer addresses requirements and application-lifecycle work. A product with embedded software may need both perspectives, with a clear reference connecting the intended hardware and software offering.
Windchill
PLM product structures, options and configurable families.
Begin with the physical product definition, its modules and the configuration process the organization intends to maintain. Identify which product structures and option records engineers must control as the family changes.
Explore Windchill
Codebeamer
ALM for product and software development.
Begin with requirements and application-lifecycle work that varies across offerings. Identify which requirements and verification activities apply to each offering, then define their relationship to physical product records and the supported integration scope.
Explore CodebeamerSelecting both products does not establish automatic synchronization. Agree authoritative records, interfaces, mappings and review responsibilities for the proposed environment.
Apply the product-family approachDifferent markets.
Different markets.
Choices built into the product.
Variant management starts with the differences a product family needs to support. Explore these industry situations to connect a customer or program choice with the product definition, build information and service context it affects.
Electronics & High-Tech
An electronics family may share a board platform while varying connectors, enclosures or installed software. Identify which combinations belong to each offering and which requirements and verification activities apply when a module changes.
Hardware and software scope
Explore Electronics & High-TechWhich hardware and software combination defines the offering your team needs to review?
Aerospace & Defense
A shared equipment platform may support different program or mission needs. Keep the selected modules and applicable product references recognizable so a program-specific variation can be distinguished from the broader family during production and sustainment.
Program-specific offerings
Explore Aerospace & DefenseWhich program choices and product references distinguish this configuration from the rest of the family?
Industrial Machinery
A machine family can combine a common base with different drives, attachments or control packages. Follow a selected option into the assembly and build preparation, then establish how the resulting machine will be recognized when service information is needed.
Machine and attachment choices
Explore Industrial MachineryWhich machine option changes both the build preparation and the information needed for service?
Clarify the configuration scopeVariant questions.
Variant questions.
Connect options, rules and definitions.
Agree the records, logic and responsibilities before expanding the configuration model.
How is an option pool different from an option set?
An option pool holds reusable options, choices and rules in a product or library context. An option set references the selected definitions and rules needed for a particular scope. Agree ownership and reuse of those definitions before building multiple sets.
Does a variant specification always create a variant BOM?
No. A specification retains selection or filtering inputs; deliverable generation depends on its type and the configured process. Some specifications can be saved without requesting deliverables, while other specification types do not support every generation capability.
Do configuration rules certify that a product will perform correctly?
Rules express the combinations and constraints the team defines. Previewing and testing those rules helps review configuration behavior, while engineering evaluation, required verification and release decisions remain separate responsibilities.
Are all options and variants capabilities included in every installation?
Advanced options/variants, independent expressions, dynamic positioning and product-family functions have distinct entitlement and configuration scope. Choice-based assigned expressions and parameter/constraint-based advanced selection logic also serve different needs. Review the required applications, release, permissions and licenses.
Will a change automatically update ERP, CPQ and manufacturing?
The interface, supported records, mappings, applicability and release rules must be defined for each receiving environment. A connected product platform does not by itself establish universal synchronization or responsibility for downstream updates.
Connect the platform to the product familyBring the variation.
Bring the variation.
Build the shared context.
Show us where product choices become difficult to manage across the lifecycle.
We’ll help frame the platform, configuration records and connections around the work your team needs to do.