Information management device, information management system, information management method, and program

Abstract

An information management device (100) is provided with: a data collection unit (170) that collects screen data for displaying information of each of a plurality of devices (200) on a display screen at a preset collection timing; a specifying unit that specifies another device (200) that satisfies a predetermined relationship with the device (200) that satisfies a predetermined condition; a screen data extraction unit that extracts screen data satisfying a preset rule from the screen data of the device (200) satisfying a condition and the screen data of the other device (200) identified by the identification unit from among the screen data collected by the data collection unit (170); and an output unit that outputs the screen data extracted by the screen data extraction unit.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to an information management apparatus, an information management system, an information management method, and a program. BACKGROUND

[0002] It is known that, in a production site, in order to analyze a cause of a failure, an anomaly, or the like of a production apparatus, an inspection apparatus, data indicating an operation state of the apparatus is collected and saved. For example, in Patent Literature 1, a display apparatus is disclosed which saves animation data obtained by imaging a necessary place or the like and state data of an apparatus in correspondence with each other, and displays the saved state data in correspondence with a reproduction period on a display screen of the saved animation data. According to this structure, it is possible to determine a time when the apparatus has failed from the state data, and it is helpful to find a cause of the failure by referring to the animation before and after the failure occurrence time.

[0003] PRIOR ART DOCUMENTS

[0004] PATENT LITERATURE

[0005] Patent Literature 1: Japanese Patent Application Publication No. 2005-056098 SUMMARY

[0006] PROBLEMS TO BE SOLVED BY THE INVENTION

[0007] Here, a failure occurring in a certain apparatus sometimes originates from other apparatuses in the same production line. Therefore, when a failure has occurred, it is preferable to analyze data not only of the apparatus in which the failure has occurred but also of other apparatuses. However, the display apparatus described in Patent Literature 1 saves data of only the connected apparatus. Therefore, in order to analyze data of a plurality of apparatuses using the technology of Patent Literature 1, it is necessary to determine a time when the failure has occurred, and to analyze the animation data and the state data before and after the time determined for each apparatus separately. Therefore, the work of data analysis is troublesome and time-consuming. Therefore, from the viewpoint of making it easier to find a cause of a failure, there is room for improvement.

[0008] The present disclosure was made in view of the above-described problems, and aims to provide an information management apparatus, an information management system, an information management method, and a program which can make it easier to find a cause of a failure.

[0009] MEANS FOR SOLVING THE PROBLEMS

[0010] To achieve the above objectives, the information management device of this disclosure includes: a data collection unit that collects screen data for displaying information of multiple production devices on a display screen at a preset collection time; a determination unit that determines other production devices that satisfy a preset relationship with production devices that satisfy preset conditions; a screen data extraction unit that extracts screen data that satisfies preset rules from the screen data collected by the data collection unit, the screen data of the production devices that satisfy the conditions, and the screen data of the other production devices determined by the determination unit; and an output unit that outputs the screen data extracted by the screen data extraction unit.

[0011] Invention Effects

[0012] According to this disclosure, other production units that satisfy a pre-defined relationship with the production unit that meets the conditions are automatically identified, and screen data that satisfies pre-defined rules is automatically extracted from the screen data of the production unit that meets the conditions and the identified production unit. By using the extracted screen data to check the status and changes of multiple production units, the cause of the fault can be identified across multiple production units. Therefore, the cause of the fault can be identified more easily. Attached Figure Description

[0013] Figure 1 This is a block diagram illustrating the structure of an information management system according to an embodiment of the present disclosure.

[0014] Figure 2 It is shown by Figure 1 The image shown is an example of screen data generated by the display.

[0015] Figure 3 It is shown Figure 1 The diagram shows an example of system structure information stored in the system structure information management department.

[0016] Figure 4 It is shown by Figure 1 The diagram shows an example of timing data generated by the output screen merging section.

[0017] Figure 5 It is shown by Figure 1 The image shown is an example of a display file generated by the file output unit, containing display screen data and back screen data.

[0018] Figure 6 This is a block diagram illustrating an example of the physical structure of an information management device according to an embodiment.

[0019] Figure 7 This is a flowchart of the collection and processing performed by the information management device in the implementation method.

[0020] Figure 8This is a flowchart of the backup process performed by the information management device in the implementation method.

[0021] Figure 9 It is shown by Figure 1 The diagram shows an example of the output data generated by the output screen merging section.

[0022] Figure 10 It is shown by Figure 1 The diagram shows another example of timing data generated by the output screen merging section.

[0023] Figure 11 It is shown by Figure 1 The diagram shows another example of timing data generated by the output screen merging section.

[0024] Figure 12 This is a block diagram illustrating the structure of a modified information management system. Detailed Implementation

[0025] The information management apparatus, information management system, information management method, and program according to embodiments of the present disclosure will now be described with reference to the accompanying drawings. Furthermore, identical or equivalent parts in the drawings will be labeled with the same reference numerals.

[0026] Applying the information management device of the embodiments of this disclosure to Figure 1 The example of information management system 1 shown is used for illustration.

[0027] As shown in the figure, the information management system 1 includes: multiple devices 200 installed on the production line 2; a display 300 that generates screen data to display the status of the devices 200, and uses the screen data to display the status of the devices 200 on the display panel; an information management device 100 that collects and stores the screen data generated by the display 300; a production management system 400 that manages the production status of the products produced by the production line 2; and a user terminal 500 used by a user. The information management device 100 is connected to the devices 200, the display 300, the production management system 400, and the user terminal 500 in a communicative manner via a network 600.

[0028] Device 200 is a production apparatus installed on production line 2, which processes workpieces to produce products while cooperating with other devices. The production apparatus includes, for example, processing devices, handling devices, conveying devices, inspection devices, and control devices. Processing and handling can be physical or chemical. Each device 200 operates according to various instructions supplied from display 300. Furthermore, device 200 outputs status data collected by sensors inherent to or installed on device 200, indicating the operating status of device 200, control data related to the control of device 200, and device data including error information indicating that a malfunction has occurred in device 200. Status data includes, for example, device 200 on / off status, operating / standby status, applied voltage, current, power, temperature, pressure, frequency, rotational speed, coordinate data, etc., and is arbitrary. Control data includes process information during execution, step information during execution, error information, and other information related to the control of device 200. Error messages indicate that some kind of adverse situation has occurred. They can be messages indicating failure in the processing of a workpiece and its contents, failure in the information processing of device 200 and its contents, or detection of its own faults or abnormalities.

[0029] The display 300 is a terminal device that includes a CPU (Central Processing Unit), memory, VRAM (Video Random Access Memory), display panel, graphics controller, etc. For ease of understanding, this embodiment shows an example of one display 300 installed on one device 200; however, one display 300 can be installed on multiple devices 200, or multiple displays 300 can be installed on one device 200. Furthermore, the display 300 can be built into the device 200, or it can be connected externally via wired or wireless means.

[0030] The display 300 generates an operation screen for the operator to input various instructions to the device 200, and displays it on the display panel.

[0031] In addition, the display 300 receives device data supplied from the device 200, generates a monitor screen indicating the status of the corresponding device 200, and displays it on the display panel. The operator can monitor the status of the device 200 by checking the monitor screen.

[0032] Reference Figure 2 Specific examples of monitor screen displays will be provided. Figure 2In the example shown, the CPU of display 300 generates four images, namely monitor screens 20a to 20d, in memory based on device data supplied from device 200, representing the status data of the corresponding device 200. The screen data of monitor screens 20a to 20d includes, for example, text data, vector image data, raster data, and table data, defining the screen, i.e., the image. For example, monitor screen 20a represents the working state of the corresponding device 200, such as on / off, working, preparing for work, and standby. Monitor screen 20b represents the status of the device 200's operating power supply, such as input voltage, input current, and power consumption. Monitor screens 20c and 20d similarly represent status data or control data, respectively. Monitor screens 20a to 20d are assigned image IDs (IDentifications) of 001 to 004. Furthermore, when referring to monitor screens 20a to 20d collectively in memory, they are sometimes called monitor screen 20. Additionally, the screen data of monitor screen 20 is sometimes referred to as screen data 20.

[0033] The CPU also converts the image data of the monitor screens 20a to 20d formed in the memory into dot pattern data, expands it on the VRAM, and generates monitor screens 21a to 21d with dot patterns. The CPU selects any one of the monitor screens 21a to 21d according to the user's instructions or the display switching sequence, and displays it on the physical screen 23. Figure 2 This example illustrates the state where monitor screen 21a is selected and displayed on physical screen 23 of the display panel. When referring collectively to monitor screens 21a to 21d on VRAM, it is sometimes called monitor screen 21, and sometimes the screen data of monitor screen 21 is called screen data 21. Screen data 20 and screen data 21 are both examples of screen data. There can be multiple physical screens 23. Furthermore, monitor screen 21 can be a color screen or a monochrome screen. In the case of a color screen, it is usually necessary to process the RGB three primary color dot pattern data on VRAM; however, this is a known fact and will not be discussed in detail below.

[0034] return Figure 1 The production management system 400 stores data related to the production status of the products, namely production management data. The production management data includes production quantity data of the products produced by production line 2, quality management data, operator names of each device 200, production methods, materials, and other operational data.

[0035] User terminal 500 is a computer, represented by industrial PCs (Personal Computers) and tablet terminals, that displays information output from information management device 100.

[0036] Information management device 100 is an edge computer installed at the production site. Information management device 100 collects and stores screen data 21 generated by display 300 at preset times. At the collection time, information management device 100 collects display screen data representing screen data 21 displayed on display 300 and back screen data representing screen data 21 that is not displayed. In the event of a device error indicating a malfunction of a device 200, information management device 100 extracts display screen data and back screen data before and after the error from display screen data storage unit 111 and back screen data storage unit 112, respectively, from the device 200 that malfunctioned and other devices 200 on the same production line 2 as the device 200 that malfunctioned. Information management device 100 takes the extracted display screen data and back screen data, merges them into a form that easily determines the cause of the error, and generates an output screen file. Information management device 100 outputs the generated output screen file to user terminal 500. The user displays the output screen file on user terminal 500 for error analysis. Furthermore, the information management device 100 is not limited to an edge computer installed at the production site; it can also be a cloud server, for example. Additionally, for example, the various functions of the information management device 100 can be implemented through a cloud server and an edge computer. Specifically, the cloud server can perform the functions of the screen data storage unit 110, the system structure information management unit 120, the output screen capture unit 130, the output screen merging unit 140, the output screen storage unit 150, the file output unit 160, the device information storage unit 180, and the production information storage unit 190, while the edge computer performs the functions of the data collection unit 170. Furthermore, not limited to situations where a device error occurs, for example, when it is determined that pre-set conditions such as the generation of defective products or the arrival of replacement periods for consumables have been met, or when an inspection instruction from an operator has been input, the information management device 100 can also acquire screen data 21 and generate an output screen file.

[0037] The information management device 100 includes: a screen data storage unit 110 that stores screen data 21 generated by the display 300; a system structure information management unit 120 that manages system structure information representing the device 200 constituting the production line 2; an output screen capture unit 130 that determines the screen data 21 of the output object from the screen data storage unit 110 and copies it; an output screen merging unit 140 that merges the screen data 21 copied by the output screen capture unit 130 to generate a display screen file; an output screen storage unit 150 that stores the display screen file generated by the output screen merging unit 140; a file output unit 160 that outputs the display screen file to the user terminal 500; a data collection unit 170 that inputs and outputs data with the device 200, the display 300, and the production management system 400; a device information storage unit 180 that stores device data representing the status of the device 200; and a production information storage unit 190 that stores data related to the production status of the products, i.e., production management data.

[0038] The screen data storage unit 110 includes: a display screen data storage unit 111, which stores screen data 21, i.e., display screen data, from among the multiple screen data 21 generated by the display 300 that are displayed on the physical screen 23 of the display panel at the time of collection; and a rear screen data storage unit 112, which stores screen data 21 that are not displayed at the time of collection, i.e., rear screen data. The screen data storage unit 110 is an example of a data storage unit.

[0039] The display screen data storage unit 111 stores display screen data. Display screen data is image data 21 of the displayed object, created on the VRAM of the display 300 and displayed on the physical screen 23 of the display panel at preset collection times such as every 1 second, every 10 seconds, and every 1 minute. Display screen data can be, for example, hard copies of the image data 21 displayed on the physical screen 23 converted into image formats such as JPEG, RGB, and BMP; data obtained by packaging the image data 21 displayed on the physical screen 23 at each collection time; and data managed according to time to reproduce the image data 21 displayed on the physical screen 23 at each collection time. Specifically, the data collection unit 170 collects the image data 21 displayed on the physical screen 23 of the display panel from the display 300 at preset collection times. The data collection unit 170 assigns the collected screen data 21 a device ID for uniquely identifying the device 200 connected to the display 300, a screen ID for uniquely identifying which screen data 21 it is, the date and time the screen data 21 was collected, and identification information for identifying that the screen data 21 is display screen data, and then stores it in the display screen data storage unit 111.

[0040] The rear screen data storage unit 112 stores rear screen data. Rear screen data is screen data 21 that can be displayed on the physical screen 23 by selection according to user instructions or display switching order, and is screen data 21 that can reproduce the monitor screen 21 displayed on the physical screen 23. Rear screen data can be, for example, a hard copy of screen data 21 that is not the object of display, which is virtually displayed on the physical screen 23 and converted into image formats such as JPEG, RGB, and BMP; data obtained by packaging the screen data 21 that is not the object of display at each collection time that is displayed on the physical screen 23; or data of the screen data 21 that is not the object of display at each collection time, managed according to time for reproducing the screen data 21 that is not the object of display at each collection time. Specifically, the data collection unit 170 collects the screen data 21 that is not the object of display from the display 300 at the same collection time as the time for collecting display screen data. The rear screen data storage unit 112 assigns the collected screen data 21 to the device ID of the device 200 connected to the display 300, the screen ID, the date and time of the collection of the rear screen data, and identification information for identifying that the screen data 21 is rear screen data, and stores it in the rear screen data storage unit 112.

[0041] The system structure information management unit 120 stores system structure information representing the devices 200 constituting production line 2. For example... Figure 3 As illustrated, the system structure information includes a system ID for uniquely identifying production line 2, a "system name" representing the name of production line 2, a device ID for uniquely identifying the device 200 constituting the production line, and a "device name" representing the name of device 200. In the illustrated example, device A with device ID "A001", device B with device ID "B001", and device C with device ID "C001" are shown as devices 200 constituting production line 2, which has a system ID of "PL1" and a system name of "production line 1".

[0042] In the event of a device error, the output screen capture unit 130 performs capture processing to determine and copy the screen data 21 before and after the error occurs. Specifically, the output screen capture unit 130 is pre-set with rules related to the period for extracting the screen data 21 used for the output target, such as extracting screen data 21 for 5 minutes before and after the error occurs. In the event of a device error, the output screen capture unit 130 extracts the screen data 21 of the device 200 that experienced the device error, collected within 5 minutes before and after the time of the error from the screen data storage unit 110, and copies it. Furthermore, the output screen capture unit 130 refers to... Figure 3The illustrated system structure information identifies other devices 200 located on the same production line 2 as the device 200 that experienced the device error. The output screen capture unit 130 extracts and copies screen data 21 collected from each of the identified other devices 200 within 5 minutes before and after the time of the device error. The output screen capture unit 130 sends the copied screen data 21 to the output screen merging unit 140. Furthermore, the output screen capture unit 130 is an example of a determination unit, a screen data extraction unit, and a structure information acquisition unit.

[0043] return Figure 1 The output screen merging unit 140 merges the screen data 21 sent by the output screen capture unit 130 to generate a display screen file. For example, ... Figure 4 As illustrated, the output screen merging unit 140 adjusts the size of the display screen data and back screen data collected at the same collection time to half in both dimensions, combines two in each dimension, and merges them to generate a single full-size image data 31. The output screen merging unit 140 generates timing data 30 for each device 200, arranging the image data 31 in chronological order before and after the error occurs. In the illustrated example, the output screen merging unit 140 merges the screen data 21 of screen IDs 001, 002, 003, and 004, representing the status of device ID "A001," collected every minute within 5 minutes before and after the error occurrence date and time "October 10, 2023, 13:00," generating image data 31 respectively, and arranges them in chronological order to generate timing data 30. The output screen merging unit 140 generates timing data 30 for all devices 200 within the production line 2 determined by the output screen capture unit 130. Next, as... Figure 5 As illustrated, the output screen merging unit 140 aggregates the timing data 30 of each device 200 into a single file on a production line 2 basis, generating a display screen file. Furthermore, the method for merging the screen data is arbitrary. For example, four full-size screen data 21s can be combined and merged in one direction to form a large-size image data 31. The output screen merging unit 140 is an example of an output data generation unit.

[0044] return Figure 1 The output screen storage unit 150 stores the display screen files generated by the output screen merging unit 140. Specifically, the output screen storage unit 150 generates a folder and stores the display screen files in the generated folder, wherein the folder name contains a string such as the device ID of the device 200 that caused the error and the date and time of the error.

[0045] The file output unit 160 outputs the display screen file stored in the output screen storage unit 150 to the user terminal 500 via the network 600. The user displays the display screen file output by the file output unit 160 on the screen of the user terminal 500, and analyzes the content of the screen data 21 generated by the display 300 connected to each device 200 before and after the device error occurred. The file output unit 160 is an example of an output unit.

[0046] The data collection unit 170 performs data input and output between the device 200, the display 300, and the production management system 400. Specifically, the data collection unit 170 acquires device data indicating the status of the device 200 from the device 200 at preset collection times, and stores it in the device information storage unit 180. Furthermore, the data collection unit 170 collects display screen data and back screen data from the display 300 at preset collection times, and stores them in the display screen data storage unit 111 and the back screen data storage unit 112, respectively. Additionally, the data collection unit 170 acquires production management data related to the production status of the products from the production management system 400 at preset collection times, and stores it in the production information storage unit 190.

[0047] The device information storage unit 180 stores device data indicating the status of the device 200. The device data includes status data indicating the operating status of the device 200, control data related to the control of the device 200, and error information indicating that a malfunction has occurred in the device 200. Specifically, the data collection unit 170 collects device data from each device 200 via the network 600 at preset intervals, and stores it in the device information storage unit 180.

[0048] The production information storage unit 190 stores production management data for the products produced by each production line 2. This production management data relates to the production status of the products and includes production quantity data, quality management data, operator names for each device 200, production methods, materials, and other operational data. Specifically, the data collection unit 170 collects production management data from the production management system 400 via the network 600 according to a pre-set schedule, and then stores this data in the production information storage unit 190.

[0049] Next, refer to Figure 6The physical structure of the information management device 100 will be described. The information management device 100 includes a processor 11 that performs program-based processing, a RAM (Random Access Memory) 12 that is volatile memory, a ROM (Read Only Memory) 13 that is non-volatile memory, a storage unit 14 that stores data, an input unit 15 that accepts information input, a display unit 16 that visualizes and displays information, and a communication unit 17 that transmits and receives information. These components are connected via an internal bus 99.

[0050] The processor 11 includes a CPU (Central Processing Unit). The processor 11 reads the program stored in the storage unit 14 into the RAM 12 and executes it, thereby performing various processes. As the main functions provided by the program, the processor 11 performs the processing of the output screen capture unit 130 and the output screen merging unit 140.

[0051] RAM12 is used as the CPU's working area. ROM13 stores control programs executed by the CPU for the basic operations of the information management device 100, BIOS (Basic Input Output System), etc.

[0052] Storage unit 14 has a hard disk drive that stores the program executed by the CPU and various data used during program execution. Storage unit 14 functions as screen data storage unit 110, system structure information management unit 120, output screen storage unit 150, device information storage unit 180, and production information storage unit 190.

[0053] The input unit 15 is a user interface with a keyboard, mouse, etc. The display unit 16 is a display device such as a liquid crystal display or an organic EL (Electro Luminescence) display that visualizes and displays information.

[0054] The communication unit 17 is a network terminal device or wireless communication device connected to a network, and a serial interface or LAN interface connected to them. The communication unit 17 receives signals from the outside and outputs the data indicated by the signals to the processor 11. The communication unit 17 functions as a file output unit 160 and a data collection unit 170.

[0055] Next, the operation of the information management device 100 having the above structure will be explained.

[0056] As a prerequisite, the devices 200 of production line 2 jointly process workpieces and manufacture products. During this period, the display 300 repeatedly performs the following actions: acquiring device data supplied from device 200, generating...Figure 2 The screen data 21 shown is displayed on the physical screen 23 of the display panel, which is the selected screen data 21. The operator can determine the operating status of the device 200 and the presence or absence of abnormalities by referring to the screen data 21 displayed on the physical screen 23.

[0057] During operation of production line 2, the information management device 100 collects and saves display screen data and back view data at pre-set collection times. In the event of a device error, the information management device 100 identifies the erroneous device 200 and other devices 200 on the same production line 2 as the erroneous device 200, and extracts their respective display screen data and back view data before and after the error occurred. The information management device 100 performs the following backup process: it merges the display screen data and back view data collected at the same time to generate image data 31, and generates and saves timing data 30 for each device 200, arranged in chronological order.

[0058] Here, firstly, refer to Figure 7 The information management device 100 collects and processes information.

[0059] When a user requests to start data collection and processing via the input section 15, the information management device 100 begins processing. Data collection and processing can also begin automatically simultaneously with the start of work on production line 2.

[0060] The data collection unit 170 determines whether it is a collection opportunity (step S11). Specifically, the data collection unit 170 determines whether a preset time has elapsed since the moment the collection processing start request was received or since the last collection opportunity. If the data collection unit 170 determines that the preset time has elapsed, it determines that it is a collection opportunity (step S11: Yes); if it determines that the preset time has not elapsed, it determines that it is not a collection opportunity (step S11: No).

[0061] When the data collection unit 170 determines that it is time to collect data (step S11: Yes), it collects screen data 21, device data, and production management data respectively (step S12). Specifically, the data collection unit 170 collects... Figure 2 The screen data 21a, 21b, 21c, 21d, ... are written into the VRAM of each of the illustrated displays 300. Figure 2In this example, the data collection unit 170 collects screen data 21a of screen ID "001" displayed on the physical screen 23 of the display panel as display screen data, and collects screen data 21b, 21c, 21d, ... of other screen IDs "002", "003", "004", ... as back screen data. Furthermore, the data collection unit 170 collects device data containing status data indicating the status of each device 200 from each device 200, and collects data related to the production status of the produced goods, i.e., production management data, from the production management system 400.

[0062] Next, the data collection unit 170 assigns attribute information to each piece of data collected in step S12 and saves it (step S13). Specifically, the data collection unit 170 assigns the collected screen data 21 with device ID for uniquely identifying the device 200 connected to the display 300, screen ID for uniquely identifying which screen data 21 it is, the date and time the screen data 21 was collected, and identification information for identifying whether it is screen data 21 displayed in the physical screen 23 of the display panel. The data collection unit 170 causes the display screen data storage unit 111 to store the screen data 21 that has been assigned identification information indicating that it is screen data 21 displayed in the physical screen 23 of the display panel, and causes the rear screen data storage unit 112 to store the screen data 21 that has been assigned identification information indicating that it is not a display object.

[0063] Furthermore, the data collection unit 170 assigns a device ID indicating which device 200 the collected device data belongs to, as well as the collection date and time, to the device information storage unit 180 for storage. Additionally, the data collection unit 170 assigns a production line ID or device ID indicating which production line 2 or device 200 the collected production management data belongs to, as well as the collection date and time, to the production information storage unit 190 for storage.

[0064] Next, the data collection unit 170 determines whether the end conditions of the collection process are met (step S14). Specifically, if the data collection unit 170 determines that the preset end conditions are met, such as receiving a signal indicating to stop the collection process, the elapsed time of a preset collection schedule, or the number of collection attempts exceeding a preset limit (step S14: Yes), the process ends. On the other hand, if the end conditions are not met (step S14: No), the process returns to step S11 and repeats the process.

[0065] Next, refer to Figure 8 The backup process of the information management device 100 is explained.

[0066] In the system structure information management unit 120, system structure information representing the devices 200 constituting the production line 2 is pre-stored based on user input. For example... Figure 3 As illustrated, the system structure information includes a system ID for uniquely identifying production line 2, a "system name" representing the name of production line 2, a device ID for uniquely identifying the device 200 constituting the production line, and a "device name" representing the name of device 200. When a user constructs a new production line 2 or changes the structure of an existing production line 2, the system structure information is created and stored by the system structure information management unit 120.

[0067] The output screen capture unit 130 determines whether an error message has been received (step S21). Specifically, the output screen capture unit 130 determines whether the device data collected in step S12 contains an error message. Inputs from operator fault or anomaly detection, inputs from detection signals from other sensors, etc., may also be included in the determination criteria.

[0068] Next, when the output screen capture unit 130 determines that an error message has been received (step S21: Yes), it identifies the device 200 that experienced the error and other devices 200 installed on the same production line 2 as the device 200 that experienced the error (step S22). Specifically, the output screen capture unit 130 refers to... Figure 3 Based on the illustrated system structure information, each device 200 is identified. For example, if an error message is received from device A, the output screen capture unit 130 identifies device A as the device 200 where the error occurred. Next, based on the system structure information, it is determined that device A is located on production line 2 with system ID "PL1" and system name "production line 1", and other devices 200 located on production line 2 are identified as devices B and C.

[0069] return Figure 8 Next, the output screen capture unit 130 extracts the screen data 21 of each device 200 before and after the error occurred, as determined in step S22 (step S23). Specifically, for example, the output screen capture unit 130 pre-sets rules related to the extraction period, such as extracting screen data for 1 minute, 5 minutes, and 10 minutes before and after the error occurred. The output screen capture unit 130 determines the date and time of the error based on the received error information. The output screen capture unit 130 extracts the display screen data and back screen data of each device 200 determined in step S22, i.e., the display screen data and back screen data that satisfy the extraction rules, from the display screen data storage unit 111 and the back screen data storage unit 112, respectively.

[0070] Next, the output screen capture unit 130 copies the display screen data and back screen data extracted in step S23 (step S24). The output screen capture unit 130 sends the copied display screen data and back screen data to the output screen merging unit 140.

[0071] Next, the output screen merging unit 140 generates a display screen file by merging the display screen data and back screen data copied in step S24, and stores it in the output screen storage unit 150 (step S25). Specifically, as follows Figure 4 As illustrated, the output screen merging unit 140 generates image data 31 by merging the display screen data and back screen data collected at the same collection time, and generates timing data 30 for each device 200 arranged in chronological order before and after the error occurs. The output screen merging unit 140 generates timing data 30 for all devices 200 in the production line 2 as determined by the output screen capture unit 130. Next, as... Figure 5 As illustrated, the output screen merging unit 140 combines the timing data 30 of each device 200 into a single file to generate a display screen file.

[0072] return Figure 8 Next, the file output unit 160 outputs the display screen file generated in step S25 to the user terminal 500 (step S26), ending the process. The user causes the user terminal 500 to display the display screen file output by the file output unit 160, and analyzes the information of the screen data 21 before and after the error occurred in the device 200 that malfunctioned and other devices 200 set on the same production line 2 as the device 200 that malfunctioned.

[0073] On the other hand, returning to step S21, when the output screen capture unit 130 determines that no error information has been received (step S21: No), it returns to step S21 to determine whether an error information has been received.

[0074] As described above, according to the information management device 100, when a device 200 malfunctions, it extracts the screen data 21 of the malfunctioning device 200 and other devices 200 on the same production line 2 as the malfunctioning device 200 before and after the malfunction occurs from the pre-collected screen data 21. The information management device 100 generates timing data 30 in a form that easily identifies the cause of the error based on the extracted screen data 21. Therefore, the user can confirm the changes in the displayed screen when the error occurred in chronological order. Thus, the user does not need to perform operations such as selecting the device 200 to be analyzed from the saved screen data 21, or extracting data from a specific time of the selected device 200, making it easier to identify the cause of the malfunction.

[0075] In addition to the display screen data shown on the physical screen 23 of the display panel, the information management device 100 also collects and stores the rear screen data. Therefore, even if a screen is not actually displayed on the display panel, the user can check it in chronological order. Thus, the user can utilize information not displayed on the physical screen 23 of the display panel in the analysis, and therefore, can more accurately determine the cause of the fault.

[0076] As long as the spirit of this disclosure is not departed from, the structures described in the above embodiments can be selected or replaced, or other structures can be appropriately modified.

[0077] In this implementation, processing is assumed to be performed by a single information management device 100; however, the system architecture is arbitrary. For example, the functions of the information management device 100 can also be implemented using multiple devices such as cloud servers and edge computers. Specifically, as... Figure 12 As illustrated, the cloud server 700 may perform the functions of the screen data storage unit 110, system structure information management unit 120, output screen capture unit 130, output screen merging unit 140, output screen storage unit 150, file output unit 160, device information storage unit 180, and production information storage unit 190 of the information management device 100, while the edge computer 800 performs the functions of the data collection unit 170 of the information management device 100. In the case of this information management system 1A, the cloud server 700 replaces the information management device 100 and connects to the user terminal 500. The edge computer 800 performs... Figure 7 The data collection process shown collects device data from device 200, display screen data and rear screen data from display 300, and production management data from production management system 400 at pre-set collection times, and sends them to cloud server 700. Cloud server 700 then executes... Figure 8 In the backup process steps S21 to S24, in the event of a device error, the screen data 21 before and after the error occurs is extracted and copied from the device 200 that malfunctioned and other devices 200 on the same production line 2 as the malfunctioning device 200. Then, the cloud server 700 executes the processing steps S25 and S26 to generate and save the display screen file. The user can then display the generated display screen file on the user terminal 500.

[0078] Furthermore, for example, the cloud server 700 can also perform the functions of the output screen merging unit 140, output screen storage unit 150, and file output unit 160 of the information management device 100. In the event of a device error, the information management device 100 extracts the screen data 21 of the erroneous device 200 and other devices 200 on the same production line 2 as the erroneous device 200 before and after the error, and sends them to the cloud server 700. Then, the cloud server 700 executes steps S25 and S26 to generate a display screen file, which is then output to the user terminal 500.

[0079] Alternatively, for example, the cloud server 700 can also perform the functions of the output screen storage unit 150 and the file output unit 160. In this case, the information management device 100 performs steps S21 to S25, generates a display screen file, and outputs the generated display screen file to the cloud server 700, where the output screen storage unit 150 of the cloud server 700 stores it. Then, the file output unit 160 of the cloud server 700 outputs the display screen file to the user terminal 500.

[0080] Furthermore, in the above embodiment, it is assumed that in step S22, a device 200 located on the same production line 2 as the device 200 that experienced the error is identified. However, the relationship with the device 200 that experienced the error is not limited to this; other devices 200 operating as a single system can be identified. In this case, Figure 3 The system structure information shown can store the structure of the device 200 that operates as a system.

[0081] Furthermore, in the above embodiment, the capture process is set to be performed when an error message is received from the device 200, but it is not limited to this. For example, the capture process may also be performed when it is determined that a defective product has occurred, or when a consumable has reached its replacement period. Specifically, the information management device 100 may perform the capture process in step S21 when it determines that the production management data collected from the production management system 400 contains information indicating that a defective product has occurred, and when it determines that the value indicating the remaining amount of consumables in the device data collected from the device 200 is below a threshold.

[0082] In addition, such as Figure 9As illustrated, the output screen merging unit 140 can also generate output data 50 that maps timing data 30 to device data 40. In this case, in step S25, the output screen merging unit 140 uses the device ID and collection date and time as keywords to retrieve the device data 40 corresponding to the image data 31 generated by the output screen merging unit 140 from the device information storage unit 180, and maps it to the image data 31. The device data 40 is, for example, the device data of a PLC, which can confirm the operating state of the device 200 in the event of a fault. Therefore, by comparing the timing data 30 obtained by arranging the screen data 21 in chronological order with the device data 40, it is easier to analyze the cause of the error. That is, the cause can be estimated based on the timing data 30, and the hypothesis can be verified based on the device data 40. In addition, the device data 40 is an example of device display data.

[0083] In addition, such as Figure 4 As illustrated, the output screen merging unit 140 generates timing data 30, which is composed of image data 31 arranged in chronological order before and after the error occurs. This image data 31 is obtained by merging screen data 21 collected at the same collection time, but is not limited to this. For example, such as Figure 10 As illustrated, timing data 30A can also be generated by arranging the frame data 21 collected at the same device ID and time according to the timing sequence, based on each frame ID. Furthermore, for example, it is also possible to... Figure 11 As illustrated, timing data 30B is generated for each collection time, and the timing data 30B displays image data 31 obtained by merging the image data 21 collected at the same collection time in one screen.

[0084] Furthermore, in the above embodiment, the data collection unit 170 is configured to collect screen data, device data, and production management data at a preset time interval, but it is not limited to this. For example, it can also collect various data by any rules such as collecting data every minute during normal operation or collecting data every 10 seconds within a certain period after receiving an error message.

[0085] Furthermore, in the above embodiment, an example is shown where, when a device 200 malfunctions, such as a fault or abnormality, the screen data 21 of all devices 200 configured on the same production line 2 is checked. This is not a limitation. It is also possible to designate a device 200 as the target for collecting screen data for each device 200, different from the production line. For example, screen data of a specific device 200 pre-defined within the same production line where a fault or abnormality was detected can be collected. Furthermore, screen data of a specific device 200 pre-defined outside the same production line where a fault or abnormality was detected can also be collected. The range of screen data to be collected can be set for each device 200. In these cases, the information set in the system structure information management unit 120 can be appropriately configured.

[0086] Furthermore, in the above embodiment, the information management device 100 collects the screen data 21, i.e., dot pattern data, on the VRAM of the display 300 and stores it in the screen data storage unit 110. However, it may also collect the screen data 20 on the memory of the display 300. The screen data 20 includes, for example, text data, vector data, table data, etc. By being able to access the screen data 20 stored in the screen data storage unit 110 directly or indirectly from the user terminal 500, it is also possible to retrieve the screen data 20. The retrieval function of the information management device 100 can also be used.

[0087] Furthermore, the information management device 100 can be implemented using a conventional computer system without relying on a dedicated device. For example, the programs for implementing the various functions in the information management device 100 can be stored on computer-readable recording media such as CD-ROM (Compact Disc Read Only Memory) or DVD-ROM (Digital Versatile Disc Read Only Memory) and distributed, and then installed on a computer, thereby constructing a computer capable of implementing the aforementioned functions.

[0088] Furthermore, in cases where functions are implemented through a sharing of the OS (Operating System) and applications, or through collaboration between the OS and applications, it is also possible to store only the applications on the recording medium.

[0089] Furthermore, this disclosure can be implemented and modified in various ways without departing from the broad spirit and scope of this disclosure. Moreover, the above-described embodiments are illustrative of this disclosure and do not limit its scope. That is, the scope of this disclosure is not shown by the embodiments, but by the claims. Furthermore, various modifications implemented within the scope of the claims and their equivalents are considered to be within the scope of this disclosure.

[0090] Label Explanation

[0091] 1. 1A: Information Management System; 2. Production Line; 11: Processor; 12: RAM; 13: ROM; 14: Storage Unit; 15: Input Unit; 16: Display Unit; 17: Communication Unit; 99: Internal Bus; 20, 20a, 20b, 20c, 20d, 21, 21a, 21b, 21c, 21d: Monitor Screen; 23: Physical Screen; 30, 30A, 30B: Timing Data; 31: Image Data; 40: Device Data; 50: Output Data; 100: Information Management Device; 110: Screen Data Storage Unit; 111: Display Screen Data Storage Unit; 112: Rear Screen Data Storage Unit; 120: System Structure Information Management Unit; 130: Output Screen Capture Unit; 140: Output Screen Merging Unit; 150: Output Screen Storage Unit; 160: File Output Unit; 170: Data Collection Unit; 180: Device Information Storage Unit; 190: Production Information Storage Unit; 200: Device; 300: Display; 400: Production Management System; 500: User Terminal; 600: Network; 700: Cloud Server; 800: Edge Computer.

Claims

1. An information management apparatus having: a data collection section that collects screen data for causing a display screen to display information of each of a plurality of production devices at a collection timing set in advance; a determination section that determines other production devices that satisfy a predetermined relationship with a production device that satisfies a predetermined condition; a screen data extraction section that extracts screen data that satisfies a predetermined rule from the screen data of each of the production device that satisfies the condition and the other production devices determined by the determination section, in the screen data collected by the data collection section; and an output section that outputs the screen data extracted by the screen data extraction section.

2. The information management apparatus according to claim 1, wherein the information management apparatus further has a structure information acquisition section that acquires structure information indicating a structure of a production line constituted by production devices, and the determination section determines, as the other production devices that satisfy the relationship, other production devices of a production line to which the production device that satisfies the condition belongs, based on the structure information acquired by the structure information acquisition section.

3. The information management apparatus according to claim 1 or 2, wherein the data collection section further collects device data indicating a state of the production device, and the determination section determines, as the production device that satisfies the condition, a production device that has transmitted the device data including error information of the production device, in a case where the device data is received.

4. The information management apparatus according to any one of claims 1 to 3, wherein the screen data extraction section extracts, as the screen data that satisfies the rule, the screen data of a period set in advance from a date and time at which it is determined that there is the production device that satisfies the condition.

5. The information management apparatus according to any one of claims 1 to 4, wherein the data collection section collects, as screen data, display screen data that is screen data displayed on the display screen at the collection timing and back screen data that is screen data that is not a display target at the collection timing, respectively.

6. The information management apparatus according to any one of claims 1 to 5, wherein the information management apparatus further has an output data generation section that generates, for each of the production devices, time series data in which the screen data extracted by the screen data extraction section is arranged in a time series order.

7. The information management apparatus according to claim 6, wherein the output data generation section generates image data obtained by combining display screen data that is screen data displayed on the display screen at the collection timing and back screen data that is screen data that is not a display target at the collection timing, and generates time series data in which the generated image data is arranged in a time series order.

8. The information management apparatus according to claim 6 or 7, wherein ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ The information management apparatus further has a data storage section that stores the screen data collected by the data collection section and device data indicating the state of the production apparatus in correspondence with each other, The output data generation section further generates device display data that displays the device data corresponding to each of the screen data, and outputs output data containing the time-series data generated by the output data generation section and the device display data.

9. The information management apparatus according to claim 8, wherein The output data is data that displays the time-series data and the device display data in one display screen.

10. The information management apparatus according to any one of claims 1 to 9, wherein The information management apparatus is a cloud server or an edge computer provided at a production site.

11. An information management system having an edge computer and a cloud server, wherein The edge computer has a data collection section that collects screen data for causing a display screen to display information of each of a plurality of production apparatuses at a predetermined collection timing, The cloud server has: a determination section that determines other production apparatuses that satisfy a predetermined relationship with a production apparatus that satisfies a predetermined condition; a screen data extraction section that extracts screen data that satisfies a predetermined rule from the screen data of the production apparatus that satisfies the condition and the other production apparatuses determined by the determination section each; and an output section that outputs the screen data extracted by the screen data extraction section.

12. An information management system having: the information management apparatus according to any one of claims 1 to 10; a plurality of displays that display information of a production apparatus in each display screen using screen data for causing a display screen to display information of the production apparatus; and a production management system that outputs production management data to the information management apparatus, the production management data being data indicating a production status of a production article produced by the production apparatus.

13. An information management method including the steps of: collecting screen data for causing a display screen to display information of each of a plurality of production apparatuses at a predetermined collection timing; determining other production apparatuses that satisfy a predetermined relationship with a production apparatus that satisfies a predetermined condition; and extracting screen data that satisfies a predetermined rule from the screen data of the production apparatus that satisfies the condition and the other production apparatuses determined each.

14. A program that causes a computer to execute the processes of: collecting screen data for causing a display screen to display information of each of a plurality of production apparatuses at a predetermined collection timing; determining other production apparatuses that satisfy a predetermined relationship with a production apparatus that satisfies a predetermined condition; and extracting screen data that satisfies a predetermined rule from the screen data of the production apparatus that satisfies the condition and the other production apparatuses determined each.

Images