JP2020203752A - Elevator group management device and elevator group management method - Google Patents

Abstract

To provide an elevator group management device and an elevator group management method for allowing a self-traveling mobile body to efficiently utilize an elevator.SOLUTION: An elevator group management device is connected to plural elevators and comprises: a call registration unit; a landing information acquisition unit; and an assignment unit. The call registration unit registers a mobile body landing call upon acquisition of a landing call registration request related to a self-traveling mobile body to use an elevator, and registers a user landing call upon acquisition of a landing call registration request according to operation by a general user of the elevator. The landing information acquisition unit acquires information indicating a degree of congestion at a landing hall of the elevator. When a mobile body landing call and a user landing call are registered for moving in the same direction at the same floor, and a degree of congestion acquired by the landing information acquisition unit exceeds a first threshold, the assignment unit assigns different elevators to the mobile body landing call and the user landing call.SELECTED DRAWING: Figure 2

Description

Embodiments of the present invention relate to an elevator group management device and an elevator group management method.

In a building where an elevator is installed, a robot device, which is a self-propelled moving body, may use the elevator to move to another floor in the building and perform various operations. In recent years, the number of high-rise buildings has increased, and along with this, the number of robot devices that use elevators for various purposes has increased.

The robot device that uses the elevator charges at the robot station installed in the building except when it is in operation, and when the timing to start operation comes, it moves to the elevator landing and automatically sends a landing call registration request to the elevator to get on. Use the elevator by calling the car.

Japanese Unexamined Patent Publication No. 2005-53670

However, if the elevator is congested when the robot device sends a landing call registration request for using the elevator, the robot device waits for the arrival of the car at the landing for a long time. The upper limit of the waiting time is set in advance in the robot device, and if the upper limit of the waiting time is exceeded before the car arrives, a timeout occurs and the robot returns to the station. When such a situation occurs, there is a problem that the operating efficiency of the robot device is lowered.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an elevator group management device and an elevator group management method for enabling a self-propelled moving body to efficiently use an elevator.

According to the embodiment for achieving the above object, the elevator group management device is connected to a plurality of elevators and includes a call registration unit, a landing information acquisition unit, and an allocation unit. When the call registration department obtains a landing call registration request for a self-propelled moving object using an elevator, it registers the mobile landing call, and when it obtains a landing call registration request operated by a general user of the elevator, the user landing call To register. The landing information acquisition unit acquires information indicating the degree of congestion at the elevator landing. When the mobile landing call and the user landing call for moving in the same direction on the same floor are registered and the congestion degree acquired by the landing information acquisition unit exceeds the first threshold value, the allocation unit is the mobile landing. Assign different elevators to the call and the user landing call.

The whole view which shows the structure of the elevator system by embodiment. The block diagram which shows the structure of the elevator system by embodiment. The flowchart which shows the process executed by the group management apparatus of the elevator system by embodiment.

<Elevator system configuration according to one embodiment>
The configuration of the elevator system 1 according to the embodiment of the present invention will be described with reference to FIGS. 1 and 2. The elevator system 1 according to the present embodiment includes the first elevator 10-1, the second elevator 10-2, and the third elevator 10-3 installed in the building, and the first elevator 10-1 to the third elevator 10 thereof. A robot device 20 that is a self-propelled moving body using -3, a first landing operation panel 31-1 installed at the landing 30, a second landing operation panel 31-2, a landing camera device 32, and a landing speaker. A device 33 and a group management device 40 installed in the upper part of the hoistway are provided. In FIG. 1, only one landing 30 is shown for simplification of the explanation, but in reality, there are landings on each floor in the building, and a landing operation panel, a landing camera device, and a landing speaker device are installed in each. Has been done. Further, a large number of landing operation panels 31, a plurality of landing camera devices 32, and a plurality of landing speaker devices 33 may be installed in one landing 30.

The first elevators 10-1 to 3rd elevators 10-3 are the first elevators 11-1 to 11-3 running in the hoistway and the first elevators 11-1 to 11-3 installed in the upper part of the hoistway and connected to the group management device 40, respectively. It has elevator control devices 12-1 to 3rd elevator control devices 12-3, and landing doors 13-1 to 13-3 installed at the landing 30. The car 11-1 to 11-3 are installed on the car doors 111-11 to 111-3 and the inside of the car 11-11 to 11-3 is photographed. Has 3 and. The in-car camera device 112-1 to 112-3 counts the number of users in the car 11-1 to 11-3 by analyzing the captured image information. The first elevator control device 12-1 to the third elevator control device 12-3 are processes for operating the elevators 10-1 to 10-3 based on the instruction from the group management device 40, and the in-car camera devices 112-1 to 112-1. The process of transmitting the information on the number of users in the cars 11-1 to 11-3 counted in 112-3 to the group management device 40 is performed.

Hereinafter, when it is not necessary to specify which of the first elevators 10-1 to 3rd elevators 10-3 is, it is described as elevator 10. The same applies to the car 11, the elevator control device 12, the landing door 13, and the landing operation panel 31.

The robot device 20 includes a movement mechanism unit 21, a call registration request unit 22, and a robot wireless communication unit 23. The moving mechanism unit 21 moves the own robot device 20 in a predetermined direction at a predetermined speed. The call registration request unit 22 outputs a landing call registration request when using any of the first elevator 10-1 to the third elevator 10-3. The robot wireless communication unit 23 wirelessly transmits the landing call registration request output from the call registration request unit 22 to the landing operation panel 31-1 and wirelessly transmits the landing call registration request from the group management device 40 via the landing operation panel 31-1. The operation instruction is received and sent to the moving mechanism unit 21. The robot device 20 is charged at the robot station S installed on the floor of the landing 30 except when it is in operation, and when it is in operation, it travels in the building by the moving mechanism unit 21 to drive elevators 10-1 to 10-3. Use it to get to and from your destination.

A landing call registration button 311-1 and an operation panel wireless communication unit 312-1 are installed on the first landing operation panel 31-1. When the landing call registration button 311-1 is operated by the user at the landing 30 when using the elevator 10, the landing call registration request is output to the group management device 40. The operation panel wireless communication unit 312-1 performs wireless communication with the robot device 20, transmits a landing call registration request received from the robot device 20 to the group management device 40, and performs call registration acquired from the group management device 40. Information on the responding elevator is transmitted to the robot device 20. A landing call registration button 321-1 is installed on the second landing operation panel 31-2.

The landing camera device 32 photographs the landing 30, analyzes the captured imaging information, counts the number of waiting users of the elevator in the landing 30, and calculates the degree of congestion based on the counted number of waiting users. It is transmitted to the group management device 40. The landing speaker device 33 outputs the announcement information to the landing 30 based on the instruction from the group management device 40.

The group management device 40 is connected to the first elevator control device 12-1 to the third elevator control device 12-3, the first landing operation panel 31-1, the second landing operation panel 31-2, and the landing camera device 32. It has a call registration unit 41, a landing information acquisition unit 42, an elevator information acquisition unit 43, an allocation unit 44, and an operation control unit 45. When the call registration unit 41 acquires the landing call registration request transmitted from the robot device 20, the call registration unit 41 registers the robot landing call. Further, when the general user acquires the landing call registration request output by operating the landing call registration button 311-1 or 321-1, the call registration unit 41 registers the user landing call.

The landing information acquisition unit 42 acquires the congestion degree information generated by the landing camera device 32. The elevator information acquisition unit 43 acquires the operating state information of the first elevator 10-1 to the third elevator 10-3. The allocation unit 44 allocates an elevator to respond to the call registered in the call registration unit 41 based on the information acquired by the landing information acquisition unit 42 and the information acquired by the elevator information acquisition unit 43. The operation control unit 45 transmits an operation instruction to the first elevator 10-1 to the third elevator 10-3 based on the elevator information assigned by the allocation unit 44 and the information acquired by the elevator information acquisition unit 43. To do.

<Operation of elevator system according to one embodiment>
Next, the operation of the elevator system 1 according to the present embodiment will be described. The robot device 20 stands by at the robot station S and charges the robot device 20 except when it is in operation. Then, when the timing for heading to the destination on another floor in the building arrives, the movement mechanism unit 21 starts moving from the robot station S toward the elevator landing 30. When the movement by the movement mechanism unit 21 starts, the call registration request unit 22 outputs a landing call registration request, which is wirelessly transmitted from the robot wireless communication unit 23 to the first landing operation panel 31-1.

In the first landing operation panel 31-1, the landing call registration request transmitted from the robot device 20 is received by the operation panel wireless communication unit 312-1 and transmitted to the group management device 40. In the group management device 40, based on the landing call registration request transmitted from the robot device 20, any car 11 is called to the floor to get the robot device 20 on board and run in a predetermined direction. Is registered in the call registration unit 41.

Further, when a general user operates the landing call registration button 311-1 or 321-1 in order to use any of the first elevator 10-1 to the third elevator 10-3, the operated landing call registration button 311 A landing call registration request is output from -1 or 321-1 and transmitted to the group management device 40. In the group management device 40, based on the landing call registration request output from the landing call registration button 311-1 or 321-1, the car 11 is called to the floor and the user is made to board and travel in a predetermined direction. The user landing call for the purpose is registered in the call registration unit 41.

Further, in the landing camera device 32, the landing 30 is photographed, and congestion degree information indicating the congestion degree of the landing 30 is generated based on the photographed imaging information and transmitted to the group management device 40. In the group management device 40, the congestion degree information transmitted from the landing camera device 32 is acquired by the landing information acquisition unit 42.

The process executed by the group management device 40 when these processes are executed will be described with reference to the flowchart of FIG. When the robot landing call and the user landing call for moving in the same direction on the same floor are registered in the call registration unit 41 (“YES” in S1), the congestion level of the landing 30 acquired by the landing information acquisition unit 42 Information is acquired by the allocation unit 44.

When the degree of congestion of the acquired landing 30 exceeds a predetermined value (“YES” in S2), the allocation unit 44 determines that the landing 30 is congested, and calls and uses the registered robot landing 30. A different elevator is assigned to the passenger landing call (S3). Here, the first elevator 10-1 that can respond to the user landing call at the earliest is assigned to the user landing call, and the car 11-2 in which the user is not boarding is assigned to the robot landing call. It is assumed that the second elevator 10-2 to have is assigned. Whether or not there are users in the car 11-1 to 11-3 is determined based on the number of users in the car counted by the in-car camera device 112-1 to 112-3.

The information of the second elevator 10-2 assigned to the robot landing call is wirelessly transmitted to the robot device 20 via the first landing operation panel 31-1. In the robot device 20, the received information of the second elevator 10-2 is acquired and held by the moving mechanism unit 21.

Ideally, the robot device 20 uses the elevator without riding with the user. Therefore, if there is no car in which the user is not on board, the first elevator 10-assigned to the user's landing call The number of users in the car 11 other than 1 is monitored, and when all the users in the car 11 get off at the destination floor and become empty, the elevator is assigned to the robot landing call.

Then, among the assigned car 11-1 and 11-2, the car 11-1 assigned to the user landing call is first opened regardless of the order of arrival at the landing 30 (S4). Here, based on the information acquired by the in-car camera device 112-1 and the information acquired by the landing camera device 32, it is determined that there is a user who could not get into the door-opened car 11-1. (“YES” in S5), the allocation unit 44 switches the second elevator 10-2 assigned to the robot landing call to an elevator that responds to the user landing call, opens the door, and newly opens another elevator 10-3. Is assigned as an elevator to respond to the robot landing call (S6). Information indicating that the elevator that responds to the robot landing call has been changed to elevator 10-3 is transmitted to the robot device 20 and held by the moving mechanism unit 21.

When it is determined that there is no user who could not get into the car 11-1 (“NO” in S5), the information assigned in step S3 is maintained. Here, it is assumed that there is no user who could not get into the car 11-1.

Next, after the user gets in the car 11-1 assigned to the user landing call and closes the door (“YES” in S7), the car 11-assigned to the robot landing call at the landing 30 2 is opened (S8). At this time, even if the car 11-2 assigned to the robot landing call arrives at the landing 30 earlier than the car 11-1, until the car 11-1 opens and closes. , Car 11-1 stands by without opening the door.

Further, when the car 11-1 assigned to the user landing call is opened, the boarding speaker device 33 outputs an announcement information notifying that the car 11-1 being opened is for the user. When the car 11-2 assigned to the robot landing call is opened, the announcement information notifying that the opened car 11-2 is for the robot device may be output.

By controlling in this way, it is possible to ensure that the user is prioritized over the robot device 20 at the landing 30 to use the elevator, and it is possible to prevent the user's convenience from being lowered due to the use of the robot device 20. it can.

When the car 11-2 opens in response to the robot landing call, the landing door 13-2 and the car door 111-2 are opened at the minimum opening degree through which the robot device 20 can pass. By controlling in this way, it is possible to prevent the user from getting on the car 11-2 assigned to the robot landing call.

When the car 11-2 opens, the robot device 20 detects that the car 11-2 has opened, and the car 11- responds to the robot landing call based on the information held in the moving mechanism section 21. Moved within 2. When the robot device 20 gets into the car 11-2, the second elevator 10-2 performs an operation for moving to the target floor of the robot device 20.

Further, in step S2, when the degree of congestion of the landing is equal to or less than a predetermined value (“NO” in S2), the allocation unit 44 determines that the landing 30 is not congested and can arrive at the landing 30 earliest. One elevator 10 having a car 11, for example, the first elevator 10-1, is assigned as an elevator that responds to a registered user landing call and a robot landing call (S9). The assigned information on the first elevator 10-1 is wirelessly transmitted to the robot device 20 via the first landing operation panel 31-1. In the robot device 20, the received information of the first elevator 10-1 is acquired and held by the moving mechanism unit 21.

Then, when the assigned car 11-1 arrives at the landing 30, the door is opened (S10). Here, when it is determined that there is a user who could not get into the car 11-1 that has been opened (“YES” in S11), the assigned first elevator 10-1 is called by the allocation unit 44 to call the user landing. It is switched to an elevator that responds only to the elevator, and another elevator, for example, the second elevator 10-2, is newly assigned as an elevator that responds to the robot landing call (S12). Information indicating that the elevator that responds to the robot landing call has been changed to the elevator 10-2 is transmitted to the robot device 20 and held in the moving mechanism unit 21.

Then, after the car 11-1 assigned to the user landing call has the user boarded and the door closed (“YES” in S7), the car 11-2 assigned to the robot landing call at the landing 30 Is opened (S8). When the car 11-2 opens, the robot device 20 detects that the car 11-2 that responds to the robot landing call has opened, and the car 11- based on the information held in the moving mechanism section 21. Moved into 2 and elevator 10-2 is used.

In step S11, when it is determined that there is no user who could not get into the car 11-1 (“NO” in S11), the process of responding to the boarding call registration is terminated.

According to the above embodiment, when both the user landing call and the robot landing call are registered in a state where the landing is crowded, the robot device cannot use the elevator by assigning different elevators to each. It is possible to prevent the occurrence of a situation in which a time-out occurs and the robot returns to the robot station.

In addition, if the number of waiting users for the landing increases after assigning elevators to the user landing call and robot landing call, all the already assigned elevators will be switched to elevators that respond to the user landing call, and the robot landing call will be used. By allocating a new elevator, the robot device will be able to use the elevator more reliably.

In addition, when the elevator car that responds to the user landing call and the elevator car that responds to the robot landing call are landed at the same time, the elevator car that responds to the user landing call By opening the door of the elevator car that responds to the robot landing call after opening and closing the door, it is possible to prevent the user from getting into the elevator car that responds to the robot landing call.

In addition, when opening the elevator car that responds to the robot landing call, by opening the door at the minimum opening that the robot device can pass through, the elevator car that responds to the robot landing call can be opened. It is possible to more reliably avoid the user getting in.

In the above-described embodiment, the case where the user's elevator use is always prioritized over the robot device has been described, but when it is set that the robot device needs to arrive at the target floor by a predetermined time, For example, when the robot device guards from a predetermined time to a predetermined floor, or when it is necessary to transport mail to a predetermined floor by a predetermined time, the robot device is more than a user from a few minutes before the time. You may give priority to the use of the elevator.

In this case, on the floor concerned, the car assigned to the robot landing call opens and closes at the minimum opening that the robot device can pass, and then the car assigned to the user landing call is doord. Open. In addition, if the robot landing call is registered during this time, but there is no car that the user is not on, the car with the least number of users is landed on the nearest floor and other elevators are used. The announcement information is output in the car, and when there are no more users in the car, the elevator having the car is made to respond to the robot landing call.

Although embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. This novel embodiment can be implemented in various other embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. This embodiment and its modifications are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.

1 ... Elevator system, 10,10-1 to 10-3 ... Elevator, 11,11-1 to 11-3 ... Car, 12,12-1 to 12-3 ... Elevator control device, 13,13-1 to 13-3 ... landing door, 20 ... robot device, 21 ... mobile mechanism unit, 22 ... call registration request unit, 23 ... robot wireless communication unit, 30 ... landing, 31, 31-1, 31-2 ... landing operation panel, 32 ... landing camera device, 33 ... landing speaker device, 40 ... group management device, 41 ... call registration unit, 42 ... landing information acquisition unit, 43 ... elevator information acquisition unit, 44 ... allocation unit, 45 ... operation control unit, 111 -1 to 111-3 ... Car door, 112-1 to 112-3 ... Car camera device, 311-1,321-1 ... Landing call registration button, 312-1 ... Operation panel wireless communication unit

Claims (7)

Connected to multiple elevators
A call to register a mobile landing call when a landing call registration request for a self-propelled mobile body using an elevator is obtained, and a call to register a user landing call when a landing call registration request operated by a general user of the elevator is obtained. Registration department and
A landing information acquisition unit that acquires information indicating the degree of congestion of the elevator landing, and
When the mobile landing call and the user landing call for moving in the same direction on the same floor are registered and the degree of congestion acquired by the landing information acquisition unit exceeds a predetermined value, the mobile landing call is called. An elevator group management device including an allocation unit that allocates a different elevator to the user landing call. When the allocation unit determines that there is a user who could not get into the car of the elevator assigned to the user landing call, the allocation unit switches the elevator assigned to the mobile landing call to an elevator that responds to the user landing call. The elevator group management device according to claim 1, wherein another elevator is newly assigned as an elevator that responds to the mobile landing call. After the elevator car assigned to the mobile landing call responds by the allocation unit to open and close the door on the corresponding floor, the elevator car assigned to the mobile landing call is concerned. The elevator group management device according to claim 1 or 2, further comprising an operation control unit that opens the door on the floor. The third aspect of claim 3, wherein the operation control unit opens the elevator car assigned to the mobile landing call on the floor with the minimum opening degree through which the mobile can pass. Elevator group management device. The operation control unit opens the door on the corresponding floor in response to the elevator car assigned to the mobile landing call during a time period in which priority is given to the use of the elevator of the mobile body. The elevator group management device according to claim 3 or 4, wherein after the door is closed, the elevator car assigned to the mobile landing call is opened on the floor. Elevator information acquisition department that acquires information indicating the presence or absence of users in the car of each elevator,
When the mobile landing call is registered, the allocation unit allocates the elevator of the car to the mobile landing call when there is a car with no passengers on board, and the ride without a user. The elevator group management device according to any one of claims 1 to 5, wherein when all the users of any of the cars get off when there is no car, the elevator is assigned to the mobile landing call. Elevator group management devices connected to multiple elevators
When a landing call registration request for a self-propelled mobile body using an elevator is obtained, a mobile landing call is registered, and when a landing call registration request operated by a general user of the elevator is obtained, a user landing call is registered.
Obtain information indicating the degree of congestion at the elevator landing,
When the mobile landing call and the user landing call for moving in the same direction on the same floor are registered and the congestion degree exceeds a predetermined value, the mobile landing call and the user landing call are different. An elevator group management method characterized by allocating elevators.

Images