Seismic combination management

Abstract

The name of the invention is earthquake combination management. A method for combined management of a plurality of elevator systems. The method executable when an accident occurs includes: receiving elevator system information from the edge IoT device of the elevator system affected by the accident; analyzing the elevator system information to determine how to classify the elevator system affected by the accident; generating an output according to a result of the analysis; pushing the output to an application layer using an application program interface (API) to provide first state information to an operator in real time; and sending the output to the operator via a communication notification protocol to provide second status information to the operator in real time.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to elevator systems, and in particular, to a system for earthquake portfolio management in conjunction with a number of elevator systems. BACKGROUND

[0002] In an elevator system, elevator shafts are built into a building, and elevator cars travel up and down the elevator shafts to reach landing doors of different floors of the building. Movement of the elevators is driven by a machine, which is controlled by a controller according to instructions received from users of the elevator system. The elevator system is typically managed by a building operator and / or a third party. The building operator and / or the third party are typically responsible for general upkeep and maintenance and repairs, as well as daily monitoring to ensure continued operating conditions. In some cases, the building operator and / or the third party manage multiple elevator systems.

[0003] In areas where earthquakes are common, elevator control systems are equipped with seismic sensors. In most modern elevator systems, when a seismic sensor is activated, the elevators are automatically placed in some form of earthquake operation (EQO) mode. The elevator systems are then categorized by the building operator and / or the third party responsible for managing the elevator systems to identify and address problems before they can resume normal operation. The categorization process can result in downtime and disruption, and does not always provide the needed insight to the right people at the right time. SUMMARY

[0004] According to aspects of the present disclosure, a method for portfolio management of multiple elevator systems. The method executable when an incident occurs includes receiving elevator system information from the edge IoT devices of the elevator systems affected by the incident; analyzing the elevator system information to determine how to categorize the elevator systems affected by the incident; generating an output according to the results of the analysis; pushing the output to an application layer using an application program interface (API) to provide first status information to an operator in real-time; and sending the output to the operator via a communication notification protocol to provide second status information to the operator in real-time.

[0005] Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the present disclosure are described in detail herein and are considered a part of the claimed technology concept. For a better understanding of the present disclosure with the advantages and features thereof, refer to the description and to the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0006] For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts:

[0007] Figure 1 is a perspective view of an elevator system according to an embodiment;

[0008] Figure 2 is a flowchart illustrating a method for combined management of multiple elevator systems according to an embodiment;

[0009] Figure 3A is a schematic diagram of a system for combined management of multiple elevator systems according to an embodiment;

[0010] Figure 3B is a table illustrating data collected by the system according to an embodiment; Figure 3A

[0011] Figure 3C is a flowchart illustrating a method of operation of the system according to an embodiment; Figure 3A

[0012] Figure 4 is a schematic diagram of a cloud-based data analysis rules engine of the system for combined management of multiple elevator systems according to an embodiment;

[0013] Figure 5 is a system for combined management of multiple elevator systems according to an embodiment; Figure 3A and Figure 3B and Figure 4 is an exemplary screenshot of a portal of the system for combined management of multiple elevator systems according to an embodiment; and

[0014] Figure 6 is a schematic diagram of an updated text message according to an embodiment. DETAILED DESCRIPTION

[0015] In areas where earthquakes are common, elevator control systems are equipped with seismic sensors. In most modern elevator systems, when a seismic sensor is activated, the elevators are automatically placed in some form of seismic operation. The elevator systems are then categorized to identify and address problems before they can resume normal operation. The categorization process can result in downtime and disruption, and does not always provide the required insight to the right people at the right time.

[0016] Accordingly, as will be described below, a system and method are provided for rapid categorization of all units in an elevator system combination.

[0017] ​​Edge Internet of Things (IoT) devices are equipped on each elevator system in the portfolio to properly monitor the status of the corresponding elevator. The IoT edge devices collect elevator system status information and send the elevator system status information to the cloud at set intervals or in response to a trigger such as an earthquake. The elevator system status information will include, but is not limited to, the landing information, the motion logic status information, the door position information (closed, closing, open, opening, fully open), and the elevator mode information. The elevator system status information goes to the cloud and is processed and analyzed in real time. This processing can be performed using a data analytics rules engine that resides in the cloud. The results of the analysis can be provided to various user applications such as the expert portal and mobile handsets. The results can also be pushed to communication notification protocols for email and text messaging. The user applications and notifications can be specifically designed for several different roles. The different roles include, but are not limited to, the engineering field support team, the elevator technicians, the building owners, the property management, the call center, and the regulators. Each of the associated portals and mobile devices are specifically designed to meet their particular function and responsibilities.

[0018] When an earthquake occurs and the earthquake sensor for a given elevator is active, a chain of events will occur. The elevator system status will transition from the running mode to the earthquake operation. The IoT edge device will report the latest status and send the earthquake mode status to the cloud. The data analytics rules engine will process the latest status data and the results will be logged and then pushed to the application layer using APIs. The APIs allow all the relevant personnel (i.e., managers, technicians, building owners and operators, tenants, etc.) to be made aware of the earthquake status simultaneously and in real time.

[0019] Once the earthquake status is published, the field operations support role has the proper information to classify the situation. The exact number of elevators affected and the location of each elevator in earthquake operation (EQO) mode, the location of each elevator service technician, the passenger stranded, and the type of building (such as hospital, office building, apartment, etc.). The real-time update of the status and the output from the data analytics rules greatly reduces the classification duration. Based on safety standards and based on business and other types of requirements, the technicians are dispatched to handle the highest priority elevators. As the technicians are dispatched and the elevators are re-commissioned, the portals and mobile devices are updated and both text messages and emails are published in real time.

[0020] REFERENCE Figure 1which is a perspective view of an elevator system 101 including an elevator car 103, a counterweight 105, a tension member 107, a guide rail 109, a machine 111, a position reference system 113, and a controller 115. The elevator car 103 and the counterweight 105 are connected to each other by the tension member 107. The tension member 107 can include or be configured as, for example, a rope, a steel cable, and / or a coated steel belt. The counterweight 105 is configured to balance the load of the elevator car 103 and to facilitate simultaneous and opposite direction movement of the elevator car 103 relative to the counterweight 105 within an elevator hoistway 117 and along the guide rail 109.

[0021] The tension member 107 is engaged with the machine 111, which is part of an overhead structure of the elevator system 101. The machine 111 is configured to control movement between the elevator car 103 and the counterweight 105. The position reference system 113 can be mounted on a stationary portion of the top of the elevator hoistway 117, such as on a sill or guide rail, and can be configured to provide a position signal related to the position of the elevator car 103 within the elevator hoistway 117. In other embodiments, the position reference system 113 can be mounted directly to a moving assembly of the machine 111, or can be positioned in other locations and / or configurations as are well known in the art. The position reference system 113 can be any device or mechanism for monitoring the position of the elevator car and / or counterweight, as is well known in the art. For example and not limitation, the position reference system 113 can be an encoder, a sensor, or other system, and can include speed sensing, absolute position sensing, etc., as will be appreciated by those skilled in the art.

[0022] As shown, the controller 115 can be positioned in a controller room 121 of the elevator hoistway 117 and configured to control operation of the elevator system 101 and, in particular, operation of the elevator car 103. It is to be appreciated that the controller 115 need not be in the controller room 121, but can be in the elevator hoistway or other location in the elevator system. For example, the controller 115 can provide drive signals to the machine 111 to control acceleration, deceleration, leveling, stopping, etc. of the elevator car 103. The controller 115 can also be configured to receive position signals from the position reference system 113 or any other desired position reference device. As the elevator car 103 moves up or down within the elevator hoistway 117 along the guide rail 109, the elevator car 103 can stop at one or more landings 125 as controlled by the controller 115. While shown in the controller room 121, it will be appreciated by those skilled in the art that the controller 115 can be positioned and / or configured in other locations or locations within the elevator system 101. In one embodiment, the controller 115 can be remotely located or located in a distributed computing network, such as a cloud computing architecture. The controller 115 can be implemented using a processor-based machine, such as a personal computer, a server, a distributed computing network, etc.

[0023] The machine 111 can include an electric motor or similar driving mechanism. According to embodiments of the present disclosure, the machine 111 is configured to include an electrically driven motor. The power supply for the motor can be any power source, including a power grid, which is supplied to the motor in combination with other components. The machine 111 can include a traction sheave that transmits force to the hoist member 107 to move the elevator car 103 within the elevator hoistway 117.

[0024] The elevator system 101 also includes one or more elevator doors 104. The elevator doors 104 can be attached integrally to the elevator car 103 or the elevator doors 104 can be positioned on a landing 125 of the elevator system 101, or both. Embodiments disclosed herein can be applicable to elevator doors 104 that are attached integrally to the elevator car 103 or to elevator doors 104 that are positioned on a landing 125 of the elevator system 101, or can be applicable to both. The elevator doors 104 open to allow passengers to enter and exit the elevator car 103.

[0025] Although shown and described with a roped system including a hoist member 107, elevator systems that employ other methods and mechanisms to move an elevator car within an elevator hoistway can employ embodiments of the present disclosure. For example, embodiments can be used in ropeless elevator systems that use linear motors to transmit motion to the elevator car. Embodiments can also be used in ropeless elevator systems that use hydraulic lifts to transmit motion to the elevator car. Embodiments can also be employed in ropeless elevator systems that use self-propelled elevator cars (e.g., elevator cars equipped with friction wheels, pinch wheels, or traction wheels). Figure 1 The non-limiting examples presented are for illustrative and explanatory purposes only.

[0026] With continuing reference to Figure 1 and with further reference to Figure 2 , a method 200 for combined management of multiple elevator systems, such as the elevator system 101 of Figure 1 is provided. The method 200 includes initially deploying edge loT devices throughout the multiple elevator systems (block 201), with each edge loT device configured to sense when an incident occurs, a corresponding elevator system affected by the incident transitions to an incident operational mode. As used herein, an incident can be any incident that can affect an elevator system, such as an earthquake, a weather event, a tsunami, a fire, etc. However, the following description will refer to the case where the incident is an earthquake and the incident operational mode is an earthquake operational (EQO) mode. This is done for clarity and simplicity and is not intended to limit the scope of the specification or the appended claims otherwise.

[0027] As Figure 1As shown in FIG. 2, the method 200 includes periodically receiving elevator system information from each of the edge IoT devices (block 202), receiving elevator system information from the edge IoT devices of the earthquake-affected elevator systems (block 203), and analyzing the elevator system information to determine how to classify the earthquake-affected elevator systems (block 204), wherein the analysis of the elevator system information includes collecting elevator system information from each of the edge IoT devices for respective dates and respective times during the dates. The method 200 further includes generating an output based on the results of the analysis (block 205), wherein the generation of the output includes generating the output based on the elevator system information for the respective dates and respective times during the dates. The method 200 further includes pushing the output to an application layer using an application program interface (API) to provide first status information to an operator in real-time (block 206), and sending the output to the operator via a communication notification protocol to provide second status information to the operator in real-time (block 207). With respect to the pushing of the output of block 206 and the sending of the output of block 207, such effective redundancy is provided to allow a greater number of operators to indeed be informed of the situation, especially in the event that one or more operators are traveling and can not have access to certain communication devices.

[0028] According to embodiments, the method 200 can further include dispatching operators to service the earthquake-affected elevator systems (block 208), repeating the analysis of the elevator system information and the generation of the output to generate an updated output (block 209), pushing the updated output to the application layer using the API to provide updated first status information to the operator in real-time (block 210), and sending the updated output to the operator via the communication notification protocol to provide updated second status information to the operator in real-time (block 211).

[0029] The elevator system information periodically received from each of the edge IoT devices of block 201 and the elevator system information received from the edge IoT devices of the earthquake-affected elevator systems of block 202 can include, but is not limited to, landing information, motion logic state information, door position information (closed, closing, open, opening, fully open), and elevator mode information. The analysis of the elevator system information of block 204 and the generation of the output of block 205 can be performed in a cloud computing environment. In particular, the analysis of the elevator system information can be performed by a cloud-based data analysis rules engine. The output can include, but is not limited to, the number of affected elevator systems, the location of each elevator system in EQO mode, the location of each elevator service technician, information related to passenger entrapment, and information related to the type of building in which each elevator system resides.

[0030] According to embodiments, the APIs can include, but are not limited to, APIs for the expert portal and APIs for the mobile handheld devices, and the communication notification protocol can be a communication protocol for email and text messaging. In some cases, the text messages by which the output is sent to the operator can be real-time updateable. In particular, unread text messages can be real-time updateable. In this way, an operator who does not immediately read a text message can not immediately be aware of a given situation. Later, when the operator checks his text messages, the given situation can have changed or become resolved. In this instance, the operator can be confused if the operator had originally received two text messages (a first text message to alert the operator about the given situation, and a second text message to alert the operator about the change or resolution of the given situation). Alternatively, if the first text message to alert the operator about the given situation is real-time updated to alert the operator about the change or resolution of the given situation before the operator reads the first text message, when the operator finally checks his text messages, the operator will be immediately alerted by a single text message of the fact that the given situation occurred and changed or resolved.

[0031] With reference to Figure 3A , Figure 3B and Figure 3C , and with reference to Figure 4 , there is provided a combined management system 300 for managing a combination of a plurality of elevator systems 301. The combined management system 300 includes an edge Internet of Things (IoT) device 310 deployed throughout each of the plurality of elevator systems 301. The edge IoT device 310 is configured to sense a plurality of characteristics or attributes of the corresponding elevator system 301, especially when the corresponding elevator system 301 is affected by an earthquake (i.e., incident) and thus transitions to an EQO mode (i.e., incident operation mode). The combined management system 300 further includes a cloud-based data analysis rules engine 320 (see Figure 4 ), which periodically receives elevator system information from the edge IoT device 310 of each of the plurality of elevator systems 301, and which receives elevator system information from the elevator system 301 affected by the earthquake. The elevator system information can include, but is not limited to, lobby information, motion logic state information, door position information (closed, closing, open, opening, fully open), and elevator mode information.

[0032] The cloud-based data analytics rules engine 320 is configured to analyze the elevator system information to determine how to classify the earthquake-affected elevator systems 301, generate an output from the results of the analysis, push the output to the application layer 330 using an application program interface (API) to provide first status information to operators in real-time, and send the output to the operators 340 via a communication notification protocol to provide second status information to operators in real-time. The output can include, but is not limited to, the number of affected elevator systems, the location of each elevator system in an EQO mode, the location of each elevator service technician, information related to passenger entrapment, and information related to the type of building in which each elevator system resides. With respect to the pushing and sending of the output by the cloud-based data analytics rules engine 320, this effective redundancy is provided to allow a greater number of operators to indeed be informed of the situation, especially in the event that one or more operators are traveling and can not have access to certain communication devices.

[0033] According to embodiments, the cloud-based data analytics rules engine 320 is further configured to dispatch operators to service the earthquake-affected elevator systems, repeat the analysis of the elevator system information and the generation of the output to generate an updated output, push the updated output to the application layer using the API to provide updated first status information to operators in real-time, and send the updated output to the operators via the communication notification protocol to provide updated second status information to operators in real-time.

[0034] In an exemplary case, as shown in Figure 3B The elevator system information collected by the edge IoT devices 310 for the cloud-based data analytics rules engine 320 includes data identifying the status of units (i.e., elevator systems or elevator cars) on various dates and at various times during those dates. These statuses include, but are not limited to, various operational modes such as idle (IDL), normal (NOR), earthquake operation (EQO), earthquake recovery (EQR), inspection (INS), automatic rescue operation (ARO), and not available (NAV).

[0035] As shown in Figure 3C The operation of the elevator system 301 is illustrated and begins with an idle or normal reading at block 360. At block 361, an earthquake occurs, and at block 362, a reading is taken from the corresponding edge IoT device 310. If the reading indicates that an operation of higher priority than EQO has occurred, such as an “emergency stop,” then at block 363, the elevator system 301 immediately enters a shutdown (where priority is defined as programmed in the elevator controller software) and a NAV status.

[0036] At block 364, it is determined whether the reading of the edge IoT device 310 indicates that a high GAL (GAL is a unit of acceleration that measures seismic intensity; 1 GAL = 1 cm / sec / sec, and high / low / ultra-low GAL values can be set differently according to building height, sensor location, etc.) is detected. At block 365, if a high GAL is detected, the elevator system 301 enters the EQO mode. At block 366, if a high GAL is not detected, it is determined whether the reading of the edge IoT device 310 indicates that a low GAL is detected, and if a low GAL is detected, at block 367, the elevator system 301 enters the EQO mode for a predefined period of time (i.e., 10 minutes), after which, at block 368, the elevator system 301 enters the EQR mode. After this, at block 369, the elevator system 301 determines whether the EQR was successful, and if so, at block 370, the elevator system 301 enters the NOR / IDL mode. After this, at block 371, the operator opens / closes the INS mode, at block 372, the elevator system 301 enters the INS mode, and then returns to the IDL / NOR mode. At block 373, if a low GAL is not detected, it is determined whether the reading of the edge IoT device 310 indicates that an ultra-low GAL is detected. If not, the elevator system 301 returns to the IDL / NOR mode. If so, at block 374, the elevator system 301 enters the EQO mode for a predefined period of time (i.e., 10 minutes), at block 375, the edge IoT device 310 is automatically reset, after which, the elevator system 301 returns to the IDL / NOR mode.

[0037] With continued reference to Figure 4 and with further reference to Figure 5 And according to embodiments, the API can include, but is not limited to, an API for the expert portal and the handheld device, which can provide, for example, various user interface screens 501, 502, 503, and 504. Each of the user interface screens 501, 502, 503, and 504 provides a plurality of types of information to the operator, including, but not limited to, the locations of elevator systems that have been affected by an earthquake, the real-time status of these elevator systems, the dispatch situation of each of these elevator systems, etc. The communication notification protocol can be a communication protocol for email and text messaging.

[0038] With reference to Figure 6In some cases, the text messages by which the output is sent to the operator can be real-time updateable. In particular, the unread text messages can be real-time updateable. In this way, an operator who does not immediately read the text messages can not immediately be aware of a given situation. Later, when the operator checks his text messages, the given situation can have changed or become resolved. In this instance, the operator can be confused if the operator had originally received two text messages (a first text message to alert the operator about the given situation, and a second text message to alert the operator about the change or resolution of the given situation). Alternatively, as shown in FIG. 6B, if the first text message to alert the operator about the given situation is real-time updated to become an updated first text message 602 to alert the operator about the change or resolution of the given situation before the operator reads the first text message 601, when the operator finally checks his text messages, the operator will be immediately alerted by a single text message (i.e., the updated first text message 602) of the fact that the given situation occurred and changed or resolved. Figure 6

[0039] The technical effect and benefit of the present disclosure is to provide a system and method for earthquake group management. When an earthquake occurs, the affected elevators will be automatically put into earthquake operation (EQO) mode and thus substantially stop service for the passenger population until the corresponding earthquake sensor is cleared, allowing the elevators to be put back into service. The classification process for achieving this is automated.

[0040] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structures, materials, or acts for performing the functions in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the technical concepts disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present disclosure. The embodiments were chosen and described in order to best explain the principles of the present disclosure and the practical application thereof, and to enable others skilled in the art to understand various embodiments with various modifications as are suited to the particular use contemplated, without affecting the general principles of the disclosure.

[0041] While the preferred embodiments of the present disclosure have been described, it is to be understood that various modifications and enhancements can be made by those skilled in the art, now or in the future, without departing from the scope of the claims which follow. These claims should be construed as maintaining proper protection for the originally described disclosure.​

Claims

1. A method for combined management of a plurality of elevator systems, wherein edge Internet of Things (IoT) devices are deployed throughout the plurality of elevator systems, the method being executable when an accident occurs and an elevator system affected by the accident switches to an accident operation mode, and comprising: receiving elevator system information from the edge IoT device of the elevator system affected by the accident; analyzing the elevator system information to determine how to classify the elevator system affected by the incident; generating an output based on the results of said analysis; Pushing the output to an application layer using an application programming interface (API) to provide first status information to an operator in real time; as well as The output is sent to the operator via a communication notification protocol to provide the operator with second status information in real time.

2. The method according to claim 1, wherein The incident is an earthquake, and the incident operating mode is an earthquake operating (EQO) mode.

3. The method according to claim 1, further comprising periodically receiving elevator system information from each of the edge IoT devices, in, The elevator system information periodically received from each of the edge IoT devices and the elevator system information received from the edge IoT device of the elevator system affected by the accident includes floor information, motion logic status information, door position information (closed, closing, open, opening, fully open) and elevator mode information.

4. The method according to claim 1, wherein: said analyzing of said elevator system information and said generating of said output are performed in a cloud computing environment, and The analyzing of the elevator system information includes collecting elevator system information for each date and each time during these dates from each edge IoT device, and the generating of the output includes generating the output based on the elevator system information for each date and each time during these dates.

5. The method according to claim 1, wherein The output includes the number of elevator systems affected, the location of each elevator system in the emergency operating mode, the location of each elevator service technician, information related to passenger detention, and information related to the type of building in which each elevator system resides.

6. The method according to claim 1, wherein The APIs include an API for an expert portal and an API for a mobile handset, and the communication notification protocol is for email and text messaging.

7. The method according to claim 6, wherein: The text message through which the output is sent to the operator is updateable in real time.

8. The method according to claim 1, further comprising: dispatching the operator to service the elevator system affected by the incident; repeating said analyzing of said elevator system information and said generating of said output to generate an updated output; Pushing the updated output to the application layer using the API to provide updated first status information to an operator in real time; as well as The updated output is sent to the operator via the communication notification protocol to provide the operator with updated second status information in real time.

9. A method for earthquake portfolio management for a plurality of elevator systems when an earthquake occurs and an elevator system affected by the earthquake switches to an earthquake operation (EQO) mode, deploying edge Internet of Things (IoT) devices throughout the plurality of elevator systems, the method comprising: receiving, at a cloud-based data analytics rules engine, elevator system information from the edge IoT device of the elevator system affected by the earthquake; analyzing the elevator system information at the cloud-based data analytics rules engine to determine how to classify the elevator system affected by the earthquake; generating, at the cloud-based data analysis rules engine, an output based on a result of the analysis; Pushing the output to an application layer using an application programming interface (API) to provide first status information to an operator in real time; as well as The output is sent to the operator via a communication notification protocol to provide the operator with second status information in real time.

10. The method according to claim 9, further comprising periodically receiving elevator system information from each of the edge IoT devices, in, The elevator system information periodically received from each of the edge IoT devices and the elevator system information received from the edge IoT device of the elevator system affected by the accident includes floor information, motion logic status information, door position information (closed, closing, open, opening, fully open) and elevator mode information.

11. The method according to claim 9, wherein The output includes the number of elevator systems affected, the location of each elevator system in the emergency operating mode, the location of each elevator service technician, information related to passenger detention, and information related to the type of building in which each elevator system resides.

12. The method according to claim 9, wherein The APIs include an API for an expert portal and an API for a mobile handset, and the communication notification protocol is for email and text messaging.

13. The method according to claim 12, wherein: The text message through which the output is sent to the operator is updateable in real time.

14. The method according to claim 9, further comprising: dispatching the operator to service the elevator system affected by the incident; repeating said analyzing of said elevator system information and said generating of said output to generate an updated output; Pushing the updated output to the application layer using the API to provide updated first status information to an operator in real time; as well as The updated output is sent to the operator via the communication notification protocol to provide the operator with updated second status information in real time.

15. A combined management system for a plurality of elevator systems, the combined management system comprising: an edge Internet of Things (IoT) device deployed throughout the plurality of elevator systems, the edge IoT device configured to sense an elevator system affected by an accident and transition to an accident operating mode; as well as A cloud-based data analysis rules engine receives elevator system information from the edge IoT device of the elevator system affected by the accident, the cloud-based data analysis rules engine being configured to: analyzing the elevator system information to determine how to classify the elevator system affected by the incident, generating output based on the results of said analysis, Pushing the output to an application layer using an application programming interface (API) to provide first status information to an operator in real time, and The output is sent to the operator via a communication notification protocol to provide the operator with second status information in real time.

16. The combination management system according to claim 15, wherein: The incident is an earthquake, and the incident operating mode is an earthquake operating (EQO) mode.

17. The portfolio management system according to claim 15, wherein: The cloud-based data analysis rules engine periodically receives elevator system information from each of the edge IoT devices, and The elevator system information periodically received from each of the edge IoT devices and the elevator system information received from the edge IoT device of the elevator system affected by the accident includes floor information, motion logic status information, door position information (closed, closing, open, opening, fully open) and elevator mode information.

18. The combination management system according to claim 15, wherein: The APIs include an API for an expert portal, an API for mobile handsets, and the communication notification protocols are for email and text messaging.

19. The combination management system according to claim 18, wherein: The text message through which the output is sent to the operator is updateable in real time.

20. The combination management system according to claim 15, wherein: The cloud-based data analysis rules engine is further configured to: dispatching the operator to service the elevator system affected by the incident, repeating the analysis of the elevator system information and the generation of the output to generate an updated output, Pushing the updated output to the application layer using the API to provide updated first status information to the operator in real time, and The updated output is sent to the operator via the communication notification protocol to provide the operator with updated second status information in real time.

Images