Whole vehicle production inspection method and electronic equipment

Abstract

The invention provides a whole vehicle production inspection method and electronic equipment, and the method comprises the steps: feeding back inspection page data of a to-be-inspected task in response to a received inspection request of the to-be-inspected task sent by an executor terminal, so as to display an inspection record page based on the inspection page data in the executor terminal, and the inspection record information and the to-be-inspected task are correspondingly stored in response to the inspection record information submitted by the executor in the inspection record page, so that online inspection and recording of each inspection task in the whole vehicle production process, such as spot inspection of first, middle and last pieces, spot inspection of an error-proofing device, spot inspection of security disaster prevention and the like, are realized; the executor can directly check the inspection record page through the terminal without printing a paper table or manually filling in the paper table, so that the inspection efficiency is greatly improved, the inspection time consumption is reduced, in addition, the inspection record information filled by the executor on line can be checked and analyzed at any time after being stored, and the management difficulty of whole vehicle production is greatly reduced.

Description

Technical Field

[0001] The present application relates to the technical field of complete vehicle production, and in particular to a complete vehicle production inspection method and electronic equipment. Background Art

[0002] A large number of process records need to be retained during vehicle production. Currently, the electronic rate accounts for 34.7% of all archived records; among them, stamping engineering accounts for 48.5%, welding engineering accounts for 17.6%, painting engineering accounts for 41.9%, and final assembly engineering accounts for 30.7%.

[0003] In the existing technology, it is usually necessary to manually sort out the same business of each factory, identify scenarios such as random inspection of the first, middle and last pieces, inspection of error-proofing devices, print paper forms, fill in records, transmit for review, collect and summarize, organize data, etc. The whole process consumes more than 35,000 hours each year, which not only leads to low efficiency and long time consumption of vehicle inspection, but also increases the difficulty of management. Summary of the invention

[0004] In view of this, the purpose of this application is to propose a vehicle production inspection method and electronic equipment to solve the problems of low efficiency, long time consumption and high management difficulty of vehicle production inspection in the prior art.

[0005] Based on the above purpose, the present application provides a vehicle production inspection method, including:

[0006] In response to receiving a check request for the task to be checked sent by the performer terminal, feeding back the check page data of the task to be checked to the performer terminal, so that the performer terminal displays the check record page based on the check page data;

[0007] In response to detecting the inspection record information submitted by the executor in the inspection record page, the inspection record information is stored correspondingly to the task to be inspected.

[0008] Optionally, the task to be inspected includes a first, second, and last piece sampling inspection task, and the method further includes:

[0009] In response to receiving the material scanning information sent by the executor terminal, determining the associated information of the stamping part to be inspected based on the material scanning information;

[0010] Sending the creation page data to the executor terminal so that the executor terminal displays the task creation page, wherein the task creation page includes the associated information of the stamping parts to be inspected and the task time item of the first, middle and last piece sampling inspection task;

[0011] In response to detecting the filled-in information of the task time item submitted by the executor in the task creation page, a first, middle and last piece sampling inspection task of the stamping parts to be inspected is established for the executor.

[0012] Optionally, the task to be inspected includes an error-proofing device inspection task, and the method further includes:

[0013] Acquire error-proofing device ledger data, wherein the error-proofing device ledger data includes each error-proofing device data and the data activation status and device inspection status corresponding to the error-proofing device data;

[0014] Based on the error-proofing device data, the data activation status and device inspection status corresponding to the error-proofing device data, the inspection frequency and shift information of each error-proofing device, the error-proofing device inspection task of each error-proofing device is established and the corresponding executor is determined.

[0015] Optionally, the task to be inspected includes a security and disaster prevention inspection task, and the method further includes:

[0016] Obtain security and disaster prevention ledger data and vehicle production plan data, wherein the security and disaster prevention ledger data includes data of each fire prevention project and data activation status corresponding to the fire prevention project data, and the vehicle production plan data includes vehicle information of each vehicle to be produced;

[0017] Based on the fire prevention project data, the data activation status corresponding to each fire prevention project data, the vehicle information of each vehicle to be produced, the inspection frequency and shift information of each fire prevention project, a security and disaster prevention inspection task for each vehicle to be produced is established and the corresponding executor is determined.

[0018] Optionally, the method further includes:

[0019] If the inspection record information of the error-proofing device inspection task contains data describing the abnormality, an abnormality confirmation reminder message is sent to the abnormality reminder terminal;

[0020] In response to receiving confirmation data fed back by the abnormality reminder terminal in response to the abnormality confirmation reminder message, writing the confirmation data into the inspection record information, and sending a maintenance reminder message to the corresponding maintenance worker terminal according to the maintenance person information in the confirmation data;

[0021] In response to receiving the maintenance data fed back by the maintenance worker terminal in response to the maintenance reminder message, a maintenance confirmation reminder message is sent to the abnormality reminder terminal.

[0022] Optionally, the method further includes:

[0023] If the inspection record information of the security and disaster prevention inspection task contains data describing anomalies, or if there are quality problems in the downstream vehicle inspection system, a countermeasure reminder message is sent to the countermeasure person terminal;

[0024] In response to receiving the countermeasure data fed back by the countermeasure person terminal in response to the countermeasure reminder message, the countermeasure data is written into the inspection record information or stored corresponding to the quality problem, and a countermeasure confirmation reminder message is sent to the confirmation recipient terminal.

[0025] Optionally, the method further includes:

[0026] Obtaining each vehicle problem recorded in the downstream vehicle inspection system;

[0027] Determine whether there is a vehicle problem that is the same as the preset problem. If so, determine the vehicle problem that is the same as the preset problem as a quality problem in the downstream vehicle inspection system.

[0028] Optionally, after storing the inspection record information in correspondence with the task to be inspected, the method further includes:

[0029] Update the task status of the task to be inspected based on the inspection record information;

[0030] The method further comprises:

[0031] In response to receiving an inspection status viewing request sent by the administrator terminal, generating a task map based on the positions corresponding to each task to be inspected;

[0032] The task map is sent to the administrator terminal, and the task status of each task to be inspected is sent to the administrator terminal, so that the administrator terminal displays the task map and displays the task status of each task to be inspected in the task map.

[0033] Optionally, the method further includes:

[0034] In response to receiving a first-in-last inspection analysis request sent by an administrator terminal, stamping part statistics information of each stamping part to be inspected is generated based on the inspection record information of each first-in-last inspection task, and the stamping part statistics information is sent to the administrator terminal for display; or,

[0035] In response to receiving an error prevention inspection analysis request sent by an administrator terminal, generating error prevention device statistical information based on the inspection record information of each error prevention device inspection task, and sending the error prevention device statistical information to the administrator terminal for display; or,

[0036] In response to receiving a disaster prevention inspection and analysis request sent by an administrator terminal, generating security disaster prevention statistical information based on the inspection record information of each security disaster prevention inspection task, and sending the security disaster prevention statistical information to the administrator terminal for display;

[0037] Among them, the stamping parts statistical information includes at least one of the straight pass rate, scrap rate and rework rate, the error-proofing device statistical information includes at least one of the error-proofing device type, inspection frequency, task completion rate and abnormal handling rate, and the security and disaster prevention statistical information includes at least one of the disaster prevention project type, inspection frequency, task completion rate and abnormal closure rate.

[0038] Based on the same purpose, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, a method provided in any embodiment of the present application is implemented.

[0039] From the above, it can be seen that the vehicle production inspection method provided by the present application, in response to receiving the inspection request of the task to be inspected sent by the executor terminal, feeds back the inspection page data of the task to be inspected to the executor terminal, so as to display the inspection record page based on the inspection page data in the executor terminal, and then in response to detecting the inspection record information submitted by the executor in the inspection record page, stores the inspection record information corresponding to the task to be inspected. Based on this method, the executor can directly view the inspection record page through the terminal without printing a paper form, and the executor can also fill in the inspection record information into the page through the terminal without printing the form and then filling it in the paper form, thereby realizing online inspection and recording of various inspection tasks in the vehicle production process, such as random inspection of the first, middle and last pieces, inspection of error-proofing devices, security and disaster prevention inspection, etc., which greatly improves the inspection efficiency and reduces the time consumption of inspection. In addition, the inspection record information filled in online by the executor can be viewed and analyzed at any time after storage, which greatly reduces the management difficulty of vehicle production. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0041] Figure 1 A flow chart of a vehicle production inspection method provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of first, middle and last item management provided in an embodiment of the present application;

[0043] Figure 3 A flow chart of first, middle and last piece sampling inspection provided in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of error-proofing device management provided in an embodiment of the present application;

[0045] Figure 5 A flowchart of an error-proofing device inspection provided in an embodiment of the present application;

[0046] Figure 6 A schematic diagram of a security and disaster prevention management provided in an embodiment of the present application;

[0047] Figure 7 A flowchart of a security and disaster prevention inspection provided in an embodiment of the present application;

[0048] Figure 8 A schematic diagram of a vehicle production management system provided in an embodiment of the present application;

[0049] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0051] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0052] Before the method provided in the embodiment of the present application is described in detail, the technical problem solved by the method is described first. In the prior art, for vehicle production, it is usually necessary to manually sort out the same business of each factory, identify the three scenarios of first, middle and last piece sampling, error prevention device inspection, and security and disaster prevention inspection, covering before, during and after production. These business operations require printing paper forms, and then manually filling in records, transmitting and checking, collecting and summarizing, and sorting data, which consumes more than 35,000 hours each year and increases management difficulty.

[0053] Therefore, in order to solve the above problems, an embodiment of the present application provides a vehicle production inspection method, which can realize online inspection and recording of various inspection tasks in the vehicle production process. The executor can directly view the inspection record page on the terminal and fill in the inspection record information on the page through the terminal. There is no need to print the form and fill it in the paper form, which greatly improves the inspection efficiency, reduces the inspection time, and reduces the management difficulty of vehicle production.

[0054] Figure 1 This is a flow chart of a vehicle production inspection method provided in an embodiment of the present application, which can be executed by a vehicle production management system. Figure 1 As shown, the vehicle production inspection method provided in the embodiment of the present application includes the following steps:

[0055] S110 . In response to receiving a verification request for the task to be verified sent by the executor terminal, feeding back verification page data of the task to be verified to the executor terminal, so that the executor terminal displays a verification record page based on the verification page data.

[0056] Among them, the tasks to be inspected can be the first, middle and last piece random inspection tasks, error-proofing device inspection tasks or security and disaster prevention inspection tasks.

[0057] Specifically, the first, middle and last piece sampling task can refer to the executors of the stamping project to conduct sampling inspections on the first, middle and last pieces of each batch of stamped parts during the production process to determine the qualified status of the stamped parts in this batch. Among them, stamped parts are metal workpieces processed by stamping technology. The first piece sampling inspection refers to the inspection of the first or first few pieces of stamped parts at the beginning of production; the middle piece sampling inspection refers to the random sampling of some stamped parts during the production process to inspect; the last piece sampling inspection refers to the inspection of the last or last few pieces of stamped parts when the production is about to end.

[0058] The error-proofing device inspection task may refer to the inspection of the error-proofing devices used before punching, welding, painting, and general engineering production according to a certain period (such as daily, weekly, or monthly frequency) and standard, in order to understand the effectiveness of the facilities and ensure that abnormalities are discovered and resolved in a timely manner; among them, the error-proofing device is a verification facility added to ensure the correct production of vehicles, including device types, system types, identification types, etc.

[0059] Security and disaster prevention inspection tasks refer to the completion confirmation management carried out during the production process in order to prevent and reduce the risk of vehicle spontaneous combustion. Disaster prevention items are inspected in welding and general engineering production on a daily, weekly, and monthly basis to understand the qualifications of operating personnel and the correctness of assembly, and to ensure that abnormalities are discovered and resolved in a timely manner.

[0060] Among them, for the first, second and last piece sampling inspection tasks, the corresponding first, second and last piece sampling inspection tasks can be assigned to each executor in advance based on the production plan of the stamping parts; or, when the executor scans the QR code or barcode, the first, second and last piece sampling inspection task can be created for the executor.

[0061] In a specific implementation, the tasks to be inspected include first, second and last piece sampling inspection tasks, and the method provided in the embodiment of the present application further includes the following steps:

[0062] Step 11: in response to receiving the material scanning information sent by the executor terminal, determining the associated information of the stamping part to be inspected based on the material scanning information;

[0063] Step 12: Sending creation page data to the executor terminal so that the executor terminal displays the task creation page, wherein the task creation page includes the associated information of the stamping parts to be inspected and the task time item of the first, middle and last piece sampling inspection task;

[0064] Step 13: In response to detecting the filled-in information of the task time item submitted by the executor in the task creation page, a first, middle and last piece sampling inspection task of the stamping parts to be inspected is established for the executor.

[0065] The material scanning information may be the scanning result of the material coding QR code or the scanning result of the material coding barcode. The material coding QR code or material coding barcode may be printed and generated after the basic data of the first, middle and last items is maintained.

[0066] Exemplarily, the basic data maintenance of the first, middle and last parts can be that the workshop technicians maintain the produced stamping parts in combination with the stamping parts BOM (Bill of Materials) and the inspection benchmark book, and maintain the inspection items and inspection standards of the first, middle and last parts of each batch of stamping parts in the system, which is used for the executor's terminal inspection benchmark and the judgment of the inspection results of each part. After maintenance, the material coding QR code or material coding barcode of the stamping part can be printed, and the material coding QR code or material coding barcode can be pasted on site to support subsequent scanning to obtain the related information of the stamping parts and reduce manual entry.

[0067] Specifically, the executor can perform random inspections of the first, middle and last stamping parts through the executor terminal (such as the executor's mobile phone). In step 11, enter the first, middle and last inspection main table, scan the material code QR code or material code barcode through the executor terminal, and after receiving the material scanning information sent by the executor terminal, the system can obtain the associated information of the stamping parts to be inspected. Among them, the associated information of the stamping parts to be inspected includes part code, part name, product model and product name.

[0068] Furthermore, in step 12, the system can send page creation data to the executor terminal, so that the terminal displays the task creation page based on the data, and displays the associated information of the stamping parts to be inspected and the task time items of the first, second and last piece sampling task in the task creation page. The task time items include date and shift.

[0069] After the executor's terminal displays the task creation page, in step 13, the executor can fill in the task time item in the task creation page displayed on the executor's terminal, and then the system can establish a first, second, and last piece sampling inspection task for the stamping parts to be inspected for the executor based on the filled-in information submitted for the task time item and combined with the associated information of the stamping parts to be inspected. It should be noted that in the process of establishing the first, second, and last piece sampling inspection task, the executor can also take a photo of the steel coil label and upload it through the executor's terminal, and then the system can automatically generate the document number, identification number, etc. of the first, second, and last piece sampling inspection task.

[0070] Through the above steps 11 to 13, the executor can scan the code through the executor terminal to realize the establishment of the first, second and last piece sampling inspection task, without manually filling in the part code, part name and other information, which can improve the efficiency of creating the tasks to be inspected. Of course, in addition to scanning the code to obtain the above information, the executor can also trigger the creation of a new control. The system displays the first, second and last piece inspection main table through the executor terminal, and then the executor enters the above task time items and part codes, part names and other information in the main table, and realizes the creation of the first, second and last piece sampling inspection task after saving.

[0071] The above-mentioned implementation method describes the establishment of the first, second and last piece random inspection task. In addition to the first, second and last piece random inspection task, in an embodiment of the present application, for the error-proofing device inspection task, the error-proofing device inspection task can be established for the executor based on the scanning information sent by the executor terminal; or, the inspection plan can be generated in advance based on the ledger and other data of the error-proofing device, and the corresponding error-proofing device inspection task can be assigned to each executor.

[0072] In another specific implementation, the task to be inspected includes an error-proofing device inspection task, and the method provided in the embodiment of the present application further includes the following steps:

[0073] Step 21, obtaining error-proofing device ledger data, wherein the error-proofing device ledger data includes each error-proofing device data and the data activation status and device inspection status corresponding to the error-proofing device data;

[0074] Step 22: Based on the data of each error proofing device, the data activation status and device inspection status corresponding to each error proofing device data, the inspection frequency of each error proofing device, and the shift information, establish the error proofing device inspection task for each error proofing device and determine the corresponding executor.

[0075] Among them, the error-proofing device ledger data can be the ledger data maintained in the system by the workshop error-proofing interface person based on the on-site error-proofing cases, including device categories, system categories, sign categories, and other categories to form an error-proofing list. The error-proofing device ledger data can be used to view the error-proofing resume and generate inspection plans.

[0076] Specifically, the error-proofing device ledger data is composed of the data of each error-proofing device, including the workshop, line, team, post, position, shift, vehicle series, error-proofing device name, error-proofing principle, etc., and each piece of data can have corresponding data activation status and device inspection status. Among them, the data activation status is used to describe whether the data is enabled during the generation of the inspection plan, and the device inspection status is used to describe whether the corresponding error-proofing device participates in the inspection.

[0077] In step 21, the system can pull the error-proofing device ledger data pre-maintained by the workshop error-proofing interface person. Further, in step 22, the system can obtain the shift information and the inspection frequency of each error-proofing device. Among them, the shift information may include the attendance shifts in the factory calendar and the shift positions in the beat management. The inspection frequency may be maintained in the system in advance by the workshop error-proofing interface person, or the inspection frequency may be automatically determined according to the type of error-proofing device, or the inspection frequency may be maintained through a separate frequency record table.

[0078] Specifically, in step 22, the system can generate a spot check plan for the day based on the data of each error-proofing device, the data activation status (enabled or not activated) and device spot check status (yes or no) corresponding to each error-proofing device data, the spot check frequency of each error-proofing device, and the shift information. For example, the spot check plan for the day can be generated regularly at 6:30 every day. The generated spot check plan includes the spot check tasks of each error-proofing device and the executors corresponding to each task.

[0079] Through the above steps 21 and 22, it is possible to create error-proofing device inspection tasks for each error-proofing device and assign corresponding executors based on the error-proofing device's ledger, attendance shifts, shift positions and other data without manual assignment, thereby ensuring the efficiency and accuracy of task assignment and avoiding omissions and wrong assignments caused by manual assignment.

[0080] It should be noted that after establishing the error-proofing device inspection tasks for each error-proofing device and determining the corresponding executors, the system can push each error-proofing device inspection task to the corresponding executor terminal before the start of the shift.

[0081] The above-mentioned implementation method describes the establishment of the first, second and last piece random inspection tasks and the error-proofing device inspection tasks. In addition to the first, second and last piece random inspection tasks and the error-proofing device inspection tasks, in an embodiment of the present application, for the security and disaster prevention inspection tasks, an inspection plan can be generated in advance based on the ledger of security and disaster prevention items and other data, and corresponding security and disaster prevention inspection tasks can be assigned to each executor.

[0082] In another specific implementation, the task to be inspected includes a security and disaster prevention inspection task, and the method provided in the embodiment of the present application further includes the following steps:

[0083] Step 31, obtaining security disaster prevention ledger data and vehicle production plan data, wherein the security disaster prevention ledger data includes data of each fire prevention project and data activation status corresponding to the fire prevention project data, and the vehicle production plan data includes vehicle information of each vehicle to be produced;

[0084] Step 32: Based on the data of each fire prevention project, the data activation status corresponding to each fire prevention project data, the vehicle information of each vehicle to be produced, the inspection frequency of each fire prevention project and the shift information, establish the security and disaster prevention inspection tasks for each vehicle to be produced and determine the corresponding executors.

[0085] Among them, the vehicle production plan data can be the data pulled by the system from the upstream MES system (Manufacturing Execution System), and the vehicle production plan data can describe the vehicle information of each vehicle to be produced, such as VIN (Vehicle Identification Number), frame number, vehicle series, etc. The vehicle production plan data can be used to generate inspection plans, select vehicle series when creating security and disaster prevention and error prevention device ledgers, check the production plan for the day during security and disaster prevention inspections, and verify vehicle information during security and disaster prevention inspections.

[0086] Security and disaster prevention ledger data can be ledger data maintained by the workshop disaster prevention interface person according to the fire hazard items. Security and disaster prevention ledger data can be used for management sedimentation, project sharing and the generation of inspection plans.

[0087] Specifically, the security disaster prevention ledger data is composed of data of various disaster prevention projects. The disaster prevention project data includes workshops, lines, teams, workstations, positions, shift positions, vehicle series, disaster prevention projects, etc., and each piece of data can have a corresponding data activation status. The data activation status is used to describe whether the data is enabled during the generation of the inspection plan.

[0088] In step 31, illustratively, the system can obtain the vehicle production plan data of the MES system from the business middle station at 7:30 every day, and pull the security disaster prevention ledger data pre-maintained by the workshop disaster prevention interface person. Further, in step 32, the system can obtain the shift information and the inspection frequency of each fire prevention project. Among them, the shift information may include the attendance shifts in the factory calendar and the shift positions in the beat management. The inspection frequency can be maintained in the system in advance by the workshop disaster prevention interface person, or the inspection frequency can be automatically determined according to the type of disaster prevention project, or the inspection frequency can be maintained through a separate frequency record table.

[0089] Specifically, in step 32, the system can generate a spot check plan for the day based on the data of each fire prevention project, the data activation status (activated or not activated) corresponding to each fire prevention project data, the vehicle information of each vehicle to be produced, the spot check frequency of each fire prevention project, and the shift information. For example, the spot check plan for the day can be generated at 5:30. The generated spot check plan includes the security and disaster prevention spot check tasks of each fire prevention project and the executors corresponding to each task.

[0090] Through the above steps 31 and 32, it is possible to create various security and disaster prevention inspection tasks and assign corresponding executors based on security and disaster prevention ledgers, attendance shifts, shift positions, vehicle production plans and other data without manual assignment, thereby ensuring the efficiency and accuracy of task assignment and avoiding omissions and wrong assignments caused by manual assignment.

[0091] It should be noted that after establishing various security disaster prevention inspection tasks and determining the corresponding executors, the system can push the error prevention device inspection tasks to the corresponding executor terminals according to the disaster prevention task reminder time set in the data dictionary. Among them, the data dictionary can be used to maintain the reminder time of various tasks, the reminder time of various tasks not completed in time, etc.

[0092] In the embodiment of the present application, after creating each task to be inspected, the executor may initiate an inspection of the task to be inspected on the executor terminal to generate an inspection request for the task to be inspected.

[0093] For example, for the first, second and last piece random inspection task, after the executor (inspector) scans the code to create the task to be inspected, the executor can be allowed to view the detailed list information. If it is detected that the executor needs to view the detailed list information, an inspection request for the task to be inspected can be generated and sent to the system.

[0094] For the inspection tasks of error-proofing devices, after assigning executors to the corresponding tasks to be inspected, the executors (on-site supervisors, team leaders or employees) can receive task reminder messages on the terminal. If the executor's terminal detects that the executor has viewed the task reminder message, an inspection request for the task to be inspected can be generated and sent to the system. At the same time, the inspection function page can be entered to display the daily inspection plan for the individual's post.

[0095] For security and disaster prevention inspection tasks, after assigning executors to the corresponding tasks to be inspected, the executors (production supervisors or team leaders) can receive task reminder messages on the terminal. If the executor's terminal detects that the executor has viewed the task reminder message, an inspection request for the task to be inspected can be generated and sent to the system. At the same time, you can also enter the inspection function page to display the production plan for the day, as well as the daily inspection plan for the line or team.

[0096] Specifically, after receiving the inspection request sent by the executor terminal, the system can feed back the inspection page data to the executor terminal, so that the executor terminal can display the inspection record page based on the data. For example, for the first, middle and last piece inspection task, the inspection page data can be the detailed table data, and the inspection record page can be the inspection detailed table, including the inspection information of the first piece, the middle piece and the last piece.

[0097] S120. In response to detecting the inspection record information submitted by the executor in the inspection record page, the inspection record information is stored correspondingly to the task to be inspected.

[0098] Specifically, after the inspection record page is displayed on the executor's terminal, the executor may fill in the inspection record information on the inspection record page.

[0099] For example, for the first, middle and last piece sampling task, the inspector can click "first piece" to determine the inspection dimension (first batch or daily) based on whether the batch of stamping parts is the first batch, and the corresponding inspection items are displayed in different inspection dimensions; the inspector can click "middle piece" to confirm the number of pieces first, and then fill in the inspection items. After filling in, you can click "add middle piece" to fill in the next inspection; the inspector can click "last piece" to fill in the inspection according to the inspection items. After filling in the detailed table, you can return to the main table to continue filling in the total production quantity, total qualified quantity, rework quantity, scrapped quantity, etc. If the inspection is abnormal, you need to fill in the description of the unqualified problem, problem analysis, countermeasures, and disposal measures. After filling in, it can be submitted to the system or temporarily saved.

[0100] It should be noted that for the first, middle and last piece sampling tasks, since the inspection items for different types of stamping parts are different, the inspection items for each stamping part can also be maintained in the system in advance. For example, the workshop technician can trigger the new control, maintain the inspection items, and select the inspection type, such as judgmental, numerical, and dual-value. Then the system can display the corresponding basic data maintenance template according to the type selected by the workshop technician. Among them, the judgment type requires further maintenance of inspection items and judgment criteria, and checking the inspection category (receiving, intermediate, and last piece, multiple selections are allowed); the numerical type requires further maintenance of inspection items, special characteristics, units, reference values, minimum values, maximum values, and inspection types; the dual-value type requires maintenance of inspection items, special characteristics, units, directions, reference values, minimum values, maximum values, and inspection categories.

[0101] For the error-proofing device inspection task, the executor clicks on "Standard Picture" to enlarge and view the standard photo, and checks whether it is standard according to the inspection standard. If no is selected, the number of abnormalities and description of abnormalities must be filled in. In addition, you can also choose whether to conduct trial and error. If yes is selected, the executor's terminal will display the trial and error standard. The executor clicks on the photo to upload the on-site picture, which can be submitted to the system only after completion.

[0102] For security and disaster prevention inspection tasks, the executor can enter the inspection results and fill in whether they comply. If not, the executor can click to take a photo and upload the on-site picture, which can be submitted to the system only after completion.

[0103] Specifically, after the executor fills in the inspection record information through the executor terminal and submits it, the system can store the inspection record information corresponding to the task to be inspected, so as to facilitate subsequent review, record viewing, data analysis, etc.

[0104] For example, for the first, second and last piece sampling tasks, the quality team leader can review the inspection record information after each executor submits it. Specifically, the quality team leader can click on the inspection item to enter the main table or detailed table page, view the unqualified inspection items in the detailed table, the abnormal description, cause, countermeasures, disposal strategy and other information in the main table, provide the team leader with approval basis, and the quality team leader can also view historical review data. In addition, the system can support the progress of each first, second and last piece sampling task, and display the progress of the first, second and last piece sampling task from multiple states such as pending submission, pending review, passed, and rejected. In the corresponding state, you can fill in the search conditions, such as part code, part name, product model, department, workshop / section, line, inspection date, etc., to query the inspection records and details under the corresponding conditions.

[0105] For error-proofing device inspection tasks, the system can also support quality control and workshop managers to view the inspection or maintenance progress of error-proofing devices in workshops and production lines. Quality control and workshop managers can find the functional path to enter the query page to display device-related data under personal authority. For security and disaster prevention inspection tasks, the system can also support quality control and workshop managers to view the inspection and abnormal handling progress of security and disaster prevention items in workshops and production lines. Quality control and workshop managers can find the functional path to enter the query page to display security and disaster prevention-related data under personal authority.

[0106] The vehicle production inspection method provided in the embodiment of the present application, in response to receiving an inspection request for the task to be inspected sent by the executor terminal, feeds back the inspection page data of the task to be inspected to the executor terminal, so as to display the inspection record page based on the inspection page data in the executor terminal, and then in response to detecting the inspection record information submitted by the executor in the inspection record page, stores the inspection record information corresponding to the task to be inspected. Based on this method, the executor can directly view the inspection record page through the terminal without printing a paper form, and the executor can also fill in the inspection record information into the page through the terminal without printing the form and then filling it in the paper form, thereby realizing online inspection and recording of various inspection tasks in the whole vehicle production process, such as random inspection of the first, middle and last pieces, inspection of error-proofing devices, security and disaster prevention inspection, etc., which greatly improves the inspection efficiency and reduces the time consumption of inspection. In addition, the inspection record information filled in online by the executor can be viewed and analyzed at any time after being stored, which greatly reduces the management difficulty of the whole vehicle production.

[0107] In the embodiment of the present application, considering that the number of tasks to be inspected may be large, a task map may be generated to facilitate administrators (such as team leaders, workshop managers, etc.) to view the progress of each task. In some embodiments, after the inspection record information is stored corresponding to the task to be inspected, the method further includes: updating the task status of the task to be inspected based on the inspection record information;

[0108] The method provided in the embodiment of the present application also includes:

[0109] In response to receiving an inspection status viewing request sent by the administrator terminal, a task map is generated based on the positions corresponding to each task to be inspected; the task map is sent to the administrator terminal, and the task status of each task to be inspected is sent to the administrator terminal, so that the administrator terminal displays the task map and displays the task status of each task to be inspected in the task map.

[0110] Specifically, after each task to be inspected is inspected, that is, after the inspection record information is stored corresponding to the task to be inspected, the task status of the task to be inspected can be updated, such as changing from unfinished to normal inspection, abnormal inspection or timed inspection.

[0111] Furthermore, if the system receives an inspection status viewing request sent by the administrator terminal, the system can generate a task map according to the positions corresponding to each task to be inspected. For example, the task map is composed of multiple sections, each module corresponds to a position, and contains all tasks to be inspected under the position.

[0112] Specifically, the system can send the task map and the task status of each task to be inspected to the administrator terminal, and then the administrator terminal can display the sections of each position in the task map and display the task status of the tasks to be inspected under each section.

[0113] In addition to displaying the task map in the form of panels as mentioned above, you can also obtain a distribution map of the positions according to their locations, and then directly feed the distribution map back to the administrator terminal as a task map. While the administrator terminal displays the distribution map, it can also display the task status of the tasks to be inspected for each position on the map.

[0114] Through the above implementation, it is convenient for administrators to view the progress of tasks to be inspected under each post, and it can help administrators quickly understand the inspection status of error-proofing devices or security and disaster prevention inspection status of each post.

[0115] In addition to generating task maps to help administrators view at a glance the inspection status of error-proofing devices or security disaster prevention inspections at each post, data analysis can also be performed based on the inspection record information of each task to be inspected that has been completed, so as to conduct statistical analysis on the first, middle and last random inspections, error-proofing device inspections and security disaster prevention inspections.

[0116] In some embodiments, the method provided in the embodiments of the present application further includes:

[0117] In response to receiving a first-in-last inspection analysis request sent by an administrator terminal, stamping part statistics information of each stamping part to be inspected is generated based on the inspection record information of each first-in-last inspection task, and the stamping part statistics information is sent to the administrator terminal for display; or,

[0118] In response to receiving an error prevention inspection analysis request sent by an administrator terminal, generating error prevention device statistical information based on the inspection record information of each error prevention device inspection task, and sending the error prevention device statistical information to the administrator terminal for display; or,

[0119] In response to receiving a disaster prevention inspection and analysis request sent by an administrator terminal, generating security disaster prevention statistical information based on the inspection record information of each security disaster prevention inspection task, and sending the security disaster prevention statistical information to the administrator terminal for display;

[0120] Among them, the statistical information of stamping parts includes at least one of the straight pass rate, scrap rate and rework rate, the statistical information of error-proofing devices includes at least one of the type of error-proofing devices, inspection frequency, task completion rate and abnormal handling rate, and the statistical information of security and disaster prevention includes at least one of the type of disaster prevention projects, inspection frequency, task completion rate and abnormal closure rate.

[0121] Specifically, the administrator can initiate a first-middle-last inspection analysis request, an error prevention analysis request, or a disaster prevention analysis request through the terminal, and the system can respond to the above request, obtain corresponding statistical information and send the statistical information to the administrator terminal for display.

[0122] If the system receives a request for first, second, and last inspection analysis, it can generate at least one of the straight pass rate, scrap rate, and rework rate based on the inspection record information of each first, second, and last inspection task. The straight pass rate can be the proportion of workpieces that pass the inspection normally, the scrap rate can be the proportion of workpieces that are inspected abnormally and determined to be scrapped, and the rework rate can be the proportion of workpieces that are inspected abnormally and reworked.

[0123] If the system receives an error proofing analysis request, it can generate at least one of the error proofing device type, inspection frequency, task completion rate, and abnormality handling rate based on the inspection record information of each error proofing device inspection task. The task completion rate can be the proportion of tasks completed by inspection, and the abnormality handling rate can be the proportion of error proofing devices that handle abnormal inspections.

[0124] If the system receives a disaster prevention inspection analysis request, it can generate at least one of the disaster prevention project type, inspection frequency, task completion rate, and abnormal closure rate based on the inspection record information of each security disaster prevention inspection task. The abnormal closure rate can be the ratio between the number of closures of inspection abnormalities and the total number of inspection abnormalities.

[0125] Through the above implementation mode, data analysis of the first, middle and last random inspections, error-proofing device inspections and security and disaster prevention inspections can be realized. Through system data analysis, it is convenient to subsequently reduce the frequency of random inspections of projects that have been operating normally for a long time, improve inspection efficiency, ensure the effectiveness of random inspections, and identify problems that occur frequently, manage such problems and prevent them from happening again.

[0126] In addition to providing an inspection record solution for inspection tasks, the embodiments of the present application can also provide solutions for first, middle and last piece management, error prevention device management and security and disaster prevention management.

[0127] In an embodiment of the present application, the management of first, middle and last parts may include basic data maintenance, part inspection, part review, inspection record query and data analysis, mainly by configuring the inspection frequency and measurement standards to realize the first, middle and last part inspection, and perform error prevention and warning on the inspection record information; and, by using calculations such as the inspection quantity and rework quantity, automatically count the pass rate and rework rate of each batch of parts (stamping parts).

[0128] like Figure 2 As shown, Figure 2 A schematic diagram of the first, middle and last parts management provided for the embodiment of the present application, wherein the workshop technician can first establish the basic data of the parts and process capability analysis, and the inspector can perform inspections according to the parts and inspection parameters during the code scanning inspection, and push the abnormalities to the production personnel for repair, and the production personnel push the disposal records to the team leader for review, and finally the workshop technician can also check the pass rate and rework rate. In addition, the management can monitor the progress at any time.

[0129] Figure 3 A flowchart of the first, second and last piece sampling inspection provided in the embodiment of this application is provided. The personnel involved in the first, second and last piece sampling inspection include production enterprise quality control specialists, workshop technicians, workshop inspectors, workshop quality team leaders, workshop repair staff, workshop production staff and other roles. The business covers stamping parts parameter maintenance, first, second and last piece sampling inspection, abnormal handling, inspection review, and progress monitoring. Figure 3 As shown, workshop technicians can maintain stamping part parameters, that is, basic part data maintenance. After production and processing, workshop inspectors can perform spot checks on the first, second and last parts of each batch of stamping parts. If the spot check is normal, the subsequent inspection data review can be continued. If the spot check is abnormal, the unqualified parts can be reworked and monitored. After the unqualified parts are reworked, a repair record will be generated and the inspection data review will continue. If it is rejected, it will be returned for re-inspection of the first, second and last parts. If it passes, the workshop quality team leader can trace the record, the workshop technician can perform on-site inspection, and the production enterprise quality control specialist can share the inspection parameters and conduct maturity review.

[0130] In an embodiment of the present application, error-proofing device management may include error-proofing ledger maintenance, inspection plan management, device inspection, inspection map management, exception confirmation, device maintenance, progress query, data analysis, etc., mainly by establishing an error-proofing ledger and usage history, combining the factory calendar and inspection frequency, generating an inspection plan and pushing it to on-site personnel, and converting the plan information into a job distribution map to achieve task-driven and status monitoring; and using terminal notifications (such as DingTalk) to provide layered reminders on job progress and push exceptions to achieve personnel job warnings.

[0131] Among them, the inspection plan management can be to generate an inspection plan and push the error-proofing device inspection task to the corresponding executor before the start of the shift. In addition, if the inspection is not completed, the system can push a warning of non-inspection to the executor every 10 minutes before the start of the shift (such as 90 minutes before), and push a reminder to the executor, the executor's team leader, and the warning person set in the message recipient before the start of the shift (such as 10 minutes).

[0132] Among them, progress query can be that quality control and workshop managers can view the inspection progress and maintenance progress of the error-proofing devices in workshops and production lines. Specifically, quality control and workshop managers can find the function path to enter the query page to display the relevant data of the error-proofing devices under personal authority. Data analysis can be that the management monitors the types of error-proofing, inspection frequency, process execution and abnormal closure trends of each factory. Inspection map management can be that the system generates a default error-proofing inspection map for all workshops and production lines on the day according to the inspection plan, which can clearly view the inspection status and maintenance status of the error-proofing devices in each position; tasks of different status can also be distinguished by color, for example, they can be divided into four categories: unfinished (gray), normal inspection (green), overtime inspection (yellow), and abnormal inspection (red).

[0133] Among them, the device inspection includes feeding back the inspection page data of the task to be inspected to the executor terminal according to the inspection request, and storing the inspection record information submitted by the executor in the inspection record page; the device inspection also includes that when the inspection record information submitted by the executor indicates that the inspection is abnormal, the system can send an abnormality confirmation reminder to the on-duty production team leader. Abnormal confirmation can be the team leader confirming the status of the abnormal device inspected or the abnormal device under maintenance. Device maintenance can be the maintenance of the device confirmed by the team leader as abnormal.

[0134] Specifically, with respect to abnormality confirmation and device maintenance, in some implementations, the method provided in the embodiments of the present application further includes the following steps:

[0135] Step 41: If the inspection record information of the error-proofing device inspection task contains data describing the abnormality, an abnormality confirmation reminder message is sent to the abnormality reminder terminal;

[0136] Step 42, in response to receiving the confirmation data fed back by the abnormality reminder terminal in response to the abnormality confirmation reminder message, write the confirmation data into the inspection record information, and send a maintenance reminder message to the corresponding maintenance worker terminal according to the maintenance person information in the confirmation data;

[0137] Step 43: In response to receiving the maintenance data fed back by the maintenance worker terminal in response to the maintenance reminder message, a maintenance confirmation reminder message is sent to the abnormality reminder terminal.

[0138] Among them, in step 41, if the inspection record information contains data describing the abnormality, that is, the error-proofing device is inspected abnormally, the system can send an abnormality confirmation reminder message to the abnormality reminder terminal, so that the abnormality reminder can view the received abnormality confirmation reminder message through the terminal, enter the abnormality confirmation function page, and display the personal data to be confirmed.

[0139] Exemplarily, the person who reminds the abnormality can select "Information to be confirmed" to enter the inspection details page, confirm the actual status of the device according to the abnormal description, and select "Confirm abnormality" or "Confirm normal". A filling window will pop up according to the selected button. If it is confirmed to be normal, you need to fill in the normal description and upload a picture. Click confirm to complete the data saving and feedback to the system as confirmation data; if it is confirmed to be abnormal, you need to fill in the abnormal description, response measures, maintenance personnel, and upload a picture. Click confirm to complete the data saving and feedback to the system as confirmation data.

[0140] Furthermore, in step 42, if the system receives confirmation data fed back by the abnormality reminder terminal, the confirmation data can be stored in the inspection record information. If a maintenance person is specified therein, a maintenance reminder message can be sent to the corresponding maintenance personnel terminal based on the maintenance person information, so that the maintenance personnel terminal can view the received maintenance reminder message, enter the device maintenance function interface, and perform maintenance according to the device abnormality description. Click the "Maintenance" button, a filling window will pop up, in which the maintenance method is entered, and after submission, it will be fed back to the system as maintenance data for storage.

[0141] Furthermore, in step 43, if the system receives maintenance data fed back by the maintenance personnel terminal, it can store the maintenance data in the inspection record information and send a maintenance confirmation reminder message to the abnormality reminder terminal so that the abnormality reminder can confirm the error-proofing device for the maintenance.

[0142] Through the above steps 41 to 43, the error-proofing device inspection task can be carried out. After the inspection is completed, the error-proofing devices with inspection abnormalities and the error-proofing devices for maintenance and repair can be confirmed. There is no need to transmit documents offline, and the entire process from abnormality to repair can be completed online, which greatly improves the efficiency of handling abnormal error-proofing devices.

[0143] Figure 4A schematic diagram of error-proofing device management provided for an embodiment of the present application, wherein the workshop interface person can establish an error-proofing device ledger, based on which an inspection plan is generated to push the inspection task to the executor. After the employee conducts the inspection, the error-proofing device with abnormal inspection can be pushed to the squad leader for confirmation. At the same time, if there are new employees among the employees, a new employee warning message can also be pushed to the squad leader to help the squad leader focus on the inspection records of the new employees to avoid erroneous inspections. After the squad leader confirms the abnormality, the abnormality can be pushed to the security maintenance. After the security maintenance repairs the abnormal error-proofing device, a repair reminder will be sent to the squad leader, and the squad leader can confirm whether the repair has passed. In addition, the management can monitor the progress at any time.

[0144] Figure 5 A flowchart of error-proofing device inspection is provided for the embodiment of this application. The personnel involved in error-proofing device inspection include production enterprise quality control specialist, factory quality control specialist, workshop error-proofing interface person, workshop security, workshop production team leader, workshop production supervisor, workshop production staff, etc. The business covers the establishment of error-proofing device ledger, new employee warning, inspection task push, device inspection record, device maintenance, progress monitoring, etc. Figure 5 As shown, the workshop interface person can establish a ledger based on the error prevention improvement, among which the factory quality control specialist can regularly spot check the update of the error prevention ledger; then the workshop employees can conduct the next device inspection, among which the workshop team leader or supervisor can pay attention to the personnel changes at any time, and take over the post instead of the inspection when the position is vacant; if the inspection is abnormal, the workshop team leader or supervisor will confirm the inspection, and the workshop interface person can monitor the execution of the inspection. If the inspection is normal, it will be directly filed. After the workshop team leader or supervisor confirms the inspection, if it is confirmed to be abnormal, the workshop security will formulate countermeasures, and the workshop security will repair it. If it is confirmed to be normal, it will be directly filed. After the workshop security repairs, the maintenance data will be archived, the workshop interface person can trace the records, the factory quality control specialist can perform on-site inspection, and the production enterprise quality control specialist can share the error prevention improvement data and conduct maturity audits.

[0145] In the embodiments of the present application, security and disaster prevention management may include disaster prevention ledger maintenance, MES production plan interface, inspection plan management, disaster prevention item inspection, inspection map management, QMS (Quality Management System, vehicle quality inspection system) problem acquisition setting, quality problem list, inspection abnormality countermeasures, abnormal countermeasures confirmation, progress query, data analysis, etc., mainly through combining the production plan of MES, terminal scanning code inspection of operating vehicles, and accurate record; as well as early warning of personnel changes in disaster prevention posts, automatic increase in the number of inspection vehicles, and support for team leaders' targeted management; as well as online countermeasures and confirmation of inspection problems, process interlocking, and improved assembly quality.

[0146] Among them, inspection plan management can be to generate an inspection plan and push the security and disaster prevention inspection tasks to the executor according to the time maintained in the data dictionary; and if the team leader fails to complete the inspection, the system can also push reminders to the production team leader and the warning person according to the reminder time maintained in the data dictionary and the message recipients who have not completed the inspection.

[0147] Among them, the inspection map management can be that the system generates a default disaster prevention inspection map for all workshops and production lines on the day according to the inspection plan, so that the inspection status of each disaster prevention item can be viewed at a glance. Progress query can be that the quality control and workshop managers can view the inspection and abnormal handling progress of the security disaster prevention items of the workshop and production line. Find the function path to enter the query page to display the device data under personal authority. Data analysis can be that the management monitors the disaster prevention item type, inspection frequency, process execution and problem closure trend of each factory.

[0148] Among them, the QMS problem acquisition setting can be that the workshop disaster prevention interface person maintains the quality problem search conditions according to the quality problems that may occur in the fire prevention items, and is used for vehicle problem synchronization in the QMS system. The quality problem list can be that the system obtains data in the QMS system every hour according to the set quality range, and searches for the maintained quality problems in the data of the QMS system to generate a quality problem list.

[0149] Among them, the countermeasures for inspection anomalies can be the countermeasures taken by the line technicians for inspection anomalies and quality problems, and records are generated after the countermeasures are taken. The confirmation of abnormal countermeasures can be the confirmation of the data that has been countermeasured by the workshop interface personnel.

[0150] Specifically, with respect to the QMS problem acquisition settings and the quality problem list, in some implementations, the method provided in the embodiments of the present application further includes the following steps:

[0151] Obtain each vehicle problem recorded in the downstream vehicle inspection system;

[0152] Determine whether there is a vehicle problem that is the same as the preset problem. If so, determine the vehicle problem that is the same as the preset problem as a quality problem in the downstream vehicle inspection system.

[0153] Among them, the preset problems can be the quality problems that may occur in the fire prevention items maintained by the disaster prevention interface person in the workshop in the system, such as missing plugs in the fuel line, missing grounding of the transmission grounding harness assembly, detachment of the engine harness clip, etc. The various vehicle problems recorded in the downstream vehicle inspection system can be the various vehicle problems recorded in the downstream QMS during the vehicle inspection process.

[0154] Specifically, each vehicle problem can be obtained from the downstream vehicle inspection system according to a preset period (such as 1 hour). Further, it can be determined whether there are vehicle problems identical to the preset problems among the obtained vehicle problems. If so, all vehicle problems identical to the preset problems can be determined as quality problems, and then a quality problem list can be generated based on the factory codes, parts, defects, etc. corresponding to all quality problems.

[0155] After the quality problem list is generated, the system can also search for the countermeasure recipients and confirmation recipients maintained in the message recipients according to the workshop and line, determine the countermeasure recipients and confirmers of the problem, and push messages awaiting countermeasures and confirmation.

[0156] Through the above implementation method, it is possible to connect with the downstream QMS, associate vehicle quality issues, achieve data linkage and business drive, further avoid quality problems, and solve operational difficulties.

[0157] In addition, with respect to spot checking of abnormal countermeasures and confirmation of abnormal countermeasures, in some implementations, the method provided in the embodiments of the present application further includes the following steps:

[0158] Step 51: If the inspection record information of the security and disaster prevention inspection task contains data describing an abnormality, or if there is a quality problem in the downstream vehicle inspection system, a countermeasure reminder message is sent to the countermeasure person terminal;

[0159] Step 52: in response to receiving the countermeasure data fed back by the countermeasure person terminal in response to the countermeasure reminder message, write the countermeasure data into the inspection record information or store it corresponding to the quality problem, and send a countermeasure confirmation reminder message to the confirmation recipient terminal.

[0160] Among them, in step 51, if the inspection record information of the security and disaster prevention inspection task contains data describing abnormalities, the line technician needs to take countermeasures for the inspection abnormalities, and a countermeasure reminder message can be sent to the countermeasure person terminal (i.e., the line technician's terminal). Alternatively, if there are quality problems in the downstream vehicle inspection system, the line technician needs to take countermeasures for the quality problems, and a countermeasure reminder message can be sent to the countermeasure person terminal (i.e., the line technician's terminal).

[0161] Furthermore, the countermeasure person can view the countermeasure reminder message, enter the problem countermeasure page, display personal data to be countermeasured, select the data to be countermeasured to enter the inspection details page or the problem details page, assign or take countermeasures on the page, select the disposal method and then pop up the corresponding window, fill in the content in the window, and after saving, all the filled in information will be fed back to the system as countermeasure data.

[0162] Specifically, after receiving the countermeasure data, the system can store it in the inspection record information, or store the countermeasure data in correspondence with the quality problem, and then send a countermeasure confirmation reminder message to the confirmed recipient terminal. It should be noted that if assignment is required, the system can push the countermeasure information to the assignor. If countermeasures are taken, the system pushes a confirmation reminder to the workshop confirmed recipient maintained in the message recipient.

[0163] After receiving the countermeasure confirmation reminder message, the recipient can view it, enter the countermeasure confirmation page, display the personal data to be confirmed, select the data to be confirmed, enter the confirmation details page, select pass or reject according to the actual confirmation result, and select the disposal method. The corresponding window pops up, fill in the content and click the confirmation button to submit it to the system for saving. If you reject it, the system will push a rejection reminder to the countermeasure holder's terminal after saving.

[0164] Through the above steps 51 and 52, it is possible to implement countermeasures for inspection anomalies of security and disaster prevention, countermeasures for downstream QMS quality issues, and confirmation of anomaly countermeasures, which can further improve the management process of security and disaster prevention. There is no need to transmit documents offline, and the efficiency of security and disaster prevention management can be further improved through online processing.

[0165] Figure 6 A schematic diagram of a security and disaster prevention management provided for an embodiment of the present application, wherein the workshop interface person can establish a disaster prevention item ledger. At the same time, the system can also pull the production plan from the MES, generate a spot inspection plan based on the production plan and the ledger, and push the spot inspection task to the corresponding squad leader, who will conduct the spot inspection. If there is a change point in the position, the squad leader can be warned, and the squad leader can also increase the number of inspection vehicles in the terminal operation. After completing the spot inspection, the squad leader will pass the assembly, product, and design problems that arise during the spot inspection to the technician for countermeasures. After the technician has taken countermeasures, he will send a confirmation reminder to the squad leader, and after the squad leader confirms the countermeasures, he will send a countermeasure reminder to the workshop interface person. In addition, the vehicle inspection system can also associate vehicle quality issues with the system, and the workshop interface person will analyze and confirm the problems. In addition, the management can monitor the progress at any time.

[0166] Figure 7 A flowchart of a security disaster prevention inspection is provided for the embodiment of this application. The personnel involved in the security disaster prevention inspection include production enterprise quality control specialists, factory quality control specialists, workshop disaster prevention contact persons, workshop technicians, workshop production team leaders, workshop production supervisors, workshop production staff, etc. The business covers the establishment of security disaster prevention project ledgers, personnel change warnings, inspection task push, vehicle inspection records, abnormal handling, progress monitoring, etc. Figure 7As shown, the workshop disaster prevention interface person can establish a ledger based on the fire prevention items, and the factory quality control specialist can regularly spot check the update of the ledger. After the workshop production staff performs production and assembly, the factory quality control specialist can also understand the personnel changes. The workshop production team leader or supervisor can inspect the vehicle disaster prevention items (usually 1-5 units), and the workshop disaster prevention interface person will monitor the inspection and execution. If the inspection is normal, it will be directly archived. If the inspection is abnormal, it will be pushed to the workshop technician for assembly reason analysis, and the analysis results will be sent to the workshop disaster prevention interface person for confirmation. If the workshop disaster prevention interface person rejects it, it will be returned to the workshop technician for assembly reason analysis again. If the workshop disaster prevention interface person confirms it, it will be directly archived. The workshop disaster prevention interface person can trace the records, the factory quality control specialist can perform on-site inspection, and the production enterprise quality control specialist can share disaster prevention improvement data and conduct maturity audits.

[0167] The above-mentioned first, middle and last piece management, error-proofing device management and security and disaster prevention management have the following technical effects:

[0168] 1. Standardize business processes through system processes, unify business management standards and implementation methods for first, middle and last piece sampling, error-proofing device inspection, and security and disaster prevention inspection, support vertical management and control of production enterprises, factories and workshops at three levels, and solve problems such as difficulty in standardization; 2. Employees, team leaders, supervisors, business controllers and managers work together on the same platform to reduce and optimize process nodes, record the entire process online, and solve problems such as difficulty in improving efficiency. It has been applied to actual business and has completed more than 150,000 sampling inspections and more than 5 million inspections; 3. Connect the upstream MES system and downstream QMS system data, link production plans and vehicle quality issues, realize data linkage and business drive, avoid data and business islands, and solve operational difficulties.

[0169] It should be noted that the method of the embodiment of the present application can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present application, and the multiple devices will interact with each other to complete the described method.

[0170] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0171] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application also provides a vehicle production management system, and the above-mentioned vehicle production inspection method can be executed by the vehicle production management system. Figure 8 As shown, Figure 8 A schematic diagram of a vehicle production management system provided for an embodiment of the present application. The system can be divided into three layers: front, middle, and back. The front layer can include a user layer and an application layer. The user layer can mainly be oriented to business managers, operators, security guards, technicians, team leaders, supervisors, and leadership. For example, business managers use PCs to supervise business processes, on-site operators, security guards, technicians, team leaders, supervisors, etc. use mobile phones to handle business, and leadership can view the operation results through I analysis. The application layer can provide services such as first, middle, and last piece management, error-proofing device management, and security and disaster prevention management through Springboot and Springcloud.

[0172] The middle platform layer can include the business layer, the middle platform capability layer and the technical platform layer. Among them, the middle platform capability layer can introduce public capabilities and human organizations such as SSO (Single Sign-On) and BPM (Business Process Management), as well as business capabilities such as MES daily plans to reduce the workload of development. At the same time, it can also precipitate and enter the data of the first, middle and last pieces, the data of error-proofing devices, and the data of security and disaster prevention to support the use of other systems or reports. The technical platform layer can include a unified authentication platform, an open platform, the Great Wall Cloud, a code quality management platform, a continuous integration platform, a distributed task scheduling platform, a software testing platform, an API interface management platform, a mobile application publishing platform, etc.

[0173] The backend layer can include the backend system and the resource layer. Among them, the backend system can include the human resources system, MES system, QMS system, EDM (Email Direct Marketing) system, G-BOM (Global Bill of Materials) system, MPM (Manufacturing Process Management) system and DingTalk platform. The resource layer can be composed of resources such as computers, MySQL, and mobile phones. The backend layer supports the stable operation of the system through a unified technical architecture, data architecture, and resource reserves.

[0174] The vehicle production management system provided by this application can use Nginx load balancing technology, Springcloud microservice framework, MySQL and OSS (Operation Support System) storage to form an overall high-availability architecture. Multi-tenant data deployment is used to meet the management demands of multiple factories, and Nginx and other technologies are used to achieve negative balancing of application services, providing users with agile and efficient digital management tools. Automated deployment is carried out through the performance platform, combined with Tianjing or APM (Application Performance Management) platform to monitor the operating status of servers and services to ensure the stable operation of the system.

[0175] The system of the above-mentioned embodiment is used to implement the corresponding vehicle production inspection method in any of the above-mentioned embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0176] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the vehicle production inspection method described in any of the above embodiments is implemented.

[0177] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Fig. 9 A specific electronic device hardware structure is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0178] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0179] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0180] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0181] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0182] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0183] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0184] The electronic device of the above-mentioned embodiment is used to implement the corresponding vehicle production inspection method in any of the above-mentioned embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0185] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the vehicle production inspection method described in any of the above embodiments.

[0186] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0187] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the vehicle production inspection method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0188] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0189] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0190] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0191] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A vehicle production inspection method, characterized in that: include: In response to receiving a check request for the task to be checked sent by the performer terminal, feeding back the check page data of the task to be checked to the performer terminal, so that the performer terminal displays the check record page based on the check page data; In response to detecting the inspection record information submitted by the executor in the inspection record page, the inspection record information is stored correspondingly to the task to be inspected.

2. The method according to claim 1, characterized in that The tasks to be inspected include first, second and last piece sampling inspection tasks, and the method further includes: In response to receiving the material scanning information sent by the executor terminal, determining the associated information of the stamping part to be inspected based on the material scanning information; Sending the creation page data to the executor terminal so that the executor terminal displays the task creation page, wherein the task creation page includes the associated information of the stamping parts to be inspected and the task time item of the first, middle and last piece sampling inspection task; In response to detecting the filled-in information of the task time item submitted by the executor in the task creation page, a first, middle and last piece sampling inspection task of the stamping parts to be inspected is established for the executor.

3. The method according to claim 1, characterized in that: The task to be inspected includes a task of spot checking an error-proofing device, and the method further includes: Acquire error-proofing device ledger data, wherein the error-proofing device ledger data includes each error-proofing device data and the data activation status and device inspection status corresponding to the error-proofing device data; Based on the error-proofing device data, the data activation status and device inspection status corresponding to the error-proofing device data, the inspection frequency and shift information of each error-proofing device, the error-proofing device inspection task of each error-proofing device is established and the corresponding executor is determined.

4. The method according to claim 1, characterized in that: The tasks to be inspected include security and disaster prevention inspection tasks, and the method further includes: Obtain security and disaster prevention ledger data and vehicle production plan data, wherein the security and disaster prevention ledger data includes data of each fire prevention project and data activation status corresponding to the fire prevention project data, and the vehicle production plan data includes vehicle information of each vehicle to be produced; Based on the fire prevention project data, the data activation status corresponding to each fire prevention project data, the vehicle information of each vehicle to be produced, the inspection frequency and shift information of each fire prevention project, a security and disaster prevention inspection task for each vehicle to be produced is established and the corresponding executor is determined.

5. The method according to claim 3, characterized in that: The method further comprises: If the inspection record information of the error-proofing device inspection task contains data describing the abnormality, an abnormality confirmation reminder message is sent to the abnormality reminder terminal; In response to receiving confirmation data fed back by the abnormality reminder terminal in response to the abnormality confirmation reminder message, writing the confirmation data into the inspection record information, and sending a maintenance reminder message to the corresponding maintenance worker terminal according to the maintenance person information in the confirmation data; In response to receiving the maintenance data fed back by the maintenance worker terminal in response to the maintenance reminder message, a maintenance confirmation reminder message is sent to the abnormality reminder terminal.

6. The method according to claim 4, characterized in that The method further comprises: If the inspection record information of the security and disaster prevention inspection task contains data describing anomalies, or if there are quality problems in the downstream vehicle inspection system, a countermeasure reminder message is sent to the countermeasure person terminal; In response to receiving the countermeasure data fed back by the countermeasure person terminal in response to the countermeasure reminder message, the countermeasure data is written into the inspection record information or stored corresponding to the quality problem, and a countermeasure confirmation reminder message is sent to the confirmation recipient terminal.

7. The method according to claim 6, characterized in that The method further comprises: Obtaining each vehicle problem recorded in the downstream vehicle inspection system; Determine whether there is a vehicle problem that is the same as the preset problem. If so, determine the vehicle problem that is the same as the preset problem as a quality problem in the downstream vehicle inspection system.

8. The method according to claim 1, characterized in that After storing the inspection record information in correspondence with the task to be inspected, the method further includes: Update the task status of the task to be inspected based on the inspection record information; The method further comprises: In response to receiving an inspection status viewing request sent by the administrator terminal, generating a task map based on the positions corresponding to each task to be inspected; The task map is sent to the administrator terminal, and the task status of each task to be inspected is sent to the administrator terminal, so that the administrator terminal displays the task map and displays the task status of each task to be inspected in the task map.

9. The method according to claim 1, characterized in that: The method further comprises: In response to receiving a first-in-last inspection analysis request sent by an administrator terminal, stamping part statistics information of each stamping part to be inspected is generated based on the inspection record information of each first-in-last inspection task, and the stamping part statistics information is sent to the administrator terminal for display; or, In response to receiving an error prevention inspection analysis request sent by an administrator terminal, generating error prevention device statistical information based on the inspection record information of each error prevention device inspection task, and sending the error prevention device statistical information to the administrator terminal for display; or, In response to receiving a disaster prevention inspection and analysis request sent by an administrator terminal, generating security disaster prevention statistical information based on the inspection record information of each security disaster prevention inspection task, and sending the security disaster prevention statistical information to the administrator terminal for display; Among them, the stamping parts statistical information includes at least one of the straight pass rate, scrap rate and rework rate, the error-proofing device statistical information includes at least one of the error-proofing device type, inspection frequency, task completion rate and abnormal handling rate, and the security and disaster prevention statistical information includes at least one of the disaster prevention project type, inspection frequency, task completion rate and abnormal closure rate.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 9 is implemented.

Images