|
(11) | EP 3 398 895 B1 |
| (12) | EUROPEAN PATENT SPECIFICATION |
|
|
| (54) |
PASSENGER-INITIATED DYNAMIC ELEVATOR SERVICE REQUEST VOM FAHRGAST INITIIERTE DYNAMISCHE DIENSTANFORDERUNG DEMANDE DE SERVICE D'ASCENSEUR DYNAMIQUE INITIÉE PAR UN PASSAGER |
|
|
|||||||||||||||||||||||||||||||
| Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). |
BACKGROUND
[0001] The subject matter disclosed herein generally relates to the field of elevator system maintenance, and more particularly to a system that facilitates system maintenance through interaction with a mobile device.
[0002] Existing elevator systems require elevator users to call a central service center when entering an elevator service request. Elevator users often do not know who to call, when to call, what to report, and fail to correctly identify the elevator error and time of the error.
[0003] WO 2014/200457 A1 discloses a method including receiving, from a portable recording device, multiple recordings of sounds made by an elevator, analyzing the recording to detect changes in elevator operation over time and generating a notification to perform an action on an elevator.
[0004] BR 102013026552-7 A2 discloses a system for remote maintenance of an elevator using a mobile phone, in which an elevator maintenance worker connects with the system through a mobile phone.
[0005] WO 2009/150251 A2 discloses an elevator system and a method for servicing such an elevator system. The elevator system comprises at least one door and at least one acceleration sensor mounted on the door.
BRIEF SUMMARY
[0006] According to the invention a method of interacting with an elevator system as claimed in claim 1 is provided.
[0007] Further embodiments of the method may include: receiving maintenance data; determining a maintenance task in response to at least one of the maintenance data and the maintenance issue; and transmitting the maintenance task to a maintenance device.
[0008] Further embodiments of the method may include activating an alarm on the maintenance device when the maintenance issue is received.
[0009] Futher emobodiments of the method may include determining a time of the issue report in response to at least one of the issue report and the performance data.
[0010] Further embodiments of the method may include determining that maintenance issue is a duplicate maintenance issue; and transmitting an alert to the user mobile device indicating the duplicate maintenance issue.
[0011] Further embodiments of the method may include: determining that maintenance issue is a duplicate maintenance issue; and transmitting an alert to the user mobile device indicating the duplicate maintenance issue.
[0012] Further embodiments of the method may include the issue report may be entered via a verbal input from a user of the user mobile device.
[0013] Further embodiments of the method may include where the issue report may be entered via selection of predefined options on a drop-down menu.
[0014] Further embodiments of the method may include where the predefined options may be selected via a verbal command.
[0015] Further embodiments of the method may include: detecting a location of the user mobile device; and determining an elevator car that triggered the issue report in response to at least one of the issue report and the location of the user mobile device.
[0016] Further embodiments of the method may include: detecting a location of the user mobile device; and determining an elevator car that triggered the issue report in response to at least one of the issue report and the location of the user mobile device.
[0017] Further embodiments of the method may include: generating on a user interface a service and maintenance screen on the user mobile device; and displaying at least one maintenance issue on the service and maintenance screen.
[0018] Further embodiments of the method may include: displaying at least one maintenance issue on the service and maintenance screen.
[0019] Further embodiments of the method may include: generating on a user interface a service and maintenance screen on the maintenance device; and displaying at least one maintenance issue on the service and maintenance screen.
[0020] Further embodiments of the method may include: receiving from the maintenance device an indication of completion of a maintenance task; and updating the maintenance database to include completion of the maintenance task.
[0021] Further embodiments of the method may include where the maintenance device is a mobile device.
[0022] Technical effects of embodiments of the present disclosure include the ability for an elevator user to report an issue with an elevator system via a mobile device.
[0023] The foregoing features and elements may be combined in various combinations within the scope of the appended claims. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be understood, however, that the following description and drawings are intended to be illustrative and explanatory in nature and non-limiting.
BRIEF DESCRIPTION
[0024] The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:
FIG. 1 illustrates a schematic view of a building system, in accordance with an embodiment of the disclosure;
FIG. 2 depicts a user interface on a mobile device, in accordance with an embodiment of the disclosure;
FIG. 3 depicts a user interface on a mobile device, in accordance with an embodiment of the disclosure; and
FIG. 4 is a flow diagram illustrating a method of interacting with an elevator system, according to an embodiment of the present disclosure.
DETAILED DESCRIPTION
[0025] A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.
[0026] FIG. 1 depicts an elevator maintenance management system 200 in an example embodiment. The elevator maintenance management system 200 includes an elevator system 204 installed at a building 202. In some embodiments, the building 202 may be a building or a collection of buildings that may or may not be physically located near each other. The building 202 may include any number of floors. Persons entering the building 202 may enter at a lobby floor, or any other floor, and may go to a destination floor via one or more conveyance devices, such as the elevator system 204.
[0027] The elevator system 204 may be operably connected to one or more computing devices, such as a controller 206. The controller 206 may be configured to control dispatching operations for one or more elevator cars (e.g., elevator cars 204-1, 204-2 ... 204-n) associated with the elevator system 204. It is understood that the elevator system 204 may utilize more than one controller 206, and that each controller may control a group of elevators cars 204-1 and 204-2. Although two elevator cars 204-1 and 204-2 are shown in FIG. 1, it is understood that any number of elevators cars 204-n may be used in the elevator system 204. The elevator cars 204-1 and 204-2 may be located in the same hoistway or in different hoistways so as to allow coordination amongst elevator cars 204-1 and 204-2 in different elevator banks serving different floors. It is understood that other components of the elevator system 204 (e.g., drive, counterweight, safeties, etc.) are not depicted for ease of illustration.
[0028] The controller 206 may include a processor 260, memory 262 and communication module 264 as shown in FIG. 1. The processor 260 can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 262 is an example of a non-transitory computer readable storage medium tangibly embodied in the controller 206 including executable instructions stored therein, for instance, as firmware. The communication module 264 may implement one or more communication protocols as described in further detail herein.
[0029] The elevator system 204 includes a sensor system 205 having one or more sensors (e.g., 205-1, 205-2,..205-n). Although two sensors 205-1 and 205-2 are shown in FIG. 1, it is understood that any number of sensors 205-n may be used in the sensor system 205. The controller 206 is coupled to the sensor system 205. The sensor system 205 may include one or more sensors (e.g., 205-1, 205-2,..205-n). The sensor system 205 may include a variety of different types of sensors (e.g., 205-1, 205-2,..205-n). The sensor system 205 captures performance and/or other operational data 325 of the elevator system 204. The performance data 325 indicates performance parameters of the elevator system 204, such as for example, location, speed, voltage, vibration, acceleration, noise, , jerk, and any other performance parameter of any component of the elevator system 204 known to one of skill in the art.
[0030] Other sensors (e.g., 205-1, 205-2,..205-n) in the sensor system may include cameras, people counters, microphones, etc. to capture information relevant to the usage of the elevator system 205. Thus, the type and nature of sensors (e.g., 205-1, 205-2,..205-n) within the sensor system 205 is not limited to the embodiments disclosed herein. The sensor system 205 collects performance data 325 regarding each elevator car (e.g., 204-1, 204-2,..204-n) that may be stored in a maintenance database 263 operatively connected to the controller 206 or stored within the controller 206. In one embodiment, the performance data may be stored on a building computer, remotely in the cloud, or on any other electronic storage medium.
[0031] Also shown in FIG. 1 is a user mobile device 208a. The user mobile device 208a may include a device that is typically carried by a person, such as a phone, PDA, smart watch, tablet, laptop, etc. The user mobile device 208a may include a processor 250a, memory 252a and communication module 254a as shown in FIG. 1. The processor 250a can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 252a is an example of a non-transitory computer readable storage medium tangibly embodied in the user mobile device 208a including executable instructions stored therein, for instance, as firmware. The communication module 254a may implement one or more communication protocols as described in further detail herein. In a non-limiting example, the user mobile device 208a may belong to a resident of the building 202 or an employee who works in the building 202.
[0032] Also shown in FIG. 1 is a maintenance device 208b. The maintenance device 208b may be a computing device such as a desktop computer. The maintenance device 208b may also be a mobile computing device that is typically carried by a person, such as, for example a phone, PDA, smart watch, tablet, laptop, etc. The maintenance device 208b may include a processor 250b, memory 252b and communication module 254b as shown in FIG. 1. The processor 250b can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 252b is an example of a non-transitory computer readable storage medium tangibly embodied in the maintenance device 208b including executable instructions stored therein, for instance, as firmware. The communication module 254b may implement one or more communication protocols as described in further detail herein. The maintenance device 208b belongs to a maintenance worker of the building 202, such as, for example, maintenance personnel, building maintenance manager, and elevator service repair person.
[0033] The user mobile device 208a and maintenance device 208b may both be referred to as a device 208 for ease of explanation. The device 208 and the controller 206 communicate with one another. For example, the device 208 and the controller 206 may communicate with one another when proximate to one another (e.g., within a threshold distance). The device 208 and the controller 206 may communicate over a wireless network, such as 802.11x (WiFi), short-range radio (Bluetooth), cellular, satellite, etc. In some embodiments, the controller 206 may include, or be associated with (e.g., communicatively coupled to) a networked element, such as kiosk, beacon, hall call fixture, lantern, bridge, router, network node, door lock, elevator control panel, building intercom system, etc. The networked element may communicate with the device 208 using one or more communication protocols or standards. For example, the networked element may communicate with the device 208 using near field communications (NFC). In other embodiments, the controller 206 may establish communication with a device 208 that is outside of the building 202. This connection may be established with various technologies including GPS, triangulation, or signal strength detection, by way of non-limiting example. In example embodiments, the device 208 communicates with the controller 206 over multiple independent wired and/or wireless networks. Embodiments are intended to cover a wide variety of types of communication between the device 208 and controller 206, and embodiments are not limited to the examples provided in this disclosure. Communication between the device 208 and the controller 206 will allow the controller 206 to determine the location of the device 208 in relation to the elevator system 204 and/or the door system 205. Knowing the relative location of the device 208 will allow the controller 206 to determine what elevator car (e.g., 204-1, 204-2,..204-n) may have caused a user to submit a maintenance request.
[0034] Embodiments generate a user interface on the device 208 through a maintenance application 255a, 255b. The maintenance application 255a may be used for user of the elevator system to report maintenance issues regarding the elevator system 204 in an issue report 302. For example, a resident may report that they heard a squeaking in elevator car 204-1.
[0035] FIGs. 2-3 depict an example user interface 300 on user mobile device 208a. Referring to FIGs. 2-3 with continued reference to FIG. 1, when the user mobile device 208a launches the maintenance application 255a, an elevator service and maintenance screen 301 may be presented as shown in FIG. 2. The maintenance application 255a may display an elevator alert 305 and an elevator notice 307. The elevator alert 305 may indicate maintenance issues 327 that have been reported in the elevator system 204. The elevator notices 307 may indicate scheduled maintenance on the elevator system 204.
[0036] In order to report an issue with the elevator system 204, a user can select the "Report an Issue" 303 button, which will prompt the user interface 300 to generate the maintenance screen 301 shown in FIG. 3. As seen in FIG. 3, the service and maintenance screen 301 includes a text input section 304 where an issue with the elevator system 204 may be reported. In an embodiment, the issue report 302 may be manually typed into a text input section 304 by a user of the user mobile device 208a. The text input section 304 is not intended to be limiting as other data input methods may be used, such as, for example drop-down menus or icons to display multiple predefined issue options. The drop-down menus or icons may include issue options for elevator cars and may be categorized with submenu to guide a user in selecting the appropriate issue. The issue options may be a static list of issues and/or dynamic list of issues built using commonly reported issues within the building itself. In an embodiment, the issue report 302 may be entered via selection of predefined issue options on the drop-down menu. In an embodiment, the predefined options may be selected via a verbal command. In another embodiment, the issue report 302 may be entered via a verbal input from a user of the user mobile device 208a. The user mobile device 208a may also contain an accelerometer (not shown) located within the user mobile device 208a and configured to collect accelerometer data. In another embodiment, the issue report 302 is generated in response to the accelerometer data. For example, if the accelerometer detects an unusual jerk of the elevator car (e.g, 204-1, 204-2,..204-n) then an issue report 302 may be automatically generated by the maintenance application 255a detailing the jerk
[0037] Also, included on the service and maintenance screen 301 is a date entry block 306 where the date that the issue occurred may be entered by the user of the user mobile device 208a. In one embodiment, the date and tome of the report may be automatically entered and/or stored by the maintenance application 255a. Additionally, the service and maintenance screen 301 may include a known issues section 308 to display issues with the elevator system 204 that are known and are currently being worked. Advantageously, a known issue section 308 will help avoid duplicity in issue reports 302 that results in wasted time for both the user and the maintenance personnel. Once a user of the user mobile device has completed entry of their issue in the text input section 304, the user may select a "Send to Maintenance" button 310 to transmit the issue report 302 to the controller 206 and eventually maintenance personnel who may view the issue on the maintenance device 208b.
[0038] Referring now to FIG. 4, while referencing components of FIGs. 1-3. FIG. 4 shows a flow chart of method 400 of interacting with an elevator system, in accordance with an embodiment of the disclosure. At block 404, a sensor system 205 detects performance data 325 for an elevator system 204. The elevator system 204 may include one or more elevator cars (e.g, 204-1, 204-2,..204-n). The sensor system 205 may include one or more sensors (e.g, 205-1, 205-2,..205-n). The performance data 325 indicates performance parameters of the elevator system 204, such as for example, location, speed, voltage, vibration, acceleration, noise, deceleration, jerk, and any other performance parameter of any component of the elevator system 204 known to one of skill in the art. Abnormalities in the performance data 325 may indicate a need for maintenance and issue reports 302 from users of the elevator system 204 may confirm the need for maintenance. In an embodiment, the sensor system 205 collects performance data 325 continuously. In another embodiment, the sensor system 205 collects performance data 325 at predefined intervals and/or when an issue report 302 is received.
[0039] At block 406, the controller 206 receives an issue report 302 from a user mobile device 208a. As mentioned above, generated on a user interface 300 is a service and maintenance screen 301 on the user mobile device 208a. The service and maintenance screen 301 is configured to allow entry of the issue report 302. In an embodiment, the issue report 302 may be manually typed into a text input section 304. In another embodiment, the issue report 302 may be entered via a verbal input from a user of the user mobile device 208a. The user mobile device 208a may also contain an accelerometer (not shown) located within the user mobile device 208a and configured to collect accelerometer data. In another embodiment, the issue report 302 is generated in response to the accelerometer data. For example, if the accelerometer detects an unusual jerk of the elevator car (e.g, 204-1, 204-2,..204-n) then an issue report 302 may automatically be generated by the maintenance application 255a detailing the jerk.
[0040] At block 408, the controller 206 determines a maintenance issue 327 of the elevator system 204 in response to at least one of the issue report 302 and the performance data 325. For example, the maintenance issue 327 may be that the guide wheel of an elevator car is squeaking. The controller 206 may also determine a maintenance task in response to at least one of the maintenance data 326 and the maintenance issue 327. The maintenance task may be transmitted to a maintenance device 208b. In an example, the maintenance task may be add a lubricant to guide wheels of the elevator car to decrease squeaking. The controller 206 may also receive maintenance data from a maintenance device 208b. For example, after maintenance personnel has performed a maintenance activity on the elevator system 204, the maintenance data 326 may be entered in to the maintenance application 255b on the maintenance device 208b and sent to the controller 206 to be stored in the maintenance database 363.
[0041] In an embodiment, the controller 206 may also determine a time of the issue report 302 in response to at least one of the issue report 302 and the performance data 325. In one example, the controller 206 correlates the issue report 302 with performance data 325 in order to determine a time of the issue report 302. In another example, a location of the user mobile device 208a may be tracked in order to determine what elevator car (e.g, 204-1, 204-2,..204-n) the user mobile device 208a has entered and at what time, thus performance data 325 at that same time and elevator car (e.g, 204-1, 204-2,..204-n) may determine the maintenance issue 327. In another embodiment, the controller 206 may also determine that the maintenance issue 327 is a duplicate maintenance issue, meaning that the maintenance issue 327 has already been reported by another issue report 302. If the maintenance issue 327 is a duplicate maintenance issue, then an alert to the user mobile device 208a indicating the duplicate maintenance issue.
[0042] At block 410, the controller 206 transmits the maintenance issue 327 to a maintenance device 208b. In an embodiment, an alarm is activated on the maintenance device 208b when the maintenance issue is received. The alarm may also be sent to a central computer/cloud, a maintenance dispatcher and/or the building owner. The alarm may be audible and/or visual. Generated on a user interface 300 is a service and maintenance screen 301 on the maintenance device 208b. The service and maintenance screen 301 being configured to display at least one maintenance issue 327 on the maintenance device 208b. Further, the maintenance issue 327 may also be sent to the user mobile device 208a. Generated on a user interface 300 is a service and maintenance screen 301 on the user mobile device 208a. The service and maintenance screen 301 being configured to display at least one maintenance issue 327 on the maintenance device 208b.
[0043] While the above description has described the flow process of FIG. 4 in a particular order, it should be appreciated that unless otherwise specifically required in the attached claims that the ordering of the steps may be varied.
[0044] As described above, embodiments can be in the form of processor-implemented processes and devices for practicing those processes, such as a processor. Embodiments can also be in the form of computer program code containing instructions embodied in tangible media, such as network cloud storage, SD cards, flash drives, floppy diskettes, CD ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the embodiments. Embodiments can also be in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes an device for practicing the embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
[0045] The term "about" is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, "about" can include a range of ± 8% or 5%, or 2% of a given value.
[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.
detecting, using the sensor system (205), performance data (325) for the elevator system (204), the elevator system (204) including one or more elevator cars;
generating on a user interface a service and maintenance screen (301) on a user mobile device (208a), through a maintenance application (255a, 255) for a user of the elevator system to report maintenance issues regarding the elevator system (204) in an issue report (302), and entering the issue report on the service and maintenance screen (301), or
collecting accelerometer data using an accelerometer located in the user mobile device (208a) and generating an issue report in response to the accelerometer data;
a controller (206) receiving the issue report from the user mobile device (208a);
the controller (206) determining a maintenance issue of the elevator system (204) in response to at least one of the issue report and the performance data (325); and
the controller (206) transmitting the maintenance issue to a maintenance device (208b) belonging to a maintenance worker of the elevator system.
the controller receiving maintenance data;
the controller (206) determining a maintenance task in response to at least one of the maintenance data and the maintenance issue; and
the controller (206) transmitting the maintenance task to the maintenance device (208b).
activating an alarm on the maintenance device (208b) when the maintenance issue is received.
determining a time of the issue report in response to at least one of the issue report and the performance data (325).
determining that maintenance issue is a duplicate maintenance issue; and
transmitting an alert to the user mobile device (208a) indicating the duplicate maintenance issue.
displaying at least one maintenance issue on the service and maintenance screen (301).
the issue report may be entered via a verbal input from a user of the user mobile device (208a), and/or wherein, optionally:
the issue report may be entered via selection of predefined options on a drop-down menu, wherein, optionally:
the predefined options may be selected via a verbal command.
detecting a location of the user mobile device (208a); and
determining an elevator car that triggered the issue report in response to at least one of the issue report and the location of the user mobile device (208a).
detecting a location of the user mobile device (208a); and
determining an elevator car that triggered the issue report in response to at least one of the issue report and the location of the user mobile device (208a).
generating on a user interface a service and maintenance screen (301) on the user mobile device (208a); and
displaying at least one maintenance issue on the service and maintenance screen (301).
generating on a user interface a service and maintenance screen (301) on the maintenance device (208b); and
displaying at least one maintenance issue on the service and maintenance screen (301).
receiving from the maintenance device (208b) an indication of completion of a maintenance task; and
updating the maintenance database to include completion of the maintenance task.
the maintenance device (208b) is a mobile device.
Detektieren von Leistungsdaten (325) für das Aufzugsystem (204) unter Verwendung des Sensorsystems (205), wobei das Aufzugsystem (204) eine oder mehrere Aufzugskabinen beinhaltet;
Generieren, an einer Benutzerschnittstelle, eines Dienst- und Wartungsbildschirms (301) auf einer mobilen Benutzervorrichtung (208a) durch eine Wartungsanwendung (255a, 255), damit ein Benutzer des Aufzugsystems Wartungsprobleme bezüglich des Aufzugsystems (204) in einem Problembericht (302) melden kann, und Eingeben des Problemberichts auf dem Dienst- und Wartungsbildschirm (301), oder
Sammeln von Daten des Beschleunigungsmessers unter Verwendung eines Beschleunigungsmessers, der sich in der mobilen Benutzervorrichtung (208a) befindet, und Generieren eines Problemberichts als Reaktion auf die Daten des Beschleunigungsmessers;
eine Steuerung (206), die den Problembericht von der mobilen Benutzervorrichtung (208a) empfängt;
wobei die Steuerung (206) ein Wartungsproblem des Aufzugsystems (204) als Reaktion auf mindestens einen des Problemberichts und der Leistungsdaten (325) bestimmt; und
wobei die Steuerung (206) das Wartungsproblem an eine Wartungsvorrichtung (208b) überträgt, die zu einem Wartungsarbeiter des Aufzugsystems gehört.
wobei die Steuerung Wartungsdaten empfängt;
wobei die Steuerung (206) eine Wartungsaufgabe als Reaktion auf mindestens eines der Wartungsdaten und des Wartungsproblems bestimmt; und
wobei die Steuerung (206) die Wartungsaufgabe an die Wartungsvorrichtung (208b) überträgt.
Aktivieren eines Alarms an der Wartungsvorrichtung (208b), wenn das Wartungsproblem empfangen wird.
Bestimmen eines Zeitpunkts des Problemberichts als Reaktion auf mindestens eines des Problemberichts und der Leistungsdaten (325).
Bestimmen, dass das Wartungsproblem ein Problem mit doppelter Wartung ist; und
Senden einer Warnung an die mobile Benutzervorrichtung (208a), die auf das Problem mit doppelter Wartung hinweist.
Anzeigen mindestens eines Wartungsproblems auf dem Dienst- und Wartungsbildschirm (301).
der Problembericht über eine verbale Eingabe von einem Benutzer der mobilen Benutzervorrichtung (208a) eingegeben werden kann, und/oder wobei optional:
der Problembericht über eine Auswahl vordefinierter Optionen aus einem Dropdown-Menü eingegeben werden kann, wobei optional:
die vordefinierten Optionen über einen verbalen Befehl ausgewählt werden können.
Detektieren eines Standorts der mobilen Benutzervorrichtung (208a); und
Bestimmen einer Aufzugskabine, die den Problembericht ausgelöst hat, als Reaktion auf mindestens eines des Problemberichts und des Standorts der mobilen Benutzervorrichtung (208a).
Detektieren eines Standorts der mobilen Benutzervorrichtung (208a); und
Bestimmen einer Aufzugskabine, die den Problembericht ausgelöst hat, als Reaktion auf mindestens eines des Problemberichts und des Standorts der mobilen Benutzervorrichtung (208a).
Generieren, an einer Benutzerschnittstelle, eines Dienst- und Wartungsbildschirms (301) auf der mobilen Benutzervorrichtung (208a); und
Anzeigen mindestens eines Wartungsproblems auf dem Dienst- und Wartungsbildschirm (301).
Generieren, an einer Benutzerschnittstelle, eines Dienst- und Wartungsbildschirms (301) auf der Wartungsvorrichtung (208b); und
Anzeigen mindestens eines Wartungsproblems auf dem Dienst- und Wartungsbildschirm (301).
Empfangen eines Hinweises über den Abschluss einer Wartungsaufgabe von der Wartungsvorrichtung (208b); und
Aktualisieren der Wartungsdatenbank, um den Abschluss der Wartungsaufgabe einzuschließen.
die Wartungsvorrichtung (208b) eine mobile Vorrichtung ist.
la détection, à l'aide du système de capteurs (205), de données de performance (325) pour le système d'ascenseur (204), le système d'ascenseur (204) comprenant une ou plusieurs cabines d'ascenseur ;
la génération, sur une interface utilisateur, d'un écran de service et de maintenance (301) sur un dispositif mobile d'utilisateur (208a), par l'intermédiaire d'une application de maintenance (255a, 255), pour qu'un utilisateur du système d'ascenseur signale des problèmes de maintenance concernant le système d'ascenseur (204) dans un rapport de problème (302), et la saisie du rapport de problème sur l'écran de service et de maintenance (301) ; ou
la collecte de données d'accéléromètre à l'aide d'un accéléromètre situé dans le dispositif mobile de l'utilisateur (208a) et la génération d'un rapport de problème en réponse aux données d'accéléromètre ;
un contrôleur (206) recevant le rapport de problème provenant du dispositif mobile de l'utilisateur (208a) ;
le contrôleur (206) déterminant un problème de maintenance du système d'ascenseur (204) en réponse à au moins l'un du rapport de problème et des données de performance (325) ; et
le contrôleur (206) transmettant le problème de maintenance à un dispositif de maintenance (208b) appartenant à un ouvrier de maintenance du système d'ascenseur.
le contrôleur recevant des données de maintenance ;
le contrôleur (206) déterminant une tâche de maintenance en réponse à au moins l'une des données de maintenance et du problème de maintenance ; et
le contrôleur (206) transmettant la tâche de maintenance au dispositif de maintenance (208b).
l'activation d'une alarme sur le dispositif de maintenance (208b) lorsque le problème de maintenance est reçu.
la détermination d'une heure du rapport de problème en réponse à au moins l'un du rapport de problème et des données de performance (325).
la détermination qu'un problème de maintenance est un problème de maintenance en double ; et
la transmission d'une alerte au dispositif mobile de l'utilisateur (208a) indiquant le problème de maintenance en double.
l'affichage d'au moins un problème de maintenance sur l'écran de service et de maintenance (301).
le rapport de problème peut être saisi par l'intermédiaire d'une entrée verbale d'un utilisateur du dispositif mobile de l'utilisateur (208a), et/ou dans lequel, facultativement :
le rapport de problème peut être saisi par la sélection d'options prédéfinies dans un menu déroulant ; dans lequel, facultativement :
les options prédéfinies peuvent être sélectionnées par l'intermédiaire d'une commande verbale.
la détection d'un emplacement du dispositif mobile de l'utilisateur (208a) ; et
la détermination d'une cabine d'ascenseur qui a déclenché le rapport de problème en réponse à au moins l'un du rapport de problème et de l'emplacement du dispositif mobile de l'utilisateur (208a).
détecter un emplacement du dispositif mobile de l'utilisateur (208a) ; et
déterminer une cabine d'ascenseur qui a déclenché le rapport de problème en réponse à au moins l'un du rapport de problème et de l'emplacement du dispositif mobile de l'utilisateur (208a).
la génération, sur une interface utilisateur, d'un écran de service et de maintenance (301) sur le dispositif mobile de l'utilisateur (208a) ; et
l'affichage d'au moins un problème de maintenance sur l'écran de service et de maintenance (301).
la génération, sur une interface utilisateur, d'un écran de service et de maintenance (301) sur le dispositif mobile de l'utilisateur (208b) ; et
l'affichage d'au moins un problème de maintenance sur l'écran de service et de maintenance (301).
la réception, en provenance du dispositif de maintenance (208b), d'une indication d'achèvement d'une tâche de maintenance ; et
la mise à jour de la base de données de maintenance pour inclure l'achèvement de la tâche de maintenance.
le dispositif de maintenance (208b) est un dispositif mobile.
REFERENCES CITED IN THE DESCRIPTION
This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.
Patent documents cited in the description