Management method, display method and management device

Abstract

To provide a management method or the like capable of more surely reducing a time required for specifying a factor of an event generated in a component mounting machine.SOLUTION: A management method is a management method for managing event information related to an event generated in a component mounting machine 100. The management method includes: a step (S42) of acquiring event generation information containing information indicating the generation of the event and acquiring video image data obtained by imaging a circumference of the component mounting machine 100 during a generation time indicating a time when the event occurs and a time before a first time from the generation time; a step (S43) of acquiring at least one of work data as a recording of a work performed to the component mounting machine 100 during the generation time and a time after a second time from the generation time and work recording data containing the event identification information issuing the generation of the event as a trigger; and a step (S44) of storing the event generation information so as to be associated with the video image data and the work data as event information.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a management method, a display method, and a management device for managing event information related to events that occur in a component mounter. [Background technology]

[0002] 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. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2018 / 055754 Summary of the Invention [Problem to be solved by the invention]

[0004] From the viewpoint of preventing 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 in a component mounter. In the system disclosed in Patent Document 1, if the cause is not captured 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.

[0005] Therefore, the present disclosure provides a management method, a display method, and a management device that can more reliably shorten the time required to identify the cause of an event that has occurred in a component mounter. [Means for solving the problem]

[0006] 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 component mounting machine, which acquires event occurrence information including information indicating the occurrence of the event, acquires video data capturing images of the surroundings of the component mounting machine 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 is a record of work performed on the component mounting machine 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.

[0007] A display method according to one embodiment of the present disclosure is a display method for displaying the event information stored by the above-described management method, which displays a list based on one or more of the event occurrence information, obtains a selection of one event from the list, and displays an image based on the video data and work record data associated with the obtained event.

[0008] A management device according to one embodiment of the present disclosure is a management device that manages event information related to an event that has occurred in a component mounter, and includes: 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 captured around the component mounter between an 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 component 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 occurs; and an association unit that associates the event occurrence information with the video data and the work record data and stores the event information. [Effects of the Invention]

[0009] According to the management method and the like according to one aspect of the present disclosure, it is possible to more reliably reduce the time required to identify the cause of an event that has occurred in a mounter. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a management system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating a functional configuration of an in-facility data collection unit according to the embodiment. [Figure 3] FIG. 3 is a block diagram illustrating a functional configuration of the outside-equipment data collection unit according to the embodiment. [Figure 4] FIG. 4 is a block diagram illustrating a functional configuration of a data synchronization management unit according to the embodiment. [Figure 5] FIG. 5 is a diagram for explaining the installation positions of the monitoring cameras according to the embodiment. [Figure 6] FIG. 6 is a first sequence diagram illustrating the operation of the management system according to the embodiment. [Figure 7] 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. [Figure 8] FIG. 8 is a second sequence diagram illustrating the operation of the management system according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of display of event information according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram showing the operation of the management system according to the modification of the embodiment. [Figure 11] 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. [Figure 12] FIG. 12 is a diagram showing an example of a registration screen for registering a work record according to the modification of the embodiment. [Figure 13] 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. DETAILED DESCRIPTION OF THE INVENTION

[0011] 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 component mounting machine, which acquires event occurrence information including information indicating the occurrence of the event, acquires video data capturing images of the surroundings of the component mounting machine 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 is a record of work performed on the component mounting machine 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.

[0012] 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, when 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, according to the management method of one aspect of the present disclosure, the time required to search for data and the time required to identify the cause can be reduced, thereby more reliably reducing the time required to identify the cause of an event that occurred in a mounter.

[0013] Also, 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 according to the event.

[0014] As a result, the video data from the camera corresponding to the event is associated with the event occurrence information, so the time required to check the video data can be reduced compared to when the video data from each of multiple cameras is associated with the event occurrence information. Therefore, according to the management method according to one aspect of the present disclosure, even when multiple cameras are installed around the mounter, the time required to identify the cause of an event that has occurred in the mounter can be more reliably reduced.

[0015] Also, 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.

[0016] As a result, video data from a camera of a type corresponding to the event is associated with the event occurrence information. In other words, video data useful for identifying the cause of the event is associated with the event occurrence information. Therefore, according to the management method according to one aspect of the present disclosure, it is possible to further reliably shorten the time required to identify the cause of an event that has occurred in a mounter.

[0017] Furthermore, for example, a mounting line may be configured that includes a plurality of the component mounters, and the video data may be video data captured by the first camera that is positioned around the component mounter that is located most upstream among the plurality of the component mounters.

[0018] 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 image data can contribute to reducing the time required to identify the cause of an event that occurred on the upstream mounter. For example, if the upstream mounter is a mounter that mounts very small components, this can significantly contribute to reducing the time required to identify the cause of an event that occurred on such a mounter.

[0019] Furthermore, for example, if the same event occurs multiple times within a specified period, the time of the last event to occur among the multiple occurrences of the event may be used as the occurrence time, and when storing the event information, the event occurrence information indicating the multiple occurrences of the event may be associated with the video data and work record data acquired based on the occurrence time of the last event to occur, and stored as the event information.

[0020] This allows video data from a time period that may be a cause of an event to be associated with event information, reducing the storage capacity required to store event information compared to when video data is associated with each event that occurs within a predetermined period.

[0021] Furthermore, for example, it may be possible to determine whether the event is an event for which the event information is to be stored based on the event occurrence information, and if the event is an event for which the event information is to be stored, to acquire the video data and the work record data.

[0022] This allows the event information to be stored only when the event is a target event. When a 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 event desired by the user.

[0023] Furthermore, for example, the target event may include a first event in which the component mounter stops and a second event in which the component mounter does not stop, and in 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.

[0024] 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.

[0025] Furthermore, for example, when work record data including event identification information issued as a trigger when the event occurs is acquired, the event information may be stored by attaching 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, the work record data may be associated with the event occurrence information and the video data associated with the event identification information included in the work record data and stored as the event information.

[0026] This allows the event occurrence information, video data, and work record data to be associated with each other using the event identification information.

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

[0028] As a result, the first time and the second time are appropriately determined, and the video data and the work record data that are useful for identifying the cause of the event occurrence can be associated with the event occurrence information.

[0029] Furthermore, a display method according to one embodiment of the present disclosure is a display method for displaying the event information stored in the described management method, which displays a list based on one or more of the event occurrence information, acquires a 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.

[0030] This allows the user to simply select an 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 having to search a database or the like for 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 is insufficient. 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 in a mounter.

[0031] Furthermore, a management device according to one aspect of the present disclosure is a management device that manages event information related to an event that has occurred in a component mounter, and includes: 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 area around the component mounter between an occurrence time indicating the time that 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 component 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 has 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.

[0032] This provides the same effect as the above management method.

[0033] Hereinafter, the embodiments will be specifically described with reference to the drawings.

[0034] 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 not described in independent claims are described as optional components.

[0035] Furthermore, each figure is a schematic diagram and is not necessarily an exact illustration. Therefore, for example, the scales and the like do not necessarily match in each figure. Furthermore, in each figure, substantially the same configurations are assigned the same reference numerals, and duplicate explanations are omitted or simplified.

[0036] Furthermore, in this specification, terms indicating relationships between elements such as "equal," as well as numerical values ​​and numerical ranges, are not expressions that only express a strict meaning, but are expressions that also mean a range that is substantially equivalent, for example, including a difference of about a few percent (e.g., about 10%).

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

[0038] [1. Management system configuration] First, the configuration of a management system according to the present 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 the present embodiment.

[0039] 1, the management system 1 includes a data management device 10, a component mounter 100, a head camera 200, a monitoring camera 300, and information terminals 400 and 600. The data management device 10 is communicably connected to the component mounter 100, the head camera 200, the monitoring camera 300, and the information terminals 400 and 600. The communication method may be wired communication or wireless communication.

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

[0041] The data management device 10 is a device that manages event information related to equipment events (events) that occur in the component mounter 100. The data management device 10 acquires various information from the component mounter 100, the head camera 200, the monitoring camera 300, and the information terminal 400, and stores the acquired information as event information in association with each other as necessary. When a target event occurs in the component mounter 100, the data management device 10 associates the in-equipment data and the out-equipment data corresponding to the event with each other and stores the associated data as event information.

[0042] 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 performs processing to associate and store the in-facility data and the outside-facility data. 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.

[0043] The mounter 100 is a device included in a production line (e.g., the first production line L1 and the second production line L2 shown in FIG. 5 ) and is a mounting facility that mounts components on targets (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 (head) equipped with component suction nozzles (nozzles) that pick up components from the feeder and can individually move up and down, 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, and a component recognition camera that determines whether the nozzle has picked up a component and 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 has a configuration that can detect abnormalities, including malfunctions inside the mounter 100. Note that the configuration of the mounter 100 is not limited to the above, and is determined appropriately depending on the type, shape, processing method, etc. of the target object and component.

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

[0045] The mounter 100 outputs an equipment log acquired within the mounter 100 to the intra-facility data collector 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 when an event occurred (an example of the occurrence date and time) and the content of the event (e.g., the content of an error). In this embodiment, the content of the event includes 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 of 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.

[0046] The target event includes, for example, at least an occurrence of an error 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 be, for example, supplying a component, performing a predetermined operation on an operation unit (e.g., a touch panel) of the mounter 100, cleaning the mounter 100, or setting conditions in 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.

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

[0048] Head camera 200 is a wearable camera worn by a worker working around component mounter 100 (for example, the floor on which component mounter 100 is placed). Head camera 200 captures, for example, video data seen from the worker's line of sight. Head camera 200 captures, for example, the state of the work performed by the worker on component mounter 100 in which 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 mistakes made by the worker. Note that head camera 200 is not limited to being worn on the worker's head, and may be worn on another part of the worker's body. Head camera 200 is an example of a first camera, and the video data captured by head camera 200 is an example of the first video data.

[0049] The surveillance camera 300 is placed around the component mounter 100 (for example, the floor on which the component mounter 100 is placed) and captures an image of a predetermined range including the component mounter 100. The predetermined range may be, for example, a range that includes the entire component mounter 100. The predetermined range may be, for example, a range that includes the entire component mounter 100 and a work area where work related to the component 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 or the like. The image captured by the surveillance camera 300 may be an overhead image. The installation position of the surveillance camera 300 will be described later. The surveillance camera 300 is an example of a second camera, and the image data captured by the surveillance camera 300 is an example of second image data.

[0050] The number of imaging devices provided in the management system 1 is not particularly limited, and the management system 1 may be provided with multiple head cameras 200 and multiple surveillance cameras 300, or with at least one of the head cameras 200 and surveillance cameras 300.

[0051] The information terminal 400 is a device that receives 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 in 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 a tablet terminal, but is not limited to these, and may also be a personal computer or the like.

[0052] The work record data includes at least one of the worker name, work start date and time, event occurrence location, event phenomenon, event cause, response work content, and work end date and time.

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

[0054] 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 input by the worker, for example.

[0055] The event occurrence location is information that identifies the mounter 100 in which the event occurred or the manufacturing line that has the mounter 100, and is input by, for example, an operator.

[0056] The event phenomenon is information indicating the phenomenon of an event that has occurred, and is input by, for example, an operator. The event phenomenon is, for example, a pickup error, a mounting error, etc., but is not limited to these.

[0057] The event cause is information that the worker considers to be the cause of the event occurrence when performing work on the mounter 100, and is input by the worker, for example. The input may be a multiple-choice format or a free-form format.

[0058] The content of the countermeasure work is the content of the work performed by the operator on the mounter 100 in which the event occurred, and is input by the operator, for example. The input may be a multiple-choice format (for example, a guide content selection format) or a free description format. The content of the work may be, for example, replacing a component, cleaning a component of the mounter 100 (for example, a nozzle), etc., but is not limited to this.

[0059] The work end date and time is the date and time when the worker finished work on the mounter 100 in which the event occurred, and is input by the worker, for example.

[0060] 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.

[0061] The information terminal 600 is connected to the data management device 10 via a wide area communication network such as the Internet 500 so as to be able to communicate wirelessly, 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 a tablet terminal, but is not limited to these and may also be a personal computer or the like.

[0062] [1-1. Configuration of data collection unit within facility] Next, the configuration of the intra-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 intra-facility data collection unit 20 according to this embodiment.

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

[0064] 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 transmit the equipment logs.

[0065] 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 from the event codes 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 or not 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 indicating that an event has occurred.

[0066] In addition to the event code, the event code extraction unit 22 may store at least one of the time when the event occurred, the number of times the event occurred, the name of the production line where the event occurred, the name of the facility where the event occurred, etc. in the second storage unit 24. For example, the event code extraction unit 22 may store in the second storage unit 24 a facility log that includes information about the event code in the event code list.

[0067] The first storage unit 23 stores information about events to be monitored. If the equipment log includes an event code that identifies an event, the first storage 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.

[0068] 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, only the event codes of the monitoring target are stored in the second storage unit 24. The second storage unit 24 may also store information indicating the time when the event occurred together with the event code. The second storage unit 24 is accessible from the data synchronization management unit 40.

[0069] The component data extraction unit 25 extracts component data included in the equipment log 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 an event to be monitored from the equipment log and stores it in the third storage unit 26. Of the component data included in the equipment log, the third storage unit 26 stores component data that corresponds to the event code of the monitoring target (for example, component data corresponding to an error). In other words, the third storage unit 26 stores component data of the component that was being mounted by the component mounter 100 when the event occurred.

[0070] 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 store, for example, 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.

[0071] The first storage unit 23, the second storage unit 24, and the third storage unit 26 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.

[0072] [1-2. Configuration of the external data collection unit] Next, the configuration of the outside-equipment 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-equipment data collection unit 30 according to this embodiment.

[0073] 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 a 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.

[0074] 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 collects second video data from the surveillance camera 300. The video data collection unit 31 may collect the first video data and the second video data periodically (for example, every few hours), or may collect the first video data and the second video data by sending a request to the head camera 200 and the surveillance camera 300 to transmit the video data. The first video data and the second video data are moving images (time-series data), but at least one of them may be a still image.

[0075] The dividing unit 32 divides the first video data and the second video data for each time interval (split interval) stored in the fourth storage unit 33, and stores the divided data in the fifth storage unit 34. That is, the first video data and the second video data are managed by dividing them into sections for each time interval. This makes it possible to prevent the storage capacity of the fifth storage unit 34 from becoming overwhelmed. Note that the time interval of the first video data and the time interval of the second video data may be the same or different.

[0076] The fourth storage unit 33 stores the time period when the dividing unit 32 divides the video data. The time period is set in advance.

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

[0078] The work record data collection unit 35 collects work record data input by the worker from the information terminal 400. The work record data collection unit 35 may collect the work record data periodically (for example, every few hours), or may collect the 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 storage unit 36.

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

[0080] The fourth storage unit 33, the fifth storage unit 34, and the sixth storage 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.

[0081] [1-3. Data Synchronization Management Unit Configuration] 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.

[0082] 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 storage 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, the component data reading unit 42, the video data reading unit 43, the work record data reading unit 44, the association unit 45, and the output unit 47 by the processor operating in accordance with a program stored in the memory.

[0083] 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 when the event occurred together with the event code. The code reading unit 41 is an example of a first acquisition unit.

[0084] 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 acquired from the code reading unit 41 from the third storage unit 26. The component data is data related to the component that was being mounted by the component mounter 100 when the event occurred.

[0085] The video data reading unit 43 reads video data stored in the fifth storage unit 34. The video data reading unit 43 reads video data for a period corresponding to the event code acquired from the code reading unit 41 from the fifth storage unit 34. The video data reading unit 43 acquires a first period set for each event code, and reads from the fifth storage unit 34 video data captured around the mounter 100 between the time when the event occurred and a time preceding the occurrence time by the first period. The video data reading unit 43 may determine the first time of the video data to be read for the event code based on a table in which events (event codes) and first times corresponding to the events are associated with each other, and the event code acquired from the code reading unit 41. The period between the event occurrence time and the time one hour before the occurrence time is a synchronization target period (video synchronization period shown in FIG. 7, described later) to be synchronized in the video data.

[0086] Furthermore, video data reading unit 43 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 code reading unit 41, 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 fifth storage unit 34. Note that at least one of head camera 200 and surveillance camera 300 is selected in accordance with the event. Video data reading unit 43 is an example of a second acquisition unit.

[0087] In the table, whether head camera 200 is associated as a camera corresponding to an event may be determined depending on whether a human work defect is included as one of the assumed causes of the event (as a possible cause of the event). For example, if a human work defect is included as one of the causes of the event, head camera 200 may be associated as a camera corresponding to the event in the table. For example, if a pickup error (component pickup error) occurs as an event, one of the assumed causes includes 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 a camera corresponding to the pickup error. Note that data synchronization management unit 40 may store, for each event, information indicating whether a human work defect is included as a cause of the event.

[0088] 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 acquired from the code reading unit 41 from the sixth memory unit 36. The work record data reading unit 44 acquires a second time period set for each event code and reads work record data from the sixth memory unit 36, the work record data being 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 second times corresponding to the events are associated with each other and the event code acquired 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 a synchronization target period (a report synchronization period shown in FIG. 7 , described later) that is the synchronization target period for the work record data.

[0089] 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 them as event information. In other words, the association unit 45 stores the event code, the target video data, and the target work record data in synchronization with each other.

[0090] For example, the association unit 45 may determine whether the event that has occurred is an event that stops the mounter 100 or an event that does not stop the mounter 100, 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 the target work record data and store them as event information in the seventh storage 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 storage unit 46.

[0091] 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.

[0092] The seventh storage unit 46 stores the event information associated by the association unit 45.

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

[0094] [1-4. Placement of surveillance cameras] 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, 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 an example of a mounting line. In FIG. 5, the board transport direction is from left to right on the page, and of the component mounters 111-115 on the first production line L1, the component mounter 111 is located at the most upstream position, and of 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 component mounters 111 to 115, 121 to 125 shown in Fig. 5. Hereinafter, when there is no need to distinguish between the component mounters 111 to 115, 121 to 125, they will also be referred to as the component mounter 100.

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

[0096] 5, when a production line is configured with a plurality of component mounters 100, the monitoring camera 300 is arranged, for example, around the component mounter 100 located on the upstream side among the plurality of component mounters 100. In this embodiment, the monitoring camera 300 is arranged around the component mounters 111 and 121 located at the most upstream side among the plurality of component mounters 100.

[0097] For example, the monitoring camera 310 on the front side of the first production line L1 is arranged near the board entrance of the component mounter 111 on the front side of the component mounter 111, and the monitoring camera 320 on the rear side of the first production line L1 is arranged near the board entrance of the component mounter 111 on the rear side of the component mounter 111. The monitoring cameras 310 and 320 are arranged, for example, so as to sandwich the component mounter 111 therebetween.

[0098] Furthermore, for example, the monitoring camera 330 on the front side of the second production line L2 is arranged near the board entrance of the component mounter 121 on the front side of the component mounter 121, and the monitoring camera 340 on the rear side of the second production line L2 is arranged near the board entrance of the component mounter 121 on the rear side of the component mounter 121. The monitoring cameras 330 and 340 are arranged, for example, so as to sandwich the component mounter 121 therebetween.

[0099] The second video data may be video data captured by the monitoring cameras 310, 320, 330, and 340 arranged around the component mounter 100 located at the most upstream position among the multiple component mounters 100.

[0100] Of the front-side and rear-side monitoring cameras, video data from a camera corresponding to an event is associated with the event. Taking the first production line L1 as an example, when an event occurs on the front side of one of the mounters 100 on the first production line L1, video data from the monitoring camera 310 capturing an image of the front side of the mounter 100, out of the monitoring cameras 310 and 320, is associated with the 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.

[0101] 5, and may be installed at any position as long as it is possible to capture an image of the entire mounting line. Also, although monitoring cameras 310 and 320 are installed around component mounter 111, this is not limiting, and only one of monitoring cameras 310 and 320 may be installed, or three or more monitoring cameras may be installed. Also, the type and position of the monitoring cameras to be installed can be selected and changed depending on the environment of the factory where the production line is installed.

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

[0103] [2-1. How to manage event information] 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 component mounter 100.

[0104] 6, the component mounter 100 starts production (S11). For example, a manufacturing line including the component mounter 100 starts production.

[0105] Next, the mounter 100 determines whether an event has occurred (S12). If an error has occurred or an operation such as supplying a component has occurred, the mounter 100 determines that an event has occurred (Yes in S12) and notifies the intra-facility data collector 20 of an equipment log indicating the occurrence of the event (S13), and if it determines that an event has not occurred (No in S12), it continues production.

[0106] If the determination in step S12 is Yes, the mounter 100 may notify the operator that an event has occurred. The mounter 100 may, for example, turn on a warning light or emit a warning sound.

[0107] The head camera 200 and the surveillance camera 300 may start capturing images when the mounter 100 starts production, or may start capturing images before the mounter 100 starts production. For example, the head camera 200 and the surveillance camera 300 may start capturing images from a time that is one hour earlier than the time the mounter 100 starts production. Therefore, the outside-facility data collection unit 30 starts 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). The collection and storage of the video data continues while the mounter 100 is in production. The division unit 32 then sequentially divides the video data acquired via the video data collection unit 31 and stores the divided data in the fifth storage unit 34.

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

[0109] When 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 the event code from the intra-facility data collection unit 20 is an example of acquiring event occurrence information including information indicating that an event has occurred.

[0110] The synchronization instruction means to output an instruction to execute a process of storing the event code of the monitored event in association with the external data. The instruction may be a dedicated command or an event code.

[0111] Furthermore, the intra-facility data collection unit 20 stores the event code in the second storage unit 24. The intra-facility data collection unit 20 may store an equipment log including the event code in the second storage unit 24. Furthermore, 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.

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

[0113] The synchronization target period will now be described with reference to Fig. 7. Fig. 7 is a diagram showing the relationship between an event and the video data and work record data associated with the event according to this embodiment. The horizontal axis in Fig. 7 represents time. Fig. 7 is a diagram showing the correspondence over time between an equipment event, work record data associated with the equipment event, 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).

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

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

[0116] The video data reading unit 43 determines a video synchronization period according to an event that has occurred. For example, the video data reading unit 43 determines a video synchronization period according to the event based on a table in which events (for example, event codes) are associated with a first time. In the example of Fig. 7, the video synchronization period is from time t2 to time t3. Time t2 is set to time t3 as a reference and is one hour before time t3.

[0117] In this way, the video data associated with the monitored event is video data captured during a specified period going back to the time of the event occurrence, in order to determine whether or not there was any external activity that could have been a cause of the event before it occurred.

[0118] 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.

[0119] 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 in which events (for example, event codes) are associated with the second time. In the example of FIG. 7, the report synchronization period is from time t3 to time t5. Time t5 is the time that is the second time after time t3, with time t3 as the reference time.

[0120] In this way, the work record data associated with the monitored event is report data for the work performed within a specified period from the time the event occurred, in order to understand the work performed by the mounter 100 after the event occurred.

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

[0122] In this embodiment, the video data is divided and stored in 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 of head camera 200, the video data of the first monitoring camera, and the video data of the second monitoring camera are read out from fifth storage unit 34 as video data of Video Split:1-1 to Video Split:1-3.

[0123] Next, the data synchronization management unit 40 reads out the work record data for the synchronization period (S43). The work record data reading unit 44 of the data synchronization management unit 40 reads out 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 when the equipment event is an event for which event information is to be stored. Step S43 is an example of acquiring work record data.

[0124] At the time an event occurs, work record data corresponding to the event is not stored in the sixth storage unit 36. The outside-equipment data collection unit 30 collects work record data from the information terminal 400 over the report synchronization period and stores the work record data in the sixth storage 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 storage unit 36. In this embodiment, "Report1," which is work record data performed between time t3 and time t5 shown in FIG. 7, is read out.

[0125] 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. 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 only 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.

[0126] Furthermore, if work record data including a synchronization ID corresponding to the equipment event is stored in the off-equipment data collection unit 30, the data synchronization management unit 40 may store the work record data including the synchronization ID in the seventh memory unit 46 in association with the equipment log (event).

[0127] Next, we will explain the same equipment event that occurred multiple times (four times of Event2) between time t8 and time t11 shown in Fig. 7. The equipment event is an event in which the same equipment event occurred multiple times (four times in the example of Fig. 7) within a predetermined period. The predetermined period is set in advance.

[0128] When determining a synchronization period for the same equipment event that occurred multiple times within a predetermined 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 among the multiple occurrences of the same equipment event. In the case of Figure 7, the video synchronization period and report synchronization period for the four occurrences of Event2 are determined based on time t11.

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

[0130] Then, in step S44, the four occurrences of the same equipment event that occurred from time t8 to time t11, the video data of 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 occurrences of the same equipment event is associated with the video data and work record data acquired based on the occurrence time of the last equipment event among the multiple occurrences of the equipment event, and stored as event information. This allows multiple occurrences of the same equipment event to be checked together, thereby reducing the time required to identify the cause of the event compared to storing multiple occurrences of the same equipment event separately.

[0131] In this way, the data synchronization management unit 40, triggered by the occurrence of a monitored event, 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 in the conventional method of identifying the cause of the event from the equipment log, 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.

[0132] Conventionally, data outside the facility is not associated with data within the facility, so when the cause of an event is outside the facility, it takes a particularly long time.

[0133] [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.

[0134] 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.

[0135] When a login process is performed on the information terminal 600, the data synchronization management unit 40 performs an access authentication process to determine whether or not access should be permitted (S102). The output unit 47 of the data synchronization management unit 40 performs the access authentication process based on, for example, a user name, a password, etc.

[0136] Next, if the access authentication is passed, 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 or the like.

[0137] 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 on a web browser or the like. For example, even if the user is in a remote location from a facility (e.g., a factory) where the production line is installed, the user can view and download event information via the information terminal 600.

[0138] 9 is a diagram showing an example of display of event information according to the present embodiment, showing an image displayed on display unit 610.

[0139] As shown in FIG. 9, first, the display unit 610 displays a first image 610a. The first image 610a is an image based on the intra-facility data out of the intra-facility data and the extra-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 an equipment event list, and is an image that allows the user to select, from among multiple events, the extra-facility data of which event to view. The equipment event list is an example of a list based on one or more pieces of event occurrence information.

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

[0141] The occurrence date and time is the date and time when 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 where the event occurred, and the facility name is information for identifying the mounter 100 where the event occurred. The side is information indicating whether the event occurred on the front side ("Front" in FIG. 9) or the rear side ("Rear" in FIG. 9) of the mounter 100. The event main message is information indicating the state of the mounter 100 where 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 external data is to be displayed.

[0142] 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).

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

[0144] The second image 610b is an image based on the external 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 internal data and external 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 internal data and external 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.

[0145] (Modification of the embodiment) The management system according to this modification will be described below with reference to FIGS. 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 that of 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 the association between events and work record data is performed based on a synchronization ID.

[0146] FIG. 10 is a sequence diagram showing the operation of the management system according to this modification.

[0147] 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 may be performed by a light-emitting unit of the mounter 100 emitting light, as long as it can notify the operator of the alert.

[0148] When the worker is notified of the alert, the worker takes action to deal with the event (S60).

[0149] 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). It can be said that the data synchronization management unit 40 issues a synchronization ID when the occurrence of a monitored event is triggered. The synchronization ID is an ID for associating 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.

[0150] The synchronization ID is not limited to a number, but may be a symbol, a letter, or a combination thereof, as long as it can associate an event with work record data. 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.

[0151] Next, the data synchronization management unit 40 determines the synchronization target 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 target period for the video data in accordance with the read event code based on a table or the like. Note that in this modification, the data synchronization management unit 40 does not determine the report synchronization period.

[0152] Here, the synchronization target period for video data will be explained with reference to Fig. 11. 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 this modification. The horizontal axis in Fig. 11 represents time. Fig. 11 is a diagram showing the correspondence over time between facility events, video data from each monitoring camera, video data from head camera 200, and work record data corresponding to the facility events.

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

[0154] First, the facility event (Event A) that occurred at time t25 will be described. This facility event is a single event that occurred.

[0155] The data synchronization management unit 40 determines the video synchronization period shown in FIG. 11 based on the event (event code) that has occurred.

[0156] The video data reading unit 43 determines a video synchronization period according to an event that has occurred. For example, the video data reading unit 43 determines a video synchronization period according to the event based on a table in which events (for example, event codes) are associated with a first time. In the example of Fig. 11, the video synchronization period is from time t24 to time t25. Time t24 is set as the reference time and is one hour before time t25.

[0157] 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 including the video synchronization period as the video data to be associated with the 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 equipment event occurrence time (time t25) as the video data to be associated with the equipment event A.

[0158] Video data readout unit 43 determines that the video data of the third monitoring camera to be associated with equipment event A is the video data of Video Split: 1-2 to Video Split: 1-4. The video data of Video Split: 1-2 to Video Split: 1-4 includes video data captured between time t25 and time t26. Furthermore, video data readout unit 43 determines that the video data of the fourth and fifth monitoring cameras to be associated with equipment event A is the video data of Video Split: 1-2 to Video Split: 1-4. The video data of Video Split: 1-2 to Video Split: 1-4 includes video data captured between time t25 and time t27. Furthermore, video data readout unit 43 determines that the video data of head camera 200 to be associated with equipment event A is the video data of Video Split: 1-1 to Video Split: 1-4. The video data of Video Split: 1-1 to Video Split: 1-4 includes video data captured between time t25 and time t28.

[0159] Next, the same equipment event (four occurrences of Event B) that occurred multiple times at time t32, time t33, time t34, and time t35 will be described. The equipment event is an event in which the same equipment event occurred multiple times (four times in the example of FIG. 11) within a predetermined period. The predetermined period is set in advance.

[0160] When determining a video synchronization period for the same equipment event that occurs multiple times within a predetermined 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 among the multiple occurrences of the same equipment event. In the case of FIG. 11, the video synchronization period (time t31 to time t35) for four occurrences of Event B is determined based on time t35. Note that the video synchronization period is longer than the predetermined period.

[0161] The processing after determining the video synchronization period is the same as in the case of event A, and detailed description will be omitted. Video data readout unit 43 determines the video data of the third monitoring camera to be associated with equipment event B as the video data of Video Split: 1-10 to Video Split: 1-12. The video data of Video Split: 1-10 to Video Split: 1-12 includes video data captured between time t35 and time t36. Furthermore, video data readout unit 43 determines the video data of the fourth and fifth monitoring cameras to be associated with equipment event B as the video data of Video Split: 1-9 to Video Split: 1-12. The video data of Video Split: 1-9 to Video Split: 1-12 includes video data captured between time t35 and time t37. Furthermore, video data readout unit 43 determines the video data of head camera 200 to be associated with equipment event B as the video data of Video Split: 1-9 to Video Split: 1-12. The video data of 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.

[0162] 10 again, next, the data synchronization management unit 40 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 storage 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) has not yet been stored in the seventh storage unit 46.

[0163] At least a part of the processing from steps S44 to S46 may be performed while the worker is handling the event. For example, all of the processing from steps S44 to S46 may be performed by the time the worker completes handling the event.

[0164] Next, when the operator finishes handling the event and receives an operation to resume production from the operator (S15), the mounter 100 resumes production (S16). The mounter 100 may receive the operation via an operation unit, or may receive the operation from another device such as the information terminal 400.

[0165] 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 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 is entered). Then, the information terminal 400 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 storage unit 36.

[0166] Here, the registration screen for registering a work record will be described with reference to Fig. 12. Fig. 12 is a diagram showing an example of the registration screen for registering a work record according to this modified example.

[0167] 12, the registration screen includes the worker ID, synchronization ID, event name, occurrence date and time, location, completion date and time, cause, work (work 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.

[0168] The worker ID displays the name of the user who is logged in to the information terminal 400. If the logged-in user is different from the user who performed the work, the worker ID of the user who performed the work is selected from the worker list by pressing the change button.

[0169] The synchronization ID displays a list of synchronization IDs issued during the time period when the event occurred (for example, the year, month, day, hour, minute). The worker selects the appropriate synchronization ID.

[0170] 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 from the data synchronization management unit 40 together with the synchronization ID, for example.

[0171] The completion date and time is the time when the event response work is completed, and is input by the worker.

[0172] The cause is a field for inputting the actual cause of an event, and is selected by the operator from a list. The example in FIG. 12 shows an example in which "splicing error" is selected. If the corresponding cause is not in 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 depending on the event that occurred, or may display pre-set causes.

[0173] The "Task" field is where the actual event response task performed is entered, and is selected by the worker from a list. In the example of Figure 12, "Splicing Correction" is selected. If the corresponding task is not in 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 displayed list of tasks may display tasks corresponding to the factors inferred by the system in response to the event that occurred, or may display pre-set tasks.

[0174] The memo is a field where supplementary information can be entered as text, if necessary.

[0175] The registration screen displayed on the information terminal 400 according to the embodiment may be a screen obtained by deleting the "synchronization ID" item from the registration screen shown in FIG.

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

[0177] Next, the data synchronization management unit 40 associates the written work record data with the synchronization ID and stores it in the seventh storage unit 46 (S47). The data synchronization management unit 40 associates the work record data acquired from the outside-equipment 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 storage 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 storage unit 46.

[0178] 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 of 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 work record data as event information, in association with the equipment log and video data associated with the one synchronization ID.

[0179] 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. Also, 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.

[0180] Fig. 13 is a diagram showing the data structure of the event information stored in the seventh storage unit 46 according to this modification. Fig. 13 shows the structure of various data associated with each other by synchronization ID.

[0181] As shown in FIG. 13, the event information is information in which the equipment log, video data, and work record data are associated with each other by a synchronization ID.

[0182] (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.

[0183] For example, in the above-described embodiment and the like, 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 limiting. The video data may be stored without being divided into split intervals. In other words, the outside-equipment data collection unit does not need to have a dividing unit.

[0184] In the above-described embodiments, an example has been described in which the mounting line includes multiple component mounters, but the present invention is not limited to this. The mounting line may include only one component mounter. Furthermore, a component mounter may not be incorporated into a mounting line and may be used as a standalone mounter.

[0185] Furthermore, in the above-described embodiment, an event code is exemplified as the event occurrence information, but the event occurrence information may be any information that can identify what event has occurred, such as an event name.

[0186] Furthermore, in the above-described embodiment, an example has been described in which it is determined whether an event is an event to be monitored (S21 shown in FIG. 6), but the present invention is not limited to this, 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 mounter may be stored in the second storage unit.

[0187] Furthermore, in the above embodiments, an example has been described in which the object is a substrate, but the present invention is not limited thereto and may be, for example, a flat object (e.g., an iron plate) or another object. Furthermore, in the above embodiments, mounting a component on a substrate has been described as an example of predetermined processing, but the present invention is not limited thereto and may be fixing a component to a substrate 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.

[0188] Furthermore, in the above-described embodiment and the like, the first time period is an hourly number (for example, 30 minutes) but may be the number of splits if the video data is stored in split units.

[0189] Furthermore, in the above-described embodiments, the data synchronization management unit may extract work record data that includes a synchronization ID issued as a trigger when the event occurs from one or more pieces of work record data that are records of work performed on the component mounter between the time the event occurred and the time two hours after the time the event occurred, and associate the extracted work record data with the equipment log and video data.

[0190] The order in which each step is executed in the sequence diagram is merely an example for specifically explaining the present disclosure, and an order other than the above may be used. Also, some of the steps may be executed simultaneously (in parallel) with other steps, or some of the steps may not be executed.

[0191] In the above embodiments, each component may be configured with dedicated hardware, or may be realized by executing a software program suitable for each component. Each component may 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.

[0192] The division of functional blocks in the block diagram is an example, and 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 another functional block.Furthermore, the functions of multiple functional blocks having similar functions may be processed in parallel or in time-sharing by a single piece of hardware or software.

[0193] Furthermore, the data management device according to the above-described 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 external data collection unit, and the data synchronization management unit may each be realized by a different device (such as a personal computer). In this case, the intra-facility data collection unit and the external data collection unit are located within a factory where a 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. 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.

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

[0195] Furthermore, each component described in the above embodiments may be implemented as software or, typically, as an LSI, an integrated circuit. These components may be integrated individually on a single chip, or some or all of them may be integrated on a single chip. While LSI is used here, it may also be referred to as an IC, system LSI, super LSI, or ultra LSI depending on the level of integration. Furthermore, the integration method is not limited to LSI; it may be implemented using a dedicated circuit (a general-purpose circuit that executes a dedicated program) or a general-purpose processor. It is also possible to use a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which allows the connection or settings of circuit cells within an LSI to be reconfigured. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or a derivative technology, that technology may naturally be used to integrate the components.

[0196] A system LSI is an ultra-multifunctional LSI manufactured by integrating multiple processing units on a single chip, and is specifically 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.

[0197] 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.

[0198] Furthermore, 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, the distributed program may be installed in a device having another processor, and the program may be executed by the processor, thereby causing the device to perform each of the above processes. [Industrial Applicability]

[0199] The present disclosure is useful for a management method for managing data related to component mounters, etc. [Explanation of symbols]

[0200] 1 Management System 10 Data management device (management device) 20 In-facility data collection section 21 Collection Department 22 Event code extraction section 23 1st memory section 24 2nd memory section 25 Parts data extraction section 26 Third memory section 30. Off-site data collection unit 31 Video data collection unit 32 Division 33 4th memory section 34 5th memory section 35 Work Record Data Collection Unit 36 6th memory section 40 Data Synchronization Management Department 41 Code reading unit (first acquisition unit) 42 Parts data reading section 43 Video data reading unit (second acquisition unit) 44 Work record data reading unit (third acquisition unit) 45 Mapping section 46 7th memory section 47 Output section 100, 111, 112, 113, 114, 115, 121, 122, 123, 124, 125 Component mounter 200 Head Camera (1st Camera) 300, 310, 320, 330, 340 Surveillance camera (second camera) 400, 600 information terminal 500 Internet 610 Display section 610a Image 1 610a1 Icon 610b 2nd image L1 First production line L2 Second production line

Claims

1. 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 associated with the video data and the work record data and stored as the event information. Management method.

2. A plurality of cameras are provided around the component mounter, In the acquisition of the video data, video data captured by one or more cameras selected from the plurality of cameras in accordance with the event is acquired. The management method according to claim 1 .

3. 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, At least one of the first camera and the second camera is selected in response to the event. The management method according to claim 2 .

4. A mounting line is configured that includes a plurality of the component mounters, The video data is video data captured by the first camera arranged around the component mounter located at the most upstream position among the plurality of component mounters. The management method according to claim 3.

5. 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; In storing the event information, the event occurrence information indicating the plurality of occurrences of the event is associated with the video data and the work record data acquired based on the occurrence time of the last event, and the event information is stored. The management method according to any one of claims 1 to 4.

6. determining whether the event is an event for which the event information is to be stored based on the event occurrence information; If the event is an event for which the event information is to be stored, the video data and the work record data are acquired. The management method according to any one of claims 1 to 5.

7. 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; If the event is the second event, the event occurrence information and the video data are stored in association with each other as the event information. The management method according to claim 6.

8. 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 associated with the event identification information included in the work record data, and the associated data is stored as the event information. The management method according to any one of claims 1 to 7.

9. determining the first time and the second time according to the event; The management method according to any one of claims 1 to 8.

10. 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; An image based on the video data and the work record data associated with the acquired event is displayed. Display method.

11. 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; an association unit that associates the event occurrence information with the video data and the work record data and stores the associated information as the event information; Management device.

Images