Heterogeneous peer-to-peer multi-CAD model control application method for product BOM

Abstract

This invention belongs to the field of product development and relates to a method for controlling heterogeneous, peer-to-peer multiple CAD models oriented towards a product BOM. This method enables developers to achieve hybrid control of heterogeneous multiple CAD models that are closely integrated with the product BOM and strictly consistent with the product's technical specifications during the product development process. It solves the problem of efficient and high-quality application of heterogeneous multiple CAD models in collaborative product development. Furthermore, this method can also facilitate better implementation of CAD software replacement work. It has significant practical value and high innovation.

Description

Technical Field

[0001] This invention belongs to the field of product development, specifically relating to a heterogeneous peer-to-peer multi-CAD model control application method for product BOM. Background Technology

[0002] A product BOM (Bill of Material) describes the composition of a product, defining the structural relationships between components, sub-components, and parts. It is typically defined and expressed using a tree structure and serves as a crucial carrier and output for engineering data and product technical status control during product development, making it indispensable. A CAD model is a vital output for product definition in complex product development. Generated using CAD tools, it provides a precise two-dimensional or three-dimensional definition of the product's geometry and physical characteristics. Since both the product BOM and CAD model express and define the product's composition and implementation, they are usually related in a one-to-one manner. A heterogeneous peer-to-peer CAD model refers to a heterogeneous CAD model that is identical to the original CAD model in terms of model identification, definition, and content expression, differing only in the CAD design tools and model format used.

[0003] Currently, collaborative product development involves the extensive use of heterogeneous CAD models. For example, CAD models of supporting equipment provided by different suppliers are often heterogeneous, and these models are also heterogeneous from the CAD models used by the product's master designer. How to ensure collaborative design work based on the same model definition and expression by all parties during collaborative product development, as well as between the master designer and assistant designers (supporting equipment developers), is a crucial issue that must be addressed in model-based collaborative product development. The current industry practice to address this is to utilize the peer-to-peer model conversion function of CAD software tools, with a designated person (usually the equipment manager) converting the original CAD model to a peer-to-peer model. The converted model is then saved in a designated shared folder for use by all parties in the collaborative product development process. The problem with this approach is that the manual conversion and management of peer-to-peer CAD models, detached from the product's BOM and the control over the product's technical status, cannot guarantee the timeliness of the conversion and application, or ensure consistency with the product's technical status. This easily leads to problems such as waiting for the model to be generated before the collaborative design process, or using an incorrect model, impacting the efficiency and quality of product development.

[0004] Furthermore, regarding CAD software replacement, CAD tools are essential core software in product development. The replacement process faces the following challenges: existing CAD software has a long history of use, abundant historical data, and stable functionality and performance, while new software, lacking application iterations, still has room for improvement in functionality and performance. Directly replacing legacy software with new software may negatively impact the product's development progress and quality, posing a significant risk. However, good software is developed through use, especially for highly complex industrial software like CAD. It requires extensive and multi-round application, iteration, and refinement in real-world product development projects to reach a fully mature and usable engineering application state. The CAD software replacement process must avoid impacting product development quality and schedule; this is the current practical need and challenge facing CAD software replacement.

[0005] To address the above issues, this invention proposes a heterogeneous peer-to-peer multi-CAD model hybrid control application method oriented towards product BOM. This method can achieve a hybrid control application of heterogeneous peer-to-peer multi-CAD models that is closely integrated with the product BOM and strictly consistent with the product's technical status, solving the problem of efficient and high-quality application of heterogeneous multi-CAD models in the collaborative R&D of heterogeneous CAD models. Furthermore, by using the peer-to-peer CAD model hybrid application method, it can realize the hybrid application of multiple heterogeneous CAD models, achieving the gradual replacement of CAD and thus promoting the better development of CAD replacement work. Summary of the Invention

[0006] The technical problem solved by this invention is to propose a heterogeneous peer-to-peer multi-CAD model control application method oriented towards product BOM, which solves the problems of efficient and high-quality mixed application of heterogeneous multi-CAD models and efficient CAD replacement in the process of product heterogeneous CAD collaborative R&D; this method can support R&D personnel to achieve mixed control application of heterogeneous multi-CAD models that are closely integrated with the product BOM and strictly consistent with the product's technical status during the product development process, thus solving the problem of efficient and high-quality application of heterogeneous multi-CAD models in product collaborative R&D. At the same time, this method can also help to better carry out CAD software replacement work.

[0007] Technical solution of the present invention:

[0008] A method for controlling heterogeneous peer-to-peer multi-CAD model applications oriented towards product BOM, the method comprising the following steps:

[0009] Step 1: Set the allowed heterogeneous pairs of CAD model values ​​in the product BOM, represented by set P, and then proceed to Step 2.

[0010] Step 2: Set the "Main Model Identifier" attribute of one or more module component nodes specified in the product BOM to any value in P, and then proceed to Step 3.

[0011] Step 3: Determine whether the product component node under the module component already has a CAD model in the format corresponding to the "main model identifier" attribute value of the module component. If yes, proceed to step 4.

[0012] Step 4: Determine whether the product component node under the module component already has a CAD model in a format other than the "main model identifier" attribute value of the module component in P. If yes, proceed to step 5.

[0013] Step 5: Determine the type of subsequent operation: If it is adding a module component, proceed to step 6; if it is changing the "Main Model Identifier" attribute value of the module component node from the original value to a value other than the original value in P, proceed to step 3; if it is opening the component node under the module component and associating it with the CAD model, proceed to step 7; if it is adding or changing the CAD model and checking it into the product BOM data, proceed to step 9.

[0014] Step 6: Set the "Main Model Identifier" attribute value of the added module component node to any value in P, and then go to step 3.

[0015] Step 7: Compare the "Main Model Identifier" attribute value of this module component with the type of CAD tool to be applied. If they match, proceed to Step 8.

[0016] Step 8: Based on the type of CAD tool to be applied, obtain the CAD model data associated with the component nodes under the module component that matches the format, and load and open the model into the CAD tool. This concludes the method.

[0017] Step 9: Determine whether the "Main Model Identifier" attribute value of the module to which the newly added or modified component belongs is consistent with the format of the currently opened CAD tool. If yes, proceed to Step 10.

[0018] Step 10: Allow check-in. Immediately after check-in, initiate the conversion of the "Master Model Identifier" to other heterogeneous CAD models. This concludes the method.

[0019] Furthermore, in the method described above, the product BOM consists of top-level components, modular components, bottom-level components, part nodes, and their node relationships. Top-level component nodes are component nodes above modular component nodes, representing the top-level composition of the product and may include several levels. Modular component nodes are the basic units for product configuration and modular design, used to organize different design instances, and are single-layer structures. Bottom-level component nodes are component nodes below modular component nodes, representing the composition of specific design instances and may include several levels. Part nodes are leaf nodes below bottom-level component nodes, representing specific product parts. Top-level component and modular component BOM nodes are not associated with CAD model data; they only describe product composition relationships and are virtual nodes. Bottom-level component and part nodes are nodes associated with the CAD model, reflecting the actual design content.

[0020] Furthermore, the method uses heterogeneous peer-to-peer CAD models, where the peer-to-peer CAD models are generated by converting the original CAD models. The original CAD models and peer-to-peer CAD models have the same model encoding, name, version, and content, with the only difference being the CAD format suffix in the physical file name of the model.

[0021] Furthermore, in step 3, it is determined whether the product component node under the module component already has a CAD model in the format corresponding to the "main model identifier" attribute value of the module component. If not, proceed to step 11: determine whether the product component node under the module component already has a CAD model in P in a format other than the "main model identifier" attribute value of the module component. If yes, proceed to "step 12: complete the equivalent conversion of any other format model in P to the corresponding main model format model, and then proceed to step 5"; otherwise, the method ends.

[0022] Furthermore, in step 12, the equivalent conversion of any other format digital model in P to the corresponding main model format digital model is completed. This equivalent conversion refers to the process of converting the original CAD format model into the target format model data using a model conversion tool. The two models must maintain consistency in model encoding, name, version, and content; only the CAD format suffix in the physical model file name differs.

[0023] Furthermore, in step 4, it is determined whether the product component node under the module component already has a CAD model in P other than the "main model identifier" attribute value of the module component. If not, proceed to step 13: complete the equivalent conversion of the main model format model to other format models in P, and then proceed to step 5.

[0024] Furthermore, in step 7, the "main model identifier" attribute value of the module component is compared with the type of CAD tool to be applied. If they are inconsistent, proceed to step 14: check whether the equivalent models associated with the component nodes under the module component have been successfully converted. If yes, proceed to step 8; otherwise, proceed to step 15: do not allow the digital model to be opened to the CAD tool to be applied. The method ends here.

[0025] Furthermore, in step 9, it is determined whether the "main model identifier" attribute value of the module to which the newly added or modified component belongs is consistent with the format of the currently opened CAD tool. If not, proceed to step 16: check-in is not allowed, and the method ends here.

[0026] The technical advantages of this invention are as follows: It defines for the first time a method for hybrid control of heterogeneous, peer-to-peer CAD models oriented towards a product BOM. This method enables R&D personnel to achieve hybrid control of heterogeneous multiple CAD models that are closely integrated with the product BOM and strictly consistent with the product's technical status during product development. It solves the problem of efficient and high-quality application of heterogeneous multiple CAD models in collaborative product development. Furthermore, this method can also facilitate better implementation of CAD software replacement work. It has significant practical value and high innovation. Attached Figure Description

[0027] Figure 1 This is a flowchart of the invention;

[0028] Figure 2 These are examples of product BOMs. Detailed Implementation

[0029] The invention will now be described in further detail with reference to examples and specific implementation methods.

[0030] One embodiment of the present invention is as follows:

[0031] A method for controlling heterogeneous peer-to-peer multi-CAD model applications oriented towards product BOM, the method comprising the following steps:

[0032] Step 1: Set the allowed heterogeneous pairs of CAD model values ​​in the product BOM, represented by set P, and then proceed to Step 2.

[0033] Step 2: Set the "Main Model Identifier" attribute of one or more module component nodes specified in the product BOM to any value in P, and then proceed to Step 3.

[0034] Step 3: Determine if the product component node under the module component already has a CAD model in the format corresponding to the "Main Model Identifier" attribute value of that module component. If yes, proceed to Step 4; otherwise, proceed to Step 11: Determine if the product component node under the module component already has a CAD model in a format other than the "Main Model Identifier" attribute value of that module component in P. If yes, proceed to "Step 12: Complete the equivalent conversion of any other format model in P to the corresponding main model format model, and then proceed to Step 5"; otherwise, the method ends. In Step 12, the equivalent conversion refers to the process of converting the original CAD format model into the target format model data using a model conversion tool. The two must maintain consistency in model encoding, name, version, and content; only the CAD format suffix in the physical model file name differs.

[0035] Step 4: Determine whether the product component node under the module component already has a CAD model in P other than the "main model identifier" attribute value of the module component. If yes, proceed to step 5; otherwise, proceed to step 13: complete the equivalent conversion from the main model format model to other format models in P, and then proceed to step 5.

[0036] Step 5: Determine the type of subsequent operation: If it is adding a module component, proceed to step 6; if it is changing the "Main Model Identifier" attribute value of the module component node from the original value to a value other than the original value in P, proceed to step 3; if it is opening the component node under the module component and associating it with the CAD model, proceed to step 7; if it is adding or changing the CAD model and checking it into the product BOM data, proceed to step 9.

[0037] Step 6: Set the "Main Model Identifier" attribute value of the added module component node to any value in P, and then go to step 3.

[0038] Step 7: Compare the "Main Model Identifier" attribute value of this module component with the type of CAD tool to be applied. If they match, proceed to Step 8. If they do not match, proceed to Step 14: Check whether the equivalent models associated with the component nodes under this module component have been successfully converted. If yes, proceed to Step 8. If no, proceed to Step 15: Do not allow the digital model to be opened to the CAD tool to be applied. This concludes the method.

[0039] Step 8: Based on the type of CAD tool to be applied, obtain the CAD model data associated with the component nodes under the module component that matches the format, and load and open the model into the CAD tool. This concludes the method.

[0040] Step 9: Determine whether the "Main Model Identifier" attribute value of the module to which the newly added or modified component belongs is consistent with the format of the currently opened CAD tool. If yes, proceed to step 10; otherwise, proceed to step 16: Check-in is not allowed. This concludes the method.

[0041] Step 10: Allow check-in. Immediately after check-in, initiate the conversion of the "Master Model Identifier" to other heterogeneous CAD models. This concludes the method.

[0042] In this invention, the product BOM consists of top-level components, modular components, bottom-level components, part nodes, and their node relationships. Top-level component nodes are those above the modular component nodes, representing the top-level composition of the product and may include several levels. Modular component nodes are the basic units for product configuration and modular design, used to organize different design instances, and are single-layer structures. Bottom-level component nodes are those below the modular component nodes, representing the composition of specific design instances and may include several levels. Part nodes are leaf nodes below the bottom-level component nodes, representing specific product parts. Top-level component and modular component BOM nodes are not associated with CAD model data; they only describe product composition relationships and are virtual nodes. Bottom-level component and part nodes are associated with the CAD model, reflecting the actual design content.

[0043] In this invention, the equivalent CAD model is generated by converting the original CAD model. The original CAD model and the equivalent CAD model have the same model code, name, version, and content, and only the CAD format suffix in the physical file name of the model is different.

[0044] The second embodiment of the present invention: Figure 1 This is a flowchart of a heterogeneous peer-to-peer multi-CAD model hybrid control application method for product BOM according to an embodiment of the present invention. The method includes the following steps:

[0045] Step 1: Set the allowed heterogeneous pairs of CAD model values ​​in the product BOM, represented by set P, and then proceed to Step 2. Figure 2 This is an example of a product BOM used to illustrate the method of the present invention. In this example, it is assumed that the set P = {CATIA; UG; ZWCAD}, where CATIA, UG, and ZWCAD are three commonly used CAD tools.

[0046] Step 2: Set the "Master Model Identifier" attribute value of one or more module component nodes specified in the product BOM to any value in P, and then proceed to Step 3. In this example, it is assumed that the "Master Model Identifier" attribute values ​​of module component M1 and module component M2 are CATIA and ZWCAD, respectively.

[0047] Step 3: Determine if the product component nodes under the module already have a CAD model in the format corresponding to the "Master Model Identifier" attribute value of that module. If yes, proceed to Step 4. In this example, it is assumed that a CATIA format model already exists under module M1, so proceed to Step 4. If there is no ZWCAD format model under module M2, proceed to Step 11: Determine if the product component nodes under M2 already have a CAD model in a format other than ZWCAD. In this example, it is assumed that a CATIA format model exists, so proceed to Step 12: Complete the equivalent conversion from CATIA format model to ZWCAD format model, and then proceed to Step 5.

[0048] Step 4: Determine if the product component node under the module component already has a CAD model in a format other than the "Main Model Identifier" attribute value of the module component in P. If yes, proceed to Step 5. In this example, it is assumed that the product component node under M1 already has a ZWCAD format model, so proceed to Step 5.

[0049] Step 5: Determine the type of subsequent operation: If it is adding a module component, proceed to step 6; if it is changing the "Main Model Identifier" attribute value of the module component node from the original value to a value other than the original value in P, proceed to step 3; if it is opening the component node under the module component and associating it with the CAD model, proceed to step 7; if it is adding or changing the CAD model and checking it into the product BOM data, proceed to step 9.

[0050] In this example, assuming that for module component M1, the subsequent operation is to change the "Master Model Identifier" attribute value from CATIA to ZWCAD, then we return to step 3: determine whether the product component node under the module component already has a CAD model in the format corresponding to the "Master Model Identifier" attribute value of the module component. If yes, proceed to step 4. In this example, M1 already has a ZWCAD format model, so we directly proceed to step 4: determine whether the product component node under the module component already has a CAD model in a format other than the "Master Model Identifier" attribute value of the module component in P. If yes, proceed to step 5. In this example, M1 already has a CATIA format model, which meets the condition, so we continue to step 5.

[0051] In this example, assuming that for module component M2, the subsequent operation is to open the CAD model associated with the component nodes under this module component using CATIA, then proceed to step 7: compare the "Master Model Identifier" attribute value of this module component with the type of CAD tool to be applied. If they match, proceed to step 8. In this example, the "Master Model Identifier" attribute value of module component M2 is ZWCAD, which is inconsistent with the CAD tool to be applied, CATIA. Therefore, proceed to step 14: check whether the equivalent models associated with the component nodes under this module component have been successfully converted. If yes, proceed to step 8; otherwise, proceed to step 15: do not allow the CAD model to be opened to the CAD tool to be applied. This concludes the method. In this example, it is assumed that the CATIA equivalent model under module component M2 has been successfully converted, so proceed to step 8.

[0052] Step 8: Based on the type of CAD tool to be applied, obtain the CAD model data associated with the component nodes under the module part that matches the format, and load and open the model into that CAD tool. This concludes the method. In this example, CATIA is used to open the equivalent model in CATIA format under module part M2.

[0053] The above description is merely a specific embodiment of the present invention, providing a detailed description of the invention. Parts not covered herein are conventional techniques. However, the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. The scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for controlling heterogeneous peer-to-peer multi-CAD model applications oriented towards product BOM, characterized in that, The method includes the following steps: Step 1: Set the allowed heterogeneous pairs of CAD models in the product BOM, represented by set P, and then proceed to step 2; Step 2: Set the "Main Model Identifier" attribute of one or more module component nodes specified in the product BOM to any value in P, and then proceed to Step 3; Step 3: Determine whether the product component node under the module component already has a CAD model in the format corresponding to the "main model identifier" attribute value of the module component. If yes, proceed to step 4. Step 4: Determine whether the product component nodes under the module component already have CAD models in other formats than the "main model identifier" attribute value of the module component in P. If yes, proceed to step 5. Step 5: Determine the type of subsequent operation: If it is adding a module component, proceed to step 6; if it is changing the "Main Model Identifier" attribute value of the module component node from the original value to a value other than the original value in P, proceed to step 3; if it is opening the component node under the module component and associating it with the CAD model, proceed to step 7; if it is adding or changing the CAD model and checking it into the product BOM data, proceed to step 9. Step 6: Set the "Main Model Identifier" attribute value of the added module component node to any value in P, and then go to step 3; Step 7: Compare the "Main Model Identifier" attribute value of this module component with the type of CAD tool to be applied. If they match, proceed to Step 8. Step 8: Based on the type of CAD tool to be applied, obtain the CAD model data associated with the component nodes under the module component with the same format, and load and open the model into the CAD tool; this concludes the method. Step 9: Determine whether the "Main Model Identifier" attribute value of the module to which the newly added or modified component belongs is consistent with the format of the currently opened CAD tool. If yes, proceed to step 10. Step 10: Allow check-in. After check-in, immediately initiate the conversion of the "Master Model Identifier" to other heterogeneous CAD models. This concludes the method.

2. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM as described in claim 1, characterized in that, In step 1, the product BOM consists of top-level components, module components, bottom-level components, part nodes, and their node relationships; The product top-level component nodes are component nodes above the product module component nodes, representing the top-level composition relationship of the product, including several levels; module component nodes are the basic units of product configuration and modular design, used to organize different design instances, and are a single-layer structure; bottom-level component nodes are component nodes below the module component nodes, representing the composition relationship of specific design instances, including several levels; part nodes are leaf nodes below the bottom-level component nodes, representing specific product parts; the top-level components and module components are not associated with CAD model data, only describe the product composition relationship, and are virtual nodes; the bottom-level components and part nodes are nodes associated with the CAD model, reflecting the actual design content.

3. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM as described in claim 1, characterized in that, In step 1, the equivalent CAD model is generated by converting the original CAD model. The original CAD model and the equivalent CAD model have the same model code, name, version, and content, and only the CAD format suffix in the physical file name of the model is different.

4. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM as described in claim 1, characterized in that, In step 3, it is determined whether the product component node under the module component already has a CAD model in the format corresponding to the "main model identifier" attribute value of the module component. If not, proceed to step 11: determine whether the product component node under the module component already has a CAD model in P in a format other than the "main model identifier" attribute value of the module component. If yes, proceed to "step 12: complete the equivalent conversion of any other format model in P to the corresponding main model format model, and then proceed to step 5"; otherwise, the method ends.

5. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM according to claim 4, characterized in that, In step 12, the equivalent conversion of any other format digital model in P to the corresponding main model format digital model is completed; The equivalent conversion refers to the process of converting the original CAD format model into the target format model data using a model conversion tool. The two must maintain consistency in model encoding, name, version, and content, with only the CAD format suffix in the physical file name of the model being different.

6. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM according to claim 1, characterized in that, In step 4, it is determined whether the product component node under the module component already has a CAD model in P other than the "main model identifier" attribute value of the module component. If not, proceed to step 13: complete the equivalent conversion of the main model format model to other format models in P, and then proceed to step 5.

7. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM according to claim 1, characterized in that, In step 7, the "main model identifier" attribute value of the module component is compared with the type of CAD tool to be applied. If they are inconsistent, proceed to step 14: check whether the equivalent models associated with the component nodes under the module component have been successfully converted. If yes, proceed to step 8; otherwise, proceed to step 15: do not allow the digital model to be opened to the CAD tool to be applied. The method ends here.

8. The heterogeneous peer-to-peer multi-CAD model control application method for product BOM according to claim 1, characterized in that, In step 9, it is determined whether the "main model identifier" attribute value of the module to which the newly added or modified component belongs is consistent with the format of the currently opened CAD tool. If not, proceed to step 16: check-in is not allowed, and the method ends here.

Images