Part numbering, and the argument you will have
Every organisation has this argument once and lives with the outcome for twenty years. It is worth having deliberately, because the losing option is the one that reads better on a drawing.
The three modes
Sequential. The next number from a counter. 510-0091 means nothing beyond being unique, which is the point — there is no information in it to become wrong.
Significant. The number encodes attributes: SCR-M3-08-SS is a stainless M3×8 screw. It is readable on a drawing, searchable by eye, and beloved by everyone who has to work with paper.
Pooled. Blocks allocated to teams, sites or systems — robotics draws from 7100–7199 — so numbers can be issued in parallel without a central service and without collisions.
The three are not exclusive. A tenant commonly runs sequential for parts, significant for documents, and pooled where a second site or a contract manufacturer issues numbers. Schemes are configured per object type.
Why significant numbering loses
It reads better, and that is a real benefit that costs a hidden one. A significant part number is a cached copy of attributes that will change.
The stainless screw gets re-specified in a different alloy. The number now says SS and the part is not. Two options follow, and both are bad: renumber it — breaking every drawing, BOM, purchase order and receipt that references it — or leave it, at which point the scheme lies and everyone learns to distrust it, which removes the readability that justified it.
The failure is slow. It takes three or four years for enough parts to drift that people stop trusting the encoding, and by then there are forty thousand numbers and no way back. That is why organisations that have been through it once choose sequential the second time.
The defensible middle is a short significant prefix for the thing that genuinely never changes — object type or broad class — and sequential digits after. SCR-0091 survives an alloy change; SCR-M3-08-SS does not.
Uniqueness scope is a decision, not a default
Unique across what? The tenant, a business unit, an object type, or a plant. Most tools assume one and never say which, and the assumption surfaces during an acquisition when two divisions both have a part 4420.
Declaring the scope explicitly means a merge is a configuration conversation rather than a data emergency. It also makes the question answerable in advance: if you acquire a company, do their numbers collide with yours, and what is the rule?
Reservations matter more than they sound. An engineer needs a number before the part exists — to put on a drawing, to send to a supplier for a quote, to reference in a specification being written today. A reservation holds it, so the number on the drawing is the number that gets created, rather than a placeholder somebody has to chase.
How it meets the rest of the product
A part number, once issued, never changes. Not on reclassification, not on a supplier change, not on a correction. It is identity, and the whole revision model rests on identity being stable — a number that can change is a number that cannot be safely referenced by a drawing printed last year.
Numbering is tenant configuration alongside object types and lifecycles, so a scheme change goes through the sandbox with a diff, a preflight against real data, and a rollback. Changing the scheme affects new numbers only; existing ones are identity and stay as they are.
Deep copy and save-as respect the scheme, so copying a product structure issues new numbers where the copy policy says to create new parts and references the originals where it does not. Getting that wrong is how a save-as quietly duplicates a hundred parts nobody wanted.
How it meets your ERP
Numbering is where the identity conversation with your ERP starts, and the default depends on the connector. In most landscapes engineering originates numbers for parts it creates and they publish outward; in SAP landscapes the material number is frequently SAP's and has been for years.
Either way it is a recorded decision in the system-of-record matrix rather than a behaviour that varies quietly by deployment. The scheme also has to respect what the target can hold — an ERP with a sixteen-character item field constrains a scheme that assumed twenty, and finding that out at publication is worse than finding it at configuration.
Manufacturing PLM never renumbers an ERP item, and does not accept a renumber in the other direction. A number that changes underneath an open purchase order is a number nobody can reconcile against the receipt when it arrives.
Where the boundary is
Manufacturing PLM will not retrospectively renumber your existing parts, and would decline the project. Renumbering breaks every external reference — drawings, purchase orders, customer documentation, supplier tooling — and the benefit is almost never worth it. The workable path is a new scheme for new parts and the old numbers left alone.
It also does not enforce meaning in a significant scheme. If your scheme encodes material in positions five and six, Manufacturing PLM validates the format rather than checking that the character matches the part's material attribute — that consistency is exactly what drifts, and pretending to guarantee it would be the wrong promise.
Facts
| Modes | Sequential · significant · pooled, per object type |
| Recommended | Short type prefix, sequential digits after |
| Uniqueness scope | Declared — tenant, business unit, type or plant |
| Reservations | A number held before the part exists |
| Once issued | A part number never changes |
| Scheme changes | Sandbox, preflight, rollback; affect new numbers only |
| ERP | Who originates numbers is a recorded matrix decision |
| Not offered | Retrospective renumbering · semantic validation |
Frequently asked
Should we use significant part numbers?
Usually not, though they read better. A significant number is a cached copy of attributes that will change — when the stainless screw is re-specified in another alloy, the number either lies or has to be reissued, and both outcomes destroy the readability that justified it.
Is there a defensible middle ground?
Yes. A short prefix for what genuinely never changes — object type or broad class — with sequential digits after. SCR-0091 survives an alloy change where SCR-M3-08-SS does not, and it keeps most of the at-a-glance benefit people actually want.
What does uniqueness scope mean?
Unique across what: the tenant, a business unit, an object type, or a plant. Most tools assume one and never say which, and the assumption surfaces during an acquisition when two divisions both turn out to have a part numbered 4420.
Can we reserve a number before creating the part?
Yes, and it matters more than it sounds. An engineer needs a number for a drawing or a supplier quote before the part exists. A reservation means the number on the drawing is the number that gets created, rather than a placeholder somebody has to chase.
Can a part number change later?
No. It is identity, and the entire revision model rests on identity being stable. A number that can change is a number that cannot safely be referenced by a drawing printed last year, a purchase order raised last month, or a unit shipped in March.
Will you renumber our existing parts?
No, and we would decline the project. Renumbering breaks every external reference — drawings, purchase orders, customer documentation, supplier tooling — and the benefit almost never justifies it. Use a new scheme for new parts and leave the old numbers alone.
Do you validate that a significant number is correct?
Only its format, not its meaning. If your scheme encodes material in positions five and six, Manufacturing PLM checks the shape rather than confirming the character matches the material attribute. That consistency is precisely what drifts, and guaranteeing it would be a false promise.