JP7001131B1 - Elevator group management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve convenience when a plurality of people use an elevator. SOLUTION: Each time a card reader 25, 36 reads a card ID, a group management control device 10 records usage mode information indicating a usage mode of an elevator and usage history data including the card ID in a usage history database, and groups the group. The management control device 10 extracts usage history data in which the usage modes of the elevator are close to each other by comparing the usage mode information of the usage history data for a predetermined number of days registered in the usage history database with each other. Then, regarding the combination of card IDs included in the approximate usage history data, the number of approximations of the usage mode in one week is counted, and the card IDs related to the combination in which the counted number of approximations is equal to or more than the predetermined number of times are grouped and grouped. Register in the database. [Selection diagram] FIG. 21.

Description

The present invention relates to a group management system for elevators.

Patent Document 1 discloses an elevator group management system including a plurality of elevators and a landing destination floor registration device. In this group management system, one user in a group composed of a plurality of users inputs the number of users and the destination floor with the landing destination floor registration device, and all the uses constituting the group. It is configured so that the same unit can be assigned to a person.

Japanese Patent No. 508721

When multiple people want to use the elevator, it is troublesome for the user to input the number of users and the destination floor with the landing destination floor registration device each time.

An object of the present invention is to improve convenience when a plurality of people use an elevator.

The elevator group management system of the present invention is
Allocate a call generated based on unique identification information for each user read from the information recording medium possessed by the user by the information reader located at or near the elevator landing to one of the multiple elevators. It is a group management system of elevators equipped with a control device.
The control device is a group when the second call based on the second identification information is generated within the first predetermined time after the first call based on the first identification information read by the information reading device is generated. When the second identification information is grouped and registered with the first identification information in the database, the second call based on the second identification information is assigned to the first call based on the first identification information. It is configured to be assigned to an elevator that is
Each time the identification information is read by the information reading device, the control device records the usage mode information indicating the usage mode of the elevator and the usage history data including the identification information in the usage history database.
The control device extracts usage history data in which the usage modes of the elevator are close to each other by comparing the usage mode information of the usage history data for a predetermined number of days registered in the usage history database with each other. The number of approximations of the usage mode is counted for each combination of identification information included in the approximate usage history data, and if the counted number of approximations is equal to or greater than the predetermined number of times, the identification information related to the combination is grouped and grouped. Register in the database.

According to the present invention, it is possible to automatically group a plurality of users whose elevator usage modes are similar to each other and perform group allocation. Therefore, it is possible to improve the convenience when a plurality of people use the elevator.

It is a schematic plan view which showed the equipment arrangement on the specific floor of the building to which the elevator system in Embodiment 1 is applied. It is a block diagram which showed the structure of an elevator system. It is a block diagram which showed the electrical composition of the destination floor registration apparatus. It is the figure which showed the appearance of the destination floor registration apparatus schematically. It is a figure which showed the display example in the display part of the destination floor registration apparatus. It is a figure which showed the display example in the display part of the destination floor registration apparatus. It is a block diagram which showed the electric structure of an elevator control device. It is a figure which showed the appearance of the security gate. It is a figure which showed the display example in the gate display of a security gate. It is a block diagram which showed the electric structure of a security server. It is a figure which showed the structure of the card reader database stored in the storage part of a security server. It is a figure which showed the structure of the card database stored in the storage part of a security server. It is a flowchart explaining the call information generation process by a security server. It is a flowchart explaining the allocation process by a group management control device. It is a flowchart explaining the setting process of a departure floor and a destination floor by a group management control device. It is a flowchart explaining the call registration process by the destination floor registration apparatus. It is a flowchart explaining the normal allocation process by a group management control device. It is a flowchart explaining the 1st user allocation process by a group management control device. It is a flowchart explaining the subsequent user allocation processing by a group management control device. It is a figure which showed the structure of the usage history database stored in the storage part of a group management control device. It is a figure which showed the structure of the group database stored in the storage part of a group management control device. It is a flowchart explaining the update process of the group database based on the data of the usage history database by the group management control device.

Embodiments of the present invention will be described with reference to the drawings.

(Embodiment 1)
1. 1. Configuration 1-1. Outline of Elevator System An outline of the elevator system according to the first embodiment will be described. FIG. 1 is a schematic plan view showing the equipment arrangement on a specific floor of a building (building) to which the elevator system according to the first embodiment is applied. The specific floor is, for example, the lobby floor connected to the outside of the building, and the user of the building moves to another floor via the specific floor.

The elevator system according to the present embodiment includes a plurality of elevators 60A to 60F and a group management system that integrally controls the operation of the elevators 60A to 60F. In this embodiment, an example is shown in which the elevator system has six elevators 60A to 60F. In the following, elevators 60A to 60F are appropriately referred to as Units 1 to 6. Elevator 60A to 60F boarding openings are provided on the elevator landing side, and users board the elevators 60A to 60F from the elevator landing. In the following, the elevators 60A to 60F may be referred to as "elevator 60" without distinction.

In this embodiment, a plurality of security gates 20 are arranged on a specific floor such as the lobby floor of a building. The user enters the specific area from the entrance side through any of the security gates 20. The specific area is an area in the building that cannot be entered unless the security gate 20 is passed from the entrance side of the specific floor. The specific area includes an elevator landing, a space in the car of each elevator 60, and a space on each floor that can be moved by using the elevator 60.

A destination floor registration device 30 is arranged near the elevator landing on each floor.

In the elevator system of the present embodiment, a destination floor registration method is adopted in which the destination floor is registered in advance by the security gate 20 or the destination floor registration device 30 before the user gets into the car of the elevator 60. The group management system assigns the call (destination floor call) related to the destination floor registered in advance to any one of the plurality of elevators 60, and notifies the user of the information indicating the assigned machine. However, it is configured to allow users to board the assigned unit.

Further, in the elevator system of the present embodiment, the user can register the destination floor by using the ID card for entering the building (security authentication card for entering the building). The ID card is composed of, for example, an IC card having a built-in IC tag. The ID card is an example of an information recording medium. A dedicated ID card is always lent to each user.

The destination floor registration device 30 on the specific floor is an elevator when a user who has entered the specific area misses the elevator 60 designated by the group management system or moves to a floor other than the default destination floor. It is provided to enable the use of 60.

1-2. Elevator system configuration 1-2-1. Schematic FIG. 2 is a block diagram showing the configuration of an elevator system. The elevator system includes a plurality of elevators 60A to 60F and a group management system that controls these elevators in an integrated manner. The elevator group management system includes a group management control device 10, a plurality of destination floor registration devices 30, a plurality of elevator control devices 40A to 40F, and a plurality of gate indicators 70. The group management system is connected to the security system so that signals can be transmitted. The security system includes a security server 100, a security gate 20, a card reader 25, and a card reader 36. The gate indicator 70 is arranged at the security gate 20.

The group management control device 10 controls the allocation of new calls to each unit while communicating with the security server 100 and the destination floor registration device 30. Each device is connected via a network NW capable of transmitting information. The network NW is configured by a LAN (Local Area Network) such as Ethernet (registered trademark), and transmission / reception of various information between each device is performed according to various protocols such as TCP / IP. Each of the above-mentioned devices connected on the network NW is capable of signal transmission (information transmission) by communication according to various protocols such as TCP / IP by the input / output interface of each device. .. It should be noted that the devices constituting the elevator system may be connected via a network of other signal formats or a dedicated signal network.

Each elevator 60 (60A to 60F) has a car, a hoist (motor), a counterweight, and the like.

1-2-2. Group management control device The group management control device 10 controls the operation of a plurality of elevators 60A to 60F in an integrated manner.

The group management control device 10 is configured by using a computer, and includes a control unit 11, a storage unit 12, and an input / output interface 13.

The storage unit 12 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the group management control device 10 of the present embodiment. The storage unit 102 stores a usage history database (hereinafter referred to as “usage history DB”) and a group database (hereinafter referred to as “group DB”) as data. The configuration of the usage history DB and the group DB will be described later.

The control unit 11 is configured by using, for example, a CPU, an MPU, or the like. The control unit 11 realizes various functions described later in the group management control device 10 by performing arithmetic processing using various data and the like based on the above program read from the storage unit 12.

The input / output interface 13 is configured by using, for example, a LAN adapter or the like. In the input / output interface 13, the group management control device 10 transmits / receives various signals to / from the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40 (40A to 40F). It is an interface for doing. The input / output interface 13 converts the signal output from the control unit 11 into a signal of a predetermined format and outputs the signal to the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40. .. Further, the input / output interface 13 converts the signal input from the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40 into a signal of a predetermined format into the control unit 11. Output.

1-2-3. Destination Floor Registration Device FIG. 3 is a block diagram showing an electrical configuration of the destination floor registration device 30. The destination floor registration device 30 is a device for the user to register the destination floor. The destination floor registration device 30 includes a control unit 31, a storage unit 32, an input / output interface 33, a display unit 34, and an operation unit 35.

The storage unit 32 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the destination floor registration device 30 of the present embodiment.

The control unit 31 is configured by using, for example, a CPU, an MPU, or the like. The control unit 31 realizes various functions described later in the destination floor registration device 30 by performing arithmetic processing using various data and the like based on the above program read from the storage unit 32.

The input / output interface 33 is configured by using, for example, a LAN adapter or the like. The input / output interface 33 is an interface for the destination floor registration device 30 to send and receive various signals to and from the group management control device 10. The input / output interface 33 converts the signal output from the control unit 31 into a signal of a predetermined format and outputs the signal to the group management control device 10. Further, the input / output interface 33 converts the signal input from the group management control device 10 into a signal of a predetermined format and outputs the signal to the control unit 31.

The display unit 34 displays an image or the like based on the display signal output from the control unit 31.

The operation unit 35 is an interface for receiving a user operation on the destination floor registration device 30. The operation unit 35 outputs a signal according to the operation content to the control unit 31.

The display unit 34 and the operation unit 35 are integrally configured by, for example, a touch panel type display device using a liquid crystal display panel or an organic EL display panel. The display unit 34 and the operation unit 35 may be configured separately by using different parts as long as it is possible to specify the same as the object such as a button displayed on the display unit 34. ..

FIG. 4 is a diagram schematically showing the appearance of the destination floor registration device 30. 5A and 5B are views showing a display example in the display unit 34 of the destination floor registration device 30.

A card reader 36 is arranged on the side of the destination floor registration device 30, and is configured to allow the user to hold the ID card over the card reader 37 to perform authentication when registering the destination floor. ..

The card reader 36 reads, for example, electromagnetically non-contact the card ID (card identification information) recorded on the IC tag of the ID card (IC card) held by the user at a position closer than a predetermined distance. The card reader 36 is an example of an information reading device. The card ID is an example of identification information that is read by an information reader and is unique to each user. The card reader 36 transmits an ID data signal including the read card ID and the card reader ID (card reader identification information) of the card reader 36 to the security server 100.

FIG. 4 shows an example in which a guidance screen as a default screen is displayed on the display unit 34 of the destination floor registration device 30. On this guidance screen, for example, the message "Please hold the ID card over the card reader" is displayed. When the ID card is held over the card reader 36 by the user while the guidance screen of FIG. 4 is displayed on the display unit 34, the registration operation screen as shown in FIG. 5A is displayed, for example. On the registration operation screen of FIG. 5A, a message "Please select a destination floor" and a destination floor button for each destination floor on the 1st to 9th floors are displayed on the display unit 34. When any of the destination floor buttons is pressed (touched) by the user on the registration operation screen of FIG. 5A, the elevator is assigned, and for example, the assigned machine notification screen as shown in FIG. 5B is displayed. .. On the assigned unit notification screen of FIG. 5B, the message "Please board Unit 1" is displayed on the display unit 34.

1-2-4. Elevator control device FIG. 6 is a block diagram showing an electrical configuration of elevator control devices 40A to 40F. The elevator control devices 40A to 40F are provided corresponding to the elevators 60A to 60F, and control the operation of the hoisting machine (motor) of the corresponding elevators 60A to 60F according to the control signal from the group management control device 10. This controls the ascent, descent, stop, etc. of the elevators 60A to 60F. Further, the elevator control devices 40A to 40F each detect the car position including the car position, traveling direction, door open / closed state, load, etc. of the corresponding elevators 60A to 60F, and provide information indicating the detected car state. Output to the group management control device 10. In the following, the elevator control devices 40A to 40F may be referred to as "elevator control device 40" without distinction.

The elevator control device 40 includes a control unit 41, a storage unit 42, and an input / output interface 43.

The storage unit 42 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the elevator control device 40 of the present embodiment.

The control unit 41 is configured by using, for example, a CPU, an MPU, or the like. The control unit 41 realizes various functions described later in the elevator control device 40 by performing arithmetic processing using various data and the like based on the above program read from the storage unit 42.

The input / output interface 43 is configured by using, for example, a LAN adapter or the like. The input / output interface 43 is an interface for transmitting and receiving various signals between the elevator control device 40 and the group management control device 10. The input / output interface 43 converts the signal output from the control unit 41 into a signal of a predetermined format and outputs the signal to the group management control device 10. Further, the input / output interface 43 converts the signal input from the group management control device 10 into a signal of a predetermined format and outputs the signal to the control unit 41.

1-2-5. Security Gate The security gate 20 is a device that permits the entry of regular users into a specific area inside a building, while restricting the entry of non-regular users. A legitimate user is a user whose card ID is registered in the card database (hereinafter referred to as "card DB"), and a non-regular user is a user whose card ID is not registered in the card database. Is. The legitimate user has a legitimate ID card for storing the card ID issued by the building manager.

FIG. 7 is a diagram showing the appearance of the security gate 20. Note that FIG. 7 shows the leftmost security gate 20 among the three security gates 20 of FIG. 1. The security gate 20 includes a gate body 20a, which is a housing, a card reader 25, a first sensor 26, a second sensor 27, a gate flapper 28, and a gate display 70.

The gate flapper 28 is a door that can be opened and closed.

The gate main body 20a has a control unit that controls the opening and closing of the gate flapper 28 based on a signal output from the security server 100, a storage unit that stores programs required for control, and a signal between the gate main body 20a and the security server 100. It houses an input / output interface for sending and receiving.

The card reader 25 is arranged on the entrance 20i side of the upper surface of the gate body 20a. The card reader 25 reads, for example, electromagnetically non-contact the card ID (card identification information) recorded on the IC tag of the ID card (IC card) held by the user at a position closer than a predetermined distance. As described above, the card ID is an example of (unique) identification information that is read by an information reading device and is unique to each user. The card reader 25 transmits an ID data signal including the read card ID and the card reader ID (card reader identification information) of the card reader 36 to the security server 100.

The first sensor 26 is composed of, for example, a photoelectric sensor, and detects a user passing through the entrance 20i side of the passage PA of the security gate 20. When the first sensor 26 detects a user, the first sensor 26 outputs a detection signal to the security server 100 via the control unit.

The second sensor 27 is composed of, for example, a photoelectric sensor, and detects a user passing through the exit 20e side of the passage PA of the security gate 20. When the second sensor 27 detects the user, the second sensor 27 outputs a detection signal to the security server 100 via the control unit.

The gate display 70 displays an assigned unit notification screen that displays the name of the elevator (allocated unit) assigned by the group management control device 10. When the gate display 70 receives the allocation result signal output from the group management control device 10, the gate display 70 displays the allocation unit notification screen.

FIG. 8 is a diagram showing a display example of the security gate 20 in the gate display 70. When the ID card is held over the card reader 25 by the user passing through the security gate 20, the group management control device 10 assigns the elevator. For example, the assigned unit notification screen as shown in FIG. 8 is displayed on the gate display 70. Is displayed. On the assigned unit notification screen of FIG. 8, the message "Please board Unit 1" is displayed.

1-2-6. Security server The security server 100 performs security authentication based on the card ID included in the ID data signal transmitted from the card reader 25 of the security gate 20 or the card reader 36 of the destination floor registration device 30, and also performs security authentication of the security gate 20. Control opening and closing. Further, when the security server 100 receives the ID data signal, it generates a call information signal including information such as the destination floor of the user and outputs the call information signal to the group management control device 10.

FIG. 9 is a block diagram showing an electrical configuration of the security server 100. The security server 100 is configured by using a computer, and includes a control unit 101, a storage unit 102, and an input / output interface 103.

The storage unit 102 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions described later of the security server 100 of the present embodiment. The storage unit 102 stores the card DB as data. The configuration of the card DB will be described later.

Further, the storage unit 102 stores a card reader database (hereinafter referred to as “card reader DB”) as data. The configuration of the card reader DB will be described later.

The control unit 101 is configured by using, for example, a CPU, an MPU, or the like. The control unit 101 realizes various functions described later in the security server 100 by performing arithmetic processing using various data and the like based on the program read from the storage unit 102.

The input / output interface 103 is configured by using, for example, a LAN adapter or the like. The input / output interface 103 is an interface for the security server 100 to send and receive various signals to and from the card reader 25, the card reader 36, the group management control device 10, and the security gate 20. The input / output interface 103 converts the signal output from the control unit 101 into a signal of a predetermined format and outputs the signal to the card reader 25, the card reader 36, the group management control device 10, and the security gate 20. Further, the input / output interface 103 converts the signals input from the card reader 25, the card reader 36, the group management control device 10, and the security gate 20 into signals of a predetermined format and outputs them to the control unit 101.

FIG. 10 is a diagram showing a configuration of a card reader DB stored in the storage unit 102 of the security server 100. The card reader DB stores information on the installation floor of each card reader (25, 36) and the installation location of each card reader (25, 36) in association with the card reader ID.

The "installation floor" is information indicating the floor on which the card reader (25, 36) corresponding to the card reader ID is installed. The installation floor is used as the departure floor of the user holding the ID card over the card reader (25, 36).

The "installation location" is information indicating the position where the card reader (25, 36) corresponding to the card reader ID is installed in the installation floor. The installation location is indicated by a serial number such as "1", "2", "3", etc. for each installation floor.

In the example shown in FIG. 10, "1" and "1" are registered as the installation floor and the installation location in association with the card reader ID "0001". In association with the card reader ID "0002", "1" and "2" are registered as the installation floor and the installation location. Similarly, for the remaining card reader IDs, information on the installation floor and installation location is registered in association with the card reader ID.

FIG. 11 is a diagram showing a configuration of a card DB stored in the storage unit 102 of the security server 100. The card DB records the default destination floor and the tenant number in association with the card ID. Registration of this information in the card DB is performed, for example, by the building manager.

As described above, the "card ID" is identification information set to uniquely identify the ID card.

The "default destination floor" is information indicating the user's default destination floor. As the destination floor corresponding to the card ID of the ID card, for example, the floor where the user who has the ID card is occupying is set.

The "tenant number" is identification information indicating the tenant to which the user who has the ID card belongs.

In the example shown in FIG. 11, "10" and "07" are registered as the default destination floor and the tenant number in association with the card ID "0001". "10" and "07" are registered as the default destination floor and the tenant number in association with the card ID "0002". Similarly, for the remaining card IDs, information on the default destination floor and the tenant number is registered in association with the card ID.

2. 2. Operation 2-1-1. Open / Close Control of Gate Flapper of Security Gate An example of open / close control of the gate flapper 28 of the security gate 20 will be described in chronological order. The gate flapper 28 defaults to the closed state. When the user enters the security gate 20 while holding the ID card over the card reader 25, the card ID is read (acquired) from the ID card by the card reader 25, and the card read from the card reader 25 to the security server 100. An ID data signal including the ID and the card reader ID of the card reader 25 is transmitted. When the card ID included in the received ID data signal does not match any of the card IDs registered in the card DB, the security server 100 sends an error signal to the security in which the card reader 25 indicated by the card reader ID is arranged. Send to gate 20. In this case, the control unit of the security gate 20 keeps the gate flapper 28 in a closed state. As a result, it is possible to prevent the user presenting the non-genuine ID card from passing through the security gate 20.

On the other hand, when the card ID included in the received ID data signal matches any of the card IDs registered in the card DB, the security server 100 transmits the release signal. In this case, the control unit of the security gate 20 controls the gate flapper 28 in the open state. As a result, the user holding the legitimate ID card can pass through the security gate 20.

The control unit of the security gate 20 keeps the gate flapper 28 in the closed state when the detection signal is received from the first sensor 26 even though the release signal is not received from the security server 100. As a result, it is possible to prevent a user who has not presented the ID card from passing through the security gate 20.

In this way, a user holding a legitimate ID card can enter the specific area, but a user who does not hold the legitimate ID card cannot enter the specific area. Therefore, security in the building is ensured.

2-1-2. Unit allocation control, etc. 2-1-2-1. When the ID card is held over the card reader of the security gate When the user enters the security gate 20 while holding the card over the card reader 25, the card reader 25 reads the card ID from the held ID card and the card is read. An ID data signal including the read card ID and the card reader ID of the card reader 25 is transmitted from the reader 25 to the security server 100. The security server 100 controls any of the following (1) and (2) based on these information included in the ID data signal.

(1) When the card ID included in the ID data signal received from the card reader 25 matches any of the card IDs registered in the card DB, the security server 100 is linked to the card ID of the ID card in the card DB. Read the information of the default destination floor registered with the attachment. Further, the security server 100 reads out the installation floor and installation location information stored in the card reader DB in association with the card reader ID received from the card reader 25. Then, the security server 100 generates call information including information on the departure floor (installation floor), the installation location, and the destination floor (default destination floor), and transmits the call information signal including the call information to the group management control device 10. do.

(2) If the card ID included in the ID data signal received from the card reader 25 does not match any of the card IDs registered in the card DB, it is considered that a non-genuine ID card has been used. In such a case, the security server 100 does not generate call information.

When the group management control device 10 receives the call information signal from the security server 100, the group management control device 10 determines the allocation unit based on the received call information signal, and the allocation result signal indicating the determined allocation unit is the installation floor indicated by the call information signal. And to the gate display 70 or the destination floor registration device 30 located at the installation location.

In determining the assigned unit, the group management control device 10 considers not only the departure floor and the destination floor but also the usage history of each user's elevator.

When the gate display 70 receives the allocation result signal from the group management control device 10, the gate display 70 displays the allocation unit notification screen.

2-1-2-2. When the ID card is held over the card reader of the destination floor registration device When the card is held over the card reader 36 of the destination floor registration device 30, the security server 100 and the group management control device 10 are the card reader 25 of the security gate 20. The same process as when the ID card is held over is performed.

When the destination floor registration device 30 receives the allocation result signal from the group management control device 10, the destination floor registration device 30 displays the allocation unit notification screen displaying the allocation unit on the display unit 34.

2-1-3. Specific operation of the elevator system The specific operation of the elevator system will be described with reference to the flowchart.

FIG. 12 is a flowchart illustrating the call information generation process by the security server 100.

The security server 100 determines whether or not the ID data signal has been received from the card reader 25 or the card reader 36 (S1). The ID data signal includes at least a card ID and a card reader ID.

If no ID data signal has been received from either the card reader 25 or the card reader 36 (NO in S1), the security server 100 executes step S1 again.

When the ID data signal is received from the card reader 25 or the card reader 36 (YES in S1), the security server 100 is the card reader from which the ID data signal is transmitted based on the card reader ID included in the ID data signal. The installation floor and installation location of the 25 or the card reader 36 are specified (S2). Specifically, the security server 100 reads information on the installation floor and installation location associated with the card reader ID indicated by the ID data signal from the card reader DB.

The security server 100 identifies the user's default destination floor based on the card ID included in the ID data signal (S3). Specifically, the control unit 101 of the security server 100 reads the default destination floor associated with the card ID indicated by the ID data signal from the card DB.

The security server 100 generates call information including information on the installation floor, installation location, default destination floor, and card ID, and transmits a call information signal including the call information to the group management control device 10 (S4). When step S4 is executed, the security server 100 executes step S1 again.

FIG. 13 is a flowchart illustrating the allocation process by the group management control device 10.

The group management control device 10 determines whether or not a call information signal has been received from the security server 100 (S10). As described above, the call information signal includes information on the installation floor, installation location, default destination floor, and card ID.

If the call information signal has not been received (NO in S10), the group management control device 10 executes step S10 again.

When the call information signal is received (YES in S10), the group management control device 10 sets the departure floor and the destination floor of the call based on the call information signal and the like (S11). The process of step S11 will be specifically described with reference to FIG.

FIG. 14 is a flowchart illustrating the setting process of the departure floor and the destination floor by the group management control device 10.

The group management control device 10 determines whether or not the card reader used by the user is the card reader 25 of the security gate 20 based on the installation floor and installation location information included in the call information received from the security server 100. Is determined (S201). This determination can be made, for example, as follows. That is, the storage unit 12 of the group management control device 10 is provided with a distinction information table in which information indicating whether or not the card reader is the card reader 25 of the security gate 20 is recorded in association with the information on the installation floor and installation location of each card reader. Store it. The group management control device 10 refers to the distinction information table based on the installation floor and the installation location indicated by the call information signal, and whether or not the card reader used by the user is the card reader 25 of the security gate 20. To judge.

When the used card reader is the card reader 25 of the security gate 20 (YES in S201), the group management control device 10 sets the installation floor included in the call information as the departure floor and defaults included in the call information. The destination floor is set as the destination floor (S202).

If the card reader used is not the card reader 25 of the security gate 20 (NO in S201), the group management control device 10 receives the reception at the destination floor registration device 30 located on the installation floor and the installation location indicated by the call information. The permission signal is transmitted (S203). The reception permission signal is a signal including a command for permitting the destination floor registration device 30 to accept the registration operation of the destination floor by the user. The reception permission signal can be transmitted, for example, as follows. That is, in the storage unit 12 of the group management control device 10, a destination information table in which the destination information is recorded in association with the information of the installation floor and the installation location of each card reader is stored. The group management control device 10 refers to the destination information table based on the installation floor and installation location indicated by the call information signal, so that the gate display 70 is arranged on the installation floor and installation location indicated by the call information signal. Alternatively, the destination information of the destination floor registration device 30 can be acquired and the reception permission signal can be transmitted. The group management control device 10 can also transmit the allocation result signal to the destination floor registration device 30 located at the installation floor and the installation location indicated by the call information in the same manner.

The group management control device 10 determines whether or not the allocation request signal has been received from the destination floor registration device 30 (S204). The allocation request signal includes information on the departure floor (installation floor), installation location, destination floor, and card ID, as will be described later.

If the allocation request signal has not been received (NO in S204), the group management control device 10 executes step S204 again.

When the allocation request signal is received (YES in S204), the group management control device 10 sets the installation floor included in the call information as the departure floor and sets the destination floor indicated by the allocation request signal as the destination floor (S205). ).

When step S202 or S205 is executed, the group management control device 10 records the usage history data in the usage history DB (S12 in FIG. 13). The usage history data includes information on the call occurrence time, card ID, departure floor, destination floor, installation location, and tenant number (S12). As the installation location here, the installation location of the card reader used by the user is recorded.

The group management control device 10 executes the process of step S13 in FIG. That is, the group management control device 10 sets the card ID included in the received call information signal in the variable lid (S13).

The group management control device 10 determines whether or not the group unit number grp_car (rid) is larger than 0 (S14). The group machine number grp_car (rid) is for a call generated by a user corresponding to any card ID registered in the group table including the card ID (rid) included in the call information signal received this time. This is the elevator number currently assigned. In addition, each user corresponding to a plurality of card IDs registered in one group table is hereinafter appropriately referred to as a "group member". Here, when the group member's call is not assigned to any elevator, the group unit number grp_car (rid) is set to 0 (zero), and the group member's call is already assigned to any elevator. When, the assigned elevator machine number is set to the group machine number grp_car (rid). The group table is a table in which the card IDs of the ID cards of each user belonging to a group such as close friends and colleagues composed of a plurality of people are grouped and registered. In the present embodiment, the group table is automatically generated by analyzing the usage mode of the elevator based on the usage history of the elevator user. The structure of the group table and the procedure for generating the group table will be described later.

When the group machine number grp_car (rid) is not larger than 0 (NO in S14), that is, when the group machine number grp_car (rid) is 0, the group management control device 10 matches the time zone with the group DB. , And it is determined whether or not the group table including the receiving card ID (rid) is registered (S17).

When the time zones match and the group table including the receiving card ID (rid) is not registered (NO in S17), the group management control device 10 normally executes the allocation process (S18). The details of the normal allocation process will be described later.

When the time zones match and the group table including the receiving card ID (rid) is registered (YES in S17), that is, when the user related to the call information signal received this time is a group member of a certain group. , The group management control device 10 initializes the ID list (S19).

The group management control device 10 registers all the card IDs registered in the group table including the receiving card ID (rid) in the ID list (S20).

The group management control device 10 executes the first user allocation process for the call by the group member related to the card ID (rid) received this time among the card IDs registered in the group table (S21). The details of the first user allocation process will be described later.

In step S14, if the group unit number grp_car (rid) is greater than 0 (YES in S14), that is, if the group member's call has already been assigned to any elevator, the group management control device 10 is concerned. It is determined whether or not the elapsed time from the call reception time prev_time (rid) is equal to or less than the first predetermined time Tint (S15). The reception time prev_time (rid) of the call is hereinafter appropriately referred to as “previous reception time prev_time (rid)”. The previous reception time prev_time (rid) is set to the time to which the call of the group member is assigned (substantially equal to the reception time of the call information signal and the occurrence time of the call). When the group member's call is not assigned to any elevator, the previous reception time prev_time (rid) is set to 0 (zero). The first predetermined time Tint is the upper limit of the time interval between the time when a new call is generated by this user and the time when an existing call is generated by the latest (immediately before) group member, and multiple users are card readers. The time is set longer than the assumed time interval when the ID card is sequentially read by 25 or the card reader 36. The first predetermined time Tint is, for example, 10 seconds. An existing call is a call that has been assigned and the service has not been completed (has not arrived at the destination floor). The previous reception time prev_time (rid) is updated to the value at the time when the subsequent user allocation process is executed in step S22 described later.

When the elapsed time from the previous reception time prev_time (rid) is not less than or equal to the first predetermined time Tint (NO in S15), the group management control device 10 executes the above-mentioned step S17.

When the elapsed time from the previous reception time prev_time (rid) is equal to or less than the first predetermined time Tint (YES in S15), the group management control device 10 is an elevator (grp_car (rid) unit) of the group unit number grp_car (rid). Determines whether or not has an empty boarding space for at least one person at the time of departure from the f-f floor (S16). It should be noted that this determination is made based on the vacant boarding space in the state where the current call has not been assigned yet, that is, the vacant boarding space in the state where only the existing call is assigned. As described above, the existing call is a call that has been allocated and the service has not been completed (has not arrived at the destination floor). In the elevator system of the destination floor registration method, the departure floor and destination floor of the existing call are linked to the assigned unit and managed, and when the grp_car (rid) unit departs from the f floor, the empty boarding space for how many people is available. Is recognized based on the destination floor and departure floor of the existing call.

If the grp_car (rid) unit has no empty boarding space at the time of departure from the f floor (NO in S16), that is, if an additional call cannot be assigned to the grp_car (rid) unit, the group management control device 10 Performs step S17 described above.

When the grp_car (rid) unit has an empty boarding space for at least one person at the time of departure from the f floor (YES in S16), the group management control device 10 is a group related to the card ID (rid) received this time. Subsequent user allocation processing is executed for the call by the configurator (S22). The details of the subsequent user allocation process will be described later.

Here, a call registration process by the destination floor registration device 30 when the user performs destination floor registration using the destination floor registration device 30 will be described. As described above, the destination floor registration using the destination floor registration device 30 is performed when a user who has passed through the security gate 20 and entered the specific area misses the elevator 60 designated when passing through the security gate 20. , This is done when moving to a floor other than the default destination floor.

FIG. 15 is a flowchart illustrating a call registration process by the destination floor registration device 30. The processing according to this flowchart is always executed while the elevator system is in operation.

The destination floor registration device 30 first displays a guidance screen on the display unit 34 (S211). For example, the destination floor registration device 30 displays a guidance screen as shown in FIG. 4 described above on the display unit 34.

The destination floor registration device 30 determines whether or not the reception permission signal has been received from the group management control device 10 (S212). As described above, the reception permission signal is a signal that permits the destination floor registration device 30 to accept the registration operation of the destination floor by the user, and is a security server when the user holds the ID card over the card reader 36. It is output from 100.

When the reception permission signal is not received from the group management control device 10 (NO in S212), the destination floor registration device 30 returns to step S211 and executes the process.

When the reception permission signal is received from the group management control device 10 (YES in S212), the destination floor registration device 30 displays the registration operation screen on the display unit 34 (S213). For example, the registration operation screen as shown in FIG. 5A described above is displayed on the display unit 34.

The destination floor registration device 30 sets the current time in the reception time rt of the reception permission signal (S214). Specifically, the control unit 31 of the destination floor registration device 30 stores the current time in the storage unit 32 as the reception time rt of the reception permission signal.

The destination floor registration device 30 determines whether or not any of the destination floor buttons has been pressed (S215).

When any of the destination floor buttons is pressed (YES in S215), the destination floor registration device 30 transmits an allocation request signal to the group management control device 10 (S216). The allocation request signal includes information on the installation floor (departure floor) of the destination floor registration device 30, the installation location of the destination floor registration device 30, and the destination floor corresponding to the pressed destination floor button. The installation floor and installation location of the destination floor registration device 30 are the same information as the installation floor and installation location stored in the card reader DB linked to the card reader 36 attached to the destination floor registration device 30. Yes, for example, it is stored in the storage unit 32 of each destination floor registration device 30. The control unit 31 of the destination floor registration device 30 reads out the installation floor and the installation location from the storage unit 32 and uses them when generating the allocation request signal.

The destination floor registration device 30 determines whether or not the allocation result signal has been received from the group management control device 10 (S217). The allocation result signal is a signal transmitted from the group management control device 10 as a response to the allocation request signal, and includes information on the optimum unit number best (information on the allocation unit).

If the allocation result signal has not been received from the group management control device 10 (NO in S217), the destination floor registration device 30 executes step S217 again.

When the allocation result signal is received from the group management control device 10 (YES in S217), the destination floor registration device 30 assigns the allocation unit to the display unit 34 for a predetermined time based on the information of the optimum unit number best indicated by the allocation result signal. Display (S218). For example, the display unit 34 displays the assigned unit notification screen as shown in FIG. 5B described above. The predetermined time is a time that is long enough for the user to visually recognize the "assigned machine", for example, 4 seconds.

When the process of step S218 is executed, the control unit 31 of the destination floor registration device 30 returns to step S211 and causes the display unit 34 to display the guidance screen.

If neither of the destination floor buttons is pressed (NO in S215), is the destination floor registration device 30 the current time later than the time obtained by adding the difference time C to the reception time rt set in step S214? It is determined whether or not (S219). The difference time C is the display duration of the registration operation screen, and is set to a time during which the user can perform the designated operation of the destination floor with a margin. The difference time C is, for example, 10 seconds.

If the current time is not later than the time obtained by adding the difference time C to the reception time rt (NO in S219), the destination floor registration device 30 executes step S215 again.

When the current time is later than the time obtained by adding the difference time C to the reception time rt (YES in S219), the control unit 31 of the destination floor registration device 30 returns to step S211 and displays a guidance screen on the display unit 34. Let me. As a result, after the registration operation screen is displayed on the display unit 34, for example, when the user leaves and no destination floor button is pressed for a difference time C or more, the screen is switched to the guidance screen. ..

Next, the details of the normal allocation process in step S18 of FIG. 13 by the group management control device 10 will be described with reference to FIG.

FIG. 16 is a flowchart illustrating a normal allocation process by the group management control device 10.

The group management control device 10 sets 1 to the machine number car and initializes the maximum allocation evaluation value Emax to 0 (S101). The machine number car is indicated by a serial number from 1 to N. N is equal to the number of elevators. The elevator with the unit number car is hereinafter referred to as "car unit" as appropriate.

The group management control device 10 initializes the assigned evaluation value E (car) of the car unit to 0 (S102).

The group management control device 10 calculates the basic evaluation value Calc of the car unit (S103).

The basic evaluation value Acalc is, for example, the time WT (waiting time) from the occurrence of a call to the arrival of each elevator at the departure floor of the call, or the time from the occurrence of the call to the arrival at the destination floor of the call. Required for each elevator based on (service completion time). The basic evaluation value Calc is, for example, a value obtained by multiplying the first evaluation value (for example, a value proportional to the reciprocal of the waiting time), which increases as the waiting time is smaller (shorter), by the first weighting factor, and the service completion time is smaller (for example, the service completion time is smaller). It is a value obtained by adding a value obtained by multiplying a second evaluation value (for example, a value proportional to the reciprocal of the service completion time), which becomes larger as (shorter), by a second weighting coefficient. The magnitudes of the first weighting coefficient and the second weighting coefficient are set so that the basic evaluation value Acalc becomes, for example, about 10 in the situation where the basic evaluation value Acalc becomes the largest. When calculating the basic evaluation value Acalc, the value obtained by multiplying the third evaluation value (for example, a value proportional to the reciprocal of the reciprocal of the number of stops) by the third weight coefficient, which increases as the number of stops until the service is completed is smaller (smaller), is further added. You may add. In this case, the sizes of the first weighting coefficient, the second weighting coefficient, and the third weighting coefficient are set so that the basic evaluation value Acalc is, for example, about 10 in the situation where the basic evaluation value Acalc is the largest. Will be done. The first evaluation value, the second evaluation value, and the third evaluation value are appropriately weighted so that the average of the basic evaluation values Acalc is, for example, about 10.

The group management control device 10 adds the basic evaluation value Acc to the allocation evaluation value E (car) (S104).

The group management control device 10 determines whether or not the allocation evaluation value E (car) is larger than the maximum allocation evaluation value Emax (S105).

When the allocation evaluation value E (car) is larger than the maximum allocation evaluation value Emax (YES in S105), the group management control device 10 sets the current unit number car as the optimum unit number best and sets the current allocation evaluation value. E (car) is set as the maximum allocation evaluation value Emax (S106).

When the allocation evaluation value E (car) is not larger than the maximum allocation evaluation value Emax (NO in S105), the group management control device 10 does not perform the process of step S106.

The group management control device 10 adds 1 to the machine number car (S107).

The group management control device 10 determines whether or not the unit number car is larger than the number of elevators (S108).

When the unit number car is not larger than the number of elevators (NO in S108), the group management control device 10 returns to step S101 and executes the process.

When the unit number car is larger than the number of elevators (YES in S108), the group management control device 10 is most suitable for the destination floor registration device 30 or the gate display 70 located at the installation floor and the installation location indicated by the call information. The allocation result signal including the information of the unit number best is transmitted (S109). As a result, the assigned machine notification screen displaying the information of the assigned machine (assigned machine name, etc.) indicated by the optimum machine number best is displayed on the display unit 34 of the gate display 70 or the destination floor registration device 30.

According to the normal allocation process in FIG. 16, the call is assigned to the elevator having the largest allocation evaluation value E (car) among the allocation evaluation values E (car) obtained for all elevators.

FIG. 17 is a flowchart illustrating the first user allocation process by the group management control device.

The group management control device 10 sets 1 as the machine number car and initializes the maximum allocation evaluation value Emax to 0 (S31).

The group management control device 10 initializes the allocation evaluation value E (car) to 0 (S32).

The group management control device 10 sets the number of card IDs registered in the ID list to the number of people P (S33).

The group management control device 10 determines whether or not the car unit has an empty boarding space for P or more at the time of departure from the f floor (S34). It should be noted that this determination is made based on the vacant boarding space in the state where the new call has not been assigned yet, that is, the vacant boarding space in the state where only the existing call is assigned. As described above, the existing call is a call that has been allocated and the service has not been completed (has not arrived at the destination floor). In the destination floor registration type elevator system, the departure floor and destination floor of the existing call are linked to the assigned unit and managed, and the number of empty boarding spaces that the car unit has at the time of departure from the f floor is existing. It can be calculated based on the destination floor and departure floor of the call.

When the car unit has an empty boarding space for P people or more at the time of departure from the f floor (YES in S34), the group management control device 10 adds a predetermined value A1 to the assigned evaluation value E (car) (S36). .. Adding the predetermined value A1 to the allocation evaluation value E (car) is an example of a predetermined correction that enhances the allocation suitability. The predetermined value A1 is a constant, and is set to a value very large as compared with the basic evaluation value Acc which is added to the assigned evaluation value E (car) in the later step S36. The predetermined value A1 is, for example, 100. On the other hand, the basic evaluation value Acalc is, for example, a value of 10 or less as described in step S103. The reason why the predetermined value A1 is set to such a large value as compared with the basic evaluation value Acalc is that the car unit has an empty boarding space for P people or more at the time of departure from the f floor in the first user allocation process. This is to emphasize.

If the car unit does not have an empty boarding space for P people or more at the time of departure from the f floor (NO in S34), the group management control device 10 does not perform the process of step S35.

The group management control device 10 calculates the basic evaluation value Acc of the car unit, and adds the basic evaluation value Acc to the assigned evaluation value E (car) (S36).

The group management control device 10 determines whether or not the allocation evaluation value E (car) is larger than the maximum allocation evaluation value Emax (S37).

When the allocation evaluation value E (car) is larger than the maximum allocation evaluation value Emax (YES in S37), the group management control device 10 sets the current unit number car as the optimum unit number best, and the maximum allocation evaluation value Emax. The current allocation evaluation value E (car) is set as (S38).

When the allocation evaluation value E (car) is not larger than the maximum allocation evaluation value Emax (NO in S37), the group management control device 10 does not perform the process of step S38.

The group management control device 10 adds 1 to the machine number car (S39).

The group management control device 10 determines whether or not the unit number car is larger than the number of elevators (S40).

If the unit number car is not larger than the number of elevators (NO in S40), the group management control device 10 returns to step S31 and executes the process.

When the unit number car is larger than the number of elevators (YES in S40), that is, when the processing up to step S39 is completed for all the units, the group management control device 10 is set to the card ID (id) registered in the ID list. The optimum machine number best and the current time are set in the group machine number grp_car (id) and the previous reception time prev_time (id) associated with each other (S41). The previous reception time prev_time (id) is the reception time of the call registered immediately before by the group member.

The group management control device 10 transmits an allocation result signal including information of the optimum machine number best to the destination floor registration device 30 or the gate display 70 located at the installation floor and the installation location indicated by the call information (S42). .. As a result, the assigned machine notification screen displaying the information of the assigned machine (assigned machine name, etc.) indicated by the optimum machine number best is displayed on the display unit 34 of the gate display 70 or the destination floor registration device 30.

According to the first user allocation process of FIG. 17, since the predetermined value A1 is added to the allocation evaluation value E (car) of the elevator 60 having an empty boarding space in which P users can board, the elevator 60 is It becomes easier to be assigned to a new call of the first user. Therefore, it becomes easy to assign the group member following the first group member to the same elevator 60 as the elevator 60 assigned to the first group member.

FIG. 18 is a flowchart illustrating a subsequent user allocation process by the group management control device 10.

The group management control device 10 executes the following settings for each of the card IDs registered in the ID list. Specifically, the group management control device 10 sets the optimum machine number best set in the first user allocation process (FIG. 17) as the group machine number grp_car (id), and sets the previous reception time prev_time (id). ) To set the current time (S71). The current time here is the time when the subsequent user allocation process is performed (substantially the same time as the time when the new call is generated by the subsequent user).

The group management control device 10 transmits an allocation result signal including information of the optimum machine number best to the destination floor registration device 30 or the gate display 70 located at the installation floor and the installation location indicated by the call information (S72). .. As a result, the assigned machine notification screen displaying the information of the assigned machine (assigned machine name, etc.) indicated by the optimum machine number best is displayed on the display unit 34 of the gate display 70 or the destination floor registration device 30.

According to the subsequent user allocation process of FIG. 18, the same elevator as the elevator assigned in the first user allocation process can be assigned to the subsequent users.

In addition, since the previous reception time prev_time (id) is moved down to the time when a new call is generated by a subsequent user (time for subsequent user allocation processing) (S71), multiple users open the security gate one by one. In the case of passing, there is a high possibility that multiple users can be on board the same elevator. Therefore, it is possible to improve the convenience when a group of a plurality of users uses the elevator.

FIG. 19 is a diagram showing a configuration of a usage history database stored in the storage unit 12 of the group management control device 10.

The group management control device 10 records the usage history data in the usage history DB each time the card ID is read by the card readers 25 and 36. In the usage history DB, each usage history data includes information on the call occurrence time, card ID, departure floor, destination floor, installation location, and tenant number. Of the usage history data, the card ID corresponds to unique identification information for each user, and the information on the call occurrence time, departure floor, destination floor, installation location, and tenant number is usage mode information indicating the usage mode of the elevator. Corresponds to. Registration of these information in the usage history DB is automatically performed by the group management control device 10 as described above.

The “call generation time” is the time when the group management control device 10 receives the call information signal generated by the security server 100 based on the card ID read by the card reader 25 or 36 from the security server 100. The "call occurrence time" can also be said to be the time (use date and time) when the user uses the card reader 25 or 36.

The "card ID" is identification information set to uniquely identify the ID card possessed by the user.

The "departure floor" is information indicating the departure floor of the user.

The "destination floor" is information indicating the destination floor of the user.

The "installation location" is information indicating the installation location (installation position) of the used card reader (25, 36). For example, when a card reader (25, 36) whose "installation location" is "1" is used, "1" is registered and a card reader (25, 36) whose "installation location" is "2" is used. If so, "2" is registered.

The "tenant number" is identification information set to uniquely identify the tenant.

In the usage history DB shown in FIG. 19, for example, the card ID, departure floor, destination floor, installation location, and tenant number are linked to the call occurrence time "2019-04-01-13-10-25" as "". 0001 ”,“ 10 ”,“ 8 ”,“ 2 ”, and“ 07 ”are registered. In addition, the card ID, departure floor, destination floor, installation location, and tenant number are "0002", "10", and "8" in association with the call occurrence time "2019-04-01-13-10-27". "," 2 ", and" 07 "are registered. In addition, the card ID, departure floor, destination floor, installation location, and tenant number are "0003", "10", and "8" in association with the call occurrence time "2019-04-01-13-10-30". "," 2 ", and" 07 "are registered. Similarly, for the remaining call occurrence time, the card ID, departure floor, destination floor, installation location, and tenant number are registered in association with the call occurrence time.

FIG. 20 is a diagram showing the configuration of the group database stored in the storage unit of the group management control device.

The group DB stores a plurality of group tables. A group table is provided for each group. In the group table, the time zone and the card ID of the ID card possessed by the group member are registered in association with the group ID. In the group table of FIG. 20A, the time zone "13: 00-13: 30" and the card IDs "0001", "0002", and "0003" are registered in association with the group ID "001". .. In the group table of FIG. 20B, the time zone "13: 00-13: 30" and the card IDs "0005" and "0006" are registered in association with the group ID "002".

Next, the group database update process by the group management control device will be described with reference to FIG. 21.

FIG. 21 is a flowchart illustrating a group database update process by the group management control device.

The process according to the flowchart of FIG. 21 is performed for each card ID. Specifically, each card ID is set to the following IDa, and the process of FIG. 21 is performed. All group tables are deleted before the group database is updated for the first card ID, and a new group table is generated by the update process for each card ID.

The group management control device 10 extracts all usage history data (all records) included in the target time zone for the past X days from the usage history DB (S401).

The group management control device 10 initializes the usage mode approximation number ct [id] corresponding to each card ID to 0 (S402). The id here is a card ID.

The group management control device 10 determines whether or not the usage history data whose card ID is IDa is included in the usage history data extracted in step S401 (S403).

When the card ID does not include the usage history data of IDa (NO in S403), the group management control device 10 ends the process of this flowchart. As a result, the contents of the group database corresponding to the IDa are determined when the contents are initialized, that is, the card ID associated with the IDa does not exist.

When the card ID includes the usage history data of IDa (YES in S403), the group management control device 10 includes one usage history data of the card ID IDa from the usage history data extracted in step S401. Extract (S404). Hereinafter, one extracted usage history data is appropriately referred to as “comparison source usage history data dt (a)”. When a plurality of usage history data having a card ID of IDa exist, the next time this step is executed, among the usage history data extracted in step S401, the usage history data having the card ID of IDa can be selected from the usage history data. Extract one usage history data for which the usage mode comparison process has not been completed.

The group management control device 10 extracts one usage history data whose card ID is other than IDa from the usage history data extracted in S401 (S405). Hereinafter, one extracted usage history data is appropriately referred to as “comparison target usage history data dt (p)”. When a plurality of usage history data whose card ID is other than IDa exists, the usage history data whose card ID is other than IDa among the usage history data extracted in step S401 when this step is next executed is included in the usage history data whose card ID is other than IDa. From, one usage history data for which the usage mode comparison process has not been completed is extracted.

In steps S406 to S410, the group management control device 10 compares the contents of the comparison source usage history data dt (a) with the contents of the comparison target usage history data dt (p). This comparison process is appropriately referred to as "usage mode comparison process" below. When the determination in steps S406 to S410 is "YES", the group management control device 10 relates to the elevator usage mode of the user related to the comparison source usage history data dt (a) and the comparison target usage history data dt (p). It is judged that the elevator usage mode of the user is similar.

Specifically, first, in step S406, the group management control device 10 has a usage time recorded in the comparison source usage history data dt (a) and a usage time recorded in the comparison target usage history data dt (p). It is determined whether or not the time difference between the two and the second predetermined time is within T seconds (S406). T is, for example, 5 seconds.

When the time difference between the usage times is within T seconds (YES in S406), the group management control device 10 has the departure floor recorded in the comparison source usage history data dt (a) and the comparison target usage history data dt (p). ) Is the same as the departure floor recorded in (S407).

When the departure floors are the same (YES in S407), the group management control device 10 is recorded in the destination floor recorded in the comparison source usage history data dt (a) and in the comparison target usage history data dt (p). It is determined whether or not the destination floor is the same (S408).

When the destination floors are the same (YES in S408), the group management control device 10 is recorded in the tenant number recorded in the comparison source usage history data dt (a) and the comparison target usage history data dt (p). It is determined whether or not the tenant number is the same (S409).

When the tenant numbers are the same (YES in S409), the group management control device 10 has the position indicated by the installation location recorded in the comparison source usage history data dt (a) and the comparison target usage history data dt (p). It is determined whether or not the position indicated by the installation location recorded in is close to a certain degree (S410). For example, if the security gates used are the same security gate or adjacent security gates, it is determined that they are close to each other to a certain extent.

When the position indicated by the installation location is close to a certain degree (YES in S410), the group management control device 10 adds 1 to the usage mode approximation count ct [id] corresponding to the card ID of the comparison target usage history data dt (p). (S411). If all the judgments in steps S406 to S410 are YES, that is, if the time difference between the usage times is within T seconds, the departure floor, destination floor and tenant number are the same, and the position indicated by the installation location is close to a certain degree, the comparison source usage history data. It is determined that the user's elevator usage mode related to dt (a) and the user's elevator usage mode related to the comparison target usage history data dt (p) are similar.

The group management control device 10 determines whether or not the usage history data whose card ID is other than IDa among the usage history data extracted in step S401 includes usage history data for which the usage mode comparison process has not been completed yet. (S412).

When there is usage history data for which the usage mode comparison process has not been completed (YES in S412) among the usage history data whose card ID is other than IDa, the group management control device 10 executes step S405. When executing step S405, the group management control device 10 has not yet completed the usage mode comparison process from the usage history data whose card ID is other than IDa, instead of the current comparison target usage history data dt (p). One of the non-use history data is set as the comparison target usage history data dt (p).

When there is no usage history data for which the usage mode comparison process has not been completed (NO in S412) among the usage history data whose card ID is other than IDa, the group management control device 10 uses the usage history data extracted in step S401. Among the usage history data whose card ID is IDa, it is determined whether or not there is usage history data for which the usage mode comparison process has not been completed (S413).

When there is usage history data for which the usage mode comparison process has not been completed (YES in S413) in the usage history data whose card ID is IDa, the group management control device 10 executes step S404. When executing step S404, the group management control device 10 has not yet completed the usage mode comparison process from the usage history data whose card ID is IDa instead of the current comparison source usage history data dt (a). One of the usage history data is set as the comparison source usage history data dt (a).

When there is no usage history data for which the usage mode comparison process has not been completed in the usage history data whose card ID is IDa (NO in S413), the group management control device 10 has a predetermined usage mode approximation count ct [id]. All the card IDs with the number of times k or more are extracted (S414). The predetermined number of times k is, for example, 5 times. By setting the predetermined number of times k to a larger value, the accuracy of determining the approximation of the usage mode can be further improved.

The group management control device 10 creates a group table in which all the extracted card IDs and IDa are grouped and recorded (S415). If the group table in which the IDa is recorded already exists, only the card IDs that have not been recorded yet among the extracted card IDs are added to the existing group table.

When any of the conditions of steps S406, S407, S408, S409, and S410 is not satisfied (NO), the group management control device 10 executes the above-mentioned step S412.

A specific example of the above-mentioned group DB update process will be described with reference to FIGS. 19 and 20.

It is assumed that the usage history DB of FIG. 19 is updated with the group DB based on the flowchart of FIG. For example, when the usage mode comparison process based on the flowchart of FIG. 21 is performed for the card ID "0001", the time difference of the usage time is within the second predetermined time T seconds (within 5 seconds), and the departure floor, destination floor, and installation. Card IDs "0002" and "0003" are extracted as card IDs having the same location and tenant number. That is, the card IDs "0002" and "0003" are extracted as the card IDs whose usage is similar to the card ID "0001". The card IDs "0004", "0005", and "0006" are not extracted because the usage modes are not similar. Further, in the time zone from 13:00 to 13:30 in one week, the number of times of such usage mode approximation is 5 with respect to the card IDs "0002" and "0003" with respect to the card ID "0001". It shall be more than once. In this case, in the group DB, a group table including the card IDs “0001”, “0002”, and “0003” is created as shown in FIG. 20 (a).

After the usage mode comparison process (group DB update process) for the card ID "0001" is completed, the usage mode comparison process for the card ID "0002" based on the flowchart of FIG. 21 is performed, and the time difference between the usage times is secondly determined. Card IDs "0001" and "0003" that are within T seconds (within 5 seconds) and have the same departure floor, destination floor, installation location, and tenant number are extracted. Further, in the time zone from 13:00 to 13:30 in one week, the number of times of such usage mode approximation is 5 with respect to the card IDs "0001" and "0003" for the card ID "0002". It shall be more than once. In this case, since the group table including the card ID "0002" and "0001" and "0003" currently being processed already exists in the group DB in the time zone from 13:00 to 13:30, it is new. Group table is not created. After that, even when the usage mode comparison process (group DB update process) based on the flowchart of FIG. 21 is performed on the card ID “0003”, the card IDs “0001” and “0002” are the same as in the case of the card ID “0002”. However, the number of such usage mode approximations is 5 or more, but since the group table including the card IDs “0003” and “0001” and “0003” already exists in the group DB. , No new group table is created.

After the usage mode comparison processing (group DB update processing) for the card ID "0003" is completed, it is assumed that the usage mode comparison processing for the card ID "0004" is performed based on the flowchart of FIG. In this case, the usage mode is not similar to any of the card IDs "0001", "0002", "0003", "0005", and "0006". Further, it is assumed that the number of times of approximation of the usage mode is less than 5 times for any of these card IDs. In this case, the group table including the card ID "0004" is not generated.

When the usage mode comparison process based on the flowchart of FIG. 21 is performed for the card ID "0005", the time difference between the usage times is within the second predetermined time T seconds (within 5 seconds), and the departure floor, destination floor, installation location, and so on. The card ID "0006" is extracted as the card ID in which all the tenant numbers are the same. That is, the card ID "0006" is extracted as the card ID whose usage mode is similar to that of the card ID "0005". The card IDs "0001", "0002", "0003", and "0004" are not extracted because the usage modes are not similar. Further, in the time zone of 13:00 to 13:30 during one week, the number of times of such usage mode approximation is 5 or more with respect to the card ID "0006" with respect to the card ID "0005". It shall be. In this case, in the group DB, a group table including the card IDs "0005" and "0006" is created as shown in FIG. 20 (b).

After the usage mode comparison processing (group DB update processing) for the card ID "0005" is completed, when the usage mode comparison processing for the card ID "0006" is performed based on the flowchart of FIG. 21, the time difference of the usage time is secondly determined. The card ID "0005" is extracted, which is within T seconds (within 5 seconds) and has the same departure floor, destination floor, installation location, and tenant number. Further, in the time zone from 13:00 to 13:30 during one week, the number of times of such usage mode approximation is 5 or more with respect to the card ID "0005" with respect to the card ID "0006". It shall be. In this case, in the group DB, since the group table including the card ID "0006" already exists in the time zone from 13:00 to 13:30, a new group table is not created.

3. 3. Action of this embodiment In recent years, a security gate has been installed on the lobby floor of a high-rise building or the like, and each user can hold his / her own ID card over the card reader to enter a specific area inside the building. May be. In addition, in a building where a security gate is installed, an elevator system may be installed in which when each user holds his / her own ID card over, the destination floor associated with the ID card is assigned to any elevator. ..

However, in the conventional elevator system as described above, this is not taken into consideration even if multiple users are close friends and colleagues, and as a result, these users are likely to be assigned to different elevators. rice field.

Conventionally, one user in a group composed of a plurality of users inputs the number of users and the destination floor with the landing destination floor registration device, so that all the users constituting the group can be notified. There is a technology to assign the same unit. However, when a plurality of people use the elevator, it is troublesome for the user to input the number of users and the destination floor with the landing destination floor registration device each time.

However, according to the elevator system of the present embodiment, a plurality of users whose usage modes of the elevator are similar to each other, for example, a plurality of users such as close friends and colleagues are automatically grouped and group-assigned. be able to. Therefore, it is possible to improve the convenience when a plurality of people use the elevator.

(Summary and effects of embodiments)
The elevator group management system of the first embodiment is
A unique card ID (identification) for each user read from an ID card (an example of an information recording medium) possessed by a user with card readers 25 and 36 (an example of an information reading device) placed at or near the elevator landing. An elevator group management system including a group management control device 10 (control device) that assigns a call based on call information generated based on information) to any of a plurality of elevators 60.
The group management control device 10 has a second call based on the second card ID within the first predetermined time Tint after the first call based on the first card ID read by the card readers 25 and 36 is generated. When the second card ID is grouped and registered with the first card ID in the group database, the second call based on the second card ID is based on the first card ID. The first call is configured to be assigned to the assigned elevator
Each time the card ID is read by the card readers 25 and 36, the group management control device 10 records the usage mode information indicating the usage mode of the elevator and the usage history data including the card ID in the usage history database.
The group management control device 10 compares the usage mode information of the usage history data for one week (an example of a predetermined number of days) registered in the usage history database with each other among the usage history data, so that the usage mode of the elevator can be changed. Usage history data that are close to each other are extracted, and the number of approximations of the usage mode during one week is counted for the combination of card IDs included in each of the approximate usage history data, and the number of approximations counted is 5 (an example of a predetermined number of times). ) Group the card IDs related to the above combinations and register them in the group database.

With this configuration, it is possible to automatically group a plurality of users whose elevator usage modes are similar to each other and perform group allocation. Therefore, it is possible to improve the convenience when a plurality of people use the elevator.

In the elevator group management system of the first embodiment,
Elevator usage mode information includes call occurrence time information, departure floor information, destination floor information, tenant number of the tenant to which the user corresponding to each card ID belongs (an example of tenant information), and each. Includes information on the installation locations of card readers 25 and 36 used by users corresponding to the card ID.
The group management control device 10 relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) The departure floor is the same,
(C) The destination floor is the same,
(D) The tenant numbers are the same and
(E) When the position indicated by the installation location is close to a certain degree,
It is judged that the usage modes are similar to each other.

With this configuration, it is possible to accurately group a plurality of users whose usage modes are similar to each other.

In the elevator group management system of the first embodiment,
In the group management control device 10, when the first card ID is read by the card readers 25 and 36, the group including the first card ID is registered in the group database, but any of the groups included in the group. When an elevator is not assigned to the card ID, the first call based on the first card ID is assigned to the elevators to which the number of calls of the number of card IDs included in the group can be assigned.

With this configuration, when a plurality of users included in a group use an elevator, there is a high possibility that they will be assigned to the same elevator.

In the elevator group management system of the first embodiment,
The group management control device 10 divides the time zone into groups and registers the card IDs included in the usage history data in which the usage modes of the elevator are close to each other in the group database.
The group management control device 10 makes a second call when the second card ID is associated with the first card ID and is registered in the group database with respect to the time zone including the current time. Assign to the elevator to which the first call based on the card ID is assigned.

With this configuration, the second call is assigned to the elevator to which the first call is assigned only if the current time when the elevator is in use belongs to the time zone of the group database. If the current time while using the elevator is not a time that belongs to the time zone of the group database, it is assumed that the first user and the second user are not acting in the group. Therefore, group allocation is not performed.

(Modified Example of Embodiment 1)
In the first embodiment, the elevator usage mode information includes the call occurrence time, the destination floor information, the tenant number (tenant information) of the tenant to which the user corresponding to each card ID (identification information) belongs, and each. In the group management control device 10, the group management control device 10 includes information on the installation location of the card reader (information reading device) used by the user corresponding to the card ID, and (a) the time difference of the call occurrence time is the second with respect to the compared usage history data. 2 Within a predetermined time T seconds, (b) the departure floor is the same, (c) the destination floor is the same, (d) the tenant number (tenant information) is the same, and (e) the installation location indicates. When the positions are close to each other to a certain extent, it is judged that the usage modes are close to each other. As a result, the card IDs related to the group members whose usage modes are similar to each other are accurately extracted. However, regarding (c) the condition that the destination floor is the same, (d) the condition that the tenant number (tenant information) is the same, and (e) the condition that the location indicated by the installation location is close to a certain degree. It may be removed as appropriate depending on the situation of the building. The conditions (a) and (b) are often satisfied at the same time by users such as close friends and colleagues. Therefore, even if the conditions (c), (d), and (e) are removed, it is possible to appropriately extract close users (identification information) based on the determination of approximation of the usage mode.

To explain a specific example, when one tenant is dispersedly occupying a plurality of floors in one building, the destination floors of close users belonging to the tenant may be different. In such a case, such users (the card ID) can be grouped by removing the condition that the destination floor of (c) is the same.

In addition, even if the users are close friends, the tenants to which they belong may be different. In such a case, such users (the card ID) can be grouped by removing the condition that the tenant of (d) is the same.

Further, depending on the building, only one card reader (information reader) may be provided on one floor. In addition, there are cases where multiple card readers are installed on one floor, but all the card readers are placed close to each other, and the conditions indicated by the installation locations of all the card readers are close to each other to a certain extent. be. In these cases, the condition that the position indicated by the installation location in (e) is close to a certain degree may be removed.

Further, depending on the time zone, which of the conditions (a) to (e) may be used as the condition for the approximation judgment may be different. For example, there is a condition that the destination floor of (c) is the same for busy hours such as commuting time and lunch time in the morning and evening, and the condition of (c) may be omitted for other off-hours. .. As a result, it is possible to suppress the allocation of users on different destination floors during busy hours and suppress the increase in the number of stoppages (stopped floors) of the assigned units. On the other hand, during off-hours, close users with different destination floors can be assigned to the same elevator.

The above-mentioned contents can be summarized as shown in the following modifications 1 to 6.

(Modification 1)
Elevator usage information includes information on the time of call occurrence and information on the departure floor.
The group management control device 10 (control device) relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) When the departure floors are the same
It is judged that the usage modes are similar to each other.

(Modification 2)
The elevator usage mode information includes information on the call occurrence time, information on the departure floor, and information on the destination floor.
The group management control device 10 (control device) relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) The departure floor is the same,
(C) When the destination floor is the same
It is judged that the usage modes are similar to each other.

(Modification 3)
The elevator usage mode information includes information on the call occurrence time, information on the departure floor, and the tenant number (an example of tenant information) of the tenant to which the user corresponding to each identification information belongs.
The group management control device 10 (control device) relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) The departure floor is the same,
(D) When the tenant numbers are the same
It is judged that the usage modes are similar to each other.

(Modification example 4)
Elevator usage information includes call occurrence time information, departure floor information, and the installation location of a card reader (an example of an information reader) used by a user corresponding to each card ID (an example of identification information). Including information
The group management control device 10 (control device) relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) The departure floor is the same,
(E) When the position indicated by the installation location is close to a certain degree,
It is judged that the usage modes are similar to each other.

(Modification 5)
Elevator usage mode information includes call occurrence time information, departure floor information, destination floor information, and tenant number (tenant information) of the tenant to which the user corresponding to each card ID (an example of identification information) belongs. (Example) and information on the installation location of the card reader (an example of the information reading device) used by the user corresponding to each card ID.
The group management control device 10 (control device) relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time T seconds.
(B) The departure floor is the same and
When any two of the following conditions are met: (c) the same departure floor, (d) the same tenant number, and (e) the location indicated by the installation location is close to a certain degree.
It is judged that the usage modes are similar to each other.

(Modification 6)
The group management control device 10 (control device) changes the criterion for approximating the usage mode according to the time zone.

(Other embodiments)
In the above embodiment, the case where the information recording medium is an ID card (IC card) has been exemplified. However, the information recording medium is not limited to this, and may be, for example, a mobile communication terminal that functions as an IC card. Further, the information recording medium is not non-contact and readable, but may be contact-readable.

In the above embodiment, in the group DB, the group table is divided for each time zone. However, it is not necessary to divide by time zone. For example, for users who work shifts, the usage mode is similar during the time zone of "13: 00-13: 30" for two days out of five days on weekdays, and "12: 00-" for three days. The usage mode may be approximated in the time zone of 12:30. If the classification by time zone is eliminated, the number of times the usage mode is approximated in one week will be 5 times or more in total, and the group DB is also used for such a user's card ID. You can register with.

In the above-described embodiment, a case where the card ID is recorded as unique identification information for each user on an ID card (an example of an information recording medium) is illustrated. However, the unique identification information for each user may be a user ID that can uniquely identify the user. Further, the user ID may include information that can identify the company.

In the above-described embodiment, the case where the tenant information is a tenant number has been described. However, the tenant information is not limited to this, and may be the company name of the tenant.

In the above-described embodiment, the case where only the card ID is recorded on the ID card has been described. However, information on the default destination floor and the tenant number may be recorded on the ID card. In this case, only the card ID for security authentication needs to be recorded in the card DB of the storage unit of the security server. The security server transmits the information of the default destination floor and the tenant number read from the ID card (IC card) to the group management control device 10.

In the above embodiment, the higher the allocation suitability, the larger the allocation evaluation value, and the case where the first call is assigned to the elevator having the largest allocation evaluation value is illustrated. Further, as a predetermined correction for increasing the allocation aptitude, it is exemplified that a predetermined value A1 (positive value) is added. However, in the present invention, the higher the allocation aptitude, the smaller the allocation evaluation value, and the elevator may be configured to allocate the first call to the elevator having the smallest allocation evaluation value. In this case, for example, as a predetermined correction for increasing the allocation aptitude, the predetermined value A1 (positive value) can be subtracted. Further, the basic evaluation value Acalc can be a value obtained by multiplying the value obtained in the first embodiment by -1.

In the above-described embodiment, the control unit of each device is configured by using a CPU, MPU, etc., and various data are used to perform arithmetic processing based on a program read from the storage unit. Realize the function. That is, each control unit is realized by the cooperation of hardware and software. However, each control unit may be configured by using, for example, only hardware (electronic circuit), FPGA, ASIC, or the like.

In the above embodiment, the network NW is Ethernet, and the input / output interface of each device is configured by using a LAN adapter or the like. However, this is an example, and the network NW may be configured by, for example, a wireless LAN conforming to the IEEE standard, and the input / output interface may be configured by a wireless LAN adapter or the like.

10 Group management control device 11 Control unit 12 Storage unit 13 I / O interface 20 Security gate 20a Gate body 20i Entrance 20e Exit 25 Card reader 26 1st sensor 27 2nd sensor 28 Gate flapper 30 Destination floor registration device 31 Control unit 32 Storage unit 33 I / O interface 34 Display unit 35 Operation unit 36 Card reader 40, 40A to 40F Elevator control device 41 Control unit 42 Storage unit 43 Input / output interface 60, 60A to 60F Elevator 70 Gate display 100 Security server 101 Control unit 102 Storage unit 103 Input / output interface Acc Basic evaluation value A1 Predetermined value car Unit number E (car) Allocation evaluation value of car No. Emax Maximum allocation evaluation value f Departure floor dst Destination floor dir Departure direction Tin 1st predetermined time T 2nd predetermined time grp_car ( id) Group machine number prev_time (id) Last reception time P Number of people best Optimal machine number

Claims (10)

Allocate a call generated based on unique identification information for each user read from the information recording medium possessed by the user by the information reader located at or near the elevator landing to one of the multiple elevators. It is a group management system of elevators equipped with a control device.
In the control device, when the first call based on the first identification information read by the information reading device is generated and the second call based on the second identification information is generated within the first predetermined time. When the second identification information is grouped and registered with the first identification information in the group database, the second call based on the second identification information is used as the first identification information. Based on said first call is configured to be assigned to the assigned elevator,
Each time the identification information is read by the information reading device, the control device records the usage mode information indicating the usage mode of the elevator and the usage history data including the identification information in the usage history database.
The control device extracts usage history data in which the usage modes of the elevator are close to each other by comparing the usage mode information of the usage history data for a predetermined number of days registered in the usage history database with each other. Then, regarding the combination of the identification information included in the approximate usage history data, the number of approximations of the usage mode during the predetermined number of days is counted, and when the counted number of approximations is the predetermined number or more, the identification information related to the combination is used. Group and register in the group database,
Elevator group management system. Elevator usage information includes information on the time of call occurrence and information on the departure floor.
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) When the departure floors are the same
Judging that the usage patterns are similar to each other,
The elevator group management system according to claim 1. The elevator usage mode information includes information on the call occurrence time, information on the departure floor, and information on the destination floor.
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) The departure floor is the same,
(C) When the destination floor is the same
Judging that the usage patterns are similar to each other,
The elevator group management system according to claim 1. The elevator usage mode information includes information on the call occurrence time, information on the departure floor, and tenant information of the tenant to which the user corresponding to each identification information belongs.
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) The departure floor is the same,
(D) When the tenant information is the same
Usage patterns are similar to each other,
The elevator group management system according to claim 1. The elevator usage mode information includes information on the call occurrence time, information on the departure floor, and information on the installation location of the information reading device used by the user corresponding to each identification information.
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) The departure floor is the same,
(E) When the position indicated by the installation location is close to a certain degree,
Judging that the usage patterns are similar to each other,
The elevator group management system according to claim 1. Elevator usage mode information includes call occurrence time information, departure floor information, destination floor information, tenant information of the tenant to which the user corresponding to each identification information belongs, and usage corresponding to each identification information. Including information on the installation location of the information reader used by the person
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) The departure floor is the same and
When either (c) the condition that the destination floor is the same, (d) the condition that the tenant information is the same, and (e) the condition that the location indicated by the installation location is close to a certain degree are satisfied. To,
Judging that the usage patterns are similar to each other,
The elevator group management system according to claim 1. Elevator usage mode information includes call occurrence time information, departure floor information, destination floor information, tenant information of the tenant to which the user corresponding to each identification information belongs, and usage corresponding to each identification information. Includes tenant information of the tenant to which the person belongs and information on the installation location of the information reading device used by the user corresponding to each identification information.
The control device relates to the compared usage history data.
(A) The time difference between the call occurrence times is within the second predetermined time, and
(B) The departure floor is the same,
(C) The destination floor is the same,
(D) The tenant information is the same,
(E) When the position indicated by the installation location is close to a certain degree,
Judging that the usage patterns are similar to each other,
The elevator group management system according to claim 1. In the control device, when the first identification information is read by the information reading device, a group including the first identification information is registered in the group database, but any of the groups included in the group. When an elevator is not assigned to the identification information, the first call based on the first identification information is assigned to the elevators to which the number of calls of the identification information included in the group can be assigned.
The elevator group management system according to any one of claims 1 to 7. The control device divides the time zone into groups and registers the identification information included in the usage history data in which the usage modes of the elevator are close to each other in the group database.
The control device makes the second call when the second identification information is registered in association with the first identification information in the group database with respect to the time zone including the current time. Assign to the elevator to which the first call based on the first identification information is assigned,
The elevator group management system according to any one of claims 1 to 8. The control device changes the criteria for determining the approximation of the usage mode according to the time zone.
The elevator group management system according to any one of claims 1 to 9.

Images