Operation management system, operation management method, and elevator system

Abstract

This operation management system manages location information of an elevator user, and comprises a determination unit that determines location information of a destination floor of the user on the basis of a plurality of location information items indicating a landing at which the user had been present or a car which the user had entered. The determination unit determines, as the location information of the destination floor, location information which indicates a landing and for which preceding location information is location information indicating the car and succeeding location information is not location information indicating the car, said landing being on the user's movement route determined based on the plurality of information items.

Description

Technical Field

[0001] The present invention relates to an operation management system, an operation management method, and an elevator system.

Background Art

[0002] An elevator system capable of operation management by group management can efficiently operate elevators for users by treating a plurality of cars as one group. When a new call occurs on a certain floor, this elevator system assigns an appropriate elevator from the group to the call for each user (hereinafter, also expressed as "assign an elevator"). In a group management elevator system, the time during which the hall call continues is called the "waiting time", and this waiting time is calculated as an important index used for evaluating the performance of the group management elevator system. However, the congestion in the hall and in the car changes according to the time zone, and the waiting time also changes.

[0003] Therefore, as a technique for performing appropriate operation management of elevators for each user, the technique described in Patent Document 1 is known. Patent Document 1 describes that "precise elevator operation management is performed by calculating at least one of the traffic flow of elevators on each floor in a building, or the waiting time, riding time, or service completion time of users."

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Incidentally, when many users board the elevator car, the car stops frequently because each user has a different destination floor. Also, when a user who boarded at the back of the car disembarks, users who boarded at the front of the car often temporarily disembark to make way, even if it's not their destination floor, and then re-board after the user at the back of the car has disembarked. When this happens, even though a user has temporarily disembarked, they are recorded as having completely disembarked. Furthermore, if a user who has temporarily disembarked re-boards the car, it is recorded as a new boarding. As a result, it was not possible to accurately measure elevator usage and properly manage elevator operation.

[0006] The technology described in Patent Document 1, while capable of determining elevator traffic flow from each user's departure and destination floors, could not account for users temporarily disembarking. As a result, even if a user who had temporarily disembarked re-boarded the elevator, they were sometimes counted as having already disembarked, leading to inaccurate figures for the number of people disembarking at their destination floor.

[0007] This invention was made in view of the above circumstances, and aims to accurately grasp the usage status of elevators even when users temporarily disembark on intermediate floors. [Means for solving the problem]

[0008] The operation management system according to the present invention is Multiple This operation management system manages the location information of elevator users. An information receiving unit receives identification information obtained from electronic devices carried by users at the building's landing and inside the elevator car; a log recording unit creates a movement log representing the user's travel route, showing the user's movement in the order of departure floor, inside the elevator car, and to the user's destination floor, based on the location information attached to the identification information received by the information receiving unit, namely location information indicating the landing and location information indicating the elevator car; and records the arrival time at the landing, the boarding time when the user enters the elevator car, and the disembarking time when the user disembarks from the elevator car in the movement log. Multiple location information indicating the boarding area where the passenger was, or the elevator car the passenger boarded. Report Of the user travel routes requested, When the location information indicating the landing immediately preceding the location information indicating the first elevator car is determined to be the location information of the departure floor, and the location information indicating the landing immediately following the location information indicating the first elevator car is obtained, it is determined that the user temporarily disembarked at the transfer floor, and the user boarded a second elevator which is different from the first elevator from which they temporarily disembarked, Previous location information , the second elevator This is location information indicating the basket, and the location information immediately following it is , the second elevator The location information indicating the landing, rather than the location information indicating the elevator car, is determined to be the location information for the destination floor. The system comprises: a determination unit; a learning unit that learns elevator usage based on movement logs, generates traffic modes specific to the building where the elevator is installed, learns trends in changes to traffic modes, identifies the current traffic mode, and generates learning results that predict the number of users per floor per hour; and an assignment unit that selects an elevator car that can be assigned to a call made at the landing and dispatches the assigned elevator car to the departure floor based on the learning results and the identified current traffic mode. . [Effects of the Invention]

[0009] According to the present invention, even if a user temporarily disembarks at an intermediate floor, the usage status of the elevator can be accurately recorded. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing an example of the overall configuration of an elevator system according to the first embodiment of the present invention. [Figure 2] This figure shows examples of various devices installed in the landing and elevator car according to the first embodiment of the present invention. [Figure 3] This figure shows an example of information that the boarding area notification unit according to the first embodiment of the present invention provides. [Figure 4] This is a block diagram showing an example of the hardware configuration of a computer according to the first embodiment of the present invention. [Figure 5] This diagram shows how users move from the first floor to the third floor. [Figure 6] This diagram shows a passenger temporarily disembarking while moving from the first floor to the third floor. [Figure 7] This figure shows an example of the configuration of location information data according to the first embodiment of the present invention. [Figure 8] This figure shows an example of the configuration of a movement log according to the first embodiment of the present invention. [Figure 9] This flowchart shows an example of the overall processing of the operation management system according to the first embodiment of the present invention. [Figure 10] This is a flowchart showing an example of the landing detection process according to the first embodiment of the present invention. [Figure 11] This flowchart shows an example of the in-car detection process according to the first embodiment of the present invention. [Figure 12] This flowchart shows an example of the movement consistency determination process according to the first embodiment of the present invention. [Figure 13] This figure shows examples of usage patterns and traffic modes for each floor according to the first embodiment of the present invention. [Figure 14]It is a diagram showing an example of an objective floor utilization number table according to the first embodiment of the present invention. [Figure 15] It is a block diagram showing an example of the overall configuration of an elevator system according to the second embodiment of the present invention. [Figure 16] It is a diagram showing an example of the configuration of two elevators (shuttle type elevator system) according to the third embodiment of the present invention.

Embodiments for Carrying out the Invention

[0011] Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same function or configuration are denoted by the same reference numerals, and redundant descriptions are omitted.

[0012] [First Embodiment] FIG. 1 is a block diagram showing an example of the overall configuration of an elevator system 200 according to the first embodiment of the present invention.

[0013] The elevator system 200 is a system for performing group management control of elevators numbered 1 to N. This elevator system 200 includes an operation management system 100, elevators 15(1) to 15(N) provided for each unit, elevator control systems 25(1) to 25(N), in-car reception units 21(1) to 21(N), a landing reception unit 31 provided for each floor, and a landing notification unit 32.

[0014] The operation management system 100 is provided, for example, at the top of a building, and elevators 15(1) to 15(N) numbered 1 to N are installed in the same building. Then, the operation management system 100 manages the operation of elevators 15(1) to 15(N) numbered 1 to N and also manages the movement information of users 10 of elevator 15 (see FIG. 2 described later). This operation management system 100 includes a learning unit 110, a time calculation unit 12, an elevator allocation unit 130, an information reception unit 140, a log processing unit 150, and a guidance display command unit 160.

[0015] The learning unit 110 learns the usage status of elevators 15(1) to 15(N) from units 1 to N based on the movement log 153 and generates learning results. For example, it learns that there are many users 10 (see Figure 2) going from the 1st floor to the office floor between 8:00 and 9:00, and many users 10 going from the office floor to the cafeteria floor between 12:00 and 12:30. It learns the increase and decrease in users 10 from time to time, as well as the changes in the departure and destination floors of users 10. Based on the usage distribution 61 for each floor shown in Figure 13, the traffic mode distribution 62, and the table 63 showing the number of users to destination floors by time of day shown in Figure 14, the learning unit 110 learns the usage status of elevators 15(1) to 15(N). Here, the departure floor is the floor on which a car call is generated when user 10 presses the car call button and user 10 first boards the elevator car 20. User 10 can move to other floors by boarding the elevator car 20 that has arrived at the departure floor. The departure floor and the departure floor from which user 10 leaves the platform can be considered the same. The destination floor is the floor from which user 10 disembarks, and this destination floor is registered using the in-car button inside the elevator car 20.

[0016] However, if another user 10 who arrived at boarding area 30 earlier has already pressed the elevator call button at boarding area 30, the user 10 who arrives at boarding area 30 later will not press the elevator call button again. Similarly, if the destination floor has already been registered by another user 10 who boarded elevator car 20 earlier, the user 10 who boards elevator car 20 later will not register the destination floor again. For this reason, the operation management system 100 needs to know which floors the user 10 is departing from and which is their destination floor from the location information obtained from elevator car 20 and boarding area 30 in order to manage the user 10's travel route.

[0017] In the following explanation, elevators 15(1) to 15(N) will not be distinguished and will be referred to as "elevator 15". Similarly, cars 20(1) to 20(N) will not be distinguished and will be referred to as "car 20". Similarly, in-car receiving units 21(1) to 21(N) will not be distinguished and will be referred to as "in-car receiving unit 21". Similarly, in-car elevator control systems 25(1) to N will not be distinguished and will be referred to as "elevator control system 25".

[0018] The learning unit 110 includes a floor-specific user prediction unit 111 that predicts the number of users 10 on each floor. The floor-specific user prediction unit 111 generates learning results that predict the number of users 10 on each floor at each time interval, enabling the elevator allocation unit 130 to prioritize allocating elevator cars 20 to floors with a large number of users 10. Therefore, the prediction results of the number of users 10 by the floor-specific user prediction unit 111 become the learning results created by the learning unit 110.

[0019] The time calculation unit 120 calculates the waiting time, boarding time, and service completion time for each user 10 in the travel log 153 recorded by the log recording unit 151. The detailed configuration of the travel log 153 is explained in Figure 8 below. The waiting time is calculated by subtracting the boarding time from the boarding time. The boarding time is calculated by subtracting the boarding time from the alighting time. The service completion time is calculated by subtracting the boarding time from the alighting time.

[0020] The elevator allocation unit 130 (an example of an allocation unit) selects an elevator 15 that can be assigned to a call made at the landing 30 based on the learning results created by the learning unit 110, and dispatches the elevator car 20 of the assigned elevator 15 to the departure floor of the call. For example, the elevator allocation unit 130 instructs one of the elevator control systems 25(1) to 25(N) to dispatch the elevator car 20 according to the number of users 10 for each floor predicted by the floor-specific passenger prediction unit 111. At this time, the elevator allocation unit 130 uses the learning results created by the learning unit 110 to perform group control management, which manages the operation of each elevator 15 according to the time of day.

[0021] The information receiving unit 140 receives location information data 50 transmitted from the landing receiving unit 31 and location information data 50 transmitted from the car receiving unit 21. A detailed example of the configuration of the location information data 50 is shown in Figure 7, which will be described later. The information receiving unit 140 can receive individual IDs (examples of identification information) obtained from mobile terminals 11 (examples of electronic devices) carried by users 10 in the landing 30 and elevator car 20. For example, the information receiving unit 140 receives location information data 50 including the individual ID of user 10 received by the landing receiving unit 31. The information receiving unit 140 also receives location information data 50 including the individual ID of user 10 received by the car receiving units 21(1) to 21(N). The location information data 50 received by the information receiving unit 140 is transferred to the elevator allocation unit 130 and the log processing unit 150 in the operation management system 100.

[0022] The log processing unit 150 creates a travel log 153 used in the operation management system 100. This travel log 153 represents the travel route of the user 10, and the travel route is indicated by the user 10's travel route (passenger flow) in the order of departure floor, inside the elevator car 20, and destination floor, based on the information received by the information receiving unit 140. Furthermore, if a user 10 who has boarded the elevator car 20 temporarily disembarks from the elevator car 20 at an intermediate floor on the way to the destination floor and re-boards the elevator car 20 within the first hour (for example, within 30 seconds), the log processing unit 150 excludes the intermediate floor where the user 10 temporarily disembarked from the travel route. Through this processing by the log processing unit 150, even if the user 10 temporarily disembarks, the subsequent travel route of the user 10 can be correctly recorded. The log processing unit 150 includes a log recording unit 151 and a log determination unit 152.

[0023] The log recording unit 151 records the movement log 153 in the RAM 43 and non-volatile storage 45, etc., as shown in Figure 4, which will be described later. Based on the location information data 50 received by the information receiving unit 140 from the landing receiving unit 31, the log recording unit 151 records the arrival time of the user 10 when they arrived at the landing 30 and the disembarkation time when the user 10 disembarked from the car 20 in the movement log 153. Based on the information received by the information receiving unit 140 from the car in-car receiving unit 21, the log recording unit 151 also records the boarding time when the user 10 boarded the car 20 in the movement log 153. The log recording unit 151 then records the waiting time, boarding time, service completion time, etc., calculated based on the individual ID, radio wave detection time, and radio wave detection location (floor) information input from the information receiving unit 140 in the movement log 153. A detailed example of the configuration of the movement log 153 will be explained in Figure 8, which will be described later.

[0024] The log determination unit 152 (an example of a determination unit) determines the location information of the user 10's destination floor based on the location information that indicates the boarding area 30 where the user 10 was, or the elevator car 20 that the user 10 boarded, as shown in the location information data 50 received by the information reception unit 140. Here, the log determination unit 152 determines that the location information of the boarding area 30, where the immediately preceding location information indicates the elevator car 20, and the immediately following location information does not indicate the elevator car 20, is the location information of the destination floor from among the user 10's travel path 51 obtained from multiple location information. In this process, the log determination unit 152 uses the immediately preceding location information and the immediately following location information to determine the location information of the destination floor, with the time when the elevator car 20 arrived at the boarding area 30 as the reference point. Furthermore, by including the condition that the immediately following location information is not location information indicating elevator car 20, the log determination unit 152 does not determine the destination floor when user 10 is still on elevator car 20 and has not yet disembarked, i.e., location information indicating platform 30 cannot be obtained.

[0025] If the information reception unit 140 has only received location data 50 up to the point when user 10 temporarily disembarked at an intermediate floor, the log determination unit 152 may incorrectly determine the intermediate floor as the destination floor based on the location information indicating the boarding area 30 at the time user 10 temporarily disembarked. However, if user 10 then boards the elevator car 20 again at an intermediate floor and travels to the destination floor, the information reception unit 140 will receive location data 50 up to the point when user 10 disembarks at the destination floor. Therefore, the log determination unit 152 can correctly determine the destination floor based on the location information indicating the boarding area 30 at the time user 10 disembarked. In this way, even if user 10 temporarily disembarks at an intermediate floor, the log determination unit 152 can determine the destination floor when user 10 boards the elevator car 20 again and disembarks. Therefore, even if user 10 boards the elevator car 20 and travels without registering a destination floor, the log determination unit 152 can correctly determine user 10's destination floor.

[0026] Furthermore, the log determination unit 152 determines the location information for each user 10 who boards or alights from the elevator car 20 at the departure floor from which the user 10 departed. The log determination unit 152 then determines that the location information indicating the boarding area 30, where the immediate next location information in the user 10's travel path 51 indicates the elevator car 20, and the immediate next location information does not indicate the elevator car 20, is the location information of the departure floor from which the user 10 departed. In this case as well, the log determination unit 152 uses the immediate next location information and the immediate next location information as the reference point when the elevator car 20 arrives at the boarding area 30 to determine the location information of the departure floor. By including the condition that the immediate next location information does not indicate the elevator car 20, the possibility of mistakenly identifying an intermediate floor as the departure floor when the user 10 temporarily alights from the elevator car 20 at an intermediate floor can be eliminated. Therefore, the log determination unit 152 can correctly determine the departure floor of the user 10 even if the user 10 does not press the elevator call button at the departure floor landing 30.

[0027] The log determination unit 152 then determines the consistency of the contents of the movement log 153 recorded in the log recording unit 151. Therefore, the log determination unit 152 can also determine the departure floor and destination floor based on the movement log 153. Furthermore, if the information receiving unit 140 receives information from the in-car receiving unit 21 within two hours (for example, within 5 minutes) after the disembarkation time is recorded in the movement log 153, the log determination unit 152 determines that the user 10 who disembarked from the car 20 has temporarily disembarked. In other words, even if user 10 disembarks, if user 10 boards the car 20 again within one hour (for example, within 30 seconds), the log determination unit 152 determines that user 10 has temporarily disembarked. Therefore, it is correctly determined that user 10 has temporarily disembarked.

[0028] On the other hand, if the log determination unit 152 determines that user 10 has temporarily disembarked, the log recording unit 151 will not record the disembarkation time in the movement log 153 based on the information received by the information reception unit 140 from the car receiving unit 21 within the first hour (for example, within 30 seconds). This is because if the time when user 10 temporarily disembarked is recorded as the disembarkation time in the movement log 153, it will not be consistent with the disembarkation time recorded after user 10 re-boards the car 20 and moves to the destination floor. For this reason, if user 10 temporarily disembarks, the disembarkation time at an intermediate floor is initially recorded in the movement log 153, but after the user disembarks at the destination floor, the disembarkation time at the destination floor is overwritten and recorded in the movement log 153.

[0029] Furthermore, if the log recording unit 151 does not receive location information indicating the elevator car 20 within a predetermined time (for example, two hours) after the information receiving unit 140 has received location information indicating the elevator car 30, it deletes the location information indicating the elevator car 30 that was temporarily stored in RAM or the like. Also, if the log determination unit 152 determines that the user 10 whose arrival time at the elevator car was recorded did not use the elevator car 15 if the boarding time is not recorded in the movement log 153 within two hours (for example, within 5 minutes) after the arrival time at the elevator car is recorded in the movement log 153, it determines that the user 10 whose arrival time at the elevator car was recorded did not use the elevator car 15. In this case, the log recording unit 151 discards the information of the user 10 who was determined not to have used the elevator car 15 from the movement log 153. Therefore, the information of the user 10 who did not use the elevator car 15 does not remain in the movement log 153.

[0030] In the following explanation, among the records in the movement log 153, records in which the elevator service has not yet been completed will be referred to as "logs in progress," and records in which the elevator service has been completed will be referred to as "confirmed logs." The elevator service is a service that moves user 10 from the departure floor where the elevator call originated to the destination floor. The log determination unit 152 may discard logs in progress based on the determination of each time in the logs in progress, but it will save confirmed logs without discarding them.

[0031] The information display command unit 160 (an example of a command unit) commands the landing notification unit 32 to display information. Based on the departure floor, destination floor, and service completion time recorded in the movement log 153, the information display command unit 160 commands the landing notification unit 32 installed at the landing 30 to notify the time required to use the elevator 15 and alternative modes of transportation that the user 10 can choose from besides the elevator 15.

[0032] Next, we will explain an example of the configuration of the elevator control system for each unit. The elevator control system 25(1) for Unit 1 controls the operation of elevator 15(1) for Unit 1. The operation of elevator 15(1) includes, for example, the up and down movement of the car 20, the opening and closing of the car 20 doors and landing doors, air conditioning inside the car 20, receiving car call information from landing buttons (not shown), and receiving destination floor information from buttons inside the car.

[0033] The landing receiver 31 is installed at the landing 30 on each floor (M floor in Figure 1) of the elevator 15 installed in the building. This landing receiver 31 can receive radio waves within a certain range. Therefore, the landing receiver 31 receives radio waves from a portable terminal 11 (an example of an electronic device) held by a user 10 in the landing 30. Depending on the area of ​​the landing 30, one or more landing receivers 31 are installed. If the range in which radio waves can be received is larger than the area of ​​the landing 30, one landing receiver 31 is installed in the landing 30. If the range in which radio waves can be received is smaller than the area of ​​the landing 30, multiple landing receivers 31 are installed so that the range in which radio waves can be received covers the landing 30.

[0034] The radio waves transmitted from the mobile terminal 11 contain unique identification information for the mobile terminal 11, such as the MAC (Media Access Control) address of the mobile terminal 11. The MAC address of the mobile terminal 11 is used as information that can effectively identify the user 10. Therefore, the landing reception unit 31 detects the user 10 present at the landing 30 based on the radio waves received from the mobile terminal 11 carried by the user 10. The landing reception unit 31 then creates an individual ID by concealing the identification information of the mobile terminal 11 extracted from the radio waves. As a method of concealment, hashing or other methods that irreversibly encrypt the information may be used. In this case, it becomes difficult to recover the identification information of the mobile terminal 11 from the created individual ID.

[0035] The elevator landing receiving unit 31 transmits location information data 50, which includes an individual ID, the time of radio wave detection, and information about the location where the radio wave was detected, to the operation management system 100 via the network N. Network N can be an in-building LAN installed within the building, or a communication line used by each elevator 15 to send and receive data. The information receiving unit 140 receives various types of information, including the location information data 50. The information received by the information receiving unit 140 is temporarily stored by the log recording unit 151, and necessary information is recorded in the movement log 153.

[0036] Furthermore, if multiple landing receivers 31 are installed on a single floor, when a user 10 moves between landings, each of the landing receivers 31 may receive radio waves from the mobile terminal 11. In this case, the information received by the information reception unit 140 from the landing receiver 31 that first received the radio waves is recorded in the movement log 153.

[0037] The landing information unit 32 is installed at the landing 30 on each floor (M floor in Figure 1). This landing information unit 32 provides various information to users 10 at the landing 30 by displaying information commands from the information display command unit 160. For example, the landing information unit 32 provides information on the time required to use the elevator 15, as commanded by the information display command unit 160, and alternative modes of transportation that users 10 can choose from. This allows users 10 at the landing 30 to check the usage status of the elevator 15 or to choose other means of transportation.

[0038] The in-car receiving unit 21 is installed inside the elevator car 20 of the elevator 15. The in-car receiving unit 21 can receive radio waves within a certain range. This certain range for the in-car receiving unit 21 includes, for example, the entire inside of the car 20. Therefore, the in-car receiving unit 21 receives radio waves from electronic devices such as mobile terminals 11 carried by users 10 who have boarded the car 20. These radio waves carry identification information unique to the mobile terminal 11, such as the MAC address of the mobile terminal 11. Therefore, the in-car receiving unit 21 detects users 10 who have boarded the car 20 based on the radio waves received from the mobile terminal 11 carried by the users 10 who have boarded the car 20. The in-car receiving unit 21 then creates an individual ID by concealing the identification information of the mobile terminal 11 extracted from the radio waves.

[0039] The in-car receiving unit 21 transmits location information data 50, which includes an individual ID, the time of radio wave detection, and information on the location of radio wave detection, to the operation management system 100 via the network N, and the information receiving unit 140 receives various information, including the location information data 50. The information received by the information receiving unit 140 is recorded in the movement log 153 by the log recording unit 151.

[0040] The operation of the elevator control system 25(N) and the in-car receiving unit 21(N) of Unit N is the same as that of the elevator control system 25(1) and the in-car receiving unit 21(1) of Unit 1, respectively, so a detailed explanation is omitted.

[0041] The wireless radio waves emitted by the mobile terminal 11 may include, for example, Bluetooth®, Wi-Fi®, etc. As mentioned above, the MAC address of the mobile terminal 11 is included in the wireless radio waves as information for identifying the mobile terminal 11. Furthermore, the mobile terminal 11 can arbitrarily change the strength of the wireless radio waves. Therefore, when a user 10 uses the elevator 15, the mobile terminal 11 can weaken the strength of the wireless radio waves, thereby controlling the in-car receiving unit 21 and the landing receiving unit 31 so that they do not receive the wireless radio waves simultaneously. Such control is effective when the car door 22 (see Figure 2) opens on an intermediate floor and the user 10 temporarily disembarks. In this example, because the strength of the wireless radio waves is weakened, the landing receiving unit 31 installed at the landing 30 on an intermediate floor does not receive the wireless radio waves emitted by the mobile terminals 11 of other users 10 who have not temporarily disembarked but whose car doors 22 are open. Therefore, only the information of the disembarking user 10 is recorded in the movement log 153 by the log recording unit 151.

[0042] Examples of mobile devices 11 include smartphones and tablet devices. Additionally, a simple device (an example of an electronic device) that allows a guardian to check the location information of an infant is also envisioned as a mobile device 11 that an infant can carry. Even with such devices, the log recording unit 151 can determine the number of devices connected to the in-car receiving unit 21 and the landing receiving unit 31 via radio waves as the number of users 10.

[0043] Figure 2 shows examples of various devices installed on the landing 30 and the elevator car 20. Here, a passenger 10 is shown standing on the landing 30, waiting for the elevator car 20 to arrive.

[0044] The landing 30 shown on the left side of Figure 2 is equipped with a landing receiver 31 and a landing notification unit 32. The landing receiver 31 is installed on the ceiling of the landing 30 to receive radio waves from the mobile terminal 11 held by the user 10 over a wide area. The landing notification unit 32 is installed on the ceiling near the elevator car 20 to make it easier for the user 10 to check the information.

[0045] A receiving unit 21 is installed on the ceiling of the elevator car 20, as shown on the right side of Figure 2. When the elevator car door 22 opens and a passenger 10 boards the elevator car 20, the receiving unit 21 receives the radio waves emitted by the mobile terminal 11 held by the passenger 10.

[0046] Figure 3 shows an example of information broadcast by the landing notification unit 32. The landing notification unit 32 shown in Figure 3 is assumed to be installed at the landing on the first floor.

[0047] A display device such as digital signage is envisioned as the landing notification unit 32. The landing notification unit 32 displays the estimated travel time for each floor when a user 10 designates a different floor as their destination floor from the departure floor of the landing 30 where the landing notification unit 32 is installed. For example, suppose the departure floor is the 1st floor and the 2nd floor is designated as the destination floor. In this case, the elevator car 20 moves from an upper floor to the 1st floor, and there is time for multiple users to disembark from the car 20 when it arrives at the 1st floor. After that, user 10, who has registered the 2nd floor as their destination floor, boards the car 20, and when the car 20 arrives at the 2nd floor, user 10 disembarks from the car 20. The time taken for this series of actions is defined as the estimated travel time, and Figure 3 shows an example where the elevator allocation unit 130 predicts the travel time as 1 minute. Similarly, when another floor is designated as the destination floor, the estimated travel time predicted by the elevator allocation unit 130 is displayed on the landing notification unit 32.

[0048] Incidentally, if the travel time to the destination floor is long, user 10 may consider using the escalator to go up to the second floor. Therefore, the landing information unit 32 also displays a sign indicating the location of the escalator as an alternative mode of transportation to the elevator. Alternatively, a sign indicating the location of the stairs may be displayed instead of the escalator. Furthermore, the sign does not need to be displayed at all times; it may be turned off when the elevator car 20 arrives at the departure floor.

[0049] Next, we will describe the hardware configuration of the computer 40 that constitutes the operation management system 100. Figure 4 is a block diagram showing an example of the hardware configuration of the computer 40. The computer 40 is an example of hardware used as a computer capable of operating as the operation management system 100 according to this embodiment. The operation management system 100 according to this embodiment realizes an elevator operation management method performed by the operation of each functional block shown in Figures 9 to 12, which will be described later, through the operation of a program by the computer 40 (computer).

[0050] The computer 40 comprises a CPU (Central Processing Unit) 41, ROM (Read Only Memory) 42, and RAM (Random Access Memory) 43, each connected to a bus 44. Furthermore, the computer 40 includes non-volatile storage 45 and a network interface 46.

[0051] The CPU 41 reads the program code of the software that implements each function according to this embodiment from the ROM 42, loads it into the RAM 43, and executes it. Variables and parameters that occur during the calculation process of the CPU 41 are temporarily written to the RAM 43, and these variables and parameters are read out by the CPU 41 as appropriate. However, an MPU (Micro Processing Unit) may be used instead of the CPU 41. The operation of each function unit in the operation management system 100 shown in Figure 1 is realized by the CPU 41 executing the program.

[0052] Examples of non-volatile storage 45 include HDDs (Hard Disk Drives), SSDs (Solid State Drives), flexible disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, or non-volatile memory. This non-volatile storage 45 stores the OS (Operating System), various parameters, and programs necessary for the computer 40 to function. The ROM 42 and non-volatile storage 45 store programs and data necessary for the CPU 41 to operate and are used as an example of a computer-readable, non-transient storage medium that stores programs executed by the computer 40. The movement log 153 shown in Figure 1 is stored in the RAM 43 or non-volatile storage 45.

[0053] The network interface 46 can, for example, be a NIC (Network Interface Card), and various types of data can be sent and received between devices via a LAN (Local Area Network), dedicated line, etc., connected to the terminals of the NIC.

[0054] Next, we will explain how user 10 uses the elevator 15, referring to Figures 5 and 6. Figure 5 shows how user 10 moves from the first floor to the third floor. In the following figures, the mobile terminal 11 may be omitted to avoid making the diagrams too complex. Also, since the in-car receiving unit 21 and the landing receiving unit 31 transmit location information data 50 to the operation management system 10 each time they receive radio waves from the mobile terminal 11, the description of the process of transmitting location information data 50 will be omitted.

[0055] (Time T1) First, when user 10 arrives at the landing on the first floor, the landing receiver 31 installed at the landing on the first floor receives radio waves emitted by the mobile terminal 11 held by user 10. Upon receiving these radio waves, the landing receiver 31 on the first floor detects that user 10 is at the landing on the first floor. At time T1, the elevator car 20 is descending from an upper floor to the first floor.

[0056] (Time T2) When elevator car 20 arrives on the first floor and passenger 10 boards elevator car 20, the in-car receiver 21 installed in elevator car 20 receives radio waves emitted by the mobile device 11 held by passenger 10. Upon receiving these radio waves, the in-car receiver 21 detects that passenger 10 has boarded elevator car 20.

[0057] (Time T3) When elevator car 20 arrives at the destination floor, the 3rd floor, and passenger 10 disembarks from elevator car 20, the landing receiver 31 installed at the landing on the 3rd floor receives radio waves emitted by the mobile terminal 11 held by passenger 10. Upon receiving these radio waves, the landing receiver 31 at the landing on the 3rd floor detects that passenger 10 is at the landing on the 3rd floor.

[0058] Figure 6 shows a passenger 10 temporarily disembarking while moving from the first floor to the third floor.

[0059] (Time T1, T2) As in Figure 5, at time T1, the platform receiver 31 receives radio waves from the mobile terminal 11 and detects the user 10 on the first floor, and at time T2, the car receiver 21 receives radio waves from the mobile terminal 11 and detects the user 10 in the car 20. However, the car 20 also has other users (not shown) in it, close to its passenger capacity, and the last user to board, 10, is assumed to be near the car door 22.

[0060] (Time T3) Let's assume elevator car 20 arrives at the second floor, which is an intermediate floor. The second floor is not the destination floor registered by user 10. However, because other users are getting off from the back of elevator car 20, user 10 gets off elevator car 20 to make way for them. In this case, the landing receiver 31 installed at the second-floor landing receives radio waves emitted by the mobile terminal 11 held by user 10. Upon receiving these radio waves, the landing receiver 31 detects that user 10 is at the third-floor landing. Subsequently, user 10 gets back into elevator car 20. Therefore, the elevator car receiver 21 detects that user 10 has boarded elevator car 20 again.

[0061] (Time T4) When passenger 10 boards the elevator car 20, which is stopped on the second floor, the in-car receiver 21 installed in the elevator car 20 receives radio waves emitted from the mobile device 11 held by passenger 10. Upon receiving these radio waves, the in-car receiver 21 detects that passenger 10 has boarded the elevator car 20.

[0062] (Time T5) When elevator car 20 arrives at its destination floor, the 3rd floor, and passenger 10 disembarks from elevator car 20, the landing receiver 31 installed at the landing on the 3rd floor receives radio waves emitted by the mobile device 11 held by passenger 10. Upon receiving these radio waves, the landing receiver 31 detects that passenger 10 is at the landing on the 3rd floor.

[0063] In conventional operation management systems, if user 10 temporarily disembarks at a floor other than the designated destination floor, the number of users on board the elevator car 20 is counted as having decreased. As a result, even if the user subsequently disembarks at the registered destination floor, the numbers may not match. Therefore, the operation management system 100 according to this embodiment is designed to accurately determine the number of users 10 on each floor, as well as the departure and destination floors of users 10, even if user 10 temporarily disembarks.

[0064] Figure 7 shows an example of the configuration of location information data 50. When user 10 uses elevator 15, location information data 50 generated in association with individual IDs received from the mobile terminal 11 at two landings 30 (departure floor and destination floor) and elevator car 20 is transmitted to the operation management system 100. As a result, the operation management system 100 acquires at least three or more pieces of location information data 50 for each user 10. Each piece of location information data 50 has the same individual ID, the location information data 50 generated by the landing receiving unit 31 includes the landing reception time, and the location information data 50 generated by the car receiving unit 21 includes the elevator car reception time. The location information of user 10 is then managed by the location information data 50. The car receiving unit 21 and the landing receiving unit 31 transmit the location information data 50 to the operation management system 100 at predetermined time intervals.

[0065] As described above, the location information data 50 consists of the following items: individual ID, landing floor, landing reception time, elevator car reception time, and elevator car number. The No. item at the left end of the location information data 50 is used by the log processing unit 150 to identify the generation order of the location information data 50. The location information data 50 transmitted from the elevator car reception unit 21 includes the individual ID, elevator car reception time, and elevator car number. The location information data 50 transmitted from the landing reception unit 31 includes the individual ID, landing floor, and landing reception time. Items with a hyphen in the diagram indicate that no information is included in that item. The location information included in the location information data 50 is the location information attached to the individual ID received by the information reception unit 140. For example, the landing floor is the location information that indicates landing 30. Also, the elevator car number is the location information that indicates elevator car 20. Furthermore, the time information included in the location data 50 is the time information attached to each individual ID received by the information reception unit 140.

[0066] In the location information data 50, only the floor information is recorded in the boarding floor item; the departure floor and destination floor are not distinguished. Furthermore, the location information data 50 is numbered No. 1, No. 2, ... by the log recording unit 151 in order of earliest boarding reception time or elevator car reception time, and temporarily stored in the RAM 43 or non-volatile storage 45 shown in Figure 4 for each individual ID. Note that even with the same individual ID, after the second time period (for example, 5 minutes) described later has elapsed, when the information reception unit 140 next receives the location information data 50, it is numbered again as No. 1, No. 2, ... and temporarily stored in the RAM 43 or non-volatile storage 45 shown in Figure 4.

[0067] Here, we will explain the contents of the location information data 50 assuming that user 10 boarded the elevator car 20 on the 1st floor, temporarily disembarked on the 2nd floor, and then disembarked from the elevator car 20 on the 5th floor. The white arrows shown in the figure visualize user 10's movement path 51. (1) When user 10 is at boarding area 30 on the 1st floor (departure floor), boarding area receiving unit 31 on the 1st floor receives user 10's individual ID and transmits location information data 50 No. 1 to the operation management system 100. The boarding reception time for location information data 50 No. 1 is "08:20:00", and boarding area 30 is on the 1st floor. (2) When user 10 boards the elevator car 20 which has arrived on the 1st floor (departure floor), the elevator car receiving unit 21 receives user 10's individual ID and transmits location data 50 No. 2 to the operation management system 100. The elevator car reception time for location data 50 No. 2 is "08:21:00" and the elevator car number is "1". (3) When user 10 temporarily disembarks from the elevator car 20 at boarding area 30 on the second floor (an intermediate floor), the boarding area receiving unit 31 on the second floor receives user 10's individual ID and transmits location data 50 No. 3 to the operation management system 100. The boarding reception time for location data 50 No. 3 is "08:21:10", and boarding area 30 is on the second floor. (4) When user 10 boards the elevator car 20 which is stopped on the second floor (intermediate floor), the elevator car receiver 21 receives user 10's individual ID and transmits location data 50 No. 4 to the operation management system 100. The elevator car reception time for location data 50 No. 4 is "08:21:20", and the elevator car number is "1". (5) When user 10 disembarks from the elevator car 20 at the boarding area 30 on the 5th floor (destination floor), the boarding area receiving unit 31 on the 5th floor receives user 10's individual ID and transmits location data 50 No. 5 to the operation management system 100. The boarding reception time for location data 50 No. 5 is "08:22:00", and boarding area 30 is on the 5th floor.

[0068] The log determination unit 152 refers to the location information data 50 shown in Figure 7 and uses time information representing the time when the location information was acquired to determine the location information for the departure floor and the destination floor. The location information for the departure floor and the destination floor is the location information acquired by the landing 30 and the elevator car 20 within a predetermined time (for example, the second hour). When using time information, the log determination unit 152 can determine the location information indicating the landing 30, which is the first location in the user's travel path 51, as the departure floor location information, and the location information indicating the landing 30, which is the last location in the time information, as the destination floor location information. As shown in Figure 7, location information data No. 1 50 is the location information indicating the landing 30, which is the first location in the time information, and the departure floor is determined to be the 1st floor. Also, location information data No. 5 50 is the location information indicating the landing 30, which is the last location in the time information, and the destination floor is determined to be the 5th floor.

[0069] Furthermore, the log determination unit 152 can also determine the departure floor and destination floor of the user 10 based not on time information, but on the sequential relationship between the location information indicating the elevator car 20 and the location information indicating the landing 30. In this case, the log determination unit 152 can determine that the location information indicating the landing 30 immediately preceding the location information indicating the first elevator car 20 in the user 10's travel path 51 is the departure floor location information, and the location information indicating the landing 30 immediately following the location information indicating the last elevator car 20 is the destination floor location information. As shown in Figure 7, location information data No. 2 50 is the location information indicating the first elevator car 20. Then, location information data No. 1 50 immediately preceding location information data No. 2 50 is the location information indicating the landing 30, and it is determined that the departure floor is the 1st floor. Also, location information data No. 4 50 is the location information indicating the last elevator car 20. Then, the location information data No. 5, which immediately follows the location information data No. 4, indicates the location of platform 30, and it is determined that the destination floor is the 5th floor.

[0070] The logging unit 151 combines multiple location data 50 and performs various calculations to create the movement log 153 shown in Figure 8. Here, an example of the configuration of the movement log 153 will be explained with reference to Figure 8. Figure 8 shows an example of the configuration of the movement log 153. The movement log 153 is recorded by the log recording unit 151 shown in Figure 1 and stored in the RAM 43 or non-volatile storage 45 shown in Figure 4.

[0071] The travel log 153 consists of a table containing the following items: individual ID, departure floor, destination floor, arrival time at boarding point, boarding time, alighting time, waiting time, boarding time, service completion time, END, and Warning. Note that the No. on the left end of the travel log 153 is used to identify the record and does not need to be stored in the travel log 153.

[0072] The individual ID field stores an individual ID that conceals information that uniquely identifies the mobile device 11, such as the MAC address of the mobile device 11. It is not possible to trace the attributes of the user 10 from the individual ID. The departure floor field stores the departure floor at which the elevator call occurred when user 10 registered the call. This departure floor is the floor at which the landing reception unit 31 detects the mobile terminal 11. The departure floor is, for example, the landing floor of location information data 50 No. 1, in which the landing reception time was first recorded, as shown in Figure 7. Even if user 10 does not register a call, the departure floor is recorded by the log recording unit 151 based on the time when the individual ID was first received at the landing 30, as shown in Figure 7.

[0073] The destination floor field stores the destination floor registered by user 10. The destination floor is, for example, the floor of location information data 50 No. 5, which has the last recorded boarding reception time among the location information data 50 shown in Figure 7. Even if user 10 does not register a destination floor, the log recording unit 151 records the destination floor based on the time when the individual ID was last received at boarding 30, as shown in Figure 7.

[0074] The boarding arrival time field stores the time when user 10 arrived at boarding 30. The boarding arrival time is, for example, the boarding reception time of location information data 50 No. 1, which is the first location information data 50 shown in Figure 7 to have the boarding reception time recorded. However, if user 10 passes near boarding reception unit 31 and then returns to the vicinity of boarding reception unit 31, or if user 10 is near the boundary of the radio wave detection range of boarding reception unit 31, the radio waves of the mobile terminal 11 may be detected repeatedly at the same boarding within a certain period of time. In this case, the boarding arrival time will be the time when boarding reception unit 31 first detected the radio waves of the mobile terminal 11.

[0075] The boarding time field stores the time when user 10 boarded elevator car 20. The boarding time is, for example, the elevator car reception time of location data 50 No. 1, which is the first location data 50 shown in Figure 7 to have the boarding time recorded. Even after elevator car 20 arrives at the departure floor, the arrival time at the boarding area and the boarding time will not be the same because it takes time for other users to disembark from elevator car 20 and for user 10 to board elevator car 20. As shown in records No. 1 and No. 2, the boarding time is the same even though the departure floor is different because it was recorded by elevators 15 of different numbers.

[0076] The disembarkation time field stores the time when user 10 disembarked from the elevator car 20. The disembarkation time is, for example, the time recorded for location data 50 No. 5, which is the last location data 50 shown in Figure 7. The disembarkation time may also be the time when the elevator car receiver 21 is no longer able to receive the radio waves from the mobile terminal 11, or the time when the elevator car receiver 31 installed at the destination floor's elevator car 30 receives the radio waves from the mobile terminal 11. However, as shown in Figure 6, the time when user 10 disembarks at a floor other than the destination floor may be recorded in the disembarkation time field. To account for temporary disembarkations at intermediate floors during peak hours, if the elevator car receiver 31 detects the radio waves from the mobile terminal 11 multiple times at different elevator cars within a certain period of time, the time when the elevator car receiver 31 last detected the radio waves at the elevator car is recorded as the disembarkation time.

[0077] The waiting time item stores the waiting time required from when user 10 arrives at the boarding area until they board the elevator car 20. The waiting time is calculated by the time calculation unit 120 as "boarding time - boarding arrival time". The boarding time field stores the boarding time of user 10 when they boarded the car 20. The boarding time is calculated by the time calculation unit 120 as "disembarking time - boarding time". The service completion time field stores the service completion time required to complete the elevator service for user 10. The service completion time is calculated by the time calculation unit 120 as "disembarking time - arrival time at the landing".

[0078] The END field stores information indicating whether the elevator service has been completed or not. If the elevator service has not been completed, "0" is stored in the END field; if the elevator service has been completed, "1" is stored in the END field. Therefore, even if a record records the time of disembarkation, if "0" is stored in the END field, it means that user 10 has temporarily disembarked, and the elevator service is continuing. Records with "0" in the END field are called "measurement logs," and records with "1" in the END field are called "confirmed logs."

[0079] When the landing receiver 31 detects the radio waves from the mobile terminal 11, a measurement log is created with "0" stored in the END field. However, if the in-car receiver 21 does not detect the radio waves from the mobile terminal 11 within a certain period of time, this measurement log is discarded.

[0080] The Warning field stores information that notifies the operator of the operation management system 100 of an anomaly if a problem occurs during the elevator service. If no anomaly occurs, "0" is stored in the Warning field; if an anomaly occurs, an alphanumeric code value corresponding to the nature of the anomaly is stored in the Warning field. For example, if the same individual ID is recorded multiple times in the measurement log within a certain period of time, a code value indicating that an anomaly has occurred in the landing receiving unit 31 is stored in the Warning field. Therefore, even if "1" is stored in the END field and the elevator service is completed, a code value indicating the occurrence of an anomaly may still be stored in the Warning field.

[0081] <Processing by the operation management system> Next, an example of the processing of the operation management system 100 will be explained with reference to Figures 9 to 12. Figure 9 is a flowchart showing an example of the overall processing of the operation management system 100.

[0082] First, the log determination unit 152 of the operation management system 100 performs a boarding detection process based on location information data 50 transmitted from the boarding reception unit 31 (S1). The boarding detection process is the process by which the log determination unit 152 detects users 10 at the boarding based on individual IDs recorded in the measurement log. For example, when the boarding reception unit 31 on each floor receives radio waves from the mobile terminal 11 of a user 10, it generates an individual ID by concealing the MAC address extracted from the radio waves. The boarding reception unit 31 then transmits the individual ID to the operation management system 100 via the network N, and the information reception unit 140 shown in Figure 1 receives the individual ID. Subsequently, the log recording unit 151 adds a record of the individual ID to the measurement log and starts recording the measurement log.

[0083] Next, the log determination unit 152 of the operation management system 100 performs in-car detection processing based on the location information data 50 transmitted from the in-car receiving unit 21 (S2). In-car detection processing is the process by which the log determination unit 152 detects a user 10 who has boarded the car 20 based on the individual ID recorded in the measurement log. When the in-car receiving unit 21 installed inside the car 20 receives radio waves from the user 10's mobile terminal 11, it generates an individual ID by concealing the MAC address extracted from the radio waves. The in-car receiving unit 21 transmits the individual ID to the operation management system 100 via the network N, and the information receiving unit 140 shown in Figure 1 receives the individual ID. After that, the log recording unit 151 confirms that it is the same as the individual ID added to the measurement log in step S1, and writes the boarding time, etc. to the record of the corresponding individual ID in the measurement log.

[0084] Next, the log determination unit 152 performs movement consistency determination processing based on the measurement log (S3). The movement consistency determination processing is a process in which the log determination unit 152 determines the consistency of the user 10's movement from when they boarded the elevator car 20 until they alighted, based on the individual IDs recorded in the measurement log. If the user 10 who boarded the elevator car 20 alights at an intermediate floor before reaching their destination floor, the unit determines whether the alighting was as intended by the user 10.

[0085] Finally, the landing notification unit 32 performs landing notification processing (S4). Landing notification processing is the process by which the landing notification unit 32 notifies users 10 on each floor landing of the time required to move to a floor that can be registered as a destination floor.

[0086] Figure 10 is a flowchart showing an example of the landing detection process. The landing detection process is a process that is repeatedly executed during the service provision time of the elevator 15.

[0087] First, the log determination unit 152 determines whether the landing reception unit 31 has detected the individual ID of user 10 at the landing 30 (S11). Here, as shown in Figure 8, the individual ID is information that uniquely identifies the mobile terminal 11 after the landing reception unit 31 receives radio waves from the mobile terminal 11, with the information being kept confidential. However, in the following explanation of the process, this will be referred to as "detection of the individual ID". If the landing reception unit 31 has not detected the individual ID of user 10 (NO in S11), then user 10 is not at the landing 30, and this process is terminated.

[0088] On the other hand, if the landing reception unit 31 has detected the individual ID of user 10 (YES in S11), the log determination unit 152 determines whether or not the individual ID of user 10 detected by the landing reception unit 31 is present in the log being measured during the measurement of individual IDs at the landing 30 by this process (S12).

[0089] If the individual ID of user 10 is not found in the measurement log (NO in S12), it means that user 10 has arrived at the boarding area 30 for the first time, so the log recording unit 151 records the individual ID of user 10 detected by the boarding area receiving unit 31 (hereinafter referred to as "the individual ID") in the measurement log (S13). Next, the log recording unit 151 records the time when the boarding area receiving unit 31 detected the individual ID (boarding area arrival time) in the boarding area arrival time item for the individual ID in the measurement log (S14), and terminates this process.

[0090] In step S12, if the individual ID of user 10 is found in the measurement log (YES in S12), the log determination unit 152 determines whether or not the arrival time at another boarding station 30 is recorded in the boarding station arrival time item in the measurement log for that individual ID (S15). If the arrival time at another boarding station 30 is not recorded in the boarding station arrival time item (NO in S15), it means that user 10 did not temporarily disembark at an intermediate floor, and the log determination unit 152 terminates this process.

[0091] On the other hand, if the arrival time at a different boarding platform 30 is recorded in the boarding platform arrival time field (YES in S15), it is possible that user 10 temporarily disembarked at an intermediate floor. For this reason, the log determination unit 152 determines whether or not the boarding time is recorded in the boarding time field within the measured log for the individual ID (S16).

[0092] If the time of boarding the elevator car is not recorded in the boarding time field (NO in S16), the log recording unit 151 discards the data for that individual ID in the measurement log (S17) and terminates this process. The fact that the time of boarding the elevator car is not recorded in the measurement log, even though the time of arrival at another boarding area 30 is recorded, suggests that the user 10 who came to boarding area 30 changed their mode of transport to the stairs or elsewhere and did not use the elevator 15.

[0093] On the other hand, if the boarding time is recorded in the boarding time field (YES in S16), the log recording unit 151 records the time when the boarding station receiving unit 31 detected the individual ID (disembarking time) in the disembarking time field within the measurement log for the individual ID (S18), and terminates this process.

[0094] Furthermore, if user 10 temporarily disembarks at an intermediate floor, their individual ID is detected at the intermediate floor's boarding area 30 (YES in S11), the detected individual ID is recorded in the measurement log (YES in S12), the arrival time at the boarding area of ​​the departure floor is recorded (YES in S15), and the time of boarding the elevator is recorded (YES in S16). Therefore, even in the case of temporary disembarkation, the disembarkation time is recorded in the measurement log.

[0095] Figure 11 is a flowchart showing an example of the in-car detection process. The in-car detection process starts when car 20 arrives at the departure floor of the call and the car door 22 opens.

[0096] First, the log determination unit 152 determines whether the in-car receiving unit 21 has detected the individual ID of user 10 inside the car 20 (S21). Here, as shown in Figure 8, the individual ID is information that uniquely identifies the mobile terminal 11 after the in-car receiving unit 21 receives radio waves from the mobile terminal 11, but in this explanation of the process, it is referred to as "detection of the individual ID". If the in-car receiving unit 21 has not detected the individual ID of user 10 (NO in S21), then user 10 is not in the car 20, and this process is terminated.

[0097] On the other hand, if the in-car receiving unit 21 detects the individual ID of user 10 (YES in S21), the log determination unit 152 determines whether the individual ID of user 10 detected by the in-car receiving unit 21 (hereinafter referred to as "the individual ID") is recorded in the boarding time item of the measurement log (S22). If the boarding time of the car for the individual ID is recorded in the measurement log (YES in S22), this process ends.

[0098] On the other hand, if the time of boarding for the individual ID is not recorded in the measurement log (NO in S22), the log recording unit 151 records the time the in-car receiving unit 21 detected the individual ID (time of boarding) in the boarding time item for the individual ID in the measurement log (S23), and terminates this process.

[0099] If user 10 temporarily disembarks from car 20, the individual ID is not detected inside car 20, so the determination in step S21 is NO. However, if user 10 who temporarily disembarked boards car 20 within a certain time, the individual ID is detected inside car 20, so the determination in step S21 is YES. In this case, the boarding time of the car for that individual ID has already been recorded in the measurement log, so a new boarding time is not recorded in the measurement log.

[0100] Figure 12 is a flowchart showing an example of the movement consistency determination process. The movement consistency determination process is a process that is repeatedly executed during the service provision time of the elevator 15. However, the movement consistency determination process may also be executed all at once after the service provision time of the elevator 15 (for example, late at night).

[0101] First, the log determination unit 152 performs the following processing for each individual ID recorded in the measurement log. That is, the log determination unit 152 determines whether or not the disembarkation time is recorded in the measurement log for the individual ID (S31). When user 10 disembarks from the car 20, the disembarkation time is recorded in the measurement log.

[0102] If the log determination unit 152 determines that the disembarkation time is recorded in the measurement log for the individual ID (YES in S31), it determines whether a threshold amount of time (for example, 30 seconds, which is the first hour) has elapsed since the disembarkation time recorded in the measurement log for the individual ID (S32). If a threshold amount of time has not elapsed since the disembarkation time (NO in S32), the log determination unit 152 determines that user 10 may have temporarily disembarked and terminates this process.

[0103] On the other hand, if a time exceeding a threshold has elapsed since the time of disembarkation (YES in S32), the log determination unit 152 considers that the user 10 who temporarily disembarked will not board the car 20 again, and therefore marks the measurement log for the individual ID as measurement complete (S33), and terminates this process. The process of marking the measurement log as measurement complete is performed by the log determination unit 152 setting "1" to the END item of the measurement log.

[0104] If, in step S31, it is determined that the disembarking time is not recorded in the measurement log for the individual ID (NO in S31), the log determination unit 152 determines whether or not the time of boarding the elevator car is recorded in the boarding time item of the measurement log for the individual ID (S34). If it is determined that the time of boarding the elevator car is not recorded in the boarding time item of the measurement log for the individual ID (NO in S34), the log determination unit 152 determines whether or not a threshold amount of time (an example of a second time, for example, 5 minutes) has elapsed since the arrival time at the boarding area in the measurement log for the individual ID (S35). If a threshold amount of time has not elapsed since the arrival time at the boarding area (NO in S35), the log determination unit 152 terminates this process. If a threshold amount of time has not elapsed since the arrival time at the boarding area, it is assumed that the user 10 is still waiting for the elevator car 20 to arrive at the departure floor where they called.

[0105] On the other hand, in step S35, if a time exceeding the threshold has elapsed since the arrival time at the boarding area (YES in S35), the log determination unit 152 discards the record of the individual ID from the measurement log (S37) and terminates this process. For example, if user 10 passes boarding area 30, the boarding time of user 10 is recorded in the measurement log, but since user 10 does not board the car 20, the boarding time is not recorded in the measurement log. As a result, a time exceeding the threshold has elapsed since the boarding time at the boarding area without the boarding time being recorded.

[0106] In step S34, if it is determined that the time of boarding the elevator car is recorded in the boarding time item of the measurement log (YES in S34), the log determination unit 152 determines whether a threshold amount of time (an example of a second time, for example, 5 minutes) has elapsed since the time of boarding the elevator car recorded in the measurement log for that individual ID (S36). If the elevator car 20 in which user 10 boarded is in motion and therefore a threshold amount of time has not elapsed since the time of boarding the elevator car (NO in S36), the log determination unit 152 terminates this process.

[0107] On the other hand, if a time exceeding a threshold has elapsed since the time of boarding the elevator car (YES in S36), the log determination unit 152 discards the record of the individual ID in question from the log being measured (S37) and terminates this process. A situation in which a time exceeding a threshold has elapsed since the time of boarding the elevator car is assumed to be, for example, when the landing receiving unit 31 installed at the landing 30 of the destination floor malfunctions and the disembarkation of user 10 at the destination floor cannot be detected.

[0108] Figure 13 shows examples of usage distribution 61 and transportation mode distribution 62 for each floor.

[0109] Traffic patterns within a building change constantly, and various traffic patterns exist depending on the building's purpose, such as office buildings, tenant buildings, and hotels. Therefore, the learning unit 110 creates a floor usage distribution 61 that shows the number of users getting on and off each floor, based on information such as the number of people getting on and off each hour, the departure floor, and the destination floor, which are obtained from the individual IDs recorded in the movement log 153.

[0110] The floor usage distribution 61 shows the number of people getting on and off the train on each floor, indicating the flow of people within the building. The numbers on the vertical axis represent each floor, the right side of the horizontal axis represents the number of people going down, and the left side of the horizontal axis represents the number of people going up. Therefore, the right side of the horizontal axis shows that the 2nd floor has the most people getting on and off, and the left side of the horizontal axis shows that the 1st floor has the most people getting on and off. Thus, the floor usage distribution 61 shows the usage status of users from their departure floor to their destination floor, and is accumulated every 5 minutes, by mode of transport, or over the entire day.

[0111] The learning unit 110 then determines the number of people from the departure floor to the destination floor based on the usage distribution 61 for each floor. For example, if (number of people on the departure floor) < (number of people on the destination floor), the learning unit 110 recognizes the users 10 waiting on the departure floor as users heading upwards, and if (number of people on the departure floor) > (number of people on the destination floor), it recognizes the users 10 waiting on the departure floor as users heading downwards.

[0112] The learning unit 110 then identifies whether the information shown in the usage distribution 61 for each floor corresponds to one of the existing traffic modes at predetermined intervals. To this end, the learning unit 110 learns which traffic mode the building's traffic flow corresponds to at predetermined intervals, according to the usage status of the elevators 15. The traffic modes are updated by the learning unit 110, for example, at the end of the day, by combining the traffic information data collected for each traffic mode with the results up to the previous day.

[0113] Furthermore, the learning unit 110 extracts new features from the learned traffic modes and generates a traffic mode Mn specific to the building based on these features. For example, the traffic mode distribution 62 shows the traffic modes M1 to M6 generated by the learning unit 110. The traffic modes M1 to M6 are divided into six regions M1 to M6 on a coordinate system where the horizontal axis represents the number of passengers boarding and alighting going downhill and the vertical axis represents the number of passengers boarding and alighting going uphill, indicating the traffic demand situation.

[0114] Typically, area M1, where the number of passengers getting on and off in both directions is low, represents a quiet mode, while area M2, where the number of passengers getting on and off in both directions is moderate, represents a normal mode. Areas M4 and M5, where the number of passengers getting on and off in both directions is high, represent a crowded mode (for example, when passengers are concentrated in a cafeteria on a middle floor of a building during lunchtime). Area M3, where the number of passengers getting on and off in the northbound direction is high, is called up-peak congestion (for example, during commuting hours), and area M6, where the number of passengers getting on and off in the southbound direction is high, is called down-peak congestion (for example, during commuting hours).

[0115] Subsequently, the learning unit 110 learns the trends in changes between traffic modes M1 to M6 and identifies which of the traffic modes M1 to M6 shown in the traffic mode distribution 62 belongs to the traffic mode shown in the usage distribution 61 for each floor, which indicates the flow of people within the building. If a new traffic mode Mn is generated by the learning unit 110, the learning unit 110 also identifies whether the traffic mode shown in the usage distribution 61 for each floor belongs to traffic mode Mn. The learning unit 110 then identifies the current traffic mode belonging to traffic modes M1 to M6 and Mn, such as commuting, lunch, leaving work, etc.

[0116] Figure 14 shows an example of a table 63 showing the number of users on each floor.

[0117] The target floor user count table 63 shows the number of users 10 who made an upward / downward service request for each floor during a predetermined time period and actually used the elevator 15. For example, the target floor user count table 63 shows an example of the number of users of the elevator 15, with the 1st to 9th floors being the basic service floors. The B1 floor houses large machinery and is not normally used except for maintenance and inspection. In this embodiment, history information is displayed every 10 minutes starting from 8:00, but the resolution of the table is not limited to every 10 minutes. Tables are formed according to the operator's request, such as every 5 minutes or every 8 hours.

[0118] For example, in Table 63 showing the number of users on the destination floor during the time period from 8:00 to 8:10, we can see that 4 out of 10 users boarded on the 1st floor and alighted on the 3rd floor, and 2 out of 10 users alighted on the 4th floor. On the other hand, 1 out of 1 user boarded on the 5th floor and alighted on the 1st floor. Thus, in the early morning (for example, during commuting hours), there are many service requests to move from the 1st floor to the 3rd floor or higher, and the traffic mode at this time is up-peak congestion, as shown in area M3 in Figure 13.

[0119] In the operation management system 100 according to the first embodiment described above, even when the elevator car 20 is full and users 10 temporarily disembark at intermediate floors, the system can correctly determine the departure floor and destination floor for each user 10 using the elevator 15. Therefore, the operation management system 100 can correctly measure the waiting time, ride time, and number of users of the elevator 15 for each user 10. Based on the measured information on the waiting time and ride time for each user 10, the operation management system 100 can then use the learned results to appropriately manage the operation of the elevator 15.

[0120] Furthermore, even if user 10 disembarks at an intermediate floor, if they board the elevator car 20 within the first hour, the log recording unit 151 records this as a temporary disembarkation in the measurement log. Subsequently, when user 10 disembarks at their destination floor, the log recording unit 151 updates the measurement log with the destination floor as the finalized log and records it in the movement log 153. On the other hand, if user 10 disembarks at an intermediate floor and does not board the elevator car 20 within the first hour, the log recording unit 151 records the intermediate floor as the destination floor and records user 10's measurement log as the finalized log in the movement log 153. In this way, regardless of whether user 10 temporarily disembarks or not, the user 10's movement path is recorded in the movement log 153, ensuring accurate measurement of pedestrian flow within the building.

[0121] Furthermore, by informing users 10 at the landing 30 of their measured waiting time and ride time, as well as alternative modes of transport other than the elevator 15, users 10 can choose a mode of transport that suits their purpose. For example, if the landing notification unit 32 informs users 10 that it takes 1 minute to travel from the 1st floor to the 2nd floor using the elevator 15, users 10 can shorten their travel time by choosing the stairs.

[0122] In the embodiment described above, information with anonymized MAC addresses was used to identify the mobile terminal 11. However, if user 10's attribute information (gender, age, wheelchair use, etc.) can be transmitted via radio waves, the user 10's attribute information may be added to the MAC address-anonymized information for management. This type of management makes it possible to manage the operation of the elevator 15 according to the user's attributes. For example, since wheelchairs take up space, if the time periods when wheelchair users 10 use the elevator 15 can be learned, the number of users who can board the car 20 during those times can be reduced to allocate the elevator 15 to user 10.

[0123] Furthermore, if a user 10 who does not have a mobile device 11 boards the car 20, there will be a difference between the number of people determined from the load value detected by the load sensor in the car 20 and the number of people inside the car detected by the in-car receiving unit 21. For this reason, the number of people determined from the load value may be used as the actual number of users 10 in the car 20, and a decision may be made regarding the temporary disembarkation and re-boarding of users 10 according to the change in the load value.

[0124] Furthermore, the operation management system 100 is not limited to a configuration that controls the operation of multiple elevators 15 as a group, but may also be configured to control the operation of only one elevator 15 installed in a building.

[0125] [Second Embodiment] The configuration described in the above-mentioned embodiment, in which an in-car receiving unit 21 is installed in the elevator car 20 and a landing receiving unit 31 is installed in the landing 30, is not mandatory. For example, a configuration in which a mobile terminal 11 carried by the user 10 acquires location information at the landing 30 is also possible. In this case, the mobile terminal 11 stores the time and order in which the location information was acquired in the RAM or elsewhere within the mobile terminal 11, and after a predetermined time, the mobile terminal 11 can transmit the location information to the operation management system 100. Now, an elevator system 200A according to a second embodiment of the present invention will be described with reference to Figure 15. Figure 15 is a block diagram showing an example of the overall configuration of the elevator system 200A according to the second embodiment.

[0126] Elevator system 200A has the same configuration as elevator system 200 shown in Figure 1, but is equipped with a portable terminal 11 carried by the user 10. In addition, the elevator car 20 does not have an in-car receiving unit 21, and the landing 30 does not have a landing receiving unit 31.

[0127] When user 10 arrives at landing 30, the mobile terminal 11 held by user 10 receives GPS signals transmitted from GPS (Global Positioning System) satellites or beacon signals transmitted from a beacon device installed at landing 30, thereby acquiring the location information of landing 30. The beacon signals transmitted from the beacon device installed at landing 30 include information about the landing floor of landing 30 as location information.

[0128] Furthermore, when user 10 boards elevator car 20 and then temporarily disembarks at an intermediate floor or at the destination floor, the mobile terminal 11 receives GPS signals or beacon signals to obtain location information of the platform 30. Alternatively, when user 10 boards elevator car 20, the mobile terminal 11 may obtain location information of elevator car 20 by receiving beacon signals transmitted from a beacon device installed on elevator car 20. In this case, the beacon signals transmitted from the beacon device installed on elevator car 20 include the elevator car number of elevator car 20 as location information.

[0129] In the elevator system 200A, each time the mobile terminal 11 acquires location information, it may sequentially record time information associated with the location information and location information indicating the landing 30, or it may sequentially record only the location information indicating the landing 30, excluding the time information. The mobile terminal 11 then transmits location information data 50, including the acquired multiple location information, to the operation management system 100 via the network N at regular intervals (for example, every 30 minutes). When the information receiving unit 140 of the operation management system 100 receives the location information data 50 from the mobile terminal 11, it transmits the multiple location information to the log processing unit 150. The log recording unit 151 then records the multiple location information as confirmed logs in the movement log 153. The subsequent processing of each function unit in the operation management system 100 is the same as in the operation management system 100 according to the first embodiment.

[0130] In this way, the operation management system 100 can manage multiple location information acquired by the mobile terminal 11, so the log determination unit 152 can determine the departure floor and destination floor for each user 10 who possesses the mobile terminal 11, that is, for each individual ID. Furthermore, since the elevator system 200A does not require the installation of an in-car receiving unit 21 in the elevator car 20 and a landing receiving unit 31 in the landing 30, the operation management system 100 can manage the location information of users 10 even with existing elevators.

[0131] <Example of a mobile device obtaining location information from the boarding area and elevator car> Here, we will describe an example in which the mobile terminal 11 according to the second embodiment acquires location information from the boarding area 30 and the elevator car 20. This section defines variations in the pattern in which the mobile terminal 11 acquires location information from the boarding area 30 and the elevator car 20. The following patterns (1) to (3) are assumed. (1) The mobile terminal 11 acquires location information from the boarding area 30 or elevator car 20 at predetermined time intervals. The predetermined time interval is assumed to be, for example, every 5 seconds, and the location information is acquired discontinuously. (2) When the mobile terminal 11 enters a predetermined range, it acquires location information once from the boarding area 30 or the elevator car 20. This predetermined range is the communication range of the beacon devices installed on the boarding area 30 and the elevator car 20, and is determined arbitrarily. (3) When the mobile terminal 11 enters the communication range of the beacon device, it continuously acquires location information from the boarding area 30 or the elevator car 20.

[0132] In the cases of patterns (1) and (3), the log determination unit 152 determines the departure floor of user 10 using the following method. For example, if the mobile terminal 11 continuously acquires the same location information from the beacon device at boarding area 30, the mobile terminal 11 transmits location information data 50, including the initially acquired location information, to the operation management system 100. The log determination unit 152 then determines the departure floor of the user 10 based on the location information of boarding area 30 added to the location information data 50 initially received by the information reception unit 140. Similarly, if the mobile terminal 11 continuously acquires the same location information from the beacon device at elevator car 20, the log determination unit 152 determines that the user 10 has boarded elevator car 20 based on the location information of elevator car 20 added to the location information data 50, including the initially acquired location information.

[0133] [Third Embodiment] In the operation management system according to the third embodiment of the present invention, we assume an example in which a user 10 moves from a lower floor to a higher floor using at least two elevators (shuttle-type elevator system) capable of moving from a lower floor to a middle floor and from a middle floor to a higher floor of a building.

[0134] Figure 16 shows an example configuration of two elevators (shuttle elevator system). Elevator 15(1) is used for travel from lower floors to middle floors, and users 10 can travel to any floor from the 1st to the 5th floor. Elevator 15(2) is used for travel from middle floors to upper floors, and users 10 can travel to any floor from the 5th to the 10th floor. In order for users 10 to travel from lower floors to upper floors, they must disembark at the landing 30 on the 5th floor of elevator 15(1), move to the landing 30 of elevator 15(2), and board the elevator car 20 of elevator 15(2).

[0135] Here, let's assume that user 10's departure floor is the 1st floor and their destination floor is the 10th floor. In the first embodiment described above, only one elevator 15 was considered, so if user 10 boarded the elevator car 20 from the 1st floor and alighted from the elevator car 20 on the 5th floor, there was a risk that the 5th floor would be determined as the destination floor. Therefore, in the shuttle elevator system, when the top floor (5th floor) of elevator 15(1) and the bottom floor (5th floor) of elevator 15(2) are transfer floors, the log determination unit 152 determines that user 10 has temporarily alighted when they alight at a transfer floor. Subsequently, if user 10 boards a different elevator than the one they temporarily alighted from, the log determination unit 152 re-determines user 10's destination floor. On the other hand, if user 10's destination floor was the 5th floor, user 10 will not immediately board another elevator after alighting on the 5th floor, so the log determination unit 152 determines that the 5th floor is the destination floor.

[0136] Here, we will explain the order in which the operation management system 100 acquires information when user 10 moves from the 1st floor to the 10th floor. Also, since the in-car receiving unit 21 and the landing receiving unit 31 transmit location information data 50 to the operation management system 10 each time they receive radio waves from the mobile terminal 11, the description of the process of transmitting location information data 50 will be omitted.

[0137] (1) When user 10 is at the landing 30 on the first floor of elevator 15(1), the operation management system 100 obtains the arrival time at the landing on the first floor, the individual ID, and the landing floor (first floor). (2) When user 10 boards the elevator car 20 in elevator 15(1), the operation management system 100 obtains the boarding time and individual ID. (3) When user 10 disembarks from elevator car 20 of elevator 15(1) on the 5th floor, the operation management system 100 obtains the arrival time at the 5th floor landing of elevator 15(1), the individual ID, and the landing floor (5th floor) of elevator 15(1).

[0138] (4) When user 10 moves to the elevator 15(2) landing 30 on the 5th floor, the operation management system 100 obtains the arrival time at the elevator 15(2) landing on the 5th floor, the individual ID, and the landing floor (5th floor) of the elevator 15(2). (5) When user 10 boards the elevator car 20 in elevator 15(2), the operation management system 100 obtains the boarding time and individual ID. (6) When user 10 disembarks from elevator car 20 of elevator 15(2) on the 10th floor, the operation management system 100 obtains the arrival time at the 10th floor landing of elevator 15(2), the individual ID, and the landing floor (10th floor) of elevator 15(2).

[0139] Furthermore, movement information representing the history of user 10's movement from the departure floor to the destination floor is recorded in the movement log 153 in one of the following two patterns. (Pattern 1) Movement information from the 1st floor to the 5th floor, and movement information from the 5th floor to the 10th floor (two pieces of movement information) (Pattern 2) Movement information from the 1st floor to the 10th floor (one piece of movement information)

[0140] The movement log 153 may be recorded in either of the patterns 1 or 2 described above. In the case of pattern 2, the movement information is recorded in the movement log 153 in one of the following ways.

[0141] The first method involves treating the elevator car 20 of elevator 15(1) and the elevator car 20 of elevator 15(2) as the same car and recording the movement information in the movement log 153. If the first method is adopted, elevators 15(1) and 15(2) can be considered as a single elevator. Therefore, the elevator car 20 of elevator 15(1) and the elevator car 20 of elevator 15(2) are assigned the same identification information (individual ID) for management. As a result, similar to the operation management system 100 according to the first embodiment, it is possible to record the boarding, temporary disembarking, and alighting of the elevator car 20 of the user 10 in the movement log 153 and manage the movement route of the user 10.

[0142] The second method involves combining the movement information of elevator 15(1) and the movement information of elevator 15(2) and recording the movement information in the movement log 153. If the second method is adopted, the operation management system 100 acquires the movement information of elevator 15(1) and elevator 15(2), then combines them and records them in the movement log 153. In this case, the elevator car numbers of the two elevator cars 20 that the user 10 rode in remain as movement information, so the learning unit 110 can identify the crowded elevator car numbers and learn the congestion times.

[0143] The operation management system 100 according to the third embodiment of the present invention can manage the destination floor to which a user 10 traveling after disembarking at a transfer floor and then boarding another elevator, using at least two elevators (shuttle-type elevator system).

[0144] Furthermore, even when user 10 moves from a high floor to a low floor, user 10 still moves to the landing 30 of another elevator at the transfer floor. In this case as well, the operation management system 100 according to the third embodiment does not treat user 10's disembarkation at the transfer floor as a temporary disembarkation, but can manage the floor on which user 10 disembarked as the destination floor.

[0145] It should be noted that the present invention is not limited to the embodiments described above, and various other applications and modifications can be taken as long as they do not depart from the gist of the present invention as described in the claims. For example, the embodiments described above are detailed and specific explanations of the system configuration in order to clearly illustrate the present invention, and are not necessarily limited to having all the configurations described. Furthermore, it is possible to add, delete, or replace some of the configurations in these embodiments with other configurations. Furthermore, the control lines and information lines shown are those deemed necessary for explanatory purposes, and not all control lines and information lines are necessarily shown in the actual product. In reality, it is safe to assume that almost all components are interconnected. [Explanation of symbols]

[0146] 10...User, 11...Mobile terminal, 15...Elevator, 20...Car, 21...In-car receiving unit, 25...Elevator control system, 30...Landing, 31...Landing receiving unit, 32...Landing notification unit, 100...Operation management system, 110...Learning unit, 111...Floor-specific passenger prediction unit, 120...Time calculation unit, 130...Elevator allocation unit, 140...Information reception unit, 150...Log processing unit, 151...Log recording unit, 152...Log judgment unit, 153...Movement log, 160...Guidance display command unit, 200...Elevator system

Claims

1. An operation management system for managing location information of users of multiple elevators installed in a building where a transfer floor is provided, An information receiving unit that receives identification information obtained from an electronic device carried by the user inside the elevator car of the aforementioned building, A log recording unit creates a travel log representing the user's travel route, which moves in the order of departure floor from which the user departed, inside the elevator car, and to the user's destination floor, based on the location information attached to the identification information received by the information receiving unit, namely the location information indicating the boarding area and the location information indicating the elevator car. The log recording unit records the boarding time when the user arrived at the boarding area, the boarding time when the user boarded the elevator car, and the disembarking time when the user disembarked from the elevator car in the travel log. A determination unit determines, from among the user's travel path obtained from a plurality of location information indicating the landing where the user was, or the elevator car the user boarded, the location information indicating the landing immediately preceding the location information indicating the elevator car of the first elevator is determined to be the location information of the departure floor, and when the location information indicating the landing immediately following the location information indicating the elevator car of the first elevator is obtained, it is determined that the user temporarily disembarked at the transfer floor, and when the user boarded a second elevator different from the first elevator from which they temporarily disembarked, and the location information immediately preceding is the location information indicating the elevator car of the second elevator, and the location information immediately following is not the location information indicating the elevator car of the second elevator, the determination unit determines that the location information indicating the landing is the location information of the destination floor. A learning unit that learns the usage status of the elevator based on the aforementioned movement log, generates a traffic mode specific to the building in which the elevator is installed, learns the trend of changes in the traffic mode, identifies the current traffic mode, and generates learning results that predict the number of users on each floor at each time interval. The system includes an assignment unit that, based on the learning results and the identified current traffic mode, selects an elevator unit that can be assigned to a call made at the landing, and dispatches the elevator car assigned to the call to the departure floor. Operation management system.

2. The determination unit determines the location information of the departure floor and the destination floor using time information which represents the time when the location information was acquired and is time information attached to the identification information received by the information receiving unit. The location information for the departure floor and destination floor is location information acquired by the boarding area and the elevator within a predetermined time. The operation management system according to claim 1.

3. The determination unit determines that the location information indicating the first boarding point in the user's travel path, based on the time information, is the location information for the departure floor, and determines that the location information indicating the last boarding point, based on the time information, is the location information for the destination floor. The operation management system according to claim 2.

4. If the information receiving unit does not receive location information indicating the elevator car within a predetermined time after receiving location information indicating the boarding area, the location information indicating the boarding area will be deleted. The operation management system according to claim 3.

5. The system includes a time calculation unit that calculates the waiting time by subtracting the boarding time from the boarding time, calculates the ride time by subtracting the boarding time from the disembarking time, and calculates the service completion time by subtracting the boarding time from the disembarking time. The operation management system according to any one of claims 1 to 4.

6. The system includes a control unit that issues a command to a landing notification unit installed at the landing, which notifies the user of the time required to use the elevator and alternative modes of transportation available to the user, based on the departure floor, destination floor, and service completion time recorded in the movement log. The operation management system according to claim 5.

7. An operation management method for managing location information of users of multiple elevators installed in a building where transfer floors are provided, The steps include receiving identification information obtained from an electronic device carried by the user at the landing of the building and inside the elevator car, Based on the location information attached to the received identification information, namely the location information indicating the boarding area and the location information indicating the elevator car, a movement log is created representing the user's movement route in the order of the departure floor from which the user departed, the inside of the elevator car, and the user's destination floor; the time of arrival at the boarding area when the user arrived at the boarding area, the time of boarding when the user got into the elevator car, and the time of disembarking when the user got out of the elevator car are recorded in the movement log; From the multiple location information indicating the landing where the user was, or the elevator car the user boarded, the location information indicating the landing immediately preceding the location information indicating the elevator car of the first elevator is determined to be the location information for the departure floor, and when the location information indicating the landing immediately following the location information indicating the elevator car of the first elevator is obtained, it is determined that the user temporarily disembarked at the transfer floor, and when the user boarded a second elevator different from the first elevator from which they temporarily disembarked, and the immediately preceding location information is the location information indicating the elevator car of the second elevator, and the immediately following location information is not the location information indicating the elevator car of the second elevator, the location information indicating the landing is determined to be the location information for the destination floor. The steps include: learning the usage status of the elevator based on the aforementioned movement log, generating a traffic mode specific to the building where the elevator is installed, learning the trend of changes in the traffic mode, identifying the current traffic mode, and generating a learning result that predicts the number of users on each floor at each time; The process includes the steps of selecting an elevator unit that can be assigned to a call made at the landing, based on the learning results and the identified current traffic mode, and dispatching the elevator car assigned to the call to the departure floor. Operation management method.

8. An elevator system having an operation management system that manages location information of users of multiple elevators installed in a building where a transfer floor is provided, An information receiving unit that receives identification information obtained from an electronic device carried by the user inside the elevator car of the aforementioned building, A log recording unit creates a travel log representing the user's travel route, which moves in the order of departure floor from which the user departed, inside the elevator car, and to the user's destination floor, based on the location information attached to the identification information received by the information receiving unit, namely the location information indicating the boarding area and the location information indicating the elevator car. The log recording unit records the boarding time when the user arrived at the boarding area, the boarding time when the user boarded the elevator car, and the disembarking time when the user disembarked from the elevator car in the travel log. A determination unit determines, from among the user's travel path obtained from a plurality of location information indicating the landing where the user was, or the elevator car the user boarded, the location information indicating the landing immediately preceding the location information indicating the elevator car of the first elevator is determined to be the location information of the departure floor, and when the location information indicating the landing immediately following the location information indicating the elevator car of the first elevator is obtained, it is determined that the user temporarily disembarked at the transfer floor, and when the user boarded a second elevator different from the first elevator from which they temporarily disembarked, and the location information immediately preceding is the location information indicating the elevator car of the second elevator, and the location information immediately following is not the location information indicating the elevator car of the second elevator, the determination unit determines that the location information indicating the landing is the location information of the destination floor. A learning unit that learns the usage status of the elevator based on the aforementioned movement log, generates a traffic mode specific to the building in which the elevator is installed, learns the trend of changes in the traffic mode, identifies the current traffic mode, and generates learning results that predict the number of users on each floor at each time interval. The system includes an assignment unit that, based on the learning results and the identified current traffic mode, selects an elevator unit that can be assigned to a call made at the landing, and dispatches the elevator car assigned to the call to the departure floor. Elevator system.

9. A landing receiving unit is installed at the landing and detects the user at the landing based on radio waves received from an electronic device carried by the user, The car includes an in-car receiving unit installed in the car, which detects the user riding in the car based on the radio waves received from the electronic device carried by the user riding in the car, The information receiving unit receives the location information transmitted from the landing receiving unit, and uses the location information received from the landing receiving unit as location information indicating the landing, and receives the location information transmitted from the car receiving unit, and uses the information received from the car receiving unit as location information indicating the car. The elevator system according to claim 8.

Images