A method for assisting in improving design change decisions in a product data management system

Abstract

The present application belongs to the technical field of data management system, and particularly relates to a method for assisting in improving design change decision in a product data management system. The method comprises the following steps: collecting data for change decision, analyzing the collected data, integrating the data according to a top-down analysis logic, and finally forming a decision tree; the decision tree is used for assisting in judgment when making a change decision, and the judgment process when making the change decision is traceable; and the decision tree is programmed to make it explicit.

Description

Technical Field

[0001] This invention belongs to the field of data management system technology, and in particular relates to a method for assisting in improving design change decision-making in a product data management system. Background Technology

[0002] Analysis and statistics of current domestic manufacturing data reveal that most companies use Product Data Management (PDM) systems to manage complex product data. Various materials, drawings, and documents for research and development projects are managed using PDM for technical status management. Research and development projects, in particular, often experience frequent changes, each potentially impacting upstream and downstream products. Ensuring the efficiency and quality of change impact analysis is crucial for change management. To guarantee the effectiveness and quality of changes, most organizations have their own change control logic. However, it's often unclear when to modify part numbers and when not to. Most decisions rely on the 3Fs (Fit, Form, Function), lacking comprehensive consideration of other factors. In practice, different personnel have different approaches, lacking unified operational standards. The same scenario can yield different analytical results from different personnel, leading to variations in product quality based on individual skill levels. Statistics show that 5% of changes require termination and re-initiation due to inadequate initial change analysis; 10% result in repeated approval cycles due to inconsistent change judgment rules.

[0003] Change decisions (version / number change) are a crucial part of the entire product lifecycle. How to make the company's best practices and tacit knowledge explicit and apply them to the company's operations is a challenge in information technology. Change decision trees provide a visual and flexible operating tool. During the change process, the initiator only needs to select "yes" or "no" according to the actual situation. The tool will automatically guide the process to the next stage until the final change conclusion is reached.

[0004] In response to the existing problems, most companies have adopted methods such as adding approval procedures and inviting experts, but these are all temporary solutions and do not address the root cause. None of these solutions can fundamentally solve the problem. They do not make tacit knowledge explicit, nor do they form unified rules. As a result, it is difficult to guarantee the quality of change decisions, the reliability of results, and the completeness of impact analysis. Summary of the Invention

[0005] The technical problem solved by this invention is as follows: This invention mainly uses a modified decision tree to carry and display tacit knowledge, unifies the decision analysis process, standardizes the content of decision analysis, and improves the quality of decision analysis, thereby improving the efficiency, quality, and standardization of the change process. The modified decision tree integrates current industry best practices and the current situation of the enterprise to form a graphical operation interface that supports change decisions. Operators only need to make decisions based on the decision points, and the system automatically moves to the next decision point based on the decision conclusion, and so on, until a decision conclusion is finally formed. It supports decision reset and decision process traceability.

[0006] The technical solution of the present invention:

[0007] A method for assisting in improving design change decision-making in a product data management system, the method comprising:

[0008] The collected data used for decision-making changes are organized and analyzed, and integrated according to a top-down analytical logic to form a decision tree. The decision tree is used to assist in the judgment when changing decisions, and the judgment process when changing decisions is traceable.

[0009] The decision tree is programmed to make it explicit.

[0010] Furthermore, the decision-making process for changing the decision can be shared.

[0011] Furthermore, the final decision tree is formed as follows:

[0012] Step 1. Do the products / components before and after the modification meet all the usage requirements of the product? If yes, proceed to Step 2.1; otherwise, proceed to Step 2.2. Meeting all the usage requirements of the product means that the products / components before and after the modification are completely interchangeable.

[0013] Step 2.1. Does the product have a relevant user manual or maintenance manual? If so, proceed to step 3.1; otherwise, proceed to step 4.1.

[0014] Step 2.2. Have all products / parts before the change achieved full interchangeability with the products / parts after the change through economical rework / repair or scrapping and replacement? If the condition is met, proceed to step 3.2; otherwise, proceed to decision conclusion 2.

[0015] Step 3.1. Will the change cause any changes to the published user manual or maintenance manual? If the condition is met, proceed to step 4.2; otherwise, proceed to step 4.1.

[0016] Step 3.2. Can all pre-modification products be traced and controlled through rework or scrapping processes? If the condition is met, proceed to step 2.1; otherwise, proceed to decision conclusion 2.

[0017] Step 4.1. From the level of the final delivered product, does this change need to be visible? If the condition is met, proceed to step 4.2; otherwise, reach decision conclusion 1.

[0018] Step 4.2. Can the visibility of the change be achieved without changing the part number of the final product? If the condition is met, decision conclusion 1 is obtained; otherwise, decision conclusion 2 is obtained. Decision conclusion 1 is to not change the part number, and decision conclusion 2 is to assign a new part number.

[0019] Furthermore, the decision tree is programmed to make it explicit, specifically as follows:

[0020] Based on the decision tree formed above, each decision point and the relationship between decision points are encoded and the encoding results are stored in the background database, thereby making the tacit knowledge explicit. The tacit knowledge is the relationship between each decision point and decision points in the decision tree.

[0021] Furthermore, regarding the decision tree mentioned above, designers invoke the decision tree before each design change and display it through a graphical interface. Each decision starts from the top of the decision tree, and the next step is guided by the description of the decision point content, ensuring the consistency of the standards and processes for forming each decision conclusion.

[0022] Furthermore, before submitting each design change, designers need to invoke the decision tree to form the final change decision roadmap from top to bottom based on the actual impact. Each final change decision roadmap is recorded. When the decision conclusions are different, the process can be traced. When the decision conclusions are consistent, the consistency of the process can be traced. This is because different decision conclusions will inevitably lead to different decision paths, and even the same decision conclusions will not necessarily lead to the same decision path.

[0023] Furthermore, during the design change process, the decision-making path and conclusions are provided to personnel at each stage to assist them in verifying the correctness of the change decision.

[0024] Furthermore, the decision tree is scalable and maintainable, and can be improved and updated during use.

[0025] The technical solutions of this invention include: 1) making the organization's tacit knowledge explicit; 2) fully utilizing industry best practices; 3) ensuring consistency in decision-making rules, preventing variations based on individual circumstances; 4) making the decision-making process traceable; 5) making the decision-making rules configurable and extensible; 6) conducting data analysis to continuously optimize and change the decision tree; and 7) improving the efficiency and quality of the change process. Attached Figure Description

[0026] Figure 1 A diagram illustrating the logical relationships extracted from data analysis rules.

[0027] Figure 2A schematic diagram illustrating the explicit interface for program coding decisions;

[0028] Figure 3 A diagram to aid in design change decision-making;

[0029] Figure 4 A diagram illustrating the decision-making process for modification. Detailed Implementation

[0030] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings.

[0031] The main problems with the existing solutions are: the process is not recorded through information technology; changes to decisions are not traceable; existing tacit knowledge cannot be extracted and shared; and offline or additional steps will increase the process cycle.

[0032] To address the shortcomings of the above solutions, this invention mainly solves them through the following points:

[0033] By summarizing the steps and judgment logic involved in change decision-making through data analysis (mainly organizing best practices), we can identify correlations, extract rules, establish program coding rules with the help of information technology, form a visual operation interface, and configure rules for the change decision-making process (adding / adjusting real-time rules can be expanded / changed).

[0034] When initiating a change, the built-in change decision rules and the actual situation need to be selected to form a change decision path for this time. The change decision process is then visualized to facilitate traceability in subsequent stages.

[0035] During the change review process, all personnel at each stage can see the change decision process path, and can also use the change decision tree to verify the change conclusions, thereby ensuring that the rules are consistent, the process is controllable, and the conclusions are credible.

[0036] Achievements include: making the change decision-making process explicit, assisting designers in quickly reaching change conclusions, ensuring the change decision-making process is traceable, verifying change decision conclusions, providing decision data support for analysis to macroscopically display areas with the most serious change problems, continuously improving product development quality, and shortening the change approval process cycle. This ultimately aims to reduce costs and increase efficiency.

[0037] This invention primarily addresses the inefficiencies, high costs, long cycles, and uncontrollable processes associated with data (materials, drawings, documents) changes during product development. It provides a solution to reduce costs, increase efficiency, and improve the quality of changes.

[0038] The detailed design scheme of this invention is mainly described from the following aspects:

[0039] 1. Data Analysis Rule Extraction

[0040] By researching industry best practices and considering our company's specific circumstances, we communicated with personnel from different professional backgrounds to understand the entire change impact analysis decision-making process, including the technologies, tools, and methods used. The collected data was organized and analyzed, integrating it according to a top-down analytical logic to ensure a streamlined decision-making process and comprehensive coverage of decision content. The final decision tree result is as follows:

[0041] Step 1. Do the product / component before and after the modification meet all the usage requirements of the product (have full interchangeability)? If yes, proceed to step 2.1; otherwise, proceed to step 2.2.

[0042] Step 2.1 Does the product have a relevant user manual or maintenance manual (including maintenance, testing, repair, inspection, etc.)? If the condition is met, proceed to step 3.1; otherwise, proceed to step 4.1.

[0043] Step 2.2: Have all products / parts before the change achieved full interchangeability with the products / parts after the change through economical rework / repair or scrapping and replacement? If the condition is met, proceed to step 3.2; otherwise, proceed to decision conclusion 2.

[0044] Will the change in step 3.1 result in any changes to the published user manual or maintenance manual? If the condition is met, proceed to step 4.2; otherwise, proceed to step 4.1.

[0045] Step 3.2 Can all pre-modification products be traced and controlled through rework or scrapping processes? If the condition is met, proceed to step 2.1; otherwise, proceed to decision conclusion 2.

[0046] Step 4.1 From the level of the final delivered product, does this change need to be visible? If the condition is met, proceed to step 4.2; otherwise, reach decision conclusion 1.

[0047] Step 4.2: If the final product does not change its part number, can the change be made visible? If the condition is met, draw decision conclusion 1; otherwise, draw conclusion 2.

[0048] Decision conclusion 1: Do not change the part number;

[0049] Decision conclusion 2: Assign a new part number;

[0050] The final logical relationship information is as follows Figure 1 As shown.

[0051] 2. Explicitizing program coding decisions

[0052] Based on the rule information formed above, each decision point and the relationships between decision points are encoded, and the encoding results are stored in the backend database (Oracle is used in this invention). The rule configuration is scalable and maintainable, facilitating management personnel to view the information, as shown in the figure below. The backend of this invention is mainly implemented based on a B / S system architecture according to the configuration rules. The frontend uses Vue technology for display, and the backend is coded in Java, based on a template formed by the configuration rules. It also supports step rollback and reset during the decision-making process. The interface is displayed as shown below. Figure 2 As shown.

[0053] 3. Assist in design change decision-making.

[0054] For the rules formed by the above coding, designers only need to call the change decision template before each submission of diagrams or document changes. The system can then generate a change decision tree based on the configured rules and display it through a graphical interface, facilitating rapid design decisions. Each decision starts from the top level of the decision tree, guiding the next step based on the node descriptions, ensuring consistency in the standards and processes used to form each conclusion. Figure 3 As shown.

[0055] 4. The decision-making process is traceable.

[0056] Regarding the above description, before each submission for review, the designer needs to invoke the change decision tree to generate a final change decision roadmap from top to bottom based on the actual impact. The system records each final change decision process. During the review process, a designated person compares the change decision results with the design's change decision results based on the change content and impact analysis. If the conclusions differ, the process can be traced back; if the conclusions are consistent, the consistency of the process can be traced back, because different results will inevitably lead to different decision paths, and even with the same results, the decision paths will not be entirely the same. Figure 4 As shown in the figure.

[0057] 5. Changes to decision-making process data can be shared.

[0058] During the change review process, since everyone involved is responsible for the review of the change, each person must check the correctness of the change decision (the flow of decision points and the correctness of the decision conclusion). Therefore, this invention uses the final change decision result as the final decision result and provides it to the reviewers at each stage to assist them in checking the correctness of the change decision, thereby reducing repetitive work, highlighting key conclusions, and improving work efficiency.

[0059] 6. Continuous iteration of decision-making models

[0060] In addition to assisting in design change decisions and reviewing change decision conclusions, this invention can also transform an organization's implicit assets into an inoperable graphical interface, unify decision-making rules, and avoid relying on personal experience for judgment, thereby improving the standardization and accuracy of change decisions. At the same time, the change decision-making process is recorded, facilitating review and tracing of the results, and the rules are continuously improved and updated during use to ensure that the decision-making process is accurate, scientific, and efficient.

[0061] This invention employs a complete closed-loop problem-solving approach, encompassing data sorting (problem identification), data analysis (problem analysis), rule extraction (solution development), program coding (solution implementation), assisted localization (solution verification), assisted review (solution verification), and self-inspection analysis (regression feedback). This approach ensures a traceable change decision-making process, verifiable conclusions, expandable rules, and explicit logic. It assists designers in making rapid change decisions, allows for the analysis of process data, and enables continuous optimization and iteration of the decision tree model, thereby improving accuracy and reliability. Ultimately, this approach aims to reduce costs, shorten cycles, and increase efficiency.

Claims

1. A method for assisting in improving design change decision-making in a product data management system, characterized in that, The method includes; The collected data used for decision-making is organized and analyzed, and the data is integrated according to a top-down analysis logic to ultimately form a decision tree; Decision trees are used to assist in making decisions when changing them, and the decision-making process when changing decisions is traceable. The decision tree is programmed to make it explicit.

2. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, The decision-making process for changing the decision can be shared.

3. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, The final decision tree is formed as follows: Step 1. Do the products / components before and after the modification meet all the usage requirements of the product? If yes, proceed to Step 2.1; otherwise, proceed to Step 2.

2. Meeting all the usage requirements of the product means that the products / components before and after the modification are completely interchangeable. Step 2.

1. Does the product have a relevant user manual or maintenance manual? If so, proceed to step 3.1; otherwise, proceed to step 4.

1. Step 2.

2. Have all products / parts before the change achieved full interchangeability with the products / parts after the change through economical rework / repair or scrapping and replacement? If the condition is met, proceed to step 3.2; otherwise, proceed to decision conclusion 2. Step 3.

1. Will the change cause any changes to the published user manual or maintenance manual? If the condition is met, proceed to step 4.2; otherwise, proceed to step 4.

1. Step 3.

2. Can all pre-modification products be traced and controlled through rework or scrapping processes? If the condition is met, proceed to step 2.1; otherwise, proceed to decision conclusion 2. Step 4.

1. From the level of the final delivered product, does this change need to be visible? If the condition is met, proceed to step 4.2; otherwise, reach decision conclusion 1. Step 4.

2. Can the visibility of the change be achieved without changing the part number of the final product? If the condition is met, decision conclusion 1 is obtained; otherwise, decision conclusion 2 is obtained. Decision conclusion 1 is to not change the part number, and decision conclusion 2 is to assign a new part number.

4. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, The decision tree is programmed to make it explicit, specifically as follows: Based on the decision tree formed above, each decision point and the relationship between decision points are encoded and the encoding results are stored in the background database, thereby making the tacit knowledge explicit. The tacit knowledge is the relationship between each decision point and decision points in the decision tree.

5. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, Regarding the decision tree mentioned above, designers invoke the decision tree before each design change and display it through a graphical interface. Each decision starts from the top of the decision tree, and the next step is guided by the description of the decision point, ensuring the consistency of the standards and processes for forming each decision conclusion.

6. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, Before submitting each design change, designers need to invoke the decision tree to form a final change decision roadmap from top to bottom based on the actual impact. Each final change decision roadmap is recorded. When the decision conclusions are different, the process can be traced. When the decision conclusions are consistent, the consistency of the process can be traced. This is because different decision conclusions will inevitably lead to different decision paths, and even the same decision conclusions will not necessarily lead to the same decision path.

7. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, During the design change process, the decision-making path and conclusions are provided to personnel at each stage to assist them in verifying the correctness of the change decision.

8. The method for assisting in improving design change decision-making in a product data management system according to claim 1, characterized in that, The decision tree is scalable and maintainable, and can be improved and updated during use.

Images