Integrating vehicle data for provider and personal rental vehicles into a vehicle-fleet platform and fleet management interface

In recent years, rental-vehicle-computing systems have developed and implemented computing tools for managing different rental vehicles. Indeed, the proliferation of web and mobile applications enable requesting computing devices to remotely submit rental requests for use of various rental vehicles. Many such rental-vehicle-computing systems can organize rental vehicle information for different types of rental vehicles in separate systems that can use different digital protocols to communicate with vehicles' computing devices, such as separate and disconnected databases or servers dedicated to differing services.

Although conventional rental-vehicle-computing systems can organize rental vehicle information in a variety of separate systems, conventional systems often face a number of technical problems, particularly with regard to efficiency and accuracy. In particular, conventional rental-vehicle-computing systems inefficiently organize and separate vehicle information into a variety of separate systems. To illustrate, rental-vehicle-computing systems often execute servers or software platforms isolated from other computing devices (or other software platforms) hosting services that receive and manage vehicle information corresponding to rental vehicles. For example, some rental-vehicle-computing systems use one software platform to manage rental vehicle pick-ups and drop-offs and another separate software platform to manage rental vehicle maintenance services and/or rental locations.

Because of such isolated software platforms or other disassociated system components, many conventional rental-vehicle-computing systems execute separate software applications with different and disconnected graphical user interfaces that confuse users. For instance, some rental-vehicle-computing systems deploy one software application for managing repairs or services of rental vehicles, another software application for reservations, and link to yet another software application for affiliated third party vehicles, where each software application uses separate graphical user interfaces and separate data. By deploying separate software applications and corresponding graphical user interfaces, conventional rental-vehicle-computing systems force users to navigate and interact with isolated menus, options, and other user-interface tools to locate or present various rental vehicle information. Such excessive interactions and navigation can consume more computing resources than necessary or practical for conventional rental-vehicle-computing systems.

In addition to inefficient user navigation and user interactions, many conventional rental-vehicle-computing systems present incomplete (or even inaccurate) rental vehicle information fetched from an isolated database or software platform. As mentioned, conventional rental-vehicle-computing systems often interact with a variety of isolated computing devices utilizing a variety of different systems, including isolated databases or software platforms for rentals, vehicle servicing, etc. Because of such isolation, many conventional systems can access and present only an incomplete or siloed snapshot of rental vehicle information.

This disclosure describes embodiments of systems, non-transitory computer-readable media, and methods that provide benefits and/or solve one or more of the foregoing or other problems in the art. For example, the disclosed systems can receive and integrate vehicle data for a fleet of different types of rental vehicles—and/or service data from vehicle service centers associated with such rental vehicles—from across different databases into a central platform. Based on one or both of the integrated vehicle data and service data, the disclosed systems generate vehicle-data summaries for such rental vehicles as well as generate and display surface tools for dispatch, service, and other vehicle managing functions. Such a fleet of rental vehicles can include personal-rental vehicles, provider-rental vehicles, such as express-provider-rental vehicles and flexible-provider-rental vehicles—as well as third-party-rental vehicles. By integrating service, renter, or other vehicle data for disparate rental vehicles into a consolidated vehicle-fleet-platform database, the disclosed systems can display and sort vehicle-data summaries in a centralized fleet management interface.

From within such a fleet management interface, the disclosed systems can sort disparate rental vehicles or renters according to historical data, vehicle manufacturing information, usage data, service status, or other criteria. In addition to sorting, the disclosed systems can further utilize the vehicle-fleet-platform database and fleet management interface to schedule or aggregate various appointment schedules for rental pickup or drop-off and vehicle servicing at either a vehicle service center or on site at a vehicle's location using mobile services. Upon reservation or schedule, the disclosed systems can provide a virtual code, including a near field communication code, to a renter computing device and facilitate exchange of the virtual code with a rental vehicle at a rental location to enable contactless pick-up.

This disclosure describes one or more embodiments of a fleet management system that receives and integrates vehicle data for a fleet of different types of rental vehicles—and/or service data from vehicle service centers associated with such rental vehicles—from across different databases into a central platform. Based on one or both of the integrated vehicle data and service data, the fleet management system generates vehicle-data summaries or surface management tools for such rental vehicles in graphical user interfaces. By surfacing summaries or tools in an integrated user interface, the fleet management system can facilitate the dispatch, scheduling, and service of a variety of rental vehicles from a fleet. Such a fleet of rental vehicles can include personal-rental vehicles, provider-rental vehicles—including express-provider-rental vehicles and flexible-provider-rental vehicles—as well as third-party-rental vehicles. By integrating service, renter, or other vehicle data for disparate rental vehicles into a consolidated vehicle-fleet-platform database, the disclosed systems can display and sort vehicle-data summaries in a centralized fleet management interface.

As indicated above, the fleet management system can receive vehicle data for provider-rental vehicles used in part for transporting transportation requestors according to a provider-use rental and vehicle data for personal-rental vehicles operated by a renter according to a personal-use rental. The fleet management system can further aggregate the vehicle data for both the provider-rental vehicles and the personal-rental vehicles into a vehicle-fleet-platform database. In some cases, the fleet management system further identifies (and aggregates into the vehicle-fleet-platform database) service data for vehicle service centers associated with the provider-rental vehicles and the personal-rental vehicles. Based on one or both of the aggregated vehicle data and the aggregated service data, the fleet management system generates vehicle-data summaries for display within the fleet management interface. Such vehicle-data summaries may include or correspond to service information from the service data. Using the vehicle data or the vehicle-data summaries, the fleet management system can further organize or sort the vehicle-data summaries or other data within the fleet management interface based on user selection of selectable criteria.

When or while integrating vehicle data, in one or more embodiments, the fleet management system receives vehicle data from a variety of computing devices. For example, the fleet management system receives vehicle data from either first-party or third-party computing devices for corresponding rental vehicles. Independent of whether the rental vehicles are first or third party, in one or more embodiments, the fleet management system receives vehicle data from computing devices associated with rental vehicles, including renter computing devices, vehicle-service-computing devices at fleet-vehicle centers, and/or rental-location-computing devices. More directly, in some embodiments, the fleet management system receives vehicle data from in-vehicle-computing devices, including telematics devices.

From these and other computing devices, the fleet management system receives and aggregates a variety of vehicle data into a vehicle-fleet-platform database. To illustrate, in one or more embodiments, the fleet management system receives and aggregates rental data, such as renter history, pickup history, and/or drop-off history. Independent or together with such rental data, in one or more embodiments, the fleet management system dynamically aggregates vehicle data representing service status of fleet vehicles or vehicle history, including vehicle service history, vehicle transportation history, or vehicle mileage. In some embodiments, the fleet management system also aggregates vehicle data corresponding to a particular vehicle, such as data for a vehicle manufacturer, vehicle model, vehicle identification number (“VIN”), and/or vehicle warranty.

After or while aggregating such vehicle data, in some cases, the fleet management system utilizes the fleet-vehicle database to manage a fleet-vehicle center. To illustrate, in one or more embodiments, the fleet management system can schedule service appointments based on availability of a fleet-vehicle center, vehicle parts, and transportation schedule of a vehicle. Further, in one or more embodiments, the fleet management system sends navigation instructions to fleet vehicles to travel to particular tracks of a fleet-vehicle center based on scheduled appointments.

Independent of the type of vehicle data aggregated into the vehicle-fleet-platform database, as noted above, the fleet management system can generate vehicle-data summaries based on such data. To illustrate, vehicle-data summaries can include vehicle data corresponding to a particular fleet vehicle or a corresponding renter or account. In one or more embodiments, the fleet management system further updates vehicle-data summaries utilizing new vehicle data received from the various computing devices and/or various systems. For instance, upon a change in rental-type status, the fleet management system can updating a vehicle-data summary for a personal-rental vehicle operated by a renter according to a personal-use rental to become a provider-rental vehicle for use transporting transportation requestors according to a provider-use rental (or vice versa).

Additionally, in one or more embodiments, the fleet management system provides the vehicle-data summaries for display in a fleet management interface. In some embodiments, the fleet management system provides the vehicle-data summaries to various computing devices (e.g. rental-location computing devices, vehicle-service computing devices, third-party computing devices) for presentation as rows in a table within the fleet management interface. In some embodiments, the fleet management interface includes selectable elements corresponding to various columns corresponding to categories of vehicle data to dynamically organize or sort vehicle-data summaries within the fleet management interface.

In addition to data first-party-rental vehicles for personal or transportation provider use, the fleet management system can integrate third-party-rental vehicles into the vehicle-fleet-platform database. To illustrate, the fleet management system can generate a vehicle-fleet-platform database by aggregating vehicles and vehicle data from both third-party and first-party systems. In addition to aggregating first-party and third-party associations of fleet vehicles, the fleet management system can manage and dynamically modify available corresponding personal or provider rental statuses.

Upon assigning or reserving a renter to a particular rental vehicle, in some embodiments, the fleet management system facilitates pick up or drop off of such a rental vehicle, including contactless pick-up and/or drop-off. To illustrate, in one or more embodiments, the fleet management system provides a virtual key to a renter computing device to facilitate contactless pickup of a rental vehicle. Additionally, in one or more embodiments, the fleet management system sends navigation instructions to a renter computing device to a rental location for pickup and/or drop-off of a rental vehicle. As part of pick-up or drop-off or some other event, the fleet management system can also automatically check a renter computing device into a rental location based on identifying the location of the renter computing device.

As suggested above, the fleet management system solves several technical problems that hinder conventional rental-vehicle-computing systems. For example, the fleet management system improves the efficiency and accuracy with which conventional rental-vehicle-computing systems (or other computing systems) aggregate or surface vehicle data into integrated databases or graphical user interfaces. As noted above, some conventional rental-vehicle-computing systems isolate various databases, software platforms, or other systems to manage rental vehicles, such as by using separate and independent databases or software platforms for transportation matching, user management, rental management, etc. By contrast, the disclosed fleet management system integrates vehicle data from across different types of rental vehicles—including provider-rental vehicles used for transporting transportation requestors and personal-rental vehicles for personal transportation—into an integrated vehicle-fleet-platform database. In some cases, the disclosed fleet management system also integrates service data from various fleet-vehicle centers (e.g. vehicle service centers) into the integrated vehicle-fleet-platform database. By utilizing a shared software platform and integrated database, the fleet management system reduces both the number of digital communications and cross-platform communications required by conventional systems. In some embodiments, the fleet management system integrates data about disparate rental vehicles from a variety of computing sources, such as renter computing devices, telematic computing devices, in-vehicle-computing devices, rental-location-computing devices, or vehicle-service-computing devices. Beyond internal vehicle data or service data, the fleet management system can also fetch and integrate third-party-rental-vehicle data (e.g., using an application programming interface (“API”) call).

As further noted above, conventional rental-vehicle-computing systems often execute separate software applications with different and disconnected graphical user interfaces—forcing user devices to navigate across (and sometimes back-and-forth between) different graphical user interfaces. By contrast, in one or more embodiments, the fleet management system generates and presents vehicle-data summaries in a single fleet management interface (or a unified series of graphical user interfaces) by drawing from vehicle data and/or service data aggregated into an integrated vehicle-fleet-platform database. The fleet management system thus provides previously isolated vehicle data in a single, efficiently navigable graphical user interface or series of graphical user interfaces. In some implementations, the fleet management system also provides previously isolated service data in the same navigable graphical user interface or series of graphical user interfaces. Rather than navigating across software applications or between isolated graphical user interfaces, in one or more embodiments, the fleet management system dynamically organizes vehicle data within the fleet management interface based on a variety of user-selectable criteria. Accordingly, the fleet management system reduces or eliminates both excessive computer processing and excessive computing device interaction experienced by conventional rental-vehicle-computing systems to locate and present vehicle data from a variety of integrated subsystems to surface in a fleet management interface.

In part due to such integrated databases or user interfaces, the fleet management system improves the accuracy with which conventional rental-vehicle-computing systems locate and surface vehicle data. As suggested above, some conventional rental-vehicle-computing systems isolate vehicle data in separate databases such that vehicle data concerning vehicle repair may be stored in one database and not communicated to a separate database concerning rental reservations—thereby inaccurately indicating a rental vehicle undergoing maintenance or repair is available for reservation. By contrast, the fleet management system integrates vehicle data, communications, and/or service data from fleet-vehicle center systems, third-party systems, in-vehicle systems, rental-location systems, and/or renter computing device systems. More specifically, the fleet management system utilizes the integration of these subsystems to generate more accurate and more comprehensive vehicle-data summaries including vehicle data received from the variety of integrated subsystems. In a single fleet management interface, for instance, the fleet management system can surface vehicle-data summaries for personal-rental vehicles, provider-rental vehicles—such as express-provider-rental vehicles and flexible-provider-rental vehicles—as well as third-party-rental vehicles.

As illustrated by the foregoing discussion, the present disclosure utilizes a variety of terms to describe features and advantages of the fleet management system. Additional detail is now provided regarding the meaning of such terms. For example, as used herein, the term “vehicle data” refers to digital information corresponding to one or more vehicles, including rental vehicles. In particular, vehicle data can include information regarding the characteristics, the current status, and/or history of a vehicle. To illustrate, vehicle data can include vehicle manufacturer, vehicle model, vehicle identification number, vehicle mileage, vehicle service history, vehicle warranty data, vehicle collision data, vehicle appointment data, current renter, or vehicle transportation history.

Additionally, as used herein, the term “vehicle-fleet-platform database” refers to a database including vehicle data and/or service data corresponding to vehicles in a fleet. In particular, a vehicle-fleet-platform database can include the underlying data for vehicle-data summaries corresponding to rental vehicles. To illustrate, a vehicle-fleet-platform database can include vehicle data received from renter computing devices, telematic computing devices, in-vehicle-computing devices, rental-location-computing devices, and/or vehicle-service-computing devices.

Also, as used herein, the term “rental vehicle” refers to a transportation vehicle for rent by a rental requestor. In particular, a rental vehicle includes a transportation vehicle operated by a rental requestor to transport the rental requestor. Such vehicles may include, but are not limited to, an automobile, airplane, boat, motorcycle, or other vehicle. Rental vehicles may be stored at rental-vehicle locations.

Further, as used herein, the term “personal-rental vehicle” refers to a transportation vehicle for rent by a rental requestor for personal use. In particular, a personal-rental vehicle can include a vehicle for rent that is not for use to provide transportation services in a transportation matching system.

Additionally, as used herein, the term “provider-rental vehicle” refers to a transportation vehicle for rent by a rental requestor for at least partial use to provide transportation services (e.g., for a transportation matching system). To illustrate, a provider-rental vehicle can include a rental vehicle matched to a rental requestor via a transportation matching system subject to one or more of a variety of mileage schemes for providing transportation to transportation requestors within the transportation matching system.

Relatedly, as used herein, the term “flexible-provider-rental vehicle” refers to a provider-rental vehicle with a rental-requestor-selected allocation of personal mileage and transportation-services mileage. To illustrate, a flexible-provider-rental vehicle can correspond to a mileage scheme that includes a number of personal miles selected by a rental requestor. Also, as used herein, the term “express-provider-rental vehicles” refers to a provider-rental vehicle with allocation of personal mileage based on transportation-services mileage. To illustrate, an express-provider-rental vehicle can correspond to a mileage scheme including a number of personal miles earned for each mile driven while providing transportation services to transportation requestors for a transportation matching system.

Also, as used herein, the term “mileage scheme” refers to a configuration or program corresponding to vehicle mileage for a rental vehicle. In particular, a mileage scheme can include a method and/or algorithm for determining personal mileage and transportation-services mileage corresponding to a provider-rental vehicle. To illustrate, a mileage scheme can include a scheme for determining mileage based on user selection of a number of miles. Additionally, a mileage scheme can include a scheme for determining personal mileage based on a number of miles driven while providing transportation services to transportation requestors for a transportation matching system.

Further, as used herein, the term “third-party-rental vehicle” refers to a rental vehicle for rent to a rental requestor via a third party. In particular, a third-party-rental vehicle can include a rental vehicle owned by a third-party system and not by a fleet management system and/or transportation matching system directly. The disclosed fleet management system can integrate data and rental options concerning a third-party-rental vehicle, including integration into a fleet management database and/or a fleet management interface. To illustrate, a third-party-rental vehicle can include a third-party provider-rental vehicle and/or a third-party personal-rental vehicle.

Additionally, as used herein, the term “vehicle-data summary” refers to a synopsis or abbreviated sampling of vehicle data and/or service data corresponding to a particular vehicle. In particular, a vehicle-data summary can include an organized collection of data corresponding to a particular vehicle in a vehicle fleet, including data concerning a provider-rental vehicle, a personal-rental vehicle, and/or a third-party-rental vehicle. To illustrate, the fleet management system can generate a fleet management interface organizing a variety of vehicle-data summaries in separate rows in tabular form.

Also, as used herein, the term “renter-activity summary” refers to a synopsis or abbreviated sampling of data reflecting historical activities of a renter corresponding to a renter account. In particular, a renter-activity summary can include rental history data, payment history data, check in and check out data, notes data, and scheduling data. To illustrate, in one or more embodiments, the fleet management system organizes one or more renter-activity summaries into renter-specific graphical user interfaces.

Additionally, as used herein, the term “renter indicator” refers to a graphical element corresponding to or representing a renter. In particular, a renter indicator can include a graphical-user-interface element corresponding to a rental account. To illustrate, a renter indicator can include one or more graphical-user-interface elements including a photo, name, and/or username associated with a rental account. In one or more embodiments, in response to receiving user selection of a renter indicator associated with a renter, the fleet management system provides a graphical user interface associated with the renter.

Further, as used herein, the term “tag” refers to a data label or indicator. In particular, a tag can include a metadata tag associated with various vehicle data, vehicle-data summaries, and/or renter accounts. To illustrate, a tag can include a vehicle-damage tag, a vehicle-maintenance tag, a vehicle-service tag, and/or a variety of tags associated with vehicle data. As used herein, the term “vehicle-damage tag” refers to a tag denoting some kind of vehicle damage, including current and/or past damage. Additionally, as used herein, the term “vehicle-maintenance tag” refers to a tag denoting some kind of vehicle maintenance, including currently needed maintenance and/or maintenance performed in the past.

Additionally, as used herein, the term “virtual code” refers to a digital code, frequency, or signal to access and/or use a rental vehicle. To illustrate, a virtual code can include a digital key corresponding to a rental vehicle. In particular, a virtual code can include a digital key received wirelessly via the internet, including a radio frequency identification code. To further illustrate, a virtual code can include a near field communication code received at a renter computing device for contactless access to a corresponding rental vehicle.

Further, as used herein, the term “in-vehicle-computing device” refers to a computing device integrated into or attached inside a vehicle. In particular, an in-vehicle-computing device can include one or more computing systems within a vehicle that display digital messages or visual indicators for a transportation requestor or provider, track vehicle data, and/or record vehicle data. To illustrate, an in-vehicle-computing device can include various telematics computing systems, such as an inertial measurement unit, a Global Positioning System (“GPS”), a fuel usage monitor, an accelerometer, a gyroscope, and/or other systems.

Also, as used herein, the term “on-board-diagnostics port” refers to an interface for a computing device within a vehicle capable of receiving and transmitting data. To illustrate, an on-board-diagnostics port includes a socket in a vehicle with data-reporting capability. In particular, an on-board-diagnostics port can include a socket that can transmit vehicle data to a connected computing device. In one or more embodiments, the fleet management system utilizes an in-vehicle-computing device attached to an on-board diagnostics port to transmit and/or receive vehicle data. Further, in some embodiments, the fleet management system utilizes an in-vehicle-computing device attached to an on-board diagnostics port to receive a virtual code from a renter computing device.

Additionally, as used herein, the term “service status” refers to an indicator of whether a rental vehicle is undergoing some kind of inspection, repair, or other service, including an indicator of a type of inspection, repair, or other service. In particular, a service status can include an active status, a maintenance status, a service status, or a damaged status. To illustrate, a maintenance status can include an indicator for a rental vehicle currently undergoing routine maintenance, such as tire rotation, oil change, battery replacement, etc. Relatedly, a service status can include an indicator for a rental vehicle currently undergoing a non-routine service, such as engine repair, malfunctioning part replacement, body repair, etc. Further, a damaged status can include an indicator for a currently damaged rental vehicle, including a rental vehicle currently undergoing repair for the damage. Additionally, an active status can include an indicator for a rental vehicle that is currently active, including active in a vehicle fleet.

Further used herein, the term “fleet-vehicle center” refers to a location for rental vehicles. In particular, a fleet-vehicle center can include a location for repair, maintenance, service, and drop-off of pick-up of rental vehicles. To illustrate, a fleet-vehicle center can include a multi-track vehicle location that facilitates maintenance, service, damage repair, and/or rentals for rental vehicles, including a from vehicle fleet for a transportation matching system.

In one or more embodiments, a fleet-vehicle center can include a vehicle service center. As used herein, the term “vehicle service center” refers to a location with facilities or equipment that provide a variety of vehicle services to rental vehicles, including for collision damage, general maintenance, and other vehicle services. In one or more embodiments, a vehicle service center includes separate tracks for collision damage, routine maintenance, and other vehicle services.

Relatedly, as used herein, the term “third-party-vehicle centers” refers to fleet-vehicle centers including third-party vehicles. In particular, third-party-vehicle centers can include rental locations, service locations, maintenance locations, and/or damage repair locations that include and/or service third-party vehicles. In some embodiments, a third-party vehicle center is managed in whole or in part by a third-party system.

1 FIG. 100 116 126 100 102 108 115 As indicated above, this disclosure includes illustrative figures portraying example embodiments and implementations of the fleet management system. In accordance with one or more embodiments,indicates a schematic diagram of an environmentin which a fleet management systemcan manage various rental vehicles using a networkwithin the environment, including a personal-rental vehicle, a provider-rental vehicle, and a third-party-rental vehicle.

100 102 104 106 107 102 114 102 114 As mentioned, the environmentincludes the personal-rental vehicle, which is associated with a personal renter, a personal-renter-computing device, and an in-vehicle-computing device. As discussed above, the personal-rental vehicleincludes rental vehicles designated for personal use, not including fulfilling transportation requests for the dynamic transportation matching system. In one or more embodiments, the personal-rental vehiclecan be a first-party vehicle associated with the dynamic transportation matching systemor a third-party vehicle.

1 FIG. 100 108 110 112 111 108 114 108 110 108 114 Additionally, as shown in, the environmentincludes the provider-rental vehicle, which is associated with a provider renter, a provider-renter-computing device, and an in-vehicle-computing device. In some embodiments, the provider-rental vehicleincludes rental vehicles designated for fulfilling transportation requests and/or providing other transportation services in the dynamic transportation matching system. Additionally, in one or more embodiments, the provider-rental vehicleis further designated for some personal use by the provider renter. In one or more embodiments, the provider-rental vehiclecan be a first-party vehicle associated with the dynamic transportation matching systemor a third-party vehicle.

1 FIG. 1 FIG. 100 115 117 119 121 115 114 115 102 108 115 116 Further, as shown in, the environmentincludes the third-party-rental vehicle, which is associated with a third-party renter, a third-party-renter-computing device, and an in-vehicle-computing device. In some embodiments, the third-party-rental vehicleis associated with a third-party system, such as a partner rental-vehicle-computing system to the dynamic transportation matching system. As mentioned above, in some embodiments, the third-party-rental vehiclealso constitutes a personal-rental vehicle. Thoughillustrates one personal-rental vehicle, one provider-rental vehicle, and one third-party-rental vehicle, the fleet management systemcan manage any number of personal-rental vehicles, provider-rental vehicles, and third-party-rental vehicles.

1 FIG. 12 FIG. 113 114 116 118 100 114 113 114 113 113 106 112 119 120 122 119 113 113 114 116 113 As further shown in, the server(s)include the dynamic transportation matching system, which in turn includes the fleet management systemand the vehicle-fleet-platform database. In some embodiments, the environmentdoes not include the dynamic transportation matching system. The server(s)can generate, store, receive, and transmit various types of data including data relating to mobile devices, transportation requests, and fleet vehicles. The dynamic transportation matching systemcan use the server(s)to communicate with various computing devices. For example, the server(s)receive vehicle data of various types from the personal-renter-computing device, the provider-renter-computing device, the third-party-renter-computing device, the rental-location-computing device, the vehicle-service-computing device, and/or the third-party-renter-computing device. In some embodiments, the server(s)sends notifications, appointment information, and other vehicle data to these various computing devices. The server(s)can include one or more server device(s) that implement the dynamic transportation matching system, and in turn the fleet management system.provides additional detail regarding the server(s).

113 114 114 114 In one or more embodiments, the server(s)can implement all or a portion of the dynamic transportation matching system. The dynamic transportation matching systemmatches provider computing devices (e.g., computing devices associated with provider-rental vehicles) with transportation requestor computing devices. Additionally, in some embodiments, the dynamic transportation matching systemreceives a transportation request from a transportation requestor computing device. The transportation request can include a pickup location and a destination location.

1 FIG. 113 116 116 118 116 118 116 As also shown in, the server(s)may include or implement all or a portion of the fleet management system. As indicated above, in one or more embodiments, the fleet management systemdynamically aggregates vehicle data into a fleet-vehicle database. The fleet management systemcan utilize the vehicle-fleet-platform databaseto generate data for, update, and provide a fleet management interface including vehicle-data summaries. Further, the fleet management systemcan dynamically reorganize the fleet management interface based on user selection of portions of vehicle-data summaries and/or vehicle data categories.

116 114 114 116 114 116 116 118 114 In some embodiments, the fleet management systemcommunicates with the dynamic transportation matching systemand receives data from the dynamic transportation matching system. For example, the fleet management systemaccesses vehicle data from various renter computing devices through the dynamic transportation matching system. In addition, or in the alternative, the fleet management systemcan receive vehicle data directly from the various computing devices. Further, the fleet management systemcan provide vehicle data, vehicle data summaries, and/or the vehicle-fleet-platform databaseto the dynamic transportation matching system.

100 106 112 119 106 112 119 106 112 119 119 120 122 119 As mentioned, the environmentincludes the personal-renter-computing device, the provider-renter-computing device, and the third-party-renter-computing device. In one or more embodiments, these computing devices are associated with an application (e.g., a transportation matching system application, a rental application). In some embodiments, the personal-renter-computing device, the provider-renter-computing device, and the third-party-renter-computing deviceinclude an application comprising web browsers, applets, or other software applications (e.g. native applications) available to each of the personal-renter-computing device, the provider-renter-computing device, and the third-party-renter-computing device. Though not illustrated, the third-party-renter-computing device, the rental-location-computing device, the vehicle-service-computing device, and/or the third-party-renter-computing devicemay similarly include a provider software application, a service software application, and/or a rental software application.

100 107 111 121 107 111 121 107 111 121 107 111 121 102 108 115 As also mentioned, the environmentincludes the in-vehicle-computing devices,, and. To illustrate, the in-vehicle-computing device,, andcan each constitute a telematics computing device. More specifically, the in-vehicle-computing device,, andcan be included in a vehicle during manufacture or may be a separate device integrated into a vehicle after manufacture. In one or more embodiments, the in-vehicle-computing device,, andreceive various vehicle data from the personal-rental vehicle, the provider-rental vehicle, and the third-party-rental vehicle, respectively.

107 111 121 107 111 121 116 To illustrate, in one or more embodiments, the in-vehicle-computing devices,, andeach receive footage from a vehicle camera, odometer, diagnostics port, and other vehicle computing systems. Further, in one or more embodiments, the in-vehicle-computing devices,, andeach provide this vehicle data to the fleet management system.

1 FIG. 100 120 120 120 120 116 As also shown in, the environmentincludes the rental-location-computing device. In one or more embodiments, the rental-location-computing devicereceives vehicle data related to rental history, pickup and/or drop-off rental locations and appointments, and other vehicle data related to vehicle rentals. Additionally, the rental-location-computing devicecan receive vehicle data related to renters and/or renter accounts utilizing various rental vehicles. In some embodiments, the rental-location-computing deviceprovides the rental vehicle data to the fleet management system.

1 FIG. 100 122 122 122 122 122 116 Additionally, as shown in, the environmentincludes the vehicle-service-computing device. In one or more embodiments, the vehicle-service-computing devicereceives and/or tracks vehicle data related to various vehicle services, including at a fleet-vehicle center. To illustrate, in one or more embodiments, the vehicle-service-computing devicereceives vehicle data related to services performed at a service track, a damage track, and/or a collision track of a fleet-vehicle center. Further, in one or more embodiments, the vehicle-service-computing devicedynamically tracks availability of appointments and vehicle components at a fleet-vehicle center. Further, the vehicle-service-computing devicecan provide the vehicle data and availability data to the fleet management system.

1 FIG. 100 124 116 116 118 124 115 124 120 122 also shows that the environmentincludes the third-party-computing device. In one or more embodiments, the fleet management systemis associated with one or more third-party systems. As mentioned above, in some embodiments, the fleet management systemintegrates one or more third-party-rental vehicles from third-party systems into the vehicle-fleet-platform database. The third-party-computing devicecan receive vehicle data related to third-party vehicles, including the third-party-rental vehicle. In some embodiments, the third-party-computing devicecan also be the rental-location-computing deviceand/or the vehicle-service-computing devicethat are maintained in a third-party system.

116 116 116 114 116 116 202 206 208 210 213 211 2 FIG. As mentioned above, the fleet management systemcan track and record a variety of vehicle data for a variety of fleet vehicles. Further, the fleet management systemcan utilize the vehicle data to perform or execute various functions for the fleet management systemand/or a dynamic transportation matching system. More specifically,illustrates the fleet management systemreceiving, maintaining, and integrating various vehicle data, rental data, and user data for subsystems ranging from vehicle management to location or user management. In particular, the fleet management systemincludes a vehicle management subsystem, a rental services subsystem, a location management subsystem, a vehicle services subsystem, a user management subsystem, and an account management subsystem.

2 FIG. 2 FIG. 2 FIG. 202 206 208 210 213 211 118 116 212 214 216 218 116 As illustrated by, in one or more embodiments, the vehicle management subsystem, the rental services subsystem, the location management subsystem, the vehicle services subsystem, the user management subsystem, and/or the account management subsystemstore the vehicle data listed inin the vehicle-fleet-platform database. In addition to maintaining the listed vehicle data illustrated by, the fleet management systemalso performs various functions for scheduling, workflow, events, and records. While the following paragraphs describe data stored or managed, or functions performed by, various subsystems, the fleet management systemas a larger system can store or manage the data described below or perform the functions described below.

116 116 118 118 116 116 118 In one or more embodiments, the fleet management systemachieves interoperability of these various subsystems in order to facilitate utilization of resources across subsystems. To illustrate, the fleet management systemcentrally manages the subsystems. Accordingly, the vehicle-fleet-platform databaseprovides unified data access across the various subsystems. By integrating vehicle data from across subsystems within the vehicle-fleet-platform database, the fleet management systemimproves efficiency in both automation and predictive models. To illustrate, the fleet management systemcan produce and utilize improved predictive models by utilizing the unified data in the vehicle-fleet-platform database.

2 FIG. 116 202 202 118 202 As shown in, in one or more embodiments, the fleet management systemincludes the vehicle management subsystem. More specifically, in one or more embodiments, the vehicle management subsystemintegrates data for both first-party vehicles and third-party vehicles into the vehicle-fleet-platform databasewhile tracking the first-party or third-party association of each vehicle. Further, in some embodiments, the vehicle management subsystemtracks third-party-rental vehicles from multiple third-parties.

2 FIG. 2 FIG. 202 202 202 202 As further shown in, the vehicle management subsystemmanages various rental vehicles including a variety of types of vehicle data. For example, the vehicle management subsystemdetermines and stores various vehicle metadata in the fleet-vehicle database. Further, the vehicle management subsystemprovides the vehicle metadata in vehicle-data summaries in a fleet management interface. For example, as shown in, the vehicle management subsystemcan determine and store telematic data, availability and reservation data, service status data, manufacturer and model data, and/or inspection data.

202 116 116 202 To illustrate, in one or more embodiments, the vehicle management subsystemreceives various telematics data from telematics devices associated with fleet vehicles (e.g. rental vehicles). As discussed above, the fleet management systemcan receive telematics data from telematics devices connected to a rental vehicle and/or from computing systems within a fleet vehicle itself. For example, telematics data can include mileage information determined based on received odometer readings. Additionally, telematics data can include collision data determined based on a diagnostics port and/or a vehicle camera. The fleet management systemcan also determine collision data based on past collision services at a vehicle-service center. Further, the vehicle management subsystemcan aggregate telematics data including tire pressure data, engine temperature data, oil pressure data, brakes information, battery information, fueling information, airbag information, security system information, traction information, washer fluid information, and/or various other telematics information.

2 FIG. 202 202 118 202 202 As also shown in, the vehicle management subsystemcan aggregate availability data corresponding to various fleet vehicles. To illustrate, in one or more embodiments, the vehicle management subsystemaggregates availability data from rental-location-computing devices, in-vehicle-computing devices, and/or renter computing devices (e.g. a personal-renter-computing device or a provider-renter computing device) into the vehicle-fleet-platform database. In one or more embodiments, the vehicle management subsystemaggregates various data appointments associated with a renter computing device and/or renter account at a fleet-vehicle center and/or a third-party-vehicle center. The vehicle management subsystemcan also receive availability and/or appointment data corresponding to a rental vehicle from renter computing devices.

202 202 202 202 In some embodiments, the vehicle management subsystemalso aggregates service status data. For example, fleet vehicles at various times may be active or may be inactive for a variety of reasons. In one or more embodiments, the vehicle management subsystemaggregates the activity and/or reason for inactivity of fleet vehicles. To illustrate, the vehicle management subsystemcan determine and aggregate whether a fleet vehicle has an active status, a maintenance status, a service status, or a damaged status. Relatedly, the vehicle management subsystemcan track and record inspection data, including results of a government safety inspection or emission inspection.

2 FIG. 202 202 202 202 116 Additionally, as shown in, the vehicle management subsystemaggregates and stores manufacture and model data corresponding to various fleet vehicles. To illustrate, in some embodiments, the vehicle management subsystemaggregates vehicle makes and models. Further, the vehicle management subsystemcan aggregate vehicle classes, sizes, and capacities. In some embodiments, the vehicle management subsystemfurther aggregates data associated with particular makes and models, such as warranty data corresponding to a manufacturer. In addition or in the alternative, the fleet management systemcan track warranty data for specific rental vehicles based on a corresponding VIN.

202 202 202 In one or more embodiments, the vehicle management subsystemtracks availability and reservation data for a variety of fleet locations, such as fleet-vehicle centers, third-party-vehicle centers, and rental locations. In some embodiments, the vehicle management subsystemtracks availability of appointments, pickup times, and drop-off times. To illustrate, the vehicle management subsystemcan track appointments for a variety of fleet locations, such as fleet-vehicle centers and/or rental locations.

2 FIG. 206 206 206 206 206 As also shown in, the rental services subsystemaggregates and stores vehicle data corresponding to rental services. For example, the rental services subsystemaggregates various reservations. In one or more embodiments, the rental services subsystemaggregates pickup dates and/or appointments and drop-off dates and/or appointments. Additionally, the rental services subsystemtracks rental vehicles associated with reservations and aggregates information regarding whether a reservation is for a personal-rental vehicle or a provider-rental vehicle. Further, in one or more embodiments the rental services subsystemaggregates data regarding mileage schemes corresponding to reservations.

206 206 206 206 9 FIG. Additionally, in one or more embodiments, the rental services subsystemtracks rental services data including virtual codes. As described below with regard to, the rental services subsystemcan store virtual codes that grant access to particular fleet rental vehicles for contactless pick up or drop off of a rental vehicle. In some embodiments, the rental services subsystemaggregates and stores these virtual codes. Additionally, in one or more embodiments, the rental services subsystemgenerates updated virtual codes based on a new rental appointment corresponding to a fleet rental vehicle.

2 FIG. 206 206 206 206 As further shown in, the rental services subsystemcan also aggregate rental categories corresponding to rental vehicles. For example, in one or more embodiments, the rental services subsystemtracks various categorizations of rental vehicles, including size, capacity, silhouette, doors, and other vehicle classifications. Further, in one or more embodiments, the rental services subsystemprovides a particular available rental vehicle in a vehicle classification for selection in a rental reservation graphical user interface. To illustrate, in one or more embodiments, the rental services subsystemprovides an indication of a specific rental vehicle rather than a vehicle classification.

206 206 206 In one or more embodiments, the rental services subsystemaggregates renter data corresponding to renter accounts. The rental services subsystemcan aggregate rental history data from rental-location-computing devices and/or renter computing devices. Additionally, in one or more embodiments, the rental services subsystemaggregates background check data, do-not-rent data indicating untrustworthy renters, outstanding balances, and other rental vehicle data.

2 FIG. 2 FIG. 208 208 208 As also shown in, the location management subsystemaggregates vehicle data corresponding to location management. In one or more embodiments, the location management subsystemtracks the physical location, including global positioning system data and address data for various locations and centers. For example, as shown in, the location management subsystemtracks the location of fleet-vehicle centers, third-party-vehicle centers, and various rental locations.

2 FIG. 210 210 210 210 210 210 Further, as shown in, the vehicle services subsystemaggregates vehicle data corresponding to fleet service management. In some embodiments, the vehicle services subsystemmanages, tracks, and aggregates data regarding past, present, and future servicing of fleet vehicles. For example, the vehicle services subsystemaggregates maintenance schedule, parts supply chain data, service and maintenance queue data, and in-center and mobile queue data. In some embodiments, the vehicle services subsystemtracks availability of particular vehicle parts, vehicle supplies, and services. Further, in one or more embodiments, the vehicle services subsystemtracks availability of rental vehicles and various classifications of rental vehicles. Additionally, the vehicle services subsystemcan determine and store maintenance schedules corresponding to fleet vehicles and a parts supply chain corresponding to various fleet locations, including vehicle-service centers.

210 210 Further, in some embodiments, the vehicle services subsystemtracks various queues in fleet-vehicle centers and third-party-vehicle centers. For example, in one or more embodiments, a fleet-vehicle center includes various separate tracks for servicing fleet vehicles, including a service track, a maintenance track, and/or a collision track. In one or more embodiments, the vehicle services subsystemtracks and manages in-center queues of vehicles for each of these tracks separately.

210 210 Further, in one or more embodiments, fleet-vehicle centers manage mobile service vehicles that drive to a location of a fleet rental vehicle and bring services to the fleet vehicle. In some embodiments, the vehicle services subsystemmonitors progress of these mobile services in real-time based on data received from mobile vehicle-service-computing devices. Accordingly, the vehicle services subsystemcan manage mobile queues corresponding to mobile service vehicles in addition to in-center queues.

2 FIG. 211 211 211 211 As also shown in, the account management subsystemaggregates and manages vehicle data corresponding to user management. To illustrate, the account management subsystemcan receive data corresponding to user accounts including renter account and provider accounts. In one or more embodiments, the account management subsystemreceives account data from renter computing devices, vehicle-service-computing devices, transportation requestor devices, and/or provider computing devices. The account management subsystemcan receive account data including account identifiers, account activity, account permissions, etc.

211 211 211 211 In one or more embodiments, the account management subsystemdetermines roles and permissions associated with various user accounts based on received account data. Relatedly, the account management subsystemcan provide vehicle data to computing devices based on associated roles and permissions. In some embodiments, the account management subsystemalso manages account configuration corresponding to various renter and/or provider accounts. To illustrate, account management subsystemcan receive and manage account settings, including notification settings, user selections, etc.

2 FIG. 213 213 116 213 213 Additionally, as shown in, the user management subsystemaggregates and manages data corresponding to user management. To illustrate, the user management subsystemcan receive data corresponding to system users, including user standing and eligibility, and user profile information. In some embodiments, the fleet management systemtracks standing and eligibility corresponding to rental requestor accounts, provider accounts, and or transportation requestor accounts. In one or more embodiments, the user management subsystemreceives user data from renter computing devices, vehicle-service-computing devices, requestor devices, and/or provider computing devices. The user management subsystemcan receive user data including user infractions or discipline, user demographic information, and/or user activity and history data.

116 116 116 116 212 214 216 218 2 FIG. As discussed above, in one or more embodiments, the fleet management systemperforms or executes various functions based on the aggregated vehicle data. To illustrate, the fleet management systemutilizes vehicle data received from a variety of computing devices and subsystems to determine various actions and/or options for the fleet management system. For example, as shown in, the fleet management systemcan perform various functions for the scheduling, the workflow, the events, and the recordsof various rental vehicles.

2 FIG. 116 212 116 116 116 As illustrated by, in one or more embodiments, the fleet management systemdetermines the schedulingfor various appointments, including rental appointments and service appointments based on the aggregated vehicle data. The fleet management systemunifies scheduling by utilizing data from various subsystems. For example, the fleet management systemcan utilize availability data, vehicle manufacturer and model data, and service status data to determine availability for pickup of a rental vehicle. In another example, the fleet management systemutilizes vehicle part availability data, service availability data, and fleet-vehicle center location data to identify the soonest appointment for a particular vehicle repair at a fleet-vehicle center within ten miles of the particular vehicle.

2 FIG. 116 214 116 116 116 Additionally, as shown in, the fleet management systemutilizes vehicle information to manage the workflowfor scheduling, services, and other items. More specifically, in one or more embodiments, the fleet management systemutilizes vehicle data to generate various schedules for various fleet-vehicle locations. For example, the fleet management systemcan utilize fleet-vehicle center data to determine efficient workflows for various service tracks. Accordingly, the fleet management systemcan build various vehicle queues based on availability at the fleet-vehicle center.

116 216 116 116 116 116 Additionally, in one or more embodiments, the fleet management systemutilizes the aggregated vehicle data to determine and schedule the events. For example, in one or more embodiments, the fleet management systemcan utilize vehicle data to determine modifications and other actions for the fleet management system. For example, the fleet management systemcan identify a projected demand for a particular kind of rental vehicle relative to an actual availability of that type of rental vehicle. Based on the demand relative to the availability, the fleet management systemcan provide notifications, incentives, or reminders to renters of the vehicle type to return the vehicle type, including to return early.

116 216 116 116 Additionally, in one or more embodiments, fleet management systemprocesses eventsincluding rental events, such as consequences, fines, and tolls. In some embodiments, the fleet management systemprovides portions of the fleet-vehicle database to a third-party system to process these rental events. In some embodiments, the fleet management systemand/or the third-party system provide notification of these rental events to a renter computing device.

116 218 116 218 116 218 Further, in some embodiments, the fleet management systemutilizes the aggregated vehicle data to generate the records. In addition to dynamically tracking various vehicle data in real-time, the fleet management systemcan archive past vehicle data in the records. In one or more embodiments, the fleet management systemcan utilize the recordsto predict future vehicle data trends, and to make a variety of other determinations.

116 116 116 116 More specifically, in some embodiments, the fleet management systemstores all documents and audit records associated with renters and rental vehicles. In one or more embodiments, the fleet management systemmanages document templates and document rendering, including for rental contracts, inspection reports, purchase orders, etc. To illustrate, the fleet management systemcan generate templates for a variety of user experience points. Additionally, the fleet management systemstores user and vehicle audit records.

116 116 3 FIG. As discussed above, the fleet management systemgenerates vehicle-summaries for display within a fleet management interface. In accordance with one or more embodiments,illustrates an overview of a process by which the fleet management systemaggregates vehicle data for provider-rental vehicles and personal-rental vehicles and generates vehicle-data summaries for the different rental vehicles for display in a fleet management interface.

3 FIG. 116 302 116 116 As shown in, the fleet management systemperforms an actof receiving vehicle data. To illustrate, the fleet management systemreceives one or both of (i) vehicle data based on data inputs associated with a set of provider-rental vehicles used in part by providers for transporting requestors according to a provider-use rental and (ii) vehicle data based on data inputs associated with a set of personal-rental vehicles operated by renters for self-transportation according to a personal-use rental. Accordingly, in some embodiments, the fleet management systemreceives vehicle data for both provider-rental vehicles and personal-rental vehicles. Further, in one or more embodiments, the provider-rental vehicles can include flexible-provider-rental vehicles and/or express-provider rental vehicles. Provider-rental vehicles and personal-rental vehicles can likewise be third-party vehicles.

116 116 More specifically, the fleet management systemreceives vehicle data from renter computing device(s), rental-location-computing device(s), vehicle-service-computing device(s), third-party computing device(s), in-vehicle-computing device(s), and/or telematic computing device(s). Additionally, the fleet management systemcan receive the vehicle data from these various computing devices, including via a dynamic transportation matching system.

116 As discussed above, in one or more embodiments, the various computing devices can be included in a variety of subsystems. To illustrate, the rental-location-computing device(s) may be part of an entity, subsystem, and organization otherwise separate from the telematic computing device(s). Thus, the fleet management systemcan aggregate vehicle data from a variety of subsystems that would be disconnected in conventional systems to improve overall efficiency of the vehicle fleet.

3 FIG. 116 303 116 As further shown in, in one or more embodiments, the fleet management systemperforms an actof identifying service data for vehicle service centers. This act is optional and may or may not be performed in various embodiments. In one or more embodiments, the fleet management systemidentifies service data for vehicle service centers associated with a set of provider-rental vehicles and a set of personal-rental vehicles.

116 116 305 116 116 305 3 FIG. As indicated above, the fleet management systemcan identify and compile service data for particular rental vehicles, including fleet vehicles and/or third-party-rental vehicles. To illustrate, as shown in, the fleet management systemidentifies service data concerning rental vehicles scheduled to be serviced by, currently serviced by, or previously serviced by a vehicle service center. The fleet management systemcan likewise identify service data corresponding to services scheduled or performed at additional vehicle service centers. For example, the fleet management systemidentifies prior services performed for rental vehicles, vehicle parts installed or repaired for rental vehicles, prior appointment times, prior renter interactions, and other data regarding the interactions of rental vehicles at the vehicle service center.

3 FIG. 116 308 118 116 308 116 Additionally, as shown in, the fleet management systemperforms an actof aggregating vehicle data into a vehicle-fleet-platform database (e.g. the vehicle-fleet-platform database). The fleet management systemintegrates vehicle data into the vehicle-fleet-platform database based on communications with the variety of computing sources described above. Optionally, the actalso includes aggregating service data into the vehicle-fleet-platform database. Accordingly, in some embodiments, the fleet management systemaggregates, into a vehicle-fleet-platform database, vehicle data for a set of provider-rental vehicles, vehicle data for a set of personal-rental vehicles, and service data for one or more vehicle service centers.

3 FIG. 3 FIG. 116 304 306 116 116 307 As shown in, the fleet management systemaggregates both provider-rental-vehicle dataconcerning provider-rental vehicles and personal-rental-vehicle dataconcerning personal-rental vehicles. As mentioned above, the fleet management systemcan further aggregate vehicle data concerning service status, vehicle manufacturers, and/or scheduling availability. As further shown in, in some embodiments, the fleet management systemaggregates service datafrom a variety of vehicle service centers, including service data from vehicle-service-computing devices or vehicle computing devices.

3 FIG. 116 310 116 116 307 307 As also shown in, the fleet management systemperforms an actof generating vehicle-data summaries for display in a fleet management interface. In one or more embodiments, the fleet management systemgenerates fleet-vehicle summaries including selected information from the aggregated vehicle data corresponding to various fleet vehicles. Additionally, in one or more embodiments, the fleet management systemgenerates (i) vehicle-data summaries for a set of provider-rental vehicles with (or including) corresponding service information from the service dataand (ii) vehicle-data summaries for a set of personal-rental vehicles with (or including) corresponding service information from the service data.

3 FIG. 5 FIG. 7 7 FIGS.A-C 116 314 316 116 312 312 More specifically, as shown in, the fleet management systemgenerates provider-rental vehicle summariesand personal-rental vehicle summaries. To illustrate, the fleet management systemgenerates vehicle summaries by organizing information based on corresponding vehicle and various vehicle data categories for display within a fleet management interface. As described below, for example, the fleet management interfacecan include the fleet management interface illustrated inand/or the fleet-location-management interfaces illustrated in.

3 FIG. 116 314 316 312 Additionally, as shown in, the fleet management systemsends data for vehicle-data summaries, including the provider-rental vehicle summariesand the personal-rental vehicle summaries, to a computing device for organization into the fleet management interface. In one or more embodiments, the computing device that received the vehicle-data summaries organizes and re-organizes the vehicle-data summaries based on user selection of various criteria, including vehicle data categories.

116 402 400 402 116 4 FIG. As discussed briefly above, in one or more embodiments, the fleet management systemmanages one or more fleet-vehicle centers.illustrates an example of a fleet-vehicle centerat a location. The fleet-vehicle centercan provide a variety of types of services to fleet vehicles, including as scheduled by the fleet management system.

4 FIG. 402 404 404 402 406 406 406 116 406 406 406 116 402 a c a b c a b c As shown in, for instance, the fleet-vehicle centerincludes various vehicle tracks-. More specifically, the fleet-vehicle centerincludes a service track, a maintenance track, and a collision track. The fleet management systemcan utilize the service track, the maintenance track, and the collision trackfor different types of services corresponding to general service, routine maintenance, and collision repair, respectively. Accordingly, the fleet management systemcan utilize the fleet-vehicle centerto provide efficient and streamlined service to rental vehicles.

404 404 404 404 116 116 a c a c Each of the vehicle tracks-include various bays within the vehicle tracks-. In one or more embodiments, the fleet management systemtracks the progress of a vehicle through the various bays. For example, the fleet management systemcan track progress of a vehicle through different service bays based on user input to a vehicle-service-computing device. In addition or in the alternative, a vehicle-service-computing device can automatically track movement of vehicles through service bays based on wireless communication with a vehicle and/or an in-vehicle-computing device.

116 116 118 116 In one or more embodiments, the fleet management systemreceives the tracking information from the vehicle-service-computing device. Further, in some embodiments, the fleet management systemintegrates the tracking information about service, maintenance, and repairs into the vehicle-fleet-platform database. Accordingly, in one or more embodiments, the fleet management systemschedules rentals for rental requestors utilizing the tracking information.

116 116 116 116 In addition to tracking scheduling and progress of vehicle repairs and maintenance, in one or more embodiments, the fleet management systemprovides updates to a renter computing device, a rental-location computing device, and/or a vehicle-service-computing device based on the progress of a corresponding service. To illustrate, in one or more embodiments, the fleet management systemprovides notifications as a fleet vehicle moves through the service bays. In addition or in the alternative, the fleet management systemcan determine an estimated time of completion of the service based on the tracked progress of a rental vehicle through the service bays. Accordingly, the fleet management systemcan provide a notification of the estimated time of completion to a corresponding renter computing device, rental-location computing device, and/or vehicle-service-computing device.

116 404 404 116 402 404 404 116 404 404 116 a c a c a c As discussed above, in one or more embodiments, the fleet management systemdynamically manages queues corresponding to the vehicle tracks-. More specifically, the fleet management systemdetermines and updates a queue of vehicles scheduled for and/or waiting for services at the fleet-vehicle center, where each of the vehicle tracks-can have a separate queue. In addition, the fleet management systemcan utilize estimated times of completion of vehicles currently inside service bays to update and manage vehicle queues corresponding to the vehicle tracks-. Further, the fleet management systemcan utilize the estimated times to generate notifications for renter computing devices in those queues.

404 404 402 404 404 404 404 404 116 404 404 116 402 116 116 a c a b c a c a c In addition to the vehicle tracks-, the fleet-vehicle centerincludes a service entrance, a maintenance entrance, and a collision entrance(collectively referred to as the entrances-). In one or more embodiments, the fleet management systemsends navigation instructions to a computing device associated with a fleet vehicle to travel to a particular entrance of the entrances-. To illustrate, the fleet management systemcan provide navigation instructions to a renter computing device for a scheduled service at the fleet-vehicle center. In some embodiments, as part of the navigation instructions, the fleet management systemprovides navigation instructions specifically to a service entrance corresponding to the scheduled service type. Additionally, in one or more embodiments, the fleet management systemprovides a renter computing device with a corresponding photo of the correct entrance for the vehicle in order to aid in navigation to the correct service track.

4 FIG. 402 408 408 402 408 408 116 408 408 408 408 408 408 116 408 408 402 a b a b a b a b a b a b As further shown in, the fleet-vehicle centeralso includes mobile service vehiclesand. In one or more embodiments, the fleet-vehicle centerprovides mobile maintenance or repair services for fleet vehicles via the mobile service vehiclesand. More specifically, the fleet management systemschedules and/or dispatches the mobile service vehiclesandfor mobile services based on vehicle supplies and capabilities of the mobile service vehiclesand. For instance, the mobile service vehiclesandoptionally include equipment or parts to repair or replace a flat tire, replace a battery, replace a windshield, supply fuel, or tow a vehicle. In one or more embodiments, the fleet management systemtracks availability, vehicle supplies, and vehicle parts for each of the mobile service vehiclesandand any additional mobile service vehicles at the fleet-vehicle center.

116 406 406 406 116 116 408 408 116 408 408 116 a b c a b a b In some embodiments, the fleet management systemdynamically manages queues corresponding to both in-center services (e.g., on the service track, the maintenance track, and the collision track) and mobile services. As discussed above, in some embodiments, the fleet management systemtracks progress of fleet vehicles through in-center services and provides queue notifications accordingly. Similarly, the fleet management systemcan track progress of mobile services corresponding to the mobile service vehiclesand. Further, in one or more embodiments, the fleet management systemtracks movement of the mobile service vehiclesandbetween service appointments via GPS. In one or more embodiments, the fleet management systemutilizes this progress to provide notifications to computing devices in a mobiles service queue.

116 402 116 402 408 408 116 116 a b To facilitate either on-site service or mobile services, in one or more embodiments, the fleet management systemprovides a renter computing device with a graphical user interface for scheduling an appointment at the fleet-vehicle center. More specifically, in some embodiments, the fleet management systemautomatically provides a notification to a renter computing device to schedule an appointment based on aggregated vehicle data indicating an upcoming vehicle service. Such vehicle service may be fulfilled either on-site at the fleet-vehicle centeror by mobile services via the mobile service vehiclesor. For example, the fleet management systemcan utilize vehicle mileage data and service history data to determine to send a notification to schedule a visit for routine maintenance. Additionally, in some embodiments, the fleet management systemutilizes data from telematics devices or other in-vehicle-computing devices to determine to send a notification to schedule a repair.

116 402 116 116 Additionally, in some embodiments, the fleet management systemdynamically tracks availability of resources, including vehicle components, at the fleet-vehicle center. Thus, the fleet management systemcan utilize the availability data to schedule vehicle appointments at fleet-vehicle centers that are equipped to perform particular service, maintenance, and/or repair. Accordingly, in one or more embodiments, the fleet management systemutilizes availability of vehicle supplies, vehicle parts, and service professionals to determine an appropriate location for a fleet-vehicle center or a mobile service for an appointment for a fleet vehicle.

402 402 402 Further, in one or more embodiments, the fleet-vehicle centercan also include a rental location. To illustrate, in some embodiments, the fleet-vehicle center can include rental vehicles for pickup or drop-off. Further, the fleet-vehicle centercan manage pickup and/or drop-off of the various rental vehicles for a rental location (e.g. a rental lot) at the fleet-vehicle center.

116 In certain implementations, the fleet management systemmanages vehicle services and computing devices at a fleet-vehicle center (e.g., a vehicle service center) as described in Laerte Zatta et al., Vehicle Service Center Dispatch System, U.S. application Ser. No. 16/727,715 (filed Dec. 26, 2019); Laerte Zatta et al., Intelligent Management of One or More Machines of a Vehicle Service Center, U.S. application Ser. No. 16/727,746 (filed Dec. 26, 2019); and Laerte Zatta et al., Intelligent Management of One or More Display Devices of a Vehicle Service Center, U.S. application Ser. No. 16/727,773 (filed Dec. 26, 2019), each of which is incorporated by reference in its entirety.

5 FIG. 5 FIG. 501 500 116 500 500 506 illustrates a computing devicepresenting a fleet management interfacein accordance with one or more embodiments. As discussed above, the fleet management systemgenerates vehicle-data summaries corresponding to fleet vehicles of various types for the fleet management interface. As shown in, the fleet management interfaceincludes these vehicle-data summaries as rows in a vehicle-data-summaries area.

116 501 500 501 500 116 116 501 500 501 500 116 5 FIG. 5 FIG. As discussed above, the fleet management systemcan provide vehicle data summaries to the computing devicefor presentation in the fleet management interfaceaccording to a software application executed by the computing device.illustrates the fleet management interfacethat the fleet management systemprovides for dynamic organization and reorganization of vehicle-data summaries. The fleet management systemcan provide data to the computing deviceto present the fleet management interfaceaccording to computer-executable instructions on a software application of the computing device(e.g., web browser or native application). Additionally, thoughillustrates the fleet management interfacewith example designs, the fleet management systemcan provide data for a fleet management interface in accordance with a variety of visual designs.

5 FIG. 5 FIG. 5 FIG. 500 502 502 502 502 502 502 502 501 As shown in, the fleet management interfaceincludes an aggregated statistics bar. The aggregated statistics barincludes various statistics regarding the vehicle fleet as a whole. In one or more embodiments, the aggregated statistics barincludes a snapshot of rental vehicles across different vehicle types according to various categories. For example, as shown in, the aggregated statistics barshows that 0.99% of fleet vehicles are inactive, 8.3% of fleet vehicles experienced expiration of a service-level-agreement (SLA), 0.99% of fleet vehicles are subject to repossession, 2.32% of fleet vehicles are undergoing maintenance, 3.65% of fleet vehicles are undergoing cleaning, 1.99% of fleet vehicles are involved in some sort of legal issue, and 23% of fleet vehicles are active. Thoughillustrates the aggregated statistics barincluding these particular statistics, the aggregated statistics barcan include a variety of types of statistics related to a fleet of rental vehicles. To illustrate, the statistics in the statistics barcan change when the computing devicesorts and/or filters the vehicle-data summaries according to various selected criteria.

5 FIG. 5 FIG. 5 FIG. 5 FIG. 500 504 506 116 504 506 504 504 116 As also shown in, the fleet management interfaceincludes a filtering barcorresponding to the vehicle-data-summaries area. In one or more embodiments, the fleet management systemcan utilize an indication of user input at a filter option within the filtering barto filter presentation of vehicle-data summaries in the vehicle-data-summaries area. For example, as shown in, the filtering barincludes filters corresponding to various vehicle data. More specifically,illustrates that the filtering barincludes filtering options (e.g., drop-down menus) corresponding to a service status, a vehicle class, vehicle tags, service locations, vehicle make (e.g. vehicle manufacturer), and vehicle model. However, the fleet management systemcan filter the vehicle-data summaries based on a variety of types of vehicle data in addition to those illustrated in.

5 FIG. 501 501 501 501 500 As suggested above and in, the computing devicecan filter the vehicle-data summaries based on a variety of selected criteria, including based on selection of columns corresponding to a table including the vehicle-data summaries. For example, in some embodiments, the computing devicefilters the vehicle-data summaries based on service status in response to detecting user selection of a sorting option corresponding to service status. Similarly, in one or more embodiments, the computing devicefilters the vehicle-data summaries based on a vehicle manufacturer or vehicle models based on user selection of a sorting option corresponding to the vehicle manufacturers or the vehicle models. Additionally, the computing devicecan order the vehicle-data summaries within the fleet management interfacebased on various user-selected criteria.

5 FIG. 5 FIG. 5 FIG. 500 508 510 511 512 508 510 511 512 508 510 511 1 500 As also shown in, the fleet management interfaceincludes a variety of columns corresponding to the vehicle-data summaries. In one or more embodiments, the columns corresponding to the vehicle-data summaries are user-selectable sorting options. For each vehicle-data summary, for example, the fleet management interface includes a VIN column(i.e., a vehicle identification number column), a make column, model column, and a license plate column. As shown in, the VIN columnincludes a VIN corresponding to rental vehicles. Additionally, the make columnincludes manufacturer information. Also, the model columnincludes model information for each rental vehicle. The license plate columnincludes license plate information. Though each of the VIN column, the make column, and the model columninclude placeholder information in(e.g., B2345678901, Make A, Model), the fleet management interfacewill include vehicle data corresponding to fleet vehicles.

500 514 116 116 116 5 FIG. In addition to the VIN, make, model, and plate columns, the fleet management interfacefurther includes a service status column. In one or more embodiments, the fleet management systemcan determine service status that reflects fleet vehicles activity or inactivity for a variety of reasons. As shown in, fleet management systemcan determine and provide service statuses including active, service, maintenance, and/or damaged. In addition or in the alternative, the fleet management systemcan utilize additional service statuses, such as down, available, providing transportation, etc.

116 116 116 116 514 In one or more embodiments, the fleet management systemutilizes the aggregated vehicle data to automatically change the service status of a fleet vehicle. For example, in one or more embodiments, the fleet management systemreceives information as to the availability of a fleet vehicle from a corresponding computing device (e.g., a renter computing device). Additionally, the fleet management systemcan determine whether and what kind of vehicle service is scheduled for the fleet vehicle. Thus, based on vehicle availability data and service schedules, the fleet management systemcan dynamically update service status in a vehicle-data summary under the service status column.

5 FIG. 500 516 518 516 518 114 As further shown in, the fleet management interfaceincludes an SLA column(i.e., a service-level-agreement column) and a downtime column. In one or more embodiments, the SLA columnincludes information as to time remaining in a service-level agreement. Additionally, the downtime columnincludes timing information as to the length that a vehicle has gone without providing transportation services for the transportation matching system.

5 FIG. 500 520 116 116 116 Further, as shown in, the fleet management interfaceincludes a tags column. In one or more embodiments, the fleet management systemcan include a variety of tags denoting a variety of information, including tags reflecting user input. For example, the fleet management systemcan automatically generate a tag based on received vehicle status data. In addition or in the alternative, the fleet management systemcan receive user input for a tag, including a service tag from a vehicle-service-computing device.

5 FIG. 520 524 116 Further, in one or more embodiments, the tags column can include a vehicle-damage tag indicating a type of damage to a rental vehicle. As shown in, the tags columnincludes a vehicle-damage tag “frnt. bumper dmg.” in a vehicle-data summary. In one or more embodiments, the vehicle-damage tag “frnt. bumper dmg.” indicates damage to the front bumper. It will be appreciated, however, that the fleet management systemcan receive and provide a variety of vehicle-damage tags indicating a variety of damage to rental vehicles.

501 524 500 524 508 510 1 511 512 514 516 518 520 As an illustration of a vehicle-data summary, the computing devicedisplays the vehicle-data summarywithin the fleet management interface. As shown in this particular example, the vehicle-data summaryincludes (i) a VIN B2345678901 in the VIN column; (ii) “Make A” in the make column; (iii) “Model” in the model column; (iv) a plate identifier “CK4728” in the plate column; (v) an active service status in the service status column; (vi) an indicator of “1 d under” in the SLA column; (vii) an indicator of “11 days” of downtime in the downtime column; and (viii) the vehicle-damage tag “Frnt. Bumper Dmg” in the tags column.

500 522 522 522 501 522 522 116 522 5 FIG. 5 FIG. 5 FIG. In addition to vehicle-data summaries, the fleet management interfaceincludes an expanded-vehicle-data summary. As shown in, the expanded-vehicle-data summaryincludes additional vehicle data corresponding to a particular selected vehicle-data summary. For example, as shown in, the expanded-vehicle-data summaryincludes additional tabs for notes and vehicle components. Additionally, the computing deviceshows various additional vehicle data, such as odometer data, maintenance information, and vehicle registration information. The expanded-vehicle-data summaryalso shows additional vehicle data, such as location data and rental information. Whileillustrates a particular arrangement of vehicle data in the expanded-vehicle-data summary, the fleet management systemcan generate the expanded-vehicle-data summaryto include a variety of different vehicle data in a variety of arrangements.

524 522 116 116 116 In one or more embodiments, the vehicle-data summaryand/or the expanded-vehicle-data summarycan include an indicator for whether the vehicle is an express-provider-rental vehicle or a flexible-provider-rental vehicle. As indicated above, in one or more embodiments, an express-provider-rental vehicle is a provider-rental vehicle corresponding to a mileage agreement that dictates personal mileage based on user selection. To illustrate, the fleet management systemcan receive (e.g., via a provider computing device) a user selection of personal mileage for a provider account. As further indicated above, in some embodiments, a flexible-provider-rental vehicle is a provider-rental vehicle corresponding to a mileage agreement that dictates personal mileage based on miles driven by a corresponding provider account in providing transportation services on a transportation matching system. To illustrate, the fleet management systemcan receive mileage driven in providing transportation services from a vehicle computing device and/or from a provider computing device. Additionally, the fleet management systemcan allocate personal mileage based on a predetermined ratio between personal mileage and mileage driven in providing transportation services.

116 116 116 116 116 In some embodiments, the fleet management systemreceives a selection from a renter computing device indicating a modification to the provider-rental status or personal-rental status of a rental vehicle. To illustrate, in some embodiments, the fleet management systemcan receive updated vehicle data from a renter computing device. For example, the fleet management systemcan receive updated vehicle data corresponding to a rental vehicle that changes a rental vehicle from a personal-rental vehicle to a provider-rental vehicle or vice versa. Additionally or in the alternative, the fleet management systemcan receive updated vehicle data corresponding to a rental vehicle that changes a rental vehicle from a flexible-provider-rental vehicle to an express-provider-rental vehicle or vice versa. Based on the receipt of such updated vehicle data, the fleet management systemcan update a vehicle-data summary for the rental vehicle to indicate the corresponding change in status.

116 116 116 In one or more embodiments, the fleet management systemprovides data for the vehicle-data summaries, statistics, and sorting concerning any provider-rental vehicle or personal-rental vehicle within a fleet. Further, the fleet management systemprovides this data for provider-rental vehicles and personal-rental vehicles across various different rental locations. Additionally, the fleet management systemcan provide data for rental provider-rental vehicles and personal-rental vehicles in different regions.

116 116 601 602 618 6 FIG.A 6 FIG.A As discussed briefly above, the fleet management systemcan facilitate fleet vehicle rentals.illustrates the fleet management systemcommunicating with a third-party systemto reserve a rental vehicle and facilitate pickup and return of a third-party-rental vehicle. More specifically,illustrates acts undertaken during a booking experienceand during pickup and return.

6 FIG.A 116 604 116 116 As shown in, the fleet management systemperforms an actof receiving a user selection of rental location, class, and date. In one or more embodiments, the fleet management systemreceives rental location, class, and date from a renter computing device. More specifically, in some embodiments, the fleet management systemreceives an indication of user selection of the rental location, class, and date from the renter computing device via a transportation matching system and/or rental application.

116 606 116 116 In some embodiments, after receiving the selection of the rental location, class, and date, the fleet management systemperforms an actof creating a reservation. More specifically, the fleet management systemutilizes the received rental location, class, and date to match the renter computing device to a particular third-party-rental vehicle of the selected class and at the selected rental location. Further, the fleet management systemgenerates a reservation for the particular third-party-rental vehicle on the selected date.

116 608 116 116 116 601 In some embodiments, upon creating a reservation, the fleet management systemperforms an actof capturing pre-payment. To illustrate, in one or more embodiments, the fleet management systemreceives an indication of user input from the renter computing device indicating payment information. However, in one or more embodiments, the fleet management systemstores rather than processes the payment details. Additionally, in one or more embodiments, the fleet management systemprovides the payment details to the third-party system.

601 601 610 612 116 116 116 116 6 FIG.A Additionally, as mentioned above, the third-party systemperforms one or more acts in rental management. For example, as shown in, in one or more embodiments, the third-party systemperforms an actof receiving reservation details and an actof providing a confirmation to the renter computing device. To illustrate, in one or more embodiments, the fleet management systemreceives a rental reservation and corresponding payment details from the fleet management system. Further, the fleet management systemgenerates a confirmation including details from the received reservation. Additionally, in one or more embodiments, the fleet management systemprovides the confirmation to the renter computing device.

6 FIG.A 601 116 614 116 116 116 601 As further shown in, in some embodiments, after capturing pre-payment and forwarding reservation details to the third-party system, the fleet management systemperforms an actof modifying or cancelling a reservation. In one or more embodiments, the fleet management systemcan receive an indication user input requesting modification or cancelation of a rental reservation from the renter computing device. Based on receiving this modification or cancellation information, the fleet management systemcan modify and/or cancel the rental reservation. In one or more embodiments, the fleet management systemmodifies and/or cancels a reservation by providing the modification and/or cancellation information to the third-party system.

116 616 116 116 116 In addition to sometimes modifying or cancelling a reservation, the fleet management systemalso performs an actof providing pre-booking support. For example, the fleet management systemcan provide the renter computing device with various resources for questions, concerns, and direction related to the rental reservation. In one or more embodiments, the fleet management systemprovides resources in an application or via contact information. Further, to facilitate pre-booking support, in one or more embodiments, the fleet management systemaggregates the rental reservation information into a fleet-vehicle database.

6 FIG.A 116 618 618 116 620 116 116 116 also shows acts performed by the fleet management systemand the third-party system during pick-up and returnof rental vehicles. To illustrate, during the pickup and return, the fleet management systemcan perform an actof sending a pickup reminder. In one or more embodiments, the fleet management systemutilizes the rental reservation information to generate a notification reminding the renter computing device of an impending pickup. Further, the fleet management systemutilizes the rental reservation information to determine when to provide the pickup reminder to the renter computing device. For example, the fleet management systemcan automatically provide the renter computing device with the pickup reminder 48 hours in advance, 12 hours in advance, etc.

116 601 622 601 601 601 In addition to the fleet management systemsending a pick-up reminder, in some embodiments, the third-party systemperforms an actof transporting to a rental location. In one or more embodiments, the third-party systemfacilitates pick-up of a renter and drop-off of the renter at a rental pickup location. More specifically, in one or more embodiments, the third-party systemutilizes a transportation vehicle from a transportation matching system to drop the renter off at the pickup location. To illustrate, the third-party systemor renter computing device can submit a transportation request from a current location of the renter computing device to travel to the rental pickup location. Accordingly, the transportation matching system can match the transportation request with a provider device for a corresponding transportation vehicle to transport the renter to the rental location.

601 623 610 601 601 In addition to facilitating transport, the third-party systemcan also perform an actof receiving and processing a deposit. Utilizing the prepayment information received at the act, for example, the third-party systemprocesses the payment details to receive a deposit for the rental reservation. In one or more embodiments, the third-party systemalso provides notification and/or confirmation of this deposit to the renter computing device.

601 626 601 116 601 8 FIG. In addition to receiving and processing the deposit, the third-party systemcan perform an actof facilitating contactless pick-up. As described below with regard to, the third-party systemcan provide access to the rental location to the renter computing device utilizing a virtual code that the fleet management systemprovides to the renter computing device, and the renter computing device transmits to various computing devices at the rental location to request access. Additionally, in one or more embodiments, the third-party systemcan allow a rental vehicle accessed via a virtual code to leave the rental location.

601 628 601 601 601 In addition to contactless pick-up, in some embodiments, the third-party systemalso performs an actof generating an option to extend a reservation. In one or more embodiments, the third-party systemdetermines whether availability at the rental location allows for any extension of the rental reservation. Accordingly, the third-party systemcan determine potential lengths of time that the rental reservation may be extended for. Thus, the third-party systemcan generate and provide an option to extend the rental reservation including different length options to the renter computing device.

116 630 601 116 116 116 116 601 In one or more embodiments, after the third-party system generates the option to extend the reservation, the fleet management systemperforms an actof extending a reservation in-application. In one or more embodiments, the third-party systemprovides the option to extend the reservation to the fleet management systemto provide via a rental and/or transportation matching system application. Accordingly, in some embodiments, the fleet management systemreceives an indication of user interaction with the option to extend the reservation. Thus, the fleet management systemcan extend the reservation based on receiving such an indication to extend. In one or more embodiments, the fleet management systemprovides the extension information to the third-party system.

6 FIG.A 601 632 601 601 601 601 As shown in, the third-party systemcan perform an actof receiving a return of a rental vehicle. In one or more embodiments, the third-party systemreceives a return of a rental vehicle at a rental location. The third-party systemcan receive the return via a rental-location-computing device. For example, the third-party systemcan receive user input indicating successful return of the rental vehicle via a rental-location-computing device. In addition or in the alternative, the third-party systemcan facilitate contactless drop-off utilizing a virtual code and/or other vehicle sensors.

116 634 116 116 Additionally, in one or more embodiments, before receiving a return of a rental vehicle, the fleet management systemperforms an actof sending a return reminder. Similar to the discussion above with regard to a pickup reminder, in one or more embodiments, the fleet management systemutilizes the rental reservation information to generate a notification reminding the renter computing device of an impending rental vehicle return. Further, the fleet management systemutilizes the rental reservation information to determine when to provide the return reminder to the renter computing device.

6 FIG.A 601 636 601 601 Further, as shown in, upon receiving the return of the rental vehicle, the third-party systemcan perform an actof scheduling transportation for the renter. Similar to the discussion above with regard to transport to the rental location, the third-party systemcan provide a rental request to a transportation matching system for the renter after return of a rental vehicle. In one or more embodiments, the third-party systemor a renter computing device requests pick-up of a renter at the rental location and drop-off of the renter at another location.

601 638 601 601 Also after the return of the rental vehicle, the third-party systemcan also perform an act ofof providing post-booking support. For example, the third-party systemcan provide the renter computing device with various resources for questions, concerns, and direction related to the rental reservation. Further, to facilitate post-booking support, the third-party systemmay maintain records of the past rental reservation.

116 116 116 7 8 FIGS.A-D In one or more embodiments, the fleet management systemintegrates third-party vehicles into graphical user interfaces, including rental selection graphical user interfaces, fleet management interfaces, and/or fleet-location-management interfaces. In some embodiments, the fleet management systemintegrates rental options corresponding to a third-party system into a rental selection graphical user interface. For example, the fleet management systemcan provide data for user selectable elements corresponding to third-party-rental vehicles in graphical user interfaces as depicted inof and further described by Keith Abdulla et al., Dynamically Determining Provider-Transportation Routes and Rental Vehicle Routes for a Multi-Modal Graphical User Interface, U.S. application Ser. No. 16/834,977 (filed Mar. 30, 2020) (hereinafter, Abdulla), which is incorporated by reference in its entirety.

116 116 601 116 601 6 6 FIGS.B-M Additionally, in one or more embodiments, the fleet management systemutilizes one or more application programming interfaces (APIs) to provide third-party information via a rental selection graphical user interface. To illustrate, the fleet management systemcan receive information from the third-party systemregarding scheduling, availability, rental vehicle data, etc. For example, the fleet management systemcan utilize a rental locations API, a calendar API, and/or vehicle APIs to receive information from the third-party systemfor display on the graphical user interfaces depicted by.

601 116 601 116 116 116 To retrieve such information from the third-party system, the fleet management systemcan issue an API call to the third-party system. The fleet management systemcan utilize various APIs to issue various API calls that query different information. To illustrate, the fleet management systemcan utilize a rental locations API call to query information about rental locations, a calendar API to query information about time-slot availability, and vehicle APIs to query information about rental vehicle availability and characteristics. Accordingly, the fleet management systemcan receive an API response indicating various information for presentation in a graphical user interface.

116 640 640 642 6 6 FIGS.B-M 6 FIG.B In some embodiments, the fleet management systemprovides this information to a renter computing device for presentation in a graphical user interface.illustrate a renter computing devicepresenting various example graphical user interfaces for booking and managing a vehicle rental corresponding to a software application (e.g., a transportation matching system application, a rental application). For example,illustrates the renter computing devicepresenting a third-party-vehicle-selection interface.

6 FIG.B 642 644 644 642 116 601 As shown in, the third-party-vehicle-selection interfaceincludes a rental vehicle listingcorresponding to a rental location “Anchorage Square.” The rental vehicle listingincludes information about different vehicle classes available at the rental location and accompanying data, including vehicle features and pricing. Though the third-party-vehicle-selection interfaceincludes particular information for the “Anchorage Square” location, the fleet management systemcan receive vehicle information from various locations associated with the third-party system.

116 642 116 601 116 116 116 640 642 6 FIG.B In one or more embodiments, the fleet management systemutilizes a rental locations API to populate the third-party-vehicle-selection interfacewith vehicle information corresponding to the particular rental location. In some embodiments, the fleet management systemgenerates a rental locations API call to the third-party system. In response, in one or more embodiments, the fleet management systemreceives a listing of regions, a current region for a renter computing device, and a list of rental locations corresponding to the different regions. Additionally, in one or more embodiments, the fleet management systemreceives a list of available vehicle types. As shown in, the fleet management systemcan provide this received data to the renter computing devicefor presentation in the third-party-vehicle-selection interface.

640 640 646 640 646 646 646 640 116 6 FIG.C 6 FIG.C In some cases, the renter computing devicepresents information associated with rental vehicles in general. As shown in, the renter computing devicepresents a rental information interface. In some embodiments, the renter computing devicepresents the rental information interfacebased on detecting a selection of a menu or a rental information icon (e.g., a circular icon with the letter “I” inside). The rental information interfaceincludes information about amenities offered at a selected rental location. For example, as shown in, the rental information interfaceincludes information about the amenities “Free ride to the lot,” “$4 per gallon,” and “After hours returns.” However, the renter computing devicecan present a rental perks interface including a variety of perks received from the fleet management system.

116 601 116 601 116 640 646 More specifically, the fleet management systemcan utilize the rental locations API to query the third-party systemfor information about amenities at a rental location. Accordingly, the fleet management systemcan receive the information about the amenities at the rental location from the third-party system. Thus, in one or more embodiments, the fleet management systemprovides the information about amenities at rental locations to the renter computing devicefor presentation in the rental information interface.

6 FIG.D 6 FIG.D 640 648 648 116 648 652 650 654 648 656 658 660 illustrates the renter computing devicedisplaying a rental-reservation-user interfaceas an example graphical user interface by which a renter can generate or modify a rental-vehicle reservation. Based on user interaction with elements of the rental-reservation-user interface, the fleet management systemmodifies the rental parameters. As illustrated in, for instance, the rental-reservation-user interfaceincludes a calendarincluding a selected-rental-duration indicatorand a duration-discount notification. The rental-reservation-user interfacefurther comprises a vehicle pickup and return time elements, a rental-vehicle rate, and a confirmation element.

6 FIG.D 6 FIG.D 652 640 652 650 648 640 650 640 650 As illustrated in, the calendarcomprises a visual representation of a monthly calendar. The renter computing devicepresents the calendar, which visually indicates (e.g., by including a circle around) the selected-rental-duration indicatorbased on renter interaction with the rental-reservation-user interface. For example, the renter computing devicecan generate the selected-rental-duration indicatorbased on detecting a user tap of the first and last dates or a dragging motion between the dates of the desired rental duration. As illustrated in, the renter computing devicegenerates the selected-rental-duration indicatorto show that the renter selected the rental duration of June 29-July 1.

6 FIG.D 648 654 640 654 654 640 654 640 As further shown in, the rental-reservation-user interfacealso includes the duration-discount notification. The renter computing devicepresents the duration-discount notificationbased on determining that the rental duration meets a threshold length. The duration-discount notificationindicates the discount value and the reason for the discount. The renter computing devicemay also present additional notifications in place of (or in addition to) the duration-discount notification. For example, the renter computing devicecan present a notification indicating a reduced rate contingent on returning the rental vehicle at a particular rental-vehicle location.

6 FIG.D 652 116 116 601 116 601 116 601 As further illustrated in, the calendarincludes both date values as well as predicted daily rates. For example, the fleet management systemassociates each date with a predicted daily rate. In one or more embodiments, the fleet management systemreceives the calendar information from the third-party systemutilizing a calendar API. More specifically, the fleet management systemcan send an API call to the third-party systemfor such calendar information. Accordingly, the fleet management systemcan receive an API response including various calendar information from the third-party systemin response to the API call.

116 116 116 640 652 116 640 To illustrate, in one or more embodiments, the fleet management systemreceives rental rate information for the calendar dates. Additionally, the fleet management systemcan receive availability information for the calendar dates. The fleet management systemcan provide this information to the renter computing devicefor presentation in the calendar. In one or more embodiments, the fleet management systemdetermines (and the renter computing devicepresents) a total rental rate for multiple selected dates based on the received rental rates for calendar dates.

6 FIG.D 648 656 640 656 640 116 As further illustrated in, the rental-reservation-user interfaceincludes the vehicle pickup and return time elements. The renter computing devicecan receive user input selecting and/or modifying pick-up and return times. Based on detected requestor interaction with the vehicle pickup and return time elementsat the renter computing device, the fleet management systemadjusts the rental vehicle pickup time and the rental vehicle return time.

6 FIG.D 640 658 640 658 116 116 601 658 658 640 660 116 In addition to a calendar and return times in, the renter computing devicepresents the rental-vehicle rate. More specifically, the requestor devicegenerates the rental-vehicle ratebased on the received renter input and the daily calendar rates received from the fleet management system. In addition or in the alternative, the fleet management systemand/or the third-party systemgenerate the rental-vehicle rateand provide the rental-vehicle rateto the renter computing device. Based on detecting selection of the confirmation element, the fleet management systemconfirms the received renter selections.

640 640 662 662 662 664 662 640 6 FIG.E 6 FIG.E In some cases, the renter computing deviceselects dates (or receives a selection of dates) for which a rental vehicle (e.g., a third-party-rental vehicle) is unavailable. As shown in, for instance, the renter computing devicepresents an unavailability noticewithin a graphical user interface. The unavailability noticeincludes the text “Dates unavailable,” “Compact is sold out between June 25-27,” and “Please change your dates.” The unavailability noticealso includes an acknowledgement button. Thoughillustrates an example unavailability notice, the renter computing devicecan present various unavailability notices based on different rental vehicle availability and user selections.

116 601 116 116 662 640 640 116 116 662 More specifically, in one or more embodiments, the fleet management systemreceives rental vehicle availability from the third-party system. Additionally, the fleet management systemreceives an indication of user selection of particular dates. Based on determining that rental vehicles in a particular location are not available for the selected dates, the fleet management systemprovides the unavailability noticeto the renter computing device. In addition or in the alternative, the renter computing devicecan receive rental-vehicle-availability information from the fleet management systemand can detect the user selection of calendar dates. In some such embodiments, the fleet management systemcan determine vehicles are unavailable for the user-selected dates and can accordingly generate and provide the unavailability notice.

640 640 668 668 668 670 6 FIG.F 6 FIG.F In addition or in the alternative to showing such an unavailability notice, in some embodiments, the renter computing devicedisplays alternative rental options or alternative rental date options within a graphical user interface. As illustrated in, for instance, the renter computing devicecan also present an alternative options interfacein response to determining a user selection is unavailable. The alternative options interfaceincludes the text “Sold out,” “The option you selected is not available between June 25-27,” and “Please change your dates or choose another car below.” As shown in, the alternative options interfacealso includes alternate rental vehicles, including listing of availability and pricing information for “Full-size” and “SUV” categories, despite “Compact” being sold out.

116 640 116 601 640 640 To illustrate, the fleet management systemand/or the renter computing devicecan determine alternate vehicle types to a selected unavailable vehicle type that are available at a rental location during selected calendar dates, including other third-party-rental vehicles. As discussed above, the fleet management systemcan receive vehicle availability data from the third-party systemand can further provide this availability data to the renter computing device. Accordingly, in one or more embodiments, the renter computing devicepresents the availability information for various rental vehicle options.

116 640 640 671 671 672 674 676 6 FIG.G 6 FIG.G When a selected third-party-rental vehicle is available on selected rental dates, the fleet management systemcan provide and the renter computing devicecan present additional information concerning the third-party-rental vehicle. As shown in, for instance, the renter computing devicepresents a reservation-review-user interfaceto provide an overview of the rental reservation—including various conformation elements—based on the renter selections. As illustrated in, the reservation-review-user interfaceincludes vehicle information, reservation details, and a rental-vehicle rate.

6 FIG.G 6 FIG.G 640 672 116 601 640 672 As shown in, the renter computing devicepresents the vehicle information. As discussed above, the fleet management systemcan receive vehicle data from the third-party systemand can further provide this availability data to the renter computing device. For example, as shown in, the vehicle informationincludes information on the type, seating capacity, handling type, and fuel type for a selected rental vehicle.

6 FIG.G 640 674 640 674 116 116 As further shown in, the renter computing devicealso presents the reservation details. More specifically, the renter computing devicepresents information regarding the rental-vehicle location, return location information, and rental duration dates. Based on receiving an indication of detected interaction with the reservation details, the fleet management systemcan adjust the corresponding rental parameter. For example, based on detecting requestor selection of a return location, the fleet management systemmay generate and transmit prompts for selecting a different rental-vehicle location for picking up the rental vehicle.

6 FIG.G 671 676 116 640 676 640 678 678 116 As further shown in, the reservation-review-user interfacealso includes the rental-vehicle rate. As discussed above, the fleet management systemand/or the renter computing devicecan determine the rental-vehicle ratebased on received user selections and received rate information. Further, the renter computing devicepresents a confirmation option. Based on receiving an indication of user interaction at the confirmation option, the fleet management systemcan confirm the reservation and its corresponding details.

6 FIG.H 6 FIG.G 6 FIG.H 640 671 640 680 682 684 As shown in, the renter computing devicecan present additional conformation elements within the reservation-review-user interfacebeyond the information illustrated in. For example, as illustrated in, the renter computing devicecan present additional confirmation elements, including rental coverage elements, an add-on-selection element, and a driver information area.

6 FIG.H 640 680 680 116 116 680 116 640 As shown in, the renter computing devicepresents the rental coverage elements, each of which can be selected by the rental requestor by interacting with corresponding options (e.g., toggle buttons). In one or more embodiments, based on user interaction with the rental coverage elements, the fleet management systemadds and/or adjusts rental coverage information for insurance purposes. In at least one embodiment, the fleet management systemprovides various degrees of insurance coverage. Based on selection of one or more of the rental coverage elements, the fleet management systemmay also transmit, for display on the renter computing device, additional coverage options, including coverage provided by the payment companies associated with the payment option selected by the rental requestor.

640 116 682 682 116 116 6 FIG.H In addition to coverage options, the renter computing devicepresents interactive elements for selecting rental vehicle add-ons. As illustrated in, the fleet management systemalso provides the add-on-selection element. Based on selection of the add-on-selection element, the requestor devicepresents various add-on options. To illustrate, the fleet management systemmay provide additional options including child/baby seats, bike or other gear racks, snow gear, GPS navigation units, and other add-ons.

6 FIG.H 640 684 116 684 640 116 114 684 As further shown in, the renter computing devicepresents the driver information area. In at least one embodiment, the fleet management systempresents the driver information areabased on information from the renter computing deviceand/or a corresponding renter account. For example, the fleet management systemaccesses information stored by the dynamic transportation matching systemregarding the requestor account. As illustrated, the driver information areaincludes the name, driver's license number, and contact information for the corresponding rental requestor. The rental requestor may select the driver information and provide updated driver information.

6 FIG.H 6 FIG.I 684 686 671 686 686 116 601 Additionally, as shown in, the driver information areaincludes an option to add another driver. As shown in, in some embodiments, in response to detecting selection of an add-driver option, the renter computing device provides the additional driver overlaywithin the reservation-review-user interface. The additional driver overlayincludes the text “Additional driver fee” and a corresponding explanation: “Third-party charges $10.00/day to your rental for each additional driver.” However, the additional driver overlaycan include a variety of fee information based on rental location information that the fleet management systemreceives from the third-party system.

6 FIG.I 686 688 688 116 640 As further shown in, the additional driver overlayincludes an add-driver-confirmation option. Based on receiving an indication of a selection of the add-driver-confirmation option, the fleet management systemcan provide a prompt to the renter computing devicefor input of information regarding the additional driver.

640 116 601 640 640 689 640 689 6 FIG.D 6 FIG.J As discussed above, in one or more embodiments, the renter computing deviceand/or the fleet management systemdetermine a total rental rate for selected dates based on rental rates for calendar dates received from the third-party system. Based on detecting a rental-rate-information icon (e.g., a circular icon with the letter “I” inside as shown in), the renter computing devicecan provide more details concerning a rental rate. As shown in, for example, the renter computing devicepresents a total rate overlaywithin a graphical user interface. As shown, the renter computing devicecan provide an itemized listing of costs corresponding to the total rate in the total rate overlay.

116 640 690 640 690 690 691 692 693 6 FIG.K 6 FIG.K In addition to graphical user interfaces for reserving a third-party-rental vehicle, the fleet management systemcan also provide graphical user interfaces to confirm a reservation or to facilitate additional options or features for a reservation. As shown in, for instance, the renter computing devicepresents a rental information interface. In one or more embodiments, the renter computing devicepresents the rental information interfaceduring an active rental period. As shown in, the rental information interfaceincludes a help element, a return details element, and an extend reservation element.

691 640 640 692 640 116 692 6 FIG.G 6 FIG.K In one or more embodiments, in response to receiving user interaction at the help element, the renter computing devicepresents different options for assistance with a rental vehicle. For example, the renter computing devicecan provide options for roadside assistance. Additionally, in response to receiving user interaction at the return details element, the renter computing devicecan provide information about returning the third-party-rental vehicle, such as driving guidance to the return location. In one or more embodiments, the fleet management systemcan provide the reservation-review-user interface illustrated inbased on detecting a selection of the return details elementillustrated in.

6 FIG.K 6 FIG.L 6 FIG.L 690 693 693 640 694 694 rd As also shown in, the rental information interfaceincludes an extend reservation option. In one or more embodiments, in response to detecting user interaction at the extend reservation option, the renter computing deviceprovides the rental extension overlayas illustrated in. As shown in, the rental extension overlayincludes the text “Extensions must be completed with 3party” and “Please contact them to extend.”

6 FIG.L 694 695 695 640 640 601 As further shown in, the rental extension overlayincludes a third-party-call option. In one or more embodiments, in response to detecting a user selection of the third-party-call option, the renter computing devicecan provide contact information for the third party (e.g., third-party-rental company). For example, the renter computing devicecan display a mobile call application with a phone number corresponding to the third-party system.

116 640 696 640 969 696 640 6 FIG.M In addition to graphical user interfaces for extending a reservation for a third-party-rental vehicle, the fleet management systemcan also provide graphical user interfaces for confirmation a reservation or selecting a particular third-party-rental vehicle for pickup. As shown in, for instance, the renter computing devicecan present a pickup information interface. In one or more embodiments, the renter computing devicepresents the pickup information interfacein response to determining that pickup is within a threshold time (e.g. 24 hours, 1 hour). To illustrate, the pickup information interfacecan include information about the pickup location and/or pickup time associated with a rental reservation. In one or more embodiments, in response to receiving user selection of pickup information, the renter computing deviceprovides options to modify the pickup information.

6 FIG.M 6 6 FIGS.B andF 696 697 697 640 640 601 116 As further shown in, the pickup information interfaceincludes a select car option. In one or more embodiments, in response to detecting user interaction at the select car option, the renter computing devicepresents one or more rental vehicles for selection. Similar to the discussion above with regard to, the renter computing devicecan provide rental vehicle data received from the third-party systemvia the fleet management system.

7 7 FIGS.A-C 7 7 FIGS.A-C 5 FIG. 7 7 FIGS.A-C 7 FIG.C 7 7 FIGS.A-C 7 7 FIGS.A-C 7 7 FIGS.A-C 116 116 116 116 701 701 116 illustrate example fleet-location-management interfaces for the fleet management system. As discussed above, the fleet management systemcan provide location-specific vehicle data in fleet-location-management interfaces.have a fleet-location-management interface that differs from that fleet management interface shown inin part because the fleet-location-management interfaces depicted inare region specific or location specific, including the example vehicle-data summaries in.illustrate example fleet-location-management interfaces that the fleet management systemprovides for regions and locations corresponding to a vehicle fleet. The fleet management systemcan provide data to a computing deviceto present the fleet-location-management interfaces depicted inaccording to computer-executable instructions on a software application of the computing device(e.g., web browser or native application). Additionally, thoughillustrate fleet-location-management interfaces with example designs, the fleet management systemcan provide data for graphical user interfaces in accordance with a variety of visual designs.

7 FIG.A 7 FIG.A 701 700 700 700 702 700 116 700 For example,illustrates the computing devicedisplaying a fleet-location-management interfaceincluding various regions. More specifically, the fleet-location-management interfaceincludes data regarding the types of fleet locations in various regions. As shown in, the fleet-location-management interfaceincludes a region ID column. In this particular example, the fleet-location-management interfaceincludes regions corresponding to airports. However, in one or more embodiments, the fleet management systemcan generate the fleet-location-management interfaceincluding regions generated based on a variety of criteria.

7 FIG.A 701 700 704 716 702 700 704 706 708 710 712 714 716 116 700 704 708 Additionally, as shown in, the computing devicedisplays, within the fleet-location-management interface, various columns-listing a number of locations of various types in the regions indicated in the region ID column. More specifically, the fleet-location-management interfaceincludes a hubs column, a vehicle service column, an express drive column, a rental lots column, an impound lots column, a storage facility column, and a miscellaneous column. In one or more embodiments, the fleet management systemaggregates data regarding fleet locations in the variety of regions and generates the fleet-location-management interfaceto reflect a number of associated fleet locations corresponding to the category set forth in each column (e.g., a number of hubs within the region in the hubs column, a number of express drive locations within the region in the express drive column).

702 116 701 720 701 720 701 720 722 724 116 720 7 FIG.B 7 FIG.B In response to receiving user input at a region of the region ID column, in some embodiments, the fleet management systemprovides a fleet-location-management interface corresponding to the selected region.illustrates the computing devicedisplaying a fleet-location-management interfacecorresponding to the region “SFO.” The computing devicedisplays, within the fleet-location-management interface, various locations in the SFO region and information corresponding to these regions. As shown in, the computing devicedisplays, within the fleet-location-management interface, first-party locationsand service locations. Accordingly, in one or more embodiments, the fleet management systemprovides location information for the fleet-location-management interfacebased on vehicle data received from first-party and third-party computing devices and systems.

7 FIG.B 701 720 701 720 726 116 As further shown in, the computing devicealso displays, within the fleet-location-management interface, various columns that include various information corresponding to the region. For example, the computing devicedisplays, within the fleet-location-management interface, a location name columnthat shows the name of various locations in the region. In one or more embodiments, the fleet management systemreceives name data from rental-location-computing devices, administrator computing devices, and/or other computing devices at the locations.

701 720 728 116 116 720 720 727 728 727 7 FIG. Additionally, the computing devicedisplays, within the fleet-location-management interface, a location type column, which indicates whether the location is a first-party location or a third-party location. As discussed above, the fleet management systemcan utilize both first-party and third-party rental and service locations to manage a vehicle fleet. The fleet management systemcan track whether each of the locations in the fleet-location-management interfaceare first-party or third-party locations. For example, as shown in, the fleet-location-management interfaceincludes a third-party location. Accordingly, the location type columnindicates that the third-party locationis a third-party location.

7 FIG.B 4 FIG. 701 730 720 730 116 116 730 116 As further shown in, the computing devicedisplays a location queue columnwithin the fleet-location-management interface. The location queue columnincludes information corresponding to queue types available at the corresponding location. As discussed above with regard to, the fleet management systemcan manage various queue types in a fleet location. Accordingly, the fleet management systemcan track the queue types at different rental locations and provide the information in the location queue column. In one or more embodiments, the fleet management systemreceives queue information from various vehicle-service-computing devices corresponding to the locations.

7 FIG.B 701 720 732 732 726 116 Additionally, as shown in, the computing devicedisplays, within the fleet-location-management interface, a location address column. The location address columnincludes physical addresses corresponding to the locations listed under the location name column. Similar to the discussion above, in one or more embodiments, the fleet management systemreceives queue information from various vehicle-service-computing devices corresponding to the locations.

7 FIG.B 701 720 734 734 726 116 Further, as shown in, the computing devicedisplays, within the fleet-location-management interface, a location services column. The location services columnincludes a listing of one or more services provided at a fleet location listed under the location name column. In one or more embodiments, the fleet management systemreceives service information from one or more vehicle-service-computing devices corresponding to a location.

720 116 720 740 116 740 720 720 720 7 FIG.C In addition to the region-specific details in the fleet-location-management interface, in some embodiments, the fleet management systemcan provide data for a location-specific fleet-location-management interface in response to receiving user selection of a fleet location in the fleet-location-management interface.illustrates a fleet-location-management interfacecorresponding to the “Lyft Driver Center—San Francisco.” To illustrate, the fleet management systemcan provide data for the fleet-location-management interfacein response to receiving user selection of an option for the Lyft Driver Center—San Francisco in the fleet-location-management interface. Such an option may be visible as a graphical element within the fleet-location-management interface, embedded in the text for the name of a fleet-vehicle center (e.g., Lyft Driver Center—San Francisco), or have some other suitable representation within the fleet-location-management interface.

7 FIG.C 8 8 FIGS.A-B 740 701 701 744 740 744 116 116 As shown in, the fleet-location-management interfaceincludes a listing of a variety of vehicle data corresponding to renters at a particular fleet location. In one or more embodiments, the computing devicedisplays vehicle-data summaries in rows with data corresponding to each column. For example, the computing devicedisplays a renter indicator columnwithin the fleet-location-management interface. The renter indicator columnincludes renter indicators including renter names and renter profile pictures. In one or more embodiments, the fleet management systemreceives the renter names and renter profile pictures from renter computing devices, provider devices, and/or requestor devices corresponding to the vehicles at the fleet location. As described below with regard to, in response to receiving user selection of a renter indicator, the fleet management systemcan provide a renter-activity summary corresponding to a particular renter.

7 FIG.C 7 FIG.C 740 746 116 116 116 740 As further shown in, the fleet-location-management interfaceincludes a queue column. As discussed above, the fleet management systemcan dynamically manage a variety of different queues corresponding to a single fleet location. As shown in, the fleet management systemmanages both a vehicle service queue and a mobile service queue at this fleet location. The fleet management systemcan provide vehicle data corresponding to a variety of vehicle queues in the fleet-location-management interface.

7 FIG.C 740 748 116 116 116 701 748 740 As also shown in, the fleet-location-management interfaceincludes a service type column. In one or more embodiments, the fleet management systemmanages vehicle queues including vehicles undergoing a variety of types of services. In some embodiments, the fleet management systemreceives information about service types corresponding to fleet vehicles based on appointment and/or reservation requests received from renter computing devices. Accordingly, the fleet management systemprovides the information about service types to the computing devicefor presentation in the service type columnof the fleet-location-management interface.

701 750 740 750 116 701 750 740 7 FIG.C In one or more embodiments, the computing devicefurther displays a vehicle identifier columnwithin the fleet-location-management interface. As shown in, the vehicle identifier columnincludes a listing of a manufacturer, model, and vehicle identification number corresponding to each fleet vehicle. The fleet management systemprovides manufacturer, model, and vehicle identification number to the computing devicefor presentation in the vehicle identifier columnof the fleet-location-management interface.

701 752 740 752 752 752 116 7 FIG.C In some embodiments, the computing devicedisplays a notes columnwithin the fleet-location-management interface. The notes columncan include a variety of information received from a vehicle-service-computing device. As shown in, the notes columnincludes service notes related to specific issues experienced by each fleet vehicle. For example, the notes columnincludes notes such as “cabin air filter, oil change” denoting services performed or to be performed. In some embodiments, the fleet management systemcan automatically generate notes for a fleet vehicle based on vehicle data received from a renter computing device during a reservation request.

7 FIG.C 701 754 740 754 116 As further shown in, the computing devicecan also display a reservation columnwithin the fleet-location-management interface. The reservation columnincludes a quoted reservation time corresponding to a service appointment for each fleet vehicle. In one or more embodiments, the fleet management systemreceives the reservation time from a vehicle-service-computing device at the fleet location and/or from the renter computing device during a reservation request.

701 756 758 740 116 116 116 756 116 758 116 701 756 758 4 FIG. In addition to the columns described above, in one or more embodiments, the computing devicealso displays a time columnand a service stage columnwithin the fleet-location-management interface. As discussed above with regard to, the fleet management systemcan track the progress of a fleet vehicle during a service at a fleet location (e.g. a fleet-vehicle center). More specifically, the fleet management systemcan receive information about the progress of a fleet vehicle through service from vehicle-service-computing devices. The fleet management systemcan utilize this information to determine time elapsed since the beginning of a service for the time column. Similarly, the fleet management systemcan utilize this information to provide a stage of the service for the service stage column, such as check-in or check-out. The fleet management systemcan provide this information to the computing devicefor presentation within the time columnor the service stage columnof the fleet-location-management interface.

744 758 701 760 740 760 760 760 2 760 760 760 7 FIG.C As an example of a vehicle-data summary with data according to the columns-, the computing devicedisplays a vehicle-data summarywithin the fleet-location-management interface. To illustrate, the vehicle-data summarycorresponds to the driver “Dan Ruble.” As shown in, the vehicle-data summarycorresponds to a vehicle in a vehicle service queue for a service. Further, the vehicle-data summaryincludes a “Make A, Model” with a VIN “C927369198.” Additionally, the vehicle-data summaryincludes notes reading “PV, Something Else, Tire and TPMS Sensors messed up.” The vehicle-data summaryalso includes a reservation time of 10:30 AM with 9 minutes in service. The vehicle-data summaryshows that the corresponding vehicle is pending check-out.

116 116 760 7 FIG.C 8 8 FIGS.A-B In addition to providing fleet-location-management interfaces corresponding to various fleet locations, the fleet management systemcan also generate and provide renter-activity summaries corresponding to particular renters and/or renter accounts. As mentioned briefly above, the fleet management systemcan provide a renter-activity summary corresponding to a renter based on a user selection of a renter indicator corresponding to the renter from the vehicle-data summaryin.illustrate example graphical user interfaces including renter-activity summaries corresponding to “Dan Ruble.”

8 FIG.A 8 FIG.A 7 FIG.C 801 800 801 800 802 802 802 a a illustrates a computing devicedisplaying a renter-activity summary. As shown in, the computing devicedisplays the renter-activity summaryincluding a renter indicator. The renter indicatorincludes a renter name, renter identification number, and renter profile photo. Similar to the discussion above with regard to, the renter indicatorcan also or alternatively include a username or account identifier corresponding to a renter.

8 FIG.A 8 FIG.A 801 804 800 804 116 801 800 a a. As further shown in, the computing devicedisplays a sidebarincluding various selectable tabs for different renter-activity data within the renter-activity summary. In, an activity tab is selected. However, the sidebaralso includes tabs for rental history, payment information, and general information. The fleet management systemcan provide vehicle data corresponding to each category to the computing devicefor presentation in the renter-activity summary

8 FIG.A 8 FIG.A 800 806 116 806 806 116 116 a As further shown in, the renter-activity summaryincludes an activity section. In one or more embodiments, the fleet management systemgenerates the activity sectionincluding various system activities corresponding to the renter. For example, in, the activity sectionlists “Checked in at SFO Lyft Location,” “Started Lyft Rentals Contract,” and “Message sent to Anthony Maseda.” However, the fleet management systemcan generate an activity section including a variety of activities undergone by a renter related to a particular rental vehicle or the fleet management system.

8 FIG.A 8 FIG.A 8 FIG.A 800 808 808 116 116 808 116 116 a As further shown in, the renter-activity summaryalso includes a notes section. The notes sectionincludes notes about the rental account received by the fleet management systemfrom various computing devices. For example, the fleet management systemcan include notes from a vehicle-service-computing device and/or a rental-location-computing device. In, the notes sectionincludes the notes “Car looks good! !” and “Needs new windshield wiper blades soon.” In one or more embodiments, the fleet management systemreceives these notes from vehicle-service computing devices and/or rental-location computing devices as user input corresponding to the renter account. Additionally, the notes have a corresponding email address or handle indicating the note's author. In addition or in the alternative to the notes shown in, the fleet management systemcan receive and provide a variety of notes from a variety of computing devices.

8 FIG.B 8 FIG.B 8 FIG.B 801 800 804 801 812 800 812 800 812 116 812 b b b illustrates the computing devicedisplays a renter-activity summarywith the “Rental History” tab selected at the sidebar. As shown in, the computing devicedisplays a rental history sectionwithin the renter-activity summary. The rental history sectionincludes details for rental reservations associated with the renter of the renter-activity summary.shows the rental history sectionincluding a rental reservation from June 25 to June 27 at SFO for a particular fleet rental vehicle. However, the fleet management systemcan generate the rental history sectionto include a variety of rental reservations in the past, present, and future.

804 801 801 In one or more embodiments, the computing device may also display additional vehicle information corresponding to other tabs in the sidebar. For example, in one or more embodiments, in response to detecting user selection of the “payment info,” the computing devicedisplays information corresponding to renter payments. Additionally, in some embodiments, in response to detecting user selection of “general info,” the computing devicedisplays renter profile and/or demographic information of the renter.

116 9 FIG. 9 FIG. As discussed briefly above, the fleet management systemcan facilitate contactless pick-up of a vehicle utilizing a virtual code.illustrates an overview for the contactless vehicle pick-up process. More specifically,illustrates the process of a renter computing device requesting access to a rental location, receiving navigation instructions to a rental car, requesting access to the rental car, and requesting to exit the rental location.

9 FIG. 116 902 116 908 As shown in, the fleet management systemcan perform an actof generating and providing a virtual code to a renter computing device. More specifically, the fleet management systemcan generate and store a virtual code associated with a particular fleet rental vehicle. As explained below, in some embodiments, the virtual code may constitute a radio frequency identification code, such as a Near Field Communications (“NFC”) code for an NFC coil.

116 116 116 In one or more embodiments, the fleet management systemprovides the virtual code to a renter computing device upon confirming a rental reservation. In addition or in the alternative, the fleet management systemcan provide the virtual code to the renter computing device at a predetermined time prior to a scheduled pick-up. The fleet management systemcan also provide the virtual code to the renter computing device upon receiving payment details from the renter computing device.

9 FIG. 116 904 116 904 904 116 116 908 908 116 904 As further shown in, the fleet management systemprovides the renter computing device access to the entranceof the rental location. In one or more embodiments, the fleet management systemutilizes a computing device at the entranceof the rental location to receive the virtual code. In response to receiving the virtual code at the entranceof the rental location, the fleet management systemcan provide access to the rental location. More specifically, the fleet management systemcan determine that the received virtual code corresponds to a rental vehicleat the rental location. In one or more embodiments, in response to determining that the received virtual code corresponds to the rental vehicleat the rental location, the fleet management systemprovides the renter computing device access to the entranceof the rental location.

116 906 116 908 116 908 After providing access to the rental location, the fleet management systemperforms an actof providing navigation instructions to a rental vehicle corresponding to the rental request. The fleet management systemdetermines a parking location corresponding to the rental vehiclebased on vehicle data received from a rental-location-computing device and/or from an in-vehicle-computing device. Accordingly, the fleet management systemcan provide the renter computing device with navigation instructions to the specific parking location of the rental vehiclecorresponding to the rental request.

9 FIG. 910 116 908 908 908 908 908 908 As also shown in, the renter computing device can perform an actof utilizing the virtual code to access and start the vehicle. More specifically, the fleet management systemcan transmit the virtual code to an in-vehicle-computing device in the rental vehicle. In one or more embodiments, the rental vehicleincludes an in-vehicle-computing device connected to an on-board diagnostics port of the rental vehicle. In addition or in the alternative, the rental vehiclecan include an in-vehicle-computing device integrated during manufacture of the rental vehicle. In one or more embodiments, the in-vehicle-computing device can provide keyless access to the rental vehiclebased on receiving its corresponding virtual code.

116 908 908 908 908 908 In some embodiments, the virtual code is a radio frequency identification code, including a near field communication code. To illustrate, the fleet management systemcan utilize an NFC code to communicate wirelessly between two devices across short differences. For example, in some embodiments, the rental vehicleincludes an NFC coil mounted to the windshield or dashboard of the rental vehicle. In some cases, the NFC coil is part of a telematics device. In addition or in the alternative, the NFC coil is plugged into the on-board diagnostics port of the rental vehicleand/or spliced into a vehicle harness. In some embodiments, the NFC coil communicates with the rental vehicleutilizing a controller area network corresponding to the rental vehicle.

908 908 908 908 The NFC coil sends and receives information exchanged at short distances. Based on detecting that the renter computing device transmitting the NFC code is within a proximity range of the NFC coil, the computing device in the rental vehiclemay unlock and otherwise enable access to the rental vehicleand functions of the rental vehicle. Thus, the renter computing device can access the rental vehiclewithout internet access.

116 116 116 By utilizing the NFC code or other virtual code, the fleet management systemcan facilitate pick-up of a rental vehicle without utilizing a vehicle key (e.g. a physical key or key fob). To illustrate, in a rental vehicle with a push to start operation, the rental vehicle can include the key in an inaccessible location. The rental vehicle can provide power to the key only in response to receiving an indication of a detection of a corresponding virtual code. In some embodiments, the fleet management systemutilizes a key power module integrated into an on-board diagnostics port. In addition or in the alternative, the fleet management systemcan utilize the key power module integrated using a T harness installed into the wiring harness behind it. In one or more embodiments, the key power module can include the NFC coil and/or LTE and NFC connectivity. Thus, the rental car can detect interaction from a renter computing device and can power the key to the rental vehicle based on the detected interaction.

908 908 908 912 116 912 908 904 116 908 As just indicated, in one or more embodiments, the in-vehicle-computing device can allow the renter and/or the renter computing device to start the rental vehiclebased on receiving the virtual code. Thus, the renter can start the rental vehicleand drive the rental vehicleout of the rental location through an exit. In one or more embodiments, the fleet management systemcan utilize a rental-location-computing device at the exitto monitor the movement of the rental vehicleout of the rental location. Similar to the discussion above with regard to the entrance, the fleet management systemcan utilize receiving the virtual code to allow removal of the rental vehiclefrom the rental location. In one or more embodiments, the fleet management system utilizes virtual codes (e.g., for near field communications) as described in Abdulla.

116 118 116 116 1002 116 116 10 FIG. 10 FIG. As discussed above, the fleet management systemcan utilize the vehicle-fleet-platform databaseto perform a variety of acts based on vehicle data.provides an overview of several examples of actions performed by the fleet management system. As illustrated in, the fleet management systemcan perform an actof utilizing aggregated vehicle data to generate device notifications. To illustrate, the fleet management systemcan receive a variety of information about a vehicle from in-vehicle-computing devices, including telematic devices. The fleet management systemcan utilize this telematic data to generate notifications for a corresponding renter computing device.

116 116 116 For example, the fleet management systemcan receive odometer readings from a telematic device corresponding to a rental vehicle. The fleet management systemcan utilize this odometer reading in combination with a service history stored at the vehicle-fleet-platform database to determine that the rental vehicle is due for an oil change. Based on this determination, the fleet management systemcan generate and provide a notification of the need for an oil change to a corresponding renter computing device.

10 FIG. 116 1004 1006 1008 116 116 1006 1008 118 116 Additionally, as shown in, the fleet management systemcan utilize vehicle data to facilitate automatic check-inof rental vehicles at fleet-vehicle centersand at rental locations. For example, in one or more embodiments, the fleet management systemcan receive global positioning data from a renter computing device associated with a rental vehicle. The fleet management systemcan utilize this global positioning data in combination with location data corresponding to the fleet-vehicle centersthe rental locationsto determine when a renter computing device is at a fleet location. In response to determining that a renter computing device is at a fleet location corresponding to a reservation stored at the vehicle-fleet-platform database, the fleet management systemcan automatically check in the corresponding rental vehicle.

10 FIG. 116 1010 116 1012 116 118 116 Further, as shown in, the fleet management systemcan perform an actof providing vehicle-tailored navigation. To illustrate, the fleet management systemcan perform an actof providing navigation instructions based on electric charging. In one or more embodiments, the fleet management systemcan store the locations of electric charging stations in the vehicle-fleet-platform database. The fleet management systemcan provide navigation instructions based on vehicle data regarding battery levels and capability such that the fleet vehicle will not run out of charge.

116 1014 116 116 In addition, the fleet management systemcan perform an actof providing navigation instructions based on a service schedule. In one or more embodiments, a provider-rental vehicle may provide for a dynamic transportation matching system around the time of a service reservation at a fleet-vehicle center. In one or more embodiments, the fleet management systemprovides matches for the provider-rental vehicle to provide that will not interfere with the scheduled service. Further, the fleet management systemcan provide navigational instructions to the fleet-vehicle center based on the time of the service reservation while a renter computing device is in a providing mode.

1 10 FIGS.- 11 FIG. 11 FIG. 116 , the corresponding text, and the examples provide several different systems, methods, techniques, components and/or devices of the fleet management systemin accordance with one or more embodiments. In addition to the above description, one or more embodiments can also be described in terms of flowcharts including acts for accomplishing a particular result. For example,illustrates a flowchart of an example sequence of acts in accordance with one or more embodiments. In addition, the acts illustrated inmay be performed with more or fewer acts. Further, the acts may be performed in different orders. The acts described herein may be repeated or performed in parallel with one another or in parallel with different instances of the same or similar acts.

11 FIG. 11 FIG. 11 FIG. 11 FIG. 11 FIG. 11 FIG. 1100 As mentioned,illustrates a flowchart of a series of actsfor aggregating vehicle data and generating vehicle-data summaries in accordance with one or more embodiments. Whileillustrates acts according to one embodiment, alternative embodiments may omit, add to, reorder, and/or modify any of the acts shown in. The acts ofcan be performed as part of a method. Alternatively, a non-transitory computer-readable medium can comprise instructions that, when executed by one or more processors, cause a computing device to perform the acts of. In some embodiments, a system can perform the acts of.

11 FIG. 1100 1102 1102 1102 1102 As shown in, the series of actsincludes an actfor receiving vehicle data for a set of provider-rental vehicles and vehicle data for a set of personal-rental vehicles. In particular, the actcan include receiving vehicle data for a set of provider-rental vehicles used in part for transporting requestors according to a provider-use rental and vehicle data for a set of personal-rental vehicles operated by a renter according to a personal-use rental. Similarly, the actcan include receiving vehicle data based on data inputs associated with a set of provider-rental vehicles used in part by providers for transporting requestors according to a provider-use rental and vehicle data based on data inputs associated with a set of personal-rental vehicles operated by renters for self-transportation according to a personal-use rental. Specifically, the actcan include wherein the set of provider-rental vehicles comprises a subset of flexible-provider-rental vehicles used in part by a subset of providers for transporting requestors under a first mileage scheme and a subset of express-provider-rental vehicles used in part by an additional subset of providers for transporting requestors under a second mileage scheme.

11 FIG. 1100 1103 1003 As further shown in, the series of actsoptionally includes an actfor identifying service data for vehicle service centers associated with the set of provider-renal vehicles and the set of personal-rental vehicles. In particular, the actcan include identifying service data for one or more vehicle service centers associated with the set of provider-rental vehicles and the set of personal-rental vehicles.

11 FIG. 1100 1104 1104 1104 1104 As shown in, the series of actsalso includes an actfor aggregating the vehicle data and/or the service data for the set of provider-rental vehicles and the set of personal-rental vehicles. In particular, the actcan include aggregating, into a vehicle-fleet-platform database, the vehicle data for the set of provider-rental vehicles and the vehicle data for the set of personal-rental vehicles. Alternatively, the actcan include aggregating, into a vehicle-fleet-platform database, the vehicle data for the set of provider-rental vehicles, the vehicle data for the set of personal-rental vehicles, and the service data for the one or more vehicle service centers. Specifically, the actcan include wherein the vehicle data comprises one or more of vehicle manufacturer, vehicle model, vehicle identification number, vehicle mileage, vehicle service history, vehicle warranty data, vehicle collision data, vehicle appointment data, current renter, or vehicle transportation history.

11 FIG. 1100 1106 1106 1106 1106 As shown in, the series of actsincludes an actfor generating vehicle-data summaries for the set of provider-rental vehicles and for the set of personal-rental vehicles based on the aggregated vehicle data. Alternatively, the actcan include, based on the aggregated vehicle data and service data, generating, for display within a fleet management interface, vehicle-data summaries for the set of provider-rental vehicles with corresponding service information from the service data and vehicle-data summaries for the set of personal-rental vehicles with corresponding service information from the service data. In particular, the actcan include generating, for display within a fleet management interface, vehicle-data summaries for the set of provider-rental vehicles and for the set of personal-rental providing, for display within the fleet management interface, a renter indicator for a particular renter associated with a vehicle-data summary from the vehicle-data summaries, receiving an indication of a user selection of the renter indicator, and based on the user selection of the renter indicator, providing a renter-activity summary of tracked activities from a rental account for the particular renter. The actcan also include providing, for display on a computing device, a vehicle-data summary for a provider-rental vehicle or a personal-rental vehicle, the vehicle-data summary comprising a renter indicator for a particular renter; receive an indication of a user selection of the renter indicator; and, based on the user selection of the renter indicator, provide, for display on the computing device, a renter-activity summary of tracked activities from a rental account for the particular renter.

1106 1106 Specifically, the actcan include receiving, from a vehicle-service-computing device, a vehicle-damage tag indicating damage to a first rental vehicle from the set of provider-rental vehicles or the set of personal-rental vehicles, receiving, from a vehicle computing device, a vehicle-maintenance tag indicating a vehicle part requiring maintenance detected by a telematics device of a second rental vehicle from the set of provider-rental vehicles or the set of personal-rental vehicles, and providing, for display within the fleet management interface, a first vehicle-data summary comprising the vehicle-damage tag for the first rental vehicle and a second vehicle-data summary comprising the vehicle-maintenance tag for the second rental vehicle. Further, in one or more embodiments, the actincludes aggregating the vehicle data by aggregating service statuses indicating one of an active status, a maintenance status, a service status, or a damaged status, receiving, from a computing device, an indication of a user selection of a sorting option corresponding to the service statuses, and providing, for display within the fleet management interface, the vehicle-data summaries ordered according to the service statuses of the active status, the maintenance status, the service status, or the damaged status.

1106 1106 1106 Also, in one or more embodiments, the actcan include aggregating the vehicle data by aggregating vehicle manufacturers or vehicle models for the set of provider-rental vehicles and the set of personal-rental vehicles, receiving, from a computing device, an indication of a user selection of a sorting option corresponding to the vehicle manufacturers or the vehicle models, and providing, for display within the fleet management interface, the vehicle-data summaries ordered according to the vehicle manufacturers or the vehicle models. Additionally, in some embodiments, the actcan include identifying fleet-vehicle centers and third-party-vehicle centers in a geographical region, determining services available at the fleet-vehicle centers and services available at the third-party-vehicle centers, and providing, for display within a fleet-location-management interface, identifiers for the fleet-vehicle centers and the third-party-vehicle centers and the services available at the fleet-vehicle centers and the third-party-vehicle centers. Also, the actcan include identifying a subset of vehicle service centers and a subset of third-party-vehicle centers in a geographical region; determining services available at the subset of vehicle service centers and services available at the subset of third-party-vehicle centers; and providing, for display within a fleet-location-management interface, identifiers for the subset of vehicle service centers and the subset of third-party-vehicle centers and the services available at the subset of vehicle service centers and the subset of third-party-vehicle centers.

1100 1100 1100 Additionally, in one or more embodiments, the series of actsincludes receiving vehicle data for third-party-rental vehicles, assigning one or more of the third-party-rental vehicles to the set of provider-rental vehicles or the set of personal-rental vehicles, and aggregating, into the vehicle-fleet-platform database, the vehicle data for the third-party-rental vehicles as assigned to the set of provider-rental vehicles or the set of personal-rental vehicles. Further, in some embodiments, the series of actsincludes receiving, from a computing device, updated vehicle data for a personal-rental vehicle indicating a change from a particular personal-use rental to a particular provider-user rental, based on the updated vehicle data, modifying a status for the personal-rental vehicle within the vehicle-fleet-platform database from the particular personal-use rental to the particular provider-use rental, and based on the modification to the particular provider-use rental, updating a vehicle-data summary for the personal-rental vehicle to become a provider-rental vehicle for display within the fleet management interface. Additionally, the series of actscan include receiving, from a computing device, updated vehicle data for a personal-rental vehicle; based on the updated vehicle data, determining a status change for the personal-rental vehicle within the vehicle-fleet-platform database from a particular personal-use rental to a particular provider-use rental; and, based on determining the status change to the particular provider-use rental, updating a vehicle-data summary for the personal-rental vehicle to become a provider-rental vehicle for display within a fleet management interface.

1100 Further, the series of actscan include receiving, from a rental requestor device, a rental request corresponding to a rental vehicle from the set of provider-rental vehicles or the set of personal-rental vehicles, based on the rental request, generating a virtual code for the rental requestor device to send to an in-vehicle-computing device connected by an on-board-diagnostics port to the rental vehicle, and providing the virtual code to the rental requestor device to access and start the rental vehicle based on the rental request.

1100 Additionally, the series of actscan include receiving, from a vehicle-service-computing device, a vehicle-damage tag indicating damage to a first rental vehicle from the set of provider-rental vehicles or the set of personal-rental vehicles; dispatching the first rental vehicle to a first vehicle service center from the one or more vehicle service centers based on the vehicle-damage tag; receiving, from a vehicle computing device, a vehicle-maintenance tag indicating a vehicle part requiring maintenance detected by a telematics device of a second rental vehicle from the set of provider-rental vehicles or the set of personal-rental vehicles; and dispatching the second rental vehicle to a second vehicle service center from the one or more vehicle service centers based on the vehicle-maintenance tag.

Embodiments of the present disclosure may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments within the scope of the present disclosure also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. In particular, one or more of the processes described herein may be implemented at least in part as instructions embodied in a non-transitory computer-readable medium and executable by one or more computing devices (e.g., any of the media content access devices described herein). In general, a processor (e.g., a microprocessor) receives instructions, from a non-transitory computer-readable medium, (e.g., a memory), and executes those instructions, thereby performing one or more processes, including one or more of the processes described herein.

Computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system, including by one or more servers. Computer-readable media that store computer-executable instructions are non-transitory computer-readable storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the disclosure can comprise at least two distinctly different kinds of computer-readable media: non-transitory computer-readable storage media (devices) and transmission media.

Non-transitory computer-readable storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to non-transitory computer-readable storage media (devices) (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a “NIC”), and then eventually transferred to computer system RAM and/or to less volatile computer storage media (devices) at a computer system. Thus, it should be understood that non-transitory computer-readable storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.

Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general-purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. In some embodiments, computer-executable instructions are executed on a general-purpose computer to turn the general-purpose computer into a special purpose computer implementing elements of the disclosure. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including, virtual reality devices, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

Embodiments of the present disclosure can also be implemented in cloud computing environments. In this description, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources. For example, cloud computing can be employed in the marketplace to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources. The shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.

A cloud-computing model can be composed of various characteristics such as, for example, on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth. A cloud-computing model can also expose various service models, such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”). A cloud-computing model can also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth. In this description and in the claims, a “cloud-computing environment” is an environment in which cloud computing is employed.

12 FIG. 12 FIG. 12 FIG. 12 FIG. 1200 113 106 112 119 120 122 124 116 1200 106 112 119 113 1202 1204 1206 1208 1210 1200 1200 illustrates, in block diagram form, an exemplary computing device(e.g., the server, the personal-renter-computing device, the provider-renter computing device, the third-party renter computing device, the rental-location-computing device, the vehicle-service-computing device, and/or the third-party device) that may be configured to perform one or more of the processes described above. One will appreciate that the fleet management systemcan comprise implementations of the computing device, including, but not limited to, the personal-renter-computing device(s), provider-renter computing device, the third-party-renter computing deviceand/or the server(s). As shown by, the computing device can comprise a processor, memory, a storage device, an I/O interface, and a communication interface. In certain embodiments, the computing devicecan include fewer or more components than those shown in. Components of computing deviceshown inwill now be described in additional detail.

1202 1202 1204 1206 In particular embodiments, the processorincludes hardware for executing instructions, such as those making up a computer program. As an example, and not by way of limitation, to execute instructions, the processormay retrieve (or fetch) the instructions from an internal register, an internal cache, memory, or a storage deviceand decode and execute them.

1200 1204 1202 1204 1204 1204 The computing deviceincludes memory, which is coupled to the processor. The memorymay be used for storing data, metadata, and programs for execution by the processor(s). The memorymay include one or more of volatile and non-volatile memories, such as Random Access Memory (“RAM”), Read Only Memory (“ROM”), a solid-state disk (“SSD”), Flash, Phase Change Memory (“PCM”), or other types of data storage. The memorymay be internal or distributed memory.

1200 1206 1206 1206 The computing deviceincludes a storage deviceincludes storage for storing data or instructions. As an example, and not by way of limitation, storage devicecan comprise a non-transitory storage medium described above. The storage devicemay include a hard disk drive (“HDD”), flash memory, a Universal Serial Bus (“USB”) drive or a combination of these or other storage devices.

1200 1208 1208 1200 1208 The computing devicealso includes one or more input or output interface(or “I/O interface”), which are provided to allow a user (e.g., requestor or provider) to provide input to (such as user strokes), receive output from, and otherwise transfer data to and from the computing device. The I/O interfacemay include a mouse, keypad or a keyboard, a touch screen, camera, optical scanner, network interface, modem, other known I/O devices or a combination of such. The touch screen may be activated with a stylus or a finger.

1208 1208 The I/O interfacemay include one or more devices for presenting output to a user, including, but not limited to, a graphics engine, a display (e.g., a display screen), one or more output providers (e.g., display providers), one or more audio speakers, and one or more audio providers. In certain embodiments, the I/O interfaceis configured to provide graphical data to a display for presentation to a user. The graphical data may be representative of one or more graphical user interfaces and/or any other graphical content as may serve a particular implementation.

1200 1210 1210 1210 1200 1210 1200 1212 1212 1200 The computing devicecan further include a communication interface. The communication interfacecan include hardware, software, or both. The communication interfacecan provide one or more interfaces for communication (such as, for example, packet-based communication) between the computing device and one or more other computing devicesor one or more networks. As an example, and not by way of limitation, communication interfacemay include a network interface controller (“NIC”) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (“WNIC”) or wireless adapter for communicating with a wireless network, such as a WI-FI. The computing devicecan further include a bus. The buscan comprise hardware, software, or both that connects components of computing deviceto each other.

13 FIG. 13 FIG. 1300 1302 114 1300 1306 106 112 119 120 122 114 1308 1304 1306 114 1308 1304 1306 114 1308 1304 1306 114 1308 1304 1306 114 1308 illustrates an example network environmentof a dynamic transportation matching system(e.g. the dynamic transportation matching system). The network environmentincludes a client device(e.g., the personal-renter-computing device, the provider-renter-computing device, the third-party-vehicle-renter-computing device, the rental-location-computing device, the vehicle-service-computing device), the dynamic transportation matching system, and a vehicle subsystemconnected to each other by a network. Althoughillustrates a particular arrangement of the client device, the dynamic transportation matching system, the vehicle subsystem, and the network, this disclosure contemplates any suitable arrangement of client device, the dynamic transportation matching system, the vehicle subsystem, and the network. As an example, and not by way of limitation, two or more of client device, the dynamic transportation matching system, and the vehicle subsystemcommunicate directly, bypassing network. As another example, two or more of client device, the dynamic transportation matching system, and the vehicle subsystemmay be physically or logically co-located with each other in whole or in part.

13 FIG. 1306 114 1308 1304 1306 114 1308 1304 1300 1306 114 1308 1304 Moreover, althoughillustrates a particular number of client devices, dynamic transportation matching system, vehicle sub systems, and networks, this disclosure contemplates any suitable number of client devices, dynamic transportation matching system, vehicle subsystems, and networks. As an example, and not by way of limitation, network environmentmay include multiple client device, dynamic transportation matching system, vehicle sub systems, and/or networks.

1304 1304 1304 1304 This disclosure contemplates any suitable network. As an example, and not by way of limitation, one or more portions of networkmay include an ad hoc network, an intranet, an extranet, a virtual private network (“VPN”), a local area network (“LAN”), a wireless LAN (“WLAN”), a wide area network (“WAN”), a wireless WAN (“WWAN”), a metropolitan area network (“MAN”), a portion of the Internet, a portion of the Public Switched Telephone Network (“PSTN”), a cellular telephone network, or a combination of two or more of these. Networkmay include one or more networks.

1306 116 1308 1304 1300 Links may connect client device, fleet management system, and vehicle subsystemto networkor to each other. This disclosure contemplates any suitable links. In particular embodiments, one or more links include one or more wireline (such as for example Digital Subscriber Line (“DSL”) or Data Over Cable Service Interface Specification (“DOCSIS”), wireless (such as for example Wi-Fi or Worldwide Interoperability for Microwave Access (“WiMAX”), or optical (such as for example Synchronous Optical Network (“SONET”) or Synchronous Digital Hierarchy (“SDH”) links. In particular embodiments, one or more links each include an ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion of the PSTN, a cellular technology-based network, a satellite communications technology-based network, another link, or a combination of two or more such links. Links need not necessarily be the same throughout network environment. One or more first links may differ in one or more respects from one or more second links.

1306 1306 1306 1306 1306 1304 1306 1306 13 FIG. In particular embodiments, the client devicemay be an electronic device including hardware, software, or embedded logic components or a combination of two or more such components and capable of carrying out the appropriate functionalities implemented or supported by client device. As an example, and not by way of limitation, a client devicemay include any of the computing devices discussed above in relation to. A client devicemay enable a network user at the client deviceto access the network. A client devicemay enable its user to communicate with other users at other client devices.

1306 1306 1306 1306 In particular embodiments, the client devicemay include a requestor application or a web browser, such as MICROSOFT INTERNET EXPLORER, GOOGLE CHROME or MOZILLA FIREFOX, and may have one or more add-ons, plug-ins, or other extensions, such as TOOLBAR or YAHOO TOOLBAR. A user at the client devicemay enter a Uniform Resource Locator (“URL”) or other address directing the web browser to a particular server (such as server), and the web browser may generate a Hyper Text Transfer Protocol (“HTTP”) request and communicate the HTTP request to server. The server may accept the HTTP request and communicate to the client deviceone or more Hyper Text Markup Language (“HTML”) files responsive to the HTTP request. The client devicemay render a webpage based on the HTML files from the server for presentation to the user. This disclosure contemplates any suitable webpage files. As an example, and not by way of limitation, webpages may render from HTML files, Extensible Hyper Text Markup Language (“XHTML”) files, or Extensible Markup Language (“XML”) files, according to particular needs. Such pages may also execute scripts such as, for example and without limitation, those written in JAVASCRIPT, JAVA, MICROSOFT SILVERLIGHT, combinations of markup language and scripts such as AJAX (Asynchronous JAVASCRIPT and XML), and the like. Herein, reference to a webpage encompasses one or more corresponding webpage files (which a browser may use to render the webpage) and vice versa, where appropriate.

114 114 114 114 114 In particular embodiments, dynamic transportation matching systemmay be a network-addressable computing system that can host a transportation matching network. The dynamic transportation matching systemmay generate, store, receive, and send data, such as, for example, user-profile data, concept-profile data, text data, transportation request data, GPS location data, provider data, requestor data, vehicle data, or other suitable data related to the transportation matching network. This may include authenticating the identity of providers and/or vehicles who are authorized to provide transportation services through the dynamic transportation matching system. In addition, the dynamic transportation matching systemmay manage identities of service requestors such as users/requestors. In particular, the dynamic transportation matching systemmay maintain requestor data such as driving/riding histories, personal data, or other user data in addition to navigation and/or traffic management services or other location services (e.g., GPS services).

114 114 In particular embodiments, the dynamic transportation matching systemmay manage transportation matching services to connect a user/requestor with a vehicle and/or provider. By managing the transportation matching services, the dynamic transportation matching systemcan manage the distribution and allocation of resources from vehicle systems and user resources such as GPS location and availability indicators, as described herein.

114 1300 1304 114 114 1306 114 The dynamic transportation matching systemmay be accessed by the other components of network environmenteither directly or via network. In particular embodiments, the dynamic transportation matching systemmay include one or more servers. Each server may be a unitary server or a distributed server spanning multiple computers or multiple datacenters. Servers may be of various types, such as, for example and without limitation, web server, news server, mail server, message server, advertising server, file server, application server, exchange server, database server, proxy server, another server suitable for performing functions or processes described herein, or any combination thereof. In particular embodiments, each server may include hardware, software, or embedded logic components or a combination of two or more such components for carrying out the appropriate functionalities implemented or supported by server. In particular embodiments, the dynamic transportation matching systemmay include one or more data stores. Data stores may be used to store various types of information. In particular embodiments, the information stored in data stores may be organized according to specific data structures. In particular embodiments, each data store may be a relational, columnar, correlation, or other suitable database. Although this disclosure describes or illustrates particular types of databases, this disclosure contemplates any suitable types of databases. Particular embodiments may provide interfaces that enable a client device, or a dynamic transportation matching systemto manage, retrieve, modify, add, or delete, the information stored in data store.

114 114 114 114 114 114 1304 In particular embodiments, the dynamic transportation matching systemmay provide users with the ability to take actions on various types of items or objects, supported by the dynamic transportation matching system. As an example, and not by way of limitation, the items and objects may include transportation matching networks to which users of the dynamic transportation matching systemmay belong, vehicles that users may request, location designators, computer-based applications that a user may use, transactions that allow users to buy or sell items via the service, interactions with advertisements that a user may perform, or other suitable items or objects. A user may interact with anything that is capable of being represented in the dynamic transportation matching systemor by an external system of a third-party system, which is separate from dynamic transportation matching systemand coupled to the dynamic transportation matching systemvia a network.

114 114 In particular embodiments, the dynamic transportation matching systemmay be capable of linking a variety of entities. As an example, and not by way of limitation, the dynamic transportation matching systemmay enable users to interact with each other or other entities, or to allow users to interact with these entities through an application programming interface (“API”) or other communication channels.

114 114 114 114 In particular embodiments, the dynamic transportation matching systemmay include a variety of servers, sub-systems, programs, modules, logs, and data stores. In particular embodiments, the dynamic transportation matching systemmay include one or more of the following: a web server, action logger, API-request server, relevance-and-ranking engine, content-object classifier, notification controller, action log, third-party-content-object-exposure log, inference module, authorization/privacy server, search module, advertisement-targeting module, user-interface module, user-profile (e.g., provider profile or requestor profile) store, connection store, third-party content store, or location store. The dynamic transportation matching systemmay also include suitable components such as network interfaces, security mechanisms, load balancers, failover servers, management-and-network-operations consoles, other suitable components, or any suitable combination thereof. In particular embodiments, the dynamic transportation matching systemmay include one or more user-profile stores for storing user profiles for transportation providers and/or transportation requestors. A user profile may include, for example, biographic information, demographic information, behavioral information, social information, or other types of descriptive information, such as interests, affinities, or location.

114 1306 114 1306 1306 1306 1306 114 114 1306 The web server may include a mail server or other messaging functionality for receiving and routing messages between the dynamic transportation matching systemand one or more client devices. An action logger may be used to receive communications from a web server about a user's actions on or off the dynamic transportation matching system. In conjunction with the action log, a third-party-content-object log may be maintained of user exposures to third-party-content objects. A notification controller may provide information regarding content objects to a client device. Information may be pushed to a client deviceas notifications, or information may be pulled from client deviceresponsive to a request received from client device. Authorization servers may be used to enforce one or more privacy settings of the users of the dynamic transportation matching system. A privacy setting of a user determines how particular information associated with a user can be shared. The authorization server may allow users to opt in to or opt out of having their actions logged by the dynamic transportation matching systemor shared with other systems, such as, for example, by setting appropriate privacy settings. Third-party-content-object stores may be used to store content objects received from third parties. Location stores may be used for storing location information received from client devicesassociated with users.

1308 1308 1308 In addition, the vehicle subsystemcan include a human-operated vehicle or an autonomous vehicle. A provider of a human-operated vehicle can perform maneuvers to pick up, transport, and drop off one or more requestors according to the embodiments described herein. In certain embodiments, the vehicle subsystemcan include an autonomous vehicle—i.e., a vehicle that does not require a human operator. In these embodiments, the vehicle subsystemcan perform maneuvers, communicate, and otherwise function without the aid of a human provider, in accordance with available technology.

1308 1308 1308 1308 In particular embodiments, the vehicle subsystemmay include one or more sensors incorporated therein or associated thereto. For example, sensor(s) can be mounted on the top of the vehicle subsystemor else can be located within the interior of the vehicle subsystem. In certain embodiments, the sensor(s) can be located in multiple areas at once—i.e., split up throughout the vehicle subsystemso that different components of the sensor(s) can be placed in different locations in accordance with optimal operation of the sensor(s). In these embodiments, the sensor(s) can include motion-related components such as an inertial measurement unit (“IMU”) including one or more accelerometers, one or more gyroscopes, and one or more magnetometers. The sensor(s) can additionally or alternatively include a wireless IMU (“WIMU”), one or more cameras, one or more microphones, or other sensors or data input devices capable of receiving and/or recording information relating to navigating a route to pick up, transport, and/or drop off a requestor.

1308 1306 116 1308 1304 In particular embodiments, the vehicle subsystemmay include a communication device capable of communicating with the client deviceand/or the fleet management system. For example, the vehicle subsystemcan include an on-board computing device communicatively linked to the networkto transmit and receive data such as GPS location information, sensor-related information, requestor location information, or other relevant information.

In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. Various embodiments and aspects of the invention(s) are described with reference to details discussed herein, and the accompanying drawings illustrate the various embodiments. The description above and drawings are illustrative of the invention and are not to be construed as limiting the invention. Numerous specific details are described to provide a thorough understanding of various embodiments of the present invention.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. For example, the methods described herein may be performed with less or more steps/acts or the steps/acts may be performed in differing orders. Additionally, the steps/acts described herein may be repeated or performed in parallel with one another or in parallel with different instances of the same or similar steps/acts. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.