JP5770150B2 - Elevator group management system - Google Patents

Description

  Embodiments described herein relate generally to an elevator group management system including a landing destination floor registration device.

  Generally, a hall call button for registering a hall call is installed at a hall on each floor of a building. When the elevator user operates this hall call button, the car responds to the registration floor of the hall call. When the user gets into the car and operates the destination floor call button on the car operation panel, the destination floor is registered and the car moves to the destination floor.

  In recent years, apart from the above-mentioned hall call button, an elevator group management system including a hall destination floor registration device that can directly designate a destination floor at the hall has been put into practical use. Such a group management system is called a “destination floor control system (DCS)”.

  The destination floor control system attempts to improve transportation efficiency by assigning a car based on the destination floor specified at the landing. In addition, when there are a plurality of elevators (cars), it is called “unit”. In addition, the machine to which the hall call is assigned is called “assigned car”.

JP-A-3-216472 JP-A-6-166476

  In the above-described DCS, in a normal operation state, each unit can be efficiently allocated and transported according to the destination floor of the user. However, because the units are assigned in the order in which the destination floors are registered at the landing, if a large number of users register during work hours, etc., it may not be possible to distribute efficiently to each unit, and the landing may be congested. is there.

  The problem to be solved by the present invention is to provide an elevator group management system that can quickly resolve the congestion situation of a hall and return it to a normal operation state.

The elevator group management system according to the present embodiment is an elevator group management system that controls the operation of a plurality of units. In the elevator group management system, a landing destination floor registration unit that registers a destination floor of a user at a landing, and the landing destination floor registration unit Based on the allocation control means for allocating the destination floor registered by the optimal unit among the above units, the registered number of destination floors registered by the landing destination floor registration unit and the operating state of each unit, Waiting number detecting means for detecting the waiting number of users, and when the waiting number detected by the waiting number detecting means exceeds a preset number of persons, the reassignment is instructed to the assignment control means, Operation control means for controlling each unit so that it can be operated with as few stops as possible, and the assignment control means is based on a reassignment instruction from the operation control means. The assigned destination floor registration performing reallocation by interchanging between each Unit.

FIG. 1 is a block diagram showing the configuration of the group management system according to the first embodiment. FIG. 2 is a diagram for explaining the situation of the hall where the hall destination floor registration device according to the embodiment is installed. FIG. 3 is a flowchart showing the operation of the group management system in the embodiment. FIG. 4 is a diagram showing the contents of the table before reassignment of the group management system in the same embodiment. FIG. 5 is a diagram showing the contents of the table after reassignment of the group management system in the same embodiment. FIG. 6 is a diagram showing a display example before reassignment of the group management system in the same embodiment, FIG. 6 (a) is a display of Unit A, FIG. 6 (b) is a display of Unit B, FIG. c) corresponds to the indicator of Unit C. FIG. 7 is a diagram showing a display example after reassignment of the group management system in the same embodiment, FIG. 7 (a) is the display of the Unit A, FIG. 7 (b) is the display of the Unit B, FIG. c) corresponds to the indicator of Unit C. FIG. 8 is a block diagram showing the configuration of the group management system according to the second embodiment. FIG. 9 is a flowchart showing the operation of the group management system in the embodiment. FIG. 10 is a diagram showing the contents of the table before reassignment of the group management system in the same embodiment. FIG. 11 is a diagram showing the contents of the table after reassignment of the group management system in the same embodiment. FIG. 12 is a diagram showing the contents of another reassigned table of the group management system in the same embodiment. FIG. 13 is a diagram showing a display example before reassignment of the group management system in the same embodiment, FIG. 13 (a) is a display of the machine A, FIG. 13 (b) is a display of the machine B, FIG. c) corresponds to the indicator of Unit C. FIG. 14 is a diagram showing a display example after reassignment of the group management system in the same embodiment, FIG. 14 (a) is a display of Unit A, FIG. 14 (b) is a display of Unit B, FIG. c) corresponds to the indicator of Unit C.

  Hereinafter, embodiments will be described with reference to the drawings.

(First embodiment)
FIG. 1 is a block diagram showing the configuration of the group management system according to the first embodiment. In the example of FIG. 1, a configuration in which three elevators are group-managed is shown, but the configuration is not limited to this configuration. In addition, when there are a plurality of elevators, the term “unit” is used.

  The machine control devices 11a, 11b, and 11c are provided corresponding to the cars 12a, 12b, and 12c of each car, and each machine includes a hoisting machine drive control and door opening / closing control (not shown). Take control. The cars 12a, 12b, 12c move up and down in the hoistway by driving a hoisting machine (not shown). In the example of FIG. 1, the car 12a is the A machine, the car 12b is the B machine, and the car 12c is the C machine.

  Here, a landing destination floor registration device 14 is installed at a landing 13 of at least a reference floor (for example, the first floor) of each floor. The landing destination floor registration device 14 is a device for a user to register a destination floor at the landing 13, and includes an operation unit 15 and a display unit 16. The operation unit 15 is a part where the user inputs a destination floor by operating a button. Note that the input method of the destination floor is not limited to the button operation, and the destination floor recorded in advance in the ID card may be read. The display unit 16 displays information on the number assigned to the destination floor.

  In addition, display units 17a, 17b, and 17c and speakers 18a, 18b, and 18c are installed in the vicinity of the landing of each unit (near a landing door (not shown)) corresponding to each unit. These are used as devices for notifying the user waiting at the hall 13 about the relationship between the destination floor and the car.

  The machine control devices 11a, 11b, 11c, the landing destination floor registration device 14, the indicators 17a, 17b, 17c, and the speakers 18a, 18b, 18c are connected to the group management control device 20, respectively.

  The group management control device 20 is a host device that performs group management control on the operation of each car (cars 12a, 12b, 12c). In the present embodiment, the group management control device 20 includes a call management unit 21, an allocation control unit 22, a waiting number detection unit 23, an operation control unit 24, and a notification unit 25. These are processing units executed by software on the microprocessor, and information can be exchanged between the respective units.

  Here, for convenience, the call management unit 21, the allocation control unit 22, the waiting number detection unit 23, the operation control unit 24, and the notification unit 25 are all arranged in the group management control device 20, but are not necessarily the same device. It is not necessary to arrange them, and they may be arranged in separate devices.

  The call management unit 21 has a table 21a, and associates information on the destination floor sent from the landing destination floor registration device 14 as a landing call with the information on the machine (assigned car) to which the destination floor is assigned and stores it in the table 21a. To do.

  When the destination floor is registered by the landing destination floor registration device 14, the assignment control unit 22 assigns the destination floor to the optimal number of each unit and makes it respond. As an allocation method, a generally known method is used. In general, for example, a method is used in which an evaluation value is obtained based on the position, driving direction, destination floor information, etc. of each unit, and the unit having the highest evaluation value is assigned as the optimal unit.

  The waiting number detection unit 23 detects the number of waiting users based on the registered number of destination floors registered by the landing destination floor registration device 14 and the operating state of each unit.

  The operation control unit 24 instructs the allocation control unit 22 to perform reassignment when the waiting number of people in the hall 13 detected by the waiting number detection unit 23 exceeds a preset number of people, and each unit reduces the number of stops as much as possible. Control so that it can be operated.

  The notification unit 25 notifies the user who waits at the hall 13 of the relationship between the destination floor and the machine changed by the reallocation by the allocation control unit 22. Specifically, the display information is notified through the display devices 17a, 17b, and 17c installed in the hall 13, or the sound information is notified through the speakers 18a, 18b, and 18c.

  FIG. 2 is a diagram for explaining the situation of the hall 13 where the hall destination floor registration device 14 is installed.

  When the user operates the operation unit 15 of the landing destination floor registration device 14 to register the destination floor, a landing call including information on the destination floor is sent to the group management control device 20 shown in FIG. In the group management control device 20, the assignment control unit 22 assigns the destination floor to the most appropriate one of the units and makes it respond. At that time, since the information on the assigned car is displayed on the display unit 16 of the landing destination floor registration device 14, the user waits before the boarding of the corresponding car according to the display. In addition, since information on the destination floor is displayed on the display devices 17a, 17b, and 17c of each unit, it is possible to prevent mistakes in riding by checking the information on the display on the destination floor.

  For example, assume that the user has registered the second floor as the destination floor. At this time, assuming that No. A is assigned, the characters “No. A” are displayed on the display unit 16 of the landing destination floor registration device 14, and the letters “2nd floor” are displayed on the display 17 a corresponding to the No. A. Is done. According to this display, the user waits in front of the landing of Unit A. At that time, since the destination floor has already been registered, there is no need to register the destination floor in the car when Unit A arrives.

  Here, usually, each unit is operated efficiently by assigning the same destination floor to the same unit. However, in order to assign the machines in the order of registration on the destination floor, efficient distribution becomes difficult if a large number of users register during work hours. As a result, the number of users waiting for each unit increases and becomes crowded.

  Hereinafter, a method for eliminating such congestion at the hall 13 will be described.

  FIG. 3 is a flowchart showing the operation of this system. Note that the processing shown in this flowchart is executed by the group management control device 20 which is a computer reading a predetermined program.

  When the user operates the operation unit 15 of the landing destination floor registration device 14 to register the destination floor (Yes in step S101), the hall call including the information on the destination floor is the group management control device 20 shown in FIG. Sent to. In the group management control device 20, by receiving this hall call, the information on the destination floor is stored in the table 21 a of the call management unit 21, and then the allocation control unit 22 assigns the destination floor to the optimum number in each unit. And the information on the assigned number is stored in the table 21a in association with the destination floor (step S102).

  At this time, as an assignment result of the assignment control unit 22, information on the assigned car is displayed on the display unit 16 of the landing destination floor registration device 14 and corresponds to the assigned car in the indicators 17a, 17b, 17c of each car. The destination floor registered by the user is displayed on the display (step S103).

  Here, the waiting number detection unit 23 provided in the group management control device 20 is based on the number of registered destination floors stored in the table 21a and the operating state (current position, driving direction, etc.) of each unit. Is detected (step S104).

  That is, as shown in FIG. 2, for example, if ten people register destination floors by using the landing destination floor registration device 14, and the No. A, No. B, and No. C machines are in service operation at that time, the waiting number is 10 Become a person. For example, if No. A has arrived at the reference floor where the hall destination floor registration device 14 is installed, and two people can board the No. A, the number of waiting persons is eight.

  In addition, the information regarding the operation state of each number machine is obtained from the number machine control apparatuses 11a, 11b, and 11c. This information shows where each unit is operating and when it responds to the reference floor, so it knows how many users are waiting at the landing 13 before each unit responds to the reference floor it can.

  The waiting number detected by the waiting number detection unit 23 is given to the operation control unit 24. The operation control unit 24 compares the waiting number detected by the waiting number detection unit 23 (hereinafter referred to as waiting number P1) with the number of people set in advance for congestion determination (hereinafter referred to as congestion determination number P0). (Step S105).

  The crowd determination number P0 is set according to the transport capacity (maximum capacity) of each unit. For example, assuming that the transport capacity (maximum capacity) of each of Unit A, Unit B, and Unit C is 10 people, the total transport capacity is 10 × 3 = 30 people. This means that it is possible to operate normally with 3 units of Unit A, Unit B and Unit C until 30 people wait. Therefore, the congestion determination number P0 = 30 is set, and it is determined that the congestion is detected when the waiting number P1 exceeds 30.

  Note that the congestion determination number P0 can be arbitrarily changed by, for example, an operation button installed in the group management control device 20, a maintenance terminal device held by maintenance personnel, or a remote operation from the outside (such as a monitoring center). .

  If the waiting number P1 exceeds the congestion determination number P0 (Yes in step S105), the operation control unit 24 determines that the hall 13 is in a congested state and instructs the allocation control unit 22 to reassign. To do. In response to this instruction, the assignment control unit 22 performs reassignment so that each unit can be operated with as few times as possible with respect to the currently assigned destination floor (step S106).

4 and 5 show specific examples of reassignment.
4 shows the contents of the table 21a before reassignment, and FIG. 5 shows the contents of the table 21a after reassignment.

  Assume that the assignment result before reassignment, that is, when the destination floor is registered is as shown in FIG. Units are assigned in the order in which the destination floors are registered by the landing destination floor registration device 14. In this case, the same destination floor is allocated as efficiently as possible to the same unit. However, when it gets congested, it becomes impossible to distribute efficiently, and the relationship between the destination floor and the machine is disturbed, and the number of stops increases. In the example of FIG. 4, the number of stops of Unit A is 3 times, the number of stops of Unit B is 4 times, and the number of stops of Unit C is 3 times.

  Therefore, reallocation is performed so that such disturbance is eliminated and each unit can be operated with as few times as possible. In the example of FIG. 5, “5F, 5F” assigned to Unit A is replaced with “3F, 3F” assigned to Unit B, and “10F, 10F” assigned to Unit B and C “6F, 6F” assigned to Unit No. has been replaced. As a result, it can be seen that the stop floors of Units A to C are two times each, and can be operated efficiently.

  The result of the reassignment is reflected in the table 21a, and thereafter each unit responds to the reference floor, which is the installation floor of the landing destination floor registration device 14, according to the result of the reassignment. At that time, the notification unit 25 provided in the group management control device 20 notifies the user that the relationship between the destination floor and the car has been changed by reassignment (step S107).

  As a notification method, in addition to being notified by display information through the display units 17a, 17b, and 17c of each unit, notification may be made by voice information through speakers 18a, 18b, and 18c.

6 and 7 show specific examples in the case of notification by display information.
FIG. 6 is a diagram showing a display example before reassignment. FIG. 6 (a) is a display unit 17a of Unit A, FIG. 6 (b) is a display unit 17b of Unit B, and FIG. This corresponds to the display device 17c. FIG. 7 is a diagram showing a display example after reassignment. FIG. 7 (a) is a display unit 17a of Unit A, FIG. 7 (b) is a display unit 17b of Unit B, and FIG. This corresponds to the display device 17c.

  The display 17a, 17b, 17c of each unit displays the relationship between the destination floor and the unit obtained by the allocation control unit 22 of the group management control device 20. In the example of FIG. 7, “2nd floor, 3rd floor, 5th floor” is the destination floor of Unit A, “3rd floor, 5th floor, 6th floor, 10th floor” is the destination floor of Unit B, and “ "6th floor, 9th floor, 10th floor" is displayed. In this case, the 3rd floor, 5th floor, 6th floor, and 10th floor are displayed on the display units of the two units, but the user knows in advance the display unit 16 of the landing destination floor registration device 14 that he / she is on. So don't get lost.

  Here, when the relationship between the destination floor and the car is changed by reassignment, it is displayed as in the example of FIG. At this time, messages 19a, 19b, etc. such as “The assignment has been changed. Be careful if you go to the 3rd floor, 5th floor, 6th floor, 10th floor” on the indicators 17a, 17b, 17c of each unit. Display 19c and note to the user that the assignment has been changed. In addition, the display character of the floor to be changed may be lit or displayed in a different color so as to call attention. By such a display, for example, a user who is waiting for Unit B on the third floor can move before the landing of Unit A.

  On the other hand, if the waiting number P1 is equal to or less than the congestion determination number P0 in step S105 of FIG. 3, the reassignment is not performed and each unit is operated normally according to the initial assignment result (step S108).

  In this way, when the number of users waiting increases and it is determined that the situation is congested, each unit can be reassigned so that it can be operated with as few stops as possible, thereby eliminating congestion early and It can be returned to the operating state. At that time, depending on the result of the reassignment, the user is moved to another unit, so that the user can be guided so as not to be confused by giving notification by display or voice.

  In the above embodiment, reassignment is performed immediately when the waiting number P1 exceeds the congestion determination number P0. However, reassignment may be performed when this state continues for a predetermined time. This is because in step S105 in FIG. 3, the operation control unit 24 compares the waiting number P1 with the congestion determination number P0, and the state of waiting number P1> congestion determination number P0 has continued for a predetermined time (for example, 5 minutes). This can be realized by determining whether or not. In this way, it is possible to avoid confusing the user by inadvertently performing reallocation due to temporary congestion.

(Second Embodiment)
Next, a second embodiment will be described.

  In the first embodiment, the reallocation is performed on the condition that the waiting number P1 exceeds the congestion determination number P0. However, in the second embodiment, the destination floor having a predetermined number of registrations or more. Reassignment is performed when (high demand floor) exists.

  FIG. 8 is a block diagram showing the configuration of the group management system according to the second embodiment. In addition, the same code | symbol is attached | subjected to the same part as FIG. 1 in the said 1st Embodiment, and the description shall be abbreviate | omitted.

  In the second embodiment, the group management control device 20 is provided with a high demand floor detection unit 26 in addition to the call management unit 21, the assignment control unit 22, the waiting number detection unit 23, the operation control unit 24, and the notification unit 25. It has been. The high demand floor detection unit 26 refers to the table 21 a of the call management unit 21, detects a destination floor having a predetermined number or more as a high demand floor, and transmits it to the operation control unit 24. In the operation control unit 24, when the waiting number P1 detected by the waiting number detection unit 23 exceeds the congestion determination number P0, and the high demand floor is detected by the high demand floor detection unit 26, the allocation control unit 22 Reassignment is instructed.

The operation of the second embodiment will be described below.
FIG. 9 is a flowchart showing the operation of the second embodiment. Note that the processing shown in this flowchart is executed by the group management control device 20 which is a computer reading a predetermined program.

  In FIG. 9, the processing from step S201 to S205 is the same as that from step S201 to S205 in FIG. That is, when the destination floor is registered by the landing destination floor registration device 14, an optimal number is assigned by the assignment control unit 22 of the group management control device 20, and the result is displayed on the display unit 16 of the landing destination floor registration device 14 and each of the display units 16. It is displayed on the indicators 17a, 17b and 17c of the number machine (steps S201 to S203). Further, the waiting number detection unit 23 detects the current waiting number P1 (step S204) and compares it with the congestion determination number P0 (step S205).

  Here, when the waiting number P1 exceeds the congestion determination number P0 (Yes in step S205), the operation control unit 24 determines whether or not the high demand floor is detected by the high demand floor detection unit 26. (Step S206).

  The high demand floor is a destination floor having a registration number equal to or greater than a predetermined number T. For example, when there are an event or a meeting and many users go to the same floor, the number of registrations on that floor increases, so that it is detected as a high demand floor.

  The predetermined number T for detecting this high demand floor is set according to the transport capacity (maximum capacity) of each unit, for example, the total transport capacity / number of units. In other words, if the transport capacity (maximum capacity) of each of the A-unit, the B-unit, and the C-unit is 10 people, 10 × 3 = 30 people is the total transport capability. Therefore, T = 30/3 = 10, and a floor having a registration number of 10 or more is detected as a high demand floor. When there are two or more destination floors having a registration number equal to or greater than the predetermined number T, the highest destination floor among them is set as the high demand floor.

  Note that the predetermined number T can be arbitrarily changed by, for example, an operation button installed in the group management control device 20, a maintenance terminal device held by maintenance personnel, or a remote operation from the outside (such as a monitoring center).

  When a higher demand floor is detected in the state of waiting number P1> congestion determination number P0 (Yes in step S205), the operation control unit 24 instructs the allocation control unit 22 to reallocate. In response to this instruction, the assignment control unit 22 executes reassignment, and at that time, creates a dedicated machine to which at least only the high demand floor is assigned (step S207).

10 and 11 show specific examples of reallocation.
FIG. 10 shows the contents of the table 21a before reassignment, and FIG. 11 shows the contents of the table 21a after reassignment.

  Assume that the assignment result before reassignment, that is, when the destination floor is registered is as shown in FIG. In this example, the number of registrations on the 10th floor is a predetermined number T or more. Therefore, when waiting number P1> congestion determination number P0, the 10th floor is detected as a high demand floor, and reallocation is performed as shown in FIG. In this example, from the beginning, Unit C, which had a high allocation of the 10th floor, which was a high demand floor, was determined as a dedicated unit, and “10F, 10F” that was allocated to Unit B and “9F, 9F "is replaced. As a result, Unit C is operated as a dedicated unit for the 10th floor.

  In the example of FIG. 11, the assignment to other destination floors is not changed. However, similarly to the first embodiment, each unit can be reassigned so that the number of stops can be reduced as much as possible. good. That is, for example, as shown in FIG. 12, if “5F, 5F” assigned to Unit A and “3F, 3F” assigned to Unit B are interchanged, the stop floors of Unit A and Unit B are each 2 It is possible to operate efficiently once each time.

  However, if the reassignment is performed focusing only on the high demand floor, there is an advantage that the number of users who move the standby place can be reduced because the number of changes is small. In the example of FIG. 11, it is only necessary to replace the user who was waiting in front of the landing of Unit B to go to 10F and the user who was waiting in front of the landing of Unit C to go to the 9th floor.

  The result of the reassignment is reflected in the table 21a, and thereafter each unit responds to the reference floor, which is the installation floor of the landing destination floor registration device 14, according to the result of the reassignment. At that time, the notification unit 25 provided in the group management control device 20 notifies the user that the relationship between the destination floor and the car has been changed by reassignment (step S208).

  As a notification method, in addition to being notified by display information through the display units 17a, 17b, and 17c of each unit, notification may be made by voice information through speakers 18a, 18b, and 18c.

FIG. 13 and FIG. 14 show specific examples in the case of notification by display information.
FIG. 13 is a diagram showing a display example before reassignment, in which FIG. 13 (a) shows the display 17a of Unit A, FIG. 13 (b) shows the display 17b of Unit B, and FIG. 13 (c) shows the display of Unit C. This corresponds to the display device 17c. FIG. 14 is a diagram showing a display example after the reassignment. FIG. 14 (a) shows the display 17a of the A machine, FIG. 14 (b) shows the display 17b of the B machine, and FIG. 14 (c) shows the display of the C machine. This corresponds to the display device 17c.

  The display 17a, 17b, 17c of each unit displays the relationship between the destination floor and the unit obtained by the allocation control unit 22 of the group management control device 20. In the example of FIG. 13, “second floor, third floor, fifth floor” is the destination floor of Unit A, “third floor, fifth floor, sixth floor, tenth floor” is the destination floor of Unit B, and “ 9th floor, 10th floor "is displayed.

  Here, when the relationship between the destination floor and the car is changed by reassignment, it is displayed as in the example of FIG. In this example, the case where the C machine is reassigned as a dedicated machine on the 10th floor is shown. At this time, messages 19a, 19b, and 19c such as “Changed assignment. Be careful if you go to the 9th and 10th floors” are displayed on the display units 17a, 17b, and 17c of each unit. Note to the user that the assignment has changed. In addition, the display character of the floor to be changed may be lit or displayed in a different color so as to call attention. By such a display, for example, a user who is waiting for Unit B on the 10th floor can move before the landing of Unit C.

  On the other hand, if the waiting number P1 is equal to or less than the congestion determination number P0 in step S205 of FIG. 9, or if a high demand floor is not detected in step S206, the reallocation is not performed, Each unit is operated normally according to the allocation result (step S209).

  In this way, in addition to exceeding the predetermined number of users waiting for the event, it is possible to reallocate the presence of a destination floor (high demand floor) having a predetermined number of registrations or more. For example, reassignment can be performed only when a large number of users go to the same floor, and congestion at that time can be eliminated. In particular, by creating a dedicated machine that responds only to the high demand floor at the time of reallocation, it is possible to efficiently carry a large number of users heading to the high demand floor and eliminate congestion as soon as possible.

  In the above embodiment, the case of creating one dedicated number machine has been described. However, the number of dedicated number machines may be increased step by step in accordance with the number of registered high demand floors. This can be realized by adding a process in which the allocation control unit 22 increases the number of dedicated units step by step in accordance with the number of registered high demand floors in step S207 of FIG. If the number of dedicated machines is increased in this way, it is possible to more efficiently carry a large number of users heading for high demand floors and to eliminate congestion at an early stage.

  Alternatively, the high demand floor may be detected when the waiting number P1 exceeds the congestion determination number P0 for a predetermined time. This is because, in step S205 of FIG. 9, the operation control unit 24 compares the waiting number P1 with the congestion determination number P0, and the state of waiting number P1> congestion determination number P0 has continued for a predetermined time (for example, 5 minutes). This can be realized by determining whether or not. In this way, it is possible to avoid confusing the user by inadvertently performing reallocation due to temporary congestion.

  According to at least one embodiment described above, it is possible to provide an elevator group management system capable of resolving congestion at a landing early and returning to a normal operation state.

  In addition, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  11a, 11b, 11c ... Unit control device, 12a, 12b, 12c ... Ride car, 13 ... landing, 14 ... landing destination floor registration device, 15 ... operation part, 16 ... display part, 17a, 17b, 17c ... indicator, 18a, 18b, 18c ... speaker, 19a, 19b, 19c ... message, 21 ... call management unit, 21a ... table, 22 ... allocation control unit, 23 ... waiting number detection unit, 24 ... operation control unit, 25 ... notification unit, 26: High demand floor detection unit.

Claims (7)

In the elevator group management system that controls the operation of multiple units,
A landing destination floor registration means for registering a user's destination floor at the landing;
Allocation control means for allocating the destination floor registered by the landing destination floor registration means to the optimum unit among the above units,
Waiting number detection means for detecting the waiting number of users based on the registered number of destination floors registered by the landing destination floor registration means and the operating state of each unit,
When the waiting number detected by the waiting number detection means exceeds a preset number of persons, the assignment control means is instructed to reassign, and control is performed so that each unit can be operated with as few stops as possible. Operation control means to perform,
With
The elevator group management system according to claim 1, wherein the allocation control means executes the reassignment by replacing the assigned destination floor registration between the units based on the reassignment instruction from the operation control means. The operation control means is
2. The reassignment is instructed to the assignment control means when the waiting number detected by the waiting number detecting means exceeds a preset number of persons for a predetermined time. Elevator group management system. It further comprises a high demand floor detecting means for detecting a destination floor having a predetermined number or more as a high demand floor,
The operation control means is
When the waiting number detected by the waiting number detection means exceeds a preset number of persons and the high demand floor is detected by the high demand floor detection means, reassignment to the assignment control means is performed. The elevator group management system according to claim 1, wherein an instruction is given. The operation control means is
The allocation control means when the waiting number detected by the waiting number detecting means exceeds a preset number of people for a predetermined time and the high demand floor is detected by the high demand floor detecting means. The elevator group management system according to claim 3, wherein reassignment is instructed to. The allocation control means is
The elevator group management system according to claim 3, wherein a dedicated unit assigned with only the high demand floor is created among the units by reassignment. The allocation control means is
6. The elevator group management system according to claim 5, wherein the number of dedicated machines is increased in stages according to the number of registrations on the high demand floor.   The elevator according to any one of claims 1 to 5, further comprising notification means for notifying a user waiting at the landing about the relationship between the destination floor and the unit after reassignment by the assignment control means. Swarm management system.

Images