Component Data Management Method, Component Data Management Device, Component Data Management Program, and Component Data Management System

Abstract

To provide a component data management method capable of efficiently accumulating component data and achievement data in a database, a component data management device, a component data management program, and a component data management system.SOLUTION: A component data management method for managing component data associating operating parameters as the operating conditions of component mounting equipment with component information, the method includes the steps of: acquiring at least component data used by the component mounting equipment and achievement data obtained when a component is mounted by the component mounting equipment using the component data (ST3); comparing component data stored in the database and acquired component data (ST4); and storing the acquired component data and the acquired achievement data in the database based on the comparison result (ST5, ST6).SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention relates to a component data management method, a component data management device, a component data management program, and a component data management system for managing component data used in a component mounting device for mounting components on a substrate.

Background Art

[0002] In a component mounting device for mounting components on a substrate, the component mounting operation is controlled based on a number of operation parameters including operation conditions related to mounting components on the substrate, sucking components with a nozzle, photographing components, etc. These operation parameters are set with appropriate values for each component as component data associated with component information including information such as the shape of the component. Patent Document 1 discloses a system that registers usage records such as component data, the number of usage times, and the number of products used in a database, and extracts selected components based on a list of components requested for selection from the database.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art including Patent Document 1, the amount of component data and usage record data acquired daily from a plurality of factories and production lines is enormous. Also, when the database is installed away from the factory or in a cloud environment, the amount of data communication between the factory and the database also becomes enormous. Therefore, there is room for further improvement in efficiently accumulating component data and performance data in the database.

[0005] Therefore, an object of the present invention is to provide a component data management method, a component data management device, a component data management program, and a component data management system capable of efficiently storing component data and performance data in a database.

Means for Solving the Problems

[0006] The component data management method of the present invention is a component data management method for managing component data in which operation parameters, which are operation conditions of a component mounting device for mounting the component on a substrate, are associated with component information of the component. The method includes: an acquisition step of acquiring at least the component data used in the component mounting device and the performance data obtained when the component is mounted by the component mounting device using the component data; a comparison step of comparing the acquired component data with the component data stored in a database that associates and stores the component data and the performance data; and a storage step of storing the acquired component data and the acquired performance data in the database based on the result of the comparison.

[0007] The component data management device of the present invention is a component data management device for managing component data in which operation parameters, which are operation conditions of a component mounting device for mounting the component on a substrate, are associated with component information of the component. The device includes: an acquisition unit that acquires at least the component data used in the component mounting device and the performance data obtained when the component is mounted by the component mounting device using the component data; a comparison unit that compares the acquired component data with the component data stored in a database that associates and stores the component data and the performance data; and a storage processing unit that stores the acquired component data and the acquired performance data in the database based on the result of the comparison.

[0008] The component data management program of the present invention is a component data management program that causes a computer to execute management of component data in which operation parameters, which are operation conditions of a component mounting apparatus for mounting the component on a substrate, are associated with component information of the component. The component data management program includes at least an acquisition step of acquiring at least the component data used in the component mounting apparatus and the performance data obtained when the component is mounted by the component mounting apparatus using the component data, a comparison step of comparing the acquired component data with the component data stored in a database that stores the component data and the performance data associated with each other, and a storage step of storing the acquired component data and the acquired performance data in the database based on the result of the comparison.

[0009] The component data management system of the present invention is a component data management system including a component mounting apparatus for mounting a component on a substrate and a component data management apparatus for managing component data in which operation parameters, which are operation conditions of the component mounting apparatus, are associated with component information of the component. The component data management system includes a data collection unit that collects performance data obtained when the component is mounted by the component mounting apparatus using the component data. The component data management apparatus includes at least an acquisition unit that acquires at least the component data used in the component mounting apparatus and the collected performance data, a comparison unit that compares the acquired component data with the component data stored in a database that stores the component data and the performance data associated with each other, and a storage processing unit that stores the acquired component data and the acquired performance data in the database based on the result of the comparison.

Advantages of the Invention

[0010] According to the present invention, component data and performance data can be efficiently accumulated in a database.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Embodiments for Carrying Out the Invention

[0012] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The configurations, shapes, etc. described below are illustrative examples for explanation, and can be appropriately changed according to the specifications of the production system (component data management system), component mounting line (production line), component mounting device, and component data management device. In the following, corresponding elements in all the drawings are denoted by the same reference numerals, and duplicate explanations are omitted.

[0013] First, referring to FIG. 1, the configuration of the production system 1 will be described. The production system 1 includes customer factories F1 to F3 and a support center S that is located at a place remote from the factories F1 to F3 and supports the customers' production activities. In each of the factories F1 to F3, a component mounting line for producing a mounting substrate is installed as a production line for producing products. Hereinafter, factory F1 will be referred to as "the first factory F1", factory F2 as "the second factory F2", and factory F3 as "the third factory F3". In FIG. 1, the configuration of factories F1 to F3 will be described taking the first factory F1 as an example.

[0014] In FIG. 1, in the first factory F1, there is one component mounting line L1 configured by connecting production devices such as a printing device M1 and a plurality of component mounting devices M2 and M3. The component mounting line L1 has a function of producing a mounted substrate while sequentially mounting components on the substrate by the printing device M1 and the component mounting devices M2 and M3. Note that it is not necessary for the component mounting line L1 installed in the first factory F1 to be one, and two or more may be provided. Also, the number of component mounting devices M2 and M3 constituting the component mounting line L1 does not have to be two, and one or three or more may be provided.

[0015] Each production device in the first factory F1 is connected to an in-plant communication network 2 such as a LAN (Local Area Network), and is connected to a production management device 3 via an internal communication unit 4. The production management device 3 has a function of creating data and parameters necessary for the operation of the production devices provided in the component mounting line L1 and transmitting them to each production device. Also, data such as the operation status and work history of each production device is transmitted from each production device to the production management device 3. Further, the production management device 3 has a function of creating component data, production data, etc. used in the production devices of the component mounting line L1. Note that the first factory F1 may be configured to include a line management device that manages the production of mounted substrates for each component mounting line L1 in addition to the production management device 3.

[0016] In FIG. 1, a component data management device 7 is installed in the support center S. The production management devices 3 of the plurality of factories F1 to F3 are provided with external communication units 5. Also, the component data management device 7 of the support center S is provided with an external communication unit 8. The external communication unit 5 and the external communication unit 8 are connected to an off-plant communication network 6 such as the Internet or a mobile communication line. With this configuration, the production management device 3 and the component data management device 7 can exchange information via the off-plant communication network 6. The component data management device 7 acquires performance information and component data of production devices from the production management devices 3 of each factory F1 to F3 and stores them in a database. Also, the component data management device 7 has a function of extracting information from the database and transmitting (outputting) it in response to a request from the production management device 3.

[0017] Note that the production management device 3 and the component data management device 7 are not limited to a configuration in which they directly exchange information via the off-premises communication network 6, and they may exchange information via the cloud. That is, the information transmitted from each device may be stored in the cloud, and the information may be transmitted from the cloud to each device in response to a request. Also, information may be transmitted and received using a communication tool such as e-mail or a data communication line.

[0018] Next, with reference to FIG. 1, the component mounting line L1 will be described. The printing device M1 is a production device having a function of performing a solder printing operation of screen-printing cream solder for component bonding on a substrate. The component mounting devices M2 and M3 are production devices having a function of performing a component mounting operation of mounting components on the substrate after solder printing.

[0019] The component mounting devices M2 and M3 take out the components supplied by the feeder by vacuum suction with the nozzles of the mounting head based on the operation parameters included in the component data set for each component to be mounted on the substrate, image the state of the components held by the nozzles with the component recognition camera, and mount them at the mounting angle designated at the mounting position on the substrate. The component mounting devices M2 and M3 are provided with a plurality of sensors, and work mistakes and operation errors in the component mounting operation, such as the suction operation in which the nozzle sucks the component and the component recognition operation in which the component recognition camera images and recognizes the taken-out component, are monitored.

[0020] Next, with reference to FIG. 2, the configuration of the production system 1 (component data management system) including the production management device 3 and the component data management device 7 will be described. Here, among the plurality of functions provided by the production management device 3 and the component data management device 7, the configuration related to the function of collecting and managing the component data and performance data used in the component mounting devices M2 and M3 will be mainly described. Also, the production management devices 3 installed in the factories F1 to F3 have the same configuration, and here, the first factory F1 will be described as an example.

[0021] The production management device 3 installed in the first factory F1 is connected to an internal communication unit 4, an external communication unit 5, an input unit 9, and a display unit 10. The production management device 3 includes a production management memory unit 11, a data collection unit 15, a totaling unit 16, and a control unit (not shown). The production management memory unit 11 is a storage device such as a semiconductor memory or a hard disk drive, and stores a production library 12, a parts library 13, performance data 14, and the like.

[0022] The input unit 9 is an input device such as a keyboard, a touch panel, or a mouse, and is used when an operation command or data is input. The display unit 10 is a display device such as a liquid crystal panel, and displays various data stored in the production management memory unit 11, as well as various information such as an operation screen and an input screen for operations by the input unit 9. The control unit is, for example, a CPU (Central Processing Unit), and controls the entire production management device 3.

[0023] In FIG. 2, the production library 12 stores production data used in the production of mounting substrates by the component mounting devices M2 and M3 for each production model name of the mounting substrates. The production data includes a part name that identifies the part to be mounted on the substrate, a part code that associates the part with the part data in the parts library 13, the mounting position of the part on the substrate, the mounting angle, the part arrangement indicating the position of the feeder that supplies the part in the component mounting devices M2 and M3, the nozzle arrangement indicating the position of the nozzle that adsorbs the part in the mounting head, and the like. The parts library 13 stores a plurality of part data in which operation parameters are associated with part information. The part data is associated with the production data in the production library 12 by a part data code.

[0024] Referring now to FIG. 3, an example of the component data 17 included in the component library 13 will be described. The component data 17 is associated with the production data by the "component n" (component data code) included in the component data 17 and the component data code of the production data included in the production library 12. In this example, the component library 13 stores component data 17 of a plurality of types of components having component data codes of n = 1, 2, 3, ···. In the component data 17, component information 18 and operation parameters 19 are defined as major classification items.

[0025] The component information 18 is information indicating attributes unique to the component. Here, as intermediate classification items, "product name" 18a, "shape" 18b, "size" 18c, and "component parameters" 18d are exemplified. The "product name" 18a is part number information for identifying the component, and the "part number" assigned for management by the component manufacturer or the company itself is defined as a minor classification item. The "shape" 18b is information regarding the shape of the component, and the "shape" indicating the outer shape of the component by shape classification such as rectangular or cylindrical, the drawing showing the shape of the component, and information specifying image information are defined as minor classification items.

[0026] In the "size" 18c, "outer dimensions" indicating the size of the component and "electrode position" indicating the number and position (spacing) of connection electrodes (leads) formed on the component are defined as minor classification items. The "component parameters" 18d are attribute information of the component, and as minor classification items, "component type" indicating the type of the component, "polarity presence or absence" indicating the presence or absence of directionality in the outer shape of the component, "polarity mark" indicating the shape of the mark attached to the component in the case of having polarity, and "mark position" indicating the position of the mark in the case of having a polarity mark are defined. Thus, the component information 18 includes at least one of the component dimensions (size 18c), part number information (product name 18a), number information of the number of leads, lead spacing information (size 18c), and image information (shape 18b).

[0027] In FIG. 3, the operation parameter 19 is a control parameter (operation condition) used to control the component mounting devices M2 and M3 when performing component mounting operations by the component mounting devices M2 and M3 arranged on the component mounting line L1 for the components specified in the component data 17. Here, as intermediate classification items, "nozzle setting" 19a, "speed parameter" 19b, "recognition" 19c, "adsorption" 19d, and "mounting" 19e are exemplified.

[0028] The "nozzle setting" 19a is data regarding the suction nozzle used when sucking and holding the component, and "nozzle" that specifies the type of suction nozzle selectable as a sub-classification item is defined. As data for the "nozzle", in addition to the type, the opening diameter, identifier, etc. may also be used. The "speed parameter" 19b is a control parameter regarding the moving speed of the suction nozzle in the work operation of taking out the component by the suction nozzle and mounting it on the substrate. These control parameters include, as sub-classification items, "suction speed" and "suction holding time" when sucking and holding the component, and "mounting speed" and "mounting holding time" when mounting the held component on the substrate.

[0029] In FIG. 3, the "recognition" 19c is a parameter regarding the execution of recognition processing for imaging and recognizing the component taken out from the component supply unit by the suction nozzle using the component recognition camera. These parameters include, as sub-classification items, "camera type" that specifies the type of camera used for imaging, "lighting mode" that indicates the mode of lighting used during imaging, and "recognition speed" when recognizing the image acquired by imaging.

[0030] "Suction" 19d is a control parameter related to the suction operation when taking out components from the component supply unit by the suction nozzle. These control parameters include, as sub-classification items, "Suction Position X", "Suction Position Y", etc., which indicate the suction position offset when the suction nozzle lands on the component. "Mounting" 19e is a control parameter related to the mounting operation of moving the mounting head that holds the component by the suction nozzle to the substrate and causing the suction nozzle to perform a lifting and lowering operation to mount the component on the substrate. These control parameters include, as sub-classification items, "Mounting Load", which is the load for pressing the component against the substrate when the suction nozzle is lowered to land the component on the substrate.

[0031] In FIG. 3, even if the "Product Name" 18a is the same, that is, the component information 18 is the same component, the operation parameters 19 of the component mounting devices M2 and M3 for mounting the component on the substrate may be changed due to changes in the type of the substrate, the material of the substrate, the electrodes of the substrate, etc., or in order to improve the mounting quality and the mounting error rate. When the operation parameters 19 of the component are changed, component data 17 is created (updated) by associating the changed operation parameters 19 with the component information 18 without changing the component information 18. At this time, a new code is assigned to "Component n" (component data code) of the component data 17 to distinguish it from the operation parameters 19 before correction.

[0032] In this way, the component data 17 has the operation parameters 19, which are the operation conditions for the component mounting devices M2 and M3 to mount the component on the substrate, associated with the component information 18 indicating the unique attributes of the component. The component data 17 in the component library 13 is transmitted together with the production data in the production library 12 to the component mounting devices M2 and M3 on the component mounting line L1 and is used for the production of the mounting substrate in the component mounting devices M2 and M3.

[0033] In FIG. 2, the data collection unit 15 collects the results of component mounting operations from the production equipment (printing device M1, component mounting devices M2, M3) on the component mounting line L1 installed in the first factory F1. The results of the component mounting operations include information such as the production start date and time, production end date and time, number of produced units, number of component pick-up times, number of component mounting times, number of work mistakes, mistake rate (frequency), number of operation errors and their details, etc.

[0034] Based on the performance information collected by the data collection unit 15, the aggregation unit 16 aggregates, for each component name of the components mounted on the substrate, the mistake rate, number of mistakes, actual number of component pick-ups, actual number of components mounted, etc. within the aggregated period. Furthermore, the aggregation unit 16 associates the aggregated information with the information identifying the component mounting devices M2, M3 that performed the component mounting operations, and stores it in the production management storage unit 11 as performance data 14. That is, the performance data 14 obtained when components are mounted by the component mounting devices M2, M3 using the component data 17 includes the period during which the components were mounted, the mistake rate when the components were mounted, the number of mistakes, the actual number of component pick-ups, the actual number of components mounted, etc.

[0035] Here, referring to FIG. 4(a), an example of the performance data 14 aggregated by the aggregation unit 16 will be described. The performance data 14 is created for each component name 40 of the components. Also, the performance data 14 is created for each of the component mounting devices M2, M3, or for each type of the component mounting devices M2, M3, and for each component mounting line L1 (production line). The performance data 14 includes the date 41, component data code 42, number of pick-up mistakes 43, number of mounting mistakes 44, and total number of pick-ups 45. In this example, the aggregation unit 16 aggregates and stores the number of pick-up mistakes 43, number of mounting mistakes 44, and total number of pick-ups 45 for one day for each component data code 42 (component n) of the component data 17 for the component with the component name 40 being "D11". Note that the aggregation does not necessarily have to be in units of one day, and units such as time units or production model units can be set as appropriate.

[0036] The total number of suction operations 45 is the total number of times the nozzle has suctioned to mount the component with part number 40 of "D11" onto the substrate during the aggregation period. The number of suction failures 43 is the total number of times the nozzle has failed to suction the component with part number 40 of "D11" during the aggregation period. The number of mounting failures 44 is the total number of times (quantity) the state of the component with part number 40 of "D11" mounted on the substrate has been defective during the aggregation period. For example, on the date 41 of "January 3rd", it indicates that using the component data 17 with the component data code 42 of "111", the component with part number 40 of "D11" has been suctioned "5000 times", with "15" suction failures and "1" mounting failure. Also, on the date 41 of "January 3rd", using the component data 17 with the component data code 42 of "112", the component with part number 40 of "D11" has been suctioned "20000 times".

[0037] In FIG. 2, the component data management device 7 installed in the support center S has a function of collecting and managing the component data 17, performance data 14, etc. used in the customer's factories F1 to F3. An external communication unit 8 and a storage device 20 are connected to the component data management device 7. The storage device 20 is, for example, a semiconductor memory or a hard disk drive. The storage device 20 includes a database 21 for storing information such as the component data 17 and performance data 14 obtained from a plurality of factories F1 to F3. Note that the database 21 may include data prepared in advance by an EDA (Electronic design automatio) vendor.

[0038] The component data management device 7 includes information processing devices such as an acquisition unit 30, a comparison unit 31, a storage processing unit 32, an output unit 33, and a control unit (not shown). Note that each information processing device may be composed of independent hardware assets or may be composed of a common CPU and programs for each information processing. The control unit is, for example, a CPU (Central Processing Unit) and controls the entire component data management device 7. Also, the component data management device 7 does not necessarily need to be composed of one computer and may be composed of a plurality of devices. For example, all or part of the storage device 20 and the information processing devices may be provided in the cloud via a server.

[0039] In FIG. 2, the acquisition unit 30 acquires component data 17 used in the component mounting apparatuses M2 and M3 from a plurality of factories F1 to F3 via the external communication unit 8, and performance data 14 corresponding to the component data 17. The acquisition of data by the acquisition unit 30 is executed, for example, once a day at a predetermined time. The comparison unit 31 compares the component data 21a stored in the database 21 with the acquired component data 17. The storage processing unit 32 executes a storage process of storing the acquired component data 17 and the acquired performance data 14 in the database 21 based on the result of the comparison by the comparison unit 31.

[0040] Specifically, when the comparison unit 31 determines that the component information 18 and the operation parameters 19 of the acquired component data 17 match the stored component data 21a, the storage processing unit 32 integrates the acquired performance data 14 with the stored performance data 21b and stores it in the database 21 (integrated storage). Further, when the comparison unit 31 determines that the acquired component data 17 does not match the stored component data 17, the storage processing unit 32 uses the acquired component data 17 as new component data 21a and the acquired performance data 14 as new performance data 21b and stores them in the database 21 (new storage).

[0041] Note that the comparison unit 31 also compares at least one item of information for specifying the component mounting apparatuses M2 and M3 that use the component data 17, the types of the component mounting apparatuses M2 and M3, the production line (component mounting line L1) where the component mounting apparatuses M2 and M3 are installed, and the factories F1 to F3 where the component mounting apparatuses M2 and M3 are installed, in addition to the component information 18 and the operation parameters 19 of the component data 17, to determine whether they match. That is, the information of the same component mounted on the same component mounting apparatuses M2 and M3 is integrated and stored in the database 21.

[0042] Here, referring to FIG. 4(b), an example of the performance data 21b integrated by the storage processing unit 32 will be described. Here, an example will be described in which the performance data 14 for January 7th obtained from factory F1 in the morning of January 8th, shown in FIG. 4(a), is integrated into the performance data 21b stored in the database 21. That is, the performance data 21b stored in the database 21 before integration was created based on the performance data 14 up to January 6th. The storage processing unit 32 integrates the performance data 14 for one week as the performance data 21b. That is, in this example, it shows the integrated state of the component data 17 for the first week of January (January 1st to January 7th). Note that the integration does not necessarily have to be in units of one week and is set as appropriate.

[0043] In FIG. 4(b), the date 41 is the final date when the performance data 14 of the component with the part name 40 being "D11" was integrated. In this example, the total of the adsorption error count 43, mounting error count 44, and total adsorption count 45 from January 3rd to January 5th using the component data 17 with the component data code 42 being "112" is stored in the column where the date 41 is "January 5th". Also, the total of the adsorption error count 43, mounting error count 44, and total adsorption count 45 from January 1st to January 3rd and from January 6th to January 7th using the component data 17 with the component data code 42 being "111" is stored in the column where the date 41 is "January 7th".

[0044] In FIG. 2, the output unit 33 extracts information that matches the requests from the production management devices 3 of factories F1 to F3 from the database 21 and outputs (transmits) it to the requesting production management device 3. In this way, based on the result of comparing the obtained component data 17 with the component data 21a stored in the database 21, by storing the obtained component data 17 and performance data 14 in the database 21, the component data 17 and performance data 14 can be efficiently accumulated in the database 21.

[0045] Next, a component data management method (data management program) for managing component data 17 will be described along the flow of FIG. 5. First, the data collection unit 15 of the production management device 3 in factories F1 to F3 collects the results of component mounting operations from the component mounting devices M2 and M3 on the component mounting lines L1 (production lines) installed in factories F1 to F3 (ST1: data collection process). Then, the aggregation unit 16 aggregates the performance data 14 from the collected results of the component mounting operations while the component mounting devices M2 and M3 are mounting components (ST2: aggregation process).

[0046] Next, the acquisition unit 30 of the component data management device 7 in the support center S acquires the component data 17 used by the component mounting devices M2 and M3 from the production management device 3 in factories F1 to F3, and the performance data 14 obtained when the component mounting devices M2 and M3 mount components using the component data 17 (ST3: acquisition process). Next, the comparison unit 31 compares the component data 21a stored in the database 21 with the acquired component data 17 (ST4: comparison process).

[0047] In FIG. 5, when it is determined as "match" in the comparison process (ST4), the storage processing unit 32 integrates the acquired performance data 14 with the stored performance data 21b and stores it in the database 21 (integrated storage) (ST5: integrated storage process). When it is determined as "mismatch" in the comparison process (ST4), the storage processing unit 32 stores the acquired component data 17 as new component data 21a and the acquired performance data 14 as new performance data 21b in the database 21 (new storage) (ST6: new storage process).

[0048] That is, the acceptance storage process (ST5) and the new storage process (ST6) are storage processes for storing the acquired component data 17 and the acquired performance data 14 in the database 21 based on the comparison result in the comparison process (ST4). In the comparison process (ST4), when the acquired component data 17 matches the stored component data 21a, in the storage process, the acquired performance data 14 is integrated into the stored performance data 21b and stored in the database 21 (ST5). If they do not match, in the storage process, the acquired performance data 14 is stored in the database 21 as new performance data 21b (ST6). As a result, the component data 17 and the performance data 14 can be efficiently accumulated in the database 21.

[0049] As described above, the component data management device 7 that manages the component data 17 of the present embodiment includes at least an acquisition unit 30 that acquires the component data 17 used in the component mounting devices M2 and M3 and the performance data 14 obtained when components are mounted by the component mounting devices M2 and M3 using the component data 17, a comparison unit 31 that compares the component data 17 stored in the database 21 that associates and stores the component data 17 and the performance data 14 with the acquired component data 17, and a storage processing unit 32 that stores the acquired component data 17 and the acquired performance data 14 in the database 21 based on the comparison result. As a result, the component data 17 and the performance data 14 can be efficiently accumulated in the database 21.

[0050] In the embodiment of the above production system 1 (component data management system), the support center S (component data management device 7) is installed outside each of the factories F1 to F3, but the support center S (component data management device 7) may be installed inside the factories F1 to F3. Further, in the above production system 1 (component data management system), the component data management device 7 has a configuration including the comparison unit 31 and the storage processing unit 32, but the production management device 3 may have a configuration including the comparison unit 31 and the storage processing unit 32.

[0051] Also, in the above-described embodiment, the output unit 33 was described as an example of extracting information that matches the requests from the production management devices 3 of factories F1 to F3 from the database 21 and outputting (transmitting) it to the production management device 3 that is the request source. As another embodiment, the output unit 33 may transmit information to the production management device 3 based on a predetermined period or reaching a predetermined storage capacity. By using the predetermined period or the predetermined storage capacity as a criterion, the production management device 3 can automatically acquire information without a request command. In addition, since the information of the same parts is integrated, the data transmission capacity can be reduced compared to a state where no integration process is performed. Furthermore, by setting the information to be transmitted with a predetermined storage capacity so as not to exceed the upper limit of the data transmission capacity, the information can be appropriately sent to the production management device 3.

Industrial Applicability

[0052] The component data management method, component data management device, component data management program, and component data management system of the present invention have the effect of being able to efficiently accumulate component data and performance data in a database, and are useful in the field of mounting components on a substrate.

Explanation of Signs

[0053] 1 Production system (component data management system) 7 Component data management device F1~F3 Factories L1 Component mounting line (production line) M2, M3 Component mounting devices

Claims

1. A component data management method for managing component data in which operation parameters, which are operating conditions of a component mounting apparatus for mounting the component on a substrate, are associated with component information of the component, comprising: an acquisition step of acquiring at least the component data used in the component mounting apparatus and the performance data obtained when the component is mounted by the component mounting apparatus using the component data; a comparison step of comparing the component data stored in a database that stores the component data and the performance data associated with each other with the acquired component data; a storage step of storing the acquired component data and the acquired performance data in the database based on the result of the comparison. The component data management method includes these steps.

2. In the comparison step, when the acquired component data matches the stored component data, in the storage step, the acquired performance data is integrated with the stored performance data and stored in the database. The component data management method according to claim 1.

3. further including a totaling step of totaling the performance data while the component mounting apparatus mounts a component, wherein the acquisition step acquires the totaled performance data. The component data management method according to claim 1 or 2.

4. In the comparison step, in addition to the component data, at least one item among information for identifying the component mounting apparatus that uses the component data, the type of the component mounting apparatus, the production line on which the component mounting apparatus is installed, and the factory in which the component mounting apparatus is installed is also compared. The component data management method according to any one of claims 1 to 3.

5. The performance data includes at least one item among the period during which the component is mounted, the error rate when the component is mounted, the number of errors, and the actual number of times the component is picked up. The component data management method according to any one of claims 1 to 4.

6. A component data management apparatus for managing component data in which operation parameters, which are operating conditions of a component mounting apparatus for mounting the component on a substrate, are associated with component information of the component, comprising: an acquisition unit that acquires at least the component data used in the component mounting apparatus and the performance data obtained when the component is mounted by the component mounting apparatus using the component data; A comparison unit that compares the component data stored in a database that associates and stores the component data and the performance data with the acquired component data; A component data management device comprising: a storage processing unit that stores the acquired component data and the acquired performance data in the database based on the result of the comparison. **Claim 7** A component data management program for causing a computer to execute management of component data in which operation parameters, which are operating conditions of a component mounting device for mounting the component on a substrate, are associated with component information of the component, An acquisition step of acquiring at least the component data used in the component mounting device and the performance data obtained when the component is mounted by the component mounting device using the component data; A comparison step of comparing the component data stored in a database that associates and stores the component data and the performance data with the acquired component data; A component data management program including a storage step of storing the acquired component data and the acquired performance data in the database based on the result of the comparison. **Claim 8** A component data management system comprising a component mounting device for mounting a component on a substrate and a component data management device for managing component data in which operation parameters, which are operating conditions of the component mounting device, are associated with component information of the component, The component data management system includes a data collection unit that collects performance data obtained when the component is mounted by the component mounting device using the component data, The component data management device An acquisition unit that acquires at least the component data used in the component mounting device and the collected performance data; A comparison unit that compares the component data stored in a database that associates and stores the component data and the performance data with the acquired component data; A component data management system comprising a storage processing unit that stores the acquired component data and the acquired performance data in the database based on the result of the comparison.

Images