U.S. patent application number 14/286049 was filed with the patent office on 2014-09-11 for system and methods for vehicle lifecycle management.
This patent application is currently assigned to Openlane, Inc.. The applicant listed for this patent is Openlane, Inc.. Invention is credited to Zachary E. Hallowell, Clarence J. Hammond.
Application Number | 20140258041 14/286049 |
Document ID | / |
Family ID | 39499421 |
Filed Date | 2014-09-11 |
United States Patent
Application |
20140258041 |
Kind Code |
A1 |
Hallowell; Zachary E. ; et
al. |
September 11, 2014 |
SYSTEM AND METHODS FOR VEHICLE LIFECYCLE MANAGEMENT
Abstract
A computerized system for vehicle management and purchase
including a database including information regarding vehicles in a
set of vehicles, wherein a plurality of the vehicles in the set of
vehicles are in arrangements wherein third parties use the
vehicles, wherein the information may include configuration of
respective vehicles. The system may also include a computer
interface that provides access to the description of the vehicles
in the database and provides for setting price of respective
vehicles, an option on the user interface to search, an option on
the user interface to indicate intent to purchase a vehicle, a
computer interface that receives information regarding a vehicle
returned, and a computer interface to facilitate a purchase of the
returned vehicle.
Inventors: |
Hallowell; Zachary E.; (San
Francisco, CA) ; Hammond; Clarence J.; (Fremont,
CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Openlane, Inc. |
Redwood City |
CA |
US |
|
|
Assignee: |
Openlane, Inc.
Redwood City
CA
|
Family ID: |
39499421 |
Appl. No.: |
14/286049 |
Filed: |
May 23, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11685120 |
Mar 12, 2007 |
8738472 |
|
|
14286049 |
|
|
|
|
60781166 |
Mar 10, 2006 |
|
|
|
Current U.S.
Class: |
705/26.62 |
Current CPC
Class: |
G06Q 10/087 20130101;
G06Q 50/30 20130101; G06Q 30/0645 20130101 |
Class at
Publication: |
705/26.62 |
International
Class: |
G06Q 30/06 20060101
G06Q030/06 |
Claims
1. A computerized system for vehicle management and purchase
comprising: a database including information regarding vehicles in
a set of vehicles, wherein a plurality of the vehicles in the set
of vehicles are in arrangements wherein third parties use the
vehicles, wherein the information includes configuration of
respective vehicles; a computer interface that provides access to
the description of the vehicles in the database and provides for
setting price of respective vehicles; an option on the user
interface to search and search logic that allows for searching for
vehicles among the set of vehicles in the database; an option on
the user interface to indicate intent to purchase a vehicle that is
currently in an arrangement where a third party uses the vehicle; a
computer interface that receives information regarding a vehicle
returned upon conclusion of an arrangement wherein a third party
used the vehicle; and a computer interface to facilitate a purchase
of the returned vehicle.
2. The system of claim 1, wherein the third parties comprise
renters of respective vehicles, and the arrangements wherein third
parties use the vehicles comprise rental agreements.
3. The system of claim 1, wherein arrangements wherein third
parties use the vehicles comprise lease agreements.
4. The system of claim 1, wherein arrangements wherein third
parties use the vehicles comprise finance agreements and the third
parties comprise owners of the vehicles.
5. The system of claim 1, including a web server that serves web
sites including the computer interface that provides access to the
description of the vehicle, wherein the web server is coupled to
the database including the description of vehicles in the set of
vehicles.
6. The system of claim 1, wherein the information regarding
vehicles in the set of vehicles includes: vehicle identification
number (\TIN), year, make, model, series, engine, transmission,
drivetrain, and photographs of the vehicle.
7. The system of claim 1, wherein the information regarding
vehicles in a set of vehicles includes at least one of condition of
respective vehicles, price of respective vehicles, status of a
contract associated with a vehicle, time remaining on a contract
associated with a vehicle, payments made on a contract associated
with a vehicle, and amount owed on a contract associated with a
vehicle.
8. The system of claim 1, including an option on a user interface
to allow a user to sell a vehicle earlier than a normally scheduled
time for sale of the vehicle.
9. The system of claim 1, including a computer interface to receive
information regarding a vehicle returned upon conclusion of an
arrangement wherein a third party used the vehicle.
10. The system of claim 1, wherein the information regarding a
vehicle returned upon conclusion of an arrangement wherein a third
party used the vehicle includes: vehicle location, final mileage
and responses to questions asked in connection with return of the
vehicle.
11. The system of claim 1, including logic that generates an
electronic receipt upon return of a vehicle.
12. The system of claim 1, including logic that offers a vehicle
exclusively to a grounding location of the vehicle for a period of
time.
13. The system of claim 1, including logic that offers a vehicle
exclusively to an entity having the grounding location of the
vehicle for a period of time and, following receipt of an
indication that the entity having the grounding location of the
vehicle does not want to purchase the vehicle, offers the vehicle
to others for purchase over a computer network.
14. The system of claim 1, including logic that sends electronic
notification to a transporter with respect to returned
vehicles.
15. A method for vehicle management and purchase comprising:
electronically maintaining information regarding vehicles in a set
of vehicles, wherein a plurality of the vehicles in the set of
vehicles are in arrangements wherein third parties use the
vehicles, wherein the information includes configuration,
condition, and price of respective vehicles; electronically
searching for vehicles among the set of vehicles, and displaying
search results, the search results including at least some vehicles
not yet returned, and information regarding status of the
arrangement with the respective third party; electronically
receiving information regarding a vehicle returned upon conclusion
of an arrangement wherein a third party used the vehicle; and
facilitating a purchase of the returned vehicle through an
electronic interface.
16. The method of claim 15, wherein arrangements wherein third
parties use the vehicles comprise rental agreements, and the status
of the arrangement with the respective third party includes status
of payment of the rental agreement
17. The method of claim 15, wherein arrangements wherein third
parties use the vehicles comprise lease agreements, and the status
of the arrangement with the respective third party includes an
indication of time remaining in term of a respective lease of the
respective vehicle.
18. The method of claim 15, wherein the information regarding
vehicles in a set of vehicles includes status of payments made for
the vehicle.
19. The method of claim 15, automatically providing an electronic
request for transport of a returned vehicle.
20. The method of claim 15, including offering a vehicle
exclusively to an entity having the grounding location of the
vehicle for a period of time and, following receipt of an
indication that the entity having the grounding location of the
vehicle does not want to purchase the vehicle, offering the vehicle
to others over a computer network for purchase.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of and claims priority to
U.S. patent application Ser. No. 11/685,120, filed Mar. 12, 2007,
which claims the benefit of and priority to U.S. Provisional
Application No. 60/781,166, filed Mar. 10, 2006, the disclosures of
each being hereby expressly incorporated herein by reference.
[0002] This application is related to copending patent application
Ser. No. 11/685,121, filed Mar. 12, 2007, now U.S. Pat. No.
8,095,422, the disclosure of which being hereby expressly
incorporated herein by reference.
BACKGROUND OF THE INVENTION
[0003] Organizations are called upon to manage inventories of
vehicles. The inventories may include, for example, vehicles under
lease agreements. Considerable amounts are invested in the
inventories, and considerable attention may be involved in managing
the vehicles. Accordingly, there is a need for improved methods and
systems relative to computer-assisted vehicle inventory
management.
INCORPORATION BY REFERENCE
[0004] All publications and patent applications mentioned in this
specification are herein incorporated by reference to the same
extent as if each individual publication or patent application was
specifically and individually indicated to be incorporated by
reference.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] FIG. 1 is a hierarchy diagram, according to an embodiment of
the invention.
[0006] FIG. 2 is a diagram of a user interface for maturities
searching, according to an embodiment of the invention.
[0007] FIG. 3 is a diagram of a user interface for search results,
according to an embodiment of the invention.
[0008] FIG. 4 is a diagram of a user interface for search results
for accounts, according to an embodiment of the invention.
[0009] FIG. 5 is a diagram of a user interface for customer intent
tracking, according to an embodiment of the invention.
[0010] FIG. 6 is a block diagram of a system with a bidding tool,
according to an embodiment of the invention.
[0011] FIG. 7 is a more detailed block diagram of a system with a
bidding tool, according to an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0012] While preferred embodiments of the present invention have
been shown and described herein, embodiments are provided by way of
example only. Numerous variations, changes, and substitutions are
possible without departing from the invention. It should be
understood that various alternatives to the embodiments of the
invention described herein may be employed in practicing the
invention.
[0013] Embodiments of the invention are directed to methods and
systems for managing inventories of vehicles. Embodiments are
directed to managing the lifecycle, including sale, of sets of used
vehicles. The vehicles may be managed by members of a wholesale
community of dealers, and presented for sale within such community.
An embodiment of the system allows for the viewing of vehicle
inventory information, the registration of a return of the vehicle,
the offering of the vehicle for sale to one or more various groups
of wholesale buyers and potential consignment to a transporter. An
embodiment of the system also supports the association of
electronic inspections with and the display of, inspection
information.
[0014] An embodiment of the invention may be directed to a system
that stores information about a set of vehicles and allows users to
view information about the vehicles. Access to the information may
be controlled so that various individuals and/or organizations have
different access to the information. The information may be
provided to parties other than the owners of the vehicles in order
to facilitate sale of the vehicles. For example, according to an
embodiment, information regarding vehicles in a fleet that includes
rental vehicles may be provided to various other dealers. This may
in turn facilitate sale of vehicles. As a result, according to some
embodiments, information regarding the vehicles is moved
electronically to facilitate sale, which can help to avoid some of
the physical movement of the vehicles in the sales process.
[0015] Electronic notifications may be provided to various systems
and users upon events in the life cycle of the vehicles. This
information may include, for example, notification that a vehicle
has been returned in connection with a lease or rental. The
notifications may be provided to the organization that owns the
vehicle, or other organization or organizations. Information
regarding vehicles may be offered exclusively to a particular
organization or organizations. For example, information regarding
vehicles may be offered exclusively to the grounding dealer. A
grounding dealer is the dealer to which a vehicle is turned in by
the user (e.g., upon conclusion of lease or rental contract), and
is also referred to the turn-in dealer. The electronic information
regarding vehicles may include details regarding the physical
aspects of the vehicle, such as make, model, and configuration. The
electronic information regarding vehicles may also or alternatively
include details regarding the contractual arrangements related to
the vehicle and/or customer or user of the vehicle. Thus, customer
account information may be maintained and made available by the
system to a user or various users.
[0016] The embodiments may be implemented in systems, such as
network-based systems, and/or in methods, such as computer software
methods. Embodiments may include combinations of systems and
processes.
[0017] Various embodiments may include processes and/or systems
having the following features in whole, in part, or in various
combinations: [0018] Vehicle is loaded into an electronic system as
data (for example, as inventory data) [0019] Data is accessible by
designated users (such as sellers) at any point from the vehicle
being loaded into the database via a personal computer [0020]
Vehicle description and accessory information is displayed (the
description may include year, make, model, series, engine,
transmission, drivetrain, mileage (odometer), photographs) [0021]
Seller may manually set prices via a web interface [0022] Seller
may choose to accelerate the vehicles lifecycle and release the
vehicle for sale to buyers [0023] Maturity manager--users
associated with the vehicle (seller, originator of lease or rental
contract, potential buyers) may access and view the vehicle
information and aspects of the vehicle's lifecycle. [0024] Users
have a search function to allow them to search for a specific
vehicle or group of vehicles [0025] Users can view vehicle
information and, if a lease vehicle, may indicate the customer's
intent to purchase, or not purchase, the vehicle at end of contract
to lease/rent the vehicle [0026] Vehicle return manager [0027] Upon
the end of the vehicle's lease contract, the customer will return
the vehicle to a location. [0028] A user associated with the
location will record the return in the system, which will update
the vehicle's status to either be available for sale to users
associated with the grounding location (provided specific
parameters are met) or will move the vehicle to a non-purchasable
status. The return includes entering and recording information
regarding the vehicle such as return date, final mileage,
indication of condition. [0029] The vehicle's location, final
mileage and responses to questions asked during the return process
will be stored in a database. [0030] A vehicle return receipt will
be generated which will be printable and may contain an electronic
signature. An electronic message version of the receipt may be
generated, for example as an e-mail. [0031] Exclusive grounding
location availability [0032] Upon completion of vehicle return, the
vehicle may be offered for online purchase to a user associated
with the grounding location of the vehicle [0033] The user(s) will
have an exclusive period in which to view the vehicle and decide
whether or not to purchase. [0034] The user may indicate that they
do not want to purchase the vehicle, which will accelerate the
vehicle's availability to other users. For example, after receipt
of the indication, the vehicle may be made available immediately
for purchase by other users. [0035] Non-grounding, affiliated user
availability [0036] Upon expiration of the exclusive grounding
location availability period, the vehicle will be made available on
a web-site for sale to a group of affiliated dealers, who have a
contractual relationship with the seller of the vehicle. [0037] The
vehicle will continue to be available to the grounding location's
user during this period. [0038] Consignment [0039] An electronic
notification may be sent to a transporter for vehicles that do not
sell. [0040] Data transmissions [0041] Vehicle status updates will
be transmitted electronically to the vehicle owner.
[0042] An embodiment of the invention is directed to an online
system allowing an automobile dealership to track the status of
vehicles and corresponding lease or retail loan customer accounts
for which they have been assigned or assumed responsibility from
the financing company.
[0043] An embodiment may be password protected and provided in a
network-deployed system (such as a web-deployed system). Various
embodiments may include in whole, in part, or in various
combinations: [0044] A set of data, stored in a database, composed
of vehicle information and user lease or retail account
information. Within the data may be an indicator of whether the
customer is pre-approved for reduced rate financing and whether the
customer is on the federal, state or corporate do not call lists.
[0045] A username and password protected login screen, presented in
a web browser or similar mechanism. [0046] A set of rules governing
the relationship between the user and the vehicle and customer data
to be retrieved. [0047] A set of rules governing the vehicle and
account data to be displayed. [0048] An account search page, where
the user can adjust controls related to defining a set of data to
be returned in search results. [0049] A search results page,
containing summary vehicle and account information, which can be
downloaded in multiple formats. The result set would be governed by
the rules applicable to the user, account and vehicle. [0050] An
account information page, on which detailed customer and vehicle
information is displayed, containing a set of controls for storing
the customer intent.
[0051] For both maturing and past-maturity leases, an embodiment
may include a hierarchy of rules that define which dealership(s)
may view the lease account information. Dealers lower in the
hierarchy may view limited or no information. For example, the
levels may include: [0052] Preferred dealer (occurs when a lessee
notifies the lessor that they would like to turn-in or patronize a
dealership other than their originating dealer, for example in the
case of disputes with their current or originating dealer) [0053]
Originating dealer (where the lessee leased the car from). If there
is no preferred dealer, the user may be displayed to the
originating dealer [0054] Non-originating, non-preferred
dealer--may not view the vehicle or account information in the
maturity manager.
[0055] For example, if the service provider receives records for a
particular vehicle reaching maturity that indicates that the
vehicle has both an originating dealer and a preferred dealer, only
the preferred dealer will be able to view the upcoming maturity in
the system.
[0056] FIG. 1 is a hierarchy diagram, according to an embodiment of
the invention. According to an embodiment, vehicles will only
become visible through the maturity manager when the account and
vehicle information pass specific rules, provided by the finance
company. Thus, for accounts for leased vehicles, according to
various levels of permissions, accounts for vehicles may be visible
for all accounts, or for accounts depending on: whether there is a
condition report, the maturity date of the underlying contract or
other arrangement (for example, whether the current date or time is
within a particular date or time range as compared to the maturity
date), vehicle model year, vehicle model and/or customer intent
(including whether the customer is on a do not call list or
database). Visibility of accounts may depend on whether the
accounts are approved or not pre-approved. According to an
embodiment, the rules are provided by a finance company, such as
the finance company that provides the financing for the respective
vehicle.
[0057] FIG. 2 is a diagram of a user interface for maturities
searching, according to an embodiment of the invention. The
interface may include user options to search based on type of
account 21, approval type 22, condition report status 23,
maturities date range 24, model years 25, model types 26, customer
intent 27, and omitting customers on the do not call list 28. The
system uses the various choices from these inputs to search for
respective accounts and/or vehicles. For example, the type of
account may be lease, rental, or loan, and the approval type may be
pre-approved or not pre-approved. The condition report status 23
may include the option to search based on whether the vehicle has a
condition report, or to search for vehicles without condition
reports, or based on the condition report. The maturities date
range 24 allows for entry of ranges of dates in which the
respective agreement or other arrangement matures, and to cause a
search to occur based on the respective range. Model years 25 may
also be a range of a from and a to model year on which the search
may be based. Model types 26 may include models selectable from a
list of models, or series, or other vehicle types. Customer intent
27 may include all intents, whether the customer intends to
purchase a new vehicle, and/or other intent. The option to omit
customers on the do not call list may be a binary option, such as a
check box that simply indicates that the system is to omit
customers on the do not call list. Pre-approval may refer to
whether the customer is pre-approved for financing of another
vehicle transaction (such as purchase or lease) and the amount of
financing for which such customer is pre-approved.
[0058] FIG. 3 is a diagram of a user interface for search results,
according to an embodiment of the invention. The system shows
respective accounts and/or vehicles in response to a search
request. Different fields may be displayed based on the different
type of accounts the dealer was reviewing. For example, the fields
may be different depending on whether the accounts were for retail
accounts versus lease accounts, and whether the accounts were
pre-approved or not pre-approved. The accounts may have customer
intent information, which may be updated as appropriate. Non
pre-approved accounts may be displayed in the same fields as
pre-approved accounts, but may indicate n/a or other designation to
the extent that the respective data does not apply. Accounts that
were on a do not call list may have an indication such as an icon
indicating that they are on such a list.
[0059] The interface may include items such as sort criteria 31,
and accounts provided in response to the search, such as accounts
32a, 32b, and 32c. Accounts may be shown in the short format
without detail, such as accounts 32a and 32b shown here, or with
more detailed record, such as account 32c, which includes detailed
information 32d, This detailed information may include items such
as the type and year of the vehicle, the YIN, the account person's
name, and/or maturity date, while the more detailed information may
include information such as the address, telephone numbers, MSRP,
adjusted maturity date, capital costs, and other detailed
information as shown, which may be provided in various combinations
or sub-combinations. The interface may include an option to add the
vehicle to a watch list 34. Additionally, the interface may include
an option to download the results, such as to a external file, such
as an Excel file by making the appropriate selection. Search
results may be sorted, such as shown here with option 31, by
criteria such as VIN, year, make, model, mileage, color, maturity,
name, or other criteria.
[0060] Various embodiments of the invention may include the
following, or various subsets of combinations thereof in search
functionality, for example, associated with a maturity manager:
[0061] The search may look for all vehicles prior to return,
provided they meet the visibility rules outlined above. [0062] If a
single vehicle was returned, then the user is taken to a update
customer intent page. [0063] Customer contact information will be
scrubbed against the do not call lists. The system shows the
contact information but indicates the do not call status with an
icon. [0064] Dealer sees grounded vehicles via a link to grounded
vehicles. [0065] For the retail pre-approved report, if the good
through date is less than the system date, then the retail vehicles
are not displayed.
[0066] FIG. 4 is a diagram of a user interface for search results
for retail accounts, according to an embodiment of the invention.
The interface may include options to sort by various criteria 31,
and search results 32a, 32b, and 32c. The interface may also
include the option to add respective items to a watchlist 34. The
interface may include options to provide vehicle detail, provide a
condition report with images, and/or provide a condition report 35.
Detailed information may be provided for respective search results,
as shown here detailed information 32d that corresponds to search
result 32c.
[0067] According to various embodiments of the invention, certain
information stored in the system may be downloaded to certain
users. This information may be downloaded according to various
formats, for example, .csv (or .pdf) formats. Such downloadable
fields may include the following, or subsets thereof, or various
combinations or subcombinations thereof:
[0068] For lease pre-approved, or non pre-approved accounts, [0069]
VIN [0070] Year, make, model, series [0071] Color [0072] Lessee
first name, lessee last name [0073] Maturity date [0074] Address 1,
city, state, zip [0075] Home telephone number [0076] Work telephone
number [0077] Lease account number [0078] Adjusted maturity date
[0079] Good through date [0080] MSRP [0081] Cap cost [0082]
Pre-approval amount [0083] Monthly payment [0084] Security deposit
[0085] Estimated GPO [0086] APR [0087] Pre-approval number [0088]
Pre-approval type [0089] Account type [0090] Term [0091] Remaining
months [0092] Contract mileage
[0093] For Retail pre-approved accounts, [0094] VIN [0095] Year,
make, model, series [0096] Lease account number [0097] Lessee first
name, lessee last name [0098] Address 1, city, state, zip [0099]
Home telephone number [0100] Work telephone number [0101] Start
date [0102] Maturity date [0103] Good through date [0104] Loan
amount [0105] Loan balance [0106] Pre-approval amount [0107]
Monthly payment [0108] Estimated GPO [0109] APR [0110] Pre-approval
number [0111] Pre-approval type [0112] Account type
[0113] FIG. 5 is a diagram of a user interface for customer intent
tracking, according to an embodiment of the invention. The
interface may include customer account information 41, customer
intent information 42, and update inputs 43. The customer account
information may include information about the vehicle and the
respective arrangement regarding the vehicle. The information
regarding the vehicle may include various items of information
regarding the vehicle, such as the model, year, make, series, VIN,
account number. The information regarding the customer may include
the customer name, address, telephone numbers. The information
regarding the arrangement may include information regarding a
financial or lease arrangement regarding the vehicle. This
information regarding the arrangement may include items such as
maturity date, adjusted maturity date, price, capital cost, monthly
payment, GPO/APR, and/or other information regarding the customer
account. Customer intent information may include information
regarding when the customer intends to purchase a vehicle. The
information may include a date or other time related information
regarding when the information was updated and an indication of the
user that updated the information. Additionally, prior intent may
be stored and displayed.
[0114] The update 43 for customer intent may include various fields
or other methods of entry that allow for the customer's intent or
related information to be entered. For example, the customer intent
update 43 may include current vehicle mileage, whether the customer
intends to purchase the current vehicle, the customer's estimated
return date, whether the dealer intends to purchase the vehicle,
whether a pre-inspection has been scheduled (for example, by the
lessee), whether the customer is interested in purchasing a new
vehicle, the customer's contact number, the customer's email
address and notes. The input regarding whether the customer intends
to purchase a new vehicle may include information regarding the
vehicle that the customer is intending to purchase, for example,
the type of vehicle. Other information regarding the purchase may
also be included, according to various embodiments of the
invention.
[0115] FIG. 6 is a block diagram of a system with a bidding tool,
according to an embodiment of the invention. Other tools and
network configurations may be used according to other embodiments
of the invention. The system shown includes an auction server 101,
seller system 102, seller system 120, and buyer system 103. Also
shown is network 104. Seller system 102 includes web pages 105, and
buyer system 103 includes web pages 106. Auction server 101
includes software 107 and storage 110. Software 107 includes
administrative software 108 and auction software 109, and storage
includes seller information 111 and buyer information 112. Seller
information 111 includes information such as vehicle information
113 and 114, and events information 115 which includes order 116,
rules 117 and catalog 118. Auction server 101 is coupled to seller
system 102 and buyer system 103 via network 104. Software 107 in
auction server 101 operates with storage 110.
[0116] Seller system 102 includes functionality to manage inventory
(such as vehicles), set up and modify bidding events, and manage
bidding events. Such functionality may be included directly in
seller system 102 or may be included in auction server 101 or in a
combination of software or other logic located in seller system 102
and auction server 101.
[0117] Buyer system 103 includes functionality to view catalog
items for bidding, to place bids and view an auction, and to select
purchase, payment and delivery options for items purchased. This
functionality may be included in functionality on buyer system 103,
auction server 101 and/or combination of functionality located on
auction server 101 and buyer system 103. The functionality may be
implemented in software, hardware, or a combination of hardware and
software according to various embodiments. Thus, according to
various embodiments, the implementations described herein for
software may also be implemented in various configurations of
software and/or hardware, in distributed or other configurations in
various machines and/or networks.
[0118] Auction server 101 includes software and storage to manage
options and the users of the auctions. Administrative software 108
manages users and information related to users, such as seller
information 111 and buyer information 112. Auction software 109
controls an auction including the progress of the auction as
requested by seller system 102 and response to bids made by buyer
system 103.
[0119] Seller system 102 includes web pages 105 that allow seller
to enter and display information regarding auction events,
inventory, and related administration.
[0120] Buyer system 103 includes web pages 106 that allow a buyer
to display information regarding bidding as well as enter
information commands in order to participate in bidding in
auctions.
[0121] FIG. 7 is a more detailed block diagram of a system with a
bidding tool, according to an embodiment of the invention. Other
tools and network configurations may be used according to other
embodiments of the invention. In the system 200 shown are auction
server 201, seller system 202, and buyer system 203. Auction server
201 is coupled to seller system 202 and buyer system 203 through
Internet 204. FIG. 7 shows a more detailed view of architecture of
the various components of the auction system. Auction server 201
may include a processor 209 for processing instructions, such as an
Intel Pentium.TM. processor, AMD Athlon.TM. processor or other
processor. Processor 209 is coupled to chip set 208 by a processor
bus 211. Chip set 208 is coupled to memory 205 by a memory bus 210
and manages access to memory 205 by processor 209. Chip set 208 is
also coupled to peripheral bus 216. Peripheral 216 bus may
comprise, for example, PCI, PCI-X, PCI Express, or other peripheral
bus. Auction server 201 also includes one or more network interface
cards 207 coupled to peripheral bus 216 for providing network
interfaces to network, such as Internet 204. Storage 206, such as a
disk array or other non-voltage storage, is also coupled to
peripheral bus 216.
[0122] According to various embodiments, memory 205 and/or storage
206 may include various forms of storage or computer-readable
memories such as, but not limited to, volatile memory (random
access memory ("RAM"), non-volatile memory (read-only memory
("ROM")), EEPROM, disk, and/or other storage devices that may
include one or more of magnetic, optical storage, or other media.
The memory and/or storage on the auction server may be configured
as a RAID (Redundant Array of Independent Disks) configuration to
provide high reliability access to software and data.
[0123] Software may be loaded into memory 205 to help provide
auction/bidding function for auction server 201. For example, web
server 212 and real-time auction software 213 may be loaded into
memory 205 and run by processor 209. Web server 212 provides web
pages for the users to interact with in order to be provided with
auctions/bidding functions. For example, web server 212 may serve
up web pages to seller system 202 and buyer system 203 in order to
allow seller system 202 to manage inventory events and bidding and
to allow buyer system 203 to view events and auction items to make
bids and to participate in auctions. Storage 206 includes
information about respective users, such as seller information 214
and buyer information 215. This information is used in order to
manage the inventory of items for sale, configuration of bidding
events, and the processing of real-time bidding. According to
various embodiments of the invention, auction system 200 may
include one or a plurality of auction servers 201 in various
configurations and architectures to provide auctions and bidding
functionality.
[0124] Seller system 202 and/or buyer system 203 may comprise
computer systems coupled to a network such as Internet 204
according to an embodiment. As shown, seller system 202 includes
processor 220 and software components such as a browser 223 and
communications software 221. Also included is a display 224 that
allows a user to see information regarding auctions and to perform
related administration. Buyer system 203 also includes a processor
230, communication software 231, browser 232, and display 233.
Various browser software or other software or functionality to
provide user interaction may be used in buyer and seller systems.
For example, browsers may include, but are not limited to, Internet
Explorer, Netscape browser, Firefox browser, Safari browser or
other browser. Alternatively, other user interface software not
including a browser may be used.
[0125] Software such as web server 212 and real-time auction
software 213 may be stored in storage 206 or other storage and may
be loaded into memory 205 for manipulation by processor 209
according to an embodiment of the invention. Portions of data such
as seller information 214 and buyer information 215 may be loaded
into data structures in memory 205 or other storage for
manipulation by processor 209 in accordance with software such as
web server 212 and real-time auction software 213. Web server 212
includes an operating system for managing system resources, such as
Microsoft Windows XP, 2000, 98, or NT, Apple OS, Linux, or other
operating systems as well as applications software running on top
of the operating systems for implementing an HTML server or other
server. Information stored in storage 206 may be stored in various
forms of database arrangements and may contain cross references or
links to one another to allow information to be queried and
retrieved. In an example embodiment, the information is stored in
databases, such as relational databases, and may be queried using
structured query language (SQL) or other mechanism.
[0126] The system may include a secure connection or connections.
For example, in an embodiment of the invention, the entire bidding
operation of the system operates on a secure connection or
connections. Various different technologies may be used to provide
a secure connection, such as encryption with, for example, public
key and private key encryption. The system may be set up over a
virtual private network (VPN).
[0127] In an example embodiment, a seller operates seller system
202 through browser 223, communications software 221, and display
224 to set up seller inventory and seller events in seller
information storage 214. The seller-user also manages the events
and bidding through seller system 202, which communicates via
Internet 204 with web server 212.
[0128] Buyer system 203 interacts with a buyer user, allowing the
buyer user to view items and events including the items for
auction. The interaction is provided to the buyer user through
display 233, browser 232, and communications software 231, which
are controlled by processor 230. Buyer system in turn communicates
with auction server 201 via Internet 204. Web server 212 in turn
provides buyer system 203 with graphical interface pages which may
be displayed on display 233.
[0129] An embodiment of the invention is directed to a computerized
system for vehicle management and purchasing. The system may
include a database including information regarding vehicles in a
set of vehicles. A plurality of the vehicles in the set of vehicles
are in arrangements wherein third parties use the vehicles, and the
information includes configuration of respective vehicles. The
system may include a computer interface that provides access to the
description of vehicles in the database and provides for setting
price of respective vehicles. The system also may include an option
on the user interface to search and search logic that allows for
searching for vehicles among the set of vehicles in the database.
The system additionally may include an option on the user interface
to indicate intent to purchase a vehicle that is currently in an
arrangement where a third party uses the vehicle. The system may
include a computer interface that receives information regarding a
vehicle returned upon conclusion of an arrangement wherein a third
party used the vehicle, and a computer interface to facilitate
purchase of the returned vehicle.
[0130] The third parties may comprise renters of respective
vehicles and the arrangements wherein third parties use the
vehicles may comprise rental agreements, Alternatively, or
additionally, the arrangements wherein third parties use the
vehicles may comprise lease agreements, or finance agreements, and
the third parties may comprise owners of the vehicles.
[0131] The information regarding vehicles in the set of vehicles
may include vehicle identification number (VIN), year, make, model,
series, engine, transmission, drivetrain, and photographs of the
vehicle. Also, alternatively, the information may include condition
and price of respective vehicles. The information may also, or
alternatively, include: the status of a contract associated with a
vehicle, time remaining on a contract associated with a vehicle,
payments made on a contract associated with a vehicle, amount owed
on a contract associated with a vehicle.
[0132] The system may include an option on the user interface to
allow a user to sell a vehicle earlier than a normally scheduled
time to sell the vehicle. An embodiment of the system includes an
interface for receiving information regarding a vehicle returned
upon conclusion of an arrangement wherein a third party used the
vehicle. The information may include items such as vehicle
location, final mileage and responses to questions asked in
connection with return of the vehicle. An embodiment may include
logic that generates an electronic receipt upon return of a
vehicle. Additionally, logic may be included that offers a vehicle
exclusively to a grounding location of the vehicle for a period of
time. Logic may be included that offers a vehicle exclusively to an
entity having the grounding location of the vehicle for a period of
time, and following receipt of an indication that the entity having
the grounding location of the vehicle does not want to purchase the
vehicle, offers the vehicle for purchase to others over a computer
network.
[0133] Another embodiment of the invention is directed to an
Internet-based system including a web server and a database coupled
to the web server. The database includes information regarding
vehicles in a set of vehicles. A plurality of the vehicles in the
set of vehicles are in arrangements wherein third parties use the
vehicles, and the information includes condition of respective
vehicles. The system includes logic in the web server that serves a
web page to a remotely located user providing access to the
description of the vehicles in the database and provides for
setting price of respective vehicles. Included logic serves a web
page to a remotely located user providing an option to search and
search logic that allows for searching for vehicles among the set
of vehicles in the database. A user is prompted for information
regarding a vehicle returned upon conclusion of an arrangement
wherein a third party used the vehicle, and the web page is served
to facilitate purchase of the returned vehicle. The arrangements
wherein third parties use the vehicles may comprise rental
agreements, lease agreements and finance agreements, according to
various embodiments of the invention.
[0134] Another embodiment of the invention is directed to a method
for vehicle management and purchasing. Information regarding the
vehicles in a set of vehicles is managed electronically. A
plurality of the vehicles in the set of vehicles are in
arrangements wherein third parties use the vehicles, and the
information includes configuration, condition and price of
respective vehicles. Vehicles are searched for electronically among
the set of vehicles, and search results are displayed. The search
results include at least some of the vehicles not yet returned and
information regarding status of the arrangement with the respective
third party. Information is received electronically regarding the
vehicle returned upon conclusion of an arrangement wherein a third
party used the vehicle, and purchase of the returned vehicle is
facilitated through an electronic interface.
[0135] An embodiment of the invention is directed to a computerized
system for vehicle management. The system includes a database
including information regarding the vehicles in the set of vehicles
and customer accounts. The information regarding the vehicles
includes configuration of respective vehicles, and the information
regarding customer accounts includes links to vehicles in the set
of vehicles owned by respective customers and status of customer
accounts. The system includes a server coupled to the database that
serves user interface pages with vehicle information including
information from the database. A protected system login mechanism
for system users is included, as well as logic implementing rules
regarding a relationship between system users on the one hand and
information regarding vehicles and customer accounts on the other
hand. A search mechanism is included as well as a search results
interface. The search mechanism finds respective vehicles or
accounts based on search criteria. Logic is included in the server
that serves a customer account interface. The customer account
interface displays information regarding customer accounts to the
extent allowed by the rules regarding the relationship between
system users on the one hand and information regarding vehicles and
customer accounts on the other hand.
[0136] The information regarding customer accounts may include
information regarding payments and time remaining in leases in
respective customer accounts. Also, the information regarding
customer accounts may additionally or alternatively include
information regarding payments and time remaining in loans in
respective customer accounts.
[0137] An embodiment of the invention includes logic that defines a
hierarchy of categories of dealers that may view particular
information of respective customer accounts. The hierarchy may
include preferred dealer users that can view most sensitive
customer account information and at least another category of
dealer users that have access to the system and cannot view certain
customer account information. Logic may be included that makes
information regarding the vehicle visible only to a preferred
dealer if the vehicle has both an originating dealer and a
preferred dealer.
[0138] An embodiment of the invention includes a first user
interface for retail accounts and a second user interface for lease
accounts. An embodiment of the invention may include pre-approval
information. Another embodiment of the invention is directed to a
computerized system for vehicle management including a database
including information regarding vehicles in a set of vehicles and
customer accounts. The system may include logic implementing rules
regarding relationship between system users on the one hand and
information regarding vehicles and customer accounts on the other
hand. The system may include a search mechanism, customer account
interface, and logic that causes the customer account interface to
display information regarding some vehicles before the vehicles are
returned and not other vehicles before the vehicles are returned
based on rules for visibility of respective vehicles. The rules may
be configurable to allow display based on existence of a condition
report, status of maturity of an underlying financial arrangement
for the vehicle, model year of the vehicle, and customer
intent.
[0139] Another embodiment of the invention is directed to an
Internet-based system comprising a web server, a database,
protected system login, logic implementing rules regarding
relationship between system users on the one hand and information
regarding vehicles and customer accounts on the other hand, a
search mechanism, logic for serving search results based on
vehicles or accounts found based on search criteria, and logic
serving a customer account web page. The database may include
information regarding vehicles in a set of vehicles and customer
accounts. Another embodiment of the invention is directed to a
method for vehicle management. Information regarding vehicles in a
set of vehicles is maintained electronically. A plurality of the
vehicles in the set of vehicles are in arrangements wherein third
parties use the vehicles. The information may include
configuration, condition and price of respective vehicles. Users
are prompted for passwords and vehicles are searched electronically
among the set of vehicles. Search results are displayed and may
include at least some vehicles not yet returned and information
regarding the status of the arrangement with respect to the third
party. Information may be received electronically regarding the
vehicle returned upon conclusion of an arrangement wherein a third
party used the vehicle, and in response to the user request with
search criteria, vehicles or accounts are searched for based on the
search criteria. A set of user permissions is maintained, wherein
the user permissions determine whether respective users have access
to respective accounts, and information displayed regarding
customer accounts to users based on user permissions.
[0140] Aspects of the systems and methods described herein may be
implemented as functionality programmed into any of a variety of
circuitry, including programmable logic devices (PLDs), such as
field programmable gate arrays (FPGAs), programmable array logic
(PAL) devices, electrically programmable logic and memory devices
and standard cell-based devices, as well as application specific
integrated circuits (ASICs). Some other possibilities for
implementing aspects of the systems and methods include
microcontrollers with memory, embedded microprocessors, firmware,
software, etc. Furthermore, aspects of the systems and methods may
be embodied in microprocessors having software-based circuit
emulation, discrete logic (sequential and combinatorial), custom
devices, fuzzy (neural network) logic, quantum devices, and hybrids
of any of the above device types. Of course the underlying device
technologies may be provided in a variety of component types, e.g.,
metal-oxide semiconductor field-effect transistor (MOSFET)
technologies like complementary metal-oxide semiconductor (CMOS),
bipolar technologies like emitter-coupled logic (ECL), polymer
technologies (e.g., silicon-conjugated polymer and metal-conjugated
polymer-metal structures), mixed analog and digital, etc.
[0141] It should be noted that the various functions or processes
disclosed herein may be described as data and/or instructions
embodied in various computer-readable media, in terms of their
behavioral, register transfer, logic component, transistor, layout
geometries, and/or other characteristics. Computer-readable media
in which such formatted data and/or instructions may be embodied
include, but are not limited to, non-volatile storage media in
various forms (e.g., optical, magnetic or semiconductor storage
media) and carrier waves that may be used to transfer such
formatted data and/or instructions through wireless, optical, or
wired signaling media or any combination thereof. Examples of
transfers of such formatted data and/or instructions by carrier
waves include, but are not limited to, transfers (uploads,
downloads, email, etc.) over the Internet and/or other computer
networks via one or more data transfer protocols (e.g., HTTP, FTP,
SMTP, etc.). When received within a computer system via one or more
computer-readable media, such data and/or instruction-based
expressions of components and/or processes under the systems and
methods may be processed by a processing entity (e.g., one or more
processors) within the computer system in conjunction with
execution of one or more other computer programs.
[0142] Unless the context clearly requires otherwise, throughout
the description and the claims, the words `comprise,` comprising,`
and the like are to be construed in an inclusive sense as opposed
to an exclusive or exhaustive sense; that is to say, in a sense of
`including, but not limited to.` Words using the singular or plural
number also include the plural or singular number, respectively.
Additionally, the words `herein,` hereunder, "above,` `below,` and
words of similar import refer to this application as a whole and
not to any particular portions of this application. When the word
`or` is used in reference to a list of two or more items, that word
covers all of the following interpretations of the word: any of the
items in the list, all of the items in the list and any combination
of the items in the list.
[0143] The above description of illustrated embodiments of the
systems and methods is not intended to be exhaustive or to limit
the systems and methods to the precise form disclosed. While
specific embodiments of, and examples for, the systems and methods
are described herein for illustrative purposes, various equivalent
modifications are possible within the scope of the systems and
methods, as those skilled in the relevant art will recognize. The
teachings of the systems and methods provided herein can be applied
to other processing systems and methods, not only for the systems
and methods described above.
[0144] The elements and acts of the various embodiments described
above can be combined to provide further embodiments. These and
other changes can be made to the systems and methods in light of
the above detailed description.
* * * * *