On this page

Part numbering for robotics, from internal IDs to approved sources

For robotics part numbering, assign one stable internal ID to each controlled item and store its revision separately. Record the manufacturer part number (MPN) and supplier SKU in the source relationship. Decide whether to reuse an item, revise it or create a new one under the team's approved identity policy.

That lets a buyer find the right source without turning a distributor's stock number into the robot's engineering identity. It also lets an engineer find every use of a screw before changing its specification.

Consider R-01, a fictional indoor inspection robot. Its internal sensor ID is SN-400, revision A. The selected synthetic manufacturer's number is SEN-X12. Distributor S-01 sells it under SKU DIST-1204. Those values describe three different identities.

Separate internal part numbers, revisions, MPNs and SKUs

Record R-01 value What it identifies
Internal item SN-400 The sensor item controlled by the engineering team
Item revision A The selected controlled definition of that item
Manufacturer part number SEN-X12 The manufacturer's product designation
Distributor SKU DIST-1204 The distributor's catalogue designation
Approved source relationship S-01 for SN-400 A The reviewed route for sourcing the selected item
Assembly relationship R-01 contains one SN-400 A A use of the item in this product release

A distributor SKU may change while the manufacturer's part remains the same. A manufacturer may also revise a specification without changing a familiar catalogue label. Preserve the source documents and review the change rather than relying on text equality.

Keep revision outside the internal ID. Writing HR-300-B into an item-ID field can make a revision look like a second item unless the system explicitly treats that format as an item-revision key. Use HR-300 and B in separate fields in the BOM template.

Choose a numbering scheme the team can maintain

The example uses DM for drive module, HR for harness and SC for screw because those labels are easy to follow in an article. A production policy can use sequential numbers or controlled family prefixes. Define the allocation rule, one register that prevents duplicates and one person or role responsible for issuing IDs.

Avoid encoding supplier, current price or release status into the permanent ID. Those properties change. Deep classifications can also become awkward when an item crosses discipline boundaries, such as a purchased motor assembly containing electrical and mechanical parts.

Before creating a number, search the item register by description, manufacturer number, specification and known aliases. Check the exact definition. A similarly named screw with another length or finish may need a different item, while the same SC-130 A used at the sensor and inside a drive module should reuse its existing ID.

Decide whether to retain, revise or replace the item

Record the decision against the proposed change and the team's own identity policy. There is no universal rule that every interchangeable change keeps its number, or that every drawing edit requires a new number.

Proposed event Decision in this example Review required
SC-130 A appears in another assembly Reuse SC-130 A Confirm the same controlled screw definition and add a relationship
Typo corrected in a sensor description Keep SN-400 Decide whether the corrected metadata needs a controlled revision
S-01 changes a catalogue SKU for the same SEN-X12 Keep SN-400, review the source record Verify manufacturer identity, specification and approved buying route
Harness strain relief improves during manufacture Keep HR-300, revise A to B ECO-017 approves the drawing change and serial applicability
Candidate sensor changes a controlled installation interface Hold a new item decision for engineering approval Assess requirements, installation, acceptance and coexistence needs

For HR-300, ECO-017 retains the installation interfaces and acceptance requirements. Drawing DW-HR-300 advances from A to B. The team approves B for serials 003–005 while keeping A for 001–002. That is the agreed decision for this fixture, rather than a general promise of interchangeability.

A new sensor proposal still needs technical assessment, even if its supplier calls it a drop-in replacement. The robot component supplier-change checklist covers the specification and evidence questions before acceptance. Buying approval and engineering acceptance should identify their own accountable owners.

Run a where-used check before approval

Search both current proposals and released structures by internal item ID. Preserve the parent, selected revision, quantity and applicable configuration in the result. For SC-130 A, R-01 uses two screws directly and two DM-100 A modules each use four.

The where-used result explains the ten-per-robot total and exposes both installation contexts. A specification change must be reviewed at both uses. One successful fit check at the sensor cannot silently cover the drive modules.

Before merging a proposed item change, record the reason, affected uses, definition before and after, approval decision and build applicability. Keep historical releases pointing at their selected revisions. The configuration guide then answers which robot serials receive the approved change.

For your next new part, ask a colleague to find its approved definition and buying source using only the internal ID. If they need a chat message to distinguish two entries, fix the identity or source records before issuing another number.

Move faster without compromising engineering rigour.

Review one product release, its change decisions and supporting evidence with Arc.