JPWO2020100229A1 - Elevator group management device - Google Patents

Abstract

Provided is an elevator group management device capable of improving operation efficiency in an elevator system having a plurality of cages in which batteries are installed. The group management device (1) is a plurality of cars (5) based on the current operation plan and the remaining battery level of the plurality of cars (5) in which the batteries (7) are installed when a new landing call occurs. Of these, the judgment unit (14) that determines whether the car (5) with less battery level than the battery consumption until the provisionally updated operation plan is completed is service-disabled, and the car (5) that is not service-free. In addition, the difference calculation unit (15) and the difference calculation unit (15) calculate the difference between the battery consumption until the provisionally updated operation plan is completed and the battery consumption until the current operation plan is completed. A call allocation unit (16) that assigns a new landing call to any one of the non-serviceable cars (5) based on the calculated difference in battery consumption is provided.

Description

The present invention relates to an elevator group management device.

Patent Document 1 discloses an elevator system including a plurality of cars in which batteries are installed. The car battery is charged by a power supply device provided on the power supply floor. In the above system, when a new landing call is assigned to a car, if the battery level of the car is low, the allocation of an additional call to the car is prohibited. A car for which the assignment of additional calls is prohibited will perform power supply running after the service for the already assigned calls is completed.

Japanese Patent No. 5892757

In the system described in Patent Document 1, a new call may be assigned to a car having a relatively large battery consumption among a plurality of cars, depending on the call allocation method. In this case, since the frequency of power supply running increases, the operating efficiency of the elevator decreases.

The present invention has been made to solve the above problems. An object of the present invention is to provide an elevator group management device capable of improving the operation efficiency in an elevator system having a plurality of cages in which batteries are installed.

The group management device for elevators according to the present invention has a plurality of cars based on the current operation plan and the remaining battery level of the plurality of cars in which rechargeable batteries are installed on the power supply floor when a new landing call occurs. Of these, a judgment unit that determines whether the car with less battery power than the battery consumption until the provisionally updated operation plan including the service for calling a new landing is completed, and each car that is not serviceable In addition, the difference calculation unit that calculates the difference between the battery consumption until the provisionally updated operation plan including the service for calling a new landing is completed and the battery consumption until the current operation plan is completed, and the difference A call allocation unit that assigns a new landing call to any one of the non-serviceable cars based on the difference in battery consumption calculated by the calculation unit is provided.

According to the present invention, a new landing call is assigned to any one of the non-serviceable cars based on the difference in battery consumption calculated by the difference calculation unit. Therefore, it is possible to improve the operation efficiency in an elevator system provided with a plurality of cars in which batteries are installed.

It is a block diagram of the elevator system in Embodiment 1. FIG. It is a block diagram of the group management apparatus in Embodiment 1. FIG. It is a sequence diagram which shows an example of the whole processing of the group management apparatus in Embodiment 1. FIG. It is a flowchart which shows the operation example of the determination part in Embodiment 1. It is a flowchart which shows the operation example of the difference calculation part in Embodiment 1. It is a flowchart which shows the operation example of the call allocation part in Embodiment 1. It is a block diagram of the group management apparatus in Embodiment 2. FIG. It is a sequence diagram which shows an example of the whole processing of the group management apparatus in Embodiment 2. It is a flowchart which shows the operation example of the determination part in Embodiment 2. It is a flowchart which shows the operation example of the waiting time calculation part in Embodiment 2. It is a flowchart which shows the operation example of the call allocation part in Embodiment 2. It is a hardware configuration diagram of a group management device.

Hereinafter, embodiments will be described with reference to the accompanying drawings. In each figure, the same or corresponding parts are designated by the same reference numerals. Overlapping description will be simplified or omitted as appropriate.

Embodiment 1.
FIG. 1 is a configuration diagram of an elevator system according to the first embodiment.

The elevator system includes a group management device 1, a plurality of car control devices 2, and a plurality of call registration devices 3. The call registration device 3 is installed in, for example, an elevator hall or an entrance gate on each floor. The group management device 1 is electrically connected to the car control device 2 and the call registration device 3.

In FIG. 1, only one car control device 2 is shown. The individual car control device 2 controls the operation of each elevator.

Each elevator comprises, for example, a hoist 4, a car 5, and a counterweight 6. The car 5 and the balance weight 6 are provided inside the hoistway. The car 5 and the balance weight 6 are suspended in the hoistway by a rope wound around the hoisting machine 4. The car 5 and the balance weight 6 are moved up and down by being driven by the hoisting machine 4. The hoisting machine 4 is controlled by the corresponding car control device 2.

The call registration device 3 accepts the input of the call registration information by the passenger. The call registration information includes, for example, the destination floor or the destination direction. The call registration device 3 includes, for example, an operation unit such as a button or a sensor that recognizes information by wireless communication. Passengers may input call registration information by operating the operation unit of the call registration device 3. The passenger may input the call registration information by having the sensor of the call registration device 3 read the call registration information transmitted from the ID tag, the ID card, the mobile terminal, or the like.

The call registration device 3 generates a landing call based on the input call registration information. The landing call includes, for example, the departure floor and the destination floor. The landing call may include, for example, the destination direction instead of the destination floor. The call registration device 3 transmits the generated landing call to the group management device 1.

The group management device 1 selects one assigned car for the landing call received from the call registration device 3. The group management device 1 transmits the landing call to the car control device 2 corresponding to the assigned car.

The car control device 2 outputs a drive command to the hoisting machine 4 based on the landing call received from the group management device 1. When the hoisting machine 4 is driven, the car 5 moves in the vertical direction and responds to the landing call.

A battery 7 and a power receiving device 8 are installed in the car 5. At least one power transmission device 9 is installed in the hoistway. The power transmission device 9 is connected to the power source 10. The floor on which the power transmission device 9 is installed is also called the "power supply floor".

The battery 7 supplies the electric power required to operate the equipment provided in the car 5. The battery 7 supplies electric power to, for example, a door opening / closing device for a car door, a lighting device, and the like. Since the battery 7 is consumed as the car 5 operates, it is charged as needed. The battery 7 can be charged on the power supply floor.

The power receiving device 8 faces the power transmitting device 9 in a state where the car 5 is stopped on the power feeding floor. The power transmitting device 9 transmits power to, for example, the opposing power receiving device 8 in a non-contact manner. The power receiving device 8 charges the battery 7 with the electric power received from the power transmitting device 9.

The group management device 1 determines whether or not power is to be supplied to the battery 7 based on, for example, a landing call or the remaining battery level of each car 5. The group management device 1 instructs the car control device 2 to run the power supply as needed. The power supply running is to move the car 5 to the power supply floor.

FIG. 2 is a configuration diagram of the group management device according to the first embodiment.

The group management device 1 includes a call acquisition unit 11, an operation plan acquisition unit 12, a battery remaining amount acquisition unit 13, a determination unit 14, a difference calculation unit 15, and a call allocation unit 16.

The call acquisition unit 11 acquires a landing call from the call registration device 3. The call acquisition unit 11 transmits the landing call to the determination unit 14.

The operation plan acquisition unit 12 acquires the current operation plan of each car 5 from the plurality of car control devices 2. The operation plan of the car 5 includes, for example, information indicating the current position of the car 5 and the planned stop floor. The operation plan acquisition unit 12 transmits the current operation plan of each car 5 to the determination unit 14.

The current position of the car 5 is represented, for example, as the floor of the building. The current position of the car 5 can also be expressed as a position between floors, for example, "between the first floor and the second floor".

For example, when the hoisting machine 4 or the like includes a motor encoder, the relative position of the car detected by using the motor encoder may be set as the current position of the car 5.

For example, when the car 5 or the car control device 2 is provided with a distance sensor using a laser, the absolute distance from the car 5 to the top or bottom of the hoistway may be the current position of the car 5.

For example, if a magnetic tape or bar code tape is installed in the hoistway and the car 5 or car control device 2 is equipped with a sensor that reads the tape, the absolute of the car 5 measured using the sensor. The position may be the current position of the car 5.

The battery remaining amount acquisition unit 13 acquires the current battery remaining amount of each car 5 from the plurality of car control devices 2. The battery remaining amount acquisition unit 13 transmits the current battery remaining amount of each car 5 to the determination unit 14.

The remaining battery level can be obtained from, for example, the voltage value of the battery 7. The remaining battery level may be estimated based on, for example, the elapsed time from the time when the battery 7 was last charged, the number of times the car door is opened and closed, and the like.

The determination unit 14 acquires a new landing call from the call acquisition unit 11. The determination unit 14 receives the current operation plan of each car 5 from the operation plan acquisition unit 12. The determination unit 14 receives the current remaining battery level of each car 5 from the battery level remaining amount acquisition unit 13.

The determination unit 14 temporarily updates the operation plan of each car 5, including the service for calling a new landing. Temporary renewal is to renew the operation plan on the assumption that a new landing call has been assigned to the car 5. In the tentatively updated operation plan, for example, the departure floor and the destination floor included in the new landing call are added to the current operation plan as new scheduled stop floors.

For example, if both the departure floor and the destination floor included in the new landing call are within the movement range of the car 5 in the current operation plan, in the provisionally updated operation plan, the service to the existing other call is used. The service to the new landing call can be completed first. For example, if at least one of the departure floor and the destination floor included in the new landing call is outside the movement range of the car 5 in the current operation plan, the service to the existing other call is provided in the temporarily updated operation plan. The service to the new landing call may be completed later than.

If the new landing call does not include the destination floor but includes the destination direction, the determination unit 14 temporarily updates the operation plan based on the destination floor estimated from the past results. For example, it is possible to probabilistically estimate the destination floor of a passenger who has registered a new landing call based on the past cumulative number of passengers getting off the train stored by time zone and floor. For example, when the car 5 is equipped with a load weight measuring device, the number of people getting off the vehicle can be estimated from the amount of decrease in the measurement result by the device. For example, when a camera is provided in the car 5 or the elevator hall, the number of people getting off the vehicle may be measured directly from the image taken by the camera.

The determination unit 14 calculates the battery consumption for each car 5 until the provisionally updated operation plan is completed. The battery consumption is also referred to as "battery consumption after provisional update". The battery consumption is calculated based on, for example, the time required to complete the provisionally updated operation plan and the number of times the car door is opened and closed. The number of times the door is opened and closed can be estimated from, for example, the number of times the car 5 is stopped in the operation plan.

The determination unit 14 determines whether or not the service is possible for each car 5. The determination unit 14 determines that the car 5 whose current battery level is less than the battery consumption until the provisionally updated operation plan is completed is a "non-service car". The non-service car is a car 5 in which the battery level becomes zero before the operation plan is completed when a new landing call is assigned.

The determination unit 14 determines whether or not power supply is necessary for each car 5. The determination unit 14 determines that the car 5 in which the remaining battery level at the completion of the provisionally updated operation plan is smaller than the threshold value is the "power supply required car". The power supply required car is a car 5 that needs to charge the battery 7 on the power supply floor after the operation plan is completed when a new landing call is assigned.

The above threshold value used for determining the necessity of power supply is, for example, every 5 cars based on the battery consumption in the power supply running for moving from the floor located at the completion of the provisionally updated operation plan to the nearest power supply floor. Is set to. The battery consumption is calculated for each car 5 based on, for example, the time required for the power supply running and the number of times the car door is opened and closed during the power supply running. The determination unit 14 holds in advance the power supply floor position information that specifies the position of the power supply floor.

The determination unit 14 transmits at least information indicating a car that cannot be serviced and information indicating a car requiring power supply to the call allocation unit 16. The determination unit 14 transmits at least information indicating an unserviceable car to the difference calculation unit 15.

The difference calculation unit 15 may, for example, from the determination unit 14, call a new landing, provide information indicating a non-service car, the current operation plan of all the cars 5 except the non-service car, and all the cars 5 excluding the non-service car. Receives battery consumption until the provisionally updated operation plan for is completed.

The difference calculation unit 15 may directly receive the new landing call from the call acquisition unit 11. Further, instead of receiving the current operation plans of all the cars 5 except the non-serviceable car from the determination unit 14, the difference calculation unit 15 acquires the current operation plans of all the cars 5 including the non-serviceable car. It may be received from the unit 12.

The difference calculation unit 15 calculates the battery consumption until the current operation plan is completed for each car 5 that is not a non-service car. The battery consumption is also referred to as "battery consumption before provisional update". The battery consumption is calculated based on, for example, the time required to complete the current operation plan and the number of times the car door is opened and closed. The battery consumption of the car 5 to which the call is not currently assigned may be replaced by the value of the battery consumption calculated for the latest call for which the service has already been completed.

The difference calculation unit 15 calculates the difference between the battery consumption until the provisionally updated operation plan is completed and the battery consumption until the current operation plan is completed for each car 5 that is not a non-serviceable car. That is, the difference calculation unit 15 calculates the difference in battery consumption in the operation plan before and after the provisional update.

The difference calculation unit 15 calls and transmits information indicating the difference in battery consumption for all the cars 5 except the non-serviceable car to the allocation unit 16.

The call allocation unit 16 receives, for example, from the determination unit 14, information indicating a new landing call, a car that cannot be serviced, and information indicating a car requiring power supply. The call allocation unit 16 receives information from the difference calculation unit 15 indicating the difference in battery consumption for all the cars 5 except the non-serviceable car.

The call allocation unit 16 may directly receive the new landing call from the call acquisition unit 11.

The call allocation unit 16 allocates a new landing call to any one of the non-serviceable cars 5 based on the difference in battery consumption calculated by the difference calculation unit 15.

The call allocation unit 16 determines, for example, the car 5 having the smallest difference in battery consumption as the allocation car.

The call allocation unit 16 transmits a new landing call to the car control device 2 corresponding to the car 5 determined as the allocation car.

When the car 5 determined as the allocation car is a car requiring power supply, the call allocation unit 16 actually updates the operation of the car control device 2 corresponding to the car 5 including the service for calling a new landing. After the completion of the plan, the car 5 is instructed to carry out the power supply running.

FIG. 3 is a sequence diagram showing an example of the overall processing of the group management device according to the first embodiment. FIG. 3 shows the above-mentioned information transmitted and received by each part of the group management device 1.

FIG. 4 is a flowchart showing an operation example of the determination unit according to the first embodiment.

In step S101, a new landing is called, the operation plan of each car 5 and the remaining battery level of each car 5 are received.

The processes from step S102 to step S107 are repeated for all the cars 5 managed by the group management device 1.

In step S102, the operation plan is provisionally updated.

In step S103, the battery consumption after the provisional update is calculated based on the provisionally updated operation plan.

In step S104, it is determined whether or not the current remaining battery level is less than the battery consumption after the provisional update. That is, it is determined whether or not a new landing call can be assigned to the target car 5.

If it is determined in step S104 that the current remaining battery level is less than the battery consumption after the provisional update, step S105 is performed.

In step S105, the target car 5 is classified as a non-service car.

If it is determined in step S104 that the current remaining battery level is not less than the battery consumption after the provisional update, step S106 is performed.

In step S106, it is determined whether or not the remaining battery level at the completion of the provisionally updated operation plan is smaller than the threshold value. That is, it is determined whether or not it is necessary to charge the battery 7 of the target car 5 after the provisionally updated operation plan is completed.

If it is determined in step S106 that the remaining battery level at the completion of the provisionally updated operation plan is smaller than the threshold value, step S107 is executed.

In step S107, the target car 5 is classified as a power supply required car.

If it is determined in step S106 that the remaining battery level at the completion of the provisionally updated operation plan is not smaller than the threshold value, the target car 5 is not classified as a non-service car or a power supply required car.

When the processes from step S102 to step S107 are completed for all the cars 5, step S108 is executed.

In step S108, information on the car that cannot be serviced and the car that requires power supply is transmitted to the call allocation unit.

In step S109, information on the non-serviceable car is transmitted to the difference calculation unit.

FIG. 5 is a flowchart showing an operation example of the difference calculation unit according to the first embodiment.

In step S201, a new landing call, information on the non-service car, the operation plan of all the cars 5 except the non-service car, and the provisionally updated battery consumption of all the cars 5 except the non-service car are received.

The processes of steps S202 and S203 are repeated for all the cars 5 except the non-serviceable car.

In step S202, the battery consumption before the provisional update is calculated.

In step S203, the difference in battery consumption before and after the temporary update is calculated.

When the processes of steps S202 and S203 are completed for all the cars 5 except the non-serviceable car, step S204 is executed.

In step S204, the battery consumption difference of each car 5 excluding the non-service car is transmitted to the call allocation unit 16.

FIG. 6 is a flowchart showing an operation example of the call allocation unit according to the first embodiment.

In step S301, a new landing call, information on the non-service car, information on the car requiring power supply, and the difference in battery consumption of each car 5 excluding the non-service car are received.

In step S302, the car 5 having the smallest battery consumption difference among the non-serviceable cars 5 is determined as the allocation car.

In step S303, a new landing call is transmitted to the car control device 2 corresponding to the assigned car. As a result, the operation plan of the allocated car is actually updated as the content including the service for calling a new landing.

In step S304, it is determined whether or not the assigned car is a power supply required car.

If it is determined in step S304 that the assigned car is a power supply required car, step S305 is carried out.

In step S305, the car control device 2 corresponding to the assigned car is instructed to carry out power feeding after the operation plan is completed.

If it is determined in step S304 that the assigned car is not a power supply required car, step S305 is not performed.

According to the first embodiment described above, the determination unit 14 has the current operation plan of each of the plurality of cars 5 in which the rechargeable battery 7 is installed on the power supply floor when a new landing call occurs. Based on the remaining battery level, the car 5 with less battery level than the battery consumption until the provisionally updated operation plan including the service for calling a new landing is completed among the multiple car 5s cannot be serviced. judge. The difference calculation unit 15 does not include the battery consumption until the provisionally updated operation plan is completed including the service for the new landing call and the service for the new landing call for each non-serviceable car 5. Calculate the difference from the battery consumption until the operation plan is completed. The call allocation unit 16 allocates a new landing call to any one of the non-serviceable cars 5 based on the difference in battery consumption for each non-serviceable car 5 calculated by the difference calculation unit 15. That is, according to the first embodiment, the allocation car is determined based on the simulation result of the battery consumption when the new landing call is assigned to the car 5 and when it is not assigned. Therefore, it is possible to improve the operation efficiency in the elevator system provided with the plurality of cars 5 in which the battery 7 is installed.

Further, the call allocation unit 16 allocates a new landing call to, for example, the car 5 which has the smallest difference in battery consumption among the cars 5 which are not non-serviceable cars. In this case, when a new landing call is generated, the new landing call is preferentially assigned to the car 5 having the smallest increase in battery consumption, so that the number of times of power supply running is minimized. As a result, the operation efficiency can be improved.

In addition, the determination unit 14 determines the battery consumption in the power supply running for moving from the floor located at the completion of the temporarily updated operation plan including the service for calling a new landing among the plurality of cars 5 to the power supply floor. The car 5 in which the remaining battery level at the completion of the temporarily updated operation plan is smaller than the threshold value based on the threshold value is determined as to whether the power supply is required. When a new landing call is assigned to a car requiring power supply, the call allocation unit 16 causes the car to carry out power supply running after the actual updated operation plan including the service for the new landing call is completed. Instruct the car control device 2 corresponding to the car. Therefore, it is possible to reliably supply power to the battery 7 whose remaining amount is low without performing unnecessary power supply running.

Further, the determination unit 14 calculates the battery consumption in the power supply running for each car 5 based on, for example, the time required for the power supply running and the number of times the car door opens and closes during the power supply running. In this case, the battery consumption due to the operation of the door opening / closing device and the lighting device of the car 5 can be calculated.

Further, the difference calculation unit 15 determines the current operation plan based on, for example, the time required to complete the current operation plan and the number of times the car door opens and closes in the current operation plan for each car 5 that is not a non-serviceable car. Calculate the battery consumption until the completion of. In this case, the battery consumption due to the operation of the door opening / closing device and the lighting device of the car 5 can be calculated.

Further, for example, when the new landing call indicates the departure floor and the destination direction and does not indicate the destination floor, the determination unit 14 makes a new landing call based on the past cumulative number of passengers getting off by time zone and floor. The destination floor of the registered passengers is estimated, and the operation plans of the plurality of cars 5 are provisionally updated to include the service for calling a new landing based on the departure floor and the estimated destination floor. In this case, even if the call registration device 3 does not have the function of accepting the input of the target floor, it is possible to calculate the difference in battery consumption.

Embodiment 2.
Hereinafter, the second embodiment will be described. The description overlapping with the first embodiment will be omitted as appropriate.

FIG. 7 is a configuration diagram of the group management device according to the second embodiment.

The group management device 1 according to the second embodiment includes a waiting time calculation unit 17 in addition to the configuration according to the first embodiment.

In the second embodiment, the determination unit 14 transmits at least information indicating a non-serviceable car to the difference calculation unit 15 and the waiting time calculation unit 17.

The waiting time calculation unit 17 receives, for example, from the determination unit 14, information indicating a new landing call, a non-service car, and the current operation plan of all the cars 5 except the non-service car.

The waiting time calculation unit 17 may directly receive the new landing call from the call acquisition unit 11. Further, the waiting time calculation unit 17 receives the current operation plans of all the cars 5 except the non-serviceable car from the determination unit 14, but instead plans the current operation plans of all the cars 5 including the non-serviceable car. It may be received from the acquisition unit 12.

The waiting time calculation unit 17 provisionally updates the operation plans of all the cars 5 except the non-serviceable cars in the same manner as the determination unit 14, for example. Instead of temporarily updating the operation plan, the waiting time calculation unit 17 may receive information indicating the temporarily updated operation plan from the determination unit 14.

The waiting time calculation unit 17 calculates the waiting time of a passenger who has registered a new landing call in the temporarily updated operation plan for each car 5 that is not a non-service car. The waiting time corresponds to the elapsed time from the time when the new landing call is registered to the time when the car 5 arrives at the floor where the new landing call is registered in the tentatively updated operation plan.

The waiting time calculation unit 17 calls and transmits information indicating the waiting time for all the cars 5 except the non-serviceable car to the allocation unit 16.

In the second embodiment, the call allocation unit 16 receives information indicating the waiting time for all the cars 5 except the non-serviceable car from the waiting time calculation unit 17.

In the second embodiment, the call allocation unit 16 is one of the non-serviceable car 5 based on the battery consumption difference calculated by the difference calculation unit 15 and the waiting time calculated by the waiting time calculation unit 17. Assign a new landing call to one.

In the second embodiment, the call allocation unit 16 calculates, for example, an evaluation value VAL for each car 5 that is not a non-serviceable car, and determines the car 5 having the minimum evaluation value VAL as the allocation car. The evaluation value VAL is calculated by the following formula using the battery consumption difference BC, the waiting time WT, the first coefficient α and the second coefficient β. The first coefficient α and the second coefficient β may be set in advance, for example, α = 0.7 and β = 0.3.
VAL = α × BC + β × WT

In the second embodiment, for example, the nominal allocation unit 16 reduces the ratio of the first coefficient α to the second coefficient β in order to lower the priority of the battery consumption as the remaining battery level increases. The 1st coefficient and the 2nd coefficient may be dynamically determined. For example, the nominal allocation unit 16 has the first coefficient and the second coefficient so that the ratio of the first coefficient α to the second coefficient β becomes larger in order to raise the priority of the battery consumption as the remaining battery level becomes smaller. The coefficient may be determined dynamically.

FIG. 8 is a sequence diagram showing an example of the overall processing of the group management device according to the second embodiment. FIG. 8 shows the above-mentioned information transmitted and received by each part of the group management device 1.

FIG. 9 is a flowchart showing an operation example of the determination unit according to the second embodiment.

Steps S401 to S408 are the same as steps S101 to S108 in FIG.

In step S409, information on the non-serviceable car is transmitted to the difference calculation unit 15 and the waiting time calculation unit 17.

FIG. 10 is a flowchart showing an operation example of the waiting time calculation unit according to the second embodiment.

In step S501, a new landing call is received, information on the non-service car and the operation plan of all the cars 5 except the non-service car are received.

The process of step S502 is repeated for all the cars 5 except the non-service car.

In step S502, the waiting time is calculated based on the operation plan after the provisional update.

When the processing of step S502 is completed for all the cars 5 except the non-service car, step S503 is executed.

In step S503, the waiting time of each car 5 excluding the non-service car is transmitted to the call allocation unit 16.

FIG. 11 is a flowchart showing an operation example of the call allocation unit according to the second embodiment.

In step S601, new landing call, information on non-serviceable car, information on power-required car, battery consumption difference of each car 5 excluding non-serviceable car, and waiting time of each car 5 excluding non-serviceable car are received. ..

In step S602, the car 5 having the smallest evaluation value based on the difference in battery consumption and the waiting time among the non-serviceable cars 5 is determined as the allocation car.

Steps S603 to S605 are the same as steps S303 to S305 in FIG.

According to the second embodiment described above, the waiting time calculation unit 17 provisionally updates, for example, for each car 5 that is not a non-serviceable car, including a service from the time when the new landing call is registered to the new landing call. The waiting time, which is the elapsed time until the time when the car 5 arrives at the floor where the new landing call is registered in the completed operation plan, is calculated. The call allocation unit 16 evaluates the sum of the value obtained by multiplying the difference in battery consumption by the first coefficient and the value obtained by multiplying the waiting time by the second coefficient for each car 5 that is not a non-service car. It is calculated as a value, and a new landing call is assigned to the car 5 having the smallest evaluation value among the cars 5 that are not non-serviceable. In this case, when a new landing call occurs, the allocation car is determined in consideration of the increase in battery consumption and the waiting time. As a result, it is possible to improve the operation efficiency while suppressing the decrease in passenger convenience.

Further, the nominal allocation unit 16 sets the first coefficient and the second coefficient so that, for example, the ratio of the first coefficient to the second coefficient increases as the remaining battery level decreases. In this case, the priority of the battery consumption can be dynamically determined according to the remaining battery level.

Further, the waiting time calculation unit 17 may calculate, for example, the difference before and after the provisional update for the total value of the waiting times of all passengers corresponding to the new landing call and the existing landing call. The waiting time calculation unit 17 may, for example, transmit information indicating the difference for all the cars 5 except the non-serviceable car to the calling allocation unit 16 instead of the waiting time WT. For example, the call allocation unit 16 may calculate the evaluation value VAL using the difference for each car 5 that is not a non-serviceable car, and determine the car 5 having the minimum evaluation value VAL as the allocation car. In this case, the overall waiting time of the plurality of elevators can be optimized.

FIG. 12 is a hardware configuration diagram of the group management device.

Each function of the call acquisition unit 11, the operation plan acquisition unit 12, the battery remaining amount acquisition unit 13, the determination unit 14, the difference calculation unit 15, the call allocation unit 16, and the waiting time calculation unit 17 in the group management device 1 is performed by a processing circuit. It will be realized. The processing circuit may be dedicated hardware 50. The processing circuit may include a processor 51 and a memory 52. The processing circuit is partially formed as dedicated hardware 50, and may further include a processor 51 and a memory 52. FIG. 12 shows an example in which a processing circuit is partially formed as dedicated hardware 50 and includes a processor 51 and a memory 52.

If at least a portion of the processing circuit is at least one dedicated hardware 50, the processing circuit may include, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or any of these. The combination is applicable.

When the processing circuit includes at least one processor 51 and at least one memory 52, each function of the group management device 1 is realized by software, firmware, or a combination of software and firmware. The software and firmware are written as programs and stored in the memory 52. The processor 51 realizes the functions of each part by reading and executing the program stored in the memory 52. The processor 51 is also referred to as a CPU (Central Processing Unit), a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a DSP. The memory 52 corresponds to, for example, a non-volatile or volatile semiconductor memory such as a RAM, ROM, flash memory, EPROM, or EEPROM, a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a DVD, or the like.

In this way, the processing circuit can realize each function of the group management device 1 by hardware, software, firmware, or a combination thereof. Each function of the car control device 2 and the call registration device 3 is also realized by the same processing circuit as the processing circuit shown in FIG.

As described above, the present invention can be applied to an elevator system having a plurality of cages in which batteries are installed.

1 Group management device 2 Car control device 3 Call registration device 4 Hoisting machine 5 Car 6 Balance weight 7 Battery 8 Power receiving device 9 Power transmission device 10 Power supply 11 Call acquisition unit 12 Operation plan acquisition unit 13 Battery remaining amount acquisition unit 14 Judgment unit 15 Difference calculation unit 16 Call allocation unit 17 Waiting time calculation unit 50 Dedicated hardware 51 Processor 52 Memory

Claims (8)

In the event of a new landing call, including the service to the new landing call among multiple cars based on the current operation plan and battery level of the cars with rechargeable batteries installed on the power supply floor. A judgment unit that determines whether the car with less battery power than the battery consumption until the provisionally updated operation plan is completed is not serviceable.
For each non-serviceable car, calculate the difference between the battery consumption until the provisionally updated operation plan is completed, including the service to the new landing call, and the battery consumption until the current operation plan is completed. Difference calculation unit and
A call allocation unit that assigns the new landing call to any one of the non-serviceable cars based on the difference in battery consumption calculated by the difference calculation unit.
Elevator group management device equipped with. The elevator group management device according to claim 1, wherein the call allocation unit allocates the new landing call to a car that minimizes the difference in battery consumption among the cars that are not non-serviceable cars. For each non-serviceable car, the time when the car arrives at the floor where the new landing call is registered in the provisionally updated operation plan including the service to the new landing call from the time when the new landing call is registered. Waiting time calculation unit, which calculates the waiting time, which is the elapsed time until
Further prepare
The call allocation unit evaluates the sum of the value obtained by multiplying the difference in battery consumption by the first coefficient and the value obtained by multiplying the waiting time by the second coefficient for each non-serviceable car. The group management device for an elevator according to claim 1, wherein the new landing call is assigned to the car having the smallest evaluation value among the cars that are not non-serviceable cars. The group management of elevators according to claim 3, wherein the nominal allocation unit sets the first coefficient and the second coefficient so that the ratio of the first coefficient to the second coefficient increases as the remaining battery level decreases. apparatus. The determination unit is a threshold value based on the battery consumption in the power supply running for moving from the floor located at the completion of the temporarily updated operation plan including the service to the new landing call among the plurality of cars to the power supply floor. Judge the car as the power supply required car when the remaining battery level becomes smaller when the temporarily updated operation plan is completed
When the new landing call is assigned to the power supply-requiring car, the call allocation unit causes the car to carry out power supply running after the completion of the updated operation plan including the service for the new landing call. The group management device for an elevator according to any one of claims 1 to 4, which is instructed to a car control device corresponding to the car. The group management device for an elevator according to claim 5, wherein the determination unit calculates the battery consumption in the power supply running for each car based on the time required for the power supply running and the number of times the car door is opened and closed during the power supply running. The difference calculation unit completes the current operation plan based on the time required to complete the current operation plan and the number of times the car door opens and closes in the current operation plan for each non-serviceable car. The group management device for an elevator according to any one of claims 1 to 6, which calculates the battery consumption. When the new landing call indicates the departure floor and the destination direction and does not indicate the destination floor, the determination unit registers the new landing call based on the past cumulative number of people getting off the vehicle stored by time zone and floor. Claims 1 to 7 that estimate the destination floor of a passenger and provisionally update the operation plans of a plurality of cars based on the departure floor and the estimated destination floor to the contents including the service to the new landing call. The elevator group management device according to any one of the above items.

Images