Standardization Push

Replace special parts with standard ones wherever function allows: fewer references, more volume, lower price.

Time45 min
FormatSmall group
StageGenerate

Standardization Push: what it is and why it works

A standardization push replaces special, near-duplicate parts with a smaller set of preferred standard parts wherever function allows. You extract the full parts list across a product family, group parts by function and geometry, and identify near-duplicates that differ without any value to the customer, for example in brand, color or minor dimensions. For each group, a preferred variant is chosen and the others are migrated to it. A design gate then blocks new non-preferred parts from entering the system.

Every unique part number carries costs that do not appear in its price: supplier management, drawings and documentation, inspection, storage, spare parts and the risk of shortage. Reducing variety concentrates volume on fewer items, which improves purchasing leverage, simplifies logistics and makes quality easier to control. The logic belongs to industrial engineering's long tradition of variety reduction. Standardization is closely linked to complexity cost analysis, which puts a price on variety, and to modular architecture, which applies the same thinking at the level of whole modules. Design rules make the result stick. Standardizing does not mean choosing the most capable part for every application; it means choosing a preferred part that meets real requirements at the best overall cost.

What you need

The full parts list across the product family, with part numbers, descriptions and attributes
Annual volumes and prices per part
Technical requirements for each part group, such as pressure rating, material and connection type
Inventory and spare parts data
Access to the product data management or ERP system for the design gate

What you get

Part groups by function and geometry with near-duplicates identified
A preferred variant for each group and a migration plan for the others
A preferred parts list available to designers
A design gate rule that blocks new non-preferred parts without justification

When to use it

When the catalog grows faster than the sales.

How to do it, step by step

Extract the full parts list across the product family.
Group parts by function and geometry.
Find near-duplicates that differ without customer value.
Decide a preferred variant per group and migrate the rest.
Block new non-preferred parts at the design gate.

Worked example: Ball valves on packaged pump skids

Illustrative scenario — figures are realistic but not from a real company.

An OEM of packaged pump skids for industrial water and chemical plants noticed that its catalog of purchased components was growing faster than its sales. A quick search showed 212 different ball valve part numbers in active use across the product family.

The team extracted all 212 valve part numbers with their attributes and annual volumes from the ERP system.
They grouped them by nominal pipe size, body material, end connection and ASME pressure class, which produced 38 functional groups.
Within groups, many valves differed only by brand, handle color or locking device, with no functional or customer-specified reason.
For each group, the team chose a preferred valve, typically one or two variants per group where a genuine requirement justified it, bringing the list to 61 part numbers. Customer-specified brands were kept only where the contract required them.
The preferred list was loaded into the product data system, and any new valve outside it now required a documented justification at the design gate.

Result. Volume per valve part number more than tripled on average, and a new frame agreement with two suppliers reduced valve prices by about 9 percent. Inventory of valves fell significantly, and assembly errors due to similar-looking valves decreased. The team noted that the design gate was essential: without it, variety would have crept back within a year.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

Choosing the most expensive, highest-rated part as the standard for every application.Select preferred parts that meet real requirements, and allow more than one variant per group where needs genuinely differ.
Cleaning up the parts list once without controlling new additions.Install a design gate that requires justification for any new non-preferred part.
Ignoring customer or contract specifications that require specific parts.Check contracts and customer standards before migrating parts, and document exceptions.
Migrating all parts at once, disrupting production and spare parts.Migrate at natural points such as design revisions or new orders, and manage existing stock.

Frequently asked questions

How do you reduce part number proliferation?

Extract the full list of part numbers, group them by function and key attributes, identify near-duplicates, and select a preferred part for each group. Migrate existing designs to the preferred parts when practical, and control new additions with a design gate. The control step is essential; without it, the number of parts tends to grow back.

What is a preferred parts list?

A preferred parts list is a controlled list of approved standard components that designers should use first, such as fasteners, valves, bearings or electrical parts. Each preferred part has been checked for technical suitability, availability and cost. Using parts outside the list is allowed only with justification, which keeps variety under control.

Does standardization mean over-specifying parts?

Not necessarily. Standardizing on the highest-rated part for every application can raise cost. The goal is to find the best overall cost, including purchasing, inventory and handling. Sometimes a slightly higher unit price is justified by volume and simplicity; sometimes two preferred variants per group are better than one.

Origin

Parts standardization — industrial engineering; variety reduction program lineage (L. P. Sullivan).

Used in these playbooks

Complexity pruning quarter 1 quarter

One quarter to cut what variety costs: measure complexity, standardize parts, modularize the platform and delete the functions nobody misses.

Related methods

More in “Generate”

Produce reduction ideas from functions, design rules and process rethink.