Do parts have revisions? What the "form fit function" rule tells us

PDXpert product lifecycle management software easily lets you identify your parts and the documents that define them. As designs evolve, the original documents get revised, and new parts are created from these revisions. This has led some to conclude that parts must also have revisions, and that these revisions must be reflected in the manufacturing management system (MRP/ERP). We'll show that, even though they may be revised, parts aren't identified by revision.

Part interchangeability and the "no revision" rule

Proper part identification is the foundation of efficient inventory management. Part identification and interchangeability must be correctly applied because a part number identifies its inventory bin location.

One part number = one bin location. Revision is irrelevant.

A part is interchangeable with another part when their relevant functional and physical properties are equivalent. Part interchangeability — that is: affecting form, fit, or function — applies to design iterations of the same part, as well as to substitute or alternate parts. (For a complete discussion, see Applying principles of interchangeability to your bill of materials.)

Practically speaking, if a revised part can be intermingled in production inventory with previous iterations of that part without any negative effect, then the part iterations are interchangeable and the part number remains unchanged. Similarly, if one supplier's parts can be intermingled with another's, then these are also interchangeable and can be stocked in the same warehouse location.

However, perhaps after revising the documentation (or qualifying another supplier's part), the new part iteration is not compatible with previous iterations (or you simply want to track its usage because you're not sure of its effect). In this case, it's not interchangeable. You must issue a new part number, and the new part must be stocked in a different inventory bin.

Therefore, design revisions that do not affect a part's interchangeability are, for inventory and production management purposes, irrelevant. Of course, any part may go through an evolution which is directly traced to revisions of the part's documentation. But the well-accepted rule is that parts are not identified by revision.

Parts binned by revision simply have weird part numbers

At some companies, assigning new part numbers can be overly bureaucratic1, and this may lead to using revision identifiers to distinguish non-interchangeable iterations.

Of course, the whole point of using the form-fit-function rule is to decide when a part iteration requires a new number and inventory location. If your warehouse is locating non-interchangeable parts by revision, then the revision has become a de facto part number suffix. Although this sidesteps assigning a new part number, it merely shifts the burden to a more complicated decision about whether a particular revision justifies the creation of a new inventory bin.

The unhappy result is that all parts get marked with revision identifiers, and all changes are treated as non-interchangeable, creating many more inventory locations than would otherwise be necessary. Unfortunately, this directly conflicts with accepted practice that revision-level changes are interchangeable, so every affected BOM must be examined, and possibly revised, manually. The significant labor savings offered by a PLM system, which updates BOMs automatically based on revision-level interchangeability, goes out the window.

The product development and inventory management costs of maintaining superfluous number+revision bins overwhelms any perceived savings in avoiding a new part number.

Authoritative references reflect the "no revision" rule

Many authorities have confirmed that parts don't have revisions, and we have not found any authority that supports part revisions. Some useful comments from our PLM book list:

Revision level - A number or letter representing the number of times a part drawing or specification has been changed.

Clement, et al.: Manufacturing Data Structures, page 265

Revision levels are preferably excluded from the identification number.

Guess: CMII for Business Process Infrastructure, page 81

Revision letter, a letter added to a drawing or other document number to indicate that a change was made to the original document.

Part number, a number used to uniquely identify a part or item. ... The revision letter is not included with the part number.

Samaras: Configuration Management Deskbook, definitions on pages 495 & 499

The revision letter or number is the change status or level of the document....

Rule: The Revision is not part of the part number.

Rule: Revision is never marked on the parts.

Rule: Never stock by revision level.

Watts: Engineering Documentation Control Handbook, page 52 (author's emphasis)

The term revision refers to any change after that drawing has been released for use.

DOD-STD-100, page 700-7

Part numbers shall not include the drawing revision.

And in DOD-STD-100 section 402.6f

d. PINs [Part or Identifying Numbers] shall not include the drawing revision.

MIL-STD-100G, section 406.6

Part database records have revisions

As an important side note, certain records that are about a part (called "part metadata" in a product lifecycle management system) can and should be tracked by revision, similar to other documentation that defines the part.

In PLM software, the part database record may include, for example, approved supplier sources, a bill of materials and document references. Obviously, these data elements aren't the actual physical part, but define important technical characteristics for its construction or acquisition. Since these attributes can change over time, and you may wish to formally control these changes, an approved set of values are identified by a unique database record revision. The record's lifecycle specifies how the revision's characteristics may be used.

The PLM/PDM part record can also support information that's useful, but not necessary for defining and managing the part under revision control. Such data might include MRP-related attributes (cost, lead time, packaging quantity, etc.), initial design sketches, vendor tooling quotes, customer requirements, regulatory compliance information, as-built inspection records.

Nonetheless, a physical part's identification remains distinct from both its defining documents' revisions and its database records' revisions contained in the PDM software.

Using interchangeability rules to auto-update bills of materials

PDXpert PLM software relies on part interchangeability rules to simplify bill of materials management. If you retain the part number for each interchangeable change, PDXpert immediately updates every bill of materials upon release of the new part record revision. A document that's listed as a reference to a part or document record will likewise display its most current released revision.

Similarly, when a supplier part record is revised (say, with a new data sheet or specification), the Sources list automatically reflects that revision without requiring an engineering change.


  1. The main reason why part number assignment can become cumbersome is that the part number is meaningful, and must be "protected" from incorrect categorization. If every new part number must be created or reviewed by a part number czar, it's time to abandon significant part numbering in favor of sequential assignment.

Contact us if you'd like to discuss how the general concepts in this note may be applied to your situation. We'd be happy to address other PLM software good practices — ask us!

Slideshow image