JP2019008659A - Vehicle sharing management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a car sharing management system capable of efficiently increasing the operating rate of a shared vehicle. A car sharing management system 100 is shared with an operating rate calculation unit 434 that calculates an operating rate of each shared vehicle based on vehicle information acquired by a vehicle information acquiring unit 433, and each shared according to the calculated operating rate. Based on the charge setting unit 435 that sets the standard charge per unit usage time of the vehicle, the set standard charge, and the usage time of the shared vehicle included in the acquired vehicle information, the usage charge of each shared vehicle is set. It is provided with a charge calculation unit 436 for calculation. The charge setting unit 435 sets the first standard charge when the calculated operating rate is lower than the target operating rate to be lower than the second standard charge when the operating rate is equal to or higher than the target operating rate. [Selection diagram] Fig. 3

Description

  The present invention relates to a car sharing management system that manages a shared vehicle used by a plurality of users.

  Conventionally, based on the distribution of a plurality of shared vehicles waiting in a state where they can be used at a plurality of stations, a degree of uneven distribution indicating the degree of uneven distribution of the plurality of shared vehicles is calculated, and the degree of uneven distribution is a predetermined value or more. In such a case, there is known an apparatus that performs processing for reducing the uneven distribution degree (see, for example, Patent Document 1). In the apparatus described in Patent Document 1, when the user selects a station whose degree of uneven distribution is reduced as a return destination station for the shared vehicle, the usage fee for the shared vehicle is reduced.

Japanese Patent Laid-Open No. 2006-95750

  However, the apparatus described in Patent Document 1 suppresses the occurrence of a bias in the distribution of shared vehicles for each station on the premise of a one-way car sharing system that returns a shared vehicle borrowed at one station at another station. is there. Therefore, in the apparatus described in Patent Document 1, it is difficult to efficiently increase the operation rate of each shared vehicle.

  A car sharing management system according to one aspect of the present invention is acquired by a vehicle information acquisition unit that acquires vehicle information of each shared vehicle including usage records of each of a plurality of shared vehicles that can be lent to a user, and a vehicle information acquisition unit. The operating rate calculation unit that calculates the operating rate of each shared vehicle based on the vehicle information, and the base rate per unit usage time or unit usage distance of each shared vehicle according to the operating rate calculated by the operating rate calculation unit The usage rate of each shared vehicle is determined based on the usage fee or usage distance of the shared vehicle included in the vehicle information acquired by the vehicle information acquisition unit. A charge calculation unit for calculating a charge. The charge setting unit sets the first reference fee when the operation rate calculated by the operation rate calculation unit is lower than the target operation rate, lower than the second reference fee when the operation rate is equal to or higher than the target operation rate.

  According to the present invention, the operation rate of each shared vehicle can be increased efficiently.

The image figure which shows the organization system with which the car sharing management system which concerns on embodiment of this invention is applied. The figure which shows the geographical arrangement | positioning of the some business entity of FIG. 1 is a block diagram showing an overall configuration of a car sharing management system according to an embodiment of the present invention. The figure which shows the relationship between the operation rate for weekdays used in the car sharing management system which concerns on embodiment of this invention, and a reference charge. The figure which shows the relationship between the operation rate for holiday used in the car sharing management system which concerns on embodiment of this invention, and a reference charge. The figure which shows the specific example of the setting of a reference charge. The flowchart which shows an example of the process performed by the calculating part of the server apparatus of FIG.

  Hereinafter, an embodiment of the present invention will be described with reference to FIGS. The car sharing business is a business that lends a vehicle unattended using an IC card registered in advance, and charges the user according to the usage time or usage distance (travel distance) of the vehicle when the vehicle is returned. A car sharing management system according to an embodiment of the present invention is a system suitable for a car sharing business mainly performed by a business entity such as a dealer (car dealer) that performs vehicle sales and maintenance (inspection and maintenance). Configured as Vehicles (shared vehicles) owned by the entity and used for the car-sharing business are parked within the premises of the entity. A place where such a shared vehicle is parked is called a station.

  Within the premises of the business entity, not only stations but also maintenance bases for workers belonging to the business entity to maintain the shared vehicle are provided. The station is provided, for example, in the same site as the maintenance base, or in a site adjacent to each other across a fence or road. As long as the station is provided in the vicinity of the maintenance base such that the distance from the maintenance base to the station is within a predetermined distance, the station may be provided at a site other than the same or adjacent site as the maintenance base.

  When a user uses a shared vehicle, for example, the same station becomes a starting point and a return point of the shared vehicle. For example, each time the shared vehicle is returned to the station, the shared vehicle is transferred to a maintenance base by an operator, 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 lend the shared vehicle to the user in a good state, the shared vehicle is maintained every time the user's use is completed.

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

  FIG. 2 is a diagram illustrating a geographical arrangement of a plurality of business entities A store to D store. As shown in FIG. 2, among a plurality of business entities A to D, stores A and B are scattered within the first range AR1, and stores C and D are adjacent to the first range AR1. It is scattered within the second range AR2. Note that the number of entities in the third hierarchy included in each of the ranges 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 may be separated from each other. In FIG. 2, C1 to C7 are common vehicles of the same vehicle type, the store A stores the vehicles C1 to C3, the store B stores the vehicles C4, the store C stores the vehicles C5 and C6, the store D stores the vehicles C7, Hold each.

  When the number of shared vehicles is insufficient in one business unit (for example, store A), it is possible to arrange a vehicle from another business unit (for example, store B) in the same range AR1 to the one business unit. When there is no vehicle to be arranged in the business entity in the same range AR1, the vehicle can be arranged from the business entity (for example, the C store or the D store) in the different range AR2. When there is a plurality of business entities that can arrange vehicles in one business entity, the distance between the station of the one business entity (for example, store A) and the stations of other business entities (for example, store B to store D) Considering L1 to L3, it is also possible to arrange vehicles preferentially from the station with the shortest distance.

  As shown in FIG. 1, the second hierarchy is an entity that manages the operations of a plurality of entities A store, B store, C store, and D store in the third hierarchy (for example, company E and F that are vehicle sales companies). Company). Company E manages stores A and B that are scattered within the first range AR1, and Company F manages stores C and D that are scattered within the second range AR2. Note that the number of entities in the second hierarchy may be one, or three or more. Company E and Company F are located, for example, in the first range AR1 and the second range AR2, respectively.

  The first hierarchy is composed of business entities that manage the operations of a plurality of business entities E and F (for example, Company G, which is a vehicle manufacturer). Company G has a call center that responds to, for example, telephone calls and mails from users. The relationship between Company G, Company E, and Company F corresponds to, for example, the relationship between the parent company and a subsidiary. Note that the number of entities in the first hierarchy may be two or more. There may be additional entities at the top of the first hierarchy.

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

  By the way, in the car sharing business, it is preferable that the operation rate of the vehicle is high. Particularly, for the plurality of vehicles C1 to C7 of the same vehicle type, the difference in the operation rate is small, and the usage frequency of the vehicles C1 to C7 is about the same. Preferably there is. However, since the operating rate depends on the geographical convenience of the station where the vehicles C1 to C7 are arranged, it is difficult to reduce the difference in operating rate while keeping the rental conditions of the vehicles C1 to C7 the same. . Therefore, in the present embodiment, in order to reduce the difference in operating rates of the plurality of vehicles C1 to C7, in other words, in order to make the frequency of use the same level, the vehicle usage charges are differentiated according to the operating rates. Configure.

  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 in the first to third tiers, and an in-vehicle provided in vehicles C1 to C7 owned by each business entity. It has the terminal 2, the user terminal 3 which the customer (user) who uses the vehicles C1-C7 has, and the server apparatus 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, the 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. 3 shows a single server device 4, the function shown in the server device 4 in 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 portable wireless terminal operated by a worker (employee) of each business entity. The business entity terminal 1 includes 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 be able to wirelessly communicate with the server device 4 via the communication network 5. The communication unit 11 transmits the usage information and maintenance information of the vehicles C <b> 1 to C <b> 7 to the server device 4 together with the employee ID for identifying the employee of the business entity.

  The input / output unit 12 is a so-called human interface (HMI), and includes a keyboard, a mouse, a monitor, a touch panel, a printer, and the like that can be operated by the user. A worker (employee) of each business entity can input various types of information on the vehicles C1 to C7 via the input / output unit 12, and can acquire information on usage fees and fee payment for the vehicles C1 to C7. it can.

  The arithmetic 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. Based on the above, predetermined processing is executed, and control signals are output to the communication unit 11, the input / output unit 12, and the storage unit 14.

  The calculation unit 13 includes a vehicle information acquisition unit 13 a that acquires various types of 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 business entity A store in the third hierarchy can acquire information on the vehicles C1 to C3 belonging to the store A, and the business entity E company in the second hierarchy manages the vehicles C1 to C4 belonging to the store A and the store B. Information can be acquired, and the entity G company in the first hierarchy can acquire information on the vehicles C1 to C7 belonging to the A store to the D store. The calculation unit 13 can output (for example, display) the vehicle information to the input / output unit 12 in such a manner that the employee can recognize the vehicle information.

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

  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 be able to wirelessly communicate 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 every predetermined time together with the vehicle ID for identifying the vehicles C1 to C7.

  The input / output unit 22 includes various switches and buttons that can be operated by the user, a microphone, a speaker, a monitor, and the like. In addition, the input / output unit 22 includes a card reader 22a that reads user information from an authentication card held by the user. 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 the 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 an 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 unlocks or locks the door lock by driving the door lock actuator. In other words, the door lock actuator unlocks the door lock when the calculation unit 25 outputs the unlock signal, and locks the door lock when the lock signal is output.

  The sensor group 24 is mounted on each of the vehicles C1 to C7 and includes various sensors that detect 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 velocity of the vehicle, an acceleration sensor that detects acceleration acting on the vehicle, a travel distance sensor that detects the travel distance, The sensor group 24 includes an energy remaining amount detection sensor that detects the remaining amount of necessary energy (gasoline in a gasoline vehicle, battery storage amount in an electric vehicle, etc.).

  The arithmetic unit 25 has a CPU, and a signal input via the input / output unit 22, a signal detected by the sensor group 24, a signal received from outside the in-vehicle terminal via the communication unit 21, and the storage unit 26 Predetermined processing is executed based on the stored data, and control signals are output to the actuators of each part of the vehicles C1 to C7, the input / output part 22, and the storage part 26. The arithmetic unit 25 further outputs a control signal to the communication unit 21 to control transmission / reception of signals between the in-vehicle terminal 2 and the server device 4. For example, the computing unit 25 transmits user information read via the card reader 22 a 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, and if there is corresponding reservation information, transmits an unlocking command to the computing unit 25, and if there is no corresponding reservation information, transmits a locking signal. . The arithmetic unit 25 outputs an unlocking signal to the door lock actuator when receiving the unlocking command, and outputs a locking signal when receiving the locking command.

  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 such as detection data from the sensor group 24. The stored detection data is transmitted to the server device 4 every predetermined time via the communication unit 21 by processing in the calculation unit 25.

  The user terminal 3 includes a personal computer operated by the user, a portable wireless terminal represented by a smartphone, and the like. The user terminal 3 includes 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 be able to wirelessly communicate with the server device 4 via the communication network 5. The communication unit 31 transmits, to the server device 4, a signal that instructs a reservation application or cancellation of the vehicles C <b> 1 to C <b> 7 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 commands such as user information input, vehicle reservation application, change, and cancellation via the input / output unit 32. The user information includes the user's address, name, contact information, license number, information necessary for payment (for example, credit card number), and the like. The user can use the shared vehicle after entering user information and registering as a member.

  When applying for a vehicle reservation, the user is instructed by the vehicle type, the station to be used, and the use date and time (use start date and time and use end date and time) of the vehicle. At this time, the server device 4 searches for a reservable vehicle that satisfies any or all of the instructed vehicle type, station, and use date and time, and transmits information on the searched vehicle to the user terminal 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.

  At the time of vehicle reservation application, the input / output unit 32 displays a vehicle usage fee as vehicle information. The displayed charges include the charges per predetermined time or distance (reference charges) and the total usage charges, and the total usage charges are calculated by multiplying the reference charges by the usage hours or usage distances. The The fee displayed at the time of reservation application is a scheduled fee, and when the vehicle usage time and mileage are determined when the vehicle is returned, the usage fee is also determined. The confirmed usage fee is displayed via the input / output unit 32, so that the user can grasp the usage fee.

  The calculation unit 33 has a CPU, and is predetermined 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. The 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 nonvolatile 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, for example, in the business entity G in the first hierarchy. The server apparatus 4 can also be configured using a virtual server function on the cloud. The server device 4 includes 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 be able to wirelessly communicate with the business entity terminal 1, the in-vehicle terminal 2, and the user terminal 3 via the communication network 5. The input / output unit 42 includes, for example, a keyboard, a mouse, a monitor, a touch panel, and the like. The arithmetic unit 43 has a CPU, and is predetermined 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. 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 nonvolatile memory (not shown). The storage unit 44 stores various programs executed by the calculation unit 43 and various data. The storage unit 44 includes a vehicle database 441, a user database 442, and an employee database 443 as functional configurations carried by 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, the vehicle model number, the vehicle number, the travel distance, the maintenance history, and the operation rate of each vehicle C1 to C7. Information, the charge information of each vehicle C1-C7, and the utilization plan of each vehicle C1-C7 are memorize | stored. The fee information includes the past and current reference fees of the vehicles C1 to C7 set by the fee setting unit 435 described later. The usage plan includes time-series usage results of the vehicles C1 to C7, current and future time-series reservation information, and a maintenance plan for the vehicles C1 to C7 executed between the reservation information. Charge information is stored in association with the usage record.

  The user database 442 includes user information, such as user ID, address, name, contact information, and license number, input via the user terminal 3 (input / output unit 32), and use of each user's vehicles C1 to C7. History information, information indicating payment status of usage charges for each user, and the like are stored.

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

  The calculation unit 43 has a functional configuration that the processor takes as a reservation reception unit 431, a plan creation unit 432, a vehicle information acquisition unit 433, an operation rate calculation unit 434, a fee setting unit 435, and a fee calculation unit 436. And an output unit 437.

  The reservation receiving unit 431 receives an application for a vehicle use reservation input by the user via the user terminal 3 (input / output unit 32). Specifically, the computing unit 43 searches the vehicle database 441 for a list of reservable vehicles that match the reservation conditions input by the user, such as the vehicle use date and time, the vehicle type, and the business entity to be used. Then, information on the vehicle selected by the user from the transmitted vehicle list or the vehicle approved by the user is received via the communication unit 41. The reservation receiving unit 431 receives an application for use reservation with the selected or approved vehicle as a reserved vehicle.

  The plan creation unit 432 creates current and future use plans for the vehicles C1 to C7 and registers the use plans in the vehicle database 441. More specifically, a use plan for a reserved vehicle received by the reservation receiving unit 431 is created and registered in the vehicle database 441. The use plan includes a use start date and time and a use end date and time of a reserved vehicle, and a maintenance plan executed before the use start date and time.

  The vehicle information acquisition unit 433 acquires vehicle information including usage records of the vehicles C1 to C7 that can be lent to the user from the vehicle database 441. The vehicle information to be acquired includes a usage time and a usage distance for each vehicle C1 to C7 for a predetermined period (for example, one month).

  The operation rate calculation unit 434 calculates the operation rate α of each of the vehicles C1 to C7 based on the vehicle information (utilization results) acquired by the vehicle information acquisition unit 433. The operation rate α is represented by a ratio (%) of the time when the vehicle is actually rented with respect to the vehicle rentable time (for example, 24 hours / day × 31 days) within a predetermined period (for example, one month). The operating rate α is calculated every predetermined period and stored in the vehicle database 441 in time series. Note that the ratio of the actual usage fee to the maximum usage fee that can be generated within a predetermined period can be calculated as the operation rate α.

  The charge setting unit 435 sets a reference charge β that is a calculation reference for the usage charges of the vehicles C1 to C7 according to the operation rate α calculated by the operation rate calculation unit 434. For example, the usage fee per hour is set as the reference fee β. For a user who has used the vehicles C1 to C7 beyond a predetermined time (for example, 24 hours), the reference fee may be set not in one hour but in units of the predetermined time. When the charge calculation unit 436 calculates the use charge according to the distance, the use charge per unit distance can be set as the reference charge.

  The fee setting unit 435 sets different usage fees for weekdays and holidays (Saturday, Sunday, and public holidays). 4A and 4B are characteristic diagrams showing the relationship between the operation rate α for weekdays and holidays stored in the storage unit 44 in advance and the reference charge β. In the characteristic f1 of FIG. 4A, when the operating rate α is equal to or higher than the target operating rate α1, the reference fee β is a fixed rate (price) β1, and when the operating rate α is lower than the target operating rate α1, the lower the operating rate α is, the reference The charge β decreases. Similarly, in the characteristic f2 of FIG. 4B, when the operating rate α is equal to or higher than the target operating rate α2, the base rate β is a fixed rate (price) β2, and when the operating rate α is lower than the target operating rate α2, the operating rate α is low. The reference charge β decreases as the time increases.

  The target operating rates α1 and α2 can be set by the employee via the input / output unit 42 in consideration of the profitability of the business. The fee setting unit 435 can calculate the average value of the operation rates of the vehicles C1 to C7 of the same vehicle type owned by a plurality of business entities, and can calculate the target operation rates α1 and α2 based on the average value. For example, the average value can be set as the target operating rate α1, α2. It is also possible to calculate the target operating rates α1 and α2 by multiplying the average value by a predetermined coefficient. The target operating rates α1 and α2 may be set to different values for each business entity. It is also possible to calculate an average value of the operating rates of not only the same vehicle type but also of similar vehicles, and calculate the target operating rates α1 and α2 based on the average value.

  4A and 4B are set to the same value, for example. On the other hand, the charge β2 in FIG. 4B is set higher than the charge β1 in FIG. 4A by a predetermined charge or by a predetermined ratio. For example, the characteristic f2 is a characteristic obtained by shifting the characteristic f1 upward by a predetermined amount. The fee setting unit 435 sets a reference fee β corresponding to the operation rate α based on the characteristics f1 and f2 of FIG. 4A or FIG. 4B. The charge setting unit 435 uses the usage time T across weekdays and holidays, such as when the use start date of the vehicles C1 to C7 is a weekday and the use end date is a holiday, or the use start date is a holiday and the use end date is a weekday. , The standard charge β for weekdays or holidays is set depending on whether or not the intermediate time between the use start time and use end time is included on weekdays. When the usage time T exceeds 24 hours, the reference fee β is set every 24 hours.

  FIG. 5 is a diagram illustrating a specific example of setting the reference fee β. As shown in pattern 1 in FIG. 5, when the use start time is a time t11 (for example, 20:00) on a weekday (Friday) and the use end time is a time t12 (for example, 12:00) on a holiday (Saturday), the intermediate time Is a holiday time t13 (for example, 4 o'clock). In this case, the charge setting unit 435 sets the base charge β for holidays according to the characteristic f2 in FIG. 4B. As shown in pattern 2 in FIG. 5, when the use start time is a time t21 (for example, 20:00) on a holiday (Sunday) and the use end time is a time t22 (for example, 18:00) on a weekday (Monday), the intermediate time Is a weekday time t23 (for example, 7:00). In this case, the fee setting unit 435 sets the standard fee β for weekdays according to the characteristic f1 in FIG. 4A.

  As shown in pattern 3 in FIG. 5, the use start time is a weekday (Friday) time t31 (for example, 20:00), and the use end time is over 24 hours at a holiday (Sunday) time t32 (for example, 12:00). At some time, the intermediate time of the first 24 hours (time t31 to t33) is a holiday (Saturday) time t34 (for example, 8:00), and the subsequent intermediate time of time t33 to t32 is the holiday (Sunday) time t35 ( For example, 4 o'clock). In this case, the fee setting unit 435 sets a reference fee β for holidays for the total usage time (40 hours).

  As shown in the pattern 4 of FIG. 5, the use start time is a time t31 (for example, 20:00) on weekdays (Friday), and the use end time exceeds 48 hours at a time t42 (for example, 12:00) on weekdays (Monday). At some time, the intermediate time of the first 24 hours (time t41 to t43) is a holiday (Saturday) time t44 (for example, 8:00), and the subsequent 24 hours (time t43 to t45) is the holiday (Sunday) time. It is t46 (for example, 8:00), and the intermediate time between the subsequent times t45 to t42 is a time t47 (for example, 4:00) on weekdays (Monday). In this case, the charge setting unit 435 sets the base charge β for holidays for the first use time T1 (48 hours) out of the total use time (64 hours), and sets the remaining use time T2 (16 hours). On the other hand, set a standard fee for weekdays.

  The fee calculation unit 436 calculates the usage fee of the vehicles C1 to C2 based on the reference fee β set by the fee setting unit 435 and the usage time T of the vehicles C1 to C7. That is, the usage fee is calculated by multiplying the usage fee T by the reference fee β. For example, in the example of pattern 4 in FIG. 5, the total usage fee is obtained by adding the amount obtained by multiplying the base fee β for holidays by the usage time T1 to the amount obtained by multiplying the basic fee β for holidays by the usage time T2. calculate. The usage time T may be not a unit of one hour but a unit of a time longer than one hour or a short time (for example, 15 minutes).

  The output unit 437 stores the usage fee information calculated by the fee calculation unit 436 in the vehicle database 441 and the user database 442 and transmits the information to the user terminal 3 via the communication unit 41. As a result, the user can grasp the usage fee. In this embodiment, the usage fee is calculated by multiplying the usage fee T by the usage fee T. However, there are two types of usage fees for weekdays and holidays determined by the intermediate time between the usage start time and the usage end time. Since the fee structure is simple, it is easy to calculate the usage fee.

  The output unit 437 further outputs the relationship between the reference fee β and the operation rate α for each predetermined period (for example, one month) of each of the vehicles C1 to C7 in time series and stores the relationship in the vehicle database 441. The communication unit 11 of the business entity terminal 1 can acquire this data from the server device 4 and display it on the input / output unit 12. Thereby, the employee can recognize the trend of the change in the operating rate α and can determine the effectiveness of changing the reference fee β. As a result, it is possible to take further measures for efficiently increasing the operating rate α, for example, by changing the characteristics f1 and f2 in FIGS. 4A and 4B.

  FIG. 6 is a flowchart illustrating an example of processing executed by the calculation unit 43 according to a program stored in advance in the storage unit 44 of the server device 4, in particular, an example of processing related to usage charge calculation. The process shown in this flowchart is started when the vehicles C1 to C7 are returned to a predetermined station by the user, for example.

  First, in step S1, vehicle information including the usage record of the returned vehicles C1 to C7 is acquired by processing in the vehicle information acquisition unit 433. Next, in step S2, the operation rate α of the vehicles C1 to C7 is calculated based on the vehicle information acquired in step S1 by processing in the operation rate calculation unit 434. Next, in step S3, an intermediate time between the use start time and use end time of the vehicles C1 to C7 included in the vehicle information is specified. Next, in step S4, it is determined whether or not a weekday fee is applied to the reference fee β depending on whether or not the specified intermediate time is included on a weekday.

  If the determination in step S4 is affirmative, the process proceeds to step S5, and a reference fee β corresponding to the operating rate α is set based on the characteristic f1 in FIG. 4A. On the other hand, if the result is negative in step S4, the process proceeds to step S6, and a reference fee β corresponding to the operation rate α is set based on the characteristic f2 in FIG. 4B. Next, in step S7, the base charge β is multiplied by the vehicle use time T to calculate the use charge. When the vehicle usage time exceeds 24 hours, the reference fee β is calculated every 24 hours and the usage fee is calculated. Next, in step S <b> 8, the fee information is transmitted to the user terminal 3 through the communication unit 41 by the processing in the output unit 437. Although detailed description is omitted, the payment process is performed via the user terminal 3 thereafter.

  FIG. 4B shows an operation rate α21 of the vehicle C1 and an operation rate α24 of the vehicle C4 as an example. When the vehicles C1 and C4 are used according to the operating rates α21 and α24, for example, according to the pattern 1 in FIG. 5, for example, as shown in FIG. 4B, the reference charges β21 and β24 are set according to the characteristic f2, respectively (step S6). ). That is, the reference fee β24 of the vehicle C4 having a low operation rate is set at a lower price than the reference fee β21 (= β2) of the vehicle C1 having a high operation rate. Thereby, the number of users who use the cheaper vehicle C4 increases, and the operating rate of the vehicle C4 can be brought close to the target operating rate α2, and the difference between the operating rates α21 and α24 between the vehicles C1 and C4 can be reduced. .

According to this embodiment, the following effects can be obtained.
(1) The car sharing management system 100 includes a vehicle information acquisition unit 433 that acquires vehicle information of each of the vehicles C1 to C7 including usage records of the plurality of vehicles C1 to C7 that can be lent to the user, and a vehicle information acquisition unit 433. The operation rate calculation unit 434 that calculates the operation rate α of each vehicle C1 to C7 based on the vehicle information acquired by the above, and the unit of each vehicle C1 to C7 according to the operation rate α calculated by the operation rate calculation unit 434 A charge setting unit 435 that sets a reference charge β per use time, a reference charge β set by the charge setting unit 435, and use times of the vehicles C1 to C7 included in the vehicle information acquired by the vehicle information acquisition unit 433 Based on T, a charge calculation unit 436 that calculates a use charge for each of the vehicles C1 to C7 is provided (FIG. 3). The charge setting unit 435 uses the standard fee β when the operation rate α calculated by the operation rate calculation unit 434 is lower than the target operation rates α1, α2, and the reference when the operation rate α is equal to or higher than the target operation rates α1, α2. Set cheaper than the charge β (FIGS. 4A and 4B).

  In this way, by setting the base rate β of a vehicle whose operating rate α is lower than the target operating rates α1 and α2 at a low price, the operating rate α of the vehicle can be increased. That is, the possibility that a potential user who has never used the car sharing service uses the vehicle is increased, and without reducing the operation rate α of other vehicles whose operation rate α is equal to or higher than the target operation rate α1, α2, The operating rate of each vehicle C1-C7 can be raised efficiently.

(2) When the usage date of the vehicles C1 to C7 is a weekday, the fee setting unit 435 sets a weekday standard fee β using the characteristic f1 (FIG. 4A), and the usage date of the vehicles C1 to C7 is a holiday. When this is the case, the base fee for holidays is set using the characteristic f2 (FIG. 4B). This makes it possible to make a difference in usage charges between weekdays and holidays, and it is possible to set charges efficiently according to the demand for car sharing services.

(3) For example, as shown in pattern 2 in FIG. 5, the charge setting unit 435 is a weekday reference when a time t23 intermediate between the use start time t21 and the use end time t22 of the vehicles C1 to C7 is included. For example, as shown in pattern 1 in FIG. 5, when a time t13 intermediate between the use start time t11 and the use end time t12 of the vehicles C1 to C7 is included in the holiday, the reference charge β for the holiday is set. Set. As a result, it is possible to clarify the charge setting as to whether to apply a weekday charge or a holiday charge. Therefore, the user can easily determine the usage fee, and the usefulness for the user increases.

(4) The fee setting unit 435 sets the reference fee β cheaper as the operation rate α calculated by the operation rate calculation unit 434 is lower than the target operation rates α1 and α2 (FIGS. 4A and 4B). Accordingly, it is possible to set an appropriate fee according to the operation rate α, and it is possible to efficiently increase the operation rate α of a vehicle having a low operation rate α.

(5) The car sharing management system 100 includes a plurality of business establishments A to D that are scattered in the geographical predetermined ranges AR1 and AR2 and that own any of the plurality of vehicles C1 to C7 (FIG. 2). . The target operating rates α1 and α2 are calculated based on, for example, the average value of the operating rates of the plurality of vehicles C1 to C7 of the same vehicle type owned by the plurality of business entities. Thereby, the operation rate (alpha) of the vehicles C1-C7 in the whole several business body can be raised efficiently.

  In the above embodiment (for example, FIG. 4B), the base rate (for example, β24) when the operating rate α calculated by the operating rate calculating unit 434 is lower than the target operating rate α2, that is, the first reference rate, is used as the operating rate. The standard fee (for example, β21) when α is equal to or higher than the target operating rate α2, that is, lower than the second standard is set. More specifically, the lower the operating rate α calculated by the operating rate calculating unit 434 is, the lower the target operating rate α2, the lower the first reference fee than the second reference fee. If the price is set lower than the 2 standard charge, the relationship between the first standard charge and the second standard charge is not limited to the above.

  In the above-described embodiment, different reference charges β are set for weekdays and holidays. In other words, the standard charges for weekdays (first standard charge, second standard charge) and the standard charges for holidays (first standard charge, second standard charge) are set separately, but these are the same standard. You may make it set as a charge, or you may make it set a different standard charge for every day of the week instead of dividing into only a weekday and a holiday. In the above embodiment, the usage fee is calculated by multiplying the reference fee β per unit time by the usage time T, but the usage fee is calculated by multiplying the reference fee per unit usage distance by the usage distance. It may be.

  In the above embodiment, a weekday charge is set when a time between the use start time and use end time of the vehicles C1 to C7 is included on a weekday, and a holiday charge is set when included on a holiday. However, the pricing method is not limited to this. In the above embodiment, the usage fee information is output from the output unit 437 and notified to the user. However, this information may be notified to the user from the call center.

  In the above embodiment, the business entity terminal 1, the in-vehicle terminal 2, the user terminal 3, and the server device 4 constitute the car sharing management system 100, and the server device 4 includes the reservation receiving unit 431, the plan creating unit 432, and vehicle information acquisition. Unit 433, operating rate calculation unit 434, fee setting unit 435, and fee calculation unit 436, which are responsible for the main functions of the car sharing management system, but some or all of these functions are other than server devices ( For example, it may be provided in a business entity terminal).

  In the above embodiment, the case where a car sharing business is performed with a dealer that performs vehicle sales, maintenance, and the like as a business entity has been described. However, the car sharing management system of the present invention is not limited to such a dealer. The present invention can be similarly 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 of upper and lower layers instead of three layers, and 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 unless the features of the present invention are impaired. It is also possible to arbitrarily combine one or more of the above-described embodiments and modifications, and it is also possible to combine modifications.

1 business entity terminal, 2 in-vehicle terminal, 3 user terminal, 4 server device, 100 car sharing management system, 433 vehicle information acquisition unit, 434 operating rate calculation unit, 435 fee setting unit, 436 fee calculation unit

Claims (5)

A vehicle information acquisition unit that acquires vehicle information of each shared vehicle including usage records of each of the plurality of shared vehicles that can be lent to the user;
An operating rate calculating unit that calculates an operating rate of each shared vehicle based on the vehicle information acquired by the vehicle information acquiring unit;
A rate setting unit that sets a reference fee per unit usage time or unit usage distance of each shared vehicle according to the operation rate calculated by the operation rate calculation unit;
Charge calculation for calculating the use charge of each shared vehicle based on the reference charge set by the charge setting unit and the use time or use distance of the shared vehicle included in the vehicle information acquired by the vehicle information acquisition unit And comprising
The charge setting unit is less expensive than the second reference charge when the operating rate is equal to or higher than the target operating rate, when the operating rate calculated by the operating rate calculating unit is lower than the target operating rate. Car sharing management system characterized by setting. In the car sharing management system according to claim 1,
The charge setting unit sets the first reference charge for weekdays or the second reference charge for weekdays when the shared vehicle usage day is a weekday, and when the shared vehicle usage day is a holiday, The car sharing management system characterized in that the first reference charge for use or the second reference charge for holidays is set. In the car sharing management system according to claim 2,
The charge setting unit sets the first reference charge for the weekday or the second reference charge for the weekday when the intermediate time between the use start time and the use end time of the shared vehicle is included on a weekday, The car sharing is characterized in that when the intermediate time between the use start time and use end time of the shared vehicle is included in a holiday, the first reference fee for the holiday or the second reference fee for the holiday is set. Management system. In the car sharing management system according to any one of claims 1 to 3,
The charge setting unit sets the first reference fee at a lower price than the second reference fee as the operation rate calculated by the operation rate calculation unit is lower than a target operation rate. system. In the car sharing management system according to any one of claims 1 to 4,
A plurality of business entities that are scattered within a geographical range and have one of a plurality of shared vehicles;
The target operating rate is calculated based on an average value of operating rates of a plurality of shared vehicles of the same vehicle type or a similar vehicle type possessed by a plurality of business entities.

Images