JP5351510B2 - Station destination floor reservation type group management elevator control device - Google Patents

Abstract

The present invention provides a destination floor reserving type controlling device of a program management system, the controlling device is capable of forecasting huddle situation of an elevator entrance before the distributed elevator cage arrives and distributing more elevators appropriately according to the huddle situation for avoiding passengers from being left. The controlling device of the program management system has a first distributing unit for the call distribution of a destination floor reserved at the entrance of the elevator to an elevator cage selected by the controlling device of the program management system, and an additional distributing unit for distributing other elevator cages additionally, before the elevator cage distributed by the first distributing unit arrives at the entrance of the elevator, and when the number of passengers in a forecasted elevator cage exceeds a predetermined value after the elevator entrance logins any one destination floor additionally and after the elevator cage distributed by the first distributing unit provides services for the elevator entrance and has left from the entrance.

Description

  The present invention relates to a group management system that manages and manages the operation of a plurality of elevators, and more particularly, to a control device for a destination management floor reservation type group management elevator that reserves a destination floor at a landing.

  The elevator group management system provides a more effective operation service to the user by handling a plurality of cars as one group. Specifically, when a plurality of cars are managed as one group, and a landing destination floor is registered on a certain floor, one optimal car is selected from the group, and the car is assigned to the car. A process of assigning a landing call is performed.

  Destination floor reservation system type group management (hereinafter referred to as destination floor reservation type group management) is a group management in which the destination floor is registered with the destination floor reservation device provided at the landing before boarding the car. It is. In general group management, an up or down call is registered at the landing and the destination floor is registered after the car arrives, whereas the destination floor reservation type uses it at an early stage for the control device. Since the destination floor of the person is known, a more optimal car can be assigned according to the destination floor. However, users coming to the landing cannot know which floor is registered, and in principle, all waiting passengers will make reservations for the desired destination floor. .

  If there are a lot of users waiting at the platform, as with a general elevator, one car could not carry all of them, and users who could not get on again registered the hall call (destination floor) and the next car I have to wait for arrival.

  In order to prevent such unloading, when there are many users, additional allocation is performed, and eventually, a plurality of cars are allocated to one landing.

  The prior arts related to the additional allocation will be listed below.

  First, in Patent Document 1, in the destination floor reservation type group management, the number of call registrations registered in the destination floor reservation device at the landing is counted, and the number of floors registered at the destination destination floor button exceeds a predetermined value. In this case, an example in which another car is additionally allocated is shown.

  Next, in Patent Document 2, although it is not destination floor reservation type group management, it is detected that there has been a predetermined number of times of landing call button operations within a predetermined time, and added preferentially to the corresponding landing call An example of making an assignment is shown.

  Patent Document 3 also shows an example of counting the number of registrations of landing call registered at one time and allocating elevators corresponding to the number of registrations, although it is not destination floor reservation type group management.

  Furthermore, Patent Document 4 shows an example in which an elevator in which the number of passengers in a predicted car exceeds a predetermined value is excluded from allocation candidate elevators in destination floor reservation type group management.

JP-A-7-232867 JP-A-5-97333 JP 2008-24412 A JP 2003-276916 A

  None of the conventional technologies listed above necessarily reduce waiting time and prevent leftovers.

  In the example shown in Patent Document 1, the number of registered floors by a landing destination floor button is used as a condition for performing additional allocation. However, when there are many users on the same destination floor, since the number of destination floors is small, additional allocation is not performed, and unloading occurs. Conversely, even if there are many destination floors and additional allocations are made, if there is only one user on each destination floor, there will be no waiting passengers at the platform even if additional allocation cars arrive. There may be waste.

  In the example shown in Patent Document 2, when a user determines that unloading occurs in one elevator dispatch, additional allocation is performed when the landing call button is pressed a predetermined number of times at a predetermined time. Can only be used by someone who knows. On the other hand, if it is abused by a user who knows this function, there is a possibility that the operation efficiency may decrease due to excessive additional allocation.

  In the example shown in Patent Document 3, the destination floor reservation type group management is not used, but a car is allocated as many times as the number of landing calls at the time of congestion. By allocating one car to one call, the number of stops per lap of one car can be reduced, but there is a possibility that the car will be called too much on one floor. This leads to a large reduction in driving efficiency.

  In the example shown in Patent Document 4, in the destination floor reservation type group management, the calculation of the number of passengers and the number of passengers getting off is used for the assignment of elevators by a learning function or sensor, and the same time every day such as attendance time and lunch time. If there is traffic demand, improvement in serviceability can be expected. However, there are cases where the learning function cannot handle a learning event before it works or a specific event or a meeting where a large number of people gather, because it does not depend on time factors. Optimal operation cannot be achieved without additional reliance on the learning function and additional allocation corresponding to the real-time traffic demand at that time.

  It is an object of the present invention to predict destination congestion before an assigned car arrives, to appropriately allocate a plurality of cars in accordance with the congestion state, and to reduce a leftover reservation group management It is to provide an elevator control device.

  In one aspect of the present invention, in the landing destination floor reservation type elevator group management system, the first assignment means for assigning the destination floor call reserved at the landing to the elevator car selected in the group management control device; When the elevator car assigned by the assigning means services the landing and departs, when the number of passengers in the predicted car exceeds a predetermined value, additional assigning means for additionally assigning another elevator car to the landing is provided. Features.

  In another aspect of the present invention, in a landing destination floor reservation type elevator group management system, first assignment means for assigning a destination floor call reserved at a landing to an elevator car selected in the group management control device; An arbitrary destination floor is additionally registered at the landing before the elevator car assigned by the one assigning means arrives at the landing, and the elevator car assigned by the first assigning means serves the landing. When the number of passengers in the predicted car at the time of departure exceeds a predetermined value, an additional assigning means for additionally assigning another elevator car to the landing is provided.

  In a preferred embodiment of the present invention, in the destination floor reservation type group management, the number of passengers in the car at the time of departure from the currently assigned car with respect to the destination floor reservation of the landing is registered as the destination destination floor call registration. Is predicted from the number of passengers, the predicted number of passengers in the car upon arrival, and the predicted number of passengers at the time of arrival, and compared with the capacity in the car, so that additional allocation is performed according to traffic demand.

  According to a preferred embodiment of the present invention, in the destination floor reservation type group management, it is possible to predict the congestion situation of the landing before arrival of the car, appropriately allocate a plurality of cars according to the congestion state, and reduce unloading. it can.

  Other objects and features of the present invention will become apparent in the embodiments described below.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is an overall configuration diagram of a landing destination floor reservation type elevator group management system according to an embodiment of the present invention. This elevator group management system is a group management using a system in which a destination floor is registered at a landing and a car is assigned according to the destination floor. The main structures are six elevator control devices 31, 32,... 36 and elevator cars 41, 442,. Each elevator device includes a car, a hoisting machine, a weight, a rope, and the like, but FIG. 1 illustrates only an elevator car and a rope. Next, the destination floor reservation devices 21, 22,... 29 are arranged on the elevator floor having a plurality of floors.

  When the destination floor reservation device 21, 22,... 29 reserves the destination floor using the numeric keypad, the destination floor and the assigned elevator car name are instantly displayed, and the display is immediately turned off. Therefore, the reservation person can know the reservation destination floor and the assigned elevator car, but the other users do not. For this reason, it is assumed that all the users who have come to the landing place individually reserve the destination floor.

  In the group management apparatus 10 that does not have the additional allocation function, the estimated arrival time calculation unit 101 of each car at the call generation floor uses the estimated arrival time of each car at the floor where the call is generated as the current position, direction, and speed of each car. It is calculated from the status of the call at the landing, destination call, and traffic demand. The number-of-stops calculation unit 102 of each car predicts the number of stops of the car from the landing call assigned to each car and the destination floor of the call.

  When assigning cars to hall calls, since the destination floor is known first, the number of stops for each car is reduced. Based on the calculated information, the first assigned car selection unit 105 selects the most appropriate car from a plurality of elevators.

  The group management apparatus 11 having an additional assignment function, which is the point of the present invention, is a group management control system using the calculation data of the group management apparatus 10 described above. The traffic demand determination unit 103 determines the traffic demand at that time or beyond from the number of passengers getting on and off between floors in that time zone, waiting time, time information, and past statistical data. For example, it is determined whether it is congested, normal, or quiet. The predicted passenger number calculation unit 104 at the time of departure calculates the predicted number of passengers at the time of departure from the number of times registered in the destination floor reservation device, the predicted number of passengers at the time of arrival, and the predicted number of passengers at the time of arrival. To do. The additional allocation execution determination unit 106 compares the calculated predicted number of passengers in the car at the time of departure with a reference value obtained by multiplying the capacity in the car according to the congestion demand by a certain ratio, and predicts occurrence of unloading. To do. If it is predicted that there will be unloading, additional allocation will be performed. This additional assignment execution determination will be described in detail with reference to FIG.

  When the additional allocation car selection unit 107 receives the determination of the additional allocation execution by the additional allocation execution determination unit 106, the most appropriate car is determined in consideration of the estimated arrival time, the number of stops, traffic demand, and the like. Assign additional.

  Finally, the information assigned by the first assigned car selection unit 105 and the additional assigned car selection unit 107 is transmitted to the control device 31, 32, or 36 of the corresponding car.

  Next, FIG. 2 is an additional allocation process flow diagram in the landing destination floor reservation type elevator group management system according to one embodiment of the present invention. The flow from call generation by the elevator group management system to additional allocation processing will be described using this flowchart.

  The flowchart of FIG. 2 starts by registering a destination floor at a platform where an elevator user is located. First, a variable k indicating the car number is initialized to zero (ST01). Then, it is determined whether or not the k-th unit (hereinafter referred to as k-th unit) is an assignable unit. (ST02). Here, whether or not the car can be allocated is determined by determining whether or not the car is actually serviceable, such as whether the number of passengers in the car is full or whether it is predicted that the car will be full before arrival at the landing. If the allocation is possible, the process goes to the next step. If the allocation is impossible, 1 is added to the value of k, and the same process is executed for the next unit (ST05).

  If the k-th car can be assigned, the evaluation value of the first assigned car is calculated for the k-th car (ST03). This evaluation value is calculated based on the estimated arrival time when the call of the relevant landing is assigned to the k-th car, the estimated waiting time of each call that has already been handled, the predicted service completion time, the predicted number of stops, and the like.

  Next, it is checked whether or not the processing has been completed for all units (ST04). If not completed, 1 is added to the value of k, and the evaluation value calculation target is moved to the next unit (ST05). ).

  If the processing has been completed for all the cars, the first assigned car is selected based on the evaluation value of the first assigned car of each assignable car (ST06). This selection is based on the evaluation value of the first assigned car of each unit, and the waiting time of the entire call including the corresponding landing is as short as possible, the service completion time of each call is as short as possible, and the number of stops is reduced. Calls are assigned to such units.

  When the first assigned car is determined for the registered destination floor call, it is determined whether additional car assignment is necessary (ST07). Details of this determination will be described later in detail with reference to FIG. If the additional car assignment execution condition is not satisfied, the additional assignment is not executed (ST08), and the process is exited. If the additional car allocation execution condition is satisfied, the variable k representing the car number is initialized to zero (ST09). Next, it is checked that the k-th car is not the first assigned car (ST10). If it is the first assigned car, 1 is added to the value of k, and the process proceeds to the next machine (ST14). If the k-th car is not the first assigned car, it is determined whether the k-th car can be assigned (ST11). If the k-th car is not an assignable car, 1 is added to the value of k, and the process proceeds to the next car (ST14). If the k-th car is an assignable car, the evaluation value of the additional assigned car is calculated (ST12). This evaluation value is calculated based on the estimated arrival time at the landing when the call of the landing is assigned to the k-th car, the predicted waiting time of the call already handled, the predicted service completion time, the number of predicted stops, and the like. Next, it is checked whether or not the processing has been completed for all the units (ST13). If not, 1 is added to the value of k, and the evaluation value calculation target for the additional assigned car is next. (ST14). If completed, the optimum additional assigned car is selected from the evaluation value of the additional assigned car of each assignable car (ST15).

  As described above, an appropriate first assigned car is immediately determined and displayed for the reserved destination floor call, and in addition, the traffic demand at that time is taken into account, and an additional car is assigned. It is possible to prevent unloading and reduce waiting time.

  Next, details of the additional assignment execution determination condition (ST07) in FIG. 2 will be described with reference to FIG.

  FIG. 3 is a flowchart of additional assignment execution determination processing according to an embodiment of the present invention.

  When the first destination floor call is reserved at the landing, as shown in the flowchart of FIG. 2, an optimal car in the situation is assigned. In FIG. 3, first, after the first destination floor registration, it is checked whether the second destination floor call (regardless of the destination floor) is registered at the platform (ST20). If there is no plurality of destination floor registrations, no additional assignment is performed (ST26). If there are a plurality of destination floor registrations, the number of registrations is counted, and the number of waiting places at the landing is calculated (ST21). Using this value, the predicted number of passengers in the car at the time of departure from the landing is calculated as follows. That is, the estimated number of passengers at arrival is subtracted from the predicted number of passengers in the car upon arrival at the landing determined by the destination floor reservation device, and the waiting number at the landing calculated in (ST21) is added. Thus, the number of passengers in the predicted car at the time of departure from the landing is calculated (ST22). By comparing 80% of the passenger capacity in the car with the predicted number of passengers in the car at the time of departure from the landing of the currently assigned car, it is determined whether or not to carry out additional assignment (ST23).

  In this embodiment, 80% of the car's capacity is listed as the judgment target, but it is not fixed to a fixed value in this way. Actually, it is judged whether it is congested, normal, or quiet depending on traffic demand. It is necessary to select a value corresponding to the result. For example, setting 80% of the car's capacity during busy hours, 60% of the car's capacity during normal times, and 40% of the car's capacity when it is quiet makes the service more efficient.

  Now, if the predicted number of passengers in the car at departure is less than 80% of the capacity in the car, no additional allocation will be implemented (ST26), and the predicted number of passengers in the car at departure will be 80% or more of the capacity in the car. If there is, the execution of additional allocation is determined (ST24), and the process proceeds to additional allocation car selection (ST25).

  The above is the condition for performing the additional assignment of the present embodiment.

  Next, two different operation examples will be given, and the effects when this control function is used will be specifically described based on the image diagrams of FIGS.

[Operation Example 1]
First, FIGS. 4 and 5 show the difference in effect depending on the presence or absence of a known additional assignment function.

  FIG. 4 is an image diagram of a fourth floor landing of an elevator having a normal landing destination floor reservation function that does not have an additional allocation function, and is controlled only by the group management device 10 of FIG.

  In this example, only two units A and B will be noted for easy understanding. The maximum number of elevators is 10.

  FIG. 4A shows a situation in which eight waiting customers 401 at a certain landing are each waiting after having reserved a destination floor above the floor by the destination floor reservation device 402. Furthermore, suppose that five people have already boarded the No. A which is the first assigned car.

  In the case of not having the additional allocation function, even if the allocated car No. A arrives, since the boarding capacity is 10, all eight waiting passengers 401 cannot get into the No. A elevator. That is, as shown in FIG. 4B, five passengers 4011 out of eight waiting customers 401 can get on the Unit A elevator, but the remaining three passengers 4012 get on the Unit A elevator. Unable to do so, the Unit A elevator departs full.

  As a result, as shown in FIG. 4 (C), the three passengers 4012 who could not get on the elevator of Unit A enter again the destination floor reservation in the destination floor registration device 402, and the next elevator I have to wait for arrival.

  FIG. 5 is an image diagram of the elevator on the fourth floor of the elevator having a landing destination floor registration function having a conventional additional allocation function. Control is performed based on the group management apparatus 10 of FIG. 1 and the conventional additional allocation function. Yes.

  In contrast to FIG. 4 described above, FIG. 5 provides a known additional allocation function to distribute users to a plurality of cars and prevent unloading in FIG. 4 as described below. Can do.

  Here, it is assumed that the additional allocation condition is “stop destination floor registration count ≧ 80% of the capacity in the car”.

  As shown in FIG. 5A, the boarding area is congested, and eight passengers 401 are each waiting for the elevator after completing the destination floor reservation. However, unlike FIG. 4 (A), 8 people made reservations for landing destination floors for 10 passengers, so the additional allocation condition “number of registrations for landing destination floors ≧ 80% of capacity in car” is It is satisfied, and the B machine is additionally allocated to the landing.

  As a result, as shown in FIG. 5 (B), it is possible to get on either A or B, and no unloading occurs as shown in FIG. 5 (C).

  As described above, the additional allocation function has the effects of preventing unloading by quick allocation addition at the time of congestion and reducing waiting time and service completion time.

[Operation example 2]
Next, the usefulness of the present invention regarding the additional allocation condition will be described using the operation examples of FIGS. 6 and 7, different additional assigned car selection conditions are provided, and the difference in movement is shown.

  In FIG. 6, the additional allocation condition is executed when the number of registrations at the landing destination floor exceeds a predetermined value (eight times: equivalent to 80% of the capacity in the car) as in FIG. This is a condition that is also used in many background technologies.

  As a precondition of FIG. 6, as shown in FIG. 6 (A), Unit A 601 is stopped on the second floor, and Unit B 602 is stopped on the first floor. The fifth floor is the destination floor. On the fourth floor, five users 603 have completed the reservation for the landing destination floor to the fifth floor and are waiting for the arrival of the car. That is, the number of registrations for the landing destination floor on the fourth floor is five.

  In this example as well, for the sake of easy understanding, it is assumed that only the two units A and B are focused and the first assigned elevator is the unit A 601. The number of passengers in the car is 10 people.

  As shown in FIG. 6B, under the condition of FIG. 6, the number of landing registrations 5 times does not satisfy the additional allocation condition 8 times, and the additional allocation is not executed. Therefore, even if the assigned Unit A 601 arrives, the capacity in the car is ten, so one unloading 604 occurs. As a result, as shown in FIG. 6 (C), the user 604 who could not get on the car must make a destination floor reservation again and wait for the next car to arrive.

  Therefore, if the additional allocation condition is simply set by the number of registrations at the landing destination floor, as in operation example 1 shown in FIG. 5, many users are waiting at a certain landing, and if the number of registrations at the destination floor is large, Additional assignments may be made and the results may be good. However, as in the operation example of FIG. 6, the destination floor registration count is 5 times, and if it is less than the predetermined value 8 times, there is a disadvantage that additional allocation is not performed even when additional allocation is required.

  On the other hand, in FIG. 7 using the embodiment of the present invention, as shown in the flowchart of FIG. 3, the additional allocation condition is determined as to whether or not the number of passengers in the car at the departure from the allocated platform exceeds a predetermined value. It is set by. That is, based on the number of registrations at the landing destination floor, the predicted number of passengers in the car at the time of departure from the corresponding floor is calculated, and the value is determined according to the traffic demand (in this embodiment, 80% of the capacity in the car). If it exceeds, it is set to execute additional allocation.

  According to the embodiment of the present invention, even when the number of destination floor registrations is small as shown in FIG. 7, additional allocation can be performed by preventing the number of passengers in the predicted car from exceeding a predetermined value, thereby preventing unloading.

  As shown in FIG. 7B, if the number of waiting customers at the landing is five and the destination floor reservation operation is performed individually, the number of destination floor registrations is five. In addition, the number of passengers in the car when arriving on the 4th floor is 6, and if this is left, the estimated number of passengers in the car when leaving the 4th floor will be 11 people, which is a predetermined value according to traffic demand (this implementation In the example, it exceeds 80% of the car capacity. Therefore, additional allocation is executed because the additional allocation condition is satisfied.

  Thereby, as shown in FIG.7 (C), an efficient operation service can be performed, without remaining.

  In the operation example of FIG. 7, since it is assumed that the vehicle is congested, the additional allocation conditional expression is “predicted number of passengers at departure ≧ 80 capacity in the car”. However, as explained in step ST23 of FIG. 3, a more efficient operation service is possible by changing the ratio of the right side of the additional allocation conditional expression to the capacity in the car according to the traffic demand situation.

  As described above, according to the embodiment of the present invention, by performing additional allocation according to traffic demand, it is possible to prevent unloading and reduce waiting time.

1 is an overall configuration diagram of a landing destination floor reservation type elevator group management system according to an embodiment of the present invention. FIG. The additional allocation process flow figure in the landing destination floor reservation type elevator group management system by one Example of this invention. The additional allocation execution determination processing flowchart by one Example of this invention. The fourth-floor landing image figure of the elevator provided with the normal landing destination floor reservation function which does not have an additional allocation function. The fourth floor landing image figure of the elevator provided with the landing destination floor registration function with the conventional additional allocation function. The image figure which shows the elevator operation | movement when only the number of registrations of landing destination floors is made into an additional car allocation condition. The image figure which shows the elevator operation | movement at the time of making the number of passengers in the estimated car at the time of departure by the one Example of this invention into an additional car allocation condition.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10,11 ... Group management device, 21-29 ... Landing destination floor reservation device, 31-36 ... Unit control device, 41-46 ... Elevator car, 402 ... Landing destination floor reservation device, 401 ... Landing waiting customer, 4011 ... A Passenger to No. 40, 4012 ... Unloader, 601 ... No. A, 602 ... No. B, 603 ... Waiting passengers on the 4th floor.

Claims (3)

Group management control device that manages the operation of multiple elevators serving multiple floors, a destination floor reservation device that reserves the destination floor of the elevator provided at the landing, and an elevator that is assigned the reserved destination floor In an elevator group management system comprising an automatic registration means for automatically registering in the operation panel in the car and a passenger number prediction means for predicting the number of passengers in the elevator car,
The destination floor reservation device is configured to display the name of the elevator car assigned to the destination floor and immediately turn off the display when the destination floor is reserved.
First assigning means for assigning a destination floor call reserved at the landing to an elevator car selected in the group management control device;
When the assigned car arrives at the landing, the estimated number of passengers in the car when the elevator car assigned by the first assigning means is provided in the car occupant number predicting means and services the departure place. The predicted number of passengers when the assigned car arrives at the platform is subtracted from the estimated number of passengers in the platform, and the number of passengers at the platform calculated based on the number of registered destination floors in the destination floor reservation device of the platform Predicted number of passengers at the time of departure, which calculates by adding the number of waiting people,
Addition that additionally allocates another elevator car to the landing when the estimated number of passengers in the departure car exceeds the predetermined value when the elevator car assigned by the first allocating means services and departs the landing An elevator group management system comprising an assigning means. Group management control device that manages the operation of multiple elevators serving multiple floors, a destination floor reservation device that reserves the destination floor of the elevator provided at the landing, and an elevator that is assigned the reserved destination floor In an elevator group management system comprising an automatic registration means for automatically registering in the operation panel in the car and a passenger number prediction means for predicting the number of passengers in the elevator car,
The destination floor reservation device is configured to display the name of the elevator car assigned to the destination floor and immediately turn off the display when the destination floor is reserved.
First assigning means for assigning a destination floor call reserved at the landing to an elevator car selected in the group management control device;
When the assigned car arrives at the landing, the estimated number of passengers in the car when the elevator car assigned by the first assigning means is provided in the car occupant number predicting means and services the departure place. The predicted number of passengers when the assigned car arrives at the platform is subtracted from the estimated number of passengers in the platform, and the number of passengers at the platform calculated based on the number of registered destination floors in the destination floor reservation device of the platform Predicted number of passengers at the time of departure, which calculates by adding the number of waiting people,
Before the elevator car assigned by the first assigning means arrives at the landing, an arbitrary destination floor is additionally registered at the landing, and the elevator car assigned by the first assigning means serves the landing An elevator group management system comprising: additional assignment means for additionally assigning another elevator car to the landing when the predicted number of passengers in the car at the time of departure exceeds a predetermined value.   3. The elevator group management system according to claim 1 or 2, wherein the predetermined value is a value obtained by multiplying different coefficient values according to traffic demand during congestion, during normal times, or during quiet periods.

Images