s that competing data management processes may create their own variation identifiers. A PLM system can provide a sequential revision "overlay" to the software developer's seemingly-arbitrary, and generally non-sequential, version.
And, given the wider role for revisions in the IPC standards, we would propose that you cannot have a version without also specifying an associated revision.
Except in specialized cases, there's little general support for using the term "variation".
Iteration describes the unique combination of an item's particular revision at a specific lifecycle phase.
MIL-STD-100 only uses "version" (once) to refer to a part. Based on the context, we believe that the more appropriate term would be "variation":
406.13 Change requiring new identification. When a repair part within an item is changed so that it is no longer interchangeable with its previous version, it shall be assigned a new PIN.
The term "revision" is used extensively. As an example:
The CAGE Code, drawing format size letter, and drawing revision letter are not considered part of the drawing number.
MIL-HDBK-61A, interestingly, seems there was no need to actually define the term "revision", though its meaning is presumed by context:
Configuration baseline (baseline). (2) An approved and released document, or a set of documents, each of a specific revision;...
Notice of Revision (NOR). A document used to define revisions to configuration documentation which require revision after Engineering Change Proposal approval.
However, a version is explicitly defined
(1) One of several sequentially created configurations of a data product.
(2) A supplementary identifier used to distinguish a changed body or set of computer-based data (software) from the previous configuration with the same primary identifier. Version identifiers are usually associated with data (such as files, databases and software) used by, or maintained in, computers.
And, reinforcing that documents have revisions while software has versions (pg 4-34):
ACTIVITY: Configuration Status Accounting: Identify data file(s) and document representations of revisions/versions of each document/software delivered, or made accessible electronically
Finally, on page 5-19 (citing ASME Y14.55M):
Revisions to Drawings
- Drawing revision identification
- Any change to a drawing, including a change to Rights-in-Data, must be recorded in the revisions block of the affected drawing.
- Record revision status, identification of change authorization documents, or description of changes, and change approvals, and if multi-sheet, revision status of sheets
MIL-STD-973 has some interesting contextual definitions:
3.70 Notice of Revision (NOR) . A document used to define revisions to drawings, associated lists, or other referenced documents which require revision after Engineering Change Proposal approval.
22.214.171.124.4 Consolidation of multiple changes into a single unrelated ECPS may be combined into a single revision to a document provided that:
a. All changes apply to the same end item.
b. All changes apply to the same revision/version...
126.96.36.199 Software identifiers. For each CSCI, the contractor shall identify its corresponding Computer Software Components (CSCs) and Computer Software Units (CSUs). For each CSCI, CSC, and CSU the contractor shall issue/obtain a software identifier, which shall consist of a name or number, and a version identifier, and shall relate the software to its associated software design documentation; revision; and release date. The contractor shall embed the software and version identifiers within the source code, and provide a method for display of the software and version identifier data to the user upon command.
EIA-649-1998: The EIA committee also didn't feel the need to explicitly define revisions, but uses the term throughout the standard:
configuration identification: ...(3)...maintain[s] document revision relationships to product configurations.
Methods of identifying documents...includes at least...organization, a unique identifier..., and a revision indicator (n