Component Libraries for CPQ Product Models
One positioner model. Forty-seven copies in the product catalog. Define components once in a library and reference them across configurators so updates propagate everywhere.
The challenge
One positioner model. Forty-seven copies in the product catalog.
A manufacturer of control valves and actuator assemblies maintains dozens of configurators for ball, butterfly, and globe valve lines. The same smart positioner, limit switch kit, and solenoid valve appear in many of them, each defined separately inside the product model. Product management updates the positioner price after a supplier revision and opens a spreadsheet to find every configurator that still carries the old number.
One line shows the new positioner spec. Another still quotes the discontinued housing material. A compatibility rule blocks an invalid pairing in the globe valve configurator but not in the butterfly line because someone updated only one copy. Sales sends a quote-ready configuration from the updated line while a dealer quote from the stale line fails review on the PDF.
Modular configuration composes platforms from slot-filling modules. Multi-level BOM configuration generates production hierarchy from a completed configuration. Configuration templates save proven quote baselines for repeat enquiries. Component libraries are different: Mercura holds one library definition per shared part with attributes, pricing, rules, and BOM data referenced by every product model that uses it.
Inquiry to config to price to approval to order should not depend on how many times product management copied the same part into separate configurators.
Define once
Component referenced across products
One update
Price and spec propagate everywhere
No drift
Same part, same rules in every config
How it works
How Mercura component libraries work
Product ops create component library entries in Mercura for shared parts: positioners, actuators, seal kits, control modules, and other building blocks used across valve lines or product families. Each entry carries attributes, pricing, compatibility rules, and BOM lines. Product modelers reference library components inside configurators instead of redefining them. When product management updates price, specification, or retirement status in the library, every referencing configuration picks up the change on the next quote. Model builders browse and search the library when authoring new products. Someone must govern library ownership, review which configs still reference retired parts, and avoid breaking references when a component splits into two library entries.
What's included
What component libraries cover
- Central library with single definition per shared component
- Reference-by-library across multiple product configurators
- Price and specification updates propagate to all references
- Compatibility rules inherited wherever the component is used
- Component versioning with change history
- Retired components removed from selection in one library action
- BOM lines on library components reused in product BOM output
- Search and browse for product model authors
The difference
Shared parts before and after component libraries
- Same positioner defined separately in each configurator
- Price updates require hunting every product model
- Compatibility rules drift between valve lines
- Discontinued parts remain selectable in stale configs
- Catalog maintenance grows with every new product line
- Shared parts defined once in the component library
- Library update reaches every referencing configurator
- Pricing and rules stay consistent across product lines
- Retirement applied everywhere in one library change
- New products reference existing library blocks
Real-world application
Example workflow: positioner library across valve lines
A builder of control valves and actuator packages maintained smart positioners and limit switch kits as separate definitions inside ball, butterfly, and globe valve configurators. A supplier price change meant updating each copy by hand and missing two lines on the first pass. After centralizing positioners in Mercura component libraries, product management updates price and specification once; every valve configurator that references the library part reflects the change on the next quote without a config-by-config hunt.
Business impact
Why component libraries are catalog architecture, not a parts spreadsheet
Component libraries turn a growing catalog from duplicated part definitions into referenced building blocks. They complement modular platforms, multi-level BOM output, configuration templates, and parametric models. Mercura does not replace your PLM as the engineering release system for new parts or your ERP item master. Someone must own library governance and migration when a shared part splits or retires. If the pain is "we changed the positioner price but three configurators still quote the old one", component libraries align inquiry, configuration, price, approval, and order with one maintained definition per shared part.
See one library update reach every valve configurator that references it
Book a demo and change a positioner price in the component library until every referencing product model quotes the new value without opening each configurator separately.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.