Point inspection workflow management system

Abstract

A spot inspection workflow management system includes a server that manages a spot inspection workflow that instructs a spot inspection process of a work machine, and a terminal connected to the server via a network, the terminal including: a communication unit that is connected to the work machine as a spot inspection target and acquires identification information of the work machine; a display unit that displays a spot inspection workflow including an instruction to acquire moving image data of a spot inspection target portion of the work machine; an operation unit that inputs spot inspection related information corresponding to the spot inspection workflow; the server includes a storage unit that stores machine attribute information of the work machine associated with the identification information and the moving image data of the spot inspection target portion acquired by the terminal. The terminal establishes an association between identification information and spot-inspection-related information with respect to moving image data of a spot-inspection target site acquired by an imaging unit, and the server further associates mechanical attribute information with the moving image data of the spot-inspection target site that has been associated and stores the same in a storage unit. The terminal or the server further has a search unit that extracts, on the basis of at least one of the identification information, the spot inspection-related information, and the mechanical attribute information inputted to the terminal, moving image data of the spot inspection target site associated with the at least one piece of information.

Description

Technical Field

[0001] This invention relates to a system for managing the inspection process of machinery. Background Technology

[0002] Operating machinery, such as hydraulic excavators, is used differently in various operating environments, resulting in different inspection points for each machine during maintenance. Therefore, regardless of the experience of the maintenance manager, the ability to quickly and reliably inspect a large number of components is required, making efficient inspection a key challenge. Patent Document 1 discloses a technology that outputs a maintenance inspection process for efficient machinery maintenance. Existing technical documents Patent documents

[0003] Patent Document 1: Japanese Patent Application Publication No. 2003-178148 Summary of the Invention

[0004] Patent document 1 describes how, when a malfunction is identified in a part of the maintenance and inspection process for machinery, a sequence of actions to address that malfunction is output (paragraphs 0052, 0068-0070). Figure 7 (etc.). However, the handling procedure is limited to a simple response of inputting the status of the inspected part. Therefore, when the cause of the malfunction cannot be determined and a fundamental solution cannot be found, entrusting a specialized handling agency to handle the matter still results in the problem of time being spent before the repair is completed.

[0005] The present invention was made in view of the above-mentioned problems, and its purpose is to shorten the time required to determine the cause of malfunctions in the maintenance and inspection of working machinery, and to enable maintenance and inspection to be carried out quickly and reliably.

[0006] To address the aforementioned issues, the present invention provides an inspection workflow management system comprising a server and a terminal connected to the server via a network. The server manages an inspection workflow that instructs the inspection procedures of machinery. The terminal includes: a communication unit connected to the machinery being inspected and acquiring its identification information; a display unit displaying the inspection workflow, which includes instructions for acquiring dynamic image data of the inspected parts of the machinery; an operation unit for inputting inspection association information corresponding to the inspection workflow; and a capturing unit for acquiring dynamic image data of the inspected parts. The server has a storage unit storing the machinery associated with the identification information. The terminal acquires the mechanical attribute information of the machine and the dynamic image data of the inspection object part obtained by the terminal. The terminal establishes an association between the identification information and the inspection association information relative to the dynamic image data of the inspection object part acquired by the imaging unit. The server further establishes an association between the mechanical attribute information and the dynamic image data of the inspection object part that has been associated and stores it in the storage unit. The terminal or the server also has a retrieval unit. The retrieval unit extracts the dynamic image data of the inspection object part that has been associated with the at least one piece of information, including the identification information, the inspection association information and the mechanical attribute information, based on at least one piece of information input to the terminal. Invention Effects

[0007] According to the present invention, images, animations, and sounds (dynamic image data) related to past adverse events are associated with inspection results and information about the operating machinery. This information is used as keywords to extract the associated dynamic image data. As a result, it is easy to use dynamic image data to determine whether the adverse events found during the inspection are the same as past adverse events, thereby reducing the time required to determine the cause of the adverse events.

[0008] Further features associated with this invention will become clear from the description and accompanying drawings. Additionally, issues, configurations, and effects beyond those described above will become clear from the following description of embodiments. Attached Figure Description

[0009] Figure 1 This is a conceptual diagram showing the overall structure of the present invention. Figure 2 This is a block diagram illustrating the overall hardware configuration of the system according to Embodiment 1 of the present invention. Figure 3 This is a flowchart illustrating the processing flow performed by the present invention. Figure 4 This is a block diagram illustrating the overall hardware configuration of the system according to Embodiment 2 of the present invention. Figure 5 This is a flowchart illustrating the processing flow executed in Example 2. Figure 6 This is a diagram used to illustrate the tag addition performed in this invention. Figure 7 It is a graph representing the categories of labeled data. Figure 8 It is a block diagram representing the overall hardware configuration of the modified system. Detailed Implementation

[0010] [Example 1] The following is a reference to the appendix. Figure 1 The following is an explanation of the embodiments. In this embodiment, a hydraulic excavator is used as an example of working machinery, but the working machinery is not limited to a hydraulic excavator. It can also be a crane, a wheel loader, a forklift, a bulldozer, or a combination of these machines.

[0011] In the operation site of machinery, maintenance and inspection personnel (hereinafter referred to as service personnel) use mobile terminals to inspect the machinery. Since the inspection areas vary depending on the operating condition of the machinery being inspected, the inspection areas are output / displayed on the terminal's screen according to the inspection target. Service personnel perform inspections according to a (digital) workflow. Here, the workflow represents the inspection procedures accompanying interface transitions. If a malfunction is discovered during the process, dynamic image data is acquired, correlated with information about the malfunction, and stored. This configuration allows for easy determination of whether a malfunction is similar to past malfunctions when it occurs.

[0012] Management System The management system in this embodiment establishes and manages the operation information sent from the operating machinery that is the object of management and the dynamic image data of the inspection results sent from the mobile terminal with any inspection process in the workflow containing multiple inspection processes, thereby providing information to service personnel when similar phenomena occur.

[0013] Figure 1 This is a schematic diagram illustrating an embodiment of the inspection workflow management system of the present invention. The management system 100 of this embodiment has multiple operating machines 10; a maintenance management server 20 that can communicate with these operating machines 10 via a network 40; and a terminal 30 that can communicate with the server 20 and the operating machines 10 via the network 40.

[0014] The work machinery 10 has operation sensors and a wireless communication mechanism on its body, enabling it to communicate with the maintenance management server 20 and the terminal 30 via the network 40. The maintenance management server 20 is used for the maintenance management of the work machinery 10, such as the hydraulic excavator. The maintenance management objects managed by the maintenance management server 20, i.e., the work machinery 10, are not limited to hydraulic excavators; for example, they can also be wheel loaders, road machinery, dump trucks, etc.

[0015] The maintenance management system 100 sends a program associated with fault prediction and maintenance information of the operating machinery to the terminal 30 based on the request from the inspector of the operating machinery 10.

[0016] Terminal 30 can be a portable laptop PC or a desktop PC located in an office, but it can also be a smartphone, tablet, mobile phone, or PDA (Personal Data Assistant) carried by the maintenance personnel or user of the hydraulic excavator 10. The maintenance personnel or user can select a specific identification number of the hydraulic excavator 10 through terminal 30, thereby requesting inspection information related to the specific hydraulic excavator 10 from server 20.

[0017] In the operating machinery 10, sensors for detecting operating status are installed in various key parts, and a controller is provided. The controller digitizes the operating status data detected by the sensors and sends it to the server 20, for example, via network 40.

[0018] Figure 2 This is a block diagram illustrating the overall hardware configuration of the system in this embodiment.

[0019] terminal The terminal 30 includes a communication unit 31, a display unit 32, a camera unit 33, a storage unit 34, an operation unit 35, a retrieval unit 36, and a diagnostic unit 37.

[0020] The communication unit 31 has wireless communication functions for example, to connect to the network 40. The display unit 32 is composed of a monitor, for example, and has the function of displaying guidance screens about the inspection operation and various information about the inspector.

[0021] The imaging unit 33 has an imaging function capable of capturing moving images. Additionally, it can be connected wirelessly / wired to a terminal with imaging capabilities (such as a smartphone). The storage unit 34 has a storage function, storing the workflow representing the inspection procedures of the machine. The operation unit 35 consists of a touch panel on the surface of the display of the display unit 32, and performs input processing regarding operations. Furthermore, the operation unit 35 also has functions such as accepting inspection results input and search criteria input. For example, the inspector can input inspection results by pressing or selecting icons and buttons displayed on the display unit 32, or by inputting via the keyboard displayed on the display unit 32.

[0022] The retrieval unit 36 ​​can access various functions stored in the storage unit 22 (described later) of the maintenance management server 20 and perform information retrieval and extraction. The diagnostic unit 37 determines the cause of the malfunction based on the sensor data obtained from the operating machine 10, and displays the determination result on the display unit 32 or sends it to the server 20.

[0023] Server maintenance and management In this embodiment, the maintenance management server 20 provides maintenance support information to the terminal, such as recommended replacement periods for parts and the degree of deterioration, based on operating information and inspection results sent from the machine 10 and the terminal 30 maintained by the service personnel. The maintenance management server 20 includes a computing unit 21, a storage unit 22, an input / output unit 23, and a communication unit 24.

[0024] The arithmetic unit 21 has a CPU (Central Processing Unit) and executes various programs. The storage unit 22, like the storage unit 34, has a storage function and stores the operating information of the machine 10 sent from the machine 10, the maintenance information sent from the terminal 30, and the individual identification information of the machine 10. Furthermore, data generated by the arithmetic unit 21 during processing is stored in the storage unit 22. Additionally, the storage unit 22 stores programs that enable the various functions executed by the arithmetic unit 21. The input / output unit 23, for example, has a touch panel to accept various inputs. The communication unit 24 receives operation instructions from the terminal 30 and performs information transmission and reception with external servers such as the machine 10 and the terminal 30.

[0025] Functions of servers and terminals On the terminal 30, a small program (inspection program) for performing inspections of the operating machinery 10 is pre-installed. By connecting with any operating machinery 10, the identification information (such as model number and manufacturing number) of the operating machinery 10 can be obtained.

[0026] Within the inspection program, multiple programs corresponding to the workflow are included for each machine. If connected to the target machine 10, the terminal's inspection program is activated, automatically inputting the machine's identification information into the terminal 30. Next, if the terminal 30 instructs the execution of the inspection, the workflow corresponding to the identification information obtained from the connected machine 10 is displayed on the terminal 30's display unit.

[0027] Here, the workflow represents the inspection procedures for various defects in the operating machinery. The workflow consists of multiple inspection procedures, each with detailed screens displaying specific inspection items. Therefore, if an inspection procedure is confirmed, the display switches to show the subsequent inspection procedures. Additionally, when a workflow is in progress, it indicates which inspection procedure is currently being performed within the overall workflow.

[0028] Service personnel perform routine inspections of the operating machinery 10 according to the workflow. If a defect is identified during the inspection process, a message instructing the acquisition of data (photos, animations, sounds) of the defective area is displayed on the terminal 30 as associated information. Service personnel operate the terminal 30 according to the message instructions to acquire the data of the defective area. The terminal 30 then associates the acquired data with the identification information of the operating machinery and the workflow.

[0029] Terminal 30 uploads data associated with the workflow to maintenance management server 20 via communication unit 31. Maintenance management server 20 stores the data in storage unit 22, and then, when any terminal 30 requests to view a dynamic image similar to a defect, it outputs dynamic image data corresponding to the conditions specified by the attributes of the operating machinery to any terminal 30.

[0030] Figure 3 This is a flowchart illustrating the processes performed by the system in this embodiment. First, in step S1, the service personnel connect the terminal 30 to the operating machinery 10, select and confirm the information of the machinery to be inspected, and then the inspection begins. Next, in step S2, the communication unit 31 of the terminal 30 is activated, establishing communication between the terminal 30 and the operating machinery 10. In step S3, the workflow (inspection procedure) is displayed on the screen of the terminal 30. The workflow is stored in the terminal 30, but it can also be stored in the server 20; in this case, the terminal 30 retrieves the workflow information from the server 20.

[0031] In step S4, the workflow progresses the inspection by switching the display screen of the inspection process. However, if the terminal 30 confirms a defective part during this process, it displays an instruction to acquire data (e.g., dynamic images and sounds) of the affected part, and acquires the necessary data via the imaging unit 33. In step S5, the workflow displays an instruction to acquire sensor values ​​indicating the operating status of the defective part, and acquires the sensor values ​​from the machine 10 via the communication unit 31. In step S6, the terminal 30 determines the cause of the defect based on the acquired sensor values. At this time, the result of the defect determination can also be displayed on the display unit 32.

[0032] In S7, the terminal 30, having determined the cause of the malfunction, ends the inspection. In S8, the terminal 30 sends data (including animation and sound) linking the inspection-object machine 10 and the inspection results to the server 20 via the communication unit 31. In S8, the terminal 30 links various information about the inspection-object machine 10 and the inspection results with the acquired dynamic image data. Here, in this embodiment, this linking is established through "tag addition," but the tag addition will be described in detail later. In S9, the terminal 30 sends the linked dynamic image data (including animation and sound) to the server 20 via the communication unit 31. In S10, the server 20 links the attribute information of the machine existing on the server with the received dynamic image data. In S11, the server 20 stores the dynamic image data linked with the machine's attribute information in the storage unit 22. The process ends there.

[0033] As described in this embodiment, the information of the operating machinery and the inspection results are associated with the acquired dynamic image data (labeling) and stored on the server or terminal. Subsequently, the service personnel performing the inspection can quickly determine the cause of the defect by using keywords and other methods to detect this information and referring to dynamic image data similar to the extracted defect.

[0034] The following lists the characteristics of the workflow described above. 1) In the workflow, the system first displays data on the operating status detected by the sensors of the machine to determine the location and type of malfunction alarms on the machine. 2) Next, a detailed screen will be displayed showing the checkpoints (confirmation items) associated with the defect. 3) Defects are often associated with multiple locations in complex ways. Furthermore, for each candidate deemed associated with a defect, necessary verification items are required. Therefore, the workflow consists of multiple detailed screens for each inspection location. These detailed screens are displayed sequentially, but sometimes also include reference animation data. In this case, the associated location is displayed with a message indicating "associated animation data." This display is generated by selecting and specifying this display on the terminal, and the animation data stored on the server is displayed. The display can occur whenever a corresponding screen is displayed, at the beginning or end of the workflow, or a combination of these displays; there are no restrictions on the timing of the display. The purpose is to identify potential causes of malfunctions by checking the details in each screen and to acquire associated motion image data. As this is a workflow, if the necessary checks in a detail screen are completed, the process moves to the next detail screen. If the check results for a certain detail screen identify a potential cause of the malfunction, a detailed inspection of sensor values, etc., is performed to further determine the root cause. The workflow's detail screens include text messages related to the checks and loop diagrams of the inspected areas. 4) The acquisition of dynamic image data is arbitrarily determined by the person executing the workflow.

[0035] Management methods for dynamic image data Through the above, a so-called "tag addition" is performed, which involves acquiring dynamic image data in terminal 30 and associating the detailed screen with the identification information of the operating machinery being inspected. The results of tag addition are displayed on display unit 32 of terminal 30. However, it is also possible to display a message indicating "acquired" on the detailed screen each time dynamic image data is acquired, or to provide a comprehensive overview of the correspondence between dynamic image data and the detailed screen at the end of the workflow. Furthermore, the display format is only one example and is not limited to these.

[0036] Adding tags Tags that associate dynamic image data acquired during the workflow with inspection results and information about the operating machinery are added to the terminal 30 and the server 20. Hereinafter, the former is referred to as "primary tag addition" and the latter as "secondary tag addition".

[0037] Figure 6 This is a concept map representing the addition of tags. A tag is added by the terminal 30 during the inspection of any machine 10 in accordance with the workflow. Specifically, information about the machine (machine identification information), information about the inspection (inspection association information), and dynamic image data 200 acquired during the workflow are correlated with each other. The machine identification information and the inspection association information will be explained later.

[0038] Secondary tagging involves the server 20 further classifying and establishing corresponding relationships based on the common attributes (machine attribute information) of multiple operating machines 10, which were initially tagged by the terminal 30. In other words, the information of individual operating machines 10 that have undergone initial tagging is aggregated through secondary tagging by the server 20. Thus, the workflow of each operating machine 10 and the information of the operating machines 10 that have undergone initial tagging by the terminal 30 are both subsequently tagged and accumulated on the server 20.

[0039] Figure 7 It is a graph representing the categories of labeled data. "Machinery identification information" includes information such as "machinery model" and "manufacturing number" used to identify each machine 10, and is stored in the controller of the machine 10. "Inspection association information" includes information such as "defects that become inspection targets," "content of inspection work," "inspection location," and "location where dynamic images are acquired," which are retained in each workflow. "Machinery attribute information" includes information related to the common attributes of the machine, such as "information of the customer who owns the machine (customer name, industry type, etc.)," ​​"region / country where the machine operates," "inspection and repair history of the machine (period, content, etc.)," ​​"operating environment of the machine (tropical, cold, high-altitude, flat, etc.)," ​​"operation content of the machine (civil engineering, dismantling, crushing, etc.)," ​​and "operational load of the machine (engine output, etc.)," ​​which are associated with the machine identification information and stored in the server 20.

[0040] The information mentioned above, which is associated through the first tag addition performed by the terminal 30, includes machine identification information as information of each operating machine 10 and inspection association information as information obtained as the result of inspection. The information associated through the second tag addition performed by the server 20 is information accumulated for multiple operating machines, namely machine attribute information.

[0041] In this way, the inspection results of each piece of machinery in its workflow are linked to dynamic image data (first-level tagging). Furthermore, the machinery is categorized and linked according to its attributes (second-level tagging). Therefore, when a malfunction occurs in a particular piece of machinery and an inspection is conducted, it is easy to retrieve dynamic image data from past inspections of other machinery of the same model, other machinery experiencing the same malfunction, or other machinery operating in the same region / country that shares attributes with the machinery being inspected. This extracted dynamic image data can then be referenced. Thus, efficient inspections can be achieved.

[0042] The tagged dynamic image data is stored on server 20 and can be retrieved and extracted by terminal 30. Specifically, if the aforementioned tag addition information is entered as a search condition on terminal 30 during or before the workflow begins, dynamic image data matching the search condition is extracted from the dynamic image data stored in server 20, and the extraction result is displayed on the display unit 32 of the terminal. The search condition can be any one of the "machine identification information" and "inspection association information" set in the first tag addition, or the "machine attribute information" set in the second tag addition, or a combination thereof.

[0043] By adding tags to the dynamic image data, it is possible to perform reverse queries during retrieval and extraction in similar cases. Furthermore, the display order can vary depending on the number of extraction results. For example, the display unit 32 of terminal 30 can selectively display markers indicating reference (e.g., "☆"). When the extracted dynamic image data serves as a reference for determining the cause of a problem, after the operator of terminal 30 selects a marker, the selected marker is associated with the dynamic image data and stored in the server's storage unit 22. Then, when retrieving and extracting dynamic image data, terminal 30 determines whether there is dynamic image data associated with a marker. If such data exists, the extraction results are displayed on display unit 32 in descending order of the number of times the markers of the dynamic image data have been selected. The number of displayed items can be arbitrarily set.

[0044] In the flowchart above, sensor values ​​are acquired by S5, but sometimes the location of a malfunction may be identified midway through the workflow. In this case, the workflow can be interrupted without any detailed screen transitions, and resumed after addressing the malfunction.

[0045] [Example 2] Figure 4 This is a block diagram illustrating the hardware configuration of the inspection workflow management system according to Embodiment 2 of the present invention. The difference between the system in Embodiment 2 and Embodiment 1 is that the maintenance management server 20 is equipped with a registration management department 25 for managing the "acquisition history of dynamic image data".

[0046] In Example 1, dynamic image data was acquired only for the parts deemed necessary by the executor of the workflow. However, even dynamic images of parts that are unnecessary during the inspection of the machine being inspected may sometimes be used as a reference during the inspection of other machines. Therefore, the acquisition of dynamic image data can also be based not only on the judgment of the executor of the workflow, but also on the display in the detailed screen.

[0047] Therefore, the registration management unit 25 manages the acquisition history (date and time) of the motion image data for each detailed screen. Furthermore, it can also, within any set period, refer to the number of times the motion image data for each detailed screen is acquired stored in the registration management unit 25; the more times a detailed screen is acquired, the higher the necessity of its motion image data is considered, thus urging the acquisition of motion image data.

[0048] The detailed screen includes both explanatory text messages and animated images, which facilitates a more flexible understanding of the inspection process. Therefore, for reference purposes regarding defect cases, there are areas where animated image data is particularly important. Thus, in this embodiment, the input / output unit 23 of the server 20 pre-specifies the animated images required for each detailed screen of the workflow. For example, in the display of the detailed screen, a pop-up message with text and an icon can be displayed indicating "animated image data required."

[0049] Figure 5 This is a flowchart illustrating the processes executed by the inspection workflow management system in Example 2. This embodiment involves the registration and management of dynamic image data. This embodiment is related to... Figure 3 The different processing steps in Example 1 are S51, S52, and S53. Therefore, the description of other steps is omitted.

[0050] In S51, the registration management unit 25 performs registration management. Specifically, the registration management unit 25 temporarily saves the acquired dynamic image data and displays it on the terminal 30, and stores it according to the final save instruction on the terminal 30 after the workflow is completed.

[0051] In S52, the processing unit 21 of the server issues an instruction to acquire data. If there is a data acquisition instruction in the workflow (yes), the process proceeds to S53 and acquires motion image data. The processing unit 21, for example, has a motion image presence / absence determination function, which determines whether the detailed screen in the workflow does not contain motion images. When switching to a detailed screen that does not contain motion images, a message indicating this is displayed. For example, a message "No motion image data" is displayed near the area where motion image data acquisition is specified. If there is no data acquisition instruction in the workflow (no), the process proceeds to S5 and acquires sensor values ​​for parts of the inspection object, etc. Through these processes, the acquisition of motion image data in the detailed screen of the workflow can be reliably determined.

[0052] Machine identification information is obtained directly from the operating machinery, while inspection-related information includes information input by service personnel. Therefore, there is a possibility of human input error. Furthermore, the dynamic image data acquired by the terminal may also be inappropriate. For example, if a detailed view contains a dynamic image of a different part than the object required for the dynamic image data, or if the object is not correctly captured, it will cause problems in establishing a correct association with the detailed view. Therefore, when dynamic image data is acquired, it is temporarily saved in the terminal (first registration). Then, the terminal notifies the user whether the registered dynamic image data is correctly associated with the information that has been tagged once, and after confirmation on the terminal, it is finally registered (second registration). This two-stage registration management, which confirms the accuracy between the dynamic image acquired by the user and the information associated with it in the terminal, ensures reliable registration of dynamic image data in the server.

[0053] [Variation Example] Finally, use Figure 8 Explain the variations. Figure 8 This is a block diagram representing the overall hardware configuration of the modified system. For example... Figure 8 As shown, in the modified example, server 20 has a retrieval unit 26 and a diagnostic unit 27. Server 20 in the modified example performs the same functions as the retrieval unit 36 ​​and diagnostic unit 37 of the terminal described above.

[0054] Furthermore, in the modified example, the terminal 30 does not have a retrieval unit and a diagnostic unit, but it can also be configured to have these functional units in the same way as in the above embodiment, so that either the server 20 or the terminal 30 can perform the retrieval or diagnostic.

[0055] The following effects can be achieved through the embodiments of the present invention described above.

[0056] (1) The inspection workflow management system of the present invention includes a server and a terminal connected to the server via a network. The server manages the inspection workflow that instructs the inspection procedures of the working machinery. The terminal has: a communication unit that connects to the working machinery as the inspection object and acquires the identification information of the working machinery; a display unit that displays the inspection workflow, the inspection workflow including an instruction to acquire dynamic image data of the inspection object part of the working machinery; an operation unit that inputs inspection association information corresponding to the inspection workflow; and a shooting unit that acquires dynamic image data of the inspection object part. The server has a storage unit that stores and establishes identification information. The system includes the mechanical attribute information of the associated operating machinery and the dynamic image data of the inspection target area obtained by the terminal. The terminal establishes an association between the identification information and the inspection association information based on the dynamic image data of the inspection target area obtained by the camera. The server further establishes an association between the mechanical attribute information and the dynamic image data of the inspection target area that has been associated and stores it in the storage unit. The terminal or server also has a retrieval unit. The retrieval unit extracts the dynamic image data of the inspection target area that has been associated with at least one piece of information, including the identification information, the inspection association information and the mechanical attribute information, based on the information input to the terminal.

[0057] Based on the above structure, tags are added to associate images, animations, and sounds (dynamic image data) related to past adverse events with inspection results and information about the operating machinery. These tags are used as keywords to retrieve and extract the associated dynamic image data. As a result, it is easy to use dynamic image data to determine whether the adverse events found during the inspection are the same as past adverse events, which can help shorten the time required to determine the cause of the adverse events.

[0058] (2) At least one of the terminal and the server also has a diagnostic unit. The diagnostic unit determines the cause of the malfunction of the inspection target part based on sensor values ​​indicating the operating status of the inspection target part of the working machinery. When the terminal acquires dynamic image data from the imaging unit, it displays the sensor value acquisition indication on the display unit. The diagnostic unit determines the cause of the malfunction of the inspection target part based on the sensor values ​​acquired by the terminal and displays the determination result on the display unit. Thus, for example, by displaying the determination result of the malfunction on the display unit, the user of the system can visually understand the cause of the malfunction of the working machinery.

[0059] (3) The server also has a registration management department, which stores the acquisition history of dynamic image data of the inspection object parts corresponding to the inspection workflow. When the terminal has the acquisition history of dynamic image data of the inspection object parts corresponding to the inspection workflow displayed on the display unit stored in the registration management department, the dynamic image data of the inspection object parts corresponding to the inspection workflow is displayed on a part of the display area of ​​the inspection workflow on the display unit. Thus, the user of the system can easily determine whether there is dynamic image data of the inspection object parts corresponding to the inspection workflow.

[0060] (4) The registration and management department calculates the number of times dynamic image data of the inspection object corresponding to the inspection workflow is acquired based on the acquisition history, and the terminal displays the acquisition count in the display area of ​​the inspection workflow. Thus, dynamic image data with a high acquisition count can be set as having high acquisition necessity and thus set a high priority.

[0061] (5) The terminal determines the display order of the extracted dynamic image data of the inspection target area in the display unit based on the reference level of the dynamic image data. As a result, the user of the system can clearly grasp the importance of the dynamic image data, which can help with maintenance inspection.

[0062] (6) The machine attribute information includes at least one of the following: information about the customer who owns the machine, information about the area where the machine operates, information about the machine's inspection and repair history, information about the machine's work content, information about the machine's operating environment, and information about the machine's workload. In this way, information related to the common attributes of multiple machines is included in the machine attribute information, thereby facilitating the retrieval and extraction of dynamic image data of similar malfunctions.

[0063] Furthermore, the present invention is not limited to the above embodiments and various modifications are possible. For example, the above embodiments have been described in detail for ease of understanding, and the present invention is not limited to having all the described configurations. Additionally, a portion of the configuration of one embodiment can be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment can be added to the configuration of one embodiment. Moreover, for a portion of the configuration of each embodiment, other configurations can be deleted, added, or replaced. Explanation of reference numerals in the attached figures

[0064] 10 Operating machinery, 20 Maintenance and management server, 24 Communication department, 25 Registration and management department, 30 Terminal, 31 Communication department, 32 Display department, 33 Photography department, 35 Operation department, 36 Retrieval department, 37 Diagnostic department.

Claims

1. An inspection workflow management system, comprising a server and terminals connected to the server via a network, the server managing an inspection workflow that instructs inspection procedures for operating machinery, characterized in that... The terminal has: A communication unit that connects to the operating machinery being inspected and acquires the identification information of the operating machinery; The display unit shows the inspection workflow, which includes instructions for acquiring dynamic image data of the inspection target parts of the operating machinery. An operation unit that inputs inspection-related information corresponding to the inspection workflow; and The camera unit that acquires dynamic image data of the inspected object area. The server has a storage unit that stores mechanical attribute information of the operating machinery associated with the identification information, as well as dynamic image data of the inspection target area obtained by the terminal. The terminal establishes an association between the recognition information and the inspection association information based on the dynamic image data of the inspection target area acquired by the camera unit. The server further associates the mechanical attribute information with the dynamic image data of the inspection object part that has been associated, and stores it in the storage unit. The terminal or the server further includes a retrieval unit, which extracts dynamic image data of the inspection object part that is associated with the at least one piece of information, namely the identification information, the inspection association information, and the mechanical attribute information, based on at least one piece of information input to the terminal.

2. The inspection workflow management system according to claim 1, characterized in that, At least one of the terminal and the server further includes a diagnostic unit, which determines the cause of any malfunction in the inspected part of the machine based on sensor values ​​representing the operating status of that part. When the terminal acquires the dynamic image data from the imaging unit, it displays the sensor value acquisition indication on the display unit. The diagnostic unit determines the cause of the malfunction of the inspection target area based on the sensor values ​​obtained by the terminal, and displays the determination result on the display unit.

3. The inspection workflow management system according to claim 1, characterized in that, The server also has a registration and management department, which stores the acquisition history of dynamic image data of the inspection object parts corresponding to the inspection workflow. When the registration management department stores the acquisition history of dynamic image data of the inspection object parts corresponding to the inspection workflow displayed in the display unit, the terminal displays the dynamic image data of the inspection object parts corresponding to the inspection workflow on a portion of the display area of ​​the inspection workflow in the display unit.

4. The inspection workflow management system according to claim 3, characterized in that, The registration and management department calculates the number of times the dynamic image data of the inspection object parts corresponding to the inspection workflow is acquired based on the acquisition history. The terminal displays the number of acquisitions in the display area of ​​the inspection workflow.

5. The inspection workflow management system according to claim 1, characterized in that, The terminal determines the display order of the extraction results of the dynamic image data of the inspection object in the display unit based on the reference level of the dynamic image data.

6. The inspection workflow management system according to claim 1, characterized in that, The machine attribute information includes at least one of the following: information about the customer who owns the machine, information about the area where the machine operates, information about the machine's inspection and repair history, information about the machine's work content, information about the machine's operating environment, and information about the machine's workload.

Images