CN113753694A

CN113753694A - System and method for displaying crowding condition of elevator

Info

Publication number: CN113753694A
Application number: CN202110609902.5A
Authority: CN
Inventors: 伊藤秀树; 小池幸裕; 三好雅则
Original assignee: Hitachi Building Systems Co Ltd
Current assignee: Hitachi Building Systems Co Ltd
Priority date: 2020-06-04
Filing date: 2021-06-01
Publication date: 2021-12-07
Also published as: JP2021187666A; JP7360995B2

Abstract

The invention provides a system and a method for displaying the congestion status of an elevator, which can easily grasp the congestion status such as the waiting time of a landing, which is difficult to grasp in the prior art. In particular, it is possible to grasp a true congestion state that is difficult to grasp only by an absolute congestion state. In order to solve the above problems, the present invention provides a screen area (401) for comparing and displaying the number of users of an elevator and a similar elevator in a company building and a screen area (402) for displaying the relative crowdedness of the elevator and the similar elevator in the company building (relative evaluation crowdedness of the elevator for each floor of a time zone), and can easily grasp the crowdedness by graphically presenting the relative crowdedness for a customer (1) or a technician (3) for each comparison unit such as a date, a time and a floor.

Description

System and method for displaying crowding condition of elevator

Technical Field

The present invention relates to a system and a method for displaying congestion status of an elevator, which are used to visualize congestion information of the elevator.

Background

When an office building or a commercial building is built, the number of users of the elevator is predicted at the time of building planning, and the elevator is installed with an optimum equipment specification for the number of installed elevators, speed, capacity, and the like, so that smooth operation can be performed. However, the number of people used varies depending on the use of the building, the floor, the type and number of tenants living in, and the like.

Therefore, the operation state of the elevator after installation may be different from the prediction at the time of building planning. Particularly, during commuting and noon break in the morning, the time is crowded. Therefore, after the installation of the elevator, a building management company or a maintenance company that performs elevator maintenance monitors the operation state, collects the operation information of the elevator, and performs data analysis. Then, the operation control of a plurality of elevators, the setting change of a starting reference floor, and the like are performed at an appropriate time, and adjustment is performed so that the landing waiting time of each floor is small, and the optimal operation can be performed.

As a prior art relating to these, patent document 1 describes the following: a visualization device and a visualization program for providing boarding/alighting operation history information for easily analyzing the movement tendency of an elevator passenger are applied to an inquiry service such as optimization of the arrangement of building tenants.

In the above patent document, the tendency of movement, the number of passengers in the car, and the like can be analyzed from the history of the floors on which the passengers are riding, but an index of congestion (congestion degree) such as waiting time at a landing is not known.

Patent document 1: japanese patent laid-open No. 2012 and 246115

Disclosure of Invention

The purpose of the present invention is to enable the congestion status of an elevator to be grasped more easily.

The present invention is to solve the above problems and to visualize the relative congestion status of an elevator in a variety of ways. Specifically, a congestion status display system for an elevator, which displays a congestion status of the elevator, comprises: an information search unit that specifies a first congestion status of an elevator specified by a user, and searches history data of congestion statuses of a plurality of similar elevators similar to the specified elevator; and a congestion status screen generation unit that calculates a second congestion status representing the congestion status of the plurality of similar elevators based on the history data, compares the first congestion status with the second congestion status for each predetermined comparison unit, specifies a relative congestion level of the elevator specified by the user using a result of the comparison, and causes a display device to display information indicating the first congestion status and the second congestion status in a display manner corresponding to the relative congestion level for each comparison unit. The present invention also includes a congestion status display method for an elevator, and a computer program for executing the congestion status display method.

By implementing the present invention, the relative congestion status of the elevator can be compared, and the congestion status can be grasped for each comparison unit such as a floor and a time slot.

Drawings

FIG. 1 is a functional block diagram of an embodiment of the present invention.

Fig. 2 is a functional block diagram showing a configuration example of a group management elevator and a traffic monitoring apparatus according to an embodiment of the present invention.

Fig. 3 is an example of a screen for selecting a building in which elevators whose congestion status is to be confirmed are installed according to an embodiment of the present invention.

Fig. 4 is an example of a screen for selecting an elevator to confirm a congestion situation according to an embodiment of the present invention.

Fig. 5 is a screen example showing the congestion degree (absolute evaluation) of an elevator according to an embodiment of the present invention.

Fig. 6 is a screen example showing the congestion degree (relative evaluation) of an elevator according to an embodiment of the present invention.

Fig. 7 shows elevator information according to an embodiment of the present invention.

FIG. 8 illustrates an average latency evaluation criterion used in an embodiment of the present invention.

Fig. 9 is a graph illustrating a method of calculating a relative congestion degree value according to an embodiment of the present invention.

FIG. 10 illustrates average latency versus evaluation criteria used in an embodiment of the present invention.

Fig. 11 is a screen example showing details of the relative congestion degree of an elevator according to an embodiment of the present invention.

Fig. 12 is an example of a screen of the improved prediction of the congestion status of the elevator according to the embodiment of the present invention.

Fig. 13 is an operation flow showing a procedure of dealing with a complaint from a user about a congestion of an elevator according to an embodiment of the present invention.

Fig. 14 is a hardware configuration diagram of a data center server according to an embodiment of the present invention.

Fig. 15 shows elevator operation information used in an embodiment of the present invention.

Fig. 16 shows traffic monitoring information used in an embodiment of the invention.

Fig. 17 shows congestion status information used in an embodiment of the present invention.

Fig. 18 is a flowchart showing a processing procedure for displaying a congestion status (relative evaluation) of an elevator according to an embodiment of the present invention.

Detailed Description

In order to explain the present invention in more detail, the description is made based on the illustrated examples. In this embodiment, the description will be given of the understanding of the congestion state of an elevator as an example of an elevator.

Fig. 1 is a functional block diagram showing the configuration of the data center server 5 and the system related thereto according to the present embodiment. 1 is the owner who owns the building or the customer who manages the building. Reference numeral 2 denotes a customer terminal for confirming the congestion status of the elevator of the building managed by the customer 1. 3 is a technician 3 of the elevator maintenance company. Reference numeral 4 denotes a technician terminal 4 which allows the technician 3 to confirm the congestion state of the elevator or perform a simulation of the operation of the group management elevator.

Reference numeral 5 denotes a data center server provided in a so-called data center. Of these, 6 is a server processing unit. The server processing unit 6 includes a congestion status screen generating unit 7 and an information retrieving unit 8 for generating screen data to be displayed on the client terminal 2 and the technician terminal 4. The server processing unit 6 also has an elevator operation simulation unit 9 for performing an operation simulation of the group management elevator from the technician terminal 4 used by the technician 3 of the elevator maintenance company.

Further, reference numeral 13 denotes an elevator operation data collecting device which collects elevator operation data 25 and traffic monitoring data 28 from the group management elevators 20 of the customer building via the communication device 12. The elevator operation data collection device 13 here collects these pieces of information periodically, preferably via a high-speed communication network. Further, reference numeral 14 denotes an elevator operation information storage unit for storing elevator operation information 15 and traffic monitoring information 16 obtained by converting (uniform in form or the like) the elevator operation data 25 and traffic monitoring data 28 collected by the elevator operation data collection device 13. This conversion will be described later.

Here, the elevator operation information 15 and the traffic monitoring information 16 will be described with reference to fig. 15 and 16. First, fig. 15 shows elevator running information 15. The elevator operation information 15 is data in which the arrival time and departure time of the car to each floor are recorded for each elevator. As an example thereof, a building ID151, a bank ID152, a building name 153, a bank name 154, a single machine 155, a floor 156, an arrival time 157, and a departure time 158 are recorded.

Next, fig. 16 shows the traffic monitoring information 16. The data is obtained by recording the arrival time of the elevator at a lobby in front of the elevator and the boarding time of the elevator for each person monitored. As an example, a building ID161, a bank ID162, a building name 163, a bank name 164, a single machine 165, a floor 166, a person 167, a hall arrival time 168, and a boarding time 169 are recorded in association with each other. The person 167 may be data having anonymity as long as it is a unit for measuring the number of users. In addition, even the same person may be given different identification information for each time slot.

Further, reference numeral 17 denotes a building elevator information storage unit which stores the building master information 10 and the elevator information 11.

Here, a hardware configuration for implementing the data center server 5 as a computer will be described with reference to fig. 14. The data center server 5 is configured by a processing unit 51, a memory unit 52, a storage device 54, and a communication device 12.

The processing unit 51 has a function of performing calculation according to a program, such as a CPU. In the present embodiment, the processing unit 51 executes processing in accordance with the congestion status screen generation program 507, the information search program 508, the elevator operation simulation program 509, and the elevator operation data collection program 513 which are developed in the memory unit 52. Here, the correspondence relationship between each program shown in fig. 14 and each configuration of fig. 1 is as follows. That is, the functions of the respective configurations of fig. 1 can be realized by operations performed according to the respective programs.

Congestion status screen generation program 507: congestion status screen generation unit 7

The information retrieval program 508: information search unit 8

Elevator operation simulation program 509: elevator operation simulation part 9

Elevator operation data collection program 513: elevator operation data collecting device 13

In addition, the storage device 54 stores the above-described various information. The communication device 12 is connected to the customer terminal 2, the technician terminal 4, and the group management elevator 20 via the high-speed communication network.

This concludes the description of the data center server 5. Next, the group management elevator 20 and the traffic monitoring device 26 connected thereto will be described with reference to fig. 2.

Fig. 2 shows a functional block diagram of the group management elevator 20 and the traffic monitoring device 26. The group management elevator 20 is installed in a customer building, includes a plurality of elevators 23a to 23n, and has a structure for controlling the elevators. This configuration includes a communication device 21 connected to a high-speed communication network, and a group management control device 22 for controlling the operation of a plurality of elevators 23a to 23n and acquiring operation data of the plurality of elevators. The group management elevator 20 also has an operation data storage unit 24 for storing elevator operation data 25. The operation data storage unit 24 can be realized by a storage medium such as an HDD (hard disk drive) or a memory card.

In addition, a traffic monitoring device 26 connected to the group management elevator 20 is installed in the customer building. The traffic monitoring device 26 has various devices for measuring traffic, that is, the number of users such as the number of waiting persons of the elevator. The system includes a landing camera 29 having a function of measuring the number of people such as the number of waiting people in a landing and the number of passengers in a car, and a traffic monitoring device 30 for measuring the number of passing people such as a security gate of a customer building. The traffic monitoring device 26 also has a traffic monitoring data storage unit 27 that stores traffic monitoring data 28 collected from the device.

The data centre servers 5 are here connected to the group management elevators 20 via a high-speed communication network. The elevator operation data collection device 13 is periodically connected to the communication device 21 via the communication device 12, and collects elevator operation data 25 and traffic monitoring data 28. That is, the elevator operation data collection device 13 collects the elevator operation data 25 and the traffic monitoring data 28 from the operation data storage unit 24 and the traffic monitoring data storage device 27. Then, the elevator operation data collection device 13 converts them into elevator operation information 15 and traffic monitoring information 16, and stores them in the elevator operation information storage unit 14. The elevator operation data 25 and the traffic monitoring data 28 are the same in content as the elevator operation information 15 and the traffic monitoring information 16. Therefore, as the conversion, there is a case where the elevator operation data collection device 13 converts the elevator operation data 25 and the traffic monitoring data 28, which are non-fixed data, into the elevator operation information 15 and the traffic monitoring information 16, which are fixed information.

Next, a conventional procedure for dealing with a complaint of a user in response to a congestion of an elevator will be described. The group management elevator 20 is controlled so as to perform an optimum operation in response to the car calls and landing calls of the plurality of

elevators

23a, 23b, … … 23 n. However, in the case of an office building or the like, for example, a waiting queue of users may be generated at a landing of an elevator during a period of business or lunch, or even if the car arrives due to a call from the landing, the car cannot be taken by a full person. In such a case, complaints and improvement needs of elevator users may occur.

In such a case, in the conventional procedure for dealing with the elevator, first, a management company or a building owner investigates the cause of congestion or complaint of the elevator. Based on the result of the survey, the management company or the building owner requests the elevator maintenance company to perform a survey concerning the operation of the elevator.

Then, the elevator maintenance company collects operation data for a certain period of time, and collectively examines the congestion status of the landings and the cars on the site. Then, based on the result, the setting related to the operation control of the elevator is changed to the optimum setting to deal with the change. Further, the field survey of the congestion situation must be continued thereafter, and it may take several months until the countermeasure is completed.

Therefore, in the present embodiment, in order to prevent such a delay, the operation statuses of a plurality of group management elevators are collected by the elevator operation data collection device 13, and the congestion status can be confirmed using the operation statuses. The steps of this embodiment will be described below with reference to the operation flow shown in fig. 13. Hereinafter, the main processing units of the processing performed on the system side will be described mainly by the constituent elements shown in the functional blocks of fig. 1 and 2.

First, in step S1, the customer 1 or the technician 3 accesses the data center server 5 via the customer terminal 2 or the technician terminal 4, and confirms the congestion status of the elevator in which the complaint is made. Specifically, the customer terminal 2 or the technician terminal 4 receives input of a building in which a complaint elevator is installed, a single elevator, a target floor, and date and time from the customer 1 or the technician 3. In the present embodiment, any of the group management elevators or the elevators constituting the group management elevator can be used. Therefore, unless otherwise specified, they will be referred to as "elevators" hereinafter.

Here, a display screen of the client terminal 2 or the technician terminal 4 when the input is made will be described. Fig. 3 is a screen for customer 1 or technician 3 to select a building in which an elevator to be selected is installed when confirming the congestion status of the elevator.

When there are a plurality of buildings managed and in charge by the customer 1 or the technician 3, data serving as search keys are set in the building contractor name 101, the building name 102, and the address input field from the screen, and the search button 104 is selected. Thereby, the customer terminal 2 or the technician terminal 4 transmits a search request with these as keys to the data center server 5. Upon receiving the request, the information search unit of the data center server 5 executes a search corresponding to the search request on the building master information 10 in the building elevator information storage unit 17. Although not shown, the building master information 10 stores the building name and address displayed in the "managed building selection" in fig. 3 in association with a building ID for identifying a building. In addition, a group name and a single machine are stored for each building.

As a result, the congestion status screen generation unit 7 that received the search result from the information search unit 8 causes the customer terminal 2 or the technician terminal 4 to display the search result, i.e., the managed building name list 105 of fig. 3. In addition, the subscriber name is determined based on the registration ID at the time of system registration, and when there are a plurality of subscriber names based on the subscription system or the like, one subscriber of the managed building to be the subject of this time can be selected.

Then, the customer terminal 2 or the technician terminal 4 receives a selection of a corresponding building from the managed building name list 105 selected by the customer 1 or the technician 3 using the radio button 106. Then, the customer terminal 2 or the technician terminal 4 receives the pressing operation of the building selection button 107 by the customer 1 or the technician 3, and the screen transitions to the screen of fig. 4.

Fig. 4 is a screen for selecting a group management elevator to be checked for congestion from the elevators installed in the building selected on the screen of fig. 3. When there are a plurality of group management elevators in a building to be managed, the group management elevator can be specified by confirming the group name and the individual from the group list 201 as the management unit of the group management elevator and selecting the corresponding group from the selection field 202. In the case of individual elevators, the identification can be made by using a single machine. Therefore, the customer terminal 2 or the technician terminal 4 transmits a search request with the previously determined building as a key to the data center server 5. Upon receiving the request, the information search unit of the data center server 5 executes a search corresponding to the search request on the building master information 10. This concludes the description of step S1.

Next, in step S2, the customer terminal 2 or the technician terminal 4 displays the congestion information of the elevator determined in step S1. Therefore, the customer terminal 2 or the technician terminal 4 transmits a search request with the selected target individual as a key to the data center server 5. Upon receiving the request, the information search unit 8 of the data center server 5 searches the elevator operation information storage unit 14. In this embodiment, the elevator operation information 15 and the traffic monitoring information 16 shown in fig. 15 and 16 are searched.

Then, the congestion status screen generating unit 7 generates congestion status information 18 indicating the congestion status based on the retrieved elevator operation information 15 and the traffic monitoring information 16. The congestion status information 18 stores the congestion status of each elevator for each comparison unit for grasping the congestion status. Fig. 17 shows an example of the congestion status information 18. The congestion status information 18 includes a building ID181, a bank ID182, a building name 183, a bank name 184, a stand-alone 185, a floor 186, a date and time 187, an average waiting time 188, and the number of people used 189. In the example of fig. 17, the floor 186 and the date and time 187 are used as the comparison units, but any one or other comparison units may be used. The date and time is 1 hour, but may be other units. The average waiting time 188 and the number of users are used as the congestion status, but any one or other indicators may be used.

Then, the congestion status screen generating unit 7 generates a screen indicating the degree of congestion, which is obtained from the congestion status of the elevator based on the absolute evaluation, as shown in fig. 5, based on the congestion status information 18. Then, the screen of the customer terminal 2 or the technician terminal 4 is shifted to the screen shown in fig. 5 by the congestion status screen generating unit 7.

Here, details of the screen shown in fig. 5 will be described. Fig. 5 shows a graph of the number of people used per time slot, the floor of the hall, and the degree of congestion per time slot, for which the date and time is specified in step S1. The number of users indicates the number of people who get on the elevator car every 1 hour, and the number of users 189 who use the congestion status information 18. And calculating and displaying. The average waiting time 188 of the number of persons using the congestion status information 18 is used by the elevator according to the floor congestion degree of the time zone. Here, the following information can be used as the average waiting time 188, that is, the degree of congestion of the elevator per-slot floor. The system has information indicating the average waiting time of the user from queuing at the landing to boarding the elevator car in units of seconds, a long-time waiting rate for calculating the frequency (%) of the occurrence of the waiting time of the user exceeding 60 seconds, the number of the persons waiting at the landing per unit time, and the like. These congestion indexes are often used to visualize the congestion status of the elevator hall. However, in order to visualize the congestion status of the elevator, elevator operation state data such as the congestion level in the elevator car and the number of times of activation indicating the frequency of use of the elevator may be used.

In order to display the screen of fig. 5, the congestion status screen generation unit 7 may perform the following processing. First, the congestion status screen generation unit 7 displays the building name of the building selected as shown in fig. 3 in the building name display field 301 of the customer terminal 2 or the technician terminal 4. Then, the congestion status screen generation unit 7 initially displays the group name of the group management elevator selected in fig. 4 in the group name display field 302 of the customer terminal 2 or the technician terminal 4.

Next, the congestion status screen generation unit 7 receives specification of the corresponding year, month and day via the target year, month and day specification field 303 of the client terminal 2 or the technician terminal 4. The customer terminal 2 or the technician terminal 4 may display a sub-screen for displaying a calendar, from which selection can be made. When the time slot is limited and displayed, the congestion status screen generation unit 7 sets a start time and an end time in the time slot specification field 304. This may be set as a pull-down of the selection time (hour, minute).

Next, the congestion status screen generating unit 7 receives selection of a congestion degree item to be displayed, such as an average waiting time or a long waiting time, via the congestion degree display item pull-down 305 of the customer terminal 2 or the technician terminal 4. The congestion status screen generation unit 7 receives selection of a time unit (hour, 30 minutes, 5 minutes, 1 minute, or the like) used for displaying the congestion degree via the display unit pull-down 306 of the customer terminal 2 or the technician terminal 4. When the selection of the search button 307 is received via the customer terminal 2 or the technician terminal 4, the congestion status screen generating unit 7 displays the number of elevator users 310 at the specified date and time and the hall congestion degree 311 for each floor and time slot as shown in fig. 5. The congestion status screen generation unit 7 may generate the congestion status information 18 in advance and display the stored information, or may generate the congestion status information 18 for each request.

It is preferable that the number of elevator users 310 and the hall congestion degree 311 for each floor for each time slot are displayed by changing the display mode based on the values indicated by the numbers. For example, the display may be made in a color suitable for each range of the reference value, or a symbol (letter) indicating the degree of congestion may be described. The number of elevator users 310 and the hall congestion degree 311 for each floor and each time zone may be displayed in any manner. In the case of color separation, it is preferable that the higher the degree of crowding, the higher the density or the more conspicuous the color.

Fig. 8 shows an average waiting time evaluation criterion 601 for changing the display mode in accordance with the congestion degree. The congestion status screen generation unit 7 determines which of the average waiting time evaluation criteria 601 stored in the server processing unit 6 the congestion degree (average waiting time) of each comparison unit (time zone, floor) corresponds to, and displays the congestion degree (average waiting time) in a display form such as a color corresponding to the corresponding column of 311.

Next, in step S3, the congestion information based on the relative evaluation of the specific individual elevator is displayed on the customer terminal 2 or the technician terminal 4. While the congestion degree based on the absolute evaluation is shown in fig. 5, the display based on the relative evaluation can be performed in the present embodiment.

To do so, the customer terminal 2 or technician terminal 4 accepts the selection of the relative evaluation tab 309 shown in FIG. 5 from the customer 1 or technician 3. As a result, the display screen shown in fig. 6 is displayed on the customer terminal 2 or the technician terminal 4. The content of the congestion state indicates a congestion state based on a relative evaluation in which the congestion degree is compared with elevators in similar buildings. In an office building or the like, since a congestion state continues at work or at noon break, it is determined that the congestion degree is always congested in the absolute evaluation in fig. 5. Therefore, in this embodiment, in such a case, the congestion status of the elevator of the building can be evaluated based on the relative congestion degree with respect to other buildings.

First, before describing the contents of the screen in fig. 6, a procedure of processing for displaying the screen will be described with reference to fig. 18. Fig. 18 is a flowchart showing a processing procedure for displaying the congestion status (relative evaluation) of the elevator shown in fig. 6. In this flowchart, information indicating the congestion status of elevators in similar buildings (similar elevators) serving as a relative evaluation criterion is searched for, and the screen shown in fig. 6 is generated using this information.

First, in step S31, the customer terminal 2 or the technician terminal 4 transmits a relative evaluation request to the data center server 5 in accordance with the input of the customer 1 or the technician 3. This may be the designation of the relative evaluation tab 309 of fig. 5, or the access performed in step S1 may be used as a trigger.

Next, in step S32, the information retrieval unit 8 of the data center server 5 retrieves elevator information related to the target elevator from the elevator information 11 using the building or the elevator individual received in step S1. As a result, the elevator information 11-1 of the target elevator shown in fig. 7 (a) is retrieved. The elevator information 11-1 is composed of a building ID111-1, a bank ID112-1, a building name 113-1, a bank name 114-1, a building application 115-1, a floor number 116-1, a delivery number 117-1, a rated speed 118-1, a transportation amount 119-1, and the like. Here, the number of delivered elevators 117-1 may be the number of elevators constituting the group management elevator 20 in a predetermined group. The information retrieval unit 8 may specify the information from the building master information 10.

Next, in step S33, the information retrieval unit 8 retrieves a similar elevator from the elevator information 11, using a predetermined item indicating the feature of the elevator in the retrieved elevator information 11-1 as a key. In this embodiment, the key is the building use 115-1, the number of floors 116-1, the number of delivery stations 117-1, the rated speed 118-1, and the transportation amount 119-1. Then, the information retrieval unit 8 retrieves elevator information whose values match or fall within a certain range.

Fig. 7 (b) shows an example of the elevator information 11-2 to be searched. The elevator information 11-2 is information corresponding to the elevator information 11-1. Therefore, the building ID111-2, the bank ID112-2, the building name 113-2, the bank name 114-2, the building application 115-2, the floor number 116-2, the number of delivered stations 117-2, the rated speed 118-2, the transportation amount 119-2, and the like. The number of delivered elevators 117-2 may be any number of predetermined groups such as the number of elevators constituting the group management elevator 20.

The search will be described by taking as an example a case where the building application 115-1 of the target elevator information 11-1 is "office building", the floor number 116-1 is "18", the delivery number 117-1 is "6", the rated speed 118-1 is "60", and the transportation amount 119-1 is "120". As data in which all of the 5 item values in the elevator information 11-2 of fig. 7 (b) match, the following 2 records are searched. The elevators used in the elevator group indicated by these data are determined to be similar elevators.

Building ID111-2 is "10003", and ladder ID112-2 is "10003-"

Building ID111-2 is "10003", and ladder ID111-2 is "10003-002"

In this example, data matching each item is searched, but data satisfying a predetermined condition, such as within a certain range, may be searched. For example, the number of floors may be previously grouped for each predetermined range, and may be determined by whether or not the number of floors matches the group. The determination may be made by whether or not the difference is within a predetermined fixed range. The data extraction processing for elevators of similar buildings includes extraction other than the extraction performed when the data is narrowed down by other customer buildings or areas, or when all of 5 items match (AND condition). The condition and the range can be determined for each item to extract, for example, by matching (OR condition) with at least 1 arbitrary item among 5 items. Further, as for the elevator information 11-1, a building ID, a bank ID, or information for identifying a similar elevator may be stored, and the data may be used to omit the time for retrieval.

In step S34, the information retrieval unit 8 retrieves elevator travel information 15 and traffic monitoring information 16 similar to elevators. That is, the data corresponding to the building ID111-2 of "10003", the bank ID112-2 of "10003-" 001 ", and" 10003- "002" are extracted.

Next, in step S35, the congestion status screen generating unit 7 generates congestion status information indicating a congestion status similar to that of an elevator. This is generated in the same manner as the congestion status information 18 of the target elevator described in step S2. That is, information is generated in which the congestion status of the similar elevator is associated with each similar elevator and each comparison unit for grasping the congestion status.

Then, the congestion status screen generating unit 7 calculates a representative value representing the entire similar elevators for each comparison unit using the congestion statuses (average waiting time and the number of people used) of the similar elevators. The representative value includes an average value. Here, information similar to the past fixed period of the elevator is used in calculating these representative values. As the information of the past fixed period, it is preferable to use information corresponding to the date and time when the complaint or the inquiry is present. For example, if the date and time of a complaint or inquiry is weekday, the information of weekday is also used as the information of a certain period in the past.

Next, in step S36, the congestion status screen generation unit 7 compares the generated representative value (congestion status information) of similar elevators with the congestion status information of the subject elevator for each comparison unit. In this example, the time zone and the floor are used as the comparison unit.

Then, the congestion status screen generating unit 7 determines a relative congestion degree indicating the relative congestion status based on the comparison result. The relative congestion degree indicates the difference value as a result of the comparison and which is large. For example, as shown in fig. 9, when the average value of the average waiting time (seconds) of the corresponding time zone of the similar building is 702 and the value of the average waiting time of the corresponding elevator managed by the customer 1 is 701, the difference value obtained by subtracting 702 from 701 is determined as the relative congestion value 703.

Then, the congestion status screen generating unit 7 determines a display mode based on the relative congestion value 703, and causes the customer terminal 2 or the technician terminal 4 to display the content shown in fig. 6 according to the determined display mode. Here, the congestion status screen generation unit 7 uses, for example, an average waiting time relative evaluation criterion shown in fig. 10 to determine the display mode. The specific contents of the display mode thus determined will be described. In fig. 6, the average waiting time of 12 to 13 points of 1 floor shown by 403 has a value of 45 seconds, and the average value of the average waiting time of similar elevators has a value of 40 seconds. In this case, the difference is-5 seconds, so the "slightly better than average" of fig. 10 is determined. Therefore, the congestion status screen generation unit 7 displays "B +" in this column.

The relative congestion degree 703 is calculated by a difference from the average, but may be calculated by a method using a standard deviation. In this way, by comparing and displaying the relative congestion degrees of the large building group and other large building groups in the order of floors and time slots, the congestion status of the comparative units in the order of floors and time slots can be grasped at a glance.

This concludes the description of fig. 18. Next, details of the display contents of fig. 6 will be described before returning to the operation flow of fig. 13. Fig. 6 is a screen showing the degree of congestion (relative evaluation) of an elevator. Here, 401 is a screen area in which the number of persons using an elevator in a target building (a building of the company) and the average number of persons using similar elevators are compared and displayed in a time slot.

Further, 402 is a screen area which displays the relative degree of congestion generated in step S36. That is, the display area displays the relative evaluation congestion degree of the elevator per each floor of the slot. In this example, as shown in the average waiting time relative to the evaluation criterion, the display color is set to be background-free (difference is minus) or background-free (difference is plus) depending on the sign (difference is plus or minus) of the relative congestion degree, and the degree thereof is represented by a + to C. The display colors may be classified into a red system (difference-plus) and a blue system (difference-plus), and the degree of congestion may be indicated by changing the colors in stages.

Further, 404 is a check box which can select a floor for which a congestion state is to be checked. The customer terminal 2 or the technician terminal 4 receives the selection of the check box and the selection of the detailed congestion degree button 405 by floor from the customer 1 or the technician 3. In response to this selection, the congestion status screen generation unit 7 causes the customer terminal 2 or the technician terminal 4 to display the screen of fig. 11.

Fig. 11 is a screen showing details of the relative congestion degree of an elevator for each time slot using the average waiting time. With this screen 901, the customer terminal 2 or the technician terminal 4 can confirm the details of the relative congestion level exemplified in the average waiting time. For example, when confirming the details of 8 o' clock at level 1 in fig. 6, the customer 1 or the technician 3 selects only level 1 in the floor selection column 404 via the customer terminal 2 or the technician terminal 4, and presses the detailed congestion degree button 405 of the floor. Upon receiving this selection, the congestion status screen generation unit 7 generates a 8 o' clock relative congestion degree table 902 from the screen of fig. 11, and displays the table on the customer terminal 2 or the technician terminal 4.

In addition, when the customer terminal 2 or the technician terminal 4 is a so-called personal computer, the value of the relative congestion degree can be confirmed by clicking the corresponding graph on the screen, and touching the corresponding graph with a finger from the screen in the case of a tablet personal computer (903). The description of the processing up to step S3 of the operation flow ends.

Through the above steps, the customer 1 or the technician 3 can confirm the congestion status of the elevator of the building to be managed. Then, although the handling of the congestion is performed thereafter, the customer 1, i.e., the manager or owner of the building determines whether or not the customer can handle the congestion. If it is determined that the situation cannot be handled (no), the routine proceeds to step S5, where the elevator maintenance company is requested to investigate the cause of the elevator congestion. The delegation may be by telephone, mail, letter, etc. When it is determined that the response is possible (yes), the customer himself/herself performs some response, and the operation flow is ended.

Next, in the elevator maintenance company that received the request, the technician 3 of the elevator performs a congestion check of the site of the elevator. Therefore, in step S6, the elevator operation simulation unit 9 of the data center server 5 executes the operation simulation in accordance with the input instruction from the technician 3 via the technician terminal 4. Therefore, first, the elevator operation simulation unit 9 analyzes the operation state of the elevator based on the elevator operation information 15 and the traffic monitoring information 16 that are periodically collected, and examines the cause.

After that, the elevator operation simulation unit 9 executes the operation simulation in accordance with the congestion relief measure input from the technician terminal 4 by the technician 3 based on the investigation result. Then, the elevator operation simulation unit 9 causes the technician terminal 4 to display the result of the operation simulation. The technician 3 understands the contents and verifies the effect of the input congestion relief countermeasure. In this case, it is preferable to input a plurality of congestion relief measures and perform the operation simulation separately.

As the operation simulator, an elevator simulator or the like proposed in japanese patent laid-open No. 2018-167966 can be used. In this case, as a result of the operation simulation, the elevator operation simulation unit 9 preferably displays the congestion status of the elevator shown in fig. 5 and 6 or displays a screen of fig. 12 described later. In this case, with respect to fig. 6, the congestion status calculated in step S3 is used as the congestion status of the similar elevator.

Next, the technician 3 presents to the customer 1 a plan which can expect an effect from the result of the operation simulation, among the plurality of congestion relief measures in step S6. The customer 1 confirms the improved prediction of the elevator congestion state by using the customer terminal 2. An example of a screen showing the improved prediction of the congestion status of the elevator when the congestion relief measures are taken is displayed on the client terminal 2. For example, a case will be described where a plurality of proposals such as improvement in operation by the user (operation for shifting the peak value by changing the noon break time) are proposed as a congestion relief measure in proposal 1.

In this case, the option is selected by the improvement option display switching pull-down 1001 in fig. 12. This switches the display screen of the customer terminal 2, and the customer 1 can check the contents. Specifically, the technician terminal 4 displays the current congestion degree 1004 and the improved congestion degree 1005 on the prediction 1002 of the number of elevator users (the current number of users, the prediction of the number of users after improvement) and the prediction 1003 of the congestion degree of the elevator for each time slot calculated based on the simulation result. Thereby, the technician 3 can compare them. The display may be controlled by the elevator operation simulation unit 9 to be displayed on the technician terminal 4. In step S7, as in step S6, it is preferable that the elevator operation simulation unit 9 displays the result of the operation simulation in the same manner as the congestion status of the elevator shown in fig. 5 and 6. However, the display may be performed by the technician terminal 4 alone according to information stored in advance in the technician terminal 4.

Thereafter, when the customer 1 differs from the content of the proposal, which is the congestion relief measure to be presented in step S7 in step S8 (no), the process returns to step S6. If yes, the process proceeds to step S9. Here, as a method of confirming the agreement of the customer 1, an investigation report for the congestion of the elevator separately proposed by an elevator maintenance company or a method of displaying the above-described congestion relief measures on the customer terminal 2 may be mentioned to obtain the agreement.

Next, the customer 1 or the elevator maintenance company actually performs the congestion relief countermeasure agreed at step S8. After the congestion relief measures are taken in step S9, in step S10, customer 1 or technician 3 determines whether the congestion relief measures have been completed. That is, it is determined whether or not the congestion relief measures are effective. For this reason, the same processing as the above-described steps S1 to S4 (particularly step S3) is performed. As a result, although the technician 3 of the elevator maintenance company has to regularly monitor the situation at the site, the customer 1 such as a management company of a building can grasp the congestion situation at any time using the customer terminal 2.

Description of reference numerals

1 customer

2 customer terminal

3 technician

4 technician terminal

5 data center server

6 Server processing section

7 crowded state picture generating part

8 information search unit

9 Elevator operation simulation part

10 building master information

11 elevator information

12 communication device

13 elevator operation data collecting device

14 elevator running information storage part

15 elevator operation information

16 people stream monitoring information

17 building elevator information storage unit

20 group management elevator

21 communication device

26 people stream monitoring device.

Claims

1. A congestion status display system for an elevator, which displays the congestion status of the elevator,

the congestion status display system includes:

an information search unit that specifies a first congestion status of an elevator specified by a user, and searches history data of congestion statuses of a plurality of similar elevators similar to the specified elevator; and

and a congestion status screen generating unit that calculates a second congestion status representing the congestion status of the plurality of similar elevators based on the history data, compares the first congestion status with the second congestion status for each predetermined comparison unit, specifies a relative congestion degree of the elevator specified by the user using a result of the comparison, and causes a display device to display information indicating the first congestion status and the second congestion status in a display manner corresponding to the relative congestion degree for each comparison unit.

2. The congestion status display system for elevators according to claim 1,

the information retrieval unit retrieves the plurality of similar elevators from elevator information indicating information related to an elevator.

3. The congestion status display system for elevators according to claim 2,

the information retrieval unit retrieves the plurality of similar elevators by using at least 1 of the use of the elevator designated by the user in the building in which the elevator is installed, the number of available floors, the number of stations, the speed, and the conveyance amount.

4. The congestion status display system of an elevator according to any one of claims 1 to 3,

the relative congestion degree indicates which of relative evaluation criteria made up of a plurality of ranges corresponds to the result of comparison between the first congestion status and the second congestion status.

5. The congestion status display system for elevators according to claim 4,

the comparison unit is the date and time and the floor of the elevator specified by the user,

the first congestion condition and the second congestion condition are an average waiting time of the time of day for each of the floors.

6. A method for displaying the congestion status of an elevator, which displays the congestion status of the elevator,

determining a first congestion status of an elevator specified by a user, searching history data of congestion statuses of a plurality of similar elevators similar to the specified elevator,

calculating a second congestion status representing the congestion statuses of the plurality of similar elevators based on the historical data,

comparing the first congestion status with the second congestion status for each predetermined comparison unit,

using the result of the comparison, determining the relative crowdedness of the user-specified elevator,

and causing a display device to display information indicating the first congestion status and the second congestion status for each of the comparison units in a display mode corresponding to the relative congestion degree.

7. The method for displaying the congestion status of an elevator according to claim 6,

the plurality of similar elevators is retrieved from elevator information representing information related to the elevator.

8. The method for displaying the congestion status of an elevator according to claim 7,

the plurality of similar elevators are retrieved using at least 1 of the use of the building in which the elevator is installed, the number of available floors, the number of stations, the speed, and the conveying amount of the elevator designated by the user.

9. The method of displaying a congestion status of an elevator according to any one of claims 6 to 8,

10. The method of displaying a congestion status of an elevator according to claim 9,