Part Number Keyspace Capacity Calculator
Part numbering schemes fail slowly and then suddenly, usually in a busy class that was given too few digits. This calculator tells you how many numbers a scheme can issue and how many years it will last before you have to change a field length or rework the format.
Your numbers
Number of distinct prefixes, each with its own serial range.
Ranges held back for customer-specific, test or legacy numbers.
Your results
Assumes issuance and existing usage spread evenly across classes. In practice a few busy classes run out first, so check your fullest class separately.
Years to exhaustion vs serial length
Sweeps Serial positions per class from 2 to 10, holding your other inputs fixed.
Numbering scheme consolidation help
Optionally ask how to map and cross-reference part numbers from multiple legacy schemes.
Optional. The tool and every export work without this. No spam.
How to use it
Pick the character set allowed in the serial portion. Excluding the letters I and O, which are easily confused with 1 and 0, leaves 24 letters, or 34 characters with digits. Enter the number of serial positions per class and how many prefix classes exist. Reserve a share for ranges you intentionally skip, such as customer-specific numbers or test ranges. Then add what you have already issued and the annual rate, plus growth. The result is the years left on a per-class average basis, so test your most active class separately by setting classes to 1 and entering its figures.
The method
Capacity per class is the alphabet size raised to the number of serial positions, and total capacity multiplies by the number of classes. Usable capacity subtracts the reserved share. With a growth rate g and starting annual issuance n, cumulative numbers after t years equal n times the quantity one plus g to the t, minus one, divided by g. Solving for t gives the natural log of one plus remaining times g over n, divided by the log of one plus g. With zero growth, it reduces to remaining divided by annual issuance. The chart shows each added position multiplies capacity by the alphabet size, so one extra digit extends life dramatically.
- Capacity = alphabet^length x classes
- Years = ln(1 + remaining x g / n) / ln(1 + g)
- Zero growth: years = remaining / annual issuance
Design guidance
Short, non-significant numbers avoid the need to renumber when a part changes category, which is the main failure of significant schemes. If you embed meaning such as material or family in the number, expect uneven fill across classes and plan for overflow ranges. Also check external limits: field lengths in the ERP, label barcodes, supplier EDI formats and legacy interfaces may cap the length well below what you would like. Avoid look-alike characters, leading zeros that spreadsheets strip, and separators that downstream systems reject. Document the scheme so that new engineers do not invent exceptions.
Frequently Asked Questions
Should part numbers be significant or non-significant?
Most modern guidance favors non-significant numbers for the primary identifier, with classification held in attributes. Significant numbers are easy to read but break when a part is reclassified, and they fill unevenly.
Why exclude the letters I and O?
They are easy to confuse with the digits 1 and 0 when read from a drawing, label or handwritten note. Excluding them reduces transcription errors at the cost of a slightly smaller alphabet.
What reserve share is sensible?
Ten to thirty percent is common. Reserve for pre-release or test numbers, customer-assigned numbers, and gaps from cancelled requests that you choose not to reuse.
Can I reuse retired part numbers?
Generally no. Historical orders, certificates, serial genealogy and supplier records reference the old number, so reuse creates traceability ambiguity. Regulated industries typically prohibit it outright.
If you are consolidating several numbering schemes after an acquisition, Netray can help map and propose cross-references from your ERP data, with your team approving every mapping.
Related Tools
Duplicate Item Merge Savings Calculator
Size the business case for merging duplicate item master records: yearly admin saving, split inventory carrying cost and payback on the merge project.
Engineering & PLMBOM Error Cost of Poor Quality Calculator
Quantify what BOM line errors cost when they are found late, and see the chance that a released BOM is completely clean.
Quality & InspectionData Quality Sigma Level Calculator
Express ERP data quality like a manufacturing process: defects per million opportunities, sigma level and the share of records with every field correct.
ERP Migration & SelectionData Cleansing Batch Effort Calculator
Plan a data cleansing or migration clean-up: how many records need manual attention, how many hours, how many weeks and what it costs.
More Engineering & PLM tools
See all- SAP Super BOM Design Worksheet
- SAP Engineering Change Number Checklist
- SAP Document Info Record Template
- SAP Change Master and Revision Level Log
- SAP Engineering Change Request (ECR) Template
- SAP BOM Usage and Item Category Reference
- SAP Engineering Change Obsolescence Exposure Calculator
- SAP Engineering Change Affected Materials Impact Worksheet
- Cloud MRP BOM Data Cleanup Worksheet