JP2022045509A - Elevator integrated control device and assigned car determination method - Google Patents

Abstract

To provide an elevator integrated control device capable of suppressing troubles that users are assigned to a possibly missed car and capable of improving serviceability for users.SOLUTION: An elevator integrated control device collates personal information of users when heading to an elevator landing and allows authorized users to enter the landing. The elevator integrated control device is respectively connected to a security gate to notify the user who is allowed to enter of assigned car information, and to a landing destination-call registration device installed at an elevator landing and to accept a destination floor registration of the user passing the security gate. The elevator integrated control device takes it as an occurrence of a missing car and analyzes its situation when the call is registered by the user passing the security gate from the landing destination-call registration device. The elevator integrated control device adjusts at least one of the allowable number of people assigned to a car and a planar estimated travel time from the security gate to the assigned car by an analysis result and determines the assigned car.SELECTED DRAWING: Figure 4

Description

An embodiment of the present invention relates to an elevator integrated control device and an allocation basket determination method.

A destination floor registration system is known in which a security gate is provided in a passage leading to an elevator landing, and a destination call registration device for registering a destination call when passing through the security gate is provided. In such a destination floor registration system, since there is a flat distance between the point where the call is registered and the elevator car, there is a risk of missing the target elevator.

As a measure to prevent such a delay, there has been a proposal to provide a device for collating whether or not a user has boarded the car. In addition, a device has been proposed in which the car is not started until the completion of boarding is detected by providing a means for comparing the weight of the person passing through the gate with the load inside the car.

International Publication No. 2010/023723 Japanese Unexamined Patent Publication No. 2013-49555

However, in the above-mentioned conventional method, there is a possibility that users are assigned to a car that may be missed, and there is a problem that the occurrence of missed rides cannot be suppressed.

In view of the above circumstances, the embodiment of the present invention is an elevator integrated control device and a method for determining an allocation car, which can suppress a problem of allocating a user to a car that may be missed and improve serviceability to the user. The purpose is to provide.

In the embodiment for achieving the above object, the personal information of the user is collated when heading to the landing of the elevator, and the authorized user is allowed to enter the landing and the entrance is permitted. A security gate that notifies the assigned user of the assigned car information, and a landing destination call registration device that is installed at the landing of the elevator and accepts the destination floor registration of the user who has passed through the security gate, respectively. The departure floor of the user from the operation status recognition unit that receives the car information necessary for recognizing the operation status of the car from the car that is connected and controlled, and the personal information collated by the security gate. , Destination floor, user attribute, authentication information recognition unit that receives authentication information including authentication security gate number, departure floor, destination floor, user attribute, and landing destination call registration from the landing destination call registration device. The landing destination call recognition unit that receives the device number, the landing destination call registration number counting unit that counts the number of calls registered in any unit time in the landing destination call recognition unit, and the landing destination call registration number. From the same car allocation allowable number change unit that changes the allowable number of people allocated to the car of each elevator at the same time according to the count result by the counting unit, and from the car information, the authentication information, and the same car allocation allowable number change unit. It is an elevator integrated control device including a landing destination call allocation car determination unit that determines the allocation car to the user so that the allocation car is within the allowable number of people based on the information.

Further, in another embodiment, when heading to the elevator landing, the personal information of the user is collated to allow the permitted user to enter the landing, and the user who is permitted to enter the landing. Elevators connected to a security gate that notifies the car information assigned to the elevator and a landing destination call registration device that is installed at the landing of the elevator and accepts registration of the destination floor of a user who has passed through the security gate. It is a method of determining the allocation car implemented by the central control device, and the case where the user who has passed the security gate registers the call from the landing destination call registration device is regarded as the occurrence of a delay in the allocation car and the situation is analyzed. However, as a result of the analysis, it is an allocation car determination method in which the allocation car is determined by adjusting at least one of the number of people permitted to allocate the car and at least one of the planar predicted travel times from the security gate to the allocation car.

The explanatory view which shows the structure of the elevator system to which the embodiment of the elevator integrated control device which concerns on this invention is applied. Explanatory drawing which shows an example of the security gate in an embodiment. The explanatory view which shows an example of the landing destination call registration apparatus in embodiment. The block diagram which shows the structure of 1st Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 1st Embodiment. The block diagram which shows the structure of the 2nd Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 2nd Embodiment. The flowchart which shows the processing procedure of 2nd Embodiment. The block diagram which shows the structure of the 3rd Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 3rd Embodiment. The block diagram which shows the structure of 4th Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 4th Embodiment. The block diagram which shows the structure of the 5th Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 5th Embodiment. The block diagram which shows the structure of the 6th Embodiment of the elevator integrated control apparatus which concerns on this invention. The flowchart which shows the processing procedure of 6th Embodiment.

FIG. 1 shows the configuration of an elevator system to which an embodiment of the present invention is applied.

As shown in FIG. 1, the elevator system 1 of the embodiment includes a security gate 10 installed in a building, three elevators (Unit 1 elevator 21, Unit 2 elevator 22, Unit 3 elevator 23), and each unit. Elevators (Unit 1 Elevator 21, Unit 2 Elevator 22, Unit 3 Elevator 23) Elevators 31, 32, 33 installed separately are provided. Further, the unit 1 control device 41, the unit 2 control device 42, and the unit 3 control device 43 for individually controlling the unit elevators 21, 22 and 23 are provided.

Further, a landing destination call registration device 60 is installed at each landing of the elevator, and landing destination floor display devices 71 to 73 are installed near the landing doors of the elevators 21 to 23 of each unit. In each car 31 to 33, display devices 81 to 83 on the destination floor in the car are installed.

The security gate 10 reads the personal information of an individual heading for the elevator landing from a security card such as an employee ID card possessed by the user (visitor), and determines whether or not the individual is a legitimate user. As shown in FIG. 2, each gate is provided with a personal information recognition device 11 and an allocation basket notification device 12.

The personal information recognition device 11 collates the personal information of the security card possessed by the user when heading to the elevator landing, and permits the authorized user to enter the landing.

Allocation car notification device 12. Notifies the assigned car information to users who are permitted to enter.

As shown in FIG. 3, the landing destination call registration device 60 includes a destination call registration device 61 having a key pad for the user to input a destination call, and a liquid crystal display for notifying the user of the assigned car. It is equipped with an assigned car notification device.

Further, the elevator system 1 of the embodiment includes an elevator integrated control device 100 (100A to 100F) that collectively controls the unit unit control devices 41 to 43.

In the elevator system 1, since there is a flat distance between the point where the call is registered and the elevator cars 31 to 33, there is a possibility that the elevator will miss the target elevator.

In order to solve this problem, the elevator integrated control device 100 of the embodiment regards the case where the user who has passed through the security gate 10 registers the call from the landing destination call registration device 60 as the occurrence of a delay in the assigned car. It has a function to analyze the situation. Then, as a result of the analysis, it has a function of adjusting at least one of the number of people permitted to allocate the car and at least one of the two-dimensional predicted travel times from the security gate 10 to the allocation car to determine the allocation car.

<First Embodiment>
<< Configuration of the first embodiment >>
FIG. 4 is a block diagram showing the configuration of the elevator integrated control device 100A of the first embodiment.

In the elevator integrated control device 100A of the first embodiment, the same car allocation allowance is provided for the operation status recognition unit 101, the authentication information recognition unit 102, the landing destination call recognition unit 103, and the unit time landing destination call registration number counting unit 104. It includes a number change unit 105, a landing destination call allocation car determination unit 106, an allocation car information output unit 107, an allocation command output unit 108, and a car call registration unit 109.

The operation status recognition unit 101 receives the car information necessary for recognizing the operation status of the car from the car to be controlled.

The authentication information recognition unit 102 receives authentication information including the departure floor, destination floor, user attributes, and authentication security gate number of the user from the personal information collated by the security gate 10.

The landing destination call recognition unit 103 receives from the landing destination call registration device 60 the departure floor, the destination floor, the attributes of the user, and the number of the landing destination call registration device 60.

The unit time landing destination call registration number counting unit 104 counts the number of calls registered per arbitrary unit time by the landing destination call recognition unit 103.

The same car allocation allowable number change unit 105 changes the allowable number of people simultaneously allocated to the elevator cars 31 to 33 according to the count result by the unit time landing destination call registration number counting unit 104.

The landing destination call allocation car determination unit 106 determines the allocation car to the user so as to be within the allowable number of people in consideration of the information from the same car allocation allowable number change unit 105.

The allocation car information output unit 107 outputs the allocation car information determined by the landing destination call allocation car determination unit 106 to the target allocation car notification device 12.

The allocation command output unit 108 outputs a response command to the allocation car.

The car call registration unit 109 outputs the car call registration information of the destination floor to the assigned car.

<< Processing procedure of the first embodiment >>
Next, the processing procedure of the elevator integrated control device 100A of the first embodiment will be described with reference to the flowchart of FIG.

When entering the building, the elevator user has the security gate 10 read the information of his / her security card to enter the building. The personal information recognition device 11 of the security gate 10 collates the personal information of the elevator user and permits the authorized user to enter the landing.

The operation status recognition unit 101 of the elevator integrated control device 100A receives the car information necessary for recognizing the operation status of the cars 31 to 33 from the cars 31 to 33 to be controlled.

Further, the authentication information recognition unit 102 receives the authentication information including the departure floor, the destination floor, the user's attribute, and the authentication security gate number of the user from the personal information collated by the security gate 10.

The landing destination call recognition unit 103 receives from the landing destination call registration device 60 the departure floor, the destination floor, the attributes of the user, and the number of the landing destination call registration device.

The unit time landing destination call registration number counting unit 104 counts the number of calls registered per arbitrary unit time by the landing destination call recognition unit 103.

The same car allocation allowable number change unit 105 changes the allowable number of people simultaneously allocated to the elevator cars 31 to 33 according to the count result by the unit time landing destination call registration number counting unit 104.

Next, the same car allocation allowable number change unit 105 determines whether or not the changed allowable number is saved (step S1).

When the changed allowable number of people is saved (step S1YES), the stored allowable number of people is set to the current allowable number of people (step S2). When the changed allowable number of people is not saved (step S1NO), the initial value of the preset allowable number of people is set to the current allowable number of people (step S3).

Next, the same car allocation allowable number change unit 105 determines whether or not the number of registered landing destination calls for a unit time is less than the first threshold value (threshold value 1) (step S4). For example, as the first threshold value, when the capacity of the car 31 to 33 is 20 people, about 16 people (about 80% of the capacity) is preferable. The idea is that the number of people should be about 0.0 to 0.5 times the number of departures per unit time. For example, if the unit time is 5 minutes and the average departure interval is 40 seconds, the elevator departs the floor 7.5 times in 5 minutes. It is considered that some people did not board the assigned machine due to factors other than the control of the elevator, and the number of people is allowed up to about 0.5 times the number of departures per unit time.

If the number of landing destination calls registered in the unit time is less than the first threshold value (threshold value 1) (step S4YES), then it is determined whether or not the same allocation or the allowable number of people is the preset upper limit value (step S5). .. The upper limit is 18 people, which is 80% of the capacity of 20 people in the cars 31 to 33.

When the same allowable number of people to be allocated does not exceed the preset upper limit value (step S5NO), n people are added to the current allowable number of people to be allocated to the same car (step S6). It is better to adjust n people little by little, and it is better to have 1 or 2 people.

If the number of landing destination calls registered in a unit time is equal to or greater than the first threshold value (threshold value 1) (step S4NO), the number of registered landing destination calls in a unit time is equal to or greater than the threshold value 1 and less than the second threshold value (threshold value 2). It is determined whether or not (step S7). As the second threshold, the number of people should be about 1.0 to 1.5 times the number of departures per unit time. For example, if the unit time is 5 minutes and the average departure interval is 40 seconds, the elevator departs the floor 7.5 times in 5 minutes. On the other hand, if there is a person who has registered a 7.5-person landing destination floor call, it means that there is a person who could not get on one person each time. Therefore, it is appropriate that the standard for changing the capacity is about 1.0 to 1.5 times the number of departures per unit time.

If the number of landing destination calls registered in the unit time is the threshold value 1 or more and less than the second threshold value (threshold value 2) (step S7YES), the number of people allowed to be assigned to the same car is not changed (step S8). When the number of landing destination calls registered in the unit time is equal to or more than the threshold value 1 but not less than the threshold value 2 (step S7NO), then it is determined whether or not the same allocation or the allowable number of people is the preset lower limit value (step S9). .. The lower limit is preferably about 45 to 55% of the number of people loaded. In the actual building, it is measured that about 55% of people got in even during the work hours when many people could not get in because they had a bag.

If the same car allocation allowable number change unit 105 reaches the preset lower limit value (step S9YES), the unit proceeds to step S8 and does not change the same car allocation allowable number. When the number of people allowed to be assigned to the same car does not reach the preset lower limit (step S9NO), the number of people allowed to be assigned to the same car is subtracted from the current number of people allowed by n (step S10).

When the same car allocation allowable number of people is set in steps S6, S8, and S10, the set number of people is saved as the current same car allocation allowable number of people (step S11).

Then, the landing destination call allocation car determination unit 106 determines the allocation car to the user so as to be within the allowable number of people in consideration of the information from the same car allocation allowable number change unit 105.

In this way, according to the first embodiment, since the allowable number of people to be assigned to the same car can be changed, it is possible to suppress the problem of allocating the user to the car that may be missed, and the serviceability to the user can be suppressed. Can be improved.

<Second Embodiment>
<< Configuration of the second embodiment >>
FIG. 6 is a block diagram showing the configuration of the elevator integrated control device 100B of the second embodiment.

The second embodiment is characterized in that, in addition to the configuration of the first embodiment shown in FIG. 4, the same car allocation allowable number of people learning unit 110 is provided.

The same car allocation allowable number learning unit 110 stores the allowable number of people determined by the same car allocation allowable number changing unit 105 for each day of the week and each time zone, and the same car for each day of the week and each time zone according to the average value for a certain period. Determine the number of people to be allocated. Then, the same car allocation allowable number change unit 105 determines the initial value of the same car allocation allowable number in each time zone based on the learning result of the same car allocation allowable number learning unit 110.

<< Processing procedure of the second embodiment >>
Next, the processing procedure of the elevator integrated control device 100B of the second embodiment will be described with reference to the flowcharts of FIGS. 7 and 8.

As shown in FIG. 7, the same car allocation allowable number change unit 105 determines whether or not the allowable number of people in the time zone learned by the same car allocation allowable number learning unit 110 is stored (step S21).

When the permissible number of people in the time zone learned is saved (step S21YES), the permissible number of people in the time zone is updated from the permissible number of people in the latest time zone and the permissible number of people in the learning (step S22). ).

When the allowable number of people learned in the time zone is not saved (step S21NO), the initial value of the allowable number of people set in advance is set as the allowable number of people for learning (step S23).

When the same number of people to be allocated to the same car learned is obtained by steps S6, S8, and S10, it is saved (step S24).

As shown in FIG. 8, when the allowable number of people by learning is saved (step S31YES), the same car allocation allowable number of people changing unit 105 sets the allowable number of people by learning to the current allowable number of people (step S32). ..

When the allowable number of people by learning is saved (step S31NO), the initial value of the allowable number of people set in advance is set to the current allowable number of people (step S33).

Hereinafter, the processing of steps S34 to S41 is the same as the processing of steps S4 to S11 shown in FIG.

Then, the landing destination call allocation car determination unit 106 determines the allocation car to the user so as to be within the allowable number of people in consideration of the information from the same car allocation allowable number change unit 105.

As described above, according to the second embodiment, the allowable number of people can be changed by learning, the problem of allocating the user to the car that may be missed can be suppressed, and the serviceability to the user is improved. be able to.

<Third Embodiment>
<< Configuration of the third embodiment >>
FIG. 9 is a block diagram showing the configuration of the elevator integrated control device 100C of the third embodiment.

The third embodiment is characterized in that, in addition to the configuration of the second embodiment shown in FIG. 6, a landing congestion status detection unit 111 and a landing congestion status output unit 112 are provided.

When the landing congestion status detection unit 111 recognizes that a certain number or more of landing destination calls are registered in a unit time based on the count result by the unit time landing destination call registration number counting unit 104, the elevator landing is set. Judge that it is crowded.

The landing congestion status output unit 112 outputs the determination result of the landing congestion status detection unit 111 to the security gate 10.

<< Processing procedure of the third embodiment >>
Next, the processing procedure of the elevator integrated control device 100C of the third embodiment will be described with reference to the flowchart of FIG.

The unit time landing destination call registration number counting unit 104 counts the number of calls recognized by the landing destination call recognition unit 103 per arbitrary unit time.

When the landing congestion status detection unit 111 recognizes that a certain number or more of landing destination calls are registered in a unit time based on the count result by the unit time landing destination call registration number counting unit 104, the elevator landing is set. Judge that it is crowded.

That is, the landing congestion status detection unit 111 first determines whether or not the number of landing destination call registrations per unit time is less than the first threshold value (threshold value 1) (step S4).

If the number of registered landing destination calls for a unit time is less than the first threshold value (threshold value 1) (step S51YES), the landing congestion status detection unit 111 clears the landing congestion flag that indicates the congestion status of the landing (step S52). ). If the number of registered landing destination calls for a unit time is equal to or greater than the first threshold value (threshold value 1) (step S51NO), the landing congestion flag is set (step S53).

The above-mentioned information on the landing congestion flag is output from the landing congestion status output unit 112 to the security gate 10 as congestion status information (step S54).

Then, when the landing destination call allocation car determination unit 106 is determined by the landing congestion status detection unit 111 that the landing is congested, the landing destination call allocation car determination unit 106 determines not to execute the allocation for the landing destination call.

As described above, according to the third embodiment, it is possible to consider the degree of congestion at the landing, suppress the problem of allocating the user to the car that may be delayed, and improve the serviceability to the user. be able to.

<Fourth Embodiment>
<< Configuration of Fourth Embodiment >>
FIG. 11 is a block diagram showing a configuration of the elevator integrated control device 100D according to the fourth embodiment.

The fourth embodiment is characterized in that, in addition to the configuration of the third embodiment shown in FIG. 9, a landing destination call registration number counting unit 113 for each destination floor and a user predicted travel time changing unit 114 are provided. ..

The landing destination call registration count unit 113 for each destination floor stores the destination floor information registered by the landing destination call registration device 60, and counts the number of landing destination calls for each destination floor.

The user prediction travel time changing unit 114 is a security gate when the registration by the landing destination call registration device 60 is larger than the preset threshold value based on the count result of the landing destination call registration count unit 113 for each destination floor. Set a long predicted travel time for the user to travel from 10 to the elevator landing. The threshold value here is preferably about 20% to 50% based on the percentage of landing destination floor call registrations with respect to the number of registrations at the security gate. For example, if the landing destination call is registered four times while the tenth floor call is registered ten times at the security gate, the predicted travel time is lengthened.

<< Processing procedure of the fourth embodiment >>
Next, the processing procedure of the elevator integrated control device 100D of the fourth embodiment will be described with reference to the flowchart of FIG.

The landing destination call registration count unit 113 for each destination floor stores the destination floor information registered by the landing destination call registration device 60, and counts the number of landing destination calls for each destination floor.

The user prediction travel time changing unit 114 is a security gate when the registration by the landing destination call registration device 60 is larger than the preset threshold value based on the count result of the landing destination call registration count unit 113 for each destination floor. Set a long predicted travel time for the user to travel from 10 to the elevator landing.

That is, the user predicted travel time changing unit 114 first determines whether or not the changed user predicted travel time is saved (step S61).

When the changed user predicted travel time is saved (step S61YES), the saved user predicted travel time is set to the current user predicted travel time (step S62). When the changed user predicted travel time is not saved (step S61NO), the initial value of the user predicted travel time set in advance is set to the current predicted travel time (step S63).

It is determined whether or not the number of landing destination call registrations of the target floor in the unit time is less than the first threshold value (threshold value 1) (step S64).

If the number of landing destination calls registered for the target floor in the unit time is less than the first threshold value (threshold value 1) (step S64YES), then it is determined whether or not the user predicted travel time is the preset upper limit value. (Step S65). The upper limit depends on the structure of the building and is set based on the distance from the security gate 10 to the elevator landing.

When the user predicted travel time does not exceed the preset upper limit value (step S65NO), the user predicted travel time is added to the current time by n seconds (step S66). As n seconds, a number of seconds of about 5 to 20% of the initial setting value is appropriate.

If the number of registered landing destination calls for the destination floor in the unit time is equal to or greater than the first threshold value (threshold value 1) (step S64NO), the number of registered landing destination calls for the target floor in the unit time is the threshold value 1 or more and the threshold value. It is determined whether or not it is less than 2 (step S67).

If the number of landing destination calls registered in the unit time is the threshold value 1 or more and less than the second threshold value (threshold value 2) (step S67YES), the user predicted travel time is not changed (step S68). When the number of landing destination calls registered in the unit time is equal to or more than the threshold value 1 but not less than the threshold value 2 (step S67NO), it is next determined whether or not the user predicted travel time is a preset lower limit value (step). S69).

If the user predicted travel time has reached the preset lower limit value (step S69YES), the process proceeds to step S68 and the user predicted travel time is not changed. When the user predicted travel time does not reach the preset lower limit value (step S69NO), the user predicted travel time is subtracted by n seconds from the current allowable number of people (step S70).

When the user predicted travel time is set in steps S66, S68, and S70, the set user predicted travel time is saved as the current user predicted travel time (step S71).

Then, the landing destination call allocation car determination unit 106 determines the allocation car from the cars that arrive after the user moves in front of the allocation car, taking into account the information from the user prediction travel time change unit 114. ,
As described above, according to the fourth embodiment, it is possible to consider the travel time of the user, suppress the problem of allocating the user to the car that may be missed, and improve the serviceability to the user. Can be made to.

<Fifth Embodiment>
<< Configuration of Fifth Embodiment >>
FIG. 13 is a block diagram showing a configuration of the elevator integrated control device 100E according to the fifth embodiment.

In the fifth embodiment, in addition to the configuration of the fourth embodiment shown in FIG. 11, the security gate authentication allocation car storage unit 115, the allocation car re-registration number counting unit 116, and the user predicted travel time for each car It is characterized by having a change unit 117.

The security gate authentication time allocation car storage unit 115 stores the personal information authenticated by the security gate 10 and stores the allocation car information for each personal information.

The allocation car re-registration number counting unit 116 is based on the information from the allocation car storage unit 115 at the time of security gate authentication and the authentication result information of the landing destination call registration device 60, and the landing destination call registration device 60 is used for each allocation car. Count the number of times you have been re-registered with.

When the count result of the re-registered number counting unit 116 for each car allocation is larger than the preset threshold value, the user-predicted travel time changing unit 117 for each car is predicted to move the car user from the security gate 10. Set a longer time.

Then, the landing destination call allocation car determination unit 106, taking into account the information from the user prediction travel time change unit 117 for each car, arrives after the user to whom the car has been assigned moves in front of the allocation car. Determine the allocation car from the car.

<< Processing procedure of the fifth embodiment >>
Next, the processing procedure of the elevator integrated control device 100E of the fifth embodiment will be described with reference to the flowchart of FIG.

The security gate authentication time allocation car storage unit 115 inputs the personal information authenticated by the security gate 10 via the authentication information recognition unit 102, stores the input personal information, and stores it as the allocation car information for each personal information. ..

The allocation car re-registration number counting unit 116 is based on the information from the allocation car storage unit 115 at the time of security gate authentication and the authentication result information of the landing destination call registration device 60, and the landing destination call registration device 60 is used for each allocation car. Count the number of times you have been re-registered with.

When the count result of the re-registered number counting unit 116 for each car allocation is larger than the preset threshold value, the user-predicted travel time changing unit 117 for each car is predicted to move the car user from the security gate 10. Change to set a longer time.

In this state, the car-specific user-predicted travel time change unit 117 determines whether or not the changed car-specific user-predicted travel time is saved (step S81).

When the changed user-specific user-predicted travel time is saved (step S81YES), the saved car-specific user-predicted travel time is set to the current predicted travel time (step S82). When the changed user predicted travel time for each car is not saved (step S81NO), the initial value of the preset predicted travel time is set to the current predicted travel time (step S83).

Next, it is determined whether or not the number of landing destination call re-registrations of the allocation car for the unit time is less than the first threshold value (threshold value 1) (step S84).

If the number of landing destination call re-registrations of the assigned car in the unit time is less than the first threshold value (threshold value 1) (step S84YES), then whether or not the user predicted travel time for each car is a preset upper limit value. Is determined (step S85).

When the estimated travel time for each car user does not exceed the preset upper limit value (step S85NO), the predicted travel time for each car user is added to the current time by n seconds (step S86).

If the number of landing destination call re-registrations of the allocated car in the unit time is equal to or greater than the first threshold value (threshold value 1) (step S84NO), the number of landing destination call re-registrations of the allocated car in the unit time is the threshold value 1 or more and , It is determined whether or not it is less than the threshold value 2 (step S87).

If the number of landing destination calls re-registered for the assigned car in the unit time is the threshold value 1 or more and less than the second threshold value (threshold value 2) (step S87YES), the user predicted travel time for each car is not changed (step S88). ). If the number of landing destination call re-registrations of the assigned car in the unit time is equal to or more than the threshold value 1 but not less than the threshold value 2 (step S87NO), then, is it the lower limit value set in advance for the user predicted travel time for each car? It is determined whether or not (step S89).

If the user predicted travel time for each car has reached the preset lower limit value (step S89YES), the process proceeds to step S88 and the predicted travel time for each car user is not changed. When the predicted travel time for each car user has not reached the preset lower limit value (step S89NO), the predicted travel time for each car user is subtracted by n seconds from the current allowable number of people (step S90).

When the user-predicted travel time for each car is set in steps S86, S88, and S90, the set user-predicted travel time for each car is saved as the current user-predicted travel time for each car (step S71).

Then, the landing destination call allocation car determination unit 106, taking into account the information from the user prediction travel time change unit 117 for each car, arrives after the user to whom the car has been assigned moves in front of the allocation car. Determine the allocation car from the car.

As described above, according to the fifth embodiment, it is possible to consider the travel time of the user for each car, suppress the problem of allocating the user to the car that may be missed, and provide service to the user. Can be improved.

<Sixth Embodiment>
<< Configuration of the Sixth Embodiment >>
FIG. 15 is a block diagram showing the configuration of the elevator integrated control device 100F of the sixth embodiment.

The sixth embodiment is characterized in that, in addition to the configuration of the fifth embodiment shown in FIG. 13, an individual-specific landing destination call registration count unit 118 and an individual-specific predicted travel time change unit 119 are provided.

The landing destination call registration count unit 118 for each individual inputs and stores the personal information authenticated by the landing destination call registration device 60 via the landing destination call recognition unit 101, and counts the number of landing destination call registrations for each personal information. do.

If the information from the individual landing destination call registration count unit 118 is greater than the threshold value set in advance for re-registration by the landing destination call registration device 60, the individual predicted travel time changing unit 119 will land from the security gate 10. Set a long estimated arrival time for the user to move to.

<< Processing procedure of the sixth embodiment >>
Next, the processing procedure of the elevator integrated control device 100F of the sixth embodiment will be described with reference to the flowchart of FIG.

The landing destination call registration count unit 118 for each individual inputs and stores the personal information authenticated by the landing destination call registration device 60 via the landing destination call recognition unit 101, and counts the number of landing destination call registrations for each personal information. do.

If the information from the individual landing destination call registration count unit 118 is greater than the threshold value set in advance for re-registration by the landing destination call registration device 60, the individual predicted travel time changing unit 119 will land from the security gate 10. Set a long estimated arrival time for the user (specific individual) to move.

That is, the individual predicted travel time changing unit 119 first determines whether or not the changed individual predicted travel time is saved (step S101).

When the changed individual predicted travel time is saved (step S101YES), the saved individual user predicted travel time is set to the current predicted travel time (step S102). When the changed individual predicted travel time is not saved (step S101NO), the initial value of the user predicted travel time set in advance is set to the current predicted travel time (step S103).

Next, it is determined whether or not the number of individual landing destination call registrations is less than the first threshold value (threshold value 1) (step S104).

If the number of individual landing destination call re-registrations is less than the first threshold value (threshold value 1) (step S104YES), then it is determined whether or not the individual predicted travel time is the preset upper limit value (step S105). ..

When the predicted travel time for each individual does not exceed the preset upper limit value (step S105NO), the predicted travel time for each individual is added to the current time by n seconds (step S106). Next, the number of registrations for individual landing destination calls is reset (step S110).

If the number of individual landing destination call re-registrations is equal to or greater than the first threshold value (threshold value 1) (step S104NO), it is determined whether or not the number of individual landing destination call registrations is equal to or greater than the threshold value 1 and less than the threshold value 2 (step S104NO). Step S107).

If the number of registrations of landing destinations by individual is not less than the threshold value 1 and less than the second threshold value (threshold value 2) (step S107YES), the predicted travel time for each individual is not changed (step S108). When the number of registrations of landing destinations by individual is not less than the threshold value 1 but not less than the threshold value 2 (step S107NO), it is next determined whether or not the predicted travel time for each individual is a preset lower limit value (step S109). ).

If the predicted travel time for each individual has reached the preset lower limit (step S109YES), the process proceeds to step S108, and the predicted travel time for each individual is not changed. When the predicted travel time for each individual has not reached the preset lower limit (step S109NO), the predicted travel time for each individual is subtracted by n seconds from the current allowable number of people (step S110). Next, the number of registrations for individual landing destination calls is reset (step S113).

When the user-predicted travel time for each car is set in steps S106, S108, and S110, the set user-predicted travel time for each car is saved as the current user-predicted travel time for each car (step S112).

Then, the landing destination call allocation car determination unit 106 takes into account the information from the individual predicted travel time change unit 119, and the vehicle to which the cars 31 to 33 are assigned arrives after moving in front of the allocation car. The allocation car is determined from the cars 31 to 33.

As described above, according to the sixth embodiment, it is possible to consider the travel time for each individual, and it is possible to suppress the problem of allocating the user to the cars 31 to 33 which may be delayed, and to the user. Serviceability can be improved.

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

1 ... Elevator system, 10 ... Security gate, 11 ... Personal information recognition device, 12 ... Allocation basket notification device, 21 ... Unit 1 elevator, 22 ... Unit 2 elevator, 23 ... Unit 3 elevator, 31, 32, 33 ... Car , 41 ... Unit 1 control device, 42 ... Unit 2 control device, 43 ... Unit 3 control device, 60 ... Landing destination call registration device, 61 ... Destination call registration device, 62 ... Allocation basket notification device, 71, 72, 73 ... Landing destination floor display device, 81, 82, 83 ... Car interior destination floor display device, 100, 100A-100F ... Elevator control device, 101 ... Landing destination call recognition unit, 102 ... Authentication information recognition unit, 103 ... Operation status recognition Unit, 104 ... Unit time landing destination call registration number counting unit (landing destination call registration number counting unit), 105 ... Same car allocation allowable number of people changing unit, 106 ... Landing destination call allocation car determination unit, 107 ... Allocation car information output unit , 108 ... Allocation command output unit, 109 ... Car call registration unit, 110 ... Same car allocation allowable number of people learning unit, 111 ... Landing congestion status detection unit, 112 ... Landing congestion status output unit, 113 ... Landing destination call registration by destination floor Number of times counting unit, 114 ... User predicted travel time changing unit, 115 ... Security gate authentication allocation car storage unit, 116 ... Allocation car re-registered number counting unit 117 ... User predicted travel time changing unit by car, 118 ... Individual landing destination call registration count unit, 119 ... Individual predicted travel time change unit

Claims (7)

When heading to the elevator landing, the personal information of the user is collated to allow the authorized user to enter the landing, and the information assigned to the authorized user. Is connected to a security gate that notifies the user and a landing destination call registration device that is installed at the elevator landing and accepts the destination floor registration of the user who has passed through the security gate.
The operation status recognition unit that receives the car information necessary for recognizing the operation status of the car from the car to be controlled, and the operation status recognition unit.
An authentication information recognition unit that receives authentication information including the user's departure floor, destination floor, user attributes, and authentication security gate number from the personal information collated by the security gate.
A landing destination call recognition unit that receives the departure floor, destination floor, user attributes, and the number of the landing destination call registration device from the landing destination call registration device.
A landing destination call registration number counting unit that counts the number of calls registered per arbitrary unit time in the landing destination call recognition unit, and a landing destination call registration number counting unit.
The same car allocation allowable number change unit that changes the allowable number of people that can be allocated to the car of each elevator at the same time according to the count result by the landing destination call registration number counting unit, and the same car allocation allowable number change unit.
Based on the car information, the authentication information, and the information from the same car allocation allowable number change unit, the landing destination call allocation car determination unit that determines the allocation car to the user so that the allocation car is within the allowable number of people. ,
Elevator integrated control device equipped with. Allowable number of people to be allocated to the same car The allowable number of people determined by the change department is stored for each day of the week and each time zone, and the allowable number of people to be allocated to the same car is determined by the average value for a certain period for each day of the week and each time zone. Equipped with a number learning department,
The same car allocation allowable number change unit determines the initial value of the same car allocation allowable number in each time zone based on the learning result of the same car allocation allowable number learning unit.
The elevator integrated control device according to claim 1. When it is recognized that a certain number or more of landing destination calls are registered in a unit time based on the count result by the landing destination call registration number counting unit, it is determined that the elevator landing is congested. Situation detector and
Further provided with a landing congestion status output unit that outputs the determination result of the landing congestion status detection unit to the security gate.
When the landing congestion status detection unit determines that the landing is congested, the landing destination call allocation car determination unit determines not to perform allocation to the landing destination call.
The elevator integrated control device according to claim 1 or 2. A landing destination call registration count unit for each destination floor that stores the destination floor information registered by the landing destination call registration device and counts the number of landing destination calls for each destination floor.
If the re-registration by the landing destination call registration device is larger than the preset threshold value based on the count result of the landing destination call registration count unit for each destination floor, the user from the security gate to the elevator landing It is further equipped with a user predicted travel time change unit that sets a longer predicted travel time to move.
The landing destination call allocation car determination unit determines an allocation car from the cars that arrive after the user moves in front of the allocation car, taking into account the information from the user predicted travel time change unit.
The elevator integrated control device according to any one of claims 1 to 3. When the landing destination call registration device has a personal information authentication function and the user performs landing destination call registration by performing personal authentication again from the landing destination call registration device.
A security gate authentication time allocation car storage unit that stores personal information authenticated by the security gate and stores allocation car information for each personal information.
Based on the information from the allocation car storage unit at the time of security gate authentication and the information of the authentication result of the landing destination call registration device, each allocation car counts the number of times re-registered by the landing destination call registration device for each allocation car. Re-registration count part and
If the count result of the re-registered number counting unit for each assigned car is larger than the preset threshold value, the predicted moving time for the user of the car to move from the security gate is set longer. Equipped with a time change section
The landing destination call allocation car determination unit takes into account the information from the car-specific predicted travel time change unit, and from the car that arrives after the user to whom the car is assigned moves in front of the allocation car. Determine the allocation basket,
The elevator integrated control device according to any one of claims 1 to 4. When the landing destination call registration device has a personal information authentication function and the user performs landing destination call registration by performing personal authentication again from the landing destination call registration device.
A personal landing destination call registration count unit that stores personal information authenticated by the landing destination call registration device and counts the number of times for each personal information.
If the information from the landing destination call registration count unit for each individual is greater than the threshold value set in advance for re-registration by the landing destination call registration device, the estimated arrival time for the user to move from the security gate to the landing. Equipped with an individual predicted travel time change part, which sets a long time,
The landing destination call allocation car determination unit allocates the car from the cars that arrive after the user to whom the car is assigned moves in front of the allocation car, taking into account the information from the individual predicted travel time change unit. Decide the basket,
The elevator integrated control device according to any one of claims 1 to 5. When heading to the elevator landing, the personal information of the user is collated to allow the authorized user to enter the landing, and the information assigned to the authorized user. The allocation basket carried out by the elevator control control device connected to the security gate that notifies the information and the landing destination call registration device that is installed at the elevator landing and accepts the destination floor registration of the user who has passed through the security gate. It ’s a decision method,
The case where the user who has passed through the security gate registers the call from the landing destination call registration device is regarded as the occurrence of a delay in the allocation car, and the situation is analyzed.
As a result of the analysis, the allocation car is determined by adjusting at least one of the number of people allowed to allocate the car and at least one of the estimated plane travel times from the security gate to the allocation car.
How to determine the allocation basket.

Images