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

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

The present disclosure relates to a management method, a display method, and a management device for managing event information regarding an event that has occurred in a mounter.

Patent Document 1 discloses an external monitoring camera that captures an image of an external work area of a component mounter, a display device that displays an image captured by the external monitoring camera, and a recording device that records the image captured by the external monitoring camera. An outboard area monitoring system for a component mounter comprising a device is disclosed.

WO2018/055754

By the way, from the viewpoint of suppressing a decrease in the operation rate of a component mounter, it is desirable to shorten the time required to identify the cause of an event that has occurred in the component mounter. In the system disclosed in Patent Literature 1, there is room for improvement because it is difficult to shorten the time required to identify the cause when the cause is not reflected in the image captured by the external monitoring camera.

Therefore, the present disclosure provides a management method, a display method, and a management device that can more reliably reduce the time required to identify the cause of an event that occurred in a component mounter.

A management method according to an aspect of the present disclosure is a management method for managing event information related to an event that has occurred in a component mounter, the event occurrence information including information indicating that the event has occurred, and the event occurrence information is acquired. obtaining image data of the surroundings of the component mounter between the occurrence time indicating the occurrence time and the time one hour before the occurrence time; Acquiring at least one of work record data, which is a record of work performed on the mounter during the time, and work record data including event identification information issued with the occurrence of the event as a trigger; The event occurrence information, the video data and the work record data are associated with each other and stored as the event information.

A display method according to an aspect of the present disclosure is a display method for displaying the event information stored by the above management method, wherein a list based on one or more of the event occurrence information is displayed, and one item from the list is displayed. A selection of an event is obtained, and an image based on the video data and the work record data associated with the obtained event is displayed.

A management device according to an aspect of the present disclosure is a management device that manages event information about an event that has occurred in a component mounter, and includes a first acquisition that acquires event occurrence information that includes information indicating that the event has occurred. a second acquisition unit configured to acquire video data obtained by imaging the surroundings of the component mounter between an occurrence time indicating the time at which the event occurred and a time one hour before the occurrence time; and the occurrence time. and work record data that is a record of work performed on the component mounter during the second time after the occurrence time, and event identification information issued with the occurrence of the event as a trigger. A third acquisition unit that acquires at least one of work record data, and an association unit that associates the event occurrence information with the video data and the work record data and stores the event information as the event information.

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 component mounter.

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

A management method according to an aspect of the present disclosure is a management method for managing event information related to an event that has occurred in a component mounter, the event occurrence information including information indicating that the event has occurred, and the event occurrence information is acquired. obtaining image data of the surroundings of the component mounter between the occurrence time indicating the occurrence time and the time one hour before the occurrence time; Acquiring at least one of work record data, which is a record of work performed on the mounter during the time, and work record data including event identification information issued with the occurrence of the event as a trigger; The event occurrence information, the video data and the work record data are associated with each other and stored as the event information.

Thus, when an event occurs, the event occurrence information of the event can be stored in association with the video data and the work record data. For example, when video data alone is insufficient for information, it is possible to identify the cause of an event by using work record data as well. In addition, it is possible to save the user from searching for the video data and work record data corresponding to the event from a database or the like. Therefore, according to the management method according to one aspect of the present disclosure, it is possible to shorten the time required to search for data and the time required to identify the cause of an event that occurred in a component mounter, so that the time required to identify the cause of an event that occurred in a mounter can be more reliable. can be shortened to

Further, for example, a plurality of cameras are provided around the component mounter, and in the acquisition of the image data, one or more cameras selected from the plurality of cameras according to the event captured images. Video data may be acquired.

As a result, video data from cameras corresponding to events can be associated with event occurrence information, making it possible to shorten the time required to check video data compared to when video data from multiple cameras are associated with event occurrence information. is. Therefore, according to the management method according to one aspect of the present disclosure, even when a plurality of cameras are provided around the mounter, the time required to identify the cause of the event that occurred in the mounter can be reduced. It can certainly be shortened.

Further, for example, 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 a camera and said second camera may be selected.

As a result, the video data of the type of camera corresponding to the event is associated with the event occurrence information. That is, the 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 reduce the time required to identify the cause of the event that occurred in the mounter.

Further, for example, a mounting line including a plurality of the component mounters is configured, and the image data is captured by the first camera arranged around the component mounter positioned most upstream among the plurality of the component mounters. may be video data captured by

As a result, the first camera can more clearly capture an image of the vicinity of the component mounter on the upstream side, where the frequency of occurrence of events is expected to increase. Such video data can contribute to shortening the time required to identify the cause of an event that has occurred in an upstream component mounter. For example, when the component mounter on the upstream side is a component mounter that mounts minute components, it can greatly contribute to shortening the time required to identify the cause of an event that occurred in such a component mounter.

Further, for example, when the same event occurs multiple times within a predetermined period, the time of the event that occurred last among the multiple events is set as the occurrence time, and the storage of the event information stores the multiple times of the event. The event occurrence information indicating an event may be associated with the video data and the work record data acquired based on the occurrence time of the last event and stored as the event information.

As a result, it is possible to associate the event information with the video data in the time period that can cause the occurrence of an event. The storage capacity required for storing event information can be reduced compared to the case where video data is associated with each event occurring within a predetermined period.

Further, for example, based on the event occurrence information, it is determined whether or not the event is an event for which the event information is to be stored, and if the event is an event for which the event information is to be stored, Acquisition of the video data and the work record data may be performed.

Thereby, the process of storing the event information can be performed only when the event is the target event. When the target event is set by the user, only the event information that the user considers necessary can be stored. Therefore, it is possible to effectively shorten the time required to identify the cause of the event desired by the user.

Further, for example, the target event includes 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, the event is the first event. , the event occurrence information, the video data and the work record data are associated with each other and stored as the event information, and when the event is the second event, the event occurrence information and the video data may be associated and stored as the event information.

As a result, it is possible to further store event information in which event occurrence information and video data are associated with an event in which the mounter does not stop. Therefore, according to the management method according to one aspect of the present disclosure, it is possible to further reduce the time required to identify the cause of an event that has occurred in a component mounter and does not stop the component mounter.

Further, for example, when work record data including event identification information issued with the occurrence of the event as a trigger is acquired, in storing the event information, before the work record data is acquired, the event occurrence information and the video data are added with event identification information and stored, and after the work record data is acquired, the event occurrence associated with the work record data and the event identification information included in the work record data The information and the video data may be associated with each other and stored as the event information.

Thereby, the event occurrence information, the video data, and the work record data can be associated with each other using the event identification information.

Also, for example, the first time and the second time may be determined according to the event.

Accordingly, by properly determining the first time and the second time, it is possible to associate the video data and the work record data useful for specifying the cause of the event occurrence with the event occurrence information.

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

As a result, the video data and work record data corresponding to the event can be presented to the user simply by selecting the event that the user wants to check from the list. In other words, it is possible to omit the work of searching a database or the like for video data and work record data corresponding to an event that the user wants to confirm. In addition, since the work record data is associated with the event, the user can specify the cause of the event occurrence by using the work record data when the information is insufficient only with the video data. Therefore, according to the display method according to one aspect of the present disclosure, it is possible to shorten the time required to search for data and the time required to identify the cause of an event that has occurred in a component mounter. can be shortened to

Further, a management device according to an aspect of the present disclosure is a management device that manages event information regarding an event that has occurred in a component mounter, and acquires event occurrence information that includes information indicating that the event has occurred. 1 acquisition unit, a second acquisition unit that acquires video data obtained by imaging the surroundings of the component mounter between an occurrence time indicating the time at which the event occurred and a time that is a first hour before the occurrence time; Work record data, which is a record of work performed on the mounter during the time of occurrence and the time after the second time from the time of occurrence, and event identification information issued with the occurrence of the event as a trigger. and a correlating unit that associates the event occurrence information with the video data and the work record data and stores the event information as the event occurrence information.

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

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

It should be noted that the embodiments described below are all comprehensive or specific examples. Numerical values, shapes, components, arrangement positions and connection forms of components, steps, order of steps, and the like shown in the following embodiments are examples, and are not intended to limit the present disclosure. Further, among the constituent elements in the following embodiments, constituent elements not described in independent claims will be described as optional constituent elements.

Each figure is a schematic diagram and is not necessarily strictly illustrated. Therefore, for example, the scales and the like do not necessarily match in each drawing. Moreover, in each figure, the same code|symbol is attached|subjected about the substantially same structure, and the overlapping description is abbreviate|omitted or simplified.

Also, in this specification, terms that indicate the relationship between elements such as equal, and numerical values and numerical ranges are not expressions that express only strict meanings, but substantially equivalent ranges, for example, about several percent This expression means that a difference of (for example, about 10%) is also included.

(Embodiment)
A management system including a management device according to the present embodiment will be described below with reference to FIGS. 1 to 9. FIG.

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

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

The management system 1 manages various types of information acquired from the mounter 100, the head camera 200, the monitoring camera 300, and the information terminal 400 in association with each other as necessary. It is an information processing system that enables confirmation of information. More specifically, the management system 1 stores in-facility data (eg, facility log) acquired from the mounter 100 and outside-facility data (eg, first video data, second video data, and work record data) are associated and managed as necessary. The information terminal 600 can acquire event information in which the in-facility data and the out-of-facility data are associated via the data management device 10 .

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

The data management device 10 performs a process of correlating and storing the in-facility data and the out-of-facility data with an in-facility data collection unit 20 that acquires in-facility data and an outside-facility data collection unit 30 that acquires outside-facility data. and a data synchronization manager 40 . Details of the data management device 10 will be described later. The data management device 10 is an example of a management device. Note that the management device may have at least the functions of the data synchronization management section 40 .

The component mounter 100 is a device included in a manufacturing line (for example, the first manufacturing line L1 and the second manufacturing line L2 shown in FIG. 5), and is a mounting facility that mounts components on an object (work) such as a substrate. . The component mounter 100 includes, for example, a transport unit that transports a substrate, a feeder that supplies components to be mounted on the substrate, and a mounting head equipped with component suction nozzles (nozzles) that can individually move up and down by sucking components from the feeder. (head), a moving unit for moving the head, and the like. The transport section is configured including, for example, one or more transport lanes. A plurality of nozzles are attached to the head, for example. The component mounter 100 further includes a flow sensor for measuring the flow rate of air flowing inside the nozzle, a sensor for determining whether or not the nozzle has picked up a component, and a sensor for calculating the amount of displacement of the picked-up position of the picked-up component. It may also have a sensor for detecting nozzle malfunction, such as a part recognition camera. Moreover, the mounter 100 may have various sensors capable of detecting malfunctions of other components such as the head, the transport section, the feeder, and the head and moving section. In this way, the mounter 100 has a configuration capable of detecting an abnormality including malfunction inside the mounter 100 . Note that the configuration of the component mounter 100 is not limited to the above, and is appropriately determined according to the type, shape, processing method, and the like of the object and components.

The components are electronic components, such as resistors and capacitors, but are not limited to these. Moreover, the object is not limited to a substrate, and may be any object to be processed that can be processed in a predetermined manner.

The mounter 100 outputs the equipment log acquired within the mounter 100 to the in-equipment data collection unit 20 . The facility log includes detection results acquired by various sensors and the like of the mounter 100 . The facility log includes, for example, the time of occurrence of the event (an example of date and time of occurrence) and the content of the event (eg, the content of the 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 occurrences of the same event, the production line name (an example of the location) of the mounter 100 where the event occurred, the event name, and the like. The equipment log may also include the number of occurrences of the same event, the production line name of the mounter 100 where the event occurred, and the like. The equipment log may also include component data regarding components mounted by the component mounter 100 . For example, the equipment log may include component data of components mounted by the component mounter 100 in which the event occurred. The part data includes, for example, part identification information (for example, model number), the number of parts used, and the like.

The target event includes, for example, at least the occurrence of an error in the mounter 100, and includes, for example, an event in which the mounter 100 stops. Moreover, the target event may further include an event in which a predetermined work is performed on the mounter 100 . The predetermined work may be, for example, supplying a component, performing a predetermined operation on the operation unit (for example, touch panel) of the mounter 100, or It may be cleaning the mounter 100 , or setting conditions in the component mounter 100 . Among target events, an event in which mounter 100 stops is an example of a first event, and an event in which mounter 100 does not stop among target events is an example of a second event. The events of interest include at least a first event.

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

The head camera 200 is a wearable camera worn by a worker who works around the mounter 100 (for example, the floor on which the mounter 100 is arranged). The head camera 200 captures, for example, video data seen from the line of sight of the worker. The head camera 200 captures, for example, the state of the work performed by the worker on the mounter 100 on which the event has occurred. Such video data shows, for example, the situation at hand of the worker, and it is possible to check the worker's work mistakes. Note that the head camera 200 is not limited to being mounted on the head of the worker, and may be mounted on other parts of the worker. Head camera 200 is an example of a first camera, and video data captured by head camera 200 is an example of first video data.

The monitoring camera 300 is arranged around the mounter 100 (for example, the floor on which the mounter 100 is arranged) and captures an image of a predetermined range including the mounter 100 . The predetermined range may be, for example, a range that includes the entire mounter 100 . The predetermined range may be, for example, a range including the entire component mounter 100 and a work area in which work related to the component mounter 100 is performed. Surveillance camera 300 is, for example, fixedly provided. The surveillance camera 300 may be, for example, a fisheye camera installed on the ceiling or the like. The image captured by surveillance camera 300 may be a bird's eye image. The installation position of the monitoring camera 300 will be described later. Monitoring camera 300 is an example of a second camera, and video data captured by monitoring camera 300 is an example of second video data.

The number of imaging devices included in the management system 1 is not particularly limited. may be provided.

Information terminal 400 accepts an input of a work record, which is a record of work (for example, repair work) performed by a worker on mounter 100 after an event of interest occurs in mounter 100, and performs the work. It is a device for generating recording data (work report). The information terminal 400 is, for example, a mobile terminal such as a smart phone or a tablet terminal, but is not limited to these, and may be a personal computer or the like.

The work record data includes at least one of the worker name, work start date and time, event occurrence location, event phenomenon, event factor, countermeasure work content, and work end date and time.

The worker name is information identifying the worker who worked on the mounter 100 after the event occurred, and is acquired when the worker logs into the information terminal 400, for example.

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

The event occurrence location is information specifying the component mounter 100 in which the event occurred or the production line having the component mounter 100, and is input by an operator, for example.

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 suction error, a mounting error, or the like, but is not limited to these.

The event factor is information that the worker considers to be the event occurrence factor when the worker performs the work of the mounter 100, and is input by the worker, for example. The input may be selective or free-form.

The countermeasure work content is the work content performed by the worker on the component mounter 100 in which the event occurred, and is input by the worker, for example. The input may be a selection formula (for example, a guide content selection formula) or a free description formula. The contents of the work include, for example, replacement of parts, cleaning of components (for example, nozzles) of the mounter 100, and the like, but are not limited to these.

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

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

The information terminal 600 is a terminal device that is wirelessly communicably connected to the data management device 10 via a wide area communication network such as the Internet 500 and that is used to confirm event information stored by the data management device 10 . The information terminal 600 is, for example, a mobile terminal such as a smart phone or a tablet terminal, but is not limited to these, and may be a personal computer or the like.

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

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

The collection unit 21 collects equipment logs from the mounter 100 . The collection unit 21 may periodically (for example, every several hours) collect equipment logs from the mounter 100, or may collect the equipment logs by transmitting a request to transmit the equipment logs to the mounter 100. You may

The event code extraction unit 22 extracts events to be monitored from the events included in the facility log collected by the collection unit 21 and stores the events in the second storage unit 24 . In the present embodiment, the event code extraction unit 22 extracts the event codes described in the event code list stored in the first storage unit 23 from the event codes included in the equipment log. It can also be said that the event code extraction unit 22 determines whether or not the event is an event for which event information is to 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.

In addition to the event code, the event code extraction unit 22 stores at least one of the event occurrence time, the number of times the event occurred, the production line name where the event occurred, the facility name where the event occurred, etc. 24 may be stored. For example, the event code extraction unit 22 may store in the second storage unit 24 an equipment log that includes information about event codes in the event code list.

The first storage unit 23 stores information about an event to be monitored. If the facility log contains an event code that identifies an event, the first storage unit 23 stores a list of event codes to be monitored. Events to be monitored include events related to errors in the mounter 100 . The event to be monitored may be, for example, an event in which the mounter 100 stops. Such events include, but are not limited to, component pickup errors, mounting errors, and the like. Also, an event to be monitored may be set by an operator or the like, for example. Before starting production in mounter 100, a list of event codes is stored.

The second storage section 24 stores the event code extracted by the event code extraction section 22 . The second storage unit 24 stores only event codes to be monitored among the event codes included in the equipment log. In addition, the second storage unit 24 may store information indicating the time when the event occurred together with the event code. The second storage section 24 is accessible from the data synchronization management section 40 .

The parts data extraction unit 25 extracts parts data included in the facility log collected by the collection unit 21 and stores the extracted parts data in the third storage unit 26 . In the present embodiment, the component data extraction unit 25 extracts component data corresponding to the monitored event from the equipment log and stores the extracted component data in the third storage unit 26 . The third storage unit 26 stores, among the component data included in the equipment log, component data corresponding to the event code to be monitored (for example, component data corresponding to an error). That is, the third storage unit 26 stores the component data of the component mounted by the component mounter 100 when the event occurred.

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

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

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

As shown in FIG. 3, the external data collection unit 30 includes a video data collection unit 31, a division unit 32, a fourth storage unit 33, a fifth storage unit 34, a work record data collection unit 35, a 6 storage unit 36 . The outside-facility data collection unit 30 is realized by at least part of a computer or smartphone including a processor, memory, and the like. Specifically, the external data collection unit 30 functions as a video data collection unit 31, a division unit 32, and a work record data collection unit 35 by the processor operating according to a program stored in a memory.

The video data collection unit 31 collects video data from one or more imaging devices included in the management system 1 . In the present embodiment, video data collection unit 31 collects first video data from head camera 200 and second video data from monitoring camera 300 . The image data collection unit 31 may collect the first image data and the second image data periodically (for example, every few hours), or may request to transmit the image data to the head camera 200 and the monitoring camera 300. You may collect 1st video data and 2nd video data by transmitting. 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.

Based on the time intervals (split intervals) stored in the fourth storage unit 33, the division unit 32 divides the first video data and the second video data for each time interval, and stores them in the fifth storage unit 34. do. In other words, the first video data and the second video data are separated and managed by time intervals. As a result, it is possible to prevent the storage capacity of the fifth storage unit 34 from becoming tight. 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.

The fourth storage unit 33 stores the time period when the dividing unit 32 divides the video data. The time period is preset.

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

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 work record data periodically (for example, every few hours), or may collect the work record data by transmitting a request to transmit the work record data to the information terminal 400. may be collected. The work record data collection unit 35 stores the collected work record data in the sixth storage unit 36 .

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

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

[1-3. Configuration of Data Synchronization Management Section]
Next, the configuration of the data synchronization manager 40 will be described with reference to FIG. FIG. 4 is a block diagram showing the functional configuration of the data synchronization manager 40 according to this embodiment.

As shown in FIG. 4, the data synchronization management unit 40 includes a code reading unit 41, a parts data reading unit 42, a video data reading unit 43, a work record data reading unit 44, an associating unit 45, and a seventh It has a storage unit 46 and an output unit 47 . The data synchronization manager 40 is realized by at least part of a computer or smart phone including a processor, memory, and the like. Specifically, the data synchronization management unit 40 operates according to the program stored in the memory so that the data synchronization management unit 40 can read a code reading unit 41, a parts data reading unit 42, a video data reading unit 43, a work record data reading unit 44, It functions as an association unit 45 and an output unit 47 .

The code reading unit 41 reads an event code from the second storage unit 24 and outputs the read event code to the parts data reading unit 42 , video data reading unit 43 , work record data reading unit 44 and 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. Also, the code reading unit 41 may read information indicating the occurrence time of the event together with the event code. The code reading unit 41 is an example of a first obtaining unit.

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

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 image data reading unit 43 acquires the first period set for each event code, and images the surroundings of the mounter 100 between the time when the event occurred and the time before the first period from the time of occurrence. The image data thus obtained is read out from the fifth storage unit 34 . Based on a table in which an event (event code) and a first time corresponding to the event are associated, and the event code acquired from the code reading unit 41, the video data reading unit 43 reads video data in the event code. may be determined. Note that the period between the event occurrence time and the time one hour before the event occurrence time is a synchronization target period (video synchronization period shown in FIG. 7 to be described later) to be synchronized in video data.

In addition, the video data reading unit 43 acquires video data captured by one or more cameras selected according to the event. The video data reading unit 43 reads a table in which an event (event code) and a camera corresponding to the event (at least one of the head camera 200 and the monitoring camera 300) are associated with each other, and the event code acquired from the code reading unit 41. , the camera from which the video data is to be read is selected in the event code, and the video data of the selected camera is read from the fifth storage unit 34 . At least one of the head camera 200 and the monitoring camera 300 is selected according to the event. The video data reading unit 43 is an example of a second obtaining unit.

In the table, depending on whether one of the assumed factors for the event that occurred (as a possible cause of the event that occurred) includes a human work defect, the camera corresponding to the event It may have been determined whether the head camera 200 is associated. For example, if one of the factors of an event that has occurred includes a human work defect, the head camera 200 may be associated with the event as the camera corresponding to the event in the table. For example, when a pick-up error (part pick-up error) occurs as an event, one of the assumed factors is a human operation defect called "splicing error". Is required. That is, the head camera 200 is associated as the camera corresponding to the adsorption error. Note that the data synchronization management unit 40 may store information indicating whether or not a human work defect is included in the cause of the event for each event.

The work record data reading unit 44 reads work record data stored in the sixth storage unit 36 . The work record data reading unit 44 reads from the sixth storage unit 36 work record data for a period corresponding to the event code acquired from the code reading unit 41 . The work record data reading unit 44 acquires the second time set for each event code, and sends a message to the mounter 100 between the time when the event occurred and the time after the second time from the time when the event occurred. Work record data, which is a record of the work performed, is read from the sixth storage unit 36 . Based on a table in which an event (event code) and a second time corresponding to the event are associated, and the event code acquired from the code reading unit 41, the work record data reading unit 44 reads the work record in the event code A second period for reading data may be determined. The work record data reading unit 44 is an example of a third acquisition unit. The period between the event occurrence time and the second time after the event occurrence time is a synchronization target period (report synchronization period shown in FIG. 7 to be described later) to be synchronized in the work record data.

The association unit 45 combines the event code read by the code reading unit 41, 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. ) are associated with each other and stored as event information. In other words, the associating unit 45 synchronously stores the event code, the target video data, and the target work record data.

The associating unit 45 determines, for example, whether the event that has occurred is an event that causes the mounter 100 to stop or an event that does not cause the mounter 100 to stop, and based on the judgment result, provides information to be associated with the event code. can be different. For example, when the event is the first event, the association unit 45 associates the event code with the target video data and the target work record data and stores the event information in the seventh storage unit 46, and the event is the second event. If it is an event, the event code may be associated with the target video data and stored as event information in the seventh storage unit 46 .

By associating the target video data and the target work record data, when the event occurrence factor is an external factor (external factor) of the mounter 100, the target video data and the target work record data can Can be used to identify factors. Examples of external factors include, but are not limited to, operational errors by operators, material deficiencies, and the like. The material deficiency is, for example, a mistake in the tape splicing work of replenishing the mounter 100 with a new tape by the operator, but is not limited to this.

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

When the output unit 47 receives an access for viewing event information from the information terminal 600, the output unit 47 reads out the event information stored in the seventh storage unit 46, and sends an image related to the read event information to the information terminal 600 via the Internet 500. Output.

[1-4. Surveillance camera placement]
Next, the installation position of surveillance camera 300 will be described with reference to FIG. FIG. 5 is a diagram for explaining the installation position of surveillance camera 300 according to the present embodiment. In FIG. 5, two production lines, a first production line L1 and a second production line L2, are provided. An example having 121 to 125 will be described. The component mounters 111 to 115 and the component mounters 121 to 125 are examples of mounting lines. Further, in FIG. 5, the direction of substrate transport is from left to right in the plane of the paper. , the component mounter 121 among the component mounters 121 to 125 is arranged on the most upstream side. Note that the component mounter 100 shown in FIG. 1 may be any one of the component mounters 111 to 115 and 121 to 125 shown in FIG. In the following, when any of the component mounters 111 to 115 and 121 to 125 is not distinguished, the component mounter 100 is also referred to.

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

As shown in FIG. 5, in the case where a manufacturing line including a plurality of component mounters 100 is configured, the monitor camera 300 is positioned around the component mounter 100 located upstream among the plurality of component mounters 100, for example. placed. In the present embodiment, surveillance camera 300 is arranged around component mounters 111 and 121 positioned most upstream among component mounters 100 .

For example, the monitoring camera 310 on the front side of the first manufacturing line L1 is arranged near the board entrance of the component mounting machine 111 on the front side of the component mounting machine 111, and the monitoring camera 320 on the rear side of the first manufacturing line L1 is , is arranged near the board entrance of the component mounter 111 on the rear side of the component mounter 111 . The monitoring camera 310 and the monitoring camera 320 are arranged so as to sandwich the component mounter 111, for example.

Further, for example, the monitoring camera 330 on the front side of the second manufacturing line L2 is arranged near the board entrance of the component mounting machine 121 on the front side of the component mounting machine 121, and the monitoring camera 330 on the rear side of the second manufacturing line L2 is arranged. 340 is arranged in the vicinity of the substrate entrance of the component mounter 121 on the rear side of the component mounter 121 . The surveillance camera 330 and the surveillance camera 340 are arranged so as to sandwich the component mounter 121, for example.

The second image data may be image data captured by surveillance cameras 310 , 320 , 330 , and 340 arranged around the most upstream component mounter 100 among the plurality of component mounters 100 .

Of the front-side and rear-side surveillance cameras, the video data of the camera corresponding to the event is associated with the event. Taking the first production line L1 as an example, if an event occurs on the front side of any component mounter 100 of the first production line L1, the surveillance cameras 310 and 320 The video data of the monitoring camera 310 capturing the front side of the mounter 100 is associated with the event. An error that occurs on the front side of the mounter 100 is exemplified by a component pickup error (component pickup error), but is not limited to this.

Note that the installation positions of the surveillance cameras 310 to 340 are not limited to the installation positions shown in FIG. In addition, monitoring cameras 310 and 320 are provided around the component mounter 111, but the present invention is not limited to this. A camera may be provided. Also, the type and position of the surveillance camera to be installed can be selectively changed according to the environment of the factory where the production line is installed.

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

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

As shown in FIG. 6, the mounter 100 starts production (S11). For example, a production line having the mounter 100 starts production.

Next, the mounter 100 determines whether an event has occurred (S12). When an error occurs or an operation such as component supply occurs, the mounter 100 determines that an event has occurred (Yes in S12), and stores an equipment log indicating that the event has occurred in the equipment. If the data collection unit 20 is notified (S13) and it is determined that no event has occurred (No in S12), production is continued.

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

Note that the head camera 200 and the monitoring camera 300 may start imaging when the mounter 100 starts production, or may start imaging before the mounter 100 starts production. may be For example, the head camera 200 and the monitoring camera 300 may start imaging at a time that is the first hour before the time when the mounter 100 starts production. Therefore, the external data collection unit 30 starts collecting and storing video data (first video data and second video data) captured by the head camera 200 and the monitoring camera 300 (S31). While the mounter 100 is producing, image data is continuously collected and stored. Then, the dividing unit 32 sequentially divides the video data acquired via the video data collecting unit 31 and stores the divided data in the fifth storage unit 34 .

Next, after acquiring the facility log from the component mounter 100, the in-facility data collection unit 20 determines whether or not the event occurring in the component mounter 100 is an event to be monitored (S21). For example, the event code extraction unit 22 of the in-facility data collection unit 20 determines whether or not the event code included in the facility log is included in the event code list stored in the first storage unit 23 .

When the in-facility data collection unit 20 determines that the event is an event to be monitored (Yes in S21), it issues a synchronization instruction to the data synchronization management unit 40 (S22). In step S22, the in-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. The data synchronization manager 40 may acquire an event code from the in-facility data collection unit 20 upon acquiring the synchronization instruction in step S22. Obtaining an event code from the in-facility data collection unit 20 is an example of obtaining event occurrence information including information indicating that an event has occurred.

It should be noted that issuing a synchronization instruction means outputting an instruction indicating execution of a process of correlating and storing the event code of the event to be monitored and the data outside the facility. The instruction may be a dedicated command or an event code.

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

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 to be described later) (S41). After reading the event code from the second storage unit 24, the data synchronization management unit 40 determines a synchronization target period based on a table or the like according to the read event code.

Here, the synchronization target period will be described with reference to FIG. FIG. 7 is a diagram showing the relationship between an event and video data and work record data associated with the event according to the present embodiment. The horizontal axis of FIG. 7 indicates time. FIG. 7 shows an equipment event, work record data corresponding to the equipment event, image data of the head camera 200, image data of the first monitoring camera (for example, the monitoring camera 310), and image data of the second monitoring camera (for example, the , and the correspondence relationship of video data of the monitoring camera 320).

First, the facility event (Event1) that occurred at time t3 will be described. The facility event is an event that occurs singly. A single occurrence is an event in which the same equipment event occurs only once within a predetermined period.

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 occurred.

The video data reading unit 43 determines the video synchronization period according to the event that has occurred. The video data reading unit 43 determines the video synchronization period according to the event, for example, based on a table in which the event (for example, event code) and the first time are associated. In the example of FIG. 7, the video synchronization period is from time t2 to time t3. Time t2 is a time one hour before time t3 with respect to time t3.

In this way, video data associated with an event to be monitored is video data captured during a specified period before the event occurrence time. This is to ascertain whether or not there is any external work that could be the cause of the event before it occurs.

FIG. 7 shows an example in which 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 all have the same synchronization period. The periods may be different from each other as long as the periods are the same.

The work record data reading unit 44 determines the report synchronization period according to the event that has occurred. The work record data reading unit 44 determines the report synchronization period according to the event, for example, based on a table in which the event (for example, event code) and the second time are associated. In the example of FIG. 7, the report synchronization period is from time t3 to time t5. A time t5 is a time after the second time has elapsed from the time t3 with respect to the time t3.

In this way, the work record data associated with the event to be monitored becomes report data for the work performed within a specified period after the event occurrence time. This is for grasping the work performed by the component mounter 100 after the occurrence of the event.

Referring to FIG. 6 again, next, the data synchronization manager 40 reads the video data of the synchronization target period (S42). The video data reading unit 43 of the data synchronization managing unit 40 reads the video data of the synchronization period (video synchronization period) determined in step S41 from the fifth storage unit . By performing the determination in step S21, the video data reading unit 43 can acquire video data when the equipment event is an event to be monitored for which event information is stored. Step S42 is an example of obtaining video data.

Note that in the present embodiment, the video data is divided and stored in the fifth storage unit 34, and readout is performed in divided units. Therefore, in the present embodiment, video data is read out from time t1 to time t4 including time t2 and time t3 shown in FIG. For example, in step S42, the image data of the head camera 200, the image data of the first monitoring camera, and the image data of the second monitoring camera, Video Split: 1-1 to Video Split: 1-3, are transferred to the fifth image data. It is read out from the storage unit 34 .

Next, the data synchronization management unit 40 reads the work record data for the synchronization target 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 storage unit 36 . By performing the determination in step S21, the work record data reading unit 44 can acquire work record data when the facility event is an event for which event information is to be stored. Step S43 is an example of acquiring work record data.

It should be noted that the work record data corresponding to the event is not stored in the sixth storage unit 36 at the time when the event occurs. The external data collection unit 30 collects work record data from the information terminal 400 over the report synchronization period, and stores it in the sixth storage unit 36 (S32). Therefore, the work record data reading unit 44 may wait until the report synchronization period has passed, and after the report synchronization period has passed, read the work record data of the report synchronization period from the sixth storage unit 36 . In this embodiment, "Report 1", which is work record data performed between time t3 and time t5 shown in FIG. 7, is read.

Next, the data synchronization management unit 40 stores the equipment log (event), the video data and the work record data in association with each other in the seventh storage unit 46 (S44). In the example of FIG. 7, the equipment event that occurred at time t3 is stored in association with the video data captured between time t1 and time t4 and "Report1". Note that the associating unit 45 performs the associating, for example, after the report synchronization period has elapsed, that is, after the second time has elapsed (after time t5) from the time when the equipment event occurred (time t3). For example, the associating unit 45 may determine whether or not the report synchronization period has passed, and perform the association when it is determined that the report synchronization period has passed. For example, if the work record data regularly collected (read) from the sixth storage unit 36 after the report synchronization period has passed, the associating unit 45 stores work record data corresponding to the facility event (Event 1). is associated with the facility event.

Further, when work record data including the synchronization ID corresponding to the equipment event is stored in the external data collection unit 30, the data synchronization management unit 40 stores the work record data including the synchronization ID in the equipment log (event). may be stored in the seventh storage unit 46 in association with .

Next, a plurality of identical facility events (4 Event 2) occurring from time t8 to time t11 shown in FIG. 7 will be described. The facility event is an event in which the same facility event occurs multiple times (four times in the example of FIG. 7) within a predetermined period. The predetermined period is set in advance.

When the data synchronization management unit 40 determines the 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 one equipment event. The video data reading unit 43 and the work record data reading unit 44 of the data synchronization management unit 40 determine the synchronization target period based on the occurrence time of the equipment event that occurred last among the same equipment events multiple times. In the case of FIG. 7, the video synchronization period and the report synchronization period for Event2 are determined four times based on time t11.

In this case, in step S42, the video data of Video Split: 1-7 to Video Split: 1-9 are the video data of the head camera 200, the video data of the first monitoring camera, and the video data of the second monitoring camera. 5 is read from the storage unit 34 . Also, in this case, in step S43, "Report21" and "Report22", which are work record data when work is performed between time t11 and time t13 shown in FIG. 7, are read.

Then, in step S44, the four same equipment events 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 associated and stored. In step S44, an event code (e.g., equipment log) indicating the same equipment event multiple times, and video data and work records acquired based on the occurrence time of the last equipment event among the multiple equipment events. It can also be said that the information is stored as event information in association with data. As a result, it is possible to collectively check the same facility event multiple times, so that the time required to specify the cause of the event can be shortened compared to the case where the same facility event multiple times are separately stored.

In this way, the data synchronization management unit 40 is triggered by the occurrence of an event to be monitored, and performs a process of correlating and storing the facility log and the facility data and the facility data outside according to the event. As a result, compared to the conventional method of identifying the cause of an event from a facility log, it becomes possible to easily acquire and view the data inside the facility and the data outside the facility corresponding to the event. It can contribute to early identification of the cause of the outbreak. In addition, by associating the data outside the facility, it can greatly contribute to specifying the external factor, especially when the cause of the event is outside the facility.

Conventionally, data outside the facility is not associated with data inside the facility, so it takes a particularly long time when the cause of the event is outside the facility.

[2-2. Event information display method]
Next, a method of displaying event information will be described with reference to FIGS. 8 and 9. FIG. 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 the event information stored by the data synchronization manager 40 on the information terminal 600. As shown in FIG.

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

When the information terminal 600 performs login processing, the data synchronization management unit 40 performs access authentication processing to determine whether or not access may be permitted (S102). The output unit 47 of the data synchronization management unit 40 performs access authentication processing based on, for example, user names and passwords.

Next, when 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), and 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, for example, data described in HTML (HyperText Markup Language) format and displayable by a web browser or the like.

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 causes the display unit 610 to display the acquired image. A display unit 610 displays an image obtained by a web browser or the like. For example, the user can view and download the event information via the information terminal 600 even if the user is in a remote location from the facility (eg, factory) where the production line is installed.

FIG. 9 is a diagram showing a display example of event information according to the present embodiment. FIG. 9 shows an image displayed on the display unit 610. As shown in FIG.

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

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

The date and time of occurrence is the date and time when the event occurred, the event code is a code for identifying the event that occurred, the number of occurrences is the number of times the same event occurred within a predetermined period, and the line name is the date and time when the event occurred. This is information for identifying the manufacturing line, and the equipment name is information for identifying the mounter 100 in which the event occurred. The side is information indicating whether the position where the event occurred is the front side ("Front" in FIG. 9) or the rear side ("Rear" in FIG. 9) of the mounter 100. FIG. The event main message is information indicating the state of the mounter 100 in which the event occurred, and examples thereof include "alarm stop state" and "trouble stop state". Also, the event sub-message is supplementary information about the event, and examples thereof include "component pick-up error" and "head error". The icon 610a1 is displayed to allow the user to select an event for displaying data outside the facility.

For example, when the user clicks the icon 610a1 on the first line, that is, when the information terminal 600 acquires the selection of one event from the facility event list from the user, the selected event (selected icon 610a1) is associated with the event. A second image 610b (an example of an image) based on the obtained video data and work record data is displayed.

Information terminal 600 outputs information indicating selected icon 610a1 to output unit 47, acquires an image corresponding to selected icon 610a1 from output unit 47, and causes display unit 610 to display the acquired image. As a result, the image displayed on the display unit 610 transitions from the first image 610a to the second image 610b.

The second image 610b is an image based on the data outside the facility 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. . Thereby, the user can easily browse the work record data and the video data only by selecting the work record data and the video data to be browsed. For example, if the in-facility data and the out-of-facility data are not associated with each other, it is necessary to search for video data corresponding to the event from a plurality of video data, and it takes time for the user to identify the cause of the event. On the other hand, in the present embodiment, the data inside the facility and the data outside the facility are automatically associated, so the user does not need to search for video data corresponding to the event, and the time required to identify the cause of the event can be shortened. can.

(Modification of Embodiment)
The management system according to this modification will be described below with reference to FIGS. 10 to 13. FIG. In addition, below, it demonstrates centering around difference with embodiment, and abbreviate|omits or simplifies description about the same or similar content as embodiment. 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 the description thereof will be omitted. This modification differs from the management system 1 according to the embodiment mainly in that the association between the event and the work record data is performed based on the synchronization ID.

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

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

By notifying the worker of the alert, the worker responds to the event (S60).

When the data synchronization manager 40 acquires a synchronization instruction from the in-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 using the occurrence of an event to be monitored as a trigger. A synchronous 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 acquires a synchronization instruction from the in-facility data collection unit 20 . The data synchronization management unit 40 may notify the worker of the issued synchronization ID. For example, the data synchronization management unit 40 may output the issued synchronization ID to the information terminal 400 used by the worker.

Note that the synchronization ID is not limited to a number as long as the event and work record data can be associated with each other, and may be a symbol, a character, or a combination thereof. Further, the synchronous data ID may be, for example, a code dedicated to each target event that has occurred, an event code of the target event, or another code associated with the target event. It may be information. A synchronization ID is an example of event identification information.

Next, the data synchronization management unit 40 determines the synchronization target period of the video data (S45). When the event code is read from the second storage unit 24, the data synchronization management unit 40 determines the synchronization target period of the video data according to the read event code based on a table or the like. Note that in this modification, the data synchronization manager 40 does not determine the report synchronization period.

Here, the synchronization target period of video data will be described with reference to FIG. 11 . FIG. 11 is a diagram showing the relationship between an event and video data and work record data associated with the event, according to this modification. The horizontal axis of FIG. 11 indicates time. FIG. 11 is a diagram showing a correspondence relationship between an equipment event, image data of each monitoring camera, image data of the head camera 200, and work record data corresponding to the equipment event, for each lapse of time.

The third monitoring camera is a fixed camera installed on the ceiling or the like, and starts imaging at time t21. The fourth monitoring camera is a fixed camera (for example, monitoring camera 310) on the front side of the production line, and starts imaging at time t22. The fifth monitoring camera is a fixed camera (for example, the monitoring camera 320) on the rear side of the manufacturing line, and starts imaging at time t22. The head camera 200 is a camera attached to the head of the worker, and starts imaging at time t23. That is, the third monitoring camera, the fourth and fifth monitoring cameras, and the head camera 200 start imaging at different times. The third to fifth surveillance cameras are examples of the first camera, and the head camera 200 is an example of the second camera.

First, the facility event (EventA) that occurred at time t25 will be described. The facility event is an event that occurs singly.

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

The video data reading unit 43 determines the video synchronization period according to the event that has occurred. The video data reading unit 43 determines the video synchronization period according to the event, for example, based on a table in which the event (for example, event code) and the first time are associated. In the example of FIG. 11, the video synchronization period is from time t24 to time t25. Time t24 is a time one hour before time t25 with respect to time t25.

The video data reading unit 43 determines the period of video data to be individually associated with 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 associated with the equipment event A. FIG. When the video synchronization period is 30 minutes and the split interval is 10 minutes, the video data reading unit 43 assigns the video split data contained within 30 minutes before the equipment event occurrence time (time t25) to the equipment event A. Determine video data to be associated.

The video data reading unit 43 determines the video data of the third monitoring camera to be associated with the equipment event A as 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 include video data captured between time t25 and time t26. In addition, the video data reading unit 43 determines the video data of the fourth monitoring camera and the fifth monitoring camera to be associated with the equipment event A as 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 include video data captured between time t25 and time t27. Further, the video data reading unit 43 determines video data of the head camera 200 to be associated with the equipment event A as 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 include video data captured between time t25 and time t28.

Next, a plurality of identical facility events (four EventBs) occurring at time t32, time t33, time t34, and time t35 will be described. The facility event is an event in which the same facility event occurs multiple times (four times in the example of FIG. 11) within a predetermined period. The predetermined period is set in advance.

When the data synchronization management unit 40 determines 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 one equipment event. The video data reading unit 43 and the 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 equipment event that occurred last among the same equipment events multiple times. In the case of FIG. 11, four video synchronization periods (time t31 to time t35) for Event B are determined with time t35 as a reference. Note that the video synchronization period is a period longer than the predetermined period.

The processing after the video synchronization period is determined is the same as the case of event A, and detailed description is omitted. The video data reading unit 43 determines the video data of the third surveillance camera to be associated with the 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 include video data captured between time t35 and time t36. In addition, the video data reading unit 43 determines the video data of the fourth monitoring camera and the fifth monitoring camera to be associated with the facility 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 include video data captured between time t35 and time t37. In addition, the video data reading unit 43 determines video data of the head camera 200 to be associated with the facility event B as 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 include video data captured during times t30 to t31 and times t35 to t38.

Referring to FIG. 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 performs a 7 store in the storage unit 46 (S46). It can also be said that the data synchronization management unit 40 assigns a synchronization ID to the equipment log and the video data and stores them, 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 been stored in the seventh storage unit 46 .

Note that at least part of the processing from steps S44 to S46 may be performed while the operator is responding to an event. For example, all of the processing from steps S44 to S46 may be performed by the time the worker completes handling the event.

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

Next, the information terminal 400 receives input of work record data with a specified synchronization ID from the worker, and registers the received work record data (S51). For example, when the synchronization ID is acquired from the data synchronization management unit 40, the information terminal 400 presents the acquired synchronization ID and allows the worker to select which synchronization ID to input the work record data. Alternatively, the input of the synchronization ID may be received from the worker. When a synchronization ID is selected and there is no corresponding synchronization ID, the synchronization ID column may be blank (a state in which no synchronization ID has been entered). The information terminal 400 then outputs the work record data to the external data collection unit 30 . Thereby, the work record data is stored in the sixth storage unit 36 .

Here, a registration screen for registering work records will be described with reference to FIG. FIG. 12 is a diagram showing an example of a registration screen for registering work records according to this modification.

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

A user name logged in to the information terminal 400 is displayed as the worker ID. If the logged-in user and the working user are different, the operator ID of the working user is selected from the operator list by the change button.

As the synchronous ID, a list of synchronous IDs issued in the time period (for example, year, month, day, hour, minute) in which the event occurred is displayed. A corresponding synchronization ID is selected by the operator.

Profile information corresponding to the selected synchronization ID is automatically displayed in the event name, date and time of occurrence, and location. The operator can confirm whether or not the synchronization ID is correct by confirming the displayed information. Note that the information may be acquired from the data synchronization manager 40 together with the synchronization ID, for example.

The date and time of completion is the time when the event handling work was completed, and is input by the worker.

Factor is a field for entering the actual event occurrence factor, which is selected by the operator from a list. The example of FIG. 12 shows an example in which "splicing miss" is selected. If the applicable factor is not on the list, the operator selects "not applicable". In this case, the operator may enter the text of the factor in the lower "memo" field. It should be noted that the items in the list of factors displayed here may display factors inferred by the system according to the event that occurred, or may display factors set in advance.

Work is a column for inputting event-handling work that has actually been performed, and is selected by the worker from a list. The example of FIG. 12 shows an example in which "splicing correction" is selected. If the applicable task is not on the list, the worker selects "not applicable". In this case, the worker inputs the text of the work in the "memo" column at the bottom. Here, the items of the displayed work list may display work corresponding to factors inferred by the system according to the event that occurred, or may display work set in advance.

Memo is a field in which supplementary information is entered as text as needed.

Note that the registration screen displayed on information terminal 400 according to the embodiment may be a screen in which the item "synchronization ID" is deleted from the registration screen shown in FIG.

Referring to FIG. 10 again, next, the external 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 The acquired work record data is output to the data synchronization management unit 40 (S34). That is, the external 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 .

Next, the data synchronization management unit 40 stores the written work record data in the seventh storage unit 46 in association with the synchronization ID (S47). The data synchronization management unit 40 associates the work record data acquired from the non-facility 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. stored in the seventh storage unit 46. The data synchronization management unit 40 associates the work record data with the facility log and video data associated with the synchronization ID that matches the synchronization ID included in the work record data, and stores them in the seventh storage unit 46 .

As described above, the data synchronization management unit 40 stores work record data including a synchronization ID triggered by the occurrence of a monitored event in association with the equipment log and video data of the monitored event. . The data synchronization management unit 40 stores work record data including one synchronization ID among a plurality of work record data as event information in association with the facility log and video data associated with the one synchronization ID. I can say.

For example, in the example of FIG. 11, the work record A containing the synchronization ID corresponding to the event A stored at time t29 includes the event A associated with the synchronization ID and various video data associated with the event A. are stored in the seventh storage unit 46 in association with each other. Further, for example, the work record B containing the synchronization ID corresponding to the event B stored at time t39 is the event B associated with the synchronization ID (four events B) and the event B associated with the event B It is stored in the seventh storage unit 46 in association with various video data.

FIG. 13 is a diagram showing the data structure of event information stored in the seventh storage unit 46 according to this modification. FIG. 13 shows the structures of various data associated by synchronization IDs.

As shown in FIG. 13, the event information is information in which equipment logs, video data, and work record data are associated by synchronization IDs.

(Other embodiments)
As described above, the management method and the like according to one or more aspects have been described based on the embodiment and the like, but the present disclosure is not limited to the embodiment and the like. As long as it does not deviate from the spirit of the present disclosure, the present disclosure may include various modifications that a person skilled in the art can come up with, and a configuration constructed by combining the components of different embodiments. .

For example, in the above-described embodiments and the like, an example in which video data is divided into split intervals by a dividing unit and stored has been described, but the present invention is not limited to this. Video data may be stored without being divided into split intervals. In other words, the outside-facility data collecting unit does not have to have the dividing unit.

Also, in the above embodiments and the like, the mounting line has been described as having a plurality of component mounters, but the present invention is not limited to this. A mounting line may have only one component mounter. Also, the component mounter may not be incorporated into the mounting line and may be used as a stand-alone mounter.

In the above-described embodiments and the like, an event code is used as the event occurrence information, but the event occurrence information may be any information, such as an event name, that can specify what event has occurred.

Further, in the above embodiments and the like, an example of determining whether an event is an event to be monitored (S21 shown in FIG. 6) has been described. It is not necessary to determine whether or not For example, all of the event codes included in the equipment log from the mounter may be stored in the second storage unit.

Further, in the above-described embodiments and the like, an example in which the object is a substrate has been described, but the object is not limited to this, and may be, for example, a flat plate-like object (for example, an iron plate), or any other object. may In addition, in the above-described embodiment and the like, the mounting of the component on the board was described as an example of the predetermined processing, but the present invention is not limited to this, and the predetermined processing may be locking or crimping (for example, thermocompression bonding) of the component. ) to fix the component to the substrate, or to harden the object applied to the object by heat or light, or to deform at least a part of the object. Alternatively, mechanical processing such as cutting may be used.

Also, in the above embodiments and the like, the first time has been described as the number of hours (for example, 30 minutes), but it may be the number of splits if the video data is stored in units of splits.

In the above-described embodiments and the like, the data synchronization management section records one or more tasks performed on the component mounter between the event occurrence time and the second time after the event occurrence time. The work record data including the synchronization ID issued with the occurrence of the event as a trigger may be extracted from the record data, and the extracted work record data may be associated with the equipment log and the video data.

Also, the order in which each step in the sequence diagram is executed is for illustrative purposes in order to specifically describe the present disclosure, and orders other than the above may be used. Also, some of the steps may be executed concurrently (in parallel) with other steps, or some of the steps may not be executed.

Further, in the above-described embodiments and the like, each component may be configured by dedicated hardware, or may be implemented by executing a software program suitable for each component. Each component may be realized by reading and executing a software program recorded in a recording medium such as a hard disk or a semiconductor memory by a program execution unit such as a CPU or processor.

Also, the division of functional blocks in the block diagram is an example, and a plurality of functional blocks can be realized as one functional block, one functional block can be divided into a plurality of functional blocks, and some functions can be moved to other functional blocks. may Moreover, single hardware or software may process the functions of a plurality of functional blocks having similar functions in parallel or in a time-sharing manner.

Further, the data management device according to the above embodiments and the like may be realized as a single device, or may be realized by a plurality of devices. When the data management device is realized by a plurality of devices, each component of the data management device may be distributed to the plurality of devices in any way. For example, the in-facility data collection unit, the out-of-facility data collection unit, and the data synchronization management unit may be implemented by different devices (personal computers, etc.). In this case, the in-facility data collection unit and the out-of-facility data collection unit are arranged in the factory where the production line is installed, and the data synchronization management unit is arranged outside the factory. The data synchronization manager may be, for example, a server device. Further, when the data management device is realized by a plurality of devices, the communication method between the plurality of devices is not particularly limited, and may be wireless communication or wired communication. Also, wireless and wired communications may be combined between devices.

In addition, these general or specific aspects may be implemented in systems, methods, integrated circuits, computer programs, or non-transitory recording media such as computer-readable CD-ROMs. It may be realized by any combination of circuits, computer programs or recording media. The program may be pre-stored in a recording medium, or may be supplied to the recording medium via a wide area network including the Internet.

Further, each component described in the above embodiments and the like may be realized as software, or typically as an LSI, which is an integrated circuit. These may be made into one chip individually, or may be made into one chip so as to include part or all of them. Although LSI is used here, it may also be called IC, system LSI, super LSI, or ultra LSI depending on the degree of integration. Further, the method of circuit integration is not limited to LSI, and may be implemented by a dedicated circuit (general-purpose circuit that executes a dedicated program) or a general-purpose processor. An FPGA (Field Programmable Gate Array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure connections or settings of circuit cells inside the LSI may be used. Furthermore, if an integrated circuit technology that replaces the LSI appears due to advances in semiconductor technology or another technology derived from it, the component may naturally be integrated using that technology.

A system LSI is an ultra-multifunctional LSI manufactured by integrating multiple processing units on a single chip, and specifically includes a microprocessor, ROM (Read Only Memory), RAM (Random Access Memory), etc. A computer system comprising A computer program is stored in the ROM. The system LSI achieves its functions by the microprocessor operating according to the computer program.

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

Also, for example, the program may be a program to be executed by a computer. Also, one 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 distributed. For example, by installing the distributed program in a device having another processor and causing the processor to execute the program, it is possible to cause the device to perform the above processes.

INDUSTRIAL APPLICABILITY The present disclosure is useful for a management method and the like for managing data related to mounters.

1 management system 10 data management device (management device)
20 internal data collection unit 21 collection unit 22 event code extraction unit 23 first storage unit 24 second storage unit 25 parts data extraction unit 26 third storage unit 30 external data collection unit 31 video data collection unit 32 division unit 33 third 4 storage unit 34 fifth storage unit 35 work record data collection unit 36 sixth storage unit 40 data synchronization management unit 41 code reading unit (first acquisition unit)
42 component data reading unit 43 video data reading unit (second acquisition unit)
44 work record data reading unit (third acquisition unit)
45 association unit 46 seventh storage unit 47 output unit 100, 111, 112, 113, 114, 115, 121, 122, 123, 124, 125 component mounter 200 head camera (first camera)
300, 310, 320, 330, 340 surveillance camera (second camera)
400, 600 Information terminal 500 Internet 610 Display unit 610a First image 610a1 Icon 610b Second image L1 First production line L2 Second production line

Claims (11)

A management method for managing event information relating to events occurring in a mounter, comprising:
Acquiring event occurrence information including information indicating that the event has occurred;
Acquiring video data captured around the component mounter between an occurrence time indicating the time when the event occurred and a time one hour before the occurrence time,
Work record data that is a record of work performed on the component mounter between the time of occurrence and the time after the second time from the time of occurrence, and an event identification issued with the occurrence of the event as a trigger obtaining at least one of the work record data containing the information;
A management method, wherein the event occurrence information, the video data and the work record data are associated with each other and stored as the event information. A plurality of cameras are provided around the component mounter,
2. The management method according to claim 1, wherein in acquiring the image data, image data captured by one or more cameras selected according to the event from among the plurality of cameras are acquired. The plurality of cameras includes a first camera installed around the mounter and a second camera worn by an operator of the mounter,
3. The management method according to claim 2, wherein at least one of said first camera and said second camera is selected according to said event. A mounting line comprising a plurality of the component mounters is configured,
4. The management method according to claim 3, wherein the image data is image data captured by the first camera arranged around a component mounter positioned most upstream among the plurality of component mounters. when the same event occurs multiple times within a predetermined period, the time of the last event occurring among the multiple events is defined as the occurrence time;
In the storage of the event information, the event occurrence information indicating the event occurring a plurality of times is associated with the video data and the work record data acquired based on the occurrence time of the event that occurred last. The management method according to any one of claims 1 to 4, wherein the information is stored as event information. determining whether the event is an event for which the event information is to be stored, based on the event occurrence information;
The management method according to any one of claims 1 to 5, wherein the video data and the work record data are acquired when the event is an event for which the event information is to be stored. The target event includes a first event that the component mounter stops and a second event that the component mounter does not stop,
In storing the event information,
when the event is the first event, storing the event occurrence information, the video data and the work record data in association with each other as the event information;
7. The management method according to claim 6, wherein when the event is the second event, the event occurrence information and the video data are associated and stored as the event information. When work record data including event identification information issued with the occurrence of the event as a trigger is acquired, in storing the event information,
Before the work record data is acquired, the event occurrence information and the video data are added with event identification information and stored;
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 stored as the event information. The management method according to any one of claims 1 to 7. The management method according to any one of claims 1 to 8, wherein said first time and said second time are determined according to said event. A display method for displaying the event information stored by the management method according to any one of claims 1 to 9,
displaying a list based on one or more of the event occurrence information;
obtain a selection of one event from the list;
A display method for displaying an image based on the video data and the work record data associated with the acquired event. A management device for managing event information relating to events occurring in a mounter,
a first acquisition unit that acquires event occurrence information including information indicating that the event has occurred;
a second acquiring unit that acquires video data obtained by imaging the surroundings of the component mounter between an occurrence time indicating the time at which the event occurred and a time that is a first hour before the occurrence time;
Work record data that is a record of work performed on the component mounter between the time of occurrence and the time after the second time from the time of occurrence, and an event identification issued with the occurrence of the event as a trigger a third acquisition unit that acquires at least one of the work record data including the information;
A management device comprising: an associating unit that associates the event occurrence information with the video data and the work record data and stores the event information as the event information.

Images