JP6109403B2 - Elevator group management control device and elevator group management control method - Google Patents

Description

  The present invention relates to an elevator group management control device and an elevator group management control method for determining an optimal allocation car for a registered landing destination call when a landing destination call is registered by a landing destination floor registration device. .

  Conventionally, if a hall lantern indicating the direction of travel of the car arriving at the landing on each floor is not installed at the landing on each floor, when the passenger gets on the car, the car departs in the direction opposite to the direction of the passenger's destination floor. A car reverse direction starting event will occur.

  In order to suppress the occurrence of such a reverse car departure event, for example, when determining the assigned car for a new landing destination call newly registered by the landing destination floor registration device, the direction of the passenger's destination floor and There is an elevator system that does not assign a car scheduled to start in the reverse direction (see, for example, Patent Document 1).

Japanese translation of PCT publication No. 2013-523566 (FIG. 1) Japanese Patent No. 3498632 (FIG. 3C)

However, the prior art has the following problems.
In the prior art described in Patent Document 1, there is a situation in which a car reverse departure event occurs on a floor (hereinafter referred to as a specific floor) where the number of passengers in the elevator is larger than other floors. We do not consider that it occurs frequently. In addition, as a specific example of such a specific floor, a lobby floor is mentioned, for example.

  That is, in the specific floor, a landing destination call whose destination floor is a floor above the specific floor is frequently registered, so that a situation in which a reverse car departure event occurs frequently occurs.

  In such a case, when the prior art described in Patent Document 1 is applied, a car reverse departure event occurs on a specific floor for a landing destination call whose destination floor is a floor above the specific floor. The car that is suitable for assignment is determined by excluding such a car. However, even if it is possible to suppress the occurrence of reverse car departure events by simply determining the assigned car using such a method, the waiting time for passengers will be longer at a specific floor, and the elevator operation efficiency will be increased. There is a problem that gets worse.

  The present invention has been made in order to solve the above-described problems. The elevator group management control is capable of suppressing the occurrence of a car reverse direction departure event and improving the operation efficiency of the elevator as compared with the prior art. An object is to obtain a device and an elevator group management control method.

The elevator group management control device according to the present invention includes an allocation candidate determination unit that determines an allocation candidate car for a landing destination call registered by the landing destination floor registration device, and an allocation candidate car determined by the allocation candidate car determination unit, Allocation car determination unit that determines the allocation car for the landing destination call, and a group management control unit that performs group management control of the elevator by allocating the allocation car determined by the allocation car determination unit to the floor where the landing destination call is generated And an elevator group management control device, wherein the upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor, and a newly registered new landing destination When the call is called “upper floor → specific floor”, the assignment candidate car determination unit excludes the assigned car for the already registered call “lower floor” as a specific process, and creates a new landing destination. The assigned car determination unit determines a car for the new landing destination call from among the allocation candidate cars for the new landing destination call determined by the assignment candidate car determining unit. The assigned car for the new landing destination call is determined by excluding the car where the event occurs.

In the elevator group management control method according to the present invention, an elevator group management control device that determines an assigned car for a landing destination call registered by the landing destination floor registration device calls a newly registered new destination destination call. This is an elevator group management control method that is executed when it is "specific floor", where the upper floor is the floor above the specific floor, the lower floor is the floor below the specific floor, and has already been registered A step of determining an allocation candidate car for the new landing destination call by excluding an allocation car for the already called call "lower floor", and the new landing destination call from among the allocation candidate cars for the determined new landing destination call Determining a car assigned to the new landing destination call by excluding a car that causes a car reverse departure event when assigned to Than is.

  According to the present invention, it is possible to obtain an elevator group management control device and an elevator group management control method capable of suppressing the occurrence of a reverse car departure event and improving the operation efficiency of an elevator.

1 is a configuration diagram of an elevator system including an elevator group management control device according to Embodiment 1 of the present invention. In Embodiment 1 of this invention, it is explanatory drawing for demonstrating a car reverse direction start event. It is explanatory drawing for comparing operation | movement with the elevator group management control apparatus in Embodiment 1 of this invention, and the conventional elevator group management control apparatus. It is explanatory drawing for comparing operation | movement with the elevator group management control apparatus in Embodiment 1 of this invention, and the conventional elevator group management control apparatus. It is explanatory drawing for comparing operation | movement with the elevator group management control apparatus in Embodiment 1 of this invention, and the conventional elevator group management control apparatus. It is explanatory drawing for comparing operation | movement with the elevator group management control apparatus in Embodiment 1 of this invention, and the conventional elevator group management control apparatus. It is explanatory drawing for comparing operation | movement with the elevator group management control apparatus in Embodiment 1 of this invention, and the conventional elevator group management control apparatus. It is a flowchart which shows a series of operation | movement of the elevator group management control apparatus in Embodiment 1 of this invention. It is a flowchart which shows a series of operation | movement of the elevator group management control apparatus in Embodiment 2 of this invention.

  Hereinafter, preferred embodiments of an elevator group management control device and an elevator group management control method of the present invention will be described with reference to the drawings. In the description of the drawings, the same reference numerals are assigned to the same elements, and duplicate descriptions are omitted. Here, a case where the above-described specific floor is the lobby floor will be described as an example.

Embodiment 1 FIG.
FIG. 1 is a configuration diagram of an elevator system including an elevator group management control device 30 according to Embodiment 1 of the present invention. In addition, in FIG. 1, the case where the elevator group management control apparatus 30 in an elevator system manages four elevators (A unit-D unit) as a group as a plurality of elevators installed in the building is illustrated. ing.

  In FIG. 1, a landing destination floor registration device 10 is installed at each of a plurality of stop floors, for example, one at each stop floor. The landing destination floor registration device 10 is for an elevator user to register a landing destination call at the landing. The user can register a landing destination call before boarding the car by operating the landing destination floor registration device 10.

  The elevator control device 20 controls each operation (travel of the car) of the elevators A (car A) to D (car D).

  The elevator group management control device 30 includes an allocation candidate car determination unit 31, an allocation car determination unit 32, and a group management control unit 33.

  The allocation candidate car determination unit 31 determines a car candidate to be allocated to a landing destination call registered by the landing destination floor registration device 10 as an allocation candidate car.

  The allocation car determination unit 32 determines an allocation car as a car to be allocated to a landing destination call registered by the landing destination floor registration device 10 from among the allocation candidate cars determined by the allocation candidate car 31.

  The group management control unit 33 instructs the elevator control device 20 to run the assigned car determined by the assigned car determining unit 32 to the floor where the landing destination call is generated. In addition, the group management control unit 33 displays the assigned car determined by the assigned car determination unit 32 on the display screen of the landing destination floor registration device 10. By being displayed in this way, the passenger can confirm the car on which he / she should get on.

  Next, referring to FIG. 2 to FIG. 4B, to suppress the occurrence of the reverse car departure event and improve the operation efficiency of the elevator, which is realized by the elevator group management control device 30 in the first embodiment. However, it explains in detail.

  In the following, for the landing destination call registered by the landing destination floor registration device 10, the landing destination call is “the boarding floor is a floor above the specific floor and the destination floor is the specific floor”. This is called “upper floor → specific floor”. A hall destination call “at least one of the boarding floor and the destination floor is a floor below the specific floor” is referred to as a “lower floor”. Furthermore, the hall destination call “the boarding floor is a specific floor and the destination floor is a floor above the specific floor” is referred to as “specific floor → upper floor”. Here, because the specific floor is the lobby floor, these three types of hall destination calls are called “upper floor → lobby floor”, “lower floor”, and “lobby floor → upper floor”, respectively. The Rukoto.

  The building illustrated in FIGS. 2 to 4B is a building having 2 floors below ground and 16 floors above ground having floors B2F to 16F, and 1F is a lobby floor with many elevator passengers. In this case, floors below the lobby floor are B1F and B2 (basement floor) with fewer users, and floors above the lobby floor are 2F to 16F.

  First, the reverse car departure event will be described with reference to FIG. FIG. 2 is an explanatory diagram for explaining a car reverse direction starting event in the first embodiment of the present invention.

In FIG. 2, it is assumed that the elevator A is under group management control under the following conditions.
The car A is traveling in the Down direction from 8F and is controlled to stop at the lobby floor, which is the destination floor.
The assigned car for the already registered call “lower floor (B2F)” is car A.
The car A is determined as the assigned car for the newly registered call “lobby floor → upper floor (6F)”.
If the elevator No. A is controlled under such conditions, the car A will stop in the order of the 8F running, the lobby floor, the B2F, the lobby floor, and the 6F, as shown in FIG.

  Here, if a hall lantern indicating the direction of travel of the car arriving at the landing on each floor is not installed at the landing on each floor, the passenger who registered the landing destination call on the lobby floor will proceed in the planned direction of the car arriving at the lobby floor I don't know. The car A is a car scheduled to depart for B2F in the direction opposite to the direction of 6F, which is the passenger's destination floor. Therefore, if the car A gets on the lobby floor from the 8th floor, the passenger goes to the B2F even though he wants to go to the 6th floor. Thus, a car reverse departure event occurs in which the car departs in the direction opposite to the passenger's desired direction.

  Next, an operation example of the elevator group management control device 30 according to the first embodiment under a first condition described later will be described in comparison with the conventional example with reference to FIGS. 3A to 3C. 3A to 3C are explanatory diagrams for comparing the operations of the elevator group management control device 30 and the conventional elevator group management control device according to Embodiment 1 of the present invention.

  Here, it is assumed that the elevator No. A to the elevator D are under group management control under the following first condition. Note that, under the first condition, a situation where there are many passengers on the lobby floor (that is, a situation where the car stops frequently on the lobby floor) is shown.

(1) Elevator No. A Car A is traveling in the Up direction from 7F, and is controlled to stop sequentially at 12F, 13F and 16F, which are destination floors.
The assigned car for the call that has already been registered (14F → 2F) is car A.
If the elevator A is controlled under such conditions, the car A will stop in the order of 12F, 13F, 16F, 14F, and 2F from 7F during traveling.

(2) Elevator No. B-Car B is traveling from 4F to Down and is controlled to stop at the lobby floor, which is the destination floor.
・ Registered calls “Lobby floor → Upper floor (6F)”, “Lobby floor → Upper floor (9F)”, “Lobby floor → Upper floor (11F)”, “Lobby floor → Upper floor (15F)” The assigned car is car B.
If the elevator No. B is controlled under such conditions, the car B will stop in the order of the 4F during traveling, the lobby floor, 6F, 9F, 11F, and 15F.

(3) Elevator C No. ・ Car C is traveling in the down direction from 13F.
The assigned car for the already registered call “upper floor (11F) → lobby floor” is car C.
・ For registered calls “Lobby Floor → Upper Floor (3F)”, “Lobby Floor → Upper Floor (5F)”, “Lobby Floor → Upper Floor (7F)”, “Lobby Floor → Upper Floor (10F)” The assigned car is car C.
If the elevator C is controlled under these conditions, the car C will stop in the order of 11F, lobby floor, 3F, 5F, 7F, and 10F from the 13F that is running.

(4) Elevator D Unit ・ Car D is traveling in the down direction from 9F.
The assigned car for the already registered call “lower floor (B2F)” is car D.
If the elevator No. D is controlled under such conditions, the car D will stop at B2F from 9F during traveling.

  Next, in the situation where the elevators A to D are under group management control under the first condition as described above, the call “upper floor → lobby floor” is newly registered as shown in FIG. 3A. And In FIG. 3A, as a specific example of a newly registered call “upper floor → lobby floor”, a case where the landing floor is 6F and the destination floor is the lobby floor is illustrated.

  Here, the elevator group management control device 30 according to the first embodiment considers the existence of an assigned car for the registered call “lower floor” and assigns it to the newly registered “upper floor → lobby floor”. Decide on a basket. In other words, the car in which the call “lower floor” has already been registered is excluded from the assigned car for the newly registered call “upper floor → lobby floor”.

  FIG. 3A illustrates a case where the destination floor is B2F as a specific example of the registered “lower floor”. Further, the case where the assigned car for the already registered call “lower floor” is the car D is illustrated.

  On the other hand, in the conventional elevator group management control device, the allocation to the newly registered call “upper floor → lobby floor” is performed without considering the existence of the allocation car for the already registered call “lower floor”. Decide on a basket.

  Specifically, in the conventional elevator group management control device, when a car is assigned to a newly registered landing destination call, the car that minimizes the increase in the waiting time of the passenger is preferentially selected as the assigned car. It is often configured as follows.

  Further, the conventional elevator group management control device exemplified here allocates a plurality of hall calls to a floor with many passengers such as a lobby floor, and limits the number of destination floors that each car takes to, for example, four. Thus, it is assumed that the number of transporters per unit time is further improved (see, for example, Patent Document 2).

  In such a case, in the case of FIG. 3A, the car D having the smallest increase in waiting time is determined as an assigned car for the newly registered call “upper floor → lobby floor” among the cars A to D. However, without considering the existence of the assigned car for the registered call “lower floor”, as shown in FIG. 3B, after the car D is determined as the assigned car, a new call “lobby floor → upper floor” is obtained. If is registered, the operation efficiency of the elevator will deteriorate.

  FIG. 3B illustrates a case where the boarding floor is 1F and the destination floor is 14F as a specific example of a newly registered call “lobby floor → upper floor”.

  That is, for the newly registered call “lobby floor → upper floor”, the assigned car is determined as follows. In the case of FIG. 3B, the car B and the car C are in a state where four destination floor numbers from the lobby floor have already been assigned. Specifically, as shown in FIG. 3B, the car B has destination floors 6F, 9F, 11F, 15F from the lobby floor, and the car C has destination floors 3F, 5F, 7F, from the lobby floor. 10F. Thus, since the number of destination floors from 1F is four, which is the limit value, the car B and the car C are not assigned to the newly registered call “lobby floor → upper floor”.

  Further, when the car D is determined as the assigned car for the newly registered call “lobby floor → upper floor”, a car reverse departure event occurs on the lobby floor. That is, as shown in FIG. 3B, after the car D arrives at the lobby floor, it travels to B2F. And the passenger who is in the lobby floor (newly registering the call “lobby floor → upper floor”) gets on the car D when it arrives on the first floor and goes to the B2F even though she wants to go to the 14th floor. It will be. Therefore, in order to suppress the occurrence of the reverse car departure event, the car D is not suitable as an assigned car for the newly registered call “lobby floor → upper floor”.

  From the above, the assigned car for the newly registered call “lobby floor → upper floor” is car A. However, when the car A is determined as the assigned car for the newly registered call “lobby floor → upper floor”, the car A stops in order on a total of five floors of 12F, 13F, 16F, 14F, and 2F. Later, it will stop at the lobby level. Therefore, although the occurrence of the reverse car departure event can be suppressed, the waiting time for passengers on the lobby floor is increased with the suppression of the occurrence of the reverse car departure event. That is, conventionally, even if the occurrence of a car reverse direction departure event can be suppressed, the accompanying deterioration in the elevator operation efficiency cannot be suppressed.

  In addition, since there are many passengers on the lobby floor, it is considered that there are many situations in which calls “lobby floor → upper floor” are newly registered one after another as in the case of FIG. 3B. Therefore, in the conventional elevator group management control device, the waiting time for passengers in the lobby floor often becomes long, and as a result, the operation efficiency of the elevator deteriorates.

  As described above, the present inventors have a longer waiting time for passengers in the lobby floor where there are many passengers even if the conventional elevator group management control device can suppress the occurrence of a reverse car departure event. As a result, we found a new problem that the operation efficiency of the elevator deteriorates.

  Therefore, in the present invention, focusing on such a new problem, there is provided an elevator group management control device 30 that can suppress the occurrence of a reverse car departure event and can improve the operation efficiency of the elevator compared to the conventional one. To do.

  As described above, the elevator group management control device 30 according to the first embodiment takes into account the existence of an assigned car for the already registered call “lower floor” and calls newly registered “upper floor → lobby floor”. Is assigned to the car. Therefore, it is possible to suppress the occurrence of a reverse car departure event and improve the operation efficiency of the elevator.

  That is, in the case of FIG. 3A, the elevator group management control device 30 according to the first embodiment corresponds to the already registered call “lower floor” as the assigned car for the newly registered call “upper floor → lobby floor”. The allocation car is not allocated.

  In other words, the car that stops at the basement (here, car D) is not assigned to the newly registered call “upper floor → lobby floor”. Accordingly, for the newly registered call “upper floor → lobby floor”, cars A to C other than the car D (that is, cars that do not move to B1F and B2F) are determined as allocation candidate cars, and this allocation candidate The allocation car is determined from the cars by adopting a conventional allocation method. Here, as a result of adopting the conventional allocation method, it is assumed that the car C is determined as the allocation car from the allocation candidate cars including the cars A to C.

  Next, as shown in FIG. 3C, after the car C is determined as the assigned car for the newly registered call “upper floor → lobby floor”, as in the case of FIG. 3B, the call “lobby floor → upper floor”. Is newly registered, the assigned car is determined as follows. In order to compare with the conventional elevator group management control device, the cars B and C whose destination floor numbers from the lobby floor are four of the limit values are for the newly registered call “lobby floor → upper floor”. The case where it cannot enter into an allocation candidate basket is illustrated.

  In such a case, cars A and D other than cars B and C are selected as allocation candidate cars for the newly registered call “lobby floor → upper floor”. Even if the car A or the car D, which is the allocation candidate car, is determined as the allocation car, the car reverse departure event does not occur on the lobby floor. Therefore, a car in which a car reverse departure event occurs is not excluded from the allocation candidate cars.

  From the above, the case of FIG. 3B in which the waiting time of passengers in the lobby floor is earlier by allocating the car D that arrives at the lobby floor first after stopping at the basement floor from among the candidate cars for allocation. Shorter than That is, in the case of FIG. 3C, it is possible to serve passengers on the lobby floor with a shorter waiting time than the case of FIG. 3B.

  As described above, the elevator group management control device 30 according to the first embodiment takes into account the existence of the assigned car (car D) for the already registered call “lower floor”, and the newly registered call “upper floor”. Decide the car for “→ Lobby Level”. Specifically, if the call “upper floor → lobby floor” is newly registered, the allocation candidate car (car A) determined to exclude the assigned car (car D) for the registered call “lower floor”. ~ C) to determine the assigned car.

  As a result, there is no situation where the car (car D) originally scheduled to stop on the basement floor stops on the lobby floor as the call “upper floor → lobby floor” is newly registered. Therefore, even if the call “lobby floor → upper floor” is newly registered, there is no situation where the car (car D) scheduled to stop on the basement floor stops on the lobby floor before stopping on the basement floor. The car reverse direction starting event can be suppressed. In addition, the car (car D) after stopping at the basement floor (after the service is terminated on the basement floor) can be included in the candidate car for the newly registered call “lobby floor → upper floor”. The operation efficiency of the elevator can be improved as compared with the conventional one.

  Next, an operation example of the elevator group management control device 30 according to the first embodiment under the second condition described later will be described in comparison with the conventional example with reference to FIGS. 4A and 4B. 4A and 4B are explanatory diagrams for comparing the operations of the elevator group management control device 30 and the conventional elevator group management control device according to Embodiment 1 of the present invention.

  Here, in the conventional elevator group management control device, as described above, when the assigned car for the newly registered call “upper floor → lobby floor” is determined, the already registered call “lower floor” Since the existence of the assigned car is not taken into account, the elevators A to D may be subjected to group management control under the second condition as described below.

(1) Elevator A ・ Car A is traveling in the Down direction from 8F and is controlled to stop at the lobby floor, which is the destination floor.
The assigned car for the already registered call “lower floor (B2F)” is car A.
If the elevator No. A is controlled under such conditions, the car A will stop in the order of the 8F running and the lobby floor and B2F.

(2) Elevator B ・ Car B is traveling in the down direction from 15F.
The assigned car for the registered call “lower floor (B1F)” is car B.
If the elevator No. B is controlled under such conditions, the car B will stop at 15F from the running 15B.

(3) Elevator C No. C ・ Car C is traveling in the Down direction from 7F.
The assigned car for the already registered call “upper floor (5F) → lobby floor” is car C.
The assigned car for the already registered call “lower floor (B1F)” is car C.
If the elevator C is controlled under such conditions, the car C will stop in the order of the running 7F, 5F, lobby floor, B1F.

(4) Elevator D No. D The car D is traveling in the Down direction from 9F and is controlled to stop at the lobby floor, which is the destination floor.
The assigned car for the registered call “lower floor (B2F)” is car D.
If the elevator No. D is controlled under such conditions, the car D will stop in the order of 9F during traveling, lobby level, and B2F.

  Here, in the situation where the elevators A to D are under group management control under the second condition as described above, as shown in FIG. 4A, the call “lobby floor → upper floor” is newly registered. And FIG. 4A illustrates a case where the boarding floor is 1F and the destination floor is 14F as a specific example of a newly registered call “lobby floor → upper floor”.

  In such a case, if any of the car A, the car C, and the car D is determined as the assigned car, a car reverse departure event occurs. Therefore, in order to suppress the occurrence of the reverse car departure event, the car B is determined as the assigned car for the newly registered call “lobby floor → upper floor”.

  Further, as shown in FIG. 4B, after the car B is determined as the assigned car for the newly registered call “lobby floor → upper floor”, the call “upper floor → lobby floor” is further newly registered. And FIG. 4B illustrates a case where the boarding floor is 13F and the destination floor is the first floor as a specific example of the newly registered call “upper floor → lobby floor”.

  In such a case, if the nearest car B is determined as the assigned car for the call “upper floor → lobby floor”, the car reverse departure event will occur. Not suitable as.

  Therefore, the car assigned to the call “upper floor → lobby floor” is one of the car A, the car C, and the car D. However, even if any of these becomes the assigned car, the car corresponds to the newly registered call “upper floor → lobby floor” after stopping in the basement floor while traveling in the Down direction. Therefore, although it is possible to suppress the occurrence of a car reverse direction departure event, the waiting time for passengers in 13F becomes longer, and the operation efficiency of the elevator deteriorates.

  Here, the elevator group management control device 30 according to the first embodiment considers the number of assigned cars for the already registered call “lower floor” and limits the number of assigned cars, thereby reversing the car. While suppressing the occurrence of a direction departure event, the operation efficiency of the elevator can be improved.

  However, in the conventional elevator group management control device, when a call “lower floor” is newly registered, it is newly registered without considering the number of cars assigned to the already registered call “lower floor”. Determine the assigned car for the call “lower floor”. Therefore, the number of cars scheduled to stop on the basement floor increases, and in some cases, all elevator cars (cars A to D) that are group-controlled are scheduled to stop on the basement floor as in the case of FIG. 4A. . Therefore, when the call “upper floor → lobby floor” is newly registered under such circumstances as in the case of FIG. 4B, the operation efficiency of the elevator deteriorates as described above.

  On the other hand, the elevator group management control device 30 according to the first embodiment is as follows so as not to cause a situation in which the number of cars stopped on the basement floor increases as in the case of FIG. 4A. Operate. That is, when a call “lower floor” is newly registered, the number of cars allocated to the already registered call “lower floor” is confirmed, and the number of cars scheduled to stop on the basement floor does not increase more than necessary. Like that.

  As a result, there will be no situation where the number of cars scheduled to stop on the basement floor will increase more than necessary. Therefore, as shown in the case of FIG. 4B, after the car scheduled to stop on the basement floor stops on the basement floor, The situation of corresponding to the call “upper floor → lobby floor” registered in is not generated. Therefore, it is possible to suppress the occurrence of a reverse car departure event and improve the operation efficiency of the elevator as compared with the conventional case.

  Next, the operation of the elevator group management control device 30 according to the first embodiment will be described with reference to FIG. FIG. 5 is a flowchart showing a series of operations of the elevator group management control device 30 according to the first embodiment of the present invention.

  In step S101, the allocation candidate car determination unit 31 determines whether or not a landing destination call newly registered in the landing destination floor registration device 10 (hereinafter referred to as a new landing destination call) has been detected.

  If the allocation candidate car determination unit 31 determines that a new landing destination call has not been detected (ie, NO), the process of step S101 is repeated. On the other hand, if the allocation candidate car determination unit 31 determines that a new landing destination call has been detected (ie, YES), the process proceeds to step S102.

  In step S102, the allocation candidate car determination unit 31 determines whether the detected new landing destination call is “upper floor → lobby floor”.

  If the allocation candidate car determination unit 31 determines that the detected new landing destination call is “upper floor → lobby floor” (ie, YES), the process proceeds to step S103. On the other hand, if the allocation candidate car determination unit 31 determines that the detected new landing destination call is not “upper floor → lobby floor” (that is, NO), the process proceeds to step S106.

  In step S103, the allocation candidate car determination unit 31 sets a constraint, determines an allocation candidate car, and proceeds to step S104. That is, the assignment candidate car determination unit 31 excludes the assigned car for the registered call “lower floor” and determines the assignment candidate car for the detected new landing destination call.

  In step S103, if the assigned car for the detected new landing destination call disappears as a result of excluding the assigned car for the registered call “lower floor”, the number of assigned car is 0 (none). decide.

  In step S104, the allocation candidate car determination unit 31 determines whether there is one or more allocation candidate cars determined in step S103.

  If the allocation candidate car determination unit 31 determines that there is one or more allocation candidate cars determined in step S103 (that is, YES), the process proceeds to step S111. On the other hand, if the allocation candidate car determination unit 31 determines that the number of allocation candidate cars determined in step S103 is zero (ie, NO), the process proceeds to step S105.

  In step S105, the allocation candidate car determination unit 31 sets constraints, re-determines the allocation candidate car, and proceeds to step S111. That is, the allocation candidate car determination unit 31 re-determines the allocation car excluded in step S103 (allocation car for the already registered call “lower floor”) as the allocation candidate car.

  In step 106, the allocation candidate car determination unit 31 determines whether or not the detected new landing destination call is a call “lower floor”.

  If the allocation candidate car determination unit 31 determines that the detected new landing destination call is the “lower floor” (that is, YES), the process proceeds to step S107. On the other hand, if the allocation candidate car determination unit 31 determines that the detected new landing destination call is not the “lower floor” (ie, NO), the process proceeds to step S111. If the allocation candidate car determination unit 31 proceeds to step S111 in this way, all the cars of the elevator cars that are group-controlled are detected without any particular restrictions. It is determined as a candidate car for the landing destination call.

  In step S <b> 107, the allocation candidate car determination unit 31 determines whether or not the number of allocation cars for the already registered call “lower floor” is less than the threshold number. The number of thresholds may be set in advance according to the total number of elevators that are group-controlled by the elevator group management control device 30. Specifically, the threshold number depends on the total number of elevators that are group-controlled by the elevator group management control device 30. For example, when the total number is 7 to 8, the threshold number is 3, When the number is 5 to 6, the threshold number is set to 2, and when the total number is 4 or less, the threshold number is set to 1 in advance.

  If the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “lower floor” is less than the threshold number (ie, YES), the process proceeds to step S109. On the other hand, if the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “lower floor” is equal to or greater than the threshold number (that is, NO), the process proceeds to step S108.

  In step S108, the allocation candidate car determination unit 31 sets a constraint and determines an allocation candidate car. That is, the allocation candidate car determination unit 31 determines the allocation car for the already registered call “lower floor” as the allocation candidate car for the detected new landing destination call.

  In step S109, the allocation candidate car determination unit 31 determines whether or not the number of the allocation cars for the already registered call “lower floor” is zero.

  If the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “lower floor” is 0 (that is, YES), the process proceeds to step S110. On the other hand, if the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “lower floor” is not zero (that is, NO), the process proceeds to step S111. If the allocation candidate car determination unit 31 proceeds to step S111 in this way, all the cars of the elevator cars that are group-controlled are detected without any particular restrictions. It is determined as a candidate car for the landing destination call.

  In step S110, the allocation candidate car determination unit 31 sets a constraint and determines an allocation candidate car. That is, the allocation candidate car determination unit 31 determines a car other than the allocation car for the already registered call “upper floor → lobby floor” as an allocation candidate car for the detected new landing destination call, and proceeds to step S111. .

  In step S111, the allocation car determination unit 32 generates a reverse departure event when allocation is made to the detected new landing destination call from the allocation candidate cars determined by the allocation candidate car determination unit 31. The car is excluded and the process proceeds to step S112. However, the car is not excluded when the number of candidate car assignments becomes 0 as a result of excluding the car in which the backward departure event occurs.

  In step S112, the assigned car determination unit 32 determines an assigned car for the detected new landing destination call from among the assignment candidate cars after the execution of step S111 (after exclusion), and ends the series of processes in the flowchart. . A method for determining an optimal allocation car from among allocation candidate cars has been described in many prior documents, and will not be described in detail. For example, the following method illustrated in step S112 of FIG. To determine the most suitable allocation car. That is, the assigned car determination unit 32 increases the waiting time increment of the passengers on the floor responding to the landing destination call of each car when the assigned car is assigned to the detected new landing destination call. The car with the smallest sum is determined as the assigned car.

  In steps S102 and S110, the call “upper floor → lobby floor” (that is, “destination destination call where the boarding floor is higher than the lobby floor and the destination floor is the lobby floor”) is targeted. However, it is also possible to target a landing destination call that “the boarding floor is the lobby floor and the destination floor is a floor below the lobby floor”.

  In step S102, whether or not the new hall destination call detected in step S101 is called “upper floor → lobby floor” is used as a criterion. However, the following configuration may be used. That is, in step S102, it may be determined whether the new landing destination call detected in step S101 is a call “upper floor → lobby floor” or a call “lobby floor → upper floor”.

  As described above, according to the first embodiment, first, when the newly registered new destination destination call is “upper floor → specific floor”, the allocation candidate car determination unit has already performed the specific process as The assigned car for the new landing destination call is determined by excluding the assigned car for the registered call “lower floor”. In addition, the assigned car determination unit is a car in which a car reverse departure event occurs when it is assigned to a new landing destination call from among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determination unit. To determine the assigned car for the new landing destination call.

  As a result, a car that stops at the specific floor after the call “upper floor → lobby floor” is newly registered after the stop at the floor below the specific floor originally is not generated. Therefore, even if the call “lobby floor → upper floor” is newly registered after that, there is no car that stops at the specific floor before stopping at the floor below the specific floor. Events can be suppressed from occurring. In addition, among the candidate cars for the newly registered call “Lobby floor → Upper floor”, it is possible to include a car scheduled to stop at a floor below the specific floor, so that the efficiency of elevator operation has been improved. Can be improved.

  Second, when the newly registered new destination call is the call “lower floor”, the allocation candidate car determination unit determines the number of assigned cars for the already registered call “lower floor” as a specific process. If the number is equal to or greater than the threshold number, the assigned car for the registered call “lower floor” is determined as the assigned candidate car for the new landing destination call. In addition, the assigned car determination unit is a car in which a car reverse departure event occurs when it is assigned to a new landing destination call from among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determination unit. To determine the assigned car for the new landing destination call.

  As a result, there will be no situation where the number of cars scheduled to stop on the floor below the specific floor will increase more than necessary, so a new registration will be made after stopping on the floor below the specific floor. There is no car corresponding to the call “upper floor → lobby floor”. Therefore, it is possible to suppress the occurrence of a reverse car departure event and improve the operation efficiency of the elevator as compared with the conventional case.

  Thirdly, when the newly registered new destination call is the call “lower floor”, the allocation candidate car determination unit determines the number of assigned cars for the already registered call “lower floor” as a specific process. When the number of cars is 0, a car other than the assigned car for the already registered call “upper floor → specific floor” is determined as an assignment candidate car for the new landing destination call.

  As a result, the car scheduled to stop on the specific floor is not assigned to the newly registered call “lower floor”. Therefore, after the stop on the specific floor, the car is moved to the floor below the specific floor. There are no cars scheduled to stop. Therefore, it is possible to suppress the occurrence of a reverse car departure event and improve the operation efficiency of the elevator as compared with the conventional case.

Embodiment 2. FIG.
In the first embodiment, when the call “upper floor → lobby floor” is newly registered, the allocation car for the already registered call “lower floor” is excluded and the allocation candidate car is determined. Explained the case. On the other hand, in the second embodiment of the present invention, if the call “upper floor → lobby floor” is newly registered, it is based on the number of cars allocated to the already registered call “upper floor → lobby floor”. A case will be described where the allocation candidate car is determined. In addition, since each component of the elevator group management control device 30 in the second embodiment is the same as that in the first embodiment, the description thereof is omitted, and the operation is different from that in the first embodiment. The explanation will be focused on.

  FIG. 6 is a flowchart showing a series of operations of the elevator group management control device 30 according to the second embodiment of the present invention.

  In step S201, the allocation candidate car determination unit 31 executes the same process as in step S101 in FIG. 5, and proceeds to step S202.

  In step S202, the allocation candidate car determination unit 31 determines whether or not the detected new landing destination call is “upper floor → lobby floor”.

  If the allocation candidate car determination unit 31 determines that the detected new landing destination call is “upper floor → lobby floor” (ie, YES), the process proceeds to step S203. On the other hand, if the allocation candidate car determination unit 31 determines that the detected new landing destination call is not “upper floor → lobby floor” (ie, NO), the process proceeds to step S205. In addition, when the allocation candidate car determination unit 31 proceeds to step S205 in this way, all the elevator cars under group management control are set as allocation candidate cars without any particular restriction. decide.

  In step S203, the assignment candidate car determination unit 31 determines whether or not the number of assigned cars for the already registered call “upper floor → lobby floor” is less than the threshold number. The number of thresholds may be set in advance according to the total number of elevators that are group-controlled by the elevator group management control device 30. That is, the threshold number depends on the total number of elevators controlled by the elevator group management control device 30. For example, when the total number is 7 to 8, the threshold number is 3 and the total number is 5 to 5. In the case of six, the threshold number is set to two, and in the case where the total number is four or less, the threshold number is set to one.

  If the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “upper floor → lobby floor” is less than the threshold number (that is, YES), the process proceeds to step S205. . In addition, when the allocation candidate car determination unit 31 proceeds to step S205 in this way, all the elevator cars under group management control are set as allocation candidate cars without any particular restriction. decide. On the other hand, if the allocation candidate car determination unit 31 determines that the number of allocation cars for the already registered call “upper floor → lobby floor” is equal to or greater than the threshold number (that is, NO), the process proceeds to step S204. .

  In step S204, the allocation candidate car determination unit 31 sets a constraint, determines an allocation candidate car, and proceeds to step S205. That is, the allocation candidate car determination unit 31 determines the allocation car for the already registered call “upper floor → lobby floor” as the allocation candidate car for the detected new landing destination call.

  Here, in the past, there was a situation where the number of cars scheduled to stop increased more than necessary on a specific floor with many passengers, and as a result, the occurrence of reverse car events could be suppressed. However, the operation efficiency of the elevator was deteriorating.

  On the other hand, in the second embodiment, since the processing contents of steps S203 and S204 are present, conventionally, the number of cars scheduled to stop on a specific floor with many passengers is not increased more than necessary. can do.

  In step S205, the assigned car determination unit 32 executes the same process as in step S111 in FIG. 5, and proceeds to step S206.

  In step S206, the assigned car determination unit 32 executes the same process as in step S112 in FIG. 5, and ends the series of processes in the flowchart.

  In steps S202 to S204, the call “upper floor → lobby floor” (that is, “destination destination call where the boarding floor is a floor above the lobby floor and the destination floor is the lobby floor”) is targeted. However, it is also possible to target a landing destination call that “the boarding floor is the lobby floor and the destination floor is a floor below the lobby floor”.

  As described above, according to the second embodiment, when a newly registered new landing destination call is called “upper floor → specific floor”, the allocation candidate car determination unit performs the already registered call as the specific process. If the number of assigned cars for “upper floor → specific floor” is equal to or greater than the threshold number, the assigned car for the registered call “upper floor → specific floor” is determined as an allocation candidate car for the new landing destination call. In addition, the assigned car determination unit is a car in which a car reverse departure event occurs when it is assigned to a new landing destination call from among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determination unit. To determine the assigned car for the new landing destination call.

  As a result, if there is a situation where the number of cars scheduled to stop increases more than necessary on a specific floor where there are many passengers, the elevator operation efficiency will deteriorate, but this situation will not occur. Therefore, it is possible to suppress the occurrence of a reverse car start event and improve the operation efficiency of the elevator as compared with the conventional case.

  In the first and second embodiments, when the number of passengers boarding from the lobby floor with the floor above the lobby floor as the destination floor is greater than or equal to the threshold number of passengers, and the total number of passengers using the elevator The specifying process by the allocation candidate car determination unit may be executed only in at least one of the cases where the number ratio is equal to or greater than the threshold ratio.

  In this case, for example, at a certain time in the past from the present or a certain time in the future predicted from the present, the number of passengers per unit time boarded from the lobby floor with the floor above the lobby floor as the destination floor is greater than or equal to the threshold number. If the configuration is made such that the specific process by the allocation candidate car determination unit is executed only in at least one of the cases where the ratio of the number of passengers to the total number of users using the elevator is equal to or greater than the threshold ratio Good.

  As a result, the assigned car determination process can be enabled only during times when there are many passengers on the lobby floor, and it is possible to suppress the reverse car departure event on the lobby floor and improve the operation efficiency of the elevator. It can be effectively performed as needed.

  Moreover, you may comprise so that the specific process by an allocation candidate car determination part may be performed only at the time of application of specific driving service patterns, such as driving service for work.

  Further, in the first and second embodiments, the case where the specific floor with many passengers is used as the lobby floor is illustrated. However, the present invention is not limited to this. It may be a connecting floor with. In addition, the lower floor is based on the lobby floor and the basement floor has few users (passengers), but the floor group on the side with few users is equivalent to the basement floor based on the floor with many passengers. Also good.

Claims (8)

An allocation candidate determination unit for determining an allocation candidate car for a landing destination call registered by the landing destination floor registration device;
An allocation car determination unit for determining an allocation car for the landing destination call from among the allocation candidate cars determined by the allocation candidate car determination unit;
A group management control unit that performs group management control of elevators by allocating the allocation car determined by the allocation car determination unit to the floor where the landing destination call has occurred;
The upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
In the case where the newly registered new destination destination call is “upper floor → specific floor”,
The allocation candidate car determination unit
As specific processing, the assigned car for the new landing destination call is determined by excluding the assigned car for the registered call “lower floor”,
The allocation car determination unit
From among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determining unit, excluding a car that causes a car reverse departure event when allocated to the new landing destination call, An elevator group management control device for determining an assigned car for the new landing destination call. An allocation candidate determination unit for determining an allocation candidate car for a landing destination call registered by the landing destination floor registration device;
An allocation car determination unit for determining an allocation car for the landing destination call from among the allocation candidate cars determined by the allocation candidate car determination unit;
A group management control unit that performs group management control of elevators by allocating the allocation car determined by the allocation car determination unit to the floor where the landing destination call has occurred;
The upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
When the newly registered new destination destination call is “downstairs”,
The allocation candidate car determination unit
As a specific process, if the number of assigned cars for the already registered call “lower floor” is equal to or greater than the threshold number, the assigned car for the already registered call “lower floor” is assigned as the candidate car for the new landing destination call. Determined as
The allocation car determination unit
From among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determining unit, excluding a car that causes a car reverse departure event when allocated to the new landing destination call, An elevator group management control device for determining an assigned car for the new landing destination call. In the elevator group management control device according to claim 2,
The allocation candidate car determination unit
As the specific process, when the number of assigned cars for the already registered call “lower floor” is 0, a car other than the assigned car for the already registered call “upper floor → specific floor” is assigned to the new landing Elevator group management control device that is determined as a candidate car for the destination call. An allocation candidate determination unit for determining an allocation candidate car for a landing destination call registered by the landing destination floor registration device;
An allocation car determination unit for determining an allocation car for the landing destination call from among the allocation candidate cars determined by the allocation candidate car determination unit;
A group management control unit that performs group management control of elevators by allocating the allocation car determined by the allocation car determination unit to the floor where the landing destination call has occurred;
The upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
In the case where the newly registered new destination destination call is “upper floor → specific floor”,
The allocation candidate car determination unit
As the specific process, if the number of assigned cars for the already registered call “upper floor → specific floor” is equal to or greater than the threshold number, the assigned car for the already registered call “upper floor → specific floor” Decide as a candidate car for the destination call,
The allocation car determination unit
From among the allocation candidate cars for the new landing destination call determined by the allocation candidate car determining unit, excluding a car that causes a car reverse departure event when allocated to the new landing destination call, An elevator group management control device for determining an assigned car for the new landing destination call. In the elevator group management control device according to any one of claims 1 to 4,
The allocation candidate car determination unit
When the upper floor is the destination floor, the number of passengers boarding from the specific floor is greater than or equal to the threshold number of persons, and at least one of the ratio of the number of passengers to the total number of users using the elevator is the threshold ratio The elevator group management control device that executes the specific process only in the case. Executed when the newly registered new destination destination call is called "upper floor → specific floor" by the elevator group management control device that determines the assigned car for the landing destination call registered by the landing destination floor registration device The elevator group management control method, wherein the upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
Determining a candidate car for the new landing destination call by excluding the assigned car for the call "lower floor" already registered;
Allocation to the new landing destination call is excluded from the determined allocation candidate cars for the new landing destination call by excluding a car that causes a car reverse departure event when assigned to the new landing destination call. A step of deciding on a car,
An elevator group management control method. Elevator group management executed when the newly registered new destination destination call is the call “lower floor” by the elevator group management control device that determines the assigned car for the landing destination call registered by the landing destination floor registration device. A control method, wherein the upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
If the number of assigned cars for the already registered call “lower floor” is equal to or greater than the threshold number, the assigned car for the already registered call “lower floor” is determined as an assignment candidate car for the new landing destination call. When,
Allocation to the new landing destination call is excluded from the determined allocation candidate cars for the new landing destination call by excluding a car that causes a car reverse departure event when assigned to the new landing destination call. A step of deciding on a car,
An elevator group management control method. Executed when the newly registered new destination destination call is called "upper floor → specific floor" by the elevator group management control device that determines the assigned car for the landing destination call registered by the landing destination floor registration device The elevator group management control method, wherein the upper floor is a floor above the specific floor, the lower floor is a floor below the specific floor,
If the number of cars assigned to the already registered call “upper floor → specific floor” is equal to or greater than the threshold number, the assigned car for the already registered call “upper floor → specific floor” is assigned to the new landing destination call. Determining a candidate car;
Allocation to the new landing destination call is excluded from the determined allocation candidate cars for the new landing destination call by excluding a car that causes a car reverse departure event when assigned to the new landing destination call. A step of deciding on a car,
An elevator group management control method.

Images