Model design change influence range identification method, device and medium

Abstract

The invention discloses a model design change influence range identification method and device and a medium, model design is decomposed into a plurality of layers, each layer represents different components or modules, a tree structure is adopted to represent the relationship between the layers, each node in the tree structure represents one component or module, and the nodes in the tree structure are used for representing the different components or modules. The edges represent the dependency relationship between the components or the modules, and a multi-level design structure model is established; comparing the model design data before and after the change, and detecting the changed component or module; mapping the detected change object to the same level of the structure tree; and based on the multi-level design structure model, all objects influenced by changes are identified by adopting a self-adaptive algorithm. By establishing the multi-level design structure model, design changes can be efficiently detected and responded, and design consistency and integrity are ensured.

Description

Technical Field

[0001] The present invention belongs to the field of model data technology, and in particular relates to a method, device and medium for identifying the impact range of model design changes. Background Art

[0002] In product design, especially in complex system design (such as automobiles, aircraft, and large-scale machinery), design changes are a common and necessary process. These changes may stem from various factors, including design optimization, functional enhancement, cost control, and regulatory compliance. 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 often rely on manual processes and simple tools. These methods 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. There are three main methods for identifying the impact of design changes: (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 design structure and the dependencies between components. (3) Dependency analysis: By analyzing the dependencies between components in the design model, it helps staff understand the scope of the impact of changes. However, this type of tool is mainly used in the field of program design, 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 the present invention is to provide a method for identifying the impact scope of a model design change, so as to solve the problem that the impact scope of a design model change cannot be accurately identified.

[0005] The present invention is achieved through the following technical solutions: The method for identifying the impact scope of model design changes includes the following steps: S01. Decompose the model design into multiple levels, each level representing a different component or module. Use a tree structure to represent the relationship between the levels. Each node in the tree structure represents a component or module, and the edges represent the dependency relationship between components or modules, thus establishing a multi-level design structure model. S02. Compare the model design data before and after the change, and detect the changed object, wherein the changed object includes the changed component or module; S03. Mapping the detected changed objects to the same level of the structure tree; S04. Adopt an adaptive algorithm based on the multi-level design structure model to identify all components or modules affected by the change.

[0006] 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; When a component or module is deleted or modified from the model design, the multi-level design structure model can automatically update the dependency relationship between the deleted or modified object and other components or modules.

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

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

[0009] In some embodiments of the present invention, the multi-level design structure model is traversed to find the lowest common ancestor node of the modified object, and the modified object is merged into the node level.

[0010] In some embodiments of the present invention, step S04 includes: Add the changed object to the impact scope set, traverse the components or modules it directly depends on in the structure tree, and add the components or modules it directly depends on to the impact scope set. Then traverse the components or modules that the newly added component or module in the impact scope set directly depends on in the structure tree, and repeat the process until no new dependent components or modules are found. Get the impact of a model design change based on the dependencies between all components or modules in the impact collection.

[0011] In some embodiments of the present invention, the step of obtaining the impact scope of the model design change includes: Starting from the bottom nodes of the multi-level design structure model, traversing, 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; The records in all impact range mapping tables are aggregated into the total mapping table to obtain the impact range of the model design change.

[0012] In some embodiments of the present invention, when traversing the bottom-level nodes, the influence ranges of different bottom-level nodes are compared, overlapping portions of the influence ranges are found, the influence degrees between the influence ranges are compared, the record with the highest influence degree is retained, and the records of the overlapping portions of the influence ranges corresponding to other bottom-level nodes are deleted; The impact range is the number and impact degree of components or modules affected when the underlying node is changed, and the impact degree is the hierarchical interval of the affected components or modules.

[0013] In another aspect, the present invention further provides an electronic device, comprising: processor; and, a memory for storing executable instructions of the processor; The processor is configured to execute the method for identifying the impact range of model design changes by executing the executable instructions.

[0014] On the other hand, the present invention further provides a computer-readable storage medium having a computer program stored thereon, which implements the method for identifying the impact range of model design changes when the computer program is executed by a processor.

[0015] Compared with the prior art, the present invention has the following advantages and beneficial effects: 1) By establishing a multi-level design structure model, the present invention can efficiently detect and respond to design changes, ensuring the consistency and integrity of the design.

[0016] 2) The method of the present 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 errors, and enhances the flexibility of team collaboration and project management, especially in complex and dynamic design environments.

[0017] 3) The present invention effectively handles complex design dependencies by mapping change objects to a unified hierarchy and adopting an adaptive impact analysis algorithm, significantly improving the efficiency and accuracy of design change management. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings in the embodiments will be briefly introduced below. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 A flowchart of a method for identifying the impact scope of model design changes according to an embodiment of the present invention.

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

[0021] In order to make the purpose, technical solutions and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. It should also be noted that, for ease of description, only parts related to the present application, not all of the contents, are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0022] The present invention is based on an adaptive multi-level analysis method and uses sub-component change information to automatically identify and locate the components affected by it. It can not only quickly determine the scope of the change, but also ensure that all related components can be updated in a timely manner to avoid omissions or errors, and realize automatic and accurate identification and tracking of the scope of influence of design changes in multi-level design structures.

[0023] The method of the present invention is well applicable to complex design projects, can significantly improve the efficiency and accuracy of process design changes, and reduce human errors in design change identification.

[0024] In some embodiments of the present invention, the model design change range identification method refers to Figure 1 , including the following steps: S01. Establish a multi-level design structure model Decompose the model design into multiple levels, each level representing a different component or module. Use a tree structure to represent these hierarchical relationships, with each node representing a component or module and edges representing the dependencies between components or modules.

[0025] Each level of the multi-level design structure model here includes not only the mapping relationship between components, but also the installation form and functional dependency information of each component. Usually, this information is expressed through a three-dimensional model.

[0026] When the model design changes, the multi-level design structure model can automatically update the corresponding hierarchy. When a new component or module is added, the multi-level design structure model can automatically add it to the corresponding level of 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 subsequently analyze the impact of the model design change.

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

[0028] When a model design is modified, a change order is received. This change order includes the modified object. Multiple instances of the modified object are searched throughout the multi-level design structure model, and the modified data content replaces the original corresponding data content. For example, if the modified object is component P, after the data of component P is modified, the sub-component information under component P is expressed according to the modified version, and the corresponding hierarchical structure is updated. When a component is deleted, instances of the modified object are also searched in the model for deletion.

[0029] The dependency relationship here refers to the hierarchical structure of the multi-level design structure model. The design of the hierarchical structure is constructed by considering scenarios such as the physical connection and functional dependency between parts; the changed object is associated with the data model of the original product through the dependency relationship.

[0030] S02. Changes in detection model design When a model design is changed, the changed object is automatically detected, including the changed component or module, by comparing the model design data before and after the change or other monitoring means.

[0031] For example, using differencing algorithms, different versions of a design model can be compared to identify differences, which may include added, deleted, or modified components.

[0032] Optimize the differential algorithm to reduce the time and space complexity of comparison, such as using an incremental differential algorithm to only compare the changed parts instead of the entire design model.

[0033] S03. Unified changes to object levels Map the detected changed objects to the same level. Use a standardized approach to ensure that all changed objects are on the same level.

[0034] For example, all changed objects are mapped to the leaf node hierarchy.

[0035] A hierarchical merging method is used to handle changes across multiple levels, merging the changed objects across multiple levels into a unified level; and merging the changed objects across multiple levels into their lowest common ancestor node level.

[0036] By traversing multiple hierarchical design structure models, the lowest common ancestor node of the changed object is found, and the changed object is merged into the node level.

[0037] Typically, design changes result in multiple change orders, and the intent of the design change cannot be understood 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 comprehensive analysis and understanding of the impact of the change. Merging, in this context, refers to the process of integrating the data of the change object into the hierarchical tree, allowing the change object and hierarchical data to be associated via drawing numbers.

[0038] S04. Identify the impact of design changes Based on a multi-level design structure model, an adaptive algorithm is used to identify all components affected by the change, including: First, the changed component is added to the affected set. Then, its directly dependent components are traversed, and the components directly dependent on them are added to the affected set. Then, the components directly dependent on these newly added components are traversed, and so on, until no more components are added. The adaptive algorithm can adaptively adjust the depth and breadth of the traversal based on the size and complexity of the design change.

[0039] In this step, the smallest common parent node of all changed objects is found.

[0040] During process design, we focus on changes to components and parts. However, design changes generally only describe changes to parts, lacking the expression of related components. The purpose of traversing component objects here is to obtain the changed components.

[0041] Next, identify the scope of the change's 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 scope of the change's impact.

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

[0043] The present invention processes complex design dependencies, uses an impact analysis algorithm, considers the dependencies between components, and determines the impact range of design changes.

[0044] By establishing a multi-level design structure model, this method can efficiently detect and respond to design changes, ensuring design consistency and integrity. This method not only automatically updates the design hierarchy to reflect new or modified components, but also quickly and accurately identifies design changes through an optimized differencing algorithm. It also utilizes graph traversal and impact analysis algorithms to precisely 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, particularly in complex and dynamic design environments.

[0045] The present invention effectively handles complex design dependencies by mapping change objects to a unified hierarchy and adopting an adaptive impact analysis algorithm, thereby significantly improving the efficiency and accuracy of design change management.

[0046] The method for identifying the impact range of model design changes of the present invention is described in detail below with reference to specific embodiments.

[0047] Aiming at the design hierarchy maintenance and change analysis of complex products, the present 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.

[0048] Specifically, the method includes the following steps: Step S01: Establish a multi-level design structure model 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 and skeleton assembly assemblies. To clearly express these hierarchical relationships, a tree structure is used to represent them, where each node represents a component or part, and edges represent the dependencies between them.

[0049] For example, refer to Figure 2 An assembly model can be broken down into multiple levels, including workstation assemblies, small assemblies, standard parts assemblies, and parts. An assembly that combines multiple parts to form a larger assembly is called a workstation assembly. Parts are further combined into smaller assembly units, called small assemblies. Standardized parts are combined into standard parts assemblies. Parts are the lowest level of a multi-level design structure model and contain the basic components that make up the assembly model.

[0050] When the assembly design changes, the product data can automatically update 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.

[0051] Step S02: Detect changes in model design When the assembly model design is changed, the changed components are automatically detected in the structure tree by comparing the multi-level design structure models before and after the change.

[0052] Use an incremental differencing algorithm to compare different versions of a multi-level design structure model and identify differences. These differences may include added, deleted, or modified components. Use daily checkpoints for version changes to implement version control for multi-level design structure model changes.

[0053] First, the version before 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: Newly added nodes: appear in the new version but not in the old version; Delete node: appears in the old version, but disappears in the new version; Modified node: exists in both versions, but the modification time is changed; Step S03: Unify the object level and map the detected changed objects to the corresponding level. A standardized approach ensures that all change objects are at the same level, mapping them to the leaf node level to handle changes across multiple levels. For example, a design's EBOM might have levels 1, 2, and 3. Some change objects might be at level 3, while others might be at level 2. An algorithm is then used to unify all change representations to level 1. The standardized approach here means expressing the change levels according to a standard.

[0054] A hierarchical merging method is used to merge the modified objects across multiple levels into a unified level. Specifically, the modified objects across multiple levels are merged into their lowest common ancestor node level.

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

[0056] like Figure 2 When both Part B and Station Assembly 3 are modified, the modified objects are consolidated into Station Assembly 1. Once the lowest common ancestor node is found, modified objects across multiple levels can be merged into that node. This node reflects the scope of the change.

[0057] Step S04: Identify the scope of impact of the change First, start traversing the multi-level design structure model from the bottom level nodes. The bottom level nodes usually represent the most basic parts of the design. For each bottom level node, do the following: Query the assembly relationships between the part and surrounding components to determine the impact of the change. This includes examining the physical connections and functional dependencies between the part and other parts. Record the specific details of each assembly relationship, such as connection method and dependency type, for subsequent analysis.

[0058] Then, record the impact range of each underlying node in detail and create an impact range mapping table to associate each underlying node with its impact range. The impact range of each underlying node refers to which components will be affected and the degree of impact when the underlying node changes; the degree of impact refers to the hierarchical interval, such as 2 levels or 3 levels. The acquisition of the impact range data of the underlying node is based on the hierarchical path of the hierarchical data. When there are multiple instances of the underlying node, the data of the affected objects needs to be merged. The specific steps are as follows: Create an entry for each underlying node and record its basic information (such as node ID, part name, etc.). List all affected components of the node and their impact in detail in the entry to ensure that the impact of each part change can be accurately tracked and recorded for subsequent integration and analysis.

[0059] After traversing all underlying nodes, you may find that the influence ranges of some nodes overlap. To ensure that each affected component is only calculated once, these overlapping parts need to be deduplicated. The specific steps are as follows: Compare the influence ranges of different underlying nodes and identify any overlaps. For any overlaps, select the records with the highest impact and retain them. Delete any records where the influence ranges of other underlying nodes overlap. Use appropriate algorithms (such as set operations) to automatically remove duplicates, ensuring efficiency and accuracy.

[0060] Finally, the impact ranges of all underlying nodes are integrated to form the final impact range of the change. The specific steps are as follows: The records in all impact scope mapping tables are aggregated into a total mapping table to obtain the impact scope of the model design change.

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

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

[0063] By identifying the impact scope of the underlying nodes, we can analyze which components are affected by the change and then obtain the relevant component objects of the change. The design change order will cover all the underlying nodes, and the changed nodes in other levels can be obtained through the underlying nodes.

[0064] In another aspect, the present invention further provides an electronic device, comprising: processor; and, a memory for storing executable instructions of the processor; The processor is configured to execute the method for identifying the impact range of model design changes by executing the executable instructions.

[0065] On the other hand, the present invention further provides a computer-readable storage medium having a computer program stored thereon, which implements the method for identifying the impact range of model design changes when the computer program is executed by a processor.

[0066] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any simple modification or equivalent change made to the above embodiment based on the technical essence of the present invention shall fall within the scope of protection of the present invention.

Claims

1. A method for identifying the impact range of model design changes, characterized in that: The following steps are involved: S01. Decompose the model design into multiple levels, each level representing a different component or module. Use a tree structure to represent the relationship between the levels. Each node in the tree structure represents a component or module, and the edges represent the dependency relationship between components or modules, thus establishing a multi-level design structure model. S02. Compare the model design data before and after the change, and detect the changed object, wherein the changed object includes the changed component or module; S03. Mapping the detected changed objects to the same level of the structure tree; S04. Adopt an adaptive algorithm based on the multi-level design structure model to identify all components or modules affected by the change.

2. The method for identifying the impact range 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 deleted or modified from the model design, the multi-level design structure model can automatically update the dependency relationship between the deleted or modified object and other components or modules.

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

4. The method for identifying the impact range of model design changes according to claim 1, characterized in that: In step S03, a hierarchical merging method is adopted to merge the modified objects across multiple levels into the lowest common ancestor node level of these modified objects.

5. The method for identifying the impact range of model design changes according to claim 4, characterized in that: By traversing the multi-level design structure model, the lowest common ancestor node of the changed object is found, and the changed object is merged into the node level.

6. The method for identifying the impact range of model design changes according to claim 1, characterized in that: Step S04 includes: Add the changed object to the impact scope set, traverse the components or modules it directly depends on in the structure tree, and add the components or modules it directly depends on to the impact scope set. Then traverse the components or modules that the newly added component or module in the impact scope set directly depends on in the structure tree, and repeat the process until no new dependent components or modules are found. Get the impact of a model design change based on the dependencies between all components or modules in the impact collection.

7. The method for identifying the impact range of model design changes according to claim 6, characterized in that: The steps to obtain the scope of impact of a design change to a model include: Starting from the bottom nodes of the multi-level design structure model, traversing, 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; The records in all impact range mapping tables are aggregated into the total mapping table to obtain the impact range of the model design change.

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

9. An electronic device, characterized in that include: processor; as well as, a memory for storing executable instructions of the processor; The processor is configured to execute the model design change impact range identification method according to any one of claims 1 to 8 by executing the executable instructions.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for identifying the impact range of a model design change according to any one of claims 1 to 8 is implemented.

Images