Production management device

Abstract

A production management device comprises a memory section configured to store sorting information for sorting component pick-up elements into multiple groups, wherein the component pick-up elements hold components and are interchangeably inserted in a component feeder forming a component pick-up machine, and error information showing an error history during an assembly operation for picking components from the component pick-up elements and mounting the components onto a circuit board in the component pick-up machine, in conjunction with identification information for each of the multiple component pick-up elements, and an aggregation section configured to aggregate or statistically process the error information for each of the multiple groups for the component pick-up elements used in a predetermined aggregation period.

Description

Technical field

[0001] The present description relates to a production management device for a component placement machine that picks up a component from a component holding element and mounts it onto a circuit board. State of the art

[0002] A technique for the mass production of printed circuit board (PCB) products by performing multi-stage production operations on a PCB bearing a circuit pattern has become widespread. A representative example of a PCB production machine that performs these production operations is a component placement machine, which carries out a placement operation to attach a component to a PCB. Generally, the component placement machine supplies a component using a component feeder in which a component holding element is interchangeably inserted, and performs a placement operation using a component placement tool. With this type of component placement machine, a fault occasionally occurs, leading to a failure of the placement operation.The location of the fault source varies, for example, between a device such as a component feeder or a component placement tool, a component holding element, and assembly data used for a placement operation. To maintain good productivity, it is important to assess the location of the fault source based on the fault occurrence status and to take appropriate countermeasures. An example of a technique for assessing the location of the fault source occurring in a circuit board production machine such as a component placement machine is disclosed in patent literature 1.

[0003] An assembly quality factor analysis method disclosed in patent literature 1 comprises a step for registering an inspection result in a soldering printing step, an inspection result in a component assembly step, an inspection result in a soldering step, and a repair result obtained by performing a circuit board repair in a quality database on a component-by-component basis; a step for capturing an inspection result in each production step; a step for aggregating defect occurrence states on a component basis and performing statistical processing; and a step for analyzing a statistical processing result between production steps and specifying a defect occurrence factor step and a defect factor.According to this technique, it is possible to narrow down the error occurrence factor step and significantly reduce quality defects by examining the error factor. List of cited documents Patent literature

[0004] Patent Literature 1: JP-A-2005-286015 Summary of the invention; Technical task

[0005] The technique described in patent literature 1 is advantageous in that the step for determining the error occurrence factor can be narrowed down by analyzing (comparing) statistical processing results between production steps. However, it is difficult to say that a method and a device for assessing the error factor (the location where an error originates) are sufficiently disclosed. In other words, the technique described in patent literature 1 does not disclose a specific method or device for assessing the location of an error origin in the assembly process that may occur in the component placement machine.

[0006] If the source of the error in the assembly process lies in the fixture, a decrease in productivity can be mitigated by countermeasures such as maintenance. If the source of the error lies in the assembly data, a further decrease in productivity can be mitigated by countermeasures such as data review and correction, and verification of the application conditions. However, if the cause lies in the component itself, it is generally difficult for the user of the component holding element to implement effective countermeasures, and productivity tends to decline. Therefore, it is necessary to implement countermeasures against errors caused by the quality of the component holding element.

[0007] Therefore, one objective of the present description is to provide a production management device capable of taking into account an error in an assembly operation of a component placement machine, in particular an error caused by the quality of a component receiving element, in an effective countermeasure by performing a more detailed aggregation or statistical processing of error information than in conventional techniques. Solution to the task

[0008] The present description discloses a production management device comprising: a memory section configured to store sorting information for sorting component holding elements into multiple groups, wherein the component holding elements hold components and are interchangeably inserted in a component feeding device forming a component picker, and error information that displays an error history during an assembly process of removing components from the component holding elements and mounting the components onto a circuit board in the component picker in conjunction with identification information of each of the multiple component holding elements;and an aggregation section configured to aggregate or statistically process the error information for each of the multiple groups for the component recording elements used in a predetermined aggregation period.

[0009] It should be noted that the present description discloses a technical idea in which "the production management device according to one of claims 1 to 3" in claim 6 is amended at the beginning of the application to "the management device according to one of claims 1 to 5", a technical idea in which "the production management device according to one of claims 1 to 3" in claim 7 is amended at the beginning of the application to "the production management device according to one of claims 1 to 6", a technical idea in which "the production management device according to one of claims 1 to 3" in claim 11 is amended at the beginning of the application to "the production management device according to one of claims 1 to 10", and a technical idea in which "the production management device according to one of claims 1 to 3" in claim 12 is amended at the beginning of the application to "the production management device according to one of claims 1 to 11".a technical idea in which the “production management device according to one of claims 1 to 3” in claim 15 is amended at the beginning of the application to “production management device according to one of claims 1 to 14”, a technical idea in which the “production management device according to one of claims 1 to 3” in claim 16 is amended at the beginning of the application to “production management device according to one of claims 1 to 5 and 7 to 15”, and a technical idea in which the “production management device according to one of claims 1 to 3” in claim 17 is amended at the beginning of the application to “production management device according to one of claims 1 to 16”. Advantageous effects of the invention

[0010] In the disclosed production management device, the memory section stores sorting information for grouping the multiple component holding elements and error information that provides an error history from the assembly process, along with identification information for each of the multiple component holding elements. The aggregation section statistically aggregates or processes the error information for each group of component holding elements used within the predetermined aggregation period. As described above, unlike the prior art, which determines whether the component is the source of the error, this method performs detailed aggregation or statistical processing for each group of multiple component holding elements. This allows for a comparison of the occurrence status of an error between groups and the consideration of the comparison result in an effective countermeasure. Brief description of the drawings Fig. Figure 1 is a perspective view that schematically illustrates an overall configuration of a component placement machine to which a production management device is applied in an exemplary embodiment. Fig. Figure 2 is a functional block diagram illustrating the production management device according to an exemplary embodiment. Fig. Figure 3 is a diagram that conceptually illustrates the machine protocol data of the component placement machine. Fig. Figure 4 is a diagram that represents determination data, which is a result of the determination processing of a determination section. Fig. Figure 5 is a diagram of a processing flow that illustrates a procedure for memory processing of a memory section. Fig. Figure 6 is a diagram illustrating the role data stored in the memory section. Fig. Figure 7 is a diagram of a processing flow that illustrates a procedure for aggregation processing of an aggregation section. Fig. Figure 8 is a diagram illustrating an aggregation result of the aggregation section. Fig. 9 is a diagram in which a display section shows the in Fig. 8 illustrates the aggregation result as a graphic, and is a diagram of the aggregation result for each supplier of a component. Fig. 10 is a diagram in which the display section shows a second aggregation result in a diagram, and is a diagram of the aggregation result for each supplier of the component. Fig. 11 is a diagram in which the display section in a diagram shows a third aggregation result, which is determined by the aggregation section for each type of component for a supplier A in Fig. 10 were aggregated. Fig. Figure 12 is a diagram of another diagram displayed by the display section and is a diagram illustrating another aggregation procedure of the aggregation section. Fig. Figure 13 is a diagram of another diagram displayed by the display section and is a diagram illustrating another aggregation procedure of the aggregation section. Description of exemplary implementations: 1. Configuration example for a component placement machine 1

[0011] First, with reference to Fig. 1 A configuration example for a component placement machine 1 is described, to which the production management device 7 of an embodiment is applied. In Fig. In Figure 1, two component placement machines 1 are arranged side by side on a system base 12. The direction in which the component placement machines 1 are arranged corresponds to an X-axis direction for transporting a circuit board, and the horizontal direction orthogonal to the X-axis direction is a Y-axis direction. Each component placement machine 1 comprises a placement machine housing 2, a circuit board conveyor 3, a component feeder 4, a head movement device 5, a placement head 52, a nozzle station 55, a parts camera 58, a control device 6, and the like. The placement machine housing 2 comprises a frame section 21, a support section 22 arranged above the frame section 21, and a protective cover 23 arranged above the support section 22 that can be opened and closed.

[0012] The circuit board conveyor 3 comprises two sets of conveyor mechanisms 31 and 32 and circuit board holding devices (not shown). The two conveyor mechanisms 31 and 32 are arranged parallel to each other and in the X-axis direction on the upper surface of the frame section 21. Each of the conveyor mechanisms 31 and 32 is rotatably driven by a motor (not shown) to transport a circuit board to be held in the X-axis direction. Two circuit board holding mechanisms are arranged essentially at a lower section of the center of each of the conveyor mechanisms 31 and 32. Each of the circuit board holding mechanisms holds a board in a predetermined mounting position. The circuit board conveyor 3 can comprise only one set of conveyor mechanisms.

[0013] The component feeding unit 4 comprises a pallet table 41 and several belt conveyors 45. The pallet table 41 is arranged on the upper surface of the frame section 21. The pallet table 41 has several slots 42 that extend parallel to each other in the Y-axis direction. Each of the several slots 42 is assigned position ID information for position identification. For example, if the total number of slots 42 is 24, the position ID information S01 to S24 is assigned.

[0014] The belt conveyor 45 is a type of component feeding device that forms the component picker 1. Each belt conveyor 45 is inserted into a slot 42. Each belt conveyor 45 carries a rotatable, mounted roller 46. The carrier belt is wound around the roller 46. The carrier belt comprises a base belt in which the components are each housed in several cavities arranged one behind the other, and a cover belt that is retractably connected to the base belt and covers the cavities. The combination of carrier belt and roller 46 is a type of component holding element. In the following description, the term "roller 46" is used to refer to a wound carrier belt.

[0015] The belt conveyor 45 drives a rotating sprocket that engages with a feed hole in the carrier belt, guides the carrier belt to a predetermined component feed position via step feeders, and releases the cover belt. The belt conveyor 45 then feeds the component to the component feed position. Each belt conveyor 45 is assigned device ID information for individual identification. The belt conveyor 45 can have a separate configuration in which a roller holding device, which holds the roller 46, is provided separately. The component feed unit 4 can include a tray feeder as the component feed device. The tray feeder uses a tray in which components are each held in several receiving sections arranged in a grid pattern.

[0016] The head movement device 5 is an XY robot type device and is located on the underside of the support section 22. The head movement device 5 moves the sliding block 51 in two horizontal directions by means of an X-axis motor and a Y-axis motor (not shown). The placement head 52 is provided on a side surface of the sliding block 51. The placement head 52 moves together with the sliding block 51 to any desired position on the frame section 21. One or more suction nozzles 53 are provided below the placement head 52. The placement head 52 performs an assembly operation in which it picks up the component from a component feed position of the conveyor belt 45 using the suction nozzle 53 and mounts the component onto a circuit board. The suction nozzle 53 is a type of component assembly tool that picks up a component from the reel 46.A clamping device assembly tool can be used as a component assembly tool, which clamps the component.

[0017] The nozzle station 55 is located next to the component feeding unit 4. The nozzle station 55 is equipped with an interchangeable nozzle tray 56 in which several suction nozzles 53 are interchangeably housed. As needed, the suction nozzle 53 attached to the placement head 52 is exchanged within the nozzle station 55.

[0018] The part camera 58 is positioned between the circuit board conveyor 3 and the component feeder 4, facing upwards. The part camera 58 captures an image of the component held by the suction nozzle 53 from below to record image data as the placement head 52 moves from the component feeder 4 to the circuit board. Image processing of the image data determines the position and orientation of the component relative to the suction nozzle 53 and takes this into account during the assembly process. For example, a digital imaging device with an image capture element such as a CCD or CMOS sensor can serve as the part camera 58.

[0019] The control device 6 comprises a computer device with a CPU that is operated by software. The mounting position of the control device 6 is not restricted. The control device 6 can be configured so that multiple CPUs are distributed and arranged within the device and are interconnected. The control device 6 controls the assembly process based on assembly data PD, which is stored in a memory (not shown). In other words, the control device 6 controls the circuit board conveyor 3, the component feeder 4, the head movement device 5, and the like, based on the assembly data PD. The assembly data PD is created for each circuit board type. The assembly data PD includes design data, component data, and layout data.

[0020] The design data describes the type of circuit board, the type, number, and mounting position of the component to be mounted on the circuit board, and the like. The component data describes the external dimensions and color of the component, the arrangement and dimensions of the electrodes provided on the component, the type (handling method) of the suction nozzle 53 used to pick up the component, and the like. The arrangement data describes a coordinate value of a component feed position for each of the multiple belt conveyors 45, a type of component fed by each of the multiple belt conveyors 45, and the like.

[0021] The control device 6 creates machine log data (LD) that represents the progress of the assembly operation. Normally, the control device 6 creates machine log data (LD) relating to the assembly operation each time the assembly operation is completed and stores the machine log data (LD) in memory (not shown). Furthermore, the control device 6 transmits the machine log data (LD) to the line management device 95, described later, essentially in real time. The machine log data (LD) can also represent an operation other than the assembly operation, such as a circuit board transport history or a suction nozzle 53 replacement history. The machine log data (LD) will be described in detail later.

[0022] An error occasionally occurs in component placement machine 1, causing the placement process to fail. Examples of placement process errors include the following cases 1) to 7). 1) A case in which no image data is captured by the parts camera 58. 2) A case in which the image data is not subjected to suitable image processing. 3) A case in which image processing reveals that the suction nozzle 53 is not picking up a component. 4) A case in which image processing reveals that the component type is incorrect. 5) A case in which image processing reveals a major error in the position of a component and the assembly process is deemed impossible. 6) A case in which the component falls out of the suction nozzle 53 while the placement head 52 moves from the parts camera 58 to the circuit board. 7) A case in which the component is not mounted on the circuit board while being picked up by the suction nozzle 53.

[0023] The location of the fault varies, for example between a device such as the belt conveyor 45 or the suction nozzle 53, the roller 46 and the assembly data PD.

[0024] If the cause lies in role 46, the following factors A) to C) will be taken into account. A) Quality of roller 46: an increase in the feed load of the carrier belt due to a faulty shape or position of roller 46, a positional deviation of the feed hole of the carrier belt, a positional deviation of the cavity, a fault or deviation in the internal dimension of the cavity, an unstable peeling condition of the cover belt and the like. B) Size of the component received in the cavity: an error in the external dimension of the component (the positive error is large even within the tolerance or the negative error is large even within the tolerance), a deviation in the external dimension of the component (positive or negative deviation within the tolerance) and the like. C) Roll 46 replacement process: Errors may occur during splicing of two carrier tapes, during insertion of a new carrier tape, during adjustment of a new roll, and the like. Errors due to this factor are rare and irrelevant to the quality of the roll 46. Even if an error does occur, the operator takes corrective action, so it is not considered a serious problem.

[0025] According to an empirical rule, the factors A) and B) described above do not occur randomly, but rather frequently with some of the rollers 46. For example, installation errors caused by roller 46 frequently occur with a specific component supplier, a specific component type, or a specific component batch. Therefore, a processing method that groups the rollers 46 by component manufacturer, type, or batch, and aggregates or statistically processes the error information (error history), can contribute to the testing and implementation of an effective countermeasure. The production management device 7 of the exemplary embodiment uses this processing method. This processing method employs the "layering" of the seven QC tools. 2. Functional configuration of the production management device 7 of the exemplary embodiment

[0026] Next, a functional configuration of the production management device 7 of the exemplary embodiment will be described with reference to Fig. 2 described. The production management device 7 is applied to four component placement machines 1, which form the printed circuit board production line 9. Machine ID information is assigned to the four component placement machines 1 to identify the respective component placement machines, for example, M1 to M4. The printed circuit board production line 9 comprises eight printed circuit board production machines arranged side by side. In particular, the printed circuit board production line 9 includes a solder paste printing machine 91, a print testing machine 92, four component placement machines 1, a printed circuit board visual inspection machine 93, and a reflow machine 94, which are arranged side by side. In addition, a line management device 95 is provided, which manages the operating status of the eight printed circuit board production machines. The line configuration of the printed circuit board production line 9 can be changed in various ways.Furthermore, the production management device 7 can be applied to component placement machines 1 that are arranged in several circuit board production lines 9.

[0027] The line management device 95 receives machine log data (LD) from each of the circuit board production machines essentially in real time. The data format of the machine log data (LD) can be different for each type of circuit board production machine or it can be standardized. The line management device 95 transmits the machine log data (LD) received by the control device 6 from at least four component pickers 1 to the production management device 7. This transmission can occur essentially in real time, can occur when multiple machine log data (LD) are collected, or can occur according to a transmission request from the production management device 7. The control device 6 of the component picker 1 can transmit the machine log data (LD) directly to the production management device 7.

[0028] Fig. Figure 3 illustrates an example of machine log data LD from component placement machine 1, whose machine ID information is M1. Each line in Fig. 3 corresponds to a set of machine log data LD. The machine log data LD has a data format in which ten pieces of information are linked together. That is, the machine log data LD is linked with time information, machine ID information, position ID information, device ID information, manufacturer, type, batch, remaining quantity, nozzle ID information, and individual operating information. Since machine log data LD is generally processed in time series, the machine log data LD from four component pickers 1 are actually mixed.

[0029] The time information specifies the point in time (hour, minute, second) at which the placement process is carried out and is represented, for example, by the point in time at which the lifting of the suction nozzle 53, which places the component onto the circuit board, ends. The machine ID information is information on the identifier of each of the four component placement machines 1, as described above. The position ID information is information on the identifier of each of the multiple slots 42, as described above. The device ID information is information on the identifier of each of the multiple belt conveyors 45, as described above.

[0030] The supplier, type, and batch information specifies the supplier, type, and batch of the component contained in reel 46. The remaining quantity information indicates the number of components still present on reel 46 at the beginning or end of the assembly process. The nozzle ID information identifies each of the suction nozzles 53 used in the assembly process. The individual process information indicates whether an error occurred during the assembly process. Fig. 3. A normal end to the assembly process is indicated by an O marking, and the occurrence of an error is indicated by an X marking.

[0031] Referring back to Fig. 2. The production management device 7 is configured using a computer device. The production management device 7 includes an input device 71, such as a keyboard or touch panel, which receives a command, selection operation, or the like from an operator or the like. Furthermore, the production management device 7 includes a display device 72, such as a liquid crystal display, which displays various information to the operator or the like. The production management device 7 includes a determination section 81, a determination database 82, a storage section 83, a roll database 84, an aggregation section 85, and a display section 86.

[0032] If the individual operating information of the machine protocol data LD includes an X mark (error occurrence), the determination section 81 performs the determination processing after waiting for the end of the use of the roller 46 used for the assembly operation. The determination section 81 determines the location of the cause of the assembly error. There are four candidates for the location of the cause: belt conveyor 45, suction nozzle 53, roller 46, and assembly data PD. The determination section 81 can, as a minimum function, determine whether the location of the cause is the roller 46. The determination section 81 stores determination data JD, which represents the result of the determination processing, in the determination database 82. The applicant of the present application discloses in Japanese patent application No. 7142149 a “device for estimating the cause of assembly errors” that corresponds to a configuration example of the determination section 81.

[0033] In summary, the root cause analysis device selects two candidates for the location of the cause and, based on a fault occurrence status, determines whether each candidate is the location of the cause when a first candidate is fixed and a second candidate is changed. For example, the root cause analysis device initially selects the suction nozzle 53 and the roller 46 as candidates for the location of the cause and fixes the suction nozzle 53. If a fault then occurs in several rollers 46 that were previously used in combination with the suction nozzle 53, the root cause analysis device estimates that the suction nozzle 53 is the location of the cause. Furthermore, if a fault occurs in only one specific roller 46 among several rollers 46, the root cause analysis device estimates that the specific roller 46, not the suction nozzle 53, is the location of the cause.Furthermore, the cause estimation device can improve the estimation accuracy by performing an estimation in which the combination of the two candidates is changed.

[0034] Memory section 83 stores sorting information for sorting the rolls 46 into multiple groups and error information in the component placement machine 1, in conjunction with identification information for each of the multiple rolls 46. Specifically, memory section 83 creates roll data RD, in which several types of sorting information, belonging to and distinct from each other, as well as error information, are linked to each of the identification information for multiple rolls 46, and stores the roll data RD in the roll database 84. As described later, memory section 83 determines the end-of-use time of the roll 46 from the machine log data LD and creates and stores roll data RD for each roll 46 whose use has ended.

[0035] The various sorting criteria described above include a supplier, a type, and a batch of a component included in roll 46. Therefore, specific supplier names correspond to the various sorting information belonging to the supplier sorting criterion. The sorting information belonging to the type sorting criterion corresponds to a specific component type name, a symbol indicating the type, or similar. Furthermore, the sorting information belonging to the batch sorting criterion corresponds to a specific batch name, a symbol indicating the batch, and similar.

[0036] The error information is information that displays an error occurrence history of the assembly process in the component placement machine 1. In one embodiment, the error information is displayed using several error ranks, which classify the severity of the error occurrence status. Furthermore, the error rank is represented by the number of error occurrences for each reel 46. For example, the error rank is represented by two ranks: "Error present," where the number of error occurrences for each reel 46 is one or more, and "Error not present," where the number of error occurrences is zero. Without limitation, three or more error ranks can be used. For example, four error ranks can be used, such as ranks where the number of error occurrences for each reel 46 is 0, 1, 2-3, and 4 or more.The error information can be represented by an indicator other than the error rank, which is based on the number of error occurrences, for example, an error occurrence rate for each role of 46.

[0037] The identification information of the reel 46 is represented, for example, by reel ID information assigned to each reel 46. Specifically, a barcode containing the reel ID information is attached to each reel 46, and the operator uses a barcode scanner to read the barcode. In this way, the control device 6 can capture the reel ID information. Generally, in addition to the reel ID, the barcode also includes component specification information, such as the manufacturer, type, batch, stock number, and similar details. Alternatively, the barcode can be linked to component specification information previously stored in a component database (not shown).

[0038] In this embodiment, a case is considered in which the roll ID is not used. That is, instead of the roll ID, memory section 83 specifies a combination of the roll 46's usage time, machine ID information, and device ID information or position ID information as the roll 46's identification information. In other words, memory section 83 identifies individual rolls 46 by specifying the roll 46's usage time and position. This identification method is also used in determination section 81 and aggregation section 85. The device ID information and the position ID information can each specify the position where the roll 46 is used, so it is not necessary to combine them.

[0039] Memory section 83 retrieves the sorting and error information for each of the multiple rolls 46 from the machine log data LD and stores this information in conjunction with the roll 46 identification information. Specifically, memory section 83 uses any manufacturer, type, and batch information contained in the retrieved machine log data LD unchanged as sorting information. Furthermore, memory section 83 retrieves the remaining usage time of the roll 46 based on the remaining quantity information contained in the machine log data LD. Memory section 83 then combines the machine ID, device ID, or position ID information with the remaining usage information contained in the machine log data LD to obtain the roll 46 identification information.In addition, memory section 83 determines error information based on whether an X-mark (error occurrence) is present in the individual operating information of several machine protocol data LD during the usage period.

[0040] However, memory section 83 excludes errors whose cause does not lie with role 46 from the error information. Specifically, memory section 83 retrieves destination data JD from the destination database 82 and sets the error information as present if the cause of the error (X-marking of the individual operating information) lies with role 46. If the location of the error cause is not role 46, memory section 83 sets the error information as absent. By setting only the error caused by role 46 as the aggregation target, it is possible to make the aggregation result of aggregation section 85 clear and efficient in contributing to the testing of an effective countermeasure.If all faults are the aggregation targets, the fault information includes not only faults caused by the roller 46, but also faults caused by the device and the assembly data PD. Therefore, the influence of many types of root cause locations is included in the aggregation result of aggregation section 85, and the verification of countermeasures becomes inefficient.

[0041] Aggregation section 85 statistically aggregates or processes the error information for each of the several groups sorted by the sort information for roll 46 used in a predetermined aggregation period. Specifically, aggregation section 85 retrieves roll data RD from roll database 84 and statistically aggregates or processes the error information for each of the several groups sorted by the sort information belonging to the specified sort criterion among the several types of sort criteria. The specified sort criterion can be set by the operator each time or preset. For example, if the specified sort criterion is a vendor, aggregation section 85 statistically aggregates or processes the error information for each of the several vendors.

[0042] Furthermore, aggregation section 85 can perform hierarchical or complex aggregation or statistical processing on groups sorted by multiple types of sorting information belonging to each of the multiple types of specified sorting criteria. In an example of hierarchical aggregation, aggregation section 85 can aggregate the defect information for each of the multiple vendors (first-layer aggregation) and further aggregate the defect information for each of the multiple types or for each of the multiple batches for a given vendor (second-layer aggregation).

[0043] In this embodiment, the aggregation section 85 aggregates the number of roles 46 used during the aggregation period (hereinafter referred to as the usage number Nu) for each of the several groups. Furthermore, the aggregation section 85 aggregates the number of roles 46 that correspond to at least one of the several error ranks into which the quality of the error information is classified. If the error rank is represented by two ranks, namely error presence and error absence, the aggregation section 85 aggregates the number of roles 46 that correspond to error presence or error absence.

[0044] Without being limited to the above, when three or more error ranks are used, aggregation section 85 can aggregate the number of roles 46 corresponding to each error rank. Furthermore, aggregation section 85 can determine the ratio of the role 46 corresponding to each error level to the usage number Nu. If the error information is represented by an error occurrence rate, aggregation section 85 can determine an average (average error occurrence rate) of the error occurrence rates of several roles 46 for each of the multiple groups (an example of statistical processing).

[0045] The aggregation period, during which the aggregation is performed, can be varied manually or preset to a specific period. For example, the operator can set any aggregation period using the input device 71. Furthermore, in a circuit board production line 9 operating 24 hours a day, a specific time (6 hours, 24 hours, or the like) can be preset as the aggregation period, and the aggregation section 85 can operate automatically. Additionally, in a circuit board production line 9 where operation ceases at night, the daytime operating time can be set as the aggregation period, and the aggregation section 85 can operate automatically after operation ceases.Furthermore, in a circuit board production line 9, a predetermined aggregation period can be set in advance during a peak period when the circuit board production line 9 operates for 24 hours, and an operating period during the day can be set as the aggregation period during a period other than the peak period when the circuit board production line 9 operates periodically. In addition to automatically setting the aggregation period for a specific period, any aggregation period can also be set manually.

[0046] Display section 86 shows the result of the aggregation or statistical processing of the error information by aggregation section 85 as a graph on the display device 72. The aggregation result of aggregation section 85 is expressed by numerical information within the production management device 7. Even when the numerical information is displayed in tabular form, it is difficult for an operator, manager, or designer to understand. Therefore, display section 86 converts the aggregation result into a bar chart, band chart, line graph, or similar format, visualizing and displaying the aggregation result in a way that is easily recognizable. The functions of determination section 81, storage section 83, aggregation section 85, and display section 86 are explained in more detail in the following functional description. 3. Operation of the production management device 7

[0047] Next, the operation of the production management device 7 will be described with reference to the Fig. 3, Fig. 4, Fig. 5, Fig. 6, Fig. 7, Fig. 8 to Fig. As described in section 9, when replacing a reel 46 whose components are exhausted in the component feeder 1 with a new reel 46, the operator uses a barcode scanner to read the barcode of the new reel 46. This allows the control device 6 to capture the component-related information, which specifies the manufacturer, type, batch, capacity, and similar details of the component. For the sake of simplicity, it is assumed that the number of components held in the new reel 46 is 200. It should be noted that the actual capacity is much greater than 200.

[0048] Furthermore, it is assumed that the component placement machine 1 with the device ID information M1 uses the belt conveyor 45 with the machine ID information F1, which is provided in the slot 42 with the position ID information S12, and the belt conveyor 45 with the device ID information F2, which is provided in the slot 42 with the position ID information S14. Fig. Figure 3 shows the machine log data LD of component picker 1 with the machine ID information of M1. In fact, component picker 1 generally uses more than two belt conveyors 45. The actual time required for the assembly process is shorter than in Fig. 3 shown.

[0049] In the machine log data LD, whose time stamp is in Fig. In the machine log data at 18:20:10, belt conveyor 45, whose device ID information is F1, delivers a component manufactured by B, type 15C, batch L01, and with a remaining quantity of 1. This component was assembled using suction nozzle 53, which uses nozzle ID N01, and its individual operating information was marked O (normal end). Additionally, in the machine log data LD, which is timed at 18:20:20, belt conveyor 45, whose device ID information is F2, delivers a component manufactured by B, type 15R, batch L11, and with a remaining quantity of 45. This component was assembled using suction nozzle 53, which contains nozzle ID N02, and its individual operating information was marked O (normal end).

[0050] Furthermore, in the machine log data LD, whose time information is 18:22:00, the belt conveyor 45, whose device ID information is F1, delivers a component whose manufacturer is B, whose type is 15C, whose batch number is L01, and whose remaining quantity is 200. Therefore, memory section 83 can recognize, based on the change in the remaining quantity, that the first roll 46 has been replaced by the second roll 46. Memory section 83 stores the end time of the usage period of the first roll 46 as 18:20 (rounded down to the nearest second) and stores the start time of the usage period of the second roll 46 as 18:22.

[0051] Furthermore, the belt conveyor 45, whose device ID information is F1 and whose time information is 19:56:25, delivers a component whose manufacturer is B, whose type is 15C, whose batch is L01, and whose remaining quantity is 1. Therefore, memory section 83 stores the end time of the usage period of the second roll 46 as 19:56. Similarly, memory section 83 stores the start time of the usage period of the third roll 46 as 19:58 based on the machine log data LD with the time information 19:58:00.

[0052] Furthermore, the belt conveyor 45, whose device ID information is F1, delivers in the machine protocol data LD, which has the time stamp 19:45:50, the component whose manufacturer is B, whose type is 15C and whose batch is L01, and whose individual operating information is the X marking (error occurrence). At this time, the determination section 81 has not yet carried out the determination processing, and the location of the error cause is unknown.

[0053] For the sake of simplicity, it is assumed that component placement machine 1 with machine ID information M2 uses belt conveyor 45 with device ID information F3, which is provided in slot 42 with position ID information S08, and belt conveyor 45 with device ID information F4, which is provided in slot 42 with position ID information S11. It is also assumed that component placement machine 1 with machine ID information M3 uses belt conveyor 45 with device ID information F5, which is mounted in slot 42 with position ID information S10, and belt conveyor 45 with device ID information F6, which is mounted in slot 42 with position ID information S13. It is assumed that the component placement machine 1 with machine ID information M4 uses the belt conveyor 45 with device ID information F7, which is mounted in slot 42 with position ID information S09.

[0054] Determination section 81 performs the determination processing after waiting for the end of the use of roller 46, which is used for the placement process for the X-mark (error occurrence) contained in the machine log data LD of four component placement machines 1, which include the machine ID information from M1 to M4. Determination section 81 stores the determination data JD created in the determination processing in the determination database 82. As in Fig. As illustrated in Figure 4, the machine ID information, position ID information, device ID information, the end time of the usage period of role 46, and the location of the cause are linked in the determination data JD. Line names A to D were added for simplicity to distinguish the four determination data JDs. As described above, the combination of machine ID information, position ID information, device ID information, and end time information corresponds to the identification information of role 46. Information about the start time of the usage period can also be used instead of the end time information.

[0055] The identification information for roll 46 (combination of machine ID information, position ID information, device ID information and end time information) shows that the determination data JD in line A is for the X marking of the machine log data LD with the time information 19:45:50 in Fig. The three identified fault locations are determined. The determination data JD in line A indicates that the fault location is roller 46. Furthermore, the determination data JD in line B indicates that the fault location, which occurred in component placement machine 1 with machine ID information M3, is belt conveyor 45. The determination data JD in line C indicates that the fault location, which occurred in component placement machine 1 with machine ID information M2, is roller 46. The determination data JD in line D indicates that the fault location, which occurred in component placement machine 1 with machine ID information M4, is suction nozzle 53.

[0056] Memory section 83 continuously carries out the data in Fig. 5 illustrated memory processing. In step S1 of Fig. In step 5, memory section 83 captures the machine log data LD from component placement machine 1. In the next step, S2, memory section 83 determines whether the remaining count information contained in the captured machine log data LD is 1, i.e., whether it is the end-of-use time of reel 46. Memory section 83 returns to the processing flow in step S1 if it is not the end-of-use time, and continues with the processing flow in step S3 if it is the end-of-use time.

[0057] In step S3, memory section 83 captures various pieces of information for role 46, whose usage end time has been reached. Specifically, memory section 83 first captures all information contained in the machine log data LD. Next, memory section 83 sets the time information contained in the machine log data LD as the end time of the usage duration of role 46. Subsequently, memory section 83 searches retrospectively for machine log data LD in which the machine ID information, the position ID information, and the device ID information match, and sets the time information of the machine log data LD in which the remaining information count is 200 as the start time of the usage duration of role 46. In this way, the identification information of role 46 is confirmed.All information about the supplier, type and batch included in the machine protocol data LD becomes sorting information unchanged.

[0058] Next, in step S4, memory section 83 determines whether the machine ID information, position ID information, and device ID information match and whether the X (error occurrence) marker is present in the individual operating information of all machine log data LD, which covers the usage duration (from start time to end time). Memory section 83 continues the processing flow to step S5 if the X marker is present and branches the processing flow to step S7 if no X marker is present. In step S5, memory section 83 retrieves determination data JD from the determination database 82 and determines whether the location of the error cause is role 46. Memory section 83 forwards the processing flow to step S6 if the location of the cause is role 46 and branches the processing flow to step S7 if the location of the cause is not role 46.

[0059] In step S6, memory section 83 sets the error information as present. In step S7, memory section 83 sets the error information as absent. After the execution of step S6 or step S7, the processing flow proceeds to step S8. In step S8, memory section 83 creates a role data record (RD) corresponding to role 46 and stores the role data record (RD) in the role database 84.

[0060] An example of role data RD is in Fig. 6 illustrates each line in Fig. 6 corresponds to one roll of RD data and is equivalent to one roll of 46. RD data has a data format in which nine pieces of information are assigned. Specifically, RD data is linked to the machine ID, position ID, device ID, manufacturer, type, batch, start and end times of the usage period, and error information. In the error information column, "error present" is abbreviated as "present" and "error absent" as "absent". Furthermore, for clarity, row numbering from 1 to 21 has been added to distinguish between multiple RD data rolls.

[0061] Here, a concrete example of the memory processing of memory section 83 for the second roll 46 is described, in which the individual operating information in the machine log data LD is combined with the time information 19:45:50 in Fig. 3 are marked with an X. In step S1, memory section 83 records machine log data LD, whose time information is 19:56:25. Since the remaining quantity information contained in the machine log data LD is 1, memory section 83 retrieves all information contained in the machine log data LD in step S3. That is, memory section 83 retrieves the time 19:56:25, the machine ID M1, the position ID S12, the device ID F1, the manufacturer B, the type 15C, the batch L01, the remaining quantity 1, the nozzle ID N01, and the individual operating information of the marker O.

[0062] Next, memory section 83 19:56 sets the time information contained in the machine log data LD as the end time of the usage period of the second roll 46. Next, memory section 83 searches retrospectively for machine log data LD containing the machine ID information M1, the position ID information S12, and the device ID information F1. As a result of this retrospective search, memory section 83 18:22 sets the time information contained in the machine log data LD containing the remaining quantity information 200 as the start time of the usage period of the second roll 46. Furthermore, memory section 83 sets the captured information of supplier B, type 15C, and batch L01 unchanged as sorting information.

[0063] Furthermore, in step S4, memory section 83 searches for all machine log data LD where the machine ID information is M1, the position ID information is S12, and the device ID information is F1, and which cover the usage period (18:22 to 19:56), and confirms the individual operating information. As a result, memory section 83 recognizes that the individual operating information contained in the machine log data LD, whose time information is 19:45:50, is the X mark. Then, in step S5, memory section 83 determines, based on the determination data JD of line A, that the location of the fault cause is roller 46, and in step S6, memory section 83 sets the fault information as fault presence. Finally, memory section 83 creates the information in the third line of Fig. 6 illustrated role data RD and stores the role data RD in the role database 84.

[0064] In Fig. The first row of figure 6 shows the roller data (RD) corresponding to the first roller 46 used before the second roller 46. The fifth row shows the roller data (RD) corresponding to the third roller 46 used after the second roller 46. Furthermore, the second, fourth, and sixth rows illustrate the roller data (RD) corresponding to the rollers 46 used in the belt conveyor with device ID information F2, which is installed in component picker 1 with machine ID information M1. The roller data (RD) corresponding to the rollers 46 used in the three component pickers 1 with machine ID information M2 to M4 is illustrated in the seventh through twenty-first rows.

[0065] With regard to the role data RD of the tenth line, memory section 83 recognizes that the individual operating information contained in the machine log data LD of the usage period is marked with an X. Then, based on the determination data JD of line C, memory section 83 determines that the location of the fault is role 46 and sets the fault information of the role data RD of the tenth line to "Fault present". With regard to the role data RD of the sixteenth line, memory section 83 recognizes that the individual operating information contained in the machine log data LD of the usage period has an X mark. However, based on the determination data JD of line B, memory section 83 determines that the location of the fault is not role 46 and sets the fault information of the role data RD of the sixteenth line to "Fault not present", without considering (excluding) the X mark.With regard to the role data RD of the twentieth line, memory section 83 recognizes that the individual operating information contained in the machine log data LD of the usage period has the X marking. However, based on the determination data JD in line D, memory section 83 determines that the cause of the fault is not with role 46 and sets the fault information of the role data RD in the twentieth line to "No fault present" without considering (excluding) the X marking.

[0066] The role data (RD) of the sixth, eleventh, twelfth, seventeenth, eighteenth, and twenty-first lines is unconfirmed data, meaning the end time and error information are not yet determined. This indicates that role 46 is still in use. This unconfirmed data does not need to be stored in role database 84 at this time. The end time and error information of the unconfirmed data will be confirmed and stored after role 46 has ceased to be used.

[0067] Aggregation section 85 introduces the in Fig. 7 illustrated aggregation processing. Part of the processing in Fig. Step 7 is executed by the operator and display section 86. In step S11 of Fig. 7. The operator defines an aggregation period as the aggregation condition and specifies a sorting criterion. The present invention is not limited to this, and the aggregation condition can be automatically predefined. In the next step S12, the aggregation section 85 extracts the roll data RD corresponding to the roll 46 used in the aggregation period. At this point, only the roll 46 whose entire usage period falls within the aggregation period can be extracted, or the roll 46 whose usage period partially overlaps with the aggregation period can be extracted. However, the roll 46 currently in use is excluded from the extraction target.

[0068] As an example, assume the current time is 9:40 PM, an aggregation period of 6:00 PM to 9:30 PM is set, and a provider is specified as the sorting criterion. Aggregation section 85 extracts seven roll data RD (indicated by a thick border) from the third, fourth, ninth, tenth, fifteenth, sixteenth, and twentieth rows in Fig. 6, where the entire usage period lies within the aggregation period. Alternatively, aggregation section 85 can also extract role data RD where part of the usage period overlaps with the aggregation period. That is, in addition to the seven role data RD described above, aggregation section 85 can extract eight role data RD from the first row, the second row, the fifth row, the seventh row, the eighth row, the thirteenth row, the fourteenth row, and the nineteenth row.

[0069] In the next step, S13, aggregation section 85 focuses on the defined sorting criterion and the sorting information of each of the several extracted role data sets (RD). In the next step, S14, aggregation section 85 aggregates the usage count (Nu) of roles 46 for each of the several groups sorted according to the sorting information. That is, aggregation section 85 focuses on the supplier information contained in the seven role data sets (RD) described above and aggregates the usage count (Nu) of supplier A as 2 (see the ninth and tenth rows). Similarly, in the case of supplier A, aggregation section 85 aggregates the usage count (Nu) of supplier B as 3 (see the third, fourth, and twentieth rows) and aggregates the usage count (Nu) of supplier C as 2 (see the fifteenth and sixteenth rows). The aggregated value is shown in the usage count (Nu) column in Fig. Figure 8 shows the aggregation result.

[0070] In the next step, S15, aggregation section 85 aggregates the number of roles 46 that correspond to the error occurrence for each of the several groups. That is, aggregation section 85 aggregates the number Ne corresponding to the error occurrence of supplier A as 1 (see tenth row). Similarly, in the case of supplier A, aggregation section 85 aggregates the number Ne corresponding to the error occurrence of supplier B as 1 (see third row) and aggregates the number Ne corresponding to the error occurrence of supplier C as 0. The number Ne is in the error occurrence column Ne in Fig. 8 is shown. The aggregation section 85 can be used instead of the number Ne of error occurrences shown in Fig. 8. Aggregate the illustrated number Nn of error absences or aggregate both the number Ne of error occurrences and the number Nn of error absences.

[0071] In the next step, S16, display section 86 converts the data into Fig. The aggregation result shown in Figure 8 of the aggregation section 85 is converted into a diagram and displayed on the display device 72. For example, the display section 86 shows a bar chart for each supplier, as shown in Figure 86. Fig. Figure 9 illustrates this. This bar chart shows three bars corresponding to supplier A, supplier B, and supplier C. The length of each bar indicates the defect rate as a percentage, calculated by dividing the number of defects (Ne) by the usage rate (Nu). Furthermore, display section 86 shows the number of defects (Ne) and the usage rate (Nu) in fractional form in the upper section of each bar. The present invention is not limited to this, and display section 86 can use a different display format, for example, showing the defect rate for each supplier in a pie chart.

[0072] In the next step, S17, the operator determines whether the aggregation condition should be changed. If the aggregation condition is changed, the processing flow returns to step S11. As a result, the operator can change at least one of the aggregation periods and the sorting criterion to perform a new aggregation and display. Alternatively, based on the aggregation result for each supplier, the operator can designate a specific supplier and perform aggregation (hierarchical aggregation) and display for each component type or for each batch. If the aggregation condition is not changed, the processing flow ends. 4. Another example of the operation of the aggregation section 85 and the display section 86

[0073] Next, another operational example for the aggregation section 85 and the display section 86 will be given with reference to the Fig. 10, Fig. 11, Fig. 12 to Fig. 13 described. Even if a longer aggregation period is specified, the aggregation section 85 can obtain a second aggregation result by performing the same aggregation processing as described above. Furthermore, the display section 86 can display the second aggregation result as described in Fig. 10 shown using the same display format as in Fig. Show 9. In the Fig. The illustrated bar chart shows four bars corresponding to suppliers A to D. The number of error occurrences (Ne) and the usage count (Nu) are displayed in fractional format and are 14 / 20 for supplier A, 8 / 20 for supplier B, 3 / 20 for supplier C, and 3 / 10 for supplier D.

[0074] The operator can, for example, select supplier A with the highest error rate and perform an aggregation and display for each component type. According to the operator's selection, aggregation section 85 focuses on supplier A's role 46, aggregates the usage count Nu and the number of error occurrences Ne for each component type, and obtains a third aggregation result. Display section 86 shows the third aggregation result as shown in Fig. 11 shown, using the same display format as in the Fig. 9 and Fig. 10 on. In which in Fig. Figure 11 shows three bars corresponding to component types 15R, 15C, and 21R. The number of failures (Ne) and the number of uses (Nu) are also displayed in fractional format: 8 / 10 for type 15R, 6 / 10 for type 15C, and 0 / 2 for type 21R.

[0075] Based on the second and third aggregation results, the manager or designer recognizes that the defect rate of role 46 from supplier A is higher than that of suppliers B through D. Furthermore, the manager or designer recognizes that the defect rate is high for role 46, which supplies the type 15R component and the type 15C component from supplier A, while no defects occur for role 46, which supplies the type 21R component. The manager or designer can incorporate these findings into effective countermeasures.

[0076] As a countermeasure, for example, supplier A can be asked to improve the quality of role 46. In this case, submitting the aggregation result can contribute to a concrete improvement measure for quality enhancement. Alternatively, the use of supplier A's role 46 can be avoided altogether. In this case, by referring to the aggregation result, it is possible to appropriately define the scope of unused roles 46 and limit their spread.

[0077] Aggregation section 85 may use a different method than the one described in Fig. 7. Use the aggregation procedures described. For example, aggregation section 85 can aggregate the number of rolls 46 corresponding to four error ranks for each supplier and obtain as an aggregation result a ratio of the roll 46 corresponding to each error rank to the usage number Nu for each supplier. Display section 86 can display the aggregation result of aggregation section 85 in the format described in Fig. Display 12 illustrative band diagrams. In Fig. 12. For each of the providers A to D, the ratio of the four error ranks, in which the number of error occurrences is 0, 1, 2 to 3 and 4 or more, is shown in the band diagram.

[0078] As described above, the error information can be represented by an error occurrence rate. In this case, aggregation section 85 can determine an average value (average error occurrence rate) of the error occurrence rates of several roles 46 for each provider and use the average value as the aggregation result. Display section 86 can display the aggregation result of aggregation section 85 in the format shown. Fig. Display the line chart shown in section 13. Fig. Figure 13 shows the average failure rates of providers A to D, represented by black circles, and four black circles are connected by a polygon line.

[0079] In the production management device 7 of the exemplary embodiment, the memory section 83 stores the sorting information for grouping multiple rolls 46 and the error information, which indicates the occurrence history of the error during the assembly process, in conjunction with the identification information of each of the multiple rolls 46. The aggregation section 85 aggregates or statistically processes the error information for each group of rolls 46 that were used in a predetermined aggregation period. As described above, in contrast to the prior art, which determines whether the location of the cause is the roll 46, detailed aggregation or statistical processing is performed for each group of multiple rolls 46, thus making it possible to compare the occurrence status of errors between groups and to consider the comparison result in an effective countermeasure.Furthermore, the productivity of component placement machine 1 is expected to improve through the implementation of an effective countermeasure. 5. Modification of the production management device 7

[0080] The production management device 7 of the exemplary embodiment can be modified by omitting the determination section 81 and the determination database 82. In this modification, no determination data JD exists. If the machine log data LD contains an X-mark in the individual operating information for the usage period of the roll 46, the memory section 83 unconditionally sets the error information from the roll data RD as an error. Furthermore, in addition to the sorting criteria (supplier, type, and batch of the component) for sorting the roll 46 itself, it is possible to define a sorting criterion relating to the handling of the roll 46.In particular, the device ID information of the belt conveyor 45, the combination of the machine ID information of the component placer 1 and the position ID information of the slot 42, the nozzle ID information of the suction nozzle 53 and the component data in the assembly data PD can be defined as a sorting criterion.

[0081] If the sorting criterion is defined with respect to the handling of the roller 46, the aggregation section 85 can obtain the aggregation result, which helps to estimate the location of the cause. For example, if the device ID information of the belt conveyor 45 is defined as the sorting criterion, the aggregation section 85 receives an aggregation result obtained by aggregating the usage count Nu of the rollers 46 and the number Ne of fault occurrences for each individual belt conveyor 45. Therefore, the operator or a similar person can easily find the belt conveyor 45 where a fault is likely to occur.

[0082] Furthermore, it is possible, for example, to define a sorting criterion for the sorting of the roll 46 itself and a sorting criterion relating to the handling of the roll 46 in combination, and to instruct the aggregation section 85 to perform complex statistical processing. For instance, a case is considered in which the failure rate is used as failure information and the component manufacturer and nozzle ID information are defined as sorting criteria. In this case, the aggregation section 85 can perform a multiple regression analysis, using the failure rate as the response variable and the component manufacturer and nozzle ID information as explanatory variables.Using multiple regression analysis, it is possible to quantitatively analyze the extent to which a difference between manufacturers and an individual difference of the suction nozzle 53 are related to a defect, and to contribute to the testing of a countermeasure. 6. Application and modification of the exemplary embodiments

[0083] The data formats of the machine log data LD and the reel data RD can be modified accordingly. Memory section 83 can receive the machine log data not only from the component placement machine 1, but also from the circuit board visual inspector 93, and detect an error in the assembly process. Since the machine log data of the circuit board visual inspector 93 includes the test result information, in which the assembly position and orientation of the assembled component are determined as normal or defective, the error range covered by the production management device 7 is extended. Furthermore, the embodiment can be applied or modified in various ways. Reference symbol list 1 Component picker 4 Component Feeding Unit 42 slots 45 belt conveyors 46 rolls 53 Suction nozzle 6 Control device 7 Production Management Device 81 Determination section 82 Identification database 83 Storage section 84 Role database 85 Aggregation section 86 Display section 9 circuit board production line 95 Line Management Device PD assembly data LD machine log data JD determination data RD role data QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP-A-2005-286015

[0004] JP 7142149

[0032]

Claims

[1] Production management device comprising the following: a memory section configured to store sorting information for sorting component holding elements into multiple groups, wherein the component holding elements hold components and are interchangeably inserted in a component feeder forming a component picker, as well as error information showing an error history during an assembly operation for collecting the components from the component holding elements and mounting the components onto a circuit board in the component picker, in conjunction with identification information for each of the multiple component holding elements; and an aggregation section configured to aggregate or statistically process the error information for each of the multiple groups for the component recording elements used in a predetermined aggregation period. [2] Production management device according to claim 1, wherein the memory section stores several types of sorting information belonging to several types of sorting criteria and differing from each other, as well as the error information in conjunction with the identification information of each of the several component intake elements, and The aggregation section statistically aggregates or processes the error information for each of the multiple groups, sorted according to the sorting information belonging to a specified sorting criterion. [3] Production management device according to claim 2, wherein the aggregation section performs hierarchical or complex aggregation or statistical processing of the group, which is sorted according to the multiple types of sorting information belonging to the multiple specified types of sorting criteria. [4] Production management device according to claim 2 or 3, wherein the multiple types of sorting criteria comprise two or more of the following criteria: a supplier, a type and a batch of the component included in the component receiving element. [5] Production management device according to claim 4, wherein the aggregation section aggregates or statistically processes the error information for each of the multiple suppliers and further aggregates or statistically processes the error information for each of the multiple types or for each of the multiple batches for a particular supplier. [6] Production management device according to any one of claims 1 to 3, comprising: a determination section configured to determine whether a location of a cause of the fault is the component receiving element, where the memory excludes from the error information the error whose cause is not the component receiving element. [7] Production management device according to one of claims 1 to 3, wherein the aggregation section aggregates for each of the several groups the number of component receiving elements used in the aggregation period and the number of component receiving elements that correspond to at least one of several fault ranks obtained by quality classification of the fault information. [8] Production management device according to claim 7, wherein the fault rank is used to determine the number of fault occurrences for each component receiving element. [9] Production management device according to claim 8, wherein the fault rank is represented using “fault presence”, where the number of fault occurrences is one or more, and “fault absence”, where the number of fault occurrences for each component receiving element is zero. [10] Production management device according to claim 9, wherein the aggregation section aggregates for each of the multiple groups the number of component receiving elements used in the aggregation period and the number of component receiving elements corresponding to the ‘presence of a fault’ or the ‘absence of a fault’. [11] Production management device according to one of claims 1 to 3, wherein the aggregation period is manually variable or is set in advance to a specific period. [12] Production management device according to one of claims 1 to 3, wherein the storage section records machine log data representing a history of the assembly process in the component picker, obtains the sorting information and the error information of each of the multiple component holding elements from the machine log data and stores the sorting information and the error information. [13] The production management device according to claim 12, wherein the machine log data includes individual operating information indicating whether the error occurred during an individual assembly operation for each of the components, time information of the assembly operation, and information about the remaining number of components held in the component holding element, and The memory receives a usage duration of the component intake elements based on the remaining number of components and the error information based on the individual operating information of the usage duration. [14] Production management device according to claim 13, wherein the machine protocol data includes machine ID information that enables identification of the component picker, and device ID information that enables identification of the component feeder, or position ID information that enables identification of a position of the component feeder in the component picker, and The memory section specifies a combination of the usage duration, machine ID information, and device ID information or position ID information as identification information for the component receiving element. [15] Production management device according to any one of claims 1 to 3, comprising: a display section configured to show a result of the aggregation section, which aggregates or statistically processes the error information, in a chart. [16] Production management device according to one of claims 1 to 3, wherein a sorting criterion comprising several sorting information is at least the component feeder in which the component receiving element is arranged, a position of the component feeder in the component picker, a component pick-up tool configured to pick up the component from the component receiving element, and component data describing a shape or handling method of the component. [17] Production management device according to one of claims 1 to 3, wherein the component receiving element is a combination of a carrier belt which receives the component in each of several cavities arranged in a series and a roller around which the carrier belt is wound, or a tray which is configured to receive the component in each of several receiving sections arranged in a grid shape.

Images