Vehicle management system, vehicle management method, program, and recording medium

Abstract

To provide a technique which promotes efficient sharing use of vehicles which run on electric power by employees of a corporate body.SOLUTION: A vehicle management system includes: memory means which stores user information for identifying a plurality of users who are employees of a corporate body and vehicle information including a lending situation of a plurality of vehicles which run on electric power; identification means which identifies a first user included in the plurality of users on the basis of the user information; first reception means which receives a lending request from the first user; lending means which executes lending processing for lending a first vehicle of the plurality of vehicles to the first user in response to the reception of the lending request, the lending processing including processing for selecting the first vehicle having not yet been selected at a time of the reception of the lending request from the plurality of vehicles on the basis of the lending situation and processing for updating the lending situation so as to reflect the lending of the first vehicle.SELECTED DRAWING: Figure 14

Description

[Technical field]

[0001] The present invention relates to a vehicle management system, a vehicle management method, a program, and a recording medium. [Background technology]

[0002] Patent Document 1 discloses a technology that utilizes electric vehicles (EVs) parked in parking lots to achieve peak cutting and peak shifting optimization over a wide area without the need to install large-scale new secondary battery facilities. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-153114 A Summary of the Invention [Problem to be solved by the invention]

[0004] The EVs in Patent Document 1 include EVs for vehicle sharing services (such as car sharing businesses), but Patent Document 1 does not take into consideration the possibility of corporations allowing their employees to share EVs.

[0005] The present invention has been made in light of the above circumstances, and has an object to provide a technology that promotes efficient shared use of electrically powered vehicles by employees of a corporation. [Means for solving the problem]

[0006] In order to solve the above problems, the present invention provides a system for providing a vehicle that is capable of running on electric power, comprising: user information for identifying a plurality of users who are employees of a corporation; vehicle information including rental statuses of a plurality of vehicles that run on electric power; reservation information including one or more loan reservations, each with a scheduled loan time and a scheduled return time; A storage means for storing a storage means for storing the rental status including a scheduled return time for each of one or more vehicles currently on loan; and an identification means for identifying a first user included in the plurality of users based on the user information; Includes the first scheduled return timeA first receiving means for receiving a loan request, and in response to receiving the loan request, a determination means for determining the number N of vehicles that are not rented out at a current time based on the rental status, decrementing N by 1 for each of one or more scheduled rental times corresponding to the one or more rental reservations, incrementing N by 1 for each of one or more scheduled return times corresponding to the one or more rental reservations, and incrementing N by 1 for each of one or more scheduled return times corresponding to the one or more vehicles, thereby determining a time series change in N from the current time to the first scheduled return time, and determining whether or not a shortage of vehicles is expected based on the time series change in N; and if it is determined that a shortage of vehicles is not expected, a rental means for executing a rental process for renting a first vehicle of the plurality of vehicles to the first user, the rental process including a process of selecting the first vehicle from the plurality of vehicles based on the rental status, the first vehicle not selected before receiving the rental request, and a process of updating the rental status to reflect the rental of the first vehicle. registering the first scheduled return time in the rental status as a scheduled return time of the first vehicle. and a rental means including: Effect of the Invention

[0007] According to the present invention, it is possible to promote efficient shared use of electrically powered vehicles by employees of a corporation. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 shows the configuration of a vehicle management system 100. [Diagram 2] Conceptual diagram of Parking Lot 200. [Diagram 3] FIG. 3 is a functional block diagram of a vehicle 300. [Figure 4] FIG. 4 is a functional block diagram of a power control device 400. [Diagram 5] FIG. 5 is a functional block diagram of a vehicle management device 500. [Figure 6] FIG. 6 is a functional block diagram of a user terminal 600. [Figure 7] FIG. 7 shows the configuration of a user DB 700. [Figure 8] FIG. 2 is a diagram showing the configuration of a vehicle DB 800. [Figure 9] FIG. 9 shows the configuration of a reservation DB 900. [Figure 10] FIG. 6 is a diagram showing an example of a screen of a vehicle application installed on the user terminal 600. [Figure 11] FIG. 6 is a diagram showing an example of a screen of a vehicle application installed on the user terminal 600. [Figure 12] 4 is a flowchart of a process executed by the vehicle management device 500. [Figure 13] 12 is a flowchart showing details of a login process (S1202 in FIG. 12). [Figure 14] 12 is a flowchart showing details of a lending process (S1204 in FIG. 12). [Figure 15] 12 is a flowchart showing details of the return process (S1206 in FIG. 12). [Figure 16] 12 is a flowchart showing details of a reservation process (S1208 in FIG. 12). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0010] Fig. 1 is a diagram showing the configuration of a vehicle management system 100. The vehicle management system 100 includes at least one corporate facility (corporate facility 110a and corporate facility 110b in the example of Fig. 1), a commercial power source 120, a plurality of vehicles 300 (not shown in Fig. 1), a vehicle management device 500, and a plurality of user terminals 600.

[0011] In addition, when it is not necessary to strictly distinguish between the corporate facilities in explaining the embodiment, the corporate facilities included in the vehicle management system 100 will be simply called the corporate facility 110. This also applies to the components included in each corporate facility, and for example, when it is not necessary to strictly distinguish between the charging facility 130a included in the corporate facility 110a and the charging facility 130b included in the corporate facility 110b in explaining the embodiment, the notation "charging facility 130" will be used.

[0012] The corporate facility 110 is a facility under the management of a corporation (e.g., a company). The corporate facility 110 includes a charging facility 130, a power generation facility 140, a load 150, a parking lot 200, and a power control device 400. In the following description, it is assumed that the corporate facility 110a is a head office building, and the corporate facility 110b is an employee dormitory.

[0013] The charging equipment 130 includes a plurality of chargers for charging a plurality of vehicles 300 parked in the parking lot 200. The charging equipment 130 charges the vehicles 300 using power received from the power control device 400 under the control of the vehicle management device 500. The charging equipment 130 can also receive power from the vehicles 300 connected to the charger and supply it to the power control device 400 under the control of the vehicle management device 500. The power generation equipment 140 is equipment for private power generation, and includes, for example, solar panels. The load 150 is a collective representation of various devices that consume power in the corporate facility 110, and includes a personal computer (PC), an air conditioner, and an electric light.

[0014] 2 is a conceptual diagram of a parking lot 200. In the parking lot 200, some of the multiple vehicles 300 included in the vehicle management system 100 are parked at high density. By adopting a parking lot that can park at least some of the multiple vehicles 300 at high density as the parking lot 200, it is possible to reduce the number of vehicle lanes in the parking lot 200, improving the utilization efficiency of the site of the corporate facility 110. Note that "high density" here refers to a state in which at least one parked vehicle 200 is so crowded together that it cannot be moved without moving at least one other parked vehicle.

[0015] FIG. 3 is a functional block diagram of the vehicle 300. The vehicle 300 is a vehicle that runs on electricity, for example, an electric vehicle (EV). The control unit 301 includes, for example, a CPU, a ROM, and a RAM, and controls the entire vehicle 300 by executing various programs. The operation unit 302 includes an input device such as a button and a touch panel, and accepts input operations by a user. The storage unit 303 includes a recording medium such as an HDD and an SSD, and stores various programs. The display unit 304 includes, for example, a liquid crystal display, and displays a user interface and various information. The communication unit 305 is a communication unit for the vehicle 300 to communicate with an external device (such as the vehicle management device 500) via a communication network. The charging control unit 306 charges the battery 307 using the power supplied from the charging facility 130. The charging control unit 306 can also supply the power stored in the battery 307 to the charging facility 130.

[0016] FIG. 4 is a functional block diagram of the power control device 400. The power control device 400 is implemented by, for example, a computer connectable to a communication network. The control unit 401 includes, for example, a CPU, a ROM, and a RAM, and controls the entire power control device 400 by executing various programs. The control unit 401 also predicts future power demand in the corporate facility 110 and notifies the vehicle management device 500 of the predicted power demand. The control unit 401 also predicts future power generation of the power generation facility 140 and notifies the vehicle management device 500 of the predicted power generation amount. The power receiving unit 402 receives power from the commercial power source 120 and the power generation facility 140. The power receiving unit 402 can also receive power stored in the battery of the vehicle 300 connected to the charger from the charging facility 130. The storage unit 403 includes, for example, a recording medium such as an HDD and an SSD, and stores various programs. The power supply unit 404 supplies the power received by the power receiving unit 402 to the charging facility 130 and the load 150. The communication unit 405 is a communication unit for allowing the power control device 400 to communicate with external devices (such as the vehicle management device 500) via a communication network.

[0017] 5 is a functional block diagram of the vehicle management device 500. The vehicle management device 500 is implemented by, for example, a computer connectable to a communication network. The control unit 501 includes, for example, a CPU, a ROM, and a RAM, and controls the entire vehicle management device 500 by executing various programs. The storage unit 503 includes a recording medium such as an HDD and an SSD, and stores various programs. The storage unit 503 also stores a user DB 700, a vehicle DB 800, and a reservation DB 900, which will be described later. The communication unit 505 is a communication unit that allows the vehicle management device 500 to communicate with external devices (such as the vehicle 300, the power control device 400, and the user terminal 600) via the communication network.

[0018] The control unit 501 of the vehicle management device 500 can plan the delivery of vehicles from outside to inside the corporate facility 110 based on the forecast of the power demand in the corporate facility 110 acquired from the power control device 400. For example, in the case of focusing on the corporate facility 110a, the control unit 501 plans the delivery of vehicles from the parking lot 200b outside the corporate facility 110a to the parking lot 200a inside the corporate facility 110a when the forecasted power demand is large. When the vehicles are delivered according to the plan, the number of vehicles 300 connected to the charger of the charging facility 130a can be increased. Then, the control unit 501 can increase the amount of power available in the corporate facility 110a by controlling the power charged in the vehicle 300 (strictly speaking, the battery 307) connected to the charger of the charging facility 130a to be supplied to the load 150a. The method of implementing the planned delivery of the vehicles is not particularly limited, but the delivery of the vehicles can be implemented by, for example, recruiting users who will deliver the vehicles, as described with reference to S1607 and S1608 of FIG. 16.

[0019] FIG. 6 is a functional block diagram of the user terminal 600. The user terminal 600 is, for example, a smartphone, but may be another type of device (for example, a tablet, etc.). The control unit 601 includes, for example, a CPU, a ROM, and a RAM, and controls the entire user terminal 600 by executing various programs. The operation unit 602 includes, for example, an input device such as a button and a touch panel, and accepts input operations by a user. The storage unit 603 includes, for example, a recording medium such as an HDD and an SSD, and stores various programs. The display unit 604 includes, for example, a liquid crystal display, and displays a user interface, various information, etc. The communication unit 605 is a communication unit that allows the user terminal 600 to communicate with an external device (such as the vehicle management device 500) via a communication network.

[0020] Next, the user DB 700, the vehicle DB 800, and the reservation DB 900 stored in the storage unit 503 of the vehicle management device 500 will be described with reference to FIGS.

[0021] 7 is a diagram showing the configuration of a user DB700 stored in the memory unit 503 of the vehicle management device 500. The user DB700 is a database (DB) for managing user information identifying multiple users who are employees of a corporation (multiple users who can rent a vehicle 300). The user DB700 includes a "user ID" and a "password" as identification information and authentication information for each user. Furthermore, in addition to the identification information and authentication information, the user DB700 may also include the "name" and "affiliation" of each user.

[0022] FIG. 8 is a diagram showing the configuration of the vehicle DB 800 stored in the storage unit 503 of the vehicle management device 500. The vehicle DB 800 is a database (DB) for managing the vehicle 300. The vehicle DB 800 includes a "vehicle ID" for identifying the vehicle 300, a "number plate" indicating the information of the number plate of the vehicle 300, and a "parking lot ID" for identifying the parking lot 200 in which the vehicle 300 is parked. In the following description, the parking lot ID is assumed to be "P001" corresponding to the parking lot 200a of the corporate facility 110a, and "P002" corresponding to the parking lot 200b of the corporate facility 110b. For vehicles 300 that are being rented, the "parking lot ID" is blank. The vehicle DB 800 also includes a "user ID" of the user who is renting the vehicle 300. For vehicles 300 that are not being rented, the "user ID" is blank. Therefore, the vehicle management device 500 can check the rental status of multiple vehicles 300 by referring to the vehicle DB 800.

[0023] Vehicle DB 800 also includes a "scheduled return time" and a "return parking lot ID" for the rented vehicle 300. The return parking lot ID is registered with the parking lot ID of the parking lot where the user plans to return the vehicle 300. For example, an entry of "vehicle ID" = "V0002" in vehicle DB 800 corresponds to a case where a vehicle has been rented out in accordance with information selected on screen 1003 in Fig. 10, which will be described later.

[0024] Furthermore, the vehicle DB 800 includes the "charge amount" of the battery 307 of the vehicle 300, and a "charging facility ID" that identifies the charging facility 130 corresponding to the charger to which the vehicle 300 is connected. In the following description, regarding the charging facility ID, "C001" corresponds to the charging facility 130a, and "C002" corresponds to the charging facility 130b. Furthermore, "disconnected" indicates that the vehicle 300 is not connected to the charger.

[0025] Furthermore, the vehicle DB 800 includes a "charging schedule" of the vehicle connected to the charger of the charging facility 130. The control unit 501 of the vehicle management device 500 determines a charging schedule according to a predetermined standard, and registers the determined charging schedule in the vehicle DB 800. Then, the control unit 501 of the vehicle management device 500 controls the charging facility 130 via the power control device 400, thereby charging the vehicle 300 according to the charging schedule registered in the vehicle DB 800.

[0026] As an example of a criterion for determining the charging schedule, the control unit 501 can determine the charging schedule based on a prediction of power demand in the corporate facility 110 acquired from the power control device 400. In this case, for example, the control unit 501 determines the charging schedule so that charging starts at a timing when the predicted power demand is small. As another example, the vehicle DB 800, the control unit 501 can determine the charging schedule based on a prediction of the amount of power generated by the power generation facility 140 acquired from the power control device 400 in addition to the prediction of the power demand. In this case, for example, the control unit 501 determines the charging schedule so that charging starts at a timing when the predicted power demand is small and the predicted amount of power generation is large.

[0027] FIG. 9 is a diagram showing the configuration of the reservation DB900 stored in the storage unit 503 of the vehicle management device 500. The reservation DB900 is a database (DB) for managing rental reservations of the vehicle 300. The reservation DB900 includes a "reservation user ID," a "passenger user ID," a "scheduled rental time," a "rental parking lot ID," a "scheduled return time," and a "return parking lot ID." The reservation user ID is registered with the user ID of the user who made the reservation. The passenger user ID is registered with the user ID of the user who plans to ride with the vehicle 300 rented by the user indicated by the reservation user ID. If there is no user who plans to ride with the user, the "passenger user ID" is blank. The rental parking lot ID is registered with the parking lot ID of the parking lot where the user plans to rent the vehicle 300. The return parking lot ID is registered with the parking lot ID of the parking lot where the user plans to return the vehicle 300.

[0028] Next, operations performed by the user of the user terminal 600 will be described with reference to Fig. 10 and Fig. 11. The user can install an application program (hereinafter referred to as a "vehicle application") for carrying out procedures such as rental of the vehicle 300 in the user terminal 600. The installed vehicle application is stored in the storage unit 603 of the user terminal 600.

[0029] When the vehicle application is started, a screen 1001 shown in FIG. 10 is displayed on the display unit 604 of the user terminal 600. The user inputs a user ID and password, and presses the "Login" button. As a result, a login request including the user ID and password is transmitted to the vehicle management device 500. The login process executed by the vehicle management device 500 in response to the login request will be described later with reference to FIG. 13.

[0030] Once the login is complete, screen 1002 is displayed. In screen 1002, the user can select whether to rent vehicle 300 without a reservation, to rent vehicle 300 according to a reservation, or to make a rental reservation for vehicle 300.

[0031] When renting the vehicle 300 without a reservation, the user presses the "Get in now (no reservation)" button on the screen 1002. This displays the screen 1003. The screen 1003 displays the user ID of the logged-in user. The user selects the rental parking lot, the return parking lot, and the scheduled return time on the screen 1003, and presses the "OK" button. This causes a rental request including the user ID, the rental parking lot ID, the return parking lot ID, and the scheduled return time to be transmitted to the vehicle management device 500. The rental process executed by the vehicle management device 500 in response to the rental request will be described later with reference to FIG. 14. The rental parking lot on the screen 1003 may be automatically selected by the control unit 601 of the user terminal 600 based on location information acquired by GPS. The control unit 601 may also determine whether the user is in the selected rental parking lot based on location information acquired by GPS, and if not, display an error message indicating that the vehicle 300 cannot be rented out.

[0032] When renting the vehicle 300 according to the reservation, the user presses the "Get in now (reservation made)" button on the screen 1002. This causes the screen 1004 to be displayed. The screen 1004 displays the user ID of the logged-in user, the rental parking lot selected at the time of reservation, the scheduled rental time, the return parking lot, and the scheduled return time. In order to display the screen 1004, the control unit 601 acquires data indicating the rental parking lot selected at the time of reservation, the scheduled rental time, the return parking lot, and the scheduled return time from the storage unit 603. When the user presses the "OK" button, a rental request including the user ID, the rental parking lot ID, the scheduled rental time, the return parking lot ID, and the scheduled return time is transmitted to the vehicle management device 500. The rental process executed by the vehicle management device 500 in response to the rental request will be described later with reference to FIG. 14. The control unit 601 may determine whether the user is in the rental parking lot selected at the time of reservation based on the position information acquired by the GPS, and if the user is not in the rental parking lot, an error message indicating that the vehicle 300 cannot be rented out may be displayed.

[0033] When the rental process by the vehicle management device 500 is completed, a screen 1101 shown in FIG. 11 is displayed on the display unit 604 of the user terminal 600. The screen 1101 displays the user ID of the logged-in user, the license plate information of the rented vehicle 300, the return parking lot, and the scheduled return time. When returning the vehicle 300, the user parks the vehicle 300 in the return parking lot and presses the "Return" button on the screen 1101. This causes a return request including the user ID to be transmitted to the vehicle management device 500. The return process executed by the vehicle management device 500 in response to the return request will be described later with reference to FIG. 15. When the return of the vehicle 300 is completed, the screen 1002 is displayed again.

[0034] When reserving a rental of vehicle 300, the user presses the "Make reservation" button on screen 1002. This causes screen 1102 shown in FIG. 11 to be displayed on display unit 604 of user terminal 600. Screen 1102 displays the user ID of the logged-in user. The user selects the rental parking lot, the scheduled rental time, the return parking lot, and the scheduled return time, and presses the "OK" button. This causes a reservation request including the user ID, rental parking lot ID, scheduled rental time, return parking lot ID, and scheduled return time to be sent to vehicle management device 500. The reservation process executed by vehicle management device 500 in response to the reservation request will be described later with reference to FIG. 16.

[0035] If the reservation is successful, screen 1103 shown in Fig. 11 is displayed on display unit 604 of user terminal 600. Screen 1103 displays the user ID of the logged-in user, as well as the rental parking lot selected at the time of reservation, the scheduled rental time, the return parking lot, and the scheduled return time. In addition, control unit 601 stores data indicating the rental parking lot selected at the time of reservation, the scheduled rental time, the return parking lot, and the scheduled return time in memory unit 603. When the user presses the "OK button" on screen 1103, screen 1002 is displayed again.

[0036] If the reservation fails due to a lack of vehicles, a screen 1104 shown in Fig. 11 is displayed on the display unit 604 of the user terminal 600. On the screen 1104, the user can select whether to request the reservation of a vehicle to succeed in the reservation, or to abandon the reservation. The screen 1104 displays an additional fee that will be incurred when the reservation of a vehicle is requested.

[0037] If the user wishes to abandon the reservation, he or she presses the "OK" button on screen 1104. This causes screen 1002 to be displayed again.

[0038] When requesting vehicle reservation, the user presses the "Request vehicle reservation" button on screen 1104. This sends a vehicle reservation request to the vehicle management device 500. The process executed by the vehicle management device 500 in response to a vehicle reservation request is included in the reservation process, and details will be described later with reference to FIG. 16. If the vehicle reservation is successful, the reservation is successful and screen 1103 is displayed. If the vehicle reservation is unsuccessful, a message indicating that the vehicle reservation has failed is displayed, and then screen 1002 is displayed again.

[0039] Fig. 12 is a flowchart of processing executed by the vehicle management device 500. In the following description, unless otherwise specified, it is assumed that the control unit 501 of the vehicle management device 500 executes a program to execute the processing of each step of this flowchart (including the flowcharts of Figs. 13 to 16, which are subroutines).

[0040] In S1201, the control unit 501 determines whether or not a login request has been received from the user terminal 600. If a login request has been received, the process proceeds to S1202, and if not, the process proceeds to S1203.

[0041] In S1202, the control unit 501 executes a login process. The details of the login process will be described later with reference to FIG.

[0042] In S1203, the control unit 501 determines whether or not a lending request has been received from the user terminal 600. If a lending request has been received, the process proceeds to S1204, and if not, the process proceeds to S1205.

[0043] In S1204, the control unit 501 executes a lending process. The details of the lending process will be described later with reference to FIG.

[0044] In S1205, the control unit 501 determines whether or not a return request has been received from the user terminal 600. If a return request has been received, the process proceeds to S1206, and if not, the process proceeds to S1207.

[0045] In S1206, the control unit 501 executes a return process. The details of the return process will be described later with reference to FIG.

[0046] In S1207, the control unit 501 determines whether or not a reservation request has been received from the user terminal 600. If a reservation request has been received, the process proceeds to S1208, and if not, the process returns to S1201.

[0047] In S1208, the control unit 501 executes a reservation process. The details of the reservation process will be described later with reference to FIG.

[0048] Fig. 13 is a flowchart showing details of the login process (S1202 in Fig. 12). In S1301, the control unit 501 determines whether or not the user ID and password included in the login request are valid by referring to the user DB 700 stored in the storage unit 503. If the user ID and password are valid (if an entry in which the combination of the user ID and password included in the login request is registered exists in the user DB 700), the processing step proceeds to S1302, and if not, the processing step proceeds to S1303.

[0049] In S1302, the control unit 501 transmits a login success message to the user terminal 600. The login success message includes a token indicating that the user terminal 600 has already logged in. When the user terminal 600 subsequently accesses the vehicle management device 500, the user terminal 600 transmits the token to the vehicle management device 500, thereby indicating that the user terminal 600 has already logged in (the user of the user terminal 600 has been identified and authenticated).

[0050] 12 are assumed to be sent by a logged-in user terminal 600. When a loan request, return request, or reservation request is received from a user terminal 600 that is not logged in, the control unit 501 sends an error message to the user terminal 600 to prompt the user to log in.

[0051] In S1303, the control unit 501 transmits to the user terminal 600 a login failure message indicating that the login has failed.

[0052] Fig. 14 is a flowchart showing details of the rental process (S1204 in Fig. 12). In S1401, the control unit 501 determines whether or not there is a vacant vehicle (a vehicle that is not currently being rented out) in the rental parking lot, based on the rental parking lot ID included in the rental request and the "parking lot ID" column in the vehicle DB 800. If there is a vacant vehicle, the process proceeds to S1402, and if not, the process proceeds to S1410.

[0053] In S1402, the control unit 501 determines whether the lending request is based on a reservation. If the lending request includes a scheduled lending time, the control unit 501 determines that the lending request is based on a reservation. Note that even if the lending request includes a scheduled lending time, if the current time is earlier than the scheduled lending time, the control unit 501 may determine that the lending request is not based on a reservation. If the lending request is based on a reservation, the processing step proceeds to S1404, and if not, the processing step proceeds to S1043.

[0054] In S1403, the control unit 501 determines whether or not a shortage of vehicles is expected when vehicles are rented out. If a shortage of vehicles is expected, the process proceeds to S1410, and if not, the process proceeds to S1404.

[0055] An example of a criterion for determining whether or not a shortage of vehicles is expected will be described. First, the control unit 501 determines the number of vacant vehicles in the rental parking lot based on the rental parking lot ID included in the rental request and the column of "parking lot ID" in the vehicle DB 800. Next, the control unit 501 determines the time series change in the number of vacant vehicles in the rental parking lot based on the columns of "scheduled return time" and "return parking lot ID" in the vehicle DB 800 and the columns of "scheduled rental time", "rental parking lot ID", "scheduled return time", and "return parking lot ID" in the reservation DB 900. If the reservation DB 900 contains an entry (rental reservation) in which the same rental parking lot ID as the rental parking lot ID included in the rental request is registered, it is determined that the number of vacant vehicles will decrease by one at the scheduled rental time corresponding to that entry. Similarly, if the reservation DB 900 contains an entry in which the same return parking lot ID as the rental parking lot ID included in the rental request is registered, it is determined that the number of vacant vehicles will increase by one at the scheduled return time corresponding to that entry. Furthermore, if the vehicle DB 800 contains an entry in which the same return parking lot ID as the rental parking lot ID included in the rental request is registered, it is determined that the number of available vehicles will increase by one at the scheduled return time corresponding to that entry. The control unit 501 then determines whether there is a timing at which the number of available vehicles will be 0 between the current time and the scheduled return time included in the rental request. If there is a timing at which the number of available vehicles will be 0, the control unit 501 determines that a shortage of vehicles is expected. Note that if the rental parking lot ID and the return parking lot ID included in the rental request do not match, the control unit 501 may determine whether there is a timing at which the number of available vehicles will be 0, including a time period after the scheduled return time (for example, from the current time to three hours after the scheduled return time).

[0056] In S1404, the control unit 501 selects a vehicle to be rented out. Although the selection criteria are not particularly limited, as an example, the control unit 501 selects the vehicle with the largest amount of charge among the vehicles parked in a position that can be exited from the parking lot.

[0057] In S1405, the control unit 501 updates the vehicle DB 800. Specifically, the control unit 501 changes the "parking lot ID" of the entry in the vehicle DB 800 corresponding to the vehicle to be rented out to a blank field. The control unit 501 also registers the user ID, expected return time, and return parking lot ID included in the rental request in the "user ID," "expected return time," and "return parking lot ID" of this entry, respectively.

[0058] In S1406, the control unit 501 determines whether the lending request is based on a reservation, as in S1402. If the lending request is based on a reservation, the process proceeds to S1407, and if not, the process proceeds to S1408.

[0059] In S1407, the control unit 501 updates the reservation DB 900. Specifically, the control unit 501 deletes an entry corresponding to the lending request from the reservation DB 900. Note that the entry corresponding to the lending request can be identified based on the user ID and the scheduled lending time included in the lending request.

[0060] In S1408, the control unit 501 unlocks the vehicle to be rented out. The unlocking is performed, for example, by the control unit 501 instructing the control unit 301 of the vehicle 300 to unlock the vehicle via the communication network. When the vehicle 300 is unlocked, the user can get in and drive the vehicle 300.

[0061] In S1409, the control unit 501 transmits a rental completion message including information on the license plate of the vehicle to be rented to the user terminal 600. Based on the rental completion message, the user terminal 600 can display a screen such as the screen 1101 in FIG.

[0062] In S1410, the control unit 501 transmits to the user terminal 600 a rental denial message indicating that the vehicle cannot be rented.

[0063] FIG. 15 is a flowchart showing details of the return process (S1206 in FIG. 12). In S1501, the control unit 501 determines whether the vehicle 300 is parked in the correct position. The parking position of the vehicle 300 can be identified, for example, by using a sensor installed in the parking lot 200. If the vehicle 300 is parked in an appropriate position in the parking lot 200 and the parking lot 200 matches the return parking lot, the control unit 501 determines that the vehicle 300 is parked in the correct position. The return parking lot can be identified by referring to the return parking lot ID corresponding to the user ID included in the return request in the vehicle DB 800. If the vehicle 300 is parked in the correct position, the process proceeds to S1502, and if not, the process proceeds to S1505.

[0064] In S1502, the control unit 501 locks the vehicle 300. The vehicle is locked, for example, by the control unit 501 instructing the control unit 301 of the vehicle 300 to lock the vehicle via a communication network.

[0065] In S1503, the control unit 501 updates the vehicle DB 800. Specifically, the control unit 501 registers the return parking lot ID in the "parking lot ID" of the entry in the vehicle DB 800 corresponding to the returned vehicle. The control unit 501 also changes the "user ID", "scheduled return time", and "return parking lot ID" of this entry to blank.

[0066] In S1504, the control unit 501 transmits to the user terminal 600 a return completion message indicating that the return of the vehicle has been completed.

[0067] In S1505, the control unit 501 transmits to the user terminal 600 a return-prohibited message indicating that the vehicle cannot be returned.

[0068] 16 is a flowchart showing details of the reservation process (S1208 in FIG. 12). First, the control unit 501 determines, through the processes of S1601 and S1602, whether or not the vehicle 300 can be rented out at the scheduled rental time included in the reservation request in the parking lot 200 indicated by the rental parking lot ID included in the reservation request.

[0069] Specifically, in S1601, the control unit 501 refers to the scheduled rental time and rental parking lot ID included in the reservation request and determines whether there is a vacant vehicle in the rental parking lot at the scheduled rental time. To make this determination, for example, the control unit 501 determines the time series change in the number of vacant vehicles in the rental parking lot, similar to S1404 in Fig. 14. Then, if the number of vacant vehicles at the scheduled rental time is one or more, the control unit 501 determines that there is a vacant vehicle in the rental parking lot at the scheduled rental time. If there is a vacant vehicle in the rental parking lot at the scheduled rental time, the process proceeds to S1602, and if not, the process proceeds to S1605.

[0070] In S1602, the control unit 501 judges whether or not a shortage of vehicles is expected. The judgment in S1602 can be performed in the same manner as the judgment in S1403. However, while in S1403 the period from the current time to the scheduled return time included in the rental request was the period subject to judgment, in S1602 the period from the scheduled rental time to the scheduled return time included in the reservation request is the period subject to judgment. Note that, similarly to S1403, if the rental parking lot ID and the return parking lot ID included in the reservation request do not match, the control unit 501 may also include the time period after the scheduled return time in the period subject to judgment. If a shortage of vehicles is expected, the process proceeds to S1605, and if not, the process proceeds to S1603.

[0071] In S1603, the control unit 501 updates the reservation DB 900. Specifically, the control unit 501 adds an entry in which the user ID, scheduled rental time, rental parking lot ID, scheduled return time, and return parking lot ID included in the reservation request are registered to the reservation DB 900 (the user ID is registered in the "reservation user ID" column).

[0072] In S1604, the control unit 501 transmits a reservation completion message indicating that the reservation has been completed to the user terminal 600. As a result, a screen such as a screen 1103 in FIG.

[0073] In S1605, the control unit 501 transmits a reservation impossible message indicating that a reservation is not possible due to a shortage of vehicles to the user terminal 600. As a result, a screen such as a screen 1104 in FIG.

[0074] In S1605, the control unit 501 determines whether or not a vehicle reservation request has been received from the user terminal 600. A vehicle reservation request is transmitted from the user terminal 600 to the vehicle management device 500 when the user presses the "Request vehicle reservation" button on the screen 1104. If a vehicle reservation request has been received, the processing proceeds to S1607, and if not, the reservation processing of this flowchart ends.

[0075] In S1607, the control unit 501 transmits a notification to the user terminal 600 of another user inviting a user to deliver a vehicle or ride-share in a manner that increases the number of vacant vehicles in the time period corresponding to the reservation request. The specific form of the invitation is not particularly limited, but for example, the control unit 501 can invite a user who will deliver a vehicle from a parking lot (e.g., parking lot 200b) other than the rental parking lot (e.g., parking lot 200a) to the rental parking lot by the scheduled rental time. As another example, the control unit 501 invites a user who will perform a ride-share in a manner that cancels a rental reservation that conflicts with the reservation request. In order to perform this invitation, the control unit 501 refers to the reservation DB 900 and searches for a rental reservation that conflicts with the reservation request (e.g., a rental reservation for renting a vehicle from a rental parking lot included in the reservation request in the time period corresponding to the reservation request). When multiple rental reservations that conflict with the reservation request are found, the control unit 501 invites a user to ride-share from the users corresponding to the multiple rental reservations found.

[0076] In S1608, the control unit 501 determines whether or not there has been an application from another user for the vehicle delivery or ride sharing recruitment. If there has been an application, the process proceeds to S1609, and if there has been no application, the process proceeds to S1610.

[0077] In S1609, the control unit 501 updates the reservation DB 900. The update of the reservation DB 900 in S1609 includes an update related to a user who has requested the reservation of a vehicle and an update related to a user who has applied for a vehicle delivery or ride sharing recruitment. The update related to a user who has requested the reservation of a vehicle is the same as that in S1603.

[0078] When a vehicle delivery solicitation is received, the control unit 501 adds an entry to the reservation DB 900 that includes the user ID of the user who applied as the "reservation user ID". The "rental parking lot" and "return parking lot" of this entry respectively register the parking lot ID of the parking lot selected by the control unit 501 at the time of solicitation and the rental parking lot included in the reservation request. The "scheduled rental time" and "scheduled return time" of this entry register the time selected by the user who applied, under the condition that the vehicle is returned by the scheduled rental time included in the reservation request.

[0079] When an application for a ride share is received, the control unit 501 deletes the entry of the user who agreed to ride in the vehicle of another user in the reservation DB 900, and registers the user ID of this user in the "passenger user ID" of the entry of the user who agreed to ride with another user.

[0080] The control unit 501 may provide a reward to a user who applied for a vehicle delivery or ride sharing recruitment. The reward is not particularly limited, but may be, for example, a coupon. In this case, the control unit 501 may transmit an electronic coupon to the user terminal 600 of the user who applied.

[0081] In S1610, the control unit 501 transmits an allocation failure message indicating that the vehicle allocation has failed to the user terminal 600 of the user who has requested the vehicle allocation.

[0082] <Summary of the embodiment> The above embodiment discloses at least the following network management device, network management method, and program.

[0083] [Item 1] A storage means for storing user information for identifying a plurality of users who are employees of a corporation and vehicle information including rental statuses of a plurality of vehicles that run on electric power; an identification means for identifying a first user included in the plurality of users based on the user information; a first receiving means for receiving a loan request from the first user; A rental means for executing a rental process to rent a first vehicle among the plurality of vehicles to the first user in response to receiving the rental request, the rental process comprising: selecting the first vehicle from the plurality of vehicles based on the rental status, the first vehicle not selected prior to receiving the rental request; updating the rental status to reflect the rental of the first vehicle; A lending instrument comprising: A vehicle management system comprising:

[0084] According to this embodiment, the vehicle to be rented to the user (employee of the corporation) is not selected before receiving the rental request, but is selected based on the rental status in response to the receipt of the rental request. Therefore, since there is no need to assign a unique vehicle to each user in advance, it becomes possible for employees of the corporation to efficiently share multiple vehicles that run on electricity.

[0085] [Item 2] An acquisition means for acquiring a forecast of electricity demand in a facility of the corporation; A determination means for determining a charging schedule for vehicles connected to a charging means provided in the facility of the corporation based on the prediction of the power demand; 2. The vehicle management system according to item 1, further comprising:

[0086] According to this embodiment, it becomes possible to adjust the amount of power usage in a corporation's facilities, making it possible to realize, for example, peak cutting or peak shifting of power usage.

[0087] [Item 3] The acquisition means acquires a forecast of the amount of power generated by the solar power generation means installed in the facility of the corporation, The determination means determines the charging schedule further based on the prediction of the amount of power generation. 3. A vehicle management system according to item 2, characterized in that:

[0088] According to this embodiment, the amount of power generated by the solar power generation means is taken into consideration, so that it is possible to more effectively adjust the amount of power usage in the corporation's facilities.

[0089] [Item 4] The vehicle information includes the charging schedule, a connection status of the plurality of vehicles to the charging means, and a charging amount of the plurality of vehicles. 4. The vehicle management system according to item 2 or 3.

[0090] According to this embodiment, it becomes possible to manage, as vehicle information, a charging schedule related to the adjustment of power usage in the corporate facilities, the connection status of multiple vehicles to charging means, and the charge amounts of multiple vehicles.

[0091] [Item 5] An acquisition means for acquiring a forecast of electricity demand in a facility of the corporation; a control means for controlling the supply of electric power charged in a vehicle connected to a charging means provided in the facility of the corporation to a load provided in the facility of the corporation; A planning means for planning a delivery of vehicles from outside the facility of the corporation to inside the facility of the corporation based on the forecast of the electricity demand; 2. The vehicle management system according to item 1, further comprising:

[0092] According to this embodiment, it becomes possible to increase the amount of power that can be supplied to the loads in the facilities of the corporation in accordance with the forecast of the power demand.

[0093] [Item 6] The vehicle parking facility further includes a parking lot capable of parking at least a portion of the plurality of vehicles at a high density. 6. A vehicle management system according to any one of items 1 to 5.

[0094] According to this embodiment, it is possible to reduce the parking area required per vehicle.

[0095] [Item 7] a second receiving means for receiving a return request from the first user while the first vehicle is being rented; A return means for executing a return process of the first vehicle in response to receiving the return request, the return process comprising: updating the rental status to reflect the return of the first vehicle. A return means including: 7. The vehicle management system according to any one of items 1 to 6, further comprising:

[0096] This embodiment allows a user who has rented a vehicle to return the vehicle.

[0097] [Item 8] The storage means stores reservation information including one or more rental reservations, each of which includes a user's identification information and a scheduled rental time; The vehicle management system includes: a third receiving means for receiving a reservation request including a first scheduled rental time from the first user; A reservation means for executing a reservation process in response to receiving the reservation request, the reservation process comprising: A process of determining whether or not the vehicle can be rented at the first scheduled rental time based on the rental status and the reservation information; adding a rental reservation including identification information of the first user and the first scheduled rental time to the reservation information when it is determined that the vehicle can be rented at the first scheduled rental time; A reservation means including: 8. The vehicle management system according to any one of items 1 to 7, further comprising:

[0098] This embodiment allows a user to reserve a vehicle for rental.

[0099] [Item 9] The reservation process includes: When it is determined that the vehicle cannot be rented at the first scheduled rental time, a process of recruiting users to ride-share by canceling a rental reservation that conflicts with the reservation request among the one or more rental reservations; When an application is received for the ride-sharing user recruitment, a process of canceling the rental reservation that conflicts with the reservation request and adding a rental reservation including the identification information of the first user and the first scheduled rental time to the reservation information; Further comprising: 9. The vehicle management system according to item 8,

[0100] This embodiment allows users to make reservations even when there is a shortage of vehicles.

[0101] [Item 10] The rental status includes identification information of a parking lot where the vehicle is parked without being rented out; The storage means stores reservation information including one or more rental reservations, each of which includes a user's identification information, an identification information of a parking lot where the rental is to be performed, and a scheduled rental time; The vehicle management system includes: a third receiving means for receiving a reservation request from the first user, the reservation request including identification information of a first parking lot where the rental will be performed and a first scheduled rental time; A reservation means for executing a reservation process in response to receiving the reservation request, the reservation process comprising: A process of determining whether or not the vehicle can be rented out at the first parking lot at the first scheduled rental time based on the rental status and the reservation information; When it is determined that the vehicle can be rented out at the first parking lot at the first scheduled rental time, a process of adding a rental reservation including identification information of the first user, identification information of the first parking lot, and the first scheduled rental time to the reservation information; A reservation means including: 8. The vehicle management system according to any one of items 1 to 7, further comprising:

[0102] This embodiment allows a user to reserve a vehicle for rental.

[0103] [Item 11] The reservation process includes: When it is determined that the vehicle cannot be rented out at the first parking lot at the first scheduled rental time, a process of recruiting a user who will deliver the vehicle to the first parking lot from a parking lot other than the first parking lot by the first scheduled rental time; When an application is received for a user who delivers the vehicle, a process of adding a rental reservation including identification information of the first user, identification information of the first parking lot, and the first scheduled rental time to the reservation information; Further comprising: 11. A vehicle management system according to item 10, characterized in that:

[0104] This embodiment allows users to make reservations even when there is a shortage of vehicles.

[0105] [Item 12] A vehicle management method executed by a vehicle management system having a storage means for storing user information for identifying a plurality of users who are employees of a corporation and vehicle information including rental statuses of a plurality of vehicles that run on electric power, the method comprising: an identification step of identifying a first user included in the plurality of users based on the user information; a first receiving step of receiving a loan request from the first user; a rental process for executing a rental process for renting a first vehicle among the plurality of vehicles to the first user in response to receiving the rental request, the rental process including: selecting the first vehicle from the plurality of vehicles based on the rental status, the first vehicle not selected prior to receiving the rental request; updating the rental status to reflect the rental of the first vehicle; A lending process including: A vehicle management method comprising:

[0106] According to this embodiment, the vehicle to be rented to the user (employee of the corporation) is not selected before receiving the rental request, but is selected based on the rental status in response to the receipt of the rental request. Therefore, since there is no need to assign a unique vehicle to each user in advance, it becomes possible for employees of the corporation to efficiently share multiple vehicles that run on electricity.

[0107] [Item 13] A program that causes a computer having a storage means for storing user information identifying multiple users who are employees of a corporation and vehicle information including the rental status of multiple vehicles that run on electricity to function as each of the means other than the storage means of a vehicle management system described in any one of items 1 to 11.

[0108] According to this embodiment, the vehicle to be rented to the user (employee of the corporation) is not selected before receiving the rental request, but is selected based on the rental status in response to the receipt of the rental request. Therefore, since there is no need to assign a unique vehicle to each user in advance, it becomes possible for employees of the corporation to efficiently share multiple vehicles that run on electricity.

[0109] [Item 14] Item 14. A computer-readable recording medium having the program according to item 13 recorded thereon.

[0110] According to this embodiment, the vehicle to be rented to the user (employee of the corporation) is not selected before receiving the rental request, but is selected based on the rental status in response to the receipt of the rental request. Therefore, since there is no need to assign a unique vehicle to each user in advance, it becomes possible for employees of the corporation to efficiently share multiple vehicles that run on electricity.

[0111] The specific configuration of the software and hardware that implements the various functions described in the above embodiments is not particularly limited. As long as it is technically possible, any software, any hardware, and any combination of any software and any hardware are included in the scope of the above embodiments.

[0112] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention. [Explanation of symbols]

[0113] 100... vehicle management system, 110... corporate facility, 130... charging equipment, 140... power generation equipment, 200... parking lot, 300... vehicle, 400... power control device, 500... vehicle management device, 600... user terminal

Claims

1. A storage means for storing user information identifying a plurality of users who are employees of a corporation, vehicle information including a rental status of a plurality of vehicles that run on electricity, and reservation information including one or more rental reservations each having a scheduled rental time and a scheduled return time, the rental status including a scheduled return time for each of the one or more vehicles currently on loan; an identification means for identifying a first user included in the plurality of users based on the user information; a first receiving means for receiving a loan request including a first scheduled return time from the first user; In response to receiving the loan request, determining the number N of vehicles that are not rented out at a current time based on the rental status; determining a time series change in N from a current time to the first scheduled return time by decreasing N by 1 at each of one or more scheduled rental times corresponding to the one or more rental reservations, incrementing N by 1 at each of one or more scheduled return times corresponding to the one or more rental reservations, and incrementing N by 1 at each of one or more scheduled return times corresponding to the one or more vehicles; determining whether a shortage of vehicles is predicted based on the time series change in N; A determination means; A rental means for executing a rental process of renting a first vehicle of the plurality of vehicles to the first user when it is determined that a shortage of vehicles is not expected, the rental process comprising: selecting the first vehicle from the plurality of vehicles based on the rental status, the first vehicle not having been selected prior to receiving the rental request; updating the rental status to reflect the rental of the first vehicle, the processing including registering the first planned return time in the rental status as a planned return time of the first vehicle; A lending instrument comprising: A vehicle management system comprising:

2. An acquisition means for acquiring a forecast of electricity demand in a facility of the corporation; A determination means for determining a charging schedule for vehicles connected to a charging means provided in the facility of the corporation based on the prediction of the power demand; The vehicle management system according to claim 1, further comprising:

3. The acquisition means acquires a forecast of the amount of power generated by the solar power generation means installed in the facility of the corporation, The determination means determines the charging schedule further based on the prediction of the amount of power generation. The vehicle management system according to claim 2 .

4. The vehicle information includes the charging schedule, a connection status of the plurality of vehicles to the charging means, and a charging amount of the plurality of vehicles.

4. The vehicle management system according to claim 2 or 3.

5. An acquisition means for acquiring a forecast of electricity demand in a facility of the corporation; a control means for controlling the supply of electric power charged in a vehicle connected to a charging means provided in the facility of the corporation to a load provided in the facility of the corporation; A planning means for planning a delivery of vehicles from outside the facility of the corporation to inside the facility of the corporation based on the forecast of the electricity demand; The vehicle management system according to claim 1, further comprising:

6. The vehicle parking facility further includes a parking lot capable of parking at least a portion of the plurality of vehicles at a high density. The vehicle management system according to any one of claims 1 to 5.

7. a second receiving means for receiving a return request from the first user while the first vehicle is being rented; A return means for executing a return process of the first vehicle in response to receiving the return request, the return process including: updating the rental status to reflect the return of the first vehicle. A return means including: The vehicle management system according to any one of claims 1 to 6, further comprising:

8. Each of the one or more rental reservations is accompanied by a user identification information; The vehicle management system includes: a third receiving means for receiving a reservation request including a first scheduled rental time from the first user; A reservation means for executing a reservation process in response to receiving the reservation request, the reservation process comprising: A process of determining whether or not the vehicle can be rented at the first scheduled rental time based on the rental status and the reservation information; adding a rental reservation including identification information of the first user and the first scheduled rental time to the reservation information when it is determined that the vehicle can be rented at the first scheduled rental time; A reservation means including: The vehicle management system according to any one of claims 1 to 7, further comprising:

9. The reservation process includes: When it is determined that the vehicle cannot be rented at the first scheduled rental time, a process of recruiting users to ride-share by canceling rental reservations that conflict with the reservation request among the one or more rental reservations; When an application is received for the ride sharing user recruitment, a process of canceling the rental reservation that conflicts with the reservation request and adding a rental reservation including the identification information of the first user and the first scheduled rental time to the reservation information; Further comprising: The vehicle management system according to claim 8 .

10. The rental status includes identification information of a parking lot where the vehicle is parked without being rented out; each of the one or more rental reservations is accompanied by an identification of a user and an identification of a parking space where the rental is to be made; The vehicle management system includes: a third receiving means for receiving a reservation request from the first user, the reservation request including identification information of a first parking lot where the rental will be performed and a first scheduled rental time; A reservation means for executing a reservation process in response to receiving the reservation request, the reservation process comprising: A process of determining whether or not the vehicle can be rented out at the first parking lot at the first scheduled rental time based on the rental status and the reservation information; When it is determined that the vehicle can be rented out at the first parking lot at the first scheduled rental time, a process of adding a rental reservation including identification information of the first user, identification information of the first parking lot, and the first scheduled rental time to the reservation information; A reservation means including: The vehicle management system according to any one of claims 1 to 7, further comprising:

11. The reservation process includes: When it is determined that the vehicle cannot be rented out at the first parking lot at the first scheduled rental time, a process of recruiting a user who will deliver the vehicle to the first parking lot from a parking lot other than the first parking lot by the first scheduled rental time; When an application is received for a user who delivers the vehicle, a process of adding a rental reservation including identification information of the first user, identification information of the first parking lot, and the first scheduled rental time to the reservation information; Further comprising: The vehicle management system according to claim 10 .

12. The determination means determines that a shortage of vehicles is expected when there is a timing at which N becomes 0 in the change in the time series of N between the current time and the first scheduled return time. The vehicle management system according to any one of claims 1 to 11.

13. A vehicle management method executed by a vehicle management system having a storage means for storing user information identifying a plurality of users who are employees of a corporation, vehicle information including a rental status of a plurality of vehicles that run on electric power, and reservation information including one or more rental reservations each having a scheduled rental time and a scheduled return time, the rental status including the scheduled return time of each of the one or more vehicles currently on loan, the method comprising: an identification step of identifying a first user included in the plurality of users based on the user information; a first receiving step of receiving a loan request including a first scheduled return time from the first user; In response to receiving the loan request, determining the number N of vehicles that are not rented out at a current time based on the rental status; determining a time series change in N from a current time to the first scheduled return time by decreasing N by 1 at each of one or more scheduled rental times corresponding to the one or more rental reservations, incrementing N by 1 at each of one or more scheduled return times corresponding to the one or more rental reservations, and incrementing N by 1 at each of one or more scheduled return times corresponding to the one or more vehicles; determining whether a shortage of vehicles is predicted based on the time series change in N; A judgment process; a lending process for executing a lending process for lending a first vehicle of the plurality of vehicles to the first user when it is determined that a shortage of vehicles is not expected, the lending process including: selecting the first vehicle from the plurality of vehicles based on the rental status, the first vehicle not having been selected prior to receiving the rental request; updating the rental status to reflect the rental of the first vehicle, the processing including registering the first planned return time in the rental status as a planned return time of the first vehicle; A lending process including: A vehicle management method comprising:

14. A program that causes a computer having a storage means to function as each of the means other than the storage means of a vehicle management system described in any one of claims 1 to 12, the storage means storing user information identifying multiple users who are employees of a corporation, vehicle information including the rental status of multiple vehicles that run on electricity, and reservation information including one or more rental reservations each accompanied by a scheduled rental time and a scheduled return time, wherein the rental status includes the scheduled return time of each of the one or more vehicles currently on loan.

15. A computer-readable recording medium having the program according to claim 14 recorded thereon.

Images