Parts valuation and use

• US 9,830,664 B1
• Filed: 06/12/2014
• Issued: 11/28/2017
• Est. Priority Date: 03/13/2013
• Status: Active Grant

• Current Assignee: Allstate Insurance Company (Allstate Corporation)
• Original Assignee: Allstate Insurance Company (Allstate Corporation)
• Inventors: Marlow, Clint J., Trinco, Robert L., Riggio, John A.
• Primary Examiner(s): Tinkler, Muriel
• Application Number:
  US14/302,794
• Time in Patent Office: 1,265 Days
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/30 Administration of product recycling or disposal
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: Y02W 90/00 Enabling technologies or technologies with a potential or indirect contribution to greenhouse gas [GHG] emissions mitigation
• CPC Class Codes: Y10T 29/49764 with testing or indicating

Abstract

Systems, methods apparatuses, and computer-readable media for analyzing vehicle accident claim information from a vehicle that is deemed a total loss, as well as historical data, to determine whether one or more parts from the vehicle are available for reuse is presented. In some examples, aspects may also relate to determining whether the parts available for reuse should be stored by the entity using the system (e.g., the insurance company) for future use in the repair of other vehicles, such as other vehicles insured by the insurance company, or should be sold. The determination to store or sell the part may be based, at least in part, on historical data of the entity.

Claims

1. A parts management system, comprising:

a processing unit comprising a processor; and

a memory unit storing computer-executable instructions, which when executed by the processing unit, cause the parts management system to;

receive, by a claim server of an entity, claim information including notice of damage to a vehicle associated with the entity, the vehicle having a plurality of parts and the notice of damage to the vehicle including information related to a type of accident and areas of the vehicle that were damaged;

transmit the received claim information from the claim server to a parts management server of the entity;

provide, to the parts management server, a parts management application;

initiate operation of the parts management application by, based on the received claim information, identifying, by the parts management server of the entity, that at least one part of the plurality of parts is available for reuse;

execute an instruction to remove the at least one part from the vehicle;

query, by the parts management server, at least one database to obtain historical data to determine, using the parts management application, whether the at least one part matches an identified need of the entity based on one or more historical data parameters;

upon determining that the at least one part matches the identified need, determine, using the parts management application, whether a likelihood that the at least one part will be reused within a predetermined period of time is at or above a predetermined threshold;

upon determining that the likelihood that the at least one part will be reused within the predetermined period of time is at or above the predetermined threshold, determine storage location information for the at least one part and execute, by the parts management application, instructions to store the at least one part for reuse; and

upon determining that the likelihood that the at least one part will be reused within the predetermined period of time is below the predetermined threshold, execute, by the parts management application, instructions to sell the at least one part.

2. The parts management system of claim 1, wherein the entity is an insurance company and the vehicle is insured by the insurance company.

3. The parts management system of claim 1, wherein storing the at least one part for reuse includes maintaining the at least one part at a facility associated with the entity.

4. The parts management system of claim 3, wherein the entity is an insurance company and the facility associated with the entity is a repair shop associated with the entity.

5. The parts management system of claim 1, wherein storing the at least one part for reuse includes storing the at least one part for reuse on another vehicle associated with the entity.

6. The parts management system of claim 1, wherein selling the at least one part includes selling the at least one part via a distributor.

7. The parts management system of claim 1, wherein the historical data is historical data of vehicles associated with the entity.

8. The parts management system of claim 1, wherein the predetermined period of time and the predetermined threshold are based on user input.

9. A computer, comprising:

a processor; and

a memory storing instructions that, when executed, cause the computer to;

receive, by a parts management application of an entity executing on the computer, claim information including notice of damage to a vehicle associated with the entity, the vehicle having a plurality of parts and the notice of damage to the vehicle including information related to a type of accident and areas of the vehicle that were damaged;

determine that the vehicle is a total loss;

based on the received claim information and the determination that the vehicle is a total loss, identify that at least one part is available for reuse;

execute an instruction to remove the at least one part from the vehicle;

query at least one database to retrieve historical data to determine whether the at least one part matches an identified need of the entity;

upon determining that the at least one part matches the identified need, determine whether a likelihood that the at least one part will be reused within a predetermined period of time is at or above a predetermined threshold;

upon determining that the likelihood that the at least one part will be reused within the predetermined period of time is at or above the predetermined threshold, determine storage location information for the at least one part and store the at least one part for reuse; and

upon determining that the likelihood that the at least one part will be reused within the predetermined period of time is below the predetermined threshold, transmitting an offer of the at least one part for sale.

10. The computer of claim 9, wherein the entity is an insurance company and the vehicle is insured by the insurance company.

11. The computer of claim 9, wherein storing the at least one part for reuse includes maintaining the at least one part at a facility associated with the entity.

12. The computer of claim 11, wherein the entity is an insurance company and the facility associated with the entity is a repair shop associated with the entity.

13. The computer of claim 9, wherein storing the at least one part for reuse includes storing the at least one part for reuse on another vehicle associated with the entity.

14. The computer of claim 9, wherein offering the at least one part for sale includes offering the at least one part for sale via a distributor.

15. The computer of claim 9, wherein the predetermined period of time and the predetermined threshold are based on user input.

16. A parts management system, comprising:

a processing unit comprising a processor; and

a memory unit storing computer-executable instructions, which when executed by the processing unit, cause the parts management system to;

receive, by a claim server of an entity, claim information including notice of damage to a first vehicle associated with the entity, the notice of damage to the first vehicle including information related to a type of accident and areas of the first vehicle that were damaged;

transmit, via a network, the received claim information from the claim server to a parts management server of the entity;

providing, to the parts management server, a parts management application;

initiating operation of the parts management application by, based on the received claim information, identifying, by the parts management server of the entity, that at least one part of the first vehicle is available for reuse;

determine, using the parts management application of the parts management server of the entity, that the at least one part matches an identified need;

execute an instruction to remove the at least one part from the first vehicle;

query at least one database to retrieve historical data to determine, using the parts management application of the parts management server, whether a likelihood that the at least one part will be used in repair of a second vehicle associated with the entity is at or above a predetermined threshold;

upon determining that the likelihood that the at least one part will be used in repair of the second vehicle is at or above the predetermined threshold, determining storage location information for the at least one part and storing the at least one part for reuse; and

upon determining that the likelihood that the at least one part will be used in repair of the second vehicle is below the predetermined threshold, offering, by the parts management application, the at least one part for sale.

17. The parts management system of claim 16, wherein storing the at least one part for reuse includes maintaining the at least one part at a facility associated with the entity.

18. The parts management system of claim 16, wherein the identified need is a projected, future need.

19. The parts management system of claim 16, wherein the entity is an insurance company.

20. The parts management system of claim 16, wherein storing the at least one part includes storing the at least one part at a repair shop associated with the entity.