Method for managing portfolio of multiple elevator systems, earthquake portfolio management method, and portfolio management system

Abstract

To provide a method for managing a portfolio of multiple elevator systems.SOLUTION: The present method can be executed when an incident occurs, and comprises receiving elevator system information from an edge IoT device of an elevator system affected by the incident, analyzing the elevator system information to determine a triage method for the affected elevator system, generating an output according to the results of the analysis, pushing an output to an application layer using an application programming interface (API) to provide first status information to an operator in real time, and transmitting the output to the operator via a communication notification protocol to provide second status information to the operator in real time.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to elevator systems, and more particularly to a system for earthquake portfolio management incorporating many elevator systems. [Background technology]

[0002] In an elevator system, an elevator shaft is integrated into a building, and elevator cars travel up and down the elevator shaft to arrive at landing doors on different floors of the building. Elevator movement is driven by machines controlled by a controller according to commands received from users of the elevator system. Elevator systems are often managed by a building operator and / or a third party, who are typically responsible for general maintenance and repairs, as well as day-to-day monitoring to ensure continued operating condition. In some cases, the building operator and / or third party manages multiple elevator systems.

[0003] In areas where earthquakes are common, elevator control systems are equipped with earthquake sensors. In most modern elevator systems, when the earthquake sensor is activated, the elevator automatically enters some kind of earthquake response operation (EQO) mode. The elevator system is then triaged by the building operator and / or a third party responsible for managing the elevator system to identify and address the issue before normal operation can resume. The triage process can result in downtime and outages and does not always provide the right people with the insight they need in a timely manner. Summary of the Invention [Problem to be solved by the invention]

[0004] The object of the present invention is therefore to improve an elevator system of the kind mentioned at the outset so that the above-mentioned disadvantages are reduced. [Means for solving the problem]

[0005] According to an aspect of the present disclosure, there is provided a method for portfolio management of multiple elevator systems, the method being executable when an incident occurs and including: receiving elevator system information from an edge IoT device of an elevator system affected by the incident, analyzing the elevator system information to determine a triage method for the elevator system affected by the incident, generating an output according to a result of the analyzing, 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 an operator via a communication notification protocol to provide second status information to the operator in real time.

[0006] Further features and advantages are realized by the techniques of the present disclosure. Other embodiments and aspects of the present disclosure are described in detail herein and are considered part of the claimed technical concept. For a better understanding of the present disclosure in terms of its advantages and features, please refer to the description and drawings.

[0007] For a more complete understanding of this disclosure, reference is now made to the following brief description in conjunction with the accompanying drawings and detailed description, wherein like reference numerals represent like parts. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a perspective view of an elevator system according to an embodiment. [Figure 2] 1 is a flow chart illustrating a method of portfolio management for multiple elevator systems according to an embodiment. [Figure 3A] FIG. 1 is a schematic diagram of a portfolio management system for multiple elevator systems according to an embodiment. [Figure 3B] 3B is a table that graphically illustrates data collected by the system of FIG. 3A according to an embodiment. [Figure 3C] 3B is a flow chart illustrating a method of operation of the system of FIG. 3A according to an embodiment. [Figure 4] FIG. 1 is a schematic diagram illustrating a cloud-based data analytics rules engine of a portfolio management system for multiple elevator systems, according to an embodiment. [Figure 5] 5 is an exemplary screenshot of a portal of a portfolio management system for the multiple elevator systems of FIGS. 3A and 3B and 4 according to an embodiment. [Figure 6] FIG. 10 is a schematic diagram of an updated text message according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] In areas where earthquakes are common, elevator control systems are equipped with earthquake sensors. In most modern elevator systems, when the earthquake sensors are activated, the elevator automatically initiates some type of seismic action. The elevator system is then triaged to identify and address the problem before normal operation can resume. The triage process can result in downtime and outages and does not always provide the right people with the insight they need in a timely manner.

[0010] Therefore, as described below, a system and method are provided for rapid triage of all units in an elevator system portfolio.

[0011] Each elevator system is equipped with an edge internet of things (IoT) device to optimally monitor the status of its corresponding elevator. The IoT edge device collects elevator system status information and transmits it to the cloud at set intervals or in response to triggers such as earthquakes. The elevator system status information includes, but is not limited to, landing information, operational logic state information, door position information (closed, closed, open, open, fully open), and elevator mode information. The elevator system status information enters the cloud for real-time processing and analysis. Processing can be performed using a data analysis rules engine residing in the cloud. The results of the analysis can be provided to various user applications, such as expert portals and mobile handheld devices. The results can also be pushed to email and text messaging communication notification protocols. User applications and notifications can be custom designed for various different personas, including, but not limited to, engineering field support teams, elevator mechanics, building owners, property managers, call centers, and supervisors. Each associated portal and mobile device is specifically designed to fulfill designated roles and responsibilities.

[0012] When an earthquake occurs and the earthquake sensor of a given elevator is activated, a series of events occurs: The elevator system status transitions from running mode to earthquake operation. The IoT edge device reports the latest status and sends the earthquake mode status to the cloud. The data analytics rules engine processes the latest status data and the results are recorded and then pushed to the application layer using APIs. The APIs allow all relevant parties (i.e., managers, mechanics, building owners and operators, tenants, etc.) to simultaneously get the earthquake status in real time.

[0013] Once an earthquake status is issued, the field operations support persona receives the appropriate information to triage the situation, including the exact number of affected elevators and the location of each elevator in earthquake-enhanced operation (EQO) mode, the location of each elevator service mechanic, entrapped passengers, and the type of building (e.g., hospital, office building, apartment complex, etc.). With real-time updated status and output from data analysis rules, triage time is significantly reduced. Mechanics are dispatched to address the highest priority elevators based on safety standards and business and other types of requirements. Once mechanics are dispatched and the elevators are back in operation, portals and mobile devices are updated, and text messages and emails are issued, all in real time.

[0014] Referring to FIG. 1, FIG. 1 is a perspective view of elevator system 101, which includes elevator car 103, counterweight 105, tension member 107, guide rails 109, machine 111, position referencing system 113, and controller 115. Elevator car 103 and counterweight 105 are connected to each other by tension member 107. Tension member 107 may include or be configured as, for example, rope, steel cable, and / or coated steel belt. Counterweight 105 is configured to balance the load of elevator car 103 and facilitate simultaneous and opposite movement of elevator car 103 along guide rails 109 within elevator shaft 117 relative to counterweight 105.

[0015] Tension member 107 engages machine 111, which is part of the overhead structure of elevator system 101. Machine 111 is configured to control movement between elevator car 103 and counterweight 105. Position reference system 113 may be attached to a fixed portion at the top of elevator shaft 117, such as a support rail or guide rail, and may be configured to provide a position signal related to the position of elevator car 103 within elevator shaft 117. In other embodiments, position reference system 113 may be attached directly to a moving component of machine 111 or may be installed in other locations and / or configurations, as known in the art. Position reference system 113 may be any device or mechanism for monitoring the position of an elevator car and / or counterweight, as known in the art. For example, without limitation, position reference system 113 may be an encoder, sensor, or other system and may include velocity sensing, absolute position sensing, etc., as will be understood by those skilled in the art.

[0016] The controller 115 may be located in a controller room 121 in the elevator shaft 117, as shown, and is configured to control the operation of the elevator system 101, and specifically the elevator car 103. It will be understood that the controller 115 need not be located in the controller room 121, but may be located elsewhere in the elevator shaft or elevator system. For example, the controller 115 may provide drive signals to the machine 111 to control the acceleration, deceleration, leveling, stopping, etc., of the elevator car 103. The controller 115 may 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 in the elevator shaft 117 along the guide rails 109, it may be controlled by the controller 115 to stop at one or more landings 125. While the controller 115 is shown in the controller room 121, those skilled in the art will understand that the controller 115 may be located and / or configured at other locations or positions within the elevator system 101. In one embodiment, the controller 115 may be located remotely or may be located within a distributed computing network (e.g., a cloud computing architecture). The controller 115 may be implemented using a processor-based machine such as a personal computer, a server, a distributed computing network, or the like.

[0017] The machine 111 may include a motor or similar drive mechanism. According to an embodiment of the present disclosure, the machine 111 is configured to include an electric motor. The power source for the motor may be any power source, including a power grid, which in combination with other components supplies the motor. The machine 111 may include a traction sheave that provides force to the tension member 107 to move the elevator car 103 within the elevator shaft 117.

[0018] Elevator system 101 also includes one or more elevator doors 104. Elevator doors 104 may be integrally attached to elevator car 103, or elevator doors 104 may be located at landings 125 of elevator system 101, or both. Embodiments disclosed herein may be applicable to elevator doors 104 integrally attached to elevator car 103, or elevator doors 104 located at landings 125 of elevator system 101, or both. Elevator doors 104 open to allow passengers to enter and exit elevator car 103.

[0019] Although a roping system including tension member 107 is shown and described, elevator systems employing other methods and mechanisms for moving an elevator car within an elevator shaft may employ embodiments of the present disclosure. For example, embodiments may be employed in ropeless elevator systems that use linear motors to impart motion to the elevator car. Embodiments may also be employed in ropeless elevator systems that use hydraulic lifts to impart motion to the elevator car. Embodiments may also be employed in ropeless elevator systems that use self-propelled elevator cars (e.g., elevator cars with friction wheels, pinch wheels, or traction wheels). Figure 1 is merely a non-limiting example presented for purposes of illustration and description.

[0020] With continued reference to FIG. 1 and further reference to FIG. 2, a method 200 of portfolio management for multiple elevator systems, such as system 101 of FIG. 1, is provided. Method 200 initially includes deploying edge IoT devices (block 201) throughout the multiple elevator systems, each configured to sense an incident, such that the corresponding elevator system affected by the incident transitions to an incident operation mode. As used herein, an incident may be any incident that may affect an elevator system, such as, for example, an earthquake, a weather event, a tsunami, a fire, etc. However, the following description will be for the case where the incident is an earthquake and the incident operation mode is an earthquake-enforced operation (EQO) mode. This is done for clarity and brevity and is not intended to limit the scope of this description or the claims below in any other way.

[0021] As shown in FIG. 1 , 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 an elevator system affected by an earthquake (block 203), and analyzing the elevator system information to determine a triage method for the elevator system affected by the earthquake (block 204). Analyzing the elevator system information includes collecting elevator system information from each of the edge IoT devices for various dates and various times between the dates. Method 200 also includes generating an output according to a result of the analyzing (block 205), where generating the output includes generating the output based on the elevator system information for various dates and various times between the dates. Method 200 also 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 blocks 206, pushing output, and 207, transmitting output, this effective redundancy is provided to ensure that more operators are informed of the situation, especially when one or more operators are mobile and unable to use a particular communication device.

[0022] According to an embodiment, method 200 may also include dispatching an operator to maintain the elevator system affected by the incident (block 208), repeating the analyzing of the elevator system information and generating the updated output to generate an updated output (block 209), pushing the updated output to an application layer using an API to provide the operator with updated first status information in real time (block 210), and sending the updated output to the operator via a communication notification protocol to provide the operator with updated second status information in real time (block 211).

[0023] The elevator system information periodically received from each of the edge IoT devices in block 201 and the elevator system information received from the edge IoT device of the elevator system affected by the incident in block 202 may include, but is not limited to, landing information, operational logic state information, door position information (closed, closed, open, open, fully open), and elevator mode information. Analyzing the elevator system information in block 204 and generating output in block 205 may be performed in a cloud computing environment. Specifically, analyzing the elevator system information may be performed by a cloud-based data analysis rules engine. The output may 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 mechanic, information related to passenger entrapment, and information related to the building type in which each elevator system resides.

[0024] According to an embodiment, the API may include, but is not limited to, an expert portal API and a mobile handheld device API, and the communication notification protocol may be a communication protocol for email and text messaging. In some cases, the output is sent to the operator via a text message, and the text message may be updateable in real time. Specifically, unread text messages may be updateable in real time. In this manner, an operator who does not immediately read the text message may not immediately recognize a given situation. Later, when the operator views the text message, the given situation may have changed or been resolved. In this case, the operator may be confused if he or she receives two text messages (one alerting the operator to the given situation and the second alerting the operator that the given situation has changed or been resolved). Instead, if a first text message alerting an operator to a given situation is updated in real time, alerting the operator to a change or resolution of the given situation before the operator reads the first text message, then when the operator finally looks through the text message, the operator will be quickly alerted to the fact that a given situation has occurred and changed or resolved from just a single text message.

[0025] 3A, 3B, and 3C, and also with reference to FIG. 4, a portfolio management system 300 for managing a portfolio of multiple elevator systems 301 is provided. The portfolio management system 300 includes edge Internet of Things (IoT) devices 310 deployed across each of the multiple elevator systems 301. The edge IoT devices 310 are configured to sense multiple features or characteristics of the corresponding elevator systems 301, particularly when the corresponding elevator systems 301 are affected by an earthquake (i.e., an incident) and, as a result, transition to an EQO mode (i.e., an incident operation mode). The portfolio management system 300 further includes a cloud-based data analytics rules engine 320 (see FIG. 4). The cloud-based data analytics rules engine 320 periodically receives elevator system information from the edge IoT devices 310 of each elevator system 301 and also receives elevator system information from elevator systems 301 affected by the earthquake. Elevator system information may include, but is not limited to, landing information, operational logic state information, door position information (closed, closed, open, open, fully open), and elevator mode information.

[0026] The cloud-based data analytics rules engine 320 is configured to analyze elevator system information to determine how to triage the earthquake-affected elevator systems 301, generate outputs according to the results of the analysis, push the outputs to the application layer 330 using an application program interface (API) to provide the operators with first status information in real time, and send the outputs to the operators 340 via a communication notification protocol to provide the operators with second status information in real time. The outputs may include, but are not limited to, the number of affected elevator systems, the location of each elevator system in EQO mode, the location of each elevator service mechanic, information related to passenger entrapment, and information related to the building type in which each elevator system resides. With regard to pushing outputs and sending outputs by the cloud-based data analytics rules engine 320, this effective redundancy is provided to ensure that more operators are informed of the situation, especially when one or more operators are traveling and unable to use a particular communication device.

[0027] According to an embodiment, the cloud-based data analytics rules engine 320 is further configured to: dispatch an operator to maintain the elevator system affected by the earthquake; iterate between analyzing the elevator system information and generating the updated output to generate an updated output; push the updated output to the application layer using an API to provide the operator with updated first status information in real time; and send the updated output to the operator via a communication notification protocol to provide the operator with updated second status information in real time.

[0028] 3B, elevator system information collected by the edge IoT device 310 for the cloud-based data analytics rules engine 320 includes data identifying the state of the unit (i.e., elevator system or elevator car) on various dates and various times between those dates. These states include, but are not limited to, various operating modes such as idle (IDL), normal (NOR), earthquake operation (EQO), earthquake recovery (EQR), inspection (INS), automatic rescue operation (ARO), and unavailable (NAV).

[0029] As shown in Figure 3C, operation of elevator system 301 is shown, starting with an idle or normal reading at block 360. At block 361, an earthquake occurs and at block 362 a reading is obtained from the corresponding edge IOT device 310. If the reading indicates that an action with a higher priority than EQO has occurred, such as an "emergency stop," then at block 363, elevator system 301 programs the priority definition into the elevator controller software and immediately enters a shutdown state and goes to the NAV state.

[0030] In block 364, it is determined whether the edge IOT device 310 reading indicates that a high GAL is detected (GAL is a unit of acceleration for measuring seismic intensity. 1 GAL = 1 cm / sec / sec, and high / low / out-of-range GAL values ​​can be set differently depending on the building height, sensor location, etc.). If a high GAL is detected, in block 365, the elevator system 301 enters EQO mode. If a high GAL is not detected, in block 366, it is determined whether the edge IOT device 310 reading indicates that a low GAL is detected. If a high GAL is detected, in block 367, the elevator system 301 enters EQO mode. After a predefined period (i.e., 10 minutes) is reached, the elevator system 301 enters EQR mode in block 368, following block 367. Following this, the elevator system 301 determines whether a successful EQR was achieved in block 369, and if so, the elevator system 301 enters NOR / IDL mode in block 370. Following this, in block 371, the operator turns INS mode on / off, and in block 372, the elevator system 301 enters INS mode and then returns to IDL / NOR mode. If a low GAL is not detected, in block 373, it is determined whether the edge IOT device 310 reading indicates that a very low GAL is detected. If not, the elevator system 301 returns to IDL / NOR mode. If so, in block 374, the elevator system 301 enters EQO mode, and after a predefined period (i.e., 10 minutes), the edge IOT device 310 automatically resets in block 375, and following block 375, the elevator system 301 returns to IDL / NOR mode.

[0031] Continuing with reference to FIG. 4 and further with reference to FIG. 5, according to an embodiment, the API may include, for example, but is not limited to, an expert portal and handheld device API that can provide various user interface screens 501, 502, 503, and 504. Each of user interface screens 501, 502, 503, and 504 provides multiple types of information to the operator, including, but not limited to, the location of elevator systems affected by the earthquake, the real-time status of those elevator systems, the dispatch status for each of those elevator systems, etc. The communication notification protocols may be communication protocols for email and text messaging.

[0032] Referring to FIG. 6 , in some cases, the output is sent to the operator via a text message, and the text message may be updateable in real time. Specifically, unread text messages may be updateable in real time. In this manner, an operator who does not immediately read the text message may not immediately recognize a given situation. Later, when the operator views the text message, the given situation may have changed or been resolved. In this case, the operator may be confused if he or she receives two text messages (one alerting the operator to the given situation and another alerting the operator that the given situation has changed or been resolved). Instead, as shown in FIG. 6, if a first text message 601 alerting an operator to a given situation is updated in real time to become an updated first text message 602, thereby alerting the operator to a change or resolution of the given situation before the operator reads the first text message, then when the operator finally looks through the text messages, the operator will be quickly alerted to the fact that the given situation has occurred and changed or resolved from only a single text message (i.e., updated first text message 602).

[0033] A technical effect and advantage of the present disclosure is the provision of a system and method for earthquake portfolio management. When an earthquake occurs, affected elevators are automatically placed into earthquake-enhanced operation (EQO) mode, essentially shutting down service to general passenger traffic until the corresponding seismic sensors are cleared and the elevators are able to operate again. The triage process to accomplish this is automated.

[0034] Corresponding structure, materials, acts, and equivalents of all means-plus-function or step-plus-function elements within the scope of the following claims are intended to include any structure, material, or acts for performing a function in combination with other claimed elements as explicitly 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 in the form disclosed. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the present disclosure. The embodiments were chosen and described to best explain the principles of the present disclosure and its practical application, and to enable those skilled in the art to understand the present disclosure for various embodiments with various modifications as suitable for the particular use intended.

[0035] While preferred embodiments of the present disclosure have been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements that fall within the scope of the following claims, which should be construed to maintain the appropriate protection for the present disclosure as originally described.

Claims

1. A portfolio management method for multiple elevator systems having edge Internet of Things (IoT) devices deployed throughout, the method being executable when an incident occurs and elevator systems affected by the incident transition to an incident operating mode; receiving elevator system information from the edge IoT device of the elevator system affected by the incident; analyzing the elevator system information to determine a triage method for the elevator system affected by the incident; generating an output according to a result of said analyzing; pushing the output to an application layer using an application program interface (API) to provide a first status information to an operator in real time; transmitting the output to the operator via a communication notification protocol to provide second status information to the operator in real time; The method comprising:

2. The method of claim 1 , wherein the incident is an earthquake and the incident operation mode is an earthquake operation (ECO) mode.

3. and periodically receiving elevator system information from each of the edge IoT devices.

2. The method of claim 1, wherein 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 incident includes landing information, operational logic state information, door position information (closed, closing, open, open, fully open), and elevator mode information.

4. the analyzing the elevator system information and the generating the output are performed in a cloud computing environment; 2. The method of claim 1, wherein analyzing the elevator system information includes collecting elevator system information from each of the Edge IOT devices for various dates and various times between those dates, and generating the output includes generating the output based on the elevator system information for the various dates and the various times between those dates.

5. 2. The method of claim 1, wherein the output includes the number of affected elevator systems, the location of each elevator system in the incident operating mode, the location of each elevator service mechanic, information related to passenger entrapment, and information related to the building type in which each elevator system is located.

6. The method of claim 1 , wherein the APIs include an expert portal API and a mobile handheld device API, and the communication notification protocols are for email and text messaging.

7. 7. The method of claim 6, wherein the output is transmitted to the operator in a text message, the text message being updatable in real time.

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

9. 1. A method for earthquake portfolio management of multiple elevator systems deployed throughout with edge Internet of Things (IoT) devices, comprising: when an earthquake occurs and elevator systems affected by the earthquake transition to an earthquake quality of operation (EQO) mode; receiving elevator system information from the edge IoT devices of the elevator system affected by the earthquake at a cloud-based data analytics rules engine; analyzing the elevator system information with the cloud-based data analysis rules engine to determine a triage method for the elevator system affected by the earthquake; generating an output in the cloud-based data analysis rules engine according to a result of the analyzing; and pushing the output to an application layer using an application program interface (API) to provide a first status information to an operator in real time; transmitting the output to the operator via a communication notification protocol to provide second status information to the operator in real time; The method comprising:

10. and periodically receiving elevator system information from each of the edge IoT devices.

10. The method of claim 9, wherein 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 incident includes landing information, operational logic state information, door position information (closed, closing, open, open, fully open), and elevator mode information.

11. 10. The method of claim 9, wherein the output includes the number of affected elevator systems, the location of each elevator system in the incident operating mode, the location of each elevator service mechanic, information related to passenger entrapment, and information related to the building type in which each elevator system is located.

12. The method of claim 9 , wherein the APIs include an expert portal API and a mobile handheld device API, and the communication notification protocols are for email and text messaging.

13. 13. The method of claim 12, wherein the output is transmitted to the operator in a text message, the text message being updatable in real time.

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

15. 1. A portfolio management system for a plurality of elevator systems, comprising: edge Internet of Things (IoT) devices deployed throughout the plurality of elevator systems, the edge IoT devices configured to sense when an elevator system affected by an incident transitions to an incident operating mode; and a cloud-based data analytics rules engine that receives elevator system information from the edge IoT devices of the elevator system affected by the incident, the cloud-based data analytics rules engine comprising: analyzing the elevator system information to determine a triage method for the elevator system affected by the incident; generating an output according to a result of said analyzing; pushing the output to an application layer using an application program interface (API) to provide a first status information to an operator in real time; transmitting the output to the operator via a communication notification protocol to provide second status information to the operator in real time; the cloud-based data analysis rules engine configured to: The portfolio management system comprising:

16. The portfolio management system of claim 15 , wherein the incident is an earthquake and the incident operation mode is an earthquake operation (ECO) mode.

17. the cloud-based data analysis rules engine periodically receives elevator system information from each of the edge IoT devices; 16. The portfolio management system of claim 15, wherein 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 incident includes landing information, operational logic state information, door position information (closed, closing, open, open, fully open), and elevator mode information.

18. 16. The portfolio management system of claim 15, wherein the APIs include an expert portal API and a mobile handheld device API, and the communication notification protocols are for email and text messaging.

19. 20. The portfolio management system of claim 18, wherein the output is transmitted to the operator in a text message, the text message being updatable in real time.

20. The cloud-based data analysis rules engine further comprises: 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; using the API to push the updated output to the application layer to provide updated first status information to the operator in real time; transmitting the updated output to the operator via the communication notification protocol to provide updated second status information to the operator in real time; The portfolio management system of claim 15 configured to:

Images