JP7716683B2 - Component data management method, component data management device, component data management program, and component data management system - Google Patents

Description

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 by a component mounting device that mounts components on a board.

Component mounting devices that mount components on boards control component mounting operations based on numerous operating parameters, including operating conditions related to component placement on the board, component pickup by the nozzle, and component photography. Appropriate values for these operating parameters are set for each component as component data linked to component information, including information such as the component's shape. Furthermore, some operating parameters may be changed if a mounting error occurs during component mounting work. Patent Document 1 discloses a system that records a component data change history and mounting error information, displays the progress of mounting errors on a display unit, and, when a date and time is specified, displays past component data and restores the component data to its correct state.

JP 2014-93335 A

When creating new component data or correcting component data to reduce mounting errors or improve productivity, a variety of methods are used, such as the worker creating or correcting the component data creating it based on past experience or performance information, or duplicating component data for similar components. However, while conventional technologies including Patent Document 1 allow for visual confirmation of the relationship between component data and trends in mounting errors, they do not allow for understanding the relationship between the creator or creation method of the component data and performance information such as mounting errors, leaving room for further improvement in creating component data that is highly productive and of high mounting quality.

The present invention therefore aims to provide a component data management method, component data management device, component data management program, and component data management system that allow for easy confirmation of component data creation methods and component mounting performance.

The component data management method of the present invention manages component data in which component information for a component is linked to operating parameters, which are the operating conditions of a component mounting device for mounting the component on a board. It includes a storage step of linking and storing in a database the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, or creation method of the component data, and performance data obtained when the component is mounted by the component mounting device using the component data, and a performance creation step of creating performance information by compiling the performance data based on the creation information.

The component data management device of the present invention manages component data in which component information for a component is linked to operating parameters, which are the operating conditions of a component mounting device for mounting the component on a board. It includes a storage processing unit that links and stores in a database at least the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, or creation method of the component data, and performance data obtained when the component is mounted by the component mounting device using the component data, and a performance creation unit that creates performance information by compiling the performance data based on the creation information.

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 for a component is linked to operating parameters, which are the operating conditions of a component mounting device for mounting the component on a board. The program includes a storage step that links and stores in a database at least the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, or creation method of the component data, and performance data obtained when the component is mounted by the component mounting device using the component data, and a performance creation step that creates performance information by compiling the performance data based on the creation information.

The component data management system of the present invention manages component data in which component information for a component is linked to operating parameters, which are the operating conditions of a component mounting device for mounting the component on a board. It includes a storage processing unit that links and stores in a database at least the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, or creation method of the component data, and performance data obtained when the component is mounted by the component mounting device using the component data, and a performance creation unit that creates performance information by compiling the performance data based on the creation information.

This invention makes it easy to check component data creation methods and component mounting performance.

FIG. 1 is a diagram illustrating the configuration of a production system according to an embodiment of the present invention. FIG. 1 is a block diagram showing the configuration of a production system according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a parts data creation screen displayed on the production management device according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a result information creation condition setting screen displayed on the production management device according to an embodiment of the present invention; FIG. 10 is a diagram showing an example of a performance information (aggregation) display screen displayed on the production management device according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a performance information (transition by item) display screen displayed on the production management device according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a display screen of performance information (transition by production method) displayed on the production management device according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a performance information (service usage effect) display screen displayed on the production management device according to an embodiment of the present invention. 1 is a flow diagram of a part data management method according to an embodiment of the present invention;

One embodiment of the present invention will be described in detail below using the drawings. The configurations, shapes, etc. described below are examples for explanatory purposes 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, production management device, and component data management device. Below, corresponding elements in all drawings will be given the same reference numerals, and duplicate explanations will be omitted.

First, the configuration of production system 1 will be explained with reference to Figure 1. Production system 1 is composed of customer factories F1-F3 and a support center S, which is located away from factories F1-F3 and supports customer production activities. Each factory F1-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-F3 will be explained using first factory F1 as an example.

In FIG. 1, the first factory F1 is equipped with one component mounting line L1, which is made up of connected production equipment 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 component mounting devices M2 and M3. Note that the component mounting line L1 installed in the first factory F1 does not need to be one, and can 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, and can be one, or three or more.

Each production device in the first factory F1 is connected to an on-site 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 on the component mounting line L1 and sending this to each production device. Each production device also sends data such as its operating status and work history 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 also be configured to have a line management device for each component mounting line L1 that manages the production of mounted boards.

In FIG. 1, a parts data management device 7 is installed at support center S. The production management devices 3 of multiple factories F1-F3 are equipped with external communication units 5. The parts data management device 7 at support center S is also equipped with external communication units 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 parts data management device 7 to exchange information via the off-site communication network 6. The parts data management device 7 acquires production device performance information and parts data from the production management devices 3 of each factory F1-F3 and stores this 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 a request from the production management device 3.

The production management device 3 and parts data management device 7 are not limited to a configuration in which they exchange information directly via the off-site communications 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 such as email or data communications lines.

Next, referring to Figure 1, component mounting line L1 will be described. Printing device M1 is a production device that performs solder printing, which screen-prints cream solder for joining components onto boards. Component mounting devices M2 and M3 are production devices that perform component mounting, which attaches components to boards after solder printing.

Component mounting devices M2 and M3 use nozzles on their mounting heads to vacuum-suck components supplied by feeders based on operational parameters included in component data set for each component to be mounted on the board. They then use a component recognition camera to capture an image of the component held by the nozzle and mount the component 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 errors during component mounting, such as the nozzle's component suction operation and the component recognition operation, in which the component recognition camera captures and recognizes the component after it has been removed.

Next, referring to Figure 2, the configuration of the production system 1 equipped with the production management device 3 and component data management device 7 will be described. Here, we will explain the multiple functions equipped in the production management device 3 and component data management device 7, focusing on the configuration related to the function of creating and managing component data including operating parameters used in component mounting operations by component mounting devices M2 and M3. Furthermore, the production management devices 3 installed in factories F1 to F3 have the same configuration, and here we will explain the first factory F1 as an example.

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 is equipped with a production management memory unit 11, a data collection unit 16, a data creation unit 17, a performance display processing unit 18, 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, performance information 15, etc.

The input unit 9 is an input device such as a keyboard, touch panel, or mouse, and is used to enter operation commands and data. The display unit 10 is a display device such as an LCD panel, and displays various data stored in the production management memory unit 11, as well as various information such as operation screens and input screens 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.

In FIG. 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 13a 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.

In FIG. 2, the component library 13 stores multiple component data 13a, each of which links component information with operational parameters. The component data 13a is associated with production data in the production library 12 by a component code. The component data 13a also contains creation information related to the creation of the component data 13a, including the creation date and time of the component data 13a, information identifying the creator, and information identifying the creation method of the component data 13a, which will be described later.

Component information is information that indicates attributes unique to the component, and includes items such as component dimensions, product number information, lead count information, lead spacing information, and component image information (see Figure 3). Operation parameters are control parameters (operating conditions) used to control component mounting devices M2 and M3 arranged on component mounting line L1 when performing component mounting work on the component specified in the component data.

Operation parameters include data related to the nozzle used to pick up and hold the component, control parameters related to the nozzle movement speed, parameters related to the component recognition process using a component recognition camera, control parameters related to the nozzle pick-up operation, and control parameters related to the operation of placing the component on the board.

Even if the component information is the same, the operating parameters may be changed due to changes in the model of the component mounting devices M2 and M3 used to mount the components on the board, the material of the board, the electrodes on the board, or to improve mounting quality or the rate of mounting errors. When the operating parameters of the component are changed, component data 13a is created (updated) linking the changed operating parameters without changing the component information. At this time, a new code is assigned to the component code in component data 13a to distinguish it from the operating parameters before the modification.

In FIG. 2, the data collection unit 16 collects component mounting work performance data from the production devices (printing device M1, component mounting devices M2, M3) on component mounting line L1 installed in first factory F1. The component mounting work performance data includes information such as the production start date and time, production end date and time, number of sheets produced, number of work errors, error rate (frequency), number of operational errors and their details. The data collection unit 16 associates the collected performance information with information identifying the component mounting devices M2, M3 that performed the component mounting work, and information identifying component data 13a including production data and operational parameters, and stores this information in the production management storage unit 11 as performance data 14.

When a worker creates or modifies component data 13a, the data creation unit 17 displays a component data creation screen on the display unit 10 to assist the worker in creating the component data. Component data 13a is created or modified during preparation work before mounting a new component on a board, or during correction work when a mounting error occurs. Hereinafter, a component for which component data 13a is created or modified will be referred to as a "first component."

Now, referring to Figure 3, an example of the component data creation screen 40 displayed on the display unit 10 by the data creation unit 17 will be described. The component data creation screen 40 has a component information setting area 41 and a creation method setting area 42. The component information setting area 41 has a component name setting frame 43, a component shape setting frame 44, a size information setting frame 45, and a detail display button 46. The creation method setting area 42 has a creation method setting frame 47, a cancel button 48, and a create button 49.

The part name setting box 43 is where the part name (part product name) of the first part for which part data 13a is to be created is entered. The part shape setting box 44 is where the external shape (part shape) of the first part is entered. The size information setting box 45 is where the external dimensions, body size, electrode position, etc. of the first part (part size) are entered. When the details display button 46 is operated, the screen transitions to a screen (not shown) for displaying and setting detailed part information.

In FIG. 3, the creation method setting frame 47 displays a manual creation method setting button 47a, an estimation method setting button 47b, an extraction method setting button 47c, a radio button 47d, and an increase/decrease button 47e. When the manual creation method setting button 47a is selected and the create button 49 is operated, the data creation unit 17 displays (transitions to) a screen (not shown) that supports the creation of component data 13a using the manual creation method, in which the operator manually creates operating parameters. When the estimation method setting button 47b is selected and the create button 49 is operated, the data creation unit 17 transmits the component information of the first component (component D11) entered in the component information setting area 41 and a command to create operating parameters using the estimation method to the component data management device 7 via the external communication unit 5.

When the extraction method setting button 47c is selected and the create button 49 is operated, the data creation unit 17 transmits the component information for the first component (component D11) entered in the component information setting area 41, the extraction conditions set using the radio buttons 47d and the increase/decrease buttons 47e, and a command to create operating parameters using the extraction method to the component data management device 7 via the external communications unit 5. In this example, the extraction method setting button 47c is selected, and the extraction conditions for extracting component data 13a with an error rate of 700 ppm or less are set using the radio buttons 47d and the increase/decrease buttons 47e. When the cancel button 48 is operated, the creation of the component data 13a is canceled.

In FIG. 2, the data creation unit 17 links the operating parameters created using the manual creation method, or the operating parameters estimated using the estimation method and extracted using the extraction method by the component data management device 7 (described later), to the component information of the first component, and stores them in the component library 13 as component data 13a. At this time, the data creation unit 17 assigns a new code to the component code of the component data 13a, and stores the linked data in the component library 13 with creation information including the creation date and time of the component data 13a, information identifying the worker such as the creator's name and the line in charge, and the creation method of the component data 13a.

In Figure 2, the parts data management device 7 installed at support center S has functions such as collecting and managing parts data 13a and performance data 14 used at customer factories F1 to F3, creating operating parameters for the parts data 13a using estimation and extraction methods, and aggregating performance data 14 to create performance information 15. The parts data management device 7 is connected to an external communications unit 8 and a storage device 20.

The storage device 20 stores learning model information 22, extraction conditions 23, and grade creation conditions 24, as well as a database 21 that stores information acquired from multiple factories F1-F3. The storage device 20 is, for example, a semiconductor memory or a hard disk drive. The database 21 may also include parts data 13a used in the production systems 1 of multiple factories F1-F3, or a database prepared in advance by an EDA (Electronic Design Automation) vendor.

In FIG. 2, the parts data management device 7 includes information processing devices such as an acquisition unit 30, a storage processing unit 31, a learning unit 32, an estimation unit 33, an extraction unit 34, a score creation unit 35, an output unit 36, 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 have to be configured with a single computer, but may be configured with multiple devices. For example, the storage device 20 and all or part of the information processing devices may be provided in the cloud via a server.

The acquisition unit 30 acquires component data 13a used in the production of mounted boards at each of the multiple factories F1-F3, creation information for the component data 13a, and performance data 14 from the multiple factories F1-F3 via the external communication unit 8. The acquisition unit 30 acquires data at a predetermined time, for example, once a day. The storage processing unit 31 associates the component data 13a used by the component mounting devices M2, M3 acquired by the acquisition unit 30, creation information including the creation date and time, creator, and creation method of the component data 13a, performance data 14 obtained when components are mounted by the component mounting devices M2, M3 using the component data 13a, and information identifying the factories F1-F3, and stores the associated data in the database 21.

In FIG. 2, the learning unit 32 uses multiple component data 13a (component information, operating parameters) stored in the database 21 and performance data 14 as teaching data, and generates a learning model that shows the relationship between operating parameters and component information using a learning algorithm that employs machine learning or the like. The learning algorithm may use neural networks (including deep learning using multi-layer neural networks), genetic programming, decision trees, Bayesian networks, support vector machines (SVMs), or the like. The generated learning model is stored in the storage device 20 as learning model information 22.

The estimation unit 33 estimates (calculates) the operating parameters of the first part based on the generated learning model (learning model data 22) and the part information of the first part transmitted from the production management device 3 of factories F1 to F3. The estimation unit 33 transmits the estimated operating parameters to the production management device 3 of the requesting factory F1 to F3 via the external communication unit 8. In this way, the estimation unit 33 estimates the operating parameters of the first part using the learning model (learning model data 22) generated by the estimation method based on the part information of the part and the part's operating parameters.

In FIG. 2, the extraction unit 34 extracts operating parameters of the first part from the database 21 based on the part information of the first part transmitted from the production management device 3 of the factories F1 to F3 and the extraction conditions 23. The extraction unit 34 transmits the extracted operating parameters to the production management device 3 of the requesting factory F1 to F3 via the external communication unit 8. In this way, the extraction unit 34 references the database 21 using an extraction method and extracts operating parameters corresponding to part information similar to or matching the part information of the first part as operating parameters of the first part.

In this way, in the parts data management system (production system 1) equipped with the production management device 3 and parts data management device 7, part data 13a is created using one of the following methods: a manual creation method in which workers at factories F1-F3 manually create the operating parameters of part data 13a; an estimation method in which support center S estimates operating parameters using machine learning or the like based on requests from factories F1-F3; or an extraction method in which operating parameters are extracted from past performance. In other words, creating the operating parameters of the first part using the estimation method or extraction method is one of the services provided by support center S.

Next, referring to Figures 2 and 4 to 8, we will explain the results creation process in which performance data 14 for component mounting lines L1 of factories F1 to F3 is compiled based on the period and the creation method of component data 13a to create performance information 15, which is then displayed on the display unit 10 of the production management device 3. Here, we will explain the results creation process in which the production management device 3 of the first factory F1 displays performance information 15 for component mounting line L1 on the display unit 10.

In Figure 2, the performance display processing unit 18 of the production management device 3 displays a performance information creation condition setting screen on the display unit 10 to assist the worker in setting the performance creation conditions, which are the conditions for creating performance information 15.

Now, referring to Figure 4, an example of the grade information creation condition setting screen 50 displayed on the display unit 10 by the grade display processing unit 18 will be described. The grade information creation condition setting screen 50 has a period setting area 51, a calculation method setting area 52, a display information setting area 53, a cancel button 54, and a confirm button 55. In the period setting area 51, the period (start date and end date) for which the performance data 14 will be calculated is entered. In this example, the calculation period is set to June 1, 2021 to June 30, 2021. In the calculation method setting area 52, the calculation method for the performance data 14 is selected using the radio buttons from "by creator," "by department," or "all." In this example, "all" is selected.

In the display information setting area 53, the items to be tallied as performance information 15 are selected using check buttons from among "Total number of mounting points," "Data creation time," "Pickup errors," "Mounting errors," and "Productivity." Operating the cancel button 54 cancels the creation of performance creation conditions. Operating the confirm button 55 causes the performance display processing unit 18 to send the performance creation conditions 24 set on the performance information creation condition setting screen 50 to the component data management device 7 via the external communications unit 5.

In FIG. 2, the acquisition unit 30 of the component data management device 7 acquires, from the production management device 3 of the first factory F1, the score creation conditions 24, which include at least one item to be compiled based on the component mounting period and performance data 14, and stores the conditions in the storage device 20. The score creation unit 35 references the database 21 and, based on the score creation conditions 24 and creation information related to the creation of component data 13a, compiles the performance data 14 for the component mounting line L1 of the first factory F1 stored in the database 21 to create performance information 15.

Specifically, the grade creation unit 35 compiles the performance data 14 for the component mounting line L1 of the first factory F1 stored in the database 21 based on the period included in the grade creation conditions 24. Furthermore, the grade creation unit 35 creates performance information 15 for each creator who created the component data 13a, for each department to which the creator belongs, or for all creators combined, based on the compilation method included in the grade creation conditions 24. Furthermore, the grade creation unit 35 compiles the performance data 14 for each creation method of the component data 13a to create performance information 15.

In FIG. 2, the output unit 36 outputs (transmits) the created performance information 15 to the production management device 3 of the requesting first factory F1 via the external communication unit 8. Upon receiving the performance information 15, the performance display processing unit 18 of the production management device 3 of the first factory F1 stores it in the production management memory unit 11. Furthermore, the performance display processing unit 18 causes the display unit 10 to display various performance information display screens that display the performance information 15 in table format or in a graph format that displays the performance information 15 in chronological order.

Now, referring to Figure 5, an example of the performance information (aggregate) display screen 60 displayed on the display unit 10 by the performance display processing unit 18 will be described. The performance information (aggregate) display screen 60 displays the aggregation results of the performance data 14 included in the performance information 15 in table format. The performance information (aggregate) display screen 60 has a performance display area 61, a service usage effect display area 62, a graph display button 63, and an exit button 64.

The performance display area 61 displays the tabulated results of performance data 14 for the usage period specified on the performance information creation condition setting screen 50 (Figure 4) in table format. Specifically, the "number of target component types," "total number of mounted components," "average data creation time," "average pickup error rate," and "average productivity (number of mounted components per unit time)" are displayed for each creation method of component data 13a (operation parameters). Creation methods are categorized into manual creation (manual creation) created manually by workers at the first factory F1, estimation (optimal value estimation) created by support center S, extraction (actual value extraction), and creation using the estimation or extraction method followed by manual correction (manual correction after use). The averages of the estimation, extraction, and manual correction after use methods (service usage averages) are also displayed.

In Figure 5, the service usage effect display area 62 displays a comparison between the manual creation method and the method using support center S (average service usage), calculated based on performance information 15. Specifically, the improvement rates (1 - (average service usage / manual creation)) for "average data creation time," "average pickup error rate," and "average productivity (number of components mounted per unit time)" are displayed. Furthermore, the effects of using the service provided by support center S are displayed as "reduction in labor hours," "number of reduced errors," and "increased number of mounted components," along with the monetary equivalents of these effects and an estimated total improvement amount.

For example, "man-hour reduction" is calculated as the number of target components x (data creation time (manual creation) - data creation time (average service use)). Also, "reduced number of errors" is calculated as the total number of mounting points x (pick-up errors (manual creation) - pick-up errors (average service use)). Also, "increased number of mounting points" is calculated as the total number of mounting points x (1 - (productivity (manual creation) / productivity (average service use))).

As such, performance information 15 includes items related to changes in labor hours (man-hour reduction rate), items related to changes in quality (error rate improvement rate), and items related to changes in productivity (productivity improvement rate). When the graph display button 63 is operated, the screen transitions to the performance information (transition by item) display screen 70 (Figure 6), which will be described later. When the end button 64 is operated, the display process of performance information 15 is stopped and the screen returns to the performance information creation condition setting screen 50 (Figure 4).

Next, referring to Figure 6, the performance information (transition by item) display screen 70 displayed on the display unit 10 by the performance display processing unit 18 will be described. The performance information (transition by item) display screen 70 displays the aggregated results of the performance data 14 included in the performance information 15 in a graph format. The performance information (transition by item) display screen 70 is provided with a first graph display area 71, a second graph display area 72, a quality button 73, a productivity button 74, a back button 75, a next button 76, and an end button 77.

The first graph display area 71 displays the "number of new creations" and "service usage rate" aggregated by month as a time series (month) on the horizontal axis as trends in component data creation labor hours. The second graph display area 72 displays the "data creation labor hours" and "service usage rate" aggregated by month as a time series (month) on the horizontal axis as trends in component data creation labor hours. In other words, the performance information 15 includes items (number of new creations, service usage rate, data creation labor hours) aggregated over time based on the performance data 14.

In Figure 6, when the quality button 73 is operated, the screen transitions to a screen (not shown) that displays quality (such as pickup errors) as a graph of progress by item. When the productivity button 74 is operated, the screen transitions to a screen (not shown) that displays productivity (such as the number of components mounted per unit time) as a graph of progress by item. When the back button 75 is operated, the screen returns to the performance information (aggregate) display screen 60 (Figure 5). When the next button 76 is operated, the screen transitions to the performance information (progression by production method) display screen 80 (Figure 7), which will be described later. When the end button 77 is operated, the display process of the performance information 15 is stopped, and the screen returns to the performance information creation condition setting screen 50 (Figure 4).

Next, referring to Figure 7, the performance information (progression by creation method) display screen 80 displayed on the display unit 10 by the performance display processing unit 18 will be described. The performance information (progression by creation method) display screen 80 displays the aggregated results of the performance data 14 included in the performance information 15 in a graph format. The performance information (progression by creation method) display screen 80 is provided with a graph display area 81, a man-hours button 82, a productivity button 83, a back button 84, a next button 85, and an end button 86.

The graph display area 81 displays the trend in pickup errors, with "pickup errors" aggregated by month and broken down by manual creation method (manual creation), estimation method (optimal value estimation), extraction method (actual value extraction), and manual correction after service use, with the horizontal axis representing time (months).

In Figure 7, when the Man-hours button 82 is operated, the screen transitions to a screen (not shown) that displays a graph of man-hours (such as data creation man-hours) as a transition by creation method. When the Productivity button 83 is operated, the screen transitions to a screen (not shown) that displays a graph of productivity (such as the number of components mounted per unit time) as a transition by creation method. When the Back button 84 is operated, the screen returns to the performance information (transition by item) display screen 70 (Figure 6). When the Next button 85 is operated, the screen transitions to the performance information (service usage effect) display screen 90 (Figure 8), which will be described later. When the End button 86 is operated, the display process of the performance information 15 is stopped and the screen returns to the performance information creation condition setting screen 50 (Figure 4).

Next, referring to Figure 8, the performance information (service usage effect) display screen 90 displayed on the display unit 10 by the performance display processing unit 18 will be described. The performance information (service usage effect) display screen 90 displays the aggregated results of the performance data 14 included in the performance information 15 in a graph format. The performance information (service usage effect) display screen 90 is provided with a first graph display area 91, a second graph display area 92, a third graph display area 93, a back button 94, and an end button 95.

The first graph display area 91 displays "data creation man-hours" aggregated by month as a trend in component data creation man-hours, with the horizontal axis representing months, separated by whether or not service is used. The second graph display area 92 displays "pickup errors" aggregated by month as a trend in pickup errors (quality), with the horizontal axis representing months, separated by whether or not service is used. The third graph display area 93 displays "productivity" aggregated by month as a trend in productivity, with the horizontal axis representing months, separated by whether or not service is used.

In Figure 8, pressing the back button 84 will return to the grade information (progression by creation method) display screen 80 (Figure 7). Pressing the end button 95 will stop the display process of the grade information 15 and return to the grade information creation condition setting screen 50 (Figure 4).

Next, a component data management method (data management program) for managing component data 13a will be described using the flow in Figure 9. Here, we will explain an example of a flow in which performance information 15 is created by aggregating performance data 14 obtained when components are mounted by component mounting devices M2 and M3 using component data 13a, and the performance information 15 is displayed on the display unit 10. First, the data collection unit 16 collects performance data of component mounting work from component mounting devices M2 and M3 (ST1: data collection step). The collected information is stored in the production management memory unit 11 as performance data 14.

The acquisition unit 30 then acquires the component data 13a used by the component mounting devices M2 and M3, creation information for the component data 13a, including the creation date and time, creator, and creation method of the component data 13a, and performance data 14 obtained when components are mounted by the component mounting devices M2 and M3 using the component data 13a (ST2: acquisition process). The storage processing unit 31 then links the acquired component data 13a, creation information, and performance data 14 and stores them in the database 21 (ST3: storage process). For example, the acquisition process (ST2) and storage process (ST3) are performed once a day at a specified time, and the component data 13a, creation information, and performance data 14 used in factories F1 to F3, etc. are periodically saved (backed up).

In Figure 9, the performance display processing unit 18 of the production management device 3 installed in factories F1-F3, etc., then sets performance creation conditions 24, including the period during which the components were mounted and the items to be tallied based on the performance data 14 (ST4: condition setting process). For example, the performance creation conditions 24 are set by the worker using the input unit 9 to operate the performance information creation condition setting screen 50 (Figure 4) displayed on the display unit 10 by the performance display processing unit 18. Next, the acquisition unit 30 acquires the performance creation conditions 24 set in the condition setting process (ST4) (ST5: condition acquisition process).

Then, the result creation unit 35 compiles the performance data 14 stored in the database 21 based on the performance creation conditions 24 and creation information to create performance information 15 (ST6: performance creation process). The output unit 36 then outputs (transmits) the created performance information 15 to the requesting production management device 3 (ST7: output process). The result display processing unit 18 then acquires (receives) the output information (ST8: performance information acquisition process). The acquired performance information 15 is stored in the production management storage unit 11. The result display processing unit 18 then displays the performance information 15 on the display unit 10 in a predetermined format such as a table or graph (e.g., Figures 5 to 8) (ST9: performance display process). This makes it easy to check the method for creating component data 13a and the component mounting performance.

As described above, the component data management device 7 of this embodiment includes a storage processing unit 31 that links and stores in the database 21 the component data 13a used by the component mounting devices M2 and M3, creation information related to the creation of the component data 13a, which includes at least one of the creation date and time, creator, and creation method of the component data 13a, and performance data 14 obtained when components are mounted by the component mounting devices M2 and M3 using the component data 13a, and a results creation unit 35 that creates performance information 15 by aggregating the performance data 14 based on the creation information. The results creation unit 35 created in this way makes it easy to check the creation method of the component data 13a and the performance of component mounting.

In the above-described embodiment of production system 1 (parts data management system), support center S (parts data management device 7) is installed outside factories F1 to F3, but support center S (parts data management device 7) may also be installed within factories F1 to F3.

In addition, the above description was of a method in which the parts data management device 7 of support center S creates performance information 15 based on requests (performance creation conditions 24) from the production management devices 3 installed in factories F1-F3, and the requesting production management device 3 displays the performance information 15 on the display unit 10 in a predetermined format (e.g., Figures 5-8). However, the display (report) of performance information 15 is not limited to this. For example, the parts data management device 7 of support center S may create a performance report summarizing the performance information 15 in a predetermined format at a predetermined time (e.g., once a month), attach it to an email, and send it to the factory managers of factories F1-F3. In other words, the parts data management device 7 may be configured to include a performance report creation unit that creates performance reports, and the output unit 36 may send the performance reports to the factory managers of factories F1-F3.

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 easily checking the component data creation method and component mounting performance, and are useful in fields where components are mounted on circuit boards.

1. Production system (parts data management system)
7 Component data management device M2, M3 Component mounting device

Claims (10)

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:
a storing step of at least linking the component data used by the component mounting device, creation information relating to the creation of the component data, including at least one of the creation date and time, creator, and creation method of the component data, and performance data obtained when components are mounted by the component mounting device using the component data, and storing the linked information in a database;
and a score creation step of creating score information by aggregating the performance data based on the created information,
The method for creating the part data includes:
a method for estimating an operational parameter of a first part using a learning model generated based on part information of the part and an operational parameter of the part;
A part data management method including at least one of the following methods: referring to the database and extracting, as the operation parameters of the first part, operation parameters corresponding to part information similar to or matching part information of the first part . 2. The parts data management method according to claim 1 , wherein in said score creating step, said score information is created for each creator who created said parts data or for each department to which said creator belongs. 3. The part data management method according to claim 1 , wherein said score information is created for each of said creation methods of said part data in said score creating step. a condition acquisition step of acquiring a result creation condition including at least one item to be tallied based on the period during which components were mounted and the performance data;
and an output step of outputting the created score information,
4. The parts data management method according to claim 1, wherein the grade creation step creates the grade information based on the grade creation conditions. 5. The parts data management method according to claim 1 , wherein the performance information includes items that are compiled in chronological order based on the performance data. 6. The parts data management method according to claim 1 , wherein the performance information includes at least one item of an item relating to a change in man-hours, an item relating to a change in quality, and an item relating to a change in productivity. 7. The component data management method according to claim 1 , wherein the performance data includes at least one item of a period during which components were mounted, a rate of errors when components were mounted, and a number of components mounted. 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,
a storage processing unit that associates at least the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, and creation method of the component data, and performance data obtained when components are mounted by the component mounting device using the component data, and stores the associated information in a database;
a result creation unit that creates result information by aggregating the performance data based on the creation information ,
The method for creating the part data includes:
a method for estimating an operational parameter of a first part using a learning model generated based on part information of the part and an operational parameter of the part;
A part data management device including at least one of a method of referring to the database and extracting, as the operation parameters of the first part, operation parameters corresponding to part information similar to or matching part information of the first part . 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,
a storing step of at least linking the component data used by the component mounting device, creation information relating to the creation of the component data including at least one of the creation date and time, creator, and creation method of the component data, and performance data obtained when components are mounted by the component mounting device using the component data, and storing the linked information in a database;
and a grade creation step of creating grade information by aggregating the performance data based on the created information,
The method for creating the part data includes:
a method for estimating an operational parameter of a first part using a learning model generated based on part information of the part and an operational parameter of the part;
A part data management program including at least one of a method of referring to the database and extracting, as the operation parameters of the first part, operation parameters corresponding to part information similar to or matching part information of the first part . A component data management system 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,
a storage processing unit that associates at least the component data used by the component mounting device, creation information related to the creation of the component data, which includes at least one of the creation date and time, creator, and creation method of the component data, and performance data obtained when components are mounted by the component mounting device using the component data, and stores the associated information in a database;
a result creation unit that creates result information by aggregating the performance data based on the creation information ,
The method for creating the part data includes:
a method for estimating an operational parameter of a first part using a learning model generated based on part information of the part and an operational parameter of the part;
A part data management system including at least one of a method of referring to the database and extracting, as the operation parameters of the first part, operation parameters corresponding to part information similar to or matching part information of the first part .