A component structure tree based order allocation system and method

Abstract

The application relates to the technical field of big data analysis, and discloses an order distribution system and method based on a component structure tree, wherein a component structure tree is constructed in advance, including a multi-level hierarchical structure based on category division and component information associated with a last-level category, the component information including at least one material coding attribute; each material coding attribute is associated with a supplier and is associated with multiple evaluation attribute data; the method comprises the following steps: obtaining a to-be-purchased order; based on the component structure tree, obtaining corresponding suppliers and material codes corresponding to each supplier according to the to-be-purchased components, extracting evaluation attribute data, and evaluating each component provided by each supplier; and based on a preset order distribution rule, distributing the suppliers according to the evaluation result. Through the establishment of the component structure tree, the integration of all components and supplier evaluation related data is realized, and objective supplier distribution can be performed on the to-be-purchased order.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of big data analysis, and particularly relates to an order allocation system and method based on a component structure tree. BACKGROUND

[0002] The statements in this section merely provide background information related to the present application and do not necessarily constitute the prior art.

[0003] The quality problem of an enterprise product mainly comes from a supplier, and therefore there is a certain risk in purchasing, especially in the manufacturing industry, where the quality of a supplier directly affects the entire product production chain. How to effectively select a supplier and how to reasonably allocate when there are multiple suppliers for a certain component are the main problems faced by the purchasing department.

[0004] Currently, the purchasing department usually evaluates a supplier according to factors such as the product quality, product quality and price of the supplier's product, but the evaluation index is too single, the same supplier may provide multiple products or components, and the importance of different components is different, the technical requirements of components with low importance degree are usually not high, and the components provided by different suppliers are not significantly different, and the price may be a more important index. If the same evaluation index is used to evaluate all components, there is an unreasonable place, which also affects the overall evaluation of the subsequent supplier. Moreover, for the quality index, the product will be inspected during the warehousing and operation stages, and the current quality index is based on single data, which may depend on the warehousing stage or only depend on the subsequent operation stage, and there is no evaluation system that considers the whole life cycle quality of the product.

[0005] In addition to perfecting the evaluation system, a comprehensive and objective evaluation also needs sufficient data support. It is too tedious for the purchasing department to collect all the data related to a certain component, although the quality management system, operation management system and supplier management system have stored relevant data, but these system data cannot be effectively utilized. SUMMARY

[0006] To overcome the above shortcomings of the prior art, the present application provides an order allocation system and method based on a component structure tree, which realizes the integration of all component and supplier evaluation related data by establishing a component structure tree, and can objectively allocate suppliers for a proposed purchase order.

[0007] To achieve the above object, one or more embodiments of the present application provide the following technical solutions:

[0008] A server configured to include:

[0009] The component structure tree management module is used to manage the component structure tree, which includes a multi-level hierarchical structure based on category division, and component information associated with the last-level category. The component information includes at least one material code attribute; wherein, each material code attribute is associated with a supplier and multiple evaluation attribute data.

[0010] The proposed purchase order acquisition module is used to acquire proposed purchase orders, which include the parts and quantities to be purchased.

[0011] The component evaluation module is used to obtain the corresponding suppliers and their corresponding material codes based on the component structure tree, according to the components to be purchased; and to extract relevant evaluation attribute data based on each material code to evaluate each component provided by each supplier.

[0012] The order allocation module is used to allocate suppliers to the orders based on the component evaluation results and preset order allocation rules.

[0013] Furthermore, the method for constructing the component structure tree includes:

[0014] All product-related functions are divided into hierarchical categories until no further division is possible, resulting in a multi-level hierarchical structure based on product category division; based on the last level of product category, component information is associated.

[0015] Obtain the registered material codes from the design phase, as well as the supplier's historical inbound material data, extract the material codes for all components, and create a corresponding number of material code attributes for each component.

[0016] Create multiple evaluation attributes for each material code attribute;

[0017] Data related to the multiple evaluation attributes is retrieved from the quality management system, operations management system, and supplier management system, and written into the corresponding evaluation attributes.

[0018] Furthermore, the server also includes: a weight allocation scheme management module, used to manage the corresponding weight allocation scheme when evaluating components of different importance levels;

[0019] The component information in the component structure tree also includes an importance level attribute;

[0020] The component evaluation module also obtains the importance level of each component based on the component structure tree, and then obtains the corresponding weight allocation scheme. Combined with relevant evaluation attribute data, it evaluates each component provided by each supplier.

[0021] Furthermore, the server also includes a supplier evaluation module, used to perform an overall evaluation of the suppliers based on the evaluation results of each component of each supplier.

[0022] Furthermore, the order allocation module is used to allocate suppliers to the orders based on the component evaluation results and the overall supplier evaluation results, according to preset order allocation rules.

[0023] Furthermore, the server also includes an order allocation rule management module for managing order allocation rules.

[0024] One or more embodiments provide a client connected to the server, configured to include: an order allocation rule editing module for formulating order allocation rules.

[0025] Furthermore, it also includes a weight allocation scheme editing module, which is used to edit the weight allocation scheme.

[0026] Furthermore, it also includes an order allocation correction module, which receives the allocation scheme generated by the server and corrects it as needed.

[0027] One or more embodiments provide an order allocation system based on a component structure tree, including the server and the client.

[0028] One or more embodiments provide an order allocation method based on a component structure tree. A component structure tree is pre-constructed, comprising a multi-level hierarchical structure based on product category division, and component information associated with the last-level product category. The component information includes at least one material code attribute; wherein each material code attribute is associated with a supplier and multiple evaluation attribute data; the method specifically includes:

[0029] Obtain the proposed purchase order, which includes the parts and quantities to be purchased;

[0030] Based on the components to be procured, obtain the corresponding suppliers and their corresponding material codes according to the component structure tree;

[0031] Based on the material codes, relevant evaluation attribute data are extracted, and evaluations are conducted on each component provided by each supplier.

[0032] Based on the component evaluation results and according to the preset order allocation rules, the orders are allocated to suppliers.

[0033] Furthermore, the method for constructing the component structure tree includes:

[0034] All product-related functions are divided into hierarchical categories until no further division is possible, resulting in a multi-level hierarchical structure based on product category division; based on the last level of product category, component information is associated.

[0035] Obtain the registered material codes from the design phase, as well as the supplier's historical inbound material data, extract the material codes for all components, and create a corresponding number of material code attributes for each component.

[0036] Create multiple evaluation attributes for each material code attribute;

[0037] Data related to the multiple evaluation attributes is retrieved from the quality management system, operations management system, and supplier management system, and written into the corresponding evaluation attributes.

[0038] Furthermore, the component information in the component structure tree also includes an importance level attribute, with each importance level corresponding to a pre-configured weight allocation scheme;

[0039] The method also obtains the importance level of each component based on the component structure tree, and then obtains the corresponding weight allocation scheme. Combined with relevant evaluation attribute data, it evaluates each component provided by each supplier.

[0040] Furthermore, after obtaining the evaluation results of each component from each supplier, an overall evaluation of the supplier is conducted based on the evaluation results of each component from each supplier.

[0041] Furthermore, based on the component evaluation results and the overall supplier evaluation results, the orders are allocated to suppliers according to preset order allocation rules.

[0042] The above one or more technical solutions have the following beneficial effects:

[0043] By establishing a component structure tree and using material codes as a guide, all component and supplier evaluation data were integrated, enabling specialized data management for the purchasing department. Furthermore, the evaluation of components reflects the situation of each supplier, providing an objective basis for supplier allocation.

[0044] By creating importance level attributes for each component and pre-configuring corresponding weight allocation schemes for each level, the different reference weights for each indicator during evaluation are fully considered for components of different importance. For example, the technical indicators of more important components have a relatively larger reference weight. This allows for the adaptive selection of a more reasonable weight allocation scheme during the evaluation of each component, resulting in more objective evaluation results. Furthermore, the weight allocation scheme can be adjusted according to user needs, providing greater flexibility.

[0045] By evaluating components and suppliers, the procurement department can be provided with multi-dimensional decision-making references. Attached Figure Description

[0046] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0047] Figure 1 This is a framework diagram of the order allocation system based on the component structure tree as described in one or more embodiments of the present invention;

[0048] Figure 2 This is a flowchart illustrating the construction of the component structure tree in one or more embodiments of the present invention;

[0049] Figure 3 This is a schematic diagram of the component structure tree in one or more embodiments of the present invention;

[0050] Figure 4 This is a flowchart of the order allocation method based on the component structure tree described in Embodiment 2 of the present invention. Detailed Implementation

[0051] It should be noted that the following detailed descriptions are exemplary and intended to provide further illustration of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0052] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0053] Where there is no conflict, the embodiments and features in the embodiments of the present invention can be combined with each other.

[0054] Example 1

[0055] This embodiment discloses an order allocation system based on a component structure tree. By establishing a component structure tree, data from various systems such as the quality management system, operation management system, and supplier management system are linked and integrated. This system can adaptively select appropriate evaluation schemes for components in an order and allocate orders based on the evaluation results.

[0056] like Figure 1As shown, the system includes a server and a client. The server is connected to the quality management system, the operations management system, and the supplier management system. Specifically, it includes a module for acquiring purchase orders, a component structure tree management module, a weight allocation scheme management module, an order allocation rule management module, a component evaluation module, a supplier evaluation module, and an order allocation module. Detailed explanations are as follows:

[0057] The proposed purchase order acquisition module is used to acquire proposed purchase orders, which include the parts to be purchased and their quantities.

[0058] A component structure tree management module is used to manage component structure trees. The component structure tree includes a multi-level hierarchical structure based on product categories, and component information associated with the lowest-level product category. The component information includes an importance level attribute and at least one material code attribute. Each material code attribute is associated with a supplier and multiple evaluation attribute data, including technical attributes, commercial attributes, price attributes, and quality attributes. The component structure tree construction method includes:

[0059] (1) Take all products as the root node, first divide the relevant functions of all products level by level until they cannot be divided, and obtain the multi-level division result of the function category, or category. Then, based on the last level category, associate specific components and further divide them according to the structural composition of the components to obtain the component structure tree.

[0060] At this point, all products that a company needs to purchase have been categorized and their components broken down. This serves as a framework for data storage and management, ensuring data standardization and facilitating subsequent data management.

[0061] Each leaf node in the component structure tree corresponds to a specific component. Each leaf node includes multiple attributes, specifically: an importance level attribute and at least one material code attribute. The number of material code attributes is related to the number of suppliers; different suppliers use different material codes for the same component. Furthermore, each material code attribute includes next-level attributes: technical attributes, commercial attributes, price attributes, and quality attributes. Technical attributes can further include performance requirements, application history, reliability and safety requirements, technical data and spare parts, packaging and transportation plans, installation and commissioning plans, and acceptance plans. Commercial attributes can further include product delivery quality, reputation, financial status, payment methods, after-sales service, supplier qualification level, and contract terms. Price attributes can further include the clarity and completeness of supplier quotations from the business unit and finance department, and the compliance of the quotations. Quality attributes can further include first-inspection issues, warehousing quality issues, production process quality issues, and operational quality issues.

[0062] like Figure 2 As shown, based on the category division, the category node of air supply brake is further associated with the main air supply unit, air cylinder and auxiliary air compressor. Furthermore, the leaf node of main air supply unit is set with three attributes, including importance level attribute and two material code attributes. Each material code attribute is set with technical attribute, commercial attribute, price attribute and quality attribute.

[0063] (2) Obtain the registered material codes in the design phase and obtain the historical material data of the supplier, extract the components and their material codes, associate them with the component structure tree by the component name, and construct the material code attribute of the component structure tree. Each material code corresponds to a material code attribute.

[0064] (3) Using the quality management system, operation management system and supplier management system as the basic data system, capture the basic data of the proposed purchase order, including the quality data of the purchased products, operation failure data, technical evaluation data, business evaluation, price data, supplier qualifications, etc.

[0065] Using the material code as the associated attribute, establish associations with product quality data, operational failure data, technical evaluation data, business evaluation, price data, and supplier data. Write product quality data and operational failure data into the quality attribute, technical evaluation data into the technical attribute, business evaluation and supplier qualifications into the business attribute, and price data into the price attribute.

[0066] Those skilled in the art will understand that after capturing the basic data, the basic data is first cleaned and processed using big data technology. Then, relevant data that needs to be associated with the component structure tree is obtained. Based on preset rules, the obtained data is standardized and normalized, and then written into the corresponding node attributes in the component structure tree.

[0067] Based on the component structure tree, by using material codes as unique identifiers for different suppliers of various components, the system integrates multiple systems such as the quality management system, operation management system, and supplier management system, providing data assurance for subsequent data analysis. By setting multi-level attributes under each material code, it can comprehensively cover all indicator data related to the component evaluation, integrating data from all processes such as component design, warehousing, and production. In other words, the component structure tree links all data related to component evaluation and supplier evaluation, facilitating an objective and comprehensive evaluation of a specific component provided by a particular supplier. Furthermore, by evaluating each component provided by a supplier, it can reflect the supplier's existing problems, providing a reference for future procurement decisions.

[0068] Importance level attributes can be assigned values ​​such as A / B / C / D to associate different weight allocation schemes.

[0069] The weight allocation scheme management module manages the weight allocation schemes for evaluating components of different importance levels. These weight allocation schemes can be adjusted via the client application according to user needs.

[0070] Generally speaking, components with higher importance have higher technical requirements and the highest weighting for technical attributes, while price has a lower weighting. Conversely, components with lower importance have lower technical requirements and a higher price weighting. As an example, the weighting scheme used in this embodiment is shown in Table 1.

[0071] Table 1. Weighting schemes for different importance levels.

[0072]

[0073]

[0074] The order allocation rule management module is used to manage order allocation rules. Users can adjust the order allocation rules as needed via the client. As an example, the following order allocation rules are used in this embodiment:

[0075] (1) For components with only one supplier, direct allocation is performed;

[0076] (2) For components with multiple suppliers, first obtain the supplier with the fewest deductions and the highest score, and allocate 10% of the share to it; then obtain the supplier with the largest historical supply quantity, and allocate 10% of the share to it; finally, distribute the remaining share equally among all suppliers.

[0077] The component evaluation module is used to evaluate components from various suppliers, specifically including:

[0078] (1) Based on the components to be purchased, obtain the importance level, corresponding suppliers, and material codes of each supplier according to the component structure tree;

[0079] (2) Extract relevant basic data based on each material code, including quality evaluation data, technical evaluation data, business evaluation data and price data;

[0080] (3) Based on the importance level of each component, obtain the corresponding weight allocation scheme and evaluate each component provided by each supplier.

[0081] In step (3), the calculation method for evaluating each component is as follows:

[0082] Total score = Technical score * weight + Business score * weight + Price score * weight + Quality and after-sales service score * weight.

[0083] Technical Score: The technical score is obtained through technical evaluation data and mainly includes performance requirements, application performance, reliability and safety requirements, technical documentation and spare parts, packaging and transportation plans, installation and commissioning plans, and acceptance plans. Technical Score = ∑Score of each evaluation item × Weight.

[0084] Business Score: The business score is obtained through business evaluation data, primarily reflecting the requirements of purchasing departments, business units, or technology management departments and supplier management departments for suppliers. These requirements include product delivery quality, reputation, financial status, payment methods, after-sales service, supplier qualification level, and contract terms. Supplier qualification levels are divided into four grades: Excellent (X≥90 points), Good (80≤X<90 points), Meets Standard (70≤X<80 points), and Unmet Standard (<70 points). Business Score = ∑Score of each evaluation item × Weight.

[0085] Price Score: The price score is obtained through price data and mainly reflects the clarity, completeness, and compliance of the supplier's quotations by the business and finance departments; Price Score = ∑Score of each evaluation item × Weight.

[0086] Quality Score: The quality score is obtained through quality data and operational failure data. Product quality aspects mainly include: first inspection issues, incoming inspection, process quality issues, supervision issues, operational quality issues, failure rate, special inspection issues, and whether the supplier is new. After-sales quality score = weight × (100 - ∑ deductions for each evaluation item / quantity supplied × total quantity).

[0087] The supplier evaluation module is used to evaluate suppliers as a whole based on the evaluation results of each component of each supplier.

[0088] This embodiment provides a reference for the procurement department through two dimensions: component evaluation and overall supplier evaluation. On the one hand, it pushes the corresponding component evaluation results of each supplier; on the other hand, it displays the overall supplier evaluation.

[0089] The order allocation module is used to allocate suppliers to orders based on component evaluation results and overall supplier evaluation results, according to preset order allocation rules. To improve the flexibility of order allocation, the supplier allocation results can be modified via the client according to user needs.

[0090] The client establishes a connection with the server, including:

[0091] The weight allocation scheme editing module is used to edit the weight allocation scheme;

[0092] The order allocation rule editing module is used to formulate order allocation rules;

[0093] The order submission module is used to confirm the items and quantities to be purchased, generate a purchase order, and send it to the server.

[0094] The order allocation correction module is used to receive the allocation scheme generated by the server and correct it as needed.

[0095] For data that was not initially managed using a component structure tree, this embodiment also provides a backend redundancy method to link it to the component structure tree. Specifically, the system also includes a quality inspection terminal for performing quality inspections during component warehousing, production, or operation. Quality engineers manually enter the responsible unit, supplier, product category, and material code for the inspected component. Based on this, early unstructured data can be gradually incorporated into the component structure tree.

[0096] The aforementioned order allocation system integrates data related to all components and supplier evaluations through a component structure tree. It also provides specific component evaluation methods and overall supplier evaluation methods, enabling the purchasing department to understand the situation of each supplier from multiple dimensions. Furthermore, it offers a flexible adjustment module that can adjust the preset weight allocation scheme, order allocation rules, and final allocation results as needed to meet the personalized needs of enterprises and has certain promotional value.

[0097] Example 2

[0098] Based on the order allocation system provided in Embodiment 1 above, this embodiment provides an order allocation method. A component structure tree is pre-constructed, comprising a multi-level hierarchical structure based on product category division, and component information associated with the last-level product category. The component information includes at least one material code attribute; wherein each material code attribute is associated with a supplier and multiple evaluation attribute data. The method includes the following steps:

[0099] Step 1: Obtain the proposed purchase order, which includes the parts to be purchased and their quantities;

[0100] Step 2: Based on the components to be procured, obtain the corresponding suppliers and their corresponding material codes according to the component structure tree;

[0101] Step 3: Extract relevant evaluation attribute data based on each material code, and evaluate each component provided by each supplier;

[0102] Step 4: Based on the component evaluation results and the preset order allocation rules, allocate suppliers to the orders.

[0103] Since different components have varying reference values ​​for indicators such as quality and price based on their importance, this embodiment assigns different importance levels to components and pre-configures corresponding weight allocation schemes for each importance level to achieve a more reasonable evaluation. Specifically, the component information in the component structure tree also includes an importance level attribute. In step 2, the importance level of the component to be procured is also obtained based on the component structure tree.

[0104] Specifically, the method for constructing the component structure tree includes:

[0105] All product-related functions are divided into hierarchical categories until no further division is possible, resulting in a multi-level hierarchical structure based on product category division; based on the last level of product category, component information is associated.

[0106] Create importance level data for each component, which can be entered manually or written according to pre-defined level rules;

[0107] Obtain the registered material codes from the design phase, as well as the supplier's historical inbound material data, extract the material codes for all components, and create a corresponding number of material code attributes for each component.

[0108] Create multiple evaluation attributes for each material code attribute;

[0109] Data related to the multiple evaluation attributes is retrieved from the quality management system, operations management system, and supplier management system, and written into the corresponding evaluation attributes.

[0110] Based on this, step 3, which evaluates each component provided by each supplier, includes: obtaining a corresponding weight allocation scheme based on the importance level of the component to be purchased, and evaluating each component provided by each supplier in conjunction with relevant evaluation attribute data.

[0111] The above method only allocates orders from the perspective of evaluating each component. In order to make the order allocation more objective and reasonable, this embodiment also introduces an overall supplier evaluation. Specifically, after performing step 3, an overall evaluation of each supplier is performed based on the evaluation results of each component.

[0112] Finally, in step 4, based on the component evaluation results and the overall supplier evaluation results, the orders are allocated to suppliers according to the preset order allocation rules.

[0113] For details regarding the component structure tree, weight allocation scheme, and preset order allocation rules involved in the above embodiment two, please refer to the relevant description section of embodiment one.

[0114] Those skilled in the art will understand that the modules or steps of the present invention described above can be implemented using general-purpose computer devices. Optionally, they can be implemented using computer-executable program code, thereby allowing them to be stored in a storage device for execution by a computer device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. The present invention is not limited to any particular combination of hardware and software.

[0115] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. A server, characterized in that, Configured to include: The component structure tree management module is used to manage the component structure tree, which includes a multi-level hierarchical structure based on category division, and component information associated with the last-level category. The component information includes at least one material code attribute; wherein, each material code attribute is associated with a supplier and multiple evaluation attribute data. The proposed purchase order acquisition module is used to acquire proposed purchase orders, which include the parts and quantities to be purchased. The component evaluation module is used to obtain the corresponding suppliers and their corresponding material codes based on the component structure tree, according to the components to be purchased; and to extract relevant evaluation attribute data based on each material code to evaluate each component provided by each supplier. The order allocation module is used to allocate suppliers to the orders based on the component evaluation results and a preset order allocation rule. The weight allocation scheme management module is used to manage the weight allocation schemes corresponding to the evaluation of components with different importance levels; The component information in the component structure tree also includes an importance level attribute; The component evaluation module also obtains the importance level of each component based on the component structure tree, and then obtains the corresponding weight allocation scheme. Combined with relevant evaluation attribute data, it evaluates each component provided by each supplier.

2. The server as described in claim 1, characterized in that, The method for constructing the component structure tree includes: All product-related functions are divided into hierarchical categories until no further division is possible, resulting in a multi-level hierarchical structure based on product category division; based on the last level of product category, component information is associated. Obtain the registered material codes from the design phase, as well as the supplier's historical inbound material data, extract the material codes for all components, and create a corresponding number of material code attributes for each component. Create multiple evaluation attributes for each material code attribute; Data related to the multiple evaluation attributes is retrieved from the quality management system, operations management system, and supplier management system, and written into the corresponding evaluation attributes.

3. The server as described in claim 1, characterized in that, The server also includes a supplier evaluation module, which is used to evaluate suppliers as a whole based on the evaluation results of each component of each supplier.

4. The server as described in claim 3, characterized in that, The order allocation module is used to allocate suppliers to the orders based on the component evaluation results and the overall supplier evaluation results, according to preset order allocation rules.

5. The server as described in claim 1 or 4, characterized in that, The server also includes an order allocation rule management module for managing order allocation rules.

6. A client connected to a server as described in claims 1-5, characterized in that, It is configured to include: an order submission module, used to confirm the items and quantities to be purchased, generate a purchase order, and send it to the server.

7. The client as described in claim 6, characterized in that, Also includes: The order allocation rule editing module is used to formulate order allocation rules.

8. An order allocation system based on a component structure tree, characterized in that, This includes the server as described in any one of claims 1-5 and the client as described in claim 6 or 7.

9. An order allocation method based on a component structure tree, characterized in that, A component structure tree is pre-constructed, comprising a multi-level hierarchical structure based on product category division, and component information associated with the last-level product category. The component information includes at least one material code attribute; wherein each material code attribute is associated with a supplier and multiple evaluation attribute data; the method specifically includes: Obtain the proposed purchase order, which includes the parts and quantities to be purchased; Based on the components to be procured, obtain the corresponding suppliers and their corresponding material codes according to the component structure tree; Based on the material codes, relevant evaluation attribute data are extracted, and evaluations are conducted on each component provided by each supplier. Based on the component evaluation results and according to the preset order allocation rules, the orders are allocated to suppliers. The component information in the component structure tree also includes an importance level attribute, with each importance level corresponding to a pre-configured weight allocation scheme; The method also obtains the importance level of each component based on the component structure tree, and then obtains the corresponding weight allocation scheme. Combined with relevant evaluation attribute data, it evaluates each component provided by each supplier.

10. The order allocation method based on the component structure tree as described in claim 9, characterized in that, The method for constructing the component structure tree includes: All product-related functions are divided into hierarchical categories until no further division is possible, resulting in a multi-level hierarchical structure based on product category division; based on the last level of product category, component information is associated. Obtain the registered material codes from the design phase, as well as the supplier's historical inbound material data, extract the material codes for all components, and create a corresponding number of material code attributes for each component. Create multiple evaluation attributes for each material code attribute; Data related to the multiple evaluation attributes is retrieved from the quality management system, operations management system, and supplier management system, and written into the corresponding evaluation attributes.

11. The order allocation method based on the component structure tree as described in claim 9, characterized in that, After obtaining the evaluation results for each component of each supplier, an overall evaluation of the supplier is also conducted based on the evaluation results for each component of each supplier.

12. The order allocation method based on the component structure tree as described in claim 11, characterized in that, Based on the component evaluation results and the overall supplier evaluation results, the orders are allocated to suppliers according to the preset order allocation rules.

Images