LENDING MANAGEMENT SYSTEM, LENDING MANAGEMENT METHOD, AND LENDING MANAGEMENT PROGRAM

Abstract

To efficiently perform management for time lending for a parking lot.SOLUTION: A lending management system 5 that manages time lending as temporary lending to a third party for a parking lot under a periodical contract, includes: a contract state acquisition unit 41 that acquires contract information 53 including a contract state 51 indicating whether a procedure of the periodical contract for the parking lot has been already made or the contract is being invited, and a use start date 52; a state determination unit 42 that determines, based on the contract state 51 and the contract information 53, whether a current state is an invitation state where the contract is being invited, or whether a current state is a contract waiting state where the procedure of the periodical contract has been already made and the use start date 52 comes after a predetermined waiting period 54 or longer, or whether a current state is an under-contract state where the procedure of the periodical contract has been already made and the use start date 52 comes after a time point during the predetermined waiting period 54; and a lending control unit 43 that permits the time lending in the contract invitation state and the contract waiting state, and prohibits the time lending in the under-contract state.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a rental management system, a rental management method, and a rental management program for managing the temporary rental of a parking space to a third party. [Background technology]

[0002] Various management systems are used to manage monthly parking lots. For example, Patent Document 1 discloses a system that manages hourly rentals of monthly parking lots during times when the monthly parking lots are not in use. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6156959 Summary of the Invention [Problem to be solved by the invention]

[0004] There is a demand for hourly parking to be available even in situations where monthly parking contracts are being solicited, and there is also a demand for more efficient management of hourly parking.

[0005] The present invention aims to efficiently manage hourly rental of parking lots. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, a rental management system according to one embodiment of the present invention is a rental management system that manages hourly rentals, which are temporary rentals of parking spaces under fixed-term contracts to third parties, and is equipped with a contract status acquisition unit that acquires contract information including a contract status indicating whether the procedures for the fixed-term contract of the parking space have already been completed or a contract is being solicited and a start date of use, a status determination unit that determines based on the contract status and the contract information whether the parking space is in a recruitment status where a contract is being solicited, a contract waiting status where the procedures for the fixed-term contract have already been completed and a specified waiting period has passed before the start date of use, or a contract underway status where the procedures for the fixed-term contract have already been completed and a point before the start date of use that is the waiting period has passed, and a rental control unit that allows the hourly rental in the recruitment status and contract waiting status and prohibits the hourly rental in the contract underway status.

[0007] A rental management method according to one embodiment of the present invention is a rental management method for managing hourly rentals, which are temporary rentals of parking spaces under fixed-term contracts to third parties, and includes the steps of: acquiring contract information including a contract status indicating whether the procedures for the fixed-term contract of the parking space have already been completed or a contract is being solicited and a start date of use; determining based on the contract status and the contract information whether the parking space is in a solicitation status where a contract is being solicited, a contract waiting status where the procedures for the fixed-term contract have already been completed and a specified waiting period has passed before the start date of use, or a contract underway status where the procedures for the fixed-term contract have already been completed and a time point before the start date of use that is the waiting period; and allowing the hourly rental in the solicitation status and contract waiting status and prohibiting the hourly rental in the contract underway status.

[0008] A rental management program according to one embodiment of the present invention is a rental management program that manages hourly rentals, which are temporary rentals of parking spaces under fixed-term contracts to third parties, and has a computer execute the following functions: a function to acquire contract information including a contract status indicating whether the procedures for the fixed-term contract of the parking space have already been completed or a contract is being solicited and the start date of use; a function to determine based on the contract status and the contract information whether the parking space is in a solicitation status where a contract is being solicited, a contract waiting status where the procedures for the fixed-term contract have already been completed and a specified waiting period has passed before the start date of use, or a contract underway status where the procedures for the fixed-term contract have already been completed and the waiting period has passed before the start date of use; and a function to permit hourly rentals in the solicitation status and contract waiting status and to prohibit hourly rentals in the contract underway status.

[0009] With the above configuration, hourly parking is permitted when a fixed-term contract has not been made and the contract is being solicited (solicited status). Even if a fixed-term contract has already been made, hourly parking is permitted even if the waiting period is still ahead of the start date of use when fixed-term use becomes possible (contract waiting status). In contrast, if a fixed-term contract has already been made and the period until the start date of use is less than the waiting period (contract underway status), hourly parking is prohibited.

[0010] After the start date of use (the start of regular use of the parking lot), the parking lot is used on a regular basis and cannot be rented out to a third party for an hourly basis. Furthermore, even if it is before the start date of use, there is a possibility that a third party may continue to park their car until the start date of use, which may interfere with regular use or interfere with preparations for regular use, resulting in trouble.

[0011] A specified waiting period is taken into consideration, and hourly rental is permitted if there is sufficient time until the start date of use, but is prohibited as the start date of use approaches. With this configuration, even after a fixed-term contract is made, hourly rental is permitted to the extent that it is unlikely to cause problems with the start of fixed-term use, making it possible to efficiently manage hourly parking lot rentals.

[0012] The system may further include a rental parking lot information generation unit that generates identification information for the parking lot for which hourly rental is permitted, and a usage reception unit that accepts applications to use the parking lot for which hourly rental is permitted, and the usage reception unit may accept applications to use the parking lot corresponding to the identification information by inputting the identification information.

[0013] With this configuration, the parking lot requested for use is identified by the identification information, and an application for use of the identified parking lot is accepted. Also, the user can apply for hourly parking by simply confirming and selecting the identification information. This simplifies the application process and makes the management of hourly parking more efficient.

[0014] The identification information may also include location information indicating a location of the parking lot.

[0015] With this configuration, the user can select a parking lot by taking into consideration the location of the parking lot.

[0016] The parking lot may further include a parking lot rental display management unit that displays the identification information on a terminal that can be used by the hourly rental user, and the usage reception unit may accept an application to use the parking lot by selecting the identification information on the terminal.

[0017] With this configuration, a user can apply for hourly parking by selecting the identification information of the parking lot he or she wishes to use from the candidate identification information displayed on any terminal. This improves the convenience of application and makes the management of hourly parking more efficient.

[0018] The system may further include a notification management unit that receives notifications that parking has occurred in at least one of the parking lots where hourly rental is permitted but applications for use are not being accepted, and the parking lots where hourly rental is prohibited.

[0019] With this configuration, it is possible to receive reports of illegal parking in the parking lot (without a fixed-term contract or application for hourly rental). This makes it possible to take measures against illegal parking, and allows for efficient management of hourly rental of the parking lot. [Brief description of the drawings]

[0020] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration for managing parking lots used by users. [Diagram 2] FIG. 1 is a diagram illustrating a schematic flow of managing a parking lot. [Diagram 3] FIG. 1 is a diagram illustrating a configuration of a usage contract system. [Figure 4] FIG. 13 is a diagram illustrating a flow for soliciting subscriptions and entering into a usage contract. [Diagram 5] FIG. 1 is a diagram illustrating a configuration of a lending management system. [Figure 6] FIG. 13 is a diagram illustrating a flow for managing hourly rentals. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] [Parking lot management] The parking lot management for managing the parking lot P will be described with reference to FIG. 1 and FIG.

[0022] A manager such as a business operator or owner manages multiple parking lots P, which are individual plots of parking lot land, as managed properties. Each parking lot P is rented out for regular use such as monthly parking, or for temporary rental by the hour (temporary use). Users use the rented parking lot P on a regular basis, and third parties use the parking lot P temporarily.

[0023] The administrator manages the parking lot P using a parking lot management system 3 constructed on a server 2 or the like. The parking lot management system 3 includes at least one of a usage contract system 4, a rental management system 5, and other management systems, and performs various management operations for the parking lot P. The usage contract system 4 processes usage contracts related to regular use of the parking lot P. The rental management system 5 accepts applications for temporary use (hourly rental) of the parking lot P, and manages the temporary use (hourly rental) of the parking lot P.

[0024] A user or a third party (hereinafter sometimes simply referred to as a user) uses a terminal 7 to access the parking lot management system 3 of the server 2 via the Internet 8 and applies for a usage contract (fixed-term contract) or hourly rental. The terminal 7 is a PC, mobile terminal, smartphone, etc. that has a display unit 7A and can be used by the user.

[0025] For example, the parking lot management system 3 first determines whether or not there are any vacant parking lots P that it manages that have no contract for use (step #1 in FIG. 2).

[0026] Next, the parking lot management system 3 executes a user solicitation process for soliciting user contracts for the vacant parking lots (step #2 in FIG. 2).

[0027] Next, the parking lot management system 3 judges whether or not an application for a usage contract has been submitted for each parking lot P that is accepting usage contracts (step #3 in FIG. 2).

[0028] If no application for a usage contract has been made (step #3 No in FIG. 2), the parking lot management system 3 executes hourly rental management processing to rent out the parking lot P by the hour (step #4 in FIG. 2). If no application for hourly rental has been made or if the hourly rental has ended, the parking lot management system 3 continues the user recruitment processing (step #2 in FIG. 2).

[0029] If an application for a usage contract has been made (Step #3 Yes in FIG. 2), the parking lot management system 3 executes usage contract processing (Step #5 in FIG. 2). The usage contract processing is a process for executing a fixed-term contract (usage contract) that allows the user to use the parking lot P on a regular basis, and specifically, a process for generating contract data 34 (see FIG. 3) that corresponds to the contract and concluding the usage contract.

[0030] Even if a usage contract has been made, if there is sufficient time before the actual use, the parking lot P under the usage contract can be temporarily rented by the hour. Therefore, as described later, the parking lot management system 3 judges whether there is sufficient time before the actual use (before the parking lot is used) (step #6 in FIG. 2).

[0031] If there is leeway in the schedule (Yes in step #6 in FIG. 2), the time-rental management process for the parking lot P under contract is carried out in the same manner as in step #4 during the period until use begins (step #7 in FIG. 2).

[0032] When use is started (step #6 No in FIG. 2), the parking lot management system 3 performs various management processes for the parking lot P under the usage contract (step #8 in FIG. 2).

[0033] For example, the parking lot management system 3 can manage hourly rentals for a parking lot P that is currently in regular use. In other words, even if regular use has started, it is possible to temporarily rent out the parking lot P by the hour during the period when the user is not using the parking lot P.

[0034] Therefore, as will be described later, the parking lot management system 3 judges whether or not it is a period during which the parking lot P is not in use (unused period 39, see FIG. 3) (step #9 in FIG. 2).

[0035] If it is the unused period 39 (Yes in step #9 of Figure 2), during the unused period 39, similar to steps #4 and #7, the parking lot management system 3 executes the time rental management process for the contracted parking lot P (step #10 of Figure 2).

[0036] If it is not an unused period 39 (No in step #9 in FIG. 2), the parking lot management system 3 determines whether the fixed-term contract has expired (step #11 in FIG. 2), and continues various fixed-term management processes (step #8 in FIG. 2) until it expires (Yes in step #11 in FIG. 2).

[0037] [Recruitment and Usage Agreement] Next, the recruitment and usage contract process for making a fixed-term contract (usage contract) for the parking lot P will be described with reference to FIGS. 3 and 4 while also referring to FIGS.

[0038] The usage contract system 4 performs solicitation and usage contracts for regular use of the parking lot P. The usage contract system 4 executes usage solicitation processing (usage solicitation method and usage solicitation program) and usage contract processing (usage contract method and usage contract program).

[0039] The usage contract system 4 includes a processor (computer) such as a CPU, and the operation of each functional block is controlled by the processor. The usage contract system 4 includes a vacancy display management unit 11, a cost display management unit 12, an input screen management unit 13, an acquisition unit 14, a contract generation unit 15, a signature management unit 16, a contract management unit 18, a cost management unit 21, an hourly rental management unit 23, and a memory unit 25.

[0040] The usage contract system 4 is not limited to being composed of the functional blocks shown in FIG. 3, and may be composed of any functional blocks. For example, each functional block of the usage contract system 4 may be further subdivided, or conversely, some or all of each functional block may be combined. The functions of the usage contract system 4 may be realized by a method (user solicitation method / user contract method) executed by any functional block, not limited to the above-mentioned functional blocks. Some or all of the functions of the usage contract system 4 may be composed of software. A program related to the software (user solicitation program / user contract program) is stored in any storage device such as the storage unit 25, and is executed by a processor (computer) such as a CPU provided in the parking management system 3 or the usage contract system 4, or a processor (computer) provided separately. For example, some or all of the processing of the program may be executed by a processor mounted on a device provided separately from the server 2.

[0041] <Application process> As part of the solicitation and usage contract process, the usage solicitation process is executed first. The parking lot management system 3 or the usage contract system 4 generates in advance identification information 28 for the parking lots P that it manages (the parking lots to be used by the user) and stores it in the storage unit 25 (step #21 in FIG. 4). The identification information 28 is information that identifies each parking lot P that it manages, and includes information on whether or not a usage contract (fixed-term contract) has already been concluded. In addition, the parking lot management system 3 or the usage contract system 4 stores in advance contract terms 31 that are in one-to-one correspondence with each parking lot P, i.e., the identification information 28.

[0042] Next, the vacant display management unit 11 determines from the identification information 28 whether or not a usage contract (fixed-term contract) has already been concluded for each parking lot P, and selects parking lots P (vacant parking lots) for which a usage contract (fixed-term contract) has not been concluded and for which usage contracts are being solicited. Then, the vacant display management unit 11 displays the identification information 28 of the vacant parking lots on the display unit 7A (vacant information display screen) of the terminal 7 that can be used by the user (step #22 in FIG. 4).

[0043] Specifically, the vacant display management unit 11 causes the display unit 7A of the terminal 7 to display an application form (application screen) on which identification information 28 of vacant parking lots available for usage contract is displayed. For example, the application form can be configured such that an application generated by the usage contract system 4 or the vacant display management unit 11, etc. is distributed via the Internet 8 and displayed on the terminal 7 that has downloaded the application.

[0044] The storage unit 25 can store in advance, as information on each parking lot P, cost information 29, which is information on costs related to regular use. In this case, the cost display management unit 12 may link the cost information 29 with the identification information 28 and display it on the application form displayed on the display unit 7A (cost information display screen) of the terminal 7. The cost information 29 may include a security deposit and the like in addition to the monthly usage fee (regular usage fee). The cost information 29 may also include a usage fee calculated on a pro rata basis when a contract is made in the middle of a regular period.

[0045] That is, the application form displays vacant parking lots available for a usage contract (fixed-term contract) and information such as identification information 28 and cost information 29 of the vacant parking lots. The identification information 28 may also include location information 30 such as map information of the parking lot P.

[0046] Next, the input screen management unit 13 displays the input screen 32 on the display unit 7A of the terminal 7, where the user can enter information (step #23 in FIG. 4). Specifically, the input screen management unit 13 displays the input screen 32 on the application form.

[0047] When applying for a usage contract (fixed-term contract) for a parking lot P (vacant parking lot), a user checks the information displayed on the application form to select the parking lot P for which the user is applying, and inputs the identification information 28 of the parking lot P for which the user is applying from the input screen 32. The information input from the input screen 32 is transmitted to the usage contract system 4 via the Internet 8. Specifically, the input screen 32 is an application button, and the application operation can be accepted by pressing (tapping) the application button with one piece of identification information 28 selected and displayed on the application form. Note that the input screen 32 may be configured to list the identification information 28 of parking lots P (vacant parking lots) for which applications can be made, and by tapping one piece of identification information 28, the application operation to use the parking lot P corresponding to that identification information 28 is accepted.

[0048] Next, the acquisition unit 14 acquires the information input from the input screen 32 (step #24 in FIG. 4). Specifically, the acquisition unit 14 acquires the identification information 28 of the parking lot P (vacant parking lot) input (selected) by the user, and stores it in the memory unit 25 as the identification information 28 of the parking lot P (vacant parking lot) for which an application has been accepted.

[0049] <User contract processing> When the identification information 28 is acquired, the usage contract system 4 executes usage contract processing.

[0050] First, the contract creation unit 15 reads out the contract terms 31 corresponding to the acquired identification information 28 from the storage unit 25. The contract terms 31 are various information related to the contract data 34, and include the cost information 29. The contract data 34 corresponds to the contract of the usage contract (fixed-term contract).

[0051] Then, the contract creating unit 15 automatically creates contract data 34 from the read contract terms 31 (step #25 in FIG. 4).

[0052] Next, the signature management unit 16 prompts the user to input the electronic signature 36 via the application form. The user inputs the electronic signature 36 via the terminal 7 (input screen 32). The signature management unit 16 acquires the input electronic signature 36 via the Internet 8 and stores it in the memory unit 25 (step #26 in FIG. 4).

[0053] Next, the contract management unit 18 adds the acquired electronic signature 36 to the generated contract data 34 to conclude a usage contract (step #27 in FIG. 4). That is, the contract management unit 18 links the contract data 34 with the electronic signature 36 to conclude a usage contract that permits the user to use the parking lot P to be used. Specifically, the contract management unit 18 displays the contract data 34 on the display unit 7A of the terminal 7 and enables the input of the electronic signature 36 from the terminal 7. Then, the contract management unit 18 determines that the usage contract has been concluded by confirming the acquisition of the electronic signature 36 and the input of a predetermined initial fee. At this time, the contract management unit 18 may accept the input of a usage plan for the parking lot P. The usage plan includes whether or not hourly rental is possible, a method of extending the contract, and the like, which will be described later.

[0054] In this way, the usage contract system 4 can conclude a usage contract (fixed-term contract) for the parking lot P simply by acquiring the identification information 28 of the parking lot P for which the user is applying to use the parking lot P and the user's digital signature 36. Therefore, the usage contract for the parking lot P can be easily made.

[0055] In addition, the user can enter into a contract (fixed-term contract) for using the parking lot P simply by inputting the identification information 28 and the electronic signature 36 via the application form, making it easy to enter into a contract for using the parking lot P.

[0056] Next, the expense management unit 21 accepts input of a method (payment method 38) for paying the usage fee for the use of the parking lot P (step #28 in FIG. 4). Specifically, the expense management unit 21 enables the terminal 7 to display a usage form for the parking lot P for which a usage contract has been made, and the user inputs the payment method 38 for various usage fees such as a regular usage fee and a security deposit via the usage form. Here, the usage form can be configured such that an application generated by the usage contract system 4 or the contract management unit 18 or the like is distributed via the Internet 8 and is displayed on the terminal 7 to which the application has been downloaded. The usage form can be used to make various settings for the parking lot P for which a usage contract has been made, and to apply for hourly rental of the parking lot P, and can be accessed not only by regular users but also by third parties who have registered to use hourly rental of the parking lot P.

[0057] The expense management unit 21 acquires (accepts) the entered payment method 38, stores it in the memory unit 25, and manages the receipt of the usage fee according to the payment method 38. The payment method 38 is a credit payment, payment by electronic money, bank transfer, etc., and includes various information such as credit information required for these payments. Upon input of the payment method 38, the contract management unit 18 permits the use of the parking lot P under the usage contract.

[0058] In this way, by accepting the payment method 38 for the usage fee and managing the payment (receipt), the usage contract system 4 can manage not only the usage contract but also the subsequent payment of the usage fee. As a result, the management of the parking lot P can be easily performed.

[0059] Furthermore, the hourly rental management unit 23 manages hourly rentals to third parties for at least one of parking lots P (vacant parking lots) for which usage contracts are being solicited and parking lots P that are unused during the unused period 39 (hourly rental management processing, step #29 in Figure 4).

[0060] For example, an empty parking lot is a parking lot P that is accepting applications for regular use, but no usage contract (regular contract) has been made, and the parking lot P is not in use. Even in parking lots P for which a regular contract has been made, there may be times when the parking lot is temporarily unused (unused period 39). In such a situation, it is possible to temporarily rent the parking lot to a third party by the hour.

[0061] The hourly rental management unit 23 can manage hourly rental to third parties for parking lots P for which usage contracts are being solicited. In addition, the hourly rental management unit 23 can accept the setting of unused periods 39 during which parking lots P for which usage contracts have been signed are not used, and can manage hourly rental of parking lots P to third parties during unused periods 39.

[0062] With this configuration, unused parking lots P can be rented out by the hour, allowing efficient use of the parking lots P and generating revenue.

[0063] In addition, when a usage contract (fixed-term contract) is concluded, the contract management unit 18 stores in the memory unit 25 contract information 53 including a contract status 51 indicating that a usage contract (fixed-term contract) has been concluded (whether the procedure for the fixed-term contract has already been completed or contract solicitation is underway) and a usage start date 52, in association with the parking lot P (identification information 28) with which the usage contract (fixed-term contract) was concluded.

[0064] [Lending Management] Next, a rental management process for managing hourly rental of the parking lot P will be described with reference to FIGS. 5 and 6 while also referring to FIGS.

[0065] The rental management system 5 includes a processor (computer) such as a CPU, and the operation of each functional block is controlled by the processor. The rental management system 5 includes a contract status acquisition unit 41, a status determination unit 42, a rental control unit 43, a rental parking information generation unit 45, a rental parking display management unit 46, a usage reception unit 47, and a memory unit 49.

[0066] The rental management system 5 is not limited to being composed of functional blocks as shown in FIG. 5, and may be composed of any functional blocks. For example, each functional block of the rental management system 5 may be further subdivided, or conversely, some or all of the functional blocks may be combined. The functions of the rental management system 5 may be realized by a method (rental management method) executed by any functional block, not limited to the above-mentioned functional blocks. Some or all of the functions of the rental management system 5 may be composed of software. A program related to the software (rental management program) is stored in any storage device such as the storage unit 49, and is executed by a processor (computer) such as a CPU provided in the parking lot management system 3 or the rental management system 5, or a processor (computer) provided separately. For example, some or all of the processing of the program may be executed by a processor mounted on a device provided separately from the server 2.

[0067] The rental management system 5 performs rental management processing (rental management method / rental management program) by determining the usage status and contract status of the parking lot P and managing the hourly rental of the parking lot P (hourly rental management processing).

[0068] First, the contract status acquisition unit 41 acquires the contract status 51 of each parking lot P, contract information 53 including the start date of use 52, waiting period 54, and unused period 39 stored in the memory unit 49 (step #41 in FIG. 6).

[0069] The contract information 53 is information stored in association with the parking lot P (identification information 28) with which the usage contract (fixed-term contract) was concluded, as contract information 53 including contract status 51 indicating that the usage contract (fixed-term contract) has been concluded (whether the procedures for the fixed-term contract have already been completed or contract solicitation is underway) and start date of use 52 when the usage contract (fixed-term contract) is concluded.

[0070] The waiting period 54 is a period set in advance and stored in the memory unit 49, and is the length of the period during which hourly rental is permitted after the procedure for the usage contract (fixed-term contract) has been completed and there is a margin of time until the usage start date 52. The unused period 39 is information input (set) by the user and stored in the memory unit 49 as a time period (period) during which the parking lot P for which the usage contract (fixed-term contract) has been made is not used temporarily.

[0071] Next, the status determination unit 42 checks the contract status 51 of the contract information 53 for each parking lot P and determines whether the application procedure for a usage contract (fixed-term contract) has already been completed for each parking lot P (step #42 in FIG. 6).

[0072] For parking lot P where it has been determined that the application procedure for the usage contract (fixed-term contract) has already been completed (step #42 Yes in FIG. 6), the status determination unit 42 further checks the usage start date 52 and waiting period 54 in the contract information 53 to determine whether the time is more than the waiting period 54 before the usage start date 52 (step #43 in FIG. 6). Note that the status determination unit 42 recognizes a situation where the usage contract (fixed-term contract) procedure has already been completed and the waiting period 54 has passed since the usage start date 52 as an under-contract status.

[0073] The status determination unit 42 determines whether or not the parking lot P that has been determined to be in a contract status (step #43 No in FIG. 6) is in the unused period 39 (step #44 in FIG. 6). Specifically, the status determination unit 42 determines that the parking lot P that is currently included in the unused period 39 is a parking lot P in the unused period 39. In other words, the status determination unit 42 determines that the parking lot P for which the unused period 39 is not set is not a parking lot P in the unused period 39, and determines that the parking lot P for which the currently not included in the unused period 39 is not a parking lot P in the unused period 39 even if the unused period 39 is set.

[0074] Then, for parking lots P that are determined not to be in the unused period 39 (No in step #44 of FIG. 6), the rental control unit 43 prohibits hourly rental (step #45 of FIG. 6). Specifically, the rental control unit 43 performs control so that the identification information 28 of parking lots P for which hourly rental is prohibited is not displayed on the usage form.

[0075] The status determination unit 42 also determines that a parking lot P for which it has been determined that the application procedure for a usage contract (fixed-term contract) has not been completed (No in step #42 of FIG. 6) is a parking lot P in an open-booking status where a usage contract (fixed-term contract) is currently being accepted. The status determination unit 42 also determines that a parking lot P for which it has been determined that the procedure for a usage contract (fixed-term contract) has already been completed and that the waiting period 54 has elapsed since the usage start date 52 (Yes in step #43 of FIG. 6) is a parking lot P in a waiting-for-contract status. The status determination unit 42 also determines that a parking lot P for which it has been determined that the usage contract (fixed-term contract) has been completed and that the waiting period 54 has elapsed since the usage start date 52 (Yes in step #44 of FIG. 6) is an unused parking lot P.

[0076] Then, the rental control unit 43 allows hourly rental for parking lots P that are in the solicitation status, contract waiting status, and unused status (step #46 in FIG. 6). Specifically, the rental control unit 43 lists on the usage form the identification information 28 of the parking lot P for which hourly rental has been allowed. Thereafter, hourly rentals are solicited, and an hourly rental management process is executed to manage the hourly rentals. More specifically, the rental control unit 43 deletes the identification information 28 that was listed on the usage form as the solicitation status, from the usage form at the time an application for use is made. Thereafter, if the rental control unit 43 determines that the parking lot P is in the contract waiting status or unused status, it lists the identification information 28 of the parking lot P again on the usage form.

[0077] <Hourly rental management processing> As part of the hourly rental management process, first, the rental parking lot information generating unit 45 generates the identification information 28 of the parking lot P for which hourly rental is permitted (step #47 in FIG. 6). Specifically, the rental parking lot information generating unit 45 selects and acquires the identification information 28 corresponding to the parking lot P for which hourly rental is permitted from the identification information 28 of each parking lot P previously stored in the memory unit 49.

[0078] Next, the parking lot rental display management unit 46 displays the identification information 28 generated by the parking lot rental information generation unit 45 on the display unit 7A of the terminal 7 that can be used by the hourly rental user (third party) (step #48 in FIG. 6). Specifically, the parking lot rental display management unit 46 displays the identification information 28 of the parking lot P available for hourly rental on the usage form displayed on the display unit 7A of the terminal 7. A third party looking for a parking lot P that is seeking (available for) hourly rental can easily search for the parking lot P by checking the identification information 28 displayed on the usage form. At this time, the identification information 28 may include location information 30 that is information indicating the location of the parking lot P. This allows the third party to easily search for a parking lot P that is available for hourly rental while checking the location of the parking lot P.

[0079] The third party determines the parking lot P for which the third party wishes to apply for hourly rental from the identification information 28 displayed on the display unit 7A (usage form) of the terminal 7, and applies for (inputs) the hourly rental of the parking lot P by selecting the identification information 28 on the terminal 7. The identification information 28 of the requested parking lot P is transmitted from the terminal 7 to the rental management system 5.

[0080] The usage acceptance unit 47 then acquires the identification information 28 sent from the terminal 7 (step #49 in FIG. 6) and accepts an application for hourly rental of the parking lot P (step #50 in FIG. 6). If an appropriate application is accepted, the usage acceptance unit 47 causes the terminal 7 (usage form) to display a message indicating that usage has been permitted and detailed usage instructions. On the other hand, if an inappropriate application is accepted, the usage acceptance unit 47 causes the terminal 7 (usage form) to display a message indicating that usage has been rejected.

[0081] The rental parking lot information generating unit 45, the rental parking lot display management unit 46, and the usage reception unit 47 correspond to the above-mentioned hourly rental management unit 23 (see FIG. 3).

[0082] Thereafter, the rental management system 5 performs management during the rental period, such as providing information about hourly rentals, managing payment of fees, and monitoring unauthorized use of the parking lot P (step #51 in FIG. 6).

[0083] For example, the rental management system 5 may further include a report management unit 48, which may receive a report that an unauthorized parking lot P is being used. When a user or a third party who can use the usage form finds that an unauthorized parking lot P is being used, they can report this via the usage form. Unauthorized use of a parking lot P may mean, for example, that a car that is not used regularly is parked in at least one of a parking lot P where hourly rental is permitted but applications for use are not being accepted, and a parking lot P where hourly rental is prohibited. Furthermore, this may include a car other than the applied car being parked in a parking lot P where applications for hourly rental are being accepted.

[0084] When such a report is received, the rental management system 5 can inform regular users or those who have applied for hourly rentals of the information. In addition, the manager of the parking lot P may contact the owner of the vehicle that is parked incorrectly, if possible. This allows the appropriate use of the parking lot P to be maintained.

[0085] [Another embodiment] (1) In each of the above embodiments, the usage solicitation process is not limited to the above configuration and may be performed in any configuration. The usage contract system 4 may not include the space display management unit 11, the cost display management unit 12, and the input screen management unit 13, and may be configured to execute the process up to concluding the usage contract (periodic contract) after accepting an application for regular use. This configuration simplifies the configuration of the usage contract system 4 and allows the usage contract (periodic contract) to be concluded in a more flexible configuration.

[0086] (2) In each of the above embodiments, the usage contract system 4 may be configured without at least one of the expense management unit 21 and the hourly rental management unit 23.

[0087] (3) In each of the above embodiments, the status determination unit 42 may not determine whether or not it is an unused period 39, and the rental control unit 43 may be configured to permit hourly rental in the recruiting status and waiting status, and to prohibit hourly rental in the under-contract status. In other words, the parking lot P where regular use has started may not be eligible for hourly rental.

[0088] (4) In each of the above embodiments, the time rental management process may be performed in any configuration, not limited to the above configuration. The rental management system 5 may be configured without the report management unit 48. With such a configuration, the configuration of the rental management system 5 can be simplified.

[0089] (5) In each of the above embodiments, the application form and usage form may be of any configuration, and applications for a usage contract (fixed-term contract) for a parking lot P, various settings for a parking lot P under a usage contract, applications for hourly rental of the parking lot P, etc. may be made in any configuration without using an application form or usage form.

[0090] (6) In each of the above embodiments, the usage reception unit 47 is not limited to being configured to accept an application for hourly rental by selecting the identification information 28 displayed on the terminal 7 by the parking lot rental display management unit 46. The rental management system 5 may not be equipped with a parking lot rental display management unit 46, and the usage reception unit 47 may accept an application for parking lot P by selecting the parking lot P in any configuration. [Industrial Applicability]

[0091] The present invention can be applied in managing the temporary rental of parking spaces to third parties. [Explanation of symbols]

[0092] 5. Loan Management System 7 Terminal 41 Contract Status Acquisition Department 42 Situation Judgment Section 43 Loan Control Unit 45 Parking lot information generation unit 46 Parking Lot Display and Management Department 47 Reception Desk 48 Report Management Department 49 Memory section 51 Contract Status 52 Start date of use 53 Contract Information 54 Waiting period P Parking lot

Claims

1. A rental management system that manages hourly rentals, which are temporary rentals of parking spaces under fixed-term contracts to third parties, comprising: a contract status acquisition unit that acquires contract information including a contract status indicating whether the procedure for the fixed term contract of the parking lot has already been completed or is currently accepting contracts and a use start date; a status determination unit that determines, based on the contract status and the contract information, whether the status is a solicitation status in which the contract is being solicited, a contract waiting status in which the procedure for the fixed-term contract has already been completed and a predetermined waiting period has elapsed since the start date of use, or a contract underway status in which the procedure for the fixed-term contract has already been completed and a time point that is the waiting period before the start date of use has passed; A rental management system comprising a rental control unit which permits the hourly rental in the recruitment status and the contract waiting status, and prohibits the hourly rental in the contract status.

2. a parking lot information generating unit that generates identification information of the parking lot for which the hourly rental is permitted; The parking lot may be provided with a parking space for which the parking lot is permitted to be rented by the hour. The rental management system according to claim 1 , wherein the usage acceptance unit accepts an application to use the parking lot corresponding to the identification information by inputting the identification information.

3. The rental management system according to claim 2 , wherein the identification information includes location information indicating a location of the parking lot.

4. The parking lot display management unit further includes a display unit for displaying the identification information on a terminal that can be used by the user of the parking lot for hourly rental. The rental management system according to claim 2 , wherein the utilization acceptance unit accepts an application for utilization of the parking lot by a selection operation of the identification information being performed on the terminal.

5. The rental management system of claim 1, further comprising a notification management unit that receives notifications that parking has occurred in at least one of the parking lots where hourly rental is permitted but applications for use are not being accepted, and the parking lots where hourly rental is prohibited.

6. A method for managing hourly parking, which is a temporary rental of a parking lot under a fixed-term contract to a third party, comprising the steps of: acquiring contract information including a contract status indicating whether the fixed-term contract procedure for the parking lot has already been completed or is currently open for contracts and a start date of use; a step of judging, based on the contract status and the contract information, whether the status is a solicitation status in which the contract is being solicited, a contract waiting status in which the procedure for the fixed-term contract has already been completed and a predetermined waiting period has elapsed since the start date of use, or a contract status in which the procedure for the fixed-term contract has already been completed and the waiting period has elapsed since the start date of use; A rental management method comprising a step of permitting the hourly rental in the recruiting status and the contract waiting status, and prohibiting the hourly rental in the contract underway status.

7. A rental management program for managing hourly rentals, which are temporary rentals of parking spaces under fixed-term contracts to third parties, comprising: A function for acquiring contract information including a contract status indicating whether the fixed-term contract procedure for the parking lot has already been completed or is currently open for contracts, and a start date of use; a function of determining, based on the contract status and the contract information, whether the status is a solicitation status in which the contract is being solicited, a contract waiting status in which the procedure for the fixed-term contract has already been completed and a predetermined waiting period has elapsed since the start date of use, or a contract status in which the procedure for the fixed-term contract has already been completed and a time point that is the waiting period before the start date of use has passed; a rental management program that causes a computer to execute a function of permitting the hourly rental in the recruiting status and the contract waiting status, and prohibiting the hourly rental in the contract underway status.

Images