WO2017090179A1

WO2017090179A1 - Elevator group management control device and group management control method

Info

Publication number: WO2017090179A1
Application number: PCT/JP2015/083391
Authority: WO
Inventors: 健二谷山
Original assignee: 三菱電機株式会社
Priority date: 2015-11-27
Filing date: 2015-11-27
Publication date: 2017-06-01
Also published as: JPWO2017090179A1; CN108349684B; CN108349684A; JP6567074B2

Abstract

Provided is an elevator group management control device that, without requiring personal authentication to be carried out, eliminates mixed riding in which users having different attributes ride together and makes it possible to inhibit a user from moving to a floor on which said user is not allowed. When a destination floor is registered by a destination floor registration device installed at the elevator landing of an entrance floor that is a floor to which the entry/exit of a building is provided, an attribute of the floor that is the destination floor is identified as an attribute of a user. When a destination floor or an elevator landing call is registered by a destination floor registration device or an elevator landing call registration device installed at the elevator landing of a floor other than the entrance floor, an attribute of the floor that is a floor other than the entrance floor and that has the destination floor registration device or the elevator landing call registration device installed thereon is identified as an attribute of the user. The attribute of an identified user is used as a basis to allocate a car to the user.

Description

Elevator group management control device and group management control method

The present invention relates to an elevator group management control device and a group management control method for managing a plurality of elevators as a group.

Conventionally, an elevator control device that selects a destination floor registered by the landing destination floor registration device and a hall call information to which the hall call information including the registration floor is assigned, and responds to the registration floor as the assigned floor, and an elevator user. An assignment changing means for changing the assignment of the unit on which the user gets to another unit when a user having a different attribute boarding the assigned unit is confirmed by the user attribute judging unit for judging the attribute of Has been proposed (for example, see Patent Document 1).

In addition, a tag that stores a usable floor indicating a user attribute detected by the first receiver at the hall where the input device is located as a car to which a call corresponding to the destination floor input to the input device is assigned. The floors other than the available floors are excluded, and the available floor of the tag detected by the corresponding second receiver is the floor of the hall where the input device is located or the destination floor. There has been proposed an elevator control system that includes a control device that excludes units that are not included and selects a unit corresponding to the destination floor from among the remaining units (for example, see Patent Document 2).

According to

Patent Documents

1 and 2, by determining a user attribute and assigning a machine based on the determined user attribute, it is possible to eliminate the sharing of users having different attributes, and the user is permitted. It is possible to suppress movement to a floor that is not.

JP 2013-067497 A International Publication No. 2013/080277

However, the prior art has the following problems.
In the elevator group management system described in Patent Document 1, in order to determine the attributes of a user, a database for managing the attributes is provided in association with the ID number of the user, and the user enters the landing destination floor registration device. The user attribute is determined from the registered ID number, or a card reader is provided to determine the user attribute by reading the information from the ID card in which the user attribute is recorded. ing.

Moreover, in the elevator control system described in Patent Document 2, in order to determine the attributes of the user, a first receiver is provided at each elevator hall, and a second receiver is provided in each elevator car. The user possesses a tag in which the usable floor is stored in association with the ID information, and the first receiver and the second receiver read the tag to determine the attribute of the user.

That is, in the inventions described in

Patent Documents

1 and 2, since the user's attributes are determined by performing personal authentication, the user enters an ID number or a card in which ID information is stored. There is a problem that it is inconvenient. Further, it is necessary to provide an authentication means for performing personal authentication, which causes problems that the system configuration becomes complicated and the cost increases.

The present invention has been made to solve the above-mentioned problems, eliminates the need for personal authentication, eliminates the sharing of users having different attributes, and moves to a floor where the user is not permitted. An object is to obtain an elevator group management control device and a group management control method capable of suppressing movement.

An elevator group management control device according to the present invention is an elevator group management control device applied to a plurality of elevators installed in a building in which floor attributes are set in advance, and is provided with a building doorway When the destination floor is registered by the destination floor registration device installed at the hall of the entrance floor that is the floor, the floor attribute of this destination floor is identified as the user attribute and the floor other than the entrance floor If the destination floor or the hall call registration device is registered by the destination floor registration device or the hall call registration device installed at the hall, the attributes of the floors other than the entrance floor where the destination floor registration device or the hall call registration device is installed are displayed. A user identification unit for identifying a user attribute, and a car allocation unit for allocating a car to the user based on the user attribute identified by the user identification unit.

The elevator group management control method according to the present invention is an elevator group management control method applied to a plurality of elevators installed in a building in which floor attributes are set in advance. When the destination floor is registered by the destination floor registration device installed at the entrance floor landing that is the floor provided with the entrance, the step of identifying the attribute of the floor of the destination floor as the user attribute; When the destination floor registration device or the hall call registration device is registered by the destination floor registration device or the hall call registration device installed at the landing on the floor other than the entrance floor, the entrance where the destination floor registration device or the hall call registration device is installed A step of identifying a floor attribute other than the floor as a user attribute, and a step of assigning a car to the user based on the identified user attribute.

According to the elevator group management control device and the group management control method according to the present invention, when the destination floor is registered by the destination floor registration device installed at the entrance floor landing, which is the floor where the entrance of the building is provided In addition to identifying the attribute of the floor on the destination floor as the attribute of the user, the destination floor or hall call is registered by the destination floor registration device or hall call registration device installed on the floor hall other than the entrance floor. If the destination floor registration device or the hall call registration device is installed, the attributes of the floor other than the entrance floor are identified as user attributes, and the car is assigned to the user based on the identified user attributes. assign.
Therefore, without performing personal authentication, it is possible to eliminate the joining of users having different attributes and to prevent the user from moving to an unauthorized floor.

It is a front view which shows the landing in the entrance floor of the elevator with which the elevator group management control apparatus which concerns on Embodiment 1 of this invention was applied. It is a front view which shows the landing in floors other than the entrance floor of the elevator with which the elevator group management control apparatus which concerns on Embodiment 1 of this invention was applied. It is a block block diagram which shows the group management control apparatus of the elevator which concerns on Embodiment 1 of this invention. It is explanatory drawing which illustrates the attribute of the floor of a building, and a riding rule in the group management control apparatus of the elevator which concerns on Embodiment 1 of this invention. It is a flowchart which shows the process of the group management control apparatus of the elevator which concerns on Embodiment 1 of this invention. It is a flowchart which shows the process of the group management control apparatus of the elevator which concerns on Embodiment 1 of this invention. It is explanatory drawing which illustrates operation | movement of the group management control apparatus of the elevator which concerns on Embodiment 1 of this invention.

Hereinafter, preferred embodiments of an elevator group management control device and a group management control method according to the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals. explain.

First, prior to the description of the embodiments, an overview of an elevator group management control device according to the present invention will be described. The elevator group management control device according to the present invention is based on the destination floor registered by the destination floor registration device installed on the entrance floor of the building and the preset floor attributes, so that the user's riding control is performed. Is to do.

Here, for this building, the attributes of the floor associated with the entrance condition of the floor of the building or the door in the floor are set. The attribute of the floor is floor information of a company occupying a female-only floor, a suite room floor, and a plurality of floors.

According to the elevator group management control device according to the present invention, the attributes of the floor of the destination floor registered by the destination floor registration device are used as user attributes, and different cars are used for a plurality of users having different attributes. By assigning, it is possible to assign, for example, a user who goes to the women-only floor and other users to different cars without performing personal authentication with a simple configuration.

Embodiment 1 FIG.
FIG. 1 is a front view showing a landing at an entrance floor of an elevator to which an elevator group management control device according to Embodiment 1 of the present invention is applied. FIG. 2 is a front view showing a landing on a floor other than the entrance floor of the elevator to which the elevator group management control device according to Embodiment 1 of the present invention is applied.

In FIGS. 1 and 2, two elevators are shown as representatives, but usually, three or more elevators are provided. The entrance floor of the building refers to the floor where the entrance of the building is provided. Moreover, the hall configuration on the entrance floor shown in FIG. 1 can be applied to floors other than the entrance floor.

1 and 2, the landing door 1 is provided on each floor where the elevator stops. A hoistway (not shown) is provided in the back of the landing door 1 and penetrates each floor of the building. In addition, a car (not shown) is installed in the hoistway and moves up and down in the hoistway. When the car arrives at the landing, the landing door 1 opens and the user gets on and off.

When the destination floor is registered in the destination floor registration device 2 installed at the entrance floor landing shown in FIG. In addition to dispatching to the floor, the assigned car display device 3 displays the car name corresponding to the destination floor. The elevator machine name corresponds to the characters and symbols shown on the machine name display 4.

Here, in the landing on the entrance floor shown in FIG. 1, the unit name display 4 shows that the elevator name on the left is A and the elevator name on the right is B. In addition, the assigned car display device 3 displays that the right car B is dispatched in response to a landing destination call to the seventh floor. Furthermore, in each hall, a notification device 5 for notifying the state of the car is provided at the landing on the entrance floor.

Further, the elevator group management control device according to the first embodiment of the present invention is the most suitable number when the hall call is registered by the hall call registration device 6 installed at a hall other than the entrance floor shown in FIG. Deliver a car to the floor

FIG. 3 is a block diagram showing an elevator group management control apparatus according to Embodiment 1 of the present invention. In FIG. 3, the elevator group management control device includes the destination floor registration device 2, the notification device 5, and the hall call registration device 6 shown in FIGS. 1 and 2, and a car call that is provided in the car and registers the destination floor. A registration device 7 and a control device 10 are provided.

The control device 10 includes a user identification unit 11, a car assignment unit 12, a riding rule setting unit 13, and an operation control unit 14. Here, the control device 10 is constituted by a microprocessor having a CPU (Central Processing Unit) (not shown) and a storage unit storing a program. Moreover, each block which comprises the control apparatus 10 is memorize | stored as a software in the memory | storage part.

When the destination floor is registered by the destination floor registration device 2 on the entrance floor, the user identification unit 11 identifies the attribute of the floor on the destination floor from the attribute of the user. In addition, when the destination floor registration device 2 is installed at a landing other than the entrance floor, the user identification unit 11 registers the destination floor with the destination floor registration device 2, and the destination floor registration device 2 The attributes of the installed floor are identified as the user attributes.

In addition, when a hall call is registered by the hall call registration device 6 installed at a hall other than the entrance floor, the user identification unit 11 sets the attribute of the floor where the hall call registration device 6 is installed. Identify with attribute. The user identification unit 11 outputs the registered destination call or hall call and the attribute of the user to the car assignment unit 12.

The car allocating unit 12 assigns allocation candidate cars based on the attributes of the user who operated the destination floor registration device 2 or the hall call registration device 6, and the attributes and the number of users who are scheduled to board or are on board each unit. The assigned car is determined by referring to the riding rule output from the riding rule setting unit 13. Note that the riding rule setting unit 13 may be omitted, and in this case, the car allocating unit 12 determines the assigned car based on the match / mismatch of the attributes of each user.

The riding rule setting unit 13 sets riding rules relating to the sharing of users having different attributes. Specifically, the riding rule setting unit 13 sets the number of people having the same attribute that allows the same car to be assigned to a plurality of users having different attributes. FIG. 4 is an explanatory diagram illustrating the floor attributes of the building and the riding rules in the elevator group management control apparatus according to Embodiment 1 of the present invention.

In FIG. 4, this building has seven floors from the Bth floor to the sixth floor, the Bth floor is a parking lot, the first floor is the ground entrance floor, the second and third floors are men-only floors, the fourth and fifth floors Is the women-only floor, the 6th floor is the family-only floor, the B and 1st floors are the entrance floor, the 2nd and 3rd floors are a attributes, the 4th and 5th floors are b attributes, and the 6th floor is c attributes To do.

At this time, as the riding rules, the number of vehicles that are on board in the a attribute alone is not assigned to users having other attributes, and the number of vehicles in which the b attribute is on board is more than three. Set in such a way as to allow the user to assign the relevant machine. In addition, when a plurality of users having different attributes are already on board, it is possible to set detailed conditions such as two or more persons including the c attribute.

Returning to FIG. 3, the car allocating unit 12 applies the user attribute to the notification device 5 installed at the entrance on the entrance floor with respect to the unit where the user with a single attribute is scheduled to board or is on board. Is output. The notification device 5 performs notification according to the input user attribute.

In addition, when the destination floor registration device 2 is installed at a landing other than the entrance floor, the user identification unit 11 has a destination floor registered by the destination floor registration device 2 other than the entrance floor, and the destination floor When the attribute of the floor on which the registration device 2 is installed does not match the attribute of the floor on the destination floor, the suspicious person information is output to the car assignment unit 12 together with the registered destination call and the attribute of the user. .

In addition, when the hall call registration device 6 is installed at a hall other than the entrance floor, the user identification unit 11 arrives at the floor where the hall call registration device 6 is operated, and the car call registration device. If the destination floor registered in 7 is other than the entrance floor and the attribute of the floor where the hall call registration device 6 is installed does not match the attribute of the floor of the destination floor, the registered destination call and its The suspicious person information is output to the car assignment unit 12 together with the user attributes.

The car allocating unit 12 outputs an entrance floor return command to the driving control unit 14 when the car is allocated to the user to whom the suspicious person information is assigned. When the entrance floor return command is input, the operation control unit 14 causes the car to travel to the entrance floor instead of the destination floor, opens the landing door 1 after arrival at the entrance floor, and then causes the car to travel to the destination floor. . Thereby, it is possible to prompt the user to whom the suspicious person information is given to get off at the entrance floor.

Hereinafter, the processing of the elevator group management control apparatus according to Embodiment 1 of the present invention will be described with reference to the flowcharts of FIGS. 5 shows processing in a configuration in which the riding rule setting unit 13 shown in FIG. 3 is omitted, and FIG. 6 shows processing in a configuration in which the riding rule setting unit 13 is not omitted.

In FIG. 5, first, the destination floor registration device 2 or the hall call registration device 6 is operated at the elevator hall, and the registered destination call or hall call is output to the user identification unit 11 (step S101).

Subsequently, the user identification unit 11 determines whether or not the operated registration device is the destination floor registration device 2 installed on the entrance floor (step S102).

In step S102, when it is determined that the registration device is the destination floor registration device 2 installed on the entrance floor (that is, Yes), the user identification unit 11 determines the floor of the registered destination floor. The attribute is identified as the attribute of the user, and the registered destination call and the attribute of the user are output to the car assignment unit 12 (step S103).

For example, in the building shown in FIG. 4, when the fourth floor is registered as the destination floor in the destination floor registration apparatus 2 installed on the first floor, the b attribute set on the fourth floor is identified as the user attribute. The user attribute becomes the b attribute.

On the other hand, if it is determined in step S102 that the registration device is not the destination floor registration device 2 installed on the entrance floor (that is, No), the user identification unit 11 determines that the destination floor registration device 2 or the landing call The floor where the registration device 6 is installed, that is, the attribute of the boarding floor is identified as the attribute of the user, and the registered destination call or hall call and the attribute of the user are output to the car assignment unit 12. (Step S104).

That is, if the operated registration device is the hall call registration device 6 in step S102, the hall call registration device 6 is installed at a hall other than the entrance floor, so the process always proceeds to step S104.

For example, when a downward hall call is registered by the hall call registration device 6 installed on the 6th floor, the c attribute set on the 6th floor where the hall call registration device 6 is installed is the user attribute. The user attribute is identified as the c attribute.

Next, the car allocating unit 12 determines whether or not there are no assignable units for the newly input user attributes, that is, whether or not all the units have the same attributes as users having different attributes. Determination is made (step S105).

Here, after assigning a user to a certain unit, when another user gets on the way from the boarding floor to the getting-off floor, it is determined that the passenger is on board. However, when the hall call is registered, the exit floor is unknown, so the terminal floor in the direction of the hall call is treated as the exit floor.

For example, in the building shown in FIG. 4, when the hall call registration device 6 installed on the 4th floor registers an upward hall call, the attribute of this user is the b attribute. At this time, since the assigned machine having the destination floor as the sixth floor from the first floor has arrived on the fourth floor, the user with the c attribute has already boarded, and therefore the same machine with the user having a different attribute is on the same floor. In addition, since the a-attribute users are scheduled to get off on the third floor, the machines assigned to the third floor as the destination floor from the first floor do not ride with users having different attributes.

In the building shown in FIG. 4, when a downward hall call is registered by the hall call registration device 6 installed on the 5th floor, the attribute of this user is the b attribute. At this time, when the landing call for the downward landing from the third floor arrives on the third floor, the user with attribute a is scheduled to board, so the passenger with the user having a different attribute is on the same ride. In addition, when a downward hall call is registered by the hall call registration device 6 installed on the 5th floor, when the b attribute user registers the hall call, the user gets off at the 4th floor or 1st floor Since it is not possible to identify whether or not to get off at the terminal B, the B floor of the terminal floor in the downward direction is set as the getting off floor.

In step S105, when it is determined that all the cars have the same power as a user having a different attribute (that is, Yes), the car allocating unit 12 has the car that becomes the empty car earliest among all the cars. However, in order to avoid riding, the car is controlled to pass until the empty car is reached, and the car is dispatched after the empty car is reached (step S106).

On the other hand, if it is determined in step S105 that the condition that all the cars are in the same power as a user having a different attribute is not satisfied, that is, there is an assignable car (that is, No), the car assignment unit No. 12 assigns an optimal number of machines using a normal assignment algorithm from those other than the number of machines with the same attribute as a user (step S107).

Subsequently, the user identification unit 11 again determines whether or not the operated registration device is the destination floor registration device 2 installed on the entrance floor (step S108).

If it is determined in step S108 that the registration device is the destination floor registration device 2 installed on the entrance floor (that is, Yes), the car assignment unit 12 notifies the notification device 5 in the vicinity of the new assignment number machine. The attribute of the user is output, the notification device 5 performs notification according to the input attribute of the user (step S109), and the process of FIG. 5 ends. Here, for example, the notification device 5 is a character display, and when the attribute of the user corresponds to the female-only floor, the character “during female-only driving” is displayed.

On the other hand, if it is determined in step S108 that the registration device is not the destination floor registration device 2 installed on the entrance floor (that is, No), the car assignment unit 12 determines that the registered destination floor is other than the entrance floor. And it is determined whether it differs from a user's attribute (step S110).

If it is determined in step S110 that the registered destination floor is other than the entrance floor and is different from the user attribute (ie, Yes), the car assignment unit 12 outputs an entrance floor return command to the operation control unit 14. Then, the operation control unit 14 controls the car to travel to the entrance floor instead of the destination floor, opens the landing door 1 after arrival at the entrance floor, and then travels to the destination floor (step S111). Then, the process of FIG.

For example, in the building shown in FIG. 4, when a downward hall call registration is registered by the hall call registration device 6 installed on the 6th floor, after the car arrives on the 6th floor, the destination is registered by the car call registration device 7. Even when the third floor is registered as the floor, the car passes through the third floor and opens and closes once on the first floor, and then arrives at the third floor.

On the other hand, if it is determined in step S110 that the registered destination floor is other than the entrance floor and does not satisfy the condition of the user attribute (that is, No), the processing of FIG.

In the case of a configuration in which the riding rule setting unit 13 shown in FIG. 3 is not omitted, steps S105 to S107 shown in FIG. 5 are replaced with steps S201 to S203 shown in FIG.

In FIG. 6, first, the car allocating unit 12 refers to the riding rules set by the riding rule setting unit 13, and determines whether or not allocation is not possible according to the riding rules in all units (step S201).

If it is determined in step S201 that all units cannot be assigned due to the riding rules (that is, Yes), the car assignment unit 12 assigns the car that becomes the empty car earliest from among all the cars. In order to avoid riding, the vehicle is driven until the empty car is reached, and the car is controlled to be dispatched after the empty car is reached (step S202), and the process of FIG. 6 is terminated.

On the other hand, in step S201, if it is determined that the condition that all the cars cannot be assigned by the riding rules does not satisfy the condition, that is, there is an assignable car (that is, No), the car assigning unit 12 An optimal number is assigned using a normal assignment algorithm from other than those that cannot be assigned due to the riding rule (step S203), and the process of FIG. 6 is terminated.

However, if a plurality of users having different attributes get on in step S203, the process of step S109 shown in FIG. 5 may be omitted.

FIG. 7 is an explanatory view illustrating the operation of the elevator group management control apparatus according to the first embodiment of the present invention. FIG. 7 shows an example of the operation of the elevator group management control device in the building shown in FIG. That is, this building is 7 stories from the B floor to the 6th floor, the B floor and the 1st floor are the entrance floor, the 2nd and 3rd floors are the a attribute, the 4th and 5th floors are the b attribute, and the 6th floor is the c attribute. Attribute. There are three elevators, A, B and C.

In FIG. 7, the A machine has two a-attribute users on the B floor, the B machine is an empty car on the fifth floor, and the C machine has a c attribute user on the third floor. Suppose that you are on board. At this time, if the third floor of the destination floor is registered on the first floor, this user is determined to have the a attribute, so that the A machine or the B machine can be assigned. Therefore, Unit A near the first floor is assigned.

Next, when the 4th and 5th floors are registered as destination floors on the 1st floor, since this user is determined to have the b attribute, only Unit B can be assigned. Therefore, Unit B is assigned.

Finally, when a downward landing call is registered on the 6th floor, a B attribute user is already scheduled to board the Unit B, but a b attribute user gets off before arriving at the 6th floor. Therefore, Unit B or Unit C can be assigned. Therefore, even if the C car is traveling downward, the C car is assigned because it is more likely to arrive earlier than the B car.

In addition, in FIG. 1, although the alerting | reporting apparatus 5 was used as the indicator, it may be alert | reported by an audio | voice and may be abbreviate | omitted. In FIG. 1, the operation control unit 14 may be omitted.

As described above, according to the first embodiment, when the destination floor is registered by the destination floor registration device installed at the entrance floor landing, which is the floor where the entrance of the building is provided, the destination floor In addition to identifying the attributes of the floor as the attributes of the user, if the destination floor or hall call is registered by the destination floor registration device or the hall call registration device installed at the floor landing other than the entrance floor, the destination floor The attributes of the floors other than the entrance floor where the registration device or the hall call registration device is installed are identified as user attributes, and a car is assigned to the user based on the identified user attributes.
Therefore, without performing personal authentication, it is possible to eliminate the joining of users having different attributes and to prevent the user from moving to an unauthorized floor.
In addition, it is not necessary for the user to input an ID number or to carry a card or tag in which ID information is stored in order to identify the user's attributes, so that convenience for the user is improved. Further, since there is no need to provide an authentication means for performing personal authentication, the system configuration is simplified and the cost can be reduced.

In addition, the car allocating unit allocates different cars to a plurality of users having different user attributes identified by the user identifying unit. Therefore, it is possible to assign a user who goes to the women-only floor and other users to different cars with a simple configuration without using authentication means.

In addition, the car allocating unit has an attribute when the attribute of the user identified by the user identifying unit is the same for a plurality of users or when a plurality of users having the same attribute are in the car. Allow the car to be assigned to different users. Therefore, the operation efficiency of an elevator can be improved.

Further, a riding rule setting unit is further provided for setting the number of people having the same attribute that allows the same car to be assigned to a plurality of users having different attributes. Therefore, it is possible to set an allowable condition that allows the same car to be assigned for each user attribute.

In addition, when the car assigned by the car assigning unit is assigned to a user having a single attribute, it is further provided with a notification device that notifies the user's attribute when installed at a landing on the entrance floor. Therefore, it is possible to suppress the riding of users having different attributes into the car.

In addition, an operation control unit is further provided for driving the car to the entrance floor before the car stops at a different destination floor, arriving at the entrance floor and opening the landing door, and then driving the car to the destination floor. ing. Therefore, it is possible to ensure the same security as the front floor forced stop operation.

Claims

An elevator group management control device applied to a plurality of elevators installed in a building in which floor attributes are set in advance,
When the destination floor is registered by the destination floor registration device installed in the entrance floor landing, which is the floor where the entrance of the building is provided, the floor attribute of the destination floor is identified as the user attribute. A destination floor registration device or a hall call registration device was installed when a destination floor or a hall call registration device was registered by a destination floor registration device or a hall call registration device installed at a landing on a floor other than the entrance floor. A user identifying unit for identifying attributes of floors other than the entrance floor as attributes of users;
A car assignment unit for assigning a car to a user based on the attributes of the user identified by the user identification unit;
Elevator group management control device.
The elevator group management control device according to claim 1, wherein the car assignment unit assigns different cars to a plurality of users having different user attributes identified by the user identification unit.
The car allocating unit has an attribute when the attributes of the user identified by the user identifying unit are the same for a plurality of users, or when a plurality of users having the same attribute are on the car. The elevator group management control device according to claim 1 or 2, wherein the car is allowed to be assigned to different users.
The riding rule setting part which sets the number of people of the same attribute which permits the allocation of the same car with respect to the several user who has a mutually different attribute is further provided in any one of Claim 1- Claim 3. Elevator group management control device.
The system further comprises a notification device that is installed at a landing on the entrance floor and that notifies a user attribute when the car assigned by the car allocating unit is assigned to a user having a single attribute. The elevator group management control device according to any one of claims 4 to 5.
An operation control unit is further provided that causes the car to travel to the entrance floor before the car stops at a different destination floor, arrives at the entrance floor, opens the landing door, and then travels the car to the destination floor. The elevator group management control device according to any one of claims 1 to 5.
A group management control method for elevators applied to a plurality of elevators installed in a building in which floor attributes are set in advance,
When the destination floor is registered by the destination floor registration device installed in the entrance floor landing, which is the floor where the entrance of the building is provided, the floor attribute of the destination floor is identified as the user attribute. Steps,
When the destination floor registration device or the hall call registration device is registered by the destination floor registration device or the hall call registration device installed at the landing on the floor other than the entrance floor, the entrance where the destination floor registration device or the hall call registration device is installed Identifying attributes of floors other than the floor from user attributes;
Assigning a car to a user based on the identified user attributes;
A group management control method for elevators.