Model design change impact scope identification method, device, and medium

Abstract

This invention discloses a method, device, and medium for identifying the impact range of model design changes. The model design is decomposed into multiple levels, each level representing different components or modules. A tree structure is used to represent the relationships between levels, where each node represents a component or module, and edges represent dependencies between components or modules, thus establishing a multi-level design structure model. The invention compares the model design data before and after the change to detect the changed components or modules. The detected changed objects are mapped to the same level in the tree structure. Based on the multi-level design structure model, an adaptive algorithm is used to identify all objects affected by the change. This invention, by establishing a multi-level design structure model, can efficiently detect and respond to design changes, ensuring the consistency and integrity of the design.

Description

Technical Field

[0001] This invention belongs to the field of model data technology, specifically relating to a method, device, and medium for identifying the impact range of model design changes. Background Technology

[0002] In product design, especially in the design of complex systems (such as automobiles, aircraft, and large machinery), design changes are a common and necessary process. These changes may stem from a variety of factors, including design optimization, functional enhancement, cost control, and compliance requirements. However, design changes often trigger a series of chain reactions, affecting multiple components and modules within the design.

[0003] Currently, the management and tracking of design changes usually rely on manual processes and simple tools, which are inefficient and prone to errors when dealing with large and complex designs. Although there are some automated tools that can help designers compare different versions of design models, these tools often lack a deep understanding of multi-level design structures and cannot accurately identify the scope of the impact of changes. The main means of identifying the impact of design changes include the following three types: (1) Manual comparison: Engineers manually compare different versions of 3D models to identify the changed parts. This method relies on personal experience and intuition, is inefficient, and is prone to missing changes or making mistakes. (2) Simple automated tools: Basic automated tools can help engineers compare different versions of 3D models, but these tools can usually only identify surface differences and lack a deep understanding of the dependencies between design structures and components. (3) Dependency analysis: By analyzing the dependencies between components in the design model, staff can understand the scope of the impact of changes. However, these tools are mainly used in the field of programming, and there is a lack of tools for design change dependency analysis in the field of process design. Summary of the Invention

[0004] The purpose of this invention is to provide a method for identifying the scope of influence of model design changes, so as to solve the problem of being unable to accurately identify the scope of influence of design model changes.

[0005] This invention is achieved through the following technical solution:

[0006] The method for identifying the scope of impact of model design changes includes the following steps:

[0007] S01. Decompose the model design into multiple levels, each level representing different components or modules. Use a tree structure to represent the relationship between levels. Each node in the tree structure represents a component or module, and the edges represent the dependencies between components or modules, thus establishing a multi-level design structure model.

[0008] S02. Compare the model design data before and after the change, and detect the changed objects, including the changed components or modules;

[0009] S03. Map the detected changed objects to the same level in the tree structure;

[0010] S04. Based on the multi-level design structure model, an adaptive algorithm is used to identify all components or modules affected by the changes.

[0011] In some embodiments of the present invention, in step S01, when a new component or module is added to the model design, the multi-level design structure model can automatically add the new component or module to the corresponding level of the tree structure.

[0012] When a component or module is removed or modified from the model design, the multi-level design structure model can automatically update the dependencies between the removed or modified object and other components or modules.

[0013] In some embodiments of the present invention, an incremental differential algorithm is used in step S02 to detect the changed components or modules.

[0014] In some embodiments of the present invention, step S03 employs a hierarchical merging method to merge modified objects spanning multiple levels into the lowest common ancestor node level of these modified objects.

[0015] In some embodiments of the present invention, the lowest common ancestor node of the modified object is found by traversing the multi-level design structure model, and the modified object is merged into the node level.

[0016] In some embodiments of the present invention, step S04 includes:

[0017] Add the changed object to the scope of influence set, traverse the components or modules that it directly depends on in the structure tree, and add the components or modules that it directly depends on to the scope of influence set. Then, traverse the components or modules that the newly added components or modules in the scope of influence set directly depend on in the structure tree, and repeat this process until no new dependent components or modules are found.

[0018] Based on the dependencies between all components or modules in the scope of influence set, obtain the scope of influence of the model design change.

[0019] In some embodiments of the present invention, the step of obtaining the scope of influence of the model design change includes:

[0020] Starting from the bottom nodes of the multi-level design structure model, the influence range of each bottom node is recorded, and an influence range mapping table is created to associate each bottom node with its influence range.

[0021] By summarizing the records in all the impact scope mapping tables into the master mapping table, the impact scope of the model design change can be obtained.

[0022] In some embodiments of the present invention, when traversing the bottom-level nodes, the influence range of different bottom-level nodes is compared, the overlapping parts of the influence range are found, the degree of influence between the influence ranges is compared, the record with the highest degree of influence is retained, and the records of the overlapping parts of the influence ranges of other bottom-level nodes are deleted.

[0023] The scope of influence refers to the number and degree of impact of components or modules affected when the underlying node is changed, and the degree of impact refers to the hierarchical interval of the affected components or modules.

[0024] On the other hand, the present invention also provides an electronic device, comprising:

[0025] Processor; and,

[0026] Memory for storing the executable instructions of the processor;

[0027] The processor is configured to execute the model design change impact range identification method by executing the executable instructions.

[0028] On the other hand, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for identifying the scope of influence of model design changes.

[0029] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0030] 1) By establishing a multi-level design structure model, this invention can efficiently detect and respond to design changes, ensuring the consistency and integrity of the design.

[0031] 2) The method of this invention automatically updates the design hierarchy to reflect newly added or modified components, uses an optimized differential algorithm to quickly and accurately identify design changes, and uses graph traversal and impact analysis algorithms to accurately assess the impact of changes on the overall design. This significantly improves the efficiency of design change management, reduces human error, and enhances the flexibility of team collaboration and project management, especially in the face of complex and dynamic design environments.

[0032] 3) This invention effectively handles complex design dependencies by mapping changed objects to a unified level and employing an adaptive impact analysis algorithm, significantly improving the efficiency and accuracy of design change management. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a flowchart illustrating the method for identifying the scope of influence of model design changes in an embodiment of the present invention.

[0035] Figure 2 This is a schematic diagram of the multi-level design structure model according to an embodiment of the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0037] This invention is based on an adaptive multi-level analysis method. By utilizing sub-component change information, it automatically identifies and locates the components affected by the changes. This not only quickly determines the scope of the changes but also ensures that all relevant components are updated in a timely manner, avoiding omissions or errors. It achieves automated and accurate identification and tracking of the scope of the impact of design changes in a multi-level design structure.

[0038] The method of this invention is well applied to complex design projects, and can significantly improve the efficiency and accuracy of process design changes, and reduce human error in design change identification.

[0039] In some embodiments of the present invention, the method for identifying the range of model design changes is described in reference to... Figure 1 This includes the following steps:

[0040] S01. Establish a multi-level design structure model

[0041] The model design is broken down into multiple levels, each representing a different component or module. A tree structure is used to represent these hierarchical relationships, where each node represents a component or module, and edges represent dependencies between components or modules.

[0042] The multi-level design structure model here includes not only the mapping relationship between components, but also information on the installation form and functional dependencies of each component. This information is usually expressed through a three-dimensional model.

[0043] When the model design changes, the multi-level design structure model can automatically update the corresponding hierarchical structure. When a new component or module is added, the multi-level design structure model can automatically add it to the corresponding level in the tree structure; when a component or module is deleted or modified, the multi-level design structure model can automatically update the related dependencies. The updated dependencies are used to analyze the impact of the model design changes in subsequent analyses.

[0044] Specifically, each component is instantiated and represented. For example, for component p, there may be a component p under component a and another component p under component b. The multi-level design structure model constructed at this time can be represented as: product-component a-component p, product-component b-component p.

[0045] When the model design changes, a change order is received. This change order includes the object being changed. Multiple instances of the changed object are retrieved throughout the multi-level design structure model, and the modified data content replaces the original corresponding data. For example, if the changed object is component P, after the data of component P is changed, the information of all sub-components under component P is expressed according to the modified version, and the corresponding hierarchical structure is updated. Similarly, when deleting a component, instances of the changed object are searched for and deleted from the model.

[0046] The dependency relationship here refers to the hierarchical structure of the multi-level design structure model. The hierarchical structure is designed with consideration of the physical connections and functional dependencies between parts. The dependency relationship links the object to be changed with the original product's data model.

[0047] S02, Changes to the design of the detection model

[0048] When the model design changes, the changed objects are automatically detected. The changed objects include modified components or modules, which is achieved by comparing the model design data before and after the change or by other monitoring methods.

[0049] For example, differential algorithms can be used to compare different versions of a design model and identify the differences. These differences may include added, deleted, or modified components.

[0050] Optimize the difference algorithm to reduce the time and space complexity of comparisons, such as by using an incremental difference algorithm that compares only the changed parts instead of the entire design model.

[0051] S03, Unify the change of object hierarchy

[0052] Map detected changed objects to the same level. Use a standardized approach to ensure all changed objects are at the same level.

[0053] For example, map all changed objects to a leaf node hierarchy.

[0054] A hierarchical merging method is used to handle changes that span multiple levels, merging change objects that span multiple levels into a unified level; or merging change objects that span multiple levels into their lowest common ancestor node level.

[0055] By traversing multiple levels of the design structure model, the lowest common ancestor node of the modified object is found, and the modified object is merged into that node level.

[0056] Typically, design changes result in multiple change orders, and the intent behind the change cannot be determined from a single change order. Therefore, this invention utilizes a hierarchical tree to merge (map) multiple change orders into a single data structure, allowing for a holistic analysis and understanding of the scope of the change's impact. Here, merging refers to the process of integrating the data of the changed objects into the hierarchical tree, thus linking the changed objects and hierarchical data through drawing numbers.

[0057] S04. Identify the scope of impact of design changes

[0058] Based on a multi-level design structure model, an adaptive algorithm is used to identify all components affected by the changes. These include:

[0059] First, add the modified component to the affected set. Then, iterate through its directly dependent components, adding those directly dependent components to the affected set. Next, iterate through the components directly dependent on these newly added components, and so on, until no more components are added. The adaptive algorithm can adjust the depth and breadth of the iteration based on the size and complexity of the design change.

[0060] In this step, find the smallest common parent node of all changed objects.

[0061] In process design, the focus is mainly on changes to components and parts. However, design changes typically only describe changes to parts, lacking descriptions of the related components. The purpose of iterating through component objects here is to retrieve the changed components.

[0062] Next, identify the scope of the changes' impact on the design. Use a graph traversal algorithm to find all components connected to the changed object. Consider the dependencies between components to determine the extent of the changes' impact.

[0063] Use depth-first search or breadth-first search algorithms to traverse the multi-level design structure model and identify the affected components.

[0064] This invention addresses complex design dependencies by employing an impact analysis algorithm that considers the dependencies between components to determine the scope of impact of design changes.

[0065] This invention establishes a multi-level design structure model, enabling efficient detection and response to design changes, ensuring design consistency and integrity. This method not only automatically updates the design hierarchy to reflect newly added or modified components, but also quickly and accurately identifies design changes through an optimized differential algorithm. Simultaneously, it utilizes graph traversal and impact analysis algorithms to precisely assess the scope of the changes' impact on the overall design. This significantly improves the efficiency of design change management, reduces human error, and enhances the flexibility of team collaboration and project management, particularly in complex and dynamic design environments.

[0066] This invention effectively handles complex design dependencies by mapping changed objects to a unified hierarchy and employing an adaptive impact analysis algorithm, significantly improving the efficiency and accuracy of design change management.

[0067] The method for identifying the scope of influence of model design changes according to the present invention will be described in detail below with reference to specific embodiments.

[0068] For the maintenance and modification analysis of the design hierarchy of complex products, this invention proposes an adaptive multi-level design change and product list association construction method to improve the quality of product data management and reduce identification errors and costs.

[0069] Specifically, it includes the following steps:

[0070] Step S01: Establish a multi-level design structure model

[0071] In a multi-level design structure model, the assembly model is decomposed into multiple levels, each representing a different cluster of components, such as assembly assemblies, skeleton assembly assemblies, etc. To clearly express these hierarchical relationships, a tree structure is used, where each node represents a component or part, and edges represent the dependencies between them.

[0072] For example, refer to Figure 2An assembly model can be decomposed into multiple levels, including station assemblies, small assemblies, standard part assemblies, and parts. An assembly that combines multiple parts to form a larger assembly is called a station assembly. Further combining parts into smaller assembly units is called a small assembly. Combining standardized parts is called a standard part assembly. Parts are the lowest level of the multi-level design structure model, containing the basic components that make up the assembly model.

[0073] When the assembly design changes, the product data can be automatically updated to the corresponding hierarchical data. For example, when a new component is added to the assembly, the multi-level design structure model can automatically add it to the corresponding level; when a component is deleted or modified, the multi-level design structure model can automatically delete or modify the corresponding data.

[0074] Step S02: Detect changes in the model design

[0075] When the assembly model design changes, the modified components are automatically detected in the structure tree by comparing the multi-level design structure model before and after the change.

[0076] An incremental differential algorithm is used to compare different versions of the multi-level design structure model and identify differences. These differences may include added, deleted, or modified components. Version change checkpoints are used daily to implement version control for checking changes to the multi-level design structure model.

[0077] First, the version preceding the inspection time is selected as the baseline version; then, an incremental difference algorithm is used to compare only the differences between the new version and the baseline version; finally, a structural comparison method is used to analyze the differences between versions, including:

[0078] New node: Appears in the new version but not in the old version;

[0079] Delete node: It appeared in the old version but disappeared in the new version;

[0080] Modified node: Exists in both versions, but the modification time has changed;

[0081] Step S03: Unify the object hierarchy and map the detected modified objects to the corresponding hierarchy.

[0082] A standardized approach is used to ensure all changed objects reside at the same level, mapping all changed objects to leaf nodes to handle changes spanning multiple levels. For example, a design's EBOM might have levels 1, 2, and 3; some changed objects might be at level 3, while others might be at level 2. An algorithm unifies the representation of all changes to level 1. Here, standardization refers to expressing the hierarchical structure of changes according to a single standard.

[0083] A hierarchical merging method is used to combine modified objects that span multiple levels into a single, unified level. Specifically, modified objects that span multiple levels are merged down to the level of their lowest common ancestor node.

[0084] By traversing the design structure model, the lowest common ancestor node of the modified object is found, and the modified object is merged into that node level.

[0085] like Figure 2 When part B and station assembly 3 are modified simultaneously, the modified objects are unified onto station assembly 1. When the lowest common ancestor node is found, modified objects spanning multiple levels can be merged onto that node. This node reflects the scope of the change's impact.

[0086] Step S04: Identify the scope of the impact of the changes

[0087] First, traverse the multi-level design structure model starting from the bottom-level nodes. Bottom-level nodes typically represent the most basic components in the design. For each bottom-level node, perform the following operations:

[0088] Query the assembly relationships between this part and surrounding components to determine the scope of its impact. This includes examining the physical connections and functional dependencies between this part and other parts. Record the specific details of each assembly relationship, such as connection method and dependency type, for subsequent analysis.

[0089] Next, the impact range of each bottom-level node is recorded in detail, and an impact range mapping table is created to associate each bottom-level node with its impact range. The impact range of each bottom-level node refers to which components will be affected and the degree of impact when the bottom-level node changes; the degree of impact is the hierarchical interval, such as 2 or 3 levels. The impact range data of bottom-level nodes is obtained according to the hierarchical path of the hierarchical data. When multiple instances of a bottom-level node exist, the data of the affected objects needs to be merged. The specific steps are as follows:

[0090] Create an entry for each underlying node to record its basic information (such as node ID, part name, etc.). List in detail all affected components of that node and the extent of their impact within the entry, ensuring that the impact of changes to each part can be accurately tracked and recorded for subsequent integration and analysis.

[0091] After traversing all the underlying nodes, it may be found that the influence ranges of some nodes overlap. To ensure that each affected component is calculated only once, these overlapping parts need to be deduplicated. The specific steps are as follows:

[0092] Compare the influence ranges of different underlying nodes to identify overlapping areas. For overlapping areas, retain the record with the highest influence and delete records whose influence ranges overlap with those of other underlying nodes. Appropriate algorithms (such as set operations) can be used to automate deduplication, ensuring efficiency and accuracy.

[0093] Finally, the impact of all underlying nodes is consolidated to form the final scope of the change's impact. The specific steps are as follows:

[0094] By summarizing the records in all the impact scope mapping tables into a single master mapping table, the impact scope of the model design change can be obtained.

[0095] Perform logical validation on the summarized mapping table to ensure there are no omissions or errors.

[0096] Generate a detailed report listing all affected components and their extent of impact, providing a comprehensive and accurate reference for process design changes.

[0097] By identifying the scope of influence of the underlying nodes, we can analyze which components are affected by the changes and thus obtain the relevant component objects. The design change order will cover all underlying nodes, and by using the underlying nodes, we can obtain other levels of nodes that have been changed.

[0098] On the other hand, the present invention also provides an electronic device, comprising:

[0099] Processor; and,

[0100] Memory for storing the executable instructions of the processor;

[0101] The processor is configured to execute the model design change impact range identification method by executing the executable instructions.

[0102] On the other hand, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for identifying the scope of influence of model design changes.

[0103] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Any simple modifications or equivalent changes made to the above embodiments based on the technical essence of the present invention shall fall within the protection scope of the present invention.

Claims

1. A method for identifying the scope of impact of model design changes, characterized in that, Includes the following steps: S01. Decompose the model design into multiple levels, each level representing different components or modules. Use a tree structure to represent the relationship between levels. Each node in the tree structure represents a component or module, and the edges represent the dependencies between components or modules, thus establishing a multi-level design structure model. Each level of the multi-level design structure model includes the mapping relationship of components and information on the installation form and functional dependencies of each component. Parts are the lowest level of a multi-level design structure model, and parts are combined to form components; S02. Compare the model design data before and after the change, and detect the changed objects, including the changed components or modules; S03. Map the detected changed objects to the same level in the tree structure; S04. Based on the multi-level design structure model, an adaptive algorithm is used to identify all components or modules affected by the changes; In step S03, a hierarchical merging method is used to merge modified objects that span multiple levels into the lowest common ancestor node level of these modified objects. Step S04 includes: adding the changed object to the scope of influence set, traversing its directly dependent components or modules in the structure tree, and adding its directly dependent components or modules to the scope of influence set, then traversing the components or modules directly dependent on the newly added components or modules in the scope of influence set in the structure tree, and so on until no new dependent components or modules are found; and obtaining the scope of influence of the model design change based on the dependency relationships between all components or modules in the scope of influence set.

2. The method for identifying the scope of influence of model design changes according to claim 1, characterized in that, In step S01, when a new component or module is added to the model design, the multi-level design structure model can automatically add the new component or module to the corresponding level of the tree structure. When a component or module is removed or modified from the model design, the multi-level design structure model can automatically update the dependencies between the removed or modified object and other components or modules.

3. The method for identifying the scope of influence of model design changes according to claim 1, characterized in that, In step S02, an incremental differential algorithm is used to detect the changed components or modules.

4. The method for identifying the scope of influence of model design changes according to claim 1, characterized in that, By traversing the multi-level design structure model, the lowest common ancestor node of the modified object is found, and the modified object is merged into the node level.

5. The method for identifying the scope of influence of model design changes according to claim 1, characterized in that, The steps to determine the scope of impact of model design changes include: Starting from the bottom nodes of the multi-level design structure model, the influence range of each bottom node is recorded, and an influence range mapping table is created to associate each bottom node with its influence range. By summarizing the records in all the impact scope mapping tables into the master mapping table, the impact scope of the model design change can be obtained.

6. The method for identifying the scope of influence of model design changes according to claim 5, characterized in that, When traversing the bottom-level nodes, compare the influence range of different bottom-level nodes, find the overlapping parts of the influence range, compare the degree of influence between the influence ranges, retain the record with the highest degree of influence, and delete the records of the overlapping parts of the influence ranges of other bottom-level nodes. The scope of influence refers to the number and degree of impact of components or modules affected when the underlying node is changed, and the degree of impact refers to the hierarchical interval of the affected components or modules.

7. An electronic device, characterized in that, include: processor; as well as, Memory for storing the executable instructions of the processor; The processor is configured to perform the model design change impact range identification method according to any one of claims 1-6 by executing the executable instructions.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for identifying the scope of influence of model design changes as described in any one of claims 1-6.

Images