Method, system and apparatus for optimizing the claims cost recovery process

Abstract

The present application relates to a method, system and device for optimizing a claim cost recovery process. The method includes receiving a fault set corresponding to a fault code in a claim form, the fault set including one or more claim items, the one or more claim items including at least a parts claim item, for each parts claim item, classifying the parts claim item into a corresponding basket by matching the parts claim item with the attributes of multiple baskets, determining the final basket to which all the parts claim items in the fault set are finally allocated based on the types of the corresponding baskets of all the parts claim items in the fault set, determining the main cause parts among all the parts involved in the fault set, and determining the claim cost sharing scheme among the suppliers of all the parts involved in the fault set based on the determination of the main cause parts.

Description

Technical Field

[0001] The present disclosure relates to process optimization, and in particular to methods, systems and apparatus for optimizing a claims cost recovery process. Background Art

[0002] After a car is sold, if a maintenance event (such as replacement of parts) occurs during the warranty period, a warranty certificate will be generated. The dealer will provide the warranty certificate to the car manufacturer. After the car manufacturer compensates the dealer based on factors such as whether it is within the warranty period, it will recover the cost from the parts supplier. Generally, the car manufacturer will extract the warranty certificate, manually analyze each item of the warranty certificate to identify the type and cause of the fault, and determine whether to recover the cost (i.e., claim) from the parts supplier based on the responsibility determination.

[0003] The entire process is completely manual, with opaque data, low efficiency and low processing accuracy. Summary of the invention

[0004] According to some embodiments of the present application, a computer-implemented method is provided, comprising: receiving a fault set corresponding to a fault code in a claim form, the fault set including one or more claim items, the one or more claim items including at least a parts claim item; for each parts claim item, classifying the parts claim item into a corresponding basket by matching the parts claim item with attributes of multiple baskets; determining a final basket to which all the parts claim items in the fault set are ultimately allocated based on the types of corresponding baskets of all the parts claim items in the fault set; determining a main cause part among all the parts involved in the fault set; and determining a claim cost sharing plan among suppliers of all the parts involved in the fault set based on the determination of the main cause part.

[0005] In some embodiments, the one or more claim items further include a labor time / auxiliary material claim item associated with the parts claim item. Wherein, based on the determination of the main cause, the step of determining the claim cost sharing scheme among all the suppliers of the parts involved in the fault set further includes: based on the determination of the main cause, determining the sharing of the labor time / auxiliary material claim costs generated by the fault set among all the suppliers of the parts involved in the fault set.

[0006] In some embodiments, the method further includes: for each basket, generating a claim billing sheet to a supplier of the parts based on the determined claim cost sharing scheme.

[0007] In some embodiments, the method further comprises creating the basket based on a user definition of properties of the basket.

[0008] In some embodiments, the attributes of the method basket include one or more of the following: basket type; basket identifier; person in charge; main cause part; supplier code; one or more fault codes included; one or more part codes included; basket status; basket name; one or more fault codes excluded; one or more part codes excluded; repair date; production date; warranty period; vehicle series; vehicle model; and frame number.

[0009] In some embodiments, the type of basket is one of: recalled (RE); internal recalled (TA); serial defect (SD); and normal occasional (NG).

[0010] In some embodiments, for each parts claim item, the step of classifying the parts claim item into a corresponding basket by matching the parts claim item with attributes of multiple baskets further includes: determining multiple baskets into which the parts claim item may be classified by matching the parts claim item with attributes of multiple baskets; and classifying the parts claim item into a basket with the highest priority order according to the priority order of the types of the multiple baskets.

[0011] In some embodiments, when there are multiple baskets with the highest priority order, one of the multiple baskets with the highest priority order is selected as the basket into which the part claim item is classified according to the creation time.

[0012] In some embodiments, based on the types of corresponding baskets of all parts claim items in the fault set, the step of determining the final basket to which all parts claim items in the fault set are finally assigned is based on the priority order of the types of corresponding baskets of all parts claim items in the fault set.

[0013] In some embodiments, the priority of the types of baskets is in descending order of recalled (RE), internal recalled (TA), serial defect (SD), and normal occasional (NG).

[0014] In some embodiments, the method further includes: determining the main cause part among all parts involved in the failure set based on the main cause part attribute of the final basket to which all part claim items in the failure set are finally allocated.

[0015] In some embodiments, the method also includes: determining the part whose installation position is the same as the installation position represented by the fault code among all parts involved in all parts claim items as the main cause part; or determining the part with the highest price among all parts involved in all parts claim items as the main cause part.

[0016] Some other embodiments provide a computer system, comprising: one or more processors, and a memory coupled to the one or more processors, the memory storing computer-readable program instructions, which when executed by the one or more processors perform the method as described above.

[0017] According to other embodiments of the present application, a computer-readable storage medium is provided, on which computer-readable program instructions are stored. When the instructions are executed by a processor, the method described above is performed.

[0018] According to other embodiments of the present application, a quality monitoring device is provided, comprising means for implementing the operations of the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a flow chart illustrating a method performed by a computer system for optimizing a claims cost recovery process.

[0020] Figure 2 A table illustrating the relationship between claim tickets, fault codes, parts claim items, and parts is shown.

[0021] Figure 3 A table illustrating the initial results of the part claim item basketing operation is shown.

[0022] Figure 4 Another table illustrating the initial results of the part claim item basketing operation is shown.

[0023] Figure 5 A table illustrating a comparison between initial basket results and final basket results is shown.

[0024] Figure 6 FIG. 4 is a schematic diagram showing a general hardware environment in which a device according to an embodiment of the present disclosure can be implemented. DETAILED DESCRIPTION

[0025] The following description is provided to enable those skilled in the art to make and use the embodiments, and is provided in the context of a specific application and its requirements. Various modifications will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the embodiments. Therefore, the embodiments are not limited to the embodiments shown, but are to be given the widest scope consistent with the principles and features disclosed herein.

[0026] Figure 1 is a flow chart illustrating a method 100 performed by a computer system for optimizing a claims cost recovery process.

[0027] like Figure 1As shown, the method 100 comprises step S101, receiving a fault set corresponding to a fault code in a claim form, the fault set comprising one or more claim items, wherein the one or more claim items at least comprise a parts claim item.

[0028] A claim form usually contains a lot of data, such as repair date, car series, model, warranty validity period, fault description, cause of fault, fault code, damaged parts, replaced parts, working hours for repair, etc.

[0029] For example, a claim form usually contains one or more fault codes, which are codes used to identify the fault that occurred. The fault code is generally defined by the manufacturer and uses numbers and letters to specify the location and type of fault.

[0030] Each fault code corresponds to one or more claim items, and the collection of one or more claim items is called a fault set. In other words, each claim item has a corresponding fault code. Some claim items contain the part number of the replaced / repaired parts, hereinafter referred to as parts claim items. Some claim items may not contain part numbers, but only contain the labor hours and auxiliary materials consumed to repair the fault corresponding to the fault code, hereinafter referred to as labor hour / auxiliary material claim items. The labor hour / auxiliary material claim item is associated with the parts claim item in the fault set corresponding to the fault code.

[0031] It is understandable that the fault set of each fault code may include one or more parts claim items. The fault set of each fault code may also include a labor time / auxiliary material claim item associated with the parts claim item.

[0032] Each claim item may contain various data, for example, one or more of the following: part number, time spent, auxiliary material consumption, fault code, person in charge, etc. Those skilled in the art may screen and extract corresponding data when generating claim items based on claim form data as needed.

[0033] Figure 2 A table showing the relationship between claim sheets, fault codes, parts claim items, and parts is shown. Figure 2 As shown, claim form A1B5NR contains two fault codes, namely 1112014800 and 1112014813, thus involving two fault sets. The fault set corresponding to fault code 1112014800 contains 4 parts claim items, each of which is associated with a corresponding part. The fault set corresponding to fault code 1112014813 contains 2 parts claim items, involving two parts.

[0034] The method 100 further comprises step S103 , in which, for each part claim item, the part claim item is classified into a corresponding basket by matching the part claim item with attributes of a plurality of baskets.

[0035] The "basket" in this application can be considered as a container with conditions (or attributes), and each claim item, including parts claim items and labor / auxiliary material claim items, can be classified into the corresponding basket based on the matching of conditions.

[0036] Baskets can be created based on user input. The user input is received, for example, via a user interface of a computer system such as a keyboard, a mouse, a touch pad, etc. The creation of a basket includes defining the properties of the basket based on the user input.

[0037] The attributes of the basket can be defined according to business requirements. In some embodiments, the attributes of the basket may include one or more of the following:

[0038] Basket Type

[0039] In some embodiments, the types of baskets may be, for example, recalled (RE), internal recalled (TA), serial defective (SD), and normal occasional (NG).

[0040] A recall is when a manufacturer takes back a product that has already been delivered to a wholesaler, retailer or end user. The typical reason for a product recall is that the product sold is found to be defective.

[0041] Internal recalls, for example, refer to the recall of products that have not yet been delivered to wholesalers, retailers or end users. The typical reason for a product recall is also that the product sold is found to be defective.

[0042] Serial defect can mean that parts in a batch are defective.

[0043] Normal incidental refers to defects that occur with normal incidence.

[0044] The above basket types are merely exemplary, and those skilled in the art will appreciate that the meaning of the basket type may be defined according to actual needs, as well as other basket types.

[0045] Basket Identifier

[0046] When a basket is created, it may be automatically assigned a unique identifier.

[0047] Person in charge

[0048] The person in charge attribute can be used to specify the person who is responsible for handling the claim items assigned to this basket.

[0049] Main factors

[0050] The main cause part attribute can be used to specify which parts are the main cause parts for the basket, that is, the parts that are mainly responsible for causing a certain failure.

[0051] Supplier code

[0052] The corresponding supplier can be specified through the supplier code.

[0053] One or more fault codes included

[0054] A fault code associated with the basket is specified, wherein for a parts claim item to be assigned to the basket, its associated fault code must match one of the one or more fault codes.

[0055] One or more part codes included

[0056] Specify the part code associated with this basket. For a part claim item to be assigned to this basket, its associated part code must match one of these one or more part codes.

[0057] Basket Status

[0058] The basket status can be, for example, a working status, a revoked / disabled status, or an ended status. The working status, for example, specifies that the basket can be used for the part claim item basket operation. The revoked / disabled status can specify that the basket has expired and cannot be used for the part claim item basket operation. The ended status can also be called a settled status, indicating that all part claim items in the basket have been settled.

[0059] Those skilled in the art can design and define various basket states as needed.

[0060] Basket Name

[0061] Basket Name is used to define the name of the basket.

[0062] One or more fault codes eliminated;

[0063] Specifying fault codes that may not be associated with the basket, wherein for a parts claim item to be assigned to the basket, its associated fault code must not match any of the one or more fault codes.

[0064] One or more part codes to exclude;

[0065] Specify part codes that must not be associated with this basket. For a part claim item to be assigned to this basket, its associated part code must not match any of these one or more part codes.

[0066] Date of repair;

[0067] Date of production;

[0068] Warranty period;

[0069] ·Car series;

[0070] Model; and

[0071] Frame number.

[0072] The above are just some examples of basket properties, and other basket properties may be conceived by those skilled in the art.

[0073] For each part claim item in the failure set, the part claim item can be classified into a corresponding basket by matching the part claim item with basket attributes of multiple baskets. When creating a basket, one or more of the attributes of the basket can be defined. When the part claim item fully matches one or more of the defined attributes of a basket, the part claim item can be classified into the basket. This can include determining a basket identifier (i.e., basket ID) of the basket to which the part claim item is classified.

[0074] Since a parts claim item is matched with all baskets in the system to find a matching basket, initially, multiple matching baskets may be found, thereby obtaining multiple matching basket IDs.

[0075] Figure 3 A table illustrating the initial results of the part claim item basketing operation is shown.

[0076] like Figure 3 As shown, part claim item 1 may find four different baskets (as shown by basket IDs 0081, 0059, 0083, 00157) by matching with the attributes of the basket, and the basket type of each basket is different.

[0077] At this time, the parts claim item can be classified into the basket with the highest priority order according to the priority order of the types of these four baskets.

[0078] In some embodiments, the priority of the basket type is in descending order of recall (RE), internal recall (TA), serial defect (SD), and normal occurrence (NG). Thus, the four basket IDs 0081, 0059, 0083, and 00157 are sorted according to the priority of the basket type, and then in descending order of 0083, 0081, 0059, and 00157. The basket ID 0083 with the highest ranking can be identified as the basket ID of the basket to which the parts claim item is assigned.

[0079] In some cases, it is possible to find two basket IDs with the highest priority through matching, for example see Figure 4 . Figure 4 Another table illustrating the initial results of the part claim item basketing operation is shown. Figure 4 The table shows two RE types of basket IDs 0083 and 0084.

[0080] In this case, one of the multiple baskets with the highest priority order may be selected according to the creation time as the basket to which the part claim item is classified. For example, a basket with an earlier creation time is selected as the basket to which the part claim item is classified. In this example, it is assumed that basket 0083 is created earlier and is selected as the basket to which the part claim item is classified.

[0081] Those skilled in the art will appreciate that a basket with a later creation time may also be used as the basket to which the parts claim item is allocated.

[0082] like Figure 1 As shown, the method 100 further includes step S105 , in which a final basket to which all the parts claim items in the fault set are finally allocated is determined based on the types of the corresponding baskets of all the parts claim items in the fault set.

[0083] In some embodiments, the final basket to which all the parts claim items in the fault set are finally allocated may be determined based on the priority order of the types of the corresponding baskets of all the parts claim items in the fault set.

[0084] Figure 5 A table illustrating a comparison between initial basket results and final basket results is shown.

[0085] For example Figure 5 As shown, assuming that in step S103, parts claim items 1-4 are respectively divided into TA type basket 0083, GN type baskets 0079, 0031 and 00157, among which TA type has a higher priority than GN type. Therefore, the basket to which all parts claim items under the fault set are finally divided can be identified as TA type basket 0083.

[0086] This takes into account that in some cases, the fault corresponding to fault code 1112014800 is mainly caused by the quality problem or failure of part 11127588412, while parts 11377502022, 07129905597 and 13537585426 are passive replacement parts. In the prior art, each part has a fixed person in charge, and regardless of whether its replacement / repair is passive, it will be assigned to the fixed person in charge of the part. In the present application, by considering the type of the corresponding basket of all parts claim items in the fault set to determine the final basket to which all parts claim items in the fault set are finally assigned, for example, the claim work of recalled parts and passive replacement parts closely related to the recalled parts can be concentrated on the person in charge associated with the recalled parts, which can improve the efficiency of the cost recovery process and the rationality and accuracy of the cost recovery results.

[0087] In addition, through the creation of baskets and the sub-basketing of parts claim items, the person in charge can view the number of parts claim items in each basket, better track the number of claims for different faults, and process claim items in batches to perform efficient cost recovery.

[0088] The method 100 further includes step S107 , in which the main cause component among all the components involved in the fault set is determined.

[0089] In some embodiments, the main contributing part among all the parts involved in the failure set may be determined based on the main contributing part attribute of the final basket to which all the part claim items in the failure set are finally allocated.

[0090] For TA / RE / SD type baskets, the part number identifying the main factor part is usually defined in the main factor part attributes.

[0091] In this case, Figure 5 Taking the data in as an example, assuming that the main factor attribute of the final basket 0083 of type TA contains the part number 11127588412, by matching the part numbers in all 4 part claim items with one or more part numbers contained in the main factor attribute of the final basket 0083, it can be determined that part 11127588412 is the main factor.

[0092] Assume that each part claim item in the fault set is matched with the main factor part attribute of the final basket, but no matching main factor part is obtained. Then the main factor part can be determined based on the price of each part. For example, the part with the highest price is determined as the main factor part.

[0093] For NG type baskets, there is usually no main factor defined.

[0094] In this case, if there is only one parts claim item in the fault set, the part of this parts claim item is determined as the main cause part.

[0095] If there are multiple parts claim items in the fault set, a part of the fault code indicating the installation position of the part (e.g., the first four digits) can be compared with a part of the part code indicating the installation position of the part (e.g., the first four digits), and the matching part code can be identified as the main cause. That is, the part whose installation position is the same as the installation position indicated by the fault code among all the parts involved in all parts claim items is determined as the main cause.

[0096] The part with the highest price in the part code may also be identified as the main cause part, that is, the part with the highest price among all parts involved in all parts claim items may be identified as the main cause part.

[0097] The above are merely some exemplary methods and rules for identifying the main factors, and those skilled in the art may conceive of various modifications without departing from the spirit of the present invention.

[0098] like Figure 1 As shown, the method 100 further includes step S109, in which a claim cost sharing scheme among suppliers of all parts involved in the fault set is determined based on the determination of the main cause.

[0099] In some embodiments, when the fault set corresponding to the fault code involves recalled parts and passive replacement parts, the supplier of the recalled parts may bear all claim costs for the recalled parts and passive replacement parts.

[0100] In other embodiments, when the fault set corresponding to the fault code involves multiple NG-type parts, the claim costs may be shared by the suppliers of the main parts and other parts in proportion to their prices.

[0101] In other embodiments, as described above, the claim items corresponding to the fault codes may also include labor / auxiliary material claim items associated with the parts claim items. In this case, the determination of the claim cost sharing scheme also includes determining the sharing of the labor / auxiliary material claim costs generated by the fault set among the suppliers of all parts involved in the fault set. This is done, for example, in a similar way to the parts cost sharing method. For example, in cases involving recalled parts, all labor / auxiliary material claim costs generated by the fault set shall be borne by the supplier of the recalled parts, i.e., the main cause parts. For another example, in the case of sharing the parts claim costs in proportion to the parts price, the labor / auxiliary material claim costs may be shared among the suppliers in a certain proportion.

[0102] The above is merely an exemplary method for determining a claim expense sharing scheme, and those skilled in the art may conceive of other various variations, such as setting the expense sharing ratio according to different rules.

[0103] The method of the present application may further include generating, for each failure set, a claim billing sheet to a corresponding supplier of each part based on a determined claim cost sharing scheme among suppliers of all parts involved in the failure set.

[0104] The method of the present application may further include generating, for each basket, a claim billing sheet to the supplier of the parts based on the determined claim expense sharing scheme. In some embodiments, the claim billing sheets to the supplier of the parts may be generated in batches on a regular basis.

[0105] Through the method of the present application, it is possible to achieve automatic basket division of parts claim items of a fault set. Furthermore, the final basket division result takes into account the relationship between different parts (such as main cause parts and passive replacement parts), achieves a more reasonable basket division, and correspondingly improves the accuracy and rationality of the assignment of claim project leaders. The method also determines the main cause parts among all parts involved in the fault set and, based on the determination of the main cause parts, determines the claim cost sharing plan among the suppliers of all parts involved in the fault set. This makes the claim cost sharing more reasonable and accurate. The method also allows for the automatic generation of claim billing slips to parts suppliers based on baskets. In addition, the method also allows for tracking the claims of various types of faults based on baskets, thereby improving the work efficiency of the claims leader.

[0106] Figure 6 FIG. 4 is a schematic diagram showing a general hardware environment in which a device according to an embodiment of the present disclosure can be implemented.

[0107] Reference now Figure 6 , a schematic diagram of an example of a computing node 600 is shown. Computing node 600 is only one example of a suitable computing node and is not intended to imply any limitation on the scope of use or functionality of the embodiments described herein. Regardless, computing node 600 is capable of implementing and / or performing any of the functions set forth above.

[0108] In computing node 600, there is a computer system / server 6012, which can operate with numerous other general or special computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that can be suitable for use with computer system / server 6012 include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, small computer systems, large computer systems, and distributed cloud computing technology environments including any of the above systems or devices, etc.

[0109] Computer system / server 6012 can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. In general, program modules can include routines, programs, objects, components, logic, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer system / server 6012 can be practiced in a distributed cloud computing environment, where tasks are performed by remote processing devices linked through a communication network. In a distributed cloud computing environment, program modules can be located on both local or remote computer system storage media including memory storage devices.

[0110] like Figure 6As shown, the computer system / server 6012 in the computing node 600 is shown in the form of a general computing device. The components of the computer system / server 6012 may include, but are not limited to: one or more processors or processing units 6016, a system memory 6028, and a bus 6018 that couples different system components including the system memory 6028 to the processing unit 6016.

[0111] Bus 6018 represents any one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example and not limitation, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, a Peripheral Component Interconnect (PCI) bus, a Peripheral Component Interconnect Express (PCIe), and an Advanced Microcontroller Bus Architecture (AMBA).

[0112] The computer system / server 6012 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer system / server 6012, including volatile and nonvolatile media, removable and non-removable media.

[0113] System memory 6028 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 6032. Computer system / server 6012 may also include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 6034 may be provided for reading from a non-removable non-volatile magnetic medium (not shown, and commonly referred to as a "hard drive") and writing to a non-removable non-volatile magnetic medium. Although not shown, a disk drive for reading from a removable non-volatile disk (e.g., a "floppy disk") and writing to a removable non-volatile disk, and an optical drive for reading from a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM, or other optical medium) and writing to a removable non-volatile optical disk may be provided. In these cases, each may be connected to bus 6018 via one or more data medium interfaces. As will be further depicted and described below, memory 6028 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of embodiments of the present disclosure.

[0114] By way of example and not limitation, a program / utility 6040 having a set (at least one) of program modules 6042 and an operating system, one or more application programs, other program modules, and program data may be stored in memory 6028. Each of the operating system, one or more application programs, other program modules, and program data, or some combination thereof, may include an implementation of a network environment. Program modules 6042 generally perform functions and / or methods as described herein in the embodiments.

[0115] The computer system / server 6012 may also communicate with one or more external devices 6014 (such as a keyboard, pointing device, display 6024, etc.), one or more devices that enable a user to interact with the computer system / server 6012, and / or any device that enables the computer system / server 6012 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may occur via an input / output (I / O) interface 22. Also, the computer system / server 6012 may communicate with one or more networks (such as a local area network (LAN), a general wide area network (WAN), and / or a public network (e.g., the Internet)) via a network adapter 20. As depicted, the network adapter 20 communicates with other components of the computer system / server 6012 via a bus 6018. It should be understood that, although not shown, other hardware and / or software components may be used in conjunction with the computer system / server 6012. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[0116] The present disclosure may be implemented as a system, method, and / or computer program product. The computer program product may include (one or more) computer-readable storage media having computer-readable program instructions thereon for causing a processor to execute aspects of the present disclosure.

[0117] Computer readable storage medium can be a tangible device that can keep and store instructions for being used by instruction execution device.Computer readable storage medium can be, for example, (but not limited to) electronic storage device, magnetic storage device, optical storage device, electromagnetic storage device, semiconductor storage device or any suitable combination of the above.The non-exhaustive list of more specific examples of computer readable storage medium includes the following: portable computer disk, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical encoding device (such as punch card or convex structure in groove with instruction stored thereon) and any suitable combination of the above.Computer readable storage medium as used herein is not interpreted as instantaneous signal itself, such as radio wave or other free propagating electromagnetic wave, electromagnetic wave propagated by waveguide or other transmission medium (for example, light pulse by optical fiber cable) or electrical signal transmitted by wire.

[0118] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards these computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0119] The computer-readable program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, C++, etc.) and conventional procedural programming languages ​​(such as "C" programming languages ​​or similar programming languages). The computer-readable program instructions may be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or may be connected to an external computer (such as using an Internet service provider via the Internet). In some embodiments, an electronic circuit may be customized by utilizing the state information of a computer-readable program instruction, including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), and the electronic circuit may execute a computer-readable program instruction to perform aspects of the present disclosure.

[0120] Aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It will be understood that each box in the flowchart and / or block diagram and the combination of boxes in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0121] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / behaviors specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these computer-readable program instructions can guide the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium in which the instructions are stored includes a manufactured product, which includes instructions for implementing aspects of the functions / behaviors specified in one or more boxes in the flowchart and / or block diagram.

[0122] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operating steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / behaviors specified in one or more boxes in the flowchart and / or block diagram.

[0123] The flow chart and block diagram in the figure show the possible architecture, function and operation of the system, method and computer program product according to each embodiment of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part of a module, segment or instruction, and a part of the module, segment or instruction contains one or more executable instructions for realizing the specified (one or more) logical functions. In some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the figure. For example, depending on the functions involved, two continuous boxes can actually be executed substantially in parallel, or these boxes can sometimes be executed in the opposite order. It will also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a system based on special hardware that performs a specified function or behavior or performs a combination of special hardware and computer instructions.

[0124] It should also be understood by those skilled in the art that the various operations illustrated in order in the embodiments of the present disclosure are not necessarily performed in the illustrated order. Those skilled in the art may adjust the order of the operations as needed. Those skilled in the art may also add more operations or omit some of the operations as needed.

[0125] The description of various embodiments of the present disclosure has been given for the purpose of illustration, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or technical improvements over technologies found in the marketplace, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A computer-implemented method comprising: Receiving a fault set corresponding to a fault code in a claim form, the fault set including one or more claim items, wherein the one or more claim items at least include a parts claim item; For each part claim item, classify the part claim item into a corresponding basket by matching the part claim item with attributes of a plurality of baskets, wherein the attributes of the plurality of baskets at least include a type of basket, and the type of basket is one of a recall RE, an internal recall TA, a series defect SD, and a normal occasional NG; Based on the corresponding basket types of all the parts claim items in the fault set, determining the final basket to which all the parts claim items in the fault set are finally allocated, which further includes for each parts claim item: determining a plurality of baskets into which the part claim item may be classified by matching the part claim item with the attributes of the plurality of baskets, and According to the priority order of the types of the plurality of baskets, the parts claim item is classified into a basket with the highest priority order as a final basket to which the parts claim item is finally allocated; Determine the main cause parts among all parts involved in the fault set based on the main cause part attribute of the final basket to which all parts claim items in the fault set are finally allocated, wherein the main cause part attribute specifies which parts are the main cause parts for a certain basket, that is, the parts that bear the main responsibility for causing a certain fault; and Based on the determination of the main cause, a claim cost sharing plan among suppliers of all parts involved in the failure set is determined.

2. The method of claim 1, wherein: The one or more claim items also include a labor time / auxiliary material claim item associated with the parts claim item, Wherein, based on the determination of the main cause parts, the step of determining the claim cost sharing scheme among suppliers of all parts involved in the fault set further includes: Based on the determination of the main cause parts, determine the allocation of labor hours / auxiliary material claim costs generated by the failure set among the suppliers of all parts involved in the failure set.

3. The method of claim 2, further comprising: For each basket, a claim billing sheet is generated to the supplier of the parts based on the determined claim cost sharing scheme.

4. The method of claim 1, further comprising: Baskets are created based on user definition of the attributes of the basket.

5. The method according to any one of claims 1 to 4, wherein: The properties of a basket may also include one or more of the following: basket identifier; Person in charge; Supplier code; One or more fault codes included; One or more part codes included; Basket status, including working status, canceled / disabled status, or ended status; Basket Name; One or more fault codes eliminated; One or more part codes to exclude; Date of repair; Date of manufacture; Warranty period; Car series; Model; and Frame number.

6. The method of claim 1, wherein: When there are a plurality of baskets having the highest priority order, one of the plurality of baskets having the highest priority order is selected as the basket into which the part claim item is classified according to the creation time.

7. The method of claim 1, wherein: The priority of the basket type decreases in the order of recall RE, internal recall TA, serial defect SD and normal occasional NG.

8. The method of claim 1, further comprising: Determine the main cause part among all the parts involved in all parts claim items, the part whose installation position is the same as the installation position indicated by the fault code; or The part with the highest price among all the parts involved in all parts claim items shall be determined as the main cause part.

9. A computer system comprising: one or more processors, and A memory coupled to the one or more processors, the memory storing computer-readable program instructions, which, when executed by the one or more processors, cause the one or more processors to perform the method of any one of claims 1-8.

10. A computer-readable storage medium storing computer-readable program instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 8.

11. A computer-implemented apparatus comprising means for performing the operations of any of the methods of claims 1-8.

Images