CN101460965A - Component data distribution method, component data distribution apparatus and program - Google Patents

Abstract

A method for distributing component data, the method being executed by a server device (10) and allowing component data used when installing components on a board to be distributed among a plurality of terminal devices (20), the method comprising: component data a collection step of collecting component data and evaluation data from the first terminal device, the evaluation data representing the degree of realizing operations required for actual production using the component data; and a component data accumulation step of accumulating all data having the collected evaluation data. The collected component data is provided to a second terminal device different from the first terminal device with the collected component data.

Description

Component data distribution method, component data distribution device and program thereof

technical field

The present invention relates to a component data distribution method and the like that allow distribution of component data to be used by a component mounting device when mounting components on a board, and more particularly, the present invention relates to a technique for stimulating component data distribution.

Background technique

Conventionally, for a component mounting apparatus for mounting a component on a board, there is known a service providing method of providing a user with various support data such as business information, electronic instructions, etc. via the Internet. , virtual training, and installed component data (hereinafter simply referred to as component data) (for example, see Patent Document 1).

Among the above, for the component data as data to be used by the component mounting device when the component is mounted on the board, Patent Document 1 particularly introduces saving component data and providing A service receiving means having data within a range specified by a component installation means, component type, etc. or all component data (paragraph [0153]). Thus, even a novice operator can receive component data according to the type of component or board to be used, thereby performing satisfactory installation production.

Component data can be obtained from successful users who manufacture quality products. In order to promote the provision of component data, it is effective to use a known method of providing an incentive to the provider.

Patent Document 1: Japanese Patent No. 3662578.

Contents of the invention

However, according to the technique of Patent Document 1, it is possible to distribute component data only after acquiring good product manufacturing records. Therefore, although the quality of distributed component data can be maintained at a high level, the amount of component data cannot be easily increased due to cumbersome operations performed before the component data can be successfully distributed.

In addition, since the component data completed to obtain excellent product manufacturing records is the result of various devices, constant exploration, and the ingenuity of each user, it is natural to be reluctant to disclose such valuable information to third parties, thereby hampering the distribution of component data .

The present invention has been made to solve the above-mentioned problems, and aims to provide a component data distribution method for improving production efficiency performed using a component mounting apparatus by facilitating and incentivizing provision and distribution of component data.

In order to achieve the above object, a component data distribution method performed by a component data distribution device and allowing distribution of component data used by a component mounting device when mounting a component on a board includes: a component data collecting step of collecting components from a first terminal device data and evaluation data indicating the degree to which operations required for actual production are realized using said component data; and a component data accumulation step of accumulating said collected component data with said collected evaluation data so as to be different from the first A second end device of an end device provides the collected component data.

In addition, the component data distribution method may further include: a component data retrieval step, when the retrieval condition is provided from the component data receiving device, one or more pieces of component data are retrieved from the collected component data according to the provided retrieval condition , and send a search result to the component data receiving device, the search result includes a component name indicating each retrieved component data and corresponding evaluation data; and a component data providing step, in which the component data receiving device provides a band When there is an acquisition request for one or more component names included and specified in the retrieval result, the component data receiving means is provided with the component data specified by the given component name.

The component data providing means may specify, among the plurality of items of component data, evaluation data of a lower rank representing component data having a large number of empty items as the evaluation data collected by the server device. When the component data providing means is implemented as the component mounting means, the component mounting means can determine that the evaluation data indicates a lower degree when the trial production is successfully performed using the component data than when it is not successfully performed. The component mounting apparatus may also determine that the degree indicated by the evaluation data is lower when the actual production with the component data is successfully performed than when it is not successfully performed.

With the above-described configuration, after being collected together with evaluation data representing operations, component data that does not yet have a record of manufacturing good products and that requires operations to be performed in order to achieve actual production is provided for use. Therefore, the amount of component data to be distributed increases, and the distribution of component data can be stimulated.

In addition, the component data distribution method may further include a reward determination step of determining the reward by judging the operation required to realize actual production based on the content indicated by the evaluation data. Distributing component data can be facilitated by giving suppliers of component data rewards determined according to ratings.

In particular, the provision of more useful component data can be facilitated by including a complaint collection step, collecting complaints pointing out problems in the supplied component data and determining in the reward determination step for a smaller number of said collected complaints A higher reward; in the reward determination step, a lower reward is determined when other component data similar to the component data have been collected than when it has not been collected; or in the reward determination step, for the required More difficult or troublesome operations determine higher rewards.

Furthermore, it is preferable that the component data distribution method further includes a bonus accumulating step of accumulating a bonus determined by associating the bonus with a provider of the component data, and the component data providing method includes a bonus display step of displaying the bonus.

With this configuration, component data providers can be encouraged to have realistic incentives to provide component data.

In addition, the component data distribution method may further include a usage fee payment instruction notification step of providing the collected component data based on the collected evaluation data of the collected component data when providing the component data receiving means to The component data receiving means notifies a usage fee payment instruction.

Since the efficiency of collecting the usage fee as a reward source can be improved with the above-described configuration, the supply of component data can be smoothly promoted by the reward.

In addition, the component data distribution method may further include a component data providing step of providing the collected component data only to users within a range set by a provider of the component data.

With the above-described configuration, since the provider of component data can limit the disclosure range of components to be registered, it is possible to reduce reluctance to provide component data because valuable component data is widely disclosed to general users. As a result, it can be expected that distribution of component data can be facilitated within a limited scope of disclosure. In addition, for example, it is convenient that practical use can be realized by registering component data disclosed only to users of related companies and the like.

Preferably, the component data further includes a portion common to a plurality of component mounting apparatuses and a plurality of portions individualized for the plurality of component mounting apparatuses; and in the component data collecting step, the The collected component data includes a plurality of pieces of evaluation data individualized for the plurality of component mounting devices. Thus, evaluation of component data can be managed for each component mounting device.

Furthermore, when the component data providing means is implemented as a component mounting means, in the component data collecting step, the component data distribution apparatus facilitates supply of the component data with a production record by notifying the component mounting means, thereby Component data with production records in the component installation can be collected.

With the configuration described above, component data with production records can be collected directly from the component mounting apparatus with high probability.

Furthermore, when the component data receiving means is realized as a component installing means, in the component data providing step, the component installing means may be provided with component data according to an acquisition request sent from the component installing means when checking the components.

Since necessary component data can be supplied from the server device with the above configuration when the data is required by the component mounting device, the efficiency of production using the component mounting device can be improved.

When the component data receiving means is implemented as a component installation means, the server means can provide the component data to the component installation means free of charge in the component data providing step.

With this configuration, the advantage of introducing a component mounting device may be attractive to potential customers by emphasizing that the component data is freely available.

The present invention can be implemented not only as the above-mentioned component data distribution method and component data providing method, but also as a device for executing the method, a system or program including the device, and a storage medium storing the program.

According to the component data distribution method, the component data providing method, etc. of the present invention, component data having no record of manufacturing good products and having operations necessary for actual production can be distributed with evaluation data representing operations. Therefore, the user of the component mounting apparatus can check the evaluation data and judge whether the component data can be used immediately, how much adjustment of the component mounting apparatus is required, and the like. As a result, the distribution of component data can be stimulated, and the component data can be rapidly improved to a level at which excellent products can be manufactured using the component data. Provision of component data can be facilitated by rewarding according to evaluation and usage environment.

Therefore, since the server device as a component data distribution device can collect and distribute component data having various rank evaluations, the number of opportunities for the component installation device to acquire available component data increases. When the operator acquires component data, the operator can select and acquire component data with necessary ratings by confirming the ratings of the component data to be acquired.

As a result, operations for adjusting component data by trial and error and operations for improving component data by analyzing problems can be reduced. Thus, it is possible to optimize the production resources required from the experimental steps to the manufacture of a good product. The optimization of production resources corresponds to, for example, a reduction in the number of operator work steps, electrical energy, fuel, water, sample material, etc.

Furthermore, using component data with desired evaluation (ie, data that has been carefully checked and completed at a high level) acquired from the server device, it is possible to improve the quality of products manufactured in the steps of manufacturing superior products. As a result, the power consumption required for the product is reduced and the lifespan is extended, thereby contributing to energy and resource conservation required by society.

Additional information on the background art of this application

The entire disclosure of Japanese Patent Application No. 2006-158741 filed on June 7, 2006 including specification, drawings and claims is incorporated herein by reference.

The entire disclosure of Japanese Patent Application No. 2006-161154 filed on June 9, 2006 including specification, drawings and claims is incorporated herein by reference.

Description of drawings

FIG. 1 shows an outline of a configuration of a component data distribution system according to an embodiment of the present invention;

FIG. 2 is a block diagram showing an example of functional configurations of a server device and a terminal device;

Figure 3 is a top view showing an example of an assembly;

4A and 4B show an example of the component data stored in the component data storage unit 11 and the component data storage unit 23;

Figure 5 shows an example of an identified portion of an image;

6A and 6B are explanatory diagrams of evaluation data;

Figure 7A shows an example of a more difficult component to generate component data, while Figure 7B shows an example of an identified portion of a component image;

Figure 8 shows an example of a reward form 160;

FIG. 9 is a flowchart showing detailed operations of the server device 10;

FIG. 10 is a flowchart showing detailed operations of the terminal device 20;

Figure 11 shows an example of the test result display screen;

Figure 12 shows an example of a shape data entry screen;

Figure 13 shows an example of an installation data entry screen;

Figure 14 shows an example of a component data registration prompt screen; and

Figure 15 shows an example of a complaint sending confirmation screen.

reference sign

1 Component data distribution system

10 server installations

11 Component data storage unit

12 component data supply unit

13 Communication I/F unit

14 Component Data Acquisition Units

15 Reward Determination Unit

16 Reward Accumulation Units

20 terminal units

21 Mounting the control unit

22 Operator I/F unit

23 component data storage unit

24 Communication I/F unit

25 Install the mechanism unit

26 component data entry unit

27 Evaluation determination unit

28 Component data registration unit

30 network

110 common parts

111 Model related parts

121 retrieval unit

122 Using Data Storage Units

150 Operational Necessities Form

151 Evaluation Form

160 Award Form

211 Component data acquisition unit

212 Complaint sending unit

Detailed ways

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

<system configuration>

FIG. 1 shows an outline of a configuration of a component data distribution system according to an embodiment of the present invention.

The component data distribution system 1 is configured by connecting the server device 10 and a plurality of terminal devices 20 via the network 30 . The server device 10 is an example of a component data distribution device, and the terminal device 20 is an example of a component data providing device.

In FIG. 1 , for example, the server device 10 is a computer provided at a service location of a component mounting device manufacturer, and each terminal device 20 is realized as a component mounting device provided at a factory of a component mounting device user, for example.

In the component data distribution system 1 thus configured, the server device 10 and the plurality of terminal devices 20 distribute the component data by exchanging the component data through the network 30 . Component data is a type of data used by component mounters when mounting components on boards, including data related to the components themselves, such as measurement data for components, and in addition to determining the duration of mounting components for each model of component mounter. Optimizing error data for device conditions. The component mounting device is informed of component data using NC data which practically indicates which component is mounted at which point on the board in what order, which is used during control of the component mounting device when mounting the component on the board.

The server device 10 collects and registers the component data provided by the first terminal device by prompting the first terminal device which is one of the terminal devices 20 to provide the component data. Then, the server device 10 provides the registered component data to a second terminal device different from the first terminal device. The second terminal device receives the component data provided from the server device 10 and uses the received component data. In this way, the server device 10 distributes the component data.

Therefore, the server device 10 functions as a component data distribution device that distributes component data, and also functions as a component providing device that provides component data to the second terminal device. The first terminal device serves as component data providing means for providing component data to the server device 10 . The second terminal device functions as component data receiving means for receiving component data from the server device 10 .

During distribution of component data, for example, terminal device 20 of factory A-1 of company A transmits component data generated by terminal device 20 together with evaluation data to server device 10 of a service location, and server device 10 receives and newly registers the component data.

Evaluation data indicates the degree to which operations required for actual production are realized using component data. That is, evaluation data is an indicator of what is lacking in current component data and what is needed in, for example, adjustment operations to improve the current component data to a level that achieves good product manufacturing.

At this time, the terminal device 20 is allowed to transmit the component data indicated by the evaluation data to the server device 10 in order to require the operation to successfully manufacture a good product and realize actual production.

The component data newly registered in the server device 10 is acquired by the component installation device of the factory A-2 of the company A, supplemented and adjusted according to the evaluation to manufacture a good product, and then together with the new evaluation data after successfully manufacturing a good product is sent to the server device 10. The server device 10 updates the registration of the component data after adjustment.

The adjusted component data whose registration is updated in the server device 10 is acquired by the component mounting device of the factory B-1 of the company B and directly used to manufacture a superior product.

Providers of component data are rewarded according to evaluation, thereby promoting new registration and updated registration of component data. The rewards awarded are associated with the provider of the component data and accumulated in the server device 10 .

<Configuration of server device and terminal device>

FIG. 2 is a block diagram of a configuration example showing the functions of the server device 10 and the terminal device 20 . FIG. 2 also shows a network 30 connecting the server device 10 and the terminal device 20 .

The server device 10 collects component data and corresponding evaluation data from the terminal device 20, and provides the collected component data to one of the terminal devices 20. The server device 10 is composed of a component data storage unit 11, a component data supply unit 12, a communication An I/F (Interface) unit 13 , a component data acquisition unit 14 , an award determination unit 15 and an award accumulation unit 16 are constituted. The component data supply unit 12 includes a retrieval unit 121 and a usage data storage unit 122 .

The component data acquisition unit 14 receives component data and corresponding evaluation data from the terminal device 20 , and stores the received component data and evaluation data in the component data storage unit 11 .

When the retrieval unit 121 receives a retrieval condition specifying a component name from the terminal device 20 , the retrieval unit 121 retrieves one or more pieces of component data matching the received retrieval condition from the component data storage unit 11 . It sends to the terminal device 20 a detection result including the component name, the model name of the component mounting device, and corresponding evaluation data as an identification key of the retrieved component data.

When the component data supply unit 12 receives an acquisition request specifying one or more identification keywords included in the detection result from the terminal device 20, the component data supply unit 12 provides the terminal device 20 with the component identified by the identification keyword data.

When the usage data storage unit 122 provides component data and receives a complaint (complaint) about the component data from the terminal device 20, the usage data storage unit 122 updates the usage data stored in the component data storage unit 11, and the usage data represents usage of the component. The number of data and the number of complaints occurred. Complaints about component data are information related to problems that occur due to insufficient component data, such as information that a component is mounted according to the component data, but cannot be picked up to the mounting head with suction or picked up with suction during the transport. Components fall from the mounting head during assembly.

The reward determination unit 15 determines a reward based on evaluation data and use data corresponding to the component data stored in the component data storage unit 11, associates the determined reward with a provider of the component data and accumulates the resulting data in the reward accumulation unit 16 .

Note that there can be multiple component data providers for a component name. For example, if multiple suppliers provide complete component data in a staged manner for good product manufacture (e.g. a first supplier provides shape data, a second augments the fit data, and a third refines the fit data until conducting the trial production phase and realizing the actual production phase, etc.), then the rewards are accumulated in the reward accumulation unit 16 by associating the data with the corresponding provider.

The communication I/F unit 13 communicates data with the terminal device 20 via the network 30 .

The terminal device 20 provides the server device 10 with component data and acquires and uses the component data already registered in the server device 10 . As an example of implementing this device as a component mounting device, it consists of a mounting control unit 21, an operator I/F unit 22, a component data storage unit 23, a communication I/F unit 24, a mounting mechanism unit 25, a component data input unit 26, The evaluation determination unit 27 and the component data registration unit 28 constitute the means. The installation control unit 21 includes a component data acquisition unit 211 and a complaint transmission unit 212 .

The mounting control unit 21 controls the mounting mechanism unit 25 using the component data stored in the component data storage unit 23 and mounts the components on the board.

The mounting mechanism unit 25 is made of, for example, a pallet, a component providing unit, a mounting head, and a camera. The pallet is used to place a board, and the component providing unit is used to provide each component by storing a component storage tape (storage tape) for a plurality of components. The head picks up the component with suction, transports it to the target location and installs the component there, and the camera is used to recognize the state of the component when it is picked up with suction. Since the mounting mechanism unit 25 is not the subject of the present invention, it is assumed to be realized using conventional techniques and its detailed description is omitted here.

When loading the component storage tape, the component providing unit performs a collation process, reads the component name from the barcode or IC tag attached to the component storage tape and notifies the mount control unit 21 of the read component name.

If the component data storage unit 23 does not store the component data identified by the notified component name and the model name of the component mounting device itself, and indicating that actual production has been realized by the evaluation data, the component data acquisition unit 211 sends an indication to the server device 10. Search conditions for component names. Then, it acquires the component name of the identification key of the component data matching the retrieval condition and the model name of the component mounting device and the corresponding evaluation data from the server device 10 and displays the data on the operator I/F unit 22 .

The operator I/F unit 22 may be, for example, a liquid crystal display attached to the frame of the component mounting device, a touch panel and a keyboard mounted on the front surface of the liquid crystal display, or the like.

The component data acquiring unit 211 accepts the operation of selecting component data according to the evaluation by the operator I/F unit 22, and transmits an activation request including the identification key of the selected component data to the server device 10, thereby acquiring the component data identified by the identification key. and store the component data in the component data storage unit 23.

When the component data input unit 26 has not retrieved component data from the server device 10 at all or has not obtained component data with sufficient evaluation, the component data input unit 26 operates to newly generate components based on the input received through the operator I/F unit 22 data or complement and correct component data. The newly generated component data or the supplemented or corrected component data is stored in the component data storage unit 23 .

The installation control unit 21 uses the component data stored in the component data storage unit 23 to perform trial production and actual production. The component data input unit 26 also performs rough adjustment and fine adjustment of component data in accordance with input operations received through the operator I/F unit 22 at the start of trial production and actual production.

The evaluation determination unit 27 determines evaluation data according to the state of the component data and stores the data in the component data storage unit 23 . The evaluation determination unit 27 redetermines the evaluation data and updates the component data storage unit 23 according to the state change of the component data. The following describes a practical example of realizing operations required for actual production according to the state of component data and details of evaluation data.

When determining and updating the evaluation data of the component data, the component data registration unit 28 notifies the operator I/F unit 22 of the promotion of registering the component data in the server device 10, and registers the component in the server device 10 according to the operator's response operation data and the corresponding evaluation data.

<component data>

The component data is described in detail below.

Figure 3 is a top view showing an example of components. The body of the assembly viewed from above is rectangular with leads extending from opposite sides to the outside. The shapes of all components sharing these features are determined using the same metric term as shown in Figure 3.

4A and 4B show examples of component data stored in component data storage unit 11 of server device 10 and component data storage unit 23 of terminal device 20, and show examples related to components shown in FIG.

FIG. 4A shows a common part 110 of component data regardless of component mounting device models, and shows shape data representing measurements of components as an example. A component has a common part.

The shape type indicates the characteristic shape of the component, and each item of shape data shows the measure of each part appearing in the top view of the component shown in FIG. 3 . It is also conceivable to assign all components whose shape is determined by the same measure into the same shape type.

FIG. 4B shows a model-related part 111 of component data depending on the model of the component installation device, for example, installation data for device conditions to minimize errors during installation of components, indicating the use of the number of times of use of the component data and the number of occurrences of complaints. data, and operation data representing the number of installation trial operations and the number of successful operations of the component mounting device. A component may have a model dependent portion of the component mounting device model number applied to the component mounting device.

Evaluation data are recorded in the model-specific section.

In the installation data, identified parts are identified as references for detecting components not being picked to the correct location. Illumination 1 and 2 determine the optimum illumination intensity for identifying components, and the suction nozzle and transport acceleration determine the optimum conditions for the mounting head to pick up with suction and transport the components, respectively.

Items of operation data may be omitted in the component data storage unit 11 , and items of use data may be omitted in the component data storage unit 23 .

FIG. 5 shows an example of an image of a recognition portion. The image of the identification portion R11 shown in this example determines the position of the lead shown on the image taken when the mounting head picks up the component shown in FIG. 3 with suction, based on the reference.

Detects the misalignment between the lead wires displayed on the image obtained by actual shooting and the lead wires displayed on the image of the identified part as failure to pick up the component to the correct position by suction, and it is possible to make mounting errors by correcting the detected misalignment minimize.

<review data>

The evaluation data will be described in detail below.

6A and 6B are explanatory diagrams of evaluation data.

FIG. 6A shows an example of the operation necessary item table 150 . The operation necessity table 150 is a matrix indicating whether each operation is necessary when the component data of the corresponding stage is used in a plurality of stages performing multiple common operations on the component data to realize the evaluation of the component data during actual production. Each row of the operation necessary item table 150 shows operations such as "generate shape data", "generate installation data", and the like. Each column shows the stages of "no component data", "shape data available", etc. Each intersection of row and column is marked with "○" to indicate that the operation is still required when using the component data of that stage, and marked with "×" to indicate that the operation is not required.

For example, the intersection of the row "Generate shape data" and the column "No component data" is marked with ○, which means that when the evaluation of component data is at a stage where there is no component data at all (even if shape data has been provided), " Generate shape data" operation.

The intersection of the "generated shape data" row and the "shape data available" column is marked with an X, which indicates that when the evaluation of the component data is in the stage where the shape data has been generated, the operation of "generate shape data" is not required to use the component data.

The operation necessity table 150 shows cost values representing the complexity and difficulty of each operation. As described below, the cost value is reflected by the reward for providing component data.

In this operation, there are four practical examples of the above-mentioned operations, namely, shape data generation operation (component data common to the mounting device model), mounting data (model-related part) generating operation, mounting data coarse adjustment in trial production operation, as well as the installation data fine-tuning operation in actual production. For example, set the cost value of each operation to 10, 30, 50, and 10 respectively. In practice, the stages of evaluation are set into five types, ie, no component data, available shape data, available installation data, successful trial production, and successful actual production.

In the stage where there is no component data, all operations after shape data generation are required in order to realize actual production using component data. In the stage where there is only shape data, operations after installation data generation are required. At the stage where the installation data is available, an operation after the installation data coarse adjustment operation in the trial production is required. In the stage of successful trial production, the installation data in actual production is required for fine-tuning operations. At the stage of successful actual production, no action is required.

The operation necessary item table 150 is used to describe the embodiment of the present invention, and it is not always necessary to provide the operation necessary item table 150 to the server device 10 and the terminal device 20 .

FIG. 6B shows an example of the evaluation table 151 . The evaluation table 151 stores different stage values and bonus points according to the above five evaluation stages. The bonus point represents the total cost value of operations (in FIG. 6A , operations denoted as unnecessary (×) in each stage (column)) that are not required on the operation necessity table 150 according to stage assumptions in practice.

This total value represents the level of complexity and difficulty of the operations assumed to have been assigned to the component data before the component data evaluation reached the current stage, and represents an actual example of the reward value. The higher the total value, that is, the higher the stage value of the evaluation, the lower the degree of using the component data to realize the necessary operations for actual production.

The evaluation table 151 is provided for the award determination unit 15 of the server device 10 .

Preferably, the higher the difficulty or the higher the complexity of generating the component data, the higher the above-mentioned reward point is set. Therefore, for example, when considering the relationship between the difficulty or complexity of generating component data and the component shape, a plurality of evaluation tables 151 are provided for determining different bonus points for a plurality of shape types representing different component shapes, and The bonus points may be determined from the evaluation table corresponding to the shape type of the component data.

FIG. 7A shows an example of components where generating component data is difficult. FIG. 7B shows an example of the component recognizing a partial image. Assign this component to a shape type different from that of the component shown in FIG. 3 . As a common example, components with a circular body are assigned a higher level of difficulty, since parts that can detect angular offsets with high accuracy cannot be easily provided, and components with a larger number of leads are also more complex.

<reward data>

The bonus data is described in detail below.

FIG. 8 shows an example of the reward table 160 . The reward table 160 is provided for the reward accumulation unit 16 of the server device 10 .

The incentive table 160 has records of new registration and updated registration of component data, each registration date and time, provider of component data, component name and model name of component mounting device as identification key of component data, evaluation data before and after registration And reward points fed back to the provider as reward data.

In addition, the reward table 160 has a record of acquired component data, each acquisition date and time, the acquirer of the component data, the component name and the model name of the component installation device as the identification key of the component data, the evaluation data at the time of acquisition, and the evaluation data for the acquisition. The point collected by the operator (that is, the usage fee) is used as the collection data.

Records of reward data and collection data on the reward form 160 are generated by the reward determination unit 15 .

The actual contents of the reward data and collection data stored in the reward table 160 will be described below by referring to the third and fourth rows shown in FIG. 8 as an example.

When reward data with an evaluation stage value of "1" has been registered (the evaluation before registration is "1"), the reward data in the third line is recorded, and the terminal device 20 registers the evaluation stage value "3" in the server device 10 The component data for (the rating after the rating is "3").

Before and after registration, the bonus point corresponding to the component data evaluation increases from "10" to "90" (refer to FIG. 6B ). Therefore, the bonus determination unit 15 determines the increment "80" as the bonus point of the provider "C3" and records it as bonus data.

When the terminal device 20 acquires component data with an evaluation stage value of "4" from the server device 10 (evaluation at the time of registration is "4"), collection data of the fourth line is recorded.

Since the reward point corresponding to the evaluation of the acquired component data is "100" (refer to FIG. 6B ), the reward determination unit 15 determines the reward point "100" as the collection point of the acquirer "C4" and records it as collection. data.

By referring to the reward table 160, the accumulation of reward points given to the provider is calculated for each provider, and the collection of collection points for the acquirer is calculated for each acquirer.

Considering that component data is generally acquired and used by multiple acquirers, the point that each acquirer needs to pay can be the actual usage fee that is obtained by multiplying the collection point by a predetermined (a few percent) rate.

<Detailed operation of the server device>

The operation of the server device 10 is described in detail below with reference to flowcharts.

FIG. 9 is a flowchart showing detailed operations of the server device 10 . This flowchart shows important operations taken by the server device 10 in order to process each request related to component data from the terminal device 20 .

The server device 10 repeats the following process until an operation termination instruction is received (NO in S401).

Data is received from the terminal device 20 (S402) and branched according to the content of the received data (S403).

When the retrieval condition is received (retrieval condition in S403), the retrieval unit 121 detects one or more component data matching the retrieval condition received from the component data storage unit 11, and sends it to the terminal device 20 as the retrieved component data The component name and component installation device model name of the identification keyword and the detection result including the corresponding evaluation data (S412).

If there is no component data matching the retrieval condition, for example, the retrieval unit 121 includes component data of other components having a similar component name of the same manufacturer and component data matching in shape type in the detection result, thereby extending the retrieval in a staged manner. range. In addition, component data for components with matching or similar shape types from other manufacturers can also be included in the scope of the search. Obtaining component data for similar components from multiple manufacturers as test results may be useful in the process of rapidly obtaining component data when substituting similar components from other manufacturers for out-of-stock components.

Upon receiving the component data acquisition request specifying the component name and the component mounting device model name as the component data identification key (component data acquisition request in S403), the component data supply unit 12 acquires from the component data storage unit 11 the The received component data identified by the identification key included in the acquisition request is sent to the terminal device 20 (S421). At this time, the component data storage unit 11 increases the usage count of the component data identified by the identification key (S422).

The reward determination unit 15 refers to the evaluation table shown in FIG. 6B, and determines reward points corresponding to the evaluation of the transmitted component data as collection points related to the acquired component data (S423).

The award determination unit 15 records the date and time of acquisition, the acquirer of the component data, the component name and the model name of the component installation device as the component data identification key, evaluation data at the time of acquisition, and collection by the acquirer in the award accumulation unit 16. point (S424). At this time, the component data supply unit 12 calculates the usage fee of the component data based on the collection point recorded in the bonus accumulating unit 16, and sends a message to the terminal device 20 informing it to pay the calculated usage fee.

When receiving a component data registration request including component data and evaluation data (component data retrieval request in S403), the component data acquisition unit 14 stores the component data included in the received component data registration request in the component data storage unit 11 and evaluation data (S431).

The reward determination unit 15 refers to the evaluation table shown in FIG. 6B, and determines the difference between the reward points corresponding to the evaluation of the component data before storage and the reward points corresponding to the evaluation of the component data after storage as the value associated with the registered component data. Bonus points (S432). For example, in the determination process, when there is component data with a matching component name but a mismatching component mounting device model name (that is, corresponding to another model of component mounting device) before storing the component data, the component pair has been registered. Common shape data for different types of component mounting devices. Therefore, set the evaluation to 1 before storing.

If other component data similar to the registered component data have been stored in the component data storage unit 11 when the component data is registered (that is, other similar component data have been collected), especially before the storage, the evaluation of the similar component data is in a position higher than that of the registered component data. At an earlier stage of the evaluation of component data (including a stage where no component data exists), the bonus determination unit 15 may determine the bonus point to be lower than the case where no similar component data exists.

In practice, similar component data refers to component data of other components with similar component names from the same manufacturer, component data of another manufacturer's components that can replace the component, component data of matching shape types, identical names but Compatible with component data and the like that differ from model to component mounting device.

The above is based on the principle that when similar component data already exists, the operation of generating component data to be registered can be performed more easily with reference to similar component data, thereby reducing the actual reward value associated with generating component data.

The bonus determination unit 15 records the date and time of registration, the supplier of the component data, the component name and the model name of the component installation device as a component data identification key, evaluation data before and after registration, and bonus points given to the supplier in the bonus accumulation unit 16 (S433).

Upon receiving the complaint specifying the component name and component mounting device model name as the identification key of the component data (complaint in S403), the usage data storage unit 122 of the component data supply unit 12 increments the component data storage unit 11 The number of complaint occurrences of the component data identified by the identification keyword (S441).

A case is also considered in which bonus points can be given not only immediately after registration but also after usage data including the number of times of use and the number of occurrences of complaints has been collected to some extent. In this case, for example, evaluation data belonging to a higher stage may be used if the number of times of use exceeds a predetermined threshold, and evaluation data belonging to a lower stage may be used if the number of occurrences of complaints exceeds a predetermined threshold.

As a variation, for example, when the number of uses exceeds a predetermined threshold by increasing the number of uses in step S422, a predetermined positive reward point may be given to the provider of the component data, and when the number of complaints is increased due to an increase in the number of complaints in step S441 And when the number of times of complaints exceeds a predetermined threshold, predetermined negative reward points may be given to the component data provider.

Furthermore, the component data provision unit 12 may transmit the component data to the terminal device 20 free of charge in step S421. Thus, free provision of component data may be attractive to users, and the advantages of introducing component mounting devices may be attractive to potential customers, thereby improving sales of the component mounting devices.

<Detailed operation of the terminal device>

The operation of the terminal device 20 is described in detail below with reference to flowcharts and screen display examples.

FIG. 10 is a flowchart showing detailed operations of the terminal device 20. As shown in FIG. As an example of implementing the terminal device 20 as a component mounting device, this flowchart shows important operations related to component data from preparing for production to realizing actual production.

The terminal device 20 starts preparing for production, including preparation of component data and NC data (S101). For each component to be mounted on the board, each piece of component data is prepared by repeating the process up to S113 (S102).

The component providing unit of the mounting mechanism unit 25 automatically reads the component name from the component storage reel or reads the component name through an operator's operation (S103). The installation control unit 21 retrieves from the component data storage unit 23 the component data identified by the read component name and component mounting device model name, in which actual production is represented by the evaluation data. In a case where there is no matching component data (No in S104), a retrieval condition specifying a component name is sent to the server device 10 (S105). The installation control unit 21 displays the retrieval result returned from the server device 10 on the operator I/F unit 22 (S106).

Fig. 11 shows an example of a search result display screen. In the display at the upper part of the screen, the component name related to the component data is P1, the shape type of the component is T1, and the model name of the component mounting device is M1. The component data matching the component name and component mounting device model name has only evaluation 2 (mounting data without trial production records). As a result of expanding the retrieval range in the server device 10, there are retrieval results including component data with an evaluation of 4 (with an actual production record), component data that match in component name but mismatch in component mounting device model name, and component data that match in shape type but not in component mounting device model name. Component data with component name mismatch. As a result of the search, an acquire button accepting an instruction to acquire component data and a new create button accepting an instruction to newly create component data are shown.

When the acquire button is touched (YES in S107), the installation control unit 21 acquires the corresponding component data from the server device 10 and stores it in the component data storage unit 23 (S108).

At this time, the component data supply unit 12 in the server device 10 instructs the terminal device 20 to pay the usage fee for the component data, and the terminal device 20 transmits information for the instructed payment of the usage fee to the server device 10, thereby performing the payment of the usage fee . As described above, the usage fee of the component data is calculated by multiplying the collection point recorded when the component data is transmitted by the predetermined rate in the server device 10 .

The server device 10 may not issue a component data usage fee payment instruction every time the component data is acquired, but periodically issue an instruction based on the accumulation of reward points recorded in the cycle, for example, once a month. At this time, when the same user provides the component data, the usage fee may also be calculated based on the offset of the collection point collected from the reward point related to the provision.

The component data input unit 26 supplements or modifies the acquired component data according to the operator's input operation, and updates the component data stored in the component data storage unit 23 with the supplemented or modified component data (S109).

On the other hand, when the new generation button is touched (No in S107), the component data input unit 26 newly generates component data according to the operator's input operation and stores the newly generated component data in the component data storage unit 23 (S110).

Fig. 12 shows an example of a shape data input screen. The operator inputs a value for each item of shape data displayed on the screen through keyboard operation, and when the OK button is touched, the newly generated, supplemented or modified content of the shape data is reflected in the component data storage unit 23 .

Figure 13 shows an example of an installation data entry screen. The operator inputs a value for each item of installation data displayed on the screen through keyboard operation, and when the determination button is touched, the newly generated, supplemented or modified content of shape data is reflected in the component data storage unit 23 .

An image of the identified portion is generated from a component image photographed by the camera of the mounting mechanism unit 25, and a photographing process is performed by touching a photographing button. As another example, an image of the identified part may also be generated based on a part of the image read by an external scanning device, and obtained by the terminal device 20 .

By touching the determination button, the newly generated or supplemented and modified content is reflected by the component data storage unit 23, and the evaluation determination unit 27 determines the evaluation data, if the shape data of all items are input, the evaluation data indicates that the shape data is available, and if the input If the installation data of all the items are found, the evaluation data indicates that the installation data is available, and then the data is recorded in the component data storage unit 23 (S111).

The component data registration unit 28 displays on the operator I/F unit 22 the contents of a report that facilitates the registration of component data in the server device 10 .

Fig. 14 shows an example of a component data registration prompt screen. The determined evaluation data is displayed, and currently accumulated bonus points and bonus points obtained by registration are displayed to facilitate the operator to perform the registration operation of the component data.

When the register button is touched, the component data registration unit 28 registers the component data and the corresponding evaluation data in the server device 10 (S112).

If all necessary component data preparations are performed from step S102 to step S113 in the loop process, the mounting control unit 21 controls the mounting mechanism unit 25 to perform trial production (S201). At this time, the installation control unit 21 records the number of trial installation operations and the number of successful installation operations in the component data storage unit 23 .

For example, if the condition that the number of successful installation operations is not less than 20 or that the successful installation rate is not higher than 80% is satisfied, it is determined that the installation rate is low ("Yes" in S202), and the complaint sending unit 212 is displayed on the operator I/F A content screen indicating whether to send a complaint is displayed on the unit 22 . Generally, the sending of the complaint is performed when the component data acquired in step S108 has not been successfully functioned. However, if the component data generated by the user in step S110 and registered in step S112 do not function successfully, the problem may also be reported by the user.

Figure 15 shows an example of a complaint sending confirmation screen. Display the recorded number of trial installation operations, number of successful installation operations, successful installation rate, etc. and display a button indicating whether to accept complaints.

When this button is touched, the complaint transmission unit 212 transmits complaint data related to the component data to the server device 10 (S203). If the button for sending or not sending the complaint data is touched, the component data input unit 26 displays the input screen shown in FIGS. 12 and 13 on the operator I/F unit 22, and accepts the revised content of the installation data. After the component data has been substantially modified on the input screen (S204), the trial production is performed again.

If it is determined in the trial production that there is no component with a low successful mounting rate (NO in S202), the evaluation determination unit 27 again determines that the evaluation of the component data involves successful trial production, and updates the component data storage unit 23 (S206).

The component data registration unit 28 again determines the evaluation of the component data registration prompt screen shown in FIG. 14 as successful trial production, and displays it on the operator I/F unit 22 . When the register button is touched, the component data registration unit 28 registers the component data and the corresponding evaluation data in the server device 10 (S206).

For the sake of clarity, the explanation given above is to update the evaluation and register component data after all components have achieved a satisfactory successful installation rate. However, although there are still components with a low successful mounting rate, the components reaching a satisfactory successful mounting rate can be sequentially registered, and the evaluation of the component data is regarded as a successful trial production.

After successful trial production, the installation control unit 21 controls the installation mechanism unit 25 to implement actual production (S301). At this time, the mounting control unit 21 judges whether a predetermined amount of actual production has been successfully performed by counting the number of times of successful production of the board (S302). If it is determined that board production has not been performed a predetermined number of times (No in S302), a complaint is sent according to the operator's operation as described above (S303), and component data is fine-tuned (S304), and actual production is continued.

When determining that the actual production of the board has been successfully performed a predetermined number of times (YES in S302), the evaluation determination unit 27 again determines the evaluation of the component data as successful actual production and updates the component data storage unit 23 (S305).

The component data registration unit 28 displays a registration prompt screen of component data shown in FIG. 14 on the operator I/F unit 22, and its evaluation is regarded as successful actual production. When the register button is touched, the component data registration unit 28 registers the component data and the corresponding evaluation data in the server device 10 (S306).

Also in this case, although a predetermined number of board productions are not successfully performed, fine components that do not interfere with successful production can be sequentially registered, that is, only boards that are correctly mounted on a predetermined number of boards are sequentially registered, and the evaluation of the component data is regarded as For successful actual production, as described above.

In the description so far, the terminal device 20 is realized as a component mounting device, but the present invention is not limited to this application. That is, the terminal device 20 may be a computer independently connected from the component mounting device via a communication circuit. In this case, the component data acquired by the terminal device 20 is sent to the component mounting device through the communication circuit and used during component mounting, and information on trial production or actual production status may be transmitted to the terminal device 20 through the communication circuit.

In the description so far, the server device 10 is a computer located at a service location of a component mounting device manufacturer that provides a service to facilitate communication between customers through the server device 10, that is, between customers of the component mounting device. Distribute component data among users. However, the service provider does not necessarily have to be the manufacturer of the component mounting device.

For example, in a manufacturer having multiple factories and operating multiple component mounting devices, its production support division may operate the server device 10 to conduct the above-mentioned business throughout the company.

In this case, for example, a main server can be provided in the production support branch, and an intermediate server implemented as a systematized distributed database can be provided for each plant. If each component mounting device acquires component data from an intermediate server in each factory that owns the component mounting device, then server device calculation complexity, communication traffic, and data volume of the component library can be appropriately distributed. The systematized distributed database itself can be configured using known techniques.

<Summary>

As described above, according to the component data distribution method and the component data providing method of the present invention, component data having no manufacturing good product record and having operations necessary for actual production can be distributed with evaluation data indicating operations. Therefore, the user of the component mounting apparatus can check the evaluation data and judge whether the component data can be used immediately, how much adjustment of the component mounting apparatus is required, and the like. Therefore, the distribution of component data can be stimulated, and the component data can be rapidly improved to a level at which excellent products can be manufactured using the component data. The provision of component data can be facilitated by rewarding based on ratings and usage.

Then, since the server device as a component data distribution device collects and distributes component data having various rank evaluations, the number of opportunities for the component mounting device to acquire available component data increases. When the operator acquires component data, the operator can select and acquire component data with necessary ratings by confirming the ratings of the component data to be acquired.

As a result, operations for adjusting component data by trial and error and operations for improving component data by analyzing problems can be reduced. Thus, it is possible to optimize the production resources required from the experimental steps to the manufacture of a good product. The optimization of production resources corresponds to, for example, a reduction in the number of operator work steps, electrical energy, fuel, water, sample material, etc.

In addition, using component data with desired evaluation (ie, data that has been carefully inspected and completed at a high level) acquired from the server device in the component mounting device, the quality of products manufactured in the manufacturing good product step can be improved. As a result, the power consumption required by the product itself is reduced and the lifespan is extended, thereby contributing to energy and resource conservation required by society.

<supplement>

The component data distribution system according to the present invention has been described above, but the present invention is not limited to the above-described embodiments of the present invention. Within the scope of the gist of the present invention, various changes to the use of the embodiments of the present invention that would occur to those skilled in the art are included in the scope of the present invention.

For example, in the embodiment of the present invention, users to whom the registered (provided) component data is disclosed are not limited. However, the present invention is not limited to this application, and for the component data generated by the provider and registered in the server apparatus 10, the following restrictions may be imposed on users to whom the component data is disclosed.

That is, when each user enters into an agreement to participate in the component data distribution system, the user group to which the user belongs is recorded. When a user searches for component data, component names of component data registered by another user in a user group different from the above user's group are excluded from detection results. The disclosure restriction of component data may be indicated for each component name, or may be indicated with a list of user groups that are allowed to be disclosed.

For example, as a practical configuration, a user group table is provided in the server device 10, and user names are stored in advance in the user group table. A user group table is stored in which user group names are associated with user names included in the user group. A user group refers to, for example, a group of groups having arbitrary relationships with related companies or the like.

The terminal device 20 accepts from the provider of the component data an operation of specifying the disclosure range of the component data generated by the provider of the component data for each component name. The provider of component data does not indicate any limitation on the disclosure range of component data that does not think that it will cause much trouble during the generation of data according to the shape of the component, but it is possible to disclose the data of components that cause much trouble during generation (such as multi-pin components, etc.) The visibility of the indicates a limit.

The terminal device 20 transmits to the server device 10 component data having information on the disclosure range specified by the provider. The server device 10 records component data having information on the disclosure range in the component data storage unit 11 .

When the retrieval unit 121 receives the retrieval condition from the terminal device 20, if the data is registered by a user in a user group different from the user who issued the retrieval condition, the retrieval unit excludes the disclosure range restriction information of the component name from the retrieval result record component data.

Since the component data excluded from the search result is not displayed on the terminal device 20, acquisition of the component data cannot be requested from the terminal device 20. As a result, a component data providing step of providing component data only to users within the range set by the provider of the component data is realized.

The user group is not only used to limit the scope of component data disclosure, but also used in the process of determining the component data usage fee to be collected when the component data is acquired.

In the embodiment of the present invention, it is described that the acquired points are determined by multiplying the collection point by a predetermined rate. For example, when a user acquiring component data belongs to a user group different from that of a provider of the component data, a higher rate can be set than when they belong to the same group.

With the above configuration, the provider of component data is prohibited from disclosing component data to users in different user groups, but can obtain higher fees from users in different user groups.

The component data distribution device according to the present invention can also be realized as a computer system.

In this case, a computer system for realizing a component data distribution system according to the present invention includes a CPU, a ROM storing a program for determining a flow of component data used by a component mounting device when mounting a component on a board, storing A RAM for working data, a mass storage unit and a communication unit for communicating with the component data providing means and the component data receiving means. Under the control of the CPU that executes the program stored in the ROM using the RAM, the communication unit can receive the component data from the component data providing device and the evaluation data indicating the degree of operation necessary for actual production using the component data, mass storage The unit may accumulate the received component data with the received evaluation data to provide the received component data to the component data providing means.

With the above configuration, the component data distribution device can be realized as a computer system operating under the control of predetermined software.

Industrial Applicability

The component data distribution method according to the present invention can be used for a server device provided at a service location of a component installation device and a factory in which the component installation device is installed, and the component data providing method can be used for the component installation device itself.

Claims (10)

1. A component data distribution method performed by a component data distribution device and allowing distribution of component data used by a component mounting apparatus when mounting a component on a board, the method comprising: collecting component data from the component data providing means and evaluation data indicating the degree to which operations necessary for actual production are realized using the component data; and The collected component data with the collected evaluation data is accumulated to provide the collected component data to a component data receiving device. 2. The component data distribution method according to claim 1, wherein the component data includes a portion common to a plurality of component mounting apparatuses and a plurality of portions individualized to the plurality of component mounting apparatuses; and In the collecting, the collected component data has a plurality of pieces of evaluation data individualized for the plurality of component mounting devices. 3. The component data distribution method according to claim 1, further comprising The reward is determined by judging operations necessary to realize the actual production based on the content indicated by the evaluation data. 4. The component data distribution method according to claim 1, wherein said component data providing means is implemented as said component installing means; and In the collection, the component data distribution device collects the component data having the production record in the component mounting device by issuing a notification to the component mounting device to facilitate provision of the component data having the production record. 5. The component data distribution method according to claim 1, further comprising: When the retrieval condition is provided from the component data receiving device, one or more pieces of component data are retrieved from the collected component data according to the provided retrieval condition, and the retrieval result is sent to the component data receiving device, the The search results include a component name and corresponding rating data indicating each piece of component data retrieved; and When said component data receiving means provides an acquisition request with one or more component names included and specified in said retrieval result, said component data receiving means is provided with component data specified by a given component name. 6. The component data distribution method according to claim 1, wherein said component data receiving means is realized as said component installing means; The component data distribution method also includes The component data is provided to the component installation device in accordance with an acquisition request sent from the component installation device when the component is checked. 7. The component data distribution method according to claim 1, further comprising When the collected component data is supplied to the component data receiving means, a royalty payment instruction is notified to the component data receiving means based on the collected evaluation data of the collected component data. 8. The component data distribution method according to claim 1, further comprising The collected component data is provided only to users within a range set by a provider of the component data. 9. A component data distribution device that supports distribution of component data used in a component mounting device when mounting components on a board, the device comprising: a component data acquisition unit for acquiring component data from the component data providing means and evaluation data indicating the degree to which operations necessary for actual production are realized using the component data; and A component data accumulation unit for accumulating the collected component data with the collected evaluation data to provide the collected component data to the component data receiving means. 10. A program for causing a computer to execute acquisition and accumulation processes included in a component data distribution method executed by a component data distribution device and allowing distribution to be used by a component mounting apparatus when mounting a component on a board component data, The methods described therein include: performing said collection of component data and evaluation data indicating the degree to which operations necessary for actual production are realized using said component data from a component data providing means; and The accumulating is performed on the collected component data with the collected evaluation data to provide the collected component data to a component data receiving device.

Images