Parts data management method, parts data management device, parts data management program, and parts data management system

Abstract

To provide a component data management method capable of efficiently storing component data and performance 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 includes: an acquisition step of acquiring at least component data used by a component mounting unit and performance data obtained when a component is mounted by a component mounting unit using component data; a comparison step of comparing component data stored in a database that links and stores component data and performance data, and the acquired component data; and a storage step of, when the acquired component data matches the stored component data based on the comparison results, integrating the acquired performance data with the stored performance data and storing the integrated data in the database, and when not matches, newly storing the acquired component data and performance data in a database.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 that mounts components on a substrate.

Background Art

[0002] A component mounting device that mounts components on a substrate controls the component mounting operation based on a number of operation parameters including operation conditions related to component mounting on the substrate, component suction by a nozzle, and component imaging. 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 requested components selected 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, the present invention aims to provide a parts data management method, a parts data management device, a parts data management program, and a parts data management system that can efficiently store parts data and performance data in a database. [Means for solving the problem]

[0006] The present invention relates to a component data management method for managing component data, which involves linking component information of a component with operating parameters that are operating conditions for a component mounting device for mounting the component onto a substrate. The method includes: an acquisition step of acquiring at least component data used by the component mounting device and actual 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 component data stored in a database that stores the component data and the actual data in association; and a storage step of, based on the results of the comparison, integrating the acquired actual data with the stored actual data and storing it in the database if the acquired component data and the stored component data match, or newly storing the acquired component data and the actual data in the database if they do not match.

[0007] The component data management device of the present invention is a component data management device that manages component data in which operating parameters, which are the operating conditions of a component mounting device for mounting the component onto a circuit board, are linked to component information of the component, and comprises: an acquisition unit that acquires at least component data used by the component mounting device and actual 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 component data stored in a database that stores the component data and the actual data linked together; and a storage processing unit that, based on the result of the comparison, if the acquired component data and the stored component data match, integrates the acquired actual data with the stored actual data and stores it in the database, and if they do not match, newly stores the acquired component data and the acquired actual data in the database.

[0008] The component data management program of the present invention is a component data management program that causes a computer to perform management of component data, which associates component information of a component with operating parameters that are operating conditions of a component mounting device for mounting the component onto a circuit board, and includes: an acquisition step of acquiring at least component data used by the component mounting device and actual 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 component data stored in a database that stores the component data and the actual data in association; and a storage step of, based on the result of the comparison, integrating the acquired actual data with the stored actual data and storing it in the database if the acquired component data and the stored component data match, or newly storing the acquired component data and the acquired actual data in the database if they do not match.

[0009] The component data management system of the present invention comprises a component mounting apparatus for mounting components onto a substrate, and a component data management device for managing component data in which operating parameters, which are the operating conditions of the component mounting apparatus, are linked to component information of the components, wherein the component data management device comprises a data collection unit for collecting actual data obtained when the components are mounted by the component mounting apparatus using the component data, and the component data management device comprises an acquisition unit for acquiring at least the component data used by the component mounting apparatus and the collected actual data, a comparison unit for comparing the component data stored in a database that stores the component data and the actual data linked together with the acquired component data, and a storage processing unit that, based on the result of the comparison, integrates the acquired actual data with the stored actual data and stores it in the database if the acquired component data and the stored component data match, and stores the acquired component data and the acquired actual data in the database if they do not match. [Effects of the Invention]

[0010] According to the present invention, component data and performance data can be efficiently stored in a database. [Brief explanation of the drawing]

[0011] [Figure 1] Diagram illustrating the configuration of a production system according to one embodiment of the present invention. [Figure 2] Block diagram showing the configuration of a production system according to one embodiment of the present invention. [Figure 3] This diagram illustrates the data structure of component data used in a production system according to one embodiment of the present invention. [Figure 4] (a) An explanatory diagram showing an example of actual data stored in a production management device used in a production system according to one embodiment of the present invention. (b) An explanatory diagram showing an example of actual data stored in a parts data management device. [Figure 5] Flowchart of a component data management method according to one embodiment of the present invention [Modes for carrying out the invention]

[0012] An embodiment of the present invention will be described in detail below with reference to the drawings. The configurations, shapes, etc. described below are illustrative examples for illustrative purposes and can be modified as appropriate according to the specifications of the production system (parts data management system), parts mounting line (production line), parts mounting equipment, and parts data management system. In the following, all corresponding elements are denoted by the same reference numerals in all drawings, and redundant explanations are omitted.

[0013] First, let's explain the configuration of Production System 1 with reference to Figure 1. Production System 1 consists of customer factories F1 to F3 and a support center S located away from factories F1 to F3 to support the customer's production activities. Each factory F1 to F3 is equipped with a component mounting line that produces mounted circuit boards as a production line for producing manufactured goods. Hereafter, factory F1 will be referred to as "Factory 1 F1", factory F2 as "Factory 2 F2", and factory F3 as "Factory 3 F3". In Figure 1, we will explain the configuration of factories F1 to F3 using Factory 1 F1 as an example.

[0014] In Figure 1, the first factory F1 is equipped with one component mounting line L1, which consists of a printing machine M1 and multiple component mounting machines M2, M3, and other production equipment connected together. The component mounting line L1 has the function of producing mounted circuit boards by sequentially mounting components onto the boards using the printing machine M1 and component mounting machines M2, M3. Note that the first factory F1 does not need to have just one component mounting line L1; there may be two or more. Also, the component mounting machines M2, M3 that make up the component mounting line L1 do not need to be two; there may be one or three or more.

[0015] Each production device within Factory F1 is connected to an internal 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 the function of creating the data and parameters necessary for the operation of the production devices on component mounting line L1 and transmitting them to each production device. In addition, data such as the operating status and work history of each production device is transmitted to the production management device 3 from each production device. Furthermore, the production management device 3 has the function of creating component data, production data, etc., used by the production devices on component mounting line L1. Note that Factory F1 may also be configured to have a line management device for each component mounting line L1, in addition to the production management device 3, to manage the production of mounted boards.

[0016] In Figure 1, a parts data management device 7 is installed in the support center S. The production management devices 3 in multiple factories F1 to F3 are equipped with external communication units 5. The parts data management device 7 in the support center S is also equipped with an external communication unit 8. The external communication units 5 and 8 are connected to an off-site communication network 6, such as the internet or a mobile communication line. This configuration allows the production management devices 3 and the parts data management device 7 to exchange information via the off-site communication network 6. The parts data management device 7 acquires production performance information and parts data from the production management devices 3 in each factory F1 to F3 and stores it in a database. The parts data management device 7 also has the function of extracting and transmitting (outputting) information from the database in response to requests from the production management devices 3.

[0017] Furthermore, the production management device 3 and the parts data management device 7 are not limited to a configuration in which they directly exchange information via the external communication network 6; they may also exchange information via the cloud. That is, information transmitted from each device may be stored in the cloud, and the information may be sent from the cloud to each device upon request. Alternatively, information may be sent and received using communication tools such as email or data communication lines.

[0018] Next, referring 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] Based on the operation parameters included in the component data set for each component to be mounted on the substrate, the component mounting devices M2 and M3 take out the components supplied by the feeder with a nozzle of the mounting head by vacuum suction, image the state of the component held by the nozzle with a component recognition camera, and mount it at the mounting angle designated for the mounting position on the substrate. The component mounting devices M2 and M3 are equipped 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, referring 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. In addition, 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] An internal communication unit 4, an external communication unit 5, an input unit 9, and a display unit 10 are connected to the production management device 3 installed in the first factory F1. The production management device 3 includes a production management storage unit 11, a data collection unit 15, a totaling unit 16, and a control unit (not shown). The production management storage unit 11 is a storage device such as a semiconductor memory or a hard disk drive, and stores a production library 12, a component library 13, performance data 14, and the like.

[0022] The input unit 9 is an input device such as a keyboard, touch panel, or mouse, and is used for inputting operation commands and data. The display unit 10 is a display device such as an LCD panel, which displays various data stored in the production management storage unit 11, as well as various information such as operation screens and input screens for operations performed by the input unit 9. The control unit is, for example, a CPU (Central Processing Unit), and controls the entire production management system 3.

[0023] In Figure 2, the production library 12 stores production data used for the production of mounted boards by component mounting machines M2 and M3, categorized by the production model name of the mounted board. The production data includes the component name that identifies the component to be mounted on the board, the component code that associates the component with component data in component library 13, the mounting position and angle of the component on the board, the component arrangement indicating the position of the feeder that supplies the component in component mounting machines M2 and M3, and the nozzle arrangement indicating the position of the nozzle that picks up the component in the mounting head. The component library 13 stores multiple component data, each with operating parameters linked to the component information. The component data is associated with the production data in production library 12 by a component data code.

[0024] Referring to Figure 3, an example of part data 17 included in the part library 13 will be explained. The part data 17 is associated with production data by the "part n" (part data code) included in the part data 17 and the part data code of the production data included in the production library 12. In this example, the part library 13 stores part data 17 for multiple types of parts, each having part data codes n=1, 2, 3, etc. The part data 17 defines part information 18 and operating parameters 19 as major classification items.

[0025] Part information 18 is information that indicates attributes specific to the part in question. Here, "Part Name" 18a, "Shape" 18b, "Size" 18c, and "Part Parameters" 18d are given as examples of major classification items. "Part Name" 18a is part number information used to identify the part in question, and the "part number" assigned by the part manufacturer or the company for management purposes is defined as a minor classification item. "Shape" 18b is information regarding the shape of the part in question, and the "shape" that indicates the external shape of the part in shape classifications such as rectangle or cylinder, and information that identifies drawings and image information showing the shape of the part are defined as minor classification items.

[0026] The "Size" 18c specifies sub-categories such as "External Dimensions" indicating the size of the part, and "Electrode Position" indicating the number and position (spacing) of connection electrodes (leads) formed on the part. The "Part Parameters" 18d are attribute information of the part, and specify sub-categories such as "Part Type" indicating the type of part, "Polarity" indicating whether or not there is directionality in the external shape of the part, "Polarity Mark" indicating the shape of the mark attached to the part if polarity is present, and "Mark Position" indicating the position of the mark if a polarity mark is present. Thus, part information 18 includes at least one of the following items: part dimensions (size 18c), part number information (part name 18a), number of leads, lead spacing information (size 18c), and image information (shape 18b).

[0027] In Figure 3, the operating parameters 19 are control parameters (operating conditions) used to control the component mounting devices M2 and M3, which are located on the component mounting line L1, when performing component mounting work on the components specified in the component data 17. Here, the following are examples of subcategory items: "Nozzle setting" 19a, "Speed ​​parameter" 19b, "Recognition" 19c, "Adsorption" 19d, and "Mounting" 19e.

[0028] "Nozzle setting" 19a is data related to the suction nozzle used to hold the component by suction, and a subcategory item, "Nozzle," is defined to specify the type of suction nozzle that can be selected. In addition to the type, the data for "Nozzle" may also include the aperture diameter, identifier, etc. "Speed ​​parameter" 19b is a control parameter related to the movement speed of the suction nozzle during the operation of picking up the component by the suction nozzle and attaching it to the substrate. These control parameters include, as subcategory items, "Suction speed" and "Suction holding time" when suctioning and holding the component, and "Attachment speed" and "Attachment holding time" when attaching the held component to the substrate.

[0029] In Figure 3, "recognition" 19c is a parameter related to the execution of a recognition process in which a part removed from the part supply unit by a suction nozzle is imaged and recognized by a part recognition camera. These parameters include, as a subcategory item, "camera type" which specifies the type of camera used for imaging, "illumination mode" which indicates the mode of illumination used during imaging, and "recognition speed" for recognizing the image acquired through imaging.

[0030] "Adsorption" 19d are control parameters related to the adsorption operation when a component is picked up from the component supply unit by the adsorption nozzle. These control parameters include, as subcategories, "Adsorption Position X" and "Adsorption Position Y," which indicate the adsorption position offset when the adsorption nozzle lands on the component. "Mounting" 19e are control parameters related to the mounting operation when the mounting head, which holds the component by adsorption nozzle, is moved to the substrate, and the adsorption nozzle is made to move up and down to mount the component on the substrate. These control parameters include, as subcategories, "Mounting Load," which is the load applied when the adsorption nozzle is lowered and the component lands on the substrate.

[0031] In Figure 3, the operating parameters 19 may be changed even if the "product name" 18a is the same, i.e., the component information 18 is the same, due to changes in the type of component mounting equipment M2, M3 used to mount the component onto the board, the material of the board, the electrodes on the board, etc., or to improve mounting quality or mounting error rate. When the operating parameters 19 of the component are changed, component data 17 is created (updated) that associates the changed operating parameters 19 without changing the component information 18. At this time, the operating parameters 19 before modification are distinguished from the modified operating parameters 19 by assigning a new code to "component n" (component data code) in the component data 17.

[0032] Thus, the component data 17 is linked to component information 18, which indicates the unique attributes of the component, and to operating parameters 19, which are the operating conditions for the component mounting devices M2 and M3 to mount the component onto the substrate. The component data 17 from the component library 13 is transmitted to the component mounting devices M2 and M3 on the component mounting line L1 together with the production data from the production library 12, and is used for the production of mounted substrates in the component mounting devices M2 and M3.

[0033] In Figure 2, the data acquisition unit 15 collects data on component mounting operations from the production equipment (printing device M1, component mounting devices M2, M3) of the component mounting line L1 installed in the first factory F1. The component mounting operation data includes information such as the production start date and time, production end date and time, number of units produced, number of times components were picked up, number of times components were mounted, number of work errors, error rate (frequency), and the number and details of operational errors.

[0034] The aggregation unit 16 aggregates, based on the performance information collected by the data collection unit 15, the error rate, number of errors, number of components picked up, and number of components mounted on the board for each component name mounted on the board during the aggregation period. Furthermore, the aggregation unit 16 associates the aggregated information with information identifying the component mounting devices M2 and M3 that performed the component mounting work, and stores it in the production management storage unit 11 as performance data 14. In other words, the performance data 14 obtained when components are mounted by component mounting devices M2 and M3 using component data 17 includes the period during which components were mounted, the error rate during component mounting, the number of errors, the number of components picked up, and the number of components mounted.

[0035] Here, with reference to Figure 4(a), an example of the performance data 14 compiled by the aggregation unit 16 will be explained. The performance data 14 is created for each part name 40 of a part. In addition, the performance data 14 is created for each part mounting device M2, M3, or for each type of part mounting device M2, M3, or for each part mounting line L1 (production line). The performance data 14 includes the date 41, part data code 42, number of suction errors 43, number of mounting errors 44, and total number of suctions 45. In this example, for parts with part name 40 "D11", the aggregation unit 16 aggregates and stores the number of suction errors 43, the number of mounting errors 44, and the total number of suctions 45 for one day for each part data code 42 (part n) of the part data 17. Note that aggregation does not need to be on a daily basis; hourly units, production model units, etc., can be set as appropriate.

[0036] The total number of suction attempts (45) is the total number of times the nozzle attempted to pick up a component with part name 40 "D11" to mount it onto the substrate during the aggregation period. The number of suction misses (43) is the total number of times the nozzle failed to pick up a component with part name 40 "D11" during the aggregation period. The number of mounting errors (44) is the total number of times (number) that a component with part name 40 "D11" mounted onto the substrate was in a defective state during the aggregation period. For example, on the date 41, "January 3rd", the nozzle picked up a component with part name 40 "D11" 5000 times using part data 17 with part data code 42 "111", resulting in 15 suction misses and 1 mounting error. Also on the date 41, "January 3rd", the nozzle picked up a component with part name 40 "D11" 20000 times using part data 17 with part data code 42 "112".

[0037] In Figure 2, the parts data management device 7 installed at the support center S has the function of collecting and managing parts data 17 and performance data 14 used at customer factories F1 to F3. An external communication unit 8 and a storage device 20 are connected to the parts data management device 7. The storage device 20 is, for example, a semiconductor memory or a hard disk drive. The storage device 20 has a database 21 that stores information such as parts data 17 and performance data 14 acquired from multiple factories F1 to F3. The database 21 may also include data prepared in advance by an EDA (Electronic Design Automation) vendor.

[0038] The parts 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). Each information processing device may be composed of independent hardware assets, or it may be composed of a common CPU and programs for each information processing device. The control unit is, for example, a CPU (Central Processing Unit) and controls the entire parts data management device 7. Furthermore, the parts data management device 7 does not need to be composed of a single computer, but may be composed of multiple devices. For example, all or part of the storage device 20 and the information processing devices may be stored in the cloud via a server.

[0039] In Figure 2, the acquisition unit 30 acquires component data 17 used by component mounting devices M2 and M3 from multiple factories F1 to F3 via the external communication unit 8, and corresponding performance data 14. The data acquisition by the acquisition unit 30 is performed, for example, once a day at a predetermined time. The comparison unit 31 compares the acquired component data 17 with the component data 21a stored in the database 21. Based on the comparison results by the comparison unit 31, the storage processing unit 32 performs storage processing to store the acquired component data 17 and the acquired performance data 14 in the database 21.

[0040] Specifically, if the comparison unit 31 determines that the acquired part data 17 and the stored part data 21a have matching part information 18 and operation parameters 19, 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). If the comparison unit 31 determines that the acquired part data 17 and the stored part data 17 do not have matching parts, the storage processing unit 32 stores the acquired part data 17 as new part data 21a and the acquired performance data 14 as new performance data 21b in the database 21 (new storage).

[0041] The comparison unit 31 also compares the part information 18 and operating parameters 19 of the part data 17, as well as at least one item of information identifying the part mounting devices M2 and M3 that used the part data 17, the type of part mounting devices M2 and M3, the production line (part mounting line L1) where the part mounting devices M2 and M3 are installed, and the factories F1 to F3 where the part mounting devices M2 and M3 are installed, to determine whether they match. In other words, it integrates information on the same parts mounted by the same part mounting devices M2 and M3 and stores it in the database 21.

[0042] Referring to Figure 4(b), an example of the performance data 21b integrated by the storage processing unit 32 will be explained. Here, we will explain an example in which the performance data 14 for January 7th, obtained from factory F1 on the morning of January 8th as shown in Figure 4(a), is integrated with the performance data 21b stored in database 21. In other words, the performance data 21b stored in database 21 before integration was created based on the performance data 14 up to January 6th. The storage processing unit 32 integrates one week's worth of performance data 14 as performance data 21b. That is, in this example, it shows the state after integrating the parts data 17 for the first week of January (January 1st to January 7th). Note that integration does not need to be on a weekly basis and can be set as appropriate.

[0043] In Figure 4(b), date 41 is the final date on which the performance data 14 for the part with part name 40 "D11" was integrated. In this example, the sum of the number of suction errors 43, the number of mounting errors 44, and the total number of suctions 45 for January 3rd to January 5th, using part data 17 with part data code 42 "112", is stored in the column for date 41 "January 5th". Also, the sum of the number of suction errors 43, the number of mounting errors 44, and the total number of suctions 45 for January 1st to January 3rd and January 6th to January 7th, using part data 17 with part data code 42 "111", is stored in the column for date 41 "January 7th".

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

[0045] Next, following the flow in Figure 5, we will explain the component data management method (data management program) for managing component data 17. First, the data acquisition unit 15 of the production management device 3 in factories F1 to F3 collects the actual component mounting work data from the component mounting devices M2 and M3 of the component mounting line L1 (production line) installed in factories F1 to F3 (ST1: data acquisition process). Then, the aggregation unit 16 aggregates the actual component mounting work data 14 from the collected data while the component mounting devices M2 and M3 are mounting components (ST2: aggregation process).

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

[0047] In Figure 5, if a "match" is determined in the comparison step (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 step). If a "mismatch" is determined in the comparison step (ST4), the storage processing unit 32 stores the acquired part data 17 as new part data 21a and the acquired performance data 14 as new performance data 21b in the database 21 (new storage) (ST6: new storage step).

[0048] In other words, the integrated storage process (ST5) and the new storage process (ST6) are storage processes that store the acquired part data 17 and the acquired performance data 14 in the database 21 based on the comparison results in the comparison process (ST4). If the acquired part data 17 and the stored part data 21a match in the comparison process (ST4), the acquired performance data 14 is integrated into the stored performance data 21b and stored in the database 21 in the storage process (ST5). If they do not match, the acquired performance data 14 is stored in the database 21 as new performance data 21b in the storage process (ST6). This allows for the efficient accumulation of part data 17 and performance data 14 in the database 21.

[0049] As described above, the component data management device 7 for managing component data 17 in this embodiment includes an acquisition unit 30 that acquires at least component data 17 used by component mounting devices M2 and M3, and actual data 14 obtained when components are mounted by component mounting devices M2 and M3 using component data 17; a comparison unit 31 that compares component data 21a stored in a database 21 that stores component data 17 and actual data 14 linked together with the acquired component data 17; and a storage processing unit 32 that stores the acquired component data 17 and acquired actual data 14 in the database 21 based on the comparison result. This makes it possible to efficiently accumulate component data 17 and actual data 14 in the database 21.

[0050] In the above embodiment of production system 1 (parts data management system), the support center S (parts data management device 7) is installed outside each factory F1 to F3, but the support center S (parts data management device 7) may also be installed inside factories F1 to F3. Furthermore, in the above embodiment of production system 1 (parts data management system), the parts data management device 7 is configured to include a comparison unit 31 and a storage processing unit 32, but the production management device 3 may also be configured to include a comparison unit 31 and a storage processing unit 32.

[0051] Furthermore, in the above embodiment, the output unit 33 was described as extracting information from the database 21 that matches the requests from the production management devices 3 of factories F1 to F3 and outputting (transmitting) it to the requesting production management device 3. In other embodiments, the output unit 33 may transmit information to the production management device 3 based on a predetermined period or when a predetermined storage capacity is reached. By using a predetermined period or predetermined storage capacity as a guideline, the production management device 3 can automatically acquire information without a request command. In addition, because information for the same parts is integrated, the data transmission capacity can be reduced compared to when integration processing is not performed. Furthermore, by setting the predetermined storage capacity so that the information to be transmitted does not exceed the upper limit of the data transmission capacity, 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 efficiently accumulating component data and performance data in a database, and are useful in the field of mounting components on a circuit board. [Explanation of Symbols]

[0053] 1. Production System (Parts Data Management System) 7. Parts Data Management Device F1-F3 Factory L1 Component mounting line (production line) M2, M3 component mounting equipment

Claims

1. A component data management method for managing component data, which associates component information of a component with operating parameters that are the operating conditions of a component mounting device for mounting the component onto a circuit board, An acquisition step of acquiring at least component data used by the component mounting device and actual data obtained when the component is mounted by the component mounting device using the component data, A comparison step involves comparing the part data stored in a database that links the part data and the performance data, with the acquired part data. A parts data management method, which includes a storage step of, if the acquired parts data and the stored parts data match based on the results of the comparison, integrating the acquired actual data with the stored actual data and storing it in the database, and if they do not match, newly storing the acquired parts data and the actual data in the database.

2. The process further includes a data aggregation step for aggregating the performance data while the component mounting device is mounting components, The component data management method according to claim 1, wherein the acquisition step is to acquire the aggregated performance data.

3. The part data management method according to claim 1 or 2, wherein in the comparison step, in addition to the part data, at least one item of information identifying the part mounting device that uses the part data, the type of part mounting device, the production line on which the part mounting device is installed, and the factory on which the part mounting device is installed is also compared.

4. The component data management method according to any one of claims 1 to 3, wherein the performance data includes at least one item: the period during which the component was mounted, the error rate when mounting the component, the number of errors, and the number of components that were actually attached.

5. A component data management device that manages component data by linking the component information of a component with operating parameters, which are the operating conditions of a component mounting device for mounting the component onto a circuit board, An acquisition unit that acquires at least component data used by the component mounting device and actual data obtained when the component is mounted by the component mounting device using the component data, A comparison unit compares the part data stored in a database that links the part data and the performance data with the acquired part data. A parts data management device comprising: a storage processing unit that, based on the results of the comparison, if the acquired parts data matches the stored parts data, integrates the acquired performance data with the stored performance data and stores it in the database; and if they do not match, newly stores the acquired parts data and the acquired performance data in the database.

6. A component data management program that uses a computer to manage component data by linking the component information of a component with operating parameters that are the operating conditions of a component mounting device for mounting the component onto a circuit board, An acquisition step of acquiring at least component data used by the component mounting device and actual data obtained when the component is mounted by the component mounting device using the component data, A comparison step involves comparing the part data stored in a database that links the part data and the performance data, with the acquired part data. A parts data management program comprising: a storage step of, if the acquired parts data and the stored parts data match based on the results of the comparison, integrating the acquired actual data with the stored actual data and storing it in the database; and if they do not match, newly storing the acquired parts data and the acquired actual data in the database.

7. A component data management system comprising a component mounting device for mounting components onto a circuit board, and a component data management device for managing component data that links component information of the component with operating parameters which are the operating conditions of the component mounting device, The system includes a data collection unit that collects actual data obtained when the component is mounted using the component mounting device with the component data. The aforementioned parts data management device is An acquisition unit that acquires at least the component data used in the component mounting device and the collected performance data, A comparison unit compares the part data stored in a database that links the part data and the performance data with the acquired part data. A parts data management system comprising: a storage processing unit that, based on the results of the comparison, if the acquired parts data matches the stored parts data, integrates the acquired performance data with the stored performance data and stores it in the database; and if they do not match, newly stores the acquired parts data and the acquired performance data in the database.

Images