JP6869822B2 - Car sharing management system - Google Patents

Description

The present invention relates to a car sharing management system capable of efficiently performing a car sharing business.

In the car sharing business, various users with different driving skills and driving modes use a common vehicle for various purposes. Therefore, before renting the vehicle so that the user can always rent the vehicle in good condition, that is, in the free time from when the vehicle is returned to the predetermined parking space until it is used for the next use. , It is preferable that the maintenance of the vehicle is performed. Regarding this point, conventionally, there has been known a system in which maintenance information is stored in a history format in a server accessible to the dealer, and the dealer side refers to the information to perform maintenance of the vehicle as appropriate (). For example, see Patent Document 1).

Japanese Unexamined Patent Publication No. 2008-117076

However, since the system described in Patent Document 1 does not perform maintenance every time the vehicle is returned to the parking space, it is not always possible to rent the vehicle to the next user who uses the vehicle in a normal state. , May damage the user.

On the other hand, when maintenance is performed every time a vehicle is returned to the parking space, in order to carry out the car sharing business efficiently, instead of starting accepting vehicle reservations after the maintenance is completed, predetermined maintenance is performed in advance. It is preferable to secure time and accept vehicle reservations after the scheduled maintenance end time at any time. However, since the actual maintenance time is determined according to the individual vehicle condition, the maintenance end time may exceed the scheduled maintenance end time, and in that case, it may interfere with the handling of reservations that have already been accepted. ..

One aspect of the present invention is a plurality of business entities scattered within a geographically predetermined range, each of which owns a shared vehicle used for car sharing, and a maintenance base and a shared vehicle that perform maintenance of the shared vehicle. It is a car sharing management system that manages the car sharing business conducted under an organizational system that includes multiple business entities that have stations where is parked, and has a reservation reception department that accepts applications for reservations for shared vehicles and reservations. The planning department that creates a reserved vehicle usage plan including the maintenance plan that is executed before the reserved vehicle usage start time accepted by the reception department, and the vehicle status of the reserved vehicle before the maintenance of the reserved vehicle ends. Necessity of alternative vehicle based on the maintenance information acquisition department that acquires information on the scheduled maintenance time according to the response, the information on the scheduled maintenance time acquired by the maintenance information acquisition department, and the usage plan created by the planning department. When the substitute vehicle necessity determination unit and the substitute vehicle necessity determination unit determine that a substitute vehicle is necessary, the vehicle search unit searches for a substitute vehicle from a plurality of shared vehicles owned by a plurality of business entities. And a plan change unit that changes the usage plan by using the alternative vehicle searched by the vehicle search unit as a new reserved vehicle. The planning department creates a maintenance plan based on a predetermined standard maintenance time including the travel time from the maintenance base to the station after the maintenance of the reserved vehicle, and the maintenance information acquisition department maintains after the maintenance of the reserved vehicle starts. Acquire the scheduled maintenance time entered by the workers at the site.

According to the present invention, even if the maintenance time of the reserved vehicle is extended, the car sharing business can be efficiently performed without hindering the reservation response by arranging the alternative vehicle.

The image diagram which shows the organizational system to which the car sharing management system which concerns on embodiment of this invention is applied. The figure which shows the geographical arrangement of the plurality of enterprises of FIG. The block diagram which shows the whole structure of the car sharing management system which concerns on embodiment of this invention. The figure which shows an example of the use plan of the vehicle used for a car sharing business. FIG. 3 is a flowchart showing an example of processing executed by the calculation unit of the server device of FIG. The figure explaining an example of the main operation of the car sharing management system which concerns on embodiment of this invention. The figure explaining another example of the main operation of the car sharing management system which concerns on embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described with reference to FIGS. 1 to 6B. The car rental business rents vehicles face-to-face, while the car sharing business rents unmanned vehicles using pre-registered IC cards. The car-sharing management system according to the embodiment of the present invention is a system suitable for carrying out a car-sharing business mainly by a business entity such as a dealer (cardilla) that sells and maintains (inspects and maintains) vehicles. It is configured as. Vehicles (shared vehicles) owned by the business entity and used for the car sharing business are parked on the premises of the business entity. The place where such a shared vehicle is parked is called a station.

On the premises of the business entity, not only stations but also maintenance bases where workers belonging to the business entity maintain shared vehicles will be set up. The stations are provided, for example, on the same site as the maintenance base, or on the site adjacent to each other across a fence or a road. If the station is provided in the vicinity of the maintenance base, such as when the distance from the maintenance base to the station is within a predetermined distance, the station may be provided in a site other than the same or adjacent site as the maintenance base.

When the user uses the shared vehicle, the station becomes the departure and return point of the shared vehicle. Every time the shared vehicle is returned to the station, for example, the shared vehicle is transferred to the maintenance base by a worker, and maintenance is performed at the maintenance base. That is, in the car sharing business, various users with different driving techniques and driving modes drive a shared vehicle for various purposes. Therefore, in order to always rent the shared vehicle to the user in good condition, maintenance of the shared vehicle is performed before renting the shared vehicle, that is, between the time when the shared vehicle is returned to the station and the time when the shared vehicle is rented to the next reservation person. ..

FIG. 1 is an image diagram showing an organizational system to which the car sharing management system according to the embodiment of the present invention is applied. As shown in FIG. 1, the organizational structure is classified into a first layer at the highest level, a second layer below the first layer, and a third layer below the second layer. The third layer is composed of a plurality of business entities (for example, A store, B store, C store, and D store, which are vehicle dealers).

FIG. 2 is a diagram showing the geographical arrangement of a plurality of business units A to D stores. As shown in FIG. 2, among the plurality of business units A to D stores, the A store and the B store are scattered in the first range AR1, and the C store and the D store are adjacent to the first range AR1. Dotted within the second range AR2. The number of third-tier business entities included in each range AR1 and AR2 may be one or three or more. In FIG. 2, the first range AR1 and the second range AR2 are shown as adjacent ranges, but they may be separated from each other. In FIG. 2, C1 to C7 are shared vehicles of the same vehicle type, store A has vehicles C1 to C3, store B has vehicle C4, store C has vehicles C5 and C6, and store D has vehicle C7. I own each.

As shown in FIG. 1, the second level is a plurality of business units in the third level, A store, B store, C store, and D store (for example, company E and F, which are vehicle sales companies). Company). Company E manages stores A and B scattered in the first range AR1, and company F manages stores C and D scattered in the second range AR2. The number of business entities in the second layer may be one or three or more. Company E and Company F are located in, for example, the first range AR1 and the second range AR2, respectively.

The first layer is composed of a plurality of business entities E and F companies (for example, company G, which is a vehicle manufacturer) that manages the business. Company G has a call center that responds to telephone calls, emails, etc. from users, for example. The relationship between Company G and Company E and Company F corresponds to, for example, the relationship between a parent company and a subsidiary. The number of business entities in the first layer may be two or more. There may be additional entities above the first level.

Under such an organizational system, in the present embodiment, the vehicles C1 to C7 owned by the third-tier business entity are used as shared vehicles for the car sharing business. The shared vehicle may include not only a vehicle dedicated to car sharing used only for the car sharing business but also a vehicle used for other purposes such as a test drive. Not only the third-tier business entity but also a part of the vehicles owned by the second-tier or first-tier business entity can be used as a shared vehicle for the car sharing business.

FIG. 3 is a block diagram showing the overall configuration of the car sharing management system 100 according to the embodiment of the present invention. As shown in FIG. 3, the car-sharing management system 100 includes a business entity terminal 1 provided in each business entity of the first to third layers and an in-vehicle vehicle provided in vehicles C1 to C7 owned by each business entity. It has a terminal 2, a user terminal 3 owned by a customer (user) who uses the vehicles C1 to C7, and a server device 4.

The business entity terminal 1, the in-vehicle terminal 2, the user terminal 3, and the server device 4 are connected to a communication network 5 such as a wireless communication network, an Internet network, and a telephone line network. In FIG. 3, for convenience, one business entity terminal 1, one in-vehicle terminal 2, and one user terminal 3 are shown, but a plurality of these terminals 1 to 3 are actually provided. Further, although a single server device 4 is shown in FIG. 3, the functions shown in the server device 4 of FIG. 3 may be distributed to a plurality of server devices. At least a part of the communication path may be wired instead of wireless.

The business entity terminal 1 includes a personal computer provided in each business entity and a mobile wireless terminal operated by an employee (employee) of each business entity. The business entity terminal 1 has a communication unit 11, an input / output unit 12, a calculation unit 13, and a storage unit 14.

The communication unit 11 is configured to enable wireless communication with the server device 4 via the communication network 5. The communication unit 11 transmits the usage information and maintenance information of the vehicles C1 to C7 to the server device 4 together with the employee ID that identifies the employee of the business entity.

The input / output unit 12 is a so-called human interface (HMI), and has a keyboard, a mouse, a monitor, a touch panel, a printer, and the like that can be operated by a user. An employee (employee) of each business entity can input various information of vehicles C1 to C7 via the input / output unit 12, and can acquire information on arrangement of a substitute vehicle. The maintenance information entered by the employee includes the time expected to be required until the maintenance is completed (scheduled maintenance time). The scheduled maintenance time is the time determined by the employee himself / herself after the employee (worker) actually starts the maintenance of the vehicles C1 to C7 returned to the station at the maintenance base, and the server is based on the scheduled maintenance time. The device 4 determines the necessity of a substitute vehicle. Instead of the scheduled maintenance time, the scheduled maintenance end time may be used as the maintenance information input by the employee.

The calculation unit 13 has a CPU (processor), a signal input via the input / output unit 12, a signal received from the outside of the business entity terminal 1 via the communication unit 11, and data stored in the storage unit 14. A predetermined process is executed based on the above, and a control signal is output to the communication unit 11, the input / output unit 12, and the storage unit 14. By the processing in the calculation unit 13, whether or not the vehicle owned by the business entity to which the company belongs is used as a substitute vehicle is notified to the employee via the input / output unit 12 (for example, a monitor).

The calculation unit 13 has a vehicle information acquisition unit 13a that acquires various vehicle information (vehicle information) from the server device 4. The vehicle information to be acquired is information on vehicles belonging to each business entity and information on vehicles belonging to business entities lower than the business entity. For example, the third-tier business entity A store can acquire information on the vehicles C1 to C3 belonging to the A store, and the second-tier business entity E company can acquire the information of the vehicles C1 to C4 belonging to the A store and the B store. The information can be acquired, and the first-level business entity company G can acquire the information of the vehicles C1 to C7 belonging to the stores A to D. The calculation unit 13 can output (for example, display) the vehicle information to the input / output unit 12 in a manner that can be recognized by the employee.

The storage unit 14 has a volatile or non-volatile memory (not shown). Various programs executed by the arithmetic unit 13 and various data are stored in the storage unit 14.

The in-vehicle terminal 2 includes, for example, an in-vehicle navigation device. The in-vehicle terminal 2 includes a communication unit 21, an input / output unit 22, a lock mechanism 23, a sensor group 24, a calculation unit 25, and a storage unit 26.

The communication unit 21 is configured to enable wireless communication with the server device 4 via the communication network 5. The communication unit 21 transmits a signal indicating the current position information of the vehicles C1 to C7 and a signal from the sensor group 24 to the server device 4 at predetermined time intervals together with the vehicle ID that identifies the vehicles C1 to C7.

The input / output unit 22 has various switches, buttons, microphones, speakers, monitors, and the like that can be operated by the user. In addition, the input / output unit 22 has a card reader 22a that reads user information from the authentication card that the user has. As the authentication card, for example, a driver's license (IC card license) in which an integrated circuit (IC) is incorporated and personal information of a user is stored is used. The card reader 22a is provided at a predetermined portion (for example, below the rear window) of the vehicles C1 to C7 so that the authentication card approached from the outside of the vehicle can be recognized.

The lock mechanism 23 has a door lock actuator (for example, an electric motor), and the door lock is unlocked or locked by driving the door lock actuator. That is, the door lock actuator unlocks the door lock when the unlocking signal is output from the calculation unit 25, and locks the door lock when the lock signal is output.

The sensor group 24 is mounted on each vehicle C1 to C7 and includes various sensors for detecting the vehicle state. For example, a GPS sensor that detects the position of the vehicle, a vehicle speed sensor that detects the vehicle speed, a gyro sensor that detects the angular speed of the vehicle, an acceleration sensor that detects the acceleration acting on the vehicle, a mileage sensor that detects the mileage, and the amount of remaining fuel. The sensor group 24 includes a residual fuel detection sensor for detecting the remaining battery capacity, a residual battery capacity detecting sensor for detecting the remaining battery capacity, and the like.

The calculation unit 25 has a CPU, and the signal input via the input / output unit 22, the signal detected by the sensor group 24, the signal received from the outside of the vehicle-mounted terminal via the communication unit 21, and the storage unit 26 A predetermined process is executed based on the stored data, and a control signal is output to the actuator, the input / output unit 22, and the storage unit 26 of each unit of the vehicles C1 to C7. The calculation unit 25 further outputs a control signal to the communication unit 21 to control transmission / reception of the signal between the vehicle-mounted terminal 2 and the server device 4. For example, the calculation unit 25 transmits the user information read via the card reader 22a to the server device 4 via the communication unit 21. The server device 4 determines whether or not there is reservation information corresponding to the received user information, transmits an unlock command to the calculation unit 25 if there is the corresponding reservation information, and transmits a lock signal if there is no corresponding reservation information. .. When the calculation unit 25 receives the unlock command, it outputs the unlock signal, and when it receives the lock command, it outputs the lock signal to the door lock actuator.

The storage unit 26 has a volatile or non-volatile memory (not shown). The storage unit 26 stores various programs executed by the calculation unit 25 and various data.

The user terminal 3 is composed of a personal computer operated by the user, a mobile wireless terminal represented by a smartphone, and the like. The user terminal 3 has a communication unit 31, an input / output unit 32, a calculation unit 33, and a storage unit 34.

The communication unit 31 is configured to enable wireless communication with the server device 4 via the communication network 5. The communication unit 31 transmits a signal for instructing reservation application or cancellation of vehicles C1 to C7 to the server device 4 together with a user ID that identifies the user.

The input / output unit 32 includes, for example, a keyboard, a mouse, a monitor, a touch panel, and the like. The user can input user information and commands such as application, change, and cancellation of vehicle reservation via the input / output unit 32. The user information includes the user's address, name, contact information, driver's license number, information necessary for payment (for example, credit card number) and the like. After entering the user information and registering as a member, the user can use the shared vehicle.

When applying for a vehicle reservation, the user commands the vehicle type, the station to be used, and the vehicle usage date and time (use start date and time and use end date and time). At this time, the server device 4 (vehicle search unit 435) searches for a reservable vehicle that satisfies any or all of the commanded vehicle type, station, usage date and time, and uses the user terminal to search for the searched vehicle information. Send to 3. This vehicle information is displayed on the input / output unit 32. When the user selects a desired vehicle from the displayed vehicles via the input / output unit 32, or when the user accepts the displayed vehicle, the vehicle reservation is confirmed.

The calculation unit 33 has a CPU, and is determined based on a signal input via the input / output unit 32, a signal received from the outside of the user terminal 3 via the communication unit 31, and data stored in the storage unit 34. Is executed, and a control signal is output to the communication unit 31, the input / output unit 32, and the storage unit 34. By the processing in the calculation unit 33, the user can change or confirm the reserved vehicle via the input / output unit 32 (monitor or the like).

The storage unit 34 has a volatile or non-volatile memory (not shown). The storage unit 34 stores various programs executed by the calculation unit 33 and various data.

The server device 4 is provided in, for example, the first-tier business entity G. The server device 4 can also be configured by using the virtual server function on the cloud. The server device 4 has a communication unit 41, an input / output unit 42, a calculation unit 43, and a storage unit 44.

The communication unit 41 is configured to enable wireless communication with the business entity terminal 1, the in-vehicle terminal 2, and the user terminal 3 via the communication network 5, respectively. The input / output unit 42 includes, for example, a keyboard, a mouse, a monitor, a touch panel, and the like. The calculation unit 43 has a CPU, and is determined based on a signal input via the input / output unit 42, a signal received from the outside of the server device 4 via the communication unit 41, and data stored in the storage unit 44. Is executed, and the control signal is output to the input / output unit 42 and the storage unit 44. The functional configuration of the calculation unit 43 will be described later.

The storage unit 44 has a volatile or non-volatile memory (not shown). The storage unit 44 stores various programs executed by the calculation unit 43 and various data. The storage unit 44 has a vehicle database 441, a user database 442, and an employee database 443 as functional configurations of the memory.

The vehicle database 441 is a vehicle that represents the vehicle state and vehicle characteristics such as the business entity to which each vehicle C1 to C7 belongs, the vehicle type, model year, vehicle body number, vehicle number, mileage, maintenance history, and operating rate of each vehicle C1 to C7. The information and the usage plan of each vehicle C1 to C7 are stored. The usage plan includes past, present, and future time-series reservation information for each vehicle C1 to C7, actual maintenance of vehicles C1 to C7 that have already been performed between the reservation information, and current or future execution. Includes planned maintenance plans.

FIG. 4 is a diagram showing an example of a utilization plan for the vehicle C1. In FIG. 4, the user's reservation is incorporated at the time points t0 to t1 (solid line arrow), then the vehicle maintenance plan is incorporated at the time points t1 to t2 (dotted line arrow), and then the time points t3 to t4 (solid line arrow). The user reservation is incorporated again. The usage plan is updated in response to reservation requests, changes, cancellations, maintenance executions, and maintenance plan changes.

The user database 442 contains user information such as a user ID, address, name, contact information, license number, etc. of each user input via the user terminal 3 (input / output unit 32), and vehicle C1 to C7 of each user. Store usage history information, etc.

The employee database 443 stores employee information such as employee ID, address, name, and contact information of each employee. Employee information also includes affiliation information to which business entity each employee belongs to. Employee information can be input only on a specific business entity terminal 1 (for example, a business entity terminal of company G).

The calculation unit 43 has a reservation reception unit 431, a plan creation unit 432, a maintenance information acquisition unit 433, a substitute vehicle necessity determination unit 434, a vehicle search unit 435, and a plan change unit as functional configurations of the processor. It has 436 and an output unit 437.

The reservation reception unit 431 accepts an application for a vehicle use reservation input by the user via the user terminal 3 (input / output unit 32). Specifically, the calculation unit 43 (vehicle search unit 435) lists a list of reservable vehicles that match the reservation conditions input by the user, such as the date and time of use of the vehicle, the vehicle type, and the business entity to be used, from the vehicle database 441. After searching and transmitting to the user terminal 3, the communication unit 41 receives information on the vehicle selected by the user or the vehicle approved by the user from the transmitted vehicle list. The reservation reception unit 431 accepts an application for a usage reservation using this as a reserved vehicle.

The planning unit 432 creates a current and future usage plan of the shared vehicle and registers the usage plan in the vehicle database 441. More specifically, a reservation vehicle usage plan accepted by the reservation reception unit 431 is created and registered in the vehicle database 441. The usage plan includes a usage start date and time and a usage end date and time of the reserved vehicle, and a maintenance plan executed before the usage start date and time. For example, as shown in FIG. 4, the usage plan includes the use start time t3 and the use end time t4 of the vehicle C1 reserved by the user, and the maintenance plan scheduled at the time points t1 to t2 before the time point t3. .. In the present embodiment, immediately after the vehicle C1 is returned to the station, that is, starting from the use end time t1 of the vehicle C1, the planning unit 432 incorporates the maintenance plan. The maintenance plan may be incorporated a predetermined time after the vehicle is returned to the station.

The maintenance plan is created in advance in consideration of the standard maintenance time. That is, the planning unit 432 sets the maintenance start time (scheduled time) as the usage end time t1 of the reserved vehicle, and sets the maintenance end time (scheduled time) as the time t2 when the predetermined standard maintenance time ΔT0 elapses from the maintenance start time (scheduled time). ), Create a maintenance plan. The standard maintenance time ΔT0 includes the actual working time, the traveling time of the vehicle C1 between the station and the maintenance base, and the predetermined preliminary time. The preliminary time is determined in consideration of the fact that the working time varies slightly, and from the viewpoint of improving the utilization efficiency of the vehicle, it is preferable that the preliminary time is short.

Workers at the maintenance base check the actual vehicle condition as soon as possible after the start of vehicle maintenance. Then, the scheduled maintenance time required until the end of maintenance is predicted, and maintenance information such as the scheduled maintenance time or the scheduled maintenance end time is input via the input / output unit 12 of the business entity terminal 1. Instead of inputting the scheduled maintenance time numerically, the worker selects one from a plurality of scheduled maintenance time candidates displayed on the input / output unit 12 (monitor), for example, and thereby sets the scheduled maintenance time. You may enter it. The maintenance information acquisition unit 433 acquires the maintenance information input by the worker via the input / output unit 12 in this way.

When the scheduled maintenance time is equal to or less than the standard maintenance time ΔT0, the worker may omit the input of the scheduled maintenance time. For example, the business entity terminal 1 may transmit information to the server device 4 that the scheduled maintenance time is the standard maintenance time ΔT0 when the scheduled maintenance time is not input by the worker for a predetermined time or more. Alternatively, when the server device 4 does not receive a signal regarding the maintenance time for a predetermined time from the maintenance start time due to no input of the scheduled maintenance time by the worker, for example, the maintenance information acquisition unit 433 performs maintenance by internal processing of the server device 4. Information that the scheduled time is the standard maintenance time ΔT0 may be acquired.

The substitute vehicle necessity determination unit 434 determines the necessity of a substitute vehicle based on the maintenance information acquired by the maintenance information acquisition unit 433 and the usage plan created by the plan creation unit 432. Specifically, the substitute vehicle necessity determination unit 434 determines the necessity of the vehicle according to the scheduled end time of the maintenance and the use start time of the reserved vehicle. For example, as shown in FIG. 4, when the scheduled maintenance time determined after the start of maintenance is ΔT1 and the scheduled end time of maintenance is later than the start time of use t3, the reserved vehicle C1 is rented out at the start time of use t3. Therefore, the substitute vehicle necessity determination unit 434 determines that a substitute vehicle is necessary. On the other hand, when the scheduled maintenance time is the standard maintenance time ΔT0, the scheduled maintenance end time is not later than the use start time t3, so the substitute vehicle necessity determination unit 434 determines that the substitute vehicle is unnecessary.

For example, when the scheduled maintenance time is ΔT1 shown in FIG. 4 and the vehicle search unit 434 determines that a substitute vehicle for the reserved vehicle C1 is required by the substitute vehicle necessity determination unit 434, the vehicle search unit 435 refers to the vehicle database 441 and selects the substitute vehicle. Search for. That is, an alternative vehicle is searched from the vehicles C2 to C7 of the same vehicle type as the reserved vehicle C1. The alternative vehicle is searched from the vehicles for which maintenance has already been completed and the reserved vehicle C1 has not yet been reserved within the usage time t3 to t4.

The plan change unit 436 changes the usage plan using the alternative vehicle searched by the vehicle search unit 435 as a new reserved vehicle. When a plurality of alternative vehicles are searched, their priorities are determined based on the geographical proximity of the reserved vehicle and the alternative vehicle, and the alternative vehicle having the highest priority is used as the reserved vehicle to change the usage plan. Specifically, when there are a plurality of business entities (stations) having alternative vehicles, if the business entities within the same geographical range have alternative vehicles, the alternative vehicle is given priority first. When there are multiple alternative vehicles within the same geographical area, secondly, the distance between each business entity having these alternative vehicles and the business entity having a reserved vehicle and the travel time between them are short. The higher the priority. The plan change unit 436 is searched by the vehicle search unit 435, and the substitute vehicle having the highest priority is tentatively reserved as a new reserved vehicle. After that, when the tentatively reserved vehicle is approved by the user, the reservation of the alternative vehicle is confirmed.

The output unit 437 transmits the information of the new reserved vehicle (information of the tentatively reserved alternative vehicle) included in the usage plan changed by the plan change unit 436 to the user terminal 3 via the communication unit 41. The user who receives this information instructs via the input / output unit 32 whether or not to approve the change of the reserved vehicle. The command by this user is transmitted to the server device 4 as a response signal including acceptance or disapproval of the change of the usage plan. At this time, when the communication unit 41 receives the response signal of consent, the change in the usage plan is confirmed, and the plan change unit 436 makes a reservation for the alternative vehicle and updates the vehicle database 441.

After the change of the usage plan is confirmed, the output unit 437 further transmits the change information of the usage plan to at least the business entity terminal 1 of the related business entity. That is, the change information of the usage plan is transmitted to the business entity terminal 1 of the business entity having the original reserved vehicle and the business entity terminal 1 of the business entity having the new reserved vehicle. This change information includes a command to workers of an entity having a new reserved vehicle, that is, a command to transfer the new reserved vehicle to a predetermined station by a predetermined time (eg, start time of use). .. If the original reserved vehicle and the new reserved vehicle belong to the same entity, the new reserved vehicle is located at the same station as the original reserved vehicle, so it is necessary to transfer the new reserved vehicle. Absent. In this case, it is not necessary to include the vehicle transfer command to the worker in the change information of the utilization plan.

FIG. 5 is a flowchart showing an example of processing executed by the calculation unit 43 according to a program stored in the storage unit 44 of the server device 4 in advance. The process shown in this flowchart is started when, for example, receives a command for applying for a reservation for use of a shared vehicle input by the user via the user terminal 3 via the communication unit 41, and is repeated at predetermined time intervals.

First, in step S1, the reservation reception unit 431 processes the application for the reservation for the use of the shared vehicle. Next, in step S2, a usage plan for the reserved vehicle is created by processing by the plan creation unit 432. This utilization plan includes a maintenance plan (for example, t1 to t2 in FIG. 4) that is executed before the usage start time of the reserved vehicle (for example, t3 in FIG. 4).

Next, in step S3, it is determined whether or not the maintenance information of the reserved vehicle, that is, the information regarding the scheduled maintenance time has been acquired from the business entity terminal 1 by the process of the maintenance information acquisition unit 433. This information is information input by the worker via the input / output unit 12 and received via the communication unit 41 when the maintenance of the reserved vehicle is started. Step S3 is repeated until affirmed, and when affirmed in step S3, the process proceeds to step S4.

In step S4, it is determined whether or not the scheduled maintenance end time is later than the reserved vehicle use start time (for example, t3 in FIG. 4) by the process of the substitute vehicle necessity determination unit 434, and a substitute vehicle is required accordingly. Judge whether or not. If affirmed in step S4, the process proceeds to step S5, and if denied, the usage plan does not need to be changed, and the process ends.

In step S5, the vehicle search unit 435 searches for a substitute vehicle of the same vehicle type as the reserved vehicle from among the plurality of shared vehicles owned by the plurality of business entities. The alternative vehicle is searched from among the vacant vehicles for which maintenance has already been completed and no reservation has been made within the reserved vehicle usage time (for example, t3 to t4 in FIG. 4).

Next, in step S6, the alternative vehicle searched in step S5 is tentatively reserved as a new reserved vehicle by the process of the plan change unit 436. In particular, when a plurality of alternative vehicles are searched for in step S5, the plurality of alternative vehicles are prioritized and the alternative vehicle having the highest priority is tentatively reserved as a new reserved vehicle. The priority order is whether or not the station where the reserved vehicle exists and the station where the alternative vehicle exists are within the same range AR1 and AR2 in FIG. 2, and the station where the reserved vehicle exists and the station where the alternative vehicle exists. Determined in consideration of geographical proximity.

Next, in step S7, the information of the substitute vehicle tentatively reserved in step S6 is transmitted to the user terminal 3 via the communication unit 41 by the processing in the output unit 437. Next, in step S8, a signal (response signal) from the user terminal 3 as to whether or not to accept the provisionally reserved alternative vehicle as a new reserved vehicle by processing by, for example, the plan change unit 436 is transmitted via the communication unit 41. To determine whether or not it was received. Step S8 is repeated until affirmed, and when affirmed in step S8, the process proceeds to step S9.

In step S9, the process by the plan change unit 436 determines whether or not the response signal received via the communication unit 41 is a consent signal. If denied in step S9, the process returns to step S6, and among the plurality of searched alternative vehicles, the alternative vehicle having the highest priority in the previous process is deferred and the second highest priority is given. Raise the priority of alternative vehicles that are considered high. That is, the priority of the alternative vehicle is changed. Then, the substitute vehicle having the highest priority is tentatively reserved as a new reserved vehicle, and the same process is repeated until it is affirmed in step S9. If affirmed in step S9, the process proceeds to step S10.

In step S10, the tentatively reserved alternative vehicle is booked and the change in the usage plan is confirmed by the process of the plan change unit 436, and the vehicle database 441 is updated. Next, in step S11, the business entity terminal 1 of the business entity having the vehicle related to the plan change, that is, the business entity terminal 1 of the business entity having the original reserved vehicle (vehicle under maintenance) by the processing in the output unit 437. And, the information of the change of the usage plan is transmitted to the business entity terminal 1 of the business entity having the new reserved vehicle, and the process is completed.

The main operation of the car sharing management system according to the present embodiment will be described more specifically. 6A and 6B are diagrams showing an example of a utilization plan for vehicles C1 to C7. Note that FIGS. 6A and 6B show different usage plan patterns.

First, an example of FIG. 6A will be described. At time t1 in FIG. 6A, the maintenance of the reserved vehicle C1 is started by the worker of the store A, the scheduled maintenance time ΔT1 exceeds the standard maintenance time ΔT0, and the scheduled maintenance end time is longer than the usage start time t3 of the reserved vehicle C1. Suppose it was later. At this time, the calculation unit 43 determines that a substitute vehicle is necessary (step S4), and in the example of FIG. 6A, empty vehicles C3, C4, C5 for which maintenance has already been completed and no reservation has been made at time points t3 to t4. , C7 are searched as alternative vehicles (step S5).

As shown in FIG. 2, when the distances from the reserved vehicle C1 to the vehicles C3, C4, C5, and C7 are compared, the distance to the vehicle C3 is smaller because the vehicle C3 belongs to the same business entity A store as the vehicle C1. The shortest. Therefore, the vehicle C3 as an alternative vehicle has the highest priority. Next, the distance from the reserved vehicle C1 increases in the order of vehicles C5, C4, C7 (L2 <L1 <L3), but the vehicle C4 exists in the same geographical range AR1 as the vehicle C1, whereas the vehicle C5 It exists in a geographical range AR2 different from the vehicle C7. Therefore, the vehicle C4 has the second highest priority, and the subsequent priorities are the vehicles C5 and C7.

From the above, as shown in FIG. 6A, the vehicle C3 having the highest priority is tentatively reserved as a new reserved vehicle (step S6). When the user approves the change of the reserved vehicle, the reservation of the vehicle C3 is confirmed (step S10), and the change information of the usage plan is transmitted to the business entity terminal 1 of the store A (step S11). At this time, the reservation of the original reserved vehicle C1 is canceled. If the user does not approve the change of the reservation to the vehicle C3, the priority of the vehicle C4 having the next highest priority is raised, and the vehicle C4 is tentatively reserved.

Next, an example of FIG. 6B will be described. In the example of FIG. 6B, when it is determined that a substitute vehicle is necessary (step S4), the vacant vehicles C4, C5, and C7 for which maintenance has already been completed and no reservation has been made in the time range t3 to t4 are substitute vehicles. Is searched for (step S5). At this time, since the vehicle C4 has the highest priority among the vehicles C4, C5, and C7, the vehicle C4 is tentatively reserved as a new reserved vehicle (step S6), and when the user approves the change of the reserved vehicle, The reservation for vehicle C4 is confirmed (step S10).

After that, the change information of the usage plan is transmitted to the business entity terminal 1 of the B store having the vehicle C4 (step S11). This change information includes a command that the worker of the business entity B store should transfer the vehicle C4 to the station of the A store by the use start time t3 at the latest. The change information transmitted to the business entity terminal 1 of the business entity A store may include a command for the worker of the business entity A store to go to the business entity B store to pick up the vehicle C4.

According to this embodiment, the following effects can be obtained.
(1) The car-sharing management system 100 of the present embodiment is a plurality of business entities scattered within a geographically predetermined range AR1 and AR2, each of which owns vehicles C1 to C7 to be used for car-sharing. It manages a car-sharing business conducted under an organizational system including a plurality of business entities having a maintenance base for performing maintenance of vehicles C1 to C7 and a station where vehicles C1 to C7 are parked (Fig. 1, FIG. 1). 2). The car sharing management system 100 has a reservation reception unit 431 that accepts an application for a vehicle use reservation and a reservation start time (for example, t3 in FIG. 4) of the reserved vehicle (for example, vehicle C1) received by the reservation reception unit 431. A plan creation unit 432 that creates a usage plan for the reserved vehicle C1 including a maintenance plan (for example, t1 to t2 in FIG. 4) to be executed before, and a vehicle condition of the reserved vehicle C1 before the maintenance of the reserved vehicle C1 is completed. The maintenance information acquisition unit 433 that acquires information about the scheduled maintenance times ΔT0 and ΔT1, the information about the scheduled maintenance times ΔT0 and ΔT1 acquired by the maintenance information acquisition unit 433, and the usage plan created by the planning unit 432. Based on this, a substitute vehicle necessity determination unit 434 that determines the necessity of a substitute vehicle and a substitute vehicle necessity determination unit 434 that determines the necessity of a substitute vehicle depending on whether or not the maintenance end time is later than the use start time of the vehicle C1 (for example, t3 in FIG. 4). When it is determined by the unit 434 that an alternative vehicle is necessary, the vehicle search unit 435 that searches for an alternative vehicle from the plurality of vehicles C2 to C7 owned by the plurality of business entities and the alternative vehicle searched by the vehicle search unit 435 are used. Is provided with a plan change unit 436 that changes the usage plan as a new reserved vehicle (Fig. 3).

With such a configuration, for example, when the maintenance time of the reserved vehicle C1 is longer than the standard maintenance time ΔT0 and the maintenance is not completed by the next use start time t3, the substitute vehicle of the reserved vehicle C1 can be easily used. Can be prepared. Therefore, even if the maintenance time is longer than initially expected, the user can use the shared vehicle without any trouble, and an efficient car sharing business can be performed by shortening the free time of the shared vehicle. In addition, since the usage plan is created so that maintenance is performed every time the shared vehicle is returned, the shared vehicle can always be used for car sharing in good condition. That is, since the car sharing management system 100 of the present embodiment is mainly performed by a business entity such as a car dealer who is scattered within a geographically predetermined range AR1 and AR2 and has a maintenance base, it is easy to maintain the vehicle. It can be done and it is easy to arrange a substitute vehicle.

(2) The car sharing management system 100 outputs the information of the new reserved vehicle included in the usage plan changed by the plan change unit 436, and outputs the output unit 437 that notifies the user of the information via the communication unit 41. Further prepare (Fig. 3). As a result, the user can recognize the information regarding the change of the reserved vehicle.

(3) When the car sharing management system 100 notifies the user of information regarding the change of the reserved vehicle by the information output from the output unit 437, the response signal transmitted from the user terminal 3, that is, the consent for the change of the reserved vehicle or the change of the reserved vehicle A communication unit 41 that receives a response signal according to a user's command including non-approval is further provided (FIG. 3). The plan change unit 436 changes (confirms the change) the usage plan on condition that the response signal of consent is received by the communication unit 41. By changing the reserved vehicle on condition of the user's consent in this way, it is possible to change the reserved vehicle in respect of the user's intention.

(4) The vehicle search unit 435 searches for an alternative vehicle from the vehicles C2 to C7 of the same vehicle type as the reserved vehicle C1 whose usage reservation has been accepted by the reservation reception unit 431. As a result, even if the reserved vehicle is changed, there is little possibility that the user will be disadvantaged, and the reserved vehicle can be changed appropriately.

(5) When the vehicle search unit 435 searches for a plurality of alternative vehicles C2 to C7 of the same vehicle type as the reserved vehicle C1, the plan change unit 436 finds a plurality of alternative vehicles C2 to C7 from the station where the reserved vehicle C1 is parked. Based on the geographical proximity to each parked station, the priority of multiple alternative vehicles C2 to C7 is determined, and the alternative vehicle with the highest priority is used as the reserved vehicle to change the usage plan (Fig. 2). .. As a result, the alternative vehicle can be efficiently arranged at the same station as the reserved vehicle C1.

(6) The car sharing management system 100 includes a user terminal 3 which is owned by a user who plans to use vehicles C1 to C7 and has an input / output unit 32 for applying for a usage reservation accepted by the reservation reception unit 431, and a plurality of user terminals 3. A plurality of business entity terminals 1 and a plurality of business entities, each of which has an input / output unit 12 for which information on the scheduled maintenance time acquired by the maintenance information acquisition unit 433 is input by the employees of the business entity. It is communicably connected to the terminal 1 and the user terminal 3, and includes the above-mentioned reservation reception unit 431, plan creation unit 432, maintenance information acquisition unit 433, substitute vehicle necessity determination unit 434, vehicle search unit 435, and planning. A server device 4 having a change unit 436 is provided. By configuring the car sharing management system 100 including the business entity terminal 1, the user terminal 3, and the server device 4 in this way, the car sharing business can be efficiently performed.

(7) A plurality of business entities manage the operations of the business entity A store having vehicles C1 to C3, the business entity B store having the vehicle C4 of the same vehicle type as the vehicles C1 to C3, and the business entity A store and the B store. Includes business entity E (Figs. 1 and 2). The business entity terminal 1 owned by the business entity A store has a vehicle information acquisition unit 13a for acquiring vehicle information of the vehicles C1 to C3, and the business entity terminal 1 owned by the business entity B store acquires the vehicle information of the vehicle C4. The business entity terminal 1 owned by the business entity E has a vehicle information acquisition unit 13a for acquiring vehicle information of the vehicles C1 to C3 and the vehicle C4. As a result, it is possible to prevent the vehicle information possessed by the business entity from being acquired by another business entity in the same row as the business entity. In addition, the upper business entity can acquire the vehicle information possessed by the lower business entity, and can appropriately manage the vehicle based on the acquired vehicle information.

In the above embodiment, the information regarding the change of the reserved vehicle is output from the output unit 437 and notified to the user, but the change information may be notified to the user from the call center. Further, if the new reserved vehicle and the original reserved vehicle are of the same model, there is little disadvantage for the user. In this case, the plan change unit does not output the information regarding the change of the reserved vehicle to the user terminal 3. The 436 may change the reserved vehicle. In this case, the output unit 437 as a notification unit for notifying the user of the information of the new reserved vehicle included in the usage plan changed by the plan change unit 436 can be omitted. Further, the communication unit 41 as a receiving unit for receiving the response signal according to the user's command including the consent or non-approval for the change of the reserved vehicle may be omitted.

In the above embodiment, the vehicle search unit 435 searches for a substitute vehicle of the same vehicle type as the reserved vehicle, but may search not only the same vehicle type but also a substitute vehicle of a similar vehicle type instead of the same vehicle type. .. In the above embodiment, when a plurality of alternative vehicles are searched by the vehicle search unit 435, the plan change unit 436 uses the station where the reserved vehicle is located (first station) and the station where the alternative vehicle is located (second station). Prioritized multiple alternative vehicles based on their geographical proximity to. Here, the geographical proximity means a short linear distance between the first station and the second station, and a short travel time from the second station to the first station.

In the above embodiment, the application for the usage reservation accepted by the reservation reception unit 431 is made via the input / output unit 32 of the user terminal 3, but the configuration of the application unit is not limited to this. The application for the usage reservation may be made via the call center. In the above embodiment, the information regarding the scheduled maintenance time is input via the input / output unit 12 of the business entity terminal 1, but the configuration of the maintenance input unit is not limited to this. For example, when the information about the scheduled maintenance time is not output from the business entity terminal 1 even though the predetermined time has passed from the start time of the maintenance, the maintenance information acquisition unit receives the information that the scheduled maintenance time does not exceed the standard maintenance time ΔT0. May be obtained.

In the above embodiment, for example, a business entity A store (first business entity) having vehicles C1 to C3 as a first shared vehicle and a business entity B store (second business entity) having a vehicle C4 as a second shared vehicle. ) And the business entity E (third business entity) that manages these business entities are included to form a plurality of business entities, but the composition of the first business entity to the third business entity is as described above. Not limited to. In addition, the vehicle information acquisition unit 13a (first vehicle information acquisition unit) of the business entity A store, the vehicle information acquisition unit 13a (second vehicle information acquisition unit) of the business entity B store, and the vehicle information acquisition of the business entity E company. Although different vehicle information is acquired by each unit 13a (third vehicle information acquisition unit), the configurations of the first vehicle information acquisition unit to the third vehicle information acquisition unit are not limited to those described above.

In the above embodiment, the car sharing management system 100 is configured by the business entity terminal 1, the in-vehicle terminal 2, the user terminal 3, and the server device 4, and the server device 4 has the reservation reception unit 431, the plan creation unit 432, and maintenance information acquisition. A unit 433, a substitute vehicle necessity determination unit 434, a vehicle search unit 435, and a plan change unit 436 are provided to play the main functions of the car sharing management system, but some or all of these functions are server devices. It may be prepared for other than (for example, a business entity terminal).

The above embodiment has described a case where a car sharing business is carried out with a dealer who sells or maintains vehicles as a business entity, but the car sharing management system of the present invention is not limited to such a dealer but other businesses. The same can be applied when a body (for example, a business entity that operates a gas station) conducts a car sharing business. The organizational system to which the car-sharing management system is applied may be two layers, an upper layer and a lower layer, instead of three layers, or may be four or more layers.

The above description is merely an example, and the present invention is not limited to the above-described embodiments and modifications as long as the features of the present invention are not impaired. It is also possible to arbitrarily combine one or a plurality of the above-described embodiments and the modified examples, and it is also possible to combine the modified examples.

1 Business terminal, 2 In-vehicle terminal, 3 User terminal, 4 Server device, 12 Input / output unit, 13a Vehicle information acquisition unit, 32 Input / output unit, 41 Communication unit, 100 Car sharing management system, 431 Reservation reception unit, 432 Plan Creation unit, 433 maintenance information acquisition unit, 434 substitute vehicle necessity determination unit, 435 vehicle search unit, 436 plan change unit, 437 output unit

Claims (7)

Multiple businesses scattered within a predetermined geographical area, each of which owns a shared vehicle for car sharing, and has a maintenance base for maintaining the shared vehicle and a station where the shared vehicle is parked. It is a car sharing management system that manages the car sharing business conducted under an organizational system that includes multiple business entities.
Reservation reception department that accepts applications for shared vehicle usage reservations,
A planning unit that creates a usage plan for the reserved vehicle, including a maintenance plan that is executed before the reservation vehicle usage start time received by the reservation reception unit.
Before the maintenance of the reserved vehicle is completed, the maintenance information acquisition unit that acquires information on the scheduled maintenance time according to the vehicle condition of the reserved vehicle, and the maintenance information acquisition unit.
Based on the information regarding the scheduled maintenance time acquired by the maintenance information acquisition unit and the usage plan created by the plan creation unit, a substitute vehicle necessity determination unit that determines the necessity of a substitute vehicle, and a substitute vehicle necessity determination unit.
When it is determined by the substitute vehicle necessity determination unit that a substitute vehicle is necessary, a vehicle search unit that searches for a substitute vehicle from a plurality of shared vehicles owned by the plurality of business entities, and a vehicle search unit.
It is provided with a plan change unit that changes the usage plan by using the alternative vehicle searched by the vehicle search unit as a new reserved vehicle .
The planning unit creates the maintenance plan based on a predetermined standard maintenance time including the travel time from the maintenance base to the station after the maintenance of the reserved vehicle.
The maintenance information acquisition unit, car sharing management system which is characterized that you acquire the maintenance base the scheduled maintenance time, which is input by the workers after the maintenance start of the reserved vehicle. In the car sharing management system according to claim 1,
A car-sharing management system, further comprising a notification unit that notifies a user of information on a new reserved vehicle included in a usage plan changed by the plan change unit. In the car sharing management system according to claim 2.
Further provided is a receiving unit for receiving a response signal according to a user's command including acceptance or non-acceptance for the change of the reserved vehicle notified by the notification unit.
The plan changing unit is a car sharing management system characterized in that the usage plan is changed on condition that a response signal of consent is received by the receiving unit. In the car sharing management system according to any one of claims 1 to 3,
The vehicle search unit is a car sharing management system characterized in that a substitute vehicle is searched from among shared vehicles of the same vehicle type or a similar vehicle type as the reserved vehicle for which a reservation for use has been accepted by the reservation reception unit. In the car sharing management system according to claim 4,
When the vehicle search unit searches for a plurality of alternative vehicles of the same or similar vehicle type as the reserved vehicle, the plan change unit parks each of the plurality of alternative vehicles from the first station where the reserved vehicle is parked. Based on the geographical proximity to the second station, the priority of the plurality of alternative vehicles is determined, and the alternative vehicle having the highest priority is used as the reserved vehicle to change the usage plan. Vehicle management system. In the car sharing management system according to any one of claims 1 to 5,
A user terminal owned by a user who plans to use a shared vehicle and having a usage reservation application unit accepted by the reservation reception unit, and a user terminal having a usage reservation application unit.
A plurality of business entity terminals each of the plurality of business entities, each of which has a maintenance input unit in which information regarding a scheduled maintenance time acquired by the maintenance information acquisition unit is input by a worker of the business entity. Business terminal and
A server device communicatively connected to the plurality of business entity terminals and the user terminal, the reservation reception unit, the plan creation unit, the maintenance information acquisition unit, and the substitute vehicle necessity determination unit. , A car sharing management system including a server device having the vehicle search unit and the plan change unit. In the car sharing management system according to claim 6,
The plurality of business entities include a first business entity having a first shared vehicle, a second business entity having a second shared vehicle of the same or similar vehicle type as the first shared vehicle, the first business entity, and the said. Including the third business entity that manages the business of the second business entity
The business entity terminal possessed by the first business entity has a first vehicle information acquisition unit that acquires vehicle information of the first shared vehicle.
The business entity terminal possessed by the second business entity has a second vehicle information acquisition unit that acquires vehicle information of the second shared vehicle.
A car-sharing management system characterized in that the business entity terminal possessed by the third business entity has a third vehicle information acquisition unit that acquires vehicle information of the first shared vehicle and the second shared vehicle.

Images