Project component list management method and device, equipment and storage medium

Abstract

The invention discloses a project component list management method and device, equipment and a storage medium, and relates to the technical field of data management. The method comprises the steps that a product specification pool of all parts is constructed in advance according to part specification values of the parts, when a project part list needs to be generated, a project party directly selects a needed target product specification from the product specification pool, project specification demand information is generated, and then the project part list is generated according to the corresponding relation between the pre-constructed product specification and an actual part. Therefore, the system can directly determine the target component conforming to the target product specification, so that the item component list is automatically generated based on the information of the target component, material confirmation of the component does not need to be manually executed, and the accuracy and efficiency of item component list management are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data management, and particularly relates to a method, device, equipment and storage medium for managing a project component list. Background Art

[0002] With the development of the server industry, the diversification of customer needs and the acceleration of platform iteration, the management of project component lists faces problems such as accuracy, timeliness and repetitive work. In related technologies, the collection and update of project component lists rely on offline forms and emails. That is, the product manager sorts out the specification information of the components required for the product in the form of an offline form, and after finishing the sorting, sends it to the component responsible person. The component responsible person needs to sequentially confirm the actual materials corresponding to each specification information in the form (the specification information only includes some parameters of the component, and the actual material is the determined model product), and then generate the project component list of the project according to the actual materials. In this solution, for each project and the update of components in the project, the component responsible person needs to manually confirm the actual materials corresponding to the specification information in the form one by one, resulting in the component responsible person spending a lot of time on material confirmation, reducing the efficiency and accuracy of project component list management, and even seriously affecting the project progress in severe cases. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a method, device, equipment and storage medium for managing a project component list, which can improve the accuracy and efficiency of project component list management. The specific solutions are as follows: In a first aspect, the present application discloses a method for managing a project component list, including: Obtaining project specification requirement information; the project specification requirement information includes component requirement information and target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; Determining the target components corresponding to the target product specification information according to the correspondence between the product specifications and the actual components; Generating a project component list based on the target components corresponding to all the target product specification information in the project specification requirement information.

[0004] In a second aspect, the present application discloses a device for managing a project component list, including: An information acquisition module for obtaining project specification requirement information; the project specification requirement information includes component requirement information and target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; A target component determination module, configured to determine a target component corresponding to the target product specification information according to the correspondence between the product specification and the actual component; An inventory generation module, configured to generate a project component inventory based on the target components corresponding to all the target product specification information in the project specification requirement information.

[0005] Thirdly, the present application discloses an electronic device, including: A memory, configured to store a computer program; A processor, configured to execute the computer program to implement the foregoing project component inventory management method.

[0006] Fourthly, the present application discloses a computer-readable storage medium, configured to store a computer program; wherein the computer program, when executed by a processor, implements the foregoing project component inventory management method.

[0007] Fifthly, the present application discloses a computer program product, including a computer program, which, when executed by a processor, implements the foregoing project component inventory management method.

[0008] In the present application, project specification requirement information is obtained; the project specification requirement information includes component requirement information and target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; according to the correspondence between the product specification and the actual component, the target component corresponding to the target product specification information is determined; and a project component inventory is generated based on the target components corresponding to all the target product specification information in the project specification requirement information.

[0009] It can be seen that by pre-constructing the product specification pool for each component according to the component specification values of the components, when it is necessary to generate a project component inventory, the project party directly selects the required target product specifications from the product specification pool to generate project specification requirement information, and then combines the pre-constructed correspondence between the product specification and the actual component, and the system can directly determine the target components that meet the target product specifications, so as to automatically generate a project component inventory based on the information of the target components, without manual material confirmation of the components, improving the accuracy and efficiency of project component inventory management. Description of the Drawings

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention, and those of ordinary skill in the art can also obtain other drawings according to the provided drawings without creative efforts. Figure 1 A flowchart of a method for managing a project component list provided by this application; Figure 2 A schematic diagram of a specific project component list structure provided by this application; Figure 3 A flowchart of a specific method for managing a project component list provided by this application. Specific implementation manners

[0011] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, rather than all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0012] In the prior art, the collection and update of the project component list rely on offline forms and emails. That is, the product manager sorts out the specification information of the components required for the product in the form of an offline form, and after finishing sorting, sends it to the component responsible person. The component responsible person needs to sequentially confirm the actual materials corresponding to the specification information in the form one by one (the specification information only includes some parameters of the component, and the actual material is the determined model product), and then generate the project component list of this project according to the actual materials. Under this solution, for each project and the update of the components in the project, the component responsible person needs to manually confirm the actual materials corresponding to the specification information in the form one by one, resulting in the component responsible person spending a lot of time on material confirmation. However, in multiple confirmations, there will be repeated confirmations of the same materials, wasting workload and increasing operational complexity; moreover, under this solution, the requirement for the component responsible person to be familiar with the components will further affect the accuracy of the list. It reduces the efficiency and accuracy of project component list management, and in serious cases, even affects project progress. To overcome the above technical problems, this application proposes a method for managing a project component list, which can improve the accuracy and efficiency of project component list management.

[0013] An embodiment of this application discloses a method for managing a project component list. Refer to Figure 1 As shown, the method may include the following steps: Step S11: Obtain project specification requirement information; the project specification requirement information includes component requirement information and the target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components.

[0014] First, obtain the project specification requirement information sent by the project party. The project specification requirement information includes the information of the required components and the target product specification information of these components. The target product specification information is selected from the product specification pool, which is pre-constructed based on the product specifications of different model components. That is to say, the project party selects the corresponding product specification information from the product specification pool as the target product specification information according to the requirements for components. It should be noted that multiple target product specification information can be added for one type of component to form the project specification requirement information. It can be understood that the product specifications of the same type of component may vary under different models. What the project party needs is not only this type of component but also components that meet certain product specifications.

[0015] As shown in Table 1 below: Table 1 Project Specification Requirement Information Table Table 1 is the project product specification package of a project. The project product specification package contains the project specification requirement information of this project. According to Table 1, the required components of this project include hard disks, memory, RAID (Redundant Array of Independent Disks) cards, graphics cards, etc. Among them, taking the hard disk as an example, the target product specification information of the hard disk includes Product Specification 1, Product Specification 2, and Product Specification 3. That is to say, the product specification pool of the hard disk may contain Product Specification 1, Product Specification 2... Product Specification n, and the project party selects 3 product specifications as the target product specification information from them. It can be understood that each type of component corresponds to a product specification pool. For example, the hard disk corresponds to a product specification pool, and the graphics card corresponds to a product specification pool. The product specification pool is pre-constructed based on the product specifications of the components. For example, taking the hard disk as an example, there are various product specifications of hard disks, and the product person in charge will construct the product specification pool of the hard disk according to all possible product specifications.

[0016] In some embodiments, the construction process of the above product specification pool includes: determining different product specifications corresponding to the components according to the correspondence between the components and the component specifications and the correspondence between the component specifications and the specification values; obtaining the product specification pool of this type of component based on all the product specifications corresponding to the same type of components.

[0017] As shown in Table 2 below: Table 2 Component and Component Specification Table Table 2 shows the correspondence between the components and the component specifications. Taking the hard disk as an example, the specifications of the hard disk include: manufacturer, capacity, size, and interface.

[0018] As shown in Table 3 below: Table 3 Hard Disk Specifications and Specification Value Table Table 3 shows the correspondence between hard disk specifications and specification values, that is, a correspondence table of specifications and specification values is constructed for components. Taking the hard disk in Table 3 as an example, the attribute values of the capacity attribute include 24T, 20T, 18T, 16T, etc. Based on the correspondence between components and component specifications, and the correspondence between component specifications and specification values, the product specifications of components under different product models can be obtained.

[0019] As shown in Table 4 for example: Table 4 Product Specification Table Table 4 shows different product specifications of the hard disk, that is, one row in the table of Table 4 is a product specification. It can be determined from Table 4 that the hard disk includes at least 4 product specifications. Product specification 1 is: Manufacturer 1, 24T, 3.5, SATA; Product specification 2 is: Manufacturer 2, 20T, 3.5, SAS; Product specification 3 is: Manufacturer 3, 16T, 2.5, SATA; Product specification 4 is: Manufacturer 4, 20T, 3.5, SAS. That is, the project party can select Product specification 1 as the target product specification information from them. By adding the maintenance of the correspondence between components and component specifications, and the correspondence between component specifications and specification values, a product specification pool is constructed, and the uniqueness of each product specification is determined through unified maintenance.

[0020] Step S12: Determine the target component corresponding to the target product specification information according to the correspondence between the product specification and the actual component; The product specification is only constructed from the specification dimension and there are still differences from the actual component (i.e., the actual material). Therefore, it is also necessary to pre-construct the correspondence between the product specification and the actual component, so that the corresponding target component can be directly found according to the obtained target product specification information.

[0021] The product manager uniformly maintains the component product specifications, creates the maintenance pages for components and component specifications, and creates the inherent attribute information of each type of component according to the component classification based on the characteristics of the components. Each specification information of each type of component has a fixed specification value. Based on the component specifications and specification values that have been introduced or will be introduced, the corresponding relationship between component specifications and specification values is created. Each type of component creates the product specifications of the corresponding component according to the actual operation requirements, forming the product specification pools of various components. In the product specification pools of each type of component that have been built, select the component product specifications required for each project to form the project specification requirement information. Through data management of component types, component specifications, and specification values, these data records are associated to form a product specification pool; the product specification pool is uniformly defined and maintained through the system, reducing non-standard situations such as different components being recognized for the same target product specification information due to human reasons, and at the same time avoiding a large amount of back-and-forth confirmation work.

[0022] Step S13: Generate a project component list based on the target components corresponding to all the target product specification information in the project specification requirement information.

[0023] Determine the target components that meet the target product specification information, and then generate a project component list based on the component information of all the determined target components. It can be understood that the target product specification information only contains some specification information, but the product specifications of the components in the product specification pool contain more comprehensive component attribute values. Taking a hard disk as an example, the target product specification information includes the capacity and interface of the hard disk. The target hard disks are screened according to the capacity and interface, and the project component list is constructed according to the attribute values of the target hard disks (such as manufacturer information, capacity, size, and interface, etc.).

[0024] Specifically, the structure of the project component list can be Figure 2 as shown, that is, based on the project product package (i.e., the project specification requirement information), determine the target components corresponding to each target product specification information, and each target component automatically brings out the confirmed component attributes. Through the system data records, the product specifications, components, and attribute information under the components are associated together to form a project component list. The export function of the project component list is supported. Specifically, based on a fixed export template, through the export function, the project component list can be exported, realizing the one-key online generation of the project component list, improving work efficiency and increasing the accuracy of the component list.

[0025] It is understandable that the introduced component products are limited, the product specifications are basically fixed, most of the product specifications are reused frequently, some product specifications are reused less frequently, and there is also a small part of the product specifications that are only used in individual items. Generally speaking, all product specifications will be used and at least used once. Since the product specifications are the same and there is basically no difference in the materials, each product specification only needs to be confirmed once in practice. However, in the related technologies, the project side first puts forward component requirements, and then the component person in charge confirms the target component corresponding to the component requirements, that is, the actual materials. The same component requirements may exist in different projects, but the requirements of each project still need to be confirmed, which increases the number of times of repeatedly confirming the materials for the same product specification. Moreover, the confirmation of materials is all manually confirmed offline, and different confirmers and different confirmation times may lead to different results of component confirmation in the project component list. Under normal circumstances, the confirmation results of the same product specification should be the same, and the component confirmation results under the product specification should not be different due to different collection and update times of the component list in different projects or different confirmers who give feedback. Through constructing a product specification pool, this application separates the process of the component person in charge confirming the component information under the product specification from the project. First, it automatically confirms the component information under the product specification, and the project integrates the project component list on the system based on their respective requirements; the information of the components in the product specification pool has been confirmed to be correct, so the information of the components exported in the project component list will be more accurate.

[0026] The combination of the current server projects, platforms, and components' diversity, along with the testing of actual scenario changes and requirements, has led to the existing collection and update of the project component list being unable to meet the actual application anymore, and the accuracy and timeliness cannot be guaranteed even more. By decomposing the project component list, separately maintaining each item of information and its associated relationships, and then using this information to achieve the automatic collection and update of the project component list, it not only improves the accuracy of the list but also reduces a large amount of repetitive work, and can also enable the project to obtain the changes in the list in a timely manner, which is more in line with the actual business scenario; it makes the collection and update of the project component list more timely, accurate, and more in line with the actual application project scenario. Through the product specification pool and the project specification requirement information, it quickly and accurately realizes the collection of the project component list, improving the collection efficiency of the project component list.

[0027] As can be seen from the above, in this embodiment, project specification requirement information is obtained; the project specification requirement information includes component requirement information and target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; according to the correspondence between the product specifications and the actual components, the target components corresponding to the target product specification information are determined; based on the target components corresponding to all the target product specification information in the project specification requirement information, a project component list is generated. It can be seen that by pre-constructing the product specification pool for each component according to the component specification values, when a project component list needs to be generated, the project party can directly select the required target product specifications from the product specification pool to generate project specification requirement information, and then combined with the pre-constructed correspondence between the product specifications and the actual components, the system can directly determine the target components that meet the target product specifications, so as to automatically generate a project component list based on the information of the target components, without manual execution of material confirmation for the components, improving the accuracy and efficiency of project component list management.

[0028] Based on the above embodiment, before determining the target components corresponding to the target product specification information according to the correspondence between the product specifications and the actual components, it further includes: obtaining the mapping relationship between the component specifications and attributes; the mapping relationship between the component specifications and attributes is pre-constructed according to the correspondence between the component specifications and the component attributes; by querying the mapping relationship between the component specifications and attributes, the correspondence between the product specifications and the actual components is determined.

[0029] It can be understood that both product specifications and component attributes are essentially used to describe the same content, but some parameters may have different forms of expression. The parameters in the product specifications are usually the common terms used by people, but the specific components cannot be determined based on the product specifications, and the components must be located according to the attribute values of the components. Therefore, it is necessary to establish the mapping relationship between the component specifications and attributes.

[0030] For example, as shown in Table 5 below: Table 5 Mapping Relationship Table of Component Specifications and Attributes Table 5 shows a specific mapping relationship between specifications and attributes. It can be seen that the target product specification information of the hard disk contains the information of "SAS hard disk", which means that the hard disk uses the SAS (Serial Attached SCSI) high-speed serial interface; however, in the actual attributes of the hard disk, this attribute is expressed as "hard disk interface type", and the corresponding component attribute value is "SAS_HDD". Therefore, it is necessary to establish the mapping relationship between the specifications and attributes of the component, so that the component attribute value corresponding to the target product specification information can be determined according to this mapping relationship, and then the target component can be determined according to the component attribute value. Through the mapping relationship between specifications and attributes, the product specification information can be corresponded to the component attributes, realizing the automatic matching of the target product specification information and the product specification pool, reducing manual participation, and improving the efficiency and accuracy of matching.

[0031] Furthermore, regarding the impact of component changes on inventory management, by obtaining the component change information and updating the corresponding mapping relationship between specifications and attributes according to the component change information, the determination process of the target component is not affected.

[0032] Based on the above embodiments, after determining the target component corresponding to the target product specification information, it may further include: generating a confirmation request based on the target product specification information and the component attribute value of the target component; displaying the confirmation request through an interactive interface and receiving the review result for the confirmation request. That is, the component requirement information, the target product specification information, and the component attribute value of the matched target component in the project specification requirement information are all displayed through the human-computer interaction interface, so that the component person in charge can conduct a re-review.

[0033] Create product specifications based on the attributes of the component, decoupling the product specifications from the project; after matching the target product specification information with the product specification pool, the target product specification information and the attribute information of the target component will be given to the corresponding component person in charge, and the component person in charge will perform component confirmation operations based on their understanding of the component.

[0034] For example, as shown in Table 6 below: Table 6 Confirmation Request Table Table 6 is a specific display table. In the table, "24T, 3.5, SATA" is a product specification in the target product specification information, and "24T, 7200, 3.5, SATA, Manufacturer 1" is the attribute value of the matched target component. That is to say, after the system automatically matches the target component, it will initiate a component confirmation task to the component responsible person, and re-confirm whether the component matching is accurate through manual review. It should be noted that even though manual review is required in this way, the efficiency of generating the overall project component list is still much higher than that of manually performing component confirmation in the related art, because at this time, the component responsible person only needs to verify whether the target product specification information in the display interface is consistent with the attribute value of the target component, and there is no high requirement for the component responsible person's familiarity with the component.

[0035] Further, after receiving the review result for the confirmation request, it further includes: if the review result contains the component attribute value of the new target component, then replace the target component with the new target component. If the matching is incorrect, it supports manual correction, that is, the component responsible person can feedback the correct component attribute value of the new target component, and the system will automatically replace the target component with the new target component, and then a project component list will be constructed according to the new target component subsequently.

[0036] Further, displaying the confirmation request through an interactive interface includes: sending the confirmation request to the person in charge in the list of component responsible persons according to the type of the target component and the list of component responsible persons corresponding to the type of the target component, so that the corresponding component responsible person can perform manual review. That is, usually, the corresponding component responsible person will be assigned according to the component type, and not one person in charge manages all components. Therefore, sending the confirmation request targeted can further improve the efficiency and accuracy of the review on the basis of the need for manual review. It can be sent to one person in charge in the list, or it can be sent to multiple persons in charge in the list. By sending it to multiple persons in charge, the manual review result can be obtained faster, further accelerating the review efficiency. Of course, after receiving the first reply, a stop review notice can be sent to other persons in charge, or the final review result can be synthesized according to the review results of multiple persons in charge.

[0037] Based on the above embodiments, the project component list management method further includes: obtaining component change information, determining the changed components according to the component change information; screening out the target project component list containing the changed components, and sending a component change reminder to the project leader corresponding to the target project component list. That is to say, when new components are introduced or existing components are changed, it is reminded that there are updates to the components in all projects where the corresponding components are located, and the overall integrated collection and update process from product specifications to component confirmation to project component list is realized, greatly improving work efficiency.

[0038] As Figure 3 shown, the project component list management includes a collection and update process. Components themselves are constantly changing in real time, and the changes in components may lead to additions, deletions, or attribute modifications of materials in the project component list. Some changes may directly determine whether the components can continue to be used. The update of the project component list is to collect update information regularly with a relatively large time interval. If these changes cannot be timely fed back to the corresponding projects, it will lead to the projects being unable to make correct judgments and operations in a timely manner, thus causing a large amount of ineffective work.

[0039] By synchronizing relevant changes to all projects where the corresponding components are located in real time when adding materials, deleting materials, or updating the attributes of the materials therein, duplicate work is reduced, and the component change information in the project list is obtained in real time, improving the accuracy and timeliness of the project component list, thereby greatly improving work efficiency.

[0040] Furthermore, when new components are introduced or existing components are changed, the person in charge of the corresponding components can be automatically reminded to re-confirm the corresponding product specifications. Based on the reminder content, the person in charge of the components re-confirms the component information under the product specifications. For example, originally the component met a certain product specification, but after the component was changed, it no longer meets the product specification; after the confirmation is completed, all projects where the corresponding components are located are reminded to update the components. That is, after the component is changed, the system automatically compares whether there are changes in the attributes of the component. If there are changes, the system will automatically trigger a task to the person in charge of the component to confirm the component information under the corresponding product specifications of the component. After the confirmation is completed, the system automatically triggers a reminder message to the project leader using the product specification, reminding the project to make corresponding changes. Without affecting the change, only by modifying the change reminder logic, the timely reminder of the component change to the using project is realized, improving the accuracy and timeliness, and quickly realizing the change of the component project list.

[0041] After automatically synchronizing the change information to the component responsible person and project responsible person under the corresponding product specification after the component change, it reminds that there is a change in the component. The component responsible person and project responsible person confirm whether the materials under the product specification are retained based on the change content. By adding these functions, the unified maintenance of product specifications is realized, the product specification information is standardized, the product specifications are made more accurate, and the component information under the product specification is automatically matched and confirmed to be separated from the project based on the matching rules. Only for the product specification, the accuracy of component information matching is increased and a large number of repeated confirmation tasks are reduced. It can also synchronize the material change in real time to the projects using the product specification, ensuring the timeliness of information transmission, enabling better operation of subsequent processes, and reducing useless work. Through the management of the entire process, the informatization control of the project component list is realized, which is convenient, fast, and not prone to errors.

[0042] Thus, not only the informatization collection and management of the project component list are realized. Through the optimization of component change and status maintenance, it also ensures the timely transmission of component information changes to the project, which can effectively control the component project list and ensure the problem of using the project component list caused by time differences, improving work efficiency and ensuring data accuracy.

[0043] Correspondingly, the embodiment of the present application also discloses a project component list management device, which includes: An information acquisition module, configured to acquire project specification requirement information; the project specification requirement information includes component requirement information and the target product specification information of the required component; the target product specification information is selected from the product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; A target component determination module, configured to determine the target component corresponding to the target product specification information according to the correspondence between the product specification and the actual component; A list generation module, configured to generate a project component list based on the target components corresponding to all the target product specification information in the project specification requirement information.

[0044] As can be seen above, in this embodiment, project specification requirement information is obtained; the project specification requirement information includes component requirement information and target product specification information of the required components; the target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; according to the correspondence between the product specifications and the actual components, the target components corresponding to the target product specification information are determined; based on the target components corresponding to all the target product specification information in the project specification requirement information, a project component list is generated. It can be seen that by pre-constructing the product specification pool of each component according to the component specification values of the components, when a project component list needs to be generated, the project party directly selects the required target product specifications from the product specification pool to generate project specification requirement information, and then combines the pre-constructed correspondence between the product specifications and the actual components, and the system can directly determine the target components that meet the target product specifications, so as to automatically generate a project component list based on the information of the target components, without manual material confirmation of the components, improving the accuracy and efficiency of project component list management.

[0045] In some specific embodiments, the construction process of the product specification pool includes: According to the correspondence between the components and the component specifications, and the correspondence between the component specifications and the specification values, different product specifications corresponding to the components are determined; Based on all the product specifications corresponding to the components of the same type, the product specification pool of this type of component is obtained.

[0046] In some specific embodiments, the matching module may specifically include: A mapping relationship acquisition unit for acquiring the mapping relationship between the specifications and attributes of the required components; the mapping relationship between the specifications and attributes is pre-constructed according to the correspondence between the component specifications and the component attributes; A conversion unit for determining the correspondence between the product specifications and the actual components by querying the mapping relationship between the specifications and attributes.

[0047] In some specific embodiments, the project component list management device may specifically include: An update unit for acquiring component change information and updating the mapping relationship between the specifications and attributes according to the component change information.

[0048] In some specific embodiments, the project component list management device may specifically include: A request generation unit for generating a confirmation request based on the target product specification information and the component attribute values of the target components after determining the target components corresponding to the target product specification information; A display unit for displaying the confirmation request through an interactive interface and receiving the review result for the confirmation request.

[0049] In some specific embodiments, the item component list management device may specifically include: A replacement unit, configured to replace the target component with the new target component if the review result received for the confirmation request contains the component attribute value of the new target component.

[0050] In some specific embodiments, the item component list management device may specifically include: A changed component confirmation unit, configured to obtain component change information and determine the changed component according to the component change information; A reminder unit, configured to filter out the target item component list containing the changed component and send a component change reminder to the project leader corresponding to the target item component list.

[0051] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation manner.

[0052] An embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above embodiments of the item component list management method.

[0053] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps in any one of the above embodiments of the item component list management method when running.

[0054] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: USB flash drive, read-only memory (ROM for short), random access memory (RAM for short), mobile hard disk, magnetic disk or optical disc, etc., various media that can store computer programs.

[0055] An embodiment of the present application further provides a computer program product. The above computer program product includes a computer program, and the computer program implements the steps in any one of the above embodiments of the item component list management method when executed by a processor.

[0056] Embodiments of the present application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps in any of the above embodiments of the item component list management method.

[0057] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0058] It should be noted that in the description of the present application, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in the present application are used to distinguish similar objects and not to describe a specific order or sequence.

[0059] The above has introduced in detail a method for managing an item component list provided by the present application. Specific examples are used herein to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. It should be pointed out that for those of ordinary skill in the art of the present technology, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the present application.

Claims

1. A method for managing a project component list, characterized in that, Including: Obtain project specification requirement information; The project specification requirement information includes component requirement information and target product specification information of the required components; The target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; According to the correspondence between the product specification and the actual component, determine the target component corresponding to the target product specification information; Based on the target components corresponding to all the target product specification information in the project specification requirement information, generate a project component list.

2. The item part list management method according to claim 1, characterized in that, The construction process of the product specification pool includes: According to the correspondence between the component and the component specification, and the correspondence between the component specification and the specification value, determine the different product specifications corresponding to the component; Based on all the product specifications corresponding to the components of the same type, obtain the product specification pool of this type of component.

3. The project component list management method according to claim 1, wherein Before determining the target component corresponding to the target product specification information according to the correspondence between the product specification and the actual component, it also includes: Obtain the mapping relationship between the component specification and the attribute; the mapping relationship between the specification and the attribute is pre-constructed according to the correspondence between the component specification and the component attribute; By querying the mapping relationship between the specification and the attribute, determine the correspondence between the product specification and the actual component.

4. The item component list management method according to claim 3, characterized in that It also includes: Obtain component change information, and update the mapping relationship between the specification and the attribute according to the component change information.

5. The method for managing the item part list according to claim 1, wherein After determining the target component corresponding to the target product specification information, it also includes: Based on the target product specification information and the component attribute value of the target component, generate a confirmation request; Display the confirmation request through an interactive interface and receive the review result for the confirmation request.

6. The project component list management method according to claim 5, wherein After receiving the review result for the confirmation request, it also includes: If the review result includes the component attribute value of the new target component, replace the target component with the new target component.

7. The item parts list management method according to any one of claims 1 to 6, characterized in that It also includes: Obtain component change information, and determine the changed component according to the component change information; Screen out the target project component list including the changed component, and send a component change reminder to the project leader corresponding to the target project component list.

8. A project component list management device, characterized in that, Including: An information acquisition module for obtaining project specification requirement information; The project specification requirement information includes component requirement information and target product specification information of the required components; The target product specification information is selected from a product specification pool; the product specification pool is pre-constructed based on the product specifications of different model components; A target component determination module for determining the target component corresponding to the target product specification information according to the correspondence between the product specification and the actual component; A list generation module for generating a project component list based on the target components corresponding to all the target product specification information in the project specification requirement information.

9. An electronic device, characterized in that, Including: A memory for storing a computer program; A processor for executing the computer program to implement the project component list management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, For storing a computer program; wherein when the computer program is executed by the processor, it implements the project component list management method according to any one of claims 1 to 7.

Images