Vehicle engineering monitoring task generation method, device, equipment and storage medium

Abstract

A method, device, equipment and storage medium for generating a whole vehicle engineering monitoring task, which determines a target inspection frequency and a target auditor corresponding to a target monitoring business according to a monitoring business and an auditor business mapping table; determines a target monitoring date and a target quantity based on the target inspection frequency; determines a target vehicle model, a target chassis number, a target production date and a target BOM date from production information based on a target production line and a target monitoring date; determines target preset parameters from vehicle model identification information or process parameter information according to the target vehicle model and BOM date; determines target monitoring items, target inspection methods and target inspection standards through target preset parameters, a target monitoring business and a monitoring business mapping table; and generates a target monitoring task based on a target production line, a target monitoring business, a target monitoring item, a target inspection method, a target inspection standard, a target auditor, a target monitoring date, a target production date, a target vehicle model, a target chassis number and a target quantity.

Description

Technical Field

[0001] The present application relates to the field of vehicle management technology, and specifically to a method, device, equipment and storage medium for generating vehicle engineering monitoring tasks. Background Art

[0002] Currently, during the vehicle production process and after it rolls off the production line, it is necessary to measure and monitor one or more quality characteristics of the vehicle (including but not limited to weight-bearing torque, VIN code, oil and water filling, three leaks, and rain exposure) in accordance with the provisions of process documents such as control plans and inspection regulations or temporarily added quality enhancement projects. The results must be compared with the specified requirements to clarify the qualification status of each characteristic, and then the whole vehicle engineering supervision is implemented to ensure the quality and safety of the whole vehicle.

[0003] In related technologies, when implementing vehicle engineering supervision, technicians usually output inspection process cards and 12 process record forms for each vehicle model, so that the inspection team leader can formulate an inspection plan for each inspector based on the process record form, the division of labor among inspectors, and the inspection frequency requirements (that is, the specific frequency is based on the inspection regulations and the record form requirements); then the inspectors manually determine the specific items of each inspection business in the inspection plan based on the production plan issued by the order room (due to changes in the actual production situation, repeated verification is required) to complete the inspection task confirmation of the vehicle engineering; based on the confirmed inspection task, the inspectors manually query the production ledger or consult the workshop to confirm the vehicle chassis number and production time, and then find the inspection vehicle and carry out engineering supervision.

[0004] It can be seen that which items need to be monitored every day rely on the independent judgment of the auditors, which is not only prone to omissions of monitoring items, but may also fail to cover all vehicle series. Moreover, each auditor has different professional qualities and ability levels, and manual-driven work management is difficult and accuracy cannot be guaranteed. In addition, since production plans may change, auditors are not clear about the production status of vehicles. Therefore, auditors need to frequently check the ledgers themselves or wait for notifications from the workshop to determine the target vehicles. This method of relying on manual tracking not only consumes a lot of manpower and is inefficient, but is also prone to omissions. In addition, all inspection standards delivered manually offline need to be queried to find the inspection standards corresponding to the monitoring items to implement the monitoring work, which is not only inefficient but also prone to errors.

[0005] Therefore, how to effectively realize the automatic generation of monitoring tasks in vehicle engineering to improve monitoring accuracy and efficiency and reduce monitoring costs is an urgent problem that needs to be solved. Summary of the Invention

[0006] The present application provides a method, device, equipment and storage medium for generating monitoring tasks for a complete vehicle project, which can effectively realize the automatic generation of monitoring tasks in the complete vehicle project, thereby improving the accuracy and efficiency of monitoring and reducing the cost of monitoring.

[0007] In a first aspect, an embodiment of the present application provides a method for generating a vehicle engineering monitoring task, comprising the following steps:

[0008] For each target monitoring service in each target production line, a target inspection frequency and a target auditor corresponding to the target monitoring service are respectively determined according to a preset monitoring service mapping table and a preset auditor service mapping table. The monitoring service mapping table includes a mapping relationship between the monitoring service type, monitoring item, inspection method, inspection standard, inspection frequency, and preset parameters. The preset parameter is a first parameter or a second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor service mapping table includes a mapping relationship between the production line, the monitoring service type, and the auditor's name.

[0009] Determine a target inspection date and target quantity based on the target inspection frequency, and determine a target vehicle model, target chassis number, target production date, and target BOM date based on the target production line and target inspection date from production information received from the production management system (MES);

[0010] Determine target preset parameters based on the target vehicle model and target BOM date from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP;

[0011] Determine the target monitoring items, target inspection methods and target inspection standards through the target preset parameters, target monitoring services and monitoring service mapping table;

[0012] Construct a mapping relationship between target production lines, target monitoring businesses, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring dates, target production dates, target vehicle models, target chassis numbers, and target quantities to generate target monitoring tasks.

[0013] In conjunction with the first aspect, in one embodiment, the production information includes a mapping relationship between a production line, a chassis number, a vehicle model, a BOM date, and a production date, and determining a target vehicle model, a target chassis number, a target production date, and a target BOM date from the production information received from the production management system (MES) based on the target production line and the target monitoring date includes:

[0014] determining, from the production information, all first production dates corresponding to the target inspection date;

[0015] For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date;

[0016] The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

[0017] In conjunction with the first aspect, in one embodiment, the vehicle type identification information includes a mapping relationship between a vehicle model, a BOM date, an energy type, and a braking mode, and determining the target preset parameters from the vehicle type identification information received from the BOM system based on the target vehicle model and the target BOM date includes:

[0018] Determining all first vehicle models corresponding to the target vehicle model from the vehicle model identification information;

[0019] For each first vehicle model, when it is detected that the BOM date corresponding to the first vehicle model in the vehicle model identification information is the same as the target BOM date, the energy type and braking method corresponding to the first vehicle model in the vehicle model identification information are used as the target energy type and target braking method respectively, and the target preset parameters are the target energy type and target braking method.

[0020] In conjunction with the first aspect, in one embodiment, the process parameter information includes a mapping relationship between a vehicle model, a BOM date, functional parts, and specifications. Determining target preset parameters from the process parameter information received from the process design system CAPP based on the target vehicle model and the target BOM date includes:

[0021] determining all second vehicle models corresponding to the target vehicle model from the process parameter information;

[0022] For each second vehicle model, when it is detected that the BOM date corresponding to the second vehicle model in the process parameter information is the same as the target BOM date, the functional parts and specifications corresponding to the second vehicle model in the vehicle model identification information are used as the target functional parts and target specifications respectively, and the target preset parameters are the target functional parts and target specifications.

[0023] In conjunction with the first aspect, in one embodiment, after the step of generating the target monitoring task, the method further includes:

[0024] The target monitoring task is transmitted to the target auditor so that the target auditor can monitor based on the target monitoring task.

[0025] In conjunction with the first aspect, in one embodiment, after the step of the target auditor performing monitoring based on the target monitoring task, the method further includes:

[0026] Receive the target monitoring results corresponding to the target monitoring tasks entered by the target auditor;

[0027] The target monitoring results are visualized.

[0028] In a second aspect, an embodiment of the present application provides a vehicle engineering monitoring task generation device, including a quality management system MQ, which is used to:

[0029] For each target monitoring service in each target production line, a target inspection frequency and a target auditor corresponding to the target monitoring service are respectively determined according to a preset monitoring service mapping table and a preset auditor service mapping table. The monitoring service mapping table includes a mapping relationship between the monitoring service type, monitoring item, inspection method, inspection standard, inspection frequency, and preset parameters. The preset parameter is a first parameter or a second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor service mapping table includes a mapping relationship between the production line, the monitoring service type, and the auditor's name.

[0030] Determine a target inspection date and target quantity based on the target inspection frequency, and determine a target vehicle model, target chassis number, target production date, and target BOM date based on the target production line and target inspection date from production information received from the production management system (MES);

[0031] Determine target preset parameters based on the target vehicle model and target BOM date from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP;

[0032] Determine the target monitoring items, target inspection methods and target inspection standards through the target preset parameters, target monitoring services and monitoring service mapping table;

[0033] Construct a mapping relationship between target production lines, target monitoring businesses, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring dates, target production dates, target vehicle models, target chassis numbers, and target quantities to generate target monitoring tasks.

[0034] In conjunction with the second aspect, in one embodiment, the production information includes a mapping relationship between a production line, a chassis number, a vehicle model, a BOM date, and a production date, and the MQ system is specifically configured to:

[0035] determining, from the production information, all first production dates corresponding to the target inspection date;

[0036] For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date;

[0037] The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

[0038] In conjunction with the second aspect, in one embodiment, the vehicle model identification information includes a mapping relationship between the vehicle model, BOM date, energy type, and braking mode, and the MQ system is further configured to:

[0039] Determining all first vehicle models corresponding to the target vehicle model from the vehicle model identification information;

[0040] For each first vehicle model, when it is detected that the BOM date corresponding to the first vehicle model in the vehicle model identification information is the same as the target BOM date, the energy type and braking method corresponding to the first vehicle model in the vehicle model identification information are used as the target energy type and target braking method respectively, and the target preset parameters are the target energy type and target braking method.

[0041] In conjunction with the second aspect, in one embodiment, the process parameter information includes a mapping relationship between vehicle models, functional parts, and specifications, and the MQ system is further configured to:

[0042] determining all second vehicle models corresponding to the target vehicle model from the process parameter information;

[0043] For each second vehicle model, when it is detected that the BOM date corresponding to the second vehicle model in the process parameter information is the same as the target BOM date, the functional parts and specifications corresponding to the second vehicle model in the vehicle model identification information are used as the target functional parts and target specifications respectively, and the target preset parameters are the target functional parts and target specifications.

[0044] In conjunction with the second aspect, in one embodiment, the MQ system is further used to:

[0045] The target monitoring task is transmitted to the target auditor so that the target auditor can monitor based on the target monitoring task.

[0046] In conjunction with the second aspect, in one embodiment, the MQ system is further used to:

[0047] Receive the target monitoring results corresponding to the target monitoring tasks entered by the target auditor;

[0048] The target monitoring results are visualized.

[0049] On the third aspect, an embodiment of the present application provides a whole vehicle engineering monitoring task generation device, which includes a processor, a memory, and a whole vehicle engineering monitoring task generation program stored on the memory and executable by the processor, wherein when the whole vehicle engineering monitoring task generation program is executed by the processor, the steps of the whole vehicle engineering monitoring task generation method as described above are implemented.

[0050] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a whole vehicle engineering monitoring task generation program is stored, wherein when the whole vehicle engineering monitoring task generation program is executed by a processor, the steps of the whole vehicle engineering monitoring task generation method as described above are implemented.

[0051] The beneficial effects of the technical solutions provided in the embodiments of the present application include:

[0052] The target inspection frequency and target auditor corresponding to the target monitoring business are determined respectively through the preset monitoring business mapping table and the preset auditor business mapping table, and then the target monitoring date and target quantity are determined based on the target inspection frequency, and the target vehicle model, target chassis number, target production date and target BOM date are determined from the production information received from the MES based on the target production line and target monitoring date; then, the target preset parameters are determined from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP based on the target vehicle model and target BOM date, and the target monitoring items, target inspection methods and target inspection standards are determined through the target preset parameters, target monitoring business and monitoring business mapping table; finally, the mapping relationship between the target production line, target monitoring business, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring date, target production date, target vehicle model, target chassis number and target quantity is constructed to automatically generate the target monitoring task. Through this application, linkage with MES, BOM and CAPP systems is achieved to realize the digitization of the entire business process, so as to effectively realize the automatic generation of monitoring tasks in the whole vehicle engineering, thereby improving the accuracy and efficiency of monitoring and reducing the cost of monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 This is a flowchart of an embodiment of the method for generating vehicle engineering monitoring tasks in this application;

[0054] Figure 2 This is a schematic diagram of the overall process involved in the embodiment of this application;

[0055] Figure 3 This is a diagram showing the monitoring business mapping involved in the embodiment of this application;

[0056] Figure 4This is a schematic diagram of the hardware structure of the vehicle engineering monitoring task generation device involved in the embodiment of this application. DETAILED DESCRIPTION

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

[0058] First, some technical terms in this application are explained to facilitate those skilled in the art to understand this application.

[0059] Vehicle Engineering Monitoring: During the vehicle production process and after it rolls off the production line, one or more quality characteristics of the vehicle are measured and inspected according to the control plan, inspection regulations and other process documents or temporarily added quality enhancement items. The results are compared with the specified requirements to determine the conformity of each characteristic.

[0060] Supervision tasks: Supervision work tasks generated based on supervision rules and vehicle production conditions.

[0061] MQ system: quality management system, which is mainly used to manage quality inspection business, quality improvement business, and quality operation business.

[0062] CAPP system: Computer-aided process design system, a system belonging to the R&D field, which focuses on manufacturing process design, process parameter management, etc., and is used to transmit process parameters (such as torque, etc.) to the MQ system.

[0063] MES system: Production management system, which mainly monitors, tracks, records and controls the entire product manufacturing process from raw materials to finished products, focusing on production scheduling, production execution, etc., and is used to transmit vehicle production information to the MQ system.

[0064] BOM system: Bill of Materials management system, which mainly records and manages all lower-level materials and related properties used in a product, that is, the subordinate relationship between the parent part and all sub-parts, unit usage and other properties, and is used to transmit vehicle model information to the MQ system.

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

[0066] In a first aspect, an embodiment of the present application provides a method for generating a vehicle engineering monitoring task.

[0067] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of the method for generating vehicle engineering monitoring tasks in this application. Figure 1 As shown in FIG, the vehicle engineering monitoring task generation method includes:

[0068] Step S10: For each target monitoring business in each target production line, the target inspection frequency and target auditor corresponding to the target monitoring business are respectively determined according to the preset monitoring business mapping table and the preset auditor business mapping table. The monitoring business mapping table includes the mapping relationship between the monitoring business type, monitoring items, inspection methods, inspection standards, inspection frequency, and preset parameters. The preset parameters are the first parameter or the second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor business mapping table includes the mapping relationship between the production line, the monitoring business type, and the auditor's name.

[0069] For example, in this embodiment, a unified digital configuration and push rules for vehicle engineering monitoring tasks as shown in Table 1 will be established in the MQ system, and automatic online allocation of monitoring tasks will be realized to avoid the phenomenon of incomplete project coverage due to manual random inspections.

[0070] Table 1 Digital configuration and push rules for vehicle engineering monitoring tasks

[0071]

[0072]

[0073]

[0074] It should be noted that Table 1 is only a presentation of an embodiment, and specific descriptions such as monitoring business type, inspection frequency, and system rule content can also be adaptively adjusted according to actual needs and are not limited here.

[0075] See also Figure 2 As shown, this embodiment will maintain the vehicle engineering monitoring business in the MQ system based on the digital configuration and push rules corresponding to Table 1 above; among them, for all monitoring business types except the weight protection torque, a mapping relationship between the monitoring business type, monitoring items, inspection methods, inspection standards, inspection frequency, and preset parameters (i.e., the first parameter, i.e., energy type and braking mode) will be constructed. For example, for the oil and water filling monitoring business type, the mapping relationship can be constructed as follows: Figure 3 The monitoring business mapping table shown in the figure should be noted that Figure 3The “×” indicates not executed, and the “√” indicates executed. Energy types include pure electric, gasoline, diesel and CNG (Compressed Natural Gas), etc. Braking methods include dual-circuit hydraulic braking (hydraulic power assist), dual-circuit hydraulic braking (vacuum power assist) and dual-circuit air braking. The monitoring items corresponding to the oil and water filling monitoring include but are not limited to brake fluid, transmission oil, transmission oil, rear axle oil, engine oil, coolant and windshield washer fluid; the inspection standard corresponding to the brake fluid item is that the brake fluid level is between MIN (minimum value) and MAX (maximum value), the inspection method is visual inspection and the inspection frequency is 2 units / shift. It should be noted that, Figure 3 The constructed monitoring service mapping table is only a presentation of an embodiment, and its specific content can be adaptively adjusted according to actual needs, which is not limited here.

[0076] For the monitoring business of the type of heavy-duty torque, a mapping relationship will be established between the monitoring business type, monitoring items, inspection methods, inspection standards, inspection frequency, and preset parameters (i.e., the second parameter, i.e., the functional part (such as the tightening part) and the specification (such as the bolt specification)) to form a monitoring business mapping table corresponding to the heavy-duty torque.

[0077] In addition, the MQ system will also maintain the auditor's supervisory business division of labor. The MQ system will compare the supervisory business and the auditor's division of labor to generate the auditor's supervisory business, thereby establishing a mapping relationship between the production line, supervisory business type, and auditor's name. If auditors are grouped, the auditor's team can also be maintained to further refine the auditor's information, thereby generating the auditor's business mapping table shown in Table 2, which supports batch import and export. It should be noted that Table 2 is only a presentation of an embodiment, and its specific content can be adaptively adjusted according to actual needs and is not limited here.

[0078] Table 2 Auditor business mapping table

[0079] Serial number production line Supervision business type team Auditor's name 1 ZD1 Oil and water filling inspection Audit Team 1 generation* 2 ZD1 Heavy torque detection Audit Team 1 Hu* 3 ZD1 Air conditioning outlet temperature measurement Audit Team 1 generation* 4 ZD3 Oil and water filling inspection Audit Team 2 Zhao* 5 ZD3 Heavy torque detection Audit Team 2 Zhao* 6 ZD3 Air conditioning outlet temperature measurement Audit Team 2 Zhao* … … … … …

[0080] It should be understood that, according to the auditor's business mapping table, each production line has its own monitoring business type that requires monitoring. Therefore, when the process of generating monitoring tasks is triggered by receiving production information (such as production line, production date, vehicle model, chassis number, etc.) sent by the MES system or process parameter information (such as vehicle model, tightening location, bolt specification, tightening quantity, torque value, etc.) sent by the CAPP system, for each target monitoring business (such as oil and water filling inspection, re-guaranteed torque detection, air conditioning outlet temperature measurement, etc.) in each target production line (such as ZD1, ZD3) in the auditor's business mapping table, a corresponding number of recommended monitoring models will be selected to generate monitoring tasks. Among them, first, the target inspection frequency corresponding to the target monitoring business can be determined from the monitoring business mapping table. For example, if the target monitoring business is oil and water filling inspection, the corresponding target inspection frequency is 2 units / shift, that is, 2 units need to be selected for monitoring in each shift every day; at the same time, the target auditor corresponding to the target production line and target monitoring business is determined from the auditor business mapping table. For example, if the target production line is ZD1 and the target monitoring business is oil and water filling inspection, the agent of the first audit shift will be used as the target auditor.

[0081] Step S20: Determine the target inspection date and target quantity based on the target inspection frequency, and determine the target vehicle model, target chassis number, target production date and target BOM date from the production information received from the production management system MES based on the target production line and target inspection date.

[0082] For example, in this embodiment, after knowing the target inspection frequency, the target monitoring date and target quantity can be determined based on it. For example, assuming that the current date is December 24, 2024 and the target inspection frequency is 2 units / shift, then the corresponding target monitoring date is December 24, 2024 and the target quantity is 2, that is, the production date corresponding to the two models recommended for monitoring should be December 24, 2024.

[0083] It should be understood that the MQ system in this embodiment will introduce production information on each production line from the MES system. The production information includes the mapping relationship between the production line, vehicle model, chassis number, production date and BOM date. For example, if the chassis number is A and the corresponding production line is ZD2, the vehicle model is B, the production date is C and the BOM date is D, then a mapping relationship between ZD2, A, B, C and D will be constructed; therefore, after determining the target monitoring date, the MQ system can query the target vehicle model, target chassis number, target production date and target BOM date corresponding to the target production line and target monitoring date from the production information sent by the MES system.

[0084] Step S30: Determine target preset parameters from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP according to the target vehicle model and the target BOM date.

[0085] For example, it should be noted that the vehicle model identification information (i.e., the vehicle model identification library) includes the mapping relationship between the vehicle model and the energy type, braking method and BOM date. For example, if the vehicle model is B and its corresponding BOM date is D, the energy type is gasoline and the braking method is dual-circuit hydraulic braking (vacuum power assist), then the mapping relationship between B, D, gasoline and dual-circuit hydraulic braking (vacuum power assist) is constructed; the process parameter information includes the mapping relationship between the vehicle model, BOM date, functional parts and specifications. For example, if the vehicle model is B and its corresponding BOM date is D, the functional part is the tightening part and the specification is E, then the mapping relationship between B, D, the tightening part and E is constructed.

[0086] In this embodiment, for non-reinforced torque inspection and monitoring services, the target energy type and target braking mode are determined from the vehicle model identification information received from the BOM system based on the target vehicle model and target BOM date, that is, the target preset parameters are the target energy type and target braking mode; and for reinforced torque monitoring services, the target functional parts and target specifications are determined from the process parameter information received from CAPP based on the target vehicle model and target BOM date, that is, the target preset parameters are the target functional parts and target specifications.

[0087] Step S40: determining the target monitoring item, target inspection method and target inspection standard through the target preset parameters, target monitoring service and monitoring service mapping table.

[0088] For example, in this embodiment, after the target preset parameters are determined, the corresponding target monitoring items and the target inspection methods and target inspection standards corresponding to the target monitoring items can be screened from the monitoring business mapping table according to the target preset parameters and the target monitoring business. For example, assuming that the target monitoring business is oil and water filling monitoring and the target preset parameters are gasoline and dual-circuit hydraulic brake (vacuum boost), then Figure 3 By looking up the monitoring business mapping table shown, it can be seen that the target monitoring items include brake fluid, transmission oil, rear axle oil, coolant and windshield washer fluid, and the target inspection standard corresponding to brake fluid is "brake fluid level between MIN and MAX", and the target inspection method is "visual inspection", etc.

[0089] Step S50: Construct a mapping relationship between the target production line, target monitoring business, target monitoring items, target inspection method, target inspection standard, target auditor, target monitoring date, target production date, target vehicle model, target chassis number and target quantity to generate a target monitoring task.

[0090] For example, in this embodiment, after determining all parameters such as the target production line, target monitoring business, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring date, target production date, target vehicle model, target chassis number and target quantity, a corresponding mapping relationship can be constructed to automatically complete the generation of all target monitoring tasks, such as the target monitoring tasks shown in Table 3.

[0091] Table 3 Target monitoring tasks

[0092]

[0093] It can be seen that this embodiment realizes the digitization of the entire business process by controlling the linkage between the MQ system and the MES, BOM and CAPP systems, so as to effectively realize the automatic generation of monitoring tasks in the whole vehicle engineering, thereby improving the accuracy and efficiency of monitoring and reducing the cost of monitoring, and supporting batch import and export; in addition, this embodiment maintains the inspection standards in the MQ system, that is, the inspection standards are matched one by one with the monitoring items, so as to realize the real-time visualization of the association between the inspection standards and the monitoring items, clarify the inspection standards, and effectively avoid errors.

[0094] In general, this embodiment launches the vehicle engineering monitoring business on the MQ system, formulates digital rules for monitoring tasks, takes data as the source, and integrates vehicle model information (BOM system), production information (MES system), monitoring information (MQ system), and process parameters (CAPP system) through interfaces between development systems. That is, the MQ system is linked with BOM / MES / CAPP to realize the digitization of the entire business process, so that all data flows online, accurately and reliably, to achieve the integration of the digital platform, thereby helping to clarify, accurately and obviously perform inspection work, which not only improves work efficiency, but also enables monitoring, reminders, sharing, analysis and traceability.

[0095] Furthermore, in one embodiment, the production information includes a mapping relationship between a production line, a chassis number, a vehicle model, a BOM date, and a production date. The determining of the target vehicle model, target chassis number, target production date, and target BOM date from the production information received from the production management system (MES) based on the target production line and the target monitoring date includes:

[0096] determining, from the production information, all first production dates corresponding to the target inspection date;

[0097] For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date;

[0098] The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

[0099] For example, in this embodiment, since the production information received from the MES includes the mapping relationship between the production line, chassis number, vehicle model, BOM date and production date, the target chassis number, target vehicle model and target BOM date can be filtered out by matching the production date and production line; wherein, the production line can be matched first and then the production date, or the production date can be matched first and then the production line, which is not limited here; since the matching methods and logic of the two are similar, for the sake of simplicity of description, the following embodiment will be explained by taking the matching of the production date first and then the production line as an example.

[0100] First, all first production dates that are the same as the target monitoring date are filtered out using the production information. Then, for each first production date, it is determined whether the production line in the mapping relationship recorded in the production information is the same as the target production line. If not, the first production date is not used as the target production date, and the judgment continues for the next first production date. If so, the first production date is used as the target production date, and the chassis number, vehicle model, and BOM date in the mapping relationship of the first production date recorded in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively. Based on this, the judgment continues for the next first production date. For example, if the target production line is ZD1 and the target monitoring date is December 24, 2024, all first production dates with a date of December 24, 2024 will be filtered out from the production information. If a first production date corresponds to the production line ZD1, the first production date is used as the target production date, and the chassis number, vehicle model, and BOM date in the mapping relationship of the first production date are used as the target chassis number, target vehicle model, and target BOM date, respectively.

[0101] Furthermore, in one embodiment, the vehicle type identification information includes a mapping relationship between a vehicle model, a BOM date, an energy type, and a braking mode. The target preset parameters are determined from the vehicle type identification information received from the BOM system based on the target vehicle model and the target BOM date, including:

[0102] Determining all first vehicle models corresponding to the target vehicle model from the vehicle model identification information;

[0103] For each first vehicle model, when it is detected that the BOM date corresponding to the first vehicle model in the vehicle model identification information is the same as the target BOM date, the energy type and braking method corresponding to the first vehicle model in the vehicle model identification information are used as the target energy type and target braking method respectively, and the target preset parameters are the target energy type and target braking method.

[0104] Exemplarily, in this embodiment, for non-reinforced torque inspection and monitoring services, all first vehicle models that are the same as the target vehicle model can be screened out from the vehicle model identification information received from the BOM system, which includes the mapping relationship between the vehicle model, BOM date, energy type, and braking mode; then, for each first vehicle model, determine whether the BOM date in the mapping relationship recorded in the vehicle model identification information is the same as the target BOM date. If they are different, the first vehicle model is abandoned, and the judgment of the next first vehicle model is continued; if they are the same, the energy type and braking mode in the mapping relationship of the first vehicle model recorded in the vehicle model identification information are respectively used as the target energy type to be matched and the target braking mode to be matched, that is, the target preset parameters are the target energy type and target braking mode, and based on this, the judgment of the next first vehicle model is continued.

[0105] Furthermore, in one embodiment, the process parameter information includes a mapping relationship between a vehicle model, a BOM date, functional parts, and specifications. The target preset parameters are determined from the process parameter information received from the process design system CAPP based on the target vehicle model and the target BOM date, including:

[0106] determining all second vehicle models corresponding to the target vehicle model from the process parameter information;

[0107] For each second vehicle model, when it is detected that the BOM date corresponding to the second vehicle model in the process parameter information is the same as the target BOM date, the functional parts and specifications corresponding to the second vehicle model in the vehicle model identification information are used as the target functional parts and target specifications respectively, and the target preset parameters are the target functional parts and target specifications.

[0108] Exemplarily, in this embodiment, for the re-insurance torque inspection and monitoring business, all second vehicle models that are the same as the target vehicle model can be screened out from the process parameter information received from the CAPP system, which includes the mapping relationship between the vehicle model, BOM date, functional parts and specifications; then, for each second vehicle model, it is determined whether the BOM date in the mapping relationship of the second vehicle model recorded in the process parameter information is the same as the target BOM date. If they are different, the second vehicle model is abandoned and the next second vehicle model is judged; if they are the same, the functional parts and specifications in the mapping relationship of the second vehicle model recorded in the process parameter information are used as the target functional parts to be matched and the target specifications to be matched, that is, the target preset parameters are the target functional parts and target specifications, and based on this, the next second vehicle model is judged.

[0109] Furthermore, in one embodiment, after the step of generating the target monitoring task, the method further includes:

[0110] The target monitoring task is transmitted to the target auditor so that the target auditor can monitor based on the target monitoring task.

[0111] For example, in this embodiment, after the target monitoring task is generated, the target monitoring task can be pushed to the target auditor recorded in the target monitoring task according to the push rules stored in Table 1, so that the target auditor can directly determine all vehicles to be monitored according to the target production line, target production date, target vehicle model, and target chassis number in the mapping relationship recorded in the target monitoring task, and screen out a target number of target vehicles from all vehicles to be monitored as the vehicles that ultimately need to be monitored, and at the same time, perform target monitoring business and target monitoring items on the target vehicles according to the target inspection method and target inspection standard.

[0112] For example, assuming that a target monitoring task is that the target production line is ZD2, the target monitoring business is oil and water filling monitoring, the target monitoring item is brake fluid, the target inspection standard is that the brake fluid level is between MIN and MAX, the target inspection method is visual, the target monitoring date is December 25, 2024, the target production date is December 25, 2024, the target vehicle model is B1, B2 and B3, the target chassis number is A1, A2 and A3, the target quantity is 2 and the target auditor is Y, then the target monitoring task is pushed to auditor Y, and the auditor Auditor Y locates all vehicles on production line ZD2 with a production date of December 25, 2024, and with model B1 and chassis number A1, model B2 and chassis number A2, and model B3 and chassis number A3. He then selects two vehicles as target vehicles for monitoring. On the target monitoring date of December 25, 2024, Auditor Y will visually inspect the brake fluid level on these two vehicles under the "oil and water filling" monitoring task, ensuring the brake fluid level is between the minimum and maximum limits. This process eliminates the need for auditors to query records or wait for notifications from the workshop. Instead, auditors can directly access all relevant information based on the pushed target monitoring tasks, effectively improving monitoring efficiency and accuracy.

[0113] Furthermore, in one embodiment, after the step of the target auditor performing monitoring based on the target monitoring task, the method further includes:

[0114] Receive the target monitoring results corresponding to the target monitoring tasks entered by the target auditor;

[0115] The target monitoring results are visualized.

[0116] For example, compared with the traditional method of manually delivering monitoring tasks, manually tracking the monitoring process, and manually recording monitoring results, this embodiment will enable the target auditor to fill in the vehicle engineering monitoring record in the MQ system after completing the monitoring task, that is, all traces generated when performing the target monitoring task and the entered target monitoring results will be recorded and displayed in the MQ system, so that the auditor's monitoring task completion status can be visualized and checked in real time, and then the team leader can accurately control the progress of the monitoring task completion, and can promptly discover and recover in time when an abnormality occurs, thereby realizing the controllable monitoring progress.

[0117] In summary, this embodiment connects the entire digital business chain and ultimately generates an accurate monitoring task, which includes the auditor's name, monitoring business type, monitoring project, vehicle model, production time, quantity (daily, weekly, monthly), etc., to clarify the monitoring task, and then make the whole vehicle engineering monitoring business process management and control accurate and effective. All data are online and true and accurate, thereby ensuring that the final monitoring results are also true and reliable, and improving the accuracy of the work.

[0118] In a second aspect, an embodiment of the present application also provides a device for generating vehicle engineering monitoring tasks.

[0119] In one embodiment, the vehicle engineering monitoring task generation device includes a quality management system MQ, which is used to:

[0120] For each target monitoring service in each target production line, a target inspection frequency and a target auditor corresponding to the target monitoring service are respectively determined according to a preset monitoring service mapping table and a preset auditor service mapping table. The monitoring service mapping table includes a mapping relationship between the monitoring service type, monitoring item, inspection method, inspection standard, inspection frequency, and preset parameters. The preset parameter is a first parameter or a second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor service mapping table includes a mapping relationship between the production line, the monitoring service type, and the auditor's name.

[0121] Determine a target inspection date and target quantity based on the target inspection frequency, and determine a target vehicle model, target chassis number, target production date, and target BOM date based on the target production line and target inspection date from production information received from the production management system (MES);

[0122] Determine target preset parameters based on the target vehicle model and target BOM date from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP;

[0123] Determine the target monitoring items, target inspection methods and target inspection standards through the target preset parameters, target monitoring services and monitoring service mapping table;

[0124] Construct a mapping relationship between target production lines, target monitoring businesses, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring dates, target production dates, target vehicle models, target chassis numbers, and target quantities to generate target monitoring tasks.

[0125] Furthermore, in one embodiment, the production information includes a mapping relationship between the production line, chassis number, vehicle model, BOM date, and production date, and the MQ system is specifically used to:

[0126] determining, from the production information, all first production dates corresponding to the target inspection date;

[0127] For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date;

[0128] The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

[0129] Furthermore, in one embodiment, the vehicle type identification information includes a mapping relationship between the vehicle model, BOM date, energy type, and braking mode, and the MQ system is further configured to:

[0130] Determining all first vehicle models corresponding to the target vehicle model from the vehicle model identification information;

[0131] For each first vehicle model, when it is detected that the BOM date corresponding to the first vehicle model in the vehicle model identification information is the same as the target BOM date, the energy type and braking method corresponding to the first vehicle model in the vehicle model identification information are used as the target energy type and target braking method respectively, and the target preset parameters are the target energy type and target braking method.

[0132] Furthermore, in one embodiment, the process parameter information includes a mapping relationship between vehicle models, functional parts, and specifications. The MQ system is further configured to:

[0133] determining all second vehicle models corresponding to the target vehicle model from the process parameter information;

[0134] For each second vehicle model, when it is detected that the BOM date corresponding to the second vehicle model in the process parameter information is the same as the target BOM date, the functional parts and specifications corresponding to the second vehicle model in the vehicle model identification information are used as the target functional parts and target specifications respectively, and the target preset parameters are the target functional parts and target specifications.

[0135] Furthermore, in one embodiment, the MQ system is also used to:

[0136] The target monitoring task is transmitted to the target auditor so that the target auditor can monitor based on the target monitoring task.

[0137] Furthermore, in one embodiment, the MQ system is also used to:

[0138] Receive the target monitoring results corresponding to the target monitoring tasks entered by the target auditor;

[0139] The target monitoring results are visualized.

[0140] Among them, the functional implementation of each part in the above-mentioned vehicle engineering monitoring task generation device corresponds to the various steps in the above-mentioned vehicle engineering monitoring task generation method embodiment, and its functions and implementation processes will not be repeated here one by one.

[0141] In a third aspect, an embodiment of the present application provides a vehicle engineering monitoring task generation device, which may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0142] Reference Figure 4 , Figure 4 Schematic diagram of the hardware structure of the vehicle engineering monitoring task generation device involved in the embodiment of the present application. In the embodiment of the present application, the vehicle engineering monitoring task generation device may include a processor, a memory, a communication interface and a communication bus.

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

[0144] Communication interfaces include input / output (I / O) interfaces, physical interfaces, and logical interfaces. These interfaces interconnect components within the vehicle engineering monitoring task generation device, as well as interfaces that connect the device to other devices (such as other computing devices or user devices). Physical interfaces can include Ethernet, fiber optic, and ATM interfaces; user devices can include displays and keyboards.

[0145] 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.

[0146] The processor may be a general-purpose processor that can call the vehicle engineering monitoring task generation program stored in the memory and execute the vehicle engineering monitoring task generation method provided in the embodiments of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the vehicle engineering monitoring task generation program is called can refer to the various embodiments of the vehicle engineering monitoring task generation method of the present application, and will not be repeated here.

[0147] Those skilled in the art will understand that Figure 4The hardware structure shown in the figure does not constitute a limitation to the present application and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

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

[0149] The readable storage medium of the present application stores a vehicle engineering monitoring task generation program, wherein when the vehicle engineering monitoring task generation program is executed by the processor, the steps of the vehicle engineering monitoring task generation method as described above are implemented.

[0150] Among them, the method implemented when the vehicle engineering monitoring task generation program is executed can refer to the various embodiments of the vehicle engineering monitoring task generation method of this application, and will not be repeated here.

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

[0152] 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 the "first", "second" and "third" to different types.

[0153] In the description of the embodiments of this application, the words "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 this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.

[0154] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “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.

[0155] In some processes described in the embodiments of the present application, multiple operations or steps are included that appear in a specific order. However, it should be understood that these operations or steps may not be performed in the order in which they appear in the embodiments of the present application or may be performed in parallel. The sequence numbers of the operations are only used to distinguish between different operations, and the sequence numbers themselves do not represent any order of execution. In addition, these processes may include more or fewer operations, and these operations or steps may be performed in sequence or in parallel, and these operations or steps may be combined.

[0156] 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 the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, 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, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device to execute the methods described in each embodiment of the present application.

[0157] The above are only preferred embodiments of the present application and do not 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 method for generating vehicle engineering monitoring tasks, characterized in that: The following steps are involved: For each target monitoring service in each target production line, a target inspection frequency and a target auditor corresponding to the target monitoring service are respectively determined according to a preset monitoring service mapping table and a preset auditor service mapping table. The monitoring service mapping table includes a mapping relationship between the monitoring service type, monitoring item, inspection method, inspection standard, inspection frequency, and preset parameters. The preset parameter is a first parameter or a second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor service mapping table includes a mapping relationship between the production line, the monitoring service type, and the auditor's name. Determine a target inspection date and target quantity based on the target inspection frequency, and determine a target vehicle model, target chassis number, target production date, and target BOM date based on the target production line and target inspection date from production information received from the production management system (MES); Determine target preset parameters based on the target vehicle model and target BOM date from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP; Determine the target monitoring items, target inspection methods and target inspection standards through the target preset parameters, target monitoring services and monitoring service mapping table; Construct a mapping relationship between target production lines, target monitoring businesses, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring dates, target production dates, target vehicle models, target chassis numbers, and target quantities to generate target monitoring tasks.

2. The method for generating vehicle engineering monitoring tasks according to claim 1, wherein: The production information includes a mapping relationship between a production line, a chassis number, a vehicle model, a BOM date, and a production date. The target vehicle model, target chassis number, target production date, and target BOM date are determined from the production information received from the production management system (MES) based on the target production line and the target monitoring date, including: determining, from the production information, all first production dates corresponding to the target inspection date; For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date; The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

3. The method for generating vehicle engineering monitoring tasks according to claim 2, wherein: The vehicle type identification information includes a mapping relationship between the vehicle model, BOM date, energy type, and braking mode. The target preset parameters are determined from the vehicle type identification information received from the BOM system according to the target vehicle model and the target BOM date, including: Determining all first vehicle models corresponding to the target vehicle model from the vehicle model identification information; For each first vehicle model, when it is detected that the BOM date corresponding to the first vehicle model in the vehicle model identification information is the same as the target BOM date, the energy type and braking method corresponding to the first vehicle model in the vehicle model identification information are used as the target energy type and target braking method respectively, and the target preset parameters are the target energy type and target braking method.

4. The method for generating vehicle engineering monitoring tasks according to claim 2, wherein: The process parameter information includes a mapping relationship between vehicle model, BOM date, functional parts, and specifications. The target preset parameters are determined from the process parameter information received from the process design system CAPP based on the target vehicle model and target BOM date, including: determining all second vehicle models corresponding to the target vehicle model from the process parameter information; For each second vehicle model, when it is detected that the BOM date corresponding to the second vehicle model in the process parameter information is the same as the target BOM date, the functional parts and specifications corresponding to the second vehicle model in the vehicle model identification information are used as the target functional parts and target specifications respectively, and the target preset parameters are the target functional parts and target specifications.

5. The method for generating vehicle engineering monitoring tasks according to claim 1, wherein: After the step of generating the target monitoring task, the method further includes: The target monitoring task is transmitted to the target auditor so that the target auditor can monitor based on the target monitoring task.

6. The method for generating vehicle engineering monitoring tasks according to claim 5, characterized in that: After the target auditor performs the monitoring based on the target monitoring task, the method further includes: Receive the target monitoring results corresponding to the target monitoring tasks entered by the target auditor; The target monitoring results are visualized.

7. A vehicle engineering monitoring task generation device, characterized in that: Includes the Quality Management System MQ, which is used to: For each target monitoring service in each target production line, a target inspection frequency and a target auditor corresponding to the target monitoring service are respectively determined according to a preset monitoring service mapping table and a preset auditor service mapping table. The monitoring service mapping table includes a mapping relationship between the monitoring service type, monitoring item, inspection method, inspection standard, inspection frequency, and preset parameters. The preset parameter is a first parameter or a second parameter. The first parameter is the energy type and braking mode, and the second parameter is the functional part and specification. The auditor service mapping table includes a mapping relationship between the production line, the monitoring service type, and the auditor's name. Determine a target inspection date and target quantity based on the target inspection frequency, and determine a target vehicle model, target chassis number, target production date, and target BOM date based on the target production line and target inspection date from production information received from the production management system (MES); Determine target preset parameters based on the target vehicle model and target BOM date from the vehicle model identification information received from the BOM system or the process parameter information received from the process design system CAPP; Determine the target monitoring items, target inspection methods and target inspection standards through the target preset parameters, target monitoring services and monitoring service mapping table; Construct a mapping relationship between target production lines, target monitoring businesses, target monitoring items, target inspection methods, target inspection standards, target auditors, target monitoring dates, target production dates, target vehicle models, target chassis numbers, and target quantities to generate target monitoring tasks.

8. The vehicle engineering monitoring task generation device according to claim 7, characterized in that: The production information includes the mapping relationship between the production line, chassis number, vehicle model, BOM date and production date. The MQ system is specifically used to: determining, from the production information, all first production dates corresponding to the target inspection date; For each first production date, when it is detected that the production line corresponding to the first production date in the production information is the same as the target production line, the first production date is used as the target production date; The chassis number, vehicle model, and BOM date corresponding to the target production date in the production information are used as the target chassis number, target vehicle model, and target BOM date, respectively.

9. A vehicle engineering monitoring task generation device, characterized in that: The whole vehicle engineering monitoring task generation device includes a processor, a memory, and a whole vehicle engineering monitoring task generation program stored in the memory and executable by the processor, wherein when the whole vehicle engineering monitoring task generation program is executed by the processor, the steps of the whole vehicle engineering monitoring task generation method as described in any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a vehicle engineering monitoring task generation program, wherein when the vehicle engineering monitoring task generation program is executed by the processor, the steps of the vehicle engineering monitoring task generation method according to any one of claims 1 to 6 are implemented.

Images