JP7027516B1 - Group management control device for double deck elevators and group management control method for double deck elevators - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a group management control device of a double deck elevator capable of executing group management control having high service performance with a low processing load. According to an embodiment, a group management control device for a double-deck elevator has a virtual call information storage unit that stores virtual call information generated by predicting the occurrence, and a double-deck elevator for a landing call. Allocation patterns for multiple double-deck elevators for landing calls and virtual calls, with the upper and lower cars assigned and only the upper or lower car assigned to virtual calls. Select the elevator group allocation pattern generation unit that generates the elevator group allocation pattern information shown, the elevator group allocation pattern evaluation unit that calculates the evaluation value for each elevator group allocation pattern, and the optimum elevator group allocation pattern from the evaluation values. It is equipped with an allocation car determination unit that determines the car to be assigned to the landing call. [Selection diagram] Fig. 1

Description

An embodiment of the present invention relates to a group management control device for a double deck elevator and a group management control method for a double deck elevator.

A system that controls multiple elevators in an integrated manner is called an elevator group management control system. In particular, a group management control system in which each elevator is composed of a double deck elevator in which an upper car and a lower car are connected is called a double deck group management control system. Service performance such as user waiting time is called group management performance, and it is desirable to build a group management control system with high group management performance.

In the elevator group management control system, when a user registers a landing call at the landing, an allocation process is performed to determine a car (allocation car) that responds to the call so that the user can be transported most efficiently.

When performing the allocation process to the landing call for a plurality of elevators, first, an allocation pattern of a plurality of elevators in which various elevators are provisionally allocated to the generated landing call is assumed. Then, the time required to respond to the landing call is estimated for each assumed allocation pattern, and the best allocation pattern that can respond to the landing call and the registered call as soon as possible is selected. Then, the allocation is actually performed based on the information in the selected allocation pattern.

Japanese Unexamined Patent Publication No. 2020-1860 Japanese Patent No. 5920674

In recent years, in order to maintain good group management performance in the future, there are cases where several calls "virtual calls" that are expected to occur in the future are prepared in advance and allocation processing is performed using these.

In the allocation process using virtual calls, it is assumed that there are multiple allocation patterns in which various baskets that are candidates for allocation are provisionally allocated to the generated landing calls and virtual calls. Then, the operation is predicted for each of the assumed patterns, the time required for the response is evaluated for the generated landing call and virtual call, and the registered call, and the best pattern as a whole is selected. .. Then, the car assigned to the landing call in the best pattern is determined as the car to be selected as the result of the allocation process (allocation car).

When this allocation process is used in a group management control system for double-deck elevators, the number of cars per number of elevators is doubled compared to when it is used in a group management control system for single-deck elevators with one car. Therefore, the number of allocation patterns generated is very large. Therefore, there is a problem that the processing required for the allocation processing becomes complicated and the processing load becomes high.

The present invention has been made in view of the above circumstances, and is capable of executing group management control having high service performance with a low processing load, a group management control device for a double deck elevator, and a group management control for a double deck elevator. The purpose is to provide a method.

According to the embodiment for achieving the above object, the group management control device of the double deck elevator includes a virtual call information storage unit, an elevator group allocation pattern generation unit, an elevator group allocation pattern evaluation unit, and an allocation basket determination unit. The virtual call information storage unit stores the virtual call information generated by predicting the occurrence. The elevator group allocation pattern generator assigns the upper and lower cars of the double deck elevator to the landing call, and assigns only either the upper car or the lower car to the virtual call, and the landing call. And generate elevator group allocation pattern information showing the car allocation pattern of multiple double deck elevator groups for virtual calls. The elevator group allocation pattern evaluation unit calculates an evaluation value for each elevator group allocation pattern. The allocation car determination unit selects the optimum elevator group allocation pattern from the evaluation values and determines the car to be assigned to the landing call.

It is a block diagram of the double deck group management control system using the group management control device of the double deck elevator according to one embodiment. It is a flowchart which shows the operation which is executed when the landing call occurs in the group management control device of the double deck elevator by one Embodiment. It is a flowchart which shows the operation which is executed when the landing call occurs in the group management control device of the double deck elevator by one Embodiment. It is a figure which shows the example of the single-unit allocation pattern information generated by the group management control device of the double deck elevator by one Embodiment. It is a figure which shows the example of the elevator group allocation pattern information generated by the group management control device of the double deck elevator by one Embodiment. It is a figure which shows the example of the elevator group allocation pattern information generated by the group management control device of the double deck elevator by one Embodiment. It is a figure which shows the example of the elevator group allocation pattern information generated by the group management control device of the conventional single deck elevator. It is a figure which shows the example of the single-unit allocation pattern information generated by the group management control device of the conventional single deck elevator. It is a figure which shows the example of the single-unit allocation pattern information generated by the group management control device of the conventional double deck elevator.

In explaining the embodiment of the present invention, first, in a group management control system using a plurality of double deck elevators, a car allocation process executed when a landing call occurs will be described.

In the elevator group management control system, when a user registers a landing call at the landing, an allocation process is performed to determine a car (allocation car) that responds to the call so that the user can be transported most efficiently. The landing call that is the target for determining the allocation car in the allocation process is called an allocation request.

In the allocation process, first, the operation prediction process of each elevator is performed according to the operation schedule generated from the allocation request generated by the user's operation and the call already registered and assigned to the elevator. In the operation prediction process, a plurality of allocation patterns are assumed according to which car is provisionally allocated to the allocation request, and future operation is predicted for each allocation pattern. In this process, there are allocation patterns for the number of cars that can be allocated to the allocation request.

Next, the time required to respond to the allocation request is estimated for each allocation pattern, the evaluation value related to service performance is calculated, and the allocation request and the registered call can be responded to as soon as possible, that is, the evaluation is Choose the highest optimal allocation pattern. Then, the allocation is actually performed based on the information in the selected allocation pattern.

An example of how to evaluate each allocation pattern to determine an allocation car is the time from when each call is registered to when the car responds to the allocation request and the registered landing call on the departure floor of each call. Waiting time) is predicted from the result of the operation prediction, the sum of the waiting times of each call or the sum of the squares of the waiting times of each call is used as the evaluation value of the pattern, and the pattern with the minimum evaluation value is selected. There is a way to make the final allocation basket the car to which the allocation request was allocated in that pattern.

At that time, good group management performance can be maintained in the future by preparing several calls "virtual calls" that are expected to occur in the future and performing allocation processing using these. The virtual call is, for example, a call in the UP direction (the destination floor is the 7th floor), which is expected to occur on the 3rd floor 15 seconds after the allocation request is generated, and is assumed to occur on the 7th floor 30 seconds later. It is a call in the DOWN direction (the destination floor is the 3rd floor).

In the allocation process using virtual calls, it is assumed that there are multiple allocation patterns in which various baskets that are candidates for allocation are provisionally allocated to the allocation request and virtual call. Operation prediction is performed for each assumed allocation pattern, the time required for response is evaluated for the allocation request, virtual call, and registered call, and the best pattern as a whole is selected. Then, in the best pattern, the car assigned to the allocation request is determined as the car (allocation car) to be selected as a result of the allocation process.

Assuming that the number of cars is c and the number of virtual calls is n, the number of temporary allocation allocation patterns generated when an allocation request is generated and the allocation process is performed exists in c ^{(n + 1)} ways. For example, when an allocation request occurs in a group management system that manages three single-deck elevators (Elevator A, Elevator B, and Elevator C), an allocation pattern is created using two preset virtual calls. When generating information, there are 27 possible allocation patterns as shown in FIG. Here, each allocation pattern allocates different elevators to three calls, one allocation request and two virtual calls. For example, pattern No. 20 shows a pattern in which the elevator B is assigned to the allocation request, the elevator A is assigned to the virtual call (1), and the elevator C is assigned to the virtual call (2).

On the other hand, considering a group management control system using a double-deck elevator having an upper car and a lower car, even if the number of elevators is the same, the number of cars is doubled and the number of allocation patterns becomes very large. For example, in the case of three elevators and two virtual calls, c = 6 and n = 2, so 216 different allocation patterns are generated. This number is much larger than in the case of a single deck elevator, the processing required for the allocation processing becomes complicated, the processing load becomes high, and there is a possibility that the processing cannot be completed normally within a limited time.

In addition, when allocation processing is performed in the group management control system, when an allocation request occurs, the evaluation value related to the service performance of each single allocation pattern is first calculated for each elevator, and this is used to calculate the elevator group allocation pattern for the entire system. Distributed processing may be executed to calculate the evaluation value for each. In this case, there are eight single-deck allocation patterns generated for one elevator, for example, in the case of three single-deck elevators and two virtual calls, as shown in FIG.

On the other hand, in the case of three double deck elevators and two virtual calls, the single allocation pattern generated for one elevator considers that both the upper and lower baskets of each elevator can be assigned to the virtual calls. As shown in 7, there are 27 ways, which is significantly more than in the case of a single deck elevator. Therefore, when calculating the evaluation value for each elevator group allocation pattern of the entire system using the evaluation value for each single allocation pattern of each generated double deck elevator, the processing becomes complicated and the processing load becomes high. ..

An embodiment of the double-deck group management control system of the present invention will be described below on the premise that the allocation process for the landing call is executed in the group management control system of a general elevator as described above.

<Configuration of double deck group management control system using group management control device according to one embodiment>
The configuration of the double deck group management control system using the group management control device according to the embodiment of the present invention will be described with reference to FIG. The double deck group management control system 1 according to the present embodiment includes a plurality of double deck elevators (Unit A elevator 10A, Unit B elevator 10B, and Unit C elevator 10C) installed in an m-story building and each floor. It is equipped with a landing call registration device 20-1 to 20-m installed at the landing and a group management control device 30.

The Unit A elevator 10A has an upper car 11A, a lower car 12A, and a Unit A control device 13A. The Unit A control device 13A outputs position information, traveling status information, door opening / closing status information, load status information, etc. of the upper car 11A and the lower car 12A to the group management control device 30 as elevator information. Further, the Unit A control device 13A causes the Unit A elevator 10A to respond to the registration floor of the call by the allocation command from the group management control device 30, and opens the corresponding car.

Since the Unit B elevator 10B and the Unit C elevator 10C have the same configuration as the Unit A elevator 10A, detailed description thereof will be omitted.

The landing call registration devices 20-1 to 20-m are devices for registering landing calls for the landing user to specify the direction of the destination floor and call one of the cars 11A to 11C and 12A to 12C, respectively. Is. The landing call registration devices 20-1 to 20-m may be landing destination floor registration devices for inputting destination floors.

The group management control device 30 manages the group A, the B unit elevator 10B, and the C unit elevator 10C in a group. The group management control device 30 includes a landing call registration unit 31, a virtual call information storage unit 32, an elevator information acquisition unit 33, a single allocation pattern generation unit 34, a single allocation pattern evaluation unit 35, and an elevator group allocation pattern generation. It has a unit 36, an elevator group allocation pattern evaluation unit 37, an allocation basket determination unit 38, and an allocation information output unit 39.

The landing call registration unit 31 receives and registers the landing call information acquired from the landing call registration devices 20-1 to 20-m. The virtual call information storage unit 32 stores virtual call information generated in anticipation of future occurrence. The elevator information acquisition unit 33 acquires elevator information output from each of the control devices 13A to 13C.

The unit allocation pattern generation unit 34 is a unit that shows the vehicle allocation pattern for the landing call registered in the landing call registration unit 31 and the virtual call stored in the virtual call information storage unit 32 for each of the elevators 10A, 10B, and 10C. Generate allocation pattern information. At that time, the single allocation pattern generation unit 34 applies three ways to the landing call: when neither the upper car nor the lower car is assigned, when the upper car is assigned, and when the lower car is assigned. .. Further, the single allocation pattern generation unit 34 applies to the virtual call in two cases, that is, when neither the upper car nor the lower car is assigned, and when the upper car is assigned, or the upper car and the lower car. Two cases are applicable, one is when none of the cars are assigned and the other is when the lower car is assigned.

The unit allocation pattern evaluation unit 35 calculates an evaluation value regarding service performance for each unit allocation pattern of each of the elevators 10A, 10B, and 10C generated by the unit allocation pattern generation unit 34. The evaluation value calculated here is called a single evaluation value.

The elevator group allocation pattern generation unit 36 is a double deck elevator group (elevator A to C elevator 10C) for the landing call registered in the landing call registration unit 31 and the virtual call stored in the virtual call information storage unit 32. Generates elevator group allocation pattern information indicating the allocation pattern of the car. At that time, for the landing call, the upper car and the lower car of the double deck elevator group are assigned, and for the virtual call, only either the upper car or the lower car of the double deck elevator group is assigned. do.

The elevator group allocation pattern evaluation unit 37 evaluates the service performance for each elevator group allocation pattern generated by the elevator group allocation pattern generation unit 36 based on the unit evaluation value calculated by the unit allocation pattern evaluation unit 35. calculate. The evaluation value calculated here is called an elevator group evaluation value.

The allocation car determination unit 38 selects the optimum elevator group allocation pattern based on the elevator group evaluation value calculated by the elevator group allocation pattern evaluation unit 37, and allocates the car to the allocation request based on the selected elevator group allocation pattern. To decide.

The allocation information output unit 39 outputs an allocation command to the corresponding elevator based on the information of the allocation car determined by the allocation car determination unit 38.

<Operation of double deck group management control system according to one embodiment>
In the present embodiment, the single allocation pattern generation unit 34 allocates the upper and lower baskets of the elevators 10A, 10B, and 10C to the landing call, and the elevators 10A, 10B, and 10C to the virtual call. It is set to generate single allocation pattern information only for the lower car of 10C. Further, the elevator group allocation pattern generation unit 36 assigns the upper and lower cages of the elevators 10A, 10B, and 10C to the landing call, and lowers the elevators 10A, 10B, and 10C for the virtual call. Elevator group allocation pattern information is set to be generated only for the car.

Here, the allocation request is a call that actually occurs, and the assumption of the car that the user actually gets in changes depending on whether it is allocated to the upper car or the lower car. Therefore, the single allocation pattern generation unit 34 and the elevator group allocation pattern The generation unit 36 needs to generate the corresponding allocation pattern assuming both the case of allocating the upper car and the case of allocating the lower car to the allocation request.

Further, when the single allocation pattern generation unit 34 generates the single allocation pattern and when the elevator group allocation pattern generation unit 36 generates the elevator group allocation pattern, the car to be assigned to the virtual call is the lower car. The reason why it is only necessary is explained below.

As will be described later, the virtual call is set in advance by designating the timing of occurrence, the departure floor, and the destination floor, such as "occurs X seconds after the allocation request is generated, and is from the 3rd floor to the 7th floor row". The virtual call is predicted and evaluated assuming the situation where the call continues to occur even after the landing call that is the target of the allocation process is registered. It is set for the purpose of maintaining a situation where you can respond quickly over time. For example, if you want to improve the service performance of the departure reference floor used when entering and exiting the building and the service performance near the upper end of the building, you may set virtual calls on the departure reference floor and the upper floor.

If the allocation process is performed without using a virtual call, even if a good service can be provided for the call that exists at the time of the allocation request, it will not be possible to operate in consideration of the call that will occur later, so in the future. There is a possibility that the waiting time will be long for the landing call that occurs. Virtual calls are provided to avoid such situations.

Generally, when considering a virtual call with a floor other than the reference floor as the departure floor, for example, a virtual call from the 7th floor to the 3rd floor near the top floor, this virtual call is limited to the 7th floor and the call is expected to occur. Rather than being there, it is intended to be a wide position where calls occur on the upper floors. When the lower car is assigned to this virtual call, that is, the lower car responds to 7F and the upper car responds to 8F, and when the upper car is assigned, that is, the lower car responds to 6F and the upper car responds to 7F. In this state, the position is only shifted on the first floor, and the difference in the overall operation of the elevator in each case is small. Therefore, for this virtual call, it is sufficient to generate the corresponding allocation pattern only when the lower car is assigned.

Considering this way, in both cases where the virtual call is generated near the lower end and near the upper end, it is practically possible to temporarily allocate only one of the upper and lower cars (lower car in this embodiment). It turns out to be enough.

If the allocation target for the virtual call is set to the lower basket, it is necessary to set the departure floor and the destination floor of the virtual call so as to avoid the top floor. In addition, when the allocation target for the virtual call is set to the upper car, it is necessary to set the departure floor and the destination floor of the virtual call so as to avoid the lowest floor. This is the end of the explanation of the reason why the car to be assigned to the virtual call is limited to the lower car.

Further, in the present embodiment, the virtual call information storage unit 32 has a virtual call (1) in the UP direction (the destination floor is the 7th floor), which is expected to occur on the 3rd floor 15 seconds after the allocation request is generated. And, the virtual call (2) in the DOWN direction (the destination floor is the 3rd floor), which is expected to occur on the 7th floor after 30 seconds, is stored. The setting method of the virtual call will be described below.

The virtual call stored in the virtual call information storage unit 32 is basically set as a pair of the departure floor and the destination floor. In the double deck group management control, when a single allocation pattern or an elevator group allocation pattern is generated assuming that the virtual call is always assigned to the lower car, the response of the lower car to the departure floor of the virtual call and one of the departure floors of the virtual call. The time required is the same for the response of the upper car to the upper floor. For example, the allocation pattern that assigns the lower basket to the virtual call of "departure floor 3rd floor, destination floor 7th floor" is the upper basket to the call of "departure floor 4th floor, destination floor 8th floor", which is one floor above the virtual call. Works the same as the allocation pattern for assigning.

Only the allocation pattern with the lower car assigned to the virtual call is generated, and the allocation pattern with the upper car assigned is not generated because there is only one floor difference between the case where the lower car is assigned and the case where the upper car is assigned. This is because no big difference can be expected in the result of operation prediction.

On the other hand, it may be necessary to consider when there is a large demand only on a specific floor. The departure reference floor of the double deck elevator (the floor used when entering and exiting the building) will be a continuous second floor with the lower reference floor where the lower car responds and the upper reference floor where the upper car responds. If the elevator stops on the first floor off the departure reference floor, the number of extra stops will increase once and the operation efficiency will decrease. Therefore, services are often restricted so that such a response cannot be made.

When assigning a virtual call to the lower car to generate a single allocation pattern or an elevator group allocation pattern, set the departure floor of the virtual call to the lower reference floor, and when assigning it to the upper car to generate an allocation pattern, the departure of the virtual call. By setting the floor to the upper reference floor, it is possible to predict that the lower car will be located on the lower reference floor and the upper car will be located on the upper reference floor when answering a virtual call, and it is possible to predict the actual operation. Can be done.

When allocating a lower car to a virtual call to generate a single allocation pattern or an elevator group allocation pattern, it is basic that both the departure floor and the destination floor of the virtual call are the floors on which the lower car can be serviced. However, if the use of the lower car is restricted, such as when group management control is performed in the mode where only the upper car is serviced, a virtual call is set on the floor below the first floor of the upper car service floor, which is often used. As for the operation prediction, it is possible to make a provisional allocation to the lower car, but to make a prediction evaluation so that the upper car stops on the floor where the car is frequently used.

For example, even if the lower reference floor is not available, if the upper reference floor continues to serve, the operation forecast evaluation should be performed assuming that the lower car is assigned to the virtual call with the departure floor set to the lower reference floor. Then, the same operation prediction evaluation as the upper car responding to the upper reference floor can be performed. This is the end of the explanation of the virtual call setting method.

The operation executed by the double deck group management control system 1 with these information set in advance will be described with reference to the flowcharts of FIGS. 2A and 2B.

When a user performs a landing call registration operation with a landing call registration device for a landing on any floor in a building, for example, a landing call registration device 20-1 for a landing on the first floor, the landing call registration unit of the group management control device 30 The information of the landing call (assignment request) is registered in 31 (“YES” in S1). When the allocation request information is registered, the single allocation pattern generation unit 34 rides on the allocation request registered in the landing call registration unit 31 and the virtual call stored in the virtual call information storage unit 32 for each double deck elevator. Generates a single allocation pattern information indicating a car allocation pattern (S2).

At that time, the single allocation pattern generation unit 34 assigns the landing call to three ways: when it is not assigned to either the upper car or the lower car of each elevator, when it is assigned to the upper car, and when it is assigned to the lower car. Applicable. Further, the single allocation pattern generation unit 34 applies two ways to the virtual call, one is when neither the upper car nor the lower car is assigned to each elevator, and the other is when the lower car is assigned.

That is, as described above, the single unit allocation pattern generation unit 34 assigns only the lower car of each elevator to the landing call, and assigns only the lower car of each elevator to the virtual call. Generate allocation pattern information.

An example of the generated unit allocation pattern information is shown in FIG. As for the single allocation pattern generated here, if there are n virtual calls, 3 × 2 ⁿ are generated. Therefore, in the single allocation pattern information of FIG. 3, there are 12 virtual calls and 12 single allocation patterns. Has been generated. By generating the single allocation pattern in this way, the number of patterns is remarkable compared to the single allocation pattern (27 ways) in FIG. 7 generated by assuming that both the upper car and the lower car of each elevator can be assigned to the two virtual calls. It will be less.

Next, the unit allocation pattern evaluation unit 35 calculates an evaluation value regarding service performance for each unit allocation pattern of each double deck elevator generated by the unit allocation pattern generation unit 34.

First, the unit allocation pattern evaluation unit 35 has pattern No. 1 of the unit allocation pattern information generated for the unit A elevator 10A as an evaluation value calculation target, that is, all of the allocation request, the virtual call (1), and the virtual call (2). Processing is started for the pattern in which the Elevator 10A of Unit A is not assigned to.

The unit allocation pattern evaluation unit 35 determines whether or not a vehicle that cannot respond to the allocation request (a vehicle that cannot be allocated) is assigned in the unit allocation pattern (S3). Here, it is determined that a car that cannot respond to the allocation request has not been allocated (“NO” in S3), and the process proceeds to step S4. Further, in step S4, the unit allocation pattern evaluation unit 35 is assigned a car (a car that cannot be assigned) that cannot respond to any of the virtual calls in the unit allocation pattern, and makes the virtual call. Whether or not the upper car cannot respond even if it is moved upward on the first floor, that is, whether or not the upper car of the corresponding Unit A elevator 10A cannot be opened on the first floor upper floor of the virtual call floor. Judgment (S4).

Here, it is determined that the condition of step S4 is not applicable (“NO” in S4), and the unit allocation pattern evaluation unit 35 predicts the operation of the Unit A elevator 10A according to the unit allocation pattern, and each of them is based on the result. The departure floor response time (waiting time) and the like are calculated from the call generation time, and the unit evaluation value related to the service performance is calculated and stored (S5).

If it is determined in step S3 or step S4 that the condition is met (“YES” in S3 or “YES” in S4), the unit allocation pattern evaluation unit 35 does not calculate the unit evaluation value. It is memorized as (S6). At this time, in step S4, among the virtual calls, the single allocation pattern including any virtual call that satisfies the condition is excluded from the calculation target of the single evaluation value.

The unit allocation pattern evaluation unit 35 executes the processes of steps S3 to S6 for each elevator (loop (1)) and for each unit allocation pattern of the unit allocation pattern information (loop (2)).

Next, the elevator group allocation pattern generation unit 36 receives a double deck elevator group (elevator units A to C) for the landing call registered in the landing call registration unit 31 and the virtual call stored in the virtual call information storage unit 32. Elevator group allocation pattern information indicating the elevator car allocation pattern of the elevator 10C) is generated (S7).

At that time, the elevator group allocation pattern generation unit 36 targets the upper car and the lower car of the double deck elevator group for the landing call, and either of the lower car of the double deck elevator group for the virtual call. Only the basket is assigned.

Examples of the generated elevator group allocation pattern information are shown in FIGS. 4A and 4B. In FIGS. 4A and 4B, "Unit A single Pt" indicates a single allocation pattern No. adopted for the Unit A elevator 10A, and "Unit B single Pt" indicates a single allocation pattern No. adopted for the Unit B elevator 10B. "Unit C unit Pt" indicates the unit allocation pattern No. adopted for the unit C elevator 10C.

In the elevator group allocation pattern generated here, if the number of double deck elevators is e (2 x e cars) and the number of virtual calls is n, 2 x e ^{(n + 1)} are generated. Therefore, in the elevator group allocation pattern information of FIGS. 4A and 4B, there are three double deck elevators (six car cars) and two virtual calls, and 54 elevator group allocation patterns are generated. By generating the elevator group allocation pattern in this way, when there are three double deck elevators and two virtual calls, both the upper and lower car of each elevator can be assigned (216 ways). The number of patterns is significantly smaller than that.

Next, the elevator group allocation pattern evaluation unit 37 calculates an evaluation value regarding service performance for each elevator group allocation pattern generated by the elevator group allocation pattern generation unit 36. The elevator group allocation pattern evaluation unit 37 first starts processing the pattern No. 1 of the elevator group allocation pattern information as an evaluation value calculation target.

In the elevator group allocation pattern evaluation unit 37, as the single allocation pattern corresponding to the elevator group allocation pattern No. 1, the single allocation pattern of the unit A elevator 10A is No. 11 and the single allocation pattern of the unit B elevator 10B is No. It is .1 and it is specified that the single unit allocation pattern of the Unit C elevator 10C is No.1. Then, the elevator group allocation pattern evaluation unit 37 acquires the evaluation value stored in step S5 for each of the specified single allocation patterns (S8).

Here, the elevator group allocation pattern evaluation unit 37 includes a single allocation pattern determined in step S6 as not being subject to calculation of the single evaluation value in the single allocation pattern corresponding to the elevator group allocation pattern No.1. It is determined whether or not it is present (S9). Here, it is determined that the corresponding single allocation pattern is not included (“NO” in S9), and the process proceeds to step S10. In step S10, the elevator group allocation pattern evaluation unit 37 calculates and stores the elevator group evaluation value related to the service performance of the elevator group allocation pattern No. 1 (S10).

At this time, the elevator group allocation pattern evaluation unit 37 calculates the corresponding elevator group evaluation value by obtaining the sum of the unit evaluation values of each corresponding unit allocation pattern. By calculating the elevator group evaluation value in this way, it is possible to calculate the elevator group evaluation value by a simple process without performing operation prediction again for each elevator group allocation pattern.

In step S9, when it is determined that the unit allocation pattern determined to be out of the calculation target of the unit evaluation value is included (“YES” in S9), the elevator group allocation pattern evaluation unit 37 assigns the elevator group. It is determined that pattern No. 1 is not feasible and is not subject to calculation of the elevator group evaluation value (S11).

The elevator group allocation pattern evaluation unit 37 executes the processes of steps S9 to S11 for each elevator group allocation pattern (loop (3)).

As a result, for example, as shown in FIG. 4B, as the single allocation pattern corresponding to the elevator group allocation pattern No. 44, the single allocation pattern of the unit A elevator 10A is No. 3, and the single allocation pattern of the unit B elevator 10B is. It is No. 4, and by identifying that the unit allocation pattern of Unit C elevator 10C is No. 7 and calculating the sum of these unit evaluation values, the elevator group evaluation value of the elevator group allocation pattern No. 44 is obtained. Is calculated.

Next, the allocation car determination unit 38 selects the optimum elevator group allocation pattern from the elevator group evaluation values calculated by the elevator group allocation pattern evaluation unit 37, and makes a corresponding landing call based on the selected elevator group allocation pattern. The car to be assigned is determined (S12).

Then, the allocation information output unit 39 outputs an allocation command to the control device of the corresponding elevator based on the information of the allocation car for the allocation request determined by the allocation car determination unit 38 (S13). The control devices 13A to 13C control the devices in the elevators 10A to 10C so as to respond to the corresponding landing call based on the acquired allocation command.

According to the above embodiment, the group management control device of the double deck elevator can execute the group management control having high service performance with a low processing load.

In the above-described embodiment, the case where only the lower car of the elevators 10A to 10C is assigned to the virtual call in the single allocation pattern generation unit 34 and the elevator group allocation pattern generation unit 36 has been described, but only the upper car. The information of the corresponding allocation pattern may be generated for each allocation target.

Further, in the above-described embodiment, the virtual call stored in the virtual call information storage unit 32 may be set differently for each day of the week or time zone. In addition, there may be a day of the week or a time zone in which the virtual call is not set. Further, the virtual call is set in a range from the lower reference floor to which the lower car responds to the floor one floor below the top floor, for example, by executing a preset program by the group management control device 30. It may be automatically generated based on a rule or the like and set in the virtual call information storage unit 32.

Further, in the above-described embodiment, the case where the group management control device 30 executes the generation of the single unit allocation pattern and the calculation of the single unit evaluation value has been described, but these processes are executed by the control device of each elevator and acquired. The information may be transmitted to the group management control device.

Although some embodiments of the present invention have been described, 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 variations 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.

1 ... Double deck group management control system, 10A ... Unit A elevator, 10B ... Unit B elevator, 10C ... Unit C elevator, 11A, 11B, 11C ... Upper basket, 12A, 12B, 12C ... Lower basket, 13A, 13B, 13C ... control device, 20-1 to 20-m ... landing call registration device, 30 ... group management control device, 31 ... landing call registration unit, 32 ... virtual call information storage unit, 33 ... elevator information acquisition unit, 34 ... single allocation Pattern generation unit, 35 ... Single allocation pattern evaluation unit, 36 ... Elevator group allocation pattern generation unit, 37 ... Elevator group allocation pattern evaluation unit, 38 ... Allocation basket determination unit, 39 ... Allocation information output unit

Claims (5)

We manage a group of double deck elevators consisting of upper and lower cages installed in the building.
The landing call registration department that registers the information of the landing call registered by the user,
A virtual call information storage unit that stores virtual call information generated in anticipation of future occurrence,
For the landing call registered in the landing call registration unit, the upper and lower baskets of the plurality of double deck elevators are assigned, and for the virtual call stored in the virtual call information storage unit. , Elevator group allocation showing the allocation pattern of the cars of the plurality of double deck elevators to the landing call and the virtual call, targeting only one of the upper car or the lower car of the plurality of double deck elevators. Elevator group allocation pattern generator that generates pattern information,
An elevator group allocation pattern evaluation unit that calculates an evaluation value related to service performance for each elevator group allocation pattern generated by the elevator group allocation pattern generation unit.
With the allocation car determination unit that selects the optimum elevator group allocation pattern based on the evaluation value calculated by the elevator group allocation pattern evaluation unit and determines the vehicle to be assigned to the landing call based on the selected elevator group allocation pattern. A group management control device for double deck elevators, characterized by being equipped with. For the landing call registered in the landing call registration unit, three ways of assigning the upper car and the lower car, allocating the upper car, and allocating the lower car are applied. For virtual calls stored in the virtual call information storage unit, there are two cases, one is when neither the upper car nor the lower car is assigned, and the other is when the upper car is assigned, or the upper car and the lower car are applied. For each double deck elevator, a single unit that generates single allocation pattern information indicating the allocation pattern of the car for the landing call and the virtual call is applied to the case where neither of the above is assigned and the case where the lower car is assigned. Allocation pattern generator and
For each single allocation pattern of each double deck elevator generated by the single allocation pattern generation unit, a single allocation pattern evaluation unit for calculating an evaluation value related to service performance is further provided.
The double deck according to claim 1, wherein the elevator group allocation pattern evaluation unit calculates an evaluation value for each elevator group allocation pattern based on the evaluation value calculated by the single allocation pattern evaluation unit. Elevator group management control device. The unit allocation pattern evaluation unit
A single allocation pattern in which an unanswerable car is assigned to the landing call, and an upper car that cannot be answered when the upper car is assigned to the virtual call, and the virtual call is assigned to the first floor below the floor. A single allocation pattern that includes a virtual call in which the lower car of the corresponding double deck elevator cannot respond even if it is shifted, and when the lower car is assigned to the virtual call, the lower car that cannot respond is assigned and the virtual call is used. It is judged that the evaluation value is not calculated for the single allocation pattern including the virtual call that the upper car of the corresponding double deck elevator cannot answer even if the call is moved to the upper floor of the first floor.
The elevator group allocation pattern evaluation unit
The double deck elevator according to claim 2, wherein the elevator group allocation pattern including the single allocation pattern excluded from the calculation of the evaluation value by the single allocation pattern evaluation unit is determined to be out of the calculation target of the evaluation value. Group management controller. The building has a lower reference floor and an upper reference floor above the lower reference floor.
When the elevator group allocation pattern generation unit allocates the upper baskets of the plurality of double deck elevators to the virtual call, the virtual call information storage unit sets the upper reference floor as the departure floor or the destination floor. When the elevator group allocation pattern generation unit stores the information of the virtual call and assigns the lower baskets of the plurality of double deck elevators to the virtual call, the lower reference floor is set as the departure floor or the destination floor. The group management control device for a double deck elevator according to any one of claims 1 to 3, wherein the information of a virtual call is stored. A group management control device that manages multiple double-deck elevators consisting of upper and lower cages installed in the building
The landing call registration step to register the information of the landing call registered by the user, and
A virtual call information storage step that stores virtual call information generated in anticipation of future occurrence,
For the landing call registered in the landing call registration step, the upper car and the lower car of the plurality of double deck elevators are assigned, and for the virtual call stored in the virtual call information storage step. , Elevator group allocation showing the allocation pattern of the cars of the plurality of double deck elevators to the landing call and the virtual call, targeting only one of the upper car or the lower car of the plurality of double deck elevators. Elevator group allocation pattern generation step to generate pattern information,
An elevator group allocation pattern evaluation step for calculating an evaluation value regarding service performance for each elevator group allocation pattern generated in the elevator group allocation pattern generation step, and an elevator group allocation pattern evaluation step.
With the allocation car determination step, the optimum elevator group allocation pattern is selected based on the evaluation value calculated in the elevator group allocation pattern evaluation step, and the car to be assigned to the landing call is determined based on the selected elevator group allocation pattern. A group management control method for a double deck elevator characterized by having.

Images