Part information management method, system and equipment and computer readable storage medium

Abstract

A part information management method, system and device and a computer readable storage medium relate to the technical field of vehicle data management, and comprise the steps of managing all part change data based on a change theme to generate a target change database, the part change data controlled by each control item in the target change database has the same change theme; when a target classification statistics instruction is received, classification statistics is carried out on the part setting change data in the target setting change database according to the target classification statistics instruction to generate a target statistics result, the target classification statistics instruction comprises a first instruction, and the first instruction comprises a second instruction; the first instruction comprises at least one of a transformation setting issuing department, a transformation setting reason and a transformation setting implementation stage. According to the application, automatic management of information such as setting and changing of the parts can be efficiently and accurately realized.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle data management, and in particular to a component information management method, system, device and computer-readable storage medium. Background Art

[0002] Auto parts are the basic data for the smooth operation of multiple links such as procurement, process, production, and finance. Among them, parts are not only of various types and complex properties, but also change frequently during the life cycle of the whole vehicle product, resulting in very large and scattered design change data. It can be seen that if the information of a large number of parts design changes is managed manually, it will be complicated, error-prone, and require a lot of manpower. Therefore, how to efficiently and accurately manage the information of parts design changes is an urgent problem to be solved. Summary of the invention

[0003] The present application provides a component information management method, system, device and computer-readable storage medium, which can efficiently and accurately realize automatic management of component design change and other information.

[0004] In a first aspect, an embodiment of the present application provides a component information management method, the component information management method comprising:

[0005] All component design change data are managed based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme;

[0006] When a target classification and statistics instruction is received, the component design change data in the target design change database is classified and counted according to the target classification and statistics instruction to generate a target statistical result. The target classification and statistics instruction includes a first instruction, and the first instruction includes at least one of a design change issuing department, a design change reason, and a design change implementation stage.

[0007] In combination with the first aspect, in one implementation, managing all component design change data based on the change theme to generate a target design change database includes:

[0008] Set a control item for each change topic;

[0009] Add component design change data with the same change theme to the corresponding control item to generate a target design change database.

[0010] In combination with the first aspect, in one implementation, classifying and counting the component design change data in the target design change database according to the target classification and statistics instruction to generate a target statistical result includes:

[0011] When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result;

[0012] When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result;

[0013] When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

[0014] In combination with the first aspect, in one implementation, the target classification statistics instruction further includes a second instruction, the second instruction includes a vehicle type, an engine type, and a new energy power model, and the component design change data in the target design change database is classified and counted according to the target classification statistics instruction to generate a target statistical result, including:

[0015] Classify and count the component design change data in the target design change database according to the second instruction to obtain target statistical data;

[0016] The target statistical data are classified and counted based on the first instruction to generate a target statistical result.

[0017] In a second aspect, an embodiment of the present application provides a parts information management system, the parts information management system comprising:

[0018] A first management module, which is used to manage all component design change data based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme;

[0019] The second management module is used to classify and count the component design change data in the target design change database according to the target classification statistics instruction when receiving the target classification statistics instruction to generate a target statistical result. The target classification statistics instruction includes a first instruction, and the first instruction includes at least one of the design change issuing department, the design change reason and the design change implementation stage.

[0020] In conjunction with the second aspect, in one implementation, the first management module is specifically configured to:

[0021] Set a control item for each change topic;

[0022] Add component design change data with the same change theme to the corresponding control item to generate a target design change database.

[0023] In conjunction with the second aspect, in one implementation, the second management module is specifically configured to:

[0024] When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result;

[0025] When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result;

[0026] When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

[0027] In conjunction with the second aspect, in one implementation, the target classification statistics instruction further includes a second instruction, the second instruction includes a vehicle type, an engine type, and a new energy power model, and the second management module is specifically further used to:

[0028] Classify and count the component design change data in the target design change database according to the second instruction to obtain target statistical data;

[0029] The target statistical data are classified and counted based on the first instruction to generate a target statistical result.

[0030] In a third aspect, an embodiment of the present application provides a parts information management device, which includes a processor, a memory, and a parts information management program stored in the memory and executable by the processor, wherein when the parts information management program is executed by the processor, the steps of the parts information management method as described above are implemented.

[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a parts information management program is stored, wherein when the parts information management program is executed by a processor, the steps of the parts information management method as described above are implemented.

[0032] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0033] All component design change data are automatically processed through change themes, so that the component design change data controlled by each control item in the generated target design change database have the same change theme, so as to realize the centralized management of design change data and avoid data omissions; at the same time, when receiving the target classification and statistical instructions, the component design change data in the target design change database are classified and counted according to the target classification and statistical instructions such as the design change issuing department, the design change reason and the design change implementation stage, so as to generate the target statistical results, thereby realizing efficient and accurate automatic management of component design change information, so as to more clearly display the design changes of parts from different angles based on the target statistical results. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 This is a flow chart of an embodiment of the parts information management method of the present application;

[0035] Figure 2 For this application Figure 1 A detailed flow chart of step S10;

[0036] Figure 3 This is a detailed schematic diagram of the control items involved in the embodiment of this application;

[0037] Figure 4 For this application Figure 1 Detailed flow chart of step S20;

[0038] Figure 5 This is a schematic diagram of the hardware structure of the component information management device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0040] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0041] In a first aspect, an embodiment of the present application provides a method for managing parts information.

[0042] In one embodiment, referring to Figure 1, Figure 1 This is a flow chart of an embodiment of the method for managing parts information of this application. Figure 1 As shown, the parts information management method includes:

[0043] Step S10: managing all component design change data based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme.

[0044] For example, it should be understood that a vehicle has about 4,500 parts, involving more than 2,000 categories including assemblies, assemblies, controllers, software, standard parts, etc., and each part contains more than a dozen attributes such as part version, identification code, change mark, color identification, drawing number, drawing mark, maturity, whether to use, security code, whether HW, whether CAN assembly part, English abbreviation, etc.; it can be seen that automotive parts are not only numerous and diverse, but also have complex attribute information; in addition, parts are changed very frequently. For example, in the entire product life cycle, only about 700 parts have no design change records, while 3,800 parts will undergo design changes, and the maximum change can reach more than 10 times. Therefore, it is very important to efficiently and accurately realize the automatic management of information such as part design changes.

[0045] In this embodiment, the management of design change data will be achieved by changing the theme, that is, the design change data of parts with the same change theme will be included in the same control item to generate a target design change database. For example, taking the S59 model as an example, all design change data need to be included in the S59 project, and the design change data with the same change theme need to be included in one control item. Assuming that there is a problem of ceiling detachment, the sunroof sunshade assembly and the top cover interior panel assembly need to be coordinated and changed, and then the sunroof sunshade assembly design change data and the top cover interior panel assembly design change data are generated; it should be understood that the sunroof sunshade assembly design change data and the top cover interior panel assembly design change data are both generated to solve the problem of ceiling detachment, so the sunroof sunshade assembly design change data and the top cover interior panel assembly design change data have the same design change theme: "Solve the problem of ceiling detachment"; so these two design change data are included in the same control item. It can be seen that all component design change data belonging to the same control item in the target design change database are generated due to the same change theme, so as to realize the centralized processing of design change data, thereby avoiding the scattered distribution of design change data with the same change theme in different control items, which can effectively improve the control accuracy of design change data and reduce the possibility of errors.

[0046] Further, see Figure 2 As shown, the management of all component design change data based on the change theme to generate a target design change database includes:

[0047] Step S101: setting a control item for each change subject;

[0048] Step S102: adding component design change data with the same change theme to the corresponding same control item to generate a target design change database.

[0049] Exemplarily, in this embodiment, a control item will be set for each change subject, that is, the design change data controlled under a control item are all generated by the same change subject; at the same time, a unique control item number will be set for each control item, that is, a control item number corresponding to each change subject, and the design change data of components with the same change subject will be added to the corresponding same control item. After all the design change data are added, the target design change database can be generated.

[0050] For example, see Figure 3 As shown, the control item number corresponding to the design change theme "Solve the problem of ceiling detachment" under the S59 model is set to S59_1075, and the sunroof sunshade assembly design change data and top cover interior panel assembly design change data generated based on the design change theme "Solve the problem of ceiling detachment" are stored in the S59_1075 control item; assuming that the product notification number corresponding to the sunroof sunshade assembly design change data is S0043838 and the product notification number corresponding to the top cover interior panel assembly design change data is S0043302, then the product notification number S0043838 and the product notification number S0043302 are stored in the S59_1075 control item. At the same time, different control detail numbers will be set for different design change data under the same control, so that the corresponding design change data can be queried through the control item number and the control detail number; for example, see Figure 3 As shown, for the design change data corresponding to the sunroof sunshade assembly numbered K700175566, an S59_1075_07 is set as its control detail number in the S59_1075 control item, and the design change data corresponding to the sunroof sunshade assembly numbered K700175566 is found through S59_1075 and S59_1075_07.

[0051] Step S20: When a target classification and statistics instruction is received, the component design change data in the target design change database is classified and counted according to the target classification and statistics instruction to generate a target statistical result, wherein the target classification and statistics instruction includes a first instruction, and the first instruction includes at least one of a design change issuing department, a design change reason, and a design change implementation stage.

[0052] For example, in this embodiment, the design change data will be classified and statistically managed to more clearly display the design changes of parts from different angles. It should be noted that the classification criteria include but are not limited to the design change issuing department, the design change reason and the design change implementation stage, where the design change issuing department refers to the department or center that generates the design change data, the design change reason refers to the reason why the design change data is generated, and the design change implementation stage refers to the stage at which the design change data needs to be implemented, that is, at which stage the design change data needs to be implemented.

[0053] It can be understood that the target classification statistics instruction can be generated according to the actual design change standard, wherein the target classification statistics instruction can include one classification standard or multiple classification standards at the same time, which is not limited here; for example, the user needs to classify and count the design change data based on the classification standard of the design change issuing department, and the target classification statistics instruction is generated according to the design change issuing department, that is, the first instruction in the target classification statistics instruction is the design change issuing department; for another example, the user needs to classify and count the design change data based on both the classification standards of the design change issuing department and the design change reason, and the target classification statistics instruction will be generated according to the design change issuing department and the design change reason, that is, the first instruction in the target classification statistics instruction is the design change issuing department and the design change reason.

[0054] Therefore, when receiving the target classification statistics instruction, this embodiment will classify and count the component design change data in the target design change database according to the classification standard corresponding to the target classification statistics instruction, and then generate the target statistical results, thereby realizing efficient and accurate automatic management of component design change information, so as to be able to more clearly display the design changes of parts from different angles.

[0055] Furthermore, in one embodiment, the classifying and counting the component design variation data in the target design variation database according to the target classification and statistics instruction to generate a target statistical result includes:

[0056] When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result;

[0057] When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result;

[0058] When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

[0059] By way of example, it should be understood that the design change issuing department, design change reason and design change implementation stage corresponding to the design change data will be described in the corresponding fields in the corresponding product definition and change notification; for example, the design change issuing department corresponding to a certain design change data A is B, the design change reason is C and the design change implementation stage is D, then the design change issuing department field in the product definition and change notification corresponding to the design change data A will be filled with B, the design change reason field will be filled with C and the design change implementation stage field will be filled with D.

[0060] Therefore, if the design change standard only selects the design change issuing department, the target design change issuing department of each component design change data can be determined based on the product definition and the design change issuing department field in the change notice, and the component design change data with the same design change issuing department can be used as a statistical item, that is, the component design change data with the same target design change issuing department are classified and counted to generate the target statistical result; if the design change standard only selects the design change reason, the target design change reason of each component design change data can be determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same design change reason can be used as a statistical item, that is, the component design change data with the same target design change reason are classified and counted to generate the target statistical result; if the design change standard only selects the design change implementation stage, the target design change implementation stage of each component design change data can be determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same design change implementation stage can be used as a statistical item, that is, the component design change data with the same target design change implementation stage are classified and counted to generate the target statistical result.

[0061] It should be understood that if more than one design change standard is selected, classification statistics can be performed based on one of the design change standards and in accordance with the classification statistics method of the above-mentioned single classification standard to obtain classification statistics results; and then the classification statistics results can be classified and counted again based on the next design change standard until the target statistical results are generated.

[0062] Furthermore, in one embodiment, the target classification statistics instruction further includes a second instruction, and the second instruction includes a vehicle model, an engine model, and a new energy power model, see Figure 4 As shown, the classification and statistics of the component design change data in the target design change database are performed according to the target classification and statistics instruction to generate a target statistical result, including:

[0063] Step S201: classifying and counting the component design change data in the target design change database according to the second instruction to obtain target statistical data;

[0064] Step S202: Classify and count the target statistical data based on the first instruction to generate a target statistical result.

[0065] For example, it is understandable that the management of all parts and components design change data is often achieved through vehicle models. However, current car companies not only sell complete vehicles, but also sell engines, new energy power modules and other non-complete vehicles. That is, some engines or new energy power modules do not exist in the form of complete vehicles, so that the engine or new energy power module cannot be found through the vehicle model. In other words, the management of the design change data of the above-mentioned engine or new energy power module cannot be achieved through the vehicle model. Therefore, in order to achieve comprehensive management of design change data, this embodiment will manage the engine and new energy power module separately to avoid the problem of missing management of engine or new energy power module design change data.

[0066] Specifically, the model of the whole vehicle, the model (i.e., the engine model) and the new energy power model can also be used as classification standards to generate the second instruction; therefore, firstly, the component design change data in the target design change database is classified and counted for the first time according to the classification standard corresponding to the second instruction, that is, the other vehicle component design change data that does not include the engine and the new energy power module are classified and counted according to the model to obtain the first statistical data, and all engine design change data are classified and counted according to the model to obtain the second statistical data, and at the same time, all new energy power module design change data are classified and counted according to the new energy power model to obtain the third statistical data, then the first statistical data, the second statistical data and the third statistical data constitute the target statistical data; then, the first statistical data, the second statistical data and the third statistical data in the target statistical data are classified and counted for the second time according to the first instruction, so as to generate the target statistical result.

[0067] In addition, this embodiment will also provide product data query of parts and manufacturing data query combined with actual downstream production to achieve more comprehensive and complete part information management; specifically, it can include more than 20 kinds of attribute information such as part maturity, version, identification code, key parts, part drawing information, color identification, function group number, etc. through part name or number query, and can intuitively display part attribute information, version change information, vehicle model information, subordinate child information, factory information, production status information, etc.; this embodiment also supports parent and child information query of parts, that is, it can obtain each level of information of parts by traversing layer by layer to obtain the vehicle model of the part and its subordinate parts list; at the same time, it supports the query of all change histories of parts to manage the entire product life cycle of parts; and for the complex and precise production of vehicle manufacturers, all plans should be formalized, so this embodiment will be officially effective after layers of approval and review, and the solidified part plan and information will be provided to downstream for analysis and application and production guidance.

[0068] The above query management can be realized through the product data management module and the manufacturing data management module. The product data management module includes the product data query module, the part attribute information management module, the part change management module and the product data calculation module, while the manufacturing data management module includes the manufacturing data query module, the change management module and the manufacturing data calculation module. It should be noted that the main difference between the manufacturing data management module and the product data management module is that the manufacturing data management module adds the management of the production plant, the use workshop and the use time.

[0069] It should be understood that the product data query module supports fuzzy query and precise query of product data, wherein fuzzy query refers to querying by part name or number to retrieve information of all matching fields, while precise query refers to accurately matching and retrieving part information by entering part code; the part attribute information management module is used to manage more than 20 kinds of part attribute information including part identification code, color identification, security code, whether it is a continued part, external project number, security code, software type, whether it is a CAN assembly part, electrical OEM version, associated ECU part number, weight, etc., which will be updated as the part changes and is strongly related to the part version. Part change management includes a part retrieval module and a part version information management module, wherein the part information that meets the target value can be retrieved through the part retrieval module, and the part version information management module can obtain the historical change history of the part (such as historical file information, specific change content, etc.), and at the same time has the ability to query the drawing information and part digital model and lightweight data information under different versions of the part, and for software parts, it supports the query of supporting documents of the part.

[0070] The product data calculation module can not only select basic models, neutral models, instantiated models, etc. according to needs, but also perform expansion regression calculations according to data at different time points and different levels, where the data at different time points are obtained by matching the vehicle BOM (Bill of Materials) and the data of the parts at the current time. For example, as shown in Table 1, when performing regression calculations on part A, assuming that the effective time on the instantiated model A is 20240305, the intersection of the model, part, block, and block configuration expression effective time is selected; for another example, when expanding assembly A, if the time is selected as 20240101, assembly A has no sub-parts. Only when the time is greater than or equal to 20240201 and assembly A is expanded, it has sub-parts, that is, the sub-part is part B.

[0071] Table 1 First data timetable

[0072]

[0073]

[0074] The manufacturing data query module also supports fuzzy query and precise query; among them, fuzzy query refers to querying by part name or number to retrieve information of all matching fields; precise query is to accurately match and retrieve part information by entering the part code. For example, if a part has multiple locations and workshops of use, all information will be displayed for users to locate and select data according to their needs. At this time, the data queried is the data that has been matched with time on the manufacturing side, which includes past time and future time.

[0075] The change management module is used to manage all design change data. This module changes the offline manual management of design changes to online automatic management to collect information from various links such as procurement, quality, process, manufacturing management, etc., and synchronize the management and control information in real time, which greatly improves the management efficiency, ensures the completeness and accuracy of information in each link, and realizes the visual monitoring of management and control information. Design changes can be managed according to vehicle model, machine model, and new energy power model, and automatically counted and classified according to the design change issuing department, design change reason and implementation stage. Among them, as shown in Table 2, the change management module is also used to realize the management of three control points including parts preparation, trial production and commissioning, and each control point information may include two parts, plan and actual, according to the actual situation; it should be noted that the parts preparation information and the time of issuing the trial assembly task book and the time of providing the tooling parts are filled in by the data engineer. After the tooling parts provision time is filled in, the subsequent control point plan time will be automatically calculated according to the working hours set in advance; the actual time of P11-T6 needs to be filled in by the parts, process, procurement, and production management departments according to the actual time. After filling in, the subsequent control information will be collected. After the information collection is initiated, the system will trigger an email to the information control personnel of each node; the filling of control points can also be monitored, which can intuitively reflect the completed control points and specific information.

[0076] Table 2 Control point information

[0077]

[0078]

[0079] The manufacturing data calculation module can not only select basic models, neutral models, instantiated models, etc. according to needs, but also perform regression calculations based on data at different time points, different levels, different production centers, and different assembly workshops; among them, data at different time points are calculated by matching the data of the vehicle BOM and parts at the current time. It should be noted that the difference between manufacturing data expansion and regression and product data expansion and regression is that the use location and time management point of the manufacturing end are added, while product data expansion and regression do not perform time control and will be calculated based on the latest detailed data.

[0080] For example, for part B300048160, it is used in both Factory 1 and Factory 2 in City F, and the vehicle model used in Factory 1 is the C68 model, and the vehicle model used in Factory 2 is the S59 model. When performing regression calculations, if Factory 1 is selected as the production center, the calculated data is the usage of the part in Factory 1, that is, the vehicle model results are calculated based on the details of Factory 1, and regression calculations can be performed according to data at different times; if Factory 2 is selected, the settled data is the usage of the part in Factory 2, that is, the vehicle model results are calculated based on the details of Factory 2; if you want to query the data of the past week, you can select a time point during regression, and the BOM module will calculate the vehicle data one week ago.

[0081] As shown in Table 3, assuming that the effective time of part A in instantiated vehicle model A is 20240625, when the regression time is selected as 20240525, since part A is in a free state at the manufacturing end and is not used by any vehicle model, the time intersection of each level is selected for calculation; if assembly A is expanded at the time point of 20240525, assembly A has no sub-component structure, but if the selected time is greater than or equal to 20240530, the expanded sub-components of assembly A are part A and part B.

[0082] Table 3 Second data timetable

[0083] Tiers name Product data release time Effective time at the manufacturing end 1 Base Model A 20231201 20231201 2 Instantiate the neutral model A 20231201 20231201 3 Instantiate Model A 20231201 20231201 4 Block A configuration expression 20240305 20240625 4 Block A 20240301 20240530 5 Assembly A 20240201 20240530 6 Part B 20240201 20240525 6 Part A 20240201 20240525

[0084] In summary, this embodiment can manage parts systematically based on the characteristics of a wide variety of parts and complex attribute information, and all parts and key attribute information are defined by templates, which improves information accuracy and completeness; due to the complex structure of parts, the design scheme can only be solidified after multiple rounds of scheme confirmation and integration, and multiple changes will occur with design optimization, and this embodiment will record and manage all version change information and drawing information in the system, thereby achieving comprehensive information management and having the characteristics of tracking change history; it can be understood that parts are an important part of the structure of the entire vehicle and parts do not exist in isolation. This embodiment has the function of managing the parent and child of parts to establish the blood relationship of parts, which is convenient for analyzing and tracking the impact of changes; in addition, combined with production needs, this embodiment will control the use location and time of parts and manage information based on the different use locations and use times of parts, which can guide upstream product design and downstream production and manufacturing to accurately locate part information, thereby improving work efficiency.

[0085] In a second aspect, an embodiment of the present application also provides a parts information management system.

[0086] In one embodiment, the parts information management system includes:

[0087] A first management module, which is used to manage all component design change data based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme;

[0088] The second management module is used to classify and count the component design change data in the target design change database according to the target classification statistics instruction when receiving the target classification statistics instruction to generate a target statistical result. The target classification statistics instruction includes a first instruction, and the first instruction includes at least one of the design change issuing department, the design change reason and the design change implementation stage.

[0089] It should be noted that the first management module and the second management module can be integrated into the change management module in the manufacturing data management module to achieve comprehensive and automated management of design change data.

[0090] Furthermore, in one embodiment, the first management module is specifically used to:

[0091] Set a control item for each change topic;

[0092] Add component design change data with the same change theme to the corresponding control item to generate a target design change database.

[0093] Furthermore, in one embodiment, the second management module is specifically used to:

[0094] When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result;

[0095] When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result;

[0096] When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

[0097] Furthermore, in one embodiment, the target classification statistics instruction further includes a second instruction, the second instruction includes a vehicle type, an engine type, and a new energy power type, and the second management module is further specifically used for:

[0098] Classify and count the component design change data in the target design change database according to the second instruction to obtain target statistical data;

[0099] The target statistical data are classified and counted based on the first instruction to generate a target statistical result.

[0100] Among them, the functional implementation of each module in the above-mentioned parts information management system corresponds to the various steps in the above-mentioned parts information management method embodiment, and its functions and implementation processes will not be repeated here one by one.

[0101] In a third aspect, an embodiment of the present application provides a parts information management device, which may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0102] Reference Figure 5 , Figure 5 Schematic diagram of the hardware structure of the parts information management device involved in the embodiment of the present application. In the embodiment of the present application, the parts information management device may include a processor, a memory, a communication interface and a communication bus.

[0103] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0104] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the parts information management device, and the interface used to realize the interconnection between the parts information management device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0105] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0106] The processor may be a general-purpose processor, which may call the component information management program stored in the memory and execute the component information management method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the component information management program is called may refer to the various embodiments of the component information management method of the present application, which will not be described in detail here.

[0107] Those skilled in the art will understand that Figure 5 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0108] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0109] The readable storage medium of the present application stores a parts information management program, wherein when the parts information management program is executed by a processor, the steps of the parts information management method as described above are implemented.

[0110] Among them, the method implemented when the parts information management program is executed can refer to the various embodiments of the parts information management method of the present application, and will not be repeated here.

[0111] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0112] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0113] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0114] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0115] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0116] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0117] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A parts information management method, characterized in that: The parts information management method comprises: All component design change data are managed based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme; When a target classification and statistics instruction is received, the component design change data in the target design change database is classified and counted according to the target classification and statistics instruction to generate a target statistical result. The target classification and statistics instruction includes a first instruction, and the first instruction includes at least one of a design change issuing department, a design change reason, and a design change implementation stage.

2. The parts information management method according to claim 1, characterized in that: The management of all component design change data based on the change theme to generate a target design change database includes: Set a control item for each change topic; Add component design change data with the same change theme to the corresponding control item to generate a target design change database.

3. The parts information management method according to claim 1, characterized in that: The classifying and counting the component design change data in the target design change database according to the target classification and counting instruction to generate a target statistical result includes: When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result; When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result; When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

4. The parts information management method according to claim 1, characterized in that: The target classification statistics instruction also includes a second instruction, the second instruction includes a vehicle type, an engine type, and a new energy power type, and the component design change data in the target design change database are classified and counted according to the target classification statistics instruction to generate a target statistical result, including: Classify and count the component design change data in the target design change database according to the second instruction to obtain target statistical data; The target statistical data are classified and counted based on the first instruction to generate a target statistical result.

5. A parts information management system, characterized in that: The parts information management system comprises: A first management module, which is used to manage all component design change data based on the change theme to generate a target design change database, wherein the component design change data controlled by each control item in the target design change database has the same change theme; The second management module is used to classify and count the component design change data in the target design change database according to the target classification statistics instruction when receiving the target classification statistics instruction to generate a target statistical result. The target classification statistics instruction includes a first instruction, and the first instruction includes at least one of the design change issuing department, the design change reason and the design change implementation stage.

6. The parts information management system according to claim 5, characterized in that: The first management module is specifically used for: Set a control item for each change topic; Add component design change data with the same change theme to the corresponding control item to generate a target design change database.

7. The parts information management system according to claim 5, characterized in that: The second management module is specifically used for: When the first instruction is a design change issuing department, the target design change issuing department of each component design change data is determined based on the product definition and the design change issuing department field in the change notice, and the design change data of the components with the same target design change issuing department are counted to generate a target statistical result; When the first instruction is a design change reason, the target design change reason of each component design change data is determined based on the product definition and the design change reason field in the change notice, and the component design change data with the same target design change reason are counted to generate a target statistical result; When the first instruction is the design change implementation stage, the target design change implementation stage of each component design change data is determined based on the product definition and the design change implementation stage field in the change notice, and the component design change data with the same target design change implementation stage are counted respectively to generate a target statistical result.

8. The parts information management system according to claim 5, characterized in that: The target classification statistics instruction also includes a second instruction, the second instruction includes a vehicle type, an engine type and a new energy power type, and the second management module is specifically used to: Classify and count the component design change data in the target design change database according to the second instruction to obtain target statistical data; The target statistical data are classified and counted based on the first instruction to generate a target statistical result.

9. A parts information management device, characterized in that: The parts information management device includes a processor, a memory, and a parts information management program stored in the memory and executable by the processor, wherein when the parts information management program is executed by the processor, the steps of the parts information management method as described in any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a parts information management program, wherein when the parts information management program is executed by a processor, the steps of the parts information management method according to any one of claims 1 to 4 are implemented.

Images