Contacts
Get in touch
Close

Contacts

Romania, Cluj-Napoca – 400157
Str. Ploiești Nr. 9

Romania, Vama – 447350
Str. Fermei Nr. 14

+40 774 463 429

info@inteliscience.net

ASME Y14.41 vs ISO 16792 (2026): Which MBD Standard?

ASME Y14.41 vs ISO 16792: The Short Version

ASME Y14.41 vs ISO 16792 is a choice between two closely related rulebooks for digital product definition data: annotated 3D models, with or without a drawing. The decisive difference lies underneath, in ASME Y14.5 versus ISO GPS tolerancing. inteliScience’s Siemens NX engineers build one NX standard and template per system, so a part never mixes both.

Aspect ASME Y14.41 ISO 16792
PublisherASME (United States)ISO/TC 10, Technical product documentation
First edition20032006, based on ASME Y14.41
Current edition (October 2026)Y14.41-2026, issued 30 June 2026ISO 16792:2021, third edition, April 2021
MethodsAnnotated model; model and drawing graphic sheet3D model-only; 3D model with 2D drawing
Tolerancing underneathASME Y14.5ISO GPS: ISO 1101, ISO 5459, ISO 8015, ISO 129-1
Default for a size toleranceEnvelope principle (Rule #1)Independency principle; envelope only where specified
In Siemens NXASME drafting standard plus your templatesISO drafting standard plus your templates

The Problem: Same PMI on Screen, Different Part on the Shop Floor

A pin dimensioned ⌀20 ±0.1 looks identical in an ASME part and an ISO part. It is not the same requirement. Under ASME Y14.5, the size tolerance also limits form, so the pin must fit inside a perfect ⌀20.1 cylinder. Under ISO 8015, size and form are independent unless the envelope requirement is specified with a circled E.

The CAx Interoperability Forum writes exactly this into its STEP AP242 practices: the dimensioning standard travels in the file, and “if an ASME standard is specified, the tolerance principle is assumed to be the envelope requirement unless otherwise specified. Likewise, if an ISO standard is specified, the tolerance principle of independence is assumed” (CAx-IF, version 4.1, June 2024).

So the MBD standard is not paperwork. A supplier working for a US-headquartered group and a German OEM can receive two NX models with the same PMI on screen and two different acceptance criteria. On a drawing, the title block says which system applies. In a model-based definition, the data set has to say it.

If the line between PMI and model-based definition is still blurry in your team, our comparison of MBD vs PMI sorts that out first.


Editions and Scope of ASME Y14.41 and ISO 16792

ASME Y14.41 is the older standard: first issued in 2003, now in its 2026 edition. ISO 16792 is its international adaptation: first published in 2006, now in its third edition from 2021. Both define how digital product definition data sets are prepared and revised, and both allow a model-only method and a method where a drawing accompanies the model.

Year ASME Y14.41 ISO 16792
2003First edition, issued 15 August 2003
2006First edition, based on ASME Y14.41
2012Revised edition, May 2012
2015Second edition
2019Revised edition, issued 23 January 2019
2021Third edition (April 2021), “adapted from ASME Y14.41:2012”
2026Revised edition, issued 30 June 2026

The scope statements show how differently the two are built. ASME Y14.41 “defines exceptions and additional requirements to existing ASME standards”, and “where no exception or additional requirements are stated, existing ASME standards shall apply” (ASME). ISO 16792:2021 complements existing standards and takes its interpretation rules “from the original definition standards, e.g. ISO 129-1 and ISO 1101” (clause 1). ASME is a layer of exceptions on top of the Y14 family; ISO keeps pointing back to the ISO GPS standards.

The 2021 ISO edition added assembly part identification and movable parts in assemblies, moved former practices to Annex A and added examples in Annex C (ISO 16792:2021, foreword). Its introduction says the text was adapted from ASME Y14.41:2012, so ISO tracks the 2012 ASME baseline, not 2019 or 2026.

ASME’s Y14 document status list of 20 August 2026 shows Y14.41-2026 as published, issued 30 June 2026. It also shows Y14.5-2018 reaffirmed in 2024 with a revision in progress, and Y14.47, Model Organization Practices, at its 2023 edition (ASME Y14 document status). We found no free summary of what changed in 2026, so the comparison below rests on the 2019 edition, the only one a contract signed before July 2026 can name.

Our advice: do not relabel your NX templates as “Y14.41-2026” until someone has read the new edition against your rules. A template that names an edition it was never checked against is worse than one that names the old edition honestly.


ASME Y14.41 vs ISO 16792: The Differences That Change Your Models

Clause by clause, the two standards are close. The UK National Physical Laboratory compared ASME Y14.41-2019 with BS ISO 16792:2021 and found that they follow a similar format, cover the same topics and reference equivalent standards, with ASME being more self-contained while ISO refers to an existing standard and highlights its recommendations (NPL Report MS 46, February 2023). The differences that change an NX model are listed below, from that report and from the ISO text.

Topic ASME Y14.41-2019 ISO 16792:2021 Effect on an NX model
Tolerancing underneathASME Y14.5 (2018 edition referenced)ISO GPS: ISO 1101, ISO 5459, ISO 8015, plus ISO 129-1Different drafting standard, symbols and defaults
Default for features of sizeEnvelope principle (Rule #1)Independency principle; envelope only where specifiedSame PMI, different acceptance
UnitsMust be stated in the data set: metric or U.S. customaryUnit of measurement stated if other than millimetersPart units are fixed when the NX part is created
Management data on the modelPlaced on an annotation planeLocation not specifiedReserve one plane or model view in the template
Security or protection markingMarking requirements for classified information, company intellectual property and government notices (clause 5.4)Protection marking (clause 5.5)NX PMI security markings
ViewsRefers to ASME Y14.3ISO 128-3, plus exceptions for saved views and section views (clause 5.6)A fixed model view set per part class
Extra model contentNot coveredAssembly model completeness, part reference numbers, identification by color, greyscale, mapping or transparency, installation models (6.4 to 6.7), thin parts whose thickness is not modeledISO assembly templates need more
Model-only identificationDesign activity identification and CAGE codeLegal owner of the data setPart attributes in the template
Data set content codeRefers to ASME Y14.100Classification codes 1 to 5 (informative Annex B)An attribute or note stating the code
TermsBasic dimension, direction-dependent tolerance, limited application of a toleranceTED, direction-dependent specification, restricted areaSame NX commands, different labels

Three of these rows deserve more than a table cell.

The default for features of size changes acceptance, not presentation. Every other difference changes what the model must contain or where it shows it. This one changes whether a part that measured fine is good or scrap. It is the reason we never let a template carry PMI from both systems.

ISO 16792 brings its reference chain with it. An ISO data set needs ISO 1101, ISO 5459, ISO 8015, ISO 129-1 and ISO 11442 on the shelf. ISO 16792 cites most of them without a date, which by its own rules means the latest edition applies. ASME Y14.41-2019 cites dated standards such as Y14.5-2018 and Y14.100-2017, and Y14.41 takes precedence if one of them conflicts with its text (NPL, Table 1).

ISO asks two things in clause 4.1 that NX templates often miss. A data set that claims conformity “shall include a reference to this document either in the data set itself or in a document referenced by the data set”, and the “computer application(s) and version(s) used to develop the data set shall be specified with other management data”. In an NX shop, that is a note and an attribute that state ISO 16792:2021 and the NX release, written once into the template instead of remembered on every part.

ISO also ties annotation planes to coordinate systems: a plane “shall be parallel to the orthogonal coordinate surface of the absolute coordinate system or a user-defined coordinate system of the 3D model”, with other directions allowed where needed (clause 5.1.2.3). A good reason to fix the coordinate systems in your start parts.


Which Standard Your MBD Needs: US Customers vs European Supply Chains

Let the tolerancing system decide, and let the customer decide the tolerancing system. If a customer’s drawings and data sets reference ASME Y14.5, their models belong under ASME Y14.41. If they tolerance to ISO GPS, ISO 16792 is the matching practice standard. Picking the MBD standard on its own, apart from GD&T, produces exactly the mixed parts a supplier cannot interpret.

Your situation Standard to work to What to agree in writing
US customer, defense or aerospace programASME Y14.41 with ASME Y14.5Editions of both (Y14.41-2019 or -2026, Y14.5-2018), units
European OEM whose drawings reference ISO GPSISO 16792:2021 with ISO GPSGeneral tolerance note, where the envelope requirement applies
Supplier with customers on both sidesBoth, but one per part numberWhich customer’s standard each part follows, in the PLM data
Own product, no customer ruleThe system your existing drawings useNo change of tolerancing system inside the MBD project
Exchange as STEP AP242Either; the file states whichThat the export carries the dimensioning standard

The US side has a head start. Siemens describes ASME Y14.41-2003 as “immediately adopted by several industrial organizations, as well as the United States Department of Defense” (Siemens white paper, 2017), and the DoD codified model-based definition in MIL-STD-31000 Revision A in 2013. If your customer’s contract names an ASME edition, follow that edition, not the newest one.

Many companies in Germany, Austria and Switzerland already define their parts to ISO standards, which puts them on the ISO route without a new decision. The trouble starts when a European supplier copies its ISO templates into a US program, or when a US-headquartered group asks its European plants for “MBD to ASME” while their legacy drawings say ISO 8015.

We’d advise against a “dual” template that tries to satisfy both systems at once. At inteliScience, a Siemens NX, NXOpen and Teamcenter specialist with NX engineers in Cluj-Napoca, we set up two clean template sets instead, one ASME and one ISO. They are cheap to maintain. A part where nobody can say which default applies is not.

Both standards also let you keep a drawing next to the model. Whether that drawing stays your master for now is a separate decision, weighed in our article on model-based definition versus a 2D drawing master.


How ASME Y14.41 and ISO 16792 Map to Siemens NX PMI Settings

Siemens NX has no single “Y14.41” or “16792” switch. The drafting standard you load sets the Drafting and PMI annotation preferences; NX ships ASME, ISO, DIN, JIS, GB and ESKD standards among its defaults. Everything else the standards ask for lives in templates, model views, attributes and notes. In its 2017 standards white paper, Siemens states that PMI authored in NX complies with ASME Y14.41, ISO 16792 and the JEITA standard for 3D part definition.

Requirement in the standards Where it lives in Siemens NX What we put in the template
Tolerancing system, symbols, defaultsDrafting standard (Menu > Tools > Drafting Standard), defaults in Customer Defaults under DraftingOne site-level standard per system, derived from the shipped ASME or ISO standard
Saved viewsModel views that hold the PMIA fixed view set per part class
Annotation planesOrientation chosen for each PMI objectPlanes tied to the absolute or a named coordinate system
Management dataPMI notes and part attributesA management view with standard, edition, units and NX release
Security or protection markingPMI security markingsCompany proprietary and export markings preset
Query and semantic PMIPMI associated with faces, datums and feature control framesCheck-Mate PMI checks before release
Model and drawing methodDrawing views that inherit PMI from model viewsA limited-dimension drawing template
UnitsPart units, set when the part is createdSeparate millimeter and inch seed parts

NX keeps drafting standards at five levels, named in the NXOpen LoadLevel enumeration: Shipped, Package, Site, Group and User (NXOpen reference, NX 1926). Put your company standard at site level, one per system. The same reference describes the part’s DraftingPreference as the object “to modify the Preference settings for PMI/drafting application”, which is why one loaded standard covers both the 3D PMI and the drawing.

This matters more with the June 2026 release, in which Siemens renamed the product from Designcenter NX to Designcenter and enabled “concurrent multi-user PMI operations” through Live Share (Siemens, 23 June 2026). Two designers annotating the same model at the same time need the same loaded standard.

Load the matching standard with NXOpen

When a part moves to another customer context, or when you clean up legacy parts, this journal does what Menu > Tools > Drafting Standard does and reports the part units, which ASME Y14.41 requires to be stated. It uses only the public NXOpen API.

# NX journal (Python): load the drafting standard that matches the part's
# MBD standard, then report the part units for the management data.
# The loaded standard sets Drafting and PMI preferences for new annotations.
# Run it with the PMI or Drafting application active, like the menu command.
import NXOpen
import NXOpen.Preferences

STANDARD = "ISO"   # name as listed in Menu > Tools > Drafting Standard, e.g. your site standard
LEVEL = NXOpen.Preferences.LoadDraftingStandardBuilder.LoadLevel.Site   # Shipped, Package, Site, Group, User

session = NXOpen.Session.GetSession()
work_part = session.Parts.Work
lw = session.ListingWindow
lw.Open()

builder = work_part.Preferences.DraftingPreference.CreateLoadDraftingStandardBuilder()
try:
    builder.Level = LEVEL
    builder.Name = STANDARD
    builder.Commit()
finally:
    builder.Destroy()

if work_part.PartUnits == NXOpen.BasePart.Units.Millimeters:
    units = "millimeters"
else:
    units = "inches"
lw.WriteLine(f"{work_part.Leaf}: standard '{STANDARD}' loaded at {LEVEL}, part units: {units}")

The members come from Siemens’ NXOpen reference: CreateLoadDraftingStandardBuilder on the DraftingPreferenceManager, available since NX 5, and PartUnits on BasePart. Loading a standard changes the preferences for what you create next; existing annotations are updated in a separate edit-settings step (NXJournaling example). Run it on a copy first.

The management note we put in every template

A setting is invisible to a supplier. A note is not. This is the text we start from; the edition and the application line change per customer and per release.

ISO template:
  DATA SET PREPARED IN ACCORDANCE WITH ISO 16792:2021.
  GEOMETRICAL TOLERANCING TO ISO GPS (ISO 1101, ISO 5459). ISO 8015 APPLIES.
  UNITS: MILLIMETERS.  CAD APPLICATION: SIEMENS NX <release>.
  CLASSIFICATION CODE <3, 4 OR 5> TO ISO 16792, ANNEX B.

ASME template:
  DATA SET PER ASME Y14.41-2019.
  DIMENSIONING AND TOLERANCING PER ASME Y14.5-2018.
  UNITS: <INCH OR MILLIMETERS>.  CAD APPLICATION: SIEMENS NX <release>.

This sets one part right. What’s missing for production: a written standard decision per customer, site-level standards and templates under change control, model content rules per part class, and an export check that proves the supplier receives what NX shows. Our MBD consulting for Siemens NX closes that gap, starting with a fixed-scope readiness assessment on five of your own parts.


Checklist: What to Settle Before the First MBD Release

Most problems with ASME Y14.41 and ISO 16792 are not misread clauses but decisions nobody wrote down. Settle these six before the first model leaves your design department without a full drawing.

  1. Standard per customer. For each customer, the MBD standard and the tolerancing standard, with editions, taken from contracts and existing data sets.
  2. One system per part. A rule, checked at release, that no part carries ASME and ISO PMI together.
  3. Site-level drafting standards. One per system, derived from the shipped ASME and ISO standards, loaded by templates rather than set by hand.
  4. Management view and note. Standard, edition, units, NX release and, for ISO, the classification code, in every template.
  5. Semantic PMI where software reads it. Datums and feature control frames associated with faces on every part a supplier will program from, checked by Check-Mate or a second application.
  6. People who can apply it. Designers who know both systems’ defaults and how NX implements them; our NX PMI and MBD training covers setup, semantic PMI, model views and the supplier export.

Our clear recommendation: write the standard decision first and configure NX second. The reverse order gives you templates that encode whoever set them up last.


Frequently Asked Questions

What is the difference between ASME Y14.41 and ISO 16792?

Both standards set requirements for preparing and revising digital product definition data, meaning annotated 3D models with or without a drawing, and ISO 16792 was first based on ASME Y14.41. In the ASME Y14.41 vs ISO 16792 comparison, the decisive difference is the tolerancing system each relies on: ASME Y14.5 with the envelope principle by default, or ISO GPS with the independency principle by default. Smaller differences cover units, where management data sits, security or protection marking, views and extra ISO clauses on assemblies.

What is the latest edition of ASME Y14.41 and ISO 16792 in 2026?

ASME Y14.41-2026 is the latest ASME edition; ASME’s Y14 status list, updated 20 August 2026, gives 30 June 2026 as its date of issuance, and it revises the 2019 edition. ISO 16792:2021, published in April 2021, is the third ISO edition and replaced ISO 16792:2015. Contracts and templates written before July 2026 can only name Y14.41-2019, so always check the edition, not just the number.

Can ISO GD&T (ISO 1101) be used in a model defined to ASME Y14.41?

Not cleanly. ASME Y14.41 defines exceptions and additions to the existing ASME standards and states that where it makes no exception, those standards apply, which for tolerancing means ASME Y14.5. ISO 16792 takes its interpretation rules from ISO standards such as ISO 129-1 and ISO 1101. A part that mixes both leaves the reader to guess whether a size tolerance also controls form, so we keep one system per part.

Does Siemens NX support both ASME Y14.41 and ISO 16792 for PMI?

Yes. Siemens states that PMI authored in NX complies with ASME Y14.41, ISO 16792 and the JEITA standard for 3D part definition, and NX ships ASME and ISO drafting standards that set Drafting and PMI preferences. The system is chosen per part through the loaded drafting standard and the template, so one NX installation can serve ASME and ISO customers side by side.

How much does it cost to set up Siemens NX for ASME Y14.41 or ISO 16792 MBD?

There is no general price, because the effort depends on how many part classes, customers and suppliers are involved and on how consistent your templates are today. Budget for the standards documents, a site-level drafting standard and templates per system, training and a supplier pilot. inteliScience offers an MBD Readiness Assessment on five of your parts, a one-week review with two workshop days at your site, at a fixed €4,900, and quotes in-house or live online NX PMI and MBD training after a short call, based on modules and group size.


Next Step

Working to ASME for one customer and to ISO for another? In an MBD Readiness Assessment, inteliScience’s Siemens NX engineers in Cluj-Napoca review five of your parts against the standard each customer requires, export them the way a supplier receives them and hand you a gap list and a roadmap. Talk to our NX engineers about your MBD standard



References

  • ASME, “Y14.41, Digital Product Definition Data Practices” (scope statement): https://www.asme.org/codes-standards/find-codes-standards/y14-41-digital-product-definition-data-practices (retrieved 2026-10-09)
  • ASME, “Y14 Document Status” (updated 20 August 2026; Y14.41-2026 issued 30 June 2026; Y14.5-2018 (R2024) revision in progress; Y14.47-2023): https://cstools.asme.org/csconnect/Filedownload.cfm?thisfile=160.pdf&dir=CommitteeFiles&preview=true (retrieved 2026-10-09)
  • ISO, “ISO 16792:2021, Technical product documentation, Digital product definition data practices”, third edition, 2021-04: https://www.iso.org/standard/73871.html; foreword, introduction, scope, normative references and clauses 3 to 5.1 from the public preview: https://cdn.standards.iteh.ai/samples/73871/29eb28fbe98f44f184ed4b147fb698f2/ISO-16792-2021.pdf (retrieved 2026-10-09)
  • Gregorio, Lorch, Hughes, “Model Based Definition: Recommendations for Supply Chain Integration”, NPL Report MS 46, Issue 2, February 2023: https://doi.org/10.47120/npl.MS46 (retrieved 2026-10-09)
  • CAx-IF, “Recommended Practices for the Representation and Presentation of Product Manufacturing Information (PMI) (AP242)”, version 4.1 (20 June 2024), section 4 “Defining the Dimensioning Standard”: https://www.mbx-if.org/home/wp-content/uploads/2024/06/rec_pracs_pmi_v41.pdf (retrieved 2026-10-09)
  • Siemens PLM Software, “Realizing a Digital Enterprise driven by standards”, white paper (2017): https://www.plm.automation.siemens.com/media/global/en/Siemens%20PLM%20Realizing%20a%20Digital%20Enterprise%20driven%20by%20Standards_tcm27-62124.pdf (retrieved 2026-10-09)
  • Siemens NXOpen .NET Reference (NX 1926): NXOpen.Preferences.LoadDraftingStandardBuilder, DraftingPreferenceManager, PartPreferences, NXOpen.BasePart: https://docs.sw.siemens.com/documentation/external/PL20191127135844554/en-US/nx_api_sc/nx/1926/nx_api_sc/en_US/nxopen_net/a07213.html, https://docs.sw.siemens.com/documentation/external/PL20191127135844554/en-US/nx_api_sc/nx/1926/nx_api_sc/en_US/nxopen_net/a07193.html, https://docs.sw.siemens.com/documentation/external/PL20191127135844554/en-US/nx_api_sc/nx/1926/nx_api_sc/en_US/nxopen_net/a07225.html, https://docs.sw.siemens.com/documentation/external/PL20191127135844554/en-US/nx_api_sc/nx/1926/nx_api_sc/en_US/nxopen_net/a00988.html (retrieved 2026-10-09)
  • Siemens NX Help, “Setting your Drafting and PMI standard” (earlier NX release, copy hosted by the University of Rochester): http://www2.me.rochester.edu/courses/ME204/nx_help/en_US/tdocExt/content/v/standard_stand_ov.xml
  • NXJournaling, “Update drawing (views, dimensions and annotations) to drafting standard”: https://www.nxjournaling.com/content/update-drawing-views-dimensions-and-annotations-drafting-standard-delete-named-title-block (retrieved 2026-10-09)
  • Siemens Designcenter blog, “Designcenter is for everyone: June 2026 release” (23 June 2026): https://blogs.sw.siemens.com/designcenter/designcenter-is-for-everyone-june-2026-release/ (retrieved 2026-10-09)
  • Wikipedia, “ASME Y14.41” (issue dates of the 2003 and 2019 editions): https://en.wikipedia.org/wiki/ASME_Y14.41 and “Model-based definition” (MIL-STD-31000 Revision A, 2013): https://en.wikipedia.org/wiki/Model-based_definition (retrieved 2026-10-09)

Cookie settings

Choose which services we may use on this website. Your choice is stored in your browser for 12 months. You can change it at any time via “Cookie settings” at the bottom of every page.

Strictly necessary

Stores your cookie choice. This cookie cannot be switched off.

Always active
Show cookies
NameProviderPurposeStorage period
is_cookie_consentinteliScienceStores your cookie choice and when you made it12 months

Google Analytics 4 measures page views, traffic sources and form use with a pseudonymous ID. Provider: Google Ireland Ltd. Data may also be processed by Google LLC in the USA (EU–US Data Privacy Framework).

Show cookies
NameProviderPurposeStorage period
_gaGoogleDistinguishes visitors with a pseudonymous ID2 years
_ga_<ID>GoogleStores the session state2 years

Google Ads measures which ads lead to enquiries (conversions) and lets us show our ads to previous visitors (remarketing). Provider: Google Ireland Ltd. Data may also be processed by Google LLC in the USA (EU–US Data Privacy Framework).

Show cookies
NameProviderPurposeStorage period
_gcl_au, _gcl_aw, _gcl_gsGoogleLinks ad clicks to enquiries90 days
_gcl_ls (local storage)GoogleLinks ad clicks to enquiries90 days
IDE (doubleclick.net)GoogleRemarketing and ad measurement13 months

Videos: YouTube videos only load when you press play (via youtube-nocookie.com). Only then does Google receive data.