U.S. patent application number 17/665683 was filed with the patent office on 2022-09-22 for vin based insurance claim system.
The applicant listed for this patent is Audatex North America, Inc.. Invention is credited to Tanya Elkins, Sergey Gorelov, Daryoush Joobbani.
Application Number | 20220301066 17/665683 |
Document ID | / |
Family ID | 1000006381154 |
Filed Date | 2022-09-22 |
United States Patent
Application |
20220301066 |
Kind Code |
A1 |
Elkins; Tanya ; et
al. |
September 22, 2022 |
VIN Based Insurance Claim System
Abstract
An insurance claim system that can display vehicle
identification key information and vehicle option, package, engine,
transmission, paint, production date information provided from
multiple different sources. The system can perform a method that
includes displaying at least one insurance claim with at least one
vehicle description, a plurality of vehicle options, and a VIN
field. A VIN is entered into the VIN field, which is decoded to
determine vehicle information and vehicle option information. One
or more vehicle options displayed by the client computer are
selected with the vehicle option information, and the selected
vehicle options are modified with supplemental vehicle options
information provided by an OEM source. Modifying the vehicle
options with the information provided by the OEM source improves
the accuracy of the options information selected on the insurance
claim page. Maintaining the additional options provided by the VIN
decode allows an operator to select/de-select options added or
removed after manufacture of the vehicle.
Inventors: |
Elkins; Tanya; (Milwaukie,
OR) ; Gorelov; Sergey; (West Linn, OR) ;
Joobbani; Daryoush; (Tigard, OR) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Audatex North America, Inc. |
Addison |
TX |
US |
|
|
Family ID: |
1000006381154 |
Appl. No.: |
17/665683 |
Filed: |
February 7, 2022 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16684165 |
Nov 14, 2019 |
11244404 |
|
|
17665683 |
|
|
|
|
15937659 |
Mar 27, 2018 |
10482541 |
|
|
16684165 |
|
|
|
|
13440751 |
Apr 5, 2012 |
9959575 |
|
|
15937659 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06Q 40/00 20130101;
G06Q 40/08 20130101 |
International
Class: |
G06Q 40/08 20060101
G06Q040/08; G06Q 40/00 20060101 G06Q040/00 |
Claims
1. A system that provides vehicle information and vehicle options
for an insurance policy to a client that displays at least one
insurance vehicle identification page that includes at least one
vehicle description, a plurality of vehicle options and a VIN
field, and receives supplemental vehicle options information from a
source that is used to modify selected vehicle options displayed by
the client, comprising: a VIN decoder that decodes a VIN received
from the client and provides vehicle information and vehicle
options information for one or more vehicles associated with said
VIN, said vehicle option information being used to select one or
more vehicle options displayed by the client.
Description
RELATED APPLICATION INFORMATION
[0001] This application is a continuation of U.S. application Ser.
No. 13/440,751 filed Apr. 5, 2012, which is hereby incorporated by
reference as if set forth fully herein.
BACKGROUND OF THE INVENTION
1. Field of the Invention
[0002] The subject matter disclosed generally relates to a method
and system for generating an insurance claim for a vehicle.
2. Background Information
[0003] When a vehicle such as an automobile is damaged the owner
may file a claim with an insurance carrier. A representative
typically inspects the vehicle to determine the amount of damage
and the costs required to repair the automobile. The owner of the
vehicle or the vehicle repair facility may receive a check equal to
the estimated cost of the repairs. If the repair costs exceed the
value of the automobile, or a percentage of the car's value, the
representative may "total" the vehicle. The owner may then receive
a check based on the value of the automobile.
[0004] The repair costs and other information may be entered by the
representative into an estimate report. After inspection the
representative sends the estimate report to a home office for
approval. To improve the efficiency of the claims process there
have been developed computer systems and accompanying software that
automate the estimate process. By way of example, the assignee of
the present invention, Audatex, Inc, ("Audatex") provides a
software product under the trademark Audatex Estimating/Autosource
that allows a representative to enter claim data. The Audatex
software includes a VIN field that allows the user to enter the VIN
(vehicle identification number) of the damaged vehicle. The VIN can
be decoded to determine the matching vehicle(s). The vehicle
identification process can also provide information regarding the
standard options for the vehicle. Vehicle information can be also
retrieved from a manufacturer proprietary vehicle database, also
referred to as the vehicle identification key. Accurate vehicle
information is essential to obtaining accurate repair cost and
vehicle valuation data.
[0005] A vehicle may be modified by a third party such as a dealer
or the owner so that the options information provided by the VIN
decode process and/or vehicle identification key information is
incomplete. This requires the user of the system, such as an
insurance representative, to select or de-select the different
options of the vehicle in the claim system. This can be a time
consuming exercise that is ripe for error.
[0006] In addition, to the traditional claim inspection process
where a representative directly enters the vehicle's physical
inspection information into a claims application to produce an
estimate or vehicle valuation request Audatex has the ability to
provide a vehicle identification key (vehicle description, engine,
transmission, options, packages, manufacture build date and paint).
A representative will utilize this report as part of a physical
inspection process to verify the loss vehicle's information. Once
the physical inspection has been completed the vehicle inspection
details can then be used to complete the vehicle information
process within Audatex or another vendor's application for an
estimate and/or vehicle valuation.
BRIEF SUMMARY OF THE INVENTION
[0007] An apparatus and method that includes displaying at least
one insurance policy with at least one vehicle description, a
plurality of vehicle options, and a Vehicle Identification Number
(VIN) field. A VIN can be entered, which is decoded to determine
key vehicle identification and option information. One or more
vehicle options displayed by the client computer can be selected
with the vehicle option information, and the selected vehicle
options are modified with supplemental vehicle options information
provided by an OEM source.
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] FIG. 1 is a schematic of a network system that can be used
to generate an insurance inspection report for a damaged
vehicle;
[0009] FIG. 2 is a schematic of a computer of the system;
[0010] FIGS. 3A and B are illustrations of a vehicle identification
page with different vehicle information fields;
[0011] FIGS. 4A and 4B are a flowchart showing a process for
automatically populating vehicle information fields based on a VIN
decode, vehicle identification key, and OEM vehicle
information;
[0012] FIGS. 5A-D are illustrations showing the linking of OEM data
with vehicle description keys;
[0013] FIG. 6 is a graphical user interface used to enter and/or
select damaged parts of a vehicle; and,
[0014] FIG. 7 is a graphical user interface that provides a running
cost total for the repair estimate of the damaged vehicle.
DETAILED DESCRIPTION
[0015] Disclosed is an insurance application system that can
display vehicle information and vehicle option information provided
by two different sources. The system can perform a method that
includes displaying at least one insurance vehicle identification
page with at least one vehicle description, a plurality of vehicle
options, and a VIN field. A VIN is entered into the VIN field,
which is decoded to determine vehicle information and vehicle
option information. One or more vehicle options displayed by a
client computer can be selected with the vehicle option
information, and the selected vehicle options can be modified with
supplemental vehicle options information provided by an OEM source.
An OEM source may include B2B, Direct Batch, Surrogate/3rd party or
B2B Batch (OEM B2B/trx based; OEM data dumps; 3rd party B2B/trx
based; 3rd party data dumps). Modifying the vehicle options with
the information provided by the OEM source improves the accuracy of
the vehicle description, engine, transmission, options, and
packages information selected on the insurance vehicle
identification page. Displaying the additional options provided by
the VIN decode allows an representative to select/de-select options
added or removed after manufacture of the vehicle.
[0016] Referring to the drawings more particularly by reference
numbers, FIG. 1 shows a system 10 that can be used to generate a
repair cost estimate and/or vehicle valuation for an insurance
claim of a vehicle. The system 10 includes at least one client 12
that is connected to an electronic communication network 14. The
electronic communication network 14 may be a wide area network
(WAN) such as the Internet. Accordingly, communication may be
transmitted through the network 14 in TCP/IP format. The client
could be any type of device that can access the network 14. For
example,
[0017] The system 10 may further include an claim server 16
connected to the network 14. The claim server 16 may provide a web
based portal that provides access to a repair cost estimate and/or
a vehicle valuation web site. The web site may provide one or more
web pages that can be used by a representative to generate a repair
cost estimate and/or a vehicle valuation. By way of example, the
representative may utilize the web pages to determine the estimate
and/or a vehicle valuation of a vehicle or claims adjuster
submitting vehicle information on a theft claim, or a policy system
that requires vehicle data to provide a price quote. Although one
claim server 16 is shown, it is to be understood that the claim
server may include two or more separate servers including a web
server and an application server that together perform the claim
functions.
[0018] The system also includes an OEM server 18 that can be
coupled to the claim server 16 and clients 12 through the network
14. The OEM server 18 contains a database that includes vehicle
model information and vehicle option information. The OEM server 18
may provide vehicle model information and vehicle options
information based on a VIN. Although a web based system is shown
and described, it is to be understood that a non-web based system
could be employed.
[0019] FIG. 2 shows an embodiment of a client 12 and the servers 16
and 18. The computer 12 includes a processor 40 connected to one or
more memory devices 42. The memory device 42 may include both
volatile and non-volatile memory such as read only memory (ROM) or
random access memory (RAM). The processor 40 is capable of
operating software programs in accordance with instructions and
data stored within the memory device 42.
[0020] The processor 40 may be coupled to a communication port 44,
a mass storage device 46, a monitor 48 and a keyboard 50 through
bus 52. The processor 40 may also be coupled to a computer mouse, a
touch screen, a microphone, a speaker, an optical code reader (not
shown). The communication port 44 may include an ETHERNET interface
that allows data to be transmitted and received in TCP/IP format,
although it is to be understood that there may be other types of
communication ports. The system bus 52 may be a PCI or other
conventional computer bus. The mass storage device 46 may include
one or more disk drives such as magnetic or optical drives. The
mass storage device 46 may also contain software that is operated
by the processor 40.
[0021] Without limiting the scope of the invention the term
computer readable medium may include the memory device 42 and/or
the mass storage device 46. The computer readable medium may
contain software programs in binary form that can be read and
interpreted by the computer. In addition to the memory device 42
and/or mass storage device 46, computer readable medium may also
include a diskette, a compact disc, an integrated circuit, a
cartridge, or even a remote communication of the software program.
In general the servers 16 and 18 may contain more memory,
additional communication ports and greater processing power than
the computer 12.
[0022] The servers 16 and 18 may contain relational databases that
correlate data with individual data fields and a relational
database management system (RDBMS). The RDBMS of the server 16 may
include a reference to a website that can be accessed by the
computers 12. The website has one or more specific uniform resource
locators (URL) that can be used to access the site through the
network 14. The URL can be entered through a web-based application
resident in the client computer 12. By way of example, the web
based application may be a browser.
[0023] FIGS. 3A and 3B show an example of an claim page 100 with a
VIN field 102 that allows a user to enter a VIN. The page 100 may
include vehicle information fields, including but not limited to
ORIGIN 104, MAKE 106, YEAR 108, MODEL 110, STYLE 112, ENGINE 114
and TRANSMISSION 116, exterior and interior Paint code, color,
refinish type and production date fields. The page may further
include vehicle packages fields 118 and vehicle options fields 120
that can be selected and deselected to indicate the options of a
vehicle. Entering the VIN automatically populates certain fields of
the page 100.
[0024] The basic decoding process may determine a vehicle and
standard vehicle options associated with the entered VIN. The basic
VIN decode can be performed by the claims server, or a separate VIN
decode server. The vehicle information is automatically inserted
into the page 100 as shown in FIG. 3A. Certain vehicle options are
also selected as indicated by the check marks in FIG. 3B. The
process also includes retrieving vehicle option information from
the OEM source. The page displays the OEM vehicle option
information. For example, FIG. 3B shows a REAR SPOILER field that
would have been selected based on the basic VIN decode but was
de-selected based on the vehicle options information provided by
the OEM server. The user can further select or de-select options
based on an inspection of the vehicle. The combination of VIN
decoding and OEM vehicle option information provides an initial
repair cost estimate or vehicle valuation that is "relatively
accurate".
[0025] The basic VIN decode may generate information for more than
one vehicle. For example, the basic VIN decode may generate
information for both a standard package and a custom package, or
for different engine sizes. The OEM vehicle information can be used
to eliminate one or more pieces of the vehicle information
identified in the basic VIN decode process.
[0026] FIGS. 4A and 4B show a flowchart for the process of
automatically populating the page based on the entry of a VIN. The
VIN is entered and decoded in block 200. The VIN can be decoded by
two different processes. By way of example, the VIN may be decoded
by a process referred to as OEM decode and/or a process referred to
as a basic decode. The validity of the basic VIN decode is checked
in decision block 202, If the decode is invalid, OEM decode data
may not be requested in block 204. If valid, OEM data for the
vehicle is requested in block 206. The vehicle identification key
generated by the basic decode process is compared with the OEM
decode data in decision block 208. If the description and OEM data
do not match then the OEM data is not used and the basic VIN decode
are inserted in blocks 210 and 212, respectively. A notification
can be provided in block 214.
[0027] In decision block 216, it is determined whether the basic
VIN decode produced multiple vehicle identification keys. If yes,
in block 218 the options and packages provided through the VIN
decode are compared with the packages provided by the OEM source.
In block 220 the vehicles identified by the OEM source that do not
have the options and packages identified through the VIN process
are removed. If this process removed all of the possible identified
vehicles as determined in decision block 222 then all of the
vehicle identification keys are displayed in block 224 and the user
has the option of selecting from a full list of displayed
descriptions. If all of the vehicle identification keys are not
removed, then the vehicle identification keys that do not match the
vehicle options identified by the OEM data are removed in block 226
and a pared list of vehicle identification keys are displayed in
block 230. If all of the vehicle identification keys are not
removed then the vehicle identification keys remaining are
displayed in block 232.
[0028] The process continues to blocks 234 and 236 where the
vehicle options identified by the OEM source are added to the
options and packages identified in the VIN process. Packages that
are formed by the added options are added to the response in block
238. The standard options identified by the OEM source are added in
block 240 and a mutual exclusion check with the vehicle
identification key options is performed in decision block 242. The
vehicle identification key standard packages are checked for
exclusions in block 244. In block 246 the process de-selects
options that would have been selected by the VIN process based on
the OEM source.
[0029] In block 248 the engine and transmission information
produced by the vehicle identification key and OEM processes are
checked. In block 250 the OEM engine and transmission is used, if
blank the vehicle identification key engine and transmission is
used. The response is scanned and notifications are sent in blocks
252, 254 and 256. A log and billing is created in blocks 258 and
260 and if available additional options are added in block 262 to
complete the process.
[0030] Before OEM data can be used by a client application, a
linking process is utilized to map OEM data to the vehicle
description keys. FIG. 5A shows an example of a linking page 270 to
map OEM model numbers to vehicle description key numbers. This
linking allows the vehicle identification key generated by the
basic decode process to be compared with the OEM decode data in
decision block 208. FIG. 5B shows an example of the linking page
272 to map OEM package codes at the make or model level to vehicle
description key package names and their contents. This linking is
used within blocks 218 and 234. FIG. 5C shows an example of a
linking page 274 to map OEM option codes at the make or model level
to vehicle description key option names which is used within blocks
242 and 246. FIG. 5D shows an example of a linking page 276 to map
vehicle description key option codes at the make or model level to
options that impact labor and/or part numbers on an estimate which
is used within block 262.
[0031] The representative may enter and/or select damaged parts for
the vehicle. FIG. 6 shows an example of an estimating page 300 that
allows the user to enter and/or select damaged parts of a vehicle.
The page 300 may include a graphical section 302 that can be
selected by the representative and a text section 304 that lists a
plurality of selectable parts for the vehicle. The parts that are
selected to be replaced or repaired can be listed in section 306.
An estimate page can be displayed by selecting the "Estimate Total"
link 308 shown in FIG. 6. FIG. 7 shows a page 320 that displays a
running cost total of the estimated damage of the vehicle. The
process may have a feature (not shown) that provides a warning to
the representative that the cost total exceeds a "totaled" value at
which point the representative may discontinue the process and
request a vehicle valuation. After all of the parts to be repaired
or damaged are selected the representative may obtain a final
repair cost estimate and/or vehicle valuation.
[0032] While certain exemplary embodiments have been described and
shown in the accompanying drawings, it is to be understood that
such embodiments are merely illustrative of and not restrictive on
the broad invention, and that this invention not be limited to the
specific constructions and arrangements shown and described, since
various other modifications may occur to those ordinarily skilled
in the art.
* * * * *