Shared property management system, shared property management method, and shared property management program
The shared property management system addresses inefficiencies in managing shared properties by identifying usable candidates and granting authority based on usage status, enhancing reservation and allocation efficiency.
Patent Information
- Application Number
- JP2020188184
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-11-11
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-11-11
AI Technical Summary
Existing systems for managing shared properties, such as aerial work vehicles at construction sites, fail to consider the varying usage methods based on the situation of the shared property, leading to inefficient management.
A shared property management system that includes a control unit, shared property information storage, and usage application to identify usable candidates and grant authority based on the usage status, allowing efficient allocation and reservation of shared properties.
Enables efficient management and allocation of shared properties by considering their usage status, facilitating accurate reservations and spot usage, reducing effort, and ensuring timely access.
Smart Images

Figure 0007593062000001 
Figure 0007593062000002 
Figure 0007593062000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a shared object management system, a shared object management method, and a shared object management program for managing a plurality of shared objects shared by a plurality of users. [Background technology]
[0002] In order to make effective use of common items, sharing of common items is sometimes carried out. Also, at a construction site, equipment shared by multiple workers may be managed. For example, at a construction site, multiple users may share a lift vehicle.
[0003] For example, as shown in Fig. 12, multiple aerial work vehicles may be managed using a usage schedule 500. A person who wishes to use the aerial work vehicle checks the usage schedule 500 and applies to use the aerial work vehicle during its free time when it is not in use or reserved. However, when multiple users share the vehicle or when the vehicles are located far apart, it is difficult to make an accurate application for use.
[0004] Technology for reserving shared equipment and materials at a construction site is also being considered (see, for example, Patent Document 1). In the technology disclosed in this document, an information processing system manages equipment and materials shared by multiple workers at a construction site. In this case, the area at the construction site where the equipment and materials are located is identified based on a signal transmitted from a transmitting means provided on the equipment and materials. Furthermore, the operation status and reservation status of the equipment and materials are identified. Then, specific information about the equipment and materials in the area is output, and reservation information about the operation information and reservation status of the equipment and materials is output. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2019-175224 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, even if a reservation is made for the use of a shared property, the method of use may differ depending on the condition of the property. Unless this situation is taken into consideration, it is not possible to efficiently manage the shared property. [Means for solving the problem]
[0007] A shared object management system for solving the above problems includes a control unit that communicates with a user terminal, a shared object information storage unit that records the usage status of a shared object, and a usage application information storage unit that records an application to use the shared object. When the control unit acquires an application to use a shared object from the user terminal and the usage application information storage unit cannot identify an available shared object, the control unit uses the shared object information storage unit to identify each usage status, identifies available shared object candidates based on the usage status, and grants the user terminal the authority to use a shared object selected from the available shared object candidates. Effect of the Invention
[0008] According to the present invention, it is possible to efficiently manage a plurality of shared objects shared by a plurality of users. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is an explanatory diagram of a system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is an explanatory diagram of a usage scene of this embodiment. [Diagram 3] FIG. 2 is an explanatory diagram of a hardware configuration of the present embodiment. [Figure 4] 4A is an explanatory diagram of a work vehicle information storage unit, FIG. 4B is an explanatory diagram of a user information storage unit, and FIG. 4C is an explanatory diagram of a utilization application information storage unit of the present embodiment. [Diagram 5] FIG. [Figure 6] FIG. [Figure 7] FIG. [Figure 8] FIG. 11 is an explanatory diagram of a processing procedure according to another embodiment. [Figure 9] FIG. 11 is an explanatory diagram of a processing procedure according to another embodiment. [Figure 10] FIG. 11 is an explanatory diagram of a processing procedure according to another embodiment. [Figure 11] FIG. 11 is an explanatory diagram of a processing procedure according to another embodiment. [Figure 12] FIG. 1 is an explanatory diagram of a conventional usage schedule. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of a shared property management system, a shared property management method, and a shared property management program will be described with reference to Figures 1 to 7. In this embodiment, the shared property management system will be described as a shared property management system used for managing the use of multiple aerial work platforms (shared property) at a construction site of a multi-story structure.
[0011] In this embodiment, as shown in FIG. 1, a control device 10, a management server 20, a user terminal 30, and a management terminal 32 are used. The control device 10 is provided in an aerial work vehicle V1. In this embodiment, a reservation application for use of the aerial work vehicle V1 shared by users is accepted by the day before. Then, the aerial work vehicle V1 is allocated in response to a reservation application for use on the day. Furthermore, a spot use application for the aerial work vehicle V1 on the day is accepted. Here, spot use is use that has not been reserved for use the day before or earlier, for example use for which a time period for use is not specified.
[0012] In this embodiment, as shown in Fig. 2, it is assumed that an application for use is made on the day of use at a multi-storey construction site. In this case, a prospective user P1 makes an application for use using a user terminal 30, and the management server 20 checks the location and operating status (usage status) of the aerial work vehicle V1. The aerial work vehicle V1 can be in an available state ("empty" in the figure), in operation ("operating" in the figure), or not in operation but reserved ("reserved" in the figure). Then, the available aerial work vehicle V1 is identified as a candidate for use according to the location and operating status.
[0013] (Hardware configuration description) 3, a hardware configuration of an information processing device H10 that constitutes the control device 10, management server 20, user terminal 30, and management terminal 32 will be described. The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is an example, and it may be realized by other hardware.
[0014] The communication device H11 is an interface that establishes a communication route with other devices and transmits and receives data, and is, for example, a network interface card or a wireless interface.
[0015] The input device H12 is a device that accepts input of various information, such as a mouse, a keyboard, a camera (photographing device), etc. The display device H13 is a display or the like that displays various information.
[0016] The storage device H14 is a storage device that stores data and various programs for executing various functions of the control device 10, the management server 20, the user terminal 30, and the management terminal 32. Examples of the storage device H14 include a ROM, a RAM, and a hard disk.
[0017] The processor H15 uses the programs and data stored in the storage device H14 to control each process in the control device 10, the management server 20, the user terminal 30, and the management terminal 32. Examples of the processor H15 include a CPU and an MPU. The processor H15 expands the programs stored in the ROM, etc., into the RAM and executes various processes for each process.
[0018] The processor H15 is not limited to a processor that performs software processing for all the processes it executes. For example, the processor H15 may be equipped with a dedicated hardware circuit (e.g., an application specific integrated circuit: ASIC) that performs hardware processing for at least a part of the processes it executes. That is, the processor H15 may be configured as a circuit including: (1) one or more processors that operate according to a computer program (software); (2) one or more dedicated hardware circuits that execute at least a part of various processes; or (3) a combination thereof. The processor includes a CPU and memory such as RAM and ROM, and the memory stores program code or instructions configured to cause the CPU to execute processes. The memory, i.e., computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer.
[0019] (System Configuration) Next, each function of the shared property management system will be described with reference to FIG. The vehicle for high-altitude work V1 is a work vehicle that performs high-altitude work using a drive mechanism powered by a battery. A two-dimensional code image including a vehicle ID is attached to the vehicle for high-altitude work V1. Furthermore, the vehicle for high-altitude work V1 is equipped with a control device 10. The control device 10 acquires the charge amount (remaining amount) of the battery of the vehicle for high-altitude work V1 and controls the start of the drive mechanism. When starting the drive mechanism, the control device 10 communicates with a user terminal 30. In this embodiment, the control device 10 holds an unlocking key for managing the locking of a key box in which a start key of the vehicle for high-altitude work V1 is stored, and manages the start of the drive mechanism. When the vehicle for high-altitude work V1 is used, the user terminal 30 is used to unlock the key box and start the vehicle for high-altitude work V1. When the use of the vehicle for high-altitude work V1 is finished, the user terminal 30 is used to stop the vehicle for high-altitude work V1 and lock the key box.
[0020] The management server 20 is a computer system that manages the use of the aerial work platform V1. The management server 20 includes a control unit 21, a work platform information storage unit 22 as a shared property information storage unit, a user information storage unit 23, and a usage application information storage unit 24.
[0021] The control unit 21 performs processes (including a reservation stage, an allocation stage, a monitoring stage, etc.) to be described later. By executing a program for each process for this purpose, the control unit 21 functions as a reservation unit 211, an allocation unit 212, a monitoring unit 213, etc.
[0022] The reservation unit 211 executes a process of accepting a reservation application for use of the aerial work vehicle V1 and a spot use application. This reservation unit 211 holds data on the cut-off time for closing the acceptance of reservation applications (for example, the end time of work on the previous day at the construction site).
[0023] The allocation unit 212 executes a process of allocating the aerial work vehicle V1 in response to a utilization reservation application or a spot utilization application. The allocation unit 212 holds a work correspondence table relating to the vehicle type of the aerial work vehicle V1 to be used according to the work content. The monitoring unit 213 executes a process of monitoring the state of the aerial work vehicle V1.
[0024] As shown in Fig. 4(a), the work vehicle information storage unit 22, which serves as a shared property information storage unit, records a work vehicle management record 220 for each aerial work vehicle V1. This work vehicle management record 220 is recorded when an aerial work vehicle V1 is registered, and is updated based on information from the user terminal 30. The work vehicle management record 220 includes information related to the work vehicle ID, vehicle type, unlocking key, user ID, operating status, location, battery status, and requested allocation.
[0025] The vehicle ID data area stores data on an identifier for identifying each vehicle for work at height V1. The vehicle type data area records data relating to the type of this vehicle for work at height V1.
[0026] The unlocking key data area stores data relating to the unlocking key for starting the aerial work platform V1. The user ID data area records information for identifying the user who is using the vehicle for high-altitude work V1. In this embodiment, when the vehicle for high-altitude work V1 is not in operation, this field is left blank, and when the vehicle for high-altitude work V1 is in operation, the user ID of the user is recorded.
[0027] The operation status data area records information for identifying the operation status of the vehicle for high-altitude work V1. In this embodiment, if the vehicle for high-altitude work V1 is not in operation, this field is left blank, and if the vehicle for high-altitude work V1 is in operation, the application ID of the user is recorded.
[0028] The location data area records data relating to the location where the vehicle V1 is located. The battery status data area records data relating to the charge level of the battery of this vehicle for work at height V1. The application allocation data area records data related to an identifier (application ID) for identifying the application to which this vehicle for working at height V1 has been allocated.
[0029] As shown in Fig. 4(b), a user management record 230 for a user of the aerial work platform vehicle V1 is recorded in the user information storage unit 23. This user management record 230 is recorded when a user is registered. The user management record 230 includes information on the user ID, affiliation, user attributes, and contact information.
[0030] The user ID data area records data regarding an identifier for identifying this user. The affiliation data area records data about the business company or department to which the user belongs.
[0031] In the user attribute data area, data on the attributes of this user (for example, worker, site manager, etc.) is recorded. In the contact data area, data regarding the contact information of this user (for example, email address, IP address of the user terminal 30, etc.) is recorded.
[0032] As shown in Fig. 4(c), an application management record 240 for an application for use of the aerial work vehicle V1 is recorded in the utilization application information storage unit 24. This application management record 240 is recorded when a utilization reservation application or a spot utilization application is received from the user terminal 30. The application management record 240 includes information related to the application ID, application type, utilization location, utilization time, work content, applicant, and work vehicle.
[0033] The application ID data area records data regarding an identifier for identifying each application. The application type data area records data regarding an identifier for identifying the type of application (use reservation application or spot use application).
[0034] The usage location data area records data relating to the location where work is performed using the aerial work platform V1. In the use time data area, for a reservation application, data on the date and time (start time and end time) of work using the aerial work platform V1 is recorded. For a spot use application, data on the time required to work using the aerial work platform V1 is recorded.
[0035] The work content data area stores data on an identifier for identifying the work content to be performed using the vehicle for high-rise work V1. The vehicle type that can be used can be identified according to the work content.
[0036] The applicant data area records data regarding an identifier for identifying the user who made the application. The work vehicle data area records data regarding an identifier for identifying the aerial work vehicle V1 used in this application.
[0037] The user terminal 30 is a computer terminal used by a user who uses the aerial work vehicle V1. The user uses the user terminal 30 to apply for use and to communicate with the control device 10 of the aerial work vehicle V1. For this reason, a management application for managing the use of the aerial work vehicle V1 is installed in the user terminal 30. This management application holds the user ID of the user. Furthermore, the user terminal 30 is equipped with a location acquisition unit that uses a GPS (Global Positioning System) or signals from a wireless base station. By using this location information acquisition unit, the user's current location (latitude, longitude, and floor) can be identified. The management terminal 32 is a computer terminal used by a manager of the aerial work platform vehicle V1.
[0038] (Work vehicle management processing) Next, a process of the vehicle management method performed in the management server 20 configured as above will be described.
[0039] (Normal reservation process) First, the normal reservation process will be described with reference to Fig. 5. This process is carried out when a reservation for use of the vehicle for high-rise work V1 is applied for on or before the previous work day.
[0040] Here, the control unit 21 of the management server 20 executes a process for accepting a reservation application (step S101). Specifically, a user who wishes to reserve the use of the aerial work platform V1 starts the management application of the user terminal 30 and inputs "normal reservation". In this case, the user terminal 30 accesses the management server 20 and transmits a normal reservation application. This normal reservation application includes data related to the user ID of the management application. In this case, the reservation unit 211 of the control unit 21 outputs a reservation screen to the user terminal 30. Then, the reservation unit 211 acquires the use location, use time, and work content inputted on the reservation screen. The reservation unit 211 generates an application management record 240 to which an application ID is assigned, and records it in the application information storage unit 24. In this application management record 240, data related to a reservation application, work time, work content, and a user ID as an applicant are recorded.
[0041] Next, the control unit 21 of the management server 20 executes a process of determining whether the deadline has arrived (step S102). Specifically, the reservation unit 211 of the control unit 21 determines whether the current time is the deadline for the use reservation application.
[0042] If it is determined that the cut-off time has not arrived ("NO" in step S102), the control unit 21 of the management server 20 continues the process of accepting the reservation request (step S101).
[0043] On the other hand, if it is determined that the cut-off time has arrived (YES in step S102), the control unit 21 of the management server 20 executes a process for identifying the reservation application (step S103). Specifically, the allocation unit 212 of the control unit 21 extracts the reservation application to which the aerial work vehicle V1 needs to be allocated from the work vehicle information storage unit 22. Here, the application management record 240 in which the next work day is recorded in the usage time data area is extracted.
[0044] Next, the control unit 21 of the management server 20 executes a process for identifying the required work vehicles (step S104). Specifically, the allocation unit 212 of the control unit 21 identifies the work content of each extracted application management record 240. Next, the allocation unit 212 identifies the vehicle type corresponding to each work content using the work correspondence table. Then, the allocation unit 212 calculates the required number of vehicles for each vehicle type in response to the utilization reservation application for the next work day.
[0045] Next, the control unit 21 of the management server 20 executes a process to determine whether the number is sufficient (step S105). Specifically, the allocation unit 212 of the control unit 21 calculates the available number of aerial work vehicles V1 for each vehicle type and each usage time using the work vehicle information storage unit 22. Then, if the required number of each vehicle type is equal to or greater than the available number, the allocation unit 212 determines that the number is sufficient. On the other hand, if the available number of any vehicle type is insufficient, the allocation unit 212 determines that the number is insufficient.
[0046] If it is determined that the number is insufficient (if "NO" in step S105), the control unit 21 of the management server 20 executes an alert process (step S106). Specifically, the allocation unit 212 of the control unit 21 transmits an alarm message to the management terminal 32. This alarm message includes the reservation application and information regarding the vehicle type that is insufficient. In this case, the manager adjusts the application for the insufficient aerial work vehicle V1 or procures an aerial work vehicle V1 from elsewhere.
[0047] On the other hand, if it is determined that the number is sufficient (if "YES" in step S105), the control unit 21 of the management server 20 executes a vehicle allocation process according to the work content and location (step S107). Specifically, the allocation unit 212 of the control unit 21 identifies an available aerial work vehicle V1 according to the work content of each use application. Then, the allocation unit 212 identifies the location of each aerial work vehicle V1 using the work vehicle information storage unit 22. Next, the allocation unit 212 allocates each aerial work vehicle V1 to the use application so that there is no conflict in the use time and the sum of the distances between the location and the use location is the shortest. In this case, when one aerial work vehicle V1 is used multiple times per day, the distance between the previous use location and the subsequent use location is used.
[0048] Next, the control unit 21 of the management server 20 executes a schedule registration process (step S108). Specifically, the allocation unit 212 of the control unit 21 records the work vehicle ID of the allocated aerial work vehicle V1 in the application management record 240 of the utilization application information storage unit 24. Furthermore, the allocation unit 212 records the application ID of the allocated utilization application in the work vehicle management record 220 of the work vehicle information storage unit 22. When there are multiple utilization applications in one day, all application IDs are recorded in this data area.
[0049] Next, the control unit 21 of the management server 20 executes a contact process with the applicant terminal (step S109). Specifically, the allocation unit 212 of the control unit 21 transmits a schedule registration message to the user terminal 30 of the usage applicant. This message includes information regarding the work vehicle ID of the allocated aerial work vehicle V1.
[0050] (Use of aerial work platforms) Next, the process of using the aerial work platform will be described with reference to FIG. First, the user terminal 30 executes an unlocking application process (step S201). Specifically, when using the aerial work platform V1, the user starts the management application of the user terminal 30 and takes a picture of the two-dimensional code image attached to the aerial work platform V1. In this case, the user terminal 30 accesses the management server 20 and transmits an unlocking application. This unlocking application includes data related to the vehicle ID included in the two-dimensional code image and the user ID of the management application.
[0051] Next, the control unit 21 of the management server 20 executes a process of confirming the reservation authority (step S202). Specifically, the monitoring unit 213 of the control unit 21 acquires the work vehicle management record 220 of the vehicle ID included in the unlocking application from the work vehicle information storage unit 22. Next, the monitoring unit 213 acquires the application management record 240 of the application ID recorded in the work vehicle management record 220 from the utilization application information storage unit 24.
[0052] Next, the control unit 21 of the management server 20 executes a process of determining whether the authentication is complete (step S203). Specifically, the monitoring unit 213 of the control unit 21 checks whether the vehicle ID and user ID included in the unlocking application are recorded in the identified application management record 240. If the application management record 240 in which the vehicle ID and user ID included in the unlocking application are recorded can be identified, the monitoring unit 213 determines that the authentication is complete.
[0053] If the control unit 21 of the management server 20 is unable to identify the application management record 240 in which the user ID included in the unlocking application is recorded and determines that the authentication is not complete ("NO" in step S203), the control unit 21 of the management server 20 executes error processing (step S204). Specifically, the monitoring unit 213 of the control unit 21 transmits an error screen to the user terminal 30. This error screen includes a message indicating that the application for use cannot be confirmed.
[0054] On the other hand, if it is determined that the authentication is complete (if "YES" in step S203), the control unit 21 of the management server 20 executes a process for sending permission to unlock (step S205). Specifically, the monitoring unit 213 of the control unit 21 acquires the work vehicle ID recorded in the identified application management record 240. Next, the monitoring unit 213 extracts the work vehicle management record 220 of the acquired work vehicle ID from the work vehicle information storage unit 22. Then, the monitoring unit 213 records the application ID in the operating status data area, and deletes the application ID recorded in the application allocation data area. Furthermore, the monitoring unit 213 acquires the unlocking key recorded in the work vehicle management record 220, and transmits it to the user terminal 30.
[0055] Next, the user terminal 30 executes a process of transmitting an unlocking signal (step S206). Specifically, the management application of the user terminal 30 temporarily stores the unlocking key acquired from the management server 20. Then, the user terminal 30 transmits an unlocking signal to the control device 10 of the aerial work platform V1. This unlocking signal includes the unlocking key acquired from the management server 20.
[0056] Next, the control device 10 executes an unlocking process (step S207). Specifically, if the unlocking key stored in advance in the control device 10 matches the unlocking key included in the unlocking signal, the control device 10 unlocks the key box. This allows the user to start and use the aerial work platform V1. The user then uses the aerial work platform V1 to perform the desired work.
[0057] Next, when the work is finished, the user terminal 30 executes a process of transmitting a locking signal (step S208). Specifically, the user stops the drive mechanism of the aerial work platform vehicle V1. Then, using the management application of the user terminal 30, the user accesses the management server 20 and transmits a locking signal.
[0058] The control device 10 that has received the lock signal executes a lock process (step S209). Specifically, the control device 10 locks the key box. Next, the control device 10 executes a process of transmitting status information (step S210). Specifically, the control device 10 acquires the charge amount from the battery of the aerial work platform vehicle V1. Then, the control device 10 transmits the status information to the user terminal 30. This status information includes data on the charge amount of the battery.
[0059] The user terminal 30, which has acquired the status information from the control device 10, executes a transfer process (step S211). Specifically, the user terminal 30 identifies the current location using the location acquisition unit. Then, the user terminal 30 transmits the status information, including the user ID, the current location, and data related to the battery charge level, to the management server 20.
[0060] Next, the control unit 21 of the management server 20 executes information update processing (step S212). Specifically, the monitoring unit 213 of the control unit 21 identifies in the work vehicle information storage unit 22 the work vehicle management record 220 in which the user ID acquired from the user terminal 30 is recorded in the operation status data area. Then, the monitoring unit 213 records the current location and battery status acquired from the user terminal 30 in the identified work vehicle management record 220. Furthermore, the monitoring unit 213 deletes the user ID recorded in the operation status data area of the work vehicle management record 220 and leaves it blank. Then, the monitoring unit 213 uses the utilization application information storage unit 24 to identify the application ID corresponding to the user ID and deletes it from the application allocation of the work vehicle management record 220.
[0061] (Spot use application processing) Next, the spot use application process will be described with reference to Fig. 7. This process is performed when an application for use of the aerial work vehicle V1 has not been made by the previous work day, and a user wishes to use the aerial work vehicle V1 on the work day.
[0062] First, the control unit 21 of the management server 20 executes a process for acquiring a spot use application (step S301). Specifically, a user who wishes to use the aerial work platform V1 starts the management application of the user terminal 30 and inputs "spot use". In this case, the user terminal 30 accesses the management server 20 and transmits a spot use application. This spot use application includes data related to the user ID of the management application. In this case, the reservation unit 211 of the control unit 21 outputs a reservation screen to the user terminal 30. Then, the reservation unit 211 acquires the use location and work content inputted on the reservation screen. The reservation unit 211 generates an application management record 240 to which the application ID is assigned, and records it in the application information storage unit 24. In this application management record 240, data related to the spot use application, the required time, the work content, and the user ID as the applicant are recorded as the application type.
[0063] Next, the control unit 21 of the management server 20 executes a search process for an "empty" work vehicle (step S302). Specifically, the allocation unit 212 of the control unit 21 identifies an available vehicle type according to the work content. Next, the allocation unit 212 searches the work vehicle information storage unit 22 for a work vehicle management record 220 in which the identified vehicle type is recorded and in which the reservation allocation data area is blank.
[0064] Next, the control unit 21 of the management server 20 executes a determination process as to whether or not there is an "empty" work vehicle (step S303). Specifically, the allocation unit 212 of the control unit 21 determines that there is an "empty" work vehicle when it is able to extract a work vehicle management record 220 in which the reservation allocation data area is blank.
[0065] If it is determined that there is an "empty" work vehicle ("YES" in step S303), the control unit 21 of the management server 20 executes a work vehicle allocation registration process (step S304). Specifically, the allocation unit 212 of the control unit 21 records the application ID in the reservation allocation data area of the identified work vehicle management record 220. Furthermore, the allocation unit 212 records the work vehicle ID of this aerial work vehicle V1 in the work vehicle ID data area of the application management record 240 of the spot use application. This grants usage authority to the user who made the spot use application.
[0066] On the other hand, if it is not possible to extract a work vehicle management record 220 with a blank reservation allocation data area and it is determined that there is no "empty" work vehicle ("NO" in step S303), the control unit 21 of the management server 20 executes a detection process for the operating status of each work vehicle (step S305). Specifically, the allocation unit 212 of the control unit 21 extracts a work vehicle management record 220 in which the identified vehicle type is recorded and an application ID is recorded in the reservation allocation data area. Then, the allocation unit 212 acquires the operating status of the extracted work vehicle management record 220.
[0067] Next, the control unit 21 of the management server 20 executes a search process for a "reserved" work vehicle that is not in operation (step S306). Specifically, the allocation unit 212 of the control unit 21 searches for a work vehicle management record 220 in which the operation status data field is blank.
[0068] Next, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a non-operating work vehicle (step S307). Specifically, when the allocation unit 212 of the control unit 21 identifies a work vehicle management record 220 in which the operation status data field is blank, it determines that there is a non-operating work vehicle.
[0069] If it is not possible to identify a vehicle management record 220 with a blank operating status data field and it is determined that there is no vehicle that is not in operation (NO in step S307), the control unit 21 of the management server 20 executes a standby process for the end of work (step S308). Specifically, the allocation unit 212 of the control unit 21 waits until the vehicle management record 220 recorded in the vehicle information storage unit 22 is updated. The control unit 21 of the management server 20 then repeats the processes from step S302 onwards.
[0070] On the other hand, when it is determined that there is a work vehicle that is not in operation (if "YES" in step S307), the control unit 21 of the management server 20 executes a process of outputting a list sorted in order of proximity (step S309). Specifically, the allocation unit 212 of the control unit 21 acquires the location recorded in all work vehicle management records 220 whose operation status data fields are blank, in association with the work vehicle ID. Furthermore, the allocation unit 212 acquires the application management record 240 recorded in the utilization application information storage unit 24, using the application ID recorded in the work vehicle management record 220. Then, the allocation unit 212 acquires information on the utilization location, required time, and applicant recorded in the application management record 240. Then, the allocation unit 212 creates a list in which the work vehicle IDs are arranged in order of proximity to the utilization location of the spot utilization application. This list includes information on the utilization location, utilization time, and applicant recorded in the application management record 240 in association with the work vehicle ID. Then, the allocation unit 212 outputs the generated list to the user terminal 30. In this case, the user who applies for spot use selects the desired aerial work vehicle V1 from the list. Then, the allocation unit 212 identifies the user of the selected aerial work vehicle V1 as a candidate for use.
[0071] Next, the control unit 21 of the management server 20 executes a process of inquiring the candidate users about whether or not they can use the spot (step S310). Specifically, the allocation unit 212 of the control unit 21 identifies the selected aerial work platform V1 as a candidate user and identifies the applicant who has applied for use. Then, the allocation unit 212 transmits a spot use request to the user terminal 30 of the candidate user.
[0072] Next, the control unit 21 of the management server 20 executes a process to determine whether the spot can be used (step S311). Specifically, the applicant who received the spot use request replies with approval or refusal in response to the spot use request, taking into consideration the work situation. If refusal information is obtained from all user terminals 30 that received the spot use request, it is determined that the spot cannot be used. In this case, the consultation result is output to the list of user terminals 30 that have submitted spot use applications.
[0073] If it is determined that the facility is unavailable (if "NO" in step S311), the control unit 21 of the management server 20 executes a process of determining whether or not to wait (step S312). Specifically, the spot use applicant who has confirmed the consultation result on the list determines whether or not to make a new consultation.
[0074] When a new selection of a work vehicle is detected in the list, the allocation unit 212 of the control unit 21 determines that the work vehicle is not on standby. In this case (if "NO" in step S312), the control unit 21 of the management server 20 repeats the processes from step S310 onwards.
[0075] If it is determined to wait (YES in step S312), the control unit 21 of the management server 20 executes a process of waiting for the end of the work (step S308). On the other hand, if acceptance information is obtained from any of the user terminals 30 that received the spot use application and it is determined that the spot can be used ("YES" in step S311), the control unit 21 of the management server 20 executes the work vehicle allocation registration process (step S313), similar to step S304.
[0076] Next, the control unit 21 of the management server 20 executes a contact process to the applicant terminal (step S314). Specifically, the allocation unit 212 of the control unit 21 transmits information about the available aerial work platform V1 to the user terminal 30 of the spot use application.
[0077] According to this embodiment, the following effects can be obtained. (1) In this embodiment, the control unit 21 of the management server 20 executes a process for accepting a reservation request (step S101). If it is determined that the cut-off time has arrived (if "YES" in step S102), the control unit 21 of the management server 20 executes a process for identifying the reservation request (step S103). If it is determined that the number of units is insufficient (if "NO" in step S105), the control unit 21 of the management server 20 executes an alert process (step S106). This makes it possible to alert the administrator when a shortage of shared items occurs in response to a request for use.
[0078] (2) In this embodiment, when it is determined that the number of vehicles is sufficient (if "YES" in step S105), the control unit 21 of the management server 20 executes a process of allocating vehicles according to the work content and location (step S107) and a process of registering a schedule (step S108). This allows for efficient allocation of shared assets suitable for the work.
[0079] (3) In this embodiment, when the user terminal 30 executes the unlocking application process (step S201), the control unit 21 of the management server 20 executes the reservation authority confirmation process (step S202). When it is determined that the authentication is complete (if "YES" in step S203), the control unit 21 of the management server 20 executes the unlocking permission transmission process (step S205). Then, the control device 10 executes the unlocking process (step S207). This eliminates the need to provide the aerial work vehicle V1 with a means for communicating with the management server 20, and the start of the aerial work vehicle V1 can be controlled by local communication using the user terminal 30. This makes key management easier.
[0080] (4) In this embodiment, the user terminal 30 that has acquired the status information from the control device 10 executes a transfer process (step S211). This allows the user terminal 30 to grasp the status of the vehicle V1 for work at height, such as the charge level of the battery and its location.
[0081] (5) In this embodiment, the control unit 21 of the management server 20 executes a process for acquiring a spot use application (step S301) and a process for searching for an "empty" work vehicle (step S302). If it is determined that there is an "empty" work vehicle (if "YES" in step S303), the control unit 21 of the management server 20 executes a process for registering the allocation of the work vehicle (step S304). This allows the aerial work vehicle V1 to be used promptly on a spot basis even if no prior application for use has been made.
[0082] (6) In this embodiment, when it is determined that there is no "empty" work vehicle (when it is "NO" in step S303), the control unit 21 of the management server 20 executes a process to detect the operating status of each work vehicle (step S305). When it is determined that there is no work vehicle that is not in operation (when it is "NO" in step S307), the control unit 21 of the management server 20 executes a process to wait for the end of work (step S308). This makes it possible to promptly encourage spot use when the use of the aerial work vehicle V1 has ended.
[0083] (7) In this embodiment, when it is determined that there is a vehicle that is not in operation (if "YES" in step S307), the control unit 21 of the management server 20 executes output processing of the list sorted in order of proximity (step S309). This allows the applicant for spot use to efficiently select the desired vehicle V1 for aerial work.
[0084] (8) In this embodiment, the control unit 21 of the management server 20 executes a process of inquiring of the availability of the spot to the candidate users (step S310). If the control unit 21 acquires acceptance information from any of the user terminals 30 that received the spot use application and determines that the spot can be used (if "YES" in step S311), it executes a process of registering the allocation of a work vehicle (step S313). This reduces the work of the applicant for spot use.
[0085] This embodiment can be modified as follows: This embodiment and the following modifications can be combined with each other to the extent that there is no technical contradiction. In the above embodiment, a shared aerial work platform is used as the shared object, but the present invention is not limited to this as long as it is something that can be shared.
[0086] In the above embodiment, a two-dimensional code image including a vehicle ID is used to identify each vehicle V1. The method of identifying each vehicle V1 is not limited to using a two-dimensional code image. For example, reading a tag including the vehicle ID or short-distance wireless communication using Bluetooth (registered trademark) may be used. In this case, the user terminal 30 acquires information related to the vehicle ID using a tag reader or communication device H11 in the unlocking application process (step S201).
[0087] In the above embodiment, the control unit 21 of the management server 20 executes a process of determining whether authentication is complete (step S203). Specifically, the monitoring unit 213 of the control unit 21 checks whether the vehicle ID and user ID included in the unlocking application are recorded in the identified application management record 240. The authentication method is not limited to using the application management record 240. For example, the user ID is recorded for each usage time in the work vehicle management record 220. Then, authentication may be performed using the user ID whose usage time in the work vehicle management record 220 for the vehicle ID includes the current time.
[0088] In the above embodiment, the control device 10 holds an unlocking key for managing the locking of the key box in which the start key of the vehicle for work at height V1 is stored, and manages the start of the drive mechanism. The user terminal 30 then executes a process for transmitting an unlocking signal (step S206). Here, as long as the use of the vehicle for work at height V1 can be managed, this is not limited to locking the key box.
[0089] In the above embodiment, when work is completed, the user terminal 30 executes a process of transmitting a locking signal (step S208). Here, for example, the user terminal 30 may be configured to monitor the operating status of the aerial work platform vehicle V1 and the locking status of the key box. Then, when the user terminal 30 detects that the drive mechanism has stopped or that the key box has been locked, it may be configured to automatically transmit a locking signal.
[0090] In the above embodiment, information related to the work content is recorded in the usage application information storage unit 24. Then, the control unit 21 of the management server 20 specifies the vehicle type of the aerial work platform vehicle V1 to be used according to the work content. Alternatively, the vehicle type may be specified in the usage application without specifying the work content.
[0091] In the above embodiment, the user terminal 30, which has acquired the status information from the control device 10, executes a transfer process (step S211). Specifically, the user terminal 30 uses a location acquisition unit to identify the current location. Then, the user terminal 30 transmits status information including data on the user ID, the current location, and the battery charge level to the management server 20. In this case, the user terminal 30 uses a GPS, a wireless base station, or the like. As long as the current location can be identified, the method of acquiring the location is not limited. For example, a location acquisition unit may be provided on the aerial work vehicle V1 side. In this case, a barometer may be installed on the aerial work vehicle V1, and the installation floor may be identified from the altitude corresponding to the air pressure.
[0092] In the above embodiment, when it is determined that there is a work vehicle that is not in operation (if "YES" in step S307), the control unit 21 of the management server 20 executes a process of outputting a list sorted in order of proximity (step S309). Then, the control unit 21 of the management server 20 executes a process of asking the candidate whether or not they can use the spot (step S310). Alternatively, the management server 20 may identify an aerial work vehicle that is not in operation and ask the applicant about spot use.
[0093] The spot use application process will be described with reference to FIG. First, the control unit 21 of the management server 20 executes a process to determine whether or not there is a non-operating work vehicle (step S307). If it is determined that there is no non-operating work vehicle ("NO" in step S307), the control unit 21 of the management server 20 executes a process to wait for the end of work (step S308).
[0094] On the other hand, when it is determined that there is a work vehicle that is not in operation (if "YES" in step S307), the control unit 21 of the management server 20 executes a process of inquiring the use candidates as to whether or not the spot can be used (step S401). Specifically, the allocation unit 212 of the control unit 21 uses the work vehicle information storage unit 22 to identify aerial work vehicles V1 that are not in operation as use candidates in order of proximity. Then, the allocation unit 212 acquires the application ID of the work vehicle management record 220 of the identified aerial work vehicle V1. Next, the allocation unit 212 acquires the application management record 240 of this application ID from the use application information storage unit 24, and acquires the applicant (user ID). Then, the allocation unit 212 transmits a spot use request to the user terminal 30 of the identified applicant.
[0095] Next, the control unit 21 of the management server 20 executes a standby process (step S402). Specifically, the allocation unit 212 of the control unit 21 waits for a response to the spot use request. Next, the control unit 21 of the management server 20 executes a process of determining whether the spot is available (step S403). Specifically, when the allocation unit 212 of the control unit 21 receives acceptance information from any of the user terminals 30 that received the spot use application, it determines that the spot is available. On the other hand, when the allocation unit 212 of the control unit 21 receives rejection information from all of the user terminals 30 that received the spot use application, it determines that the spot is not available.
[0096] If it is determined that use is not possible (if "NO" in step S403), the control unit 21 of the management server 20 executes a determination process as to whether all are not possible (step S404). Specifically, the allocation unit 212 of the control unit 21 checks whether there are any work vehicle management records 220 for which a spot use request has not yet been sent. If refusal information is acquired for all work vehicle management records 220 of the aerial work vehicle V1 that is not in operation, the allocation unit 212 determines that all are not possible.
[0097] If it is determined that all of the operations are unsuccessful (YES in step S404), the control unit 21 of the management server 20 executes a process of waiting for the end of the operations (step S308). If there are still work vehicle management records 220 remaining for aerial work vehicles V1 for which spot use applications have not yet been submitted and it is determined that all of them are not unsuitable ("NO" in step S404), the control unit 21 of the management server 20 executes a process to inquire of the applicants for the remaining work vehicles as to whether or not they can use the spot (step S401).
[0098] On the other hand, if it is determined that the vehicle is available for use (YES in step S403), the control unit 21 of the management server 20 executes a process of identifying an available vehicle for use (step S405). Specifically, the allocation unit 212 of the control unit 21 identifies the vehicle for use at an elevation V1 in the record in which the current position closest to the location of use of the spot use application is recorded in the vehicle management record 220 in which the application ID for which the acceptance information has been obtained is recorded.
[0099] Next, the control unit 21 of the management server 20 executes the vehicle allocation registration process in the same manner as in step S313 (step S406). Next, the control unit 21 of the management server 20 executes a contact process to the applicant terminal, similar to step S314 (step S407). This reduces the workload of the applicant for spot use and enables the aerial work vehicle V1 to be allocated.
[0100] In the above embodiment, the control unit 21 of the management server 20 executes a process of outputting the list sorted in order of proximity (step S309). Then, the control unit 21 of the management server 20 executes a process of asking the candidate users whether or not they can use the spot (step S310). Here, the candidate users may be identified taking into account the charge amount.
[0101] The process of identifying candidates for use will be described with reference to Fig. 9. Here, the following process is repeatedly executed for each worker working at height. First, the control unit 21 of the management server 20 executes a process of acquiring the current charge amount (step S501). Specifically, the allocation unit 212 of the control unit 21 acquires the charge amount of each aerial work vehicle V1 using the battery status of the work vehicle management record 220 recorded in the work vehicle information storage unit 22.
[0102] Next, the control unit 21 of the management server 20 executes a process for identifying the usage schedule for the entire day (step S502). Specifically, the allocation unit 212 of the control unit 21 acquires the application ID recorded in the application allocation data area of each work vehicle management record 220.
[0103] Next, the control unit 21 of the management server 20 executes a process of calculating the charge margin (step S503). Specifically, the allocation unit 212 of the control unit 21 acquires the application management record 240 of the acquired application ID from the usage application information storage unit 24. Then, the allocation unit 212 calculates the predicted power usage amount according to the length of the usage time recorded in the application management record 240 of each aerial work vehicle. Next, the allocation unit 212 calculates the charge margin by subtracting the predicted power usage amount from the charge amount of each aerial work vehicle.
[0104] Next, the control unit 21 of the management server 20 executes a process of determining whether there is a margin (step S504). Specifically, the allocation unit 212 of the control unit 21 calculates a predicted amount of power usage according to the length of time required for the spot use application. Then, the allocation unit 212 calculates the difference between the charging margin and the predicted amount of power usage. Here, if the difference is equal to or greater than a reference value, it is determined that there is a margin.
[0105] When it is determined that there is a surplus (if "YES" in step S504), the control unit 21 of the management server 20 executes a process of identifying the vehicle as a candidate for use (step S505). Specifically, the allocation unit 212 of the control unit 21 identifies the vehicle V1 having a surplus as a candidate for use for the spot use application.
[0106] On the other hand, if it is determined that there is no surplus (if "NO" in step S504), the control unit 21 of the management server 20 executes a process of deleting the candidate from the usage candidates (step S506). Specifically, the allocation unit 212 of the control unit 21 specifies the candidate as not eligible for the spot usage application.
[0107] In the above embodiment, the control unit 21 of the management server 20 executes a process of outputting the list sorted in order of proximity (step S309). Then, the control unit 21 of the management server 20 executes a process of asking the candidate users whether or not they can use the spot (step S310). Here, the candidate users may be identified according to the attributes of the user who applied for the reservation. In this case, the allocation unit 212 holds information for identifying the user attributes according to the user ID. Then, a reference distance management table is provided for identifying the reference distance in association with the user attributes. In this reference distance management table, a short reference distance is set for the attributes of the worker who uses the aerial work vehicle V1, and a long reference distance is set for the attributes of the site manager.
[0108] The process of identifying available candidates will be described with reference to Fig. 10. Here, the following process is repeated for each worker working at height. First, the control unit 21 of the management server 20 executes a process for identifying the location of the user terminal (step S601). Specifically, the allocation unit 212 of the control unit 21 acquires the current location of the user terminal 30 of the applicant.
[0109] Next, the control unit 21 of the management server 20 executes a process of identifying the use location (step S602). Specifically, the allocation unit 212 of the control unit 21 acquires the use location recorded in the application management record 240 of the use application information storage unit 24.
[0110] Next, the control unit 21 of the management server 20 executes a distance calculation process (step S603). Specifically, the allocation unit 212 of the control unit 21 calculates the distance from the current location of the user terminal 30 to the location of use.
[0111] Next, the control unit 21 of the management server 20 executes a process of specifying a reference distance according to the user attributes (step S604). Specifically, the allocation unit 212 of the control unit 21 acquires the user attributes of the applicant's user ID recorded in the application management record 240 from the user information storage unit 23. Next, the allocation unit 212 uses the reference distance management table to specify a reference distance according to the user attributes.
[0112] Next, the control unit 21 of the management server 20 executes a process of determining whether the aerial work vehicle is being used (step S605). Specifically, the allocation unit 212 of the control unit 21 determines that the vehicle is in use when the distance to the location of use is within a reference distance, and determines that the vehicle is not in use when the distance is longer than the reference distance.
[0113] When it is determined that the aerial work vehicle is not being used (if "NO" in step S605), the control unit 21 of the management server 20 executes a process of identifying the vehicle as a candidate for use (step S606). Specifically, the allocation unit 212 of the control unit 21 identifies the vehicle as a candidate for use in the spot use application.
[0114] On the other hand, when it is determined that the aerial work vehicle is being used (if "YES" in step S605), the control unit 21 of the management server 20 executes a process of deleting it from the usage candidates (step S607). Specifically, the allocation unit 212 of the control unit 21 specifies it as being outside the scope of the usage candidates for the spot usage application.
[0115] As a result, if the worker is away from the usage location, it is determined that the spot can be used. Also, in the case of the site manager, there is a possibility that the worker will leave the usage location after unlocking the aerial work platform V1. In this case, even if the worker is far from the usage location, the spot can be excluded from usage.
[0116] In the above embodiment, the control unit 21 of the management server 20 executes an information update process (step S212). At this point, a process of checking the charge level of the battery of the vehicle for high altitude work may also be performed.
[0117] The process of checking the charge amount will be described with reference to FIG. First, the control unit 21 of the management server 20 executes a process for acquiring the charge amount (step S701). Specifically, the monitoring unit 213 of the control unit 21 uses the work vehicle management record 220 recorded in the work vehicle information storage unit 22 to identify the charge amount of the battery of the aerial work vehicle V1 that has been decommissioned.
[0118] Next, the control unit 21 of the management server 20 executes a process for identifying a subsequent use (step S702). Specifically, the monitoring unit 213 of the control unit 21 identifies the application ID recorded in the application allocation data area of the work vehicle management record 220 as the subsequent use.
[0119] Next, the control unit 21 of the management server 20 executes a calculation process of the predicted power usage amount (step S703). Specifically, the monitoring unit 213 of the control unit 21 extracts the application management record 240 of the identified application ID from the usage application information storage unit 24. Then, the monitoring unit 213 calculates the predicted power usage amount according to the length of the usage time recorded in the application management record 240.
[0120] Next, the control unit 21 of the management server 20 executes a process of determining whether the charge amount is sufficient or not (step S704). Specifically, the monitoring unit 213 of the control unit 21 calculates the charge margin by subtracting the predicted power usage amount from the charge amount. Then, if the charge margin is equal to or greater than a reference value, it is determined that there is a margin.
[0121] If it is determined that the charged amount is sufficient (YES in step S704), the charged amount confirmation process ends. If it is determined that the charging amount is insufficient (if "NO" in step S704), the control unit 21 of the management server 20 executes a process of determining whether there is charging time (step S705). Specifically, the monitoring unit 213 of the control unit 21 calculates the remaining time from the current time to the start time recorded in the usage time of the subsequent application management record 240. Then, if the remaining time is equal to or greater than the reference time, it is determined that there is charging time.
[0122] When it is determined that there is a charging time (if "YES" in step S705), the control unit 21 of the management server 20 executes a charging instruction process (step S706). Specifically, the monitoring unit 213 of the control unit 21 transmits a charging instruction to the user terminal 30 and the management terminal 32.
[0123] On the other hand, if it is determined that the remaining time is less than the reference time and there is no charging time ("NO" in step S705), the control unit 21 of the management server 20 executes an alert process (step S707). Specifically, the monitoring unit 213 of the control unit 21 transmits an alarm message to the management terminal 32. This alarm message includes information related to the work vehicle ID and application ID. In this case, the administrator adjusts the application to use the aerial work vehicle V1 and alerts the user. [Explanation of symbols]
[0124] V1...aerial work vehicle, 10...control device, 20...management server, 21...control unit, 211...reservation unit, 212...allocation unit, 213...monitoring unit, 22...work vehicle information storage unit, 23...user information storage unit, 24...usage application information storage unit, 30...user terminal, 32...management terminal.
Claims
1. A control unit that communicates with a user terminal; A shared property information storage unit that records the usage status of the aerial work vehicle; A shared property management system including a usage application information storage unit that records the usage application for the aerial work vehicle, The control unit: A usage application including a location where the aerial work vehicle is to be used is acquired from the user terminal, and recorded in the usage application information storage unit; When the use application information storage unit cannot identify an available aerial work vehicle, the shared property information storage unit is used to identify each use state and location, Identifying aerial work vehicle candidates that can be used based on the usage state and according to a distance between the usage location and the location; A shared property management system characterized in that the authority to use an aerial work vehicle selected from the aerial work vehicle candidates is granted to the user terminal.
2. The control unit: Acquire from the user terminal a usage application including a location where the aerial work vehicle will be used until the deadline, When the application information storage unit is unable to identify an available aerial work vehicle after the deadline has passed, the shared property information storage unit is used to identify the usage status and location of each vehicle, The shared property management system according to claim 1, characterized in that each aerial work vehicle candidate is available based on the usage status and is allocated to each usage application according to the sum of the distances between the usage location and the location.
3. The control unit: For the aerial work vehicle selected from the aerial work vehicle candidates, a spot use request is transmitted to a user terminal of an applicant who has applied to use the aerial work vehicle candidate; 2. The shared property management system according to claim 1, wherein when permission information is acquired from the user terminal, the authority to use the candidate aerial work vehicle is granted to the user terminal.
4. A shared property management system as described in any one of claims 1 to 3, characterized in that the control unit identifies at least one of the operating state of the drive mechanism of the aerial work vehicle and the charging state of the battery as the usage state.
5. A control unit that communicates with a user terminal; A shared property information storage unit that records the usage status of the aerial work vehicle; A method for managing an aerial work vehicle using a shared property management system including a usage application information storage unit that records the usage application for the aerial work vehicle, The control unit: A usage application including a location where the aerial work vehicle is to be used is acquired from the user terminal, and recorded in the usage application information storage unit; When the use application information storage unit cannot identify an available aerial work vehicle, the shared property information storage unit is used to identify each use state and location, Identifying aerial work vehicle candidates that can be used based on the usage state and according to a distance between the usage location and the location; A shared property management method, comprising the step of granting to the user terminal the right to use a vehicle selected from the vehicle candidates.
6. A control unit that communicates with a user terminal; A shared property information storage unit that records the usage status of the aerial work vehicle; A program for managing an aerial work vehicle using a shared property management system including a usage application information storage unit that records the usage application for the aerial work vehicle, The control unit, A usage application including a location where the aerial work vehicle is to be used is acquired from the user terminal, and recorded in the usage application information storage unit; When the use application information storage unit cannot identify an available aerial work vehicle, the shared property information storage unit is used to identify each use state and location, Identifying aerial work vehicle candidates that can be used based on the usage state and according to a distance between the usage location and the location; a shared property management program that functions as a means for granting to the user terminal the right to use an aerial work vehicle selected from the aerial work vehicle candidates.
Citation Information
Patent Citations
Vehicle sharing system having vehicle allocation means for inspection waiting vehicle and vehicle allocation method
JP1999265410A
Common-use vehicle operation system
JP2002175588A
Shared vehicle management device and shared vehicle management method
JP2016177411A
Management system and management program
JP2019145020A
Architectural equipment reservation management system and program
JP2019175224A
