JP7734337B2 - Management method, display method and management device - Google Patents

Description

This disclosure relates to a management method, display method, and management device for managing event information related to events that occur in a component mounter.

Patent Document 1 discloses an external area monitoring system for a component mounter that includes an external monitoring camera that captures images of the external work area of the component mounter, a display device that displays images captured by the external monitoring camera, and a recording device that records the images captured by the external monitoring camera.

International Publication No. 2018/055754

In order to prevent a decline in the availability rate of component mounters, it is desirable to shorten the time required to identify the cause of an event that occurs on a component mounter. With the system disclosed in Patent Document 1, if the cause is not visible in the image captured by the external monitoring camera, it is difficult to shorten the time required to identify the cause, so there is room for improvement.

This disclosure therefore provides a management method, display method, and management device that can more reliably reduce the time required to identify the cause of an event that occurs on a component mounter.

A management method according to one aspect of the present disclosure is a management method for managing event information related to an event that has occurred in a mounter, which acquires event occurrence information including information indicating the occurrence of the event, acquires video data capturing images of the surroundings of the mounter between the occurrence time indicating the time the event occurred and a time one hour before the occurrence time, acquires at least one of work record data that records work performed on the mounter between the occurrence time and a time two hours after the occurrence time, and work record data including event identification information issued as a trigger for the occurrence of the event, and associates the event occurrence information with the video data and the work record data and stores them as the event information.

A display method according to one aspect of the present disclosure displays the event information stored by the above-described management method, by displaying a list based on one or more pieces of event occurrence information, acquiring a selection of one event from the list, and displaying an image based on the video data and work record data associated with the acquired event.

A management device according to one aspect of the present disclosure manages event information related to an event that has occurred in a mounter, and includes: a first acquisition unit that acquires event occurrence information including information indicating the occurrence of the event; a second acquisition unit that acquires video data captured around the mounter between the occurrence time indicating the time the event occurred and a time one hour before the occurrence time; a third acquisition unit that acquires at least one of work record data that records work performed on the mounter between the occurrence time and a time two hours after the occurrence time, and work record data that includes event identification information issued as a trigger when the event occurred; and an association unit that associates the event occurrence information with the video data and the work record data and stores the event information.

The management method according to one aspect of the present disclosure can more reliably reduce the time required to identify the cause of an event that occurs in a component mounter.

FIG. 1 is a diagram showing the overall configuration of a management system according to an embodiment. FIG. 2 is a block diagram illustrating a functional configuration of an in-facility data collection unit according to the embodiment. FIG. 3 is a block diagram illustrating a functional configuration of the outside-facility data collection unit according to the embodiment. FIG. 4 is a block diagram illustrating a functional configuration of a data synchronization management unit according to the embodiment. FIG. 5 is a diagram for explaining the installation positions of the surveillance cameras according to the embodiment. FIG. 6 is a first sequence diagram illustrating the operation of the management system according to the embodiment. FIG. 7 is a diagram showing a relationship between an event and video data and work record data associated with the event, according to the embodiment. FIG. 8 is a second sequence diagram illustrating the operation of the management system according to the embodiment. FIG. 9 is a diagram showing an example of display of event information according to the embodiment. FIG. 10 is a sequence diagram illustrating the operation of the management system according to the modified example of the embodiment. FIG. 11 is a diagram showing the relationship between an event and the video data and work record data associated with the event, according to a modification of the embodiment. FIG. 12 is a diagram showing an example of a registration screen for registering a work record according to the modification of the embodiment. FIG. 13 is a diagram illustrating a data structure of event information stored in a seventh storage unit according to the modification of the embodiment.

A management method according to one aspect of the present disclosure is a management method for managing event information related to an event that has occurred in a mounter, which acquires event occurrence information including information indicating the occurrence of the event, acquires video data capturing images of the surroundings of the mounter between the occurrence time indicating the time the event occurred and a time one hour before the occurrence time, acquires at least one of work record data that records work performed on the mounter between the occurrence time and a time two hours after the occurrence time, and work record data including event identification information issued as a trigger for the occurrence of the event, and associates the event occurrence information with the video data and the work record data and stores them as the event information.

As a result, when an event occurs, the video data and work record data can be stored in association with the event occurrence information for that event. For example, if video data alone is insufficient, the work record data can also be used to identify the cause of the event. This also eliminates the need for the user to search for video data and work record data corresponding to the event in a database, etc. Therefore, the management method according to one aspect of the present disclosure can reduce the time required to search for data and identify the cause, thereby more reliably reducing the time required to identify the cause of an event that occurred on a component mounter.

Furthermore, for example, multiple cameras may be installed around the component mounter, and the video data may be acquired by acquiring video data captured by one or more cameras selected from the multiple cameras in accordance with the event.

As a result, video data from cameras corresponding to events is associated with event occurrence information, which reduces the time required to review video data compared to when video data from multiple cameras is associated with event occurrence information. Therefore, according to one aspect of the management method disclosed herein, even when multiple cameras are installed around a component mounter, it is possible to more reliably reduce the time required to identify the cause of an event that has occurred on the component mounter.

Furthermore, for example, the multiple cameras may include a first camera installed around the component mounter and a second camera worn by an operator of the component mounter, and at least one of the first camera and the second camera may be selected depending on the event.

This allows video data from a camera type appropriate for the event to be associated with event occurrence information. In other words, video data that is useful for identifying the cause of the event is associated with the event occurrence information. Therefore, according to one aspect of the management method of the present disclosure, it is possible to further reliably reduce the time required to identify the cause of an event that has occurred on a component mounter.

Furthermore, for example, a mounting line may be configured with multiple component mounters, and the video data may be video data captured by the first camera positioned around the component mounter located most upstream of the multiple component mounters.

This allows the first camera to capture clearer images of the area around the upstream mounter, where events are expected to occur more frequently. Such video data can contribute to reducing the time it takes to identify the cause of an event that occurs on an upstream mounter. For example, if the upstream mounter is a mounter that mounts very small components, this can significantly contribute to reducing the time it takes to identify the cause of an event that occurs on such a mounter.

Furthermore, for example, if the same event occurs multiple times within a predetermined period, the time of the last occurrence of the event may be used as the occurrence time, and the event information may be stored by associating the event occurrence information indicating the multiple occurrences of the event with the video data and work record data acquired based on the occurrence time of the last occurrence of the event.

This allows video data from a time period that may be the cause of an event to be associated with event information. This reduces the amount of storage required to store event information compared to associating video data with each event that occurs within a specified period.

Furthermore, for example, it may be determined based on the event occurrence information whether the event is an event for which the event information is to be stored, and if the event is an event for which the event information is to be stored, the video data and the work record data may be acquired.

This allows the process of storing event information only if the event is the target event. When the target event is set by the user, only the event information that the user considers necessary can be stored. This effectively reduces the time required to identify the cause of the user's desired event.

Furthermore, for example, the target event may include a first event in which the mounter stops and a second event in which the mounter does not stop, and when storing the event information, if the event is the first event, the event occurrence information may be associated with the video data and the work record data and stored as the event information, and if the event is the second event, the event occurrence information may be associated with the video data and stored as the event information.

This makes it possible to store event information that associates event occurrence information with video data for events that do not cause the mounter to stop. Therefore, the management method according to one aspect of the present disclosure can further reduce the time required to identify the cause of an event that occurs in a mounter and does not cause the mounter to stop.

Furthermore, for example, when work record data including event identification information issued in response to the occurrence of the event is acquired, the event information may be stored by assigning the event identification information to the event occurrence information and the video data before the work record data is acquired, and then, after the work record data is acquired, associating the work record data with the event occurrence information and the video data associated with the event identification information included in the work record data and storing them as the event information.

This allows event occurrence information, video data, and work record data to be associated using event identification information.

Furthermore, for example, the first time and the second time may be determined depending on the event.

By appropriately determining the first and second times, video data and work record data that are useful for identifying the cause of an event occurrence can be associated with event occurrence information.

Furthermore, a display method according to one aspect of the present disclosure is a display method for displaying the event information stored by the described management method, which displays a list based on one or more pieces of event occurrence information, acquires the selection of one event from the list, and displays an image based on the video data and work record data associated with the acquired event.

As a result, the user can simply select the event they want to check from the list, and the video data and work record data corresponding to that event can be presented to the user. In other words, the user can avoid the task of searching a database or the like for the video data and work record data corresponding to the event they want to check. Furthermore, by associating the work record data with the event, the user can use the work record data to identify the cause of the event when the video data alone does not provide enough information. Therefore, the display method according to one aspect of the present disclosure can reduce the time required to search for data and identify the cause, thereby more reliably reducing the time required to identify the cause of an event that occurred on a component mounter.

A management device according to one aspect of the present disclosure manages event information related to an event that has occurred in a mounter, and includes: a first acquisition unit that acquires event occurrence information including information indicating the occurrence of the event; a second acquisition unit that acquires video data captured around the mounter between the occurrence time indicating the time the event occurred and a time one hour before the occurrence time; a third acquisition unit that acquires at least one of work record data that is a record of work performed on the mounter between the occurrence time and a time two hours after the occurrence time, and work record data that includes event identification information issued as a trigger when the event occurred; and an association unit that associates the event occurrence information with the video data and the work record data and stores the event information.

This achieves the same effect as the management method described above.

The following describes the embodiments in detail, with reference to the drawings.

The embodiments described below are all comprehensive or specific examples. The numerical values, shapes, components, component placement and connection configurations, steps, and step order shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components that are not recited in independent claims will be described as optional components.

Furthermore, each figure is a schematic diagram and is not necessarily an exact representation. Therefore, for example, the scales and other details do not necessarily match between figures. Furthermore, in each figure, substantially identical components are assigned the same reference numerals, and redundant explanations are omitted or simplified.

In addition, in this specification, terms indicating relationships between elements, such as "equivalent," as well as numerical values and numerical ranges, are not expressions that express only the strict meaning, but also expressions that include a range of substantial equivalence, for example, a difference of a few percent (e.g., about 10%).

(Embodiment)
A management system including a management device according to this embodiment will be described below with reference to FIGS.

[1. Management system configuration]
First, the configuration of a management system according to this embodiment will be described with reference to Figures 1 to 5. Figure 1 is a diagram showing the overall configuration of a management system 1 according to this embodiment.

As shown in FIG. 1, the management system 1 includes a data management device 10, a component mounter 100, a head camera 200, a surveillance camera 300, and information terminals 400 and 600. The data management device 10 is communicatively connected to each of the component mounter 100, the head camera 200, the surveillance camera 300, and the information terminals 400 and 600. The communication method may be wired communication or wireless communication.

The management system 1 is an information processing system that manages various information acquired from the mounter 100, head camera 200, surveillance camera 300, and information terminal 400, associating the information as necessary, and allows the associated information to be viewed from an external information terminal 600. More specifically, the management system 1 manages, as necessary, in-facility data (e.g., equipment logs) acquired from the mounter 100 and out-facility data (e.g., first video data, second video data, and work record data) acquired from devices external to the mounter 100. The information terminal 600 can then acquire event information in which the in-facility data and out-facility data are associated via the data management device 10.

The data management device 10 is a device that manages event information related to equipment events (events) that occur in the mounter 100. The data management device 10 acquires various information from the mounter 100, head camera 200, surveillance camera 300, and information terminal 400, and stores the acquired information as event information, correlating it as necessary. When a target event occurs in the mounter 100, the data management device 10 associates the in-facility data and out-facility data corresponding to the event and stores them as event information.

The data management device 10 includes an in-facility data collection unit 20 that acquires in-facility data, an outside-facility data collection unit 30 that acquires outside-facility data, and a data synchronization management unit 40 that processes the in-facility data and the outside-facility data in association with each other and stores them. Details of the data management device 10 will be described later. The data management device 10 is an example of a management device. It is sufficient that the management device has at least the functions of the data synchronization management unit 40.

The mounter 100 is a device included in a production line (e.g., the first production line L1 and second production line L2 shown in FIG. 5 ) and is a mounting facility that mounts components on workpieces such as circuit boards. The mounter 100 includes, for example, a transport unit that transports circuit boards, a feeder that supplies components to be mounted on the circuit boards, a mounting head equipped with component suction nozzles that pick up components from the feeder and can be individually raised and lowered, and a moving unit that moves the head. The transport unit includes, for example, one or more transport lanes. The head is equipped with, for example, multiple nozzles. The mounter 100 may further include sensors for detecting nozzle malfunctions, such as a flow sensor that measures the flow rate of air flowing through the nozzle, a component recognition camera that determines whether the nozzle has picked up a component, and a component recognition camera that calculates the amount of deviation in the pickup position of the picked-up component. The mounter 100 may also include various sensors that can detect malfunctions in the head, transport unit, feeder, head, moving unit, and other components. In this way, the mounter 100 is configured to be able to detect abnormalities, including malfunctions within the mounter 100. Note that the configuration of the mounter 100 is not limited to the above, and can be determined appropriately depending on the type, shape, and processing method of the target object and component.

The components are electronic components, such as, but not limited to, resistors and capacitors. The target object is not limited to a substrate, but may be any workpiece that can be subjected to the specified processing.

The mounter 100 outputs an equipment log acquired within the mounter 100 to the in-facility data collection unit 20. The equipment log includes detection results acquired by various sensors and the like possessed by the mounter 100. The equipment log includes, for example, the time an event occurred (an example of the occurrence date and time) and the details of the event (e.g., the details of the error). In this embodiment, the details of the event include an event code that identifies the event. The equipment log may also include the number of times the same event has occurred, the name of the production line (an example of a location) of the mounter 100 where the event occurred, the event name, etc. The equipment log may also include the number of times the same event has occurred, the name of the production line of the mounter 100 where the event occurred, etc. The equipment log may also include component data related to components mounted by the mounter 100. For example, the equipment log may include component data for the components that were being mounted by the mounter 100 where the event occurred when the event occurred. The component data includes, for example, component identification information (e.g., model number), the number of components used, etc.

The target event includes, for example, at least an error occurring in the mounter 100, and includes, for example, an event in which the mounter 100 stops. The target event may also include an event in which a predetermined task is performed on the mounter 100. The predetermined task may, for example, be supplying a component, performing a predetermined operation on the operation unit (e.g., a touch panel) of the mounter 100, cleaning the mounter 100, or setting conditions on the mounter 100. An event in which the mounter 100 stops among the target events is an example of a first event, and an event in which the mounter 100 does not stop among the target events is an example of a second event. The target event includes at least the first event.

The head camera 200 and the surveillance camera 300 are one or more imaging devices provided in the management system 1.

The head camera 200 is a wearable camera worn by a worker working around the mounter 100 (for example, the floor on which the mounter 100 is located). The head camera 200 captures, for example, video data seen from the worker's line of sight. The head camera 200 captures, for example, the state of the work performed by the worker on the mounter 100 where an event has occurred. Such video data may show, for example, the state of the worker's hands, making it possible to check for any errors made by the worker. Note that the head camera 200 does not have to be worn on the worker's head, and may be worn on another part of the worker's body. The head camera 200 is an example of a first camera, and the video data captured by the head camera 200 is an example of the first video data.

The surveillance camera 300 is placed around the mounter 100 (for example, the floor on which the mounter 100 is placed) and captures a predetermined range including the mounter 100. The predetermined range may be, for example, a range that includes the entire mounter 100. The predetermined range may be, for example, a range that includes the entire mounter 100 and a work area where work related to the mounter 100 is performed. The surveillance camera 300 is, for example, installed in a fixed position. The surveillance camera 300 may be, for example, a fisheye camera installed on the ceiling, etc. The video captured by the surveillance camera 300 may be a bird's-eye view video. The installation position of the surveillance camera 300 will be described below. The surveillance camera 300 is an example of a second camera, and the video data captured by the surveillance camera 300 is an example of second video data.

The number of imaging devices provided in the management system 1 is not particularly limited, and the management system 1 may include multiple head cameras 200 and multiple surveillance cameras 300, or may include only one head camera 200 and one surveillance camera 300.

The information terminal 400 is a device that accepts input of a work record, which is a record of work (e.g., repair work) performed by an operator on the mounter 100 after a target event occurs on the mounter 100, and generates work record data (work report). The information terminal 400 is, for example, a mobile terminal such as a smartphone or tablet terminal, but is not limited to these and may also be a personal computer, etc.

Work record data includes at least one of the following: worker name, work start date and time, event occurrence location, event phenomenon, event cause, response work details, and work completion date and time.

The worker name is information that identifies the worker who performed work on the mounter 100 after an event occurred, and is obtained, for example, when the worker logs in to the information terminal 400.

The work start date and time is the date and time when the worker started work on the mounter 100 where the event occurred, and is entered, for example, by the worker.

The location of the event is information that identifies the mounter 100 where the event occurred or the production line that has that mounter 100, and is entered, for example, by an operator.

An event phenomenon is information indicating the phenomenon of an event that has occurred, and is entered, for example, by a worker. Event phenomena include, but are not limited to, pickup errors and mounting errors.

The event cause is information that the worker considers to be the cause of the event when performing work on the mounter 100, and is input by the worker, for example. The input may be multiple choice or free description.

The details of the response work are the details of the work performed by the operator on the mounter 100 in which the event occurred, and are input by the operator, for example. The input may be multiple choice (for example, guide content selection) or free description. Examples of the work include, but are not limited to, replacing components and cleaning components of the mounter 100 (for example, nozzles).

The work completion date and time is the date and time when the worker finished work on the mounter 100 where the event occurred, and is entered, for example, by the worker.

The work record data may include the synchronization data ID described in the modified example of the embodiment. The work record data is stored as text data, but is not limited to this.

The information terminal 600 is wirelessly connected to the data management device 10 via a wide area communication network such as the Internet 500, and is a terminal device for checking event information stored in the data management device 10. The information terminal 600 is, for example, a mobile terminal such as a smartphone or tablet terminal, but is not limited to these and may also be a personal computer, etc.

[1-1. Configuration of in-facility data collection unit]
Next, the configuration of the in-facility data collection unit 20 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the functional configuration of the in-facility data collection unit 20 according to this embodiment.

As shown in FIG. 2, the in-facility data collection unit 20 includes a collection unit 21, an event code extraction unit 22, a first memory unit 23, a second memory unit 24, a part data extraction unit 25, and a third memory unit 26. The in-facility data collection unit 20 is realized by at least part of a computer or smartphone including a processor, memory, etc. Specifically, the in-facility data collection unit 20 functions as the collection unit 21, event code extraction unit 22, and part data extraction unit 25 by the processor operating in accordance with a program stored in the memory.

The collection unit 21 collects equipment logs from the mounter 100. The collection unit 21 may collect equipment logs from the mounter 100 periodically (for example, every few hours), or may collect equipment logs by sending a request to the mounter 100 to send the equipment logs.

The event code extraction unit 22 extracts events to be monitored from the events included in the equipment log collected by the collection unit 21 and stores them in the second storage unit 24. In this embodiment, the event code extraction unit 22 extracts event codes included in the equipment log that are listed in the event code list stored in the first storage unit 23. It can also be said that the event code extraction unit 22 determines whether an event is an event for which event information should be stored, and stores the determination result in the second storage unit 24. The event code is an example of event occurrence information that indicates that an event has occurred.

In addition to the event code, the event code extraction unit 22 may store in the second storage unit 24 at least one of the following: the time the event occurred, the number of times the event occurred, the name of the production line on which the event occurred, the name of the equipment on which the event occurred, etc. For example, the event code extraction unit 22 may store in the second storage unit 24 an equipment log containing information about the event codes in the event code list.

The first memory unit 23 stores information about events to be monitored. If the equipment log contains an event code that identifies an event, the first memory unit 23 stores a list of the event codes to be monitored. Events to be monitored include events related to errors in the mounter 100. Events to be monitored may be, for example, an event that causes the mounter 100 to stop. Examples of such events include, but are not limited to, component pickup errors and mounting errors. Events to be monitored may also be set by, for example, an operator. The list of event codes is stored before production begins in the mounter 100.

The second storage unit 24 stores the event codes extracted by the event code extraction unit 22. Of the event codes included in the equipment log, the second storage unit 24 stores only the event codes that are the subject of monitoring. The second storage unit 24 may also store information indicating the time when the event occurred along with the event code. The second storage unit 24 is accessible from the data synchronization management unit 40.

The component data extraction unit 25 extracts component data included in the equipment logs collected by the collection unit 21 and stores it in the third storage unit 26. In this embodiment, the component data extraction unit 25 extracts component data corresponding to the monitored event from the equipment log and stores it in the third storage unit 26. The third storage unit 26 stores component data included in the equipment log that corresponds to the monitored event code (for example, component data corresponding to an error). In other words, the third storage unit 26 stores component data for the component that was being mounted by the mounter 100 when the event occurred.

The third storage unit 26 stores the part data extracted from the equipment log by the part data extraction unit 25. The third storage unit 26 may, for example, store an event code and part data in association with each other. The third storage unit 26 is accessible from the data synchronization management unit 40.

The first memory unit 23, the second memory unit 24, and the third memory unit 26 may be different memory devices, or may be a single memory device. The memory device may be, for example, a semiconductor memory, but is not limited to this.

[1-2. Configuration of the external data collection unit]
Next, the configuration of the outside-facility data collection unit 30 will be described with reference to Fig. 3. Fig. 3 is a block diagram showing the functional configuration of the outside-facility data collection unit 30 according to this embodiment.

As shown in FIG. 3, the off-equipment data collection unit 30 includes a video data collection unit 31, a division unit 32, a fourth memory unit 33, a fifth memory unit 34, a work record data collection unit 35, and a sixth memory unit 36. The off-equipment data collection unit 30 is realized by at least part of a computer or smartphone including a processor, memory, etc. Specifically, the off-equipment data collection unit 30 functions as the video data collection unit 31, the division unit 32, and the work record data collection unit 35 by the processor operating in accordance with a program stored in the memory.

The video data collection unit 31 collects video data from one or more imaging devices included in the management system 1. In this embodiment, the video data collection unit 31 collects first video data from the head camera 200 and second video data from the surveillance camera 300. The video data collection unit 31 may collect the first video data and second video data periodically (for example, every few hours), or may collect the first video data and second video data by sending a request to the head camera 200 and the surveillance camera 300 to transmit video data. The first video data and second video data are video (time-series data), but at least one of them may be a still image.

The splitting unit 32 splits the first video data and second video data into time intervals (split intervals) based on the time intervals stored in the fourth storage unit 33, and stores the split data in the fifth storage unit 34. In other words, the first video data and second video data are managed by dividing them into time intervals. This prevents the storage capacity of the fifth storage unit 34 from becoming overwhelmed. Note that the time intervals of the first video data and the second video data may be the same or different.

The fourth memory unit 33 stores the time period when the division unit 32 divides the video data. The time period is set in advance.

The fifth storage unit 34 stores the first video data and second video data split by the split unit 32 for each time interval. The first video data and second video data stored in the fifth storage unit 34 are read, deleted, etc., in units of time intervals (split units). The fifth storage unit 34 is accessible from the data synchronization management unit 40.

The work record data collection unit 35 collects work record data entered by the worker from the information terminal 400. The work record data collection unit 35 may collect work record data periodically (for example, every few hours), or may collect work record data by sending a request to the information terminal 400 to transmit the work record data. The work record data collection unit 35 stores the collected work record data in the sixth memory unit 36.

The sixth memory unit 36 stores the work record data collected by the work record data collection unit 35. The sixth memory unit 36 may, for example, store an event code and work record data in association with each other. The sixth memory unit 36 is accessible from the data synchronization management unit 40.

The fourth memory unit 33, the fifth memory unit 34, and the sixth memory unit 36 may be different storage devices, or may be a single storage device. The storage device may be, for example, a semiconductor memory, but is not limited to this.

[1-3. Configuration of data synchronization management unit]
Next, the configuration of the data synchronization management unit 40 will be described with reference to Fig. 4. Fig. 4 is a block diagram showing the functional configuration of the data synchronization management unit 40 according to this embodiment.

As shown in FIG. 4, the data synchronization management unit 40 includes a code reading unit 41, a component data reading unit 42, a video data reading unit 43, a work record data reading unit 44, an association unit 45, a seventh memory unit 46, and an output unit 47. The data synchronization management unit 40 is realized by at least a part of a computer or smartphone including a processor, memory, etc. Specifically, the data synchronization management unit 40 functions as the code reading unit 41, component data reading unit 42, video data reading unit 43, work record data reading unit 44, association unit 45, and output unit 47 when the processor operates in accordance with a program stored in the memory.

The code reading unit 41 reads the event code from the second storage unit 24 and outputs the read event code to the part data reading unit 42, the video data reading unit 43, the work record data reading unit 44, and the association unit 45. The event code read by the code reading unit 41 is the event code extracted as the event code to be monitored. The code reading unit 41 may also read information indicating the time the event occurred along with the event code. The code reading unit 41 is an example of a first acquisition unit.

The component data reading unit 42 reads component data corresponding to the event from the third storage unit 26. The component data reading unit 42 reads component data corresponding to the event code obtained from the code reading unit 41 from the third storage unit 26. This component data is data related to the component being mounted by the mounter 100 when the event occurred.

The video data reading unit 43 reads video data stored in the fifth memory unit 34. The video data reading unit 43 reads video data for a period corresponding to the event code obtained from the code reading unit 41 from the fifth memory unit 34. The video data reading unit 43 obtains a first period set for each event code and reads from the fifth memory unit 34 video data captured around the mounter 100 between the time the event occurred and a time preceding the occurrence time by the first period. The video data reading unit 43 may determine the first period of the video data to be read for the event code based on a table in which events (event codes) and first periods corresponding to the events are associated, and the event code obtained from the code reading unit 41. The period between the event occurrence time and the time one period before the occurrence time is the synchronization target period (the video synchronization period shown in FIG. 7, described below) to be synchronized in the video data.

The video data reading unit 43 also acquires video data captured by one or more cameras selected in accordance with the event. Based on a table in which events (event codes) and cameras (at least one of head camera 200 and surveillance camera 300) corresponding to the event are associated with each other, and the event code acquired from the code reading unit 41, the video data reading unit 43 selects a camera from which to read video data for the event code, and reads the video data of the selected camera from the fifth memory unit 34. Note that at least one of head camera 200 and surveillance camera 300 is selected in accordance with the event. The video data reading unit 43 is an example of a second acquisition unit.

In this table, whether head camera 200 is associated as the camera corresponding to an event may be determined depending on whether a human work defect is one of the expected causes of the event that has occurred (as a possible cause of the event that has occurred). For example, if a human work defect is one of the causes of the event that has occurred, head camera 200 may be associated in this table as the camera corresponding to the event. For example, if a pickup error (component pickup error) occurs as an event, one of the expected causes is a human work defect called a "splicing error," and therefore video data from head camera 200 is required to infer the cause. In other words, head camera 200 is associated as the camera corresponding to the pickup error. Note that data synchronization management unit 40 may store information for each event indicating whether a human work defect is included as a cause of the event.

The work record data reading unit 44 reads work record data stored in the sixth memory unit 36. The work record data reading unit 44 reads work record data for a period corresponding to the event code obtained from the code reading unit 41 from the sixth memory unit 36. The work record data reading unit 44 obtains the second time period set for each event code and reads work record data from the sixth memory unit 36, which is a record of work performed on the mounter 100 between the time the event occurred and the time two hours after the event occurred. The work record data reading unit 44 may determine the second period for reading work record data for the event code based on a table in which events (event codes) and the second times corresponding to the events are associated, and the event code obtained from the code reading unit 41. The work record data reading unit 44 is an example of a third acquisition unit. The period between the time the event occurred and the time two hours after the event occurred is the synchronization target period (the report synchronization period shown in FIG. 7, described below) that is the synchronization target period for the work record data.

The association unit 45 associates the event code read by the code reading unit 41 with the video data (target video data) read by the video data reading unit 43 and the work record data (target work record data) read by the work record data reading unit 44, and stores the associated information as event information. In other words, the association unit 45 synchronizes and stores the event code with the target video data and target work record data.

The association unit 45 may, for example, determine whether the event that has occurred is an event that causes the mounter 100 to stop or an event that does not cause the mounter 100 to stop, and may change the information associated with the event code based on the determination result. For example, if the event is a first event, the association unit 45 may associate the event code with the target video data and target work record data and store them as event information in the seventh memory unit 46; and if the event is a second event, the association unit 45 may associate the event code with the target video data and store them as event information in the seventh memory unit 46.

By associating the target video data and the target work record data, if the cause of the event is a factor external to the mounter 100 (external factor), the target video data and the target work record data can be used to identify the factor. Examples of external factors include, but are not limited to, an operator's operational error or a material defect. An example of a material defect is, but is not limited to, a tape splicing error when an operator refills the mounter 100 with new tape.

The seventh memory unit 46 stores the event information associated by the association unit 45.

When the output unit 47 receives access from the information terminal 600 to view event information, it reads the event information stored in the seventh memory unit 46 and outputs an image related to the read event information to the information terminal 600 via the Internet 500.

[1-4. Surveillance camera placement]
Next, the installation position of the monitoring camera 300 will be described with reference to FIG. 5 . FIG. 5 is a diagram for explaining the installation position of the monitoring camera 300 according to this embodiment. FIG. 5 illustrates an example in which two production lines, a first production line L1 and a second production line L2, are provided, and the first production line L1 includes component mounters 111-115, and the second production line L2 includes component mounters 121-125. The component mounters 111-115 and the component mounters 121-125 are examples of mounting lines. In FIG. 5 , the board transport direction is from left to right on the page, and among the component mounters 111-115 on the first production line L1, the component mounter 111 is located at the most upstream position, while among the component mounters 121-125 on the second production line L2, the component mounter 121 is located at the most upstream position. 1 may be any one of the mounters 111 to 115 and 121 to 125 shown in Fig. 5. Hereinafter, when there is no need to distinguish between the mounters 111 to 115 and 121 to 125, they will also be referred to as the mounter 100.

The first production line L1 and the second production line L2 produce mounted boards with components mounted by, for example, performing solder printing, component mounting, and reflow operations on boards carried in from the upstream side, and then carry out the produced mounted boards downstream. Mounting includes, for example, component mounting, but is not limited to this.

As shown in FIG. 5, when a production line is configured with multiple component mounters 100, the surveillance camera 300 is placed, for example, around the component mounter 100 located upstream among the multiple component mounters 100. In this embodiment, the surveillance camera 300 is placed around the component mounters 111 and 121 located most upstream among the multiple component mounters 100.

For example, the surveillance camera 310 on the front side of the first production line L1 is positioned near the board entrance of the component mounter 111 on the front side of the component mounter 111, and the surveillance camera 320 on the rear side of the first production line L1 is positioned near the board entrance of the component mounter 111 on the rear side of the component mounter 111. The surveillance cameras 310 and 320 are positioned, for example, so that the component mounter 111 is sandwiched between them.

Furthermore, for example, the surveillance camera 330 on the front side of the second production line L2 is positioned near the board entrance of the component mounter 121 on the front side of the component mounter 121, and the surveillance camera 340 on the rear side of the second production line L2 is positioned near the board entrance of the component mounter 121 on the rear side of the component mounter 121. The surveillance cameras 330 and 340 are positioned, for example, so that the component mounter 121 is sandwiched between them.

The second video data may be video data captured by surveillance cameras 310, 320, 330, and 340 positioned around the component mounter 100 located most upstream of the multiple component mounters 100.

Of the front and rear surveillance cameras, video data from a camera corresponding to an event is associated with that event. Using the first production line L1 as an example, if an event occurs on the front side of one of the mounters 100 on the first production line L1, video data from surveillance camera 310, of the surveillance cameras 310 and 320, capturing an image of the front side of the mounter 100, is associated with that event. An example of an error that occurs on the front side of the mounter 100 is a component pickup error (component pickup error), but is not limited to this.

The installation locations of the surveillance cameras 310-340 are not limited to those shown in Figure 5, and may be any location that can capture an image of the entire mounting line. While surveillance cameras 310 and 320 are installed around the mounter 111, this is not limiting, and only one of the surveillance cameras 310 and 320 may be installed, or three or more surveillance cameras may be installed. The type and location of the surveillance cameras to be installed can be selected and changed depending on the environment of the factory where the production line is installed.

2. Operation of the Management System
Next, the operation of the management system 1 configured as above will be described with reference to FIGS.

[2-1. Event information management method]
First, a method for managing event information will be described with reference to Fig. 6 and Fig. 7. Fig. 6 is a first sequence diagram showing the operation (management method) of the management system 1 according to this embodiment. Fig. 6 shows the management method for managing event information related to events that have occurred in the mounter 100.

As shown in FIG. 6, the component mounter 100 starts production (S11). For example, a manufacturing line that includes the component mounter 100 starts production.

Next, the mounter 100 determines whether an event has occurred (S12). If an error occurs or an operation such as the supply of a component occurs, the mounter 100 determines that an event has occurred (Yes in S12) and notifies the in-facility data collection unit 20 of an equipment log indicating that an event has occurred (S13). If the mounter 100 determines that an event has not occurred (No in S12), it continues production.

If the answer is Yes in step S12, the mounter 100 may notify the operator that an event has occurred. For example, the mounter 100 may illuminate a warning light or emit a warning sound.

The head camera 200 and the surveillance camera 300 may begin capturing images when the mounter 100 starts production, or may begin capturing images before the mounter 100 starts production. For example, the head camera 200 and the surveillance camera 300 may begin capturing images from a time that is one hour earlier than the time the mounter 100 starts production. Therefore, the off-facility data collection unit 30 begins collecting and storing the video data (first video data and second video data) captured by the head camera 200 and the surveillance camera 300 (S31). While the mounter 100 is in production, the collection and storage of the video data continues. The division unit 32 then sequentially divides the video data acquired via the video data collection unit 31 and stores it in the fifth storage unit 34.

Next, when the in-facility data collection unit 20 acquires the facility log from the mounter 100, it determines whether the event that occurred in the mounter 100 is a monitored event (S21). For example, the event code extraction unit 22 of the in-facility data collection unit 20 determines whether the event code included in the facility log is included in the list of event codes stored in the first storage unit 23.

If the intra-facility data collection unit 20 determines that the event is a monitored event (Yes in S21), it issues a synchronization instruction to the data synchronization management unit 40 (S22). In step S22, the intra-facility data collection unit 20 outputs a synchronization instruction to the data synchronization management unit 40, and the data synchronization management unit 40 acquires the synchronization instruction. Upon acquiring the synchronization instruction in step S22, the data synchronization management unit 40 may acquire an event code from the intra-facility data collection unit 20. Acquiring an event code from the intra-facility data collection unit 20 is an example of acquiring event occurrence information that includes information indicating that an event has occurred.

Note that issuing a synchronization instruction means outputting an instruction to execute a process to associate and store the event code of the monitored event with the off-facility data. The instruction may be a dedicated command or an event code.

The intra-facility data collection unit 20 also stores the event code in the second storage unit 24. The intra-facility data collection unit 20 may also store an equipment log including the event code in the second storage unit 24. If the intra-facility data collection unit 20 determines that the event is not a monitored event (No in S21), it waits until the next equipment log is acquired.

Next, the data synchronization management unit 40 determines the synchronization target period (the video synchronization period and report synchronization period shown in FIG. 7, which will be described later) (S41). The data synchronization management unit 40 reads the event code from the second storage unit 24, and then determines the synchronization target period based on a table or the like in accordance with the read event code.

The synchronization period will now be described with reference to Figure 7. Figure 7 is a diagram showing the relationship between an event and the video data and work record data associated with that event in this embodiment. The horizontal axis in Figure 7 represents time. Figure 7 is a diagram showing the correspondence over time between equipment events, work record data corresponding to those equipment events, video data from head camera 200, video data from a first monitoring camera (e.g., monitoring camera 310), and video data from a second monitoring camera (e.g., monitoring camera 320).

First, we will explain the equipment event (Event1) that occurred at time t3. This equipment event is a single occurrence. A single occurrence means that the same equipment event occurs only once within a specified period.

The data synchronization management unit 40 determines the report synchronization period and video synchronization period shown in Figure 7 based on the event that occurred (event code).

The video data reading unit 43 determines the video synchronization period according to the event that has occurred. For example, the video data reading unit 43 determines the video synchronization period according to the event based on a table that associates events (e.g., event codes) with a first time. In the example of Figure 7, the video synchronization period is from time t2 to time t3. Time t2 is based on time t3 and is one hour before time t3.

In this way, the video data associated with a monitored event will be video data captured during a specified period prior to the time the event occurred. This is to determine whether there was any external activity that could have been a cause of the event before it occurred.

Note that Figure 7 shows an example in which the synchronization periods for the video data from the head camera 200, the video data from the first monitoring camera, and the video data from the second monitoring camera are equal, but the video synchronization periods may be different periods as long as they are based on time t3.

The work record data reading unit 44 determines the report synchronization period according to the event that has occurred. For example, the work record data reading unit 44 determines the report synchronization period according to the event based on a table that associates events (e.g., event codes) with the second time. In the example of Figure 7, the report synchronization period is from time t3 to time t5. Time t5 is the second time that has elapsed since time t3, with time t3 being the reference time.

In this way, the work record data associated with the monitored event will be report data for work performed within a specified period after the event occurred. This is to identify the work performed by the mounter 100 in question after the event occurred.

Referring again to FIG. 6, next, the data synchronization management unit 40 reads video data for the synchronization target period (S42). The video data reading unit 43 of the data synchronization management unit 40 reads video data for the synchronization period (video synchronization period) determined in step S41 from the fifth memory unit 34. By making the determination in step S21, the video data reading unit 43 can acquire video data if the equipment event is a monitored event for which event information is stored. Step S42 is an example of acquiring video data.

In this embodiment, the video data is divided and stored in the fifth storage unit 34, and is read out in divided units. Therefore, in this embodiment, video data from time t1 to time t4, including time t2 and time t3 shown in FIG. 7, is read out. For example, in step S42, the video data from Video Split: 1-1 to Video Split: 1-3 is read out from the fifth storage unit 34 for the video data from the head camera 200, the video data from the first surveillance camera, and the video data from the second surveillance camera.

Next, the data synchronization management unit 40 reads the work record data for the synchronization period (S43). The work record data reading unit 44 of the data synchronization management unit 40 reads the work record data for the synchronization period (report synchronization period) determined in step S41 from the sixth memory unit 36. By making the determination in step S21, the work record data reading unit 44 can acquire work record data if the equipment event is an event for which event information is to be stored. Step S43 is an example of acquiring work record data.

At the time an event occurs, work record data corresponding to that event is not stored in the sixth memory unit 36. The off-equipment data collection unit 30 collects work record data from the information terminal 400 over the report synchronization period and stores it in the sixth memory unit 36 (S32). Therefore, the work record data reading unit 44 may wait until the report synchronization period has elapsed, and after the report synchronization period has elapsed, read out the work record data for the report synchronization period from the sixth memory unit 36. In this embodiment, "Report1," which is the work record data for work performed between time t3 and time t5 shown in FIG. 7, is read out.

Next, the data synchronization management unit 40 associates the equipment log (event), video data, and work record data and stores them in the seventh storage unit 46 (S44). In the example of FIG. 7, the video data captured between times t1 and t4 and "Report 1" are stored in association with the equipment event that occurred at time t3. Note that the association unit 45 performs the association, for example, after the report synchronization period has elapsed, that is, after a second time has elapsed (after time t5) since the time the equipment event occurred (time t3). The association unit 45 may, for example, determine whether the report synchronization period has elapsed and perform the association if it determines that the report synchronization period has elapsed. For example, if the work record data periodically collected (read) from the sixth storage unit 36 after the report synchronization period has elapsed contains work record data corresponding to the equipment event (Event 1), the association unit 45 associates the work record data with the equipment event.

If work record data including a synchronization ID corresponding to the equipment event is stored in the external data collection unit 30, the data synchronization management unit 40 may further associate the work record data including the synchronization ID with the equipment log (event) and store it in the seventh memory unit 46.

Next, we will explain the same equipment event that occurred multiple times (four times of Event 2) between times t8 and t11 shown in Figure 7. This equipment event is an event in which the same equipment event occurred multiple times (four times in the example of Figure 7) within a specified period. The specified period is set in advance.

When determining the synchronization period for the same equipment event that occurred multiple times within a specified period, the data synchronization management unit 40 may process the multiple equipment events as a single equipment event. The video data reading unit 43 and work record data reading unit 44 of the data synchronization management unit 40 determine the synchronization period based on the occurrence time of the last equipment event of the same equipment event that occurred multiple times. In the case of Figure 7, the video synchronization period and report synchronization period for the four occurrences of Event 2 are determined based on time t11.

In this case, in step S42, the video data of Video Split: 1-7 to Video Split: 1-9 from the head camera 200, the first surveillance camera, and the second surveillance camera are all read from the fifth memory unit 34. Also, in this case, in step S43, "Report 21" and "Report 22," which are the work record data for the work performed between time t11 and time t13 shown in FIG. 7, are read.

Then, in step S44, the four identical equipment events that occurred between time t8 and time t11, the video data for Video Split: 1-7 to Video Split: 1-9, and "Report 21" and "Report 22" are stored in association with each other. In other words, in step S44, an event code (e.g., an equipment log) indicating multiple identical equipment events is associated with the video data and work record data acquired based on the occurrence time of the last equipment event among the multiple equipment events, and stored as event information. This allows multiple identical equipment events to be viewed together, thereby reducing the time required to identify the cause of the event compared to storing multiple identical equipment events separately.

In this way, the data synchronization management unit 40 is triggered by the occurrence of a monitored event and performs a process of storing the equipment log in association with the internal and external equipment data corresponding to the event. This makes it easier to obtain, view, etc. the internal and external equipment data corresponding to the event than when the cause of the event was identified from the equipment log, as was conventionally done, which can contribute to the early identification of the cause of the event. Furthermore, the association of the external equipment data can significantly contribute to the identification of external factors, especially when the cause of the event is outside the equipment.

In the past, data outside the facility was not associated with data inside the facility, which took a particularly long time when the cause of the event was outside the facility.

[2-2. How to display event information]
Next, a method for displaying event information will be described with reference to Fig. 8 and Fig. 9. Fig. 8 is a second sequence diagram showing the operation (display method) of the management system 1 according to this embodiment. Fig. 8 shows a display method for displaying event information stored by the data synchronization management unit 40 on the information terminal 600.

As shown in FIG. 8, the information terminal 600 logs in to a dedicated application (app) or the like (S101). The dedicated app is an app for displaying event information on the display unit 610 of the information terminal 600, and is pre-installed.

When login processing is performed on the information terminal 600, the data synchronization management unit 40 performs access authentication processing to determine whether access should be permitted (S102). The output unit 47 of the data synchronization management unit 40 performs access authentication processing based on, for example, a username, password, etc.

Next, if access authentication is successful, the output unit 47 reads the data (event information) requested by the information terminal 600 from the seventh storage unit 46 (S103), generates an image to be displayed on the information terminal 600 (S104), and outputs the generated image to the information terminal 600 (S105). The image generated in step S104 is written in, for example, HTML (HyperText Markup Language) format, and is data that can be displayed on a web browser, etc.

Next, the information terminal 600 acquires the image output by the output unit 47 and outputs the acquired image (S106). Specifically, the information terminal 600 displays the acquired image on the display unit 610. The display unit 610 displays the acquired image using a web browser or the like. For example, a user can view and download event information via the information terminal 600 even if they are in a location remote from the facility where the production line is installed (e.g., a factory).

Figure 9 is a diagram showing an example of event information display according to this embodiment. Figure 9 shows an image displayed on the display unit 610.

As shown in FIG. 9, the display unit 610 first displays a first image 610a. The first image 610a is an image based on the in-facility data out of the in-facility data and the out-facility data. It can also be said that the display unit 610 displays the first image 610a including one or more pieces of event occurrence information. The first image 610a includes a facility event list, and is an image that allows the user to select, from multiple events, the out-facility data for which event to view. The facility event list is an example of a list based on one or more pieces of event occurrence information.

The first image 610a includes the date and time of occurrence, event code, number of occurrences, line name, equipment name, side, event main message, event sub-message, and icon 610a1.

The occurrence date and time is the date and time the event occurred, the event code is a code for identifying the event that occurred, the occurrence count is the number of times the same event occurred within a specified period, the line name is information for identifying the production line on which the event occurred, and the facility name is information for identifying the mounter 100 on which the event occurred. The side is information indicating whether the event occurred on the front side ("Front" in Figure 9) or rear side ("Rear" in Figure 9) of the mounter 100. The event main message is information indicating the state of the mounter 100 on which the event occurred, such as "alarm stopped state" or "trouble stopped state." The event sub-message is supplementary information related to the event, such as "component pickup error" or "head abnormality." Icon 610a1 is displayed to allow the user to select an event for which off-facility data is to be displayed.

For example, when the user clicks on the icon 610a1 in the first row, that is, when the information terminal 600 receives a selection of an event from the equipment event list from the user, it displays a second image 610b (an example of an image) based on the video data and work record data associated with the selected event (selected icon 610a1).

The information terminal 600 outputs information indicating the selected icon 610a1 to the output unit 47, obtains an image corresponding to the selected icon 610a1 from the output unit 47, and displays the obtained image on the display unit 610. As a result, the image displayed on the display unit 610 transitions from the first image 610a to the second image 610b.

The second image 610b is an image based on the off-facility data associated with the selected event, and displays a work record list, which is a list of work record data, and a list of video data captured by the surveillance camera. This allows the user to easily view the work record data and video data by simply selecting the work record data and video data they wish to view. For example, if the on-facility data and off-facility data are not associated, the user must search for video data corresponding to the event from multiple video data, which takes time for the user to identify the cause of the event. In contrast, in this embodiment, the on-facility data and off-facility data are automatically associated, so the user does not need to search for video data corresponding to the event, thereby reducing the time required to identify the cause of the event.

(Modification of the embodiment)
The management system according to this modification will be described below with reference to Figures 10 to 13. The following description will focus on differences from the embodiment, and explanations of content that is the same as or similar to the embodiment will be omitted or simplified. For example, the configuration of the management system according to this modification may be the same as the management system 1 according to the embodiment, and explanations will be omitted. This modification differs from the management system 1 according to the embodiment mainly in that association between events and work record data is performed based on a synchronization ID.

Figure 10 is a sequence diagram showing the operation of the management system related to this variant.

As shown in FIG. 10, when an event occurs (Yes in S12), the mounter 100 notifies (outputs) an alert indicating that the event has occurred to the information terminal 400 (S14). This allows the operator to be notified that an alert has occurred. Note that the alert notification may be performed by a device other than the information terminal 400, or by a light-emitting unit of the mounter 100 emitting light, as long as it is possible to notify the operator of the alert.

The worker is notified of the alert and takes action in response to the event (S60).

When the data synchronization management unit 40 receives a synchronization instruction from the intra-facility data collection unit 20 (S22), it issues a synchronization ID (S44). The occurrence of a monitored event is considered to be a trigger for the data synchronization management unit 40 to issue a synchronization ID. The synchronization ID is an ID used to associate an event with work record data. For example, the data synchronization management unit 40 issues a different synchronization ID each time it receives a synchronization instruction from the intra-facility data collection unit 20. The data synchronization management unit 40 may notify the worker of the issued synchronization ID. For example, the data synchronization management unit 40 may output the issued synchronization ID to the information terminal 400 used by the worker.

Note that the synchronization ID is not limited to being a number, and may be a symbol, letter, or a combination thereof, as long as it allows for association between the event and the work record data. Furthermore, the synchronization data ID may be, for example, a dedicated code for each target event that has occurred, an event code for the target event, or other information associated with the target event. The synchronization ID is an example of event identification information.

Next, the data synchronization management unit 40 determines the synchronization period for the video data (S45). After reading the event code from the second storage unit 24, the data synchronization management unit 40 determines the synchronization period for the video data based on a table or the like in accordance with the read event code. Note that in this modified example, the data synchronization management unit 40 does not determine the report synchronization period.

Here, the synchronization period for video data will be explained with reference to Figure 11. Figure 11 is a diagram showing the relationship between an event and the video data and work record data associated with that event in this modified example. The horizontal axis in Figure 11 represents time. Figure 11 is a diagram showing the correspondence over time between equipment events, video data from each monitoring camera, video data from the head camera 200, and work record data corresponding to that equipment event.

The third monitoring camera is a fixed camera mounted on the ceiling or elsewhere, and begins capturing images at time t21. The fourth monitoring camera is a fixed camera on the front side of the production line (e.g., monitoring camera 310), and begins capturing images at time t22. The fifth monitoring camera is a fixed camera on the rear side of the production line (e.g., monitoring camera 320), and begins capturing images at time t22. The head camera 200 is a camera worn on the worker's head, and begins capturing images at time t23. In other words, the third monitoring camera, the fourth monitoring camera, the fifth monitoring camera, and the head camera 200 begin capturing images at different times. The third to fifth monitoring cameras are examples of first cameras, and the head camera 200 is an example of a second camera.

First, we will explain the equipment event (Event A) that occurred at time t25. This equipment event was a single event that occurred.

The data synchronization management unit 40 determines the video synchronization period shown in Figure 11 based on the event (event code) that occurred.

The video data reading unit 43 determines the video synchronization period according to the event that has occurred. For example, the video data reading unit 43 determines the video synchronization period according to the event based on a table that associates events (e.g., event codes) with a first time. In the example of FIG. 11, the video synchronization period is from time t24 to time t25. Time t24 is the time one hour before time t25, with time t25 being the reference time.

The video data reading unit 43 determines the period of video data to be associated individually for each monitoring camera based on the video synchronization period. The video data reading unit 43 determines the video split data that includes the video synchronization period as the video data to be associated with equipment event A. If the video synchronization period is 30 minutes and the split interval is 10 minutes, the video data reading unit 43 determines the video split data included within 30 minutes prior to the time the equipment event occurred (time t25) as the video data to be associated with equipment event A.

The video data reading unit 43 determines that the video data from the third monitoring camera to be associated with equipment event A is the video data for Video Split: 1-2 to Video Split: 1-4. The video data for Video Split: 1-2 to Video Split: 1-4 includes video data captured between time t25 and time t26. The video data reading unit 43 also determines that the video data from the fourth and fifth monitoring cameras to be associated with equipment event A is the video data for Video Split: 1-2 to Video Split: 1-4. The video data for Video Split: 1-2 to Video Split: 1-4 includes video data captured between time t25 and time t27. Additionally, the video data reader 43 determines that the video data from head camera 200 to be associated with facility event A is the video data for Video Split: 1-1 to Video Split: 1-4. This video data for Video Split: 1-1 to Video Split: 1-4 includes video data captured between time t25 and time t28.

Next, we will explain the same equipment event (Event B four times) that occurred at times t32, t33, t34, and t35. This equipment event is an event in which the same equipment event occurred multiple times (four times in the example of Figure 11) within a predetermined period. The predetermined period is set in advance.

When determining a video synchronization period for the same equipment event that occurred multiple times within a specified period, the data synchronization management unit 40 may process the multiple equipment events as a single equipment event. The video data reading unit 43 and work record data reading unit 44 of the data synchronization management unit 40 determine the video synchronization period based on the occurrence time of the last equipment event of the same equipment event. In the case of Figure 11, the video synchronization period (time t31 to time t35) for the four occurrences of Event B is determined based on time t35. Note that the video synchronization period is longer than the specified period.

The processing after determining the video synchronization period is the same as for Event A, so detailed explanation will be omitted. The video data reading unit 43 determines the video data from the third surveillance camera to be associated with Equipment Event B as video data from Video Split: 1-10 to Video Split: 1-12. The video data from Video Split: 1-10 to Video Split: 1-12 includes video data captured between time t35 and time t36. The video data reading unit 43 also determines the video data from the fourth and fifth surveillance cameras to be associated with Equipment Event B as video data from Video Split: 1-9 to Video Split: 1-12. The video data for Video Split: 1-9 to Video Split: 1-12 includes video data captured between time t35 and time t37. Furthermore, video data reader 43 determines that the video data from head camera 200 to be associated with equipment event B is the video data for Video Split: 1-9 to Video Split: 1-12. The video data for Video Split: 1-9 to Video Split: 1-12 includes video data captured between time t30 and time t31 and between time t35 and time t38.

Referring again to FIG. 10, the data synchronization management unit 40 then associates the video data read in step S43, the equipment event (equipment log), and the synchronization ID issued in step S44, and stores them in the seventh memory unit 46 (S46). It can also be said that the data synchronization management unit 40 stores the equipment log and video data with a synchronization ID, for example, before the work record data is acquired. At this point, the work record data corresponding to the equipment event (equipment log) is not stored in the seventh memory unit 46.

Note that at least some of the processing from steps S44 to S46 may be performed while the worker is responding to the event. For example, all of the processing from steps S44 to S46 may be performed by the time the worker has completed responding to the event.

Next, when the worker has finished responding to the event and has received an instruction to resume production from the worker (S15), the mounter 100 resumes production (S16). The mounter 100 may receive this instruction via the operation unit, or may receive this instruction from another device such as the information terminal 400.

Next, the information terminal 400 accepts input of work record data specifying a synchronization ID from the worker and registers the accepted work record data (S51). For example, if the information terminal 400 has acquired a synchronization ID from the data synchronization management unit 40, it may present the acquired synchronization ID and allow the worker to select which synchronization ID's work record data to enter, or it may accept input of a synchronization ID from the worker. Note that when selecting a synchronization ID, if there is no corresponding synchronization ID, the synchronization ID field may be left blank (a state in which no synchronization ID has been entered). The information terminal 400 then outputs the work record data to the off-equipment data collection unit 30. As a result, the work record data is stored in the sixth memory unit 36.

The registration screen for registering work records will now be described with reference to Figure 12. Figure 12 shows an example of the registration screen for registering work records in this modified example.

As shown in FIG. 12, the registration screen includes the worker ID, synchronization ID, event name, occurrence date and time, location, completion date and time, cause, task (task content), and memo (memo field). The registration screen also displays a register button, which is an icon for registration, and a cancel button, which is an icon for canceling.

The worker ID displays the name of the user logged in to the information terminal 400. If the logged-in user is different from the user who performed the work, the change button can be used to select the worker ID of the user who performed the work from the worker list.

The synchronization ID displays a list of synchronization IDs issued during the time period when the event occurred (e.g., year, month, day, hour, minute). The worker can select the appropriate synchronization ID.

The profile information corresponding to the selected synchronization ID is automatically displayed in the event name, occurrence date and time, and location. The worker can check the displayed information to ensure that the synchronization ID is correct. Note that this information may be obtained, for example, from the data synchronization management unit 40 along with the synchronization ID.

The completion date and time is the time when the event response work is completed and is entered by the worker.

The "Cause" field is where the actual cause of an event is entered, and is selected by the operator from a list. The example in Figure 12 shows an example where "Splice Error" is selected. If the corresponding cause is not on the list, the operator selects "Not Applicable." In this case, the operator may enter the cause as text in the "Memo" field below. Note that the items in the list of causes displayed here may display causes inferred by the system based on the event that occurred, or may display pre-set causes.

The "Task" field is where the actual event response task performed is entered, and is selected by the worker from a list. The example in Figure 12 shows an example where "Splicing Correction" is selected. If the corresponding task is not on the list, the worker selects "Not Applicable." In this case, the worker enters the task as text in the "Memo" field at the bottom. Here, the items in the list of tasks displayed may be tasks that correspond to the factors inferred by the system in response to the event that occurred, or may be pre-set tasks.

Notes is a field where additional text information can be entered as needed.

Note that the registration screen displayed on the information terminal 400 in this embodiment may be a screen in which the "Synchronization ID" field has been deleted from the registration screen shown in FIG. 12.

Referring again to FIG. 10, next, the off-equipment data collection unit 30 acquires work record data from the information terminal 400 (S33), writes the acquired work record data to the sixth memory unit 36, and outputs the acquired work record data to the data synchronization management unit 40 (S34). In other words, the off-equipment data collection unit 30 stores the acquired work record data in the sixth memory unit 36, and outputs the acquired work record data to the data synchronization management unit 40.

Next, the data synchronization management unit 40 associates the written work record data with the synchronization ID and stores it in the seventh memory unit 46 (S47). The data synchronization management unit 40 associates the work record data acquired from the external data collection unit 30 via the work record data reading unit 44 with the equipment log and video data corresponding to the synchronization ID included in the work record data and stores them in the seventh memory unit 46. The data synchronization management unit 40 associates the work record data with the equipment log and video data associated with a synchronization ID that matches the synchronization ID included in the work record data and stores them in the seventh memory unit 46.

As described above, the data synchronization management unit 40 stores work record data including a synchronization ID that is issued in response to the occurrence of a monitored event, in association with the equipment log and video data for the monitored event. It can also be said that the data synchronization management unit 40 stores work record data including one synchronization ID among multiple pieces of work record data as event information, in association with the equipment log and video data associated with that one synchronization ID.

For example, in the example of FIG. 11, work record A stored at time t29 and including a synchronization ID corresponding to event A is associated with event A to which the synchronization ID is associated and various video data associated with event A, and is stored in the seventh storage unit 46. Furthermore, work record B stored at time t39 and including a synchronization ID corresponding to event B is associated with event B (four occurrences of event B) to which the synchronization ID is associated and various video data associated with event B, and is stored in the seventh storage unit 46.

Figure 13 is a diagram showing the data structure of event information stored in the seventh storage unit 46 in this modified example. Figure 13 shows the structure of various data associated with synchronization IDs.

As shown in Figure 13, event information is information in which equipment logs, video data, and work record data are associated with each other using a synchronization ID.

(Other embodiments)
The management methods and the like according to one or more aspects have been described above based on the embodiments, but the present disclosure is not limited to these embodiments. As long as they do not deviate from the spirit of the present disclosure, various modifications that a person skilled in the art can make to the present embodiments and forms constructed by combining components of different embodiments may also be included in the present disclosure.

For example, in the above embodiments, an example has been described in which the video data is divided into split intervals by the dividing unit and stored, but this is not limited to this. The video data may also be stored without being divided into split intervals. In other words, the off-equipment data collection unit does not need to have a dividing unit.

Furthermore, in the above embodiments, examples have been described in which the mounting line is equipped with multiple component mounters, but this is not limited to this. The mounting line may also be equipped with only one component mounter. Furthermore, the component mounter may not be incorporated into the mounting line, but may be used as a standalone mounter.

Furthermore, in the above embodiments, an event code is used as an example of event occurrence information, but the event occurrence information may be any information that can identify what event has occurred, such as an event name.

Furthermore, in the above embodiments, an example has been described in which it is determined whether an event is an event to be monitored (S21 shown in Figure 6), but this is not limiting, and it is not necessary to determine whether an event is an event to be monitored. For example, all of the event codes included in the equipment log from the component mounter may be stored in the second storage unit.

In addition, in the above embodiments, examples have been described in which the object is a circuit board, but this is not limited to this and the object may be, for example, a flat object (e.g., an iron plate) or another object. In addition, in the above embodiments, mounting a component on a circuit board has been described as an example of predetermined processing, but this is not limited to this and the predetermined processing may be fixing the component to the circuit board by locking or compressing (e.g., thermocompression bonding) the component, hardening a substance applied to the object by heat or light, or mechanical processing such as deforming or cutting at least a portion of the object.

In addition, in the above embodiments, the first time is described as a number of hours (e.g., 30 minutes), but if the video data is stored in split units, it may be the number of splits.

Furthermore, in the above-described embodiments, the data synchronization management unit may extract work record data that includes a synchronization ID issued in response to the occurrence of an event, from one or more pieces of work record data that are records of work performed on the mounter between the time the event occurred and the time two hours after the event occurred, and associate the extracted work record data with the equipment log and video data.

Furthermore, the order in which each step is executed in the sequence diagram is merely an example to specifically explain the present disclosure, and orders other than those described above may also be used. Furthermore, some of the steps may be executed simultaneously (in parallel) with other steps, or some of the steps may not be executed at all.

Furthermore, in the above embodiments, each component may be configured with dedicated hardware, or may be realized by executing a software program appropriate for that component. Each component may also be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

Furthermore, the division of functional blocks in the block diagram is one example; multiple functional blocks may be realized as a single functional block, one functional block may be divided into multiple blocks, or some functions may be moved to other functional blocks. Furthermore, the functions of multiple functional blocks with similar functions may be processed in parallel or time-shared by a single piece of hardware or software.

Furthermore, the data management device according to the above embodiments may be realized as a single device or may be realized by multiple devices. When the data management device is realized by multiple devices, the components of the data management device may be distributed among the multiple devices in any manner. For example, the intra-facility data collection unit, the extra-facility data collection unit, and the data synchronization management unit may each be realized by different devices (such as personal computers). In this case, the intra-facility data collection unit and the extra-facility data collection unit are located within the factory where the production line is installed, and the data synchronization management unit is located outside the factory. The data synchronization management unit may be, for example, a server device. Furthermore, when the data management device is realized by multiple devices, the communication method between the multiple devices is not particularly limited and may be wireless communication or wired communication. Furthermore, wireless communication and wired communication may be combined between the devices.

Furthermore, these general or specific aspects may be realized as a system, method, integrated circuit, computer program, or non-transitory recording medium such as a computer-readable CD-ROM, or as any combination of a system, method, integrated circuit, computer program, or recording medium. The program may be pre-stored on the recording medium, or may be supplied to the recording medium via a wide area communication network, including the Internet.

Furthermore, each component described in the above embodiments may be implemented as software, or typically as an LSI, which is an integrated circuit. These components may be individually integrated into a single chip, or some or all of them may be integrated into a single chip. Here, we refer to LSIs, but depending on the level of integration, they may also be referred to as ICs, system LSIs, super LSIs, or ultra LSIs. Furthermore, the integration method is not limited to LSIs; dedicated circuits (general-purpose circuits that execute dedicated programs) or general-purpose processors may also be used. It is also possible to use FPGAs (Field Programmable Gate Arrays), which can be programmed after LSI manufacturing, or reconfigurable processors, which allow the connections or settings of circuit cells within an LSI to be reconfigured. Furthermore, if an integrated circuit technology that can replace LSIs emerges due to advances in semiconductor technology or other derivative technologies, that technology may naturally be used to integrate the components.

A system LSI is an ultra-multifunctional LSI manufactured by integrating multiple processing units onto a single chip. Specifically, it is a computer system comprising a microprocessor, ROM (Read Only Memory), RAM (Random Access Memory), etc. Computer programs are stored in the ROM. The system LSI achieves its functions when the microprocessor operates in accordance with the computer program.

Another aspect of the present disclosure may be a computer program that causes a computer to execute each of the characteristic steps included in the data management method shown in FIG. 6 and the data display method shown in FIG. 8.

Also, for example, the program may be a program to be executed by a computer. Another aspect of the present disclosure may be a computer-readable, non-transitory recording medium on which such a program is recorded. For example, such a program may be recorded on a recording medium and distributed or circulated. For example, by installing the distributed program on a device having another processor and having that processor execute the program, it becomes possible to cause that device to perform each of the above processes.

This disclosure is useful for management methods for managing data related to component mounters.

1 Management system 10 Data management device (management device)
20 In-facility data collection unit 21 Collection unit 22 Event code extraction unit 23 First storage unit 24 Second storage unit 25 Part data extraction unit 26 Third storage unit 30 Out-facility data collection unit 31 Video data collection unit 32 Dividing unit 33 Fourth storage unit 34 Fifth storage unit 35 Work record data collection unit 36 Sixth storage unit 40 Data synchronization management unit 41 Code reading unit (first acquisition unit)
42 Component data reading unit 43 Video data reading unit (second acquisition unit)
44 Work record data reading unit (third acquisition unit)
45 Corresponding unit 46 Seventh storage unit 47 Output unit 100, 111, 112, 113, 114, 115, 121, 122, 123, 124, 125 Component mounter 200 Head camera (first camera)
300, 310, 320, 330, 340 Surveillance camera (second camera)
400, 600 Information terminal 500 Internet 610 Display unit 610a First image 610a1 Icon 610b Second image L1 First production line L2 Second production line

Claims (11)

A management method for managing event information relating to an event that has occurred in a component mounter, comprising:
acquiring event occurrence information including information indicating that the event has occurred;
acquiring video data of the surroundings of the component mounter between an occurrence time indicating the time when the event occurred and a time a first hour before the occurrence time;
acquire at least one of work record data that is a record of work performed on the mounter between the occurrence time and a time second hour after the occurrence time, and work record data that includes event identification information issued with the occurrence of the event as a trigger;
the event occurrence information is stored as the event information in association with the video data and the work record data. A plurality of cameras are provided around the component mounter,
The management method according to claim 1 , wherein the acquisition of the video data includes acquiring video data captured by one or more cameras selected from the plurality of cameras in accordance with the event. the plurality of cameras include a first camera installed around the component mounter and a second camera worn by an operator of the component mounter,
The management method according to claim 2 , wherein at least one of the first camera and the second camera is selected in response to the event. A mounting line is configured that includes a plurality of the component mounters,
The management method according to claim 3 , wherein the video data is video data captured by the first camera disposed around the component mounter located most upstream among the plurality of component mounters. If the same event occurs multiple times within a predetermined period, the time of the last event to occur among the multiple occurrences of the event is set as the occurrence time;
The management method according to any one of claims 1 to 4, wherein the event information is stored by associating the event occurrence information indicating the occurrence of multiple events with the video data and the work record data acquired based on the occurrence time of the last event that occurred. determining whether the event is an event for which the event information is to be stored based on the event occurrence information;
The management method according to any one of claims 1 to 5, wherein the video data and the work record data are acquired when the event is an event for which the event information is to be stored. the target event includes a first event in which the mounter stops and a second event in which the mounter does not stop,
In storing the event information,
If the event is the first event, the event occurrence information is associated with the video data and the work record data and stored as the event information;
The management method according to claim 6 , wherein, when the event is the second event, the event occurrence information and the video data are stored as the event information in association with each other. When work record data including event identification information issued as a trigger by the occurrence of the event is acquired, the event information is stored by:
Before the work record data is acquired, the event occurrence information and the video data are stored with event identification information added thereto;
After the work record data is acquired, the work record data is associated with the event occurrence information and the video data to which event identification information included in the work record data is associated, and the associated event information and video data are stored as the event information. The management method according to any one of claims 1 to 7. The management method according to any one of claims 1 to 8, wherein the first time period and the second time period are determined in accordance with the event. A display method for displaying the event information stored by the management method according to any one of claims 1 to 9, comprising:
Displaying a list based on one or more of the event occurrence information;
Obtaining a selection of one event from the list;
A display method for displaying an image based on the video data and the work record data associated with the acquired event. A management device that manages event information related to an event that occurs in a component mounter,
a first acquisition unit that acquires event occurrence information including information indicating that the event has occurred;
a second acquisition unit that acquires video data of the surroundings of the component mounter between an occurrence time indicating the time when the event occurred and a time one hour before the occurrence time;
a third acquisition unit that acquires at least one of work record data that is a record of work performed on the mounter between the occurrence time and a time that is two hours after the occurrence time, and work record data that includes event identification information that is issued with the occurrence of the event as a trigger;
a correlation unit that correlates the event occurrence information with the video data and the work record data and stores the correlated information as the event information.