Written By: Katherine Brown-Siebenaler
Engineers have experienced the positive impact of model-based definition (MBD) practices on downstream manufacturing and service productivity, yet most have not seen similar benefits in their own design workflows due to the limitations of their tool sets.
Historically, engineers have grappled with disjointed workflows and siloed software, using one platform for their primary CAD modeling work and multiple others for supporting capabilities in areas like simulation, generative design, and manufacturing. The upside to these tools is advanced functionality. However, this approach simply can’t compete with the benefits associated with model-based product development (MBPD), a design workflow built around a unified set of tools and a shared, native file format.
Without a common-model definition and MBPD framework, engineers are forced to switch between applications and rely on manual, unproductive workarounds to import, export, and translate data and models between applications. CAD tools like PTC Creo feature associative, parametric modeling, which ensures changes made in one part of the model are automatically shared with all related geometry. Unfortunately, specialized add-on tools break that design chain, leaving engineers trapped in a complex cycle where costly errors and detractions can hamper engineering innovation.