Order verification methods, devices, equipment and computer-readable storage media

Abstract

A method, apparatus, device, and computer-readable storage medium for order verification are disclosed, relating to the field of order verification technology. The method includes, before production scheduling of a target order, determining at least one first local identifier and at least one first part identifier based on a central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table; filtering a target local identifier from all first local identifiers based on the date range and usage range of the local identifiers corresponding to the target order, and filtering a target part identifier from all first part identifiers based on the date range and usage range of the part identifiers corresponding to the target order; diagnosing whether the local identifiers of the target order are missing or duplicated based on a preset first code of the target local identifiers, and diagnosing whether the part identifiers of the target order are missing or duplicated based on a preset second code of the target part identifiers. This application enables the verification of manufacturing parameters or bill of materials data before production.

Description

Technical Field

[0001] This application relates to the field of order verification technology, specifically to an order verification method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] With increasing market competition and diversified customer demands, companies have adjusted their production processes and organizational methods to adapt to increasingly personalized order requirements. In the current production model, order-based production has replaced the traditional inventory-based production model and become the mainstream.

[0003] However, existing order verification technologies only identify instantiated vehicle model codes and cannot verify manufacturing parameters or BOM (Bill of Materials) data before production. This leads to missing parts or information gaps during the order production stage, affecting on-time delivery and production efficiency. Therefore, providing an order verification method to verify manufacturing parameters or BOM data before production is a pressing issue that needs to be addressed. Summary of the Invention

[0004] This application provides an order verification method, apparatus, device, and computer-readable storage medium, which can verify manufacturing parameters or BOM data before production.

[0005] In a first aspect, embodiments of this application provide an order verification method, the order verification method comprising:

[0006] Before production scheduling for a target order, at least one first local identifier and at least one first part identifier are determined based on the central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order.

[0007] Target local flags are selected from all first local flags based on the local flag date range and local flag usage range corresponding to the target order; and target part flags are selected from all first part flags based on the part flag date range and part flag usage range corresponding to the target order.

[0008] The system uses a preset first code based on the target local identifier to diagnose whether there are missing or duplicate local identifiers in the target order, and a preset second code based on the target part identifier to diagnose whether there are missing or duplicate part identifiers in the target order.

[0009] In conjunction with the first aspect, in one implementation, the step of filtering the target local identifier from all first local identifiers based on the local identifier date range and local identifier usage range corresponding to the target order includes:

[0010] For each first local flag, determine whether the date of the first local flag is within a preset local flag date range and whether the scope of use of the first local flag is within a preset local flag usage range;

[0011] If so, then the first local identifier is used as the target local identifier;

[0012] If not, then the first local identifier will not be used as the target local identifier.

[0013] In conjunction with the first aspect, in one implementation, the step of filtering the target part marker from all first part markers based on the part marker date range and part marker usage range corresponding to the target order includes:

[0014] For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use.

[0015] If so, then the first part identifier shall be used as the target part identifier;

[0016] If not, then the first part identifier will not be used as the target part identifier.

[0017] In conjunction with the first aspect, in one implementation, the method of diagnosing whether local identifiers in a target order are missing or duplicated using a preset code based on the target local identifier includes:

[0018] Determine whether there exists a first local identifier in the target order that has the same code as a preset first code, wherein the preset first code is a parameter value of the local identifier;

[0019] If so, it is determined that the local flag in the target order is not lost, and if the number of the first local flag is greater than 1, it is determined that there is a duplicate local flag in the target order.

[0020] If not, then the local flag in the target order is determined to be missing.

[0021] In conjunction with the first aspect, in one implementation, the method of diagnosing whether there are missing or duplicate part markers in a target order based on a preset code for the target part marker includes:

[0022] Determine whether there is a second part identifier in the target order that has the same code as the preset second code, wherein the preset second code is the part number of the part identifier;

[0023] If so, it is determined that the part markers in the target order are not lost, and if the number of second part markers is greater than 1, it is determined that there is a duplicate part marker problem in the target order.

[0024] If not, then the part markings in the target order are deemed missing.

[0025] In conjunction with the first aspect, in one embodiment, the method further includes:

[0026] If there are missing or duplicate local identifiers and part identifiers in the target order, the target order will be graded based on the preset processing level corresponding to the local identifier or part identifier. The preset processing level includes at least one of mandatory level, mandatory inspection level and pre-inspection level. The mandatory level is used to indicate that the target order will not be produced, the mandatory inspection level is used to indicate that the target order is frozen, and the pre-inspection level is used to indicate that the target order has risks.

[0027] Secondly, embodiments of this application provide an order verification device, the order verification device comprising:

[0028] The first processing module is used to determine at least one first local identifier and at least one first part identifier based on the central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table before the target order is scheduled for production. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order.

[0029] The second processing module is used to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order, and to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order.

[0030] The third processing module is used to diagnose whether there are missing or duplicate local identifiers in the target order based on the preset first code of the target local identifier, and to diagnose whether there are missing or duplicate part identifiers in the target order based on the preset second code of the target part identifier.

[0031] In conjunction with the second aspect, in one implementation, the second processing module is specifically used for:

[0032] For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use.

[0033] If so, then the first part identifier shall be used as the target part identifier;

[0034] If not, then the first part identifier will not be used as the target part identifier.

[0035] Thirdly, embodiments of this application provide an order verification device, which includes a processor, a memory, and an order verification program stored in the memory and executable by the processor, wherein when the order verification program is executed by the processor, it implements the steps of the order verification method as described in any of the foregoing claims.

[0036] Fourthly, embodiments of this application provide a computer-readable storage medium storing an order verification program, wherein when the order verification program is executed by a processor, it implements the steps of the order verification method as described in any of the preceding claims.

[0037] The beneficial effects of the technical solutions provided in this application include:

[0038] Before producing a target order, at least one first local identifier (for managing the configuration coding information of the vehicle order), at least one first part identifier (for managing the manufacturing parameters of the vehicle order), and at least one first part identifier (for managing the key part information of the vehicle order) can be determined based on the central identifier corresponding to the target order (used to manage the configuration coding information of the vehicle order), a preset local identifier mapping table, and a preset part identifier mapping table. The target local identifier is selected from all first local identifiers based on the date range and usage scope of the local identifier corresponding to the target order, and the target part identifier is selected from all first part identifiers based on the date range and usage scope of the part identifier. This ensures that only valid identifiers that meet the requirements of the current order are selected, thereby improving data accuracy. Furthermore, the preset first code of the target local identifier is used to automatically diagnose whether there are missing or duplicate local identifiers in the target order; similarly, the preset second code of the target part identifier is used to diagnose missing or duplicate part identifiers. This application, by establishing a systematic identifier management and screening mechanism, reduces the risk of missing parts or information during the order production stage, and improves the on-time delivery and production efficiency of orders. Attached Figure Description

[0039] Figure 1 This is a flowchart illustrating an embodiment of the order verification method of this application;

[0040] Figure 2 For this application Figure 1 A detailed flowchart of step S20;

[0041] Figure 3 For this application Figure 1 A detailed flowchart of step S30;

[0042] Figure 4 This is a schematic diagram of the architecture of an embodiment of the order verification device of this application;

[0043] Figure 5 This is a schematic diagram of the hardware structure of the order verification device involved in the embodiments of this application. Detailed Implementation

[0044] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0045] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.

[0046] Order-based production: refers to a company starting to produce products only after receiving orders from users.

[0047] Inventory production refers to a company starting to produce products or provide services before receiving customer orders or knowing the customer demand.

[0048] Instantiated vehicle model code: A code consisting of a set of numbers and letters that represents different equipment, optional features, and colors of vehicle models.

[0049] BOM: Bill of Materials, which in the automotive industry generally refers to the detailed list of all vehicles.

[0050] Manufacturing parameters: Parameters that guide industrial equipment (such as filling and turning) during the vehicle production process.

[0051] Synchronous parts: Parts supplied in a synchronous manner. Synchronous supply means that when a vehicle needs to install a certain part on the production line, the part can be delivered to the assembly station on time.

[0052] Function code: Used to indicate the technical function of a part in the whole vehicle, and can consist of 8 to 10 characters.

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0054] In a first aspect, embodiments of this application provide an order verification method.

[0055] In one embodiment, reference is made to Figure 1 , Figure 1This is a flowchart illustrating an embodiment of the order verification method of this application. Figure 1 As shown, the order verification methods include:

[0056] Step S10: Before scheduling production for the target order, at least one first local identifier and at least one first part identifier are determined based on the central identifier corresponding to the target order, the preset local identifier mapping table, and the preset part identifier mapping table. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order.

[0057] As an example, in this embodiment, a preset local identifier mapping table stores a one-to-one correspondence between multiple sets of local identifiers and central identifiers, and a preset part identifier mapping table stores a one-to-one correspondence between multiple sets of part identifiers and central identifiers. The preset local identifier mapping table and the preset part identifier mapping table can be determined according to actual needs and are not limited here. It is understood that the target order has a unique central identifier that has been preset in advance. Therefore, before the target order is scheduled for production, the central identifier of the target order can be used and the production of the whole vehicle can be effectively managed through the preset local identifier mapping table and the part identifier mapping table.

[0058] It should be noted that, as shown in Table 1, the central identifier is an identifier used to identify and manage the configuration coding information of the complete vehicle order, ensuring that the configuration of each component and system meets the design requirements during the production process, and facilitating the tracking of the vehicle's construction; as shown in Table 2, the first local identifier is used to manage the manufacturing parameters related to the complete vehicle order, ensuring that each manufacturing parameter in the order production process is carried out in accordance with the established specifications and requirements; as shown in Table 3, the first part identifier is used to identify key parts in the complete vehicle order, ensuring that key parts are given priority management and quality control during the production process to guarantee the safety and functionality of the complete vehicle.

[0059] Table 1. Central Symbols and Their Descriptions

[0060] Central logo illustrate CB0DA4* Four-door sedan CDCO02* Rear electric

[0061] It should be understood that CB0DA4* in Table 1 represents a four-door sedan, and CDCO02* represents a rear electric vehicle.

[0062] Table 2 Local Signs and Their Descriptions

[0063] Local sign illustrate MVIN*** VIN ER12*** Add transmission fluid

[0064] It should be understood that MVIN*** in Table 2 stands for VIN (Vehicle Identification Number), and ER12*** is for adding transmission fluid.

[0065] Table 3 Part Markings and Descriptions

[0066] Part marking function code Part Name 8001*** R1A01001 Rear bumper assembly 8030*** E3115001 Right front wheel assembly

[0067] Among them, the part markings correspond one-to-one with the function codes in the vehicle BOM; it should be understood that in Table 3, 8001*** is the rear bumper assembly, and its corresponding function code is R1A01001.

[0068] Specifically, the first local identifier and the first part identifier corresponding to the target order can be quickly determined through the central identifier of the target order, as well as the local identifier mapping table and the part identifier mapping table. By managing the central identifier, local identifier, and part identifier, the efficiency, quality, and resource utilization of vehicle production can be effectively improved, bringing a competitive advantage to manufacturing enterprises.

[0069] Step S20: Filter the target local flag from all first local flags based on the local flag date range and local flag usage range corresponding to the target order, and filter the target part flag from all first part flags based on the part flag date range and part flag usage range corresponding to the target order.

[0070] As an example, in this embodiment, the date range refers to a specific time interval consisting of a start date and an end date, and the scope of use refers to the specific conditions or scenarios to which the mark applies. Therefore, the first local mark that meets the scope of use requirements within this time interval is the target local mark. The selection of target part marks is similar and will not be elaborated upon here.

[0071] Specifically, target local flags that meet the criteria can be filtered from all first local flags based on the date range and usage scope of the local flags associated with the target order, ensuring that the selected local flags match the time requirements and applicable scenarios of the target order. Similarly, target part flags that meet the criteria can be filtered from all first part flags based on the date range and usage scope of the part flags corresponding to the target order, ensuring that the selected part flags accurately reflect the requirements of the target order.

[0072] Step S30: Based on the preset first code of the target local identifier, diagnose whether there is a missing or duplicate problem of the local identifier in the target order, and based on the preset second code of the target part identifier, diagnose whether there is a missing or duplicate problem of the part identifier in the target order.

[0073] As an example, in the embodiments of this application, the preset first code is a unique identifier (parameter value of the local mark) used to identify a specific target local mark, and the preset second code is a unique identifier (part number of the part mark) used to identify a specific target part mark. The specific value of the preset first code can be determined according to the specific type of the local mark, and the specific value of the preset second code can be determined according to the specific type of the part mark. For example, if the local mark is a general assembly vehicle, its corresponding preset first code can be MVEH (i.e., the parameter value of the general assembly vehicle is MVEH); if the part mark is a rear bumper assembly, its corresponding preset second code can be 8001 (i.e., the part number of the rear bumper assembly is 8001).

[0074] Specifically, the code of the local identifier can be compared one by one with the preset first code. If the code of the local identifier in the target order is not found, it is determined that the local identifier in the target order is missing; conversely, if the code of the same local identifier appears multiple times, it is determined that the local identifier in the target order is duplicated. The same principle applies to determining the missing or duplicate of part identifiers, which will not be elaborated here.

[0075] This application determines at least one first local identifier (for managing manufacturing parameters of the vehicle order) and at least one first part identifier (for managing key part information of the vehicle order) before production of a target order, based on a central identifier corresponding to the target order (used to manage configuration coding information of the vehicle order), a preset local identifier mapping table, and a preset part identifier mapping table. Target local identifiers are selected from all first local identifiers based on the date range and usage scope of the local identifiers corresponding to the target order, and target part identifiers are selected from all first part identifiers based on the date range and usage scope of the part identifiers. This ensures that only valid identifiers that meet the requirements of the current order are selected, thereby improving data accuracy. Furthermore, the preset first code of the target local identifier automatically diagnoses whether there are missing or duplicate local identifiers in the target order; similarly, the preset second code of the target part identifier diagnoses whether there are missing or duplicate part identifiers. By establishing a systematic identifier management and screening mechanism, this application reduces the risk of missing parts or information during the order production stage, improving on-time delivery and production efficiency.

[0076] Furthermore, in one embodiment, reference is made to Figure 2 As shown, the step of filtering the target local flag from all first local flags based on the local flag date range and local flag usage range corresponding to the target order includes:

[0077] Step S201: For each first local flag, determine whether the date of the first local flag is within a preset local flag date range and whether the usage scope of the first local flag is within a preset local flag usage scope;

[0078] Step S202: If yes, then use the first local identifier as the target local identifier;

[0079] Step S203: If not, then the first local identifier is not used as the target local identifier.

[0080] As an example, in the embodiments of this application, the preset local mark date range and the preset local mark usage range can be determined according to actual needs and are not limited here; for example, the preset local mark (transmission fluid filling) date range is [A, B], where A is the start date and B is the end date; the preset local mark (transmission fluid filling) usage range is automatic transmission.

[0081] Specifically, this can be done by checking whether the date of the first local flag is within the preset local flag date range and whether the scope of use of the first local flag is within the preset local flag usage range. If the date of the first local flag is within the local flag date range and the scope of use of the first local flag is within the local flag usage range, it means that the flag is still valid and applicable to the current order verification scenario, and the first local flag is used as the target local flag. If the date of the first local flag is not within the local flag date range or the scope of use of the first local flag is not within the local flag usage range, the first local flag may have expired or is no longer applicable and is not applicable to the current scenario, and the first local flag is not used as the target local flag.

[0082] Understandably, strict date and scope of use checks ensure that only valid and applicable local identifiers are used as target local identifiers, thereby improving the accuracy of order verification.

[0083] Further, in one embodiment, the step of filtering the target part marker from all first part markers based on the part marker date range and part marker usage range corresponding to the target order includes:

[0084] For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use.

[0085] If so, then the first part identifier shall be used as the target part identifier;

[0086] If not, then the first part identifier will not be used as the target part identifier.

[0087] As an example, in the embodiments of this application, the preset part marking date range and the preset part marking usage range can be determined according to actual needs and are not limited here; for example, the preset part marking (rear bumper assembly) date range is [C, D], where C is the start date and D is the end date; the rear bumper assembly is an important component of the automotive safety system, and its usage range is wide, applicable to various types of cars, such as all Yipai 007 models are equipped with a rear bumper assembly.

[0088] Specifically, this can be done by checking whether the date of the first part marker is within the preset part marker date range and whether the scope of use of the first part marker is within the preset part marker scope. If the date of the first part marker is within the part marker date range and the scope of use of the first part marker is within the part marker scope, it means that the marker is still valid and applicable to the current order verification scenario, and the first part marker is used as the target part marker. If the date of the first part marker is not within the part marker date range or the scope of use of the first part marker is not within the part marker scope, the first part marker may have expired or is no longer applicable and is not applicable to the current scenario, and the first part marker is not used as the target part marker.

[0089] Furthermore, in one embodiment, reference is made to Figure 3 As shown, the preset code based on the target local identifier diagnoses whether there are missing or duplicate local identifiers in the target order, including:

[0090] Step S301: Determine whether there is a first local identifier in the target order that has the same code as the preset first code, wherein the preset first code is the parameter value of the local identifier;

[0091] Step S302: If yes, then it is determined that the local flag in the target order is not lost, and if the number of the first local flag is greater than 1, then it is determined that there is a duplicate local flag in the target order;

[0092] Step S303: If not, determine that the local flag in the target order is missing.

[0093] In this exemplary embodiment, a preset first code can be compared one by one with the codes of all first local identifiers in the target order. Based on the comparison results, if a local identifier with the same parameter value as the preset first code is found, it indicates that no local identifier is missing in the target order. If multiple local identifiers with the same parameter value as the preset first code are found, it indicates that there is a duplicate local identifier problem in the target order. If no local identifier with the same parameter value as the preset first code is found, it indicates that a local identifier is missing in the target order. This embodiment can promptly identify the problem of missing or duplicate local identifiers, preventing resource waste and customer inconvenience, thereby ensuring that the products received by customers meet expectations and improving customer satisfaction.

[0094] Furthermore, in one embodiment, the method of diagnosing whether there are missing or duplicate part markers in the target order based on the preset code of the target part marker includes:

[0095] Determine whether there is a second part identifier in the target order that has the same code as the preset second code, wherein the preset second code is the part number of the part identifier;

[0096] If so, it is determined that the part markers in the target order are not lost, and if the number of second part markers is greater than 1, it is determined that there is a duplicate part marker problem in the target order.

[0097] If not, then the part markings in the target order are deemed missing.

[0098] As an example, in this embodiment of the application, the preset second code can be compared one by one with the codes of all second part markers in the target order; according to the comparison results, if a part marker with the same part number as the preset second code is found, it means that the part markers in the target order are not lost; if multiple part markers with the same part number as the preset second code are found, it means that there is a duplicate problem of part markers in the target order; if no part marker with the same part number as the preset second code is found, it means that the part markers in the target order are lost.

[0099] Furthermore, in one embodiment, the method further includes:

[0100] If there are missing or duplicate local identifiers and part identifiers in the target order, the target order will be graded based on the preset processing level corresponding to the local identifier or part identifier. The preset processing level includes at least one of mandatory level, mandatory inspection level and pre-inspection level. The mandatory level is used to indicate that the target order will not be produced, the mandatory inspection level is used to indicate that the target order is frozen, and the pre-inspection level is used to indicate that the target order has risks.

[0101] As an example, in this embodiment, the preset processing level can be determined according to actual needs and is not limited here. Preferred preset processing levels may include a mandatory level, a mandatory inspection level, and a pre-inspection level, each representing a different response measure. The mandatory level indicates that the target order cannot be produced normally; the mandatory inspection level indicates that the target order will be frozen, but can be manually unfrozen; the pre-inspection level is used to indicate potential risks in the order and suggests monitoring and evaluation. It should be noted that different flags can be preset with different processing levels according to actual needs.

[0102] Specifically, for target orders with missing or duplicate local or part markings, the target order can be graded using at least one of the pre-set mandatory, mandatory inspection, and pre-inspection levels. Corresponding error alerts can also be provided, shortening the order production cycle and improving the efficiency of order-based production.

[0103] Table 4 Examples of Errors

[0104]

[0105] Understandably, referring to Table 4, in the target order with order number 3L2X8148, the processing level corresponding to the target part marker with code 8001 (i.e., the rear bumper assembly) is mandatory inspection level. Therefore, if there is a duplicate target part marker, the target order needs to be frozen. Similarly, the processing level corresponding to the target local marker with code ER12 (i.e., transmission fluid filling) is mandatory inspection level. Therefore, if there is a missing target local marker, the target order needs to be frozen.

[0106] Secondly, embodiments of this application also provide an order verification device.

[0107] In one embodiment, reference is made to Figure 4 , Figure 4 This is a schematic diagram of the functional modules of an embodiment of the order verification device of this application. Figure 4 As shown, the order verification device includes:

[0108] The first processing module is used to determine at least one first local identifier and at least one first part identifier based on the central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table before the target order is scheduled for production. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order.

[0109] The second processing module is used to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order, and to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order.

[0110] The third processing module is used to diagnose whether there are missing or duplicate local identifiers in the target order based on the preset first code of the target local identifier, and to diagnose whether there are missing or duplicate part identifiers in the target order based on the preset second code of the target part identifier.

[0111] Furthermore, in one embodiment, the second processing module is specifically used for:

[0112] For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use.

[0113] If so, then the first part identifier shall be used as the target part identifier;

[0114] If not, then the first part identifier will not be used as the target part identifier.

[0115] Furthermore, in one embodiment, the second processing module is specifically used for:

[0116] For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use.

[0117] If so, then the first part identifier shall be used as the target part identifier;

[0118] If not, then the first part identifier will not be used as the target part identifier.

[0119] Furthermore, in one embodiment, the third processing module is specifically used for:

[0120] Determine whether there exists a first local identifier in the target order that has the same code as a preset first code, wherein the preset first code is a parameter value of the local identifier;

[0121] If so, it is determined that the local flag in the target order is not lost, and if the number of the first local flag is greater than 1, it is determined that there is a duplicate local flag in the target order.

[0122] If not, then the local flag in the target order is determined to be missing.

[0123] Furthermore, in one embodiment, the third processing module is specifically used for:

[0124] Determine whether there is a second part identifier in the target order that has the same code as the preset second code, wherein the preset second code is the part number of the part identifier;

[0125] If so, it is determined that the part markers in the target order are not lost, and if the number of second part markers is greater than 1, it is determined that there is a duplicate part marker problem in the target order.

[0126] If not, then the part markings in the target order are deemed missing.

[0127] Furthermore, in one embodiment, the third module is specifically used for:

[0128] If there are missing or duplicate local identifiers and part identifiers in the target order, the target order will be graded based on the preset processing level corresponding to the local identifier or part identifier. The preset processing level includes at least one of mandatory level, mandatory inspection level and pre-inspection level. The mandatory level is used to indicate that the target order will not be produced, the mandatory inspection level is used to indicate that the target order is frozen, and the pre-inspection level is used to indicate that the target order has risks.

[0129] This application determines at least one first local identifier (for managing manufacturing parameters of the vehicle order) and at least one first part identifier (for managing key part information of the vehicle order) before production of a target order, based on a central identifier corresponding to the target order (used to manage configuration coding information of the vehicle order), a preset local identifier mapping table, and a preset part identifier mapping table. Target local identifiers are selected from all first local identifiers based on the date range and usage scope of the local identifiers corresponding to the target order, and target part identifiers are selected from all first part identifiers based on the date range and usage scope of the part identifiers. This ensures that only valid identifiers that meet the requirements of the current order are selected, thereby improving data accuracy. Furthermore, the preset first code of the target local identifier automatically diagnoses whether there are missing or duplicate local identifiers in the target order; similarly, the preset second code of the target part identifier diagnoses whether there are missing or duplicate part identifiers. By establishing a systematic identifier management and screening mechanism, this application reduces the risk of missing parts or information during the order production stage, improving on-time delivery and production efficiency.

[0130] The functions of each module in the above-mentioned order verification device correspond to the steps in the above-mentioned order verification method embodiment, and their functions and implementation processes will not be described in detail here.

[0131] Thirdly, embodiments of this application provide an order verification device, which can be a personal computer (PC), laptop computer, server, or other device with data processing capabilities.

[0132] Reference Figure 5 , Figure 5 This is a schematic diagram of the hardware structure of the order verification device involved in the embodiments of this application. In the embodiments of this application, the order verification device may include a processor, a memory, a communication interface, and a communication bus.

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

[0134] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting components within the order verification device, as well as interfaces used for interconnecting the order verification device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

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

[0136] The processor can be a general-purpose processor, which can call the order verification program stored in memory and execute the order verification method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the order verification program is called can be referred to in the various embodiments of the order verification method of this application, and will not be repeated here.

[0137] Those skilled in the art will understand that Figure 5 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0138] Fourthly, embodiments of this application also provide a readable storage medium.

[0139] The present application has an order verification program stored on a readable storage medium, wherein when the order verification program is executed by a processor, it implements the steps of the order verification method described above.

[0140] The method implemented when the order verification procedure is executed can be referred to in the various embodiments of the order verification method of this application, and will not be repeated here.

[0141] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or devices. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0142] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0143] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

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

[0145] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0146] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0147] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. An order verification method, characterized in that, The order verification method includes: Before production scheduling for a target order, at least one first local identifier and at least one first part identifier are determined based on the central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order. Target local flags are selected from all first local flags based on the local flag date range and local flag usage range corresponding to the target order; and target part flags are selected from all first part flags based on the part flag date range and part flag usage range corresponding to the target order. The system uses a preset first code based on the target local identifier to diagnose whether there are missing or duplicate local identifiers in the target order, and a preset second code based on the target part identifier to diagnose whether there are missing or duplicate part identifiers in the target order. The method of diagnosing whether part icons in the target order are missing or duplicated based on the preset code of the target part icon includes: Determine whether there is a second part identifier in the target order that has the same code as the preset second code, wherein the preset second code is the part number of the part identifier; If so, it is determined that the part markers in the target order are not lost, and if the number of second part markers is greater than 1, it is determined that there is a duplicate part marker problem in the target order. If not, then the part markings in the target order are deemed missing.

2. The order verification method as described in claim 1, characterized in that, The process of filtering the target local flag from all first local flags based on the local flag date range and local flag usage range corresponding to the target order includes: For each first local flag, determine whether the date of the first local flag is within a preset local flag date range and whether the scope of use of the first local flag is within a preset local flag usage range; If so, then the first local identifier is used as the target local identifier; If not, then the first local identifier will not be used as the target local identifier.

3. The order verification method as described in claim 1, characterized in that, The process of filtering the target part flag from all first part flags based on the part flag date range and part flag usage range corresponding to the target order includes: For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use. If so, then the first part identifier shall be used as the target part identifier; If not, then the first part identifier will not be used as the target part identifier.

4. The order verification method as described in claim 1, characterized in that, The preset code diagnosis based on the target local identifier to determine whether there are missing or duplicate local identifiers in the target order includes: Determine whether there exists a first local identifier in the target order that has the same code as a preset first code, wherein the preset first code is a parameter value of the local identifier; If so, it is determined that the local flag in the target order is not lost, and if the number of the first local flag is greater than 1, it is determined that there is a duplicate local flag in the target order. If not, then the local flag in the target order is determined to be missing.

5. The order verification method as described in claim 1, characterized in that, The method further includes: If there are missing or duplicate local identifiers and part identifiers in the target order, the target order will be graded based on the preset processing level corresponding to the local identifier or part identifier. The preset processing level includes at least one of mandatory level, mandatory inspection level and pre-inspection level. The mandatory level is used to indicate that the target order will not be produced, the mandatory inspection level is used to indicate that the target order is frozen, and the pre-inspection level is used to indicate that the target order has risks.

6. An order verification device, characterized in that, The order verification device includes: The first processing module is used to determine at least one first local identifier and at least one first part identifier based on the central identifier corresponding to the target order, a preset local identifier mapping table, and a preset part identifier mapping table before the target order is scheduled for production. The central identifier is used to manage the configuration coding information of the vehicle order, the first local identifier is used to manage the manufacturing parameters of the vehicle order, and the first part identifier is used to manage the key parts of the vehicle order. The second processing module is used to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order, and to filter out the target part mark from all first part marks based on the part mark date range and part mark usage range corresponding to the target order. The third processing module is used to diagnose whether there are missing or duplicate local identifiers in the target order based on the preset first code of the target local identifier, and to diagnose whether there are missing or duplicate part identifiers in the target order based on the preset second code of the target part identifier.

7. The order verification device as described in claim 6, characterized in that, The second processing module is specifically used for: For each first part mark, determine whether the date of the first part mark is within a preset part mark date range and whether the scope of use of the first part mark is within a preset part mark scope of use. If so, then the first part identifier shall be used as the target part identifier; If not, then the first part identifier will not be used as the target part identifier.

8. An order verification device, characterized in that, The order verification device includes a processor, a memory, and an order verification program stored in the memory and executable by the processor, wherein when the order verification program is executed by the processor, it implements the steps of the order verification method as described in any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an order verification program, wherein when the order verification program is executed by a processor, it implements the steps of the order verification method as described in any one of claims 1 to 5.

Images