JP6940228B2 - Elevator group management system - Google Patents

Description

Embodiments of the present invention relate to a group management system for elevators.

Generally, a landing call button for registering a landing call is installed at the landing on each floor of the building. When the elevator user operates this landing call button, the car responds to the registration floor of the landing call. When the user gets into the car and operates the destination floor button on the car operation panel, the destination floor is registered and the car moves to the destination floor.

In recent years, an elevator system equipped with a landing destination floor registration device (HDC: Hall Destination Controller) capable of directly designating a destination floor at the landing has been put into practical use in addition to the above-mentioned landing call button. Such an elevator system is called a "destination control system (DCS)". The DCS selects the most suitable car from a plurality of cars based on the destination floor registered by the user at the landing, and responds to the landing. In this case, transportation efficiency is improved by having users on the same destination floor board the same car.

Here, when the car (allocated car) that responds to the destination floor of the user is determined, the information of the assigned car is displayed on the landing destination floor registration device. As a result, the user can confirm the car to be boarded and can wait in front of the boarding place where the car arrives.

Japanese Patent No. 5885978

However, normally, the information of the assigned car displayed on the landing destination floor registration device is erased after a certain period of time (several seconds). In addition, when the subsequent user performs the registration operation within the above-mentioned fixed time, the information of the allocation car displayed before that is deleted. For this reason, if you forget the car you should ride, you may not be able to confirm it, and you may have to re-register the destination floor. In this case, since the previously registered destination floor cannot be canceled, so-called "wasteful call" occurs, which causes a decrease in operation efficiency.

An object to be solved by the present invention is to provide an elevator group management system that can later confirm the car to be boarded at the landing and prevent a decrease in operation efficiency due to re-registration of the destination floor.

The elevator group management system according to one embodiment manages a plurality of cars in a group, and each of the above cars is based on the destination floor of the user registered by the landing destination floor registration device installed on any floor. In a system that selects the most suitable car from among them and makes it respond to the registration floor as an allocation car, each user who has performed the registration operation holds the allocation information indicating each destination floor and the allocation car as history information, and the above It is provided with display control means for displaying on a part of the display unit provided in the landing destination floor registration device.
The display unit has a first display area and a second display area, and the display control means displays allocation information indicating the destination floor and the allocation car of the user who has performed the registration operation in the first display. Display in the area and display the allocation information indicating the destination floor and allocation car of at least one user who performed the registration operation before the user who performed the registration operation in the second display area. It is a feature.

FIG. 1 is a diagram showing a configuration of an elevator landing according to the first embodiment. FIG. 2 is a diagram showing a configuration of an operation unit provided in the landing destination floor registration device in the same embodiment. FIG. 3 is a diagram showing another configuration of the operation unit provided in the landing destination floor registration device in the same embodiment. FIG. 4 is a diagram showing a configuration of a display unit provided in the landing destination floor registration device in the same embodiment. FIG. 5 is a diagram showing a display example of the allocation information displayed on the display unit. FIG. 6 is a diagram showing a display example of the allocation information displayed on the display unit. FIG. 7 is a diagram showing a display example of the allocation information displayed on the display unit. FIG. 8 is a diagram showing a display example of the allocation information displayed on the display unit. FIG. 9 is a diagram showing another configuration of the display unit. FIG. 10 is a diagram showing a configuration of an elevator group management system in the same embodiment. FIG. 11 is a block diagram showing a functional configuration of the landing destination floor registration device in the same embodiment. FIG. 12 is a diagram showing the contents of the storage unit provided in the landing destination floor registration device in the same embodiment. FIG. 13 is a flowchart showing the operation of the embodiment. FIG. 14 is a flowchart showing the operation of the second embodiment. FIG. 15 is a diagram showing a display example of allocation information displayed on the display unit during off-peak hours in the same embodiment. FIG. 16 is a flowchart showing a normal display process in the same embodiment. FIG. 17 is a flowchart showing the operation of the third embodiment. FIG. 18 is a diagram showing an example of a case where a specific floor is hidden in the same embodiment. FIG. 19 is a flowchart showing the operation of the fourth embodiment. FIG. 20 is a diagram showing a display example of allocation information displayed on the display unit in the same embodiment. FIG. 21 is a diagram showing a display example of allocation information displayed on the display unit in the same embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
(First Embodiment)
FIG. 1 is a diagram showing a configuration of an elevator landing according to the first embodiment. The elevator mentioned here is basically a "car".

In the figure, 10 is a landing on any floor, and 11a and 11b are landing doors. The landing door 11a opens and closes in conjunction with the car door when the car of Unit A arrives. The landing door 11b opens and closes in conjunction with the car door when the car of Unit B arrives.

A landing destination floor registration device (HDC) 12 is installed at a place away from the landing 10 via, for example, a security gate. The landing destination floor registration device 12 may be installed only on the reference floor, for example, or may be installed on each floor.

The landing destination floor registration device 12 includes an operation unit 13 for the user to register the destination floor, and a display unit 14 for displaying the car (allocated car) on which the user is boarding. The operation unit 13 includes a button key 15 as shown in FIG. 2 or a card reading unit 16 as shown in FIG. In the case of the button key 15, the destination floor is registered by pressing the button key 15. In the case of the card reading unit 16, the user's ID card 17 is brought close to the card reading unit 16 to read the user's ID (identification information) and destination floor information recorded in advance on the ID card 17. The operation unit 13 may be configured with a touch panel, and the destination floor may be registered by touch operation.

The display unit 14 is composed of a display such as an LCD, and when the user registers the destination floor, the display unit 14 displays the information of the car (allocated car) to which the destination floor is assigned in association with the destination floor. In the following, the information in which the destination floor and the allocation basket are associated with each other will be referred to as "allocation information".

Here, the landing destination floor registration device 12 has a history display function for displaying allocation information indicating the destination floor and the allocation car for each user who has performed the registration operation of the destination floor on a part of the display unit 14. Is provided.

FIG. 4 shows the configuration of the display unit 14.
The display unit 14 has a first display area 14a and a second display area 14b. In the first display area 14a, allocation information indicating the destination floor and the allocation car of the user who performed the registration operation is displayed. In the second display area 14b, allocation information indicating the destination floor and the allocation car of at least one or more users who performed the registration operation before the user who performed the registration operation is displayed.

Specifically, each user is designated as P1, P2, P3, P4 in the order of registration on the destination floor. In this case, the allocation information indicating the destination floor of the user P4 and the allocation car is displayed as the latest information in the first display area 14a. In the second display area 14b, allocation information indicating the destination floors and allocation baskets of the users P1 to P3 who performed the registration operation before the user P4 is displayed as history information.

In the second display area 14b, the allocation information of the user P3 is displayed at the top, and then the allocation information of the user P2 and the allocation information of the user P1 are displayed in chronological order. In the example of FIG. 4, the display unit 14 is divided into left and right, the left side is the first display area 14a and the right side is the second display area 14b, but the left side is the second display area 14b and the right side is the second display area 14b. The display area 14a of 1 may be used.

Here, for example, if a new user P5 comes and performs a registration operation on the destination floor, as shown in FIG. 5, the allocation information of the user P5 is displayed in the first display area 14a as the latest information. .. Along with this, the allocation information of the user P4 displayed in the first display area 14a is moved to the second display area 14b and displayed at the highest level in the display area 14b.

Further, the display holding time of the first display area 14a is predetermined, and after a certain period of time (for example, 3 seconds) elapses, the allocation information displayed in the first display area 14a is erased and the second display is displayed. It is displayed at the top of the area 14b. This state is shown in FIG. For example, when a certain period of time elapses while the allocation information of the user P4 is displayed in the first display area 14a, the allocation information of the user P4 is erased from the first display area 14a, and the second display area 14a is used as the past information. It is displayed at the top of the display area 14b.

The number of displays in the second display area 14b can be arbitrarily set according to the screen size. Further, the corresponding allocation information is deleted from the second display area 14b at the timing when the allocation car arrives at the registration floor and the door is closed after a certain period of time. For example, when the car of Unit C is closed, the allocation information corresponding to Unit C is deleted from the second display area 14b. This is because it is meaningless to leave the allocation information of the user P1 who has Unit C as an allocation car in the second display area 14b because he / she cannot board the vehicle after the door is closed.

Here, in DCS, basically the same destination floor is assigned to the same car, but even if the destination floor is the same, it may be assigned to another car depending on the operating conditions of each unit. In such a case, a plurality of cars having the same destination floor may be displayed in the second display area 14b, and it may not be possible to determine which car to ride from the information of only the destination floor.

In order to solve such a problem, for example, as shown in FIG. 7, the registration time 14c is added to the allocation information for each user, and if there is a car having the same destination floor, it is composed of some mark. It is preferable to add caution information 14d.

In the example of FIG. 7, the destination floors of the user P3 and the user P6 are common on the 3rd floor, and the car of the No. A machine is assigned to the user P3 and the car of the No. C machine is assigned to the user P6. Here, assuming that the registration time of the user P3 is 8:00 and the registration time of the user P6 is 7:59, it is possible to determine the car to be boarded from the difference in the registration times. In addition, if the registration time of each user is close, it may not be possible to determine which car to ride, so for example, as shown in Fig. 8, how many seconds before the current time was registered in the allocation information for each user? The time information 14e indicating the above may be added.

Although FIGS. 4 to 8 show an example in which the display unit 14 is divided into left and right, for example, as shown in FIG. 9, the display unit 14 is divided into upper and lower parts, and the upper side is the first display area 14a and the lower side. May be set as the second display area 14b.

FIG. 10 is a diagram showing a configuration of an elevator group management system. Here, a configuration in which four passenger cars of Units A to D are group-managed is shown, but the configuration is not particularly limited to this configuration, and the number of passenger cars may be any number. The same parts as those in FIG. 1 will be described with the same reference numerals.

In the present embodiment, the elevator group management system is composed of the car control devices 31a, 31b, 31c, 31d and the group management control device 32 connected to these car control devices 31a, 31b, 31c, 31d. ..

The car control devices 31a, 31b, 31c, 31d are provided corresponding to the car 21a, 21b, 21c, 21d. The car control devices 31a, 31b, 31c, and 31d perform control of the car alone, including drive control of the hoisting machine (not shown) and door opening / closing control.

A display 20a is connected to the car control device 31a. A display 20b is connected to the car control device 31b. As shown in FIG. 1, the display 20a is installed near the landing door 11a of the car 21a of the No. A machine, and displays the destination floor and the driving direction of the car 21a. The display 20b is installed near the landing door 11b of the car 21b of the No. B machine, and displays the destination floor and the driving direction of the car 21b.

Similarly, a display 20c is connected to the car control device 31c, and a display 20d is connected to the car control device 31d. The display 20c is installed near the landing door of the car 21c of the No. C machine, and displays the destination floor and the driving direction of the car 21c. The display 20d is installed near the landing door of the car 21d of Unit D to display the destination floor, the driving direction, etc. of the car 21d. In the example of FIG. 1, the indicators 20a, 20b, 20c are used for convenience. , 20d are shown only one by one, but in reality, indicators 20a, 20b, 20c, 20d are installed at the landing on each floor.

Here, at least one landing destination floor registration device 12 is installed at the landing on any floor. When the destination floor of the user is registered by the landing destination floor registration device 12, destination calls that combine two pieces of information, the destination floor and the registration floor (the floor where the registration operation of the destination floor is performed), are grouped. It is sent to the management control device 32.

When the group management control device 32 receives the destination call from the landing destination floor registration device 12, the optimum car among the cars 21a, 21b, 21c, and 21d is based on the destination floor of the user included in the destination call. Is selected as an allocation basket and responds to the registration floor. At this time, the display unit 14 of the landing destination floor registration device 12 operated by the user displays the allocation information indicating the information of the user's destination floor and the allocation car.

FIG. 11 is a block diagram showing a functional configuration of the landing destination floor registration device 12.
The landing destination floor registration device 12 is provided with a control unit 41 and a storage unit 42 in addition to the operation unit 13 and the display unit 14 shown in FIG. The control unit 41 has a call registration control unit 41a and a display control unit 41b.

When the destination floor of the user is registered through the operation unit 13, the call registration control unit 41a issues a destination call with the information of the registered floor added to the destination floor and transfers it to the group management control device 32. The display control unit 41b controls the display on the display unit 14.

As shown in FIG. 12, in the storage unit 42, allocation information indicating the destination floor and the allocation car is stored in the order of registration time for each user who has performed the registration operation of the destination floor. The display control unit 41b performs display control on the display unit 14 based on the allocation information stored in the storage unit 42. In the present embodiment, the landing destination floor registration device 12 is provided with display control functions (display control unit 41b and storage unit 42), but the group management control device 32 controls the display of the landing destination floor registration device 12. May be.

Next, the operation of the first embodiment will be described.
FIG. 13 is a flowchart showing the operation of the first embodiment, and shows the flow from the registration of the destination floor by the landing destination floor registration device 12 to the display of the assigned car.

When the user performs the registration operation of the destination floor through the operation unit 13 of the landing destination floor registration device 12 on any floor (Yes in step S101), the destination call with the information of the registration floor added to the destination floor is the control unit. It is issued by the call registration control unit 41a of 41 and transferred to the group management control device 32 (step S102).

When the group management control device 32 receives the destination call, the group management control device 32 selects the optimum car among the cars 21a, 21b, 21c, and 21d as the allocation car based on the destination floor of the user included in the destination call. Respond to the registration floor. When the allocation car is determined, the information (unit name) of the allocation car is sent from the group management control device 32 to the landing destination floor registration device 12 operated by the user as the allocation result. When the landing destination floor registration device 12 receives this allocation result (Yes in step S103), it stores it in the storage unit 42 shown in FIG. 12, and also displays the following with history through the display control unit 41b of the display unit 14. Execute the process.

That is, first, the display control unit 41b displays the allocation information indicating the destination floor of the user who performed the registration operation and the allocation basket in the first display area 14a of the display unit 14 (step S104). Here, after a certain period of time (for example, 3 seconds) has elapsed (Yes in step S105), the display control unit 41b erases the currently displayed allocation information from the first display area 14a (step S106), and deletes the allocation information. It is displayed at the top of the second display area 14b (step S107).

The same applies when a new user registers the destination floor within the above-mentioned fixed time (No in step S105, Yes in step S108), and the display control unit 41b is currently displaying from the first display area 14a. The allocation information is deleted (step S109), and the allocation information is displayed at the top of the second display area 14b (step S110). In this case, the allocation car is selected based on the destination floor of the new user, and the information of the allocation car is displayed together with the destination floor in the first display area 14a as the allocation information (steps S102 to S104).

In this way, the allocation information indicating the destination floor and the allocation car of the user who performed the registration operation is displayed in the first display area 14a of the display unit 14, and the above registration operation is performed in the second display area 14b. Allocation information indicating the destination floor and allocation car of at least one user who performed the registration operation before the user who performed the registration is displayed (see FIGS. 4 to 9).

Therefore, if you forget the car you should ride after registering the destination floor, you can check it in the second display area 14b of the display unit 14. For example, as shown in FIG. 4, if the registered user P3 with the 3rd floor as the destination floor forgets the car to ride on, the car for the 3rd floor can be searched for in the second display area 14b. It turns out that it is Unit A.

Here, when the allocation car arrives at the registration floor and the door is closed after a certain period of time (Yes in step S111), the display control unit 41b erases the corresponding allocation information from the storage unit 42 and the second display area 14b. The display of the allocation information is erased from (step S112).

As described above, according to the first embodiment, when the user registers the destination floor, the allocation information indicating the destination floor and the allocation car at that time is displayed in the first display area 14a of the display unit 14, and then. It is displayed as a history in the second display area 14b. Therefore, if you forget the car you should ride, you can check it in the second display area 14b, and you can prevent the operation efficiency from decreasing due to re-registration of the destination floor.

(Second Embodiment)
Next, the second embodiment will be described.
For example, in an office building, a large number of users may concentrate on the same floor during the morning commuting time. In such a case, since subsequent users register the destination floors one after another, it may not be possible to confirm the car on which they should ride in the first display area 14a of the display unit 14, and in the second display area 14b. You need to confirm. On the other hand, when the number of users is low, the display of the first display area 14a is held for a certain period of time, so that the second display area 14b is often not required. In addition, when it is off, you may feel uneasy that the car you should ride on is displayed as a history in the second display area 14b.

Therefore, in the second embodiment, the history display mode and the normal display mode are switched according to the traffic conditions. The "history display mode" is a mode in which the user's allocation information (destination floor and allocation basket) is displayed as a history in the second display area 14b of the display unit 14. The "normal display mode" is a mode in which the user's allocation information (destination floor and allocation basket) is displayed only in the first display area 14a of the display unit 14, and the history display for the second display area 14b is prohibited. ing.

FIG. 14 is a flowchart showing the operation of the second embodiment.
When the destination floor of the user is registered in the landing destination floor registration device 12 (Yes in step S201), the display control unit 41b determines whether or not it is a busy time when a large number of users are concentrated (step S202). ..

Specifically, the display control unit 41b prepares a congestion status table (not shown) in which a congestion time zone and a quiet time zone are set in advance, and refers to this congestion status table to see if the current time is a congestion time. Judge whether or not. For example, a camera may be installed at the landing and the congestion status may be determined from the image of the camera. Alternatively, the number of registrations per unit time of the landing destination floor registration device 12 may be calculated, and the congestion status may be determined from the number of registrations.

If it is crowded (Yes in step S202), the display control unit 41b switches to the history display mode and executes the display process with history described in the first embodiment (step S203). That is, the display control unit 41b displays the allocation information indicating the destination floor and the allocation car of the user who performed the registration operation in the first display area 14a of the display unit 14, and is before the user who performed the registration operation. The allocation information indicating the destination floor and the allocation car of at least one user who has performed the registration operation in is displayed in the second display area 14b (see FIGS. 4 to 9).

On the other hand, if it is off-peak (No in step S202), the display control unit 41b switches to the normal display mode and executes the display process without history (step S204). In this case, as shown in FIG. 15, the display of the allocation information for the second display area 14b is prohibited, and the allocation information is displayed only for the first display area 14a.

In the example of FIG. 15, one of the screens divided into two is used as the first display area 14a, and the allocation information of the user P4 who has performed the registration operation is displayed there. The screen may be switched to the first display area 14a.

FIG. 16 is a flowchart showing a normal display process executed in step S204. The processing of steps S301 to S304 is the same as the processing of steps S101 to S104 of the flowchart shown in FIG.

That is, when the user performs the registration operation of the destination floor through the operation unit 13 of the landing destination floor registration device 12 on any floor (Yes in step S301), the destination call with the registration floor information added to the destination floor is issued. It is issued by the call registration control unit 41a of the control unit 41 and transferred to the group management control device 32 (step S302).

When the group management control device 32 receives the destination call, the group management control device 32 selects the optimum car among the cars 21a, 21b, 21c, and 21d as the allocation car based on the destination floor of the user included in the destination call. Respond to the registration floor.

When the allocation car is determined, the information (unit name) of the allocation car is sent from the group management control device 32 to the landing destination floor registration device 12 operated by the user as the allocation result. When the landing destination floor registration device 12 receives the allocation result (Yes in step S303), the landing destination floor registration device 12 transmits the allocation information indicating the user's destination floor and the allocation basket to the first display area 14a of the display unit 14 through the display control unit 41b. Display (step S304).

Here, when a certain period of time has elapsed (Yes in step S305), the display control unit 41b deletes the allocation information currently being displayed from the first display area 14a, and then displays the allocation information in the second display area 14b. It is prohibited to display in (step S306). The same applies when a new user registers the destination floor in the landing destination floor registration device 12 within the above-mentioned fixed time (No in step S305, Yes in step S307), and the display control unit 41b displays the first display. After deleting the currently displayed allocation information from the area 14a, it is prohibited to display the allocation information in the second display area 14b (step S308). In this case, the allocation car is selected based on the destination floor of the new user, and the information of the allocation car is displayed together with the destination floor in the first display area 14a as the allocation information (steps S302 to S304).

As described above, according to the second embodiment, the re-registration of the destination floor can be prevented by displaying the allocation information of the users in the second display area 14b in the history at the time of congestion with many users. On the other hand, by prohibiting the history display when the number of users is low and the number of users is low, it is possible to prevent others from knowing the car in which the vehicle is being driven.

(Third Embodiment)
Next, a third embodiment will be described.
When you go to a specific floor, for example, a floor used by an important person, you may not want other users to know about it. Therefore, in the third embodiment, when a specific floor is registered as a destination floor, the allocation information having that destination floor is hidden in the second display area 14b.

FIG. 17 is a flowchart showing the operation of the third embodiment. The process shown in this flowchart is executed in step S107 or S110 of FIG.

That is, in step S107 or S110, the display control unit 41b determines whether or not the destination floor of the user is a preset specific floor (step S401). It is assumed that the information regarding the specific floor is stored in the storage unit 42 shown in FIG.

When the destination floor of the user is a specific floor (Yes in step S401), the display control unit 41b hides the allocation information having the destination floor in the second display area 14b (step S402). On the other hand, when the destination floor of the user is not a specific floor (No in step S401), the display control unit 41b provides the allocation information having the destination floor to the second, as in the first embodiment. Display in the display area 14b (step S403).

FIG. 18 shows an example of the case where the specific floor is hidden.
For example, suppose that the destination floor of user P1 is 12F, and the car No. C car 21c is assigned as the car allocation car. When 12F is set as a specific floor, the allocation information (destination floor and allocation basket) of the user P1 is masked in the second display area 14b and is hidden as shown in FIG. Become. On the other hand, when 12F is not set as a specific floor, as shown in FIG. 4, the allocation information (destination floor and allocation basket) of the user P1 is the second, like the other users P2 and P3. It is displayed in the display area 14b.

As described above, according to the third embodiment, when a specific floor is registered as a destination floor, the allocation information having that destination floor is hidden in the second display area 14b of the display unit 14. Therefore, it is possible to prevent the destination floor from being known to others.

(Fourth Embodiment)
Next, a fourth embodiment will be described.
In the fourth embodiment, the same destination floor can be registered by designating an arbitrary destination floor in the second display area 14b of the display unit 14.

FIG. 19 is a flowchart showing the operation of the fourth embodiment. The process shown in this flowchart is executed in a state where the user's allocation information (destination floor and allocation car) is displayed in the second display area 14b of the display unit 14. It is assumed that the touch panel 18 (see FIGS. 20 and 21) is arranged on the screen of the second display area 14b of the display unit 14, and the user can perform a touch operation on the screen.

Now, with the allocation information (destination floor and allocation basket) of at least one user displayed in the second display area 14b of the display unit 14, subsequent users are in the second display area 14b. Suppose you touch any destination floor of. When an arbitrary destination floor is designated by a touch operation on the second display area 14b (Yes in step S501), the call registration control unit 41a of the control unit 41 additionally registers the designated destination floor (step). S502), the information of the registered floor is added to the destination floor, a destination call is issued, and the destination floor is transferred to the group management control device 32 (step S503).

The group management control device 32 performs allocation control based on the destination call. In this case, basically, the same car is selected as the allocation car for the same destination floor, and the allocation car is fed back to the landing destination floor registration device 12 as the allocation result, and the first display area of the display unit 14 It is displayed on 14a.

This situation is shown in FIGS. 20 and 21.
Now, as shown in FIG. 20, it is assumed that the allocation information (destination floor and allocation basket) of the users P1, P2, P3 is displayed in the second display area 14b of the display unit 14. Here, for example, when the subsequent user P7 goes to the same destination floor "3F" as the user P3, if the "3F" in the second display area 14b is touched with a finger, the "3F" becomes the destination floor. As shown in FIG. 21, the information of the car to which the destination floor is assigned is displayed in the first display area 14a.

As described above, according to the fourth embodiment, the same destination floor can be easily registered by designating an arbitrary destination floor in the second display area 14b of the display unit 14. Therefore, when a plurality of users belonging to the same group, such as a family member, go to the same floor, it is possible to save the trouble of operating the operation unit 13 for each user to register the destination floor.

According to at least one embodiment described above, it is possible to provide an elevator group management system that can later confirm the car to be boarded at the landing and prevent a decrease in operation efficiency due to re-registration of the destination floor. ..

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 modifications thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.

10 ... landing, 11a, 11b ... landing door, 12 ... landing destination floor registration device, 13 ... operation unit, 14 ... display unit, 14a ... first display area, 14b ... second display area, 15 ... button keys, 16 ... card reader, 17 ... ID card, 18 ... touch panel, 20a to 20d ... display, 21a to 21d ... car, 31a to 31d ... car control device, 32 ... group management control device, 41 ... control unit, 41a ... Call registration control unit, 41b ... Display control unit, 42 ... Storage unit.

Claims (10)

A group of multiple cars is managed, and the most suitable car is selected and assigned from each of the above cars based on the destination floor of the user registered by the landing destination floor registration device installed on any floor. In the elevator group management system that responds to the registration floor as a car
Each user who has performed the registration operation is provided with display control means that holds allocation information indicating each destination floor and allocation car as history information and displays it on a part of the display unit provided in the above-mentioned landing destination floor registration device. and,
The display unit has a first display area and a second display area.
The display control means
The allocation information indicating the destination floor and the allocation car of the user who performed the above registration operation is displayed in the above first display area.
An elevator characterized by displaying allocation information indicating the destination floor and allocation car of at least one or more users who performed the registration operation before the user who performed the registration operation in the second display area. Group management system. The display control means
After a certain period of time has passed or when a new user performs the registration operation while the allocation information indicating the destination floor and the allocation car of the user who performed the above registration operation is displayed in the first display area. elevator group control system according to claim 1, wherein the displaying the assignment information displayed on the first display area to the second display area. The display control means
The feature is that the corresponding allocation information is deleted from the history information and the display of the allocation information is deleted from the second display area at the timing when the door is closed after the allocation car arrives at the registration floor. The elevator group management system according to claim 1. The display control means
Elevator group control system according to claim 1, wherein the allocation information of each user are arranged in chronological order displayed on the second display area. The display control means
Elevator group control system according to claim 1, wherein the by adding registration time the allocation information of each user displayed on the second display area. The display control means
Group management system according to claim 1, wherein the elevator, characterized in that by adding the time information indicating a few seconds registered prior to the current time to the allocation information of each user displayed on the second display area .. The display control means
Elevator group control system according to claim 1, wherein the allocation information by adding warning information to the allocation information when exists and displaying on the second display area having the same destination floor. The display control means
The history display mode and the normal display mode are switched according to the traffic conditions. In the history display mode, the allocation information of each user is displayed in the second display area, and in the normal display mode, the second display area is displayed. an elevator group supervisory control system according to claim 1, wherein the prohibiting display. The display control means
When the preset floor is registered as a destination floor, the elevator group control system according to claim 1, wherein the allocation information, characterized in that the non-displayed on the second display area having a destination floor .. When any destination floor in the second display area is designated by a predetermined operation, the elevator according to claim 1, characterized by further comprising a registration control means for additionally registering the destination floor Group management system.

Images