Model Based Definition
Model Based Definition - Capturing and conveying manufacturing requirements
Model Based Definition
基于模型的定义能够在 3D 模型内生成产品的完整数字化定义，从而取代传统绘图。 产品团队可以将模型用作单一数据源，从而通过整合产品和流程信息来节省宝贵的时间，并确保完全把握意图，同时将其与模型相关联。 与以绘图为中心的工作流程相比，NX 减少了在工程文档上花费的时间，推动了下游验证和制造工具，并减少了后期的更改和产生的废料。 由于尺寸和公差信息来源相同，这样就不必担心图纸和模型彼此不一致的问题。 此外，带注释的 3D 模型比复杂的图纸容易理解，这样就减少了培训需求和出错的机率。
Model Based Definition is made up of powerful features that allow you to build a custom solution. Read more about these features below.
Leveraging Legacy Data
Not every project begins with a clean sheet. Convert to PMI automatically converts drawing views and objects to corresponding model views and PMI objects saving tremendous time when leveraging legacy data. With Convert to PMI, you can use legacy drawings to add intelligence to 3D models quickly and easily. Convert to PMI is highly customizable with options to convert entire drawings or individual sheets, views and annotation objects. A conversion report provides a detailed summary results. Convert to PMI enables support for processes based on 3D models with much lower cost and higher quality of data.
Replacing the Universal 2D Drawing
People are familiar with 2D drawings and use them as a means of defining a finished product. 2D drawings contain standard symbology that is universally understood and interpreted. However, in some cases, the existence of multiple, redundant data required to define a manufactured part can lead to deviations in the final 3D form. Interpretation errors, duplication errors or revision inconsistencies can contribute to costly mistakes that quickly translate into lower quality and productivity.
The use of 2D drawings for the purpose of communicating downstream production requirements adds an unnecessary burden to the product development cycle. A simple change in the product definition not only requires updated 3D digital data, but also necessitates numerous engineering changes to all 2D documentation associated with the product. Since it takes time to maintain this documentation, the lifecycle for implementing a product change grows with the extent of its associated 2D data.
Product teams can capture and share engineering requirements within the 3D model, thereby permitting full utilization of the design intent, eliminating the need for 2D drawings and ensuring that the final product complies with its engineering specifications.