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 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 board. [Background technology]

[0002] A component mounting device that mounts components on a board controls the component mounting operation based on a large number of operating parameters, including operating conditions related to component mounting on the board, component pickup by a nozzle, and component photography. Appropriate values are set for each component as component data linked to component information, including information such as the component shape. Patent Document 1 discloses a system that registers component data and usage records, such as the number of uses and the number of products in which the component is used, in a database, and extracts selected components from the database based on a list of requested selection components. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-87276 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with conventional technologies including Patent Document 1, the amount of parts data and usage history data acquired daily from multiple factories and production lines becomes enormous. Furthermore, if 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, so there is room for further improvement in order to efficiently store parts data and usage history data in the database.

[0005] SUMMARY OF THE INVENTION It is therefore an object of the present invention 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 component data management method of the present invention is a component data management method for managing component data in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, and includes the following steps: an acquisition step of acquiring at least component data used by the component mounting device and 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 component data stored in a database that stores the component data and the performance data in a linked manner; and a storage step of integrating the acquired performance data with the stored performance data and storing them in the database if the acquired component data and the stored component data match based on the result of the comparison; and if they do not match, newly storing the acquired component data and the performance data in the database.

[0007] The component data management device of the present invention is a component data management device that manages component data in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, and includes an acquisition unit that acquires at least component data used by the component mounting device and 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 component data stored in a database that stores the component data and the performance data in a linked manner, and a storage processing unit that, based on the result of the comparison, if the acquired component data matches the stored component data, integrates the acquired performance data with the stored performance data and stores them in the database, and if they do not match, newly stores the acquired component data and the acquired performance 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 manage component data in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, and includes the following steps: an acquisition step of acquiring at least component data used by the component mounting device and 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 component data stored in a database that stores the component data and the performance data in a linked manner; and a storage step of integrating the acquired performance data with the stored performance data and storing them in the database if the acquired component data and the stored component data match based on the result of the comparison; and if they do not match, newly storing the acquired component data and the acquired performance data in the database.

[0009] The component data management system of the present invention is a component data management system comprising: a component mounting device that mounts components on a board; and a component data management device that manages component data in which component information of the components is linked to operating parameters that are operating conditions of the component mounting device, and the component data management system comprises a data collection unit that collects performance data obtained when the components are mounted by the component mounting device using the component data, and the component data management device comprises: an acquisition unit that acquires at least the component data used by the component mounting device and the collected performance data; a comparison unit that compares the acquired component data with component data stored in a database that stores the component data in a linked relationship with the performance data, and a storage processing unit that, based on the result of the comparison, if the acquired component data matches the stored component data, integrates the acquired performance data with the stored performance data and stores them in the database; and if they do not match, newly stores the acquired component data and the acquired performance data in the database. [Effects of the Invention]

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

[0011] [Figure 1] FIG. 1 is a diagram illustrating the configuration of a production system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a block diagram showing the configuration of a production system according to an embodiment of the present invention. [Figure 3] FIG. 2 is an explanatory diagram showing the data structure of parts data used in the production system according to an embodiment of the present invention; [Figure 4] FIG. 1A is an explanatory diagram showing an example of performance data stored in a production management device used in a production system according to an embodiment of the present invention; FIG. 1B is an explanatory diagram showing an example of performance data stored in a parts data management device; [Figure 5] 1 is a flow diagram of a part data management method according to an embodiment of the present invention; DETAILED DESCRIPTION OF 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 examples for the purpose of explanation, and can be modified as appropriate depending on 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 drawings will be given the same reference numerals, and duplicated explanations will be omitted.

[0013] First, the configuration of production system 1 will be described with reference to Figure 1. Production system 1 is composed of customer factories F1 to F3 and a support center S that is located away from factories F1 to F3 and supports customer production activities. Each of factories F1 to F3 is equipped with a component mounting line that produces mounted boards 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 Figure 1, the configuration of factories F1 to F3 will be described using first factory F1 as an example.

[0014] In FIG. 1, the first factory F1 is equipped with one component mounting line L1, which is configured by connecting production devices such as a printing device M1 and multiple component mounting devices M2 and M3. The component mounting line L1 has the function of producing mounted boards by sequentially mounting components onto boards using the printing device M1 and the component mounting devices M2 and M3. The component mounting line L1 installed in the first factory F1 does not need to be one, but may be two or more. Furthermore, the component mounting devices M2 and M3 that make up the component mounting line L1 do not need to be two, but may be one, or three or more.

[0015] Each production device in the first 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 data and parameters necessary for the operation of the production devices equipped on the component mounting line L1 and transmitting them to each production device. In addition, each production device transmits data such as the operating status and work history of each production device to the production management device 3. The production management device 3 also has the function of creating component data, production data, etc. used by the production devices on the component mounting line L1. In addition to the production management device 3, the first factory F1 may be configured to include a line management device for managing the production of mounted boards for each component mounting line L1.

[0016] In FIG. 1, a parts data management device 7 is installed in a support center S. The production management devices 3 of the multiple factories F1 to F3 are each equipped with an external communication unit 5. The parts data management device 7 of 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 device 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 performance information and parts data of the production devices from the production management devices 3 of each of the factories F1 to F3 and stores the information in a database. The parts data management device 7 also has the function of extracting information from the database and transmitting (outputting) it in response to a request from the production management device 3.

[0017] 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 off-premise communication network 6, and may exchange information via the cloud. That is, information sent from each device may be stored in the cloud, and the information may be sent from the cloud to each device upon request. Information may also be sent and received using communication tools that utilize email or data communication lines.

[0018] Next, the component mounting line L1 will be described with reference to Figure 1. The printing device M1 is a production device that performs a solder printing operation, which screen-prints cream solder for joining components onto a board. The component mounting devices M2 and M3 are production devices that perform a component mounting operation, which attaches components to the board after solder printing.

[0019] Based on the operation parameters included in the component data set for each component to be mounted on the board, component mounting devices M2 and M3 use a nozzle on the mounting head to vacuum-suck components supplied by the feeder, capture images of the components held by the nozzle with a component recognition camera, and mount the components at the specified mounting angle on the board at the mounting position. Component mounting devices M2 and M3 are equipped with multiple sensors to monitor for operational mistakes and operational errors during component mounting, such as the suction operation in which the nozzle picks up the component and the component recognition operation in which the component recognition camera captures and recognizes the picked-up component.

[0020] Next, the configuration of the production system 1 (component data management system) equipped with the production management device 3 and the component data management device 7 will be described with reference to Fig. 2. Here, the configuration will be mainly explained regarding the function of collecting and managing component data and performance data used by component mounting devices M2 and M3, among the multiple functions equipped in the production management device 3 and the component data management device 7. Furthermore, the production management devices 3 installed in 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 a production management device 3 installed in the first factory F1. The production management device 3 is equipped with a production management memory unit 11, a data collection unit 15, a counting 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, etc.

[0022] The input unit 9 is an input device such as a keyboard, touch panel, or mouse, and is used to input operation commands and data. The display unit 10 is a display device such as a liquid crystal panel, and displays various data stored in the production management storage unit 11, as well as various information such as an operation screen and input screen for operation 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] 2, production library 12 stores production data used in the production of mounted boards by component mounting devices M2 and M3 for each production model name of the mounted board. The production data includes component names that identify the components to be mounted on the board, component codes that associate the components with component data in component library 13, the mounting position and mounting angle of the components on the board, component layout indicating the position of the feeder that supplies the components in component mounting devices M2 and M3, and nozzle layout indicating the position of the nozzle that picks up the components in the mounting head. Component library 13 stores multiple component data in which operating parameters are linked to component information. The component data is associated with the production data in production library 12 by component data codes.

[0024] An example of part data 17 contained in part library 13 will now be described with reference to Fig. 3. The part data 17 is associated with production data by "part n" (part data code) contained in the part data 17 and the part data code of the production data contained in production library 12. In this example, part library 13 stores part data 17 of multiple types of parts having part data codes of n = 1, 2, 3, .... The part data 17 defines part information 18 and operation parameters 19 as major classification items.

[0025] Part information 18 is information that indicates attributes unique to the part. Here, "product name" 18a, "shape" 18b, "size" 18c, and "part parameters" 18d are exemplified as medium-category items. "Product name" 18a is product number information for identifying the part, and the "product number" assigned by the part manufacturer or the company for management purposes is defined as a minor category. "Shape" 18b is information about the shape of the part, and the minor categories include "shape" that indicates the external shape of the part using a shape classification such as rectangular or cylindrical, and information that specifies a drawing or image information showing the shape of the part.

[0026] "Size" 18c includes subcategories such as "external dimensions" indicating the size of the component and "electrode position" indicating the number and position (spacing) of connection electrodes (leads) formed on the component. "Component parameters" 18d are attribute information of the component, and includes subcategories such as "component type" indicating the type of component, "polarity" indicating whether the component has a directional characteristic in its external shape, "polarity mark" indicating the shape of the mark affixed to the component if polarity is present, and "mark position" indicating the position of the mark if polarity is present. Thus, component information 18 includes at least one of the following items: component dimensions (size 18c), part number information (product name 18a), lead number information, lead spacing information (size 18c), and image information (shape 18b).

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

[0028] "Nozzle settings" 19a is data related to the suction nozzle used to pick up and hold the component, and a subcategory item, "nozzle," is defined to specify the type of suction nozzle that can be selected. In addition to type, "nozzle" data may also include the opening diameter, identifier, etc. "Speed parameters" 19b is a control parameter related to the movement speed of the suction nozzle in the work operation of picking up the component with the suction nozzle and placing it on the board. These control parameters include, as subcategory items, "pickup speed" and "suction holding time" when picking up and holding the component, and "placement speed" and "placement holding time" when placing the held component on the board.

[0029] 3, "recognition" 19c is a parameter related to the execution of a recognition process in which a component picked up by a suction nozzle from a component supply unit is imaged and recognized by a component recognition camera. These parameters include, as subcategory items, a "camera type" that specifies the type of camera used for image capture, a "lighting mode" that indicates the lighting mode used for image capture, and a "recognition speed" for recognizing the image acquired by image capture.

[0030] "Pickup" 19d is a control parameter related to the pickup operation when a component is picked up from the component supply unit by a pickup nozzle. These control parameters include sub-categories such as "pickup position X" and "pickup position Y" that indicate the pickup position offset when the pickup nozzle lands on the component. "Placement" 19e is a control parameter related to the placement operation in which the mounting head, which picks up and holds the component by the pickup nozzle, is moved to the board and the pickup nozzle is raised and lowered to place the component on the board. These control parameters include sub-categories such as "placement load," which is the load that presses the component against the board when the pickup nozzle is lowered to place the component on the board.

[0031] 3, even if the "product name" 18a is the same, i.e., the component information 18 is the same, the operating parameters 19 may be changed due to changes in the type of component mounting device M2, M3 used to mount the component on the board, the material of the board, the electrodes on the board, or to improve the mounting quality or mounting error rate. When the operating parameters 19 of the component are changed, the component information 18 is not changed, and component data 17 linked to the changed operating parameters 19 is created (updated). At this time, a new code is assigned to "component n" (component data code) in the component data 17 to distinguish it from the operating parameters 19 before the correction.

[0032] In this way, component data 17 is linked to component information 18 indicating the unique attributes of the component and operation parameters 19 that are operation conditions for component mounting devices M2, M3 to mount the component on a board. Component data 17 in component library 13 is transmitted to component mounting devices M2, M3 on component mounting line L1 together with production data in production library 12, and is used in the production of mounted boards by component mounting devices M2, M3.

[0033] 2, the data collection unit 15 collects component mounting work results from the production devices (printing device M1, component mounting devices M2 and M3) on component mounting line L1 installed in first factory F1. The component mounting work results include information such as the production start date and time, production end date and time, number of components picked up, number of components placed, number of work errors, error rate (frequency), number of operational errors and their contents, etc.

[0034] Based on the performance information collected by data collection unit 15, tallying unit 16 tally the error rate, number of errors, number of component pickups, number of component mountings on boards, and the like for each component name of the components mounted on the board during the tallying period. Furthermore, tallying unit 16 associates the tallying information with information identifying component mounting devices M2 and M3 that performed the component mounting work, and stores the associated information as performance data 14 in production management storage unit 11. That is, performance data 14 obtained when components are mounted by component mounting devices M2 and M3 using component data 17 includes the period during which the components were mounted, the error rate when mounting the components, the number of errors, the number of component pickups, the number of component mountings, and the like.

[0035] 4(a), an example of performance data 14 compiled by the compilation unit 16 will be described. Performance data 14 is created for each component name 40. Furthermore, performance data 14 is created for each component mounting device M2, M3, or for each type of component mounting device M2, M3, and for each component mounting line L1 (production line). Performance data 14 includes date 41, component data code 42, number of pickup errors 43, number of placement errors 44, and total number of pickups 45. In this example, the compilation unit 16 compiles and stores the number of pickup errors 43, number of placement errors 44, and total number of pickups 45 for one day for each component data code 42 (component n) in component data 17 for a component with component name 40 "D11." Note that compilation does not need to be done on a daily basis; it can be done by hourly or production model, as appropriate.

[0036] The total number of pickups 45 is the total number of times during the collection period that the nozzle picked up a component with the component name 40 "D11" to mount it on a board. The number of pickup errors 43 is the total number of times during the collection period that the nozzle was unable to pick up a component with the component name 40 "D11". The number of placement errors 44 is the total number of times (number of parts) that were placed on a board with the component name 40 "D11" and were in poor condition during the collection period. For example, on date 41 (January 3), a component with the component name 40 "D11" was picked up 5,000 times using component data 17 with the component data code 42 "111", with 15 pickup errors and one placement error. Also, on date 41 (January 3), a component with the component name 40 "D11" was picked up 20,000 times using component data 17 with the component data code 42 "112".

[0037] 2, a parts data management device 7 installed in a support center S has a function of collecting and managing parts data 17 and performance data 14 used in 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 includes a database 21 that stores information such as the parts data 17 and performance data 14 acquired from the 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 configured with independent hardware assets, or may be configured with a common CPU and programs for each information processing. 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 configured with a single computer, but may be configured with multiple 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] 2, an acquisition unit 30 acquires component data 17 used by component mounting devices M2, M3 and performance data 14 corresponding to the component data 17 from multiple factories F1 to F3 via an external communication unit 8. The acquisition of data by the acquisition unit 30 is performed, for example, once a day at a predetermined time. A comparison unit 31 compares component data 21a stored in a database 21 with the acquired component data 17. A storage processing unit 32 executes a storage process to store the acquired component data 17 and the acquired performance data 14 in the database 21 based on the comparison result by the comparison unit 31.

[0040] Specifically, when the comparison unit 31 determines that the acquired component data 17 matches the component information 18 and the operation parameters 19 of the stored component data 21a, the storage processing unit 32 integrates the acquired performance data 14 with the stored performance data 21b and stores (integrated and stored) them in the database 21. 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 stores (newly 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.

[0041] Note that the comparison unit 31 compares the component information 18 and operation parameters 19 of the component data 17, as well as at least one of information specifying the component mounting devices M2 and M3 that used the component data 17, the types of the component mounting devices M2 and M3, the production line (component mounting line L1) on which the component mounting devices M2 and M3 are installed, and the factories F1 to F3 in which the component mounting devices M2 and M3 are installed, to determine whether or not they match. That is, the information on the same components mounted by the same component mounting devices M2 and M3 is integrated and stored in the database 21.

[0042] An example of performance data 21b integrated by the storage processing unit 32 will now be described with reference to FIG. 4(b). Here, an example will be described in which performance data 14 for January 7, acquired from factory F1 on the morning of January 8, as shown in FIG. 4(a), is integrated with performance data 21b stored in database 21. That is, performance data 21b stored in database 21 before integration was created based on performance data 14 up to January 6. The storage processing unit 32 integrates one week's worth of performance data 14 as performance data 21b. That is, this example shows a state in which parts data 17 for the first week of January (January 1 to January 7) have been integrated. Note that integration does not have to be on a weekly basis and can be set as appropriate.

[0043] In FIG. 4(b), date 41 is the latest date when performance data 14 for a component with component name 40 "D11" was integrated. In this example, the totals of the number of pickup errors 43, the number of placement errors 44, and the total number of pickups 45 from January 3rd to January 5th, when component data 17 with component data code 42 "112" was used, are stored in the "January 5th" column for date 41. Also, the totals of the number of pickup errors 43, the number of placement errors 44, and the total number of pickups 45 from January 1st to January 3rd and January 6th to January 7th, when component data 17 with component data code 42 "111" was used, are stored in the "January 7th" column for date 41.

[0044] 2, the output unit 33 extracts information that matches a request from the production management device 3 of the factories F1 to F3 from the database 21, and outputs (transmits) it to the requesting production management device 3. In this way, by storing the acquired part data 17 and performance data 14 in the database 21 based on the result of comparing the acquired part data 17 with the part data 21a stored in the database 21, the part 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 with reference to the flow chart in Fig. 5. First, data collection unit 15 of production management device 3 in factories F1 to F3 collects component mounting work results from component mounting devices M2 and M3 on component mounting line L1 (production line) installed in factories F1 to F3 (ST1: data collection step). Then, while component mounting devices M2 and M3 are mounting components, aggregation unit 16 aggregates performance data 14 from the collected component mounting work results (ST2: aggregation step).

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

[0047] 5, if the comparison step (ST4) determines that the data match, the storage processing unit 32 integrates the acquired performance data 14 with the stored performance data 21b and stores the integrated performance data 14 in the database 21 (integrated storage) (ST5: integrated storage step). If the comparison step (ST4) determines that the data do not match, 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 step).

[0048] That is, the integration and storage step (ST5) and the new storage step (ST6) are storage steps in which the acquired component data 17 and the acquired performance data 14 are stored in the database 21 based on the results of the comparison in the comparison step (ST4). If the acquired component data 17 matches the stored component data 21a in the comparison step (ST4), the acquired performance data 14 is integrated with the stored performance data 21b and stored in the database 21 in the storage step (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 step (ST6). This allows the component data 17 and performance data 14 to be efficiently accumulated in the database 21.

[0049] As described above, the component data management device 7 that manages component data 17 in this embodiment includes an acquisition unit 30 that acquires at least the component data 17 used by the component mounting devices M2, M3 and the performance data 14 obtained when components are mounted by the component mounting devices M2, M3 using the component data 17, a comparison unit 31 that compares the acquired component data 17 with component data 21a stored in a database 21 that associates and stores the component data 17 and the performance data 14, 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. This allows the component data 17 and the performance data 14 to be efficiently accumulated in the database 21.

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

[0051] In the above embodiment, the output unit 33 extracts information matching a request from the production management device 3 of each of the factories F1 to F3 from the database 21 and outputs (transmits) it to the requesting production management device 3. In other embodiments, the output unit 33 may transmit information to the production management device 3 when a predetermined period or a predetermined storage capacity is reached. By using a predetermined period or a predetermined storage capacity as a guide, the production management device 3 can automatically acquire information without a request command. In addition, because information about the same parts is integrated, the data transmission volume can be reduced compared to when the integration process 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 volume, the information can be appropriately transmitted 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 storing component data and performance data in a database, and are useful in the field of mounting components on boards. [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 in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, comprising: an acquiring step of acquiring at least component data used by the component mounting device and performance data obtained when the component mounting device mounts the component using the component data; a comparison step of comparing the acquired part data with part data stored in a database that stores the part data and the performance data in association with each other; a storing step of integrating the acquired performance data with the stored performance data and storing the integrated data in the database when the acquired part data matches the stored part data based on the result of the comparison, and newly storing the acquired part data and the performance data in the database when they do not match.

2. a counting step of counting the performance data while the component mounting device is mounting components, The parts data management method according to claim 1 , wherein the acquiring step acquires the aggregated performance data.

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

4. 4. The component data management method according to claim 1, wherein the performance data includes at least one of the following items: a period during which components were mounted, a failure rate when components were mounted, the number of failures, and a performance number of components picked up.

5. A component data management device that manages component data in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, an acquisition unit that acquires at least component data used by the component mounting device and performance data obtained when the component mounting device mounts the component using the component data; a comparison unit that compares the acquired part data with part data stored in a database that stores the part data and the performance data in association with each other; and a storage processing unit that, if the acquired part data matches the stored part data based on the result of the comparison, integrates the acquired performance data with the stored performance data and stores the integrated data in the database, and if they do not match, newly stores the acquired part data and the acquired performance data in the database.

6. A component data management program that causes a computer to manage component data in which component information of a component is linked to operating parameters that are operating conditions of a component mounting device for mounting the component on a board, an acquiring step of acquiring at least component data used by the component mounting device and performance data obtained when the component mounting device mounts the component using the component data; a comparison step of comparing the acquired part data with part data stored in a database that stores the part data and the performance data in association with each other; a storing step of integrating the acquired performance data with the stored performance data and storing the integrated data in the database when the acquired part data matches the stored part data based on the result of the comparison, and newly storing the acquired part data and the acquired performance data in the database when they do not match.

7. A component data management system including a component mounting device that mounts components on a board, and a component data management device that manages component data in which component information of the components is linked to operating parameters that are operating conditions of the component mounting device, a data collection unit that uses the component data to collect performance data obtained when the component is mounted by the component mounting device, The part 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 acquired part data with part data stored in a database that stores the part data and the performance data in association with each other; and a storage processing unit that, if the acquired part data matches the stored part data based on the result of the comparison, integrates the acquired performance data with the stored performance data and stores the integrated data in the database, and if they do not match, newly stores the acquired part data and the acquired performance data in the database.

Images