JP2013184816A - Group management control system of elevator - Google Patents

Abstract

PROBLEM TO BE SOLVED: To effectively add a system to enable a destination call to a group management control system of an existing elevator having only an up/down call function.SOLUTION: A destination call expansion system for an existing system having an up/down call function and a car call function includes a registration device, first and second storage units, an allocation unit, and first and second converters. The registration device registers a destination call that dedicates a destination floor. The first storage unit stores the destination call. The allocation unit allocates a car to a new destination call. The second storage unit stores operation schedule information including a departure floor, the car, and the destination floor for each destination call. The first converter converts the operation schedule information of the new destination call to the up/down call and the car call, to be applied to the existing system. The second converter converts the information on the up/down call and the car call existing on the existing system to the operation schedule information of the destination call except the one converted from the destination call, to be applied to the second memory unit.

Description

  Embodiments described herein relate generally to an elevator group management control system.

  As a way for users to call elevators, the “up and down direction call (hereinafter referred to as up and down direction call)” that pushes the button of the up and down direction call registration device at the landing on the departure floor has been mainly adopted. As a method of designating “car call”, “car call” has been mainly adopted in which a car call button corresponding to each destination floor is pressed in the car.

  On the other hand, attention has been paid to “destination call” in which a user calls a car and designates a destination floor at the same time by registering the destination floor with a landing destination floor registration device on the departure floor.

  Conventionally, when a landing destination floor registration device is installed on some floors in relation to an existing elevator group management control system with only up / down calls, the up / down calls and destination calls are processed by a single allocation processing unit. There was a need to do. For this reason, it was necessary to remove the existing system and install a system including a new single allocation processing unit capable of processing the vertical call and the destination call.

  For example, the old and new group management control system can be operated at the same time by, for example, an old method of controlling a car before renewal for the purpose of executing it in the middle of replacing the existing group management control system with a new group management control system. A system has been proposed in which a group management control system and a new group management control system for controlling a car after renewal are operated in a coordinated manner.

  In the first technique, a call registered in one of the old and new group management control systems is registered in both group management control systems, and the both group management control systems allocate cars respectively. When two cars respond to a single call, it is useless, and when the first car responds, the call registration is deleted from the group management control system on the side that has not responded.

  In the second technique, the call of the old group management control system is transferred to the new group management control system, and the new group management control system determines whether to assign to either the new group management side or the old group management side.

  However, the new and old group management control systems each control a separate car. Therefore, the existing group management control system that controls all cars has the purpose of adding a mechanism for handling new types of calls. ,I can not use it. In addition, the first technique is inefficient because two cars are temporarily selected every time one call is registered, and there is a possibility that one car does not need to be operated. In the second technique, the allocation process is first performed on the new group management side, and if the allocation on the old group management is considered appropriate, the allocation process needs to be performed on the old group management side. Time for two times is required, and processing takes a lot of time.

Japanese Patent No. 3170539 Japanese Patent No. 3772051

  There was no effective way to add a system so that a destination call can be made to an existing elevator group management control system that can only make a vertical call.

  This embodiment provides an elevator group management control system in which a system can be effectively added to an existing elevator group management control system capable of only calling in the vertical direction so that a destination call can also be made. The purpose is to do.

  According to the embodiment, in order to manage the operation of a plurality of cars, information on the up-and-down call generated at each departure floor assigned to each car, and the car call for each destination floor generated within each car An extension to add destination calls to the existing elevator group management control system for up / down direction call and car call with up / down direction operation schedule storage unit that stores up / down direction operation schedule information including information about The elevator group management control system includes a landing destination floor registration device, a destination call registration storage unit, a destination call assignment processing unit, a destination call operation schedule storage unit, a first conversion unit, and a second conversion unit. A part. The landing destination floor registration device is provided on at least one departure floor, and registers a destination call specifying the destination floor. The destination call registration storage unit stores registration of the destination call by the landing destination floor registration device. The destination call assignment processing unit assigns an assigned car to the new registration of the destination call. The destination call operation schedule storage unit stores destination call operation schedule information including information on the departure floor, the assigned car, and the destination floor for each of the destination calls. The first conversion unit converts the destination call operation schedule information for the new registration of the destination call into the information about the up / down direction call and the information about the car call, and the converted information about the up / down direction call and the car call. Is given to the up-down direction operation schedule storage unit. The second conversion unit is the destination call operation schedule except for the information about the up / down direction call and the information about the car call stored in the up / down direction operation schedule storage unit, except for the information converted from the destination call. The information is converted into information, and the converted destination call operation schedule information is given to the destination call operation schedule storage unit.

FIG. 3 is an exemplary block diagram of an existing group management control system. 1 is an exemplary block diagram of a group management control system according to an embodiment. 6 is an exemplary flowchart of assignment processing when a destination call occurs. The figure which shows an example of destination call registration data. The figure which shows an example of destination call operation schedule data. The figure which shows an example of an up-down direction operation schedule data. The figure which shows an example of an up-down direction call registration data. The figure which shows an example of the operation condition of a cage | basket | car. The figure which shows an example of pseudo destination call operation schedule data. The figure which shows an example of capacity management data. The figure which shows the example of an output of the future prediction when not considering temporary allocation. The figure which shows the example of an output of the future prediction at the time of considering temporary allocation. 7 is an exemplary flowchart of a process for assigning a destination call to a vertical call system.

  Hereinafter, an elevator group management control system according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that, in the following embodiments, the same numbered portions are assumed to perform the same operation, and repeated description is omitted.

  In this embodiment, an extension system for adding a destination call, which will be described later, to an existing elevator group management control system capable of registering and assigning only “up and down direction calls” and “car calls” A case where registration and assignment processing of “destination call” is made possible by adding “” will be described.

  In the existing group management control system, the operation management of all the cars and the allocation process in the vertical direction are continued, and the new system performs the allocation process of the destination call. Therefore, it is possible to construct a group management control system that can be assigned by a destination call while leaving an existing system. Since the allocation process is performed in each system according to the type of call, it is not necessary to allocate two units to one call, so that useless movement of the car can be suppressed. In addition, since it is not necessary to repeat the assignment process twice, the assigned car can be obtained quickly.

  In addition, in this embodiment, not only when adding an extension system for adding a destination call later to the elevator group management control system for the up-down direction call and car call, but also newly When manufacturing and shipping an elevator group management control system including an elevator group management control system for up and down calls and a car call and an expansion elevator group management control system for adding destination calls It is possible as well. In this case, taking advantage of the design of the elevator group management control system for up and down calls and car calls, the elevator group management control system that enables destination calls in addition to the up and down calls and car calls is easy. Can be realized.

  First, an existing elevator group management control system before expansion will be described.

  In FIG. 1, the structural example of the group management control system of the existing elevator in this embodiment is shown.

As shown in FIG. 1, the existing elevator group management control system 100 according to the present embodiment includes an up / down direction call system 1, a single car control unit _{21 -X} , a car 31 _-X , and a “up / down direction call”. The vertical direction call registration devices ₄₁ to _Y are provided. In addition, in each of the cars 31 to _X , car call buttons ₃₁₁ to _X including buttons corresponding to, for example, each destination floor for “car call” are installed. Here, X is the number of cars, and Y is the total number of floors where the up / down direction call registration device is installed. As a specific example, for example, in an office building with 10 floors, when a vertical direction call registration device is installed on each floor and there are 6 cars, X = 6, Y = 10 (that is, 6 single car control units) 6 cars, 6 sets of car call buttons, and 10 up / down direction call registration devices). Needless to say, this embodiment is not limited to this.

In addition, the up-and-down direction call registration devices _{41 to Y} provided on the lowest floor include only an up button, and the up-and-down direction call registration devices _{41 to Y} provided on the top floor include only a down button, and the others The up / down direction call registration devices _{41 to Y} provided on the floor include an up direction button and a down direction button.

  The up / down direction call system 1 includes an up / down direction call registration storage unit 11, up / down direction allocation processing unit 12, up / down direction operation schedule storage unit 13, up / down direction future prediction unit 14, and car operation control monitoring unit 15.

In response to the user pressing the up or down button on the up / down direction call registration device 4 _j on a certain floor (departure floor), the up / down direction call system 1 responds to the up / down direction call (up call). (Call in the downward direction) is recorded, an assigned car is selected for the call registration, the selected assigned car is stored as an operation schedule, and the operation is controlled while monitoring each car. The “assigned car” means the “car” assigned to get on the boarding user.

The up-and-down direction call registration devices _{41 to Y} are installed at a landing on the floor that enables up-and-down direction calls, and are for operating according to the direction in which the user wants to use the elevator. For example, in a 10-story office building, when two units are installed on each floor, twenty vertical call registration devices _{41 to 20} are installed.

  The up / down direction call registration storage unit 11 stores the registered up / down direction call. When a signal indicating that a response to the call has been made is received from the car operation control monitoring unit 15, the call storage is deleted.

  The up / down direction allocation processing unit 12 selects an assigned car for the up / down direction call registered in the up / down direction call registration storage unit 11. When selecting an assigned car for a newly registered call, it receives from the up / down direction operation schedule storage unit 13 the up / down direction allocation information set for each car and the car call information. Information on the position, direction, and door open state of each car is received from the operation control monitoring unit 15, and the information is given to the vertical future prediction unit 14 to predict the future operation of each car. Prediction is performed for each car in a state before a new call is assigned and a state after the assignment. From the predicted result, the expected time of answering each call is known, so the assigned car is determined from the magnitude of those times. For example, the difference between the total value of “predicted unanswered time” in the state before assigning a new call and the total value of “predicted unanswered time” in the state after assigning a new call is minimized. You may choose a basket like this.

  Here, the predicted unanswered time value indicates, for example, a predicted value of time from the registration time of each call to “expected time to respond to each call”.

  The up-and-down future prediction unit 14 uses the up-and-down allocation information set for each car, the car call information, the position and direction of each car, and the information on the door open state, and the future operation of the car. Is predicted in time series. As a result of the prediction, it is possible to obtain a predicted value of the time until response to each allocation.

  The up / down direction operation storage unit 13 stores the assigned car determined by the up / down direction assignment processing unit 12 as a part of the operation schedule.

The car operation control monitoring unit 15 receives the change of the operation schedule from the vertical operation storage unit 13 and notifies the target single car control unit 2 _i (i is a corresponding one of 1 to X).

Single car control unit _{2 1 to X,} respectively, in accordance with instructions from the car operation control monitoring unit 15, to navigate a corresponding cage _{3 1 to X.}

Incidentally, the car call button 31 _i in the car 3 _i is operated by the user, via a single car control unit 2 _i and the car operation control monitoring unit 15, the car call is stored in the vertical direction service schedule storage unit 13 The In addition, the car operation control monitoring unit 15 controls the operation of the single car control units ₂₁ to _{X in} accordance with the car call stored in the up-and-down direction operation schedule storage unit 13.

  The present embodiment is not limited to the existing elevator group management control system capable of performing registration and assignment processing only for the above-described “up and down direction call” and “car call”.

  Hereinafter, according to the present embodiment, an extension system that enables registration and assignment processing of “destination call” is added to the existing elevator group management control system that operates according to “up and down direction call” and “car call”. The extended elevator group management control system will be described.

  Here, a case where the system shown in FIG. 1 is targeted as an example of an existing elevator group management control system will be described as an example, but the present embodiment is not limited to this.

  FIG. 2 shows an example of the configuration of an expanded group management control system for an elevator according to this embodiment.

  As shown in FIG. 2, an expanded elevator group management control system 101 is obtained by adding an expansion system 102 to an existing elevator group management control system 100.

As shown in FIG. 2, the expansion system 102 includes a destination call system 5, landing destination floor registration devices _{61 to Z} , and an allocation information conversion unit 7.

  The destination call system 5 includes a destination call registration storage unit 51, a destination call assignment processing unit 52, a destination call operation schedule storage unit 53, a capacity management storage unit 54, a destination call future prediction unit 55, and a car operation monitoring unit 56.

  The allocation information conversion unit 7 includes an operation schedule conversion output unit 71 (first conversion unit) and an operation schedule conversion extraction unit 72 (second conversion unit).

  Note that the expanded elevator group management control system 101 in FIG. 2 includes components included in the existing elevator group management control system 100 in FIG. 1. These individual elements are the same as those in FIG. 1, and a repeated description is omitted.

However, here, an example will be described in which the up / down direction call registration device _4j is not installed on the floor where the landing destination floor registration device _6k is installed. As a specific example, in a 10-story office building, landing destination floor registration devices 6 ₁ and 6 ₂ are installed on the first floor and the fourth floor, respectively, and up and down direction call registration devices are respectively installed on the second floor, the third floor, and the fifth to tenth floors 4 ₁ to 4 ₈ are installed.

The present embodiment, the floor of the car stop destination floor registration device 6 _k is installed, is also feasible if the vertical call registration device 4 _j is installed together.

  Hereinafter, components of the expansion system 102 to be newly added will be described.

The landing destination floor registration devices _{61 to Z} are devices that are installed at landings on some floors and are used by a user to input a destination floor as a “destination call”. _Any input method may be _used in the landing destination floor registration devices _{61 -Z} . For example, a numeric keypad and an enter key are displayed on the touch panel using software keys, and the user can enter the destination floor using the numeric keypad and confirm with the enter key. Alternatively, each destination floor can be displayed on the touch panel. It is also possible to display a selection button corresponding to, and the user may press the selection button corresponding to the desired destination floor. Further, for example, in an office building, the user may enter his / her ID card close to the landing destination floor registration devices ₆₁ to _Z , and then input the destination floor after inputting the ID number. Various other variations are possible.

  Since the departure floor can be specified on the system side, it is not necessary to have a function for the user to input.

  When each user inputs a destination floor, a destination call is registered and notified to the destination call registration storage unit 51.

In addition, in the destination call, in addition to the “destination floor”, the “departure floor” is specified from the floor where the input destination destination floor registration device 6 _k is installed (k is 1 to Y) Corresponding one). For example, it may be notified of the "departure floor" from the hall destination floor registration device 6 _k to the destination call system 5 side, or, for example, the landing hall destination floor registration from the destination floor registration device 6 _k to the destination call system 5 side The device identification information (hereinafter referred to as HDC-ID) is notified, and the destination call system 5 side may identify the corresponding “departure floor” from the HDC-ID, or other methods may be used. It may be used.

  Further, whether the call direction is upward or downward is specified from the vertical relationship between the “destination floor” and the “departure floor”.

  The destination call system 5 is a group management control system for performing assignment processing for a destination call and operating a car according to the result of the assignment. However, the destination call system 5 does not operate alone, but rather by using the allocation information conversion unit 7 together with the existing group management control system 100 shown in FIG. Works as.

  Note that the existing “up / down direction call” or “cage call” does not correspond to individual users, but is a set of users waiting on the same floor and in the same direction, or in a single car. This corresponds to a set of users whose destination floor is the same floor. On the other hand, here, a case will be described as an example in which each “destination call” is processed as occurring for each user.

The destination call registration storage device 51 stores the destination call registered using the landing destination floor registration devices ₆₁ to _Z. Further, the destination call assignment processing unit 52 is notified of a new destination call, and the assignment process is started. When the assignment process is completed, the destination call registration storage device 51 receives information on “assigned car” and “lap to be boarded” from the destination call assignment processing unit 52. Furthermore, when the current position information, the “direction”, and the “lap” information of the car is received from the car operation monitoring unit 56, and it is determined that a response to the assignment is possible before the car goes around once in the future. the allocated car, and notifies the target landing to a destination floor registration device 6 _k. Then, the destination call memory is erased.

  Here, the circumference is a value that is incremented by 1 every time the car changes from the first direction (for example, the downward direction) to the second direction (for example, the upward direction). Eyes. Note that the first direction may be the upward direction and the second direction may be the downward direction. In addition, the lap to be boarded indicates the number of laps in which the car should be boarded. That is, the time when the “boarding” should coincide with the “lap” of the current car is the time (lap) when the boarding is to be performed.

The landing destination floor registration devices _{61 to Z display} “allocated cars” (or “allocated cars” and “laps to be boarded”) corresponding to the registered calls.

For example, the landing destination floor registration devices _{61 to Z} may display only the _assigned car only when it becomes possible to board in one more lap. In this case, it is not necessary to display “the lap to be boarded”. Further, even after the car to be assigned is decided, before the car can be boarded in one more lap, for example, “Please wait for a while” or the like may be displayed to prompt the user to wait.

Alternatively, the landing destination floor registration devices _{61 to Z display} , for example, “allocated cars” and “laps to be boarded” immediately after the call registration, regardless of whether or not it is possible to board in one more lap. May be.

  The destination call assignment processing unit 52 performs a process of determining an “assigned car” and a “lap to be boarded” for a newly registered destination call. The destination call assignment processing unit 52 receives an operation schedule based on the destination call from the operation schedule storage unit 53, and receives "capacity management information" that means how many people are scheduled to board when each car departs from each floor. The information is received from the capacity management storage unit 54, and the “position”, “direction”, and “information on which lap is currently running” of each car are acquired from the car operation monitoring unit 56. Further, the destination call assignment processing unit 52 performs the assignment processing in consideration of the operation schedule recorded in the vertical call system 1 from the operation schedule conversion extraction unit 72 (or via the operation schedule storage unit 53). ), The operation schedule of each car as the up-down direction call system 1 is converted into the destination call format and received. The received information is sent to the destination call future prediction unit 55, except for the information obtained from the capacity management storage unit 54, and used for prediction of future car operation.

  The destination call assignment processing unit 52 uses the information obtained from the capacity management storage unit 54 to obtain “laps” for each car that can be assigned a new destination call. It is a condition that even if a user who has registered a new call is boarded, the capacity will not be exceeded in the section from the “departure floor” to the “destination floor”. In addition, you may manage a load instead of managing capacity. For example, a predetermined value may be used as the load per person. Details of the capacity over determination will be described later.

  From the result of the operation prediction, the predicted value of the waiting time of each call and the predicted value of the boarding time in each car are obtained for both cases where a new destination call is not assigned and when it is assigned. Then, a car to be assigned is determined from those predicted values.

  Here, the predicted value of the waiting time indicates, for example, a predicted value of time from registration of the destination call until the assigned car opens on the departure floor. The predicted value of the boarding time indicates, for example, a predicted value of time from the response of the assigned car until the assigned car is subsequently opened on the destination floor.

  Information on the “assigned car” and the “boarding schedule” is notified to the destination call registration storage unit 51 and the destination call operation schedule storage unit 53. In addition, the capacity management storage unit 54 increases the number of reserved persons by the amount corresponding to the contents of allocation as a new reservation.

  The assigned operation information conversion unit 7 is for converting and communicating call information between the destination call system 5 and the vertical call system 1.

  The operation schedule conversion output unit 71 divides the assigned destination calls stored in the destination call operation schedule storage unit 53 into an up / down direction call and a car call, and notifies the up / down direction call system 1, thereby calling up / down direction calls. Allows system 1 to operate the car according to the destination call registration. Calls that are determined to be able to be answered within one lap from the “position”, “direction”, and “current lap” of the car obtained from the car operation monitoring unit 56 are converted into an allocation in the vertical direction. Write to the direction operation schedule storage unit 13. When the “location”, “direction”, and “current lap” of the assigned car obtained from the car operation monitoring unit 56 match the “departure floor”, “direction”, and “lap” of the assigned destination call, It is determined that the assigned destination call has been responded, and the car call data of the assigned car is generated on the floor corresponding to the destination floor of the destination call and notified to the up / down direction operation schedule storage unit 13.

The car operation control monitoring unit 15 converts from the destination call to the single car control units ₂₁ to _{X in addition} to the _{allocation and the} car call for the existing vertical direction call notified to the vertical direction operation schedule storage unit 13. Since the elevator group management control system 101 directs the operation according to the allocation to the up and down calls and the car call, the expanded elevator group management control system 101 operates the car according to the operation plan of the destination call operation schedule storage unit 53. be able to. Further, when the up / down direction assignment processing unit 12 assigns up / down direction calls, the “car” to be assigned can be selected reflecting the operation schedule in the destination call operation schedule storage unit 53.

  The operation schedule conversion extraction unit 72 is for reflecting the allocation and car call information recorded in the up-and-down call system 1 in the future prediction and the evaluation of the allocated car when performing the destination call allocation process. . The operation schedule conversion extraction unit 72 converts the operation schedule of each car as the up-and-down direction call system 1 into a destination call format, and gives the converted destination call operation schedule information to the operation schedule storage unit 53. Note that the converted destination call operation schedule information may be given to the destination call assignment processing unit 52. Since the operation of the car is performed according to the schedules of both the up-and-down direction operation schedule storage unit 13 and the destination call operation schedule storage unit 53, it is possible to predict future movement of the car more accurately by using both information. Can do.

Next, a flow of processing from when a destination call is registered by a user in the landing destination floor registration devices _{61 to Z} until allocation is performed and an operation instruction is sent to the car will be described.

FIG. 3 shows a flow of allocation processing that is started when the user operates the landing destination floor registration devices ₆₁ to _Z and registers a destination call.

  The process of FIG. 3 may be activated periodically, for example, to detect registration of a new destination call. For example, it may be activated every tenth of a second.

In step S1, if there is a new destination floor operation, the landing destination floor registration devices _61-Z proceed to step S2. If there is no operation, the process is once ended, and the process starts again from step S1 at the next activation.

In step S2, the destination call operation schedule storage unit 53 stores the destination call registration. Further, the registration storage unit 51 destination call, the destination call not yet guided allocation, in association with the landing identification information of the destination floor registration device 6 _k.

Destination call registration storage unit 51 of FIG. 4 is for recording the relationship between the hall registered as call ID HDC-ID of the destination floor registration device, until guides the allocated car to the car stop destination floor registration device 6 _k Retain memory only during

FIG. 4 shows an example of the data structure of the destination call registration data stored in the destination call registration storage unit 51. In the example of FIG. 4, the destination call registration data includes “HDC-ID” for identifying the landing destination floor registration device 6 _k and “call ID” for identifying the destination call.

Incidentally, in this case, the landing identification information of the destination floor registration device 6 _k may be of any type. For example, the HDC-ID = 1 of the car stop destination floor registration device 6 _k installed in floor lowest, since, in order to become a floor above, may be assigned a serial number from 2 in order. Of course, the present embodiment is not limited to this.

  In FIG. 5, the example of the data structure of the destination call operation schedule data memorize | stored in the destination call operation schedule memory | storage part 53 is shown. In the example of FIG. 5, the destination call operation schedule data includes “call ID” for identifying the destination call, “departure floor” indicating the floor where the destination call is input, and “destination floor” indicating the destination floor input by the destination call. , “Assigned car” indicating the car assigned to the destination call, “assigned lap” indicating the lap assigned to the destination call, “occurrence time” indicating the time when the destination call was input, destination call "Boarding time" indicating the time when the boarding was performed is included.

  Here, as described above, one “call ID” corresponds to only one user.

  In the example of FIG. 5, when a new destination call is registered, a line is added. A new call ID is generated and entered in the “call ID” field of the added row. The “departure floor” is the floor where the call registration is performed, and the “destination floor” is the floor input by the destination call. The “occurrence time” is the time when the call registration operation is performed. “Allocation car” and “Allocation cycle” are fields for storing the result of the allocation process, and there is no data when the allocation process is not completed. “Boarding time” records, for example, the time when the assigned car responds to the call and starts to open (on the departure floor and in the direction of the call and on the assigned lap).

  4 and 5 show a case where a destination call with call ID = 4 is newly generated and registered at the current time “8: 0: 10”.

  In the following, regarding the time notation, “hh hour mm minute ss second” is described as “hh: mm: ss”. According to this notation, for example, “8:00:10” means “8 hours 0 minutes 10 seconds”.

  In step S3, the first car is set as a car to be processed as an allocation candidate. For example, when there are six cars such as A machine, B machine, etc., first, the first A machine is a processing target.

Here, all the cars 31 to _X are targets to be assigned destination calls, but only a part of the cars 31 to _X may be targets to be assigned destination calls.

  In step S4, the vertical allocation already assigned in the vertical call system 1 for the car to be processed is converted into a destination call format.

  The allocation in the vertical direction is recorded in the vertical operation schedule storage unit 13 of the vertical call system 1.

  FIG. 6 shows an example of the data structure of the up / down direction operation schedule data stored in the up / down direction operation schedule storage unit 13. Up / down direction operation schedule data is stored for each car. In the example of FIG. 6, the up-and-down direction operation schedule data of each car is “upward allocation” indicating the floor where the upward call is generated, and “downward direction” indicating the floor where the downward call is generated. "Assignment", "cage call" indicating the destination floor.

  The up / down direction call registration time is stored in the up / down direction call registration storage unit 11.

  FIG. 7 shows an example of the data structure of the vertical direction call registration data stored in the vertical direction call registration storage unit 11. In the example of FIG. 7, the up / down direction call registration data includes “upper call registration time” indicating the time at which an upward call is registered and “down call registration” indicating the time at which a downward call is registered for each floor. Time "is included.

  Now, in order to convert the allocation in the vertical direction into the destination call format, it is necessary to supplement the information on the “destination floor” and “the circumference to be boarded”. The destination floor may be, for example, a floor that terminates in the calling direction. For example, if the 10th floor is the top floor and the 1st floor is the bottom floor, the destination for the upward allocation may be the 10th floor, and the destination for the downward allocation may be the first floor. The circumference to be boarded is, for example, a circumference in which the car can pass the floor next time in a specified direction.

  FIG. 8 shows an example of a car operation status monitored by the car operation monitoring unit 56.

  Here, it is assumed that the current “floor” and “direction” of the car can be grasped. If the car has already passed, the next lap is set. If the car has not passed yet, the current lap is set.

  By the way, the operation schedule stored in the up / down direction operation schedule storage unit 13 is also mixed with the operation plan based on the destination call converted into the vertical format and written. The information that needs to be transferred to the destination call system 5 is only the information corresponding to the call generated on the side of the system in the vertical direction (existing group management control system 100).

Whether or not the allocation in the vertical direction is generated from a call in the vertical direction can be determined from, for example, the floor where the call is generated. For example, in a 10-story office building, landing destination floor registration devices 6 ₁ and 6 ₂ are installed only on the first and fourth floors, and the up and down direction call registration device registration is performed only on each floor other than the first and fourth floors. When the devices 4 ₁ to 4 ₈ are installed, it can be determined that the assignment with the floor other than the first floor and the fourth floor as the departure floor is based on the up-down direction call.

  The call registration time corresponding to the allocation in the vertical direction is obtained from the vertical call registration storage unit 11 in FIG.

  It should be noted that a predetermined number of people or loads may be set for the call in the up-down direction and taken into account in the assignment.

  For the car call, for example, if the car is already on the destination floor of the destination call before getting off, it is based on the destination call, so there is no need for conversion. Select only car calls that have already boarded and are not on the destination floor of the destination call before getting off. More specifically, for example, referring to the destination call operation schedule data in FIG. 5, a destination call that satisfies the condition that the boarding time exists (has already boarded) and has not reached the “destination floor” (before getting off). 6, it can be determined that the “destination floor” that is the same as the destination call among the destination floors in the up-and-down direction travel schedule data of FIG. 6 is due to the destination call, and therefore, there is no need for conversion . On the other hand, if there is no destination call that satisfies the above conditions among the destination floors in the up-and-down direction travel schedule data of FIG. 6, it can be determined that the car is a “car call” that has occurred in the car. Can be selected as a car call. Here, a case where a corresponding car call is generated when the boarding time occurs after the destination call is registered is taken as an example. In addition, when the destination call information having the boarding time is deleted from the destination call operation schedule data in FIG. 5 when the getting-off is permitted, the destination call information is present, so that it is before the departure. Is shown.

  In the example of FIGS. 5 and 6, the car call having the seventh floor in FIG. 6 as the destination floor corresponds to the call ID 1 in FIG. 5, and thus is not subject to conversion. On the other hand, the car call having the tenth floor in FIG. 6 as the destination floor is subject to conversion because it can be seen that the corresponding destination call does not exist in FIG.

  Since the time at which the car call occurred is unknown, the current time may be substituted for the destination call generation time after converting the car call. Further, since the boarding time is unknown, for example, the current time may be substituted.

  In addition, since the departure floor of the car call cannot be grasped by the system, it may be a terminal floor that follows the direction opposite to the direction of the car. For example, if the 10th floor is the top floor and the 1st floor is the bottom floor, for example, if the car is an upward car that gets off at the 10th floor, it may be taken only on the first floor of the bottom floor.

  FIG. 9 shows pseudo destination call operation schedule data (hereinafter referred to as pseudo destination call operation) obtained by the operation schedule conversion extraction unit 72 converting information in the up / down direction operation schedule storage unit 13 and the up / down direction call registration storage unit 11. An example of the data structure) is shown. The data structure in FIG. 9 is assumed to be the same as the data structure in FIG.

  By the operation as described above, for example, the second floor upward allocation in FIG. 6 can be converted into the call ID 102 in FIG. 9, and the 10 floor downward allocation can be converted into the call ID 103 in FIG. 9. The car call on the 10th floor can be converted into the call ID 101 of FIG.

  In step S5, the destination call assignment processing unit 52 calculates a circumference in which a car (for example, No. A) that is currently being processed can be assigned to a newly registered destination call. This calculation may be performed using, for example, a new destination call, the positional relationship of the car, and capacity data stored in the capacity management storage unit 54.

  First, based on the positional relationship between the car and the call, the circumference that can be passed next in the direction indicated by the call is obtained.

  For example, in FIG. 8, No. A is in the third floor upward direction in the first lap. Considering the allocation of A-unit to the upward call (call ID 102 in FIG. 9) on the second floor in FIG. 6, since A-A can no longer respond in the first lap, the lap that can be answered earliest is the second lap. On the other hand, if it is a downward call on the 10th floor (call ID 103 in FIG. 9), Unit A can pass in this lap (because it can respond in the first lap), so the lap that can answer the earliest is the first lap become.

  Next, after the first lap that can be passed, the earliest lap that does not exceed the capacity even if a new call is assigned is obtained. However, the capacity over determination will be described later in detail.

  The capacity management storage unit 54 indicates the number of reservations regarding the number of people on the floor in the designated direction for departure with respect to the destination call assignment.

  FIG. 10 shows an example of the data structure of the capacity management data stored in the capacity management storage unit 54. The capacity management data is stored for each car to be assigned a destination call. In the example of FIG. 10, for each floor and each lap, “upper number of users” indicating the number of users boarding by an upper destination call, and “lower usage” indicating the number of users boarding by a lower destination call. Number ".

  For example, in the example of FIG. 5, in the first lap of the upward destination call on the 4th floor, there are two users, call ID1 that goes from the 1st floor to the 7th floor and call ID2 that goes from the 4th floor to the 8th floor. Since it exists, “2” is stored in the corresponding field in FIG.

  In addition, in the up / down direction call, it is not clear how many people get on and off in one response, so the pseudo destination call operation schedule data converted from the up / down direction allocation shown in FIG. 9 is not subject to the above capacity management. It is also good. However, since the number of passengers who can get on the destination call is reduced by the number of passengers who get on the call in the vertical direction, the upper limit for reservation of the destination call should be set to a value smaller than the capacity of that car for each car. Anyway. As a result, it is possible to reduce the possibility that the user cannot get on the vehicle as assigned to the destination call. For example, it may be determined that the destination call can be reserved with an upper limit of 80% of the capacity of the car, and the capacity limit may be determined. For the sake of simplicity, if the number of people that can be reserved is up to two, a new call with call ID = 4 cannot be boarded in the first lap, so the second lap is the earliest It is a lap that can be reserved. In addition, you may determine by a load instead of the number of people. For example, a predetermined value may be used as the load per person.

  In step S <b> 6, the destination call future prediction unit 55 performs the future prediction when a new call is not allocated while the future operation of the car is predicted. For example, assuming that there is no assignment for the destination call with call ID = 4 in the example of FIG. 5 (that is, assignment for boarding Unit A in the second lap from the fourth floor to the ninth floor), the future operation of Unit A is predicted. . This calculation is performed by using, for example, the time required for the car to travel from any floor to any floor, which is recorded in advance in the destination call future prediction unit 55, and the standard time required for opening the car. It can be easily obtained.

  FIG. 11 shows an example of the result of future prediction when temporary allocation is not considered.

  From the result of FIG. 11, it is possible to obtain a predicted boarding time and a predicted time of getting off for each call. Therefore, the service level for calls excluding the destination call with call ID = 4 can be calculated. An evaluation value can be obtained from the service level of each call, and an evaluation value as the entire future prediction can be obtained. For example, the sum of the waiting time and the boarding time for each call may be used as the evaluation value for each call, and the evaluation value for the entire future prediction may be the sum of the evaluation values for each call.

  In step S <b> 7, the destination call future prediction unit 55 performs the future prediction when a new call is allocated while the future operation of the car is predicted. For example, the future operation of Unit A is predicted, including the allocation to the destination call with call ID = 4 in the example of FIG. 5 (that is, the allocation from the 4th floor to the 9th floor in the second lap on board A).

  FIG. 12 shows an example of the result of future prediction when temporary allocation is considered.

  For future predictions that take into account provisional allocation, it is possible to obtain evaluation values for each call and use them to obtain evaluation values for the entire future prediction. The evaluation value obtained in step S7 is different from the evaluation value obtained in step S6 in that a destination call with call ID = 4 is added to the call to be evaluated. Next, the difference is that the change in the traveling of the car due to the addition of the destination call with call ID = 4 has an effect on the response to calls other than the destination call with call ID = 4.

  In step S8, it is determined whether the evaluation has been completed for all the cars. For example, when there are six cars, it is checked whether the process up to the sixth car has been completed. If completed, the process proceeds to step S9. If not completed, the number of cars to be processed is advanced by one and the process returns to step S4. For example, when the machine A has been set as a processing target until now, the machine B is set as a processing target next.

  In step S9, the assigned car is determined based on the evaluation of each car. The future actual operation plan of the elevator is to allocate a new destination call with call ID = 4 to any one car and not all the remaining cars to operate. Therefore, an evaluation value when a destination call with call ID = 4 is temporarily assigned to a specific vehicle, and an evaluation when a destination call with call ID = 4 is not temporarily assigned to all the remaining cars. All the sums with the values may be obtained for each car to be temporarily assigned, and the car that has been temporarily assigned with the smallest sum of the evaluation values may be selected as the final assigned car.

  In step S <b> 10, the determined assigned car is added to the destination call operation schedule storage unit 53 and the capacity management storage unit 54. In the row of call ID 4 in FIG. 5, a cycle in which the allocation car and the allocation car are temporarily allocated is assigned to the allocation car and allocation cycle column. Further, 1 is added to the elements in the fourth floor, the upward direction, and the second lap in FIG.

By the way, at this stage, the allocation information is not transmitted to the landing destination floor registration devices ₆₁ to _Z or the up and down direction calling system 1. Therefore, the user cannot know the assigned car. For example, at the time of going to YES in step S1 in the flowchart of FIG. 3, the landing destination floor registration devices _{61 to Z} display a message prompting to wait for notification of the assigned car, such as “Please wait for a while”. Also good.

  Also, at this stage, the operation of the car according to the allocation does not start. A method for notifying the user of the assignment or transferring the assignment to the up and down call system 1 will be described.

  FIG. 13 shows an example of a process for transferring the destination call assignment to the up and down call system 1.

  The process of FIG. 13 is executed periodically, for example. For example, it may be activated every tenth of a second.

In step S21, the car operation monitoring unit 56 detects whether the current floor and / or direction of the single cars 31- _X has changed. If there is a change, the process proceeds to step S22. If there is no change, the process proceeds to step S25.

  In step S22, the allocation up to one turn ahead is converted into the vertical allocation for each car. For example, the destination call with call ID = 4 in FIG. 5 does not correspond to the condition that the first round is ahead when Unit A is in the state before passing the fourth floor on the first lap as shown in FIG. Applicable at the time of departure from the floor, it can be converted to the 4th floor upward allocation.

  In step S23, the allocation data in the vertical direction obtained by the conversion in step S22 is transferred to the vertical operation schedule storage unit 13 of the vertical direction call system 1. For example, if the machine A has departed from the 4th floor, the allocation of the upward movement of the 4th floor of the A machine is transferred to the up / down direction operation schedule storage unit 13 of the A machine shown in FIG.

  In the example of FIG. 6, for example, if the car is in the first round and shows the state before responding to the allocation in the fourth floor upward direction, the second round of the call ID = 4 in the example of FIG. The assignment (getting on the 4th floor, getting off on the 9th floor, the assigned car is A, the assigned lap is 2) is not yet transferred to the up / down direction operation schedule storage unit 13. In response to the allocation of the fourth floor in the first round of the car, when the car departs from the fourth floor, the allocation of the second lap of call ID = 4 in FIG.

In step S24, the car navigation monitor 56, the subject is called transferred in step S23 in the vertical direction service schedule storage unit 13, the registration storage unit 51 destination call, the allocated car to the corresponding car stop destination floor registration device 6 _k Instruct to display.

In the destination call registration storage unit 51, to the corresponding car stop destination floor registration device 6 _k, and it notifies to display the allocated car. In this notification, an assigned car (or an assigned car, an assigned lap) may be instructed. The landing destination floor registration devices _{61 to Z} that receive this notification display the assigned car at a predetermined timing. In addition, for example, the hall destination floor registration device 6 ₂ of the fourth floor of the hall is, "Please ride in the second round to the A Unit." As in, may display the notification of the allocated car.

For example, as described above, when only the _assigned car is displayed on the landing destination floor registration devices ₆₁ to _Z for the first time when it is possible to board in one more lap, Only calls that are ready for transfer can be displayed.

  In addition, for example, when the “assigned car” and “the lap to be boarded” are displayed immediately after the call registration regardless of whether or not it can be boarded in one more lap, it is transferred to the up / down direction operation schedule storage unit 13. Even in the previous stage, the “assigned car” and the “lap to be boarded” can be displayed.

Further, the destination call registration storage unit 51 deletes the call ID of the call for which the assigned car has been notified from the storage area. For example, in FIG. 4, when it is notified of the allocated car for the destination call of the call ID = 4 to the fourth floor of the car stop destination floor registration device 6 _2, called ID = 4 corresponding to the car stop destination floor registration device HDC-ID = 1 Delete the information.

  In step S25, the car operation monitoring unit 56 determines that the car has responded to the assigned destination call. For this determination, for example, it is possible to use a method that considers that the assigned car has responded when the car is opened on the departure floor in the assigned circumference and direction.

  If it is determined that the car responds to the destination call, the process proceeds to step S26. If it is determined not to respond, the process proceeds to step S29.

  In step S26, since the assigned user is expected to get on, it is necessary to notify the up / down direction operation schedule storage unit 13 of the schedule for stopping the car on the destination floor. The operation schedule conversion output unit 71 generates a car call for all the destination floors of the responded calls. For example, in the example of call ID = 2 in FIG. 5, when the A machine responds on the 4th floor in the first lap, a car call is generated on the 8th floor.

  In step S27, the car call generated in step S26 is transferred to the up / down direction operation schedule storage unit 13 of the up / down direction call system 1. In the example of FIG. 6, a car call is written on the eighth floor.

  In step S28, the car operation monitoring unit 56 writes the boarding time for the responded destination call stored in the destination call operation schedule storage unit 53. The boarding time is the time when the response is started. For example, when the current time is 8: 0: 21, and Unit A responds in the upward direction on the fourth floor, 8: 0: 21 is written in the boarding time of the destination call with call ID = 2 in FIG. The destination call data in which the boarding time has already been written is not changed again.

  In step S29, it is determined whether or not the assigned car is opened on the destination floor of the destination call for which the boarding time is set. If it is determined that the assigned car has been opened, the process proceeds to step S30. Otherwise, the flowchart ends.

  In step S30, the user who registered the call opened on the destination floor gets off at the destination floor and ends the service use. Therefore, the information on the destination call that ended the service is deleted from the destination call operation schedule storage unit 53. . For example, in the example of FIG. 5, when Unit A opens on the 7th floor in the first lap, the row in which the destination call with call ID = 2 is deleted from the table.

  Thus, every time a new destination call is registered, the operation schedule stored in the up / down direction operation schedule storage unit 13 is used by the destination call future prediction unit 55 via the operation schedule conversion output unit 71. When the destination call assignment processing unit 52 performs destination call assignment processing, the destination call assignment processing unit 52 stores not only the operation schedule based on the destination call stored in the destination call operation schedule storage unit 53 but also the up / down direction operation schedule storage unit 13. In addition, since the operation plan by the up-down direction call and the car call can also be reflected, the future car operation can be predicted more accurately than the case where the future prediction is performed using only the operation schedule of the destination call operation schedule storage unit 53, It is possible to select an allocation car that can provide a more appropriate service. The index for measuring the appropriateness of the service is determined by a method for evaluating the future prediction used in step S6 and step S7 in FIG.

In addition, since the assigned destination call is transferred to the up / down direction operation schedule storage unit 13 in accordance with the operation of the car, the operation plan stored in the destination call operation schedule storage unit 53 is transferred to the up / down direction operation schedule storage unit 13. The cars ₃₁ to _X can be operated by reflecting in the above.

  Furthermore, when assigning the up / down direction call, since the up / down direction operation schedule storage unit 13 records the assignment by the destination call for one lap in the future, the up / down direction allocation processing unit 12 performs the car operation plan by the destination call. Reflecting the above, it is possible to select an assigned car for up and down calls.

  For example, in the above-described method of displaying the “assigned car” and “the lap to be boarded”, when the lap to be boarded is the first lap, the display of “the lap to be boarded” is omitted, Only the “assigned car” may be displayed, and the “assigned car” and “the lap to be boarded” may be displayed only when the lap to be boarded is after the second lap.

  In addition, for example, the above-described method of displaying the “assigned car” and “the lap to be boarded” is used only in a specific time zone (for example, a time zone registered in advance as a busy hour), and other times. For the belt, the method of displaying only the “assigned car” as described above (only when it becomes possible to board in one more lap) may be used.

  In addition, the processing related to “the lap to be boarded” may be performed only in a specific time zone (for example, a time zone registered in advance as a time of congestion).

  Further, the processing related to “the lap to be boarded” may be omitted.

In the above description, it is assumed that the vertical direction call registration devices ₄₁ to _Y and the landing destination floor registration devices ₆₁ to _Z are exclusively installed on individual floors where the elevator can be used. However, there may be a floor where both the vertical direction call registration devices ₄₁ to _Y and the landing destination floor registration devices ₆₁ to _Z are installed.

Moreover, according to a time slot _| zone, the floor which uses the up-down direction call registration apparatus _41-Y and the landing destination floor registration apparatuses _61-Z exclusively may exist.

  As described above, according to the present embodiment, when an existing group management control system capable of registering and assigning only up-and-down calls is expanded to enable registration and assignment of destination calls, the existing group management control system can be used. Without removing the system, it can be expanded while retaining its functionality. Therefore, the amount of work required for expansion can be reduced compared with the method of removing the existing system. In addition, during the expansion, by continuing the operation of the existing group management control system, it is possible to continue the operation of the elevator with the function before the expansion. Therefore, the period during which the elevator cannot be used due to renewal can be made shorter than before.

  According to the elevator group management control system of the embodiment described above, the system is effectively added to enable the destination call to the existing elevator group management control system capable of only calling up and down. It becomes possible.

The instructions shown in the processing procedure shown in the above embodiment can be executed based on a program that is software. A general-purpose computer system stores this program in advance, and by reading this program, it is possible to obtain the same effect as the effect of the elevator group management control system of the above-described embodiment. The instructions described in the above-described embodiments are, as programs that can be executed by a computer, magnetic disks (flexible disks, hard disks, etc.), optical disks (CD-ROM, CD-R, CD-RW, DVD-ROM, DVD). ± R, DVD ± RW, etc.), semiconductor memory, or a similar recording medium. As long as the recording medium is readable by the computer or the embedded system, the storage format may be any form. If the computer reads the program from the recording medium and causes the CPU to execute instructions described in the program based on the program, the same operation as the elevator group management control system of the above-described embodiment is realized. Can do. Of course, when the computer acquires or reads the program, it may be acquired or read through a network.
In addition, the OS (operating system), database management software, MW (middleware) such as a network, etc. running on the computer based on the instructions of the program installed in the computer or embedded system from the recording medium implement this embodiment. A part of each process for performing may be executed.
Furthermore, the recording medium in the present embodiment is not limited to a medium independent of a computer or an embedded system, but also includes a recording medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.
Further, the number of recording media is not limited to one, and when the processing in this embodiment is executed from a plurality of media, it is included in the recording medium in this embodiment, and the configuration of the media may be any configuration.

The computer or the embedded system in the present embodiment is for executing each process in the present embodiment based on a program stored in a recording medium. The computer or the embedded system includes a single device such as a personal computer or a microcomputer. The system may be any configuration such as a system connected to the network.
In addition, the computer in this embodiment is not limited to a personal computer, but includes an arithmetic processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions in this embodiment by a program. ing.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the 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.

DESCRIPTION OF SYMBOLS 100 ... Existing elevator group management control system, 101 ... Expanded elevator group management control system, 102 ... Expansion system, 1 ... Vertical call system, 11 ... Vertical call registration memory | storage part, 12 ... Vertical direction allocation process parts, 13 ... vertical service schedule storage unit, 14 ... vertical future prediction unit, 15 ... car operation control monitoring unit, _{2 1 to X ...} single car control unit, _{3 1 to X ...} basket, 31 _{1 to X ...} basket Call button, 4 1 _-Y ... _{Up and} down direction call registration device, 5 ... Destination call system, 51 ... Destination call registration storage unit, 52 ... Destination call assignment processing unit, 53 ... Destination call operation schedule storage unit, 54 ... Capacity management storage , 55 ... Destination call future prediction unit, 56 ... _Car operation monitoring unit, _61-Z ... Landing destination floor registration device, 7 ... Assignment information conversion unit, 71 ... Operation schedule conversion output unit, 72 ... Operation schedule conversion extraction Part

Claims (10)

In order to manage the operation of multiple cars, the vertical direction contains information about the up-and-down calls made on each departure floor assigned to each car and the car calls made to each destination floor in each car Elevator group management for expansion to add destination calls to the existing elevator group management control system for up / down direction call and car call with up / down direction operation schedule storage unit that stores operation schedule information A control system,
A landing destination floor registration device provided on at least one departure floor, for registering a destination call specifying the destination floor;
A destination call registration storage unit for storing registration of the destination call by the landing destination floor registration device;
A destination call assignment processing unit for assigning an assigned car to the new registration of the destination call;
For each of the destination calls, a destination call operation schedule storage unit for storing destination call operation schedule information including information on the departure floor and the assigned car and the destination floor;
The destination call operation schedule information for the new registration of the destination call is converted into information about the up / down direction call and information about the car call, and the converted up / down direction call and information about the car call are stored in the up / down direction operation schedule storage. A first conversion unit to be given to the unit;
The information about the up / down direction call and the information about the car call stored in the up / down direction operation schedule storage unit are converted into the destination call operation schedule information except for the information converted from the destination call, and the conversion The elevator group management control system including a second conversion unit that provides the destination call operation schedule information to the destination call operation schedule storage unit. In order to manage the operation of multiple cars, the vertical direction contains information about the up-and-down calls made on each departure floor assigned to each car and the car calls made to each destination floor in each car Elevator group management control system for up and down direction calls and car calls with an up and down direction operation schedule storage unit for storing operation schedule information, and an elevator group management control system for expansion to add destination calls An elevator group management control system comprising:
An elevator group management control system for expansion for adding the destination call,
A landing destination floor registration device provided on at least one departure floor, for registering a destination call specifying the destination floor;
A destination call registration storage unit for storing registration of the destination call by the landing destination floor registration device;
A destination call assignment processing unit for assigning an assigned car to the new registration of the destination call;
For each of the destination calls, a destination call operation schedule storage unit for storing destination call operation schedule information including information on the departure floor and the assigned car and the destination floor;
The destination call operation schedule information for the new registration of the destination call is converted into information about the up / down direction call and information about the car call, and the converted up / down direction call and information about the car call are stored in the up / down direction operation schedule storage. A first conversion unit to be given to the unit;
The information about the up / down direction call and the information about the car call stored in the up / down direction operation schedule storage unit are converted into the destination call operation schedule information except for the information converted from the destination call, and the conversion The elevator group management control system including a second conversion unit that provides the destination call operation schedule information to the destination call operation schedule storage unit.   The second conversion unit uses a predetermined value corresponding to the direction of the car related to the up / down direction call as the destination floor for the up / down direction call stored in the up / down direction operation schedule storage unit. The elevator group management control system according to claim 1, wherein conversion to a destination call is performed.   The second conversion unit performs conversion into a destination call by using a predetermined value as the number of users or the load for the up / down direction call stored in the up / down direction operation schedule storage unit. The elevator group management control system according to claim 1 or 2.   The second conversion unit uses a predetermined value corresponding to the direction of the car related to the car call as a departure floor with respect to the car call stored in the up-and-down direction operation schedule storage unit. The elevator group management control system according to any one of claims 1 to 4, wherein conversion into a destination call is performed by the following.   The elevator group management control system according to any one of claims 1 to 5, wherein registration of one destination call corresponds to one user. The allocation processing unit also allocates a lap to be boarded in the allocation car for a new registration of the destination call,
The elevator group management control system according to claim 6, wherein the destination call operation schedule information includes the circumference to be boarded.   The allocation processing unit allocates a circumference to be boarded in the allocated car in consideration of the capacity of the car and the number of persons or the load corresponding to the destination call for the new registration of the destination call. The elevator group management control system according to claim 7. The elevator group management control system for the up-down direction call and the car call is as follows:
An up / down direction call registration device for registering up / down direction calls that are provided on a plurality of departure floors that allow up / down direction calls and that designates only the direction;
An up / down direction call registration storage unit for storing registration of the up / down direction call by the up / down direction call registration device;
An up-down direction allocation processing unit for allocating an assigned car for the new registration of the up-down direction call;
The operation control monitoring part which instruct | indicates operation to a single-car control part based on the said up-down direction operation schedule information memorize | stored in the said up-down direction operation schedule memory | storage part, and monitors the condition of operation is included. The elevator group management control system according to any one of the above. The elevator group management control system for adding the destination call further includes a car operation monitoring unit for grasping the position and direction of each car and the number of laps currently in operation.
The first conversion unit obtains information about the position and direction of each car and the number of laps currently in operation from the car operation monitoring unit, and the assigned destination stored in the destination call operation schedule storage unit Select one of the calls that will be answered before each car goes around the hoistway, and give the converted up / down call and information about the car call to the up / down operation schedule storage unit. The elevator group management control system according to any one of claims 1 to 9.

Images