WO2020261361A1 - Elevator group management system - Google Patents

Elevator group management system Download PDF

Info

Publication number
WO2020261361A1
WO2020261361A1 PCT/JP2019/025065 JP2019025065W WO2020261361A1 WO 2020261361 A1 WO2020261361 A1 WO 2020261361A1 JP 2019025065 W JP2019025065 W JP 2019025065W WO 2020261361 A1 WO2020261361 A1 WO 2020261361A1
Authority
WO
WIPO (PCT)
Prior art keywords
destination floor
car
floor
group management
destination
Prior art date
Application number
PCT/JP2019/025065
Other languages
French (fr)
Japanese (ja)
Inventor
颯 棚林
孝道 星野
訓 鳥谷部
知明 前原
貴大 羽鳥
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to JP2021528682A priority Critical patent/JP7169448B2/en
Priority to PCT/JP2019/025065 priority patent/WO2020261361A1/en
Priority to CN201980097826.5A priority patent/CN114007971B/en
Publication of WO2020261361A1 publication Critical patent/WO2020261361A1/en

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00—Control systems of elevators in general
    • B66B1/02—Control systems without regulation, i.e. without retroactive action
    • B66B1/06—Control systems without regulation, i.e. without retroactive action electric
    • B66B1/14—Control systems without regulation, i.e. without retroactive action electric with devices, e.g. push-buttons, for indirect control of movements
    • B66B1/18—Control systems without regulation, i.e. without retroactive action electric with devices, e.g. push-buttons, for indirect control of movements with means for storing pulses controlling the movements of several cars or cages

Definitions

  • the present invention relates to an elevator group management system.
  • the elevator group management system provides more effective operation services to users by treating a plurality of cars as one group. Specifically, when multiple cars are managed as one group and the landing destination floor is registered on a certain floor, one of the most suitable cars is selected from this group, and the above car is used as the above. Perform the process of allocating the landing call.
  • Destination floor reservation system type group management (hereinafter referred to as destination floor reservation type group management) is a group management method in which the destination floor is registered with the destination floor registration device provided at the platform before boarding the car. Is.
  • destination floor reservation type group management In general elevator group management, an up or down call is registered at the platform and the destination floor is registered after getting in the car that arrived, whereas in the destination floor reservation type group management, the user's destination floor Is known in advance, so it is possible to allocate a more optimal car according to the destination floor.
  • Patent Document 1 the number of registered calls registered in the destination floor registration device at the landing is counted, and if the number of floors registered for the landing destination floor button exceeds a predetermined value, another car is provided.
  • Technology is disclosed that additionally allocates, predicts the congestion situation of the landing before the allocated car arrives, allocates multiple cars appropriately according to the congestion state, and reduces the leftover of the user. ..
  • a stable car call occurrence probability is calculated based on the traffic flow of an elevator, and cars are assigned, or by destination floor.
  • a technology for predicting car calls in consideration of designated landing call information and allocating cars in response to changes in traffic flow more accurately is disclosed.
  • the present invention provides an elevator group management system that can improve operation efficiency by increasing the number of passengers in the same car having the same destination floor.
  • the elevator group management device that manages the operation of a plurality of cars serving on a plurality of floors and the destination floor of the elevator user are registered at the landing.
  • the elevator group management device is provided with a destination floor registration device provided, and the elevator group management device includes an allocation processing unit that allocates the registered destination floor to a predetermined car among the plurality of cars, and a destination floor of an elevator user that will occur in the future.
  • the destination floor prediction processing unit that predicts the above, the destination floor call fullness determination unit that determines whether the number of registered people allocated in the predetermined car is equal to or greater than the first predetermined value, and the newly registered destination floor are described above.
  • the same floor determination unit that determines whether the destination floor is the same as the destination floor already registered in the predetermined car, and determines whether the number of floors of the destination floor already registered in the predetermined car is equal to or greater than the second predetermined value.
  • the elevator group management device determines whether the number of registrants assigned to the predetermined car is equal to or more than the third predetermined value.
  • the destination floor information of the user generated in the future output by the destination floor prediction processing unit is used. It is characterized by further including a future destination floor determination unit that excludes the allocation of a predetermined car.
  • an elevator group management system capable of improving operation efficiency by increasing the number of passengers in the same car having the same destination floor. Issues, configurations and effects other than those described above will be clarified by the description of the following embodiments.
  • FIG. 1 It is an overall block diagram of the destination floor reservation type group management system of Example 1 which concerns on one Example of this invention. It is a figure which shows the output data of the destination floor prediction processing unit which constitutes the elevator group management apparatus shown in FIG. 1, and is an example of a destination floor prediction table. It is a flowchart which shows the processing flow of the allocation target car determination part which constitutes the elevator group management apparatus shown in FIG. It is a figure which shows the output data structure of the destination floor number grasping part constituting the elevator group management apparatus shown in FIG. 1, and is an example of the registered number table A by the car departure floor and the destination floor for car A. It is a figure which shows the output data structure of the destination floor number grasping part constituting the elevator group management apparatus shown in FIG.
  • FIG. 1 is an overall configuration diagram of a destination floor reservation type group management system according to a first embodiment of the present invention.
  • the car is assigned according to the destination floor, and the user gets into the car. It is a group management using a method of servicing the destination floor.
  • the main configurations of the elevator group management system 30 are three cars A1a, a car B1b, and a car C1c, a car control device A2a for controlling each car, a car control device B2b, and a car control device C2c.
  • the destination floor registration device 4 When the destination floor is registered, the destination floor registration device 4 displays the car name received from the destination floor and the boarding car information transmitting unit 18, displays the car name for a certain period of time, and then returns to the initial screen. .. Therefore, in order to inform the operator who operates the destination floor registration device 4 of the registered destination floor and the assigned car name, it is assumed that all the users who come to the platform individually register the destination floor. ing.
  • the destination floor input to the destination floor registration device 4 is received by the destination floor information receiving unit 5 in the elevator group management device 3.
  • the predetermined value setting unit 6 sets a predetermined value used for determining the car to be allocated. This predetermined value is, for example, a determination value used for determining a full car.
  • the determination value is set to a value of 20 people when the occupancy rate of 80% is applied to a car with a capacity of 24 people.
  • the predetermined value used for determining the car to be allocated can be changed by the maintenance staff or the customer according to the local usability. Actually, it is desirable to determine a congested state, a normal state, or a quiet state according to traffic demand, and select a value corresponding to the result as a predetermined value. For example, in a congested state, by setting a high predetermined value for determining that the car is full, more people can be transported by one car and the transportation capacity can be improved. However, in normal times and off-peak hours, if many users are assigned to one car as in the case of congestion, users may be reluctant to ride in the crowded car and users may not board the assigned car. Therefore, by lowering the predetermined value for determining that the car is full, it is possible to provide an easy-to-use and lean operation service.
  • the elevator group management device 3 includes a destination floor information receiving unit 5, a predetermined value setting unit 6, a destination floor number grasping unit 7, a car information input / output unit 8, a learning processing unit 9, and a destination floor prediction processing. It is composed of a unit 10, an allocation target car determination unit 11, an allocation processing unit 17, and a passenger car information transmission unit 18.
  • the destination floor number grasping unit 7 uses the allocation result, for example, the registered number table A20 for each car departure floor and destination floor for car A, which will be described in detail later. Data is created by counting up the corresponding values in the registered number table B21 for each car departure floor and destination floor for car B in FIG. 5 and the registered number table C22 for each departure floor and destination floor for car C in FIG. .. That is, the registered number table 20, 21, 22 for each departure floor and destination floor for each car is provided with a table for each car, and the number of registered people is managed for each departure floor and each destination floor.
  • the car information input / output unit 8 measures the current position of the car, the open / closed state of the door, and the current load in the car by the load sensor in the car, and grasps the approximate number of people. Further, the car information input / output unit 8 transmits the allocation result referred to by the allocation processing unit 17 to the car control device A2a, the car control device B2b, and the car control device C2c, thereby responding to the service request of the user. To dispatch.
  • the learning processing unit 9 accumulates the number of passengers and the number of passengers getting off each floor in the past, which can be obtained by referring to the car information input / output unit 8. From the information of users that changes from moment to moment, it is judged what kind of elevator traffic demand is currently. Elevator traffic demand indicates the distribution of the number of passengers getting on and off the building. For example, when many users get on the entrance and get off at each floor, the traffic demand of the elevator when going to work in the building, and when the users get on from each floor and get off at the cafeteria floor, lunch in the building. The traffic demand of the elevator at that time, the state where the user gets on from each floor and gets off at the entrance floor is judged as the traffic demand of the elevator at the time of leaving work in the building.
  • the determination of elevator traffic demand is not limited to this.
  • By judging the traffic demand of the current elevator it becomes possible to predict from which floor the future user will get on and on which floor. For example, if a user is enrolled only on the 3rd floor of a 10-story building, the daily traffic demand of the elevator is learned from the usage situation of getting on from the entrance floor and getting off on the 3rd floor. Therefore, when the traffic demand of the elevator at the time of commuting is detected, it can be predicted that there is a user who moves to the 3rd floor out of the 10th floor. Using such data, it is predicted whether or not there will be users by departure floor and destination floor.
  • the number of passengers getting on / off, the current number of passengers, the running state of the elevator, the state of the door, etc. are detected, and the traffic demand of the elevator indicating the number of passengers getting on and off each floor in the building is calculated. It may be detected and the presence or absence of users by departure floor and destination floor may be predicted based on the characteristics of the traffic demand of this elevator.
  • the destination floor prediction processing unit 10 refers to the learning processing unit 9 and manages whether or not there are users by departure floor and destination floor in the destination floor prediction table 19 which will be described in detail later.
  • the above-mentioned destination floor number grasping unit 7, car information input / output unit 8, learning processing unit 9, and destination floor prediction processing unit 10 are, for example, processors such as a CPU (Central Processing Unit) (not shown) and various programs. It is realized by a ROM that stores data, a RAM that temporarily stores data in the calculation process, and a storage device such as an external storage device, and a processor such as a CPU reads and executes various programs stored in the ROM, and the execution result. The calculation result is stored in the RAM or an external storage device.
  • processors such as a CPU (Central Processing Unit) (not shown) and various programs. It is realized by a ROM that stores data, a RAM that temporarily stores data in the calculation process, and a storage device such as an external storage device, and a processor such as a CPU reads and executes various programs stored in the ROM, and the execution result.
  • the calculation result is stored in the RAM or an external storage device.
  • the allocation target car determination unit 11 constituting the elevator group management device 3 includes a destination floor call full determination unit 12, the same floor determination unit 13, a stop floor number suppression processing unit 14, and a future ride evaluation start processing unit. It is composed of 15 and a future destination floor determination unit 16.
  • the allocation target car determination unit 11 excludes the car satisfying the predetermined condition from the allocation target car, limits the selected car, and gives priority to the car satisfying the predetermined condition as the allocation target. Performs discrimination processing such as priority car selection.
  • the destination floor call fullness determination unit 12, the same floor determination unit 13, the stop floor number suppression processing unit 14, the future sharing evaluation activation processing unit 15, and the future destination floor determination unit 16 are, for example, CPUs (Central Processing Units) (not shown). It is realized by a processor such as Unit), a ROM that stores various programs, a RAM that temporarily stores data of the calculation process, and a storage device such as an external storage device, and various processors such as a CPU are stored in the ROM. The program is read and executed, and the calculation result, which is the execution result, is stored in the RAM or an external storage device.
  • CPUs Central Processing Units
  • the destination floor call fullness determination unit 12 is provided by the destination floor number grasping unit 7 on the floors from the departure floor to the destination floor, and the registered number table for each departure floor and destination floor. That is, the number of registered people table A20 by car departure floor and destination floor for car A, the number of registered people table B21 by car departure floor and destination floor for car B, and the number of registered people table C22 by car departure floor and destination floor for car C Therefore, it is judged that the car in which the number of registered people is equal to or more than the predetermined value A is full, and the car is excluded from the allocation because no more passengers can board.
  • the predetermined value A is set to 20 people when the occupancy rate of 80% is applied to a car with a capacity of 24 people.
  • the same floor determination unit 13 currently selects a car for which the same destination floor as the destination floor registered by the destination floor registration device 4 has already been registered as a priority car.
  • the reason for giving priority to cars with the same destination floor instead of deciding the allocation is that if there are two or more cars with the same destination floor, it is more appropriate to consider the registration status and position of the two cars. This is to allocate to the basket.
  • the stop floor number suppression processing unit 14 limits the number of destination floors assigned to one car to prevent the boarding time from becoming long.
  • the stop floor number suppression processing unit 14 temporarily allocates the departure floor and the destination floor registered this time to each car, and at that time, the car whose stop floor number of the car is the predetermined value B or more is excluded from the allocation.
  • the predetermined value B is set to four floors as the upper limit of the number of stopped floors.
  • the future sharing evaluation activation processing unit 15 excludes cars whose number of people registered in the car is less than the predetermined value C on the floors from the departure floor to the destination floor to be processed by the future destination floor determination unit 16. .. This process is to prevent users with the same destination floor from getting into different cars due to fullness unless the cars are assigned a certain number of people at the time of registration. It is done in.
  • a predetermined value C is used as a value for determining whether the number of people assigned to the car is close to full. For example, the predetermined value C is set to a value of 18 people. Since the car having a predetermined value A or more is excluded from the cars to be allocated by using the destination floor call fullness determination unit 12, the predetermined value C is set to a value having a relationship of predetermined value A> predetermined value C. Is desirable.
  • the future destination floor determination unit 16 determines that the destination floor of the user who will occur in the future is the same floor as the destination floor assigned to the car for the car determined to be near full by the future ride evaluation activation processing unit 15. Alternatively, if the destination floor of the user that occurs in the future is the same floor as the destination floor of the user who registered this time, the allocation exclusion of the car is excluded in order to promote the sharing of users on the same destination floor to the same car. Do. In the above process, in order to promote the sharing, it is necessary to use the prediction information of the time that the user can board before the car departs. This is because, for example, even if the user's prediction information after 5 minutes is used, if the car departs from the departure floor after 3 minutes, it is impossible to share the vehicle. Therefore, the presence or absence of the destination floor of the user that occurs before the car departs is used in the above processing.
  • the allocation processing unit 17 constituting the elevator group management device 3 refers to the determination processing results such as allocation exclusion and priority car selection of each car from the allocation target car determination unit 11, and is a car information input / output unit among the allocation target cars. From the car information obtained from 8, the most suitable car is assigned.
  • the boarding car information transmitting unit 18 refers to the allocation result from the allocation processing unit 17 and transmits the boarding car information to the destination floor registration device 4.
  • FIG. 2 is a diagram showing output data of the destination floor prediction processing unit constituting the elevator group management device 3, and shows an example of a destination floor prediction table.
  • the destination floor prediction processing unit 10 constituting the elevator group management device 3 creates a destination floor prediction table 19. As shown in FIG. 2, it manages the occurrence / non-occurrence prediction information of users who move from each departure floor to each destination floor every minute. In this example, it is predicted whether or not there will be users for each departure floor and destination floor after 1 minute and 2 minutes with respect to the current time, and 0/1 data is stored in the table data. "0" stores prediction information that has not occurred, and "1" stores prediction information that has occurred.
  • the 7:31 record stores user occurrence prediction information such as from the departure floor 3rd floor to the destination floor 2nd floor, 4th floor, 5th floor, 6th floor, and 7th floor.
  • the 7:32 record stores user occurrence prediction information such as from the departure floor 3rd floor to the destination floor 1st floor, 4th floor, 5th floor, 6th floor, and from the departure floor 4th floor to the destination floor 1st floor.
  • the 7:33 record stores user occurrence prediction information from the departure floor 3rd floor to the destination floor 2nd floor, 4th floor, 7th floor, and the like.
  • the 7:34 record stores user occurrence prediction information such as from the first floor of the departure floor to the second floor of the destination floor, and from the third floor of the departure floor to the first floor of the destination floor, the second floor, the third floor, and the sixth floor.
  • the prediction information of the destination floor prediction table 19 When using the destination floor prediction table 19, it is necessary to use the prediction information of the destination floor prediction table 19 for the time when the user can board before the car departs. This is because, for example, even if the user's prediction information after 5 minutes is used, if the car departs from the departure floor after 3 minutes, it is impossible to share the vehicle.
  • the current time is 7:30. If the car A is predicted to depart after 2 minutes, the prediction information in the destination floor prediction table 19 uses the records of 7:31 and 7:32. If the car B1b is expected to depart after 1 minute and 30 seconds, the forecast information in the destination floor forecast table 19 uses the record at 7:31. If the car C1c is expected to depart after 30 seconds, the prediction information in the destination floor prediction table 19 is not used.
  • the prediction information in the destination floor prediction table 19 is , Not available.
  • the case where the occurrence / presence / absence prediction information is managed every minute is shown, but the present invention is not limited to this, and for example, the occurrence / presence / absence prediction information may be managed every 30 seconds.
  • FIG. 4 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table A for each car departure floor and destination floor for car A.
  • FIG. 5 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table B for each car departure floor and destination floor for car B.
  • FIG. 6 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table C for each car departure floor and destination floor for car C.
  • the destination floor number grasping unit 7 is a registration number table for each departure floor and destination floor for each car, that is, a registration number table A20 for each car departure floor and another destination floor for car A, and a registration for each car departure floor and destination floor for car B.
  • a number table B21 and a registered number table C22 for each car departure floor and destination floor for car C are created.
  • the registered number table A20 for each car departure floor and destination floor for car A the number of people moving from the departure floor 1st floor to the destination floor 4th floor is 20 and the departure floor 6th floor to the destination floor 2nd floor. It means that one person moves to the car, one person moves from the fourth floor of the departure floor to the third floor of the destination floor, and the car A1a (Fig.
  • the registered number table B21 for each car departure floor and destination floor for car B the number of people moving from the departure floor 1st floor to the destination floor 5th floor is 10 and the departure floor 3rd floor to the destination floor. It means that the number of people moving to the 5th floor is 2 and the number of people moving from the 5th floor of the departure floor to the 1st floor of the destination floor is 1 and is assigned to the car B1b (Fig. 1).
  • the registered number table C22 for each car departure floor and destination floor for car C shows that the number of people moving from the first floor of the departure floor to the sixth floor of the destination floor is 18 and is assigned to the car C1c. Represent.
  • FIG. 3 is a flowchart showing a processing flow of the allocation target car determination unit 11 constituting the elevator group management device 3 shown in FIG.
  • the destination floor call fullness determination unit 12 constituting the allocation target car determination unit 11 is set on the floors from the departure floor to the destination floor when the destination floor is registered. If the number of people registered in the car is equal to or greater than the specified value A, the car will be excluded from the allocation. On the other hand, for a car in which the number of people registered in the car is less than the predetermined value A (a car that does not correspond), the process of the next step S12 is performed.
  • step S12 the same floor determination unit 13 constituting the allocation target car determination unit 11 selects the car as the priority car for the currently registered destination floor and the car for which the same destination floor has already been registered.
  • the process of the next step S13 is executed for the car. For example, when registration is made from the 3rd floor of the departure floor to the 5th floor of the destination floor, if the 5th floor of the destination floor is already registered in the car B1b from any of the 1st to 4th floors of the departure floor, the car B1b has priority. Select as a basket.
  • the process of the next step S13 is executed for the car C1c. ..
  • step S13 the stop floor number suppression processing unit 14 constituting the allocation target car determination unit 11 temporarily allocates the destination floor registered this time to each car, and at that time, the car whose stop floor number of the car is a predetermined value B or more is assigned. Exclude allocation.
  • the process of the next step S14 is executed for the car whose stop floor number is less than the predetermined value B.
  • the predetermined value B which is the upper limit of the number of stopped floors, is a floor with four stopped floors, when registration is performed from the departure floor 3rd floor to the destination floor 5th floor, the 7th floor, 6th floor, and 3rd floor are already registered.
  • step S14 the future ride evaluation activation processing unit 15 constituting the allocation target car determination unit 11 is registered in the car on the floors from the departure floor to the destination floor when the destination floor is registered. Cars whose number of people is less than the predetermined value C are not excluded from the allocation, and the cars are subject to allocation.
  • the process of the next step S15 is executed for the car in which the number of people registered in the car is the predetermined value C or more.
  • the number of passengers in the car B1b upon arrival on the 3rd floor is as follows from the number of registered passengers table B21 (Fig. 5) by departure floor and destination floor for car B. Since it is predicted that there are 12 people and the number is less than 18 of the predetermined value C, the following steps S15 and S16 are not executed for the car B1b and are subject to allocation. From the registered number of passengers table C22 (Fig. 6) by departure floor and destination floor for car C, the number of passengers in car C1c when arriving on the 3rd floor is estimated to be 18, which is 18 or more of the predetermined value C. The following processes of step S15 and step S16 are executed for C1c.
  • step S15 the future destination floor determination unit 16 constituting the allocation target car determination unit 11 is a destination already registered with the user's destination floor that will occur in the future on the departure floor predicted by the destination floor prediction processing unit 10. Cars with matching floors will be deallocated.
  • the process of the next step S16 is executed for the car in which the destination floor of the user that occurs in the predicted departure floor and the destination floor already registered do not match.
  • Destination floor prediction table 19 departure floor by car, registration number table by destination floor, car departure floor, registration number table A20, car B, departure floor, destination floor, registration number table B21 , Car C1c, which is the target of step S15, when registration is performed from the departure floor 3rd floor to the destination floor 7th floor at 7:30 from the registered number table C22 by departure floor and destination floor for car C. If it is expected that the passenger will depart one minute later, the destination floor prediction table 19 predicts that users from the departure floor 3rd floor to the destination floor 6th floor will occur at 7:31, so the 6th floor that will occur in the future will be the destination floor. In order to allow users to ride in the car C1c, the car C1c is allocated and excluded.
  • step S16 performs allocation exclusion when the destination floor of the user that occurs in the future and the destination floor currently registered match. In order to allow future users who have the same destination floor as the registered user to ride in an empty car, the allocation of the car will be excluded. Similar to the process of step S15, this process is performed when the predicted user predicts that it will occur by the departure of the car that can be assigned at the time of process of step S16.
  • Destination floor prediction table 19 departure floor by car, registered number of people by destination floor, car for car A, registered number of people by destination floor, table A20, car for car B, registered number of people by destination floor, B21 , Car for car C Departure floor by destination floor Registration number table C22, from 7:30, when registration is done from the departure floor 3rd floor to the destination floor 7th floor, the car B1b to be allocated is 1 minute If it is expected to depart later, the car C1c is allocated and excluded because the destination floor prediction table 19 predicts that users from the departure floor 3rd floor to the destination floor 7th floor will occur at 7:31, and the 7th floor will be assigned to the car B1b. Share the users who have it as the destination floor.
  • steps S15 and S16 may be configured to carry out either one or both. Further, when both step S15 and step S16 are carried out, the processes may be performed in the order of step S15 and step S16, or may be processed in the order of step S16 and step S15.
  • step S15 the car is subject to allocation.
  • each of the above configurations, functions, processing units and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit.
  • each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function.
  • Information such as programs, tables, and files that realize each function can be placed in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

Abstract

Provided is an elevator group management system such that it is possible to improve operational efficiency by increasing the number of passengers with the same destination floor in the same car.　This elevator group management system comprises: an elevator group management device that manages the operation of a plurality of cars that serve a plurality of floors; and a destination floor registration device that registers the destination floor of elevator users and is disposed at a landing. This elevator group management device has: an allocation processing unit that allocates the registered destination floor to a predetermined car of the plurality of cars; a destination floor prediction processing unit that predicts the destination floors of future elevator users; a destination floor call fullness determination unit that determines whether the number of registrants allocated in the predetermined car is equal to or greater than a first predetermined value; and a processing unit for suppressing the number of stop floors, which determines whether the number of the destination floors already registered in the predetermined car is equal to or greater than a second predetermined value. This elevator group management device is also equipped with: a future ridesharing evaluation activation determination unit that determines whether the number of registrants allocated to the predetermined car is equal to or greater than a third predetermined value; and a future destination floor determination unit that uses the destination floor information of future users output by the destination floor prediction processing unit to exclude the allocation of a predetermined car having a value that is determined to be equal to or greater than the third predetermined value by the future ridesharing evaluation activation determination unit.

Description

エレベーター群管理システムElevator group management system
　本発明は、エレベーター群管理システムに関する。 The present invention relates to an elevator group management system.
　エレベーター群管理システムは、複数台のかごを１つのグループとして扱うことで、利用者に対してより効果的な運行サービスを提供する。　
　具体的には、複数台のかごを１つのグループとして管理し、ある階にて乗り場行先階が登録された場合に、このグループの中から最適なかごを１つ選択して、そのかごに上記乗り場呼びを割当てる処理を実施する。 The elevator group management system provides more effective operation services to users by treating a plurality of cars as one group.
Specifically, when multiple cars are managed as one group and the landing destination floor is registered on a certain floor, one of the most suitable cars is selected from this group, and the above car is used as the above. Perform the process of allocating the landing call.
　行先階予約システム式の群管理（以下、行先階予約式群管理と称する）とは、かごに乗車する前に、乗り場に設けられている行先階登録装置で行先階を登録する方式の群管理である。　
　一般のエレベーター群管理では、乗り場で上または下方向の呼びを登録して、到着したかごに乗った後に行先階を登録するのに対して、行先階予約式群管理では、利用者の行先階が事前に分かるので、行先階に応じてより最適なかごを割当てることができる。 Destination floor reservation system type group management (hereinafter referred to as destination floor reservation type group management) is a group management method in which the destination floor is registered with the destination floor registration device provided at the platform before boarding the car. Is.
In general elevator group management, an up or down call is registered at the platform and the destination floor is registered after getting in the car that arrived, whereas in the destination floor reservation type group management, the user's destination floor Is known in advance, so it is possible to allocate a more optimal car according to the destination floor.
　例えば、特許文献１には、乗り場にて行先階登録装置に登録された呼び登録個数を計数して、この乗り場行先階釦登録階床数が所定値を超えた場合には、別のかごを追加で割当てることや、割当てられたかごが到着する前に乗り場の混雑状況を予測し、その混雑状態に応じて複数のかごを適切に割当て、利用者の積み残しを軽減する技術が開示されている。 For example, in Patent Document 1, the number of registered calls registered in the destination floor registration device at the landing is counted, and if the number of floors registered for the landing destination floor button exceeds a predetermined value, another car is provided. Technology is disclosed that additionally allocates, predicts the congestion situation of the landing before the allocated car arrives, allocates multiple cars appropriately according to the congestion state, and reduces the leftover of the user. ..
　また、行先階予約式群管理ではないが、例えば、特許文献２には、エレベーターの交通流に基づいて、安定したかご呼びの発生確率を演算し、かごの割当てを行うことや、行先階別に指定された乗り場呼び情報を考慮してかご呼びを予測し、より正確に交通流の変化へ対応したかごの割当てを行う技術が開示されている。 Further, although it is not a destination floor reservation type group management, for example, in Patent Document 2, a stable car call occurrence probability is calculated based on the traffic flow of an elevator, and cars are assigned, or by destination floor. A technology for predicting car calls in consideration of designated landing call information and allocating cars in response to changes in traffic flow more accurately is disclosed.
特開２０１０－１５００１３号公報Japanese Unexamined Patent Publication No. 2010-150013 特開平１１－２０９０１０号公報Japanese Unexamined Patent Publication No. 11-209010
　しかしながら、特許文献１および特許文献２に記載される技術では、予測した将来発生する利用者の行先階情報を用いて、同一行先階の利用者を、既に同一の行先階へ向かうことが決定しているかごへの乗り合いを促進することについては何ら考慮されていない。これにより、当該かごが満員となった後、予測した利用者が発生した場合、満員のかごに割当てることは不可となるため、別のかごに割当てされ、同一の行先階に２台以上向かうこととなり、全体の停止階数が増加し運行効率が低下する虞がある。 However, in the techniques described in Patent Document 1 and Patent Document 2, it is determined that the users on the same destination floor are already headed to the same destination floor by using the predicted future destination floor information of the users. No consideration is given to facilitating riding in the car. As a result, if the predicted number of users occurs after the car is full, it will not be possible to assign it to a full car, so it will be assigned to another car and two or more cars will be headed to the same destination floor. Therefore, there is a risk that the total number of stopped floors will increase and the operation efficiency will decrease.
　そこで、本発明は、同一行先階を有する利用者の同一かごへの乗り合い人数を増加させることで、運行効率を向上し得るエレベーター群管理システムを提供する。 Therefore, the present invention provides an elevator group management system that can improve operation efficiency by increasing the number of passengers in the same car having the same destination floor.
　上記課題を解決するため、本発明に係るエレベーター群管理システムは、少なくとも、複数階床にサービスする複数台のかごの運行を管理するエレベーター群管理装置とエレベーター利用者の行先階が登録され乗り場に設けられる行先階登録装置とを備え、前記エレベーター群管理装置は、前記複数台のかごのうち所定のかごに前記登録された行先階を割当てる割当て処理部と、将来発生するエレベーター利用者の行先階の予測を行う行先階予測処理部と、前記所定のかごにおいて割当てられた登録人数が第一の所定値以上であるか判定する行先階呼び満員判定部と、新たに登録された行先階が前記所定のかごに既に登録された行先階と同一であるかを判定する同一階判定部と、前記所定のかごに既に登録されている行先階の階床数が第二の所定値以上かを判定する停止階数抑制処理部と、を備えるエレベーター群管理システムにおいて、前記エレベーター群管理装置は、前記所定のかごに割当てられた登録者数が第三の所定値以上かを判定する将来乗り合い評価起動判定部と、前記将来乗り合い評価起動判定部が第三の所定値以上であると判定した前記所定のかごについて、前記行先階予測処理部が出力する将来発生する利用者の行先階情報を用いて前記所定のかごの割当て除外を行う将来行先階判定部と、を更に備えることを特徴とする。 In order to solve the above problems, in the elevator group management system according to the present invention, at least the elevator group management device that manages the operation of a plurality of cars serving on a plurality of floors and the destination floor of the elevator user are registered at the landing. The elevator group management device is provided with a destination floor registration device provided, and the elevator group management device includes an allocation processing unit that allocates the registered destination floor to a predetermined car among the plurality of cars, and a destination floor of an elevator user that will occur in the future. The destination floor prediction processing unit that predicts the above, the destination floor call fullness determination unit that determines whether the number of registered people allocated in the predetermined car is equal to or greater than the first predetermined value, and the newly registered destination floor are described above. The same floor determination unit that determines whether the destination floor is the same as the destination floor already registered in the predetermined car, and determines whether the number of floors of the destination floor already registered in the predetermined car is equal to or greater than the second predetermined value. In the elevator group management system including the stop floor number suppression processing unit, the elevator group management device determines whether the number of registrants assigned to the predetermined car is equal to or more than the third predetermined value. With respect to the unit and the predetermined car determined by the future ride evaluation activation determination unit to be equal to or higher than the third predetermined value, the destination floor information of the user generated in the future output by the destination floor prediction processing unit is used. It is characterized by further including a future destination floor determination unit that excludes the allocation of a predetermined car.
　本発明によれば、同一行先階を有する利用者の同一かごへの乗り合い人数を増加させることで、運行効率を向上し得るエレベーター群管理システムを提供することが可能となる。　
　上記した以外の課題、構成及び効果は、以下の実施形態の説明により明らかにされる。 According to the present invention, it is possible to provide an elevator group management system capable of improving operation efficiency by increasing the number of passengers in the same car having the same destination floor.
Issues, configurations and effects other than those described above will be clarified by the description of the following embodiments.
本発明の一実施例に係る実施例１の行先階予約式群管理システムの全体構成図である。It is an overall block diagram of the destination floor reservation type group management system of Example 1 which concerns on one Example of this invention. 図１に示すエレベーター群管理装置を構成する行先階予測処理部の出力データを示す図であって、行先階予測テーブルの一例である。It is a figure which shows the output data of the destination floor prediction processing unit which constitutes the elevator group management apparatus shown in FIG. 1, and is an example of a destination floor prediction table. 図１に示すエレベーター群管理装置を構成する割当て対象かご判定部の処理フローを示すフローチャートである。It is a flowchart which shows the processing flow of the allocation target car determination part which constitutes the elevator group management apparatus shown in FIG. 図１に示すエレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＡ用のかご出発階別行先階別登録人数テーブルＡの一例である。It is a figure which shows the output data structure of the destination floor number grasping part constituting the elevator group management apparatus shown in FIG. 1, and is an example of the registered number table A by the car departure floor and the destination floor for car A. 図１に示すエレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＢ用のかご出発階別行先階別登録人数テーブルＢの一例である。It is a figure which shows the output data structure of the destination floor number grasping part constituting the elevator group management apparatus shown in FIG. 1, and is an example of the registered number table B by the car departure floor and the destination floor for car B. 図１に示すエレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＣ用のかご出発階別行先階別登録人数テーブルＣの一例である。It is a figure which shows the output data structure of the destination floor number grasping part which comprises the elevator group management apparatus shown in FIG. 1, and is an example of the registered number table C by the car departure floor and the destination floor for car C.
　以下、図面を用いて本発明の実施例について説明する。 Hereinafter, examples of the present invention will be described with reference to the drawings.
　[エレベーター群管理システム]　
　図１は、本発明の一実施例に係る実施例１の行先階予約式群管理システムの全体構成図である。本実施例に係るエレベーター群管理システム３０は、利用者が乗り場で行先階登録装置４を用いて行先階を登録し、その行先階に応じてかごを割当て、利用者がかごに乗り込んだ後、行先階にサービスする方式を用いた群管理である。　
　エレベーター群管理システム３０の主な構成は、３台のかごＡ１ａ、かごＢ１ｂ、およびかごＣ１ｃと、それぞれのかごを制御するかご制御装置Ａ２ａ、かご制御装置Ｂ２ｂ、およびかご制御装置Ｃ２ｃと、かご制御装置Ａ２ａ、かご制御装置Ｂ２ｂ、およびかご制御装置Ｃ２ｃへ運転指令を出力するエレベーター群管理装置３と、複数階床の乗り場に設置される行先階登録装置４から成る。 [Elevator group management system]
FIG. 1 is an overall configuration diagram of a destination floor reservation type group management system according to a first embodiment of the present invention. In the elevator group management system 30 according to the present embodiment, after the user registers the destination floor at the landing using the destination floor registration device 4, the car is assigned according to the destination floor, and the user gets into the car. It is a group management using a method of servicing the destination floor.
The main configurations of the elevator group management system 30 are three cars A1a, a car B1b, and a car C1c, a car control device A2a for controlling each car, a car control device B2b, and a car control device C2c. It includes an elevator group management device 3 that outputs an operation command to the device A2a, a car control device B2b, and a car control device C2c, and a destination floor registration device 4 installed at a landing on a plurality of floors.
　この行先階登録装置４は、行先階を登録すると、その行先階と乗車かご情報送信部１８から受信した、かご名を表示し、一定時間かご名を表示した後、初期画面に戻るものである。したがって、行先階登録装置４を操作する操作者に対して、登録した行先階と割当てかご名を案内するため、乗り場に来た利用者全員が、個別に、行先階を登録することが想定されている。　
　行先階登録装置４に入力された行先階は、エレベーター群管理装置３内の行先階情報受信部５にて受信される。所定値設定部６では、割当て対象かごの判別に用いる所定値を設定する。この所定値は、例えば、満員かごの判別に使用する判定値である。ここで判定値は、定員２４人のかごに対して乗車率８０％を適用した場合、２０人という値が設定される。 When the destination floor is registered, the destination floor registration device 4 displays the car name received from the destination floor and the boarding car information transmitting unit 18, displays the car name for a certain period of time, and then returns to the initial screen. .. Therefore, in order to inform the operator who operates the destination floor registration device 4 of the registered destination floor and the assigned car name, it is assumed that all the users who come to the platform individually register the destination floor. ing.
The destination floor input to the destination floor registration device 4 is received by the destination floor information receiving unit 5 in the elevator group management device 3. The predetermined value setting unit 6 sets a predetermined value used for determining the car to be allocated. This predetermined value is, for example, a determination value used for determining a full car. Here, the determination value is set to a value of 20 people when the occupancy rate of 80% is applied to a car with a capacity of 24 people.
　また、割当て対象かごの判別に用いる所定値は、現地の使い勝手に応じて、保守員或いはお客様によって変更可能とすることが好ましい。実際には交通需要により、混雑状態、通常状態、或いは閑散状態の判定を行い、その結果に対応した値を所定値として選定することが望ましい。　
　例えば混雑状態であれば、かご内が満員と判定する所定値を高く設定することで一つのかごによって、より多くの人を輸送可能となり輸送能力の向上が図られる。但し、通常時や閑散時の場合は、混雑時と同様に一つのかごに多くの利用者を割当てた場合、混雑したかごへの乗車を嫌がり、割当てされたかごに利用者が乗り込まないことが考えられるため、満員と判定する所定値を低くすることで、使い勝手が良く無駄の無い運行サービスが図られる。 Further, it is preferable that the predetermined value used for determining the car to be allocated can be changed by the maintenance staff or the customer according to the local usability. Actually, it is desirable to determine a congested state, a normal state, or a quiet state according to traffic demand, and select a value corresponding to the result as a predetermined value.
For example, in a congested state, by setting a high predetermined value for determining that the car is full, more people can be transported by one car and the transportation capacity can be improved. However, in normal times and off-peak hours, if many users are assigned to one car as in the case of congestion, users may be reluctant to ride in the crowded car and users may not board the assigned car. Therefore, by lowering the predetermined value for determining that the car is full, it is possible to provide an easy-to-use and lean operation service.
　[エレベーター群管理装置]　
　図１に示すように、エレベーター群管理装置３は、行先階情報受信部５、所定値設定部６、行先階人数把握部７、かご情報入出力部８、学習処理部９、行先階予測処理部１０、割当て対象かご判定部１１、割当て処理部１７、および、乗車かご情報送信部１８より構成されている。 [Elevator group management device]
As shown in FIG. 1, the elevator group management device 3 includes a destination floor information receiving unit 5, a predetermined value setting unit 6, a destination floor number grasping unit 7, a car information input / output unit 8, a learning processing unit 9, and a destination floor prediction processing. It is composed of a unit 10, an allocation target car determination unit 11, an allocation processing unit 17, and a passenger car information transmission unit 18.
　行先階人数把握部７は、割当て処理部１７にて割当てかごが決定した際に、割当て結果より、例えば詳細後述する、図４のかごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、図５のかごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、および図６のかごＣ用のかご出発階別行先階別登録人数テーブルＣ２２の該当する値をカウントアップしデータを作成する。すなわち、かご別出発階別行先階別登録人数テーブル２０、２１、２２には、かご別にテーブルを設けて、出発階別、行先階別に、登録人数を管理する。また、かご情報入出力部８を参照し各かごが各階に到着した際、かご別出発階別行先階別登録人数テーブルである、かごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２の登録人数の該当階の値をリセットする。 When the allocation processing unit 17 determines the allocation car, the destination floor number grasping unit 7 uses the allocation result, for example, the registered number table A20 for each car departure floor and destination floor for car A, which will be described in detail later. Data is created by counting up the corresponding values in the registered number table B21 for each car departure floor and destination floor for car B in FIG. 5 and the registered number table C22 for each departure floor and destination floor for car C in FIG. .. That is, the registered number table 20, 21, 22 for each departure floor and destination floor for each car is provided with a table for each car, and the number of registered people is managed for each departure floor and each destination floor. In addition, when each car arrives at each floor with reference to the car information input / output unit 8, the number of registered people table by car departure floor and destination floor for car A, the number of registered people table by car departure floor and destination floor A20, The value of the corresponding floor of the number of registered people in the car departure floor-specific destination floor registration number table B21 for car B and the registration number table C22 by car departure floor and destination floor for car C is reset.
　かご情報入出力部８では、かごの現在位置やドアの開閉状態やかご内の荷重センサによるかご内の現在の積載荷重を測定し、おおよその人数を把握する。また、かご情報入出力部８は、割当て処理部１７より参照した割当て結果を、かご制御装置Ａ２ａ、かご制御装置Ｂ２ｂ、かご制御装置Ｃ２ｃに送信することで、利用者のサービス要求に対応するかごを配車する。 The car information input / output unit 8 measures the current position of the car, the open / closed state of the door, and the current load in the car by the load sensor in the car, and grasps the approximate number of people. Further, the car information input / output unit 8 transmits the allocation result referred to by the allocation processing unit 17 to the car control device A2a, the car control device B2b, and the car control device C2c, thereby responding to the service request of the user. To dispatch.
　学習処理部９は、かご情報入出力部８を参照し得られた、過去の各階の乗車人数、降車人数を蓄積する。時々刻々と変化する利用者の情報から、現在どのようなエレベーターの交通需要であるか判断する。エレベーターの交通需要とは、ビルにおける利用者の乗車人数、降車人数の分布を示す。例えば、エントランスから多くの利用者が乗車し、各階で降車するような状態をビルにおける出勤時のエレベーターの交通需要、各階から利用者が乗車し、食堂階で降車するような状態をビルにおける昼食時のエレベーターの交通需要、各階から利用者が乗車し、エントランス階で降車するような状態をビルにおける退勤時のエレベーターの交通需要と判定する。なお、エレベーターの交通需要の判定は、これに限られるものではない。　
　現在のエレベーターの交通需要を判断することで、将来の利用者がどの階から乗車し、どの階で降車することが予測可能となる。例えば１０階建てのビルに対して、３階にのみ利用者が在籍していた場合、日々のエレベーターの交通需要は、エントランス階から乗車し、３階で降車する利用状況が学習される。よって出勤時のエレベーターの交通需要を検出すると、１０階のうち、３階へ移動する利用者が存在することが予測可能となる。このようなデータを用いて、出発階別行先階別利用者の発生の有無を予測する。 The learning processing unit 9 accumulates the number of passengers and the number of passengers getting off each floor in the past, which can be obtained by referring to the car information input / output unit 8. From the information of users that changes from moment to moment, it is judged what kind of elevator traffic demand is currently. Elevator traffic demand indicates the distribution of the number of passengers getting on and off the building. For example, when many users get on the entrance and get off at each floor, the traffic demand of the elevator when going to work in the building, and when the users get on from each floor and get off at the cafeteria floor, lunch in the building. The traffic demand of the elevator at that time, the state where the user gets on from each floor and gets off at the entrance floor is judged as the traffic demand of the elevator at the time of leaving work in the building. The determination of elevator traffic demand is not limited to this.
By judging the traffic demand of the current elevator, it becomes possible to predict from which floor the future user will get on and on which floor. For example, if a user is enrolled only on the 3rd floor of a 10-story building, the daily traffic demand of the elevator is learned from the usage situation of getting on from the entrance floor and getting off on the 3rd floor. Therefore, when the traffic demand of the elevator at the time of commuting is detected, it can be predicted that there is a user who moves to the 3rd floor out of the 10th floor. Using such data, it is predicted whether or not there will be users by departure floor and destination floor.
　なお、乗車／降車人数、現在の乗り人数、エレベーターの走行状態、ドアの状態などエレベーターの状態を検出し、建造物内の各階で乗車する乗客人数及び降車する乗客人数を表すエレベーターの交通需要を検出し、このエレベーターの交通需要の特徴に基づいて、出発階別行先階別利用者の発生の有無を予測しても良い。 In addition, the number of passengers getting on / off, the current number of passengers, the running state of the elevator, the state of the door, etc. are detected, and the traffic demand of the elevator indicating the number of passengers getting on and off each floor in the building is calculated. It may be detected and the presence or absence of users by departure floor and destination floor may be predicted based on the characteristics of the traffic demand of this elevator.
　行先階予測処理部１０は、学習処理部９を参照し、出発階別行先階別利用者の発生の有無を、詳細後述する行先階予測テーブル１９にて管理している。 The destination floor prediction processing unit 10 refers to the learning processing unit 9 and manages whether or not there are users by departure floor and destination floor in the destination floor prediction table 19 which will be described in detail later.
　ここで、上述の行先階人数把握部７、かご情報入出力部８、学習処理部９、および、行先階予測処理部１０は、例えば、図示しないＣＰＵ（Ｃｅｎｔｒａｌ　Ｐｒｏｃｅｓｓｉｎｇ　Ｕｎｉｔ）などのプロセッサ、各種プログラムを格納するＲＯＭ、演算過程のデータを一時的に格納するＲＡＭ、外部記憶装置などの記憶装置にて実現されると共に、ＣＰＵなどのプロセッサがＲＯＭに格納された各種プログラムを読み出し実行し、実行結果である演算結果をＲＡＭ又は外部記憶装置に格納する。 Here, the above-mentioned destination floor number grasping unit 7, car information input / output unit 8, learning processing unit 9, and destination floor prediction processing unit 10 are, for example, processors such as a CPU (Central Processing Unit) (not shown) and various programs. It is realized by a ROM that stores data, a RAM that temporarily stores data in the calculation process, and a storage device such as an external storage device, and a processor such as a CPU reads and executes various programs stored in the ROM, and the execution result. The calculation result is stored in the RAM or an external storage device.
　＜割当て対象かご判定部＞　
　図１に示すように、エレベーター群管理装置３を構成する割当て対象かご判定部１１は、行先階呼び満員判定部１２、同一階判定部１３、停止階数抑制処理部１４、将来乗り合い評価起動処理部１５、および、将来行先階判定部１６より構成されている。割当て対象かご判定部１１は、所定の条件を満たしたかごを割当て対象かごから除外し、選択されるかごを限定する割当て除外や、所定の条件を満たしたかごを優先して割当ての対象とする優先かご選択などの判別処理を行う。　
　ここで、行先階呼び満員判定部１２、同一階判定部１３、停止階数抑制処理部１４、将来乗り合い評価起動処理部１５、および、将来行先階判定部１６は、例えば、図示しないＣＰＵ（Ｃｅｎｔｒａｌ　Ｐｒｏｃｅｓｓｉｎｇ　Ｕｎｉｔ）などのプロセッサ、各種プログラムを格納するＲＯＭ、演算過程のデータを一時的に格納するＲＡＭ、外部記憶装置などの記憶装置にて実現されると共に、ＣＰＵなどのプロセッサがＲＯＭに格納された各種プログラムを読み出し実行し、実行結果である演算結果をＲＡＭ又は外部記憶装置に格納する。 <Assignment target car judgment unit>
As shown in FIG. 1, the allocation target car determination unit 11 constituting the elevator group management device 3 includes a destination floor call full determination unit 12, the same floor determination unit 13, a stop floor number suppression processing unit 14, and a future ride evaluation start processing unit. It is composed of 15 and a future destination floor determination unit 16. The allocation target car determination unit 11 excludes the car satisfying the predetermined condition from the allocation target car, limits the selected car, and gives priority to the car satisfying the predetermined condition as the allocation target. Performs discrimination processing such as priority car selection.
Here, the destination floor call fullness determination unit 12, the same floor determination unit 13, the stop floor number suppression processing unit 14, the future sharing evaluation activation processing unit 15, and the future destination floor determination unit 16 are, for example, CPUs (Central Processing Units) (not shown). It is realized by a processor such as Unit), a ROM that stores various programs, a RAM that temporarily stores data of the calculation process, and a storage device such as an external storage device, and various processors such as a CPU are stored in the ROM. The program is read and executed, and the calculation result, which is the execution result, is stored in the RAM or an external storage device.
　行先階呼び満員判定部１２は、行先階の登録が行われた際、出発階から行先階までの階において、行先階人数把握部７より提供されるかご別出発階別行先階別登録人数テーブル、すなわち、かごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２より、登録人数が所定値Ａ以上であるかごは満員と判定しこれ以上は利用客が乗り込めないとして当該かごを割当て除外とする。例えば、所定値Ａは定員数２４名のかごに対して、乗車率８０％を適用した場合、２０人という値が設定される。 When the destination floor is registered, the destination floor call fullness determination unit 12 is provided by the destination floor number grasping unit 7 on the floors from the departure floor to the destination floor, and the registered number table for each departure floor and destination floor. That is, the number of registered people table A20 by car departure floor and destination floor for car A, the number of registered people table B21 by car departure floor and destination floor for car B, and the number of registered people table C22 by car departure floor and destination floor for car C Therefore, it is judged that the car in which the number of registered people is equal to or more than the predetermined value A is full, and the car is excluded from the allocation because no more passengers can board. For example, the predetermined value A is set to 20 people when the occupancy rate of 80% is applied to a car with a capacity of 24 people.
　同一階判定部１３は、現在、行先階登録装置４にて登録された行先階と、同一の行先階が既に登録済みであるかごを、優先かごとして選択する。同一行先階を有するかごに割当て決定とせず優先とする理由は、同じ行先階を有するかごが二つ以上あった場合、その二つのかごの内、かごの登録状況や位置を考慮してより適切なかごに割当てを行うためである。 The same floor determination unit 13 currently selects a car for which the same destination floor as the destination floor registered by the destination floor registration device 4 has already been registered as a priority car. The reason for giving priority to cars with the same destination floor instead of deciding the allocation is that if there are two or more cars with the same destination floor, it is more appropriate to consider the registration status and position of the two cars. This is to allocate to the basket.
　停止階数抑制処理部１４は、一つのかごに割当てる行先階の数を制限することで、乗車時間が長くなることを防止する。停止階数抑制処理部１４では、今回登録された出発階と行先階を仮に各かごに割当てし、その際かごの停止階数が所定値Ｂ以上であるかごは割当て除外とする。例えば、所定値Ｂは停止階数上限値として４つの階という値が設定される。 The stop floor number suppression processing unit 14 limits the number of destination floors assigned to one car to prevent the boarding time from becoming long. The stop floor number suppression processing unit 14 temporarily allocates the departure floor and the destination floor registered this time to each car, and at that time, the car whose stop floor number of the car is the predetermined value B or more is excluded from the allocation. For example, the predetermined value B is set to four floors as the upper limit of the number of stopped floors.
　将来乗り合い評価起動処理部１５は、出発階から行先階までの階において、そのかごに登録されている人数が所定値Ｃ未満となるかごは、将来行先階判定部１６による処理の対象外とする。本処理は、登録が行われた時点である程度の人数が割当てられているかごでなければ、満員のために同一行先階を有する利用者が別々のかごに乗り込む事象が発生することを防止するために行われる。かごに割当てられた人数が満員近くであるか判別する値として所定値Ｃを用いる。例えば、所定値Ｃは１８人という値が設定される。なお、所定値Ａ以上のかごは、行先階呼び満員判定部１２を用いて割当て対象かごから除外しているため、所定値Ｃは、所定値Ａ＞所定値Ｃの関係となる値を設定することが望ましい。 The future sharing evaluation activation processing unit 15 excludes cars whose number of people registered in the car is less than the predetermined value C on the floors from the departure floor to the destination floor to be processed by the future destination floor determination unit 16. .. This process is to prevent users with the same destination floor from getting into different cars due to fullness unless the cars are assigned a certain number of people at the time of registration. It is done in. A predetermined value C is used as a value for determining whether the number of people assigned to the car is close to full. For example, the predetermined value C is set to a value of 18 people. Since the car having a predetermined value A or more is excluded from the cars to be allocated by using the destination floor call fullness determination unit 12, the predetermined value C is set to a value having a relationship of predetermined value A> predetermined value C. Is desirable.
　将来行先階判定部１６は、将来乗り合い評価起動処理部１５にて満員近くと判別されたかごに対して、将来発生する利用者の行先階が当該かごに割当てられている行先階と同一階、或いは将来発生する利用者の行先階が今回登録を行った利用者の行先階と同一階の場合に、同一行先階の利用者を同じかごに割当てる乗り合いを促進するため、当該かごの割当て除外を行う。　
　上記処理において、乗り合いを促進するためには、かごが出発するまでに利用者が乗車可能な時間の予測情報を利用する必要がある。これは、例えば５分後の利用者の予測情報を利用しても、かごが３分後に出発階を出発しては、乗り合いが不可能であるためである。よって、当該かごが出発するまでに発生する利用者の行先階の有無を上記処理にて用いる。 The future destination floor determination unit 16 determines that the destination floor of the user who will occur in the future is the same floor as the destination floor assigned to the car for the car determined to be near full by the future ride evaluation activation processing unit 15. Alternatively, if the destination floor of the user that occurs in the future is the same floor as the destination floor of the user who registered this time, the allocation exclusion of the car is excluded in order to promote the sharing of users on the same destination floor to the same car. Do.
In the above process, in order to promote the sharing, it is necessary to use the prediction information of the time that the user can board before the car departs. This is because, for example, even if the user's prediction information after 5 minutes is used, if the car departs from the departure floor after 3 minutes, it is impossible to share the vehicle. Therefore, the presence or absence of the destination floor of the user that occurs before the car departs is used in the above processing.
　エレベーター群管理装置３を構成する割当て処理部１７は、割当て対象かご判定部１１より各かごの割当て除外や優先かご選択などの判別処理結果を参照し、割当て対象かごのうち、かご情報入出力部８から得られるかご情報より、最適なかごを割当てる。　
　乗車かご情報送信部１８は、割当て処理部１７より割当て結果を参照し、乗車かご情報を行先階登録装置４に送信する。 The allocation processing unit 17 constituting the elevator group management device 3 refers to the determination processing results such as allocation exclusion and priority car selection of each car from the allocation target car determination unit 11, and is a car information input / output unit among the allocation target cars. From the car information obtained from 8, the most suitable car is assigned.
The boarding car information transmitting unit 18 refers to the allocation result from the allocation processing unit 17 and transmits the boarding car information to the destination floor registration device 4.
　＜行先階予測テーブル＞　
　図２にエレベーター群管理装置３を構成する行先階予測処理部の出力データを示す図であって、行先階予測テーブルの一例を示す。　
　エレベーター群管理装置３を構成する行先階予測処理部１０は、行先階予測テーブル１９を作成している。図２に示すように、１分毎に各出発階から各行先階へ移動する利用者の発生有無予測情報について管理している。本例では、現在時刻に対して、１分後、２分後、の各出発階別行先階別の利用者の発生有無について予測し、テーブルのデータには０／１のデータが格納され、「０」は発生無し、「１」は発生有りの予測情報が格納される。具体的に本実施例において、７：３１のレコードには出発階３階から行先階２階、４階、５階、６階、７階等の利用者の発生予測情報を格納する。７：３２のレコードには出発階３階から行先階１階、４階、５階、６階、出発階４階から行先階１階等の利用者の発生予測情報が格納される。７：３３のレコードには出発階３階から行先階２階、４階、７階等の利用者の発生予測情報が格納される。７：３４のレコードには出発階１階から行先階２階、出発階３階から行先階１階、２階、３階、６階等の利用者の発生予測情報が格納される。 <Destination floor forecast table>
FIG. 2 is a diagram showing output data of the destination floor prediction processing unit constituting the elevator group management device 3, and shows an example of a destination floor prediction table.
The destination floor prediction processing unit 10 constituting the elevator group management device 3 creates a destination floor prediction table 19. As shown in FIG. 2, it manages the occurrence / non-occurrence prediction information of users who move from each departure floor to each destination floor every minute. In this example, it is predicted whether or not there will be users for each departure floor and destination floor after 1 minute and 2 minutes with respect to the current time, and 0/1 data is stored in the table data. "0" stores prediction information that has not occurred, and "1" stores prediction information that has occurred. Specifically, in the present embodiment, the 7:31 record stores user occurrence prediction information such as from the departure floor 3rd floor to the destination floor 2nd floor, 4th floor, 5th floor, 6th floor, and 7th floor. The 7:32 record stores user occurrence prediction information such as from the departure floor 3rd floor to the destination floor 1st floor, 4th floor, 5th floor, 6th floor, and from the departure floor 4th floor to the destination floor 1st floor. The 7:33 record stores user occurrence prediction information from the departure floor 3rd floor to the destination floor 2nd floor, 4th floor, 7th floor, and the like. The 7:34 record stores user occurrence prediction information such as from the first floor of the departure floor to the second floor of the destination floor, and from the third floor of the departure floor to the first floor of the destination floor, the second floor, the third floor, and the sixth floor.
　行先階予測テーブル１９を活用する場合、かごが出発するまでに利用者が乗車可能な時間の行先階予測テーブル１９の予測情報を利用する必要がある。これは、例えば５分後の利用者の予測情報を利用しても、かごが３分後に出発階を出発しては、乗り合いが不可能であるためである。　
　本例における具体例を示すと、現在時刻が７：３０とする。かごＡが２分後に出発すると予測される場合、行先階予測テーブル１９の予測情報は、７：３１、７：３２のレコードを利用する。かごＢ１ｂが１分３０秒後に出発すると予想される場合、行先階予測テーブル１９の予測情報は、７：３１のレコードを利用する。かごＣ１ｃが３０秒後に出発すると予想される場合、行先階予測テーブル１９の予測情報は、利用しない。 When using the destination floor prediction table 19, it is necessary to use the prediction information of the destination floor prediction table 19 for the time when the user can board before the car departs. This is because, for example, even if the user's prediction information after 5 minutes is used, if the car departs from the departure floor after 3 minutes, it is impossible to share the vehicle.
To show a specific example in this example, the current time is 7:30. If the car A is predicted to depart after 2 minutes, the prediction information in the destination floor prediction table 19 uses the records of 7:31 and 7:32. If the car B1b is expected to depart after 1 minute and 30 seconds, the forecast information in the destination floor forecast table 19 uses the record at 7:31. If the car C1c is expected to depart after 30 seconds, the prediction information in the destination floor prediction table 19 is not used.
　本実施例では、１分毎に発生有無予測情報について管理しているため、１分以内にかごが到着する場合、利用者が乗車不可と予測されるため、行先階予測テーブル１９の予測情報は、利用できない。なお、本実施例では、１分毎に発生有無予測情報について管理する場合を示すが、これに限らず、例えば、３０秒毎に発生有無予測情報について管理する構成としても良い。 In this embodiment, since the occurrence / non-occurrence prediction information is managed every minute, if the car arrives within 1 minute, it is predicted that the user cannot board the vehicle. Therefore, the prediction information in the destination floor prediction table 19 is , Not available. In this embodiment, the case where the occurrence / presence / absence prediction information is managed every minute is shown, but the present invention is not limited to this, and for example, the occurrence / presence / absence prediction information may be managed every 30 seconds.
　＜かご別出発階別行先階別登録人数テーブル＞　
　図４は、エレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＡ用のかご出発階別行先階別登録人数テーブルＡの一例である。図５は、エレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＢ用のかご出発階別行先階別登録人数テーブルＢの一例である。図６は、エレベーター群管理装置を構成する行先階人数把握部の出力データ構造を示す図であって、かごＣ用のかご出発階別行先階別登録人数テーブルＣの一例である。 <Registered number table by car, departure floor, destination floor>
FIG. 4 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table A for each car departure floor and destination floor for car A. FIG. 5 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table B for each car departure floor and destination floor for car B. FIG. 6 is a diagram showing an output data structure of a destination floor number grasping unit constituting an elevator group management device, and is an example of a registered number table C for each car departure floor and destination floor for car C.
　行先階人数把握部７は、かご別出発階別行先階別登録人数テーブル、すなわち、かごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、およびかごＣ用のかご出発階別行先階別登録人数テーブルＣ２２を作成している。　
　図４に示すように、かごＡ用のかご出発階別行先階別登録人数テーブルＡ２０は、出発階１階から行先階４階に移動する人数が２０人、出発階６階から行先階２階に移動する人数が１人、出発階４階から行先階３階に移動する人数が１人、かごＡ１ａ（図１）に割当てられていることを表す。　
　また、図５に示すように、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１は、出発階１階から行先階５階に移動する人数が１０人、出発階３階から行先階５階に移動する人数が２人、出発階５階から行先階１階に移動する人数が１人、かごＢ１ｂ（図１）に割当てられていることを表す。　
　図６に示すように、かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２は、出発階１階から行先階６階に移動する人数が１８人、かごＣ１ｃに割当てられていることを表す。 The destination floor number grasping unit 7 is a registration number table for each departure floor and destination floor for each car, that is, a registration number table A20 for each car departure floor and another destination floor for car A, and a registration for each car departure floor and destination floor for car B. A number table B21 and a registered number table C22 for each car departure floor and destination floor for car C are created.
As shown in FIG. 4, in the registered number table A20 for each car departure floor and destination floor for car A, the number of people moving from the departure floor 1st floor to the destination floor 4th floor is 20 and the departure floor 6th floor to the destination floor 2nd floor. It means that one person moves to the car, one person moves from the fourth floor of the departure floor to the third floor of the destination floor, and the car A1a (Fig. 1) is assigned.
Further, as shown in FIG. 5, in the registered number table B21 for each car departure floor and destination floor for car B, the number of people moving from the departure floor 1st floor to the destination floor 5th floor is 10 and the departure floor 3rd floor to the destination floor. It means that the number of people moving to the 5th floor is 2 and the number of people moving from the 5th floor of the departure floor to the 1st floor of the destination floor is 1 and is assigned to the car B1b (Fig. 1).
As shown in FIG. 6, the registered number table C22 for each car departure floor and destination floor for car C shows that the number of people moving from the first floor of the departure floor to the sixth floor of the destination floor is 18 and is assigned to the car C1c. Represent.
　＜割当て対象かご判定部の処理フロー＞　
　図３は、図１に示すエレベーター群管理装置３を構成する割当て対象かご判定部１１の処理フローを示すフローチャートである。　
　図３に示すように、ステップＳ１１では、割当て対象かご判定部１１を構成する行先階呼び満員判定部１２は、行先階の登録が行われた際、出発階から行先階までの階において、そのかごに登録されている人数が所定値Ａ以上であるかごは割当て除外とする。一方、そのかごに登録されている人数が所定値Ａ未満のかご（該当しないかご）に対しては、次のステップＳ１２の処理を行う。　
　例えば、出発階３階から行先階５階への登録が行われた際、かごＡ１ａが３階に到着した時点で、既に２０人乗車していることが予測される。これは、図４に示すかごＡ用のかご出発階別行先階別登録人数テーブルＡ２０より、出発階１階から行先階４階の登録人数が２０人のため、途中階である３階に、かごＡ１ａが到着した時点でかご内の乗り人数が所定値Ａを上回るため、割当て除外となる。一方、図５に示すかごＢ用のかご出発階別行先階別登録人数テーブルＢ２１および図６に示すかごＣ用のかご出発階別行先階別登録人数テーブルＣ２２では、登録人数が２０人を下回り、該当しないかごＢ１ｂおよびかごＣ１ｃに対しては、次のＳ１２の処理が実行される。 <Processing flow of the car determination unit to be allocated>
FIG. 3 is a flowchart showing a processing flow of the allocation target car determination unit 11 constituting the elevator group management device 3 shown in FIG.
As shown in FIG. 3, in step S11, the destination floor call fullness determination unit 12 constituting the allocation target car determination unit 11 is set on the floors from the departure floor to the destination floor when the destination floor is registered. If the number of people registered in the car is equal to or greater than the specified value A, the car will be excluded from the allocation. On the other hand, for a car in which the number of people registered in the car is less than the predetermined value A (a car that does not correspond), the process of the next step S12 is performed.
For example, when registration is made from the 3rd floor of the departure floor to the 5th floor of the destination floor, it is predicted that 20 people are already on board when the car A1a arrives at the 3rd floor. This is because the number of registered people from the departure floor 1st floor to the destination floor 4th floor is 20 from the registration number table A20 for each car departure floor and destination floor shown in Fig. 4, so it is on the 3rd floor, which is an intermediate floor. When the car A1a arrives, the number of passengers in the car exceeds the predetermined value A, so the allocation is excluded. On the other hand, in the registered number table B21 for each car departure floor and destination floor for car B shown in FIG. 5, and the registered number table C22 for each departure floor and destination floor for car C shown in FIG. 6, the number of registered persons is less than 20. , The following processing of S12 is executed for the car B1b and the car C1c that do not correspond.
　ステップＳ１２では、割当て対象かご判定部１１を構成する同一階判定部１３は、現在登録された行先階と、既に同一行先階が登録済みのかごは優先かごとして、当該かごを選択する。一方、現在登録された行先階と同一行先階が登録済みのかごでない場合は、当該かごに対し次のステップＳ１３の処理が実行される。　
　例えば、出発階３階から行先階５階への登録が行われた際、かごＢ１ｂに出発階１階から４階のいずれかから行先階５階が既に登録されている場合、かごＢ１ｂを優先かごとして選択する。一方、かごＣ１ｃについては、図６に示すように、出発階１階から４階のいずれかから行先階５階が登録されていないため、かごＣ１ｃに対し次のステップＳ１３の処理が実行される。 In step S12, the same floor determination unit 13 constituting the allocation target car determination unit 11 selects the car as the priority car for the currently registered destination floor and the car for which the same destination floor has already been registered. On the other hand, if the same destination floor as the currently registered destination floor is not a registered car, the process of the next step S13 is executed for the car.
For example, when registration is made from the 3rd floor of the departure floor to the 5th floor of the destination floor, if the 5th floor of the destination floor is already registered in the car B1b from any of the 1st to 4th floors of the departure floor, the car B1b has priority. Select as a basket. On the other hand, with respect to the car C1c, as shown in FIG. 6, since the fifth floor of the destination floor is not registered from any of the first floor to the fourth floor of the departure floor, the process of the next step S13 is executed for the car C1c. ..
　ステップＳ１３では、割当て対象かご判定部１１を構成する停止階数抑制処理部１４は、今回登録された行先階を仮に各かごに割当てし、その際かごの停止階数が所定値Ｂ以上であるかごを割当て除外とする。一方、停止階数が所定値Ｂ未満であるかごに対しては次のステップＳ１４の処理が実行される。　
　例えば、停止階数の上限値である所定値Ｂが、停止階数４つの階であった場合、出発階３階から行先階５階への登録が行われた際、既に７階、６階、３階の行先階が割当てられたかごがいる場合、７階、６階、５階、３階が行先階となり、行先階床数が所定値Ｂの停止階数４つの階以上となるため、当該かごは割当て除外となる。　
　ステップＳ１４では、割当て対象かご判定部１１を構成する将来乗り合い評価起動処理部１５は、行先階の登録が行われた際、当該出発階から当該行先階までの階において、そのかごに登録されている人数が所定値Ｃ未満であるかごは割当て除外を行わず、当該かごを割当ての対象とする。一方、かごに登録されている人数が所定値Ｃ以上であるかごに対しては次のステップＳ１５の処理が実行される。　
　登録が出発階３階から行先階７階に行われた際に、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１（図５）より、３階到着時のかごＢ１ｂの乗車人数は１２人と予測され、所定値Ｃの１８人未満であるため、かごＢ１ｂに対しては以下のステップＳ１５、ステップＳ１６の処理は実行されず、割当ての対象とする。かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２（図６）より、３階到着時のかごＣ１ｃの乗車人数は１８人と予測され、所定値Ｃの１８人以上であるため、かごＣ１ｃに対しては以下のステップＳ１５およびステップＳ１６の処理が実行される。 In step S13, the stop floor number suppression processing unit 14 constituting the allocation target car determination unit 11 temporarily allocates the destination floor registered this time to each car, and at that time, the car whose stop floor number of the car is a predetermined value B or more is assigned. Exclude allocation. On the other hand, the process of the next step S14 is executed for the car whose stop floor number is less than the predetermined value B.
For example, if the predetermined value B, which is the upper limit of the number of stopped floors, is a floor with four stopped floors, when registration is performed from the departure floor 3rd floor to the destination floor 5th floor, the 7th floor, 6th floor, and 3rd floor are already registered. If there is a car to which the destination floor of the floor is assigned, the 7th, 6th, 5th, and 3rd floors will be the destination floor, and the number of destination floors will be 4 or more stopped floors with a predetermined value B. Is an allocation exclusion.
In step S14, the future ride evaluation activation processing unit 15 constituting the allocation target car determination unit 11 is registered in the car on the floors from the departure floor to the destination floor when the destination floor is registered. Cars whose number of people is less than the predetermined value C are not excluded from the allocation, and the cars are subject to allocation. On the other hand, the process of the next step S15 is executed for the car in which the number of people registered in the car is the predetermined value C or more.
When registration is performed from the 3rd floor of the departure floor to the 7th floor of the destination floor, the number of passengers in the car B1b upon arrival on the 3rd floor is as follows from the number of registered passengers table B21 (Fig. 5) by departure floor and destination floor for car B. Since it is predicted that there are 12 people and the number is less than 18 of the predetermined value C, the following steps S15 and S16 are not executed for the car B1b and are subject to allocation. From the registered number of passengers table C22 (Fig. 6) by departure floor and destination floor for car C, the number of passengers in car C1c when arriving on the 3rd floor is estimated to be 18, which is 18 or more of the predetermined value C. The following processes of step S15 and step S16 are executed for C1c.
　ステップＳ１５では、割当て対象かご判定部１１を構成する将来行先階判定部１６は、行先階予測処理部１０にて予測された出発階に将来発生する利用者の行先階と既に登録されている行先階が一致したかごは割当て除外を行う。一方、予測された出発階に将来発生する利用者の行先階と既に登録されている行先階が一致しないかごに対しては次のステップＳ１６の処理が実行される。　
　既に割当てられている行先階を有するかごと同じ行先階を有する利用者が発生すると、行先階予測処理部１０にて予測した際、乗り合いを促進するため当該かごを割当て除外する。　
　既に割当てられている行先階を有するかごが出発するまでに同じ行先階を有する利用者が登録を行うことで、初めて乗り合いが可能であるため、予測した利用者が乗り合い可能となるかごが出発までに発生する場合に本処理を行うこととする。　
　行先階予測テーブル１９、かご別出発階別行先階別登録人数テーブルであるかごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２、より７：３０に登録が出発階３階から行先階７階に行われた際に、ステップＳ１５の処理の対象であるかごＣ１ｃが１分後に出発すると予想される場合、７：３１に出発階３階から行先階６階の利用者が発生すると行先階予測テーブル１９にて予測したため、将来発生する６階を行先階とする利用者をかごＣ１ｃにて乗り合いさせるため、かごＣ１ｃを割当て除外する。 In step S15, the future destination floor determination unit 16 constituting the allocation target car determination unit 11 is a destination already registered with the user's destination floor that will occur in the future on the departure floor predicted by the destination floor prediction processing unit 10. Cars with matching floors will be deallocated. On the other hand, the process of the next step S16 is executed for the car in which the destination floor of the user that occurs in the predicted departure floor and the destination floor already registered do not match.
When a user who has the same destination floor as a car having an already assigned destination floor occurs, when the destination floor prediction processing unit 10 predicts, the car is allocated and excluded in order to promote sharing.
By the time the car with the already assigned destination floor departs, the user with the same destination floor can register for the first time, so the predicted user can ride until the car departs. This process shall be performed when it occurs in.
Destination floor prediction table 19, departure floor by car, registration number table by destination floor, car departure floor, registration number table A20, car B, departure floor, destination floor, registration number table B21 , Car C1c, which is the target of step S15, when registration is performed from the departure floor 3rd floor to the destination floor 7th floor at 7:30 from the registered number table C22 by departure floor and destination floor for car C. If it is expected that the passenger will depart one minute later, the destination floor prediction table 19 predicts that users from the departure floor 3rd floor to the destination floor 6th floor will occur at 7:31, so the 6th floor that will occur in the future will be the destination floor. In order to allow users to ride in the car C1c, the car C1c is allocated and excluded.
　上記までの処理を行うことで、同じ行先階へ向かう将来発生する利用者と既に割当てがされている利用者とを乗り合いさせることが可能となる。 By performing the above processing, it is possible to make future users heading to the same destination floor and users who have already been assigned ride on each other.
　ステップＳ１６の処理は、将来発生する利用者の行先階と現在登録した行先階が一致した場合、割当て除外を行う。今回登録した利用者と同一な行先階を有する将来発生する利用者を空いたかごにて乗り合いさせるため、当該かごの割当て除外を行う。　
　ステップＳ１５の処理と同様に予測した利用者がステップＳ１６の処理時点で割当て可能であるかごの出発までに発生すると予測した場合に本処理を行うこととする。
行先階予測テーブル１９、かご別出発階別行先階別登録人数テーブルであるかごＡ用のかご出発階別行先階別登録人数テーブルＡ２０、かごＢ用のかご出発階別行先階別登録人数テーブルＢ２１、かごＣ用のかご出発階別行先階別登録人数テーブルＣ２２、より７：３０に登録が出発階３階から行先階７階に行われた際に、割当て対象かごであるかごＢ１ｂが１分後に出発すると予想される場合、７：３１に出発階３階から行先階７階の利用者が発生すると行先階予測テーブル１９にて予測したためかごＣ１ｃを割当て除外し、かごＢ１ｂにて７階を行先階として有する利用者を乗り合いさせる。 The process of step S16 performs allocation exclusion when the destination floor of the user that occurs in the future and the destination floor currently registered match. In order to allow future users who have the same destination floor as the registered user to ride in an empty car, the allocation of the car will be excluded.
Similar to the process of step S15, this process is performed when the predicted user predicts that it will occur by the departure of the car that can be assigned at the time of process of step S16.
Destination floor prediction table 19, departure floor by car, registered number of people by destination floor, car for car A, registered number of people by destination floor, table A20, car for car B, registered number of people by destination floor, B21 , Car for car C Departure floor by destination floor Registration number table C22, from 7:30, when registration is done from the departure floor 3rd floor to the destination floor 7th floor, the car B1b to be allocated is 1 minute If it is expected to depart later, the car C1c is allocated and excluded because the destination floor prediction table 19 predicts that users from the departure floor 3rd floor to the destination floor 7th floor will occur at 7:31, and the 7th floor will be assigned to the car B1b. Share the users who have it as the destination floor.
　上記までの処理を行うことで、今回行先階を登録した利用者のみならず、将来発生する利用者を考慮した上で、乗り合いを促進することが可能となる。 By performing the above processing, it will be possible to promote sharing, taking into consideration not only the users who registered the destination floor this time but also the users who will occur in the future.
　なお、上述のステップＳ１５、ステップＳ１６の処理はいずれか一方を実施する構成としても良く、両方を実施する構成としても良い。　
　また、ステップＳ１５、ステップＳ１６の両方を実施する際、ステップＳ１５、ステップＳ１６の順で処理しても良く、ステップＳ１６、ステップＳ１５の順で処理しても良い。 It should be noted that the above-mentioned processes of steps S15 and S16 may be configured to carry out either one or both.
Further, when both step S15 and step S16 are carried out, the processes may be performed in the order of step S15 and step S16, or may be processed in the order of step S16 and step S15.
　ステップＳ１５、ステップＳ１６にも該当しない場合、当該かごを割当ての対象とする。
以上のように、将来発生する利用者の行先階を予測することで割当て除外を行い、同一行先階を有する利用者の同一かごへの乗り合い人数を増加させることが可能となる。 If neither step S15 nor step S16 is applicable, the car is subject to allocation.
As described above, it is possible to perform allocation exclusion by predicting the destination floors of users that will occur in the future, and to increase the number of users who have the same destination floors in the same car.
　なお、本発明は上記した実施例に限定されるものではなく、様々な変形例が含まれる。例えば、上記した実施例は本発明を分かりやすく説明するために詳細に説明したものであり、必ずしも説明した全ての構成を備えるものに限定されるものではない。また、上記の各構成、機能、処理部等は、それらの一部又は全部を、例えば集積回路で設計する等によりハードウェアで実現しても良い。また、上記の各構成、機能等は、プロセッサがそれぞれの機能を実現するプログラムを解釈し、実行することによりソフトウェアで実現してもよい。各機能を実現するプログラム、テーブル、ファイル等の情報は、メモリや、ハードディスク、ＳＳＤ（Ｓｏｌｉｄ　Ｓｔａｔｅ　Ｄｒｉｖｅ）等の記録装置、または、ＩＣカード、ＳＤカード、ＤＶＤ等の記録媒体に置くことができる。 The present invention is not limited to the above-mentioned examples, and includes various modifications. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those having all the described configurations. Further, each of the above configurations, functions, processing units and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. Further, each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function can be placed in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
１ａ…かごＡ、１ｂ…かごＢ、１ｃ…かごＣ、２ａ…かご制御装置Ａ、２ｂ…かご制御装置Ｂ、２ｃ…かご制御装置Ｃ、３…エレベーター群管理装置、４…行先階登録装置、５…行先階情報受信部、６…所定値設定部、７…行先階人数把握部、８…かご情報入出力部、９…学習処理部、１０…行先階予測処理部、１１…割当て対象かご判定部、１２…行先階呼び満員判定部、１３…同一階判定部、１４…停止階数抑制処理部、１５…将来乗り合い評価起動判定部、１６…将来行先階判定部、１７…割当て処理部、１８…乗車かご情報送信部、１９…行先階予測テーブル、２０…かご出発階別行先階別登録人数テーブルＡ、２１…かご出発階別行先階別登録人数テーブルＢ、２２…かご出発階別行先階別登録人数テーブルＣ、３０…エレベーター群管理システム 1a ... car A, 1b ... car B, 1c ... car C, 2a ... car control device A, 2b ... car control device B, 2c ... car control device C, 3 ... elevator group management device, 4 ... destination floor registration device, 5 ... Destination floor information receiving unit, 6 ... Predetermined value setting unit, 7 ... Destination floor number grasping unit, 8 ... Car information input / output unit, 9 ... Learning processing unit, 10 ... Destination floor prediction processing unit, 11 ... Allocation target car Judgment unit, 12 ... Destination floor call full judgment unit, 13 ... Same floor judgment unit, 14 ... Stopped floor number suppression processing unit, 15 ... Future ride evaluation start judgment unit, 16 ... Future destination floor judgment unit, 17 ... Allocation processing unit, 18 ... Boarding car information transmission unit, 19 ... Destination floor prediction table, 20 ... Registered number of people by car departure floor, destination floor A, 21 ... Registered number of people by car departure floor, destination floor B, 22 ... Destination by car departure floor Number of registered people by floor Table C, 30 ... Elevator group management system

Claims (7)

  1. 　少なくとも、複数階床にサービスする複数台のかごの運行を管理するエレベーター群管理装置とエレベーター利用者の行先階が登録され乗り場に設けられる行先階登録装置とを備え、
    　前記エレベーター群管理装置は、前記複数台のかごのうち所定のかごに前記登録された行先階を割当てる割当て処理部と、将来発生するエレベーター利用者の行先階の予測を行う行先階予測処理部と、前記所定のかごにおいて割当てられた登録人数が第一の所定値以上であるか判定する行先階呼び満員判定部と、新たに登録された行先階が前記所定のかごに既に登録された行先階と同一であるかを判定する同一階判定部と、前記所定のかごに既に登録されている行先階の階床数が第二の所定値以上かを判定する停止階数抑制処理部と、を備えるエレベーター群管理システムにおいて、
    　前記エレベーター群管理装置は、前記所定のかごに割当てられた登録者数が第三の所定値以上かを判定する将来乗り合い評価起動判定部と、前記将来乗り合い評価起動判定部が第三の所定値以上であると判定した前記所定のかごについて、前記行先階予測処理部が出力する将来発生する利用者の行先階情報を用いて前記所定のかごの割当て除外を行う将来行先階判定部と、を更に備えることを特徴とするエレベーター群管理システム。     At a minimum, it is equipped with an elevator group management device that manages the operation of multiple cars that serve multiple floors, and a destination floor registration device that registers the destination floors of elevator users and is provided at the platform.
    The elevator group management device includes an allocation processing unit that allocates the registered destination floors to a predetermined car among the plurality of cars, and a destination floor prediction processing unit that predicts the destination floors of elevator users that will occur in the future. , The destination floor call fullness determination unit that determines whether the number of registered people allocated in the predetermined car is equal to or greater than the first predetermined value, and the destination floor in which the newly registered destination floor is already registered in the predetermined car. It is provided with the same floor determination unit for determining whether it is the same as the above, and the stop floor suppression processing unit for determining whether the number of floors of the destination floor already registered in the predetermined car is equal to or more than the second predetermined value. In the elevator group management system
    The elevator group management device includes a future ride evaluation activation determination unit that determines whether the number of registrants assigned to the predetermined car is equal to or greater than a third predetermined value, and a future ride evaluation activation determination unit having a third predetermined value. With respect to the predetermined car determined to be the above, the future destination floor determination unit that excludes the allocation of the predetermined car by using the destination floor information of the user generated in the future output by the destination floor prediction processing unit. An elevator group management system characterized by further provision.
  2. 　請求項１に記載のエレベーター群管理システムおいて、
    　前記将来乗り合い評価起動判定部は、前記行先階呼び満員判定部により割当てられた登録人数が第一の所定値未満であり、かつ、前記同一階判定部により登録された行先階が既に割当てられた行先階と異なり、かつ、前記停止階数抑制処理部により登録行先階床数が第二の所定値未満である前記所定のかごについて、前記割当てられた登録人数が第三の所定値以上か否かを判定することを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1,
    In the future sharing evaluation activation determination unit, the number of registered people assigned by the destination floor call fullness determination unit is less than the first predetermined value, and the destination floor registered by the same floor determination unit has already been assigned. Whether or not the number of registered people assigned to the predetermined car, which is different from the destination floor and whose number of registered destination floors is less than the second predetermined value by the stop floor number suppression processing unit, is equal to or more than the third predetermined value. Elevator group management system characterized by determining.
  3. 　請求項１または請求項２に記載のエレベーター群管理システムおいて、
    　前記将来行先階判定部は、前記将来乗り合い評価起動判定部により第三の所定値以上と判定され、かつ、前記かごに既に割当てられた行先階と同一行先階を有する利用者が発生すると前記行先階予測処理部にて予測された前記所定のかごについて、前記所定のかごの割当て除外を行うことを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1 or 2.
    When the future destination floor determination unit is determined by the future ride evaluation activation determination unit to be equal to or higher than a third predetermined value and a user who has the same destination floor as the destination floor already assigned to the car is generated, the destination An elevator group management system characterized in that the predetermined car is assigned or excluded from the predetermined car predicted by the floor prediction processing unit.
  4. 　請求項１または請求項２に記載のエレベーター群管理システムおいて、
    　前記将来行先階判定部は、前記将来乗り合い評価起動判定部により第三の所定値以上と判定され、かつ、新たに登録された行先階と同一行先階を有する利用者が発生すると前記行先階予測処理部にて予測された前記所定のかごについて、前記所定のかごの割当て除外を行うことを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1 or 2.
    The future destination floor determination unit predicts that a user who is determined by the future ride evaluation activation determination unit to have a third predetermined value or more and has the same destination floor as the newly registered destination floor will occur. An elevator group management system characterized in that allocation exclusion of the predetermined car is performed for the predetermined car predicted by the processing unit.
  5. 　請求項１または請求項２に記載のエレベーター群管理システムおいて、
    　前記将来行先階判定部は、前記将来乗り合い評価起動判定部により第三の所定値以上と判定され、かつ、前記かごに既に割当てられた行先階と同一行先階を有する利用者が発生しないと前記行先階予測処理部にて予測され、かつ、新たに登録された行先階と同一行先階を有する利用者が発生すると前記行先階予測処理部にて予測された前記所定のかごについて、前記所定のかごの割当て除外を行うことを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1 or 2.
    The future destination floor determination unit is determined by the future ride evaluation activation determination unit to be equal to or higher than the third predetermined value, and the user who has the same destination floor as the destination floor already assigned to the car does not occur. The predetermined car predicted by the destination floor prediction processing unit and having the same destination floor as the newly registered destination floor is predicted by the destination floor prediction processing unit. An elevator group management system characterized by deallocating cars.
  6. 　請求項１または請求項２に記載のエレベーター群管理システムおいて、
    　前記第三の所定値は、混雑時、平常時、または閑散時の交通需要に応じた値が設定されることを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1 or 2.
    The third predetermined value is an elevator group management system characterized in that a value is set according to traffic demand during busy times, normal times, or off-peak hours.
  7. 　請求項１または請求項２に記載のエレベーター群管理システムおいて、
    　前記将来行先階判定部は、前記所定のかごが出発するまでに発生すると前記行先階予測処理部にて予測した利用者の行先階を用いて前記所定のかごの割当て除外を行うことを特徴とするエレベーター群管理システム。     In the elevator group management system according to claim 1 or 2.
    The future destination floor determination unit is characterized in that the allocation exclusion of the predetermined car is performed using the destination floor of the user predicted by the destination floor prediction processing unit when the occurrence occurs by the time the predetermined car departs. Elevator group management system.
PCT/JP2019/025065 2019-06-25 2019-06-25 Elevator group management system WO2020261361A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2021528682A JP7169448B2 (en) 2019-06-25 2019-06-25 Elevator group management system
PCT/JP2019/025065 WO2020261361A1 (en) 2019-06-25 2019-06-25 Elevator group management system
CN201980097826.5A CN114007971B (en) 2019-06-25 2019-06-25 Elevator group management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2019/025065 WO2020261361A1 (en) 2019-06-25 2019-06-25 Elevator group management system

Publications (1)

Publication Number Publication Date
WO2020261361A1 true WO2020261361A1 (en) 2020-12-30

Family

ID=74060816

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/025065 WO2020261361A1 (en) 2019-06-25 2019-06-25 Elevator group management system

Country Status (3)

Country Link
JP (1) JP7169448B2 (en)
CN (1) CN114007971B (en)
WO (1) WO2020261361A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112660951A (en) * 2020-12-31 2021-04-16 郭静炜 Elevator group scheduling strategy method and device
JP2022105452A (en) * 2021-01-04 2022-07-14 東芝エレベータ株式会社 Elevator control device, elevator control system, method, and program

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0769551A (en) * 1993-09-06 1995-03-14 Hitachi Ltd Guide display device for elevator
JPH0986808A (en) * 1995-09-25 1997-03-31 Hitachi Ltd Group management controller for elevator
WO2009123014A1 (en) * 2008-04-03 2009-10-08 三菱電機株式会社 Group management device of elevator
JP2010150013A (en) * 2008-12-26 2010-07-08 Hitachi Ltd Control device for destination floor reservation type group supervisory operation elevator at landing
JP2012140232A (en) * 2011-01-05 2012-07-26 Toshiba Corp Group supervisory operation control device of elevator
JP2016113237A (en) * 2014-12-12 2016-06-23 株式会社日立製作所 Elevator system and management method for elevator system
JP2017030893A (en) * 2015-07-30 2017-02-09 株式会社日立製作所 Group management elevator apparatus
JP2017178474A (en) * 2016-03-28 2017-10-05 株式会社日立製作所 Elevator device and controlling method of elevator device
WO2018131115A1 (en) * 2017-01-12 2018-07-19 三菱電機株式会社 Elevator group management control device and elevator group management control method
JP2019006542A (en) * 2017-06-22 2019-01-17 株式会社日立製作所 Group management elevator system
JP2019023124A (en) * 2017-07-24 2019-02-14 株式会社日立製作所 Elevator system, image recognition method, and operation control method

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6012853B2 (en) * 2013-04-18 2016-10-25 株式会社日立製作所 Elevator system
JP6212290B2 (en) * 2013-06-05 2017-10-11 株式会社日立製作所 Group management control method for elevator system
JP6445401B2 (en) * 2015-07-03 2018-12-26 株式会社日立製作所 Elevator group management system
JP6622240B2 (en) * 2017-03-22 2019-12-18 株式会社日立ビルシステム Elevator user guidance system and method

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0769551A (en) * 1993-09-06 1995-03-14 Hitachi Ltd Guide display device for elevator
JPH0986808A (en) * 1995-09-25 1997-03-31 Hitachi Ltd Group management controller for elevator
WO2009123014A1 (en) * 2008-04-03 2009-10-08 三菱電機株式会社 Group management device of elevator
JP2010150013A (en) * 2008-12-26 2010-07-08 Hitachi Ltd Control device for destination floor reservation type group supervisory operation elevator at landing
JP2012140232A (en) * 2011-01-05 2012-07-26 Toshiba Corp Group supervisory operation control device of elevator
JP2016113237A (en) * 2014-12-12 2016-06-23 株式会社日立製作所 Elevator system and management method for elevator system
JP2017030893A (en) * 2015-07-30 2017-02-09 株式会社日立製作所 Group management elevator apparatus
JP2017178474A (en) * 2016-03-28 2017-10-05 株式会社日立製作所 Elevator device and controlling method of elevator device
WO2018131115A1 (en) * 2017-01-12 2018-07-19 三菱電機株式会社 Elevator group management control device and elevator group management control method
JP2019006542A (en) * 2017-06-22 2019-01-17 株式会社日立製作所 Group management elevator system
JP2019023124A (en) * 2017-07-24 2019-02-14 株式会社日立製作所 Elevator system, image recognition method, and operation control method

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112660951A (en) * 2020-12-31 2021-04-16 郭静炜 Elevator group scheduling strategy method and device
JP2022105452A (en) * 2021-01-04 2022-07-14 東芝エレベータ株式会社 Elevator control device, elevator control system, method, and program
JP7171774B2 (en) 2021-01-04 2022-11-15 東芝エレベータ株式会社 ELEVATOR CONTROLLER, ELEVATOR CONTROL SYSTEM, METHOD AND PROGRAM

Also Published As

Publication number Publication date
JP7169448B2 (en) 2022-11-10
CN114007971B (en) 2023-04-18
CN114007971A (en) 2022-02-01
JPWO2020261361A1 (en) 2020-12-30

Similar Documents

Publication Publication Date Title
JP6552445B2 (en) Elevator apparatus and control method of elevator apparatus
JP5464979B2 (en) Elevator group management system
JP5351510B2 (en) Station destination floor reservation type group management elevator control device
JP5566740B2 (en) Elevator group management control device
JP5511037B1 (en) Elevator group management system
JP5705704B2 (en) Elevator group management system and control method thereof
KR920001299B1 (en) Group control device of elevator
JP2019081622A (en) Vehicle allocation system of external system cooperation and method
JP6894982B2 (en) Group management control device and group management control method
JP5951421B2 (en) Elevator group management system
WO2020261361A1 (en) Elevator group management system
WO2019087250A1 (en) Congestion avoidance operation system and method
JP5294171B2 (en) Elevator group management control device
JP6503313B2 (en) Group management control device and group management control system
JPS62121186A (en) Group control method of elevator
KR101024799B1 (en) Elevator traffic control
JPS61136883A (en) Group controller for elevator
JPS6153976B2 (en)
JPH04286581A (en) Elevator group-control control device
JPH0476914B2 (en)
JP6420217B2 (en) Elevator device and control method of elevator device
JP6759417B1 (en) Elevator allocation device
JPS6334111B2 (en)
JPS6124295B2 (en)
JPS6247787B2 (en)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19935267

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021528682

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19935267

Country of ref document: EP

Kind code of ref document: A1