JP7440848B2 - Lease vehicle management system and lease vehicle management method - Google Patents

Description

The present invention relates to a leased vehicle management system and a leased vehicle management method that allow employees to appropriately use a company's leased vehicle for personal use.

2. Description of the Related Art Conventionally, a technology is known in which a company leases a vehicle from a leasing company and lends the leased vehicle to an employee for personal use. For example, in Patent Document 1, a company lends a leased vehicle from a leasing company to an employee, automatically determines the classification of public and private expenses based on past usage records, and the leasing company provides the company with a lump sum of expenses. A technology has been disclosed in which a company can charge employees for the cost of personal use.

Patent No. 6277316

However, the technique disclosed in Patent Document 1 may cause problems because employees can use the leased vehicle for personal use without restriction. Specifically, when a company leases a vehicle and allows its employees to use it for personal use, this is considered to be a type of joint use between the company and the individual. When providing services in this shared usage format, users (employees) will be responsible for paying the cost within the amount that does not exceed the allocated amount of vehicle maintenance and management costs (lease fees, parking fees, and insurance fees paid by the company). If the cost is incurred (if the employee does not make a profit through personal use), it is not considered to be a rental business. On the other hand, if the user (employee) incurs costs that exceed the allocated amount of vehicle maintenance and management costs, there is a risk that the business will fall under the rental business.

In other words, even though the company allows employees to use leased vehicles for personal purposes in order to provide employee benefits and reduce vehicle maintenance and management costs, this is considered a rental business. There is a possibility that the purpose of the service will be lost.

In addition, the original purpose of companies leasing vehicles is to use such leased vehicles publicly as company cars. For this reason, it is not reasonable to allow private use of leased vehicles at the cost of hindering public use. Therefore, when allowing employees to use a company's leased vehicles for personal purposes, an important issue is how to allow the employees to use the vehicles appropriately.

The present invention has been made in order to solve the above-mentioned problems of the prior art, and is a lease that allows employees to use a company's leased vehicle for private purposes in an appropriate manner. The purpose is to provide a vehicle management system and a leased vehicle management method.

In order to solve the above problems, the present invention provides a leased vehicle management system that includes a management device that manages vehicle information related to vehicles leased by a predetermined company, and a user terminal of a user belonging to the company . The management device includes storage means for storing vehicle maintenance and management costs of the company associated with the lease of the vehicle and usage fees charged for each private use of the vehicle. a reception means for accepting a private use request including the purpose of private use of the vehicle and designation of the date and time of use from the user terminal; and a storage means when the reception means receives the private use request. The total amount of usage fees for private use of the vehicle for a predetermined period including the date and time of use is calculated based on the usage fee for each private use of the vehicle stored in the memory, and the calculated total amount is stored in the storage. and limiting means for notifying the user terminal that reservation for private use of the vehicle is not possible if the vehicle maintenance and management cost is greater than or equal to the vehicle maintenance and management cost stored in the means, thereby restricting private use of the vehicle. It is characterized by

Further, in the above invention, the present invention is provided with a payment request means for making a payment request to a predetermined payment agency center with a usage fee for private use of the vehicle as the payment request amount, The settlement agency center is characterized in that it includes a transfer processing means for transferring the amount of the usage fee to the bank account of the company once the settlement request has been approved.

Further, in the present invention, in the above invention, the user terminal makes a credit payment request, a debit payment request, or an electronic money payment request for the usage fee of the vehicle to the approval agency center, and the settlement agency center: It is characterized by making a payment request to the corresponding server device according to the payment request type.

Further, the present invention is characterized in that, in the above-mentioned invention, the management device further includes display control means for displaying and controlling the status of public and private use of the vehicle and the reservation status of the vehicle on a predetermined display unit.

Further, in the above invention, the present invention provides a calculation means for calculating the inspection timing of the vehicle based on the actual results of public use and private use of the vehicle, and The present invention is characterized in that the vehicle further includes inspection timing notification means for notifying a predetermined terminal device of the inspection timing of the vehicle.

Further, in the above invention, the present invention further includes an administrator terminal operated by a manager of the company, and the management device receives the request for private use of the vehicle by the reception means . The present invention is characterized in that the user is allowed to use the vehicle for private purposes on the condition that the manager uses a user terminal to permit private use.

The present invention also provides a leased vehicle management method in a leased vehicle management system that includes a management device that manages vehicle information related to vehicles leased by a predetermined company, and a user terminal of a user belonging to the company . The management device stores the vehicle maintenance and management costs of the company associated with the lease of the vehicle and the usage fee charged for each private use of the vehicle in a predetermined storage unit. a storage step in which the management device receives a private use request including specification of the purpose of private use of the vehicle and the date and time of use from the user terminal; When the private use request is accepted, the usage fee for the private use of the vehicle for a predetermined period including the date and time of use, based on the usage fee for each private use of the vehicle stored in the storage unit. calculate the total amount, and if the calculated total amount is greater than the vehicle maintenance and management cost stored in the storage unit, notify the user terminal that reservation for private use of the vehicle is not possible; The present invention is characterized by including a restriction step of restricting private use of the vehicle.

According to the present invention, when allowing an employee to use a company's leased vehicle for personal purposes, it is possible to allow the employee to use the company's leased vehicle appropriately for personal use.

FIG. 1 is an explanatory diagram of an overview of a leased vehicle management system according to a first embodiment. FIG. 2 is a diagram showing the system configuration of the leased vehicle management system according to the first embodiment. FIG. 3 is a diagram showing the configuration of the management device shown in FIG. 2. FIG. 4 is a diagram showing an example of the business hours data, employee data, and parking lot data shown in FIG. 3. FIG. 5 is a diagram showing an example of the vehicle data shown in FIG. 3. FIG. 6 is a diagram showing an example of the fare data, reservation data, and operation data shown in FIG. 3. FIG. 7 is a diagram showing an example of the expense data and billing data shown in FIG. 3. FIG. 8 is a diagram showing the configuration of the administrator terminal shown in FIG. 2. FIG. 9 is a diagram showing the configuration of the user terminal shown in FIG. 2. FIG. 10 is a diagram illustrating an example of employee authority according to the first embodiment. FIG. 11 is a diagram illustrating an example of a business hours setting screen on the administrator terminal according to the first embodiment. FIG. 12 is a diagram illustrating an example of a joint use contract screen on the user terminal according to the first embodiment. FIG. 13 is a diagram showing an example (part 1) of a vehicle reservation screen on the user terminal according to the first embodiment. FIG. 14 is a diagram illustrating an example (part 2) of a vehicle reservation screen on the user terminal according to the first embodiment. FIG. 15 is a diagram illustrating an example of a reservation status confirmation screen on the user terminal according to the first embodiment. FIG. 16 is a diagram illustrating an example of a usage start email screen on the user terminal according to the first embodiment. FIG. 17 is a diagram illustrating an example of a usage termination email screen on the user terminal according to the first embodiment. FIG. 18 is a diagram illustrating an example of a usage fee confirmation screen on the user terminal according to the first embodiment. FIG. 19 is a diagram illustrating an example of a reservation time extension screen on the user terminal according to the first embodiment. FIG. 20 is a diagram illustrating an example of a private usage situation according to the first embodiment. FIG. 21 is a diagram illustrating an example of business operation rates by vehicle according to the first embodiment. FIG. 22 is a diagram illustrating an example of business operation rates by base according to the first embodiment. FIG. 23 is a flowchart showing a processing procedure for vehicle usage reservation in the management device according to the first embodiment. FIG. 24 is a flowchart showing a processing procedure for credit card payment for private usage fees according to the first embodiment. FIG. 25 is an explanatory diagram of an overview of the leased vehicle management system according to the second embodiment. FIG. 26 is a diagram showing the configuration of the management device shown in FIG. 25. FIG. 27 is a diagram showing an example of the operation data shown in FIG. 26. FIG. 28 is a diagram showing an example of the diary data shown in FIG. 26. FIG. 29 is a diagram showing an example of the emergency information data and log data shown in FIG. 26. FIG. 30 is a diagram showing the configuration of the administrator terminal according to the second embodiment. FIG. 31 is a diagram showing the configuration of the user terminal shown in FIG. 25. FIG. 32 is a diagram illustrating an example of an input screen at the time of starting use of the user terminal according to the second embodiment. FIG. 33 is a diagram illustrating an example of an input screen before the end of use on the user terminal according to the second embodiment. FIG. 34 is a diagram illustrating an example of a vehicle inspection schedule screen on the user terminal according to the second embodiment. FIG. 35 is a flowchart showing a processing procedure when using a vehicle in a user terminal according to the second embodiment.

[Embodiment 1]
The leased vehicle management system and leased vehicle management method according to the first embodiment will be described in detail below. In the embodiment described below, a leased vehicle leased by a company will be simply referred to as a "vehicle."

<Overview of leased vehicle management system according to Embodiment 1>
First, an overview of the leased vehicle management system according to the first embodiment will be explained. FIG. 1 is an explanatory diagram for explaining an overview of a leased vehicle management system according to the first embodiment.

In the leased vehicle management system according to the first embodiment, leased vehicles can be used for business purposes and private purposes. For private use, a usage fee will be collected by credit card payment each time the vehicle is used, and usage will be permitted as long as the total monthly usage fee does not exceed the vehicle maintenance and management costs. The burden of charges between legal joint users should not be such that anyone can make a profit, so it is undesirable for a company to require employees to bear charges that exceed the cost of maintaining the vehicle in order to lease a vehicle. It's for a reason.

When reserving a vehicle, employee A checks the available time of vehicle A, which is the vehicle he wishes to use, from the user terminal 30, performs the reservation operation with the purpose of use set as personal use, and the user terminal 30 is connected to the management device. 10 of the reservation details (S1). The management device 10 confirms that the total usage fee for the reservation month is less than or equal to the vehicle maintenance and management cost of car A, approves the reservation, and notifies the user terminal 30 that the reservation has been completed (S2).

After using the vehicle, the user terminal 30 notifies the management device 10 of the end of use through the operation of employee A (S3). The management device 10 calculates the usage fee based on the received usage details and notifies the user terminal 30 (S4).

The user terminal 30 displays the received usage fee and, through the operation of the employee A, notifies the payment agency center 40 of a credit card payment request for the employee A as an individual (S5). The payment agency center 40 performs payment based on the credit card payment request, and transfers the usage fee to the bank account of the company to which employee A belongs on a predetermined date (S6).

In this way, the leased vehicle management system according to the first embodiment can allow employees to use a company's leased vehicle for personal purposes in an appropriate manner.

<System configuration>
Next, the system configuration of the leased vehicle management system according to the first embodiment will be described. FIG. 2 is a diagram showing the system configuration of the leased vehicle management system according to the first embodiment. As shown in FIG. 2, a company that uses leased vehicles is equipped with a management device 10 that manages the operation of the leased vehicles. The management device 10 is communicably connected to an administrator terminal 20, a user terminal 30, and a payment processing center 40 via the Internet.

The management device 10 is a device that manages vehicle reservations, operations, usage fees, and analyzes private usage status. The management device 10 stores information regarding business hours, employees, parking lots, vehicles, and fees received from the administrator terminal 20.

When the management device 10 receives vehicle reservation information or reservation change information from the user terminal 30 or the administrator terminal 20, the management device 10 determines that the vehicle is in a permitted time slot, and that no other reservations have been made. For private use, reservations or reservation changes will be accepted on the condition that the total usage fee for the same month as the date of use is less than the vehicle maintenance and management cost of the vehicle used, and this will be notified to the user terminal 30 or the management. The user terminal 20 is notified. When the management device 10 receives vehicle reservation cancellation information from the user terminal 30 or the manager terminal 20, it cancels the reservation and notifies the user terminal 30 or the manager terminal 20 to that effect.

The management device 10 extracts monthly parking fees, lease fees, and insurance fees for each vehicle and stores them as expense information. When the management device 10 receives the usage start information and usage end information from the user terminal 30, it stores the start date and time, end date and time, usage mileage, etc. as operation information. If the purpose of use of the vehicle in the usage end information is for private use, the management device 10 calculates the usage fee and stores it as billing information.

When the management device 10 receives the analysis instruction from the administrator terminal 20, the management device 10 uses the operation information, expense information, and billing information to calculate the business usage utilization rate of each vehicle, the business usage utilization rate of each base, and the private usage status. etc. and notifies the administrator terminal 20 of the analysis results.

The administrator terminal 20 is a device that manages vehicle reservations, operations, and usage fees, and instructs and displays analysis of private usage status. The administrator terminal 20 receives information regarding business hours, employees, parking lots, vehicles, and fees, and notifies the management device 10 of the information. When the administrator terminal 20 receives information regarding business hours, employees, parking lots, vehicles, and fees from the management device 10, it displays the information.

Upon receiving reservation information, reservation change information, or reservation cancellation information (hereinafter referred to as "reservation-related information"), the administrator terminal 20 notifies the management device 10 of the reservation-related information. When the administrator terminal 20 receives a notification of completion, change, or cancellation of a reservation from the management device 10, it displays the notification.

Upon receiving an instruction to display the registered reservation status (hereinafter referred to as "reservation registration information"), the administrator terminal 20 notifies the management device 10 of an instruction to notify the reservation registration information. When the administrator terminal 20 receives the reservation registration information from the management device 10, it displays the reservation registration information.

When the administrator terminal 20 receives an instruction to analyze the status of vehicle expenses and usage fees, it notifies the management device 10 of the instruction. Upon receiving the analysis result from the management device 10, the administrator terminal 20 displays the analysis result.

The user terminal 30 is a device for reserving a vehicle, notifying operation information, displaying billing information, etc., and requesting credit card payment. The user terminal 30 receives employee information, reservation-related information, usage start information, and usage end information, and notifies the management device 10 of the information. When the user terminal 30 receives a notification of reservation completion, change, or cancellation from the management device 10, it displays the notification.

When the user terminal 30 receives the instruction to display the reservation registration information or the vehicle information, it notifies the management device 10 of the notification instruction of the reservation registration information or the vehicle information. When the user terminal 30 receives the reservation registration information or vehicle information from the management device 10, it displays the reservation registration information or the vehicle information.

When the user terminal 30 receives the billing information from the management device 10, it displays the billing information. The billing information display screen includes a procedure screen for making credit card payments.

Upon receiving the instruction for credit card payment, the user terminal 30 notifies the payment agency center 40 of a request for credit card payment for the amount included in the instruction. When the user terminal 30 receives the result of the credit card payment from the payment agency center 40, the user terminal 30 displays the result of the payment.

The payment agency center 40 is a center that performs credit card payments. When the payment agency center 40 receives a request for credit card payment, it performs credit card payment based on the request. The payment agency center 40 transfers the paid amount to the bank account of the company to which the credit card payment requester belongs on a predetermined date.

<Configuration of management device 10>
Next, the configuration of the management device 10 shown in FIG. 2 will be explained. FIG. 3 is a block diagram showing the configuration of the management device 10 shown in FIG. 2. As shown in FIG. As shown in FIG. 3, the management device 10 includes a display section 11, an input section 12, a communication section 13, a storage section 14, and a control section 15.

The display unit 11 is a display device such as a liquid crystal panel or a display device. The input unit 12 is an input device such as a keyboard or a mouse. The communication unit 13 is an interface unit for data communication with the user terminal 30 and the like via the Internet.

The storage unit 14 is a storage device such as a hard disk device or a nonvolatile memory, and stores business time data 14a, employee data 14b, parking lot data 14c, vehicle data 14d, fee data 14e, reservation data 14f, operation data 14g, and expenses. Data 14h and billing data 14i are stored.

The business hours data 14a is data for setting business hours. The vehicle can be used for private purposes during times other than the business hours set in the business hours data 14a. The employee data 14b is data that associates employee IDs, names, branch names, department names, etc. related to employees.

The parking lot data 14c is data that associates the parking lot name, address, monthly parking lot maintenance cost, etc. regarding the parking lot. The vehicle data 14d is data that associates vehicle information, car share operation, cost, fee, vehicle class, etc. regarding the vehicle. The fee data 14e is data that associates vehicle class, usage fee, fuel fee, etc.

The reservation data 14f is data that associates a reservation number, reservation date and time, user, purpose of use, etc. regarding a vehicle reservation. The operation data 14g is data that associates the reservation number, start date and time, end date and time, used mileage, usage fee, etc. regarding the operation of the vehicle.

The expense data 14h is data that associates the vehicle ID, parking lot fee, lease fee, insurance fee, etc. related to the expenses of the leased vehicle. The billing data 14i is data that associates the vehicle ID, target month, private usage billing, etc. regarding the usage fee for private use.

The control unit 15 is a control unit that performs overall control of the management device 10, and includes a setting management unit 15a, a reservation management unit 15b, a reservation determination unit 15c, an operation management unit 15d, an expense management unit 15e, a billing unit 15f, and an analysis unit 15g. has. In reality, by loading these programs into a CPU (Central Processing Unit) and executing them, the settings management section 15a, reservation management section 15b, reservation judgment section 15c, operation management section 15d, expense management section 15e, and billing section are executed. 15f and the analysis section 15g are caused to execute corresponding processes, respectively.

The setting management section 15a is a processing section that manages setting information such as business hours. The setting management unit 15a stores information regarding business hours, employees, parking lots, vehicles, and fees received from the administrator terminal 20 as business hours data 14a, employee data 14b, parking data 14c, vehicle data 14d, and fee data 14e. to be memorized.

The reservation management section 15b is a processing section that manages the reservation data 14f. When the reservation management section 15b receives vehicle reservation information from the user terminal 30 or the administrator terminal 20, it passes the process to the reservation determination section 15c. When the reservation management unit 15b receives the determination that reservation is possible from the reservation determination unit 15c, it stores the reservation information received from the user terminal 30 or the administrator terminal 20 in the reservation data 14f, and The administrator terminal 20 is notified that the reservation has been completed. When the reservation management section 15b receives the determination that the reservation is not possible from the reservation determination section 15c, it notifies the user terminal 30 or the administrator terminal 20 that the reservation is not possible.

When the reservation management section 15b receives vehicle reservation change information from the user terminal 30 or the administrator terminal 20, it passes the process to the reservation determination section 15c. When the reservation management unit 15b receives the determination that the reservation is possible from the reservation determination unit 15c, the reservation management unit 15b updates the corresponding data in the reservation data 14f with the reservation change information received from the user terminal 30 or the administrator terminal 20, and The administrator terminal 30 or the administrator terminal 20 is notified that the reservation change has been completed. When the reservation management section 15b receives the determination that the reservation is not possible from the reservation determination section 15c, it notifies the user terminal 30 or the administrator terminal 20 that the reservation cannot be changed.

When the reservation management unit 15b receives the vehicle reservation cancellation information from the user terminal 30 or the manager terminal 20, it updates the corresponding data in the reservation data 14f and sends the information to the user terminal 30 or the manager terminal 20. The recipient will be notified that the reservation cancellation has been completed.

When the reservation management unit 15b receives an instruction to notify the reservation data 14f from the user terminal 30 or the administrator terminal 20, it notifies the user terminal 30 or the administrator terminal 20 of the reservation data 14f.

The reservation determination unit 15c is a processing unit that determines whether or not a reservation is possible. The reservation determination unit 15c determines whether the reservation information or reservation change information received from the user terminal 30 or the administrator terminal 20 is in a time slot in which usage is permitted, and if no other reservations have been made, and if the reservation information is private. When using the vehicle, a determination is made as to whether or not a reservation is possible, provided that the total usage fee for the same month as the day of use is less than or equal to the vehicle maintenance and management cost of the vehicle used, and if possible, a notification indicating that the reservation is possible. is passed to the reservation management section 15b, and if it is not possible, a message indicating that the reservation is not possible is passed to the reservation management section 15b.

The operation management section 15d is a processing section that manages the operation data 14g. The operation management unit 15d uses the usage start information and usage end information received from the user terminal 30 to store the start date and time, end date and time, usage mileage, etc. in the operation data 14g. When the operation management section 15d receives usage fee information from the charging section 15f, it stores it in the operation data 14g.

The expense management section 15e is a processing section that manages expense data 14h. The expense management unit 15e uses the vehicle data 14d to extract monthly parking fees, lease fees, and insurance fees for each vehicle, and stores them in the expense data 14h.

The billing unit 15f is a processing unit that calculates usage fees for private use of the vehicle and manages billing data 14i. The billing unit 15f receives usage termination information from the user terminal 30, and if the purpose of use of the vehicle in the usage termination information is for private use, the charging unit 15f uses the vehicle data 14d, the fee data 14e, and the operation data 14g to The usage fee for private use of the vehicle is calculated, and the calculation result is passed to the operation management section 15d as usage fee information.

The analysis unit 15g is a processing unit that analyzes the status of vehicle expenses and usage fees. Upon receiving the analysis instruction from the administrator terminal 20, the analysis unit 15g uses the operation data 14g, expense data 14h, and billing data 14i to determine the business usage utilization rate of each vehicle, business usage utilization rate of each base, and personal information. The management terminal 20 analyzes the usage status, etc., and notifies the administrator terminal 20 of the analysis results.

Next, an example of data stored in the storage unit 14 of the management device 10 shown in FIG. 3 will be described. 4 to 7 are business hours data 14a, employee data 14b, parking lot data 14c, vehicle data 14d, fee data 14e, reservation data 14f, operation data 14g, expense data 14h, and billing data 14i shown in FIG. It is a figure showing an example.

The business hours data 14a shown in FIG. 4(a) associates the business hours "-" with the date "2020/11/01" and the day of the week "Sunday", and the date "2020/11/02". , the business hours "9:00-18:00" are associated with the "Monday" day of the week, and the business hours "9:00-18" are associated with the date "2020/11/03" and the day of the week "Tuesday". :00" is associated.

The employee data 14b shown in FIG. 4(b) includes an email address "abc@xyz.....jp" and a backup email address "def@xyz.....jp" for the employee ID "12345". ”, Name “Tokutoku Taro”, Mobile phone “09012345678”, Office number “1001”, Branch name “Shinjuku Branch”, Branch address “Shinjuku-ku, Tokyo...”, Department code “2010”, Department name “1st ``Sales Department'', title ``Manager'', and authority ``Authority by location'' are associated.

The parking lot data 14c shown in FIG. 4(c) includes the parking lot name "Shinjuku Daiichi Parking Lot", the address "Shinjuku-ku, Tokyo...", the location description "adjacent to the Shinjuku branch", and the garage number. "11" and the monthly parking lot maintenance fee of "20,000 yen" are associated.

Vehicle data 14d shown in FIG. 5 includes vehicle information such as vehicle number "Nerima 00-00", name "vehicle A", grade "S", equipment information "ETC", and car share information for vehicle ID "201". Operational base “Shinjuku Branch”, parking lot “Shinjuku Daiichi Parking Lot”, parking space “11”, operational location “Shinjuku Branch”, key “Shinjuku Branch”, private use day restriction “Excluding weekdays” ”, private usage fee “Class 1”, parking fee as cost/fee “20,000 yen”, lease fee “50,000 yen”, insurance fee “5,000 yen”, private usage upper limit “50,000 yen”, as maintenance registration date "2019/05/01", vehicle inspection expiration date "2022/04/30", inspection notification schedule "2021/04/01", vehicle inspection notification schedule "2022/04/01", lease expiration date " 2022/03/31'', the leasing company ``Lease ABC Co., Ltd.'', the management department ``Shinjuku Branch'', the manager ``Tokyo Jiro'', the vehicle class ``Class 1'', and the engine code ``Gasoline''. There is.

The fee data 14e shown in FIG. 6(a) includes, for the class "Class 1", "550 yen" for weekday nights, "1,650 yen" for 12 hours, "2,200 yen" for 24 hours, and "1,650 yen" for the next day, Gasoline "8 yen/L", HV "5 yen/L" and diesel "6 yen/L" are associated, and for the class "Class 2", weekday night "800 yen", 12 hours "2000 yen", 24 It associates "2,800 yen" for the hour, "2,000 yen" for the next day, "10 yen/L" for gasoline, "7 yen/L" for HV, and "8 yen/L" for diesel.

The reservation data 14f shown in FIG. 6(b) includes reservation date and time "2020/11/01", vehicle ID "201", vehicle number "Nerima 00-00", and user "Patent" for the reservation number "100123". Taro'', employee ID ``12345'', purpose of use ``private use'', business content ``-'', and cancellation date and time ``-'' are associated.

The operation data 14g shown in FIG. 6(c) includes a start date and time "2020/11/08 10:00", an end date and time "2020/11/08 17:00", and a starting mileage for the reservation number "100123". "5000km", end mileage "5100km", usage mileage "100km", and usage fee "3300 yen" are associated.

Expense data 14h shown in FIG. 7(a) includes vehicle ID "201", vehicle number "Nerima 00-00", name "vehicle A", parking lot "Shinjuku Daiichi Parking Lot", and parking space "11". ”, target month “2020/10”, parking lot fee “20,000 yen”, lease fee “50,000 yen”, insurance fee “5,000 yen”, and total amount “75,000 yen” are associated.

The charging data 14i shown in FIG. 7(b) includes a vehicle number "Nerima 00-00", a name "vehicle A", a target month "2020/10", and a personal use charge "35000" for the vehicle ID "201". yen" is associated with it.

<Configuration of administrator terminal 20>
Next, the configuration of the administrator terminal 20 shown in FIG. 2 will be explained. FIG. 8 is a block diagram showing the configuration of the administrator terminal 20 shown in FIG. 2. As shown in FIG. As shown in FIG. 8, the administrator terminal 20 includes a display section 21, an input section 22, a communication section 23, a storage section 24, and a control section 25.

The display unit 21 is a display device such as a liquid crystal panel or a display device. The input unit 22 is an input device such as a keyboard or a mouse. The communication unit 23 is an interface unit for data communication with the management device 10 via the Internet. The storage unit 24 is a storage device such as a hard disk device or a nonvolatile memory, and stores data necessary for the control unit 25.

The control unit 25 is a control unit that performs overall control of the administrator terminal 20, and includes a vehicle information management unit 25a, a parking lot information management unit 25b, an employee information management unit 25c, a charge information management unit 25d, and a reservation information management unit 25e. and an analysis section 25f. Actually, by loading these programs into the CPU and executing them, the vehicle information management section 25a, parking lot information management section 25b, employee information management section 25c, fee information management section 25d, reservation information management section 25e, and The analysis unit 25f is caused to execute the corresponding process.

The vehicle information management section 25a is a processing section that notifies and displays vehicle information. When the vehicle information management section 25a receives the vehicle information from the input section 22, it notifies the management device 10 of the vehicle information. When the vehicle information management unit 25a receives the vehicle information display instruction from the input unit 22, it notifies the management device 10 of a vehicle information notification instruction. When the vehicle information management section 25a receives vehicle information from the management device 10, it displays the vehicle information on the display section 21.

The parking lot information management unit 25b is a processing unit that notifies and displays parking lot information. When the parking lot information management section 25b receives the parking lot information from the input section 22, it notifies the management device 10 of the parking lot information. When the parking lot information management unit 25b receives the parking lot information display instruction from the input unit 22, it notifies the management device 10 of a parking lot information notification instruction. Upon receiving the parking information from the management device 10, the parking information management unit 25b displays the parking information on the display unit 21.

The employee information management unit 25c is a processing unit that notifies and displays employee information. Upon receiving the employee information from the input unit 22, the employee information management unit 25c notifies the management device 10 of the employee information. Upon receiving the employee information display instruction from the input section 22, the employee information management section 25c notifies the management device 10 of an employee information notification instruction. Upon receiving the employee information from the management device 10, the employee information management unit 25c displays the employee information on the display unit 21.

The fee information management unit 25d is a processing unit that notifies and displays fee information. When the fee information management unit 25d receives the fee information from the input unit 22, it notifies the management device 10 of the fee information. When the charge information management unit 25d receives the charge information display instruction from the input unit 22, it notifies the management device 10 of a charge information notification instruction. Upon receiving the fee information from the management device 10, the fee information management section 25d displays the fee information on the display section 21.

The reservation information management section 25e is a processing section that notifies and displays reservation information. When the reservation information management unit 25e receives the reservation related information from the input unit 22, it notifies the management device 10 of the reservation related information. When the reservation information management unit 25e receives a notification of completion, change, or cancellation of a reservation from the management device 10, the reservation information management unit 25e displays the notification on the display unit 21. When the reservation information management section 25e receives the instruction to display the reservation registration information from the input section 22, it notifies the management device 10 of an instruction to notify the reservation registration information. Upon receiving the reservation registration information from the management device 10, the reservation information management section 25e displays the reservation registration information on the display section 21.

The analysis unit 25f is a processing unit that instructs and displays analysis regarding the status of vehicle expenses and usage fees. When the analysis unit 25f receives an instruction to analyze the status of vehicle expenses and usage fees from the input unit 22, it notifies the management device 10 of the instruction. Upon receiving the analysis result from the management device 10, the analysis section 25f displays the analysis result on the display section 21.

<Configuration of user terminal 30>
Next, the configuration of the user terminal 30 shown in FIG. 2 will be explained. FIG. 9 is a block diagram showing the configuration of the user terminal 30 shown in FIG. 2. As shown in FIG. As shown in FIG. 9, the user terminal 30 includes a display operation section 31, a communication section 32, a storage section 33, and a control section 34.

The display operation unit 31 is a display and input device such as a liquid crystal touch panel. The communication unit 32 is an interface unit that connects to the Internet via wireless communication and performs data communication with the management device 10. The storage unit 33 is a storage device such as a nonvolatile memory, and stores data necessary for the control unit 34.

The control unit 34 is a control unit that performs overall control of the user terminal 30, and includes an employee information management unit 34a, a reservation information management unit 34b, an operation information registration unit 34c, a vehicle information display unit 34d, a billing information display unit 34e, and It has a payment control section 34f. In reality, by loading and executing these programs on the CPU, the employee information management section 34a, reservation information management section 34b, operation information registration section 34c, vehicle information display section 34d, billing information display section 34e, and payment This causes the control unit 34f to execute the respective corresponding processes.

The employee information management unit 34a is a processing unit that notifies and displays employee information. Upon receiving the employee information from the display operation unit 31, the employee information management unit 34a notifies the management device 10 of the employee information. Upon receiving the employee information display instruction from the display operation section 31, the employee information management section 34a notifies the management device 10 of an employee information notification instruction. Upon receiving the employee information from the management device 10, the employee information management section 34a displays the employee information on the display operation section 31.

The reservation information management section 34b is a processing section that notifies and displays reservation information and the like. When the reservation information management unit 34b receives the reservation related information from the display operation unit 31, it notifies the management device 10 of the reservation related information. When the reservation information management unit 34b receives a notification of completion, change, or cancellation of a reservation from the management device 10, the reservation information management unit 34b displays the notification on the display operation unit 31. Upon receiving the instruction to display the reservation registration information from the display operation section 31, the reservation information management section 34b notifies the management device 10 of an instruction to notify the reservation registration information. Upon receiving the reservation registration information from the management device 10, the reservation information management section 34b displays the reservation registration information on the display operation section 31.

The operation information registration unit 34c is a processing unit that notifies operation information. When the operation information registration unit 34c receives the usage start information or the usage end information from the display operation unit 31, it notifies the management device 10 of the usage start information or the usage end information.

The vehicle information display section 34d is a processing section that displays vehicle information. When the vehicle information display section 34d receives vehicle information from the management device 10, it displays the vehicle information on the display operation section 31.

The billing information display section 34e is a processing section that displays billing information. When the billing information display unit 34e receives billing information from the management device 10, it displays the billing information on the display operation unit 31. The billing information display screen includes a procedure screen for making credit card payments.

The payment control unit 34f is a processing unit that requests credit card payment. Upon receiving the credit card payment instruction from the display operation unit 31, the payment control unit 34f notifies the payment agency center 40 of a request for credit card payment for the amount included in the instruction. When the payment control unit 34f receives the result of the credit card payment from the payment agency center 40, the payment control unit 34f displays the payment result on the display operation unit 31.

<Employee authority>
Next, an example of employee authority according to the first embodiment will be explained. FIG. 10 is a diagram illustrating an example of employee authority according to the first embodiment. As shown in FIG. 10, employee authority is divided into authority 1 to authority 8.

Authority 1 is the master authority and all authorities are granted. Authority 2 is an account editing authority and can create, edit, and delete accounts. Authority 3 is the authority to view the operating status, and can confirm the operating status and payment status. Authority 4 is the authority to set business hours, and can set business hours.

Authority 5 is authority management authority, and can control in which base an account (employee) has authority 6 to authority 8. Authority 6 is a site-specific authority, and can register, edit, and delete vehicles, change the delivery method, manage non-operational reservations and key boxes, and create, edit, and delete parking lots within the site. Authority 7 is a business usage authority and can be used for business purposes. Authority 8 is a private use authority and can be used for private purposes.

<Setting business hours, etc. on administrator terminal 20>
Next, the setting of business hours on the administrator terminal 20 according to the first embodiment will be explained. FIG. 11 is a diagram showing an example of a business hours setting screen on the administrator terminal 20. As shown in FIG. 11, business hours are set by setting time zones for each day. Specifically, specify the year and month to be set, specify whether or not each day is a business day, and if it is a business day, specify the time zone of business hours.

For example, in October 2020, weekdays are set as business days, and business hours are set as "08:30-18:00". At this time, it is possible to set each day individually, or if the business hours are the same, it is also possible to set multiple days at once.

In addition, by storing business hours in separately created data such as CSV format and reading the data, it is also possible to set the business hours at once on a yearly, monthly, etc. basis.

Similarly, information regarding employees, parking lots, vehicles, and fees can be set individually, or can be set all at once by reading separately created data in CSV format or the like.

<Reservation and use of private use on user terminal 30>
Next, reservation and use of private use in the user terminal 30 according to the first embodiment will be explained. First, if an employee uses a vehicle for personal use, a joint use agreement must be concluded based on the Road Transportation Act.

FIG. 12 is a diagram showing an example of a joint use contract screen on the user terminal 30 according to the first embodiment. When reserving private use of a vehicle for the first time on the user terminal 30, a joint use contract screen shown in FIG. 12 is displayed. FIG. 12(a) is an initial screen of the joint usage agreement screen, and by scrolling the screen, it is possible to display the joint usage agreement in sequence.

FIG. 12(b) is a display screen when the joint usage agreement has been displayed, and at this point, the item "I agree to the use based on the joint usage agreement" can be selected. By selecting this item and tapping "Next," you agree to and conclude the joint use agreement.

Next, vehicle reservation at the user terminal 30 according to the first embodiment will be explained. 13 and 14 are diagrams showing an example of a vehicle reservation screen on the user terminal 30 according to the first embodiment. FIG. 13(a) shows a screen that displays vehicle reservation status.

Specifically, the vehicle name is "Vehicle A" and the vehicle number is "Shinagawa 01-01", the vehicle name is "Vehicle A" and the vehicle number is "Shinagawa 01-02", and the vehicle name is "Vehicle B" and the vehicle number is "Shinagawa 02-01" and the vehicle name is "Vehicle B" and the vehicle number is "Shinagawa 02-02". As of November 1, 2020, any vehicle will be displayed. also indicates that there are no reservations.

Further, FIG. 13(b) shows a screen that displays information about a vehicle when a vehicle whose vehicle name is "vehicle B" and whose vehicle number is "Shinagawa 02-01" is selected.

Specifically, regarding the amount to be paid for personal use, the vehicle class is Class 1, the 12-hour fee is ``1,650 yen,'' the 24-hour fee is ``2,200 yen,'' plus the 1-day fee is ``1,650 yen,'' and the fee is ``1,650 yen'' on weekday nights. It shows that the pack is ``550 yen'' and the fuel cost is ``8 yen/1km.''

Furthermore, both the vehicle pick-up location and key pick-up method are "Shinjuku Branch" and the address is "Shinjuku-ku, Tokyo...". Regarding vehicle maintenance, it also indicates that the next inspection date is "February 27, 2021" and the next vehicle inspection deadline is "February 26, 2022." By tapping the "Reserve" button displayed at the bottom of the screen, you will be taken to the reservation screen for the displayed vehicle.

FIG. 14(a) shows a screen for making a reservation for the selected vehicle. On this screen, enter the start date and time, end date and time, purpose of use, driver, and notes. Specifically, the start is "2020/11/01 10:00", the end is "2020/11/01 16:00", the purpose of use is "business use", the driver is "Patent Taro", and the notes are " Ikebukuro, ABC Co., Ltd., meeting'' is shown. In the case of business use, you can enter the usage details in the notes field.

FIG. 14(b) is a screen that displays input contents when a reservation is input. By displaying this screen, the input contents can be confirmed. Specifically, on "November 1, 2020", if you reserve a vehicle with the vehicle name "Vehicle B" and the vehicle number "Shinagawa 02-01" from "10:00" to "16:00". It shows that the driver is "Tokyo Taro" and the purpose of use is "Ikebukuro, ABC Co., Ltd., meeting." It also shows that the mileage of the reserved vehicle is "10,200 km."

Next, confirmation of the reservation status on the user terminal 30 according to the first embodiment will be explained. FIG. 15 is a diagram showing an example of a reservation status confirmation screen on the user terminal 30 according to the first embodiment. As shown in FIG. 15, the reservation statuses made on the user terminal 30 are displayed in a list format.

Specifically, the vehicle name is "Vehicle A" and the vehicle number is "Shinagawa 01-01" from "2020/10/30 (Friday) 12:00" to "2020/10/30 (Friday) 18:00". 00'', the purpose of use is ``business use'' and the vehicle name is ``Vehicle B'' and the vehicle number is ``Shinagawa 02-01''. " to "2020/11/1 (Sunday) 16:00", the purpose of use is "Business use" and the vehicle name is "Vehicle A" and the vehicle number is "Shinagawa 01-02". between "2020/11/20 (Friday) 18:00" to "2020/11/23 (Monday) 8:30", the purpose of use is "private use", the usage fee is "5500 yen", and the fuel cost. shows a situation where the reservation is made at ``8 yen/1km''.

Next, confirmation of the start of use and end of use and notification of extension of use time in the user terminal 30 according to the first embodiment will be explained.

First, when the reservation start time arrives, the management device 10 notifies the user terminal 30 of a usage start email. FIG. 16 is a diagram showing an example of a usage start email screen on the user terminal 30 according to the first embodiment. This email notifies you of the reservation details and the start time of use.

Specifically, the reservation details include the vehicle name as "Vehicle A", the vehicle number as "Shinagawa 01-01", and the reservation date and time as "10/30 (Friday) 12:00 to 10/30 (Friday) 18:00". ”. It also indicates that the link destination for checking the details of the reservation is "https://abcd...".

Furthermore, when the reservation end time comes, the management device 10 notifies the user terminal 30 of a usage end e-mail. FIG. 17 is a diagram showing an example of a usage termination email screen on the user terminal 30 according to the first embodiment. This email notifies you of the reservation details and the end time of use.

Specifically, the reservation details include the vehicle name as "Vehicle A", the vehicle number as "Shinagawa 01-01", and the reservation date and time as "10/30 (Friday) 12:00 to 10/30 (Friday) 18:00". ”. It also indicates that the link destination for checking the details of the reservation is "https://abcd...".

Further, in the case of private use, the management device 10 notifies the user terminal 30 of a usage fee confirmation email after the usage is completed. FIG. 18 is a diagram showing an example of a usage fee confirmation screen on the user terminal 30 according to the first embodiment. This email notifies you of the usage fee and urges you to pay by credit card.

Specifically, the vehicle class of the vehicle used is "Class 1" and "Diesel", and the usage fee is "2200 yen" for the hour, "800 yen" for the distance fee, and "3300 yen" for the total. It shows that there is. It also indicates that the link destination for credit card payment is "https://efgh...".

Furthermore, if it becomes necessary to extend the reservation time during use, the user terminal 30 notifies the management device 10 of the extension of the reservation time. Upon receiving the notification, the management device 10 accepts the extension of the reserved time on the condition that the extended time is within the permitted time slot and that no other reservations have been made.

FIG. 19 is a diagram illustrating an example of a reservation time extension screen on the user terminal according to the first embodiment. On this screen, set the extension end date and time for the target vehicle within a range that does not cover the next reservation time.

Specifically, since the next reservation is "10/28 (Wednesday) 15:00~", "2020/10/28 13:00", which is before that time, is set as the extension end date and time. Further, as the total usage charge after the extension, it is shown that the vehicle class is "Class 1", the hourly charge is "2200 yen", and the fuel cost is "8 yen/1km".

<Display of analysis results of vehicle usage status on administrator terminal 20>
Next, the display of the analysis results of the vehicle usage status on the administrator terminal 20 according to the first embodiment will be described. First, upon receiving an instruction to analyze the vehicle usage status, the administrator terminal 20 notifies the management device 10 of the analysis instruction, and displays the analysis result received from the management device 10.

Analysis of vehicle usage includes the following: private usage status, which compares vehicle maintenance and management costs with usage fees for private use, business operation rate by vehicle, which shows the business operation rate of each vehicle, and vehicle operation rate by location. There are business operation rates by location, etc. that indicate the utilization rate.

FIG. 20 is a diagram illustrating an example of a private usage situation according to the first embodiment. As shown in Figure 20, the private usage status is calculated by comparing the vehicle maintenance and management costs, which are expenses, and the private usage fees, which are income, and using the difference between them, the actual vehicle maintenance and management costs are displayed using a graph. are doing.

Specifically, for each month's charges for the Shinjuku branch for one year from June 2018 to May 2019, the bar graph shows vehicle maintenance costs in the negative direction and personal usage charges in the positive direction. There is. Additionally, the difference between vehicle maintenance and management costs and private usage fees is shown in a line graph.

For example, in May 2019, the vehicle maintenance and management cost is -9,500 yen, the total amount for private use is 6,300 yen, and the actual vehicle maintenance and management cost is -3,200 yen. For private use, the cost is less than the vehicle maintenance and management cost, so in May 2019, private use was possible for up to 3,200 yen.

FIG. 21 is a diagram illustrating an example of business operation rates by vehicle according to the first embodiment. As shown in FIG. 21, the business operation rate for each vehicle is shown in a bar graph as the operation rate of the business usage time relative to the total business hours in the month specified by the operation. In addition, the total operating time, which includes business use time and personal use time, is shown numerically.

Specifically, the total business hours in October 2020 was 180 hours, the business use time of the vehicle with the vehicle name "Vehicle A" and the vehicle number "Shinagawa 01-01" was 18 hours, and the operating rate was 10. %, the personal use time is 12 hours and the total operating time is 30 hours, and the business use time of the vehicle with the vehicle name "Vehicle A" and the vehicle number "Shinagawa 01-02" is 43.2 hours, and the operating rate is 24%, personal use time is 8 hours and total operating time is 51.2 hours, and the business use time of the vehicle with the vehicle name "Vehicle B" and vehicle number "Shinagawa 02-01" is 93.6 hours. The operating time is 52%, the personal use time is 12 hours, and the total operating time is 105.6 hours, and the business use time of the vehicle with the vehicle name "Vehicle B" and the vehicle number "Shinagawa 02-02" is 108 hours, the operating rate is 60%, the personal use time is 11 hours, and the total operating time is 119 hours, and the business use time of the vehicle with the vehicle name "Vehicle C" and the vehicle number "Shinagawa 03-01" is 142 hours, the operating rate is 78.9%, the personal use time is 2 hours, and the total operating time is 144 hours.The vehicle name is "Vehicle C" and the vehicle number is "Shinagawa 03-02". The usage time is 144 hours, the operating rate is 80%, the personal usage time is 0 hours, and the total operating time is 144 hours.

FIG. 22 is a diagram illustrating an example of business operation rates by base according to the first embodiment. As shown in FIG. 22, the business operation rate for each location is shown in a bar graph as the operation rate of the business usage time relative to the total business hours in the month specified by the operation.

Specifically, the total business hours in August 2020 was 180 hours, the average vehicle usage time at the base was 72 hours, and the operating rate was 40%, and the Shinjuku branch vehicle usage time was 45 hours. , the occupancy rate is 25%, indicating that the Ikebukuro branch's vehicles are used for 86.4 hours, and the occupancy rate is 48%.

<Processing procedure for vehicle usage reservation in the management device 10 according to the first embodiment>
Next, a processing procedure for vehicle usage reservation in the management device 10 according to the first embodiment will be explained. FIG. 23 is a flowchart showing the processing procedure for vehicle usage reservation in the management device 10 according to the first embodiment.

If the management device 10 receives reservation information from the user terminal 30 or the administrator terminal 20 (step S101; Yes), it determines whether the reservation time included in the reservation information is a reservation available time (step S102). . If the reservation information is for personal use, reservations can be made for time slots other than business hours.

If the reservation time is not a reservation available time (step S102; No), a notification to the effect that reservation is not possible is sent to the user terminal 30 or administrator terminal 20 that received the reservation information (step S108), and the process is continued. end. If the reservation time is a reservation available time (step S102; Yes), it is determined whether the reservation time has already been booked (step S103).

If a reservation has already been made for the reservation time (step S103; Yes), a notification to the effect that the reservation is not possible is sent to the user terminal 30 or administrator terminal 20 that received the reservation information (step S108); Processing ends immediately. If there is no reservation at the reserved time (step S103; No), it is determined whether the reservation information is for private use (step S104).

If the reservation information is for private use (Step S104; Yes) and the total amount of usage fees for the same month as the date of use of the reserved vehicle exceeds the vehicle maintenance and management cost of the reserved vehicle (Step S105; No), A notification to the effect that the reservation is not possible is sent to the user terminal 30 or the administrator terminal 20 that received the reservation information (step S108), and the process is immediately terminated.

The reservation information is for business use (Step S104; No), or the reservation information is for private use (Step S104; Yes), and the total amount of usage fees for the same month as the date of use of the vehicle to be reserved is the same as that of the vehicle to be reserved. If it is less than the vehicle maintenance and management cost (step S105; Yes), the reservation is accepted, the reservation information is stored (step S106), and the reservation is completed to the user terminal 30 or administrator terminal 20 that received the reservation information. A notification to that effect is transmitted (step S107), and the process ends.

<Processing procedure for credit card payment for private usage fees according to Embodiment 1>
Next, a processing procedure for credit card payment for private usage fees according to the first embodiment will be explained. FIG. 24 is a flowchart showing a processing procedure for credit card payment for private usage fees according to the first embodiment.

If the use of the vehicle has ended (step S201; Yes), the user terminal 30 transmits a usage end notification to the management device 10 (step S202).

When the management device 10 receives the usage termination notification (step S203), it calculates the usage fee for private use (step S204), and transmits the calculated usage fee to the user terminal 30 (step S205).

When the user terminal 30 receives the usage fee (step S206), it transmits a request for credit card payment to the payment agency center 40 (step S207).

When the payment agency center 40 receives the credit card payment request (step S208), it performs payment processing (step S209), and sends a notification that the payment has been completed to the user terminal 30 (step S210).

When the user terminal 30 receives the payment completion notification (step S211), it displays the payment completion notification (step S212). The payment agency center 40 transfers the settled usage fee on a predetermined date to the bank account of the company to which the credit card payment requester belongs (step S213).

In this way, the leased vehicle management system according to the first embodiment can allow employees to use a company's leased vehicle for personal purposes in an appropriate manner.

As described above, in the first embodiment, leased vehicle management includes a management device 10 that manages vehicle information related to vehicles leased by a predetermined company, and user terminals 30 of employees belonging to the organization. In the system, the management device 10 stores restriction information on private use by employees and limits the private use of employees based on the restriction information when a request for private use of a vehicle is received. Since the system is configured to do so, it is possible to allow employees to use the system for appropriate personal purposes.

In addition, in the above-mentioned Embodiment 1, a configuration was described in which the private use of a vehicle is limited so that the total amount of usage fees for the same month as the day of use is less than or equal to the vehicle maintenance and management cost of the target vehicle. is not limited to this, and may be configured to limit the public/private use of the vehicle to a predetermined public/private ratio between business use and private use.

In addition, in the first embodiment described above, a configuration was described in which the private use of a vehicle is limited so that the total amount of usage fees for the same month as the day of use is less than the vehicle maintenance and management cost of the target vehicle. is not limited to this, and may be configured to be limited to a predetermined usage condition, such as limited to users with a predetermined number of years of service.

In addition, in the first embodiment described above, a configuration is described in which usage fees for private use are settled with a credit card, but the present invention is not limited to this, but can be configured to be settled with debit settlement or electronic money. You can also do that.

In addition, in the first embodiment described above, a configuration was described in which the private use of a vehicle is limited so that the total amount of usage fees for the same month as the day of use is less than the vehicle maintenance and management cost of the target vehicle. is not limited to this, and may be configured to allow the private use request on the condition that the administrator terminal 20 approves the private use when the private use request is received.

[Embodiment 2]
Incidentally, in the first embodiment described above, vehicle information such as vehicle inspection is displayed on the reservation screen of the user terminal 30. It is also possible to calculate the inspection timing based on the above information and notify the user of the calculated inspection timing. In addition, by inputting daily reports at the start and end of use, it automatically generates an operation log, notifies emergency information to respond to accidents during use, or outputs log information so that business status can be audited. It can also be configured like this. In Embodiment 2, a configuration will be described that notifies inspection timing calculated based on vehicle usage history, automatically generates a driving log, notifies emergency information, and outputs log information.

<Overview of leased vehicle management system according to Embodiment 2>
First, an overview of the leased vehicle management system according to the second embodiment will be explained. FIG. 25 is an explanatory diagram for explaining an overview of the leased vehicle management system according to the second embodiment.

First, at the start of use, employee A inputs a daily report before departure into the user terminal 300 and notifies the management device 100 (S11). When the use ends, the daily report before the end is input into the user terminal 300 and is notified to the management device 100 (S12). The management device 100 automatically generates an operation log based on the daily reports before departure and before completion (S13).

Furthermore, if a trouble such as a vehicle accident occurs during use, employee B inputs emergency information into the user terminal 300 and notifies the management device 100 (S14).

Furthermore, before the vehicle inspection, the management device 100 calculates the inspection timing based on the usage history of the vehicle (S15), and notifies the user terminal 300 of the calculated inspection timing (S16). Furthermore, the management device 100 receives an operation from the administrator and outputs log information (S17).

In this way, the leased vehicle management system according to the second embodiment notifies the inspection period calculated based on the usage history of the vehicle, automatically generates the operation log, notifies the emergency information, and outputs the log information. Vehicles can be used efficiently.

<Configuration of management device 100>
Next, the configuration of the management device 100 shown in FIG. 25 will be explained. FIG. 26 is a block diagram showing the configuration of management device 100 shown in FIG. 25. Note that descriptions of functional units similar to those of the management device 10 shown in FIG. 3 will be omitted.

As shown in FIG. 26, the management device 100 includes a display section 11, an input section 12, a communication section 13, a storage section 110, and a control section 120.

The storage unit 110 is a storage device such as a hard disk drive or non-volatile memory, and stores business time data 14a, employee data 14b, parking lot data 14c, vehicle data 14d, fee data 14e, reservation data 14f, operation data 111, and a logbook. Data 112, expense data 14h, billing data 14i, emergency information data 113, and log data 114 are stored.

The operation data 111 is data that associates a reservation number, start date and time, end date and time, used mileage, amount of refueling, accidents, scratches, defects, usage fees, etc. regarding the operation of a vehicle. The logbook data 112 is data that associates the vehicle ID, vehicle number, user name, start date and time of use, end date and time of use, mileage, amount of fuel, daily inspection, health condition, drinking status, etc. related to the operation log.

The emergency information data 113 is data in which vehicle ID, vehicle number, user name, emergency information content, scheduled end date and time of use, etc. related to emergency information at the time of use are associated with each other. The log data 114 is data that associates the date and time, user name, action, notes, etc. regarding audit materials by the administrator.

The control unit 120 is a control unit that performs overall control of the management device 100, and includes a setting management unit 15a, a reservation management unit 15b, a reservation determination unit 15c, an operation management unit 121, an expense management unit 15e, a billing unit 15f, and an analysis unit 15g. , a diary management section 122, an inspection timing management section 123, an emergency information management section 124, and a log management section 125. In reality, by loading these programs into the CPU and executing them, the settings management section 15a, reservation management section 15b, reservation judgment section 15c, operation management section 121, expense management section 15e, billing section 15f, and analysis section 15g are executed. , the diary management section 122, the inspection timing management section 123, the emergency information management section 124, and the log management section 125, respectively, to execute corresponding processes.

The operation management unit 121 is a processing unit that manages the operation data 111. The operation management unit 121 uses the usage start information and usage end information received from the user terminal 30 to store the start date and time, end date and time, mileage used, amount of refueling, accidents, scratches, defects, etc. in the operation data 111. . When the operation management section 121 receives usage fee information from the charging section 15f, it stores it in the operation data 111.

The diary management section 122 is a processing section that manages the diary data 112. Using the usage start information and usage end information received from the user terminal 30, the logbook management unit 122 uses the vehicle ID, vehicle number, user name, start date and time of use, end date and time of use, mileage, amount of fuel, and daily inspection. , health condition, drinking status, etc. are stored in the diary data 112. When the logbook management unit 122 receives the instruction to generate a logbook from the administrator terminal 200, it generates an operation logbook using the logbook data 112 and notifies the administrator terminal 200 of the generated operation logbook.

The inspection timing management unit 123 is a processing unit that calculates the inspection timing based on the usage history of the vehicle. The inspection timing management unit 123 accumulates the mileage of the vehicle using the operation data 111, and calculates the inspection timing according to the cumulative result. The inspection timing management unit 123 stores the calculated inspection timing in the vehicle data 14d. The inspection timing management unit 123 notifies the user terminal 300 of the employee who is a joint user of the vehicle and the manager terminal 200 of the inspection timing at a predetermined time before the inspection timing of the vehicle data 14d.

The emergency information management unit 124 is a processing unit that manages the emergency information data 113. When the emergency information management unit 124 receives emergency information from the user terminal 300, it notifies the administrator terminal 200 of the emergency information and stores it in the emergency information data 113.

The log management unit 125 is a processing unit that manages the log data 114. The log management unit 125 stores various requests received from the user terminal 300 and the administrator terminal 200 in the log data 114. Upon receiving the log information output instruction from the administrator terminal 200, the log management unit 125 notifies the administrator terminal 200 of the log data 114.

Next, an example of data stored in the storage unit 110 of the management device 100 shown in FIG. 26 will be described. 27 to 29 are diagrams showing examples of the operation data 111, diary data 112, emergency information data 113, and log data 114 shown in FIG. 26.

The operation data 111 shown in FIG. 27 has a start date and time of "2020/11/08 10:00", an end date and time of "2020/11/08 17:00", and a starting mileage of "5000 km" for the reservation number "100123". , the finished mileage is "5100 km," the used mileage is "100 km," the amount of refueling is "10 L," "no accidents," "no damage," "none" defects, and the usage fee "3500 yen."

The diary data 112 shown in FIG. 28 includes vehicle ID "201", vehicle number "Nerima 00-00", name "vehicle A", and employee ID "12345" for the date and time "2020/11/07 15:20". ”, Name “Patent Taro”, Start date and time of use “2020/11/07 10:10”, End date and time of use “2020/11/07 15:20”, Usage time “310 minutes”, Mileage “100 km”, Refueling By linking the quantity ``10L'', daily inspection ``no abnormalities'', health condition ``no abnormalities'', drinking status ``no abnormalities'', accidents ``no'', scratches ``no'', defects ``no'', and usage fee ``3500 yen''. There is.

The emergency information data 113 shown in FIG. 29(a) includes, for reservation number “100123”, vehicle ID “201”, vehicle number “Nerima 00-00”, name “vehicle A”, employee ID “12345”, The name "Patent Taro", the date and time "2020/11/15 10:20", the content "contact accident, no injuries", and the expected end of use date and time "unknown" are associated.

The log data 114 shown in FIG. 29(b) includes the employee ID "12345", the name "Patent Taro", the action "change car share", and the note "Kyodo" for the date and time "2020/11/01 10:20". Use ID: 1189 Vehicle ID: 201 Classification: Personal use" is associated with the date and time "2020/11/01 10:35", employee ID "15678", name "Jitsugishi Hanako", action "Credit card registration" '', note ``Employee ID: 15678'' is associated, and the date and time ``2020/11/01 10:48'' is associated with employee ID ``10789'', name ``Jiro Ubibun'', action ``Cancel Car Share,'' and note `` Joint use ID: 1321 Vehicle ID: 221 Category: Business use" are associated.

<Configuration of administrator terminal 200>
Next, the configuration of the administrator terminal 200 according to the second embodiment will be explained. FIG. 30 is a block diagram showing the configuration of the administrator terminal 200 according to the second embodiment. Note that descriptions of functional units similar to those of the administrator terminal 20 shown in FIG. 8 will be omitted.

As shown in FIG. 30, the administrator terminal 200 includes a display section 21, an input section 22, a communication section 23, a storage section 24, and a control section 210.

The control unit 210 is a control unit that performs overall control of the administrator terminal 200, and includes a vehicle information management unit 25a, a parking information management unit 25b, an employee information management unit 25c, a charge information management unit 25d, and a reservation information management unit 25e. , an analysis section 25f, and an emergency information management section 211. Actually, by loading these programs into the CPU and executing them, the vehicle information management section 25a, the parking lot information management section 25b, the employee information management section 25c, the charge information management section 25d, the reservation information management section 25e, The analysis unit 25f and the emergency information management unit 211 are caused to execute corresponding processes.

The emergency information management unit 211 is a processing unit that controls the display of emergency information. Upon receiving the emergency information from the management device 100, the emergency information management unit 211 displays the emergency information on the display unit 21. When the emergency information management unit 211 receives an instruction to display emergency information from the input unit 22, it notifies the management device 100 of a request for emergency information.

<Configuration of user terminal 300>
Next, the configuration of the user terminal 300 shown in FIG. 25 will be explained. FIG. 31 is a block diagram showing the configuration of user terminal 300 shown in FIG. 25. Note that descriptions of functional units similar to those of the user terminal 30 shown in FIG. 9 will be omitted.

As shown in FIG. 31, the user terminal 300 includes a display operation section 31, a communication section 32, a storage section 33, and a control section 310.

The control unit 310 is a control unit that performs overall control of the user terminal 300, and includes an employee information management unit 34a, a reservation information management unit 34b, an operation information registration unit 34c, a vehicle information display unit 34d, a billing information display unit 34e, and It has an emergency information registration section 311. In reality, by loading these programs into the CPU and executing them, the employee information management section 34a, reservation information management section 34b, operation information registration section 34c, vehicle information display section 34d, billing information display section 34e, and emergency This causes the information registration unit 311 to execute the corresponding processes.

The emergency information registration unit 311 is a processing unit that notifies emergency information. The emergency information registration unit 311 receives input of emergency information and notifies the management device 100 of the emergency information.

<Daily report and notification of inspection timing>
Next, the daily report and notification of inspection timing will be explained. The daily report is notified from the user terminal 300 to the management device 100 before departure and before the end of vehicle use. FIG. 32 is a diagram showing an example of an input screen at the time of starting use of the user terminal 300 according to the second embodiment. As shown in FIG. 32, before departure, the daily inspection and safety confirmation of the vehicle are input and notified to the management device 100.

Specifically, the daily inspection items include ``brake fluid level,'' ``cooling water level,'' ``engine oil level,'' ``battery fluid level,'' ``window washer fluid level,'' and ``lights. ``Lighting/flashing'', ``Cracks or damage to tires'', ``Tire air pressure'', ``Tire tread depth'', ``Engine running condition, abnormal noises'', ``Window washer fluid injection status'', ``Wiper wiping ability," "how much to leave the brake on and how effective it is," "how much to apply (depress) on the parking brake," and "the deceleration and acceleration status of the engine." In addition, as a safety check, we will check your health condition and alcohol consumption.

FIG. 33 is a diagram showing an example of an input screen before the end of use on the user terminal 300 according to the second embodiment. As shown in FIG. 33, before the end, the mileage, amount of refueling, vehicle status, and usage fee are notified.

Specifically, the distance traveled before departure (for example, 100 km), the distance traveled before the end (for example, 200 km), the amount of refueling when refueling (for example, 10 liters), and the occurrence of accidents, scratches, and vehicle malfunctions. Check availability and usage fees.

In addition, the management device 100 notifies the user terminal 300 of the inspection timing calculated based on the usage history of the vehicle. FIG. 34 is a diagram showing an example of a vehicle inspection schedule screen on the user terminal 300 according to the second embodiment.

As shown in FIG. 34, vehicle inspection information and maintenance information for a vehicle whose vehicle name is "Vehicle A" and whose vehicle number is "Shinagawa 01-01" are notified. Specifically, the vehicle inspection information indicates that the registration date is "2019/05/01", the vehicle inspection expiration date is "2022/04/30", and the next vehicle inspection deadline is "2021/04/01". It shows that the next maintenance inspection date is "2021/04/01", the lease expiration date is "2021/04/01", and the leasing company is "Lease ABC Co., Ltd.".

<Processing procedure when using a vehicle in the user terminal 300 according to the second embodiment>
Next, a processing procedure when using a vehicle in the user terminal 300 according to the second embodiment will be described. FIG. 35 is a flowchart showing a processing procedure when using a vehicle in the user terminal 300 according to the second embodiment.

First, if the usage start email is received (step S301; Yes), a report on the day before departure is input and sent (step S302). If a usage time extension application has not been sent after starting use (step S303; No), the process moves to step S306.

If an application for extension of usage time is sent (step S303; Yes) and an e-mail as a result of the extension application is received (step S304; Yes), the received e-mail as a result of the extension application is displayed (step S305).

Next, if the usage termination email is received (step S306; Yes), a report on the day before termination is input and sent (step S307). If the confirmation email after the end of use is received (step S308; Yes), the received confirmation email after the end of use is displayed (step S309), and the process ends.

In this way, the leased vehicle management system according to the second embodiment notifies the inspection period calculated based on the usage history of the vehicle, automatically generates the operation log, notifies the emergency information, and outputs the log information. Vehicles can be used efficiently.

Note that each of the configurations illustrated in the above embodiments is a functional schematic, and does not necessarily have to be physically configured as illustrated. In other words, the form of dispersion/integration of each device is not limited to the one shown in the diagram, but all or part of it can be functionally or physically distributed/integrated in arbitrary units depending on various loads and usage conditions. Can be configured.

The leased vehicle management system and leased vehicle management method according to the present invention are suitable for efficient use of leased vehicles and for reducing the burden of payment operations.

10 Management device 11 Display unit 12 Input unit 13 Communication unit 14 Storage unit 14a Business hours data 14b Employee data 14c Parking lot data 14d Vehicle data 14e Fares data 14f Reservation data 14g Operation data 14h Expenses data 14i Billing data 15 Control unit 15a Settings Management Department 15b Reservation Management Department 15c Reservation Judgment Department 15d Operation Management Department 15e Expense Management Department 15f Billing Department 15g Analysis Department 20 Administrator Terminal 21 Display Department 22 Input Department 23 Communication Department 24 Storage Department 25 Control Department 25a Vehicle Information Management Department 25b Parking Department Car lot information management department 25c Employee information management department 25d Fares information management department 25e Reservation information management department 25f Analysis department 30 User terminal 31 Display operation section 32 Communication department 33 Storage section 34 Control section 34a Employee information management department 34b Reservation information management Section 34c Operation information registration section 34d Vehicle information display section 34e Billing information display section 34f Payment control section 40 Payment agency center 100 Management device 110 Storage section 111 Operation data 112 Logbook data 113 Emergency information data 114 Log data 120 Control section 121 Operation management section 122 Logbook Management Department 123 Inspection Timing Management Department 124 Emergency Information Management Department 125 Log Management Department 200 Administrator Terminal 210 Control Department 211 Emergency Information Management Department 300 User Terminal 310 Control Department 311 Emergency Information Registration Department

Claims (7)

A leased vehicle management system comprising a management device that manages vehicle information related to a vehicle leased by a predetermined company, and a user terminal of a user belonging to the company ,
The management device includes:
storage means for storing vehicle maintenance and management costs of the company associated with the lease of the vehicle and usage fees charged for each private use of the vehicle;
reception means for receiving a private use request from the user terminal , including specification of the purpose of private use of the vehicle and the date and time of use ;
When the reception means accepts the private use request , based on the usage fee for each private use of the vehicle stored in the storage means, the private use of the vehicle for a predetermined period including the date and time of use is determined. Calculate the total amount of usage fees, and if the calculated total amount is greater than the vehicle maintenance and management cost stored in the storage means, notify the user terminal that reservations for private use of the vehicle are not possible. A leased vehicle management system comprising: a restriction means for notifying and restricting private use of the vehicle. The user terminal is
comprising a payment requesting means for making a payment request to a predetermined payment agency center with the usage fee for private use of the vehicle as the payment request amount;
The settlement agency center is
The leased vehicle management system according to claim 1 , further comprising a transfer processing means for transferring the amount of the usage fee to the bank account of the company once the settlement request has been approved. The user terminal is
Make a credit payment request, debit payment request, or electronic money payment request for the usage fee of the vehicle to the settlement agency center,
The settlement agency center is
The leased vehicle management system according to claim 2, wherein a payment request is made to a corresponding server device according to a payment request type. The management device includes:
Lease vehicle management according to any one of claims 1 to 3 , further comprising display control means for displaying and controlling the public and private usage status of the vehicle and the reservation status of the vehicle on a predetermined display unit. system. The management device includes:
Calculation means for calculating the inspection timing of the vehicle based on the actual results of public use and private use of the vehicle;
Lease vehicle management according to any one of claims 1 to 4, further comprising: inspection time notification means for notifying a predetermined terminal device of the inspection time of the vehicle calculated by the calculation means. system. further comprising an administrator terminal operated by an administrator of the company,
The management device includes:
When a request for private use of the vehicle is received by the reception means, the user is permitted to use the vehicle for private use, subject to permission for private use by the administrator using the administrator terminal. The leased vehicle management system according to any one of claims 1 to 5 . A leased vehicle management method in a leased vehicle management system comprising a management device that manages vehicle information related to a vehicle leased by a predetermined company, and a user terminal of a user belonging to the company , the method comprising:
The management device stores, in a predetermined storage unit, a vehicle maintenance and management cost of the company associated with the lease of the vehicle and a usage fee charged for each private use of the vehicle. The memory process of
a reception step in which the management device receives a private use request from the user terminal including designation of the purpose of private use of the vehicle and the date and time of use ;
When the management device receives the private use request in the reception step, the management device receives the request for private use during the predetermined period including the date and time of use based on the usage fee for each private use of the vehicle stored in the storage unit. Calculate the total amount of usage fees for private use of the vehicle, and if the calculated total amount is equal to or greater than the vehicle maintenance and management cost stored in the storage unit, it is determined that reservation for private use of the vehicle is not possible. and a restriction step of notifying the user terminal to restrict private use of the vehicle.

Images