JP2022094543A - Determination method of allocation car unit and group management control device - Google Patents

Abstract

To provide a group management control device capable of enabling a split operation without losing convenience for a user.SOLUTION: A group management control device controls the operation of multiple car units based on the landing call input by an elevator system capable of switching which device to use on the floor where a destination floor registration device at a landing and an up/down call registration device are arranged together. Upon determining an allocation car unit by the group management control device, a split operation is not carried out while using the destination floor registration device at the landing when the split operation to split the multiple car units by system and to operate them is carried out. The group management control device checks departure floor information, destination floor information, a landing call non-stop floor of each car unit, and a car call non-stop floor, and selects a car unit capable of answering, and determines an allocation car unit from among the selected car units. The group management control device separates the up/down call registration device by system while using the up/down call registration device, and based on the floor position of the up/down call registration device with the call input, selects which car unit is to be allocated, and determines the allocation car unit.SELECTED DRAWING: Figure 2

Description

An embodiment of the present invention relates to a method for determining an assigned unit and a group management control device.

To call the elevator on which the user rides at the elevator landing, use the up / down call registration device that calls the elevator in the direction of the user's destination floor by operating the up / down call button. In some cases, a destination floor registration device (hereinafter, also referred to as “HDC device”) is installed at the landing, and a landing destination floor registration system that performs destination floor registration from the HDC device may be used.

In the landing destination floor registration system, there are cases where the landing destination floor registration device is not installed at the landing but is installed at the entrance or in the middle of the moving passage.

On the other hand, the up / down call button of the landing on the low-rise unit side is set as a button for calling the low-rise unit as in the split operation in the group management. On the other hand, the up and down buttons on the landing on the high-rise unit side are set as buttons for calling the high-rise unit.

As described above, it is difficult to control the system separately in the upper and lower call registration device, and there is a problem that the convenience for the user is impaired.

Japanese Unexamined Patent Publication No. 2016-16990

However, when performing split operation in the landing destination floor registration system that switches between the conventional up / down call button and the destination floor registration device, it is difficult to control the system separately in this way, and it is also difficult for the user. It will impair convenience.

The present invention proposes a response sharing method when performing split operation in a landing destination floor registration system that switches between an up / down call button and a destination floor registration device, and performs split operation without impairing user convenience. It is an object of the present invention to provide a method for determining an assigned unit and a group management control device that enable it.

The embodiment for achieving the above object is based on the landing call input from the elevator system which can switch which device is used on the floor where the landing destination floor registration device and the vertical call registration device are installed side by side. When the group management control device that controls the operation of a plurality of units performs a split operation in which the plurality of units are divided according to the system to determine the assigned unit, the use of the landing destination floor registration device. Without performing the above-mentioned split operation, the departure floor information, the destination floor information, the landing call non-stop floor of each unit, and the car call non-stop floor are checked to select and select the units that can respond. The assigned unit is determined from the units, and while the vertical call registration device is in use, the vertical call registration device is system-separated, and which unit is assigned based on the floor position of the vertical call registration device to which the call is input. It is a method of determining the assigned machine by selecting whether it is a target or not and determining the assigned machine.

The block diagram of the elevator system which applied the group management apparatus of embodiment. The flowchart which shows the processing procedure of the group management control apparatus of embodiment. An explanatory diagram showing the concept of the embodiment. An explanatory diagram showing the concept of the embodiment. The flowchart which shows the processing procedure of the group management control apparatus of another embodiment. The flowchart which shows the processing procedure of the group management control apparatus of still another embodiment. A flowchart showing the non-stop floor check process by the learning unit.

<Concept of embodiment>
As shown in FIG. 3, in the divided operation in the group management using the up and down buttons, the up and down buttons to be used are installed in the form of one for each unit or one for every two units. FIG. 3 is an example of one in two.
In the figure, △ ▽ indicates the up / down call button or the call direction, and 〇 indicates the car call.

During normal operation using the up and down buttons, any of the eight units A to H is assigned to all the up and down buttons.

At this time, if the demand of users becomes particularly high, each unit will stop on each floor if all units are left on all floors, and the lap time will become longer, resulting in better landing call service performance. It will drop significantly.

For this reason, each unit is divided / shared, for example, for lower floor services / higher floor services, and the floors that can be serviced are restricted by setting landing non-stop / car call non-stop as shown in Fig. 4. Implement split operation / response sharing. As a result, it is possible to reduce the number of stopped floors, shorten the lap time, and improve service performance for both low-rise and high-rise units.

In this split operation, the up and down buttons cannot determine on which floor the user wants to get off. For this reason, on floors where user demand for boarding is extremely high, for example, on the reference floor during work hours, the up and down buttons should be forcibly separated for low-rise units and high-rise units (separate the input system). I have to. For example, in FIG. 4, the upper and lower buttons installed in the low-rise units A to D are treated as for the low-rise unit, and the upper and lower buttons installed in the E to H units are treated as for the high-rise unit, and the upper and lower buttons of which unit are pressed. Based on the fact that it was done, it is first decided whether to allocate to the low-rise unit or the high-rise unit, and then the most suitable unit is selected.

However, in the landing destination floor registration device, it is not always installed in the form of one for each unit or two units like the up and down buttons. It may be installed in front of the landing entrance or in a place away from the landing, and there are cases where each landing destination floor registration device cannot be forcibly treated as a low-rise / high-rise machine. In addition, when inputting a call using the landing destination floor registration device, not only the floor on which the user gets on (departure floor) but also the floor on which the user gets off (destination floor, destination floor) is input as information. It is not necessary to forcibly decide whether to allocate to the low-rise unit or the high-rise unit, and the allocation can be carried out in consideration of the convenience of the user.

Therefore, in the embodiment, which of the up / down button / the landing destination floor registration device is used by the floor where the user's boarding demand is extremely large (the reference floor of the work time zone, etc.) when the divided operation is performed. By changing the allocation control, it is possible to carry out split operation / response sharing.

<First Embodiment>
<< Configuration of Embodiment >>
FIG. 1 is a block diagram showing a configuration of an elevator system 100 to which a landing call registration method switching method and an embodiment of a group management control device are applied.

As shown in FIG. 1, the elevator control system 1 includes a group management control device 10 for group management control of eight elevators A to H, and a landing destination floor registration device connected to the group management control device 10. It is equipped with 20 and two vertical call registration devices 30 and 40. We have at least two up / down call registration devices. Further, under the control of the group management control device 10, the Unit A control device 50A for controlling the Unit A elevator, the Unit B control device 50B for controlling the Unit B elevator, ..., The Unit H control device for controlling the Unit H elevator. It is equipped with 50H.

The group management control device 10 includes a landing call input unit 11, a registration method switching unit 12, an allocation control unit 13, a unit information input unit 14, and an allocation command output unit 15.

The landing call input unit 11 includes a vertical call registration information input unit 16 and a destination floor registration information input unit 17. The vertical call registration information input unit 16 inputs the vertical call information registered from the vertical call registration devices 30 and 40. The destination floor registration information input unit 17 inputs the destination call registration information registered from the landing destination floor registration device 20.

The registration method switching unit 12 switches whether to select the up / down call registration information input unit 16 or the destination floor registration information input unit 17 when a predetermined condition such as a time condition is satisfied.

The allocation control unit 13 evaluates each elevator from the vertical call information from the vertical call registration information input unit 16 and the unit information from the unit information input unit 14, and determines the optimum vertical call allocation unit. Further, from the destination call registration information from the landing destination floor registration device 50 and each unit information from the unit information input unit 14, each elevator information such as response information, car direction, and car load, and elevator demand information are used. Elevator is evaluated and the optimum assigned machine is determined for each registered destination floor call.

The unit information input unit 14 collects unit information from the unit control devices 50A to 50H of each unit and outputs the unit information to the allocation control unit 13.

The allocation command output unit 15 outputs the allocation command generated by the allocation control unit 13 to the unit control devices 50A to 50H.

<< Processing procedure of the first embodiment >>
Next, the processing procedure of the first embodiment will be described with reference to the flowchart of FIG.

First, it is determined whether or not a landing call has been input (step S1). Once the landing call is input, it is determined whether the input call is from the landing destination floor registration device (step S2).

It is determined whether the departure floor of the input call is a serviceable floor, that is, a non-stop floor for the landing call (step S3). If the departure floor is a serviceable floor (step S3YES), then it is determined whether the input destination floor of the call is serviceable, that is, whether it is a car call non-stop floor (step S4). If the destination floor is a serviceable floor (step S4YES), the corresponding machine is designated as a assignable machine (step S5). The processing of steps S3 to S5 is determined for all units.

When the processing of steps S3 to S5 for all the units is completed, the allocation processing is performed for the allottable units, and the optimum unit is determined (step S6).

On the other hand, when the call is from the up / down button in step S2, it is next determined whether the input floor is the system separation floor (step S7).

If the input floor is a system separation floor (step S7YES), then it is determined whether the input system is a low-rise unit (step S8). When the input system is a low-rise unit (step S8YES), the assignable unit is only the low-rise unit (step S9). When the input system is not a low-rise unit, that is, when the input is from a high-rise unit (step S8NO), the assignable unit is limited to the high-rise unit (step S10). That is, the units are assigned according to whether the upper and lower call registration devices 30 and 40, which are input systems, are located in the low-rise unit, the high-rise unit, or the floor position. For example, if the vertical call registration device 30 is in the low-rise unit and the vertical call registration device 40 is in the high-rise unit, if the input system is the vertical call registration device 30, the low-rise unit is assigned, and if the input system is the vertical call registration device 40. Allocate high-rise units.

If the input floor is not a system separation floor (step S7NO), the assigned units are all units (step S11).

Next, it is determined whether the input departure floor of the call is serviceable, that is, whether it is a landing call non-stop floor (step S12). If the service is possible, the corresponding unit remains assignable (step S13). If the service is not possible, the corresponding machine is changed to unassignable (step S14).

After performing the processes of steps S12 and S13 for the number of allottable units, the allottable units are subjected to the allocation process to determine the optimum unit (step S6).

Next, the operation of the embodiment will be specifically described.

For example, in the response sharing shown in FIG. 4, it is assumed that the call from the 1st floor to the 7th floor is registered from the landing destination floor registration device 20 during the division operation. At this time, the landing call non-stop on the 1st floor upward (UP) is not set for all Units, but the 7th floor car call non-stop is set for Units A to D and set for Units E to H. It has not been. Therefore, as a result, the allottable units are assigned to the units E to H, and the most suitable unit is assigned to any of the units.

Further, it is assumed that the call from the 10th floor to the 1st floor is registered by the landing destination floor registration device 20 during the split operation. At this time, the non-stop calling of the car on the 1st floor is not set for all Units, but the non-stop calling of the landing on the 10th floor (DN) is set for Units A to D, and for Units E to H. Not set. Therefore, as a result, the allottable units are assigned as the E to H units, and are assigned to the most suitable unit among any of the units.

On the other hand, if the call for UP on the 1st floor is registered by the vertical call registration device on the Unit A to D side during the split operation, it is not possible to check the car call non-stop because there is no destination floor information. It is unclear whether the allocation should be made to low-rise units or high-rise units. Therefore, based on the input system, the low-rise units A to D are first assigned as the assignable units, and then the response sharing is made possible by checking the 1st floor UP landing call non-stop of the A to D units.

As described above, according to the first embodiment, the divided operation can be performed without impairing the convenience of the user.

Further, the split operation can be applied even in a configuration in which a landing destination floor registration device 20 such as a flapper gate, which is difficult to separate the system, is installed.

<< Modification 1 of the first embodiment >>
When all floors of the building are using the landing destination floor registration device 20, normal allocation is performed by ignoring non-stop floors when calling the destination floor even during split operation, and by allocation control. Carry out divided operations. When the upper and lower call registration devices 30 and 40 are being used on some floors, the non-stop floor information by the destination floor call is checked and the allocation is performed. This makes it possible to realize the same operation as the split operation.

<< Modification 2 of the first embodiment >>
When all floors of the building are using the landing destination floor registration device 20, the non-stop floor information of the car call is not checked, and it is based on the unique number (ID) attached to each landing destination floor registration device 20. , Determine the allocation destination by judging the system of the unit to which the car was called. This makes it possible to improve the operability of the user.

<Second Embodiment>
<< Configuration of Embodiment >>
FIG. 5 is a block diagram showing the configuration of the elevator system 1B of the second embodiment.

The elevator system 1B shown in FIG. 5 is provided with a learning unit 18 in the group management control device 10. The learning unit 18 measures the usage status from the departure floor to the destination floor and creates an OD table (Origin Destination Table). This OD table is a table showing how many users have moved from the departure floor to the destination floor in the past fixed period by time zone. By creating this OD table, it is possible to determine which unit will be serviced on which floor and how many units will be serviced, and flexibly change the non-stop floor to enable more response sharing according to demand.

<< Processing procedure of the second embodiment >>
Next, the processing procedure of the second embodiment will be described with reference to the flowcharts of FIGS. 7 and 6.

In the flowchart of FIG. 6, the process of step S20 is added between the process of step S5 and the process of step S6 of the flowchart of FIG. 2, and the non-stop floor check process is performed by the learning unit 18. Since the other processes are the same as those in the first embodiment, the description thereof will be omitted.

FIG. 7 is a flowchart showing a non-stop floor check process executed by the learning unit in step S20.

First, it is determined whether or not the landing destination floor registration device is in use on all floors (step S21). If it is in use, an OD table is created for all the units based on the past data (step S22). Then, based on the created OD table, it is determined which unit and how many units are to be serviced on which floor, and the non-stop floor information is changed (steps S23 and S24).

In this way, according to the second embodiment, by creating a past OD table, determining which unit and how many units are to be serviced on which floor, and flexibly changing the non-stop, it is possible to better meet the demand. Response sharing is possible.

<< Modification example of the second embodiment >>
When the non-stop setting determined by learning is applied based on the call registration information in the current landing destination floor registration device, the appropriate service can be implemented as a result of the judgment based on the index such as the average unresponsive time. May not be. For example, when the average unresponsive time exceeds a certain value, the non-stop setting may be changed to control so that an appropriate service can be executed.

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

1A, 1B ... Elevator system, 10 ... Group management control device, 11 ... Landing call input unit, 12 ... Registration method switching unit, 13 ... Allocation control unit, 14 ... Unit information input unit, 15 ... Allocation command output unit, 16 ... Vertical call registration information input unit, 17 ... Destination floor registration information input unit, 18 ... Learning unit, 20 ... Landing destination floor registration device, 30, 40 ... Vertical call registration device, 50A ... Unit A control device, 50B ... Unit B control Device, 50C ... Unit C control device, 50H ... Unit H control device

The embodiment for achieving the above object is based on the landing call input from the elevator system which can switch which device is used on the floor where the landing destination floor registration device and the vertical call registration device are installed side by side. In determining the assigned unit, the group management control device that controls the operation of a plurality of units is in the process of performing a split operation in which the plurality of units are divided into systems and operated , and the landing destination floor. While using the registration device, check the departure floor information, destination floor information, landing non-stop floor of each unit, and car call non-stop floor to select the units that can respond without separating the system . The assigned unit is determined from the selected units, and while the division operation is being carried out and the upper / lower call registration device is in use, the upper / lower call registration device is system-separated and the upper / lower call is input. This is a method for determining an assigned unit by selecting which unit is to be assigned based on the floor position of the registration device and determining the assigned unit.

Claims (6)

Group management that controls the operation of multiple units based on the landing call input from the elevator system that can switch which device to use on the floor where the landing destination floor registration device and the vertical call registration device are installed. When the control device decides the assigned unit,
When carrying out a split operation in which the plurality of units are divided and operated for each system
While using the landing destination floor registration device, it is possible to check and respond to departure floor information, destination floor information, landing call non-stop floor, and car call non-stop floor of each unit without performing the split operation. Units are selected, and the assigned unit is determined from the selected units.
While using the vertical call registration device, the vertical call registration device is system-separated, and based on the floor position of the vertical call registration device to which the call is input, which unit is to be assigned is selected and the assigned unit is selected. How to determine the assigned machine to be determined. When all floors of the building are using the landing destination floor registration device, normal allocation is performed by ignoring non-stop floors in the destination floor call even during split operation, and by allocation control. Carry out divided operation,
The method for determining an allotted machine according to claim 1, wherein when the up / down call registration device is being used on some floors, the non-stop floor information by the destination floor call is checked and the allocation is carried out. If all floors of the building are using the landing destination floor registration device, the non-stop floor information of the car call is not checked, and the car call is based on the unique number attached to each landing destination floor registration device. The method for determining an assigned unit according to claim 2, wherein the system of the assigned unit is determined and the allocation destination is determined. If you are using the landing destination floor registration device on all floors and you want to check the non-stop floors and make allocations, the learning function will be used to determine which floor based on past departure and destination floor information. The method for determining an allotted unit according to claim 1, wherein the number of units to be serviced is determined and the non-stop floor information is changed. When the non-stop setting determined by learning is applied based on the call registration information in the current landing destination floor registration device, the appropriate service can be implemented as a result of the judgment based on the index such as the average unresponsive time. The method for determining the assigned machine according to claim 4, wherein if it is determined that there is no such information, the non-stop floor information is changed. A group management control device that implements the allocation unit determination method according to any one of claims 1 to 5.

Images