What is model-based definition (MBD)?
Model-based definition is an approach to creating 3D models so that they effectively contain all the data needed to define a product. With MBD, the model becomes the source authority that drives all engineering activities. This model may further be used downstream by suppliers and across organizations within an enterprise.
Why MBD?
For years, engineers used 2D drawings to deliver product manufacturing information—even as they designed models in 3D. Now, using model-based definition (MBD) methods, engineers embed product data directly in the 3D models, creating a single, reliable source of truth for the whole extended team that prevents errors and saves everybody time.
PTC’s solutions for model-based definition
GD&T and tolerance analysis are part of a broader model-based definition journey. MBD is an approach to creating 3D models that effectively contain all product data needed to define a product.
GD&T is the process of annotating designs, using a symbolic language to define the allowable geometry dimensions. Tolerance analysis allows engineers to understand how stack-up of variation impacts the design quality and manufacturability.
Use these resources to assess your MBD needs:
Model-based product development (MBPD)
Model-based product development is the process of using the native CAD model throughout the entire product development cycle. Beginning with concept development, including industrial design, ranging all the way through detailed design, simulation, tooling development, manufacturing process development and service instructions, the native CAD model drives the digital thread through the entire product development lifecycle.
What the experts say
Model-based definition has a barrier to adoption and it is the tools currently available. Take a look at what else Jennifer Herron, the founder and CEO of Action Engineering and author of the book Re-Use Your CAD: The Model-Based CAD Handbook.2D, had to say.
The benefits of Creo GD&T Advisor
The GD&T Advisor Plus allows you to reuse the accurate parts of your legacy GD&T annotations while highlighting errors that they may have and providing recommendations on how best to resolve any uncovered problems.