MBD embeds GD&T, tolerances, and material callouts directly in the 3D model — eliminating the drawing as a separate deliverable.
2D drawings remain legally and contractually dominant in aerospace and defense; AS9100-certified shops often require them by default.
Mixed-mode workflows — a 3D model plus a minimal 2D drawing — offer the best of both for most production programs.
PMI (Product and Manufacturing Information) quality inside the CAD file is the single biggest factor in whether MBD actually works downstream.
Switching to MBD mid-program without updating your supplier qualification process is a fast path to inspection disputes.
What Is Model-Based Definition?
This is different from simply having a 3D model on file. Most engineering teams have had 3D CAD files for decades — but those models typically existed only to generate 2D print packages. MBD flips that relationship. The 3D model with embedded PMI is released, controlled under revision management, and transmitted to manufacturing partners as the governing document. Any 2D representations, if they exist at all, are considered reference-only.
MBD is formally defined in ASME Y14.41 (Digital Product Definition Data Practices) and has been adopted as a requirement on major aerospace programs, including Boeing’s 777X and various DoD platforms. The standard defines how PMI must be structured, what datum references must look like, and how model views should be organized to ensure unambiguous interpretation. Without adherence to Y14.41 or an equivalent, MBD can become inconsistent fast.
What 2D Drawings Still Do Well
First, 2D drawings are viewer-agnostic. A PDF, a printed sheet, or a TIFF file can be read by any machine shop, any quality inspector, and any auditor anywhere in the world with zero software dependency. No CAD license required. No concern about file format compatibility between CATIA, SolidWorks, NX, or STEP AP242. This matters enormously in a contract manufacturing environment where a part may move through multiple suppliers and inspection stations across its lifecycle.
Second, 2D drawings are legally unambiguous in most contract frameworks. Procurement contracts, first article inspection (FAI) packages, and AS9100 quality management systems have been built around drawing revision control. When a dispute arises, the drawing revision on the purchase order is the governing document — and everyone in the supply chain understands that. Replacing drawings with model files in regulated industries requires explicit contractual language and supplier qualification steps that most organizations have not yet completed.
Third, 2D drawings handle complex callout stacking cleanly. Weld symbols, surface texture, thread callouts, and special process notes often read faster and more reliably on a well-structured 2D print than scattered across a 3D model viewport.
Where 2D Drawings Create Real Problems
The most common problem is drawing-model disagreement. When a 3D model is updated but the drawing revision lags — or vice versa — the manufacturing partner is left to guess which document governs. This happens constantly in fast-moving development programs. It causes scrap, rework, and NCRs (nonconformances) that trace back to documentation, not machining error. In an AS9100 audit, this is a finding. It slows programs down in exactly the moments when speed matters most.
Second, 2D drawings do not transmit intent efficiently for complex geometry. A freeform surface, a multi-axis blended fillet, or a deep pocket with compound draft angles is extremely difficult to fully define on a flat sheet. Engineers add notes, add views, add sections — and the drawing becomes a reference document that still requires the machinist to open the 3D model to actually understand the geometry. At that point, the drawing is theater. The model is doing the real work, but it has no PMI and no formal authority.
Third, revision management across large drawing packages is expensive. A complex assembly with 50 detail drawings requires 50 revision cycles when a design change propagates. MBD consolidates that into a single model release with a single revision event — dramatically reducing the administrative overhead on engineering change orders (ECOs).
PMI Quality: The Hidden Variable in MBD Success
PMI must be associative to be reliable. Associative PMI is directly linked to the model geometry — if the geometry changes, the annotation updates or flags a broken reference. Non-associative PMI (annotations placed near geometry but not mathematically linked to it) is essentially a floating label. It can survive a geometry change completely unchanged, becoming silently incorrect. Most CAD platforms support associative PMI, but it requires disciplined authoring practice that many teams do not enforce.
PMI also needs to be organized into meaningful model views. A single 3D annotation cloud visible from any angle is not equivalent to a drawing with orthographic projections. Best practice is to create named saved views — front, top, section cuts, detail magnifications — that mirror the organizational logic of a good 2D print. Inspection technicians and CMM programmers need to navigate the model quickly. Without structured views, they lose that ability and revert to asking for drawings.
Finally, downstream software compatibility matters. PMI authored in CATIA needs to survive a STEP AP242 export and be readable in the CMM software, ERP system, or viewer your supplier uses. Test that chain before committing to a full MBD rollout.
MBD in Aerospace and Defense: Where the Adoption Is Real
These programs work — but they also illustrate the infrastructure required. Supplier qualification for MBD is a real process. It includes verifying that the supplier’s CAM software can ingest PMI and use it for toolpath generation, that their CMM software can consume the model directly for inspection programming, and that their quality management system has been updated to accept model files as governing documents under revision control. None of this is trivial, and none of it is free.
For suppliers operating in AS9100 and ITAR-regulated environments — like the certified partner network Nimble Manufacturing works with — documentation control requirements add additional layers. ITAR-controlled technical data transmitted as a model file must be handled with the same access controls as a drawing. The format is different; the compliance obligation is identical. Teams that conflate format modernization with reduced compliance burden will find themselves in front of an auditor explaining that decision.
AS9100 Rev D explicitly supports model-based approaches, but it requires that the organization define and control the product definition method — including format, validation, and revision authority.
Mixed-Mode Workflows: The Practical Middle Ground
In a well-structured mixed-mode workflow, the 3D model carries full PMI for use in CAM programming and CMM inspection. The 2D drawing — often called a minimal drawing or reduced drawing — carries only the title block, revision history, general notes, material and finish callouts, and a reference statement confirming the model is the geometric authority. Critical tolerances may be repeated on the drawing for quick reference during first article review, but they are not re-dimensioned independently.
This approach requires explicit documentation of the hierarchy. The contract, purchase order, or specification must state unambiguously which document governs in the event of conflict. Most quality systems recommend the statement: ‘In case of conflict between the model and the drawing, the model governs for geometry and the drawing governs for notes and material callouts.’ That sentence needs to be in your drawing template before you ship a single part under this system.
Mixed-mode is also the default recommendation for teams quoting through managed sourcing partners like Nimble Manufacturing, where the certified partner network spans multiple machining, sheet metal, and molding facilities — each with different CAD viewer capabilities.
Choosing the Right Approach for Your Program
For development and prototype work, a clean 3D model with a basic drawing or model-only package is usually sufficient. The geometry changes frequently, the tolerance stack is still being validated, and formal drawing revision cycles slow the team down. Submit the STEP file, include critical dimensions in a brief PDF, and use the DFM review process to catch manufacturability issues before committing to tight tolerances. Nimble’s free DFM review and 24-hour quoting process is structured specifically to handle development-phase documentation that is not yet fully locked.
For production and flight-critical hardware, invest in a proper mixed-mode or full MBD package with AS9100-compliant revision control. The cost of an NCR, a failed FAI, or a drawing-model conflict that triggers a stop-ship is orders of magnitude higher than the engineering hours required to do the documentation correctly the first time. CMM inspection — which Nimble includes with production orders — requires either a well-structured 2D drawing or a PMI-complete model to generate the inspection plan efficiently.
For ITAR-controlled programs, confirm your supplier’s data handling capabilities before transmitting any model files. A STEP file containing controlled geometry is a controlled technical document from the moment it leaves your network.
File Formats, Software, and Downstream Compatibility
STEP AP242 is the current international standard for transmitting MBD data, replacing the older AP203 and AP214 formats. AP242 supports semantic PMI (machine-readable GD&T that can be directly consumed by CMM software and CAM systems) rather than just graphical PMI (annotations that look correct but are essentially pictures of text). The difference matters enormously. Semantic PMI enables automated inspection plan generation. Graphical PMI requires a human to re-enter tolerance values — which reintroduces transcription error and defeats much of the efficiency argument for MBD.
CAD system support for AP242 semantic PMI export varies widely. CATIA V5/V6, NX, and Creo have mature AP242 export pipelines. SolidWorks support has improved significantly in recent releases but still requires validation against your specific downstream tools. Fusion 360 support for semantic PMI is limited and should be verified before committing to it on a production program.
On the receiving end, CMM software from Zeiss (Calypso), Hexagon (PC-DMIS), and Renishaw (MODUS) all support STEP AP242 import to varying degrees. CAM platforms including Mastercam, Hypermill, and Siemens NX CAM can consume PMI for feature-based machining. Validate the specific version compatibility in your supply chain — a theoretical standard and a deployed software version are not always the same thing.
Get a quote from Nimble’s certified partner network.
Upload your drawings and get a detailed quote within 24 hours. Free DFM review included.
- What Is Model-Based Definition?
- What 2D Drawings Still Do Well
- Where 2D Drawings Create Real Problems
- PMI Quality: The Hidden Variable in MBD Success
- MBD in Aerospace and Defense: Where the Adoption Is Real
- Mixed-Mode Workflows: The Practical Middle Ground
- Choosing the Right Approach for Your Program
- File Formats, Software, and Downstream Compatibility
Precision parts, quoted in 24 hours.
AS9100 and ISO 9001 certified partner network. CNC machining, sheet metal, injection molding, and more.

