Work management device

Abstract

This work management device comprises: an acquisition unit that, for each of a plurality of causal factors that can cause an abnormality in prescribed work, acquires period information that indicates a period in which the causal factor is used in or applied to execution of the prescribed work; and a determination unit that, when an abnormality has occurred in the prescribed work, determines, for each of the plurality of causal factors, a period level that indicates a level for the period in which the causal factor is used in or applied to execution of the prescribed work for the time at which the abnormality occurred on the basis of the period information acquired by the acquisition unit.

Description

work management device

[0001] The technology disclosed in this specification relates to a work management device that assists in identifying the cause of an abnormality that occurs during a predetermined work performed in a board work facility.

[0002] Patent Literature 1 discloses a defect cause estimation countermeasure output device that, when a defect occurs in a circuit board, estimates the cause of the defect and outputs countermeasures. The defect cause estimation countermeasure output device extracts the cause of the defect based on, for example, trouble information indicating the details of the trouble that occurred in the device and recovery information indicating the details of the countermeasures taken to recover the device from which the trouble occurred.

[0003] Japanese Patent Application Laid-Open No. 2005-327909

[0004] The failure cause estimation and countermeasure output device of Patent Document 1 requires recovery information to extract the cause of the failure. Therefore, the failure cause estimation and countermeasure output device cannot extract the cause of the failure unless the problem has been successfully resolved. This specification provides a technology that can more easily identify the cause of an abnormality than conventional technology.

[0005] The technology disclosed in this specification is embodied in a work management device that supports identification of the cause of an abnormality that occurs in a predetermined work performed in a circuit board processing facility. The work management device includes an acquisition unit that acquires, for each of a plurality of causal factors that may be the cause of the abnormality in the predetermined work, duration information indicating a period during which the causal factor was used or applied in performing the predetermined work, and a determination unit that, when the abnormality occurs in the predetermined work, determines, for each of the plurality of causal factors, a duration level indicating a level of a period during which the causal factor was used or applied in performing the predetermined work at the time the abnormality occurred, based on the duration information acquired by the acquisition unit.

[0006] For example, a causal element that has been used or applied to the execution of a predetermined task for a short period of time is more likely to be a cause of an abnormality than a causal element that has been used or applied to the execution of the predetermined task for a long period of time. In the above-described work management device, a duration level indicating the level of the duration for which the causal element has been used or applied to the execution of the predetermined task is determined for each of a plurality of causal elements. This makes it easy to identify the cause of an abnormality. Note that in this specification, "short duration" includes cases where there is no duration as well as cases where there is a short duration.

[0007] 1 is a schematic diagram of a component mounting system including a work management device according to a first embodiment; FIG. 2 is a side view of a component mounter; FIG. 3 is a control configuration diagram of the work management device; and FIG. 4 is a flowchart of work management processing executed by the work management device.

[0008] The main features of the embodiments described below are listed below. Note that the technical elements described below are independent technical elements that exhibit technical utility alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing.

[0009] (Feature 1) The above-described work management device may further include a first display unit that displays the period level determined by the determination unit for each of the plurality of causal elements when the abnormality occurs.

[0010] With this configuration, for example, a manager operating the work management device can easily identify, from among multiple causal factors, a causal factor that could be the cause of an abnormality based on the period level displayed on the first display unit.

[0011] (Feature 2) The work management device may further include a first identification unit that identifies a first period level indicating a shortest period among the period levels determined by the determination unit for each of the plurality of causal factors. In this case, the first display unit may display the first period level determined by the first identification unit in a first manner and display another period level different from the first period level in a second manner different from the first manner.

[0012] A causal element corresponding to the first period level, which has the shortest period, may be highly likely to be the cause of the abnormality. With this configuration, the first period level is displayed in the first manner different from the second manner, so that the administrator can easily identify the causal element corresponding to the first period level.

[0013] (Feature 3) The above-mentioned work management device may further include a first identification unit that identifies a first period level that indicates the shortest period level among the period levels determined by the determination unit for each of the plurality of causal elements, and a second display unit that, when the abnormality occurs, displays the causal element corresponding to the first period level identified by the first identification unit.

[0014] With this configuration, the manager can easily know the causal element corresponding to the identified first period level by looking at the causal element displayed on the second display unit.

[0015] (Feature 4) In the above-described work management device, the plurality of causal factors may include a user involved in performing the predetermined work. In this case, the work management device may further include a memory that stores user identification information that identifies the user and a user period that indicates a period during which the user engaged in the predetermined work, in association with each other. In response to acquiring the user identification information, the acquisition unit may acquire the period information based on the user period that is stored in association with the user identification information in the memory.

[0016] A user who has been engaged in a predetermined task for a short period of time is more likely to be the cause of an abnormality than a user who has been engaged in the predetermined task for a long period of time. With this configuration, the cause of an abnormality can be identified based on the user period.

[0017] (Feature 5) In the above-described work management device, the plurality of causal factors may include a mounter used to perform the predetermined work. In this case, the work management device may further include a memory that stores mounter identification information that identifies the mounter and a mounter period that indicates a period during which the mounter was used for the predetermined work, in association with each other. In response to acquiring the mounter identification information, the acquisition unit may acquire the period information based on the mounter period that is stored in association with the mounter identification information in the memory.

[0018] A mounter that has been used for a short period of time to perform a predetermined task is more likely to be the cause of an abnormality than a mounter that has been used for a long period of time to perform a predetermined task. With this configuration, the cause of the abnormality can be identified based on the mounter's period of use.

[0019] (Feature 6) In the above-described work management device, the plurality of causal factors may include a material used in performing the predetermined work. In this case, the work management device may further include a memory that stores material identification information that identifies the material and a material period that indicates a period during which the material was used in performing the predetermined work, in association with each other. In response to acquiring the material identification information, the acquisition unit may acquire the period information based on the material period that is stored in association with the material identification information in the memory.

[0020] A material that has been used for a short period of time to perform a predetermined operation is more likely to be the cause of an abnormality than a material that has been used for a long period of time to perform the predetermined operation. With this configuration, the cause of the abnormality can be identified based on the material period.

[0021] (Feature 7) In the above-described work management device, the plurality of causal factors may include an execution method for executing the predetermined work. In this case, the work management device may further include a memory that stores, in association with each other, execution method identification information that identifies the execution method and an execution method period that indicates a period during which the execution method was used to execute the predetermined work. In response to acquiring the execution method identification information, the acquisition unit may acquire the period information based on the execution method period that is stored in association with the execution method identification information in the memory.

[0022] An execution method that has been used for a short period of time to perform a predetermined task is more likely to be the cause of an abnormality than an execution method that has been used for a long period of time to perform a predetermined task. With this configuration, the cause of the abnormality can be identified based on the execution method duration.

[0023] (Feature 8) In the above-described work management device, the plurality of causal factors may include an inspection method performed in the predetermined work. The work management device may further include a memory that stores inspection method identification information that identifies the inspection method and an inspection method period that indicates a period during which the inspection method was used in performing the predetermined work, in association with each other. In response to acquiring the inspection method identification information, the acquisition unit may acquire the period information based on the inspection method period that is stored in association with the inspection method identification information in the memory.

[0024] An inspection method that has been used for a short period of time to perform a predetermined task is more likely to be the cause of an abnormality than an inspection method that has been used for a long period of time to perform the predetermined task. With this configuration, the cause of the abnormality can be identified based on the inspection method duration.

[0025] (Feature 9) In the above-described work management device, the plurality of causal factors may include environmental conditions surrounding the execution of the predetermined work. In this case, the work management device may further include a memory that stores, in association with each other, environmental condition identification information that identifies the environmental condition and an environmental condition period that indicates a period during which the environmental condition was applied to the execution of the predetermined work. In response to acquiring the environmental condition identification information, the acquisition unit may acquire the period information based on the environmental condition period that is stored in association with the environmental condition identification information in the memory.

[0026] An environmental condition that is applied to the execution of a predetermined task for a short period of time is more likely to be a cause of an abnormality than an environmental condition that is applied to the execution of a predetermined task for a long period of time. With this configuration, the cause of the abnormality can be identified based on the environmental condition period.

[0027] (Feature 10) In the above-described work management device, the period level may include a first level indicating that the causal element has not been used or applied to the specified work, and a second level indicating that the causal element was used or applied within a first period before the occurrence of the abnormality, and was not used or applied thereafter beyond a second period until the occurrence of the abnormality.

[0028] A causal element that has not been used or applied to a predetermined task has a higher possibility of being a cause of an abnormality than a causal element that has been used or applied to a predetermined task. Also, even if a causal element has been used or applied to a predetermined task within a first period, if the causal element has not been used or applied for a period exceeding a second period until the occurrence of an abnormality, the causal element may be a cause of an abnormality. With this configuration, by specifying multiple period levels according to the possibility of the causal element being a cause of an abnormality, the cause of an abnormality can be more easily identified.

[0029] First Embodiment FIG. 1 shows a perspective view of a component mounting system 100 including a work management device 30 according to a first embodiment. The component mounting system 100 includes, in addition to the work management device 30, component mounters 10A, 10B, and 10C and a kitting stand 40. The component mounting system 100 uses the component mounters 10A, 10B, and 10C to mount components 4 (see FIG. 2) on a board 2 (see FIG. 2). Each of the component mounters 10A, 10B, and 10C is a board processing device also known as an electronic component placement device or chip mounter. Each of the component mounters 10A, 10B, and 10C is installed alongside other board processing equipment, such as a solder printer and a board inspection machine (not shown), to form a continuous mounting line. Hereinafter, the +Z direction in the coordinate system in the figure may be simply referred to as "up," and the opposite direction may be referred to as "down." Furthermore, the -X direction in the coordinate system in the drawing may be simply referred to as "front," and the opposite direction may be simply referred to as "rear." Furthermore, the right direction (i.e., the -Y direction) as seen from user U1 standing in front of mounter 10A facing mounter 10A may be simply referred to as "right," and the opposite direction may be referred to as "left."

[0030] User U1 is an operator who performs various tasks in each of the mounters 10A, 10B, and 10C and the kitting stand 40. User U1 is assigned user identification information UI1. The user identification information UI1 is information for identifying user U1, and may be, for example, the employee number, department, and name of user U1.

[0031] The mounter 10A includes a touch screen 11A, a feeder set 12A, and a feeder holder 14A. Similarly, the mounter 10B includes a touch screen 11B, a feeder set 12B, and a feeder holder 14B, and the mounter 10C includes a touch screen 11C, a feeder set 12C, and a feeder holder 14C. The mounters 10A, 10B, and 10C have similar configurations, but to identify the mounters 10A, 10B, and 10C, mounter identification information DI1 is assigned to the mounter 10A, mounter identification information DI2 is assigned to the mounter 10B, and mounter identification information DI3 is assigned to the mounter 10C. In this embodiment, the leftmost mounter 10A of the mounters 10A, 10B, and 10C will be mainly described.

[0032] The touch screen 11A displays information about the mounter 10A and accepts operations from the user U1. For example, the user U1 logs in to the component mounting system 100 by entering their own user identification information UI1 and a password on the touch screen 11A. In a modified example, the user U1 may log in to the component mounting system 100 via the work management device 30. The feeder set 12A includes a plurality of feeders arranged in the left-right direction. The feeder holding unit 14A detachably holds the plurality of feeders of the feeder set 12A.

[0033] The kitting stand 40 is a board work facility located adjacent to the mounter 10C. The kitting stand 40 is a jig that allows, for example, a user U1 to handle a feeder 12E removed from the feeder set 12A of the mounter 10A. The kitting stand 40 includes a touch screen 41 and a feeder storage area 42. The feeder storage area 42 is, for example, a stand on which the feeder 12E is placed. As shown in FIG. 1 , the user U1, for example, removes a reel R1 containing components from the feeder 12E or attaches a new reel R1 to the feeder 12E while the feeder 12E is placed on the feeder storage area 42.

[0034] The work management device 30 is a computer that manages the operation of each of the board work facilities 10A, 10B, 10C, and 40. The work management device 30 is configured to be able to communicate with each of the board work facilities 10A, 10B, 10C, and 40. In this embodiment, the work management device 30 is disposed at a location away from each of the board work facilities 10A, 10B, 10C, and 40, but in a modified example, the work management device 30 may be disposed adjacent to the component mounter 10A, for example.

[0035] As shown in FIG. 2, in addition to the touch screen 11A, feeder set 12A, and feeder holding unit 14A described above, the component mounter 10A further includes a head unit 15A consisting of a mounting head 16A and a head moving device 18A, a board conveyor 20A, a camera 24A, a control device 22A, and a temperature sensor 26A.

[0036] Each feeder in the feeder set 12A supplies components 4 to a mounting head 16A of the head unit 15A. The mounting head 16A has a cylindrical nozzle 6A. The nozzle 6A extends downward from the mounting head 16A. The mounter 10A maintains negative pressure inside the nozzle 6A, for example, using a compressor (not shown), to pick up and place components 4 on the tip of the nozzle 6A. The mounting head 16A can move the nozzle 6A vertically, moving the nozzle 6A toward and away from each feeder in the feeder set 12A or the surface of the board 2. When the negative pressure inside the nozzle 6A is released while the mounting head 16A is bringing the tip of the nozzle 6A close to the surface of the board 2, the component 4 is mounted on the surface of the board 2. The head moving device 18A moves the mounting head 16A and the camera 24A between each feeder in the feeder set 12A and the board 2.

[0037] The camera 24A is fixed to the movable base 19A via a fixing member and moves integrally with the mounting head 16A and the movable base 19A. Although not shown, the camera 24A includes an illumination light source and a prism. The camera 24A captures images of the side of the component 4 picked up by the nozzle 6A and the tip of the nozzle 6A from behind (i.e., the right side of the paper in FIG. 2 ). The camera 24A may be, for example, a CCD camera. The illumination light source is composed of an LED and illuminates the imaging surface of the component 4 and the tip of the nozzle 6A. The prism aligns the optical axis of the camera 24A with the imaging target. The illumination light source illuminates the side of the component 4 and the tip of the nozzle 6A, and the reflected light is reflected by the prism and directed to the camera 24A, allowing the camera 24A to capture images of the side of the component 4 and the tip of the nozzle 6A. The camera 24A is configured to be able to communicate with the control device 22A. The camera 24A captures an image based on an image capture instruction transmitted from the control device 22A, and transmits image data of the captured image to the control device 22A. The control device 22A inspects, for example, the suction posture of the component 4 based on the image data received from the camera 24A.

[0038] The temperature sensor 26A is disposed on the rear wall of the mounter 10A. The temperature sensor 26A acquires the temperature inside the mounter 10A and transmits it to the control device 22A.

[0039] The board conveyor 20A is a device that carries in, positions, and carries out the board 2. As an example, the board conveyor 20A in this embodiment includes a pair of belt conveyors and a support device (not shown) that supports the board 2 from below. The board conveyor 20A carries out the board 2, on which the mounting of components 4 has been completed in the component mounter 10A, to the component mounter 10B. Similarly, the board conveyor of the component mounter 10B carries in the board 2 that has been carried out from the component mounter 10A, and once the mounting of the components 4 is complete, carries it out to the component mounter 10C. The board 2 is transported in the order of the component mounters 10A to 10C, and once all of the multiple components 4 have been mounted on the board 2 in the component mounter 10C and the board 2 is carried out from the component mounter 10C, the circuit board is completed.

[0040] The control configuration of the work management device 30 will be described with reference to FIG. 3 . The work management device 30 includes an operation unit 32, a display 34, and a control unit 36. The operation unit 32 is an interface, such as a keyboard, that accepts various inputs from an administrator of the component mounting system 100. The display 34 displays various information related to the component mounting system 100. The control unit 36 ​​includes a CPU 38 and a memory 39. The memory 39 is configured with volatile memory, non-volatile memory, etc. The memory 39 stores a program P1, a cause element table Ta1, a first threshold number of days Th1, a second threshold number of days Th2, and a third threshold number of days Th3. The CPU 38 executes, for example, the work management process shown in FIG. 4 in accordance with the program P1 stored in the memory 39.

[0041] The cause element table Ta1 stores, for each of the six cause elements F1 to F6, period information indicating the period during which the cause element was used or applied to the mounting work W1. The period information indicates the number of days during which each cause element F1 to F6 was used or applied to the mounting work W1. Hereinafter, the number of days during which each cause element F1 to F6 was used or applied to the mounting work W1 may be simply referred to as the "actual period."

[0042] The mounting work W1 is, for example, the work of mounting a predetermined number of components 4 on the board 2 and completing the circuit board within a predetermined time. The mounting work W1 also includes the work of a user (e.g., user U1) replenishing reels (e.g., reel R1) at the kitting stand 40 when the components 4 stored in the feeders of the feeder sets 12A to 12C of each of the mounters 10A to 10C are insufficient.

[0043] Each of the six causal factors F1 to F6 indicates a factor that could be the cause of an abnormality in mounting operation W1. In this example, an "abnormality" includes, for example, the detection of a defect rate exceeding a threshold value in mounting operation W1 (for example, a nozzle suction error) and the failure to complete production of the board 2 within a predetermined time in mounting operation W1.

[0044] Here, the CPU 38 stores the period information for each of the six causal elements F1-F6, dividing it into a first implementation period T1, a second implementation period T2, and a third implementation period T3. Each implementation period T1-T3 indicates the time when each causal element F1-F6 was used or applied to the mounting work W1. Hereinafter, the time when each causal element F1-F6 was used or applied to the mounting work W1 may be referred to simply as the "performance period." The performance period indicates the time when each causal element F1-F6 was used or applied to the mounting work W1 without any problems. Therefore, the longer the performance period, the lower the likelihood that the causal element will cause an abnormality. However, even if causal elements have the same performance period, the likelihood of them causing an abnormality may change if their performance period differs. For example, a causal element with a performance period that is the most recent period is considered to be less likely to cause an abnormality because it was used or applied to the mounting work W1 without any problems in its most recent state. On the other hand, if the actual performance date is several years ago, even if the causal factor has a long performance period, it is considered to have a high possibility of being a cause of the abnormality.

[0045] Each implementation period T1 to T3 is a period for identifying causal elements that are likely to be the cause of an abnormality based on the performance dates of the causal elements F1 to F6. The first implementation period T1 is a period for identifying causal elements with the most recent performance date, for example, within 30 days from the current time. The second implementation period T2 is a period for identifying causal elements that do not have a recent performance date but have a relatively recent performance date, for example, six months from the current time. The third implementation period T3 is a period prior to the second implementation period T2. Because causal elements whose performance dates fall within the second implementation period T2 have a relatively recent performance date, they are less likely to be the cause of an abnormality than causal elements whose performance dates fall within the third implementation period T3.

[0046] Each of the threshold days Th1 to Th3 is a threshold for determining whether a performance period exists within each of the implementation periods T1 to T3. As previously mentioned, the existence of a performance period reduces the possibility that a cause of an abnormality may occur. However, even if the cause element F1 is used or applied to the mounting work W1 for only a few hours, for example, if the possibility that the cause element F1 may cause an abnormality is reduced based on that short period, the cause of the abnormality may not be accurately identified. Furthermore, for example, when a factory or other facility is shut down on a holiday or other such day, the cause elements F1 to F6 are not used or applied to the mounting work W1 during that shutdown period. Therefore, the CPU 38 determines that a performance period exists when each of the cause elements F1 to F6 is used or applied to the mounting work W1 for a period equal to or longer than each of the threshold days Th1 to Th3. The CPU 38 also determines that a performance period does not exist even if each of the cause elements F1 to F6 is used or applied to the mounting work W1 for a period shorter than each of the threshold days Th1 to Th3. The first threshold number of days Th1 is, for example, 20 days, and the second threshold number of days Th2 and the third threshold number of days Th3 are, for example, both 2 days. Note that each of the threshold numbers of days Th1 to Th3 may be, for example, 0 (zero) days, and can be changed by the administrator afterwards.

[0047] The causal element F1 indicates a user involved in the execution of the mounting work W1. For example, a user with a short period of experience in the mounting work W1 is unfamiliar with the work and therefore works slower and more likely to make errors than a user with a long period of experience. For example, when attaching reels R1 to multiple feeders 12E in the kitting stand 40, a user with a short period of experience in the mounting work W1 may exceed the planned work time. In this case, the production of circuit boards may not be completed within the specified time, resulting in the above-mentioned abnormality.

[0048] In other words, a user who has been involved in the mounting work W1 for a short period of time is more likely to cause an abnormality than a user who has been involved in the mounting work W1 for a long period of time. In particular, a first-time user who has no experience of participating in the mounting work W1 is more likely to cause an abnormality. For example, when user U1 logs in via the touch screen 11A of the component mounter 10A, the CPU 38 of the control unit 36 ​​of the work management device 30 associates the user identification information UI1 entered at the time of login with the mounting work performed after login and stores them in memory 39. This acquires a user period indicating the period during which user U1 was involved in the execution of the mounting work.

[0049] In the example shown in FIG. 3 , user U1 (see FIG. 1 ) with user identification information UI1 was not involved in the execution of mounting work W1 during the first implementation period T1. In this case, the CPU 38 associates a user period "N," indicating that user U1 was not involved in the execution of mounting work W1, with the first implementation period T1 and the user identification information UI1 of the cause element F1, and stores this in the cause element table Ta1. Similarly, user U1 was not involved in the execution of mounting work W1 during either the second implementation period T2 or T3. Therefore, the CPU 38 stores in the cause element table Ta1 the user period "N" associated with the second implementation period T2 and the user identification information UI1, and the user period "N" associated with the third implementation period T3 and the user identification information UI1.

[0050] For example, as shown in the cause element table Ta1, during the first implementation period T1, a user with user identification information UI3 was involved in the execution of mounting work W1 for 20 days. In contrast, user U1 with user identification information UI1 and a user with user identification information UI2 were not involved in the execution of mounting work W1. Furthermore, during the second implementation period T2, a user with user identification information UI3 was involved in the execution of mounting work W1 for 100 days. During the third implementation period T3, a user with user identification information UI2 was involved in the execution of mounting work W1 for 180 days. In this manner, the CPU 38 stores the user period for each of the user identification information UI1 to UI3. Similarly to the cause element F1, the CPU 38 also stores period information for the following cause elements F2 to F6 in the cause element table Ta1 for each of the identification information for each of the implementation periods T1 to T3.

[0051] The causal element F2 indicates the mounter used to perform the mounting operation W1. For example, a mounter immediately after manufacturing may not have undergone detailed adjustments, resulting in unexpected defects. Mounters with little production history are more likely to cause abnormalities than mounters with a long production history. In particular, a new mounter with no production history is more likely to cause abnormalities. The CPU 38 acquires mounter identification information DI1 (see FIG. 1 ), for example, when user U1 logs in via the touch screen 11A of the mounter 10A. Furthermore, the CPU 38 measures the period during which the mounter 10A was used to perform the mounting operation W1. The CPU 38 acquires the mounter period indicating the period during which the mounter 10A was used to perform the mounting operation W1 and stores it in the cause element table Ta1. At this time, the CPU 38 stores the mounter period for each implementation period T1 to T3 in the cause element table Ta1, similar to the user period described above. For example, in this embodiment, in the first implementation period T1, the mounters 10A and 10B are used to perform the mounting work W1 for 10 days each.

[0052] The causal element F3 indicates the material used in the execution of the mounting operation W1. Here, "material" refers to the material of each component used in the execution of the mounting operation W1, including, for example, the material of the tape on the reel R1 (e.g., paper tape or embossed tape) and the manufacturer of the reel R1. For example, if the material or manufacturer of the tape on the reel R1 used in the execution of the mounting operation W1 changes, the components 4 may not be properly removed from the tape. In this case, the mounting operation W1 may not be completed within the specified time. Furthermore, a change in the material or manufacturer of the tape on the reel R1 may cause the defect rate to exceed a threshold. In other words, a change in the material or manufacturer of the tape on the reel R1 may cause an abnormality. In other words, the material of a reel R1 that has been used for a short period of time in the execution of the mounting operation W1 is more likely to cause an abnormality than the material of a reel that has been used for a long period of time in the execution of the mounting operation W1. For example, when a feeder (e.g., feeder 12E) is set in the feeder holding unit 14A of the mounter 10A, the CPU 38 acquires reel identification information (e.g., RI1) that identifies the reel R1 loaded on the feeder 12E from the feeder 12E via the control device 22A of the mounter 10A. The reel identification information RI1 and RI2 includes information that identifies the vendor of the reel R1, the product number of the reel R1, etc. The product number of the reel R1 includes information that indicates the tape material. In a modified example, the causal element F3 may be the material and manufacturing vendor of the component 4.

[0053] Causal element F4 indicates the execution method for executing the mounting operation W1. Here, the "execution method" includes various job information related to the processing executed by the mounters 10A-10C. Job information includes, for example, the type of components 4 to be mounted by the mounter 10A, the mounting positions on the board 2, the mounting order, the movement path and movement speed of the mounting head 16A, and the like. The job information is input by the administrator into the work management device 30. For example, for a first production of a board 2, the mounter 10A operates according to job information that the mounter 10A has never executed before. Job information for which the mounting operation W1 was executed for a short period of time is more likely to cause an abnormality than job information for which the mounting operation W1 was executed for a long period of time. The job information is transmitted from the work management device 30 to each mounter 10A-10C. Each mounter 10A-10C mounts components 4 on the board 2 according to the received job information. In response to the job information input by the administrator, the CPU 38 assigns job identification information JI1 and JI2 that identify the job information. As a result, the CPU 38 acquires the job identification information JI1 and JI2. In a modified example, the CPU 38 may receive the job information from a higher-level management device (not shown), or the job information may be stored in advance in the program P1.

[0054] The causal element F5 indicates the inspection method executed in the mounting operation W1. In this embodiment, the "inspection method" includes the brightness of the illumination light source of the camera 24A shown in FIG. 2, the number of measurement points in the image, and other factors. For example, if the brightness of the illumination light source of the camera 24A is changed, the anomaly detection rate may change. Therefore, an inspection method executed for a short period of time in the mounting operation W1 is more likely to cause an anomaly than an inspection method executed for a long period of time in the mounting operation W1. The CPU 38 receives input from the administrator, along with the above-mentioned job information, such as the brightness of the illumination light source of the camera 24A and the number of measurement points in the image. In response to the inspection method input by the administrator, the CPU 38 assigns inspection identification information EI1 and EI2 that identify the inspection method. Thus, the CPU 38 acquires the inspection identification information EI1 and EI2. In a modified example, the inspection method may be received from a higher-level management device or may be pre-stored in the program P1.

[0055] The causal factor F6 includes the environmental conditions under which the mounting operation W1 is performed. In this embodiment, "environmental conditions" include the temperature around the mounters 10A-10C. For example, if the temperature inside the mounter 10A is extremely low, the tape on the reel R1 may not peel properly, making it impossible to remove the component 4. In this case, the mounting operation W1 may not be completed within the specified time. In other words, the occurrence rate of abnormalities may vary depending on the temperature inside the mounter 10A. Temperatures that have only been applied for a short period of time during the execution of the mounting operation W1 are more likely to cause abnormalities than temperatures that have only been applied for a long period of time during the execution of the mounting operation W1. In particular, temperatures that have not been applied for a long period of time during the execution of the mounting operation W1 are more likely to cause abnormalities. The CPU 38 acquires the temperature inside the mounter 10A, for example, acquired by the temperature sensor 26A (see FIG. 1) of the mounter 10A via the control device 22A. The CPU 38 assigns temperature identification information TI1 and TI2 to identify the temperature upon acquiring the temperature from the control device 22A. As a result, the CPU 38 acquires the temperature identification information TI1 and TI2. In a modified example, the causal element F6 may include the humidity around the mounters 10A to 10C.

[0056] The work management process executed by the CPU 38 of the control unit 36 ​​of the work management device 30 of this embodiment will be described with reference to Fig. 4. The CPU 38 starts the process of Fig. 4 in response to the start of mounting work W1 by the manager.

[0057] First, in S2, the CPU 38 receives work information from each of the mounters 10 A to 10 C. The work information includes, for example, the number of circuit boards produced in the mounting work W1, the production time, and the defect rate.

[0058] Next, in S10, the CPU 38 detects the occurrence of an abnormality based on the work information received in S2. Specifically, the CPU 38 determines whether production of the circuit boards was completed within the aforementioned predetermined time based on, for example, the production quantity and production time included in the work information. The CPU 38 also determines whether a defect rate exceeding a threshold number has been detected based on the defect rate included in the work information. If production of the boards 2 was completed within the predetermined time and the defect rate includes a number of pickup errors smaller than the threshold number, the CPU 38 determines NO in S10 and receives new work information again (S2). On the other hand, if the CPU 38 determines that any abnormality has occurred, it proceeds to S12.

[0059] In S12, the CPU 38 acquires the latest current identification information (for example, user identification information UI1) for each of the cause elements F1 to F6 from the cause element table Ta1 in the memory 39.

[0060] Furthermore, in S14, the CPU 38 identifies one piece of identification information from the identification information acquired in S12. In this embodiment, the CPU 38 identifies the identification information in the order of the cause elements F1 to F6. Hereinafter, the identification information identified in S14 may be referred to as "target identification information." The CPU 38 further acquires, from the cause element table Ta1, target period information (e.g., user period) for each implementation period T1 to T3 that is stored in association with the target identification information.

[0061] In S20, the CPU 38 compares first period information, which is period information for the first implementation period T1 among the target period information, with the first threshold number of days Th1 in the memory 39. If the first period information is smaller than the first threshold number of days Th1 (NO in S20), the CPU 38 proceeds to S30, and if the first period information is equal to or greater than the first threshold number of days Th1 (YES in S20), the CPU 38 proceeds to S22.

[0062] If the first period information is equal to or greater than the first threshold number of days Th1 (YES in S20), the target causal element stored in association with the target identification information has been used or applied to the execution of the mounting work W1 for equal to or greater than the first threshold number of days Th1 during the first implementation period T1 immediately preceding the current time point (i.e., the time point at which the occurrence of the abnormality was detected). In this case, in S22, the CPU 38 determines a period level L4 for the target causal element stored in association with the target identification information. The period level L4 indicates the level at which the target causal element is considered to be least likely to be the cause of the abnormality detected in S10.

[0063] In S30, the CPU 38 compares second period information, which is period information for the second implementation period T2 among the target period information, with the second threshold number of days Th2. If the second period information is smaller than the second threshold number of days Th2 (NO in S30), the CPU 38 proceeds to S40, and if the second period information is equal to or greater than the second threshold number of days Th2 (YES in S30), the CPU 38 proceeds to S32.

[0064] If the second period information is equal to or greater than the second threshold number of days Th2 (YES in S30), the target causal element has been used or applied to the execution of the mounting work W1 for equal to or greater than the second threshold number of days Th2 within the second implementation period T2. However, the target causal element has not been used or applied to the execution of the mounting work W1 during the first implementation period T1, which is immediately preceding the current time point. In this case, in S32, the CPU 38 determines a period level L3 for the target causal element. The period level L3 indicates a level at which the target causal element is considered more likely to be the cause of the abnormality than the above-mentioned period level L4.

[0065] In S40, the CPU 38 compares third period information, which is period information for the third implementation period T3 among the target period information, with the third threshold number of days Th3. If the third period information is smaller than the third threshold number of days Th3 (NO in S40), the CPU 38 proceeds to S50, and if the third period information is equal to or greater than the third threshold number of days Th3 (YES in S40), the CPU 38 proceeds to S42.

[0066] If the third period information is equal to or greater than the third threshold number of days Th3 (YES in S40), the target causal element was used or applied to the execution of the mounting work W1 for equal to or greater than the third threshold number of days Th3 during the third implementation period T3. However, the target causal element was not used or applied to the execution of the mounting work W1 during the most recent first implementation period T1 and second implementation period T2. In this case, in S42, the CPU 38 determines a period level L2 for the target causal element. The period level L2 indicates a level at which the target causal element is considered more likely to be the cause of the abnormality than the above-mentioned period levels L3 and L4.

[0067] If the third period information is less than the third threshold number of days Th3 (NO in S40), the target causal element has not been used or applied in the execution of the mounting work W1 during any of the implementation periods T1 to T3. In other words, in this case, the target causal element has never been used or applied in the execution of the mounting work W1. In this case, in S50, the CPU 38 determines a period level L1 for the target causal element. The period level L1 indicates the level at which the target causal element is most likely to be the cause of the abnormality. In this way, the CPU 38 determines a period level L1 indicating that no actual period exists, a period level L2 indicating that an actual period exists within the third implementation period T3, a period level L3 indicating that an actual period exists within the second implementation period T2, and a period level L4 indicating that an actual period exists within the most recent first implementation period T1. By identifying multiple period levels L1 to L4 according to the possibility that the target causal element may be a cause of the abnormality, the cause of the abnormality can be more reliably identified.

[0068] In S60, the CPU 38 determines whether or not a period level has been determined for all of the causal elements identified from the identification information acquired in S12. If there are any causal elements for which a period level has not been determined (NO in S60), the CPU 38 returns to S14 and determines the period level of the target causal element again. On the other hand, if the CPU 38 determines that all period levels have been determined (YES in S60), the CPU 38 proceeds to S62.

[0069] In S62, the CPU 38 displays a causes screen SC1 on the display 34. As shown in the upper part of FIG. 4, the causes screen SC1 displays the period levels L1 to L4 determined by the above-described process for each of the cause elements F1 to F6. Furthermore, in S62, the CPU 38 identifies, among the determined period levels L1 to L4, the period level L1 for which no actual period exists, and displays the identified period level L1 and the cause element F1 corresponding to the period level L1 with hatching H1 on the causes screen SC1. The other period levels L2 to L4 and cause elements F2 to F6 are displayed without hatching H1. This allows the administrator to easily determine, by viewing the causes screen SC1, which of the multiple cause elements F1 to F6 is likely to be the cause of the abnormality detected in S10 of FIG. 4. Furthermore, because only cause elements F1 and period levels L1 for which no performance period exists are displayed with hatching H1, the manager can easily identify cause elements that are likely to be the cause of the abnormality. If multiple period levels L1 are identified, the CPU 38 displays the cause screen SC1 with hatching H1 applied to the multiple period levels L1 and the corresponding cause elements. The CPU 38 repeats the work management process of FIG. 4 while the mounting work W1 is being performed.

[0070] (Effects of the Present Embodiment) The period level L1, which does not have a period used or applied to the execution of the mounting task W1, is more likely to cause an abnormality than the other period levels L2 to L4. Furthermore, the period level L2, which has an older performance date, is more likely to cause an abnormality than the period levels L3 to L4, which have a relatively recent performance date. Furthermore, the period level L4, which has a recent performance date, is less likely to cause an abnormality than the period levels L1 to L3, which do not have a recent performance date. In this way, the work management device 30 of the present embodiment determines the period levels L1 to L4 for each of the six causal elements F1 to F6 based on the presence or absence of a performance period and the performance date (S22, S32, S42, and S50 of FIG. 4). This allows the administrator to easily identify the cause of an abnormality.

[0071] The correspondence relationships in this embodiment are as follows: The mounters 10A to 10C and the kitting stand 40 are an example of "board work equipment." The mounting task W1 is an example of "predetermined task." The period level L1 is an example of "first period level." The display with hatching H1 on the cause screen SC1 is an example of "first mode," and the display without hatching H1 is an example of "second mode." The period level L1 is an example of "first level," and the period level L3 is an example of "second level." The second implementation period T2 is an example of "first period," and the first threshold number of days Th1 is an example of "second period."

[0072] 4 is an example of a process executed by a “first display unit” and a “first identification unit.” The processes of S22, S32, S42, and S50 are an example of a process executed by a “determination unit.”

[0073] Second Embodiment A work management device 30 according to a second embodiment will be described with reference to FIG. 4 . In the process of S62 in FIG. 4 , the work management device 30 according to this embodiment displays a cause screen SC2 on the display 34 instead of the cause screen SC1 of the first embodiment. In this embodiment, the CPU 38 identifies a period level L1 among the determined period levels L1 to L4 for which no performance period exists, and displays only the identified period level L1 and cause element F1 on the cause screen SC2, while excluding the remaining period levels L2 to L4 and cause elements F2 to F6. This allows the administrator to easily identify cause elements that are likely to be the cause of the abnormality by viewing the cause screen SC2. In this embodiment, the process of S22 is an example of processing executed by the “second display unit.” Note that, in a modified example, the CPU 38 may display, on the cause screen SC2, not only the period level L1 but also the period level L2 and the cause elements corresponding to the period level L2. That is, the CPU 38 may display, on the cause screen SC2, cause elements that are likely to be the cause of the abnormality.

[0074] The following points should be noted regarding the work management device 30 described in the embodiment. The "board work equipment" is not limited to the component mounters 10A to 10C and the kitting stand 40. The "board work equipment" may be, for example, a solder printing machine or a board inspection machine.

[0075] The CPU 38 may not necessarily mark the period level L1 and the cause element F1 with hatching H1 on the cause screen SC1. Alternatively, instead of using hatching H1, the cause screen SC1 may display only the period level L1 and the cause element F1 in red, for example, and display the other period levels and cause elements in black. In this modification, displaying them in red is an example of a "first mode," and displaying them in black is an example of a "second mode." In another modification, the period levels L1, L2, L3, and L4 may be displayed in this order from the top of the cause screen SC1. In this modification, displaying them at the top is an example of a "first mode," and displaying them at the bottom is an example of a "second mode."

[0076] The cause element table Ta1 does not necessarily have to include at least one of the cause elements F1 to F6.

[0077] The cause element table Ta1 does not need to store period information separately for each implementation period T1-T3. In this case, the CPU 38 may, for example, identify a cause element for which no performance period exists for each of the cause elements F1-F6, or may identify a cause element for which the performance period is shorter than a predetermined period for each of the cause elements F1-F6. In a further modification, the CPU 38 may identify the period levels L1-L4 for each of the cause elements F1-F6 in ascending order of performance period length, regardless of the performance period. In this case, the CPU 38 may display the cause element with the shortest performance period on the cause screen SC1 by hatching H1.

[0078] The cause element table Ta1 does not need to store each of the threshold number of days Th1 to Th3. In that case, the CPU 38 may determine that an actual performance period exists, for example, if there is a period in which each of the cause elements F1 to F6 was used or applied to the mounting work W1, regardless of the length of that period and when the performance was performed. In that case, the CPU 38 may display only the presence or absence of an actual performance period for each of the cause elements F1 to F6 on the cause screen SC1.

[0079] The technical elements described in this specification or drawings exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technologies illustrated in this specification or drawings simultaneously achieve multiple objectives, and achieving one of those objectives is itself technically useful.

[0080] For example, this specification also discloses a technical idea in which claim 5 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 4." Similarly, the following technical ideas are also disclosed: a technical idea in claim 6 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 5," a technical idea in claim 7 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 6," a technical idea in claim 8 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 7," a technical idea in claim 9 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 8," a technical idea in claim 10 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 9," and a technical idea in claim 11 changes "the work management device according to claim 1" to "the work management device according to any one of claims 1 to 10."

Claims

1. A work management device that assists in identifying the cause of an abnormality that occurs in a specified work performed in a board work facility, comprising: an acquisition unit that acquires, for each of a plurality of causal elements that may be the cause of an abnormality in the specified work, period information indicating the period during which the causal element was used or applied in the execution of the specified work; and a determination unit that, when an abnormality occurs in the specified work, determines, for each of the plurality of causal elements, a period level indicating the level of the period during which the causal element was used or applied in the execution of the specified work at the time the abnormality occurred, based on the period information acquired by the acquisition unit.

2. The work management device according to claim 1, further comprising: a first display unit that displays the period level determined by the determination unit for each of the plurality of causal factors when the abnormality occurs.

3. The work management device of claim 2, further comprising a first identification unit that identifies a first period level that indicates the shortest period level among the period levels determined by the determination unit for each of the plurality of causal elements, and the first display unit displays the first period level determined by the first identification unit in a first manner, and displays another period level different from the first period level in a second manner different from the first manner.

4. The work management device of claim 1 further comprises: a first identification unit that identifies a first period level that indicates the shortest period level among the period levels determined by the determination unit for each of the plurality of causal elements; and a second display unit that, when the abnormality occurs, displays the causal element corresponding to the first period level identified by the first identification unit.

5. The work management device of claim 1, wherein the plurality of causal factors include a user involved in performing the specified work, the work management device further includes a memory that stores user identification information that identifies the user and a user period that indicates a period during which the user was involved in the specified work, in association with each other, and the acquisition unit acquires the period information based on the user period that is stored in association with the user identification information in the memory in response to acquiring the user identification information.

6. The work management device according to claim 1, wherein the plurality of causal factors include a component mounter used to perform the specified work, and the work management device further comprises a memory that stores mounter identification information that identifies the component mounter and a mounter period that indicates a period during which the component mounter was used for the specified work, in association with each other, and the acquisition unit acquires the period information based on the mounter period that is stored in association with the mounter identification information in the memory in response to acquiring the mounter identification information.

7. The work management device of claim 1, wherein the plurality of causal factors include materials used in the execution of the specified work, the work management device further comprises a memory that stores material identification information that identifies the material and a material period that indicates the period during which the material was used in the execution of the specified work, in association with each other, and the acquisition unit acquires the period information based on the material period that is stored in association with the material identification information in the memory in response to acquiring the material identification information.

8. The work management device of claim 1, wherein the plurality of causal factors include an execution method for executing the specified work, the work management device further includes a memory that stores execution method identification information that identifies the execution method and an execution method period that indicates a period during which the execution method was used to execute the specified work, in association with each other, and the acquisition unit acquires the period information based on the execution method period that is stored in association with the execution method identification information in the memory in response to acquiring the execution method identification information.

9. The work management device of claim 1, wherein the plurality of causal factors include an inspection method performed in the specified work, the work management device further includes a memory that stores inspection method identification information that identifies the inspection method and an inspection method period that indicates a period during which the inspection method was used in performing the specified work, in association with each other, and the acquisition unit acquires the period information based on the inspection method period that is stored in association with the inspection method identification information in the memory in response to acquiring the inspection method identification information.

10. The work management device of claim 1, wherein the plurality of causal factors include environmental conditions in the vicinity of where the specified work is performed, the work management device further includes a memory that stores, in association with each other, environmental condition identification information that identifies the environmental conditions and an environmental condition period that indicates the period during which the environmental conditions were applied to the performance of the specified work, and the acquisition unit, in response to acquiring the environmental condition identification information, acquires the period information based on the environmental condition period that is stored in association with the environmental condition identification information in the memory.

11. The work management device of claim 1, wherein the period levels include: a first level indicating that the causal element has never been used or applied to the specified work; and a second level indicating that the causal element was used or applied within a first period before the abnormality occurred, and was not used or applied thereafter for more than a second period until the abnormality occurred.

Images