Patent Description:
Equipment system operators may oversee multiple equipment systems at one or more geographic locations. Equipment systems can include many components with varying maintenance schedules, expected service lives, and component ages. Overseeing equipment system servicing can be challenging due to the large volume of data, geographical distribution of equipment, and variations in equipment characteristics installed at one or more locations. <CIT> discloses an elevator maintenance business support system wherein the elevator monitoring system of the maintenance sales support system sequentially transmits the monitoring system log to an analysis device. The maintenance worker portable terminal sequentially transmits the terminal operation log to the analysis device. When an analysis instruction is generated by the maintenance worker portable terminal, the analysis unit acquires the monitoring system log from the log database, correlates the results and transmits it to a control centre PC or maintenance portable terminal.

According to the invention as stipulated in claim <NUM>, a method includes identifying an entity and an entity location of a plurality of equipment. A data repository is accessed that includes a plurality of equipment servicing data associated with the equipment at the entity location. A map image is output on a graphical user interface including one or more icons indicating one or more equipment locations and status of the equipment based on the equipment servicing data from the data repository. One or more equipment status details are selectively displayed on the graphical user interface responsive to a detected user input action.

Further embodiments may include where the detected user input action includes a hovering action over at least one of the one or more icons, and the one or more equipment status details are associated with a specific instance of the equipment at the entity location depicted on the map image.

Further embodiments may include where one or more display characteristics of the one or more icons vary based on the status of the equipment indicative of one or more differences in operational conditions of the equipment.

Further embodiments may include outputting a health score on the graphical user interface that summarizes a plurality of conditions of the equipment at the one or more equipment locations displayed on the graphical user interface.

Further embodiments may include outputting an uptime indicator on the graphical user interface that summarizes a performance history of the equipment at the one or more equipment locations displayed on the graphical user interface for a first predetermined period of time.

Further embodiments may include outputting an activity history on the graphical user interface that summarizes a total number of visits, scheduled visits, predictive maintenance events, and service requests for the equipment at the one or more equipment locations displayed on the graphical user interface for a second predetermined period of time.

Further embodiments may include outputting a unit summary on the graphical user interface of a plurality of units of the equipment at the one or more equipment locations displayed on the graphical user interface, where each of the units includes an elevator system.

Further embodiments may include updating the graphical user interface with a plurality of unit status details based on detecting a unit selection from the plurality of units, and replacing the map image on the graphical user interface with a schematic view of a plurality of components of the elevator system including the unit selection.

Further embodiments may include where the unit status details include the health score for the unit selected, the activity history for the unit selected, and one or more time history plots for the unit selected.

Further embodiments may include detecting a change in a zoom level of the map image on the graphical user interface, identifying a plurality of entity locations of the entity within a geographic area displayed on the map image, retrieving the equipment servicing data associated with the equipment at the plurality of entity locations from the data repository, updating the map image on the graphical user interface with a plurality of icons indicative of the status of the equipment at the plurality of entity locations, determining an update to a plurality of summary data associated with the equipment at the plurality of entity locations, and updating one or more values displayed on the graphical user interface with the update to the summary data.

According to the invention as stipulated in claim <NUM>, a system includes a processing system, a user interface driver, and a memory system. The user interface driver is operable to output a graphical user interface and receive input through the graphical user interface. The memory system includes a plurality of instructions stored thereon that, when executed by the processing system, cause the system to perform a plurality of operations. The operations include identifying an entity and an entity location of a plurality of equipment. A data repository is accessed that includes a plurality of equipment servicing data associated with the equipment at the entity location. A map image is output on the graphical user interface including one or more icons indicating one or more equipment locations and status of the equipment based on the equipment servicing data from the data repository. One or more equipment status details are selectively displayed on the graphical user interface responsive to a detected user input action.

Wherein, in some further embodiments, the detected user input action comprises a hovering action over at least one of the one or more icons, and the one or more equipment status details are associated with a specific instance of the equipment at the entity location depicted on the map image.

Wherein, in some further embodiments, one or more display characteristics of the one or more icons vary based on the status of the equipment indicative of one or more differences in operational conditions of the equipment.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: output a health score on the graphical user interface that summarizes a plurality of conditions of the equipment at the one or more equipment locations displayed on the graphical user interface.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: output an uptime indicator on the graphical user interface that summarizes a performance history of the equipment at the one or more equipment locations displayed on the graphical user interface for a first predetermined period of time.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: output an activity history on the graphical user interface that summarizes a total number of visits, scheduled visits, predictive maintenance events, and service requests for the equipment at the one or more equipment locations displayed on the graphical user interface for a second predetermined period of time.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: output a unit summary on the graphical user interface of a plurality of units of the equipment at the one or more equipment locations displayed on the graphical user interface, wherein each of the units comprises an elevator system.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: update the graphical user interface with a plurality of unit status details based on detecting a unit selection from the plurality of units; and replace the map image on the graphical user interface with a schematic view of a plurality of components of the elevator system comprising the unit selection.

Wherein, in some further embodiments, the unit status details comprise the health score for the unit selected, the activity history for the unit selected, and one or more time history plots for the unit selected.

Wherein, in some further embodiments, the instructions when executed by the processing system cause the system to: detect a change in a zoom level of the map image on the graphical user interface; identify a plurality of entity locations of the entity within a geographic area displayed on the map image; retrieve the equipment servicing data associated with the equipment at the plurality of entity locations from the data repository; update the map image on the graphical user interface with a plurality of icons indicative of the status of the equipment at the plurality of entity locations; determine an update to a plurality of summary data associated with the equipment at the plurality of entity locations; and update one or more values displayed on the graphical user interface with the update to the summary data.

Technical effects of embodiments of the present disclosure include providing an equipment service graphical interface with a graphical user interface operable to selectively display equipment status details and resizable map images with icons indicating one or more equipment locations and status. The equipment service graphical interface can access a data repository and provide summarized results to reduce network traffic with respect to multiple monitoring access systems.

However, it should be understood that the following description and drawings are intended to be exemplary in nature and non-limiting.

Referring to <FIG>, an exemplary embodiment of an equipment service system <NUM> including a data collection system <NUM> is depicted for collecting equipment servicing data for a plurality of equipment <NUM>. The equipment <NUM> can include one or more units <NUM> with one or more equipment controllers <NUM> operable to monitor and control the units <NUM> at one or more entity locations. Each of the units <NUM> can be, for example, an elevator system, where an entity location may include multiple elevator systems (e.g., multiple single elevator car systems or multi-car elevator banks) within a same physical structure, such as a building or parking garage, or may be a campus location with multiple structures including the units <NUM>. An entity, such as company or property management group, may oversee multiple locations, such as locations <NUM>, <NUM>, that each includes multiple units <NUM> and equipment controllers <NUM>. The equipment controllers <NUM> may each include respective processors <NUM> (e.g., microprocessors), and storage mediums <NUM> that may be computer writeable and readable for controlling and monitoring operations of the units <NUM>. The equipment controllers <NUM> may establish communication through one or more communication pathways <NUM> with the data collection system <NUM>. The communication pathways <NUM> may be associated with such communication protocols as Bluetooth®, Wi-Fi, infrared, mobile broadband (e.g., <NUM>, <NUM>, etc.), satellite, and others over wired, wireless, and/or optical connections. The data collection system <NUM> may be cloud-based (i.e., in a cloud network environment). In one embodiment, the data collection system may be local to locations <NUM>, <NUM>, controllers <NUM>, and/or units <NUM> and may transmit the collected data along the communication pathways to a remote computer system, such as the cloud, equipment service graphical interface <NUM>, monitoring access systems <NUM>, or some other device.

The equipment service system <NUM> can also include one or more monitoring access systems <NUM> operable to interface with the data collection system <NUM> to retrieve equipment servicing data associated with the equipment <NUM>. The monitoring access systems <NUM> can include, for example, one or more laptop computers 50A, smartphones 50B, tablet computers 50C, and/or other electronic devices. The data collection system <NUM> can include a system <NUM> operable to provide an equipment service graphical interface <NUM> including a plurality of graphical user interfaces to the monitoring access systems <NUM> for interactively viewing and analyzing equipment servicing data associated with the equipment <NUM>. The system <NUM> can be distributed over one or more computer systems that form the data collection system <NUM>, for instance, as one or more cloud-based/networked computer systems. In the example of <FIG>, the system <NUM> includes a processing system <NUM>, a user interface driver <NUM>, and a memory system <NUM>. The user interface driver <NUM> is operable to output one or more graphical user interfaces for one or more of the monitoring access systems <NUM> and receive input through graphical user interfaces from one or more monitoring access systems <NUM>. For instance, a keypad, a touchscreen, a pointer device, or other such input device of the one or more monitoring access systems <NUM> collects user input for further processing by the system <NUM>. The memory system <NUM> includes a plurality of instructions stored thereon that, when executed by the processing system <NUM>, cause the system <NUM> to perform a plurality of operations. The processing system <NUM> may be but is not limited to a single-processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory system <NUM> may include one or more storage devices such as, for example, a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable storage medium.

In embodiments, equipment servicing data associated with the equipment <NUM> is stored in a data repository <NUM>, which may be part of the data collection system <NUM>. The data repository <NUM> is accessible by the system <NUM> and supports filtering and summarizing actions for the one or more monitoring access systems <NUM>. In embodiments, the equipment controllers <NUM>, the system <NUM>, or other elements run diagnostics and monitor the performance of the units <NUM>, with the results being stored as equipment servicing data associated with the equipment <NUM> in the data repository <NUM>. The system <NUM> selectively provides data summarizing the equipment servicing data as needed/requested through the monitoring access systems <NUM>. The equipment controllers <NUM> or other elements can push the equipment servicing data to the data repository <NUM> as events are observed associated with the units <NUM>. The data repository <NUM> can collect data for many instances of the equipment <NUM> that may not be relevant to a particular user of the monitoring access systems <NUM>. The system <NUM> can filter the equipment servicing data selected for summarizing and reporting to the monitoring access systems <NUM> to ensure that relevant data values are reported. The system <NUM> may also interface with a mapping system <NUM> operable to provide one or more map images for displaying and overlaying of icons indicative of the status of the equipment <NUM> at the plurality of entity locations <NUM>, <NUM>. The memory system <NUM> can include instructions operable to produce the equipment service graphical interface <NUM> for interactive display on the monitoring access systems <NUM>, including a plurality of graphical user interfaces as further described herein with respect to <FIG>.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> can include an information bar <NUM>, a map image <NUM>, a status data panel <NUM>, an entity <NUM>, and an entity location <NUM>. In the example of <FIG>, the information bar <NUM> can include a variety of high-level information, such as a name of the entity <NUM>, a number of buildings managed by the entity <NUM>, a number of maintenance contracts with the entity <NUM>, and other such information. Further, the information bar <NUM> can support search operations, alerts, and provide other information associated with the entity <NUM>. The map image <NUM> can graphically depict a plurality of structures, such as one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM> and one or more structures <NUM> that do not include equipment <NUM> of <FIG> managed by the entity <NUM>. In the example of <FIG>, the entity location <NUM> includes equipment <NUM> (<FIG>) at multiple equipment locations 216A, 216B, 216C, 216D as depicted graphically as one or more icons (e.g., pins) that overlay the map image <NUM>.

Further details about the equipment <NUM> may be provided on the status data panel <NUM> including unit specific information <NUM>, such as a unit specific health status, a unit identifier number, and a unit name. The unit specific health status for each unit <NUM> (<FIG>) of the equipment <NUM> at the equipment locations 216A-216D can also be graphically depicted as an icon to summarize the condition of each unit <NUM>. The display characteristics of the one or more icons can vary based on the status of the equipment <NUM> indicative of one or more differences in operational conditions of the equipment <NUM>. For instance, an "In-Service" indicator may be green while a "Shutdown" indicator may be red. Further icons that may be displayed depending on the operating conditions can include a "Trending Sick" indicator, a "Needs Attention" indicator, an "Open Service Request" indicator, and other such indicators. Status and condition of the equipment <NUM> presently visible on the map image <NUM> can be summarized on a status summary bar <NUM>. For instance, in the example of <FIG>, the status summary bar <NUM> indicates that four units <NUM> include one unit <NUM> having a status of "Shutdown" (at equipment location 216A), three units <NUM> having a status of "In-Service" (at equipment locations 216B, 216C, 216D), and no units <NUM> having a status of "Open Service Request", "Trending Sick", or "Needs Attention".

The status data panel <NUM> may also include a health score <NUM> on the graphical user interface <NUM> that summarizes a plurality of conditions of the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM>. The health score <NUM> may represent an average health status of the equipment at the entity location <NUM> (e.g., one or more structures <NUM> that include equipment <NUM>) over a predetermined period of time. For instance, if one of the units <NUM> at equipment location 216A was in a Needs Attention state for two days out of thirty days while units <NUM> at equipment locations 216B-216D remained In-Service for the same period of thirty days, then the resulting health score <NUM> may indicate <NUM>% (<NUM> healthy unit days / <NUM> total unit days). In some embodiments, the period of time for computing the health score <NUM> is configurable. In one embodiment, the health score <NUM> is an instantaneous reading of the health of the units <NUM>.

The status data panel <NUM> may also include an uptime indicator <NUM> on the graphical user interface <NUM> that summarizes a performance history of the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM> for a predetermined period of time, such as thirty days. In one embodiment, the predetermined period of time may be greater than or less than thirty days. The uptime indicator <NUM> may represent an average uptime status of the equipment at the entity location <NUM> (e.g., one or more structures <NUM> that includes equipment <NUM>) over the predetermined period of time. For instance, if one of the units <NUM> at equipment location 216A was in a Shutdown state for one day out of thirty days while units <NUM> at equipment locations 216B-216D remained In-Service for the same period of thirty days, then the resulting uptime indicator <NUM> may indicate <NUM>% (<NUM> active unit days / <NUM> total unit days). In some embodiments, the period of time for computing the uptime indicator <NUM> is configurable. The uptime indicator <NUM> may be a higher score than the health score <NUM> if the equipment <NUM> was operational but encountered one or more events that resulted in degraded operation, for example.

The status data panel <NUM> may also include an activity history <NUM> on the graphical user interface <NUM> that summarizes a total number of visits <NUM>, scheduled visits <NUM>, predictive maintenance events <NUM>, and service requests <NUM> for the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM> for a predetermined period of time. Total visits <NUM> may be indicative of a total number of service visits by a mechanic in a predetermined period of time. Scheduled visits <NUM> may be indicative of a total number of scheduled service visits (i.e., regularly scheduled maintenance appointments) by a mechanic in a predetermined period of time. Predictive visits <NUM> may be indicative of a total number of service visits made as a result of sensor data indicating a component had not yet failed but was in need of maintenance in a predetermined period of time. Service requests <NUM> may be indicative of a total number of service requests made by the customer/building owner in a predetermined period of time. The predictive maintenance events <NUM> can be flagged, for example, by one or more equipment controllers <NUM> (<FIG>) or other diagnostic/prognostic systems of the equipment service system <NUM> (<FIG>), for instance, using trending of sensor data for the equipment <NUM> and/or other techniques known in the art. The predetermined period of time for the activity history <NUM> may differ from the predetermined period of time for the health score <NUM> and/or the uptime indicator <NUM> (e.g., twelve months versus thirty days). In some embodiments, the period of time for computing the activity history <NUM> is configurable. Although a number of specific examples of status and summarized data are depicted in the example of <FIG>, it will be understood that variations include other indicators or fewer indicators are contemplated.

In some embodiments, the map image <NUM> is interactive and supports panning, zooming, rotation, and/or other actions through map controls <NUM> and/or through point/click actions, keyboard commands, or touchscreen gestures. As a field of view of the map image <NUM> is adjusted, the values of the status data panel <NUM> can be dynamically adjusted depending on whether one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM> are visible on the map image <NUM>. For instance, user requested changes to the zoom level or viewable area of the map image <NUM> may result in the system <NUM> (<FIG>) querying the mapping system <NUM> for updates to the map image <NUM> and querying the data repository <NUM> to retrieve an updated data set corresponding with any equipment locations 216A-216D having positions that are within a viewable area of the map image <NUM>. In some embodiments, the system <NUM> can buffer data for a larger area than is presently visible on the map image <NUM> to enable smoother panning or other display adjustments.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> includes the same information bar <NUM>, status data panel <NUM>, entity <NUM>, entity location <NUM>, one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM>, equipment locations 216A-216D, unit specific information <NUM>, status summary bar <NUM>, health score <NUM>, uptime indicator <NUM>, and activity history <NUM> as previously described with respect to <FIG>. A map image <NUM> of <FIG> is a zoomed-in view of the map image <NUM> of <FIG> (e.g., as selected through the map controls <NUM>). The map image <NUM> also depicts a pop-up summary <NUM> of one or more equipment status details associated with a specific instance of the equipment <NUM> at the entity location <NUM>. In the example of <FIG>, the pop-up summary <NUM> is associated with the unit <NUM> (<FIG>) at equipment location 216C. The pop-up summary <NUM> can include information such as a unit identifier number, a unit name, a number of floors/landings (e.g., when embodied as an elevator system), a unit-specific health score, a unit-specific uptime, and/or other data. The system <NUM> can output the pop-up summary <NUM> based on a detected user input action, such as a hovering action over at least one of the one or more icons on the map image <NUM>.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> is an example of updating the graphical user interface <NUM> of <FIG> with a plurality of unit status details based on detecting a unit selection from the plurality of units <NUM> (<FIG>). The graphical user interface <NUM> includes the same information bar <NUM>, entity <NUM>, and entity location <NUM> as in <FIG> and <FIG>; however, other unit-specific details are displayed. For example, an action or gesture associated with the unit <NUM> at equipment location 216C of <FIG>, which was summarized by the pop-up summary <NUM> of <FIG>, may trigger a more detailed view of the unit <NUM>. For instance, the system <NUM> may replace the map image <NUM> on the graphical user interface <NUM> of <FIG> with a schematic view <NUM> of a plurality of components <NUM> of an elevator system <NUM> comprising the unit selection in graphical user interface <NUM>. Components <NUM> can include names, operational summaries, and approximate placement information with respect to a specific model of the elevator system <NUM> at the selected location. In the context of elevators, the components <NUM> may include a machine, a car guide, a door operator, a door detection device, a microprocessor board, a drive, belts, a monitoring system, and/or other elements. The system <NUM> may also display the unit status details <NUM>, such as a health score <NUM> and uptime <NUM> for the unit selected, an activity history <NUM> for the unit selected, and one or more time history plots <NUM> for the unit selected.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> includes the same information bar <NUM>, status data panel <NUM>, entity <NUM>, entity location <NUM>, one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM>, equipment locations 216A-216D, unit specific information <NUM>, status summary bar <NUM>, health score <NUM>, uptime indicator <NUM>, and activity history <NUM> as previously described with respect to <FIG>. A map image <NUM> of <FIG> is similar to the map image <NUM> of <FIG>; however, the map image <NUM> also depicts a pop-up summary <NUM> of one or more equipment status details associated with a specific instance of the equipment <NUM> at the entity location <NUM>. In the example of <FIG>, the pop-up summary <NUM> is associated with the unit <NUM> (<FIG>) at equipment location 216A. The pop-up summary <NUM> can include information such as a unit identifier number, a unit name, a number of floors/landings (e.g., when embodied as an elevator system), a unit-specific health score, a unit-specific uptime, and/or other data. The system <NUM> can output the pop-up summary <NUM> based on a detected user input action, such as a hovering action over at least one of the one or more icons on the map image <NUM>. Notably, the pop-up summary <NUM> is an example for a unit <NUM> in an unhealthy/shutdown state.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> is an example of updating the graphical user interface <NUM> of <FIG> with a plurality of unit status details based on detecting a unit selection from the plurality of units <NUM> (<FIG>). The graphical user interface <NUM> includes the same information bar <NUM>, entity <NUM>, and entity location <NUM> as in <FIG>; however, other unit-specific details are displayed. For example, an action or gesture associated with the unit <NUM> at equipment location 216A of <FIG>, which was summarized by the pop-up summary <NUM> of <FIG>, may trigger a more detailed view of the unit <NUM>. For instance, the system <NUM> may replace the map image <NUM> on the graphical user interface <NUM> of <FIG> with a schematic view <NUM> of a plurality of components <NUM> of an elevator system <NUM> comprising the unit selection in graphical user interface <NUM>. Notably the configuration of the elevator system <NUM> differs from the configuration of the elevator system <NUM> of <FIG>. Components <NUM> can include names, operational summaries, and approximate placement information with respect to a specific model of the elevator system <NUM> at the selected location. In the context of elevators, the components <NUM> may include hoist ropes, a door operator, a counterweight, a controller, a machine/motor, a governor, and/or other elements. The system <NUM> may also display the unit status details <NUM>, such as a health score <NUM> and uptime <NUM> for the unit selected, an activity history <NUM> for the unit selected, and one or more time history plots <NUM> for the unit selected.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> includes the same information bar <NUM>, and entity <NUM> of <FIG> after using the map controls <NUM> to perform a zoom-out operation resulting in a change in map area covered in a map image <NUM> as compared to the map image <NUM> of <FIG>. The map image <NUM> covers a plurality of entity locations <NUM>, which may be in different towns/states/provinces/countries as graphically depicted as icons or pins. A status data panel <NUM> of the graphical user interface <NUM> can include financial information <NUM>, a status summary bar <NUM>, a health score <NUM>, an uptime indicator <NUM>, an activity history <NUM>, and other such information associated with the equipment <NUM> at the entity locations <NUM> depicted in the map image <NUM>. In the example of <FIG>, the map image <NUM> also depicts a pop-up summary <NUM> of one or more equipment status details associated with the equipment <NUM> at a selected instance of an entity location <NUM>. The pop-up summary <NUM> can include, for example, an entity name, a building name, a contract number, a number of units at the building, a number of open service requests, a number of shutdown units, a number of in-service units, a number of trending sick units, a number of units needing attention and/or other values.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> includes a similar format as previously described with respect to the graphical user interface <NUM> of <FIG>, such as the information bar <NUM>, status data panel <NUM>, entity <NUM>, entity location <NUM>, one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM>, equipment locations 816A-816D, unit specific information <NUM>, status summary bar <NUM>, health score <NUM>, uptime indicator <NUM>, and activity history <NUM>. A map image <NUM> of <FIG> depicts a different physical location, where the one or more structures <NUM> are at different geographic locations than the one or more structures <NUM> of <FIG>. In the example of <FIG>, units <NUM> (<FIG>) at equipment locations 816A and 816D have a status of "In-Service" and units <NUM> at equipment locations 816B and 816C have a status of "Trending Sick".

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> includes a similar format as previously described with respect to the graphical user interface <NUM> of <FIG>, such as the information bar <NUM>, status data panel <NUM>, entity <NUM>, entity location <NUM>, one or more structures <NUM> that include equipment <NUM> of <FIG> managed by the entity <NUM>, equipment locations 816A-816D, unit specific information <NUM>, status summary bar <NUM>, health score <NUM>, uptime indicator <NUM>, and activity history <NUM>. A map image <NUM> the graphical user interface <NUM> of <FIG> also depicts a pop-up summary <NUM> of one or more equipment status details associated with a specific instance of the equipment <NUM> at the entity location <NUM>. In the example of <FIG>, the pop-up summary <NUM> is associated with the unit <NUM> (<FIG>) at equipment location 816C. The pop-up summary <NUM> can include information such as a unit identifier number, a unit name, a number of floors/landings (e.g., when embodied as an elevator system), a unit-specific health score, a unit-specific uptime, and/or other data. The system <NUM> can output the pop-up summary <NUM> based on a detected user input action, such as a hovering action over at least one of the one or more icons on the map image <NUM>.

<FIG> depicts an example of a graphical user interface <NUM> of the equipment service graphical interface <NUM> of <FIG> that can be generated by the system <NUM> for the monitoring access systems <NUM> of <FIG>. The graphical user interface <NUM> is an example of updating the graphical user interface <NUM> of <FIG> with a plurality of unit status details based on detecting a unit selection from the plurality of units <NUM> (<FIG>). The graphical user interface <NUM> includes the same information bar <NUM>, entity <NUM>, and entity location <NUM> as in <FIG>; however, other unit-specific details are displayed. For example, an action or gesture associated with the unit <NUM> at equipment location 816C of <FIG>, which was summarized by the pop-up summary <NUM> of <FIG>, may trigger a more detailed view of the unit <NUM>. For instance, the system <NUM> may replace the map image <NUM> on the graphical user interface <NUM> of <FIG> with a schematic view <NUM> of a plurality of components <NUM> of an elevator system <NUM> comprising the unit selection in graphical user interface <NUM>. Notably the configuration of the elevator system <NUM> may differ from the configuration of the elevator system <NUM> of <FIG>, for example. Components <NUM> can include names, operational summaries, and approximate placement information with respect to a specific model of the elevator system <NUM> at the selected location. In the context of elevators, the components <NUM> may include hoist ropes, a door operator, a counterweight, a controller, a machine/motor, a governor, and/or other elements. The system <NUM> may also display the unit status details <NUM>, such as a health score <NUM> and uptime <NUM> for the unit selected, an activity history <NUM> for the unit selected, and one or more time history plots <NUM> for the unit selected.

<FIG> depicts a process <NUM> that can be performed by the system <NUM> of <FIG> as shown and described herein and/or by variations thereon. Various aspects of the process <NUM> can be carried out using one or more sensors, one or more processors, and/or one or more machines and/or controllers. For example, some aspects of the flow process involve sensors (e.g., accelerometers, speed sensors, position sensors, temperature sensors, strain gauges, torque sensors, cameras, etc.), as described above, in communication with a processor or other control device and transmission of detected information thereto. The process <NUM> is described in reference to <FIG>. The process <NUM> can be invoked through one or more monitoring access systems <NUM> using, for example, the equipment service graphical interface <NUM> of <FIG>. For purposes of explanation, the process <NUM> is primarily described with respect to the examples of <FIG> but is applicable to the examples of <FIG> and other embodiments as well.

At block <NUM>, the system <NUM> identifies an entity <NUM> and an entity location <NUM> of a plurality of equipment <NUM>. At block <NUM>, the system <NUM> accesses a data repository <NUM> including a plurality of equipment servicing data associated with the equipment <NUM> at the entity location <NUM>.

At block <NUM>, the system <NUM> outputs a map image <NUM> on the graphical user interface <NUM> including one or more icons indicating one or more equipment locations 216A-216D and status of the equipment <NUM> based on the equipment servicing data from the data repository <NUM>. One or more display characteristics of the one or more icons can vary based on the status of the equipment <NUM> indicative of one or more differences in operational conditions of the equipment <NUM>. Differences in display characteristics can include variations in color, shape, flashing, animation, and/or other distinguishing properties.

At block <NUM>, the system <NUM> can selectively display one or more equipment status details on the graphical user interface <NUM> responsive to a detected user input action. The detected user input action can include a hovering action over at least one of the one or more icons. The one or more equipment status details can be associated with a specific instance of the equipment <NUM> at the entity location depicted on the map image <NUM>, such as displaying the pop-up summary <NUM>.

In some embodiments, the system <NUM> can output a health score <NUM> on the graphical user interface <NUM> that summarizes a plurality of conditions of the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM>. The system <NUM> can output an uptime indicator <NUM> on the graphical user interface <NUM> that summarizes a performance history of the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM> for a first predetermined period of time. The system <NUM> can output an activity history <NUM> on the graphical user interface <NUM> that summarizes a total number of visits <NUM>, scheduled visits <NUM>, predictive maintenance events <NUM>, and service requests <NUM> for the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM> for a second predetermined period of time. The system <NUM> can output a unit summary (e.g., unit specific information <NUM> and/or status summary bar <NUM>) on the graphical user interface <NUM> of a plurality of units <NUM> of the equipment <NUM> at the one or more equipment locations 216A-216D displayed on the graphical user interface <NUM>, where each of the units <NUM> may be an elevator or escalator system.

The system <NUM> can update the graphical user interface <NUM> with a plurality of unit status details <NUM> based on detecting a unit selection from the plurality of units <NUM>. For example, the system <NUM> can replace the map image <NUM> on the graphical user interface <NUM> with a schematic view <NUM> of a plurality of components <NUM> of an elevator system <NUM> comprising the unit selection. The unit status details <NUM> may include a health score <NUM> for the unit selected, an uptime for the unit selected, the activity history <NUM> for the unit selected, and/or one or more time history plots <NUM> for the unit selected.

In some embodiments, the system <NUM> can detect a change in a zoom level of the map image <NUM> on the graphical user interface <NUM>, for example, through the map controls <NUM>. The system <NUM> can identify a plurality of entity locations <NUM> of the entity <NUM> within a geographic area displayed on the map image <NUM>. The system <NUM> may retrieve the equipment servicing data associated with the equipment <NUM> at the plurality of entity locations <NUM> from the data repository <NUM>. The system <NUM> can update the map image <NUM> on the graphical user interface <NUM> with a plurality of icons indicative of the status of the equipment <NUM> at the plurality of entity locations <NUM>. The system <NUM> can determine an update to a plurality of summary data associated with the equipment <NUM> at the plurality of entity locations <NUM>. The system <NUM> may update one or more values displayed on the graphical user interface <NUM> with the update to the summary data.

Although described with a particular sequence of steps, it will be understood that the process <NUM> of <FIG> can be performed in an alternate order and include a greater or fewer number of steps.

The various functions described above may be implemented or supported by a computer program that is formed from computer readable program codes and that is embodied in a computer readable medium. Computer readable program codes may include source codes, object codes, executable codes, and others. Computer readable mediums may be any type of media capable of being accessed by a computer, and may include Read Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or other forms.

Claim 1:
A method (<NUM>) comprising:
identifying an entity (<NUM>) and an entity location (<NUM>, <NUM>; <NUM>; <NUM>; <NUM>) of a plurality of equipment (<NUM>);
accessing a data repository (<NUM>) comprising a plurality of equipment servicing data associated with the equipment (<NUM>; <NUM>) at the entity location (<NUM>, <NUM>; <NUM>; <NUM>; <NUM>); and
outputting a map image (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) on a graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) comprising one or more icons indicating one or more equipment locations (216A, 216B, 216C, 216D) and status of the equipment based on the equipment servicing data from the data repository;
selectively displaying one or more equipment status details on the graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) responsive to a detected user input action;
outputting a unit summary (<NUM>, <NUM>) on the graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) of a plurality of units (<NUM>) of the equipment (<NUM>) at the one or more equipment locations (216A, 216B, 216C, 216D) displayed on the graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>), wherein each of the units (<NUM>) comprises an elevator system (<NUM>; <NUM>; <NUM>);
updating the graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) with a plurality of unit status details (<NUM>; <NUM>; <NUM>) based on detecting a unit selection from the plurality of units (<NUM>);
and replacing the map image (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) on the graphical user interface (<NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>; <NUM>) with a schematic view (<NUM>) of a plurality of components (<NUM>; <NUM>; <NUM>) of the elevator system (<NUM>; <NUM>; <NUM>) comprising the unit selection.