Parts information management method, system, device and computer-readable storage medium

Abstract

A kind of component information management method, system, equipment and computer readable storage medium, involve whole vehicle data management technical field, including based on change subject to all components set data management, to generate target set database, the set data of each piece of control item in the target set database controlled component has the same change subject;When receiving target classification statistical instruction, according to the target classification statistical instruction, the set data of component in the target set database is classified and counted, to generate target statistical result, the target classification statistical instruction includes first instruction, and the first instruction includes at least one in set change issuing department, set change reason and set change implementation stage.By the present application, the automatic management of component set change information etc. can be efficiently and accurately realized.

Description

TECHNICAL FIELD

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

[0002] Automobile components are basic data for the smooth operation of multiple links such as procurement, process, production and finance; among them, components are not only various in types and complex in attributes, and their changes in the whole vehicle product life cycle are also very frequent, so that the change data is very large and scattered. It can be seen that if the change information of a large number of components is managed by relying on manual work, it will have the defects of being complex and tedious, easy to make mistakes and requiring a large amount of manpower. Therefore, how to efficiently and accurately automatically manage the change information of components is a problem that needs to be solved at present. SUMMARY

[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 change information.

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

[0005] All component change data is managed based on change topics to generate a target change database, and the component change data controlled by each control item in the target change database has the same change topic;

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

[0007] In combination with the first aspect, in an implementation mode, the management of all component change data based on change topics to generate a target change database comprises:

[0008] A control item is set for each change topic;

[0009] The component change data with the same change topic is added to the corresponding same control item to generate a target change database.

[0010] In combination with the first aspect, in an implementation mode, the classification and counting of the component change data in the target change database according to the target classification statistical instruction to generate a target statistical result comprises:

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

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

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

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

[0015] The part change data in the target change database is classified and counted according to the second instruction to obtain target statistical data;

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

[0017] In the second aspect, an embodiment of the present application provides a part information management system, and the part information management system includes:

[0018] A first management module is configured to manage all part change data based on a change theme to generate a target change database, and part change data managed by each piece of management item in the target change database has the same change theme;

[0019] A second management module is configured to, when a target classification statistical instruction is received, classify and count part change data in the target change database according to the target classification statistical instruction to generate a target statistical result, the target classification statistical instruction including a first instruction, and the first instruction including at least one of a change-issuing department, a change reason and a change implementation stage.

[0020] In combination with the second aspect, in an implementation manner, the first management module is specifically configured to:

[0021] setting a control item for each change subject;

[0022] adding the part data with the same change subject to the corresponding same control item to generate a target setting change database.

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

[0024] when the first instruction is a setting change issuing department, determining a target setting change issuing department of each part setting change data based on a setting change issuing department field in the product definition and the change notice, and respectively counting the part setting change data with the same target setting change issuing department to generate a target counting result;

[0025] when the first instruction is a setting change reason, determining a target setting change reason of each part setting change data based on a setting change reason field in the product definition and the change notice, and respectively counting the part setting change data with the same target setting change reason to generate a target counting result;

[0026] when the first instruction is a setting change implementation stage, determining a target setting change implementation stage of each part setting change data based on a setting change implementation stage field in the product definition and the change notice, and respectively counting the part setting change data with the same target setting change implementation stage to generate a target counting result.

[0027] In combination with the second aspect, in an implementation, the target classification counting instruction further includes a second instruction, the second instruction includes a vehicle type, a model and a new energy power type, and the second management module is specifically further configured to:

[0028] performing classification counting on the part setting change data in the target setting change database according to the second instruction to obtain target counting data;

[0029] performing classification counting on the target counting data based on the first instruction to generate a target counting result.

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

[0031] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a part information management program, wherein the part information management program, when executed by a processor, implements the steps of the part information management method as described above.

[0032] The technical scheme provided by the embodiment of the present application has the beneficial effects of:

[0033] By changing the subject of all parts of the change data to automatically process, the generated target change database has the same change subject for each part of the change data controlled by the control item, so as to realize centralized management of the change data and avoid data omission. At the same time, when receiving the target classification statistical instruction, the part change data in the target change database is classified and counted according to the change issuing department, change reason and change implementation stage, etc. to generate a target statistical result, and then the part change information is efficiently and accurately automatically managed, so that the design change of the part can be more clearly displayed from different angles based on the target statistical result. BRIEF DESCRIPTION OF DRAWINGS

[0034] Figure 1 The flowchart of the part information management method embodiment of the present application is shown in the figure.

[0035] Figure 2 The detailed flowchart of step S10 in the present application is shown in the figure. Figure 1

[0036] The detailed flowchart of step S20 in the present application is shown in the figure. Figure 3

[0037] The detailed flowchart of step S20 in the present application is shown in the figure. Figure 4 Figure 1 The hardware structure diagram of the part information management device involved in the embodiment of the present application is shown in the figure.

[0038] DETAILED DESCRIPTION Figure 5 In order to enable the personnel in the technical field to better understand the present application, the technical scheme in the present application will be described clearly and completely in the following with reference to the drawings in the embodiment of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the person skilled in the art without creative labor are within the scope of protection of the present application.

[0039] In order to make the purpose, technical scheme and advantages of the present application more clear, the present application will be further described in detail with reference to the drawings.

[0040] In order to make the purpose, technical scheme and advantages of the present application more clear, the present application will be further described in detail with reference to the drawings.

[0041] In the first aspect, the present application provides a part information management method.

[0042] In an embodiment, with reference to Figure 1 ​, Figure 1 The flowchart of the embodiment of the part information management method of the present application is shown in FIG. 1. As shown in FIG. 1, the part information management method comprises the following steps. Figure 1

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

[0044] For example, it should be understood that there are about 4500 parts in a whole vehicle, involving more than 2000 types including components, assemblies, controllers, software, standard parts, etc., and each part contains more than ten attributes such as part version, identification code, change mark, color identification, drawing number, drawing mark, maturity, whether to continue, security code, whether HW, whether CAN assembly part, English abbreviation, etc. It can be seen that the automobile parts are not only numerous in quantity and variety, but also complex in attribute information. In addition, the change of parts is very frequent. For example, in the whole product life cycle, only about 700 parts have no change record, and 3800 parts will be changed, and the highest change can reach more than 10 times. Therefore, it is very important to efficiently and accurately realize the automatic management of part change information and the like.

[0045] In this embodiment, the management of change data is realized by change topics, that is, the part change data with the same change topic is listed in the same control item to generate a target change database. For example, taking S59 vehicle as an example, all change data needs to be included in S59 project, and change data with the same change topic needs to be listed in a control item. Assuming that the roof comes off, the sunroof sunshade curtain assembly and the roof interior panel assembly need to be changed, and then the sunroof sunshade curtain assembly change data and the roof interior panel assembly change data are generated. It should be understood that the sunroof sunshade curtain assembly change data and the roof interior panel assembly change data are both generated because of solving the problem of the roof coming off, so the sunroof sunshade curtain assembly change data and the roof interior panel assembly change data have the same change topic: solving the problem of the roof coming off. Therefore, the two change data are included in the same control item. It can be seen that all part change data belonging to the same control item in the target change database is generated because of the same change topic, so as to realize the centralized processing of change data, thereby avoiding the scattered distribution of change data with the same change topic in different control items, which can effectively improve the control accuracy of change data and reduce the possibility of error.

[0046] Further, as shown in FIG. 1, the management of all part change data based on change topics to generate a target change database comprises the following steps. Figure 2

[0047] ​​Step S101: Set a control item for each change topic;

[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] For example, 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 roof 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 roof 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 statistics instruction is received, 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. The target classification 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] Exemplarily, in the embodiment, the change data is classified and statistically managed to more clearly show the design change of the parts from different angles. It should be noted that the classification criteria include but are not limited to the change issuing department, the change reason and the change implementation stage, wherein the change issuing department refers to the department or center that generates the change data, the change reason refers to the reason for generating the change data, and the change implementation stage refers to the stage in which the change data needs to be implemented, i.e., in which stage the change data needs to be implemented.

[0053] It can be understood that the target classification statistical instruction can be generated according to the actual change standard, wherein the target classification statistical instruction can include one classification criterion or multiple classification criteria, which are not limited herein; for example, the user needs to classify and statistically manage the change data based on the change issuing department, and then generates the target classification statistical instruction according to the change issuing department, i.e., the first instruction in the target classification statistical instruction is the change issuing department; for another example, the user needs to classify and statistically manage the change data based on the change issuing department and the change reason, and then generates the target classification statistical instruction according to the change issuing department and the change reason, i.e., the first instruction in the target classification statistical instruction is the change issuing department and the change reason.

[0054] Therefore, when the target classification statistical instruction is received, the embodiment classifies and statistically manages the part change data in the target change database according to the classification criterion corresponding to the target classification statistical instruction, and then generates the target statistical result, so as to realize efficient and accurate automatic management of the part change information, and to more clearly show the design change of the parts from different angles.

[0055] Further, in an embodiment, the classification and statistical management of the part change data in the target change database according to the target classification statistical instruction to generate the target statistical result comprises:

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

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

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

[0059] It is understood that, for the change issuing department, the change reason and the implementation phase of the change corresponding to the change data, the corresponding fields in the product definition and change notice corresponding thereto are described; for example, the change issuing department corresponding to a change data A is B, the change reason is C and the implementation phase of the change is D, the change issuing department field in the product definition and change notice corresponding to the change data A is filled with B, the change reason field is filled with C and the implementation phase of the change field is filled with D.

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

[0061] It is understood that, if more than one change standard is selected, the classification and counting can be performed based on one of the change standards and according to the classification and counting method of the single classification standard described above to obtain the classification and counting result; then the classification and counting result is classified and counted again based on the next change standard until the target statistical result is generated.

[0062] Further, in an embodiment, the target classification and counting instruction further includes a second instruction, which includes a vehicle model, a machine model and a new energy power model, as shown in Figure 4 The classification and counting of the part change data in the target change database according to the target classification and counting instruction to generate the target statistical result includes:

[0063] Step S201: According to the second instruction, the part change data in the target change database is classified and counted to obtain target statistical data;

[0064] Step S202: Based on the first instruction, the target statistical data is classified and counted to generate a target statistical result.

[0065] Exemplarily, it can be understood that at present, the management of all part change data is often realized through vehicle models. However, current vehicle enterprises 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 they cannot be found through vehicle models, in other words, the management of the change data of the above engines or new energy power modules cannot be realized through vehicle models. Therefore, in order to realize the comprehensive management of change data, the engine and the new energy power module are managed separately in the embodiment to avoid the problem of missing management of engine or new energy power module change data.

[0066] Specifically, the model of the complete vehicle, the engine model (i.e. the engine model) and the new energy power model can also be used as classification standards to generate a second instruction. Therefore, first, the part change data in the target change database is classified and counted according to the classification standard corresponding to the second instruction, that is, the change data of other complete vehicle parts not containing engines and new energy power modules is classified and counted according to the model to obtain first statistical data, all engine change data is classified and counted according to the engine model to obtain second statistical data, and all new energy power module change data is classified and counted according to the new energy power model to obtain third statistical data. 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 again according to the first instruction, that is, the target statistical result can be generated.

[0067] In addition, the embodiment also provides product data query of the part and manufacturing data query combined with actual downstream production, so as to realize more comprehensive and complete part information management; specifically, the part maturity, version, identification code, key part, part drawing information, color identification, function grouping number and more than 20 kinds of attribute information can be included by part name or number query, and the attribute information, version change information, vehicle model information, subordinate child information, factory information, production situation information and the like of the part can be intuitively displayed; the embodiment also supports part parent and child information query, that is, each level information of the part can be obtained by layer-by-layer traversal, so as to obtain the vehicle model using the part and the subordinate part list of the part; meanwhile, the query of all change histories of the part is supported, so as to manage the entire product life cycle of the part; and for complex and precise production of the vehicle manufacturer, all schemes should be formalized, therefore, the embodiment will be formally effective after layer-by-layer approval and check, and the solidified part scheme and information are provided to the downstream for analysis and application, guiding production.

[0068] The above query management can be realized by the product data management module and the manufacturing data management module, the product data management module includes a product data query module, a part attribute information management module, a part change management and a product data calculation module, and the manufacturing data management module includes a manufacturing data query module, a change management module and a 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 factory, the use workshop and the use time.

[0069] It should be understood that the product data query module supports fuzzy query and accurate query of product data, wherein the fuzzy query refers to query by part name or number to retrieve information of all matching fields, and the accurate query refers to accurate matching of part information by inputting part code; the part attribute information management module is used for managing more than 20 kinds of attribute information of the part including part identification code, color identification, security code, whether to follow the part, external item number, security code, software type, whether CAN assembly part, electrical appliance OEM version, associated ECU part number, weight and the like, which will be updated with the change of the part and is strongly related to the part version. The part change management includes a part retrieval module and a part version information management module, wherein the part retrieval module can retrieve part information meeting the target value after retrieval, and the part version information management module can obtain the historical change history of the part (such as including historical file information, specific change content and the like), and simultaneously has the functions of querying drawing information and part model, lightweight data information under different versions of the part, and supporting the query of supporting documents of software parts.

[0070] The product data calculation module can not only select base models and neutral models, instantiate models, etc. according to requirements, but also can perform regression calculation according to different time point data and different levels. The different time point data is obtained by matching the whole vehicle BOM (Bill of Materials) and the data of the parts at the current time for calculation. For example, referring to Table 1, when performing regression calculation on part A, it is assumed that the effective time on the instantiated model A is 20240305, then the intersection of the model, the part, the block, and the block configuration table expressing the effective time is selected; for another example, when expanding assembly A, if the time selected is 20240101, then assembly A has no subparts, only when the time is greater than or equal to 20240201, the expansion of assembly A has subparts, i.e. the subpart is part B.

[0071] Table 1 first data time table

[0072]

[0073]

[0074] The manufacturing data query module also supports fuzzy query and accurate query; wherein, the fuzzy query refers to query by part name or number to retrieve information of all matching fields; the accurate query is to accurately match the part information by inputting the part code, for example, if the part has multiple use places and use workshops, then all information will be displayed for the user to select data according to requirements, at this time, the data queried is the data that has been matched with the time at the manufacturing end, which contains past time and future time.

[0075] The change management module is used for managing all change data. This module changes manual management of changes to online automatic management to collect information of procurement, quality, process, manufacturing management and other links, and makes real-time synchronization update of management and control information, greatly improves management efficiency, ensures complete and accurate information of each link, and realizes visual monitoring of management and control information. Changes can be managed according to vehicle type, model, new energy power type, and automatically classified according to change issuing department, change reason and implementation stage. Referring to Table 2, the change management module is also used to realize management of three control points including part preparation, trial installation and commissioning, and production, and each control point information can include plan and actual contents according to actual situation. It should be noted that part preparation information, trial installation task sheet issuing time and tooling part providing time are filled by data engineers, and after tooling part providing time is filled, subsequent control point plan time is automatically calculated according to preset working hours. Actual time of P11-T6 needs to be filled by parts, process, procurement and production management departments according to actual time, and after filling, subsequent control information is collected. After information collection is initiated, the system triggers an email to each node management information personnel. Control point filling monitoring can be performed, and completed control points and specific information can be intuitively reflected.

[0076] Table 2 Control point information

[0077]

[0078]

[0079] The manufacturing data calculation module can not only select base vehicle type and neutral vehicle type, instantiate vehicle type according to demand, but also can perform regression calculation according to different time point data, different levels, different production centers and different assembly workshops. Different time point data is calculated by matching whole vehicle BOM and part data at 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 manufacturing end are distinguished, while product data expansion and regression do not control time, and will calculate based on the latest detailed data.

[0080] For example, for part B300048160, both factory 1 and factory 2 in city F use the part, and factory 1 uses the C68 vehicle model and factory 2 uses the S59 vehicle model. When performing regression calculation, if the production center selects factory 1, the calculated data is the use of the part in factory 1, that is, the vehicle model result is calculated according to the details of factory 1, and regression calculation can be performed according to data at different times; if factory 2 is selected, the calculated data is the use of the part in factory 2, that is, the vehicle model result is calculated according to the details of factory 2; if the data in the past week is queried, the time point can be selected during regression, and the BOM module calculates the whole vehicle data one week ago.

[0081] Referring to Table 3, it is assumed that the instantiation vehicle model A of part A is effective on June 25, 2024, and the regression time is selected as May 25, 2024. Since part A is in a free state at the manufacturing end, it has no vehicle model use, and the time intersection of each level is selected for calculation. If assembly A is expanded at the time point of May 25, 2024, assembly A has no sub-structure, but if the time is greater than or equal to May 30, 2024, the sub-structure of assembly A expanded is part A and part B.

[0082] Table 3 second data time table

[0083] Hierarchy Name Product data release time Manufacturing end effective time 1 Base vehicle model A 20231201 20231201 2 Instantiated neutral vehicle model A 20231201 20231201 3 Instantiated vehicle 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, the embodiment can manage parts according to the characteristics of various types of parts and complex attribute information, and all parts and key attribute information are defined by templates, improving information accuracy and completeness. Since the part structure is complex, the design scheme needs to be confirmed and combined through multiple rounds before it can be solidified, and multiple changes will occur as the design is optimized. The embodiment records and manages all version change information and drawing information in the system, thereby achieving comprehensive information management and tracking change history. It can be understood that parts are important components of vehicle structures and are not isolated. The embodiment has the function of managing parent and child parts to establish the blood relationship of parts, thereby facilitating analysis and tracking of change impact. In addition, according to production needs, the embodiment manages and controls parts according to different use locations and use times, 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, the embodiment also provides a part information management system.

[0086] In an embodiment, the part information management system comprises:

[0087] a first management module configured to manage all part change data based on change subjects to generate a target change database, wherein part change data managed by each control item in the target change database has the same change subject;

[0088] a second management module configured to, when receiving a target classification and statistics instruction, classify and statistically analyze part change data in the target change database according to the target classification and statistics instruction to generate a target statistical result, wherein the target classification and statistics instruction comprises a first instruction, and the first instruction comprises at least one of a change issuing department, a change reason and a change implementation stage.

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

[0090] Further, in an embodiment, the first management module is specifically configured to:

[0091] set one control item for each change subject;

[0092] add part change data with the same change subject to the same control item to generate the target change database.

[0093] Further, in an embodiment, the second management module is specifically configured to:

[0094] when the first instruction is the change issuing department, determine the target change issuing department of each part change data based on the change issuing department field in the product definition and the change notice, and statistically analyze part change data with the same target change issuing department to generate the target statistical result;

[0095] when the first instruction is the change reason, determine the target change reason of each part change data based on the change reason field in the product definition and the change notice, and statistically analyze part change data with the same target change reason to generate the target statistical result;

[0096] when the first instruction is the change implementation stage, determine the target change implementation stage of each part change data based on the change implementation stage field in the product definition and the change notice, and statistically analyze part change data with the same target change implementation stage to generate the target statistical result.

[0097] Further, in an embodiment, the target classification and statistics instruction further comprises a second instruction, wherein the second instruction comprises a vehicle model, a machine model and a new energy power model, and the second management module is specifically further configured to:

[0098] According to the second instruction, the part change data in the target change database is classified and counted to obtain target statistical data;

[0099] According to the first instruction, the target statistical data is classified and counted to generate a target statistical result.

[0100] The functions of each module in the part information management system correspond to the steps in the part information management method, and the functions and implementation processes will not be repeated here.

[0101] In a third aspect, the embodiments of the present application provide a part information management device. The part information management device can be a personal computer (PC), a notebook computer, a server, or other devices with data processing functions.

[0102] Reference Figure 5 , Figure 5 The figure shows the hardware structure of the part information management device involved in the embodiments of the present application. In the embodiments of the present application, the part information management device can include a processor, a memory, a communication interface, and a communication bus.

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

[0104] The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, which are used to interconnect the devices inside the part information management device, and interfaces used to interconnect the part information management device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber interface, an ATM interface, etc.; the user device can be a display screen (Display), a keyboard (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 disks, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0106] The processor can be a general processor, which can invoke a spare part information management program stored in the memory and execute the spare part information management method provided in the embodiments of the present application. For example, the general processor can be a central processing unit (CPU). The method executed when the spare part information management program is invoked can refer to the embodiments of the spare part information management method of the present application, which will not be described herein.

[0107] Those skilled in the art can understand that the hardware structure shown in the foregoing Figure 5 The hardware structure shown in the foregoing embodiments of the present application does not constitute a limitation on the present application, and can include more or fewer components than those shown in the figure, or combine certain components, or different arrangement of components.

[0108] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium.

[0109] The computer readable storage medium of the present application stores a spare part information management program, wherein the spare part information management program is executed by the processor to implement the steps of the spare part information management method as described above.

[0110] The method implemented when the spare part information management program is executed can refer to the embodiments of the spare part information management method of the present application, which will not be described herein.

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

[0112] The terms "comprising" and "having" and any variations thereof in the specification and claims of the present application and the above-described drawings are intended to cover not exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device. The terms "first", "second" and "third" and the like descriptions are used to distinguish different objects, and do not represent the order or limit the types of "first", "second" and "third".

[0113] In the description of the embodiments of the present application, "exemplary", "for example" or "for instance" is used to mean as an example, illustration or description. Any embodiment or design scheme described as "exemplary", "for example" or "for instance" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words "exemplary", "for example" or "for instance" are intended to present the relevant concept in a specific manner.

[0114] In the description of the embodiments of the present application, unless otherwise specified, " / " means the meaning of or, for example, A / B can mean A or B; the text "and / or" only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist together, and B exists alone, and in addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

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

[0116] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk) as described above, and includes a plurality of instructions for making a terminal device execute the method described in each embodiment of the present application.

[0117] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation using the content of the present application specification and drawings, or direct or indirect application 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 includes: All component design change data are managed based on the change theme to generate a target design change database, where 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, classification and statistics are performed on 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, 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; 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 the target design change database.

2. The parts information management method according to claim 1, wherein: 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 target statistical results 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, a target design change reason for each component design change data is determined based on the product definition and the design change reason field in the change notice, and the design change data of the components with the same target design change reason are statistically analyzed 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 to generate the target statistical results.

3. The parts information management method according to claim 1, wherein: The target classification statistics instruction further includes a second instruction, the second instruction including vehicle type, engine type and new energy power model, and the classification statistics of the component design change data in the target design change database are performed according to the target classification statistics instruction to generate target statistical results, 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.

4. A parts information management system, characterized in that: The parts information management system includes: A first management module is configured to manage all component design change data based on a 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; a second management module configured to, upon receiving a target classification and statistics instruction, classify and count 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, wherein the target classification and statistics instruction includes a first instruction, wherein the first instruction includes at least one of a design change issuing department, a design change reason, and a design change implementation stage; 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 the target design change database.

5. The parts information management system according to claim 4, wherein: The second management module is specifically configured to: 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, a target design change reason for each component design change data is determined based on the product definition and the design change reason field in the change notice, and the design change data of the components with the same target design change reason are statistically analyzed 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 to generate the target statistical results.

6. The parts information management system according to claim 4, wherein: The target classification statistics instruction further includes a second instruction, the second instruction including vehicle type, engine type and new energy power type, and the second management module is further specifically configured 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.

7. 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 according to any one of claims 1 to 3 are implemented.

8. 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 parts information management method according to any one of claims 1 to 3 is implemented.

Images