JP2017178475A - Elevator device and controlling method of elevator device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress the number of long waiting people to enhance service quality by predicting individual waiting time periods for respective users to evaluate the whole long waiting ratio on the basis of excessive waiting time periods and number of waiting people.SOLUTION: An elevator device of the invention is an elevator device for allocating cars for service to respective users on the basis of boarding floors and destination floors of respective users, as well as the number of the users registered before boarding to the elevators. The elevator device comprises: a prediction part for predicting a waiting time distribution of the whole users from users arrival time at boarding sites and predicted arrival time of the respective allocated cars; an evaluation part for evaluating a long waiting time ratio by calculating the number of people waiting for longer than a long waiting determination time, and long waiting time periods exceeding the long waiting determination time, for respective allocated cars at respective boarding sites, on the basis of the waiting time distribution for the whole users; and a car allocation determination part for allocating the cars for service to respective users on the basis of the evaluation result of the evaluation part.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an elevator apparatus and an elevator apparatus control method, and more particularly to a group management elevator apparatus that collectively manages a plurality of elevators and a control method for the group management elevator apparatus.

  In relatively large buildings, multiple elevators are installed in order to improve the user transportation capacity of the elevators, and a service is provided by selecting the optimal elevator from the multiple elevators when registering the call at the landing. System is introduced. In addition, as the size of the building increases, the number of elevators installed will increase. Therefore, by appropriately managing these multiple elevators with the group management system, services such as reducing waiting time for users will be improved. (See, for example, Patent Documents 1 to 3).

  Patent Document 1 states that “a destination floor input via a landing destination floor registration device is registered as a landing call and a car is assigned to the landing call. For each car, the car is a specific floor. When the predicted value of the waiting number at a specific floor at the time of reaching the floor in a predetermined direction is determined, and the predicted value of the waiting number determined for a certain car is equal to or greater than the predetermined value, "It is operated in an operation mode that does not respond to hall calls made on floors other than the floor."

  In Patent Document 2, “a service index value of each floor according to a change in the number of passengers or the number of people in the car from the time of assignment of the hall call is calculated based on the hall information, in-car information, and assignment information. The hall call is reassigned based on the service index value ". Also,

  Patent Document 3 describes that “the service for passengers with individual average waiting time longer than the total average waiting time obtained by averaging the waiting times of all passengers is given priority”.

Japanese Patent Laying-Open No. 2015-67371 Japanese Patent Laying-Open No. 2015-67432 Japanese Patent Laid-Open No. 5-78045

  In the prior art described in Patent Document 1, although priority is given to services on the floor according to the number of people waiting on a specific floor, the waiting time of each waiting customer is not taken into account, There is no consideration for the long wait until the car arrives. Therefore, since long wait evaluation is performed only by the waiting time of the person who waited first, in situations where long waits occur on multiple floors such as during lunch hours, the number of long waits is larger than the floor with many long waits There are cases where a few floors are given priority, and there is a problem that the average waiting time of the entire building increases.

  In addition, since the prior art described in Patent Document 2 changes the allocation to the car in consideration of changes in the number of passengers in the platform and the car, for long-awaited users, the long-awaited phrase, the car Will be changed and the frustration will be further increased. Moreover, although the prior art described in Patent Document 3 is a technology for providing priority services to passengers who are waiting longer than the total average waiting time, a new long waiting time is generated by performing priority services on multiple floors. There is a problem to do.

  The present invention evaluates the overall long wait rate based on the excessive long wait time exceeding the long wait determination time and the long wait number, thereby suppressing the long wait number and improving the service. And it aims at providing the control method of an elevator apparatus.

In order to solve the above problems, for example, the configuration described in the claims is adopted.
The present application includes a plurality of means for solving the above problems.
This is an elevator device that assigns a boarding machine to be serviced to each user based on the user's boarding floor, destination floor and number of users registered before boarding the elevator. Based on the waiting time distribution of all users and the prediction unit that predicts the waiting time distribution of all users from the arrival time of the user's landing and the estimated arrival time of each assigned boarding car, the waiting time of the user is Based on the evaluation unit that evaluates the long wait rate by calculating the number of waiters exceeding the long wait determination time and the long wait time exceeding the long wait determination time for each assigned boarding station at each platform, and the evaluation result of the evaluation unit An assigned number determination unit for assigning a service to be served to each user;
It is characterized by providing.

According to the present invention, the waiting time distribution of all users is predicted from the arrival time of the user's landing and the estimated arrival time of each assigned boarding car, and the overall long waiting rate is based on the waiting time distribution of all the users. By evaluating the above, it is possible to suppress the long waiting time and improve the service.
Problems, configurations, and effects other than those described above will become apparent from the description of the following examples.

It is an example of the block diagram which shows the outline of the system configuration | structure of the group management elevator apparatus which concerns on 1st Embodiment of this invention. It is an example of the block diagram which shows the outline of the system configuration | structure of the group management elevator apparatus which concerns on 2nd Embodiment of this invention. It is an example of the flowchart which shows the flow of operation | movement of the landing call duration measurement timer which concerns on Example 1. FIG. It is an example of the flowchart which shows the flow of the process which estimates the waiting time of each user which concerns on Example 2. FIG. It is an example of the figure which shows a long waiting number person recording time table (N). It is an example of the figure which shows a long waiting time total table (K, J, I). It is an example of the figure which shows the table (K, J, I, N) according to long waiting time number of people. It is an example of the flowchart which shows the flow of the process which performs long waiting evaluation of each floor concerning Example 3. It is an example of the figure which shows the long waiting determination time table (N) according to traffic demand. It is an example of the flowchart which shows the flow of the process which performs long waiting evaluation of each floor concerning Example 4. FIG. It is an example of the flowchart which shows the flow of the process which performs long waiting evaluation of each floor concerning Example 5. It is an example of the explanatory view of the prediction long waiting number display concerning Example 6. It is an example of the explanatory view of the prediction long waiting number display concerning Example 7. It is an example of the explanatory view of the past long waiting number of persons and long waiting fatigue display concerning Example 8. FIG. It is an example of the explanatory view of the past frustration index display concerning Example 9. It is an example of the explanatory view of the long waiting situation display at the time of registration concerning Example 10. It is an example of the explanatory view of the long waiting situation display before registration concerning Example 11. It is an example of the explanatory view of the long waiting judgment time setting concerning Example 12.

  Hereinafter, modes for carrying out the present invention (hereinafter referred to as “embodiments”) will be described in detail with reference to the drawings. The present invention is not limited to the embodiments, and various numerical values in the embodiments are exemplifications, and various modifications and application examples are included in the scope of the technical concept of the present invention. Is included.

<Elevator apparatus according to the first embodiment of the present invention>
The elevator apparatus according to the first embodiment of the present invention is a group management elevator apparatus that adopts a group management system configuration that collectively manages a plurality of elevators.

[System configuration]
FIG. 1 is an example of a configuration diagram showing an outline of a system configuration of a group management elevator apparatus according to the first embodiment of the present invention. As shown in FIG. 1, the group management elevator device 10 according to the present embodiment includes an elevator unit 1, a group management control unit (group management control device) 2, a landing call registration unit (landing call registration device) 3, The system configuration includes an operation information display unit (operation information display device) 4.

(Elevator)
The elevator unit 1 includes n elevators (n is an integer of 2 or more) elevators 11_1, 11_2,..., 11_n, and unit control units 12_1, 12_2,. .., 12_n. Hereinafter, the individual elevators 11_1, 11_2,..., 11_n of the elevator unit 1 may be described as boarding cars or simply cars. The n elevators 11_1, 11_2,..., 11_n (No. 1 unit 11_1, No. 2 unit 11_2,..., n unit 11_n) are collectively managed under the control of the group management control unit 2, and waiting time, etc. From the viewpoint, allocation of the optimal number of machines (elevators) to the user is performed via the number control units 12_1, 12_2,.

  Each of the elevators 11_1, 11_2,..., 11_n of the elevator unit 1 has a known configuration in which, for example, a car 111 and a counterweight 112 installed in the hoistway are coupled to both ends of the main rope 113. ing. In the elevators 11_1, 11_2,..., 11_n, the main rope 113 is wound around a sheave 114 and a pulley 115 of a hoisting machine (not shown).

(Group management control unit)
The group management control unit 2 includes a usage information acquisition unit 20, a usage information prediction unit 21, a waiting time evaluation unit 22, an interval evaluation unit 23, a long wait evaluation unit 24, a comprehensive evaluation unit 25, an assigned number machine determination unit 26, and an operation information management. A portion 27 is provided. The group management control unit 2 having these functional units (20 to 27) has n elevators 11_1, 11_2,... In order to assign an optimal unit (elevator) to the user from the viewpoint of waiting time and the like.・, 11_n is collectively managed.

  The usage information acquisition unit 20 takes in elevator usage information, which will be described later, registered by the user in the landing call registration unit 3 before boarding the elevator, and gives the fetched elevator usage information to the usage information prediction unit 21. The usage information prediction unit 21 uses the elevator usage information given from the usage information acquisition unit 20 and the operation information of each boarding machine given from the operation information management unit 27, and then the boarding machine arrives after each user arrives at the landing. Predict the waiting time to wait and the number of people waiting on each floor.

  The waiting time evaluation unit 22 evaluates the waiting time of each floor from the waiting time and waiting number of users of each floor predicted by the usage information prediction unit 21 and the operation information of each boarding car. The interval evaluation unit 23 operates each future car at regular intervals from the waiting time and waiting number of users on each floor and the operation information of each car, as predicted by the use information predicting part 21. Assess spacing. The long waiting evaluation unit 24 calculates the long waiting time and the long waiting number of people on each floor from the waiting time and waiting number of users on each floor and the operation information of each boarding machine predicted by the usage information prediction unit 21. Evaluate the waiting rate. Here, the long wait rate is the ratio of users whose elevator user (passenger) wait time exceeds a predetermined long wait determination time.

  Based on various evaluation values such as the waiting time evaluation unit 22, the interval evaluation unit 23, the long wait evaluation unit 24, etc., the comprehensive evaluation unit 25 determines which unit is most suitable for assigning boarding cars from the viewpoint of waiting time and the like. Comprehensive evaluation of The assigned number determination unit 26 assigns to the boarding number that has the best (high) overall evaluation value of the comprehensive evaluation unit 25. The operation information management unit 27 creates operation information from the assigned boarding machine determined by the assigned car determining unit 26 (hereinafter referred to as “assigned car”) and the elevator usage information predicted by the usage information prediction unit 21, The operation information is output to the operation information display unit 4 installed in the portable terminal or the landing or monitoring room.

  Each functional unit (20 to 27) of the group management control unit 2 described above can be realized by software by the processor interpreting and executing a program that realizes each function. At this time, for information such as programs, tables, and files for realizing the functions of the function units (20 to 27), a recording device such as a memory, a hard disk, and an SSD, or a recording medium such as an IC card, an SD card, and a DVD Can be recorded. Moreover, about each function part (20-27) of the group management control part 2, it is also possible to implement | achieve part or all of them by hardware, for example by the design in an integrated circuit.

(Platform call registration / operation information display)
The landing call registration unit 3 includes an operation unit including a numeric keypad and a display unit, and is installed at an elevator landing. In this landing call registration unit 3, elevator usage information including at least the landing floor and the destination floor of each user is registered under an operation by the user. For example, when the user registers the fifth floor as the destination floor in the landing call registration unit 3 installed at the landing on the first floor, the first floor is registered as the landing floor and the fifth floor is registered as the destination floor. .

  The operation information display unit 4 is a display unit of a portable terminal owned by a user of the elevator, or a display device installed in a landing or a monitoring room. And the operation information display part 4 presents the said operation information to a user by the operation information created from the assigned number machine and elevator utilization information being output from the operation information management part 27 (providing). Details of the operation information presented to the user will be described later.

  In the group management elevator apparatus 10 according to the above-described first embodiment, paying attention to the long wait that occupies most of the dissatisfaction of the elevator users, and that the dissatisfaction is proportional to the long wait time and the long wait number of people, the long wait determination time The long wait time and the number of long waits are predicted and the long wait rate is evaluated.

  Specifically, the waiting time distribution of all users is predicted from the arrival time (registration time) of the user's landing and the predicted arrival time of each assigned car. The waiting time distribution shows the waiting time status of all users at each platform. Each user's destination floor registration time, each floor's landing call duration (wait time), and each boarding number on each floor Can be calculated from the estimated arrival time. Based on the waiting time distribution of all users, the number of long waiting people whose user waiting time exceeds the long waiting determination time and the long waiting time exceeding the long waiting determination time are calculated for each assigned station at each platform. And evaluate the long wait rate.

  As a result, even if long waits occur frequently on multiple floors, it is possible to preferentially service the floor with a long waiting time and a large number of long waits. Can be improved and the service can be further improved. In other words, since the waiting time of each user is taken into consideration, even in the floor where the same long waiting time has occurred, the priority is higher as the floor is expected to have many people with longer waiting time, and more Increase in waiting time of many long waiting customers can be suppressed.

  In order to facilitate understanding, more specific explanation will be given using numerical values. As an example, on the first floor, 10 users are waiting for the arrival of the boarding car, and one of the 10 people is waiting for about 180 seconds, and the remaining 9 are 15 of the expected arrival time of the boarding car. Suppose you arrive at the platform within seconds. That is, on the first floor, one of 10 users has a long waiting time, and nine have a waiting time distribution with a short waiting time. On the other hand, on the third floor, it is assumed that ten users are also waiting for the arrival of the boarding car, and all the ten persons or a person close thereto is waiting time distribution waiting for about 180 seconds.

  In the case of such waiting time distribution on each floor, according to the group management elevator apparatus 10 according to the first embodiment, the third floor has a higher priority than the first floor by taking into account the waiting time of each user. Since it is set higher, it is possible to suppress an increase in waiting time of more long waiting customers. As a result, it is possible to improve the service for a larger number of users and to reduce the average waiting time and the long waiting rate of the entire building.

  In addition, according to the group management elevator apparatus 10 according to the first embodiment, since the arrival time (registration time) of each user is stored and held, and learning is performed, the learning / A simulation can be performed, and the long wait determination time can be calculated accurately for each traffic flow.

  In addition, in the group management elevator apparatus 10 which concerns on 1st Embodiment, although it is made to acquire from the hall call registration part 3 about the elevator utilization information registered before elevator boarding, it is not restricted to this. For example, ID authentication by a security gate installed at a location away from the landing, detection information of the building arrival detection unit such as a sensor installed in the building, detection information of the landing arrival detection unit, and information terminal carried by each user It is also possible to acquire elevator usage information.

  Below, the elevator apparatus of the structure which acquires elevator utilization information from the detection information of the apparatus which specifies each individual at the entrance and exit of a building is demonstrated as a group management elevator apparatus which concerns on 2nd Embodiment.

<Elevator apparatus according to the second embodiment of the present invention>
The elevator apparatus according to the second embodiment of the present invention uses the elevator usage information from the detection information of the apparatus that identifies each person at the entrance and exit of a building under the control of a group management system that collectively manages a plurality of elevators. It is a group management elevator device that acquires By acquiring the elevator usage information at the building entrance and landing, it is possible to make the detection timing of the elevator usage information earlier than in the case of the group management elevator device 10 according to the first embodiment. Can be increased.

[System configuration]
FIG. 2 is an example of a configuration diagram illustrating an outline of a system configuration of a group management elevator apparatus according to the second embodiment of the present invention. As shown in FIG. 2, the group management elevator device 50 according to the present embodiment includes an elevator unit 1, a group management control unit (device) 2, a user management unit (device) 5, and a building arrival detection unit (device). ) 6, a landing arrival detection unit (device) 7, and a display unit (device) 8.

(Elevator / Group Management Control)
The elevator unit 1 has the same configuration as the group management elevator device 10 according to the first embodiment. The group management control unit 2 includes a use information management unit 28 in addition to a waiting time evaluation unit 22, an interval evaluation unit 23, a long wait evaluation unit 24, a comprehensive evaluation unit 25, an assigned number machine determination unit 26, and an operation information management unit 27. ing. The usage information management unit 28 manages the prediction data of the waiting time of each user and the number of waiting people on each floor received from the user management unit 5.

  The waiting time evaluation unit 22 evaluates the waiting time of each floor from the waiting time and waiting number of users of each floor and the operation information of each boarding car managed by the usage information management unit 28. The interval evaluation unit 23 operates each future car at regular intervals from the waiting time and waiting number of users on each floor managed by the use information management unit 28 and the operation information of each car. Assess spacing. The long waiting evaluation unit 24 calculates the long waiting time and the long waiting number of people on each floor from the waiting time and waiting number of users on each floor managed by the usage information management unit 28 and the operation information of each boarding machine. Evaluate the waiting load.

  Based on various evaluation values such as the waiting time evaluation unit 22, the interval evaluation unit 23, the long wait evaluation unit 24, etc., the comprehensive evaluation unit 25 determines which unit is most suitable for assigning boarding cars from the viewpoint of waiting time and the like. Comprehensive evaluation of The assigned number determination unit 26 assigns to the boarding number that has the best (high) overall evaluation value of the comprehensive evaluation unit 25. The operation information management unit 27 creates operation information from the assigned number determined by the assigned number determination unit 26 and the elevator use information predicted by the use information prediction unit 21, and transmits the operation information to the user management unit 5.

  The function units (22 to 28) of the group management control unit 2 described above can be realized by software by the processor interpreting and executing a program that realizes each function. Moreover, about each function part (22-28) of the group management control part 2, those part or all can also be implement | achieved by hardware by the design etc. in an integrated circuit, for example.

(Building arrival detection unit / Platform arrival detection unit / Display unit)
The building arrival detection unit 6 includes a sensor such as a camera installed at the entrance of the building, and detects the user's building arrival. The landing arrival detection unit 7 includes a sensor such as a camera installed at the landing of the elevator, and detects the arrival of the user at the landing. The building arrival detection unit 6 and the landing arrival detection unit 7 detect the arrival of the user, and at the same time, acquire the elevator usage information such as the destination floor of the user and the usage information regarding the individual user. Usage information relating to individual users can be acquired from various information terminals such as an ID card and a portable terminal. The display unit 8 is a display unit of a portable terminal owned by the user or a display device installed in a landing or a monitoring room, and presents (provides) elevator operation information to the user.

(User Management Department)
The user management unit 5 includes a usage information acquisition unit 51, a usage information prediction unit 52, a usage information management unit 53, an operation information acquisition unit 54, a usage information transmission unit 55, and a display information notification unit 56. The usage information acquisition unit 51 takes in the elevator usage information such as the user's destination floor from the building arrival detection unit 6 and the landing arrival detection unit 7. The usage information prediction unit 52 determines the waiting time of each user and the waiting time of each floor from the elevator usage information acquired by the usage information acquisition unit 51 and the elevator operation information acquired by the operation information acquisition unit 54 from the group management control unit 2. Predict the number of people.

  The usage information management unit 53 records and manages the current elevator usage information and the elevator usage information predicted by the usage information prediction unit 52. The operation information acquisition unit 54 receives operation information transmitted from the operation information management unit 27 of the group management control unit 2. The usage information transmission unit 55 transmits the elevator usage information predicted by the usage information prediction unit 52 to the group management control unit 2. The display information notification unit 56 outputs elevator operation information and elevator usage information to the display unit 8 installed in a landing or a monitoring room.

  Each of the function units (51 to 56) of the user management unit 5 described above can be realized by software by the processor interpreting and executing a program that realizes each function. Moreover, about each function part (51-56) of the user management part 5, it is also possible to implement | achieve part or all of them by hardware, for example by the design in an integrated circuit.

  As described above, the group management elevator device 50 according to the second embodiment uses the user information and elevator usage information obtained from various information terminals such as ID cards and mobile terminals, and sensors such as cameras, as a user management unit. 5 is managed. In other words, the user management unit 5 has a part of the functions of the group management control unit 2. Thereby, the system change of the group management control part 2 can be suppressed to the minimum. Further, based on the elevator usage information and the elevator operation information obtained from the group management control unit 2, the elevator usage to the mobile terminals and digital signage owned by each user under the management of the user management unit 5 Information and elevator operation information can be displayed.

  Next, a specific example of a control method for the group management elevator apparatus 10 according to the first embodiment having the above-described configuration or the group management elevator apparatus 50 according to the second embodiment will be described. In the following embodiments, the function units (20 to 28) of the group management control unit 2 and the function units (51 to 56) of the user management unit 5 are realized by software and controlled by a CPU (Central Processing Unit). The functions of the function units (20 to 29, 51 to 56) are executed below. However, the control is not limited to the CPU.

[Example 1]
Example 1 is an example of the operation of the landing call duration measurement timer in the usage information prediction unit 21 in FIG. 1 and the usage information prediction unit 52 in FIG. The landing call duration measurement timer is a timer that measures the waiting time of the user at the elevator landing. A landing call duration measurement timer is provided for each floor and service direction. If the system resources are sufficient, it may be provided for each passenger car.

  Here, if a timer is provided for each user and the waiting time is measured, the waiting time of each user can be easily measured. However, there is a problem that system resources become enormous. For example, when 1000 users are generated, it is necessary to provide 1000 timers. Therefore, the waiting time of each user is measured using a conventionally used landing call duration measurement timer.

  FIG. 3 is an example of a flowchart illustrating a flow of operations of the landing call duration measurement timer according to the first embodiment.

  First, the CPU determines whether the landing call duration measurement timer for each floor is activated or stopped (step S1). If the floor is stopped (not activated) (YES in S1), the floor Then, it is determined whether or not there is a new landing call (step S2). When there is a new landing call (YES in S2), the CPU activates a landing call duration measurement timer for the floor to be determined for timer activation (step S3), and when there is no new landing call (NO in S2). ), The process returns to step S1.

  When the CPU determines in step S1 that the floor has already started the timer (NO in S1), all the boarding cars assigned to the floor for which the timer is to be determined serve the floor. It is determined whether it is completed (step S4). When the service is complete (YES in S4), the waiting customer is zero, so the active timer is stopped (step S5). When the service is not complete (NO in S4), Since there is a waiting customer, the process returns to step S1 to continuously start the timer.

  Here, when the number of assigned cars is exhausted, if the landing call duration measurement timer is stopped, there will be a problem that the number of people who could not get on will be counted again from zero seconds when the number of people exceeding the transport capacity is waiting . Therefore, the number of people who can not get on is predicted in advance, and even if people who can not get on are registered again, for example, at the landing call registration unit 3 in FIG. 1, the landing call duration measuring timer is not counted from zero. Prediction of the number of passengers who cannot board may be estimated from the number of people getting on and off at each floor of each boarding machine, or may be estimated from the detection results of sensors provided at each boarding place.

[Example 2]
The second embodiment is an example in which the waiting time of each user is predicted using a landing call duration measurement timer. FIG. 4 is an example of a flowchart illustrating a process flow for predicting the waiting time of each user according to the second embodiment.

  First, the CPU determines whether or not the landing call duration measurement timer on the J direction I floor of each floor is being activated (step S11). Then, when the landing call duration measurement timer is stopped (NO in S11), the CPU waits for a long waiting time according to a later-described table (see FIG. 7) on the floor and a long-waiting person cumulative table described later on the floor. (See FIG. 6) is reset (step S12), and the process returns to step S11. The total waiting number of people on the corresponding floor is stored in the long waiting time total table.

  When the landing call duration measurement timer is activated (YES in S11), the CPU determines whether or not a landing call has occurred on the I-direction floor I and No. K has been assigned (step S13). If no landing call has occurred (NO in S13), the process returns to step S11.

  When a new landing call is generated (YES in S13), the CPU waits for a long waiting number on the floor where the new landing call has been generated (K, J, I) of the floor assigned by the assigned number determination unit 26. Is added to the number of newly generated persons (step S14). Here, the number of newly generated persons is usually one person, but there may be a plurality of persons when group use is designated for group use or when the number of groups is entered.

  Next, the CPU determines whether or not the landing call duration time of the floor where the new landing call is generated is equal to or shorter than the time of the long waiting time recording time table (N) in FIG. 5 (step S15). The determination is repeated until the time is less than or equal to the time in the long waiting time recording time table (N) (NO in S15). FIG. 5 is an example of a diagram showing a long waiting time recording time table (N). N represents the number of people per unit time. In the long waiting number recording time table (N), for example, 10 seconds when N = 0 and 20 seconds when N = 1, a landing call duration for which a long waiting number is desired to be recorded is set in units of 10 seconds, for example.

  As an example, when the landing call duration is 15 seconds and there is an input from a new landing call in the UP direction on the first floor and the first car is assigned, the following processing is performed in steps S14 and S15. . That is, in step S14, one person is added to the long wait number cumulative table (0, 0, 0) of FIG. FIG. 6 is an example of a diagram showing a long waiting time total table (K, J, I).

  In step S15, the long waiting time recording time table (1) shown in FIG. 5 is selected, and the total number of people generated is recorded in the long waiting time number table (0, 0, 0, 1) shown in FIG. That is, in the long waiting time table (0, 0, 0, 0), the number of people generated within 10 seconds of the landing call duration, the long waiting time table (0, 0, 0, 1) The number of people who occurred within the landing call duration 20 seconds is recorded. FIG. 7 is an example of a diagram showing the long waiting time table (K, J, I, N).

  If the CPU determines in step S15 that the floor landing call duration time is less than or equal to the time in the long waiting number recording time table (N) (YES in S15), the long waiting number time table (K, J, I, N) is substituted for the long wait number cumulative table (K, J, I) (step S16), and a series of processing is completed.

[Example 3]
The third embodiment is an example in which long waiting evaluation of each floor is performed using the long waiting time table (K, J, I, N). FIG. 8 is an example of a flowchart illustrating a flow of processing for performing long waiting evaluation of each floor according to the third embodiment.

  First, the CPU determines whether or not the landing call duration timer for each floor is activated (step S21). If it is stopped (NO in S21), the corresponding long waiting time table (K, J) , I, N) and the long waiting time cumulative table (K, J, I) are reset (step S22), and the process returns to step S21.

  When the timer is activated (YES in S21), the CPU calculates the waiting time of each user by subtracting the long waiting time recording time table (N) from the landing call duration time of the corresponding floor. The waiting time of each user is predicted by adding the estimated time until the assigned machine arrives to the waiting time (step S23). Next, the CPU determines whether or not the predicted waiting time of each user exceeds the long waiting determination time (step S24), and if not (NO in S24), the CPU returns to step S21.

  When the predicted waiting time of each user exceeds the long wait determination time (YES in S24), the CPU subtracts the determination time of FIG. 9 from each user's predicted waiting time to determine the future long wait remaining time (N ) Is calculated (step S25). FIG. 9 is an example of a diagram illustrating a long wait determination time table (M) according to traffic demand. Here, the long wait determination time table (M) according to traffic demand in FIG. 9 may use a predetermined value set in advance for each traffic flow mode, but learns the daily usage situation and creates learning for each traffic flow mode. The use of time has the advantage that it is easier to set the determination time according to the characteristics of each building.

  Next, the CPU multiplies the square of the future long waiting time (N) by the number of long waiting people for each long waiting time, thereby obtaining a long waiting load (N for each long waiting time for the corresponding floor). ) Is obtained (step S26). The long waiting number by long waiting time is obtained by subtracting the long waiting time table (K, J, I, N-1) from the long waiting time table (K, J, I, N). It is done. Here, it is assumed that the time to wait for the long wait determination time or more is the time when the user is frustrated (irritated time). Then, the frustration time is assumed to be added with a time weight that is a square of the normal time when no long wait occurs, and evaluation is performed by squaring the future long wait remaining time (N).

  Next, the CPU calculates the total long wait load (N) for each long wait remaining time of the corresponding floor, and calculates the long wait evaluation value of the corresponding floor (step S27). The long wait evaluation value is calculated for all floors or all floors that serve up to the floor where a new user is generated. In other words, the evaluation takes into account not only the new user occurrence floor but also the long wait status of other floors. Next, the CPU calculates a comprehensive evaluation value from the long wait evaluation value of the corresponding floor and other evaluation values such as a waiting time evaluation value and an interval evaluation value, and determines an assigned machine (step S28). A series of processes for performing long waiting evaluation of each floor is completed.

  Here, the waiting time evaluation at the waiting time evaluation unit 22 is an evaluation with respect to the predicted time from the current time to the arrival of the elevator, and the interval evaluation at the interval evaluation unit 23 is an evaluation with respect to the equal interval between the future boarding cars. is there. That is, the waiting time evaluation and the interval evaluation do not take into account the long waiting time and the long waiting number for each user, and only the maximum long waiting time is considered. In this embodiment, since long wait evaluation is performed from information on long wait, not only the long wait time and the long wait number are suppressed, but a floor with a high risk of increasing the wait time is predicted, and other floors are predicted. Risk can be avoided while maintaining a balance with the risk of increased waiting time.

  In the present embodiment, the general user is mainly shown. However, a special user such as a handicapped person or a VIP who meets a pre-registered condition is identified from the user information read from the ID authentication or the mobile terminal. It is also possible to provide special services to special users. For example, there is a case where a special user such as a disabled person or VIP wants to get on a car that arrives as soon as possible and has a sufficient occupancy rate of the users in the car.

  In the case of such a special user, the long wait determination time is set to the minimum determination time (for example, zero seconds), or the determination time is set lower than that of a general user, or the number of users is set as a plurality of users, Increase service priority. As a result, special users such as disabled people and VIPs are regarded as long-waiting users, and a comfortable service can be provided to the special users while taking into consideration the waiting time and long-waiting of general users.

[Example 4]
The fourth embodiment is a modification of the third embodiment, and a new evaluation index is added to the calculation of the long waiting remaining time (N). FIG. 10 is an example of a flowchart illustrating a flow of processing for performing long waiting evaluation of each floor according to the fourth embodiment.

  In the flowchart of FIG. 10, the processing content of step S25A is different from the processing content of step S25 in the flowchart of FIG. In step S25A, the CPU takes into consideration the average boarding prediction time and average walking prediction time recorded in the same table as the long waiting time table (K, J, I, N) as new evaluation indexes, and in the future. The long waiting remaining time (N) is calculated. The average boarding estimated time can be calculated from destination floor information of each user detected in advance.

  By taking the average boarding estimated time as an evaluation index, it is possible to evaluate the service completion time up to the time of arrival at the registered floor. In addition, the travel time in the building can be evaluated by taking into account the average walking prediction time from the detection device or the like installed at a position away from the entrance of the building or the landing to the landing. Furthermore, when the travel time after getting off the unit differs greatly depending on the user, the time after getting off may be included. In this way, in addition to the waiting time at the elevator landing, various movement times in the building are taken into consideration, so that the movement time in the entire building can be shortened.

[Example 5]
The fifth embodiment is a modification of the third embodiment. In the third embodiment, the long wait evaluation is performed according to the waiting time of each user. In this case, the amount of calculation increases because N detailed calculations are required. The fifth embodiment is an example in which substantially the same effect can be obtained while reducing the amount of calculation compared to the third embodiment.

  FIG. 11 is an example of a flowchart illustrating a flow of processing for performing long waiting evaluation of each floor according to the fifth embodiment.

  First, the CPU determines whether or not the landing call duration timer for each floor is being activated (step S31). If it is stopped (NO in S31), the corresponding long waiting time table (K, J) , I, N) and the long waiting number accumulated table (K, J, I) are reset (step S32), and the process returns to step S31.

  When the timer is activated (YES in S31), the CPU calculates the waiting time of each user by subtracting the long waiting time recording time table (N) from the landing call duration time of the corresponding floor. The waiting time of each user is predicted by adding the estimated time until the assigned machine arrives to the waiting time (step S33). Next, the CPU determines whether or not the predicted waiting time of each user exceeds the long wait determination time (step S34), and if not (NO in S34), the CPU returns to step S31.

  When the predicted waiting time of each user exceeds the long wait determination time (YES in S34), the CPU calculates a long waiting time load (step S35). The long waiting time load can be calculated by the square of {(stop call continuation time + assigned station arrival prediction time) −long waiting determination time}. That is, it is assumed that the time to wait beyond the long wait determination time is the time when the user is frustrated (irritated time). And the frustration time assumes that the time weight which becomes the square of the normal time when long waiting does not occur is added, and this is set as a long waiting time load.

  Next, the CPU multiplies the long wait time load by the total long wait number normalized number to obtain a long wait evaluation value (step S36). Here, the total waiting number normalized number is a numerical value obtained by normalizing the total waiting number by the number of passengers in the boarding car. By normalizing the total waiting number with the number of people in the boarding machine, the degree of dependence on each project can be reduced, and evaluation independent of the size of the boarding machine can be performed. Furthermore, for example, if the number of passengers is assigned to the number of passengers x 80%, the number of passengers exceeding the number of passengers is considered to be left behind and may be re-registered. As a result, it is possible to perform a long wait evaluation with high accuracy at the time of congestion.

  Further, the system resource can be minimized when the maximum value of N indicating the size of the table is as small as possible. Therefore, all users who occur in the time exceeding the long waiting time recording time table (N_MAX) which is the maximum recording time are included in the long waiting time recording time table (N_MAX). When the occurrence of users from a specific floor is extremely large, such as when going to work, a plurality of cars are assigned to the specific floor, and the landing call duration time is enlarged.

  In this case, a landing call duration timer may be provided for each car number, or may not be provided for each car number in order to secure system resources. If the number of passengers is not provided separately, including the excess number of people in the maximum value of the table as described above makes it possible to assign vehicles with higher priority to specific floors when there is an extremely large number of users from specific floors. It is possible to eliminate the floor congestion early.

  Here, the long waiting time recording time table (N_MAX) is normally desirably set so that the maximum recording time is, for example, about 5 to 10 minutes. If the landing call continues for more than 5 minutes, there is a high possibility that the landing on the specific floor is congested, and the average waiting time for the entire building will be almost the same as the waiting time on the specific floor, so ride intensively The dispatch of Unit No. leads to a reduction in the average waiting time of the entire building. On the other hand, even in peak work hours, if the building is not congested on a specific floor, the long wait evaluation will be low, making it difficult to assign multiple units to the specific floor, which can suppress departures from small groups and increase the boarding rate. , The waiting time can be shortened.

  In addition, for each boarding station, the sum of long waiting evaluation values for all floors is calculated and added as an evaluation penalty value to the floor to which each boarding station is not assigned, thereby suppressing long waiting times and long waiting numbers. Can be planned. Specifically, for a floor where a new landing call has occurred, a car with a floor with a low long-waiting evaluation is easier to be assigned than a boarding car with a floor with a high long-waiting evaluation. , Long waiting time and long waiting time can be controlled.

  Furthermore, at the time of going to work, it is possible to improve the transportation capacity by setting the upper limit value of the number of stops of each boarding car according to the long waiting evaluation value for each boarding car. For example, the upper limit value of the number of stops of the boarding machine having a large long wait evaluation value is set relatively low, and the upper limit value of the number of stops of the boarding machine having a small long wait evaluation value is set relatively high. Thus, the long waiting user can not only suppress the long waiting time but also shorten the boarding time in the boarding car.

  Finally, the CPU calculates a comprehensive evaluation value from the long waiting evaluation value of the corresponding floor and other evaluation values such as a waiting time evaluation value and an interval evaluation value, and determines an assigned car (step S37). A series of processes for performing long waiting evaluation of each floor is completed.

  Here, the fifth embodiment assumes a normal usage method in which registration is performed once for each user. However, the actual usage includes irregular usage. For example, there are cases where one user registers the same destination floor multiple times and calls a plurality of boarding machines, or only one representative is registered even though a plurality of people get on when using a group. . Therefore, for irregular usage, we do the following.

  First, for a user who registers the same destination floor a plurality of times, the same destination floor is continuously registered a predetermined number of times within a predetermined time by the same registration device (for example, landing call registration unit 3 in FIG. 1). In this case, it is considered that the same person has registered multiple times. Then, the registered number of people is reset to one, a preset number of people, or the number of people learned from daily usage history. By doing so, it is possible to suppress irregular use cases.

  In addition, for the case where only one representative is registered even though multiple passengers are on board, the number of users per registration is classified by floor based on the number of registrations and the number of passengers (passengers). In addition, it is possible to suppress irregular use cases by learning for each traffic flow mode and changing the number of users per registration. Here, the reason for setting for each floor is that the rate of occurrence of irregular use cases varies depending on the tenant or department. In addition, the reason for setting for each traffic flow mode is that irregular use cases are likely to occur when waiting time is long, such as when it is congested. It is because it ends up.

  Moreover, in Example 5, the individual user is not considered, and the user who encounters a long waiting time has not been able to reduce the chance of encountering a long waiting time again. Dissatisfaction can increase. Therefore, as in the case of the group management elevator apparatus 50 (see FIG. 2) according to the second embodiment, a user management unit 5 that records and manages the use history such as the waiting time of each individual is provided. Then, the number of times that the waiting time of the currently registered user exceeds the long wait determination time within the predetermined period in the past is set as the long wait number of the user so as to increase the service priority. Thereby, long waiting concentration to the specific user can be suppressed.

  Examples 6 to 12 described below are examples in which elevator operation information is provided (presented) in a form that is visible to the user.

  The group management elevator device 10 according to the first embodiment and the group management elevator device 50 according to the second embodiment are methods that reduce the risk of an increase in waiting time of the entire building, and therefore, such as specific floors with low usage The waiting time tends to increase on the floor. For example, even in a floor where the same long wait is occurring, a floor with a large number of long waits is given priority, and a floor with a small number of long waits may have a longer waiting time than before.

  Therefore, elevator operation information is provided in a form that is visible to the user. By providing this information, the elevator user can understand why the waiting time is long, so that the elevator user's feeling of frustration when waiting for a long time can be alleviated.

[Example 6]
Example 6 is an example in which the predicted long wait number is provided to the elevator user, and is displayed on a display device (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2) installed at the landing or on the mobile terminal. The number of expected long waiters is displayed in the section. FIG. 12 is an example of an explanatory diagram of a predicted long wait number display according to the sixth embodiment.

  As shown in FIG. 12, in Example 6, the predicted number of waiters for each elevator bank, the predicted number of waiters for each floor service direction, the number of passengers in the unit at the time of departure of each boarding car, and the number of people getting off at the time of arrival. It is trying to display. The long wait number calculated by the long wait evaluation unit 24 is displayed as the predicted long wait number for each bank. By providing this information, users should understand whether the long wait index of the entire building is high or low.

  Based on the current predicted waiting number and the current predicted waiting number for each floor, the predicted future waiting number predicted for each traffic flow mode from the learning results is displayed, and the long waiting time Display fatigue level. Further, a long wait load index (long wait evaluation value) is obtained from the long wait number and fatigue level and displayed. By providing such prediction information, the user can see that the load on the other floor is the same as or higher than that on the other floors, leading to a reduction in discomfort.

  And as information provision by the display of Example 6, the display of the said installation floor is not performed with respect to the floor in which the display apparatus (The operation information display part 4 of FIG. 1 or the display part 8 of FIG. 2) is installed. Like that. Thereby, since a user pays attention only to other floors, he can make a user grasp the use situation of the whole building more. Moreover, by displaying the boarding / exiting situation at the time of departure or arrival, it can be understood that it takes time for boarding / exiting on other floors, and the reason for first-come-first-served can be understood when other than the assigned car arrives first. In addition, when a display device is installed near the landing door of each boarding car, it is possible to display the information of only the assigned car, so that the passing of other car is not known, so the car position may be displayed at the same time.

[Example 7]
Example 7 is an example in which the predicted long wait number is provided to the elevator user, and is displayed on a display device (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2) installed at the landing or on the mobile terminal. The number of expected long waiters is displayed in the section. FIG. 13 is an example of an explanatory diagram of a predicted long wait number display according to the seventh embodiment.

  As shown in FIG. 13, in the seventh embodiment, the current predicted waiting number of all floors, the future predicted waiting number, and the boarding / exiting status are displayed for each boarding car, and only the operation information of the assigned car is displayed. Like to do. The user can understand the long waiting status of all floors and the operation status of the assigned units, and display only the operation information of the assigned units, so that other units in the vicinity do not service and feel uncomfortable. The risk of increasing can be avoided.

[Example 8]
Example 8 is an example in which the number of long-waiting persons and the degree of long-term fatigue are provided to elevator users, and a display device installed at the landing (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2). Or, the number of long-waiting persons and the long-waiting fatigue level are displayed on the display unit of the portable terminal. FIG. 14 is an example of an explanatory diagram of a past long waiting number and long waiting fatigue display according to the eighth embodiment.

  As shown in FIG. 14, in the eighth embodiment, the number of long waiters by service direction in the congestion time zone is displayed. As a result, the user can grasp the long waiting state other than the time zone that is normally used based on the display, and thus the usage time can be adjusted. By displaying the long wait evaluation value calculated from the long wait time and the long wait number instead of the long wait number as the long wait fatigue level, provision of wait information that matches the actual user's feeling can be realized.

[Example 9]
Example 9 is an example in which the past frustration index is provided to the elevator user, and the display device installed in the landing (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2) or the display of the portable terminal The past irritated index is displayed in the section. FIG. 15 is an example of an explanatory diagram of past frustration index display according to the ninth embodiment.

  As shown in FIG. 15, in Example 9, the long wait fatigue degree obtained by adding the long wait time to the long wait number of persons is displayed as a long wait load index. Thereby, the user can grasp | ascertain the encounter rate to the situation which feels discomfort at a glance. As a result, the user can take an action that avoids the use of a time zone in which the encounter rate is high. Also, if the current encounter rate is found to be high, the user can take actions other than waiting for the elevator, so that time can be used effectively.

[Example 10]
The tenth embodiment is an example of providing the elevator user with a long waiting state at the time of registration, and a display device (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2) installed at the landing or a portable terminal The long wait status at the time of past registration is displayed on the display section. FIG. 16 is an example of an explanatory diagram of a long wait status display during registration according to the tenth embodiment.

  As shown in FIG. 16, in Example 10, after the user registers the destination floor and the boarding number is displayed, if it is predicted that the scheduled boarding time will exceed the long waiting determination time, the long waiting user is notified. For example, a message that “the platform is very crowded” is displayed. Thereby, when the destination floor is registered at a position away from the landing, the user's movement to the landing can be delayed spontaneously, so that congestion at the landing can be eased. In addition, since the movement can be delayed spontaneously, even if the movement distance of the assigned car is set slower than the normal walking speed, it is possible to obtain a boarding car in time. For example, when the moving distance is 20 m, a normal walking speed of 1.3 m / sec is changed to 1.0 m / sec, and a boarding car that departs within 20 sec is not an assignment target.

[Example 11]
Example 11 is an example of providing a long waiting state before registration to an elevator user, a display device installed in a landing (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2), or a portable terminal The long wait status before registration in the past is displayed on the display. FIG. 17 is an example of an explanatory diagram of a long wait status display before registration according to the eleventh embodiment.

  In the eleventh embodiment, before the user registers the destination floor, a message indicating a long waiting state of the landing, for example, “the landing is very crowded” or “a long waiting number expected 20 people” is displayed. I have to. As a result, the user can confirm the long waiting state of the landing before registering the destination floor, so that the user can spontaneously delay the movement to the landing as in the tenth embodiment.

  Moreover, like Example 9, the user can take action other than waiting for an elevator. For example, it is possible to temporarily stop moving to the landing and change to another action such as using a vending machine corner, convenience store, smoking area, or staircase in the building, so the increase in congestion at the landing can be reduced. Moreover, it is not necessary to newly install a display device by displaying the long waiting state before registration on a registration device (for example, the landing call registration unit 3 in FIG. 1) or a portable terminal possessed by the user. Furthermore, since predicted numerical values such as the number of long-waiting persons and long-waiting fatigue are displayed, that is, the congestion state of the future landing predicted from the current landing state is displayed, it is highly effective in pre-relaxing the congestion of the landing.

[Example 12]
Example 12 is an example in which the long wait determination time setting is provided to the elevator user, and the display device installed in the landing (the operation information display unit 4 in FIG. 1 or the display unit 8 in FIG. 2) or the mobile terminal. The long wait determination time setting is displayed on the display. FIG. 18 is an example of an explanatory diagram of setting a long wait determination time according to the twelfth embodiment.

  In the twelfth embodiment, when a user performs a specific operation such as an encryption operation or holding an administrator card, the operation target registration device (for example, the landing call registration unit 3 in FIG. 1) or the portable terminal The system shifts to the administrator mode so that the long wait determination time can be changed in the administrator mode. Thereby, the long wait determination time recorded in the external device or the group management control unit 2 can be changed for each time zone. That is, it is possible to change the setting using a device (a registration device or a portable terminal) used by the user without using a dedicated setting tool.

  When displaying the long wait number or the long wait load as in the sixth to twelfth embodiments, the long wait determination time value, which is the determination criterion for long wait, is important, and can be easily changed. Is preferred. In particular, when the user is desired to control the user's behavior by providing the user with a long waiting number or a long waiting load, it can be realized by changing the long waiting determination time. For example, when it is desired to alleviate congestion at the landing during work, the long wait determination time during work is set short so that the long wait number and long wait load are displayed high. Conversely, when it is desired to increase the boarding rate at the time of going to work, the long waiting time determination time at the time of going to work is set to be long so that the long waiting number and the long waiting load are displayed low.

  In addition, this invention is not limited to the Example mentioned above, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, one means of the configuration of a certain embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of a certain embodiment. Further, it is possible to add, delete, and replace other configurations for one means of the configuration of each embodiment.

  DESCRIPTION OF SYMBOLS 1 ... Elevator part, 2 ... Group management control part, 3 ... Platform call registration part, 4 ... Operation information display part, 5 ... User management part, 6 ... Building arrival detection part, 7 ... Landing arrival detection part, 8 ... Display , 10... Group management elevator apparatus according to the first embodiment, 11_1, 11_2,..., 11_n. Elevator (boarding machine), 20, 51 ... Usage information acquisition unit, 21, 52 ... Usage information prediction unit, 22. ... waiting time evaluation part, 23 ... interval evaluation part, 24 ... long wait evaluation part, 25 ... comprehensive evaluation part, 26 ... assigned number machine determination part, 27 ... operation information management part, 28, 53 ... usage information management part, 50 ... Group management elevator apparatus according to the second embodiment, 54 ... Operation information acquisition unit, 55 ... Usage information transmission unit, 56 ... Display information notification unit

Claims (13)

An elevator device that assigns a boarding machine to be serviced to each user based on the user's boarding floor, destination floor, and number of users registered before the elevator boarding,
A prediction unit that predicts the waiting time distribution of all users from the arrival time of the user's platform and the estimated arrival time of each assigned boarding car,
Based on the waiting time distribution of all users, the number of waiting people whose waiting time exceeds the long wait determination time and the long waiting time that exceeds the long wait determination time are calculated for each assigned car number at each platform. And an evaluation unit that evaluates the long wait rate,
An assigned number determination unit that assigns a boarding machine to be serviced for each user based on the evaluation result of the evaluation unit;
An elevator apparatus comprising: The elevator apparatus according to claim 1, wherein the long wait determination time is set based on a time created for each traffic flow mode from a past learning result. The waiting time distribution of all users is calculated from the registered time of each user's destination floor, the landing call duration of each floor, and the estimated arrival time of each boarding car to each floor. The elevator device described. The elevator apparatus according to claim 1, wherein the evaluation unit evaluates the long wait rate by normalizing a waiting number exceeding the long wait determination time with a number of passengers assigned to the assigned boarding car. The said evaluation part sets the said long waiting time determination time to the minimum determination time, and raises a service priority, when the said user is a special user corresponding to the conditions registered previously. The elevator apparatus as described in. When registering the user's boarding floor, destination floor, and number of passengers, if the same destination floor is registered a predetermined number of times within a predetermined time using the same registration device, it is considered that the same person has registered multiple times. The elevator apparatus according to claim 1, wherein the number of users is reset as one person. When registering the user's boarding floor, destination floor, and number of passengers from the landing registration device installed at the landing, the number of users per registration is determined based on the number of registrations and the number of passengers in the landing registration device. The elevator apparatus according to claim 1, wherein learning is performed for each floor and for each traffic flow mode, and the number of users per registration is changed. The prediction unit records the user's past waiting time, and when detecting the number of users whose waiting time in the past predetermined period has exceeded the long wait determination time, the number of times of the user is determined. The elevator apparatus according to claim 1, wherein the elevator apparatus is set as a long waiting number of persons to increase service priority. The elevator apparatus according to claim 1, wherein the total number of persons exceeding the long wait determination time and the number of persons for each floor are presented to the user. The elevator apparatus according to claim 1, wherein a past number of people and a time zone exceeding the long wait determination time or a future time zone exceeding the long wait determination time is presented to the user. When the destination floor is registered by the user, if it is predicted that the long wait determination time will be exceeded, there is a possibility that the user will become a long wait user, or the expected number of long waits will be shown to the user together with the boarding number. The elevator apparatus according to claim 1, wherein the elevator apparatus is presented. The elevator apparatus according to claim 1, wherein when a user performs a specific operation, the long wait determination time can be changed in an administrator mode of a registration apparatus to be operated. A method of controlling an elevator device that assigns a boarding machine to be serviced to each user based on the user's boarding floor, destination floor and number of passengers registered before boarding the elevator,
Predict the waiting time distribution of all users from the arrival time of the user's landing and the estimated arrival time of each assigned boarding car,
Based on the waiting time distribution of all users, the number of waiting people whose waiting time exceeds the long wait determination time and the long waiting time that exceeds the long wait determination time are calculated for each assigned car number at each platform. And evaluate the long wait rate,
A control method for an elevator apparatus, wherein a service number is assigned to each user based on the evaluation result.

Images