A maker may receive a 3D model, a drawing, a preview, and an export of the same product. Each file can look finished. That does not make each file the authority for the product requirements.
Before production starts, the handoff should say which definition controls. If that choice is silent, the maker has to guess which note, dimension, or picture wins.
A product definition can be more than one file
ISO 16792:2021 is a standard for preparing, revising, and presenting digital product definition data. It calls that information a data set. A product definition data set is one or more computer files that disclose the physical and functional requirements of a product, either directly or by reference.
The standard supports two methods: a 3D model only, and a 3D model together with a 2D drawing in digital format. It sets out requirements so the information stays consistent between the model and the drawing.
The document is written for digital product definition, especially 3D mechanical computer-aided design. It says the practices can also be applied to other disciplines, such as electronic design. The rules for interpreting dimensions and geometrical tolerances still come from the original standards, including ISO 129-1 and ISO 1101. This article does not restate those rules.
Say which document is original
ISO 16792 uses classification codes to say what sits on the drawing, what sits in the data set, and which one is original.
Code 1: the data elements are on the drawing, and the drawing is the original.
Code 2: the drawing is the original. A model, when one is provided, is supplementary.
Code 3: a model is paired with a simplified drawing. The data set is the original, and the model and drawing are used together.
Code 4: the data elements are in both the model and the drawing. Either one can be used on its own. The data set is the original.
Comments
Loading comments...
Log in to post, reply, mark contributions as helpful, or report a concern.
Code 5: the data elements are in the annotated model. No drawing exists.
A Goodiee handoff does not have to use these code numbers. The codes show the decision that should not stay implicit: the drawing controls, the model controls, or both are required together.
Keep the set consistent and identifiable
For a data set that follows ISO 16792, the standard requires a complete product definition. An example it gives is a design model, its annotation, and related documentation. It also says the information presented shall not conflict.
The current revision, and the computer applications and versions used to develop the data set, have to be specified with the other management data. The data set identifier has to be unique.
Related information can live inside the data set or be referenced from it. The standard's examples include parts lists, material specifications, and process and finish requirements. Related data that is not inside the data set may be revised on its own. That is one more reason to name the current controlling file.
An export is not automatically the authority
A NIST report published on 6 July 2011 describes model-based engineering as an approach in which a digital 3D representation is the normative source shared through the product lifecycle. The report says the primary challenge is to organize the intent in the master model, then translate that intent accurately into the derivative formats used downstream.
It also says derivative files have moved beyond simple viewing. They are used for archival, machining, and inspection. Those uses still need quality assurance of the translation between the original CAD data and the derivative format.
That 2011 report is not a current software specification. It does not say a 3D model is always the authority. ISO 16792 still allows the drawing to be the original. The narrower point is this: a file that was exported, previewed, or converted is not automatically equivalent to the controlling definition.
A short handoff workflow
Step 1: name the controlling definition
State whether the model, the drawing, or the pair is the authority for this revision.
Step 2: label everything else
Mark previews, screenshots, and converted files as references unless one of them is the named authority.
Step 3: record identity
Include the revision. When the workflow depends on a particular application, also name the application and version used to develop the controlling file.
Step 4: look for conflict
If a dimension, note, or requirement disagrees across the files, stop and correct the set before either file is treated as ready.
Step 5: confirm the file the maker will use
The creator states the design intent and which file controls it. The maker confirms which received file will be used for the physical process, and asks when an export does not match the named authority.
Quality check
One controlling definition is named for this revision.
Supplementary files are labeled as supplementary.
The revision is visible.
Conflicting requirements are resolved before production.
A converted file is checked against the controlling definition before it is used as that definition.
Goodiee's view
A maker should not have to infer the authority from whichever file opens first. Name the controlling definition, name the revision, and say whether the other files are required or only helpful. An easier file to preview is not a reason to treat it as the product requirement.
Limits and counter-case
Many jobs have one agreed production file and no model-and-drawing pair. ISO 16792 does not have to be applied to a single print, cut, or embroidery file. The decision matters when more than one file could be read as the requirement. This article does not interpret geometrical tolerances, and it is not a claim that any particular export format preserves annotations.
What varies
The right authority depends on the file type, whether a drawing exists, the software and version that created the data, whether annotations survived translation, and the discipline of the product. A mechanical model, a print graphic, and a machine-specific export can follow different rules.
Next action
Check the rest of the information that has to travel with a design file before a maker assesses the job.
Evidence
ISO 16792:2021 specifies requirements for preparing, revising, and presenting digital product definition data sets, supports a 3D model-only method and a 3D model with a 2D drawing, and sets requirements so the information stays consistent between the model and the drawing.[1]
ISO 16792:2021 defines a product definition data set as one or more computer files that disclose, directly or by reference, the physical and functional requirements of a product.[1]
ISO 16792:2021 classification codes 1 and 2 identify the drawing as the original, with the model supplementary under code 2. Code 3 uses the model and simplified drawing together. Code 4 allows the model or the drawing to be used individually. Code 5 places the data elements in the annotated model and has no drawing.[1]
ISO 16792:2021 requires a conforming data set to provide a complete product definition, says the presented information shall not conflict, requires the current revision and the computer applications and versions used to develop the data set to be specified, and requires a unique data set identifier. Related data such as parts lists, material specifications, and process and finish requirements are integral to or referenced by the data set.[1]
NISTIR 7796, published on 6 July 2011, describes model-based engineering as an approach in which a digital 3D representation is the normative source through the product lifecycle, identifies accurate translation from the master model into derivative formats as a primary challenge, and says derivative uses such as archival, machining, and inspection still need quality assurance of that translation.[2]
Goodiee’s view
A maker should not have to infer the product authority from whichever file opens first. Name the controlling definition and revision, and label other files as required or only helpful. A file that is easier to preview is not, for that reason, the requirement.
Limits and counter-case
Many jobs have one agreed production file and no model-and-drawing pair. ISO 16792 does not have to be applied to every print, cut, or embroidery file. This article does not interpret geometrical tolerances, and it does not claim that any export format preserves annotations.
What varies
The controlling file depends on the file type, whether a drawing exists, the software and version that created the data, whether annotations survived translation, and the product discipline. A mechanical model, a print graphic, and a machine-specific export can follow different rules.
Sources & verification
Each numbered link in the evidence section maps to a source below.
National Institute of Standards and Technology · Research · Published July 6, 2011 · Accessed
Content owner: Goodiee · Reviewed by: Alexander Luis · Next review: October 19, 2027 · Report a correction
Reference this resource
Cite this article
Use the reference below, or import a file into your reference manager to apply your required citation style.
Goodiee. (October 26, 2026). When more than one file describes the product, state which one controls. https://goodiee.com/learn/state-which-product-definition-controls
