METHOD AND DEVICE FOR MACHINE-ASSISTED REPORTING OF FAULT CONDITIONS CONCERNING COMPONENTS OF A PASSENGER TRANSPORTATION SYSTEM AND FOR MACHINE-ASSISTED INFORMING A MONITORING DEVICE ABOUT REPORTED FAULT CONDITIONS

Description

[0001] The present invention relates to a method and a device for machine-assisted reporting of fault conditions concerning components of a passenger transport system. The invention further relates to a method and a device for machine-assisted informing a monitoring device about reported fault conditions concerning components of a passenger transport system. The invention also relates to a corresponding computer program product and a computer-readable medium containing such a computer program product.

[0002] Passenger transport systems, such as elevators, escalators, or moving walkways, are used to transport people within buildings. These systems must meet high standards of safety and reliability. Therefore, even during installation, it must be ensured that the passenger transport system is correctly assembled according to the relevant specifications. Furthermore, during operation, monitoring and maintenance measures must be implemented to ensure that safety and reliability requirements are met.

[0003] EP 1 628 899 B1 describes a method and a device for the maintenance of an elevator or escalator system.

[0004] JP2007153581A offers a maintenance inspection management system to streamline maintenance inspections at elevator sites. Various maintenance checkpoints are marked with QR codes containing information specifying each checkpoint. When a maintenance personnel's information transmitter scans a QR code, a monitoring center identifies the maintenance inspection location and sends relevant inspection information to the transmitter. This allows maintenance personnel to quickly perform maintenance and inspection work at each station.

[0005] WO2017037240A1 discloses a method for maintaining a transport system. The method comprises: receiving image data of a component of the system, wherein the image data is generated with a camera of a mobile device directed at the component; identifying the component by evaluating the image data; retrieving maintenance data associated with the identified component from a central maintenance database; and displaying the maintenance data in the mobile device.

[0006] Passenger transportation systems generally consist of a variety of different components. For example, an elevator system may include a cabin and a counterweight suspended from load-bearing elements and guided along rails in an elevator shaft. The movement of the cabin and counterweight is initiated by a drive unit and controlled by a control unit. Sensor components can detect prevailing conditions within the elevator system, for example, to adjust the elevator's operation accordingly. Safety components can be distributed throughout the elevator system to monitor its safe operation. All of these different components can malfunction, for example, due to wear and tear or defects.

[0007] Therefore, even during the installation of a passenger transport system, care must be taken to ensure that all components are correctly selected, function correctly, and are installed correctly. Subsequent monitoring, maintenance, and component replacements must also ensure that the components used possess the required properties.

[0008] Previously, a technician installing or maintaining a passenger transport system had to independently check the components used for compliance with the required specifications. If the required specifications were not met, the technician had to find a solution independently to complete the installation or maintenance of the passenger transport system. This sometimes required the technician to painstakingly determine the specifications of a component using, for example, operating instructions or other documentation, in order to modify the component appropriately and thus make it operational.

[0009] Since identical or similarly designed passenger transport systems and their components are frequently installed, it was also desirable that the technician, if he discovered an undesirable characteristic or defect in a component to be installed, should write a report about it. In other words, the technician should not only determine that a component was not functioning as intended and then repair or replace it if necessary, but should also prepare a report as the rapporteur.

[0010] Such reports should, for example, enable a development department at a manufacturer of the passenger transport system to identify and, if possible, eliminate system-related and therefore frequently occurring error conditions or sources of error in the passenger transport system.

[0011] However, practical experience has shown that reports on fault conditions compiled by technicians are often either not compiled at all or not compiled appropriately. Furthermore, it has been found that the reports that were compiled were frequently difficult to analyze.

[0012] Therefore, there may be a need to be able to detect fault conditions concerning components of a passenger transport system more reliably and to report them in such a way that useful information regarding the reported fault conditions in the components can be derived from this.

[0013] Such a need can be met by the methods or devices, as well as a computer program product and a computer-readable medium provided therewith, according to one of the independent claims. Advantageous embodiments are defined in the dependent claims and the description.

[0014] According to a first aspect of the invention, a method for machine-assisted reporting of fault conditions concerning components of a passenger transport system is proposed. The method is hereinafter also referred to in part as the "reporting method". The method comprises at least the following process steps, preferably in the specified order: Acquisition of identity information and / or fault information by means of a reporting device, wherein the identity information represents the identity of an examined component and wherein the fault information represents a fault condition in the examined component; automatic transmission of the identity information and / or the fault information to an analysis device in a first data transmission operation; automatic selection of a range of fault cause possibilities from a list of fault cause possibilities stored in the analysis device based on the identity information and / or the fault information and transmission of selection information, which represents the selection of fault cause possibilities, to the reporting device in a second data transmission operation;Automatic output of the selection information for possible causes of failure by the reporting unit and recording of sub-selection information, which represents a sub-selection chosen by a reporter from the selection of possible causes of failure; and automatic transmission of the sub-selection information to the analysis unit in a third data transmission process.

[0015] According to a second aspect of the invention, a method for machine-assisted information provision to a monitoring device regarding reported fault conditions concerning components of a passenger transport system is proposed. This method is hereinafter also referred to in part as the "information method". The method comprises at least the following steps, preferably in the order given: Collecting root cause information for reported fault conditions, comprising repeatedly performing the following procedure steps: receiving identity information and / or fault information in an analysis unit, wherein the identity information was acquired by a reporting unit and represents the identity of an investigated component, and wherein the fault information was acquired by the reporting unit and represents a fault condition in the investigated component; automatically selecting a range of root cause information from a list of root cause information stored in the analysis unit based on the identity information and / or the fault information, and transmitting selection information, representing the selection of root cause information, to the reporting unit;Receiving subselection information in the analysis unit, wherein the subselection information represents a subselection chosen by a rapporteur from the selection of failure cause possibilities; and automatically informing the monitoring unit as soon as the frequency with which a failure cause possibility specific to a particular component type has been received from the analysis unit exceeds a predetermined frequency threshold.

[0016] According to a third aspect of the invention, a device for machine-assisted reporting of fault conditions relating to components of a passenger transport system is proposed, wherein the device is configured to perform or control a method according to an embodiment of the first aspect of the invention. Such a device is referred to herein as a reporting device.

[0017] According to a fourth aspect of the invention, a device for machine-assisted evaluation of reported fault conditions concerning components of a passenger transport system and for machine-assisted information provision to a monitoring device is proposed, wherein the device is configured to perform or control a method according to an embodiment of the second aspect of the invention. Such a device is referred to herein as an evaluation device.

[0018] According to a fifth aspect of the invention, a computer program product is proposed which includes computer-readable instructions which cause a processor to perform or control a method according to the first aspect or the second aspect of the invention.

[0019] According to a sixth aspect of the invention, a computer-readable medium is proposed which includes a computer program product stored thereon according to the fifth aspect of the invention.

[0020] Possible features and advantages of embodiments of the invention can be considered, among other things and without limiting the invention, as being based on the ideas and findings described below.

[0021] As mentioned in the introduction, the reporting of detected fault conditions in components of a passenger transport system has often been neglected or inadequate. Even when a report was generated, it frequently failed to provide useful information from the reported fault conditions for improving the component or its use in the passenger transport system in the future.

[0022] In particular, it was observed that the task of writing a report placed a considerable additional burden on a technician and was therefore sometimes ignored. Furthermore, it was noted that reports from different technicians were formulated in very different ways, even when similar or even identical defects were present in a component. Adding to the complexity was the fact that passenger transport systems and their components are installed and operated under very different conditions. For example, the technicians involved in their installation or maintenance may have different qualifications, speak different languages, or have access to different tools or documentation.Furthermore, evaluating the reported data proved extremely difficult, as some information necessary for a meaningful evaluation was not included. Ultimately, it was often nearly impossible to derive information from the reported data that would have enabled, for example, a manufacturer of the passenger transport system to systematically improve the system or related products or services.

[0023] Embodiments of the method and the device proposed herein, according to the first and third aspects of the invention, are intended to simplify the reporting process and enable the detected fault conditions to be reported in such a way that their subsequent evaluation can be carried out simply and efficiently. For this purpose, the reporting can be performed using a specially configured reporting device and an analysis device. On the one hand, the reporting can be machine-assisted by the reporting device; on the other hand, the reported fault conditions can be appropriately analyzed by the analysis device, thereby supporting the reporter in the reporting process.

[0024] Embodiments of the proposed method or device according to the second and fourth aspects of the invention can then be used to analyze the reported error states in a suitable manner in order to derive useful information from them. For this purpose, the analysis device can, for example, execute the proposed method and thereby collect possible causes of errors that have been identified as causative for certain error states over many reports and, for example, automatically inform a monitoring device based on the frequency with which a possible cause of an error occurs. Based on the information then available in the monitoring device, developers can, for example, further develop the defective component in order to systematically correct error states, for example, by structural or functional changes.

[0025] The following section explains possible configurations and embodiments of the method according to the first aspect of the invention and of the reporting device according to the third aspect of the invention.

[0026] To generate a report regarding a fault condition in a component of the passenger transport system, a technician can utilize the functionalities provided by the reporting unit and the analysis unit. These functionalities are implemented in the reporting device, which can therefore comprise a reporting unit and an analysis unit as separate entities. Each reporting unit and the analysis unit can have a suitable processor and, if necessary, data storage to process and store data. Furthermore, both units can have suitable communication capabilities to exchange information with each other.

[0027] As soon as the technician determines that a component of the passenger transport system is faulty and decides to create a report, he can use the reporting system. This reporting system is specifically designed to support the technician in reporting the fault condition in such a way that, on the one hand, the technician has to put in as little effort as possible to create the report, and on the other hand, the report is created in a way that facilitates a subsequent useful evaluation of the information it contains.

[0028] The reporting device can be a portable device that the technician can carry with them. The reporting device can utilize hardware specifically designed for this purpose. Alternatively, the reporting device can utilize existing hardware, for example, in the form of a smart portable device such as a smartphone or a tablet, whereby the desired functionality can be achieved through programming with suitable computer software.

[0029] With the help of the reporting device, the technician can, with machine support, determine the identity of the examined, faulty component on the one hand, and on the other hand, record corresponding identity information and forward it as a signal.

[0030] For example, each component installed in a passenger transport system can be assigned a unique ID (identification code). Components belonging to a specific component type can have the same IDs, possibly supplemented by a serial number.

[0031] The ID of a component can be stored on the component itself in the form of machine-readable information, allowing it to be read by the reporting device. This enables the identity of the component under investigation to be automatically determined and thus easily shared by the technician. Preferably, the information is stored in a way that allows it to be read contactlessly, i.e., without physical contact.

[0032] For example, the identification information can be stored as an optically readable code, such as a barcode or QR code, and then read using a scanner integrated into the reporting device. Such optically readable codes can be easily and cost-effectively applied to a component, for example, as a sticker. Alternatively, they can be read easily and reliably with an optical scanner, such as a camera.

[0033] Additionally or alternatively, the technician can use the reporting device to record fault information that reflects or correlates with a fault condition of the component under investigation.

[0034] For example, the technician can use a camera integrated into the reporting device to take a picture of a defective component. Alternatively, the technician can record the fault information by entering a short description, selecting a corresponding symbol, or similar methods.

[0035] The identity information and / or error information captured in this way is transmitted to the analysis unit in the first data transmission process. The analysis unit can be located remotely from the reporting unit. In particular, the analysis unit can be a separate computer, server, or in the form of a data cloud (cloud). Information transmission between the reporting unit and the analysis unit can be wired or wireless. This transmission can occur via a data network such as the internet. Specifically, the analysis unit can receive information from a multitude of different reporting units, allowing it to gradually accumulate information on a wide variety of reported error states and their associated root causes.

[0036] Within the analysis unit, the received identity information and / or the received error information can be further processed to identify a selection of possible causes of the error that could be responsible for the observed error state in the component under investigation. For this purpose, the analysis unit may, for example, store a list of possible causes of the error in a database. From this list, those possible causes of the error that are most likely to explain the observed error state can be selected based on the identity information and / or the error information.

[0037] For example, a list of multiple known error causes can be stored for each component type. If an error occurs in a component of that type, all of these possible error causes for that component type can then be selected. Additionally, the error information can be used to filter out those possible error causes that could be the cause of a specific error condition, as indicated by the error information, or that are considered to be the cause with a particularly high probability.

[0038] In addition to the list of possible causes of failure, the analysis device may also contain one or more suggestions for correcting the associated failure condition for each possible cause of failure.

[0039] In a second data transmission process, the analysis unit can then transmit the information found about the selected possible causes of the error, which is referred to herein as "selection information", as well as any associated suggestions for remedying the error condition, i.e. the remedy information, to the reporting unit.

[0040] The selection information and / or the remediation information can preferably be transmitted in a language preset by the rapporteur. In the analysis setup, all possible causes of failure can be stored in the list of possible causes translated into various languages. Alternatively, translations of possible causes of failure can be created as needed, for example, using translation software. The same applies to the suggested solutions for the respective failure states. The rapporteur can thus configure their reporting setup so that the selection and / or remediation information is displayed in a language they understand. This reduces the risk of misunderstandings due to the technician's lack of foreign language skills.

[0041] The reporting device can automatically output the selection information, including, if applicable, the remediation information, in a way that allows it to be perceived by the reporting technician. For example, the selection information and / or the remediation information can be displayed on a screen of the reporting device in the form of text, symbols, or similar.

[0042] The technician can then select from the displayed selection information the possible cause of the fault that, in their opinion, is actually responsible for the observed fault condition. If necessary, the technician can use the accompanying troubleshooting information to attempt to repair the component under investigation or to resolve the fault condition. This allows the technician to identify with even greater certainty which of the possible causes of the fault condition suggested in the selection information is actually the cause of the fault condition and can therefore be rectified according to the troubleshooting information.

[0043] The technician can then make a sub-selection from the output selection information on their reporting device. This corresponding sub-selection information can then be automatically transmitted to the analysis device as part of a third data transmission process.

[0044] Following the execution of the proposed reporting procedure, the analysis device contains both the identity information and / or the fault information, which allows conclusions to be drawn about the component under investigation and possibly its current fault state, as well as the subselection information, which allows conclusions to be drawn about a most probable possible cause of the observed fault state. This information has been captured and transmitted by the technician using his reporting device in a standardized manner, thus enabling a standardized evaluation.

[0045] According to one embodiment, the first transmission process can additionally transmit location information, which indicates the location of the component under investigation. In other words, in addition to the identity information and / or the fault information, the reporting device can transmit information to the analysis device that, for example, indicates where the reporting device is used and thus where the component under investigation was installed.

[0046] The deployment location information can, for example, be permanently stored in the reporting system, provided it can be assumed that a reporting system is only used in a specific region or country. Alternatively, the deployment location information can be determined from data collected on-site, such as GPS information. The deployment location information can then indicate the location of the personnel transport system.

[0047] The installation location information allows for consideration of the specific location where the component under investigation was installed when later evaluating the identity, fault, and subselection information. Influences on the component that ultimately lead to a fault condition can, in many cases, depend on the installation location. For example, environmental influences such as climatic conditions and stresses acting on a component can differ from one installation location to another. Environmental influences can, for instance, lead to faster wear of a component. Methods for installing components in a passenger transport system can also vary from one installation location to another. For example, technicians in some countries may use different tools or have different training than those in others.

[0048] In a more specialized form, the deployment location information can also specify the deployment location of the component more precisely, thus indicating the position of the component under investigation within the passenger transport system.

[0049] If the evaluation of the information reveals that certain error conditions and their selected possible causes occur only or predominantly at certain locations, this can provide valuable information on how the component under investigation would need to be modified to avoid these error conditions in the future.

[0050] Possible configurations and embodiments of the information method according to the second aspect of the invention and of the evaluation device according to the fourth aspect of the invention are explained below.

[0051] While the previously described method for machine-assisted reporting of fault conditions typically uses two separate devices, namely the reporting device and the analysis device, with various process steps being carried out on each of these devices, the method for machine-assisted informing a monitoring device about reported fault conditions, as proposed in the second aspect of the invention, typically takes place exclusively in the evaluation device. The evaluation device can be identical to or encompass the previously described analysis device in terms of its technical specifications or functionalities. In particular, the evaluation device can be configured as a single technical device, for example, a single computer, or as a network of devices, for example, in the form of a data cloud.

[0052] In the first step of the information process, a multitude of possible causes for reported error states are collected over time. In other words, the reporting process described above can be carried out multiple times, for example by different reporters and with regard to different passenger transport systems, thereby collecting the possible causes for the errors that are specified in the selection information transmitted to the analysis unit.

[0053] During each reporting procedure, the evaluation device or its analysis unit receives identity information and / or fault information regarding the identity or fault state of an examined component. Based on this identity and / or fault information, the analysis unit automatically selects a range of possible fault causes and transmits this selection information to the respective reporting unit from which the identity or fault information was received. The analysis unit then receives from the reporting unit the sub-selection information selected by the reporter, which indicates the most probable fault cause for an observed fault state.

[0054] However, the information on the possible causes of errors should not only be collected in the analysis facility, but should also serve, for example, to enable a manufacturer of passenger transport systems to identify systematically occurring errors in components of a passenger transport system and to be able to further develop the component appropriately.

[0055] In principle, every generated report could be forwarded to a monitoring system, such as one operated by the manufacturer of the passenger transport system. However, it has been observed that many fault conditions occurring in field operation are not systematically caused, but rather occur randomly. Fault conditions can also arise simply because the wrong component is inadvertently used in a passenger transport system. Therefore, indiscriminately forwarding reports can lead to an unnecessary and inefficient evaluation process.

[0056] In the information procedure proposed here, the monitoring device is therefore only automatically informed if a specific fault cause occurs particularly frequently for a specific component type and is thus reported to the analysis device with particular frequency.

[0057] For this purpose, a frequency threshold can be predefined for each component type and each possible cause of failure associated with that component type. As soon as a possible cause of failure for that component type is reported more frequently than the frequency threshold, the analysis unit automatically informs the monitoring unit. Based on this information, developers can recognize that the possible cause of failure appears to occur systematically for the component type in question and is causing faulty conditions. The component type can then be modified accordingly.

[0058] The frequency limit can be predetermined by considering the physical properties and / or functionalities of the specific component type. In other words, the way a component type is structured can influence the determination of the frequency limit. Functionality to be implemented with the component type can also be considered when determining the frequency limit.

[0059] For example, if a component type is inherently prone to a certain degree of wear due to its physical design, and this has already been taken into account in the design of the passenger transport system, the corresponding frequency limit for related fault conditions can be set relatively high. Conversely, if a component type is intended to implement safety-relevant functionality, the frequency limit for potential causes of failure leading to malfunctions in that component type can be chosen to be low.

[0060] The frequency limit can also be predetermined taking into account the frequency of use of the specific component type. In other words, when setting a frequency limit, consideration can be given to how often the component type in question is actually used in passenger transport systems. For component types that are rarely installed, a lower frequency limit can be predetermined than for component types that are frequently installed and for which, statistically, fault conditions also occur and are reported more frequently.

[0061] According to one embodiment, when collecting possible causes of failure, the analysis device can additionally receive location information. This location information indicates the location of use of the component under investigation. In this case, the frequency limit can be predetermined taking into account the location of use of the specific component type.

[0062] In other words, as mentioned above, the operating environment can influence how frequently certain fault conditions occur in a given component type. Information about the operating environment can therefore be transmitted when informing the monitoring device, in order to provide a developer, for example, with clues and conclusions about which operating environment-specific conditions might explain an observed fault.

[0063] By considering the deployment location when predetermining the frequency threshold, the analysis unit's decision on whether to inform the monitoring unit can be made dependent on the deployment location from which specific failure modes are reported. This allows for consideration of situations where it is already known that certain failure modes occur more frequently at specific deployment locations, for example, due to prevailing climatic conditions, and this is tolerated, while at other deployment locations, a high incidence of failure modes could indicate a systematic design flaw in that component type.

[0064] According to one embodiment of the method proposed here, information can further be transmitted from the analysis unit to the reporting unit as soon as a solution for a potential cause of the fault has been found. The potential cause of the fault may, for example, have been eliminated by a technical improvement of the component type. This information can then reach the technician who previously reported the fault condition via the reporting unit.

[0065] This can, on the one hand, ensure that the technician is informed that there may now be further developed components available, so that in the future, for example, faulty components can be replaced by such further developed components.

[0066] On the other hand, such information transfer can contribute to motivating technicians to report fault conditions. In particular, it has been observed that technicians who are given the impression that the reports they submit actually lead to the further development of a faulty component are more motivated to undertake the effort of creating a report.

[0067] If necessary, the creation of a report, either directly or after a solution to the reported potential cause of the error has been developed based on the report, can be further motivated or incentivized by paying a bonus. For this purpose, the evaluation or analysis device can keep a record of when and about what a technician created a report, and the data stored therein can then be taken into account when calculating bonuses.

[0068] Implementations of the reporting or information method described herein can be implemented on programmable devices using a computer program. The computer program can be executed on one or more processors of a reporting device or an evaluation device, in particular on a processor of a reporting device and / or a processor of an analysis device. The computer program can, in particular, be executed in a distributed manner across multiple components of a data cloud. The computer program can be programmed in any computer language.

[0069] The computer program product can be stored on any computer-readable medium. For example, the computer program product can be stored on a CD, a DVD, a flash memory, etc. The computer program product can also be stored on individual computers or a network of computers and downloaded from there, for example via the internet.

[0070] It is noted that some of the possible features and advantages of the invention are described herein with reference to different embodiments of the methods presented herein, on the one hand, and the devices that can be used for them, on the other. A person skilled in the art will recognize that the features can be suitably combined, transferred, adapted, or exchanged to arrive at further embodiments of the invention.

[0071] The following describes embodiments of aspects of the invention with reference to the accompanying drawing, whereby neither the drawing nor the description is to be interpreted as limiting the invention.

[0072] Fig. 1 shows an arrangement of devices by means of which the methods proposed herein can be implemented according to an embodiment of the present invention.

[0073] The figure is schematic only and not to scale. Identical reference symbols denote identical or equivalent features.

[0074] Fig. 1Figure 1 shows a reporting device 1, by means of which, according to one embodiment of the present invention, fault conditions relating to various components 11', 11", 11‴ of a passenger transport system can be reported using machine assistance. The reporting device 1 comprises at least one reporting unit 5 and an analysis unit 7. The analysis unit 7 can simultaneously be considered part of an evaluation unit 3, by means of which reports generated by the reporting device 1 can be evaluated and, optionally, a monitoring unit 9 can be suitably automatically informed of a frequent occurrence of reported fault conditions.

[0075] The reporting device 5 has a scanner 17, for example in the form of a camera 27. Using this scanner 17, a technician can, if he detects a fault condition in a component 11 of a passenger transport system, read machine-readable information 13 stored on the component 11, for example in the form of a QR code 15. The machine-readable information 13 can include identification information, which may contain, for example, details about the component type of the component under investigation, its specific properties, a serial number, a location of use, and / or other information.

[0076] Additionally or alternatively, the technician can also record fault information that allows conclusions to be drawn about the fault condition of the examined component 11. For this purpose, the technician can, for example, use the camera 27 of the reporting device 5 to take a picture of faulty components 31 of component 11.

[0077] The identity information and / or error information recorded by the reporting unit 5 is then automatically transmitted to the analysis unit 7 in a first data transmission process 19. The analysis unit 7, or the evaluation device 3 implemented with it, can be configured as multiple computers that together form a data cloud. Alternatively, the analysis unit 7 can be a single central computer. The analysis unit 7, or the evaluation device 3, can communicate with and receive information from a multitude of different reporting units 5.

[0078] Analysis unit 7 contains a list 33 of possible causes of failure 37. For each identity information (ID) 35, i.e., for each component type, problems (P) that occur and the resulting possible causes of failure 37 can be listed. Possible solutions may also be listed in the list 33. For each possible cause of failure 37, the frequency (H) 39 with which it occurs is also logged.

[0079] In the analysis unit 7, using list 33, a selection of possible causes of errors is automatically selected based on the received identity information and / or error information and then transmitted back to the reporting unit 5 in the form of selection information as part of a second data transmission process 21.

[0080] The selection information thus represents a selection of possible fault causes F1, F2, F3, F4, etc., which could be responsible for the observed fault condition. For example, fault cause F1 could be that a component was delivered incorrectly for the installation of a passenger transport system, fault cause F2 could be that a component has incorrect dimensions, fault cause F3 could be that the component has incorrect functional properties, etc. The fault causes F1, F2, F3, F4 can, for example, be displayed on a display 25 of the reporting device 5, so that a technician can easily perceive them visually.

[0081] The reporting technician can then make a subselection from the displayed selection information. For example, the technician can select the fault cause F1, F2, F3, or F4 that, in their opinion, is actually or with a high degree of probability the cause of the observed fault condition in the present case.

[0082] The corresponding subselection information is then automatically transmitted from the reporting unit 5 to the analysis unit 7 as part of a third data transmission process 23.

[0083] Over time, the analysis device 7 or the evaluation device 3 can thus receive a large number of reports from different reporting devices 5 and collect the possible causes of errors mentioned therein for the reported error conditions.

[0084] As soon as the frequency 39 with which a specific fault cause possibility 37 has been reported to the evaluation device 3 specifically for a specific component type exceeds a predetermined frequency limit, the evaluation device 3 can then appropriately inform the monitoring device 9 about this.

[0085] Developers can then try to further develop the corresponding component type to avoid the observed error condition occurring in the future.

[0086] If this is successful, corresponding information can be transmitted to the analysis unit 7, and this unit can then transmit the information to all corresponding reporting units 5, or at least to those reporting units 5 that had previously reported a corresponding error condition, as part of a fourth data transmission process 41.

[0087] Overall, the approach presented here can make it easier for a technician to generate reports on fault conditions in components of a passenger transport system, as the technician is largely supported automatically by the reporting device 1. Furthermore, the reports can be generated in a standardized manner, allowing the evaluation device 3 to easily extract information that enables targeted further development of components 11.

[0088] Finally, it should be noted that terms such as "comprising," "encompassing," etc., do not exclude other elements or steps, and terms such as "a" or "an" do not exclude a plurality. Reference numerals in the claims are not to be considered as limitations. Reference symbol list

[0089] 1 Reporting device 3 Evaluation device 5 Reporting device 7 Analysis device 9 Monitoring device 11 Components of the passenger transport system 13 Machine-readable information 15 QR code 17 Scanner 19 First data transmission process 21 Second data transmission process 23 Third data transmission process 25 Display 27 Camera 31 Components of a component 33 List of possible causes of failure 35 Identification information 37 Possible cause of failure 39 Frequency 41 Fourth data transmission process

Claims

1. A method for reporting fault states relating to components (11) of a passenger transport system in a machine-supported manner, with said method comprising the steps of: - acquiring identity information (35) and / or fault information by means of a reporting device (5), wherein the identity information (35) describes an identity of a component (11) being examined, and wherein the fault information describes a fault state in a component (11) being examined; wherein the method is characterized in that - automatically transmitting the identity information (35) and / or the fault information to an analysis device (7) in a first data transmission process (19); - automatically selecting a selection of possible causes (37) of the fault from a list (33) of possible causes (37) of faults stored in the analysis device (7) based on the identity information (35) and / or the fault information and transmitting corresponding selection information, which describes the selection of possible causes (37) of the fault, to the reporting device (5) in a second data transmission process (21); - automatically outputting the selection information on possible causes (37) of the fault by means of the reporting device (5) and receiving sub-selection information, which describes a sub-selection selected by a reporter from the selection of possible causes (37) of the fault; and - automatically transmitting the sub-selection information to the analysis device (7) in a third data transmission process (23).

2. The method according to claim 1, wherein the identity information (35) is acquired by reading out machine-readable information (13) stored on the component (11) being examined.

3. The method according to claim 2, wherein the identity information (35) is stored on the component being examined in the form of an optically readable code (15) and read out by means of a scanner (17) integrated into the reporting device (5).

4. The method according to one of the preceding claims, wherein the selection information is transmitted to the reporting device (5) in a language that can be preset by the reporter.

5. The method according to one of the preceding claims, wherein usage site information is additionally transmitted in the first transmission process (19), and wherein the usage site information describes a usage site of the component (11) being examined.

6. The method according to claim 1, in which the possible causes (37) of faults for reported fault states are collected by carrying out the steps according to claim 1 multiple times, and wherein a monitoring device (9) is automatically informed on the collected possible causes (37) of faults as soon as a frequency, with which a possible cause (37) of a fault was received by the analysis device (7) specifically for a certain component type, exceeds a predefined frequency threshold value.

7. The method according to claim 6, wherein the frequency threshold value is predefined with consideration of physical properties and / or functionalities of the certain component type.

8. The method according to one of claims 6 and 7, wherein the frequency threshold value is predefined with consideration of the frequency of use of the certain component type.

9. The method according to one of claims 6 to 8, wherein usage site information is additionally received when possible causes (37) of faults are collected, wherein the usage site information describes a usage site of the component (11) being examined, and wherein the frequency threshold value is predefined with consideration of the usage site of the certain component type.

10. The method according to one of claims 6 to 9, wherein corresponding information is transmitted from the analysis device (7) to the reporting device (5) as soon as an option for correcting a possible cause of a fault has been found.

11. A report generating device (1) for reporting fault states relating to components (11) of a passenger transport system in a machine-supported manner, characterized in that, the report generating device (1) is configured for carrying out or for controlling a method according to one of claims 1 to 6.

12. The report generating device (1) according to claim 11, wherein the report generating device (1) can be connected to the evaluating device (3) such that the evaluating device (3) can receive information from the report generating device (1), and wherein the evaluating device (3) is provided for evaluating reported fault states relating to components (11) of a passenger transport system in a machine-supported manner, as well as for informing a monitoring device (9) in a machine-supported manner, and configured for carrying out or for controlling a method according to one of claims 7 to 10.

13. A computer program product comprising machine-readable instructions that prompt a processor to carry out or to control the method according to one of claims 1 to 10.

14. A machine-readable medium with a computer program product according to claim 13 stored thereon.